[Kernel-packages] [Bug 2018420] Re: linux kerkel 6.2.0.20-generic failed to install
** Project changed: launchpad => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018420 Title: linux kerkel 6.2.0.20-generic failed to install Status in linux package in Ubuntu: New Bug description: Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ... Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: error processing package linux-headers-6.2.0-20-generic (--configure): installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-generic: linux-headers-generic depends on linux-headers-6.2.0-20-generic; however: Package linux-headers-6.2.0-20-generic is not configured yet. dpkg: error processing package linux-headers-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however: Package linux-headers-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.37-0ubuntu2) ... No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. Processing triggers for man-db (2.11.2-1) ... Processing triggers for mailcap (3.70+nmu1ubuntu1) ... Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for desktop-file-utils (0.26-1ubuntu5) ... Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ... Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/vhba-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.2.0-20-generic (--configure): installed linux-image-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 No apport report written because MaxReports is reached already Errors were encountered while processing: linux-headers-6.2.0-20-generic linux-headers-generic linux-generic linux-image-6.2.0-20-generic E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2014037] Re: ACPI bios error on dell laptop.
** Project changed: launchpad => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2014037 Title: ACPI bios error on dell laptop. Status in linux package in Ubuntu: New Bug description: Identified a bug ACPI bios error on dell laptop. In kernel version 5.14.0-1058-oem no existing a bug, after update kernel to 5.15.0-67-generic or 5.15.0-69-generic the bug is throwed. Ubuntu version used is a 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2014037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007308] Re: linux-tools-common: bpftool wrapper causes build failure for xdp-tools
We plan to switch the buildd host system from Ubuntu 20.04 to 22.04 fairly soon, which would result in using a 5.15 kernel instead of 5.4. Would that be enough to fix this problem? ** Project changed: launchpad => launchpad-buildd -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007308 Title: linux-tools-common: bpftool wrapper causes build failure for xdp-tools Status in launchpad-buildd: New Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: New Bug description: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: linux-restricted-modules-5.4.0-139-generic N/A linux-backports-modules-5.4.0-139-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/2007308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 283316] Re: CD-ROM tray closes automatically after eject
** Changed in: ubuntu-release-notes Assignee: Colin Watson (cjwatson) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/283316 Title: CD-ROM tray closes automatically after eject Status in Linux: Invalid Status in Release Notes for Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in udev package in Ubuntu: Fix Released Status in linux source package in Intrepid: Invalid Status in udev source package in Intrepid: Fix Released Status in udev package in Fedora: Won't Fix Status in Gentoo Linux: Fix Released Bug description: Binary package hint: hal Ubuntu intrepid ibex beta (updated) Problem: When I try to eject a cd/dvd, Ubuntu intrepid inserts the cdrom right back in the cd/dvd drive Steps to reproduce: 1) Either by pressing eject button on the device or using the "eject" command or using the eject icon in nautilus sidebar 2) The dvd is ejected successfully 3) The dvd is loaded back in right after being ejected. This happens after the message "eject: CD-ROM eject command succeeded" of "eject -v" command. Note 1: The cd/dvd-rw drive is a SATA device Note 2: This happens while in tty and ubuntu gnome desktop manager $ apt-cache policy eject hal eject: Installed: 2.1.5-9ubuntu2 Candidate: 2.1.5-9ubuntu2 Version table: *** 2.1.5-9ubuntu2 0 500 http://archive.ubuntu.com intrepid/main Packages 100 /var/lib/dpkg/status hal: Installed: 0.5.11-4ubuntu2 Candidate: 0.5.11-4ubuntu2 Version table: *** 0.5.11-4ubuntu2 0 500 http://archive.ubuntu.com intrepid/main Packages 100 /var/lib/dpkg/status $ eject -v eject: using default device `cdrom' eject: device name is `cdrom' eject: expanded name is `/dev/cdrom' eject: `/dev/cdrom' is a link to `/dev/scd0' eject: `/dev/scd0' is mounted at `/media/cdrom0' eject: unmounting device `/dev/scd0' from `/media/cdrom0' eject: `/dev/scd0' is not a multipartition device eject: trying to eject `/dev/scd0' using CD-ROM eject command eject: CD-ROM eject command succeeded $ sudo lshw -C disk [...] *-cdrom description: DVD-RAM writer product: DVD-RW DVR-212 vendor: PIONEER physical id: 0.0.0 bus info: scsi@2:0.0.0 logical name: /dev/cdrom logical name: /dev/cdrw logical name: /dev/dvd logical name: /dev/dvdrw logical name: /dev/scd0 logical name: /dev/sr0 logical name: /media/cdrom0 version: 1.21 capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram configuration: ansiversion=5 mount.fstype=iso9660 mount.options=ro,nosuid,nodev,utf8 state=mounted status=ready *-medium physical id: 0 logical name: /dev/cdrom logical name: /media/cdrom0 configuration: mount.fstype=iso9660 mount.options=ro,nosuid,nodev,utf8 state=mounted To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/283316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940984] Re: 5.11.0-1017 fails to boot on qemu builders
OK, this is actually due to the changes between u-boot-menu 4.0.1ubuntu0.1 and 4.0.2ubuntu5~20.04.1. The relevant difference is that the menu entry now has `fdtdir /lib/firmware/5.8.0-29-generic/device-tree/` (or similar) when it previously didn't load a device tree at all. I successfully worked around this by adding the following to `/etc/default/u-boot`: # XXX cjwatson 2021-08-24: Revert to old (nonexistent) default, since using # the device tree in /lib/firmware/ results in an image that fails to boot. # See https://bugs.launchpad.net/bugs/1940984. U_BOOT_FDT_DIR="/usr/lib/linux-image-" ** Package changed: linux-riscv-5.11 (Ubuntu) => u-boot-menu (Ubuntu) ** Summary changed: - 5.11.0-1017 fails to boot on qemu builders + u-boot fails to load FDT from linux-firmware on qemu builders -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1940984 Title: u-boot fails to load FDT from linux-firmware on qemu builders Status in u-boot-menu package in Ubuntu: New Bug description: I tried to do a routine upgrade and reflash of the Launchpad riscv64 builders, which pulled in linux-image-5.11.0-1017-generic 5.11.0-1017.18~20.04.1. The resulting image failed to boot with the following (complete) console output: Device 0: QEMU VirtIO Block Device Type: Hard Disk Capacity: 71680.0 MB = 70.0 GB (146800640 x 512) ... is now current device Scanning virtio 0:1... Found /boot/extlinux/extlinux.conf Retrieving file: /boot/extlinux/extlinux.conf 1391 bytes read in 1 ms (1.3 MiB/s) U-Boot menu 1: Ubuntu 20.04.3 LTS 5.11.0-1017-generic 2: Ubuntu 20.04.3 LTS 5.11.0-1017-generic (rescue target) 3: Ubuntu 20.04.3 LTS 5.8.0-29-generic 4: Ubuntu 20.04.3 LTS 5.8.0-29-generic (rescue target) Enter choice: 1:Ubuntu 20.04.3 LTS 5.11.0-1017-generic Retrieving file: /boot/initrd.img-5.11.0-1017-generic 18962 bytes read in 509 ms (355.3 MiB/s) Retrieving file: /boot/vmlinuz-5.11.0-1017-generic 25258496 bytes read in 70 ms (344.1 MiB/s) append: root=UUID=b797e480-278b-4efc-ae1a-bb1634c8cbcf rw noquiet root=/dev/vda1 Unhandled exception: Load access fault EPC: fffb642c RA: fff73bc4 TVAL: EPC: 8024a42c RA: 80207bc4 reloc adjusted ### ERROR ### Please RESET the board ### For the time being I've set `U_BOOT_DEFAULT="l1"` in `/etc/default/u-boot` to force it back to the 5.8 kernel, although that's obviously not very robust. Let me know if there's anything else useful I can provide. The full image is kind of massive (70G, though sparse so with only 13G of actual data), so I hope you can reproduce it with something more stripped-down. I've attached the libvirt domain definition. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot-menu/+bug/1940984/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940984] Re: 5.11.0-1017 fails to boot on qemu builders
Hm, I actually get similar results when I revert to 5.8.0-29: Device 0: QEMU VirtIO Block Device Type: Hard Disk Capacity: 71680.0 MB = 70.0 GB (146800640 x 512) ... is now current device Scanning virtio 0:1... Found /boot/extlinux/extlinux.conf Retrieving file: /boot/extlinux/extlinux.conf 1391 bytes read in 2 ms (678.7 KiB/s) U-Boot menu 1: Ubuntu 20.04.3 LTS 5.11.0-1017-generic 2: Ubuntu 20.04.3 LTS 5.11.0-1017-generic (rescue target) 3: Ubuntu 20.04.3 LTS 5.8.0-29-generic 4: Ubuntu 20.04.3 LTS 5.8.0-29-generic (rescue target) Enter choice: 3:Ubuntu 20.04.3 LTS 5.8.0-29-generic Retrieving file: /boot/initrd.img-5.8.0-29-generic 181049573 bytes read in 461 ms (374.5 MiB/s) Retrieving file: /boot/vmlinuz-5.8.0-29-generic 20059580 bytes read in 80 ms (239.1 MiB/s) append: root=UUID=b797e480-278b-4efc-ae1a-bb1634c8cbcf rw noquiet root=/dev/vda1 Unhandled exception: Load access fault EPC: fffb642c RA: fff73bc4 TVAL: EPC: 8024a42c RA: 80207bc4 reloc adjusted ### ERROR ### Please RESET the board ### I'll investigate further. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1940984 Title: 5.11.0-1017 fails to boot on qemu builders Status in linux-riscv-5.11 package in Ubuntu: New Bug description: I tried to do a routine upgrade and reflash of the Launchpad riscv64 builders, which pulled in linux-image-5.11.0-1017-generic 5.11.0-1017.18~20.04.1. The resulting image failed to boot with the following (complete) console output: Device 0: QEMU VirtIO Block Device Type: Hard Disk Capacity: 71680.0 MB = 70.0 GB (146800640 x 512) ... is now current device Scanning virtio 0:1... Found /boot/extlinux/extlinux.conf Retrieving file: /boot/extlinux/extlinux.conf 1391 bytes read in 1 ms (1.3 MiB/s) U-Boot menu 1: Ubuntu 20.04.3 LTS 5.11.0-1017-generic 2: Ubuntu 20.04.3 LTS 5.11.0-1017-generic (rescue target) 3: Ubuntu 20.04.3 LTS 5.8.0-29-generic 4: Ubuntu 20.04.3 LTS 5.8.0-29-generic (rescue target) Enter choice: 1:Ubuntu 20.04.3 LTS 5.11.0-1017-generic Retrieving file: /boot/initrd.img-5.11.0-1017-generic 18962 bytes read in 509 ms (355.3 MiB/s) Retrieving file: /boot/vmlinuz-5.11.0-1017-generic 25258496 bytes read in 70 ms (344.1 MiB/s) append: root=UUID=b797e480-278b-4efc-ae1a-bb1634c8cbcf rw noquiet root=/dev/vda1 Unhandled exception: Load access fault EPC: fffb642c RA: fff73bc4 TVAL: EPC: 8024a42c RA: 80207bc4 reloc adjusted ### ERROR ### Please RESET the board ### For the time being I've set `U_BOOT_DEFAULT="l1"` in `/etc/default/u-boot` to force it back to the 5.8 kernel, although that's obviously not very robust. Let me know if there's anything else useful I can provide. The full image is kind of massive (70G, though sparse so with only 13G of actual data), so I hope you can reproduce it with something more stripped-down. I've attached the libvirt domain definition. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv-5.11/+bug/1940984/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940984] [NEW] 5.11.0-1017 fails to boot on qemu builders
Public bug reported: I tried to do a routine upgrade and reflash of the Launchpad riscv64 builders, which pulled in linux-image-5.11.0-1017-generic 5.11.0-1017.18~20.04.1. The resulting image failed to boot with the following (complete) console output: Device 0: QEMU VirtIO Block Device Type: Hard Disk Capacity: 71680.0 MB = 70.0 GB (146800640 x 512) ... is now current device Scanning virtio 0:1... Found /boot/extlinux/extlinux.conf Retrieving file: /boot/extlinux/extlinux.conf 1391 bytes read in 1 ms (1.3 MiB/s) U-Boot menu 1: Ubuntu 20.04.3 LTS 5.11.0-1017-generic 2: Ubuntu 20.04.3 LTS 5.11.0-1017-generic (rescue target) 3: Ubuntu 20.04.3 LTS 5.8.0-29-generic 4: Ubuntu 20.04.3 LTS 5.8.0-29-generic (rescue target) Enter choice: 1:Ubuntu 20.04.3 LTS 5.11.0-1017-generic Retrieving file: /boot/initrd.img-5.11.0-1017-generic 18962 bytes read in 509 ms (355.3 MiB/s) Retrieving file: /boot/vmlinuz-5.11.0-1017-generic 25258496 bytes read in 70 ms (344.1 MiB/s) append: root=UUID=b797e480-278b-4efc-ae1a-bb1634c8cbcf rw noquiet root=/dev/vda1 Unhandled exception: Load access fault EPC: fffb642c RA: fff73bc4 TVAL: EPC: 8024a42c RA: 80207bc4 reloc adjusted ### ERROR ### Please RESET the board ### For the time being I've set `U_BOOT_DEFAULT="l1"` in `/etc/default/u-boot` to force it back to the 5.8 kernel, although that's obviously not very robust. Let me know if there's anything else useful I can provide. The full image is kind of massive (70G, though sparse so with only 13G of actual data), so I hope you can reproduce it with something more stripped-down. I've attached the libvirt domain definition. ** Affects: linux-riscv-5.11 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "riscv64-qemu-lcy01-002.xml" https://bugs.launchpad.net/bugs/1940984/+attachment/5520278/+files/riscv64-qemu-lcy01-002.xml -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1940984 Title: 5.11.0-1017 fails to boot on qemu builders Status in linux-riscv-5.11 package in Ubuntu: New Bug description: I tried to do a routine upgrade and reflash of the Launchpad riscv64 builders, which pulled in linux-image-5.11.0-1017-generic 5.11.0-1017.18~20.04.1. The resulting image failed to boot with the following (complete) console output: Device 0: QEMU VirtIO Block Device Type: Hard Disk Capacity: 71680.0 MB = 70.0 GB (146800640 x 512) ... is now current device Scanning virtio 0:1... Found /boot/extlinux/extlinux.conf Retrieving file: /boot/extlinux/extlinux.conf 1391 bytes read in 1 ms (1.3 MiB/s) U-Boot menu 1: Ubuntu 20.04.3 LTS 5.11.0-1017-generic 2: Ubuntu 20.04.3 LTS 5.11.0-1017-generic (rescue target) 3: Ubuntu 20.04.3 LTS 5.8.0-29-generic 4: Ubuntu 20.04.3 LTS 5.8.0-29-generic (rescue target) Enter choice: 1:Ubuntu 20.04.3 LTS 5.11.0-1017-generic Retrieving file: /boot/initrd.img-5.11.0-1017-generic 18962 bytes read in 509 ms (355.3 MiB/s) Retrieving file: /boot/vmlinuz-5.11.0-1017-generic 25258496 bytes read in 70 ms (344.1 MiB/s) append: root=UUID=b797e480-278b-4efc-ae1a-bb1634c8cbcf rw noquiet root=/dev/vda1 Unhandled exception: Load access fault EPC: fffb642c RA: fff73bc4 TVAL: EPC: 8024a42c RA: 80207bc4 reloc adjusted ### ERROR ### Please RESET the board ### For the time being I've set `U_BOOT_DEFAULT="l1"` in `/etc/default/u-boot` to force it back to the 5.8 kernel, although that's obviously not very robust. Let me know if there's anything else useful I can provide. The full image is kind of massive (70G, though sparse so with only 13G of actual data), so I hope you can reproduce it with something more stripped-down. I've attached the libvirt domain definition. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv-5.11/+bug/1940984/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904339] Re: kernel 5.4.0-53 (amd64) won't shut down
** Project changed: canonical-identity-provider => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904339 Title: kernel 5.4.0-53 (amd64) won't shut down Status in linux package in Ubuntu: New Bug description: Whenever using the "Shutdown" button in Linux Mint 20 Cinnamon, laptop GUI disappears until only a white cursor on black background appears. Cursor does not blink. No other messages or text. Same when using "shutdown" in terminal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904339/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917275] Re: MSI MS-7817 desktop linux kernel 5.4
*** This bug is a duplicate of bug 1917274 *** https://bugs.launchpad.net/bugs/1917274 ** This bug has been marked a duplicate of bug 1917274 MSI MS-7817 desktop linux kernel 5.4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1917275 Title: MSI MS-7817 desktop linux kernel 5.4 Status in linux package in Ubuntu: Incomplete Bug description: MSI MS-7817 desktop linux kernel 5.4 working --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: snowden1435 F pulseaudio /dev/snd/controlC0: snowden1435 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-15 (13 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: MSI MS-7817 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 RelatedPackageVersions: linux-restricted-modules-5.4.0-66-generic N/A linux-backports-modules-5.4.0-66-generic N/A linux-firmware1.187.9 RfKill: Tags: focal Uname: Linux 5.4.0-66-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/21/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) 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.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 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/1917275/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1914848] Re: linux kernel 5.8 jammed
** Project changed: launchpad => linux (Ubuntu) ** Changed in: linux (Ubuntu) Assignee: edsnowden2021 (edsnowden2021) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1914848 Title: linux kernel 5.8 jammed Status in linux package in Ubuntu: Confirmed Bug description: Computer Information: Manufacturer: Unknown Model: Unknown Form Factor: Desktop No Touch Input Detected Processor Information: CPU Vendor: GenuineIntel CPU Brand: Intel(R) Pentium(R) CPU G3420 @ 3.20GHz CPU Family: 0x6 CPU Model: 0x3c CPU Stepping: 0x3 CPU Type: 0x0 Speed: 3200 Mhz 2 logical processors 2 physical processors HyperThreading: Unsupported FCMOV: Supported SSE2: Supported SSE3: Supported SSSE3: Supported SSE4a: Unsupported SSE41: Supported SSE42: Supported AES: Unsupported AVX: Unsupported AVX2: Unsupported AVX512F: Unsupported AVX512PF: Unsupported AVX512ER: Unsupported AVX512CD: Unsupported AVX512VNNI: Unsupported SHA: Unsupported CMPXCHG16B: Supported LAHF/SAHF: Supported PrefetchW: Unsupported Operating System Version: Ubuntu 20.04.2 LTS (64 bit) Kernel Name: Linux Kernel Version: 5.8.0-41-generic X Server Vendor: The X.Org Foundation X Server Release: 12009000 X Window Manager: GNOME Shell Steam Runtime Version: steam-runtime_0.20201203.1 Video Card: Driver: Intel Open Source Technology Center Mesa DRI Intel(R) HD Graphics (HSW GT1) Driver Version: 3.0 Mesa 20.2.6 OpenGL Version: 3.0 Desktop Color Depth: 24 bits per pixel Monitor Refresh Rate: 60 Hz VendorID: 0x8086 DeviceID: 0x402 Revision Not Detected Number of Monitors: 1 Number of Logical Video Cards: 1 Primary Display Resolution: 1280 x 1024 Desktop Resolution: 1280 x 1024 Primary Display Size: 13.39" x 10.63" (17.09" diag) 34.0cm x 27.0cm (43.4cm diag) Primary VRAM Not Detected Sound card: Audio device: Intel Haswell HDMI Memory: RAM: 3798 Mb VR Hardware: VR Headset: None detected Miscellaneous: UI Language: English LANG: fi_FI.UTF-8 Total Hard Disk Space Available: 937366 Mb Largest Free Hard Disk Block: 878389 Mb The runtime information tool is preparing a report, please wait... have to restart again jammed again linux kernel 5.8 jammed this platform To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912646] Re: Ubuntu 20.10 freeze after update
** Project changed: launchpad => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912646 Title: Ubuntu 20.10 freeze after update Status in linux package in Ubuntu: Incomplete Bug description: After the update to 20.10 (from 20.04) the laptop freezes regularly. Screen is frozen, mouse cursor frozen and the only chance to recover is to switch off. Since it is hard to tell which part is broken I appended the kernel logs of the last boot. I found two "[ cut here ]" in the logs which seems to be a bad sign. I tried different kernels 5.8.0-36, 5.8.0-38, 5.8.0-40 and a 5.10.8 from the kernel team. All freeze. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1473723] Re: Elantech 0501 touch pad bug
** Package changed: linux-kernel (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1473723 Title: Elantech 0501 touch pad bug Status in linux package in Ubuntu: Incomplete Bug description: A lot of modern laptop use Elantech 0501 touch pad. One properly works only with 3.13 kernels. A have found that only one, higher than 3.13 is 3.18.7. The rest of kernels does not work properly. It means that there are problems with Click and marking text or touch pad do not work at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1473723/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905179] Re: SDcard show wrong date (one month later)
** Project changed: linux => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1905179 Title: SDcard show wrong date (one month later) Status in linux package in Ubuntu: New Bug description: When mount an SD card date is wrong shown on SD-card (it is shown as to be one month ahead). Very strange. There is already some report about here, but I don't find a bug here in launchpad. https://www.explorelinux.com/ubuntu-wrong-date-from-sd-card-pictures/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905179/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875916] Re: upgrading to 4.15.0-99-generic breaks the sound
** Project changed: launchpad => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875916 Title: upgrading to 4.15.0-99-generic breaks the sound Status in linux package in Ubuntu: Incomplete Bug description: I am using kubuntu LTS 18.04. This morning I was promped to update the kernel to the 4.15.0-99-generic. After the upgrade I did not manage to get any sound. I checked everything, pavucontrol, alsamix, everything was in order, the streams showed as if they were playing, however I couldn't get any sound from the speakers headphones and I could not get any sound recorded either. I then rebooted with the previous version of the Kernel, and have my sound back without doing anything at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875916/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871232] Re: Removing zfsutils-linux/focal 0.8.3-1ubuntu11 package in a chroot environment tries to unmount all zfs datasets
** Project changed: launchpad => zfs-linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1871232 Title: Removing zfsutils-linux/focal 0.8.3-1ubuntu11 package in a chroot environment tries to unmount all zfs datasets Status in zfs-linux package in Ubuntu: New Bug description: I ran "apt remove zfsutils-linux" to remove the package in a chroot environment, it tried to run "/etc/init.d/zfs-mount stop" which would unmount all zfs datasets. This caused issue as my chroot environment has various folders mounted as zfs file systems. On Ubuntu 19.04 where zfs version is 0.7.12, it does not do that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1871232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836707] Re: LXD Storage pool on an NFS share strange user mapping
This isn't a bug against Launchpad (i.e. the launchpad.net site itself). Judging from the history of https://github.com/lxc/lxd/issues/5962, it seems as though Stéphane's view was that it's a kernel bug, so reassigning there. ** Bug watch added: LXD bug tracker #5962 https://github.com/lxc/lxd/issues/5962 ** Project changed: launchpad => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836707 Title: LXD Storage pool on an NFS share strange user mapping Status in linux package in Ubuntu: New Bug description: Hi Ref: 18.04 LTS I originally posted this problem on JUJU discourse (https://discourse.jujucharms.com/t/lxc-with-nfs-storage-pool-fail- bootstrap-and-deploy/1654) but then move to LXD issue (https://github.com/lxc/lxd/issues/5962). The problem is when an LXD container has a storage pool on an NFS share is dir mode creating files either touch, vim, ... the UID of the file is set to nobody but chown of the file to root fixes the problem. I am in the process of testing 19.04 and 19.10 as well. Matthew Here is the report from LXD issue. Required information Distribution:Ubuntu Distribution version: 18.04 LTS The output of "lxc info" or if that fails: config: core.https_address: 10.0.4.1:8443 core.trust_password: true maas.api.key: maas.api.url: http://*:5240/MAAS api_extensions: storage_zfs_remove_snapshots container_host_shutdown_timeout container_stop_priority container_syscall_filtering auth_pki container_last_used_at etag patch usb_devices https_allowed_credentials image_compression_algorithm directory_manipulation container_cpu_time storage_zfs_use_refquota storage_lvm_mount_options network profile_usedby container_push container_exec_recording certificate_update container_exec_signal_handling gpu_devices container_image_properties migration_progress id_map network_firewall_filtering network_routes storage file_delete file_append network_dhcp_expiry storage_lvm_vg_rename storage_lvm_thinpool_rename network_vlan image_create_aliases container_stateless_copy container_only_migration storage_zfs_clone_copy unix_device_rename storage_lvm_use_thinpool storage_rsync_bwlimit network_vxlan_interface storage_btrfs_mount_options entity_description image_force_refresh storage_lvm_lv_resizing id_map_base file_symlinks container_push_target network_vlan_physical storage_images_delete container_edit_metadata container_snapshot_stateful_migration storage_driver_ceph storage_ceph_user_name resource_limits storage_volatile_initial_source storage_ceph_force_osd_reuse storage_block_filesystem_btrfs resources kernel_limits storage_api_volume_rename macaroon_authentication network_sriov console restrict_devlxd migration_pre_copy infiniband maas_network devlxd_events proxy network_dhcp_gateway file_get_symlink network_leases unix_device_hotplug storage_api_local_volume_handling operation_description clustering event_lifecycle storage_api_remote_volume_handling nvidia_runtime candid_authentication candid_config candid_config_key usb_optional_vendorid api_status: stable api_version: "1.0" auth: trusted public: false auth_methods: tls environment: addresses: 10.0.4.1:8443 architectures: x86_64 i686 certificate: | -BEGIN CERTIFICATE- -END CERTIFICATE- certificate_fingerprint: driver: lxc driver_version: 3.0.3 kernel: Linux kernel_architecture: x86_64 kernel_version: 4.15.0-54-generic server: lxd server_pid: 30277 server_version: 3.0.3 storage: dir storage_version: "1" server_clustered: true server_name: m-node-01 project: "" UID mapping incorrect when creating a file. When touching or creating a file with vim (or any other method) is created with the UID on nobody (65534) but other files are all correct the startup. The correct UID can be set by chown of the file Steps to reproduce Create container (lxc launch -s nfs ubuntu:18.04) Access container ( lxc exec modest-ladybug -- sudo /bin/bash ) touch file (touch test) list dir (ls -la) root@modest-ladybug:~# ls -la total 50 drwx-- 3 root root6 Jul 15 21:18 . drwxr-xr-x 22 root root 22 Jun 27 16:28 .. -rw-r--r-- 1 root root 3106 Apr 9 2018 .bashrc -rw-r--r-- 1 root root 148 Aug 17 2015 .profile drwx-- 2 root root3 Jul 15 21:17 .ssh -rw-r--r-- 1 nobody root0 Jul 15 21:18 test Change own (chown root:root test) root@modest-ladybug:~# ls -la total 50 drwx-- 3 root root6 Jul 15 21:18 . drwxr-xr-x 22 root root 22 Jun 27 16:28 .. -rw-r--r-- 1 root root 3106 Apr 9 2018 .bashrc -rw-r--r-- 1 root root 148 Aug 17
[Kernel-packages] [Bug 1829749] Re: Please add support for zipl signing
** Changed in: launchpad
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1829749
Title:
Please add support for zipl signing
Status in Launchpad itself:
Fix Released
Status in linux-signed package in Ubuntu:
New
Status in s390-tools package in Ubuntu:
In Progress
Bug description:
Please add support for zipl ("z/ecureBoot") signing.
It should be similar to opal signing, but using the new zipl signing
key.
I am expecting to sign s390-tools stage3.bin and kernel images using
this key.
s390-tools -> can be signed already
kernels -> should only sign v5.2+
To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1829749/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829749] Re: Please add support for zipl signing
** Changed in: launchpad
Importance: Undecided => High
** Changed in: launchpad
Status: New => Fix Committed
** Changed in: launchpad
Assignee: (unassigned) => Andy Whitcroft (apw)
** Branch linked: lp:~apw/launchpad/signing-sipl
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1829749
Title:
Please add support for zipl signing
Status in Launchpad itself:
Fix Committed
Status in linux-signed package in Ubuntu:
New
Status in s390-tools package in Ubuntu:
New
Bug description:
Please add support for zipl ("z/ecureBoot") signing.
It should be similar to opal signing, but using the new zipl signing
key.
I am expecting to sign s390-tools stage3.bin and kernel images using
this key.
s390-tools -> can be signed already
kernels -> should only sign v5.2+
To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1829749/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819907] Re: 19.04 installer hangs on installation complete dialog
** Information type changed from Proprietary to Public ** Project changed: null-and-void => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819907 Title: 19.04 installer hangs on installation complete dialog Status in linux package in Ubuntu: New Bug description: Installed version 19.04 on a Lenovo P1 laptop and when the installation Complete dialog came up I hit the restart button and the system froze. I then have to hard power down. At this point it boots to a login prompt. I login but there is no desktop after ten minutes or more finally reinstalled. On reinstall again same freeze at install complete but this time after several minutes the desktop did finally show up. Only difference on the installs was first time I selected the update wifi and other drivers click box and second time I did not. BIOS N2EET38W CPU i7-8850H To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819907/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818881] Re: ath10k_pci crashing
** Project changed: launchpad => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818881 Title: ath10k_pci crashing Status in linux package in Ubuntu: New Bug description: The below happens on a regular basis on my DELL XPS 13 9380: [77451.338493] RIP: 0010:ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 [ath10k_core] [77451.338494] Code: 74 32 48 8b 87 10 02 00 00 48 85 c0 74 26 48 8b 40 28 48 85 c0 74 17 45 31 c0 b9 02 00 00 00 e8 dd c1 d7 db 48 89 d8 5b 5d c3 <0f> 0b 31 db 48 89 d8 5b 5d c3 48 8b 05 de 67 5a dc eb d1 0f 1f 40 [77451.338531] RSP: 0018:9d996e503d78 EFLAGS: 00010246 [77451.338533] RAX: RBX: 9d97b7c12290 RCX: 9d96cbfd5528 [77451.338534] RDX: 37af2804 RSI: 9d9944c51ed4 RDI: 9d9944c51de0 [77451.338535] RBP: 9d996e503d80 R08: 0020 R09: [77451.338537] R10: 9d94f045ecd8 R11: 01ff R12: 9d9944c51520 [77451.338538] R13: 9d996e503e40 R14: 0040 R15: 9d996e503e28 [77451.338540] FS: () GS:9d996e50() knlGS: [77451.338541] CS: 0010 DS: ES: CR0: 80050033 [77451.338542] CR2: 1f1104c31000 CR3: 00017aa0a005 CR4: 003606e0 [77451.338543] Call Trace: [77451.338545] [77451.338557] ath10k_htt_txrx_compl_task+0x3d6/0xe40 [ath10k_core] [77451.338561] ? ath10k_pci_irq_msi_fw_unmask+0x70/0x70 [ath10k_pci] [77451.338563] ? ath10k_pci_wake.part.24+0xa0/0xa0 [ath10k_pci] [77451.338567] ath10k_pci_napi_poll+0x54/0x110 [ath10k_pci] [77451.338571] net_rx_action+0x140/0x3a0 [77451.338575] __do_softirq+0xe4/0x2d4 [77451.338580] irq_exit+0xc5/0xd0 [77451.338582] do_IRQ+0x8a/0xe0 [77451.338585] common_interrupt+0xf/0xf [77451.338586] [77451.338589] RIP: 0010:cpuidle_enter_state+0xa5/0x2c0 [77451.338590] Code: 8b 3d df bf 9d 63 e8 6a 09 89 ff 48 89 c3 0f 1f 44 00 00 31 ff e8 cb 14 89 ff 45 84 ff 0f 85 c8 01 00 00 fb 66 0f 1f 44 00 00 <48> 2b 5d d0 48 ba cf f7 53 e3 a5 9b c4 20 48 89 d8 48 c1 fb 3f 48 [77451.338621] RSP: 0018:af4601993e50 EFLAGS: 0246 ORIG_RAX: ffde [77451.338623] RAX: 9d996e522c40 RBX: 46710b80e2b6 RCX: 001f [77451.338624] RDX: 46710b80e2b6 RSI: 4041cc98 RDI: [77451.338625] RBP: af4601993e90 R08: 0002 R09: 000224c0 [77451.338626] R10: af4601993e20 R11: 00d9 R12: 0004 [77451.338626] R13: 9d996e52ce00 R14: 9d3849f8 R15: [77451.338630] cpuidle_enter+0x17/0x20 [77451.338632] call_cpuidle+0x23/0x40 [77451.338634] do_idle+0x204/0x280 [77451.338636] cpu_startup_entry+0x73/0x80 [77451.338639] start_secondary+0x1ab/0x200 [77451.338642] secondary_startup_64+0xa5/0xb0 [77451.338643] ---[ end trace 22914e3b3a848f81 ]--- [77451.338655] ath10k_pci :02:00.0: failed to pop paddr list: -2 $ uname -a Linux perseus 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ modinfo ath10k_pci filename: /lib/modules/4.18.0-15-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko firmware: ath10k/QCA9377/hw1.0/board.bin firmware: ath10k/QCA9377/hw1.0/firmware-5.bin firmware: ath10k/QCA9377/hw1.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/board-2.bin firmware: ath10k/QCA6174/hw3.0/board.bin firmware: ath10k/QCA6174/hw3.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/firmware-5.bin firmware: ath10k/QCA6174/hw3.0/firmware-4.bin firmware: ath10k/QCA6174/hw2.1/board-2.bin firmware: ath10k/QCA6174/hw2.1/board.bin firmware: ath10k/QCA6174/hw2.1/firmware-5.bin firmware: ath10k/QCA6174/hw2.1/firmware-4.bin firmware: ath10k/QCA9887/hw1.0/board-2.bin firmware: ath10k/QCA9887/hw1.0/board.bin firmware: ath10k/QCA9887/hw1.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/board-2.bin firmware: ath10k/QCA988X/hw2.0/board.bin firmware: ath10k/QCA988X/hw2.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/firmware-4.bin firmware: ath10k/QCA988X/hw2.0/firmware-3.bin firmware: ath10k/QCA988X/hw2.0/firmware-2.bin license:Dual BSD/GPL description:Driver support for Qualcomm Atheros 802.11ac WLAN PCIe/AHB devices author: Qualcomm Atheros srcversion: D49EBAB0107B6CE28383BB8 alias: pci:v168Cd0050sv*sd*bc*sc*i* alias: pci:v168Cd0042sv*sd*bc*sc*i* alias: pci:v168Cd0046sv*sd*bc*sc*i* alias: pci:v168Cd0056sv*sd*bc*sc*i* alias: pci:v168Cd0040sv*sd*bc*sc*i* alias: pci:v168Cd003Esv*sd*bc*sc*i* al
[Kernel-packages] [Bug 1813819] Re: The kernel speeds up and down unexpectedly
** Project changed: launchpad => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813819 Title: The kernel speeds up and down unexpectedly Status in linux package in Ubuntu: Incomplete Bug description: It initially started while I was browsing and I noticed the page load idle logo was going a bit too fast. First I ignored it assuming I was wrong or it was not significant. So i decided to test the playback time in videos and the Linux clock and sure enough, everything is about 10% tp 20% faster. So I rebooted the OS to see if problem persists.it actually got worse Everytime I rebooted. The os starts up normally but as soon as I log in, everything gets faster and faster until keyboard, mouse become unusable. A gentle tap of the keyboard spams the screen with that letter. Then I rebooted again and as if it was some kind of overflow the os is now snail pace slow. When I tap a button it outputs a letter about 1 to 2 seconds after. The mouse moves at normal speed however.unfortunately the OS is unusable and I'm typing this bug report using a different device. Please let me know if there is a way for me to get logs remotely cause as it is OS is useless. I'll try too keep rebooting to see if there is a "usable" speed that I can get logs and upload. Hopefully by the time this bug is processed I'll get the report. In the mean time please feel free to ask me anything that would help you pin point the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808600] Re: Dell venue 7140 micro SD card reader doesnt work with SD card 400GB, it works on windows8.1/10
** Project changed: launchpad => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808600 Title: Dell venue 7140 micro SD card reader doesnt work with SD card 400GB, it works on windows8.1/10 Status in linux package in Ubuntu: New Bug description: 2018-12-01T17:06:36.572303+01:00 DELLVENUE7140 su: pam_systemd(su:session): Cannot create session: Already running in a session 2018-12-01T17:06:36.572578+01:00 DELLVENUE7140 su: pam_unix(su:session): session opened for user root by filarsky(uid=1000) 2018-12-01T17:06:38.809874+01:00 DELLVENUE7140 kernel: [ 34.145441] mmc0: Timeout waiting for hardware interrupt. 2018-12-01T17:06:38.809901+01:00 DELLVENUE7140 kernel: [ 34.145443] mmc0: sdhci: SDHCI REGISTER DUMP === 2018-12-01T17:06:38.809902+01:00 DELLVENUE7140 kernel: [ 34.145448] mmc0: sdhci: Sys addr: 0x0008 | Version: 0x0603 2018-12-01T17:06:38.809903+01:00 DELLVENUE7140 kernel: [ 34.145452] mmc0: sdhci: Blk size: 0x7200 | Blk cnt: 0x0008 2018-12-01T17:06:38.809903+01:00 DELLVENUE7140 kernel: [ 34.145456] mmc0: sdhci: Argument: 0x | Trn mode: 0x003b 2018-12-01T17:06:38.809904+01:00 DELLVENUE7140 kernel: [ 34.145460] mmc0: sdhci: Present: 0x01ff | Host ctl: 0x0017 2018-12-01T17:06:38.809905+01:00 DELLVENUE7140 kernel: [ 34.145464] mmc0: sdhci: Power: 0x000f | Blk gap: 0x 2018-12-01T17:06:38.809914+01:00 DELLVENUE7140 kernel: [ 34.145467] mmc0: sdhci: Wake-up: 0x | Clock: 0x0007 2018-12-01T17:06:38.809915+01:00 DELLVENUE7140 kernel: [ 34.145471] mmc0: sdhci: Timeout: 0x000a | Int stat: 0x 2018-12-01T17:06:38.809916+01:00 DELLVENUE7140 kernel: [ 34.145475] mmc0: sdhci: Int enab: 0x02ff008b | Sig enab: 0x02ff008b 2018-12-01T17:06:38.809955+01:00 DELLVENUE7140 kernel: [ 34.145478] mmc0: sdhci: AC12 err: 0x0004 | Slot int: 0x 2018-12-01T17:06:38.809956+01:00 DELLVENUE7140 kernel: [ 34.145482] mmc0: sdhci: Caps: 0x25f8c8bf | Caps_1: 0x2077 2018-12-01T17:06:38.809957+01:00 DELLVENUE7140 kernel: [ 34.145486] mmc0: sdhci: Cmd: 0x123a | Max curr: 0x005800c8 2018-12-01T17:06:38.809957+01:00 DELLVENUE7140 kernel: [ 34.145490] mmc0: sdhci: Resp[0]: 0x | Resp[1]: 0x 2018-12-01T17:06:38.809958+01:00 DELLVENUE7140 kernel: [ 34.145494] mmc0: sdhci: Resp[2]: 0x | Resp[3]: 0x 2018-12-01T17:06:38.809959+01:00 DELLVENUE7140 kernel: [ 34.145496] mmc0: sdhci: Host ctl2: 0x800b 2018-12-01T17:06:38.809960+01:00 DELLVENUE7140 kernel: [ 34.145499] mmc0: sdhci: ADMA Err: 0x | ADMA Ptr: 0x3fc00208 2018-12-01T17:06:38.809961+01:00 DELLVENUE7140 kernel: [ 34.145500] mmc0: sdhci: 2018-12-01T17:06:38.809966+01:00 DELLVENUE7140 kernel: [ 34.145684] mmcblk0: error -84 sending status command, retrying 2018-12-01T17:06:38.869767+01:00 DELLVENUE7140 kernel: [ 34.201457] mmc0: Tuning timeout, falling back to fixed sampling clock 2018-12-01T17:06:38.869781+01:00 DELLVENUE7140 kernel: [ 34.201709] mmcblk0: error -84 sending status command, retrying 2018-12-01T17:06:38.925667+01:00 DELLVENUE7140 kernel: [ 34.257457] mmc0: Tuning timeout, falling back to fixed sampling clock 2018-12-01T17:06:38.925684+01:00 DELLVENUE7140 kernel: [ 34.259406] mmcblk0: error -84 sending status command, aborting 2018-12-01T17:06:39.309674+01:00 DELLVENUE7140 kernel: [ 34.641396] mmc0: Tuning timeout, falling back to fixed sampling clock 2018-12-01T17:06:40.315726+01:00 DELLVENUE7140 systemd-timesyncd[857]: Synchronized to time server 129.250.35.251:123 (2.opensuse.pool.ntp.org). 2018-12-01T17:06:49.561926+01:00 DELLVENUE7140 kernel: [ 44.899647] mmc0: Timeout waiting for hardware interrupt. 2018-12-01T17:06:49.561938+01:00 DELLVENUE7140 kernel: [ 44.899648] mmc0: sdhci: SDHCI REGISTER DUMP === 2018-12-01T17:06:49.561939+01:00 DELLVENUE7140 kernel: [ 44.899653] mmc0: sdhci: Sys addr: 0x0008 | Version: 0x0603 LSPCI : https://pastebin.com/sVKA47r3 After update to kernel 4.19 (OS: opensuse) [Previous log applies to 4.12] 2018-12-02T10:26:57.264780+01:00 DELLVENUE7140 kernel: [ 39.552776] mmc0: Tuning timeout, falling back to fixed sampling clock 2018-12-02T10:26:57.264814+01:00 DELLVENUE7140 kernel: [ 39.553062] mmc0: new ultra high speed SDR104 SDXC card at address 2018-12-02T10:26:57.280688+01:00 DELLVENUE7140 kernel: [ 39.570818] mmcblk0: mmc0: SR400 367 GiB 2018-12-02T10:26:57.336742+01:00 DELLVENUE7140 kernel: [ 39.624763] mmc0: Tuning timeout, falling back to fixed sampling clock 2018-12-02T10:26:57.596691+01:00 DELLVENUE7140 kernel: [ 39.887665] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31
[Kernel-packages] [Bug 1805433] Re: Call trace in dmesg (need to specify later what this is)
** Project changed: launchpad => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805433 Title: Call trace in dmesg (need to specify later what this is) Status in linux package in Ubuntu: Incomplete Bug description: Hello, I get a few call traces in my dmesg log which seems to indicate some problem. I'm trying to get my hardware better compatible with Ubuntu 18.10 therefor i report this bug. Actually i have no idea what this is about so i'll be happy to provide more information on request. There are actually a few call traces so i will upload the entire output from dmesg together with information on my system. Possibly the issues should be separated into several bug reports. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 872711] Re: Kernel does not report some USB printers correctly, making them not being detected by CUPS
** Attachment removed: "printrtr.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/872711/+attachment/5212583/+files/printrtr.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/872711
Title:
Kernel does not report some USB printers correctly, making them not
being detected by CUPS
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Oneiric:
Fix Released
Status in linux source package in Precise:
Fix Released
Bug description:
See the following CUPS upstream bug report:
http://www.cups.org/str.php?L3884
Users complain that their USB printers do not get detected by CUPS and
so they cannot set them up for printing. In the last comment it is
told that the kernel is the culprit and a link to a patch proposal on
the Kernel mailing list is given:
http://lkml.org/lkml/2011/9/25/57
The patch attached there is supposed to solve the problem.
I have also a printer (HP Color LaserJet CM3530 MFP) which is only
detected by the HPLIP CUPS backend (this backend uses another
detection method but is only avaiolable for HP printers) and not by
CUPS' own backend, so I can reproduce the bug.
I did not test the kernel patch.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: till 2561 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfc02 irq 48'
Mixer name : 'Conexant CX20561 (Hermosa)'
Components : 'HDA:14f15051,17aa211c,0010'
Controls : 17
Simple ctrls : 9
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw
7VHT12WW-1.01'
Mixer name : 'ThinkPad EC 7VHT12WW-1.01'
Components : ''
Controls : 1
Simple ctrls : 1
Card29.Amixer.values:
Simple mixer control 'Console',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
DistroRelease: Ubuntu 11.10
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=9185f036-2e72-40e6-bf31-d9a8926a7883
MachineType: LENOVO 7417CTO
Package: linux (not installed)
PccardctlIdent:
Socket 0:
product info: "MoGo Mouse BT", " ", "", ""
PccardctlStatus:
Socket 0:
5.0V 16-bit PC Card
Subdevice 0 (function 0) [unbound]
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-12-generic
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
RelatedPackageVersions:
linux-restricted-modules-3.0.0-12-generic N/A
linux-backports-modules-3.0.0-12-generic N/A
linux-firmware1.60
StagingDrivers: mei
Tags: oneiric running-unity staging
Uname: Linux 3.0.0-12-generic x86_64
UpgradeStatus: Upgraded to oneiric on 2011-09-30 (11 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 10/13/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 7UET79WW (3.09 )
dmi.board.name: 7417CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvr7UET79WW(3.09):bd10/13/2009:svnLENOVO:pn7417CTO:pvrThinkPadT400:rvnLENOVO:rn7417CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 7417CTO
dmi.product.version: ThinkPad T400
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/872711/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 818544] Re: Brother MFC-240C FAX/Printer error
** Attachment removed: "printrtr.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/818544/+attachment/5211037/+files/printrtr.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/818544 Title: Brother MFC-240C FAX/Printer error Status in linux package in Ubuntu: Expired Bug description: Before the extensive listing. I had the printer working fine through manually installing the printer drivers from the Brother software site since 9.10, and also for a HP printer. A couple weeks back, the universal printer drivers were changed on my Computer via a popup updater (damned thing). I tried removing everything, and re- installing the origional printers. One problem is most of the online help is for the older 10.10, and is always using menues that have been removed. I also busted out my linux manual and used the lpadmin, and manually configuring cups. The cups file looks fine, but constantly changes permissions every ten minutes to only allow root to access it. In addition I get the following error: lpinfo: cups-driverd failed to execute. cupsd: Child exited on signal 15! The main error printed starts like this: Cannot execute command due to filter stopping job because scheduler cannot execute filter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/818544/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775672] Re: virtualbox-dkms installation hangs in 18.04 (with secure boot)
My current workaround is to remove the redirection of /usr/lib/dkms/dkms_autoinstaller's stdout to /dev/null in /etc/kernel/header_postinst.d/dkms. This may even be the correct fix: it's a little noisier, but not unacceptably so and it's definitely better than a hung installation. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1775672 Title: virtualbox-dkms installation hangs in 18.04 (with secure boot) Status in DKMS: New Status in dkms package in Ubuntu: Confirmed Bug description: apt install virtualbox hangs during virtualbox-dkms installation: # apt install virtualbox Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: dkms libgsoap-2.8.60 libqt5opengl5 libqt5printsupport5 libvncserver1 virtualbox-dkms virtualbox-qt Suggested packages: menu vde2 virtualbox-guest-additions-iso The following NEW packages will be installed: dkms libgsoap-2.8.60 libqt5opengl5 libqt5printsupport5 libvncserver1 virtualbox virtualbox-dkms virtualbox-qt 0 upgraded, 8 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/27.0 MB of archives. After this operation, 117 MB of additional disk space will be used. Do you want to continue? [Y/n] y Selecting previously unselected package dkms. (Reading database ... 185903 files and directories currently installed.) Preparing to unpack .../0-dkms_2.3-3ubuntu9.1_all.deb ... Unpacking dkms (2.3-3ubuntu9.1) ... Selecting previously unselected package libgsoap-2.8.60:amd64. Preparing to unpack .../1-libgsoap-2.8.60_2.8.60-2build1_amd64.deb ... Unpacking libgsoap-2.8.60:amd64 (2.8.60-2build1) ... Selecting previously unselected package libqt5opengl5:amd64. Preparing to unpack .../2-libqt5opengl5_5.9.5+dfsg-0ubuntu1_amd64.deb ... Unpacking libqt5opengl5:amd64 (5.9.5+dfsg-0ubuntu1) ... Selecting previously unselected package libqt5printsupport5:amd64. Preparing to unpack .../3-libqt5printsupport5_5.9.5+dfsg-0ubuntu1_amd64.deb ... Unpacking libqt5printsupport5:amd64 (5.9.5+dfsg-0ubuntu1) ... Selecting previously unselected package libvncserver1:amd64. Preparing to unpack .../4-libvncserver1_0.9.11+dfsg-1ubuntu1_amd64.deb ... Unpacking libvncserver1:amd64 (0.9.11+dfsg-1ubuntu1) ... Selecting previously unselected package virtualbox-dkms. Preparing to unpack .../5-virtualbox-dkms_5.2.10-dfsg-6_all.deb ... Unpacking virtualbox-dkms (5.2.10-dfsg-6) ... Selecting previously unselected package virtualbox. Preparing to unpack .../6-virtualbox_5.2.10-dfsg-6_amd64.deb ... Unpacking virtualbox (5.2.10-dfsg-6) ... Selecting previously unselected package virtualbox-qt. Preparing to unpack .../7-virtualbox-qt_5.2.10-dfsg-6_amd64.deb ... Unpacking virtualbox-qt (5.2.10-dfsg-6) ... Setting up libvncserver1:amd64 (0.9.11+dfsg-1ubuntu1) ... Processing triggers for mime-support (3.60ubuntu1) ... Processing triggers for ureadahead (0.100.0-20) ... Processing triggers for desktop-file-utils (0.23-1ubuntu3) ... Setting up libqt5printsupport5:amd64 (5.9.5+dfsg-0ubuntu1) ... Setting up libqt5opengl5:amd64 (5.9.5+dfsg-0ubuntu1) ... Processing triggers for bamfdaemon (0.5.3+18.04.20180207.2-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Setting up libgsoap-2.8.60:amd64 (2.8.60-2build1) ... Setting up dkms (2.3-3ubuntu9.1) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Processing triggers for systemd (237-3ubuntu10) ... Processing triggers for man-db (2.8.3-2) ... Processing triggers for shared-mime-info (1.9-2) ... Processing triggers for gnome-menus (3.13.3-11ubuntu1) ... Processing triggers for hicolor-icon-theme (0.17-2) ... Setting up virtualbox-dkms (5.2.10-dfsg-6) ... Loading new virtualbox-5.2.10 DKMS files... Building for 4.15.0-22-generic Progress: [ 85%] [#.] $ dpkg -l | grep virtualbox ii unity-scope-virtualbox 0.1+13.10.20130723-0ubuntu1 all VirtualBox scope for Unity iU virtualbox 5.2.10-dfsg-6 amd64x86 virtualization solution - base binaries iF virtualbox-dkms5.2.10-dfsg-6 all x86 virtualization solution - kernel module sources for dkms iU virtualbox-qt 5.2.10-dfsg-6 amd64x86 virtualization solution - Qt based user interface $ $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ $ apt-cache policy virtualbox-dkms virtualbox-dkms: Installed: 5.2.10-dfsg-6 Candidate: 5.2.10-dfsg-6 Version table: *** 5.2.10-dfsg-6 500 500 http://us.archive.ubu
[Kernel-packages] [Bug 1776076] Re: package virtualbox-dkms 5.2.10-dfsg-6 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed)
*** This bug is a duplicate of bug 1775672 *** https://bugs.launchpad.net/bugs/1775672 ** This bug has been marked a duplicate of bug 1775672 virtualbox-dkms installation hangs in 18.04 (with secure boot) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1776076 Title: package virtualbox-dkms 5.2.10-dfsg-6 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed) Status in dkms package in Ubuntu: Confirmed Bug description: virtualbox installation getting stuck ProblemType: Package DistroRelease: Ubuntu 18.04 Package: virtualbox-dkms 5.2.10-dfsg-6 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Jun 10 19:11:06 2018 ErrorMessage: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed) InstallationDate: Installed on 2018-06-10 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: virtualbox Title: package virtualbox-dkms 5.2.10-dfsg-6 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1776076/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1736770] Re: debian-installer/main-menu changes priority
** Package changed: debconf (Ubuntu) => cdebconf (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1736770 Title: debian-installer/main-menu changes priority Status in cdebconf package in Ubuntu: New Status in linux package in Ubuntu: Invalid Bug description: During a test install of Bionic it appears that the debian-installer /main-menu option changes priority from medium to critical part way through the test: Dec 6 04:18:55 debconf: --> INPUT medium debian-installer/main-menu Dec 6 04:18:55 debconf: <-- 30 question skipped Dec 6 04:18:55 debconf: --> GO ... Dec 6 04:19:54 debconf: --> METAGET debian-installer/live-installer/title Description Dec 6 04:19:54 debconf: <-- 0 Install the system Dec 6 04:19:54 debconf: --> SET debian-installer/main-menu Install the system Dec 6 04:19:54 debconf: <-- 0 value set Dec 6 04:19:54 debconf: --> INPUT critical debian-installer/main-menu Dec 6 04:19:54 debconf: <-- 0 question will be asked Dec 6 04:19:54 debconf: --> GO Working test on Dec 1: https://paste.ubuntu.com/26126878/ Failing test on Dec 6: https://paste.ubuntu.com/26126090/ Steps to reproduce: 1. Get latest ISO from: http://cdimage.ubuntu.com/ubuntu-server/daily/pending/ 2. Pull out the kernel and initrd $ mkdir iso $ bsdtar xfp bionic-server-amd64.iso -C iso $ cp iso/install/vmlinuz . $ cp iso/install/initrd.gz . 3. Create QEMU disk $ qemu-img create -f qcow2 vdisk.img 4G 4. Launch ISO via QEMU $ qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -boot d \ -initrd initrd.gz -kernel vmlinuz -display none -nographic \ -hda vdisk.img -cdrom bionic-server-amd64.iso \ -append 'console=ttyS0 locale=en_US.UTF-8 priority=critical' 5. Proceed with the install by 1) enter user info and 2) select disk 6. Eventually the "Ubuntu installer main menu" will appear. Even if you click on "Install the system" the installation step will fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cdebconf/+bug/1736770/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device
** Project changed: debian-installer => debian-installer (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779815 Title: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device Status in The Ubuntu-power-systems project: Triaged Status in debian-installer package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: == Comment: #0 - ABDUL HALEEM - 2018-07-02 03:55:33 == ---Problem Description--- Ubuntu 18.04.01 ppc64el installer does not detect LSI3008 base SAS disks / MD RAID devices Used 20101020ubuntu543 version to install http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/ Contact Information = abdha...@in.ibm.com ---uname output--- Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = BostonLC ---boot type--- Network boot Installer fails to detect the LSI SAS disks / RAID MD device ===console error log=== ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device ? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? ? ?? ? ? ??? moves; selects; activates buttons To make sure it detects the disks I had to Detect disks-->Guided partitioning--> Guided - use entire disk ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075 ? ? SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume ? ? SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ ? ? ? ?? ? ? ??? IPR had similar issue reported #164932 and fixed with 4.15.0-20, looks installer need a fix for LSI (mpt3sas) devices too == Comment: #2 - SEETEENA THOUFEEK - 2018-07-03 02:01:47 == 164932 - refers LP1751813 == Comment: #3 - SEETEENA THOUFEEK - 2018-07-03 02:02:51 == Jul 2 08:49:52 anna-install: Installing mdadm-udeb Jul 2 08:49:52 disk-detect: No Intel/DDF RAID disks detected. Jul 2 08:49:52 anna-install: Installing dmraid-udeb Jul 2 08:49:52 disk-detect: No Serial ATA RAID disks detected Jul 2 08:49:53 check-missing-firmware: looking at dmesg again, restarting from \[ 330.659712\] Jul 2 08:49:53 check-missing-firmware: timestamp found, truncating dmesg accordingly Jul 2 08:49:53 check-missing-firmware: saving timestamp for a later use: Jul 2 08:49:53 check-missing-firmware: /dev/.udev/firmware-missing does not exist, skipping Jul 2 08:49:53 check-missing-firmware: /run/udev/firmware-missing does not exist, skipping Jul 2 08:49:53 check-missing-firmware: no missing firmware in loaded kernel modules Jul 2 08:49:53 main-menu[1425]: (process:8933): ERROR: unsupported sector size 4096 on /dev/sda. Jul 2 08:49:53 main-menu[1425]: (process:8933): File descriptor 3 (pipe:[38926]) leaked on pvs invocation. Parent PID 8940: /bin/sh Jul
[Kernel-packages] [Bug 1774771] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1774771/+attachment/5147815/+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/1774771 Title: Thinkpad T450s frequently hangs with black screen on resume Status in linux package in Ubuntu: New Bug description: My laptop, a Thinkpad T450s, often hangs with a black screen on resume from suspend; I have to power off and back on to recover. I'd estimate that this happens perhaps one in every two or three resumes, so it's pretty annoying. I'm currently running 18.04, but was on 16.04 up to a few months ago. I suspend relatively infrequently so I don't have great data, but my sense is that this happened occasionally on 16.04 but has become very much more frequent on 18.04. I haven't been able to find any useful log information about what the problem might be: syslog has log entries for suspending and then goes straight into the log of the next successful boot, with nothing that I can see relevant to the failed resume. I'm willing to dig given specific pointers, though. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jun 2 11:30:18 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/mapper/system-swap InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) MachineType: LENOVO 20BXCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic root=/dev/mapper/system-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: wayland-session bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker fuse kvm libvirt libvirtd lpadmin lxd mojo plugdev sambashare sbuild sudo uml-net _MarkForUpload: True dmi.bios.date: 12/14/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET67WW (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET67WW(1.31):bd12/14/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774771] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1774771/+attachment/5147826/+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/1774771 Title: Thinkpad T450s frequently hangs with black screen on resume Status in linux package in Ubuntu: New Bug description: My laptop, a Thinkpad T450s, often hangs with a black screen on resume from suspend; I have to power off and back on to recover. I'd estimate that this happens perhaps one in every two or three resumes, so it's pretty annoying. I'm currently running 18.04, but was on 16.04 up to a few months ago. I suspend relatively infrequently so I don't have great data, but my sense is that this happened occasionally on 16.04 but has become very much more frequent on 18.04. I haven't been able to find any useful log information about what the problem might be: syslog has log entries for suspending and then goes straight into the log of the next successful boot, with nothing that I can see relevant to the failed resume. I'm willing to dig given specific pointers, though. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jun 2 11:30:18 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/mapper/system-swap InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) MachineType: LENOVO 20BXCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic root=/dev/mapper/system-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: wayland-session bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker fuse kvm libvirt libvirtd lpadmin lxd mojo plugdev sambashare sbuild sudo uml-net _MarkForUpload: True dmi.bios.date: 12/14/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET67WW (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET67WW(1.31):bd12/14/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774771] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1774771/+attachment/5147825/+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/1774771 Title: Thinkpad T450s frequently hangs with black screen on resume Status in linux package in Ubuntu: New Bug description: My laptop, a Thinkpad T450s, often hangs with a black screen on resume from suspend; I have to power off and back on to recover. I'd estimate that this happens perhaps one in every two or three resumes, so it's pretty annoying. I'm currently running 18.04, but was on 16.04 up to a few months ago. I suspend relatively infrequently so I don't have great data, but my sense is that this happened occasionally on 16.04 but has become very much more frequent on 18.04. I haven't been able to find any useful log information about what the problem might be: syslog has log entries for suspending and then goes straight into the log of the next successful boot, with nothing that I can see relevant to the failed resume. I'm willing to dig given specific pointers, though. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jun 2 11:30:18 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/mapper/system-swap InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) MachineType: LENOVO 20BXCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic root=/dev/mapper/system-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: wayland-session bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker fuse kvm libvirt libvirtd lpadmin lxd mojo plugdev sambashare sbuild sudo uml-net _MarkForUpload: True dmi.bios.date: 12/14/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET67WW (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET67WW(1.31):bd12/14/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774771] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1774771/+attachment/5147820/+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/1774771 Title: Thinkpad T450s frequently hangs with black screen on resume Status in linux package in Ubuntu: New Bug description: My laptop, a Thinkpad T450s, often hangs with a black screen on resume from suspend; I have to power off and back on to recover. I'd estimate that this happens perhaps one in every two or three resumes, so it's pretty annoying. I'm currently running 18.04, but was on 16.04 up to a few months ago. I suspend relatively infrequently so I don't have great data, but my sense is that this happened occasionally on 16.04 but has become very much more frequent on 18.04. I haven't been able to find any useful log information about what the problem might be: syslog has log entries for suspending and then goes straight into the log of the next successful boot, with nothing that I can see relevant to the failed resume. I'm willing to dig given specific pointers, though. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jun 2 11:30:18 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/mapper/system-swap InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) MachineType: LENOVO 20BXCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic root=/dev/mapper/system-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: wayland-session bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker fuse kvm libvirt libvirtd lpadmin lxd mojo plugdev sambashare sbuild sudo uml-net _MarkForUpload: True dmi.bios.date: 12/14/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET67WW (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET67WW(1.31):bd12/14/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774771] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1774771/+attachment/5147811/+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/1774771 Title: Thinkpad T450s frequently hangs with black screen on resume Status in linux package in Ubuntu: New Bug description: My laptop, a Thinkpad T450s, often hangs with a black screen on resume from suspend; I have to power off and back on to recover. I'd estimate that this happens perhaps one in every two or three resumes, so it's pretty annoying. I'm currently running 18.04, but was on 16.04 up to a few months ago. I suspend relatively infrequently so I don't have great data, but my sense is that this happened occasionally on 16.04 but has become very much more frequent on 18.04. I haven't been able to find any useful log information about what the problem might be: syslog has log entries for suspending and then goes straight into the log of the next successful boot, with nothing that I can see relevant to the failed resume. I'm willing to dig given specific pointers, though. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jun 2 11:30:18 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/mapper/system-swap InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) MachineType: LENOVO 20BXCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic root=/dev/mapper/system-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: wayland-session bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker fuse kvm libvirt libvirtd lpadmin lxd mojo plugdev sambashare sbuild sudo uml-net _MarkForUpload: True dmi.bios.date: 12/14/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET67WW (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET67WW(1.31):bd12/14/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774771] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1774771/+attachment/5147824/+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/1774771 Title: Thinkpad T450s frequently hangs with black screen on resume Status in linux package in Ubuntu: New Bug description: My laptop, a Thinkpad T450s, often hangs with a black screen on resume from suspend; I have to power off and back on to recover. I'd estimate that this happens perhaps one in every two or three resumes, so it's pretty annoying. I'm currently running 18.04, but was on 16.04 up to a few months ago. I suspend relatively infrequently so I don't have great data, but my sense is that this happened occasionally on 16.04 but has become very much more frequent on 18.04. I haven't been able to find any useful log information about what the problem might be: syslog has log entries for suspending and then goes straight into the log of the next successful boot, with nothing that I can see relevant to the failed resume. I'm willing to dig given specific pointers, though. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jun 2 11:30:18 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/mapper/system-swap InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) MachineType: LENOVO 20BXCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic root=/dev/mapper/system-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: wayland-session bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker fuse kvm libvirt libvirtd lpadmin lxd mojo plugdev sambashare sbuild sudo uml-net _MarkForUpload: True dmi.bios.date: 12/14/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET67WW (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET67WW(1.31):bd12/14/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774771] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1774771/+attachment/5147819/+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/1774771 Title: Thinkpad T450s frequently hangs with black screen on resume Status in linux package in Ubuntu: New Bug description: My laptop, a Thinkpad T450s, often hangs with a black screen on resume from suspend; I have to power off and back on to recover. I'd estimate that this happens perhaps one in every two or three resumes, so it's pretty annoying. I'm currently running 18.04, but was on 16.04 up to a few months ago. I suspend relatively infrequently so I don't have great data, but my sense is that this happened occasionally on 16.04 but has become very much more frequent on 18.04. I haven't been able to find any useful log information about what the problem might be: syslog has log entries for suspending and then goes straight into the log of the next successful boot, with nothing that I can see relevant to the failed resume. I'm willing to dig given specific pointers, though. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jun 2 11:30:18 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/mapper/system-swap InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) MachineType: LENOVO 20BXCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic root=/dev/mapper/system-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: wayland-session bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker fuse kvm libvirt libvirtd lpadmin lxd mojo plugdev sambashare sbuild sudo uml-net _MarkForUpload: True dmi.bios.date: 12/14/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET67WW (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET67WW(1.31):bd12/14/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774771] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1774771/+attachment/5147812/+files/AudioDevicesInUse.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/1774771 Title: Thinkpad T450s frequently hangs with black screen on resume Status in linux package in Ubuntu: New Bug description: My laptop, a Thinkpad T450s, often hangs with a black screen on resume from suspend; I have to power off and back on to recover. I'd estimate that this happens perhaps one in every two or three resumes, so it's pretty annoying. I'm currently running 18.04, but was on 16.04 up to a few months ago. I suspend relatively infrequently so I don't have great data, but my sense is that this happened occasionally on 16.04 but has become very much more frequent on 18.04. I haven't been able to find any useful log information about what the problem might be: syslog has log entries for suspending and then goes straight into the log of the next successful boot, with nothing that I can see relevant to the failed resume. I'm willing to dig given specific pointers, though. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jun 2 11:30:18 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/mapper/system-swap InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) MachineType: LENOVO 20BXCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic root=/dev/mapper/system-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: wayland-session bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker fuse kvm libvirt libvirtd lpadmin lxd mojo plugdev sambashare sbuild sudo uml-net _MarkForUpload: True dmi.bios.date: 12/14/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET67WW (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET67WW(1.31):bd12/14/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774771] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1774771/+attachment/5147822/+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/1774771 Title: Thinkpad T450s frequently hangs with black screen on resume Status in linux package in Ubuntu: New Bug description: My laptop, a Thinkpad T450s, often hangs with a black screen on resume from suspend; I have to power off and back on to recover. I'd estimate that this happens perhaps one in every two or three resumes, so it's pretty annoying. I'm currently running 18.04, but was on 16.04 up to a few months ago. I suspend relatively infrequently so I don't have great data, but my sense is that this happened occasionally on 16.04 but has become very much more frequent on 18.04. I haven't been able to find any useful log information about what the problem might be: syslog has log entries for suspending and then goes straight into the log of the next successful boot, with nothing that I can see relevant to the failed resume. I'm willing to dig given specific pointers, though. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jun 2 11:30:18 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/mapper/system-swap InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) MachineType: LENOVO 20BXCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic root=/dev/mapper/system-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: wayland-session bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker fuse kvm libvirt libvirtd lpadmin lxd mojo plugdev sambashare sbuild sudo uml-net _MarkForUpload: True dmi.bios.date: 12/14/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET67WW (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET67WW(1.31):bd12/14/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774771] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1774771/+attachment/5147814/+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/1774771 Title: Thinkpad T450s frequently hangs with black screen on resume Status in linux package in Ubuntu: New Bug description: My laptop, a Thinkpad T450s, often hangs with a black screen on resume from suspend; I have to power off and back on to recover. I'd estimate that this happens perhaps one in every two or three resumes, so it's pretty annoying. I'm currently running 18.04, but was on 16.04 up to a few months ago. I suspend relatively infrequently so I don't have great data, but my sense is that this happened occasionally on 16.04 but has become very much more frequent on 18.04. I haven't been able to find any useful log information about what the problem might be: syslog has log entries for suspending and then goes straight into the log of the next successful boot, with nothing that I can see relevant to the failed resume. I'm willing to dig given specific pointers, though. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jun 2 11:30:18 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/mapper/system-swap InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) MachineType: LENOVO 20BXCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic root=/dev/mapper/system-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: wayland-session bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker fuse kvm libvirt libvirtd lpadmin lxd mojo plugdev sambashare sbuild sudo uml-net _MarkForUpload: True dmi.bios.date: 12/14/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET67WW (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET67WW(1.31):bd12/14/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774771] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1774771/+attachment/5147817/+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/1774771 Title: Thinkpad T450s frequently hangs with black screen on resume Status in linux package in Ubuntu: New Bug description: My laptop, a Thinkpad T450s, often hangs with a black screen on resume from suspend; I have to power off and back on to recover. I'd estimate that this happens perhaps one in every two or three resumes, so it's pretty annoying. I'm currently running 18.04, but was on 16.04 up to a few months ago. I suspend relatively infrequently so I don't have great data, but my sense is that this happened occasionally on 16.04 but has become very much more frequent on 18.04. I haven't been able to find any useful log information about what the problem might be: syslog has log entries for suspending and then goes straight into the log of the next successful boot, with nothing that I can see relevant to the failed resume. I'm willing to dig given specific pointers, though. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jun 2 11:30:18 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/mapper/system-swap InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) MachineType: LENOVO 20BXCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic root=/dev/mapper/system-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: wayland-session bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker fuse kvm libvirt libvirtd lpadmin lxd mojo plugdev sambashare sbuild sudo uml-net _MarkForUpload: True dmi.bios.date: 12/14/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET67WW (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET67WW(1.31):bd12/14/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774771] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1774771/+attachment/5147818/+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/1774771 Title: Thinkpad T450s frequently hangs with black screen on resume Status in linux package in Ubuntu: New Bug description: My laptop, a Thinkpad T450s, often hangs with a black screen on resume from suspend; I have to power off and back on to recover. I'd estimate that this happens perhaps one in every two or three resumes, so it's pretty annoying. I'm currently running 18.04, but was on 16.04 up to a few months ago. I suspend relatively infrequently so I don't have great data, but my sense is that this happened occasionally on 16.04 but has become very much more frequent on 18.04. I haven't been able to find any useful log information about what the problem might be: syslog has log entries for suspending and then goes straight into the log of the next successful boot, with nothing that I can see relevant to the failed resume. I'm willing to dig given specific pointers, though. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jun 2 11:30:18 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/mapper/system-swap InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) MachineType: LENOVO 20BXCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic root=/dev/mapper/system-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: wayland-session bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker fuse kvm libvirt libvirtd lpadmin lxd mojo plugdev sambashare sbuild sudo uml-net _MarkForUpload: True dmi.bios.date: 12/14/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET67WW (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET67WW(1.31):bd12/14/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774771] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1774771/+attachment/5147823/+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/1774771 Title: Thinkpad T450s frequently hangs with black screen on resume Status in linux package in Ubuntu: New Bug description: My laptop, a Thinkpad T450s, often hangs with a black screen on resume from suspend; I have to power off and back on to recover. I'd estimate that this happens perhaps one in every two or three resumes, so it's pretty annoying. I'm currently running 18.04, but was on 16.04 up to a few months ago. I suspend relatively infrequently so I don't have great data, but my sense is that this happened occasionally on 16.04 but has become very much more frequent on 18.04. I haven't been able to find any useful log information about what the problem might be: syslog has log entries for suspending and then goes straight into the log of the next successful boot, with nothing that I can see relevant to the failed resume. I'm willing to dig given specific pointers, though. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jun 2 11:30:18 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/mapper/system-swap InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) MachineType: LENOVO 20BXCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic root=/dev/mapper/system-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: wayland-session bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker fuse kvm libvirt libvirtd lpadmin lxd mojo plugdev sambashare sbuild sudo uml-net _MarkForUpload: True dmi.bios.date: 12/14/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET67WW (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET67WW(1.31):bd12/14/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774771] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1774771/+attachment/5147821/+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/1774771 Title: Thinkpad T450s frequently hangs with black screen on resume Status in linux package in Ubuntu: New Bug description: My laptop, a Thinkpad T450s, often hangs with a black screen on resume from suspend; I have to power off and back on to recover. I'd estimate that this happens perhaps one in every two or three resumes, so it's pretty annoying. I'm currently running 18.04, but was on 16.04 up to a few months ago. I suspend relatively infrequently so I don't have great data, but my sense is that this happened occasionally on 16.04 but has become very much more frequent on 18.04. I haven't been able to find any useful log information about what the problem might be: syslog has log entries for suspending and then goes straight into the log of the next successful boot, with nothing that I can see relevant to the failed resume. I'm willing to dig given specific pointers, though. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jun 2 11:30:18 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/mapper/system-swap InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) MachineType: LENOVO 20BXCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic root=/dev/mapper/system-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: wayland-session bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker fuse kvm libvirt libvirtd lpadmin lxd mojo plugdev sambashare sbuild sudo uml-net _MarkForUpload: True dmi.bios.date: 12/14/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET67WW (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET67WW(1.31):bd12/14/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774771] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1774771/+attachment/5147816/+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/1774771 Title: Thinkpad T450s frequently hangs with black screen on resume Status in linux package in Ubuntu: New Bug description: My laptop, a Thinkpad T450s, often hangs with a black screen on resume from suspend; I have to power off and back on to recover. I'd estimate that this happens perhaps one in every two or three resumes, so it's pretty annoying. I'm currently running 18.04, but was on 16.04 up to a few months ago. I suspend relatively infrequently so I don't have great data, but my sense is that this happened occasionally on 16.04 but has become very much more frequent on 18.04. I haven't been able to find any useful log information about what the problem might be: syslog has log entries for suspending and then goes straight into the log of the next successful boot, with nothing that I can see relevant to the failed resume. I'm willing to dig given specific pointers, though. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jun 2 11:30:18 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/mapper/system-swap InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) MachineType: LENOVO 20BXCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic root=/dev/mapper/system-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: wayland-session bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker fuse kvm libvirt libvirtd lpadmin lxd mojo plugdev sambashare sbuild sudo uml-net _MarkForUpload: True dmi.bios.date: 12/14/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET67WW (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET67WW(1.31):bd12/14/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774771] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1774771/+attachment/5147813/+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/1774771 Title: Thinkpad T450s frequently hangs with black screen on resume Status in linux package in Ubuntu: New Bug description: My laptop, a Thinkpad T450s, often hangs with a black screen on resume from suspend; I have to power off and back on to recover. I'd estimate that this happens perhaps one in every two or three resumes, so it's pretty annoying. I'm currently running 18.04, but was on 16.04 up to a few months ago. I suspend relatively infrequently so I don't have great data, but my sense is that this happened occasionally on 16.04 but has become very much more frequent on 18.04. I haven't been able to find any useful log information about what the problem might be: syslog has log entries for suspending and then goes straight into the log of the next successful boot, with nothing that I can see relevant to the failed resume. I'm willing to dig given specific pointers, though. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jun 2 11:30:18 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/mapper/system-swap InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) MachineType: LENOVO 20BXCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic root=/dev/mapper/system-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: wayland-session bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker fuse kvm libvirt libvirtd lpadmin lxd mojo plugdev sambashare sbuild sudo uml-net _MarkForUpload: True dmi.bios.date: 12/14/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET67WW (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET67WW(1.31):bd12/14/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774771] [NEW] Thinkpad T450s frequently hangs with black screen on resume
Public bug reported: My laptop, a Thinkpad T450s, often hangs with a black screen on resume from suspend; I have to power off and back on to recover. I'd estimate that this happens perhaps one in every two or three resumes, so it's pretty annoying. I'm currently running 18.04, but was on 16.04 up to a few months ago. I suspend relatively infrequently so I don't have great data, but my sense is that this happened occasionally on 16.04 but has become very much more frequent on 18.04. I haven't been able to find any useful log information about what the problem might be: syslog has log entries for suspending and then goes straight into the log of the next successful boot, with nothing that I can see relevant to the failed resume. I'm willing to dig given specific pointers, though. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jun 2 11:30:18 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/mapper/system-swap InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) MachineType: LENOVO 20BXCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic root=/dev/mapper/system-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: wayland-session bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker fuse kvm libvirt libvirtd lpadmin lxd mojo plugdev sambashare sbuild sudo uml-net _MarkForUpload: True dmi.bios.date: 12/14/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET67WW (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET67WW(1.31):bd12/14/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-collected bionic wayland-session ** Package changed: linux-signed (Ubuntu) => linux (Ubuntu) ** Tags added: apport-collected ** Description changed: My laptop, a Thinkpad T450s, often hangs with a black screen on resume from suspend; I have to power off and back on to recover. I'd estimate that this happens perhaps one in every two or three resumes, so it's pretty annoying. I'm currently running 18.04, but was on 16.04 up to a few months ago. I suspend relatively infrequently so I don't have great data, but my sense is that this happened occasionally on 16.04 but has become very much more frequent on 18.04. I haven't been able to find any useful log information about what the problem might be: syslog has log entries for suspending and then goes straight into the log of the next successful boot, with nothing that I can see relevant to the failed resume. I'm willing to dig given specific pointers, though. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jun 2 11:30:18 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-03-01 (1918 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) + --- + ApportVersion: 2.20.9-0ubuntu7.1 + Architecture: amd64 + CurrentDesktop: GNOME + DistroRelease: Ubuntu 18.04 + EcryptfsInUse: Yes + HibernationDevice: RESUME=/dev/mapper/system-swap + InstallationDate: Inst
[Kernel-packages] [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
** Attachment removed: "C72957374002D7EF17AED2B17BEF18FE.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264789/+attachment/4870526/+files/C72957374002D7EF17AED2B17BEF18FE.jpg ** Attachment removed: "428E18A7EF2A80EE1218968A65B3C947.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264789/+attachment/4875133/+files/428E18A7EF2A80EE1218968A65B3C947.jpg ** Attachment removed: "9791D64EC53F47A1CB31EEE7A11E24B4.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264789/+attachment/4879827/+files/9791D64EC53F47A1CB31EEE7A11E24B4.jpg ** Attachment removed: "AEE8B53C164C793EE55DF5B276E714BA.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264789/+attachment/4882217/+files/AEE8B53C164C793EE55DF5B276E714BA.jpg ** Attachment removed: "02DFF7ADFCAF6D004E693D7906C06B8B.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264789/+attachment/4886118/+files/02DFF7ADFCAF6D004E693D7906C06B8B.jpg ** Attachment removed: "907BCBC20D4EDC1872A10011C91D6A94.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264789/+attachment/4888710/+files/907BCBC20D4EDC1872A10011C91D6A94.jpg ** Attachment removed: "07FA491269357B5FE8D8F2586E5DA865.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264789/+attachment/4916079/+files/07FA491269357B5FE8D8F2586E5DA865.jpg ** Attachment removed: "A15A27255BA4C89123D076C12CC37C7A.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264789/+attachment/4900542/+files/A15A27255BA4C89123D076C12CC37C7A.jpg ** Attachment removed: "D4D79674A43A0C32F3BB8BD963AAB4CF.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264789/+attachment/4917933/+files/D4D79674A43A0C32F3BB8BD963AAB4CF.jpg ** Attachment removed: "BBE1AB4128BE8BC0.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264789/+attachment/4947459/+files/BBE1AB4128BE8BC0.jpg ** Attachment removed: "59A8518FF2EC83ED.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264789/+attachment/4974398/+files/59A8518FF2EC83ED.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/264789 Title: USB Hard Drive Not Accessible, vol_id hangs Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Intrepid: Invalid Bug description: I updated to 2.6.27-2 today, and one of my hard drives is no longer recognized. It is in a Vantec NexStar GX enclosure, and was working fine on .26, and continues to work fine on a Hardy machine. Here is the dmesg for it: [ 6722.944029] usb 5-5: new high speed USB device using ehci_hcd and address 27 [ 6723.077863] usb 5-5: configuration #1 chosen from 1 choice [ 6723.079511] hub 5-5:1.0: USB hub found [ 6723.080345] hub 5-5:1.0: 4 ports detected [ 6732.712034] usb 5-5: reset high speed USB device using ehci_hcd and address 27 [ 6733.124011] usb 5-5.1: new high speed USB device using ehci_hcd and address 28 [ 6733.364598] usb 5-5.1: configuration #1 chosen from 1 choice [ 6733.365180] scsi17 : SCSI emulation for USB Mass Storage devices [ 6733.365818] usb-storage: device found at 28 [ 6733.365830] usb-storage: waiting for device to settle before scanning [ 6738.364276] usb-storage: device scan complete [ 6738.361002] scsi 17:0:0:0: Direct-Access ST340063 2A 3.04 PQ: 0 ANSI: 0 [ 6738.361002] sd 17:0:0:0: [sdm] 781422769 512-byte hardware sectors (400088 MB) [ 6738.361002] sd 17:0:0:0: [sdm] Write Protect is off [ 6738.361002] sd 17:0:0:0: [sdm] Mode Sense: 03 00 00 00 [ 6738.361002] sd 17:0:0:0: [sdm] Assuming drive cache: write through [ 6738.361002] sd 17:0:0:0: [sdm] 781422769 512-byte hardware sectors (400088 MB) [ 6738.370354] sd 17:0:0:0: [sdm] Write Protect is off [ 6738.370362] sd 17:0:0:0: [sdm] Mode Sense: 03 00 00 00 [ 6738.370365] sd 17:0:0:0: [sdm] Assuming drive cache: write through [ 6738.371516] sdm: sdm1 [ 6738.418089] sd 17:0:0:0: [sdm] Attached SCSI disk [ 6738.418995] sd 17:0:0:0: Attached scsi generic sg8 type 0 [ 6738.656598] sd 17:0:0:0: [sdm] Sense Key : No Sense [current] [ 6738.656614] sd 17:0:0:0: [sdm] Add. Sense: No additional sense information From there, the last 2 lines about Sense Key and Add Sense repeat over and over again. The 4 port hub that is a part of the enclosure continues to work fine though, with a floppy drive, a printer, and another hard drive. I have a Vantec NexStar 3 enclosure as well, and it is working just fine. Dmesg for the working enclosure: [ 4281.996024] usb 5-3: new high speed USB device using ehci_hcd and address 19 [ 4282.131863] usb 5-3: configuration #1 chosen from 1 choice [ 4282.133222] scsi12 : SCSI emulation for USB Mass Storage devices [ 4282.133561] usb-storage: device found at 19 [ 4282.133566] usb-storage: waiting for device to settle before scanning [ 4287.132002] u
[Kernel-packages] [Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: intel-microcode (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759920 Title: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux- image-4.13.0-37-generic) Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in intel-microcode source package in Xenial: New Status in linux source package in Xenial: New Status in intel-microcode source package in Artful: Confirmed Status in linux source package in Artful: Confirmed Bug description: I don't know if this is a problem with the kernel or the microcode, but we have a significant number of computers in our organization (on both 16.04 and 17.10) that fail if they have both updated. Booting with either linux-image-4.13.0-36-generic or intel-microcode 3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1744546] Re: systemd boot and kernel crash. tpm_crb MSFT0101:00, watchdog: BUG: soft lockup
** Project changed: launchpad => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1744546 Title: systemd boot and kernel crash.tpm_crb MSFT0101:00, watchdog: BUG: soft lockup Status in linux package in Ubuntu: New Bug description: I don't know how to explain the bug. The crash is for all distro linux with a kernel > 4.10 (so ubuntu, fedora, and others) The bug is tpm_crb MSFT0101:00: [firmware bug] acpi region does not cover... and watchdog: BUG: soft lockup - CPU#0 stuck for 23s... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743427] Re: Black screen with iMac 2011 and ATI Radeon 6970M
** Project changed: launchpad => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1743427 Title: Black screen with iMac 2011 and ATI Radeon 6970M Status in linux package in Ubuntu: Incomplete Bug description: Dear community! I have installed Ubuntu 17.10 (also tried 17.04 and 16.04), and the system gets a black screen on boot with all tested Ubuntu versions. Also ping and ssh to the host does not work. The fan's are running, the screen is black and nothing more. When i insert in Grub nomodeset, the system can boot. I have also tested Kernel 4.14 and 4.15RC7. Hardware Information: 00:02.0 Display controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Blackcomb [Radeon HD 6970M/6990M] Thanks for help or any hint. Best regards, Hans To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743427/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743125] Re: Wi-Fi doesn't work since 4.4.0-104
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1743125 Title: Wi-Fi doesn't work since 4.4.0-104 Status in linux package in Ubuntu: Incomplete Bug description: since 4.4.0-104 kernels my Wi-Fi isn't working. It doesn't show up in Network Manager, wireless network device is not visible via ifconfig/ip a l commands, though, it's visible for lspci. I had to revert back to 104 kernel. Wi-Fi card is: Broadcom Corporation BCM43142 802.11b/g/n (rev 01) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743125/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 839157] Re: Bluetooth applet (OBEX send/browse) does not work since Natty (after bluetoothd 4.84 exactly)
** Attachment removed: "0D5EAE0F25F0BA20.jpg" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/839157/+attachment/4920575/+files/0D5EAE0F25F0BA20.jpg ** Attachment removed: "A7435C9644AEB554.jpg" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/839157/+attachment/4994317/+files/A7435C9644AEB554.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/839157 Title: Bluetooth applet (OBEX send/browse) does not work since Natty (after bluetoothd 4.84 exactly) Status in bluez package in Ubuntu: Expired Status in gnome-bluetooth package in Ubuntu: Invalid Bug description: I have Ubuntu Natty 11.04 and a Nokia N81 (Symbian S60v3.1). In Ubuntu 10.04 (Lucid) and 10.10 (Maverick) bluetooth file transfers do work fast and stable on my hardware. Since Natty it stopped working all together! UPDATE 26-2-2012: everything works again if the executable /usr/sbin/bluetoothd (4.91 in Natty) is replaced with 4.84 or earlier. I verified this workaround on several machines and with the Live-CD of Natty. Precise alpha 2 is affected too. (see also my comment 30 below) The attachment shows the output of "sudo hcidump -XYt" when browsing fails (bluetooth-applet - menu - - Browse files...) Running " bluetooth-applet -d" in a terminal and trying to browse and send files shows this: ** Message: adding killswitch idx 1 state KILLSWITCH_STATE_UNBLOCKED ** Message: adding killswitch idx 4 state KILLSWITCH_STATE_UNBLOCKED ** Message: killswitch 1 is KILLSWITCH_STATE_UNBLOCKED ** Message: killswitch 4 is KILLSWITCH_STATE_UNBLOCKED ** Message: killswitches state KILLSWITCH_STATE_UNBLOCKED ** (bluetooth-applet:4108): DEBUG: Unhandled UUID 111b--1000-8000-00805f9b34fb (0x111b) ** (bluetooth-applet:4108): DEBUG: Unhandled UUID 5005--1000-8000-0002ee01 (0x5005) ** (bluetooth-applet:4108): DEBUG: Unhandled UUID 5601--1000-8000-0002ee01 (0x5601) ** Message: killswitch 1 is KILLSWITCH_STATE_UNBLOCKED ** Message: killswitch 4 is KILLSWITCH_STATE_UNBLOCKED ** Message: killswitches state KILLSWITCH_STATE_UNBLOCKED ** (bluetooth-sendto:4120): DEBUG: Unhandled UUID 111b--1000-8000-00805f9b34fb (0x111b) ** (bluetooth-sendto:4120): DEBUG: Unhandled UUID 5005--1000-8000-0002ee01 (0x5005) ** (bluetooth-sendto:4120): DEBUG: Unhandled UUID 5601--1000-8000-0002ee01 (0x5601) And I saw interesting lines in /var/log/auth.log: oliverhp dbus-daemon: [system] Rejected send message, 2 matched rules; type="method_return", sender=":1.99" (uid=0 pid=3356 comm="/usr/sbin/bluetoothd --udev ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply=0 destination=":1.139" (uid=1000 pid=3768 comm="bluetooth-applet -d ")) ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: bluez 4.91-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic i686 Architecture: i386 Date: Fri Sep 2 00:10:38 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427) InterestingModules: rfcomm sco bnep l2cap btusb bluetooth MachineType: Hewlett-Packard HP Compaq nx8220 (PY517EA#ABD) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=de_CH:en PATH=(custom, user) LANG=de_CH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic root=UUID=a4380962-8df8-486d-a8e3-2232227f97aa ro nosplash elevator=deadline SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68DTV Ver. F.18 dmi.board.name: 0934 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 43.1D dmi.chassis.asset.tag: oliverhp dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68DTVVer.F.18:bd07/24/2009:svnHewlett-Packard:pnHPCompaqnx8220(PY517EA#ABD):pvrF.18:rvnHewlett-Packard:rn0934:rvrKBCVersion43.1D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq nx8220 (PY517EA#ABD) dmi.product.version: F.18 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:16:41:7C:AC:64 ACL MTU: 377:10 SCO MTU: 16:0 UP RUNNING PSCAN ISCAN RX bytes:11936 acl:127 sco:0 events:287 errors:0 TX bytes:3254 acl:110 sco:0 commands:102 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/839157/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1696154] Re: [17.10 FEAT] Sign POWER host/NV kernels
We believe the Launchpad side of this is done, so closing this task. ** Changed in: launchpad Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1696154 Title: [17.10 FEAT] Sign POWER host/NV kernels Status in Launchpad itself: Fix Released Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux-signed package in Ubuntu: In Progress Bug description: Feature Description: Sign POWER host and NV kernels with sign-file in anticipation of POWER secure boot. Provide the associated certificate. Ideally it would be possible to reuse the UEFI shim private key and certificate used to sign and verify x86_64 kernels. More details to follow. Guest kernels will be addressed in a future separate feature request. Business Case: As a system administrator I want to verify the integrity of my kernels so that I can prevent malicious kernels from being executed. Use Case: Signed POWER kernels will be validated by OPAL as OpenPOWER systems boot when keys are properly installed and the system is booted in secure mode. Test Case: Sign and install a POWER kernel on an OpenPOWER machine with a firmware level that supports secure boot. Install a PK, distro KEK certificat, and distro DB certificate. Boot the system and verify that it will boot the kernel. Negative tests: Separately remove the signature, install an usigned kernel, and modify the kernel image and test that the kernel will not boot. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1696154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720197] Re: Every second(?) boot fails to display anything [MSHYBRID mode]
** Package changed: grub (Ubuntu) => grub2 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720197 Title: Every second(?) boot fails to display anything [MSHYBRID mode] Status in grub2 package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: When this laptop's firmware is set to MSHYBRID mode (intel/nvidia switchable graphics) it seems that every second boot it fails to display anything. This appears to be regardless of whether or not I enter the grub menu. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 3020 F pulseaudio CurrentDesktop: GNOME Date: Thu Sep 28 13:41:53 2017 InstallationDate: Installed on 2017-09-20 (8 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Oryx Pro ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic.efi.signed root=ZFS=rpool/system ro RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA1 02/20/2017 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1720197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1707409] Re: testsuite fails under qemu (SIGILL) works fine on real hw [missing getrandom 384 syscall]
qemu isn't involved. We intentionally run armhf builds on an arm64 kernel (with an appropriate personality set) because this allows us to make denser use of our build resources; I don't expect this to change. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1707409 Title: testsuite fails under qemu (SIGILL) works fine on real hw [missing getrandom 384 syscall] Status in launchpad-buildd: New Status in linux package in Ubuntu: Invalid Status in qemu package in Ubuntu: Confirmed Bug description: Hello, after spending a lot of time debugging notmuch failure under armhf, we came to a conclusion: it started to fail when the infra moved to a new kernel 3.2 to a 4.2, and moved under qemu/kvm environment. the latest successful build is here created on 2016-03-13 https://launchpad.net/ubuntu/+source/notmuch/0.21-3ubuntu2/+build/9344826 and the first bad is this one: Started on 2016-08-31 https://launchpad.net/ubuntu/+source/notmuch/0.22.1-2ubuntu1/+build/1062 Kernel version: Linux kishi10 3.2.0-98-highbank #138-Ubuntu SMP PREEMPT Mon Jan 11 13:24:41 UTC 2016 armv7l Kernel version: Linux bos01-arm64-024 4.2.0-42-generic #49-Ubuntu SMP Tue Jun 28 21:24:20 UTC 2016 aarch64 so, in the first case armhf was ran on top of an armv7 kernel, in the other case it became an arm64 one this might not even be a regression in qemu/kvm, but rather a change in buildd system that spot a new bug doing a xenial build failed aswell, so I presume this is not a toolchain regression (also because it works fine on real HW), but a qemu/linux bug. I did run the test under strace/valgrind, I can't do much more testing, but I hope the logs can be useful for you https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+build/13169431 https://launchpadlibrarian.net/331134898/buildlog_ubuntu-artful-armhf.notmuch_0.25-2ubuntu1_BUILDING.txt.gz You can see the strace/valgrind outputs between "BEGIN" and "END" keywords To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1707409/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 711397] Re: package firmware-b43legacy-installer 4.178.10.4-5 failed to install/upgrade due to unsupported hardware
** Attachment removed: "4827E1007C3C6FEF.jpg" https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/711397/+attachment/4928025/+files/4827E1007C3C6FEF.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to b43-fwcutter in Ubuntu. https://bugs.launchpad.net/bugs/711397 Title: package firmware-b43legacy-installer 4.178.10.4-5 failed to install/upgrade due to unsupported hardware Status in b43-fwcutter package in Ubuntu: Fix Released Bug description: All of the bug reports collected here deal with the package installation failing due to unsupported hardware. Binary package hint: b43-fwcutter it failed ProblemType: PackageDistroRelease: Ubuntu 11.04 Package: firmware-b43legacy-installer 4.178.10.4-5 ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2 Uname: Linux 2.6.38-1-generic i686 NonfreeKernelModules: wl Architecture: i386 Date: Tue Feb 1 11:55:39 2011 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 PackageArchitecture: allSourcePackage: b43-fwcutter Title: package firmware-b43legacy-installer 4.178.10.4-5 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/711397/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1696154] Re: [17.10 FEAT] Sign POWER host/NV kernels
** Also affects: launchpad Importance: Undecided Status: New ** Changed in: launchpad Status: New => Fix Committed ** Changed in: launchpad Importance: Undecided => High ** Changed in: launchpad Assignee: (unassigned) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1696154 Title: [17.10 FEAT] Sign POWER host/NV kernels Status in Launchpad itself: Fix Committed Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Bug description: Feature Description: Sign POWER host and NV kernels with sign-file in anticipation of POWER secure boot. Provide the associated certificate. Ideally it would be possible to reuse the UEFI shim private key and certificate used to sign and verify x86_64 kernels. More details to follow. Guest kernels will be addressed in a future separate feature request. Business Case: As a system administrator I want to verify the integrity of my kernels so that I can prevent malicious kernels from being executed. Use Case: Signed POWER kernels will be validated by OPAL as OpenPOWER systems boot when keys are properly installed and the system is booted in secure mode. Test Case: Sign and install a POWER kernel on an OpenPOWER machine with a firmware level that supports secure boot. Install a PK, distro KEK certificat, and distro DB certificate. Boot the system and verify that it will boot the kernel. Negative tests: Separately remove the signature, install an usigned kernel, and modify the kernel image and test that the kernel will not boot. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1696154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706499] Re: NMI Watchdog Soft Lockup CPU Frozen for 22s
** Information type changed from Private to Public ** Project changed: null-and-void => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1706499 Title: NMI Watchdog Soft Lockup CPU Frozen for 22s Status in linux package in Ubuntu: Confirmed Bug description: Whenever switching from high to low, or low to high CPU loads I encounter the attached lockup. This happens at least twice daily when the server is left alone, more often when it actually does anything. The CPU# changes with each crash, but seems to always be for 22s. ul 25 08:01:59 necronomicon kernel: [32989.183560] [ cut here ] Jul 25 08:01:59 necronomicon kernel: [32989.183569] WARNING: CPU: 0 PID: 0 at /build/linux-Fsa3B1/linux-4.10.0/net/sched/sch_generic.c:316 dev_watchdog+0x22c/0x230 Jul 25 08:01:59 necronomicon kernel: [32989.183571] NETDEV WATCHDOG: enp37s0 (r8169): transmit queue 0 timed out Jul 25 08:01:59 necronomicon kernel: [32989.183572] Modules linked in: binfmt_misc nls_iso8859_1 joydev input_leds snd_hda_codec_hdmi snd_hda_codec_realtek eeepc_wmi snd_hda_codec_generic asus_wmi snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_timer snd soundcore sparse_keymap ccp edac_mce_amd edac_core shpchp i2c_piix4 kvm irqbypass i2c_designware_platform i2c_designware_core 8250_dw mac_hid ib_iser rdma_cm iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid nouveau crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc mxm_wmi video i2c_algo_bit ttm drm_kms_helper aesni_intel syscopyarea aes_x86_64 sysfillrect Jul 25 08:01:59 necronomicon kernel: [32989.183610] crypto_simd sysimgblt glue_helper fb_sys_fops cryptd drm r8169 mii ahci libahci wmi gpio_amdpt fjes gpio_generic Jul 25 08:01:59 necronomicon kernel: [32989.183619] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G L 4.10.0-28-generic #32-Ubuntu Jul 25 08:01:59 necronomicon kernel: [32989.183620] Hardware name: System manufacturer System Product Name/PRIME B350M-A, BIOS 0805 06/20/2017 Jul 25 08:01:59 necronomicon kernel: [32989.183621] Call Trace: Jul 25 08:01:59 necronomicon kernel: [32989.183623] Jul 25 08:01:59 necronomicon kernel: [32989.183627] dump_stack+0x63/0x81 Jul 25 08:01:59 necronomicon kernel: [32989.183629] __warn+0xcb/0xf0 Jul 25 08:01:59 necronomicon kernel: [32989.183631] warn_slowpath_fmt+0x5f/0x80 Jul 25 08:01:59 necronomicon kernel: [32989.183634] dev_watchdog+0x22c/0x230 Jul 25 08:01:59 necronomicon kernel: [32989.183637] ? qdisc_rcu_free+0x50/0x50 Jul 25 08:01:59 necronomicon kernel: [32989.183639] call_timer_fn+0x35/0x140 Jul 25 08:01:59 necronomicon kernel: [32989.183641] run_timer_softirq+0x215/0x4b0 Jul 25 08:01:59 necronomicon kernel: [32989.183643] ? ktime_get+0x41/0xb0 Jul 25 08:01:59 necronomicon kernel: [32989.183646] ? lapic_next_event+0x1d/0x30 Jul 25 08:01:59 necronomicon kernel: [32989.183648] ? clockevents_program_event+0x7f/0x120 Jul 25 08:01:59 necronomicon kernel: [32989.183651] __do_softirq+0x104/0x2af Jul 25 08:01:59 necronomicon kernel: [32989.183654] irq_exit+0xb6/0xc0 Jul 25 08:01:59 necronomicon kernel: [32989.183656] smp_apic_timer_interrupt+0x3d/0x50 Jul 25 08:01:59 necronomicon kernel: [32989.183659] apic_timer_interrupt+0x89/0x90 Jul 25 08:01:59 necronomicon kernel: [32989.183661] RIP: 0010:native_safe_halt+0x6/0x10 Jul 25 08:01:59 necronomicon kernel: [32989.183662] RSP: 0018:bec03de0 EFLAGS: 0246 ORIG_RAX: ff10 Jul 25 08:01:59 necronomicon kernel: [32989.183665] RAX: RBX: bec10500 RCX: Jul 25 08:01:59 necronomicon kernel: [32989.183666] RDX: RSI: RDI: Jul 25 08:01:59 necronomicon kernel: [32989.183667] RBP: bec03de0 R08: 0100 R09: 1e001b9b5d00 Jul 25 08:01:59 necronomicon kernel: [32989.183668] R10: 0001007cafbd R11: R12: Jul 25 08:01:59 necronomicon kernel: [32989.183668] R13: bec10500 R14: R15: Jul 25 08:01:59 necronomicon kernel: [32989.183670] Jul 25 08:01:59 necronomicon kernel: [32989.183673] default_idle+0x20/0xd0 Jul 25 08:01:59 necronomicon kernel: [32989.183675] arch_cpu_idle+0xf/0x20 Jul 25 08:01:59 necronomicon kernel: [32989.183677] default_idle_call+0x23/0x30 Jul 25 08:01:59 necronomicon kernel: [32989.183679] do_idle+0x16f/0x200 Jul 25 08:01:59 necronomicon kernel: [32989.183682] cpu_startup_entry+0x71/0x80 Jul 25 08:01:59 necronomico
[Kernel-packages] [Bug 711397] Re: package firmware-b43legacy-installer 4.178.10.4-5 failed to install/upgrade due to unsupported hardware
** Attachment removed: "3009F87FCE3BCB798B85F6CD7A6EC791.jpg" https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/711397/+attachment/4908518/+files/3009F87FCE3BCB798B85F6CD7A6EC791.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to b43-fwcutter in Ubuntu. https://bugs.launchpad.net/bugs/711397 Title: package firmware-b43legacy-installer 4.178.10.4-5 failed to install/upgrade due to unsupported hardware Status in b43-fwcutter package in Ubuntu: Fix Released Bug description: All of the bug reports collected here deal with the package installation failing due to unsupported hardware. Binary package hint: b43-fwcutter it failed ProblemType: PackageDistroRelease: Ubuntu 11.04 Package: firmware-b43legacy-installer 4.178.10.4-5 ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2 Uname: Linux 2.6.38-1-generic i686 NonfreeKernelModules: wl Architecture: i386 Date: Tue Feb 1 11:55:39 2011 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 PackageArchitecture: allSourcePackage: b43-fwcutter Title: package firmware-b43legacy-installer 4.178.10.4-5 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/711397/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1707409] Re: testsuite fails under qemu (SIGILL) works fine on real hw
I think it's very unlikely indeed that this is a Launchpad bug, and we're not here to go on fishing expeditions for you testing random things. qemu/kernel developers are generally better placed to be able to bisect this sort of thing. Of course you can reopen this if there turns out to be some evidence that this is in fact a Launchpad bug. ** Project changed: launchpad => launchpad-buildd ** Changed in: launchpad-buildd Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1707409 Title: testsuite fails under qemu (SIGILL) works fine on real hw Status in launchpad-buildd: Invalid Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Bug description: Hello, after spending a lot of time debugging notmuch failure under armhf, we came to a conclusion: it started to fail when the infra moved to a new kernel 3.2 to a 4.2, and moved under qemu/kvm environment. the latest successful build is here created on 2016-03-13 https://launchpad.net/ubuntu/+source/notmuch/0.21-3ubuntu2/+build/9344826 and the first bad is this one: Started on 2016-08-31 https://launchpad.net/ubuntu/+source/notmuch/0.22.1-2ubuntu1/+build/1062 Kernel version: Linux kishi10 3.2.0-98-highbank #138-Ubuntu SMP PREEMPT Mon Jan 11 13:24:41 UTC 2016 armv7l Kernel version: Linux bos01-arm64-024 4.2.0-42-generic #49-Ubuntu SMP Tue Jun 28 21:24:20 UTC 2016 aarch64 so, in the first case armhf was ran on top of an armv7 kernel, in the other case it became an arm64 one this might not even be a regression in qemu/kvm, but rather a change in buildd system that spot a new bug doing a xenial build failed aswell, so I presume this is not a toolchain regression (also because it works fine on real HW), but a qemu/linux bug. I did run the test under strace/valgrind, I can't do much more testing, but I hope the logs can be useful for you https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+build/13169431 https://launchpadlibrarian.net/331134898/buildlog_ubuntu-artful-armhf.notmuch_0.25-2ubuntu1_BUILDING.txt.gz You can see the strace/valgrind outputs between "BEGIN" and "END" keywords To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1707409/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 205715] Re: couldn't start with 2.6.24-12
** Attachment removed: "84940DEB9D11DDF4993BB4FB101A73FE.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/205715/+attachment/4874857/+files/84940DEB9D11DDF4993BB4FB101A73FE.jpg ** Attachment removed: "6FCA37363A8172A3CCCD277ABB513F8C.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/205715/+attachment/4876688/+files/6FCA37363A8172A3CCCD277ABB513F8C.jpg ** Attachment removed: "A50E7465BD99462CE5D6502EADE88863.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/205715/+attachment/4907036/+files/A50E7465BD99462CE5D6502EADE88863.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/205715 Title: couldn't start with 2.6.24-12 Status in linux package in Ubuntu: Fix Released Bug description: Problem found with 2.6.24-12 IBM ThinkPad T30 Starting in normal mode i found the following [50.261006] intel_rng: FWH not detected and in recovery mode [41.135147] input: TPPS/2 IBM TrackPoint as /devices/platform/i8047/serio1/serio2/input/input8 I start ubuntu choosing the previous release, some clue for this issue. Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/205715/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 448332] Re: BUG: scheduling while atomic: swapper/0/0x10010000
** Attachment removed: "BE85B521302FA812095AAD86CB9BBF40.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/448332/+attachment/4907504/+files/BE85B521302FA812095AAD86CB9BBF40.jpg ** Attachment removed: "8F3F4E6C909ED2C4649350E16E03E08D.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/448332/+attachment/4905982/+files/8F3F4E6C909ED2C4649350E16E03E08D.jpg ** Attachment removed: "3F2DE1215ABF040DC9B043BB0B99.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/448332/+attachment/4905329/+files/3F2DE1215ABF040DC9B043BB0B99.jpg ** Attachment removed: "5F929AB408CB16D2CCFE00045E60B142.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/448332/+attachment/4903806/+files/5F929AB408CB16D2CCFE00045E60B142.jpg ** Attachment removed: "CC05DDF1329CE548ACA7C7BEC2398D5C.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/448332/+attachment/4887522/+files/CC05DDF1329CE548ACA7C7BEC2398D5C.jpg ** Attachment removed: "6712B9E4898906886B784D6C79C1FB9E.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/448332/+attachment/4881659/+files/6712B9E4898906886B784D6C79C1FB9E.jpg ** Attachment removed: "D38120AA2B531881BD116706761299A7.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/448332/+attachment/4879723/+files/D38120AA2B531881BD116706761299A7.jpg ** Attachment removed: "9C0FC04D97AE81273DAF71B0E6A6AF15.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/448332/+attachment/4876290/+files/9C0FC04D97AE81273DAF71B0E6A6AF15.jpg ** Attachment removed: "373288957559C31680EC591CAC93C179.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/448332/+attachment/4874799/+files/373288957559C31680EC591CAC93C179.jpg ** Attachment removed: "0BD7F2C77CD05A9E440A3C29F8F184A1.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/448332/+attachment/4872081/+files/0BD7F2C77CD05A9E440A3C29F8F184A1.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/448332 Title: BUG: scheduling while atomic: swapper/0/0x1001 Status in linux package in Ubuntu: Won't Fix Bug description: Binary package hint: linux-image-2.6.31-13-generic After updating to kernel 2.6.31-13-generic my system became more unstable Description:Ubuntu karmic (development branch) Release:9.10 Installed: 2.6.31-13.43 Candidate: 2.6.31-13.43 Version table: *** 2.6.31-13.43 0 500 http://br.archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status ProblemType: KernelOops Annotation: Your system might become unstable now and might need to be restarted. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andre 21242 F pulseaudio andre 21244 F kmix CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfe9fc000 irq 21' Mixer name : 'SigmaTel STAC9228' Components : 'HDA:14f12c06,14f1000f,0010 HDA:10951392,10280242,0010 HDA:83847616,10280242,00100402' Controls : 33 Simple ctrls : 20 Date: Sat Oct 10 13:08:30 2009 DistroRelease: Ubuntu 9.10 Failure: oops HibernationDevice: RESUME=UUID=5c911086-b42e-4b82-8ae7-98f9a565b1d9 MachineType: Dell Inc. Inspiron 1525 NonfreeKernelModules: wl Package: linux-image-2.6.31-13-generic 2.6.31-13.43 ProcCmdLine: root=UUID=0c1b8172-52a0-4bc5-91f4-98e6569c6ed3 ro splash ProcVersionSignature: Ubuntu 2.6.31-13.43-generic RelatedPackageVersions: linux-firmware 1.21 RfKill: 0: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: yes SourcePackage: linux Tags: kernel-oops Title: BUG: scheduling while atomic: swapper/0/0x1001 Uname: Linux 2.6.31-13-generic i686 WpaSupplicantLog: dmi.bios.date: 10/16/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0D109D dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd10/16/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0D109D:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/448332/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 607617] Re: package bcmwl-kernel-source 5.60.48.36 bdcom-0ubuntu3 failed to install/upgrade: bcmwl kernel module failed to build
** Attachment removed: "F1E0501E6C0A1AAEC9C4F1E0B65DDB32.jpg" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/607617/+attachment/4903807/+files/F1E0501E6C0A1AAEC9C4F1E0B65DDB32.jpg ** Attachment removed: "45DBEF267CE3FB0A84F23E4348AC40A2.jpg" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/607617/+attachment/4905330/+files/45DBEF267CE3FB0A84F23E4348AC40A2.jpg ** Attachment removed: "2CE4BE4B3F86CC18B0D128CFC2C63E1D.jpg" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/607617/+attachment/4905983/+files/2CE4BE4B3F86CC18B0D128CFC2C63E1D.jpg ** Attachment removed: "85A8FCC9239F457FB939CA104B27A21F.jpg" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/607617/+attachment/4887523/+files/85A8FCC9239F457FB939CA104B27A21F.jpg ** Attachment removed: "A78D60C6C8427CD36C0F60D8F7A81AF0.jpg" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/607617/+attachment/4886018/+files/A78D60C6C8427CD36C0F60D8F7A81AF0.jpg ** Attachment removed: "BBDC246D19C63DA7C5580A8F1AFE7BD9.jpg" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/607617/+attachment/4881658/+files/BBDC246D19C63DA7C5580A8F1AFE7BD9.jpg ** Attachment removed: "470585DE194D6FB6A958ED9875601C8D.jpg" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/607617/+attachment/4879722/+files/470585DE194D6FB6A958ED9875601C8D.jpg ** Attachment removed: "8A1B4741D6FB6CB2DE8EC1E0196498D9.jpg" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/607617/+attachment/4876291/+files/8A1B4741D6FB6CB2DE8EC1E0196498D9.jpg ** Attachment removed: "595D6BD8A6F070D990872C0BB0327EB1.jpg" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/607617/+attachment/4876265/+files/595D6BD8A6F070D990872C0BB0327EB1.jpg ** Attachment removed: "772C1B02BBB4C96A8C191CA3669D26D4.jpg" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/607617/+attachment/4876190/+files/772C1B02BBB4C96A8C191CA3669D26D4.jpg ** Attachment removed: "DACC6012AFBAAE0509AFE41F6AB63C73.jpg" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/607617/+attachment/4872082/+files/DACC6012AFBAAE0509AFE41F6AB63C73.jpg ** Attachment removed: "3AE5452A6D54CB9624801F9952714E4D.jpg" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/607617/+attachment/4874798/+files/3AE5452A6D54CB9624801F9952714E4D.jpg ** Attachment removed: "image001.jpg" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/607617/+attachment/4777634/+files/image001.jpg -- 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/607617 Title: package bcmwl-kernel-source 5.60.48.36 bdcom-0ubuntu3 failed to install/upgrade: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Lucid: Won't Fix Status in bcmwl source package in Natty: Fix Released Bug description: My system is a Dell Vostro 1320 on which I installed the Broadcom wireless network driver after I had installed Ubuntu 10.04 LTS. I received this error when I tried to install the "flashplugin-installer" from the Synaptic Package Manager. I also tried to run the Flash Player Install from the Adobe web page and that also failed. I selected the "APT for Ubuntu 9.04+" and then pressed the "Agree and Install Now" button. I expected the Flash player to be installed as a plugin for Firefox but it fails to complete. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: bcmwl-kernel-source 5.60.48.36+bdcom-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-23-generic x86_64 Architecture: amd64 Date: Tue Jul 20 02:15:57 2010 ErrorMessage: bcmwl kernel module failed to build InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) PackageVersion: 5.60.48.36+bdcom-0ubuntu3 SourcePackage: bcmwl Title: package bcmwl-kernel-source 5.60.48.36+bdcom-0ubuntu3 failed to install/upgrade: bcmwl kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/607617/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1684120] Re: Linux version 4.8.0-36-generic (buildd@lgw01-18) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #36~16.04.1-Ubuntu SMP Sun Feb 5 09:39:57 UTC 2017 (U
** Project changed: launchpad => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1684120 Title: Linux version 4.8.0-36-generic (buildd@lgw01-18) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #36~16.04.1-Ubuntu SMP Sun Feb 5 09:39:57 UTC 2017 (Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11) Will intermittent crash when connect to above 2 USB device and reset USB device-Mobile Status in linux package in Ubuntu: New Bug description: Clean installed with Ubuntu 16.04.02 TLS Desktop 64bit We used some desktop computer to test the android mobile phone. Link to PC through USB Type-C and Micro USB. We set an APK file to let mobile auto mount/dismount around 1 time/minutes. Kernel will intermittent crash, Even test from 16.04.01 LTS same as well. Seek your advise if any kernel upgrade or idea can resolve this issue.How to create the trace log for deep analysis if need? I have attach the log file for your reference, Thanks very much!! Kernel info: Apr 17 16:17:00 SH-11F3-A10-0605 kernel: [0.00] Linux version 4.8.0-36-generic (buildd@lgw01-18) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #36~16.04.1-Ubuntu SMP Sun Feb 5 09:39:57 UTC 2017 (Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11) Apr 17 16:17:00 SH-11F3-A10-0605 kernel: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic.efi.signed root=UUID=4e264b55-dafb-4b87-9c25-6902e5f54272 ro quiet splash vt.handoff=7 Log as below: Apr 14 21:15:51 SH-11F3-A10-0401 kernel: [13702.235348] scsi 1506:0:0:0: CD-ROMLinuxFile-CD Gadget 0401 PQ: 0 ANSI: 2 Apr 14 21:15:51 SH-11F3-A10-0401 kernel: [13702.236703] sr 1506:0:0:0: [sr2] scsi-1 drive Apr 14 21:15:51 SH-11F3-A10-0401 kernel: [13702.237193] sr 1506:0:0:0: Attached scsi CD-ROM sr2 Apr 14 21:15:51 SH-11F3-A10-0401 kernel: [13702.237436] sr 1506:0:0:0: Attached scsi generic sg3 type 5 Apr 14 21:15:51 SH-11F3-A10-0401 kernel: [13702.286619] usb 1-3: new high-speed USB device number 120 using xhci_hcd Apr 14 21:15:52 SH-11F3-A10-0401 kernel: [13702.415975] usb 1-3: New USB device found, idVendor=12d1, idProduct=107e Apr 14 21:15:52 SH-11F3-A10-0401 kernel: [13702.415982] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Apr 14 21:15:52 SH-11F3-A10-0401 kernel: [13702.415987] usb 1-3: Product: HUAWEI Apr 14 21:15:52 SH-11F3-A10-0401 kernel: [13702.415990] usb 1-3: Manufacturer: unknown Apr 14 21:15:52 SH-11F3-A10-0401 kernel: [13702.415993] usb 1-3: SerialNumber: K4Q011642205 Apr 14 21:15:52 SH-11F3-A10-0401 kernel: [13702.417894] usb-storage 1-3:1.3: USB Mass Storage device detected Apr 14 21:15:52 SH-11F3-A10-0401 kernel: [13702.418103] scsi host1507: usb-storage 1-3:1.3 Apr 14 21:15:52 SH-11F3-A10-0401 kernel: [13702.838577] usb 1-7: new high-speed USB device number 121 using xhci_hcd Apr 14 21:15:52 SH-11F3-A10-0401 kernel: [13702.967820] usb 1-7: New USB device found, idVendor=12d1, idProduct=107e Apr 14 21:15:52 SH-11F3-A10-0401 kernel: [13702.967829] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Apr 14 21:15:52 SH-11F3-A10-0401 kernel: [13702.967833] usb 1-7: Product: HUAWEI Apr 14 21:15:52 SH-11F3-A10-0401 kernel: [13702.967837] usb 1-7: Manufacturer: unknown Apr 14 21:15:52 SH-11F3-A10-0401 kernel: [13702.967841] usb 1-7: SerialNumber: R3E011611771 Apr 14 21:15:52 SH-11F3-A10-0401 kernel: [13702.969529] usb-storage 1-7:1.3: USB Mass Storage device detected Apr 14 21:15:52 SH-11F3-A10-0401 kernel: [13702.969724] scsi host1508: usb-storage 1-7:1.3 Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.415340] scsi 1507:0:0:0: CD-ROMLinuxFile-CD Gadget 0401 PQ: 0 ANSI: 2 Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.416594] sr 1507:0:0:0: [sr3] scsi-1 drive Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.417121] sr 1507:0:0:0: Attached scsi CD-ROM sr3 Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.417352] sr 1507:0:0:0: Attached scsi generic sg4 type 5 Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.967196] scsi 1508:0:0:0: CD-ROMLinuxFile-CD Gadget 0401 PQ: 0 ANSI: 2 Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.968605] sr 1508:0:0:0: [sr4] scsi-1 drive Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.969154] sr 1508:0:0:0: Attached scsi CD-ROM sr4 Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.969358] sr 1508:0:0:0: Attached scsi generic sg5 type 5 Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13704.120986] usb 1-1: USB disconnect, device number 117
[Kernel-packages] [Bug 1656259] [NEW] Linux ZFS port doesn't respect RLIMIT_FSIZE
Public bug reported: bash -c 'ulimit -f 1024; yes | head -n2097152' >/path/on/filesystem/under/test On ext4, this test case prints something along the lines of: bash: line 1: 11274 Broken pipe yes 11275 File size limit exceeded(core dumped) | head -n2097152 On ZFS, this test case incorrectly exits zero with no output, demonstrating that ZFS does not respect RLIMIT_FSIZE. I asked a friend to run this on Solaris 5.10 and FreeBSD 10.0-CURRENT, and on those systems this test case correctly generates SIGXFSZ; so it seems that this is a bug in the Linux port of ZFS. (This was discovered while tracking down Launchpad test suite failures under LXD on ZFS. Launchpad uses RLIMIT_FSIZE in one place to guard against bugs that cause debdiff to generate arbitrarily large amounts of output and fill the disk.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-57-generic 4.4.0-57.78 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 13 10:01:36 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=139ad421-b014-4c34-ae8c-dd1d15205875 InstallationDate: Installed on 2013-03-01 (1413 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) MachineType: LENOVO 20BXCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic.efi.signed root=UUID=12c52021-a1ab-4984-9dd7-63cf0dcaac16 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-57-generic N/A linux-backports-modules-4.4.0-57-generic N/A linux-firmware1.157.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET49WW (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET49WW(1.14):bd05/21/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: High Assignee: Colin Ian King (colin-king) Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656259 Title: Linux ZFS port doesn't respect RLIMIT_FSIZE Status in linux package in Ubuntu: New Bug description: bash -c 'ulimit -f 1024; yes | head -n2097152' >/path/on/filesystem/under/test On ext4, this test case prints something along the lines of: bash: line 1: 11274 Broken pipe yes 11275 File size limit exceeded(core dumped) | head -n2097152 On ZFS, this test case incorrectly exits zero with no output, demonstrating that ZFS does not respect RLIMIT_FSIZE. I asked a friend to run this on Solaris 5.10 and FreeBSD 10.0-CURRENT, and on those systems this test case correctly generates SIGXFSZ; so it seems that this is a bug in the Linux port of ZFS. (This was discovered while tracking down Launchpad test suite failures under LXD on ZFS. Launchpad uses RLIMIT_FSIZE in one place to guard against bugs that cause debdiff to generate arbitrarily large amounts of output and fill the disk.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-57-generic 4.4.0-57.78 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 13 10:01:36 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=139ad421-b014-4c34-ae8c-dd1d15205875 InstallationDate: Installed on 2013-03-01 (1413 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) MachineType: LENOVO 20BXCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic.efi.signed root=UUID=12c52021-a1ab-4984-9dd7-63cf0dcaac16 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-57-generic N/A linux-backports-modules-4.4.0-57-generic N/A linux-firmware1.157.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET49WW (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 S
[Kernel-packages] [Bug 1655123] Re: Kernel 4.10 stalls on restart
** Project changed: launchpad => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655123 Title: Kernel 4.10 stalls on restart Status in linux package in Ubuntu: Incomplete Status in linux source package in Zesty: Incomplete Bug description: For rc2 and rc3, the machine stalls on first restart only (no tty) and runs OK after (no shutdown problems). Same result when removing the lowest Kernel (all of them). Canonical Kernel permanently stalls on restart but runs OK. Plus, the boot sequence passes by the Grub menu under 4.10.0-0 (not dual-boot, UEFI). Since last night, suspend mode won’t wake-up under rc3 (no tty). Kernel 4.9 stable (.0 and .1) are working properly. 4.10-rc1=Kernel panic. FYI, for a couple of months now, Gnome Software refuses to install custom kernel. 20170107 build. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655123/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1655085] Re: bugs linux 64bits and intel hd graphics card 4600
** Project changed: launchpad => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655085 Title: bugs linux 64bits and intel hd graphics card 4600 Status in linux package in Ubuntu: New Bug description: Hello, I just bought Euler 4785T and a 27" Iiyama ProLite X2783HSU-B1 screen. When trying to install Ubuntu/Xubuntu 16.04 or 16.10 (32 or 64bits) I have some display problems (brightness button is blocked, right-click in Firefox bugs...) Same problem with Linux Mint 17 and 18 (64bits), but so far, it seems to work with Linux Mint XFCE 32 bits. I wrote a post in Ubuntu forum (in French) here : http://forum.ubuntu- fr.org/viewtopic.php?pid=21657030#p21657030. I have been told to report the bug on Launchpad. It may be helpful. Don't hesitate to ask me for details. Best regards. Intel HD Graphics 4600 Intel H87 Intel Core i7 4785T Hardware : SSD 500Go Memory : 16 Go To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655085/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1648524] Re: [AMD]Power-off/reboot stalls = no tty on Kernel 4.9.0.x
** Project changed: launchpad => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1648524 Title: [AMD]Power-off/reboot stalls = no tty on Kernel 4.9.0.x Status in linux package in Ubuntu: Incomplete Bug description: I’m able to build and run custom Kernel if and only if I don’t shutdown or reboot. Otherwise, the process ends in a dead screen CRTL+ALT+xyz has no effect. Works fine up to Kernel 4.8.12. Apport is not showing anything. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648524/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1630906] Re: QML segfault on arm64 due to builder kernel change
The kernel running on the builders is a custom fork at the moment, which isn't a good long-term situation, so please don't mark the kernel task here as 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/1630906 Title: QML segfault on arm64 due to builder kernel change Status in linux package in Ubuntu: Confirmed Status in online-accounts-api package in Ubuntu: New Status in qmenumodel package in Ubuntu: New Status in qtdeclarative-opensource-src package in Ubuntu: New Status in ubuntu-push-qml package in Ubuntu: New Status in unity8 package in Ubuntu: New Status in webbrowser-app package in Ubuntu: New Bug description: Builders were changed from wily to xenial (4.4) kernel for arm64, and likely due to this the following kind of errors started happening: https://launchpadlibrarian.net/288487533/buildlog_ubuntu-yakkety-arm64 .ubuntu-push-qml_0.1+15.10.20150826.1-0ubuntu2_BUILDING.txt.gz They happen when executing QML code. I've ruled out that reverting to previous qtbase and qtdeclarative versions don't affect this, so it's not coming from a Qt change. I've also verified there's no problem eg on our Bq tablet running the same tests on xenial+overlay. There are currently no found changes at least in Qt upstream to backport arm64 related fixes. Cause is unknown. But the same problem is there on vivid, xenial and yakkety builds: https://launchpadlibrarian.net/288516465/buildlog_ubuntu-yakkety-arm64.online-accounts-api_0.1+16.10.20161006.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288515705/buildlog_ubuntu-xenial-arm64.online-accounts-api_0.1+16.04.20161006.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288515510/buildlog_ubuntu-vivid-arm64.online-accounts-api_0.1+15.04.20161006.1-0ubuntu1_BUILDING.txt.gz This means it does not matter if it's Qt 5.4 or 5.6, GCC 4.9, 5 or 6, or glibc 2.21, 2.23 or 2.24. More logs from affected packages: https://launchpadlibrarian.net/288493058/buildlog_ubuntu-yakkety-arm64.qtdeclarative-opensource-src_5.6.1-7ubuntu3~1_BUILDING.txt.gz https://launchpadlibrarian.net/288347391/buildlog_ubuntu-xenial-arm64.webbrowser-app_0.23+16.04.20161005.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288385063/buildlog_ubuntu-vivid-arm64.qmenumodel_0.2.10+15.04.20161005.1-0ubuntu1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630906/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1630549] Re: Traffic Shaping under kernel 4.4
** Project changed: launchpad => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1630549 Title: Traffic Shaping under kernel 4.4 Status in linux package in Ubuntu: Incomplete Bug description: Hi All, I am seeking information whether anyone come across this issue before. Basically traffic shaping stopped working as I started to use kernel 4.4.19 The rules seem to be in place but packets do not get queued at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630549/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1629415] Re: Broken hardware buttons on Dell XPS 12-9Q33
** Project changed: launchpad => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1629415 Title: Broken hardware buttons on Dell XPS 12-9Q33 Status in linux package in Ubuntu: New Bug description: System Ubuntu 16.04 Kernel 4.4.0-36 and newer break the hardware volume control buttons on Dell XPS 12-9Q33. On key press kernel reports: intel-vbtn INT33D6:00: unknown event index 0xc6 intel-vbtn INT33D6:00: unknown event index 0xc7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629415/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1620027] Re: sound doesn't work - ubnt 16.04.1, asus laptop, snd-hda-intel
** Project changed: launchpad => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1620027 Title: sound doesn't work - ubnt 16.04.1, asus laptop, snd-hda-intel Status in linux package in Ubuntu: New Bug description: Hi guys, sound doesn't work on my asus V1J laptop. I tried change /etc/modprobe.d/alsa.conf and set: options snd-hda-intel position_fix=1 model=3stack then i tried: options snd-hda-intel power_save=10 power_save_controller=N position_fix=1 model=3stack as described there (find V1J keyword): https://doc.ubuntu-fr.org/audio_intel_hda after that i tried these models: model=laptop model=laptop-imic model=epad model=auto In year 2007, model=3stack works for me (I was running gentoo). my sound card chipset: AD1986A lspci: 00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 02) I think, that there is problem in acpi, because model 3stack works for me some years before. I tried config grub and boot options: acpi=off -> doesn't help acpi=on -> doesn't help acpi=noirq -> doesn't help In year 2007, there was an article - How to install debian on ASUS V1J: http://sgxris.blogspot.cz/2007/03/install-debian-unstable-on- asus.html There is written, that sound will work, after I will install http://acpi4asus.sourceforge.net/. But these drivers are included in kernel since 2.6.19 - so I does not need compile acpi4asus. But in 2007 it helped for me. user@asus-v1j:~$ aplay -l Seznam PLAYBACK Hardwarových zařízení karta 0: Intel [HDA Intel], zařízení 0: AD1986A Analog [AD1986A Analog] Podzařízení: 1/1 Podzařízení #0: subdevice #0 karta 0: Intel [HDA Intel], zařízení 1: AD1986A Digital [AD1986A Digital] Podzařízení: 1/1 Podzařízení #0: subdevice #0 karta 0: Intel [HDA Intel], zařízení 6: Si3054 Modem [Si3054 Modem] Podzařízení: 1/1 Podzařízení #0: subdevice #0 I have no idea, how to repair my sound in Ubuntu. Do you have any idea? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1620027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1619646] Re: Wi-Fi signal strength very low beside router, gets lower on moving 2-3 metres away from router
** Project changed: launchpad => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1619646 Title: Wi-Fi signal strength very low beside router, gets lower on moving 2-3 metres away from router Status in linux package in Ubuntu: New Bug description: Laptop gets enough Wi-Fi signals beside router but as you move 2-3 metres away from router it barely gets one line strength. And then won't connect due to low strength. Wi-Fi worked fine before the 3-4 kernel updates but after the updates I'm facing this problem. Ubuntu version : 16.10 Present Kernel Verion : Linux roopam 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:01:55 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Wireless Device : 0a:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter What I tried : tried installing alternative wireless driver from sudo add-apt-repository ppa:hanipouspilot/rtlwifi sudo apt-get update sudo apt-get install rtlwifi-new-dkms linux-firmware NO Luck! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1619646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1617686] Re: Kernel 4.4.0-34 caused Redshift/Flux/brightness-controller etc. to stop working
** Project changed: launchpad => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1617686 Title: Kernel 4.4.0-34 caused Redshift/Flux/brightness-controller etc. to stop working Status in linux package in Ubuntu: Incomplete Bug description: As per reported by several users, such as in https://ubuntuforums.org/showthread.php?t=298, apps that control screen gamma, such as Redshift/Flux/brightness-controller, stopped working under the newest kernel 4.4.0-34 in Ubuntu 16.04 LTS, and we're not sure what caused the issue. Those apps are still working well on external monitors. It's just the internal monitor that is not responsive. Any setting just simply has no effect. It seems that all the users are using Skylake-based laptop. In my case, my laptop is on Skylake and GTX980M. Links for the individual apps mentioned above: - Redshift http://jonls.dk/redshift/ - Flux https://justgetflux.com/linux.html - brightness-controller https://apps.ubuntu.com/cat/applications/brightness-controller/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1617686/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1613359] Re: Xrandr gamma and brightness problem on 4.4.0-34 kernel
** Project changed: launchpad => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1613359 Title: Xrandr gamma and brightness problem on 4.4.0-34 kernel Status in linux package in Ubuntu: Incomplete Bug description: Situation Xubuntu 16.04 after the automatic update of the kernel, from 4.4.0-31 to 4.4.0-34. If I give a xrandr command that does not change the resolution or the output monitor, but only the gamma and brightness xrandr --output eDP1 --mode 1368x768 --rate 60 --gamma 1.25: 1.25: 1.25 --brightness 1:25 In eDP1 already 60 hertz and already 1368x768 Nothing is happening. The change in brightness occurs if you change the resolution: xrandr --output eDP1 --mode 1024x768 The screen is considerably brighter. After the command: xrandr --output eDP1 --mode 1024x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Nothing happens, but the change of brightness occurs to the resolution change. for example xrandr --output eDP1 --mode 1360x768 or xrandr --output eDP1 --mode 1360x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Loading the previous kernel 4.4.0-31 the brightness and gamma change immediately. Is my first report, I hope it is clear. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613359/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1531768] Re: [arm64] lockups some time after booting
@dannf, this bug seems to be *worse* in xenial than in wily, so I don't think backporting a change from xenial to wily is going to help matters? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1531768 Title: [arm64] lockups some time after booting Status in Auto Package Testing: Triaged Status in linux package in Ubuntu: Confirmed Bug description: I created an 8 CPU arm64 instance on Canonical's Scalingstack (which I want to use for armhf autopkgtesting in LXD). I started with wily as that has lxd available (it's not yet available in trusty nor the PPA for arm64). However, pretty much any LXD task that I do (I haven't tried much else) on this machine takes unbearably long. A simple "lxc profile set default raw.lxc lxc.seccomp=" or "lxc list" takes several minutes. I see tons of [ 1020.971955] rcu_sched kthread starved for 6000 jiffies! g1095 c1094 f0x0 [ 1121.166926] INFO: task fsnotify_mark:69 blocked for more than 120 seconds. in dmesg (the attached apport info has the complete dmesg). ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-22-generic 4.2.0-22.27 ProcVersionSignature: User Name 4.2.0-22.27-generic 4.2.6 Uname: Linux 4.2.0-22-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 09:18 seq crw-rw 1 root audio 116, 33 Jan 7 09:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.19.1-0ubuntu5 Architecture: arm64 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: CRDA: N/A Date: Thu Jan 7 09:24:01 2016 IwConfig: eth0 no wireless extensions. lono wireless extensions. lxcbr0no wireless extensions. Lspci: 00:00.0 Host bridge [0600]: Red Hat, Inc. Device [1b36:0008] Subsystem: Red Hat, Inc Device [1af4:1100] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic root=LABEL=cloudimg-rootfs earlyprintk RelatedPackageVersions: linux-restricted-modules-4.2.0-22-generic N/A linux-backports-modules-4.2.0-22-generic N/A linux-firmware1.149.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1531768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1531768] Re: [arm64] lockups some time after booting
We're seeing rather similar symptoms on Launchpad builders after upgrading the guests from wily to xenial (console-log not very informative, e.g. https://pastebin.canonical.com/160898/plain/; build output appears hung; I can't tell for sure that it's the same thing, this is just a guess). These are on the same scalingstack hosts as Martin is using, so if anything the surprise is that we weren't seeing it before (we had different problems, mainly occasional hangs on boot). KVM is enabled, host is 4.2 per Junien's comments above, only interesting kernel parameter we're using at present is "compat_uts_machine=armv7l". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1531768 Title: [arm64] lockups some time after booting Status in Auto Package Testing: Triaged Status in linux package in Ubuntu: Confirmed Bug description: I created an 8 CPU arm64 instance on Canonical's Scalingstack (which I want to use for armhf autopkgtesting in LXD). I started with wily as that has lxd available (it's not yet available in trusty nor the PPA for arm64). However, pretty much any LXD task that I do (I haven't tried much else) on this machine takes unbearably long. A simple "lxc profile set default raw.lxc lxc.seccomp=" or "lxc list" takes several minutes. I see tons of [ 1020.971955] rcu_sched kthread starved for 6000 jiffies! g1095 c1094 f0x0 [ 1121.166926] INFO: task fsnotify_mark:69 blocked for more than 120 seconds. in dmesg (the attached apport info has the complete dmesg). ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-22-generic 4.2.0-22.27 ProcVersionSignature: User Name 4.2.0-22.27-generic 4.2.6 Uname: Linux 4.2.0-22-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 09:18 seq crw-rw 1 root audio 116, 33 Jan 7 09:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.19.1-0ubuntu5 Architecture: arm64 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: CRDA: N/A Date: Thu Jan 7 09:24:01 2016 IwConfig: eth0 no wireless extensions. lono wireless extensions. lxcbr0no wireless extensions. Lspci: 00:00.0 Host bridge [0600]: Red Hat, Inc. Device [1b36:0008] Subsystem: Red Hat, Inc Device [1af4:1100] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic root=LABEL=cloudimg-rootfs earlyprintk RelatedPackageVersions: linux-restricted-modules-4.2.0-22-generic N/A linux-backports-modules-4.2.0-22-generic N/A linux-firmware1.149.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1531768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1592122] Re: [16.10 FEAT] Update ipr driver to latest level for POWER
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1592122 Title: [16.10 FEAT] Update ipr driver to latest level for POWER Status in linux package in Ubuntu: New Bug description: Update the ipr device driver with the latest fixes and enhancements to provide continued support of IBM POWER SAS VRAID adapters. This includes performance enhancements to better optimize the driver for SSDs. The target is iprutils version 2.4.12 if it is released in time, otherwise, the target will be 2.4.11. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1592122/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1587078] Re: OOM in guest Ubuntu with inflated balloon
** Project changed: ubuntu-ubuntu-server => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1587078 Title: OOM in guest Ubuntu with inflated balloon Status in linux package in Ubuntu: Incomplete Bug description: There is QEMU/KVM and a Linux OS running inside the guest. Inside the Linux guest a balloon consumes memory in accordance with commands performed on the host side in QEMU. Rapid increases of memory consumption inside the guest may end up with guest OOMs since memory locked by balloon couldn’t be returned to the guest OS/vm in time. The problem is addressed in mainstream Linux with the following patchset: commit 5a10b7dbf904bfe01bb9fcc6298f7df09eed77d5 Author: Raushaniya Maksudova Date: Mon Nov 10 09:36:29 2014 +1030 virtio_balloon: free some memory from balloon on OOM Excessive virtio_balloon inflation can cause invocation of OOM-killer, when Linux is under severe memory pressure. Various mechanisms are responsible for correct virtio_balloon memory management. Nevertheless it is often the case that these control tools does not have enough time to react on fast changing memory load. As a result OS runs out of memory and invokes OOM-killer. The balancing of memory by use of the virtio balloon should not cause the termination of processes while there are pages in the balloon. Now there is no way for virtio balloon driver to free some memory at the last moment before some process will be get killed by OOM-killer. This does not provide a security breach as balloon itself is running inside guest OS and is working in the cooperation with the host. Thus some improvements from guest side should be considered as normal. To solve the problem, introduce a virtio_balloon callback which is expected to be called from the oom notifier call chain in out_of_memory() function. If virtio balloon could release some memory, it will make the system to return and retry the allocation that forced the out of memory killer to run. Allocate virtio feature bit for this: it is not set by default, the the guest will not deflate virtio balloon on OOM without explicit permission from host. Signed-off-by: Raushaniya Maksudova Signed-off-by: Denis V. Lunev Acked-by: Michael S. Tsirkin Signed-off-by: Rusty Russell commit 1fd9c67203af91977bf3b964ff3744cf74fc6f3f Author: Raushaniya Maksudova Date: Mon Nov 10 09:35:29 2014 +1030 virtio_balloon: return the amount of freed memory from leak_balloon() This value would be useful in the next patch to provide the amount of the freed memory for OOM killer. Signed-off-by: Raushaniya Maksudova Signed-off-by: Denis V. Lunev CC: Rusty Russell CC: Michael S. Tsirkin Signed-off-by: Rusty Russell The problem is present in Ubuntu 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1587078/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1568347] Re: nl80211: Could not set interface
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1568347 Title: nl80211: Could not set interface Status in linux package in Ubuntu: New Bug description: On Ubuntu 16.04 beta upgraded from 14.04 I get this error message bombarding syslog and related CPU usage. Obviously the WIFI interface cannot be setup Apr 9 19:18:23 wpa_supplicant[869]: Could not set interface wlxb9127b4c3dbb flags (UP): Cannot assign requested address Apr 9 19:18:23 wpa_supplicant[869]: nl80211: Could not set interface 'wlxb9127b4c3dbb' UP Apr 9 19:18:23 wpa_supplicant[869]: nl80211: deinit ifname=wlxb9127b4c3dbb disabled_11b_rates=0 Apr 9 19:18:23 wpa_supplicant[869]: Could not set interface wlxb9127b4c3dbb flags (UP): Cannot assign requested address Apr 9 19:18:23 wpa_supplicant[869]: WEXT: Could not set interface 'wlxb9127b4c3dbb' UP Apr 9 19:18:23 wpa_supplicant[869]: wlxb9127b4c3dbb: Failed to initialize driver interface lsusb output: Bus 002 Device 003: ID 160a:3184 VIA Technologies, Inc. VIA VNT-6656 [WiFi 802.11b/g USB Dongle] Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 003: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser Bus 004 Device 002: ID 05a4:9881 Ortek Technology, Inc. IR receiver [VRC-1100 Vista MCE Remote Control] Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 003 Device 002: ID 08bb:2704 Texas Instruments Audio Codec Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub lspci output: 00:00.0 Host bridge: NVIDIA Corporation MCP79 Host Bridge (rev b1) 00:00.1 RAM memory: NVIDIA Corporation MCP79 Memory Controller (rev b1) 00:03.0 ISA bridge: NVIDIA Corporation MCP79 LPC Bridge (rev b2) 00:03.1 RAM memory: NVIDIA Corporation MCP79 Memory Controller (rev b1) 00:03.2 SMBus: NVIDIA Corporation MCP79 SMBus (rev b1) 00:03.3 RAM memory: NVIDIA Corporation MCP79 Memory Controller (rev b1) 00:03.4 RAM memory: NVIDIA Corporation MCP79 Memory Controller (rev b1) 00:03.5 Co-processor: NVIDIA Corporation MCP79 Co-processor (rev b1) 00:04.0 USB controller: NVIDIA Corporation MCP79 OHCI USB 1.1 Controller (rev b1) 00:04.1 USB controller: NVIDIA Corporation MCP79 EHCI USB 2.0 Controller (rev b1) 00:06.0 USB controller: NVIDIA Corporation MCP79 OHCI USB 1.1 Controller (rev b1) 00:06.1 USB controller: NVIDIA Corporation MCP79 EHCI USB 2.0 Controller (rev b1) 00:08.0 Audio device: NVIDIA Corporation MCP79 High Definition Audio (rev b1) 00:09.0 PCI bridge: NVIDIA Corporation MCP79 PCI Bridge (rev b1) 00:0a.0 Ethernet controller: NVIDIA Corporation MCP79 Ethernet (rev b1) 00:0b.0 IDE interface: NVIDIA Corporation MCP79 SATA Controller (rev b1) 00:0c.0 PCI bridge: NVIDIA Corporation MCP79 PCI Express Bridge (rev b1) 00:0d.0 PCI bridge: NVIDIA Corporation MCP79 PCI Express Bridge (rev b1) 00:10.0 PCI bridge: NVIDIA Corporation MCP79 PCI Express Bridge (rev b1) 00:16.0 PCI bridge: NVIDIA Corporation MCP79 PCI Express Bridge (rev b1) 04:00.0 VGA compatible controller: NVIDIA Corporation C79 [GeForce 9300 / nForce 730i] (rev b1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1568319] Re: Incoming scp locks up the network
This seems like it must be a kernel bug; at this level scp is just an ordinary userspace program using the network, and shouldn't be *able* to lock it up if the kernel is behaving correctly. ** Package changed: openssh (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1568319 Title: Incoming scp locks up the network Status in linux package in Ubuntu: New Bug description: I am running 16.04 beta 2 on MacBookAir5,2. I tried to copy an El Capitan to it from an El Capitan MacBook Pro and every time I did, the copy would go for ~140M and then lock the network on the Air. I resolved it by restarting the Air's network. This is over WiFi. jeward@ward-MacBookAir:~$ lsb_release -rd Description:Ubuntu Xenial Xerus (development branch) Release:16.04 jeward@ward-MacBookAir:~$ apt-cache policy openssh-server openssh-server: Installed: 1:7.2p2-2 Candidate: 1:7.2p2-2 Version table: *** 1:7.2p2-2 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1272622] Re: bluetooth manager is crashing. I cant browse files from my bluetooth device when its connected via FTp
** Project changed: canonical-identity-provider => bluez (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1272622 Title: bluetooth manager is crashing. I cant browse files from my bluetooth device when its connected via FTp Status in bluez package in Ubuntu: New Bug description: I am using dell inspiron-3521 and i am using ubuntu 12.04. Bluetooth was working without any bugs but today when i tried to access it, it want even turn on. I have download bluetooth manager from ubuntu store. After it i am able to turn on bluetooth. But i cant browse any files from my bluetooth connected mobile. Its hanging and suddenly crashed... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1272622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1317165] Re: Broadcom BCM 94318 MPG 802.11 card not functioning
** Project changed: canonical-identity-provider => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1317165 Title: Broadcom BCM 94318 MPG 802.11 card not functioning Status in linux package in Ubuntu: New Bug description: I can't seem to get the Wireless card in my laptop working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1317165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1520627] Re: New personality for more accurate armv7l emulation on arm64
This is a specific actionable feature request with no relevant log files. ** 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/1520627 Title: New personality for more accurate armv7l emulation on arm64 Status in linux package in Ubuntu: Confirmed Bug description: We're working on bringing up new arm64 builder infrastructure in Launchpad scalingstack to replace the current bare-metal builders, and the current plan is that they should be able to cover armhf as well. Ideally, we would be able to do this using the same guest images: scalingstack builders are reset at the end of the previous build so that latency for new builds is lower when the build farm isn't at 100% use, which means that we don't in general know which architecture a given builder is going to need to build next, so we can get better density out of our hardware by having the same guest images be able to handle more than one architecture. Things mostly work just by chrooting into an armhf chroot under linux32. However, this causes "uname -m" to print "armv8l", while our current value on our armhf builders is "armv7l". I'd initially thought that this would be tolerable, but my understanding from Adam Conrad is that the breakage from poorly-written build scripts that misdetect the architecture as a result is quite widespread. So, we would like to have a personality value available that would cause "uname -m" to print "armv7l". This doesn't look completely trivial, because newuname() basically just has compat and non-compat mode for architectures based on whether the personality is PER_LINUX32 or not, and doesn't currently seem to have extension points beyond that. I'm hoping this is fixable. If not, we need to know with as much lead time as possible so that we can bring up separate armhf guests, since that's going to be a fair amount of work for us to arrange. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520627/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1520627] [NEW] New personality for more accurate armv7l emulation on arm64
Public bug reported: We're working on bringing up new arm64 builder infrastructure in Launchpad scalingstack to replace the current bare-metal builders, and the current plan is that they should be able to cover armhf as well. Ideally, we would be able to do this using the same guest images: scalingstack builders are reset at the end of the previous build so that latency for new builds is lower when the build farm isn't at 100% use, which means that we don't in general know which architecture a given builder is going to need to build next, so we can get better density out of our hardware by having the same guest images be able to handle more than one architecture. Things mostly work just by chrooting into an armhf chroot under linux32. However, this causes "uname -m" to print "armv8l", while our current value on our armhf builders is "armv7l". I'd initially thought that this would be tolerable, but my understanding from Adam Conrad is that the breakage from poorly-written build scripts that misdetect the architecture as a result is quite widespread. So, we would like to have a personality value available that would cause "uname -m" to print "armv7l". This doesn't look completely trivial, because newuname() basically just has compat and non-compat mode for architectures based on whether the personality is PER_LINUX32 or not, and doesn't currently seem to have extension points beyond that. I'm hoping this is fixable. If not, we need to know with as much lead time as possible so that we can bring up separate armhf guests, since that's going to be a fair amount of work for us to arrange. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-stop-nagging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1520627 Title: New personality for more accurate armv7l emulation on arm64 Status in linux package in Ubuntu: New Bug description: We're working on bringing up new arm64 builder infrastructure in Launchpad scalingstack to replace the current bare-metal builders, and the current plan is that they should be able to cover armhf as well. Ideally, we would be able to do this using the same guest images: scalingstack builders are reset at the end of the previous build so that latency for new builds is lower when the build farm isn't at 100% use, which means that we don't in general know which architecture a given builder is going to need to build next, so we can get better density out of our hardware by having the same guest images be able to handle more than one architecture. Things mostly work just by chrooting into an armhf chroot under linux32. However, this causes "uname -m" to print "armv8l", while our current value on our armhf builders is "armv7l". I'd initially thought that this would be tolerable, but my understanding from Adam Conrad is that the breakage from poorly-written build scripts that misdetect the architecture as a result is quite widespread. So, we would like to have a personality value available that would cause "uname -m" to print "armv7l". This doesn't look completely trivial, because newuname() basically just has compat and non-compat mode for architectures based on whether the personality is PER_LINUX32 or not, and doesn't currently seem to have extension points beyond that. I'm hoping this is fixable. If not, we need to know with as much lead time as possible so that we can bring up separate armhf guests, since that's going to be a fair amount of work for us to arrange. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520627/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1508767] Re: IBM POWER8 unhandled signal 11 / SEGV
A full rebuild is in progress at the moment, and nova-compute segfaulted yesterday, so it doesn't look as though disabling KSM was enough. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in apparmor package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-roo
[Kernel-packages] [Bug 1398507] Re: Remove makedumpfile from syncpackage blacklist
Done some time back: revno: 556 committer: Colin Watson branch nick: sync-blacklist timestamp: Tue 2015-01-27 15:48:18 + message: unblacklist makedumpfile; newer version syncable from experimental ... and we got a suitable version in vivid by way of a sync from experimental. ** Changed in: makedumpfile (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1398507 Title: Remove makedumpfile from syncpackage blacklist Status in makedumpfile package in Ubuntu: Fix Released Bug description: Please sync makedumpfile 1.5.7-3 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Merge from Debian unstable. Remaining changes: - kdump-config: load kdump kernel from vmlinux too. This has been merged in debian by Louis Bouchard. Changelog entries since current vivid version 1.5.7-1ubuntu1: makedumpfile (1.5.7-3) unstable; urgency=medium [Mauricio Faria de Oliveira ] * Add possibility to find vmlinux for ppc64el arch Closes: #763688 -- Louis Bouchard Fri, 14 Nov 2014 15:56:15 +0100 makedumpfile (1.5.7-2) unstable; urgency=medium [Lee Schermerhorn] * Add '-F' [flatten] to makedumpefile args for remote kdump vi ssh. Closes: #768317 -- Louis Bouchard Mon, 10 Nov 2014 16:51:04 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1398507/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1504308] Re: wifi light indicator doesn't stop flashing after update kernel linux to 4.1.10
** Project changed: launchpad => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1504308 Title: wifi light indicator doesn't stop flashing after update kernel linux to 4.1.10 Status in linux package in Ubuntu: New Bug description: After updating my kernel to 4.1.10 in ubuntu 14.04.3 LTS, the wifi light do not stop flashing . What is wrong ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1451239] Re: SD Card Reader Problems
** Project changed: launchpad => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1451239 Title: SD Card Reader Problems Status in linux package in Ubuntu: New Bug description: I have three laptop computers with SD Card Reader problems: I installed 64-bit Ubuntu Linux on a Gateway NE56R41u laptop. It recgognizes and mounts the SD Card volume when it installs but will not find or mount it afterward. It recognizes these usb SD Card Readers.: A. SIYOTEAM Model SYM83 - mounts B. Micro S USB 2.0 - mounts C. All-in-One Mini Multi in One Memory Card Reader - mounts D. Internal SD Card Reader - mounts I installed 32-bit Ubuntu Linux on a Dell Latitude D510 laptop A. SIYOTEAM Model SYM83 - mounts B. Micro S USB 2.0 - doesn't mount C. All-in-One Mini Multi in one Memory Card Reader - doesn't mount D. Acer 4-in-1 PCMIA SD Card Reader - doesn't mount I installed 32-bit Linux Lite on a Dell Latitude C600 laptop A. SIYOTEAM Model SYM83 - does not mount B. Micro S USB 2.0 - does not mount C. All-In-One Mini Multi in one Memory Card Reader - mounts Is this related to the Linux Kernel itself? I cannot get drivers to work with these devices. The SIYOTEAM and Micro S readers may be having a problem with the Micro SD card itself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451239/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1436451] Re: can't power off when shutting down
** Project changed: launchpad => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436451 Title: can't power off when shutting down Status in linux package in Ubuntu: New Bug description: We have a dozen of HP laptop here running ubuntu and xubuntu 14.04 and 14.10 and, since few months, all of them can't power off when we try to shutdown them. Indeed, after few seconds of an apparent power off, the laptops restart. Please find attached, the dmesg result of one of them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436451/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1386867] Re: radeon fence failure reduces screen resolution
** Project changed: launchpad => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1386867 Title: radeon fence failure reduces screen resolution Status in “linux” package in Ubuntu: New Bug description: While using Kubuntu 14.10 sometimes the screen blacks out for a few seconds and then comes back to life, but often with highly reduced resolution. The resolution of the screen actually seems to be fine (as evident by taking a screenshot) but things seem to get rendered on a much too small buffer and then streched to fit the screen (terrible upscaling?). Sorry I'm having a hard time explaining it, but see the attached screenshot. This actually happened multiple times. One time it logged me out of KDE, another time KDE stayed active but the resolution was reduced (or whatever this is) Attached is the output of dmesg, the relevant error seems to start here: [12105.193052] radeon :01:00.0: ring 0 stalled for more than 10140msec [12105.193058] radeon :01:00.0: GPU lockup (waiting for 0x000dec08 last fence id 0x000dec03 on ring 0) [12105.674184] radeon :01:00.0: Saved 592 dwords of commands on ring 0. [12105.674320] radeon :01:00.0: GPU softreset: 0x006C To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386867/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1334793] Re: PowerVM: ubuntu-14.04 stuck in ibm, client-architecture-support reboot loop
** Package changed: linux (Ubuntu) => grub2 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1334793 Title: PowerVM: ubuntu-14.04 stuck in ibm,client-architecture-support reboot loop Status in “grub2” package in Ubuntu: Confirmed Bug description: ---Problem Description--- This bug is a follow-up of Bug#110009. The problem here is after successful installation of Ubuntu 14.04, the system fails to boot the OS. When I select installed OS "Ubuntu" from grub menu, it throws below error and falls back to GRUB menu again and again: .. .. OF stdout device is: /vdevice/vty@3000 Preparing to boot Linux version 3.13.0-24-generic (buildd@fisher04) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #46-Ubuntu SMP Thu Apr 10 19:09:21 UTC 2014 (Ubuntu 3.13.0-24.46-generic 3.13.9) Detected machine type: 0101 Max number of cores passed to firmware: 256 (NR_CPUS = 2048) Calling ibm,client-architecture-support... ibm,sp /vdevice/IBM,sp@4000 \ ibm,sp /vdevice/IBM,sp@4000 \ Elapsed time since release of system processors: 10675 mins 3 secs error: no suitable video mode found. Machine Type = IBM,8286-42A Mach serial number: 1069B3T ---Steps to Reproduce--- 1) Try virtual DVD installation 2) Boot the LPAR via cdrom i.e try below commands from openfirmware prompt: 0> devalias cdrom /vdevice/v-scsi@3010/disk@8300 0> boot cdrom 3) proceed with default installation, 100% installation completes. Boot the installed OS from hard disk and you hit this "no suitable video mode found" error and system falls back to GRUB. Install method: virtual DVD Install ISO Information: ubuntu-14.04-server-ppc64el.iso *Additional Instructions for backup: khusr...@in.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. == Comment: #1 - David Heller - 2014-06-11 15:32:48 == This seems to be a pretty common problem, albeit with multiple causes. I see that you already tried some of the workarounds in similar bug here: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/699802 Still, it seems likely this is due to the video mode that grub is attempting to user for the splash screen. Either that, or it's a video driver issue at the grub level. Can you please try the procedure in comment #4 here: http://.ubuntuforums.org/showthread.php?t=1471399 This involves booting to an alternate method, such as a live cd, and operating on the grub config files in the newly installed system. If you are unable to, or have no success with updating the files, it would at least be good to collect the files and attach the information here, before sending this back to launchpad If you are successful in booting to live CD on the same system where the boot fails, it would be good to compare the files from live CD to those in the failing system. Also, do you mind installing with Ubuntu 14.10 alpha images? http://cdimage.ubuntu.com/ubuntu-server/daily/current/utopic-server- ppc64el.iso To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1334793/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1320711] Re: Sync makedumpfile 1.5.6-1 (main) from Debian unstable (main)
This bug was fixed in the package makedumpfile - 1.5.6-1 Sponsored for Artur Rona (ari-tczew) --- makedumpfile (1.5.6-1) unstable; urgency=medium [ Louis Bouchard ] * New upstream version * Add x32 armel armhf and ppa64el to Achitecture to close the delta with Ubuntu -- Louis Bouchard Tue, 29 Apr 2014 16:07:03 +0200 ** Changed in: makedumpfile (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1320711 Title: Sync makedumpfile 1.5.6-1 (main) from Debian unstable (main) Status in “makedumpfile” package in Ubuntu: Fix Released Bug description: Please sync makedumpfile 1.5.6-1 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Merge from Debian unstable (LP: #1277065). Remaining changes: - Build makedumpfile on armel, armhf, ppc64el, and x32. Debian has merged Ubuntu changes. Changelog entries since current utopic version 1.5.5-2ubuntu1: makedumpfile (1.5.6-1) unstable; urgency=medium [ Louis Bouchard ] * New upstream version * Add x32 armel armhf and ppa64el to Achitecture to close the delta with Ubuntu -- Louis Bouchard Tue, 29 Apr 2014 16:07:03 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1320711/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 560155] Re: 04f2:b022 wireless card crash while try to use or test webcam
** No longer affects: null-and-void -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/560155 Title: 04f2:b022 wireless card crash while try to use or test webcam Status in “linux” package in Ubuntu: Incomplete Bug description: Hi First of all sorry for my english... I'm gabriele from italy and i have this problem with *Ubuntu 9.10* and my *laptot O.book 2.1 Belinea*: when i try to use or test webcam with cheese or camorama or emesene, etc (or doing gstreamer-properties)... my internet connection disconnect and crash the wifi card. To restore all wireless' functions i must remove laptop's battery and boot normally . If i don't remove battery first of reboot my laptop the wireless card connect normally with the router but don't have access to internet. If i try to use webcam with *guvcview or doing by terminal "luvcview -f yuv"* it start normally and perfect while internet wireless connection is online and it not crash! I attach a text file with the results of "lsusb,lsmod,lspci" by terminal. Notebook's processor is *AMD TURION 64x2 TL-56*, *ATI radeon x1200 my graphic card, integrated webcam Chicony Gateway USB 2.0 Webcam (100% compatibile with ubuntu), integrated wireless card Ralink Technology, Corp. RT2501USB Wireless Adapter. My OS is UBUNTU 9.10 Kernel 2.6.31-21 in dual boot with Windows 7 *Last, the problem don't disappear if i try in livemode with the bootable cd inserts and it persists also with other Distro like Fedora, OpenSuse, Ubuntu 10.04 beta1, Mandriva...ONLY WITH gOS i don't have any problem between webcam and wireless card... Thanx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/560155/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1315619] Re: Job with 4 threads not assigned 4 distinct cores
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1315619 Title: Job with 4 threads not assigned 4 distinct cores Status in “linux” package in Ubuntu: New Bug description: On 12.04, I have reliably found that a job which starts 4 long-running threads on an otherwise-idle machine (there are some other threads which have been running for some time, but they have been kill -STOPped) gets the threads allocated to 4 distinct cores on my Haswell. On 14.04, I found that the threads were allocated to cores 0, 1, 5, 6 - that is, two were running on the two hyper-threads 1 and 5 of the same core, and performance was 30% less than expected. I can get around this with explicit taskset commands, but for my use case it's a serious regression from 12.04. I am not willing to disable hyperthreading, because it gives a large performance boost on other things I do on the same machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1315619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1303819] Update Released
The verification of the Stable Release Update for bluez has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1303819 Title: Bluetooth menu's content disappeared after resume. Status in “bluez” package in Ubuntu: Fix Released Status in “bluez” source package in Precise: Fix Released Status in “bluez” source package in Trusty: Fix Released Bug description: [Impact] * It is very annoying to see Bluetooth menu's content disappeared after suspending and resuming when playing music through Bluetooth audio output. * The better user experience is still seeing Bluetooth menu's content. [Test Case] * Pairing Bluetooth audio device. * Playing music through Bluetooth audio output. * Suspending the system. * Resuming the system. [Regression Potential] * No obvious regression exists. [Other Info] * The patch is to reset default_adapter_id's value to -1, then it can send the signal 'DefaultAdapterChanged' next time when new default adapter is set. * Reproducing Steps 1. Playing music through Bluetooth audio ouput. 2. Suspending the system. 3. Resuming the system. 4. Check Bluethooth menu's content * Expected Result The Bluetooth menu's content is not affected. * Actual Result The Bluetooth menu's content disappeared. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: bluez 4.98-2ubuntu7.1 ProcVersionSignature: Ubuntu 3.5.0-48.72~precise1-generic 3.5.7.31 Uname: Linux 3.5.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Mon Apr 7 19:08:01 2014 InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Latitude E6230 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-48-generic root=UUID=8da8a808-6d55-4e04-a813-3f1217ab4f35 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 098M9Y dmi.board.vendor: Dell Inc. dmi.board.version: X03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd09/19/2012:svnDellInc.:pnLatitudeE6230:pvr01:rvnDellInc.:rn098M9Y:rvrX03:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6230 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 74:DE:2B:D4:BB:8E ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:6082 acl:32 sco:0 events:625 errors:0 TX bytes:949448 acl:1140 sco:0 commands:45 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1303819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1307105] Re: Kernel install fails due PAE checks
Just put the forcepae option after the "--" entry on the installer command line and it will be copied to the target system. The "--" entry defines the boundary between options which are specific to the installer and ones that are copied to the target system. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1307105 Title: Kernel install fails due PAE checks Status in “linux” package in Ubuntu: Triaged Bug description: [TRIAGE NOTE] When a user boots Ubuntu Live/Install media with 'forcepae' option, the option should automatically be added to /etc/default/grub, or kernel upgrades will refuse to install when they do not see pae capability in cpuinfo. [ORIGINAL REPORT] On Thinkpad T42 with Pentium M processor linux image upgrade fails with message "This kernel does not support a non-PAE CPU.". System was installed from ubuntu-14.04-beta2-desktop-i386.iso with "forcepae" kernel option. After install, system works, but cannot be upgraded to laters kernel. root@t42:/boot# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these. The following packages have unmet dependencies: linux-image-extra-3.13.0-24-generic : Depends: linux-image-3.13.0-24-generic but it is not installed linux-image-generic : Depends: linux-image-3.13.0-24-generic but it is not installed E: Unmet dependencies. Try using -f. root@t42:/boot# apt-get install -f Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following extra packages will be installed: linux-image-3.13.0-24-generic Suggested packages: fdutils linux-doc-3.13.0 linux-source-3.13.0 linux-tools The following NEW packages will be installed: linux-image-3.13.0-24-generic 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 3 not fully installed or removed. Need to get 0 B/14.6 MB of archives. After this operation, 32.3 MB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 196089 files and directories currently installed.) Preparing to unpack .../linux-image-3.13.0-24-generic_3.13.0-24.46_i386.deb ... This kernel does not support a non-PAE CPU. dpkg: error processing archive /var/cache/apt/archives/linux-image-3.13.0-24-generic_3.13.0-24.46_i386.deb (--unpack): subprocess new pre-installation script returned error exit status 1 Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.13.0-24-generic /boot/vmlinuz-3.13.0-24-generic run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.13.0-24-generic /boot/vmlinuz-3.13.0-24-generic Errors were encountered while processing: /var/cache/apt/archives/linux-image-3.13.0-24-generic_3.13.0-24.46_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1307105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1270930] Re: Nouveau driver crashes in trusty-desktop-i386.iso Jan 15
** Package changed: ubiquity (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1270930 Title: Nouveau driver crashes in trusty-desktop-i386.iso Jan 15 Status in “linux” package in Ubuntu: New Bug description: I tried to install Ubuntu 14.04 from trusty-desktop-i386.iso Jan 15 into old PC. Installer crashed after laguage selection. Nouveau driver seems to cause it. GeForce 6200. I took pictures. Sorry about bad quality. If usefull I can repeat test. I took pictures from display: http://jkn.iki.fi/bug2/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1295112] Re: Unable to install 64-bit kernel on 64-bit-capable system installed with 32-bit userland+kernel
This is an important part of being able to transition people in-place to amd64, so I'd like to see this fixed in trusty if possible. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1295112 Title: Unable to install 64-bit kernel on 64-bit-capable system installed with 32-bit userland+kernel Status in “linux” package in Ubuntu: New Bug description: $ arch i686 $ dpkg -l linux-generic Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---== ii linux-generic 3.13.0.18.22 i386 Complete Generic Linux kernel and headers $ sudo dpkg --add-architecture amd64 $ sudo apt-get update $ sudo apt-get install linux-generic:amd64 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. linux-generic:amd64 : Depends: linux-headers-generic:amd64 (= 3.13.0.18.22) but it is not going to be installed E: Unable to correct problems, you have held broken packages. $ sudo apt-get install linux-generic:amd64 linux-headers-generic:amd64 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. linux-headers-generic:amd64 : Depends: linux-headers-3.13.0-18-generic:amd64 but it is not going to be installed E: Unable to correct problems, you have held broken packages. $ sudo apt-get install linux-generic:amd64 linux-headers-generic:amd64 linux-headers-3.13.0-18-generic:amd64 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. linux-headers-3.13.0-18-generic:amd64 : Depends: linux-headers-3.13.0-18:amd64 but it is not installable E: Unable to correct problems, you have held broken packages. $ sudo apt-get install linux-generic:amd64 linux-headers-generic:amd64 linux-headers-3.13.0-18-generic:amd64 linux-headers-3.13.0-18:amd64 Reading package lists... Done Building dependency tree Reading state information... Done Package linux-headers-3.13.0-18:amd64 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'linux-headers-3.13.0-18:amd64' has no installation candidate $ cjwatson identified the issue: 12:52:11 the bug is that linux-headers-3.13.0-18 isn't Multi-Arch: foreign fwiw ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-18-generic 3.13.0-18.38 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3834 F pulseaudio /dev/snd/controlC0: james 3834 F pulseaudio /dev/snd/pcmC0D0p: james 3834 F...m pulseaudio CurrentDesktop: Unity Date: Thu Mar 20 12:52:29 2014 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (1246 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash intel_pstate=enable RelatedPackageVersions: linux-restricted-modules-3.13.0-18-ge
[Kernel-packages] [Bug 1265550] Re: linux-firmware: iwlwifi: add firmware for 7260 / 3160 devices
** Tags added: verification-done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1265550 Title: linux-firmware: iwlwifi: add firmware for 7260 / 3160 devices Status in “linux-firmware” package in Ubuntu: Fix Released Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-firmware” source package in Precise: Fix Committed Status in “linux-lts-saucy” source package in Precise: In Progress Status in “linux-firmware” source package in Trusty: Fix Released Status in “linux-lts-saucy” source package in Trusty: Invalid Bug description: iwlwifi: add firmware for 7260 / 3160 devices Support for linux v3.10+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1265550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
