[Kernel-packages] [Bug 1774964] Comment bridged from LTC Bugzilla
--- Comment From pavsu...@in.ibm.com 2018-06-05 01:26 EDT--- I have downloaded the test kernel from the link and installed the same. root@ltc-wspoon8:~# dpkg -i linux-modules-4.15.0-22-generic_4.15.0-22.25~lp1774964_ppc64el.deb Selecting previously unselected package linux-modules-4.15.0-22-generic. (Reading database ... 74250 files and directories currently installed.) Preparing to unpack linux-modules-4.15.0-22-generic_4.15.0-22.25~lp1774964_ppc64el.deb ... Unpacking linux-modules-4.15.0-22-generic (4.15.0-22.25~lp1774964) ... Setting up linux-modules-4.15.0-22-generic (4.15.0-22.25~lp1774964) ... root@ltc-wspoon8:~# dpkg -i linux-image-unsigned-4.15.0-22-generic_4.15.0-22.25~lp1774964_ppc64el.deb Selecting previously unselected package linux-image-unsigned-4.15.0-22-generic. (Reading database ... 80003 files and directories currently installed.) Preparing to unpack linux-image-unsigned-4.15.0-22-generic_4.15.0-22.25~lp1774964_ppc64el.deb ... Unpacking linux-image-unsigned-4.15.0-22-generic (4.15.0-22.25~lp1774964) ... Setting up linux-image-unsigned-4.15.0-22-generic (4.15.0-22.25~lp1774964) ... I: /boot/vmlinux is now a symlink to vmlinux-4.15.0-22-generic I: /boot/initrd.img is now a symlink to initrd.img-4.15.0-22-generic Processing triggers for linux-image-unsigned-4.15.0-22-generic (4.15.0-22.25~lp1774964) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast /etc/kernel/postinst.d/kdump-tools: kdump-tools: Generating /var/lib/kdump/initrd.img-4.15.0-22-generic W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast /etc/kernel/postinst.d/zz-update-grub: Generating grub configuration file ... Found linux image: /boot/vmlinux-4.15.0-22-generic Found initrd image: /boot/initrd.img-4.15.0-22-generic Found linux image: /boot/vmlinux-4.15.0-20-generic Found initrd image: /boot/initrd.img-4.15.0-20-generic done root@ltc-wspoon8:~# dpkg -i linux-modules-extra-4.15.0-22-generic_4.15.0-22.25~lp1774964_ppc64el.deb (Reading database ... 80006 files and directories currently installed.) Preparing to unpack linux-modules-extra-4.15.0-22-generic_4.15.0-22.25~lp1774964_ppc64el.deb ... Unpacking linux-modules-extra-4.15.0-22-generic (4.15.0-22.25~lp1774964) over (4.15.0-22.25~lp1774964) ... Setting up linux-modules-extra-4.15.0-22-generic (4.15.0-22.25~lp1774964) ... Processing triggers for linux-image-unsigned-4.15.0-22-generic (4.15.0-22.25~lp1774964) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast /etc/kernel/postinst.d/kdump-tools: kdump-tools: Generating /var/lib/kdump/initrd.img-4.15.0-22-generic W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast /etc/kernel/postinst.d/zz-update-grub: Generating grub configuration file ... Found linux image: /boot/vmlinux-4.15.0-22-generic Found initrd image: /boot/initrd.img-4.15.0-22-generic Found linux image: /boot/vmlinux-4.15.0-20-generic Found initrd image: /boot/initrd.img-4.15.0-20-generic done Then again triggered the test scenario and verified the bug with the test kernel. root@ltc-wspoon8:~# uname -a Linux ltc-wspoon8 4.15.0-22-generic #25~lp1774964 SMP Mon Jun 4 19:51:41 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@ltc-wspoon8:~# ./statedisable.sh ./statedisable.sh: line 8: /sys/devices/system/cpu/cpu*/cpuidle/state5/disable: No such file or directory ./statedisable.sh: line 9: /sys/devices/system/cpu/cpu*/cpuidle/state6/disable: No such file or directory ./statedisable.sh: line 10: /sys/devices/system/cpu/cpu*/cpuidle/state7/disable: No such file or directory ./statedisable.sh: line 11: /sys/devices/system/cpu/cpu*/cpuidle/state8/disable: No such file or directory root@ltc-wspoon8:~# ./run_workload.sh root@ltc-wspoon8:~# ./scom_addr_p9.sh 0x1001080c 7 EQ[ 1]: 0x1101080c EX[ 3]: 0x11010c0c C[ 7]: 0x3701080c root@ltc-wspoon8:~# ./skiboot/external/xscom-utils/getscom -c 0x8 0x11010c0c root@ltc-wspoon8:~# ./skiboot/external/xscom-utils/putscom -c 0x8 0x11010c0c 0c00 0c00 In the SOL console we see the following Machine Check Interrupt messages as expected. Ubuntu 18.04 LTS ltc-wspoon8 hvc0 ltc-wspoon8 login: [ 265.635189] Disabling lock debugging due to kernel taint [ 265.635194] Severe Machine check interrupt [Not recovered] [ 265.63[ 395.356139869,0] OPAL: Reboot requested due to Platform error. [ 395.357920113,3] OPAL: Reboot requested due to Platform error.[ 395.361558129,5] Software initiated checkstop disabled. [ 395.362802920,5] OPAL: Reboot request... 5205] NIP [c0ac4da8]: menu_select+0x98/0x600 [ 265.635206] Initiator: CPU [ 265.635208] Error type: UE [Load/Store] [ 265.635211] opal: Hardware platform error: Unrecoverable Machine Check exception [
[Kernel-packages] [Bug 1774569] Re: gsmartcontrol, hdparm, and ZFS all refuse to talk to an apparently working Seagate Backup+ Hub drive after upgrade to 18.04
I pulled the hdparm binary from Artful, and it can't spin down the drive with -y either. -- 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/1774569 Title: gsmartcontrol, hdparm, and ZFS all refuse to talk to an apparently working Seagate Backup+ Hub drive after upgrade to 18.04 Status in gsmartcontrol package in Ubuntu: New Status in hdparm package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Bug description: I recently upgraded from 17.10 to 18.04. After the upgrade, I noticed that my Seagate Backup+ Hub external drive was displaying a series of puzzling symptoms: 1. gsmartcontrol can't get SMART data from the drive. I am pretty sure it used to report SMART data? Here's a log of it not working: [hz] Warning: exit: Command line did not parse. [app] execute_smartctl(): Smartctl binary did not execute cleanly. [app] StorageDevice::execute_device_smartctl(): Smartctl binary did not execute cleanly. [app] SmartctlParser::parse_section_info_property(): Unknown property "Physical block size" [app] SmartctlParser::parse_section_info_property(): Unknown property "Logical Unit id" [app] SmartctlParser::parse_section_info_property(): Unknown property "Temperature Warning" [app] SmartctlParser::parse_section_data(): Unknown Data subsection encountered. [hz] Warning: exit: Some SMART command to the disk failed, or there was a checksum error in a SMART data structure [app] SmartctlParser::parse_section_info_property(): Unknown property "Physical block size" [app] SmartctlParser::parse_section_info_property(): Unknown property "Logical Unit id" [app] SmartctlParser::parse_section_info_property(): Unknown property "Temperature Warning" [app] SmartctlParser::parse_section_data(): Unknown Data subsection encountered. 2. hdparm used to be able to spin down the drive. I had it configured to spin it down after a few minutes of inactivity, in the hdparm config file. Now that no longer happens, and hdparm can't seem to talk to the drive meaningfully at all: [anovak@octagon ~]$ sudo hdparm -I /dev/sdb /dev/sdb: SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 00 00 00 00 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ATA device, with non-removable media Standards: Likely used: 1 Configuration: Logical max current cylinders 0 0 heads 0 0 sectors/track 0 0 -- Logical/Physical Sector size: 512 bytes device size with M = 1024*1024: 0 MBytes device size with M = 1000*1000: 0 MBytes cache/buffer size = unknown Capabilities: IORDY not likely Cannot perform double-word IO R/W multiple sector transfer: not supported DMA: not supported PIO: pio0 [anovak@octagon ~]$ sudo hdparm -y /dev/sdb /dev/sdb: issuing standby command SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 00 00 00 00 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 I think this may be related to https://askubuntu.com/questions/1037997 /upgraded-to-18-04-usb-harddrive-doesn-t-idle-anymore which is someone else having the same problem. 3. The ZFS tools think the drive is hosed: [anovak@octagon ~]$ sudo zpool status hub pool: hub state: UNAVAIL status: One or more devices could not be used because the label is missing or invalid. There are insufficient replicas for the pool to continue functioning. action: Destroy and re-create the pool from a backup source. see: http://zfsonlinux.org/msg/ZFS-8000-5E scan: none requested config: NAME STATE READ WRITE CKSUM hubUNAVAIL 0 0 0 insufficient replicas ata-ST6000DM003-2CY186_ZF200PC8 UNAVAIL 0 0 0 This may be related to the drive having adopted a new /dev/disk/by-id name during the upgrade? I think it was "ata- ST6000DM003-2CY186_ZF200PC8" when I added it to my zpool by its symlink under /dev/disks/by-id, but now it is "usb- Seagate_Backup+_Hub_BK_NA8TQC87-0:0": [anovak@octagon ~]$ ls -lah /dev/disk/by-id/usb-Seagate_Backup+_Hub_BK_NA8TQC87-0\:0 lrwxrwxrwx 1 root root 9 May 31 20:52 /dev/disk/by-id/usb-Seagate_Backup+_Hub_BK_NA8TQC87-0:0 -> ../../sdb This *shouldn't* cause trouble; you should be able to export the zpool and re-import it under the new name. But zpool import shows nothing to import: [anovak@octagon ~]$ sudo zpool import no pools available to import And I also can't export or even destroy the busted zpool, because zpool doesn't think it exists for exporting or destroying purposes: [anovak@octagon ~]$ sudo zpool export
[Kernel-packages] [Bug 1772930] Re: linux-azure: 4.15.0-1013.13 -proposed tracker
4.15.0-1013.13 - azure Regression test CMPL, RTB. Issue to note in x86_64 (azure): ebizzy - failed on Standard_A0, passed on the rest libhugetlbfs - Unable to build libghugetlbfs test on 4.15 Bionic (bug 1765279) monotonic_time - tsc failed on some instances, clock failed on Standard_E4s_v3, Standard_E64-16s(bug 1774959), passed on the rest ubuntu_kvm_smoke_test - Unable to boot Xenial cloud image on Bionic ARM64 ThunderX / Azure (bug 1765668) ubuntu_kvm_unit_tests - test skipped due to no KVM support, vmx_control will crash E4 nodes (bug 1747892) ubuntu_ltp - test disabled on azure ubuntu_lttng_smoke_test - failed on Basic_A1, Standard_A0 (bug 1765035) and B1s, passed on the rest ubuntu_lxc - lxc-tests package is not available in Bionic (bug 1758255) ubuntu_qrt_apparmor - failed with setup task, but the test itself has passed ubuntu_stress_smoke_test - sysfs caused kernel oopsed on some instances (bug 1757057), DCCP retesting on Standard_DS4_V2 ubuntu_unionmount_overlayfs_suite - File unexpectedly on union layer (bug 1751243) ubuntu_zfs_smoke_test - RETESTING ubuntu_zram_smoke_test - zram module missing (bug 1762756) Skipped / blacklisted: * ubuntu_quota_smoke_test * ubuntu_ramfs_stress * ubuntu_seccomp * ubuntu_vfat_stress ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1772930 Title: linux-azure: 4.15.0-1013.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772927 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774569] Re: gsmartcontrol, hdparm, and ZFS all refuse to talk to an apparently working Seagate Backup+ Hub drive after upgrade to 18.04
Even after rebooting with the drive for the zpool physically removed from the system, I still had a zpool I couldn't destroy, export, or otherwise remove from the listing. Using "sudo zpool status -Pv" I worked out that my ZFS was actually expecting to find the data on partition 1 of the drive: errors: No known data errors pool: hub state: UNAVAIL status: One or more devices could not be used because the label is missing or invalid. There are insufficient replicas for the pool to continue functioning. action: Destroy and re-create the pool from a backup source. see: http://zfsonlinux.org/msg/ZFS-8000-5E scan: none requested config: NAME STATE READ WRITE CKSUM hub UNAVAIL 0 0 0 insufficient replicas /dev/disk/by-id/ata-ST6000DM003-2CY186_ZF200PC8-part1 UNAVAIL 0 0 0 I'd previously tried symlinking the old device name to the new one, but I was inspired to try it with just the partition: [anovak@octagon ~]$ cd /dev/disk/by-id/ [anovak@octagon by-id]$ sudo ln -s 'usb-Seagate_Backup+_Hub_BK_NA8TQC87-0:0-part1' ata-ST6000DM003-2CY186_ZF200PC8-part1 When I did that, the pool immediately came back online, and I was able to export it to make it go away. Then I managed to import it under a more stable name with "sudo zpool import -a -d /dev/disk/by-partuuid/". I still can't see the drive data in gsmartcontrol, and I still can't spin it down, but at least I can now use it. -- 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/1774569 Title: gsmartcontrol, hdparm, and ZFS all refuse to talk to an apparently working Seagate Backup+ Hub drive after upgrade to 18.04 Status in gsmartcontrol package in Ubuntu: New Status in hdparm package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Bug description: I recently upgraded from 17.10 to 18.04. After the upgrade, I noticed that my Seagate Backup+ Hub external drive was displaying a series of puzzling symptoms: 1. gsmartcontrol can't get SMART data from the drive. I am pretty sure it used to report SMART data? Here's a log of it not working: [hz] Warning: exit: Command line did not parse. [app] execute_smartctl(): Smartctl binary did not execute cleanly. [app] StorageDevice::execute_device_smartctl(): Smartctl binary did not execute cleanly. [app] SmartctlParser::parse_section_info_property(): Unknown property "Physical block size" [app] SmartctlParser::parse_section_info_property(): Unknown property "Logical Unit id" [app] SmartctlParser::parse_section_info_property(): Unknown property "Temperature Warning" [app] SmartctlParser::parse_section_data(): Unknown Data subsection encountered. [hz] Warning: exit: Some SMART command to the disk failed, or there was a checksum error in a SMART data structure [app] SmartctlParser::parse_section_info_property(): Unknown property "Physical block size" [app] SmartctlParser::parse_section_info_property(): Unknown property "Logical Unit id" [app] SmartctlParser::parse_section_info_property(): Unknown property "Temperature Warning" [app] SmartctlParser::parse_section_data(): Unknown Data subsection encountered. 2. hdparm used to be able to spin down the drive. I had it configured to spin it down after a few minutes of inactivity, in the hdparm config file. Now that no longer happens, and hdparm can't seem to talk to the drive meaningfully at all: [anovak@octagon ~]$ sudo hdparm -I /dev/sdb /dev/sdb: SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 00 00 00 00 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ATA device, with non-removable media Standards: Likely used: 1 Configuration: Logical max current cylinders 0 0 heads 0 0 sectors/track 0 0 -- Logical/Physical Sector size: 512 bytes device size with M = 1024*1024: 0 MBytes device size with M = 1000*1000: 0 MBytes cache/buffer size = unknown Capabilities: IORDY not likely Cannot perform double-word IO R/W multiple sector transfer: not supported DMA: not supported PIO: pio0 [anovak@octagon ~]$ sudo hdparm -y /dev/sdb /dev/sdb: issuing standby command SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 00 00 00 00 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 I think this may be related to https://askubuntu.com/questions/1037997 /upgraded-to-18-04-usb-harddrive-doesn-t-idle-anymore which is someone else having the same problem. 3. The ZFS tools think the drive is hosed: [anovak@octagon
[Kernel-packages] [Bug 1381968] Re: Fstrim destroys data on loopback device
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1381968
Title:
Fstrim destroys data on loopback device
Status in linux package in Ubuntu:
Expired
Bug description:
I've upgraded Ubuntu Server 12.04 LTS to 14.04 LTS.
The setup contains a loopback device (/dev/loop3) mounted into a
software raid 1 (/dev/md2).
After the weekly cronjob (/etc/cron.weekly/fstrim) ran, I've
discovered that it wiped all data on the loopback device from the
raid.
fstrim-all skips check because the loopback device is part of device mapper
raid.
if [ "${REALDEV#/dev/dm-}" != "$REALDEV" ]; then
echo "device $DEV is on devmapper, skipping TRIM feature check"
Issue can be reproduced on raid setup and plain loopback mount setup!
Here is step-by-step how to reproduce the issue:
1.) create sparse image file
dd of=/sparse-file bs=1k seek=1024000
2.) losetup loopback device
losetup /dev/loop3 /sparse-file
3.) create raid1
mdadm --create /dev/md2 --auto md --level=1 --raid-devices=1 /dev/loop3
4.) create fs
mkfs.ext4 /dev/md2
4.1.) check sparse-file size
ls -lash /sparse-file
5.) mount and copy data
mount /dev/md2 /mnt
copy some random files on /mnt
5.1.) check sparse-file size again
ls -lash /sparse-file -> size indicates it contains the copied data
6.) destroy loopback via fstrim
fstrim -v /mnt
7.) data is wiped
umount /mnt
ls -lash /sparse-file -> size indicates that all data is wiped out!
fsck -v -f /dev/md2 -> will report infinite errors on filesystem
I could not find any similiar bugreport.
Best Regards
Daniel
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381968/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1618464] Re: Ubuntu 16.04 wireless networking does not allow WD MyCloud access
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1618464 Title: Ubuntu 16.04 wireless networking does not allow WD MyCloud access Status in linux package in Ubuntu: Expired Bug description: Fresh install of Ubuntu 16.04 64-bit with all updates applied. Hardware: Acer Aspire One 722 with 8ig of RAM and 500Gig SSD. Dual core AMD C60 not that it matters. Wireless: Boot, open Files from task bar, click network, I can see WDMYCLOUD. Click it, enter connection user/password and many seconds later the "opening" dialog pops up. Eventually, many minutes later, error dialog pops up saying unable to connect. Wired: Boot, open Files from task bar, click network, I can see WDMYCLOUD. Click it, enter connection user/password and 1-2 seconds later "opening" dialog pops up. Another second or two and I see the contents of the drive. Only change is from wireless to wired. Using same router. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1618464/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774865] Re: 4.15.0-22 won't boot on Dell XPS 15 9570
Can you try kernel parameter "acpi_osi=Linux-Dell-Video" for that? That's a workaround that in ACPI uses old _DSM for Linux. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774865 Title: 4.15.0-22 won't boot on Dell XPS 15 9570 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: 4.15.0-22 fails on boot on a Dell XPS 9570 with "not all CPUs entered broadcast exception handler". 4.15.0-20 works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774865/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770108] Re: No wifi in 4.13.0-41-generic
Please attach the output of $ dpkg -l | grep linux | grep extra -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770108 Title: No wifi in 4.13.0-41-generic Status in linux package in Ubuntu: Confirmed Bug description: Wifi adapter not showing since upgrading to 4.13.0-41-generic, still works fine if i roll back to 4.13.0-39-generic. Ubuntu 16.04 adapter details *-network description: Wireless interface product: RTL8192CE PCIe Wireless Network Adapter vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:01:00.0 logical name: wlp1s0 version: 01 serial: width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774865] Re: 4.15.0-22 won't boot on Dell XPS 15 9570
Thanks! Leaving some notes in case someone else runs into this and finds this page. I was having some problems with bumblebee (installation would hang, then the whole system would freeze when trying to reboot), and I think that broke something. I assumed it was the kernel because it was the first time booting that version and it seemed like a very serious error that happened very early in the boot process. I reinstalled (this was Linux Mint 19 beta) and stayed away from bumblebee and I had no problems (the kernel works fine). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774865 Title: 4.15.0-22 won't boot on Dell XPS 15 9570 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: 4.15.0-22 fails on boot on a Dell XPS 9570 with "not all CPUs entered broadcast exception handler". 4.15.0-20 works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774865/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773643] Re: [Clevo W253EUQ] Turn on bluetooth with Fn+F12 not working
So it's a regression between 12.04 (Linux v3.2) and 14.04 (Linux v3.13). Can you find the first -rc Linux kernel between 3.2 and 3.13 that causes the regression in [1]? [1] http://kernel.ubuntu.com/~kernel-ppa/mainline/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773643 Title: [Clevo W253EUQ] Turn on bluetooth with Fn+F12 not working Status in linux package in Ubuntu: Incomplete Bug description: Hello, Since long time my [Clevo W253EUQ] Turn on bluetooth with Fn+F12 not working For more information see this link bellow https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322068 Could you help me to fix this bug ? Best regards Battant ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 27 13:21:46 2018 InstallationDate: Installed on 2018-04-29 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mparchet 1714 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-29 (28 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=9d6286f1-598b-46c8-a491-3e29fc732cb9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W240EU/W250EUQ/W270EUQ dmi.board.vendor: CLEVO CO. dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd11/11/2013:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W240EU/W250EUQ/W270EUQ dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO CO. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mparchet 1714 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-29 (28 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=9d6286f1-598b-46c8-a491-3e29fc732cb9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W240EU/W250EUQ/W270EUQ dmi.board.vendor: CLEVO CO. dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd11/11/2013:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W240EU/W250EUQ/W270EUQ dmi.product.version: Not
[Kernel-packages] [Bug 1774865] Re: 4.15.0-22 won't boot on Dell XPS 15 9570
Try kernel parameter "nouveau.modeset=0". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774865 Title: 4.15.0-22 won't boot on Dell XPS 15 9570 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: 4.15.0-22 fails on boot on a Dell XPS 9570 with "not all CPUs entered broadcast exception handler". 4.15.0-20 works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774865/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770840] Re: My Inspiron-1420 shuts down when waking from Suspended Mode.
** Changed in: linux (Ubuntu) Status: Confirmed => 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/1770840 Title: My Inspiron-1420 shuts down when waking from Suspended Mode. Status in linux package in Ubuntu: Fix Released Bug description: Hello, I installed Ubuntu Budgie - amd64 on my Inspiron 1420. When I close the lid the Notebook (apparently) goes into suspend mode. Instead of starting-up upon opening the lid, the notebook shuts down. I couldn't find the settings for the lid in the settings menu. I can think of two possible reasons (not necessarily true): 1) My HDD is password protected. When I open my notebook it asks for HD password and then takes to the boot menu. 2) I have two operating systems (Dual Boot) installed on my Notebook: Windows 10 developer edition and Ubuntu Budgie. Please look into this. Thanks, Sakib. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sat May 12 18:34:57 2018 InstallationDate: Installed on 2018-05-10 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: s 1410 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-15 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 1420 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=f689a411-dda2-49d1-a590-1cdb86b27530 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/11/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0KN548 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd07/11/2008:svnDellInc.:pnInspiron1420:pvr:rvnDellInc.:rn0KN548:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1420 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770840/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1708043] Re: Lenovo X1 Carbon Gen5 fails to resume
I'm on the X1 Carbon 6th gen config Peter Bittner describes. I'm seeing the same behavior. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1708043 Title: Lenovo X1 Carbon Gen5 fails to resume Status in linux package in Ubuntu: Fix Committed Bug description: Last week it worked fine, this week however if I open the lid for it to resume the power light flashes for a bit, then comes on solid, the but screen stays blank and the machine is unresponsive. I have to power it off / on again in order to use it. It might be related to the APST issue with Samsung NVMe SSDs, I'm not sure. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-10-generic 4.11.0-10.15 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: dean 1652 F...m pulseaudio /dev/snd/controlC0: dean 1652 F pulseaudio CurrentDesktop: GNOME Date: Tue Aug 1 17:39:20 2017 HibernationDevice: RESUME=UUID=fb0675d7-391c-4293-a2c5-d283708f1284 InstallationDate: Installed on 2017-07-23 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720) MachineType: LENOVO 20HRCTO1WW ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash nvme_core.default_ps_max_latency_us=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.11.0-10-generic N/A linux-backports-modules-4.11.0-10-generic N/A linux-firmware 1.167 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET37W (1.22 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20HRCTO1WW dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-07-23 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720) Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: artful wayland-session Uname: Linux 4.13.0-041300rc3-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708043/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773905] Re: Support UVC1.5 Camera for Xenial
** Also affects: linux (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/1773905 Title: Support UVC1.5 Camera for Xenial Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: New Bug description: ===SRU Justification=== [Impact] UVC1.5 USB class is not in UVC driver's device ID, so the driver doesn't get loaded. [Test] See if the uvcvideo module is loaded for UVC1.5 camera. I can confirm with this commit, uvcvideo.ko is loaded. In addition, cheese can use the webcam without issue. [Fix] Add UVC1.5 device id to uvcvideo. [Regression Potential] Low. The short control message is already fixed by another commit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
kernel-bug-exists-upstream tag has been added and changed tag to say 'bionic' instead of 'artful' as bug does not affect machine in artful Ubuntu or Kubuntu 17.10 ** Tags removed: artful ** Tags added: bionic kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Incomplete Bug description: I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773299] Re: Dell systems crash when disabling Nvidia dGPU
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Alex Hung (alexhung) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773299 Title: Dell systems crash when disabling Nvidia dGPU Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: Some Dell systems crash when disabling Nvidia dGPU with I+N configurations As NV Linux driver doesn't now support RTD3, BIOS removed the code to prevent system crashes as a short-term solution This is for Linux as Nvidia's Windows driver supports RTD3. In this workaround an _OSI string, Linux-Dell-Video, was used in BIOS as a workaround in Linux. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1773299/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
Assuming using UKUU to try various kernels is fine, I have tried the following kernels and experienced the same suspend failure: 4.17.0 (4.17.0-041700.201806032231) 4.16.13 (4.16.13-041613.201805300810) 4.15.18 (4.15.18-041518.201804190330) 4.15.1 4.15.1-041501.201802031831 Using the latest 4.14 kernel (4.14.47-041447.201805301730) allows suspend to work as expected. The kern.log shows that for a failed suspend on the 4.15, 4.16 and 4.17 kernels it only gets as far as PM: suspend entry (deep) and there are no further entries until startup (after having to shut the machine down) A succesful suspend using the 4.14 kernel gives the kern.log entries as Jun 4 23:27:28 PAviX360 kernel: [ 50.875164] PM: suspend entry (deep) Jun 4 23:27:28 PAviX360 kernel: [ 50.875167] PM: Syncing filesystems ... done. Jun 4 23:27:33 PAviX360 kernel: [ 50.883987] Freezing user space processes ... (elapsed 0. 001 seconds) done. Jun 4 23:27:33 PAviX360 kernel: [ 50.885799] OOM killer disabled. Jun 4 23:27:33 PAviX360 kernel: [ 50.885800] Freezing remaining freezable tasks ... (elaps ed 0.001 seconds) done. etc... So when it fails at 'PM: suspend entry (deep)' using 4.15 kernels and later, it does not move on to PM: Syncing filesystems etc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Incomplete Bug description: I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1738259] Re: need to ensure microcode updates are available to all bare-metal installs of Ubuntu
Agree with Explorer09. Why are my Intel systems now getting AMD
microcode packages and why are my AMD systems getting Intel microcode
packages?? This is a bug.
I would rather it see that I already have one of them installed that
matches my CPU and call it good. If that isn't an option, then just a
recommends.
In the meantime, I just blocked these meta packages from updating on my
systems.
Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1738259
Title:
need to ensure microcode updates are available to all bare-metal
installs of Ubuntu
Status in linux-meta package in Ubuntu:
Triaged
Status in linux-meta-hwe package in Ubuntu:
New
Status in linux-meta-hwe-edge package in Ubuntu:
New
Status in linux-meta-lts-xenial package in Ubuntu:
Fix Released
Status in linux-meta-oem package in Ubuntu:
Fix Released
Status in linux-meta source package in Precise:
New
Status in linux-meta source package in Trusty:
Fix Released
Status in linux-meta source package in Xenial:
Fix Released
Status in linux-meta-hwe source package in Xenial:
Fix Released
Status in linux-meta-hwe-edge source package in Xenial:
Fix Released
Status in linux-meta-lts-xenial source package in Xenial:
Fix Committed
Status in linux-meta-oem source package in Xenial:
Fix Released
Status in linux-meta source package in Zesty:
Invalid
Status in linux-meta source package in Artful:
Fix Released
Status in linux-meta source package in Bionic:
Fix Committed
Bug description:
From time to time, CPU vendors release updates to microcode that can
be loaded into the CPU from the OS. For x86, we have these updates
available in the archive as amd64-microcode and intel-microcode.
Sometimes, these microcode updates have addressed security issues with
the CPU. They almost certainly will again in the future.
We should ensure that all users of Ubuntu on baremetal x86 receive
these security updates, and have them applied to the CPU in early boot
where at all feasible.
Because these are hardware-dependent packages which we don't want to
install except on baremetal (so: not in VMs or containers), the
logical place to pull them into the system is via the kernel, so that
only the kernel baremetal flavors pull them in. This is analogous to
linux-firmware, which is already a dependency of the linux-
image-{lowlatency,generic} metapackages, and whose contents are
applied to the hardware by the kernel similar to microcode.
So, please update the linux-image-{lowlatency,generic} metapackages to
add a dependency on amd64-microcode [amd64], intel-microcode [amd64],
and the corresponding hwe metapackages also.
Please time this change to coincide with the next updates of the
microcode packages in the archive.
I believe we will also need to promote the *-microcode packages to
main from restricted as part of this (again, by analogy with linux-
firmware).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1738259/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771480] Re: WARNING: CPU: 28 PID: 34085 at /build/linux-90Gc2C/linux-3.13.0/net/core/dev.c:1433 dev_disable_lro+0x87/0x90()
** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Trusty) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771480 Title: WARNING: CPU: 28 PID: 34085 at /build/linux- 90Gc2C/linux-3.13.0/net/core/dev.c:1433 dev_disable_lro+0x87/0x90() Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Triaged Bug description: [impact] with a specific network configuration, a kernel WARNING is issued. [test case] configure a trusty system with e/n/i like this: auto bond0.2004 iface bond0.2004 inet manual mtu 9100 vlan-raw-device bond0 auto bond0 iface bond0 inet manual mtu 9100 bond-slaves eth1 eth2 bond-mode 802.3ad bond-miimon 100 bond-use-carrier 1 bond-lacp-rate fast bond-updelay 3000 bond-downdelay 1000 bond-ad-select bandwidth bond-xmit-hash-policy layer3+4 post-up sleep 45 auto br-mesh iface br-mesh inet static bridge_ports bond0.2004 address 192.168.210.3/24 auto eth1 iface eth1 inet manual mtu 9100 bond-master bond0 auto eth2 iface eth2 inet manual mtu 9100 bond-master bond0 adjusting the interface names as needed, of course. then reboot, and the kernel WARNING will appear in the dmesg. [regression potential] the kernel patch has the potential to incorrectly set, or incorrectly not set, features on devices. [other info] previous bug description: I have multiple instances of this dev_disable_lro error in kern.log. Also seeing this: systemd-udevd[1452]: timeout: killing 'bridge-network-interface' [2765] <4>May 1 22:56:42 xxx kernel: [ 404.520990] bonding: bond0: Warning: No 802.3ad response from the link partner for any adapters in the bond <4>May 1 22:56:44 xxx kernel: [ 406.926429] bonding: bond0: Warning: No 802.3ad response from the link partner for any adapters in the bond <4>May 1 22:56:45 xxx kernel: [ 407.569020] [ cut here ] <4>May 1 22:56:45 xxx kernel: [ 407.569029] WARNING: CPU: 28 PID: 34085 at /build/linux-90Gc2C/linux-3.13.0/net/core/dev.c:1433 dev_disable_lro+0x87/0x90() <4>May 1 22:56:45 xxx kernel: [ 407.569032] netdevice: bond0.2004 <4>May 1 22:56:45 xxx kernel: [ 407.569032] failed to disable LRO! <4>May 1 22:56:45 xxx kernel: [ 407.569035] Modules linked in: 8021q garp mrp bridge stp llc bonding iptable_filter ip_tables x_tables nf_conntrack_proto_gre nf_conntrack_ipv6 nf_defrag_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack ipmi_devintf mxm_wmi dcdbas x86_pkg_temp_thermal coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd lpc_ich mei_me mei ipmi_si shpchp wmi acpi_power_meter mac_hid xfs libcrc32c raid10 usb_storage raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 igb ixgbe i2c_algo_bit multipath ahci dca ptp libahci pps_core linear megaraid_sas mdio dm_multipath scsi_dh <4>May 1 22:56:45 xxx kernel: [ 407.569112] CPU: 28 PID: 34085 Comm: brctl Not tainted 3.13.0-142-generic #191-Ubuntu <4>May 1 22:56:45 xxx kernel: [ 407.569115] Hardware name: Dell Inc. PowerEdge R730xd/072T6D, BIOS 2.7.1 001/22/2018 <4>May 1 22:56:45 xxx kernel: [ 407.569118] 881fcc753c70 8172e7fc 881fcc753cb8 <4>May 1 22:56:45 xxx kernel: [ 407.569129] 0009 881fcc753ca8 8106afad 883fcc6f8000 <4>May 1 22:56:45 xxx kernel: [ 407.569139] 883fcc696880 883fcc6f8000 881fce82dd40 <4>May 1 22:56:45 xxx kernel: [ 407.569150] Call Trace: <4>May 1 22:56:45 xxx kernel: [ 407.569160] [] dump_stack+0x64/0x82 <4>May 1 22:56:45 xxx kernel: [ 407.569168] [] warn_slowpath_common+0x7d/0xa0 <4>May 1 22:56:45 xxx kernel: [ 407.569175] [] warn_slowpath_fmt+0x4c/0x50 <4>May 1 22:56:45 xxx kernel: [ 407.569183] [] dev_disable_lro+0x87/0x90 <4>May 1 22:56:45 xxx kernel: [ 407.569195] [] br_add_if+0x1f3/0x430 [bridge] <4>May 1 22:56:45 xxx kernel: [ 407.569205] [] add_del_if+0x5d/0x90 [bridge] <4>May 1 22:56:45 xxx kernel: [ 407.569215] [] br_dev_ioctl+0x5b/0x90 [bridge] <4>May 1 22:56:45 xxx kernel: [ 407.569223] [] dev_ifsioc+0x313/0x360 <4>May 1 22:56:45 xxx kernel: [ 407.569230] [] ? dev_get_by_name_rcu+0x69/0x90 <4>May 1 22:56:45 xxx kernel: [ 407.569237] [] dev_ioctl+0xe9/0x590 <4>May 1 22:56:45 xxx kernel: [ 407.569245] [] sock_do_ioctl+0x45/0x50 <4>May 1 22:56:45 xxx kernel: [ 407.569252] [] sock_ioctl+0x1f0/0x2c0 <4>May 1 22:56:45 xxx kernel: [ 407.569260] [] do_vfs_ioctl+0x2e0/0x4c0 <4>May 1 22:56:45 xxx kernel: [ 407.569267] [] ? fput+0xe/0x10 <4>May 1 22:56:45 xxx kernel: [ 407.569273] []
[Kernel-packages] [Bug 1770254] Re: [SRU][Artful] using vfio-pci on a combination of cn8xxx and some PCI devices results in a kernel panic.
-- Host with -proposed kernel -- ubuntu@anuchin:~$ virsh nodedev-detach pci_0002_01_00_1 Device pci_0002_01_00_1 detached ubuntu@anuchin:~$ ubuntu@anuchin:~$ readlink /sys/bus/pci/devices/0002\:01\:00.1/driver ../../../../../../../bus/pci/drivers/vfio-pci ubuntu@anuchin:~$ -- Bionic Guest -- ubuntu@ubuntu-pcitest:~$ lspci -k 00:00.0 Host bridge: Red Hat, Inc. QEMU PCIe Host bridge Subsystem: Red Hat, Inc QEMU PCIe Host bridge 00:01.0 PCI bridge: Red Hat, Inc. QEMU PCIe Root port Kernel driver in use: pcieport Kernel modules: shpchp 00:01.1 PCI bridge: Red Hat, Inc. QEMU PCIe Root port Kernel driver in use: pcieport Kernel modules: shpchp 00:01.2 PCI bridge: Red Hat, Inc. QEMU PCIe Root port Kernel driver in use: pcieport Kernel modules: shpchp 00:01.3 PCI bridge: Red Hat, Inc. QEMU PCIe Root port Kernel driver in use: pcieport Kernel modules: shpchp 00:01.4 PCI bridge: Red Hat, Inc. QEMU PCIe Root port Kernel driver in use: pcieport Kernel modules: shpchp 00:01.5 PCI bridge: Red Hat, Inc. QEMU PCIe Root port Kernel driver in use: pcieport Kernel modules: shpchp 01:00.0 Ethernet controller: Red Hat, Inc Virtio network device (rev 01) Subsystem: Red Hat, Inc Virtio network device Kernel driver in use: virtio-pci 02:00.0 Communication controller: Red Hat, Inc Virtio console (rev 01) Subsystem: Red Hat, Inc Virtio console Kernel driver in use: virtio-pci 03:00.0 SCSI storage controller: Red Hat, Inc Virtio block device (rev 01) Subsystem: Red Hat, Inc Virtio block device Kernel driver in use: virtio-pci 04:00.0 SCSI storage controller: Red Hat, Inc Virtio block device (rev 01) Subsystem: Red Hat, Inc Virtio block device Kernel driver in use: virtio-pci 05:00.0 Ethernet controller: Cavium, Inc. THUNDERX Network Interface Controller virtual function (rev 08) Subsystem: Cavium, Inc. THUNDERX Network Interface Controller virtual function Kernel modules: nicvf ubuntu@ubuntu-pcitest:~$ ** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770254 Title: [SRU][Artful] using vfio-pci on a combination of cn8xxx and some PCI devices results in a kernel panic. Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Committed Bug description: [Impact] Using vfio-pci on a combination of cn8xxx and some PCI devices results in a kernel panic. This is triggered by issuing a bus or a slot reset on the PCI device. [Fix] The following patches checks indicate that the reset is not possible preventing the kernel panic. 357027786f35 PCI: Avoid bus reset if bridge itself is broken 822155100e58 PCI: Mark Cavium CN8xxx to avoid bus reset 33ba90aa4d44 PCI: Avoid slot reset if bridge itself is broken These patches are already in Bionic, we need these patches in Artful so that xenial linux-hwe also has the fix. The platforms of interest were certified with Xenial and linux-hwe, so we are interested in fixing this only in Artful. [Test] - Artful Host with Artful/bionic guests - Pass though PCI device (vfio-pci) from Artful to bionic and make sure its usable. - The device should pass through and not cause a kernel panic. A test kernel is available in ppa:manjo/lp1770254 [Regression Potential] None. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
Hi Joseph - I have used UKUU to try the 4.17 kernel. As far as I am aware, this is an easy way to try the 4.17 kernel ubuntu build. Can you just confirm that I'm correct in that assumption or do i need to try a different method? (i.e follow the wiki.ubuntu.com/KernelMainlineBuilds method rather than using UKUU?) UKUU 4.17 latest version exhibited same suspend problem last time. I will try it again though and let you know. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Incomplete Bug description: I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772991] Re: [Ubuntu 18.04.1] POWER9 - Nvidia Volta - Kernel changes to enable Nvidia driver on bare metal
We are still waiting for a couple of acks at this point. The patch set should meeting the SRU criteria, just waiting for review. I'll resend the SRU request if the acks don't happen soon. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772991 Title: [Ubuntu 18.04.1] POWER9 - Nvidia Volta - Kernel changes to enable Nvidia driver on bare metal Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: == SRU Justification == 12 kernel patches have been identified as needed to support Nvidia Volta on bare metal. All are accepted upstream in 4.17. Three of those are already in bionic, leaving a total of 9 remaining commits needed in bionic. This pull request is for those other 9 commits. == Regression Potential == All of the commits are specific to powerpc. == Test Case == A test kernel was built with these patches and tested by IBM. == Comment: #0 - Barry B. Arndt - 2018-05-23 13:40:33 == 12 kernel patches have been identified as needed to support Nvidia Volta on bare metal. All are accepted upstream in 4.17. Three of those are already in bionic, leaving a total of 9 remaining commits needed in bionic. Those 9 commits are: 720c84046c26 powerpc/npu-dma.c: Fix crash after __mmu_notifier_register failure 2b74e2a9b39d powerpc/powernv/npu: Fix deadlock in mmio_invalidate() 5ee573e8ef03 powerpc/powernv/mce: Don't silently restart the machine fb5924fddf9e powerpc/mm: Flush cache on memory hot(un)plug 7fd6641de28f powerpc/powernv/memtrace: Let the arch hotunplug code flush cache 28a5933e8d36 powerpc/powernv/npu: Add lock to prevent race in concurrent context init/destroy a1409adac748 powerpc/powernv/npu: Prevent overwriting of pnv_npu2_init_contex() callback parameters d0cf9b561ca9 powerpc/powernv/npu: Do a PID GPU TLB flush when invalidating a large address range 75ecfb49516c powerpc/mce: Fix a bug where mce loops on memory UE. We cherry-picked the commits, and all applied cleanly. The resultant kernel built successfully and loaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1772991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772991] Re: [Ubuntu 18.04.1] POWER9 - Nvidia Volta - Kernel changes to enable Nvidia driver on bare metal
hi Joseph, I tried to discover if the patchset above was accepted/acked but I didn't find anything. Do you know if the patchset would make the SRU criteria? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772991 Title: [Ubuntu 18.04.1] POWER9 - Nvidia Volta - Kernel changes to enable Nvidia driver on bare metal Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: == SRU Justification == 12 kernel patches have been identified as needed to support Nvidia Volta on bare metal. All are accepted upstream in 4.17. Three of those are already in bionic, leaving a total of 9 remaining commits needed in bionic. This pull request is for those other 9 commits. == Regression Potential == All of the commits are specific to powerpc. == Test Case == A test kernel was built with these patches and tested by IBM. == Comment: #0 - Barry B. Arndt - 2018-05-23 13:40:33 == 12 kernel patches have been identified as needed to support Nvidia Volta on bare metal. All are accepted upstream in 4.17. Three of those are already in bionic, leaving a total of 9 remaining commits needed in bionic. Those 9 commits are: 720c84046c26 powerpc/npu-dma.c: Fix crash after __mmu_notifier_register failure 2b74e2a9b39d powerpc/powernv/npu: Fix deadlock in mmio_invalidate() 5ee573e8ef03 powerpc/powernv/mce: Don't silently restart the machine fb5924fddf9e powerpc/mm: Flush cache on memory hot(un)plug 7fd6641de28f powerpc/powernv/memtrace: Let the arch hotunplug code flush cache 28a5933e8d36 powerpc/powernv/npu: Add lock to prevent race in concurrent context init/destroy a1409adac748 powerpc/powernv/npu: Prevent overwriting of pnv_npu2_init_contex() callback parameters d0cf9b561ca9 powerpc/powernv/npu: Do a PID GPU TLB flush when invalidating a large address range 75ecfb49516c powerpc/mce: Fix a bug where mce loops on memory UE. We cherry-picked the commits, and all applied cleanly. The resultant kernel built successfully and loaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1772991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770108] Re: No wifi in 4.13.0-41-generic
I only upgrade via the Ubuntu Software Updater whenever it feels like doing so. How do I ensure the -extra package gets installed? Does this indicate a problem with the Updater Software? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770108 Title: No wifi in 4.13.0-41-generic Status in linux package in Ubuntu: Confirmed Bug description: Wifi adapter not showing since upgrading to 4.13.0-41-generic, still works fine if i roll back to 4.13.0-39-generic. Ubuntu 16.04 adapter details *-network description: Wireless interface product: RTL8192CE PCIe Wireless Network Adapter vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:01:00.0 logical name: wlp1s0 version: 01 serial: width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774127] Re: linux-gcp: 4.13.0-1019.23 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1774127 Title: linux-gcp: 4.13.0-1019.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1774124 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1774127/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774190] Re: linux: 3.13.0-151.201 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774190 Title: linux: 3.13.0-151.201 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1774191 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1774190/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774964] Re: [LTCTest][OPAL][OP910.20] WARNING: CPU: 97 PID: 11965 at /build/linux-0zaMZw/linux-4.15.0/kernel/sched/core.c:1189 set_task_cpu+0x240/0x250
** Changed in: ubuntu-power-systems Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774964 Title: [LTCTest][OPAL][OP910.20] WARNING: CPU: 97 PID: 11965 at /build/linux- 0zaMZw/linux-4.15.0/kernel/sched/core.c:1189 set_task_cpu+0x240/0x250 Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: == Comment: #0 - PAVAMAN SUBRAMANIYAM <> - 2018-04-25 01:59:10 == ---Problem Description--- WARNING: CPU: 97 PID: 11965 at /build/linux-0zaMZw/linux-4.15.0/kernel/sched/core.c:1189 set_task_cpu+0x240/0x250 ---uname output--- Linux ltc-wspoon8 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = P9 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install a P9 Open Power Hardware with the latest OP910.20 Firmware images. root@witherspoon:~# cat /etc/os-release ID="openbmc-phosphor" NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)" VERSION="ibm-v2.0" VERSION_ID="ibm-v2.0-0-r46-0-gbed584c" PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) ibm-v2.0" BUILD_ID="ibm-v2.0-0-r46" root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION open-power-witherspoon-v1.21.2-251-ge2e9363-dirty buildroot-2017.11-5-g65679be skiboot-v5.10.3-op910-1-p240231e hostboot-0aa5bed linux-4.14.24-openpower1-p3e84190 petitboot-v1.6.6-pd7224b4 machine-xml-4af occ-8c5b727 hostboot-binaries-9bd4056 capp-ucode-p9-dd2-v3 sbe-7e02c23 Then we have installed the Ubuntu 18.04 OS on the machine. root@ltc-wspoon8:~# uname -a Linux ltc-wspoon8 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@ltc-wspoon8:~# cat /etc/os-release NAME="Ubuntu" VERSION="18.04 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic root@ltc-wspoon8:~# cat /proc/cpuinfo | tail cpu : POWER9, altivec supported clock : 2300.00MHz revision: 2.1 (pvr 004e 1201) timebase: 51200 platform: PowerNV model : 8335-GTC machine : PowerNV 8335-GTC firmware: OPAL MMU : Radix root@ltc-wspoon8:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-20-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-20-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=a2cd572c-9047-4f0a-843b-6996fae3e999 ro quiet splash nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@ltc-wspoon8:~# ps -ef | grep opal root880 2 0 01:25 ?00:00:00 [kopald] root 3604 1 2 01:25 ?00:00:03 /usr/sbin/opal-prd root 4858 4278 0 01:28 pts/000:00:00 grep --color=auto opal root@ltc-wspoon8:~# service opal-prd status ? opal-prd.service - OPAL PRD daemon Loaded: loaded (/lib/systemd/system/opal-prd.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2018-04-25 01:25:48 CDT; 2min 43s ago Docs: man:opal-prd(8) Main PID: 3604 (opal-prd) Tasks: 1 (limit: 22118) CGroup: /system.slice/opal-prd.service ??3604 /usr/sbin/opal-prd Apr 25 01:25:52 ltc-wspoon8 opal-prd[3604]: IMAGE: hbrt_init complete, version 0290 Apr 25 01:25:52 ltc-wspoon8 opal-prd[3604]: HBRT: hservices_init done Apr 25 01:25:52 ltc-wspoon8 opal-prd[3604]: HBRT: calling enable_attns Apr 25 01:25:52 ltc-wspoon8 opal-prd[3604]: HBRT: ATTN_SLOW:I>>>ATTN_RT::enableAttns Apr 25 01:25:52 ltc-wspoon8 opal-prd[3604]: HBRT: ATTN_SLOW:I>Service::enableAttns() enter Apr 25 01:25:52 ltc-wspoon8 opal-prd[3604]: HBRT: ATTN_SLOW:I>Service::enableAttns() exit Apr 25 01:25:52 ltc-wspoon8 opal-prd[3604]: HBRT: ATTN_SLOW:I>< CR: 24002882 XER: [ 191.741188] CFAR: c0181b54 DAR: 2018faf69194 DSISR: 8000 SOFTE: 1
[Kernel-packages] [Bug 1642510] Re: sched: clsact qdisc is missing in xenial
It looks like the patch got one commit, but not a second:
https://lists.ubuntu.com/archives/kernel-team/2016-November/081059.html
https://lists.ubuntu.com/archives/kernel-team/2016-December/081429.html
https://lists.ubuntu.com/archives/kernel-team/2016-December/081432.html
Would it be possible to add some detail to the bug to address the "no-
ack" posted to the mailing list?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1642510
Title:
sched: clsact qdisc is missing in xenial
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
In Progress
Bug description:
This is implemented in linux v4.5 by the following upstream patch:
1f211a1b929c ("net, sched: add clsact qdisc")
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1f211a1b929c
The backport is straightforward.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1642510/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774964] Re: [LTCTest][OPAL][OP910.20] WARNING: CPU: 97 PID: 11965 at /build/linux-0zaMZw/linux-4.15.0/kernel/sched/core.c:1189 set_task_cpu+0x240/0x250
I built a test kernel with commit 75ecfb49516c53. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1774964 Can you test this kernel and see if it resolves this bug? Note about installing test kernels: • If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages. • If the test kernel is 4.15(Bionic) or newer, you need to install the linux-modules, linux-modules-extra and linux-image-unsigned .deb packages. Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774964 Title: [LTCTest][OPAL][OP910.20] WARNING: CPU: 97 PID: 11965 at /build/linux- 0zaMZw/linux-4.15.0/kernel/sched/core.c:1189 set_task_cpu+0x240/0x250 Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: == Comment: #0 - PAVAMAN SUBRAMANIYAM <> - 2018-04-25 01:59:10 == ---Problem Description--- WARNING: CPU: 97 PID: 11965 at /build/linux-0zaMZw/linux-4.15.0/kernel/sched/core.c:1189 set_task_cpu+0x240/0x250 ---uname output--- Linux ltc-wspoon8 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = P9 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install a P9 Open Power Hardware with the latest OP910.20 Firmware images. root@witherspoon:~# cat /etc/os-release ID="openbmc-phosphor" NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)" VERSION="ibm-v2.0" VERSION_ID="ibm-v2.0-0-r46-0-gbed584c" PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) ibm-v2.0" BUILD_ID="ibm-v2.0-0-r46" root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION open-power-witherspoon-v1.21.2-251-ge2e9363-dirty buildroot-2017.11-5-g65679be skiboot-v5.10.3-op910-1-p240231e hostboot-0aa5bed linux-4.14.24-openpower1-p3e84190 petitboot-v1.6.6-pd7224b4 machine-xml-4af occ-8c5b727 hostboot-binaries-9bd4056 capp-ucode-p9-dd2-v3 sbe-7e02c23 Then we have installed the Ubuntu 18.04 OS on the machine. root@ltc-wspoon8:~# uname -a Linux ltc-wspoon8 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@ltc-wspoon8:~# cat /etc/os-release NAME="Ubuntu" VERSION="18.04 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic root@ltc-wspoon8:~# cat /proc/cpuinfo | tail cpu : POWER9, altivec supported clock : 2300.00MHz revision: 2.1 (pvr 004e 1201) timebase: 51200 platform: PowerNV model : 8335-GTC machine : PowerNV 8335-GTC firmware: OPAL MMU : Radix root@ltc-wspoon8:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-20-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-20-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=a2cd572c-9047-4f0a-843b-6996fae3e999 ro quiet splash nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@ltc-wspoon8:~# ps -ef | grep opal root880 2 0 01:25 ?00:00:00 [kopald] root 3604 1 2 01:25 ?00:00:03 /usr/sbin/opal-prd root 4858 4278 0 01:28 pts/000:00:00 grep --color=auto opal root@ltc-wspoon8:~# service opal-prd status ? opal-prd.service - OPAL PRD daemon Loaded: loaded (/lib/systemd/system/opal-prd.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2018-04-25 01:25:48 CDT; 2min 43s ago Docs: man:opal-prd(8) Main PID: 3604 (opal-prd) Tasks: 1 (limit: 22118) CGroup: /system.slice/opal-prd.service ??3604 /usr/sbin/opal-prd Apr 25 01:25:52 ltc-wspoon8 opal-prd[3604]: IMAGE: hbrt_init complete, version 0290 Apr 25 01:25:52 ltc-wspoon8 opal-prd[3604]: HBRT: hservices_init done Apr 25 01:25:52 ltc-wspoon8 opal-prd[3604]: HBRT: calling enable_attns Apr 25
[Kernel-packages] [Bug 1642510] Re: sched: clsact qdisc is missing in xenial
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Assignee: Tim Gardner (timg-tpi) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1642510
Title:
sched: clsact qdisc is missing in xenial
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
In Progress
Bug description:
This is implemented in linux v4.5 by the following upstream patch:
1f211a1b929c ("net, sched: add clsact qdisc")
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1f211a1b929c
The backport is straightforward.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1642510/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774964] Re: [LTCTest][OPAL][OP910.20] WARNING: CPU: 97 PID: 11965 at /build/linux-0zaMZw/linux-4.15.0/kernel/sched/core.c:1189 set_task_cpu+0x240/0x250
** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => Joseph Salisbury (jsalisbury) ** Also affects: linux (Ubuntu Cosmic) Importance: High Assignee: Joseph Salisbury (jsalisbury) Status: In Progress ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774964 Title: [LTCTest][OPAL][OP910.20] WARNING: CPU: 97 PID: 11965 at /build/linux- 0zaMZw/linux-4.15.0/kernel/sched/core.c:1189 set_task_cpu+0x240/0x250 Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: == Comment: #0 - PAVAMAN SUBRAMANIYAM <> - 2018-04-25 01:59:10 == ---Problem Description--- WARNING: CPU: 97 PID: 11965 at /build/linux-0zaMZw/linux-4.15.0/kernel/sched/core.c:1189 set_task_cpu+0x240/0x250 ---uname output--- Linux ltc-wspoon8 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = P9 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install a P9 Open Power Hardware with the latest OP910.20 Firmware images. root@witherspoon:~# cat /etc/os-release ID="openbmc-phosphor" NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)" VERSION="ibm-v2.0" VERSION_ID="ibm-v2.0-0-r46-0-gbed584c" PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) ibm-v2.0" BUILD_ID="ibm-v2.0-0-r46" root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION open-power-witherspoon-v1.21.2-251-ge2e9363-dirty buildroot-2017.11-5-g65679be skiboot-v5.10.3-op910-1-p240231e hostboot-0aa5bed linux-4.14.24-openpower1-p3e84190 petitboot-v1.6.6-pd7224b4 machine-xml-4af occ-8c5b727 hostboot-binaries-9bd4056 capp-ucode-p9-dd2-v3 sbe-7e02c23 Then we have installed the Ubuntu 18.04 OS on the machine. root@ltc-wspoon8:~# uname -a Linux ltc-wspoon8 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@ltc-wspoon8:~# cat /etc/os-release NAME="Ubuntu" VERSION="18.04 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic root@ltc-wspoon8:~# cat /proc/cpuinfo | tail cpu : POWER9, altivec supported clock : 2300.00MHz revision: 2.1 (pvr 004e 1201) timebase: 51200 platform: PowerNV model : 8335-GTC machine : PowerNV 8335-GTC firmware: OPAL MMU : Radix root@ltc-wspoon8:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-20-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-20-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=a2cd572c-9047-4f0a-843b-6996fae3e999 ro quiet splash nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@ltc-wspoon8:~# ps -ef | grep opal root880 2 0 01:25 ?00:00:00 [kopald] root 3604 1 2 01:25 ?00:00:03 /usr/sbin/opal-prd root 4858 4278 0 01:28 pts/000:00:00 grep --color=auto opal root@ltc-wspoon8:~# service opal-prd status ? opal-prd.service - OPAL PRD daemon Loaded: loaded (/lib/systemd/system/opal-prd.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2018-04-25 01:25:48 CDT; 2min 43s ago Docs: man:opal-prd(8) Main PID: 3604 (opal-prd) Tasks: 1 (limit: 22118) CGroup: /system.slice/opal-prd.service ??3604 /usr/sbin/opal-prd Apr 25 01:25:52 ltc-wspoon8 opal-prd[3604]: IMAGE:
[Kernel-packages] [Bug 1774994] Re: Laptop wakes up immediately after suspend or hibernation
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17 ** Package changed: linux-signed (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774994 Title: Laptop wakes up immediately after suspend or hibernation Status in linux package in Ubuntu: Incomplete Bug description: After going into suspend (via command line or lid close), the MacBook Pro (early 2015) wakes up immediately again. Same for hibernation. Running Ubuntu 18.04. extract from dmesg for a lid-close -> suspend -> wake-up -> lid-open cycle: [0.00] Linux version 4.15.0-22-generic (buildd@lgw01-amd64-013) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #24-Ubuntu SMP Wed May 16 12:15:17 UTC 2018 (Ubuntu 4.15.0-22.24-generic 4.15.17) [ ... ] [ 778.968982] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [ 783.011399] PM: suspend entry (deep) [ 783.011400] PM: Syncing filesystems ... done. [ 783.028538] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 783.030844] OOM killer disabled. [ 783.030844] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 783.032193] Suspending console(s) (use no_console_suspend to debug) [ 783.049960] sd 1:0:0:0: [sda] Synchronizing SCSI cache [ 783.054107] sd 1:0:0:0: [sda] Stopping disk [ 783.146124] thunderbolt :07:00.0: suspending... [ 783.146685] thunderbolt :07:00.0: suspend finished [ 783.146689] thunderbolt :07:00.0: stopping RX ring 0 [ 783.146698] thunderbolt :07:00.0: disabling interrupt at register 0x38200 bit 12 (0x1001 -> 0x1) [ 783.146710] thunderbolt :07:00.0: stopping TX ring 0 [ 783.146718] thunderbolt :07:00.0: disabling interrupt at register 0x38200 bit 0 (0x1 -> 0x0) [ 783.146725] thunderbolt :07:00.0: control channel stopped [ 783.246464] ACPI: Preparing to enter system sleep state S3 [ 783.418015] ACPI: EC: event blocked [ 783.418016] ACPI: EC: EC stopped [ 783.418018] PM: Saving platform NVS memory [ 783.418027] Disabling non-boot CPUs ... [ 783.434574] IRQ 65: no longer affine to CPU1 [ 783.435629] smpboot: CPU 1 is now offline [ 783.454574] IRQ 66: no longer affine to CPU2 [ 783.456378] smpboot: CPU 2 is now offline [ 783.478405] IRQ 21: no longer affine to CPU3 [ 783.478414] IRQ 43: no longer affine to CPU3 [ 783.478435] IRQ 71: no longer affine to CPU3 [ 783.479449] smpboot: CPU 3 is now offline [ 783.481656] ACPI: Low-level resume complete [ 783.481733] ACPI: EC: EC started [ 783.481734] PM: Restoring platform NVS memory [ 783.482160] Enabling non-boot CPUs ... [ 783.482240] x86: Booting SMP configuration: [ 783.482241] smpboot: Booting Node 0 Processor 1 APIC 0x2 [ 783.558589] cache: parent cpu1 should not be sleeping [ 783.687159] CPU1 is up [ 783.687212] smpboot: Booting Node 0 Processor 2 APIC 0x1 [ 783.687812] cache: parent cpu2 should not be sleeping [ 783.688001] CPU2 is up [ 783.688028] smpboot: Booting Node 0 Processor 3 APIC 0x3 [ 783.783709] cache: parent cpu3 should not be sleeping [ 783.978233] CPU3 is up [ 783.982020] ACPI: Waking up from system sleep state S3 [ 784.093246] pcieport :06:03.0: quirk: waiting for thunderbolt to reestablish PCI tunnels... [ 784.093249] pcieport :06:04.0: quirk: waiting for thunderbolt to reestablish PCI tunnels... [ 784.093362] pcieport :06:06.0: quirk: waiting for thunderbolt to reestablish PCI tunnels... [ 784.093475] pcieport :06:05.0: quirk: waiting for thunderbolt to reestablish PCI tunnels... [ 784.112655] thunderbolt :07:00.0: control channel starting... [ 784.112660] thunderbolt :07:00.0: starting TX ring 0 [ 784.112673] thunderbolt :07:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) [ 784.112677] thunderbolt :07:00.0: starting RX ring 0 [ 784.112689] thunderbolt :07:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) [ 784.112696] thunderbolt :07:00.0: resuming... [ 784.112699] thunderbolt :07:00.0: resetting switch at 0
[Kernel-packages] [Bug 1775065] Re: No brightness controls and /sys/class/backlight empty after upgrade to Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter acpi_osi= is a workaround)
** Attachment added: "dmidecode" https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1775065/+attachment/5148734/+files/dmidecode -- 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/1775065 Title: No brightness controls and /sys/class/backlight empty after upgrade to Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter acpi_osi= is a workaround) Status in linux-signed package in Ubuntu: New Bug description: This is a case of "Backlight control does not work, and there are no entries in /sys/class/backlight" for what lspci reports as "NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)" where the kernel parameter acpi_osi= is a workaround. (The workaround is also recorded on Ask Ubuntu at https://askubuntu.com/questions/1030526 /brightness-on-laptop-msi-gt72vr-in-ubuntu-18-04-with-nvidia-gtx-1060 -mobile-does/1043598#1043598.) The problem is new for me after upgrade to Bionic, although the cause might be the corresponding update to the NVIDIA drivers. I will add attachments following the instructions at https://wiki.ubuntu.com/Kernel/Debugging/Backlight, though most of them seem to be uninteresting. If I can provide further information, please let me know. 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: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 4 14:20:34 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-06-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1775065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775065] Re: No brightness controls and /sys/class/backlight empty after upgrade to Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter acpi_osi= is a workaround)
** Attachment added: "fwts method" https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1775065/+attachment/5148733/+files/fwts%20method -- 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/1775065 Title: No brightness controls and /sys/class/backlight empty after upgrade to Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter acpi_osi= is a workaround) Status in linux-signed package in Ubuntu: New Bug description: This is a case of "Backlight control does not work, and there are no entries in /sys/class/backlight" for what lspci reports as "NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)" where the kernel parameter acpi_osi= is a workaround. (The workaround is also recorded on Ask Ubuntu at https://askubuntu.com/questions/1030526 /brightness-on-laptop-msi-gt72vr-in-ubuntu-18-04-with-nvidia-gtx-1060 -mobile-does/1043598#1043598.) The problem is new for me after upgrade to Bionic, although the cause might be the corresponding update to the NVIDIA drivers. I will add attachments following the instructions at https://wiki.ubuntu.com/Kernel/Debugging/Backlight, though most of them seem to be uninteresting. If I can provide further information, please let me know. 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: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 4 14:20:34 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-06-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1775065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775065] Re: No brightness controls and /sys/class/backlight empty after upgrade to Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter acpi_osi= is a workaround)
** Attachment added: "grep -r . proc-acpi" https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1775065/+attachment/5148730/+files/grep%20-r%20.%20proc-acpi -- 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/1775065 Title: No brightness controls and /sys/class/backlight empty after upgrade to Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter acpi_osi= is a workaround) Status in linux-signed package in Ubuntu: New Bug description: This is a case of "Backlight control does not work, and there are no entries in /sys/class/backlight" for what lspci reports as "NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)" where the kernel parameter acpi_osi= is a workaround. (The workaround is also recorded on Ask Ubuntu at https://askubuntu.com/questions/1030526 /brightness-on-laptop-msi-gt72vr-in-ubuntu-18-04-with-nvidia-gtx-1060 -mobile-does/1043598#1043598.) The problem is new for me after upgrade to Bionic, although the cause might be the corresponding update to the NVIDIA drivers. I will add attachments following the instructions at https://wiki.ubuntu.com/Kernel/Debugging/Backlight, though most of them seem to be uninteresting. If I can provide further information, please let me know. 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: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 4 14:20:34 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-06-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1775065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775065] Re: No brightness controls and /sys/class/backlight empty after upgrade to Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter acpi_osi= is a workaround)
** Attachment added: "dsdt.dsl" https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1775065/+attachment/5148731/+files/dsdt.dsl -- 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/1775065 Title: No brightness controls and /sys/class/backlight empty after upgrade to Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter acpi_osi= is a workaround) Status in linux-signed package in Ubuntu: New Bug description: This is a case of "Backlight control does not work, and there are no entries in /sys/class/backlight" for what lspci reports as "NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)" where the kernel parameter acpi_osi= is a workaround. (The workaround is also recorded on Ask Ubuntu at https://askubuntu.com/questions/1030526 /brightness-on-laptop-msi-gt72vr-in-ubuntu-18-04-with-nvidia-gtx-1060 -mobile-does/1043598#1043598.) The problem is new for me after upgrade to Bionic, although the cause might be the corresponding update to the NVIDIA drivers. I will add attachments following the instructions at https://wiki.ubuntu.com/Kernel/Debugging/Backlight, though most of them seem to be uninteresting. If I can provide further information, please let me know. 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: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 4 14:20:34 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-06-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1775065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775065] Re: No brightness controls and /sys/class/backlight empty after upgrade to Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter acpi_osi= is a workaround)
** Attachment added: "fwts" https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1775065/+attachment/5148732/+files/fwts -- 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/1775065 Title: No brightness controls and /sys/class/backlight empty after upgrade to Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter acpi_osi= is a workaround) Status in linux-signed package in Ubuntu: New Bug description: This is a case of "Backlight control does not work, and there are no entries in /sys/class/backlight" for what lspci reports as "NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)" where the kernel parameter acpi_osi= is a workaround. (The workaround is also recorded on Ask Ubuntu at https://askubuntu.com/questions/1030526 /brightness-on-laptop-msi-gt72vr-in-ubuntu-18-04-with-nvidia-gtx-1060 -mobile-does/1043598#1043598.) The problem is new for me after upgrade to Bionic, although the cause might be the corresponding update to the NVIDIA drivers. I will add attachments following the instructions at https://wiki.ubuntu.com/Kernel/Debugging/Backlight, though most of them seem to be uninteresting. If I can provide further information, please let me know. 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: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 4 14:20:34 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-06-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1775065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775065] Re: No brightness controls and /sys/class/backlight empty after upgrade to Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter acpi_osi= is a workaround)
Although step 3 at https://wiki.ubuntu.com/Kernel/Debugging/Backlight asks for the output of ls /sys/class/backlight, it gives no output, so I do not include an attachment. Steps 9, 10, and 12–16 either cause no changes or do not apply. Step 11, as noted, is a workaround. -- 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/1775065 Title: No brightness controls and /sys/class/backlight empty after upgrade to Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter acpi_osi= is a workaround) Status in linux-signed package in Ubuntu: New Bug description: This is a case of "Backlight control does not work, and there are no entries in /sys/class/backlight" for what lspci reports as "NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)" where the kernel parameter acpi_osi= is a workaround. (The workaround is also recorded on Ask Ubuntu at https://askubuntu.com/questions/1030526 /brightness-on-laptop-msi-gt72vr-in-ubuntu-18-04-with-nvidia-gtx-1060 -mobile-does/1043598#1043598.) The problem is new for me after upgrade to Bionic, although the cause might be the corresponding update to the NVIDIA drivers. I will add attachments following the instructions at https://wiki.ubuntu.com/Kernel/Debugging/Backlight, though most of them seem to be uninteresting. If I can provide further information, please let me know. 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: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 4 14:20:34 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-06-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1775065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775065] [NEW] No brightness controls and /sys/class/backlight empty after upgrade to Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter acpi_osi= is a workaround)
Public bug reported: This is a case of "Backlight control does not work, and there are no entries in /sys/class/backlight" for what lspci reports as "NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)" where the kernel parameter acpi_osi= is a workaround. (The workaround is also recorded on Ask Ubuntu at https://askubuntu.com/questions/1030526/brightness-on- laptop-msi-gt72vr-in-ubuntu-18-04-with-nvidia-gtx-1060-mobile- does/1043598#1043598.) The problem is new for me after upgrade to Bionic, although the cause might be the corresponding update to the NVIDIA drivers. I will add attachments following the instructions at https://wiki.ubuntu.com/Kernel/Debugging/Backlight, though most of them seem to be uninteresting. If I can provide further information, please let me know. 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: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 4 14:20:34 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-06-04 (0 days ago) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1775065 Title: No brightness controls and /sys/class/backlight empty after upgrade to Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter acpi_osi= is a workaround) Status in linux-signed package in Ubuntu: New Bug description: This is a case of "Backlight control does not work, and there are no entries in /sys/class/backlight" for what lspci reports as "NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)" where the kernel parameter acpi_osi= is a workaround. (The workaround is also recorded on Ask Ubuntu at https://askubuntu.com/questions/1030526 /brightness-on-laptop-msi-gt72vr-in-ubuntu-18-04-with-nvidia-gtx-1060 -mobile-does/1043598#1043598.) The problem is new for me after upgrade to Bionic, although the cause might be the corresponding update to the NVIDIA drivers. I will add attachments following the instructions at https://wiki.ubuntu.com/Kernel/Debugging/Backlight, though most of them seem to be uninteresting. If I can provide further information, please let me know. 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: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 4 14:20:34 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-06-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1775065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773643] Re: [Clevo W253EUQ] Turn on bluetooth with Fn+F12 not working
Hello, My laptop use the fn + f12 key to switch on/off the Bluetooth. Here is my laptop Manuel : https://www.manualslib.com/products/Clevo-W253euq-5889604.html Best regards Battant -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773643 Title: [Clevo W253EUQ] Turn on bluetooth with Fn+F12 not working Status in linux package in Ubuntu: Incomplete Bug description: Hello, Since long time my [Clevo W253EUQ] Turn on bluetooth with Fn+F12 not working For more information see this link bellow https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322068 Could you help me to fix this bug ? Best regards Battant ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 27 13:21:46 2018 InstallationDate: Installed on 2018-04-29 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mparchet 1714 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-29 (28 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=9d6286f1-598b-46c8-a491-3e29fc732cb9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W240EU/W250EUQ/W270EUQ dmi.board.vendor: CLEVO CO. dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd11/11/2013:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W240EU/W250EUQ/W270EUQ dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO CO. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mparchet 1714 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-29 (28 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=9d6286f1-598b-46c8-a491-3e29fc732cb9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W240EU/W250EUQ/W270EUQ dmi.board.vendor: CLEVO CO. dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd11/11/2013:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W240EU/W250EUQ/W270EUQ dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO CO.
[Kernel-packages] [Bug 1775044] Re: continuously freeze the system
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17 ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775044 Title: continuously freeze the system Status in linux package in Ubuntu: Incomplete Bug description: I am unable to use the system properly because it is continuously freezing, please fix the problems ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-43-generic 4.13.0-43.48 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic i686 ApportVersion: 2.20.7-0ubuntu3.9 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gunikhan 1720 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Jun 4 23:12:31 2018 HibernationDevice: RESUME=UUID=1a5d8668-3638-45e8-8ca9-921f550d0b82 InstallationDate: Installed on 2018-03-01 (95 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412) MachineType: Dell Inc. Vostro 1015 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic root=UUID=ee099561-bdde-44f5-b4cc-fbd3241f4922 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-43-generic N/A linux-backports-modules-4.13.0-43-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0TFXK9 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd11/26/2010:svnDellInc.:pnVostro1015:pvr:rvnDellInc.:rn0TFXK9:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Vostro 1015 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1714485] Re: Ubuntu 16.04: kdump fails with error "kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs.
Also available on artful-proposed. ** Tags added: verification-needed-artful verification-needed-xenial -- 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/1714485 Title: Ubuntu 16.04: kdump fails with error "kdump-tools[1532]: /etc/init.d /kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs. Status in The Ubuntu-power-systems project: Triaged Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Fix Committed Status in makedumpfile source package in Zesty: Won't Fix Status in makedumpfile source package in Artful: Fix Committed Status in makedumpfile source package in Bionic: Fix Released Bug description: == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-08-31 00:33:37 == ---Problem Description--- Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs. ---Steps to Reproduce--- 1. Install Ubuntu 16.04.03 with / as xfs. 2. Configure kdump. 3. trigger crash. Machine hangs after below log. Attaching console log. [ OK ] Reached target Network is Online. Starting Kernel crash dump capture service... Starting iSCSI initiator daemon (iscsid)... [ 12.263089] kdump-tools[1205]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator [ OK ] Started Kernel crash dump capture service. [ OK ] Started iSCSI initiator daemon (iscsid). Starting Login to default iSCSI targets... [ OK ] Started Login to default iSCSI targets. [ OK ] Reached target Remote File Systems (Pre). 4. After manual reboot /etc/default/kdump-tools is empty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1714485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773643] Re: [Clevo W253EUQ] Turn on bluetooth with Fn+F12 not working
Hello, My computer was provided with ubuntu12.04. the Bluetooth worked. With ubutu 14.04 Bluetooth doesn't work See this bug report for more information https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322068 kernel 4.4.0-22 work according report Best regards Battant -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773643 Title: [Clevo W253EUQ] Turn on bluetooth with Fn+F12 not working Status in linux package in Ubuntu: Incomplete Bug description: Hello, Since long time my [Clevo W253EUQ] Turn on bluetooth with Fn+F12 not working For more information see this link bellow https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322068 Could you help me to fix this bug ? Best regards Battant ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 27 13:21:46 2018 InstallationDate: Installed on 2018-04-29 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mparchet 1714 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-29 (28 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=9d6286f1-598b-46c8-a491-3e29fc732cb9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W240EU/W250EUQ/W270EUQ dmi.board.vendor: CLEVO CO. dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd11/11/2013:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W240EU/W250EUQ/W270EUQ dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO CO. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mparchet 1714 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-29 (28 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=9d6286f1-598b-46c8-a491-3e29fc732cb9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W240EU/W250EUQ/W270EUQ dmi.board.vendor: CLEVO CO. dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd11/11/2013:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name:
[Kernel-packages] [Bug 1714485] Re: Ubuntu 16.04: kdump fails with error "kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs.
Hello bugproxy, or anyone else affected, Accepted makedumpfile into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.3-2~16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: makedumpfile (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: makedumpfile (Ubuntu Artful) Status: New => Fix Committed -- 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/1714485 Title: Ubuntu 16.04: kdump fails with error "kdump-tools[1532]: /etc/init.d /kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs. Status in The Ubuntu-power-systems project: Triaged Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Fix Committed Status in makedumpfile source package in Zesty: Won't Fix Status in makedumpfile source package in Artful: Fix Committed Status in makedumpfile source package in Bionic: Fix Released Bug description: == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-08-31 00:33:37 == ---Problem Description--- Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs. ---Steps to Reproduce--- 1. Install Ubuntu 16.04.03 with / as xfs. 2. Configure kdump. 3. trigger crash. Machine hangs after below log. Attaching console log. [ OK ] Reached target Network is Online. Starting Kernel crash dump capture service... Starting iSCSI initiator daemon (iscsid)... [ 12.263089] kdump-tools[1205]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator [ OK ] Started Kernel crash dump capture service. [ OK ] Started iSCSI initiator daemon (iscsid). Starting Login to default iSCSI targets... [ OK ] Started Login to default iSCSI targets. [ OK ] Reached target Remote File Systems (Pre). 4. After manual reboot /etc/default/kdump-tools is empty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1714485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774225] Re: netns: unable to follow an interface that moves to another netns
I built one more test kernel using the Bionic master-next repository. I
confirmed the test kernel has the following two commits:
38e01b30563a ("dev: advertise the new ifindex when the netns iface changes")
c36ac8e23073 ("dev: always advertise the new nsid when the netns iface changes")
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1774225
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the
linux-image and linux-image-extra .deb packages.
• If the test kernel is 4.15(Bionic) or newer, you need to install the
linux-modules, linux-modules-extra and linux-image-unsigned .deb packages.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1774225
Title:
netns: unable to follow an interface that moves to another netns
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
The following upstream patches are missing (v4.16):
6621dd29eb9b ("dev: advertise the new nsid when the netns iface changes")
c36ac8e23073 ("dev: always advertise the new nsid when the netns iface
changes")
38e01b30563a ("dev: advertise the new ifindex when the netns iface changes")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6621dd29eb9b
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c36ac8e23073
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=38e01b30563a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774225/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1750021] Re: fails to dump with latest kpti fixes
I will verify this works with makedumpfile on -proposed.
** Changed in: makedumpfile (Ubuntu Artful)
Status: New => Fix Committed
** Changed in: makedumpfile (Ubuntu Xenial)
Status: New => Fix Committed
** Tags added: verification-needed-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/1750021
Title:
fails to dump with latest kpti fixes
Status in linux package in Ubuntu:
Fix Released
Status in makedumpfile package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Invalid
Status in makedumpfile source package in Xenial:
Fix Committed
Status in linux source package in Artful:
Fix Released
Status in makedumpfile source package in Artful:
Fix Committed
Status in linux source package in Bionic:
Fix Released
Status in makedumpfile source package in Bionic:
Fix Released
Bug description:
When commit 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4 ("mm/sparsemem:
Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y") was
backported, it broke the exporting of mem_section on vmcoreinfo.
makedumpfile will fail to dump in that case. Backporting a kernel fix
will make it work again, but that means that some kernel versions
won't be dumpable. A solution for makedumpfile should be done as well.
Cascardo.
break-fix: 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4
a0b1280368d1e91ab72f849ef095b4f07a39bbf1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750021/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768435] Re: aio-dio-extend-stat test in aio_dio_bugs failed on s390x
Fixed the testcases under aio_dio_bugs/src/ on autotest-client-tests repo. ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released ** Changed in: linux (Ubuntu) Status: Triaged => Invalid ** Changed in: linux (Ubuntu Xenial) Status: Triaged => Invalid ** Changed in: linux (Ubuntu Artful) Status: New => Invalid ** Changed in: linux (Ubuntu Bionic) 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/1768435 Title: aio-dio-extend-stat test in aio_dio_bugs failed on s390x Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux source package in Artful: Invalid Status in linux source package in Bionic: Invalid Bug description: It can be reproduced on zVM, zKVM and Ubuntu on LPAR This should not be considered as a regression, the test suite stopped on the first test in this test suite before. Steps: 1. git clone --depth=1 https://github.com/autotest/autotest-client-tests.git 2. make -C autotest-client-tests/aio_dio_bugs/src 3. sudo ./autotest-client-tests/aio_dio_bugs/src/aio-dio-extend-stat file Running 'apt-get install --yes --force-yes build-essential gcc' Reading package lists... Building dependency tree... Reading state information... build-essential is already the newest version (12.1ubuntu2). gcc is already the newest version (4:5.3.1-1ubuntu1). The following packages were automatically installed and are no longer required: linux-headers-4.4.0-121 linux-headers-4.4.0-121-generic linux-image-4.4.0-121-generic linux-image-extra-4.4.0-121-generic Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Running 'which gcc' /usr/bin/gcc Dependency libaio successfully built Running 'LD_LIBRARY_PATH=/home/ubuntu/autotest/client/deps/libaio/lib/ /home/ubuntu/autotest/client/tmp/aio_dio_bugs/src/aio-dio-extend-stat file' write of 1024 bytes @0 finished, expected filesize at least 1024, but got 0 Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/aio_dio_bugs/aio_dio_bugs.py", line 42, in run_once utils.system(var_ld_path + ' ' + cmd) File "/home/ubuntu/autotest/client/shared/utils.py", line 1232, in system verbose=verbose).exit_status File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run "Command returned non-zero exit status") CmdError: Command failed, rc=1, Command returned non-zero exit status * Command: LD_LIBRARY_PATH=/home/ubuntu/autotest/client/deps/libaio/lib/ /home/ubuntu/autotest/client/tmp/aio_dio_bugs/src/aio-dio-extend-stat file Exit status: 1 Duration: 0.10453414917 stdout: write of 1024 bytes @0 finished, expected filesize at least 1024, but got 0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-123-generic 4.4.0-123.147 ProcVersionSignature: Ubuntu 4.4.0-123.147-generic 4.4.128 Uname: Linux 4.4.0-123-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.16 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Wed May 2 02:24:25 2018 HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-123-generic N/A linux-backports-modules-4.4.0-123-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
[Kernel-packages] [Bug 1730895] Re: aio-dio-invalidate-failure test failed with event res -22 on s390x
Fixed the testcases under aio_dio_bugs/src/ on autotest-client-tests
repo.
** No longer affects: linux (Ubuntu)
** No longer affects: linux (Ubuntu Xenial)
** No longer affects: linux (Ubuntu Artful)
** No longer affects: linux (Ubuntu Bionic)
** Changed in: ubuntu-kernel-tests
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730895
Title:
aio-dio-invalidate-failure test failed with event res -22 on s390x
Status in ubuntu-kernel-tests:
Fix Released
Bug description:
This bug is for tracking purpose, this is not a regression for current
cycle as this issue exists for a long time.
It can be reproduced on zVM, zKVM and Ubuntu on LPAR
Steps:
1. git clone --depth=1 https://github.com/autotest/autotest-client-tests.git
2. make -C autotest-client-tests/aio_dio_bugs/src
3. sudo ./autotest-client-tests/aio_dio_bugs/src/aio-dio-invalidate-failure
poo
Result:
event res -22
From the code itself, it's expecting a -EIO return value:
if (event.res == -EIO) {
printf("invalidation returned -EIO, OK\n");
exit(0);
}
The actual return value is -22, which I think is -EINVAL
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-100-generic 4.4.0-100.123
ProcVersionSignature: Ubuntu 4.4.0-100.123-generic 4.4.95
Uname: Linux 4.4.0-100-generic s390x
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
CurrentDmesg:
Date: Wed Nov 8 01:57:40 2017
HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9
crashkernel=196M BOOT_IMAGE=0
RelatedPackageVersions:
linux-restricted-modules-4.4.0-100-generic N/A
linux-backports-modules-4.4.0-100-generic N/A
linux-firmware 1.157.13
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1730895/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751243] Re: ubuntu_unionmount_overlayfs_suite failed with Bionic kernel
** Also affects: ubuntu-kernel-tests 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/1751243 Title: ubuntu_unionmount_overlayfs_suite failed with Bionic kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: In Progress Bug description: This issue can be found on different architectures of the Bionic kernel. Steps: 1. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b master-next 2. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest 3. rm -fr autotest/client/tests 4. ln -sf ~/autotest-client-tests autotest/client/tests 5. AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_qrt_kernel_security/control Result: * Command: ./run --ov Exit status: 1 Duration: 0.465664863586 stdout: *** *** ./run --ov --ts=0 open-plain *** TEST open-plain.py:10: Open O_RDONLY /mnt/a/foo100: File unexpectedly on union layer ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic s390x NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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': 'aplay' ApportVersion: 2.20.8-0ubuntu10 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Fri Feb 23 09:57:36 2018 HibernationDevice: RESUME=UUID=caaee9b2-6bc1-4c8e-b26c-69038c092091 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=c7d7bbcb-a039-4ead-abfe-7672dea0add4 crashkernel=196M RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.171 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1751243/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768430] Re: aio-dio-subblock-eof-read test in aio_dio_bugs failed on s390x
Fixed the testcases under aio_dio_bugs/src/ on autotest-client-tests repo. ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Xenial) Status: Triaged => Invalid ** Changed in: linux (Ubuntu Artful) Status: New => Invalid ** Changed in: linux (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Triaged => 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/1768430 Title: aio-dio-subblock-eof-read test in aio_dio_bugs failed on s390x Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux source package in Artful: Invalid Status in linux source package in Bionic: Invalid Bug description: It can be reproduced on zVM, zKVM and Ubuntu on LPAR This should not be considered as a regression, the test suite stopped on the first test in this test suite before. Steps: 1. git clone --depth=1 https://github.com/autotest/autotest-client-tests.git 2. make -C autotest-client-tests/aio_dio_bugs/src 3. sudo ./autotest-client-tests/aio_dio_bugs/src/aio-dio-subblock-eof-read eoftest Running 'apt-get install --yes --force-yes build-essential gcc' Reading package lists... Building dependency tree... Reading state information... build-essential is already the newest version (12.1ubuntu2). gcc is already the newest version (4:5.3.1-1ubuntu1). The following packages were automatically installed and are no longer required: linux-headers-4.4.0-121 linux-headers-4.4.0-121-generic linux-image-4.4.0-121-generic linux-image-extra-4.4.0-121-generic Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Running 'which gcc' /usr/bin/gcc Dependency libaio successfully built Running 'LD_LIBRARY_PATH=/home/ubuntu/autotest/client/deps/libaio/lib/ /home/ubuntu/autotest/client/tmp/aio_dio_bugs/src/aio-dio-subblock-eof-read eoftest' buffered read returned -1, should be 300 Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/aio_dio_bugs/aio_dio_bugs.py", line 42, in run_once utils.system(var_ld_path + ' ' + cmd) File "/home/ubuntu/autotest/client/shared/utils.py", line 1232, in system verbose=verbose).exit_status File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run "Command returned non-zero exit status") CmdError: Command failed, rc=1, Command returned non-zero exit status * Command: LD_LIBRARY_PATH=/home/ubuntu/autotest/client/deps/libaio/lib/ /home/ubuntu/autotest/client/tmp/aio_dio_bugs/src/aio-dio-subblock-eof- read eoftest Exit status: 1 Duration: 0.00215792655945 stdout: buffered read returned -1, should be 300 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-123-generic 4.4.0-123.147 ProcVersionSignature: Ubuntu 4.4.0-123.147-generic 4.4.128 Uname: Linux 4.4.0-123-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.16 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Wed May 2 02:21:12 2018 HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-123-generic N/A linux-backports-modules-4.4.0-123-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade
[Kernel-packages] [Bug 1772505] Re: [18.04] [regression testing] ubuntu_fan_smoke_tests failing on s390x
Fixed the ubuntu_fan_smoke_test/smoke_test_old.sh testcase from autotest-client-tests repo. ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: ubuntu-kernel-tests Importance: Undecided => Medium ** Changed in: ubuntu-kernel-tests Importance: Medium => High ** Changed in: ubuntu-kernel-tests Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772505 Title: [18.04] [regression testing] ubuntu_fan_smoke_tests failing on s390x Status in ubuntu-kernel-tests: Fix Released Bug description: see logs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1772505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775044] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775044 Title: continuously freeze the system Status in linux package in Ubuntu: Confirmed Bug description: I am unable to use the system properly because it is continuously freezing, please fix the problems ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-43-generic 4.13.0-43.48 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic i686 ApportVersion: 2.20.7-0ubuntu3.9 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gunikhan 1720 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Jun 4 23:12:31 2018 HibernationDevice: RESUME=UUID=1a5d8668-3638-45e8-8ca9-921f550d0b82 InstallationDate: Installed on 2018-03-01 (95 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412) MachineType: Dell Inc. Vostro 1015 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic root=UUID=ee099561-bdde-44f5-b4cc-fbd3241f4922 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-43-generic N/A linux-backports-modules-4.13.0-43-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0TFXK9 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd11/26/2010:svnDellInc.:pnVostro1015:pvr:rvnDellInc.:rn0TFXK9:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Vostro 1015 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775044] [NEW] continuously freeze the system
Public bug reported: I am unable to use the system properly because it is continuously freezing, please fix the problems ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-43-generic 4.13.0-43.48 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic i686 ApportVersion: 2.20.7-0ubuntu3.9 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gunikhan 1720 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Jun 4 23:12:31 2018 HibernationDevice: RESUME=UUID=1a5d8668-3638-45e8-8ca9-921f550d0b82 InstallationDate: Installed on 2018-03-01 (95 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412) MachineType: Dell Inc. Vostro 1015 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic root=UUID=ee099561-bdde-44f5-b4cc-fbd3241f4922 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-43-generic N/A linux-backports-modules-4.13.0-43-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0TFXK9 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd11/26/2010:svnDellInc.:pnVostro1015:pvr:rvnDellInc.:rn0TFXK9:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Vostro 1015 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug artful i386 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775044 Title: continuously freeze the system Status in linux package in Ubuntu: Confirmed Bug description: I am unable to use the system properly because it is continuously freezing, please fix the problems ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-43-generic 4.13.0-43.48 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic i686 ApportVersion: 2.20.7-0ubuntu3.9 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gunikhan 1720 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Jun 4 23:12:31 2018 HibernationDevice: RESUME=UUID=1a5d8668-3638-45e8-8ca9-921f550d0b82 InstallationDate: Installed on 2018-03-01 (95 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412) MachineType: Dell Inc. Vostro 1015 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic root=UUID=ee099561-bdde-44f5-b4cc-fbd3241f4922 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-43-generic N/A linux-backports-modules-4.13.0-43-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0TFXK9 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd11/26/2010:svnDellInc.:pnVostro1015:pvr:rvnDellInc.:rn0TFXK9:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Vostro 1015 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765007] Re: Xenial update to 4.4.127 stable release
** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765007 Title: Xenial update to 4.4.127 stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.127 upstream stable stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.127 stable release shall be applied: * Linux 4.4.127 * Revert "ip6_vti: adjust vti mtu according to mtu of lower device" * net: cavium: liquidio: fix up "Avoid dma_unmap_single on uninitialized ndata" * spi: davinci: fix up dma_mapping_error() incorrect patch * Revert "mtip32xx: use runtime tag to initialize command header" * Revert "cpufreq: Fix governor module removal race" * Revert "ARM: dts: omap3-n900: Fix the audio CODEC's reset pin" * Revert "ARM: dts: am335x-pepper: Fix the audio CODEC's reset pin" * Revert "PCI/MSI: Stop disabling MSI/MSI-X in pci_device_shutdown()" * nospec: Kill array_index_nospec_mask_check() * nospec: Move array_index_nospec() parameter checking into separate macro * net: hns: Fix ethtool private flags * md/raid10: reset the 'first' at the end of loop * ARM: dts: am57xx-beagle-x15-common: Add overide powerhold property * ARM: dts: dra7: Add power hold and power controller properties to palmas * Documentation: pinctrl: palmas: Add ti,palmas-powerhold-override property definition * vt: change SGR 21 to follow the standards * Input: i8042 - enable MUX on Sony VAIO VGN-CS series to fix touchpad * Input: i8042 - add Lenovo ThinkPad L460 to i8042 reset list * staging: comedi: ni_mio_common: ack ai fifo error interrupts. * fs/proc: Stop trying to report thread stacks * crypto: x86/cast5-avx - fix ECB encryption when long sg follows short one * crypto: ahash - Fix early termination in hash walk * parport_pc: Add support for WCH CH382L PCI-E single parallel port card. * media: usbtv: prevent double free in error case * mei: remove dev_err message on an unsupported ioctl * USB: serial: cp210x: add ELDAT Easywave RX09 id * USB: serial: ftdi_sio: add support for Harman FirmwareHubEmulator * USB: serial: ftdi_sio: add RT Systems VX-8 cable * usb: dwc2: Improve gadget state disconnection handling * scsi: virtio_scsi: always read VPD pages for multiqueue too * llist: clang: introduce member_address_is_nonnull() * Bluetooth: Fix missing encryption refresh on Security Request * netfilter: x_tables: add and use xt_check_proc_name * netfilter: bridge: ebt_among: add more missing match size checks * xfrm: Refuse to insert 32 bit userspace socket policies on 64 bit systems * net: xfrm: use preempt-safe this_cpu_read() in ipcomp_alloc_tfms() * RDMA/ucma: Introduce safer rdma_addr_size() variants * RDMA/ucma: Don't allow join attempts for unsupported AF family * RDMA/ucma: Check that device exists prior to accessing it * RDMA/ucma: Check that device is connected prior to access it * RDMA/ucma: Ensure that CM_ID exists prior to access it * RDMA/ucma: Fix use-after-free access in ucma_close * RDMA/ucma: Check AF family prior resolving address * xfrm_user: uncoditionally validate esn replay attribute struct * arm64: avoid overflow in VA_START and PAGE_OFFSET * selinux: Remove redundant check for unknown labeling behavior * netfilter: ctnetlink: Make some parameters integer to avoid enum mismatch * tty: provide tty_name() even without CONFIG_TTY * audit: add tty field to LOGIN event * frv: declare jiffies to be located in the .data section * jiffies.h: declare jiffies and jiffies_64 with cacheline_aligned_in_smp * fs: compat: Remove warning from COMPATIBLE_IOCTL * selinux: Remove unnecessary check of array base in selinux_set_mapping() * cpumask: Add helper cpumask_available() * genirq: Use cpumask_available() for check of cpumask variable * netfilter: nf_nat_h323: fix logical-not-parentheses warning * Input: mousedev - fix implicit conversion warning * dm ioctl: remove double parentheses * PCI: Make PCI_ROM_ADDRESS_MASK a 32-bit constant * writeback: fix the wrong congested
[Kernel-packages] [Bug 1768103] Re: Lancer A0 Asic HBA's won't boot with 18.04
Yes, I've asked Vinay to test it again. thank you Laurie -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768103 Title: Lancer A0 Asic HBA's won't boot with 18.04 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: We have discovered that an early asic model (A0) of our 16/32GB HBA's doesn't boot with the lpfc driver in Ubuntu 18.04. After further review and discussion, this has been deemed a low risk issue since early A0 HBA's were only ever shipped to OEMs for test purposes. These cards were never shipped to end customers. We have been working to replace those cards whenever we discover them. We'll leave it up to Canonical to decide whether they want to pull this in this single patch to an 18.04 subsequent update. Symptom: Ubuntu 18.04 with lpfc driver 12.0.0.0 they can't see LPe16002-M6 but can see LPe16002B-M6 Resolution: new lpfc driver patch update. scsi: lpfc: Fix WQ/CQ creation for older asic's. https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=4.18/scsi-queue=83fae8ca4ae09403bfb99542f1aaa292c06cb111 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774883] Re: GPF using CIFS and ACQ107 under heavy use
it was a fresh install. I update kernel and still GPF general protection fault: [#1] SMP PTI Jun 4 21:53:59 klimt kernel: [ 435.469311] Modules linked in: md4 nls_utf8 cifs ccm fscache binfmt_misc snd_hda_codec_hdmi intel_rapl nfit x86_pkg_temp_thermal intel_powerclamp coretemp arc4 iwlmvm mac80211 kvm_intel iwlwifi kvm snd_hda_codec_realtek irqbypass snd_hda_codec_generic cfg80211 intel_cstate mxm_wmi intel_wmi_thunderbolt snd_hda_intel snd_hda_codec intel_rapl_perf snd_hda_core snd_hwdep snd_pcm snd_timer snd mei_me soundcore mei shpchp ioatdma wmi mac_hid nvidia_uvm(POE) sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel Jun 4 21:53:59 klimt kernel: [ 435.484304] pcbc raid1 drm_kms_helper syscopyarea aesni_intel sysfillrect sysimgblt aes_x86_64 fb_sys_fops crypto_simd cryptd drm glue_helper ipmi_devintf igb ipmi_msghandler e1000e atlantic dca ahci i2c_algo_bit libahci Jun 4 21:53:59 klimt kernel: [ 435.488138] CPU: 12 PID: 6203 Comm: ffprobe Tainted: P OE 4.17.0-041700-generic #201806032231 Jun 4 21:53:59 klimt kernel: [ 435.490048] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X299 Professional Gaming i9 XE, BIOS P1.40 02/26/2018 Jun 4 21:53:59 klimt kernel: [ 435.492252] RIP: 0010:prefetch_freepointer+0x14/0x30 Jun 4 21:53:59 klimt kernel: [ 435.493227] RSP: 0018:bdefcc727b78 EFLAGS: 00010202 Jun 4 21:53:59 klimt kernel: [ 435.494235] RAX: RBX: 1e82c610471cb943 RCX: 0025 Jun 4 21:53:59 klimt kernel: [ 435.495562] RDX: 0024 RSI: 1e82c610471cb943 RDI: 98960eb76400 Jun 4 21:53:59 klimt kernel: [ 435.496889] RBP: bdefcc727b78 R08: ddefbf718020 R09: Jun 4 21:53:59 klimt kernel: [ 435.498255] R10: R11: R12: 015004c0 Jun 4 21:53:59 klimt kernel: [ 435.499582] R13: 9895d7d8a000 R14: 98960eb76400 R15: 98961ed7bd80 Jun 4 21:53:59 klimt kernel: [ 435.500910] FS: 7f466cd2d500() GS:98961f30() knlGS: Jun 4 21:53:59 klimt kernel: [ 435.557736] CS: 0010 DS: ES: CR0: 80050033 Jun 4 21:53:59 klimt kernel: [ 435.584068] CR2: 7f466a3485c0 CR3: 00200d00e005 CR4: 003606e0 Jun 4 21:53:59 klimt kernel: [ 435.609964] DR0: DR1: DR2: Jun 4 21:53:59 klimt kernel: [ 435.635179] DR3: DR6: fffe0ff0 DR7: 0400 Jun 4 21:53:59 klimt kernel: [ 435.659628] Call Trace: Jun 4 21:53:59 klimt kernel: [ 435.683234] kmem_cache_alloc_node+0x13c/0x1f0 Jun 4 21:53:59 klimt kernel: [ 435.706624] ? __alloc_skb+0x5b/0x1e0 Jun 4 21:53:59 klimt kernel: [ 435.729475] __alloc_skb+0x5b/0x1e0 Jun 4 21:53:59 klimt kernel: [ 435.751636] alloc_skb_with_frags+0x67/0x1c0 Jun 4 21:53:59 klimt kernel: [ 435.773434] ? wait_woken+0x80/0x80 Jun 4 21:53:59 klimt kernel: [ 435.794619] sock_alloc_send_pskb+0x1f2/0x220 Jun 4 21:53:59 klimt kernel: [ 435.815454] ? _cond_resched+0x19/0x40 Jun 4 21:53:59 klimt kernel: [ 435.835587] ? wait_for_unix_gc+0x37/0xb0 Jun 4 21:53:59 klimt kernel: [ 435.855156] unix_stream_sendmsg+0x29d/0x3b0 Jun 4 21:53:59 klimt kernel: [ 435.874290] sock_sendmsg+0x3e/0x50 Jun 4 21:53:59 klimt kernel: [ 435.892743] sock_write_iter+0x8c/0xf0 Jun 4 21:53:59 klimt kernel: [ 435.910656] __vfs_write+0xfe/0x170 Jun 4 21:53:59 klimt kernel: [ 435.928048] vfs_write+0xb1/0x1a0 Jun 4 21:53:59 klimt kernel: [ 435.944928] ksys_write+0x55/0xc0 Jun 4 21:53:59 klimt kernel: [ 435.961233] __x64_sys_write+0x1a/0x20 Jun 4 21:53:59 klimt kernel: [ 435.977030] do_syscall_64+0x5a/0x120 Jun 4 21:53:59 klimt kernel: [ 435.992487] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 4 21:53:59 klimt kernel: [ 436.008246] RIP: 0033:0x7f46697d4154 Jun 4 21:53:59 klimt kernel: [ 436.023716] RSP: 002b:7ffcb0736f48 EFLAGS: 0246 ORIG_RAX: 0001 Jun 4 21:53:59 klimt kernel: [ 436.055572] RAX: ffda RBX: 0029 RCX: 7f46697d4154 Jun 4 21:53:59 klimt kernel: [ 436.072479] RDX: 0029 RSI: 7ffcb0737c34 RDI: 0002 Jun 4 21:53:59 klimt kernel: [ 436.089401] RBP: 7ffcb0737c34 R08: 0029 R09: 0029 Jun 4 21:53:59 klimt kernel: [ 436.105931] R10: ffd7 R11: 0246 R12: 7f4669ab0680 Jun 4 21:53:59 klimt kernel: [ 436.122081] R13: 0029 R14: 7f4669aab760 R15: 0029 Jun 4 21:53:59 klimt kernel: [ 436.137928] Code: 39 50 9c e8 b2 84 e9 ff eb 91 0f 1f 00 66 2e 0f 1f 84 00 00 00 00 00 0f
[Kernel-packages] [Bug 1774225] Re: netns: unable to follow an interface that moves to another netns
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1774225
Title:
netns: unable to follow an interface that moves to another netns
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
The following upstream patches are missing (v4.16):
6621dd29eb9b ("dev: advertise the new nsid when the netns iface changes")
c36ac8e23073 ("dev: always advertise the new nsid when the netns iface
changes")
38e01b30563a ("dev: advertise the new ifindex when the netns iface changes")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6621dd29eb9b
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c36ac8e23073
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=38e01b30563a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774225/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768103] Re: Lancer A0 Asic HBA's won't boot with 18.04
I built a test kernel with the following two patches: scsi: lpfc: Fix WQ/CQ creation for older asic's. scsi: lpfc: Fix 16gb hbas failing cq create. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1768103 Can you test this kernel and see if it resolves this bug? Note about installing test kernels: • If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages. • If the test kernel is 4.15(Bionic) or newer, you need to install the linux-image-unsigned, linux-modules and linux-modules-extra .deb packages. Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768103 Title: Lancer A0 Asic HBA's won't boot with 18.04 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: We have discovered that an early asic model (A0) of our 16/32GB HBA's doesn't boot with the lpfc driver in Ubuntu 18.04. After further review and discussion, this has been deemed a low risk issue since early A0 HBA's were only ever shipped to OEMs for test purposes. These cards were never shipped to end customers. We have been working to replace those cards whenever we discover them. We'll leave it up to Canonical to decide whether they want to pull this in this single patch to an 18.04 subsequent update. Symptom: Ubuntu 18.04 with lpfc driver 12.0.0.0 they can't see LPe16002-M6 but can see LPe16002B-M6 Resolution: new lpfc driver patch update. scsi: lpfc: Fix WQ/CQ creation for older asic's. https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=4.18/scsi-queue=83fae8ca4ae09403bfb99542f1aaa292c06cb111 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free
> So they should not be operating on the same sock concurrently. But, of course, all this is caused by bugs, so yes it's certainly possible a bug allowed what you said to happen, but you'll need to dig in deeper to find where such a bug is (if any), since the locking design is correct as far as I can tell. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1711407 Title: unregister_netdevice: waiting for lo to become free Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Zesty: Won't Fix Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Bug description: This is a "continuation" of bug 1403152, as that bug has been marked "fix released" and recent reports of failure may (or may not) be a new bug. Any further reports of the problem should please be reported here instead of that bug. -- [Impact] When shutting down and starting containers the container network namespace may experience a dst reference counting leak which results in this message repeated in the logs: unregister_netdevice: waiting for lo to become free. Usage count = 1 This can cause issues when trying to create net network namespace and thus block a user from creating new containers. [Test Case] See comment 16, reproducer provided at https://github.com/fho/docker- samba-loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free
> is it possibility that sk->sk_dst_cache is overwritten? maybe ;-) > like in __sk_dst_check, > when tcp timer tries to resend a packet, at the same time, tcp_close is called tcp_close() locks the sock; tcp_retransmit_timer() is also called with the sock locked. So they should not be operating on the same sock concurrently. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1711407 Title: unregister_netdevice: waiting for lo to become free Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Zesty: Won't Fix Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Bug description: This is a "continuation" of bug 1403152, as that bug has been marked "fix released" and recent reports of failure may (or may not) be a new bug. Any further reports of the problem should please be reported here instead of that bug. -- [Impact] When shutting down and starting containers the container network namespace may experience a dst reference counting leak which results in this message repeated in the logs: unregister_netdevice: waiting for lo to become free. Usage count = 1 This can cause issues when trying to create net network namespace and thus block a user from creating new containers. [Test Case] See comment 16, reproducer provided at https://github.com/fho/docker- samba-loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29
Is there any update on this issue? Hibernation works with kernel 4.10 but I can't keep using that forever... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1743094 Title: [regression] hibernation (freezes on resume) since 4.13.0-25.29 Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: After hibernating the system and than resuming it the system reboots notifying that it is resuming and than stops/freezes. The system does not respond to anything (no tty's other notifying textg are available). After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep functions as proposed. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jb 1717 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478 InstallationDate: Installed on 2017-12-10 (34 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124 MachineType: Acer Aspire S3-391 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-26-generic N/A linux-backports-modules-4.13.0-26-generic N/A linux-firmware 1.157.14 Tags: sylvia Uname: Linux 4.13.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/31/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Hummingbird2 dmi.board.vendor: Acer dmi.board.version: V2.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10: dmi.product.family: ChiefRiver System dmi.product.name: Aspire S3-391 dmi.product.version: V2.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774875] Re: Internal laptop display defaults to low refresh rate
*** This bug is a duplicate of bug 1773520 *** https://bugs.launchpad.net/bugs/1773520 ** This bug has been marked a duplicate of bug 1773520 After update to 4.13-43 Intel Graphics are Laggy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774875 Title: Internal laptop display defaults to low refresh rate Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Bug description: It appears that ever since kernel ~4.14, there was a bug in i915 DRM that caused the internal laptop displays connected by eDP to default to 40 Hz screen refresh rate. Affected Ubuntu release: 18.04 Kernel package version: 4.15.0-22.24 What you expected to happen: The refresh rate has a sane default setting What happened instead: The refresh rate defaults to 40 Hz Upstream bug report: https://bugs.freedesktop.org/show_bug.cgi?id=103497 This has already been fixed in drm-tip: https://cgit.freedesktop.org/drm-tip/commit/?id=d93fa1b47b8fcd149b5091f18385304f402a8e15 I do confirm that the latest daily build cod/tip/drm-tip/2018-06-03 (8fdb62e0511e81fa935059c274a2457361fdb679) of drm-tip kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/ indeed fixes this issue for me. Known workarounds: The user can force the display to use other refresh rates close to 60 Hz (59,96 works quite well in my case) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 Uname: Linux 4.17.0-994-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 3 16:53:20 2018 InstallationDate: Installed on 2018-06-03 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774471] Comment bridged from LTC Bugzilla
--- Comment From vajai...@in.ibm.com 2018-06-04 11:22 EDT--- (In reply to comment #6) > I built a test kernel with the six commits posted in the bug description. > The test kernel can be downloaded from: > http://kernel.ubuntu.com/~jsalisbury/lp1774471 > > Can you test this kernel and see if it resolves this bug? > > Note about installing test kernels: > ? If the test kernel is prior to 4.15(Bionic) you need to install the > linux-image and linux-image-extra .deb packages. > ? If the test kernel is 4.15(Bionic) or newer, you need to install the > linux-modules, linux-modules-extra and linux-image-unsigned .deb packages. > > Thanks in advance! Verified the cxl kernel patches and ran quick regression tests which passed. Please mark the bug as 'Veritied' -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774471 Title: Various fixes for CXL kernel module Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: ---Problem Description--- Couple of CXL patches need to be merged to Ubuntu 18.04.1 kernel source tree. They fix various issues found after the 18.04 kernel freeze: 401dca8cbd14 cxl: Set the PBCQ Tunnel BAR register when enabling capi mode 497a0790e2c6 cxl: Report the tunneled operations status ad7b4e8022b9 cxl: Fix possible deadlock when processing page faults from cxllib 02b63b420223 cxl: Remove function write_timebase_ctrl_psl9() for PSL9 cxl: Configure PSL to not use APC virtual machines : http://patchwork.ozlabs.org/patch/899062/ cxl: Disable prefault_mode in Radix mode : http://patchwork.ozlabs.org/patch/916159/ ---uname output--- 4.15.0-12-generic ---Additional Hardware Info--- a compatible capi FPGA adapter Machine Type = Boston-LC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1774471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775018] Re: Fix for openssl 1.0.2 backport
** Package changed: linux (Ubuntu) => openssl (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/1775018 Title: Fix for openssl 1.0.2 backport Status in openssl package in Ubuntu: New Bug description: This is a fix for this feature's backport to openssl 1.0.2 ( 1.1.0 and upstream code are not affected ). Original LP ticket : https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1743750 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1775018/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774964] Re: [LTCTest][OPAL][OP910.20] WARNING: CPU: 97 PID: 11965 at /build/linux-0zaMZw/linux-4.15.0/kernel/sched/core.c:1189 set_task_cpu+0x240/0x250
** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Tags added: p9 triage-g ** Changed in: ubuntu-power-systems Importance: Undecided => High ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774964 Title: [LTCTest][OPAL][OP910.20] WARNING: CPU: 97 PID: 11965 at /build/linux- 0zaMZw/linux-4.15.0/kernel/sched/core.c:1189 set_task_cpu+0x240/0x250 Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: == Comment: #0 - PAVAMAN SUBRAMANIYAM <> - 2018-04-25 01:59:10 == ---Problem Description--- WARNING: CPU: 97 PID: 11965 at /build/linux-0zaMZw/linux-4.15.0/kernel/sched/core.c:1189 set_task_cpu+0x240/0x250 ---uname output--- Linux ltc-wspoon8 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = P9 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install a P9 Open Power Hardware with the latest OP910.20 Firmware images. root@witherspoon:~# cat /etc/os-release ID="openbmc-phosphor" NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)" VERSION="ibm-v2.0" VERSION_ID="ibm-v2.0-0-r46-0-gbed584c" PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) ibm-v2.0" BUILD_ID="ibm-v2.0-0-r46" root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION open-power-witherspoon-v1.21.2-251-ge2e9363-dirty buildroot-2017.11-5-g65679be skiboot-v5.10.3-op910-1-p240231e hostboot-0aa5bed linux-4.14.24-openpower1-p3e84190 petitboot-v1.6.6-pd7224b4 machine-xml-4af occ-8c5b727 hostboot-binaries-9bd4056 capp-ucode-p9-dd2-v3 sbe-7e02c23 Then we have installed the Ubuntu 18.04 OS on the machine. root@ltc-wspoon8:~# uname -a Linux ltc-wspoon8 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@ltc-wspoon8:~# cat /etc/os-release NAME="Ubuntu" VERSION="18.04 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic root@ltc-wspoon8:~# cat /proc/cpuinfo | tail cpu : POWER9, altivec supported clock : 2300.00MHz revision: 2.1 (pvr 004e 1201) timebase: 51200 platform: PowerNV model : 8335-GTC machine : PowerNV 8335-GTC firmware: OPAL MMU : Radix root@ltc-wspoon8:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-20-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-20-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=a2cd572c-9047-4f0a-843b-6996fae3e999 ro quiet splash nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@ltc-wspoon8:~# ps -ef | grep opal root880 2 0 01:25 ?00:00:00 [kopald] root 3604 1 2 01:25 ?00:00:03 /usr/sbin/opal-prd root 4858 4278 0 01:28 pts/000:00:00 grep --color=auto opal root@ltc-wspoon8:~# service opal-prd status ? opal-prd.service - OPAL PRD daemon Loaded: loaded (/lib/systemd/system/opal-prd.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2018-04-25 01:25:48 CDT; 2min 43s ago Docs: man:opal-prd(8) Main PID: 3604 (opal-prd) Tasks: 1 (limit: 22118) CGroup: /system.slice/opal-prd.service ??3604 /usr/sbin/opal-prd Apr 25 01:25:52 ltc-wspoon8 opal-prd[3604]: IMAGE: hbrt_init complete, version 0290 Apr 25 01:25:52 ltc-wspoon8 opal-prd[3604]: HBRT: hservices_init done Apr 25 01:25:52 ltc-wspoon8 opal-prd[3604]: HBRT: calling enable_attns Apr 25 01:25:52 ltc-wspoon8 opal-prd[3604]: HBRT: ATTN_SLOW:I>>>ATTN_RT::enableAttns Apr 25 01:25:52 ltc-wspoon8 opal-prd[3604]: HBRT: ATTN_SLOW:I>Service::enableAttns() enter Apr 25 01:25:52 ltc-wspoon8 opal-prd[3604]: HBRT: ATTN_SLOW:I>Service::enableAttns() exit Apr 25 01:25:52 ltc-wspoon8 opal-prd[3604]: HBRT: ATTN_SLOW:I>< CR: 24002882 XER:
[Kernel-packages] [Bug 1775018] s390x-fix-aes-gcm-tls
Default Comment by Bridge ** Attachment added: "s390x-fix-aes-gcm-tls" https://bugs.launchpad.net/bugs/1775018/+attachment/5148593/+files/s390x-fix-aes-gcm-tls.patch ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775018 Title: Fix for openssl 1.0.2 backport Status in linux package in Ubuntu: New Bug description: This is a fix for this feature's backport to openssl 1.0.2 ( 1.1.0 and upstream code are not affected ). Original LP ticket : https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1743750 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775018/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774845] Re: [Dell Inspiron 1525] Booting takes a couple more minutes than normal
Dear Christopher, as I posted "upstream" (https://bugs.freedesktop.org/show_bug.cgi?id=93782), both - Latest ubuntu drm-tip kernel (as of June 3rd) - applying the patch suggested C#12 of the upstream post (on the source I already had of 4.17 rc3 drm-tip) were NOT successful fixing the bug. If you look at C#11 of my initial post upstream (https://bugs.freedesktop.org/show_bug.cgi?id=106422#c11), Jim Rees implies that bissecting has already been done and that it boils down to commit: eaf0 "Roll out the helper nonblock tracking" This commit is supposed to be "too difficult" to revert starting from kernel 4.14 (probably due to major rewrites of parts of the drm stack). You are right, things can get worse... and they did: indeed the "bug" was only spitting some messages in the system log prior to the change, and is now triggering several time outs. But for the moment, I'll have to take my chances that this tv-out issue doesn't get worse, since I really don't have time to do a lot more tests. Also, I don't have permanent access to this hardware (it's not mine), and that doesn't help! ** Bug watch added: freedesktop.org Bugzilla #93782 https://bugs.freedesktop.org/show_bug.cgi?id=93782 ** Bug watch added: freedesktop.org Bugzilla #106422 https://bugs.freedesktop.org/show_bug.cgi?id=106422 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774845 Title: [Dell Inspiron 1525] Booting takes a couple more minutes than normal Status in linux package in Ubuntu: Incomplete Bug description: Booting into a installed environment takes a few more minutes than normal. WORKAROUND: Use kernel parameter: video=SVIDEO-1:d --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rose 1084 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=f871d5a4-72c8-4c2b-b9a2-17f18a8ae520 InstallationDate: Installed on 2018-05-07 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 1525 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=903c6b4d-dc72-4b1e-ad11-fc1ac80687ea ro quiet splash 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 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/27/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0U990C dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd06/27/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C: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/1774845/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775018] [NEW] Fix for openssl 1.0.2 backport
You have been subscribed to a public bug: This is a fix for this feature's backport to openssl 1.0.2 ( 1.1.0 and upstream code are not affected ). Original LP ticket : https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1743750 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-168542 severity-high targetmilestone-inin16044 -- Fix for openssl 1.0.2 backport https://bugs.launchpad.net/bugs/1775018 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746299] Re: update makedumpfile tool version to v1.6.3
Hello bugproxy, or anyone else affected, Accepted makedumpfile into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.3-2~16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: makedumpfile (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed-xenial -- 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/1746299 Title: update makedumpfile tool version to v1.6.3 Status in The Ubuntu-power-systems project: In Progress Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Fix Committed Status in makedumpfile source package in Artful: Fix Committed Status in makedumpfile source package in Bionic: Fix Released Bug description: [Impact] New upstream kernel versions, as those in linux-hwe package, require a newer makedumpfile to be supported. Otherwise, all copies fallback to copying the entire memory. [Test case] kdump-tools has been installed, system rebooted, then crash trigerred and verified that a small dump file was present on /var/crash/. Tested on amd64 and ppc64le. [Regression potential] Many other bug fixes have been included in the latest version of the package. The changes are supposed to fix these bugs, and have been tested as well. However, as the total of changes is not trivial, there is impact of regression that has been minimized by the tests done. Regression potential of not supporting older kernels has been tested with the kernels shipped on xenial and artful as well. == Comment: #0 - Hari Krishna Bathini - 2018-01-30 10:46:53 == ---Problem Description--- update makedumpfile to latest version v1.6.3 that officially supports up to kernel version 4.14.8. Since makedumpfile is inherently backward compatible, this would not break existing functionality.. Contact Information = hbath...@in.ibm.com ---uname output--- na Machine Type = na ---Debugger--- A debugger is not configured ---Steps to Reproduce--- makedumpfile reports ""The kernel version is not supported" while generating vmcore Also, there is a possibility of bogus address translations in makedumpfile tool with missing upstream patches. Can't be so sure without an exhaustive testing. Instead, it would be a good idea to go with the version which officially supports the kernel version in question. Userspace tool common name: makedumpfile The userspace tool has the following bit modes: 64-bit Userspace rpm: makedumpfile Userspace tool obtained from project website: na *Additional Instructions for hbath...@in.ibm.com: -Attach ltrace and strace of userspace application. == Comment: #1 - Hari Krishna Bathini - 2018-01-30 10:49:13 == With kernel version updated to 4.13.0, please update makedumpfile tool version to 1.6.3 which officially supports up to kernel version 4.14.8 [1]. Thanks Hari [1] http://lists.infradead.org/pipermail/kexec/2018-January/019853.html This needs to be tagged for both 16.04.4 & 18.04 releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1746299/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774793] Re: touchpad not detected
Thank you Joseph for your help, I'm going to start with the mailing list. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774793 Title: touchpad not detected Status in linux package in Ubuntu: Triaged Bug description: I'm unable to get the name of the touchpad on system. And, I'm unable to copy text as well to support investigation on this bug-report. The following bug-report was the closest to my issue. However, I tried to use the patched kernel (mainline 4.17.0-1-generic) but it didn't fix my problem. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728244 I tried updating the GRUB_CMDLINE_LINUX_DEFAULT wit i8042.reset and i8042.nomux, but it didn't work as well. I'm using Ubuntu 18.08 LTS on a tablet PC that came preloaded with windows 10. The device is called Cherry ZE55L, it's very close to Chuwi products. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-30 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 4.17.0-1.2~lp1728244-generic 4.17.0-rc6 Tags: bionic dist-upgrade Uname: Linux 4.17.0-1-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hussam 1675 F pulseaudio /dev/snd/controlC1: hussam 1675 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-30 (3 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Cherry ZE55 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-1-generic root=UUID=162571f7-a7f2-4cd6-b090-0f4453300b7b ro quiet splash i8042.reset i8042.nomux i8042.nopnp i8042.noloop vt.handoff=1 ProcVersionSignature: Ubuntu 4.17.0-1.2~lp1728244-generic 4.17.0-rc6 RelatedPackageVersions: linux-restricted-modules-4.17.0-1-generic N/A linux-backports-modules-4.17.0-1-generic N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.17.0-1-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: WH-BI-13.3-S133AR100-A54A-036-E dmi.board.asset.tag: Default string dmi.board.name: i1331 dmi.board.vendor: alldocube dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrWH-BI-13.3-S133AR100-A54A-036-E:bd01/18/2018:svnCherry:pnZE55:pvrDefaultstring:rvnalldocube:rni1331:rvrDefaultstring:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZE55 dmi.product.version: Default string dmi.sys.vendor: Cherry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774793/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770003] Comment bridged from LTC Bugzilla
--- Comment From kla...@br.ibm.com 2018-06-04 09:42 EDT---
Canonical or Breno,
can we move this to accepted/verified? When is the release to customers
due?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1770003
Title:
qla2xxx: Fix page fault at kmem_cache_alloc_node()
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
IBM is requesting these nine patches to be SRU'd to Bionic. IBM found
that the current Bionic kernel contains a problem related to qla2xxx
driver which causes the following:
[ 66.295233] Unable to handle kernel paging request for data at address
0x8882f6ed90e9151a
[ 66.295297] Faulting instruction address: 0xc038a110
cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
sp: c692f8d0
msr: 90009033
dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000 softe: 0irq_happened: 0x01
pid = 1762, comm = systemd-journal
Linux version 4.15.0-20-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu
4.15.0-20.21-generic 4.15.20)
enter ? for help
[c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350
(unreliable)
[c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
[c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
[c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
[c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
[c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
[c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
[c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
[c692fe30] c000b184 system_call+0x58/0x6c
--- Exception: c00 (System Call) at 74826f6fa9c4
SP (75dc5510) is in userspace
We were able to get rid of this problem cherry picking some of the
upstream patches. Do you think they might fit in the SRU criteria?
The commit ids are below and they were easily cherry picked.
eaf75d1815dad230dac2f1e8f1dc0349b2d50071: scsi: qla2xxx: Fix double free bug
after firmware timeout
6d67492764b39ad6efb6822816ad73dc141752f4: scsi: qla2xxx: Prevent relogin
trigger from sending too many commands
7ac0c332f96bb9688560726f5e80c097ed8de59a: scsi: qla2xxx: Fix warning in
qla2x00_async_iocb_timeout()
045d6ea200af794ba15515984cff63787a7fc3c0: scsi: qla2xxx: Don't call
dma_free_coherent with IRQ disabled.
1ae634eb28533b82f9777a47c1ade44cb8c0182b: scsi: qla2xxx: Serialize session
free in qlt_free_session_done
d8630bb95f46ea118dede63bd75533faa64f9612: scsi: qla2xxx: Serialize session
deletion by using work_lock
Requries: 1c6cacf4ea6c04a58a0e3057f5ed60c24a4ffeff ('scsi: qla2xxx:
Fixup locking for session deletion')
94cff6e114df56d0df74cdabe3481df38d9b0c1e: scsi: qla2xxx: Remove unused
argument from qlt_schedule_sess_for_dele?
9cd883f07a54e5301d51e259acd250bb035996be: scsi: qla2xxx: Fix session cleanup
for N2N
== Regression Potential ==
Medium. There are nine patches in this pull request. They are not specific
to a
paticular arch, but they are specific to qla2xxx.
== Test Case ==
A test kernel was built with these patches and tested by IBM.
IBM states the test kernel resolved the bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1770003/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743529] Re: Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic -not syncing: Out of memory message when crash is triggered.
Hello bugproxy, or anyone else affected, Accepted kexec-tools into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/kexec- tools/1:2.0.16-1ubuntu1~16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: kexec-tools (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1743529 Title: Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic -not syncing: Out of memory message when crash is triggered. Status in The Ubuntu-power-systems project: In Progress Status in kexec-tools package in Ubuntu: Fix Released Status in kexec-tools source package in Xenial: Fix Committed Status in kexec-tools source package in Artful: Fix Committed Status in kexec-tools source package in Bionic: Fix Released Bug description: [Impact] Latest kexec-tools is needed to load/kexec recent kernels. For older releases, like xenial, it's needed to support linux-hwe kernels. [Regression Potential] It might fail to load the GA kernels, like a 4.4 kernel on xenial. [Test case] Different kernels on different architectures have been tested. == Comment: #0 - INDIRA P. JOGA Problem Description: === System hung with kernel panic Kernel panic - not syncing: Out of memory message when crash is triggered Steps to re-create: == > Installed ubuntu1804 daily build on Witherspoon test system root@whip:~# uname -a Linux whip 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux root@whip:~# uname -r 4.13.0-17-generic > root@whip:~# free -h totalusedfree shared buff/cache available Mem: 507G2.0G504G 19M728M 503G Swap: 2.0G 0B2.0G > Edited the grub /etc/default/grub.d/kexec-tools.cfg file and set the crash kernel parameter=4096M > Updated grub using update-grub command and reboot system. cat root@whip:~# cat /proc/cmdline root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet crashkernel=4096M > kdump status before triggering crash root@whip:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.13.0-17-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.13.0-17-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet irqpoll noirqdistrib nr_cpus=1 nousb systemd.unit=kdump-tools.service ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@whip:~# kdump-config status current state : ready to kdump > Enabled sysrq root@whip:~# sysctl -w kernel.sysrq=1 kernel.sysrq = 1 > Triggered crash and it hangs with kernel panic- OOM message as below root@whip:~# echo c > /proc/sysrq-trigger [ 85.731415] sysrq: SysRq : Trigger a crash [ 85.731472] Unable to handle kernel paging request for data at address 0x [ 85.731584] Faulting instruction address: 0xc078f588 [ 85.731670] Oops: Kernel access of bad area, sig: 11 [#1] [ 85.731744] SMP NR_CPUS=2048 [ 85.731745] NUMA [ 85.731790] PowerNV [ 85.731853] Modules linked in: rpcsec_gss_krb5 nfsv4 nfs fscache sctp_diag sctp dccp_diag dccp tcp_diag udp_diag raw_diag inet_diag unix_diag af_packet_diag netlink_diag binfmt_misc vmx_crypto crct10dif_vpmsum ofpart cmdlinepart idt_89hpesx powernv_flash ipmi_powernv opal_prd ibmpowernv mtd ipmi_devintf ipmi_msghandler at24 uio_pdrv_genirq uio dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua nfsd auth_rpcgss sch_fq_codel nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs xor raid6_pq nouveau bnx2x ast
[Kernel-packages] [Bug 1743529] Re: Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic -not syncing: Out of memory message when crash is triggered.
Hello bugproxy, or anyone else affected, Accepted kexec-tools into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/kexec- tools/1:2.0.16-1ubuntu1~17.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: kexec-tools (Ubuntu Artful) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1743529 Title: Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic -not syncing: Out of memory message when crash is triggered. Status in The Ubuntu-power-systems project: In Progress Status in kexec-tools package in Ubuntu: Fix Released Status in kexec-tools source package in Xenial: New Status in kexec-tools source package in Artful: Fix Committed Status in kexec-tools source package in Bionic: Fix Released Bug description: [Impact] Latest kexec-tools is needed to load/kexec recent kernels. For older releases, like xenial, it's needed to support linux-hwe kernels. [Regression Potential] It might fail to load the GA kernels, like a 4.4 kernel on xenial. [Test case] Different kernels on different architectures have been tested. == Comment: #0 - INDIRA P. JOGA Problem Description: === System hung with kernel panic Kernel panic - not syncing: Out of memory message when crash is triggered Steps to re-create: == > Installed ubuntu1804 daily build on Witherspoon test system root@whip:~# uname -a Linux whip 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux root@whip:~# uname -r 4.13.0-17-generic > root@whip:~# free -h totalusedfree shared buff/cache available Mem: 507G2.0G504G 19M728M 503G Swap: 2.0G 0B2.0G > Edited the grub /etc/default/grub.d/kexec-tools.cfg file and set the crash kernel parameter=4096M > Updated grub using update-grub command and reboot system. cat root@whip:~# cat /proc/cmdline root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet crashkernel=4096M > kdump status before triggering crash root@whip:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.13.0-17-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.13.0-17-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet irqpoll noirqdistrib nr_cpus=1 nousb systemd.unit=kdump-tools.service ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@whip:~# kdump-config status current state : ready to kdump > Enabled sysrq root@whip:~# sysctl -w kernel.sysrq=1 kernel.sysrq = 1 > Triggered crash and it hangs with kernel panic- OOM message as below root@whip:~# echo c > /proc/sysrq-trigger [ 85.731415] sysrq: SysRq : Trigger a crash [ 85.731472] Unable to handle kernel paging request for data at address 0x [ 85.731584] Faulting instruction address: 0xc078f588 [ 85.731670] Oops: Kernel access of bad area, sig: 11 [#1] [ 85.731744] SMP NR_CPUS=2048 [ 85.731745] NUMA [ 85.731790] PowerNV [ 85.731853] Modules linked in: rpcsec_gss_krb5 nfsv4 nfs fscache sctp_diag sctp dccp_diag dccp tcp_diag udp_diag raw_diag inet_diag unix_diag af_packet_diag netlink_diag binfmt_misc vmx_crypto crct10dif_vpmsum ofpart cmdlinepart idt_89hpesx powernv_flash ipmi_powernv opal_prd ibmpowernv mtd ipmi_devintf ipmi_msghandler at24 uio_pdrv_genirq uio dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua nfsd auth_rpcgss sch_fq_codel nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs xor raid6_pq nouveau bnx2x
[Kernel-packages] [Bug 1746299] Re: update makedumpfile tool version to v1.6.3
Hello bugproxy, or anyone else affected, Accepted makedumpfile into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.3-2~17.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: makedumpfile (Ubuntu Artful) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-artful -- 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/1746299 Title: update makedumpfile tool version to v1.6.3 Status in The Ubuntu-power-systems project: In Progress Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: New Status in makedumpfile source package in Artful: Fix Committed Status in makedumpfile source package in Bionic: Fix Released Bug description: [Impact] New upstream kernel versions, as those in linux-hwe package, require a newer makedumpfile to be supported. Otherwise, all copies fallback to copying the entire memory. [Test case] kdump-tools has been installed, system rebooted, then crash trigerred and verified that a small dump file was present on /var/crash/. Tested on amd64 and ppc64le. [Regression potential] Many other bug fixes have been included in the latest version of the package. The changes are supposed to fix these bugs, and have been tested as well. However, as the total of changes is not trivial, there is impact of regression that has been minimized by the tests done. Regression potential of not supporting older kernels has been tested with the kernels shipped on xenial and artful as well. == Comment: #0 - Hari Krishna Bathini - 2018-01-30 10:46:53 == ---Problem Description--- update makedumpfile to latest version v1.6.3 that officially supports up to kernel version 4.14.8. Since makedumpfile is inherently backward compatible, this would not break existing functionality.. Contact Information = hbath...@in.ibm.com ---uname output--- na Machine Type = na ---Debugger--- A debugger is not configured ---Steps to Reproduce--- makedumpfile reports ""The kernel version is not supported" while generating vmcore Also, there is a possibility of bogus address translations in makedumpfile tool with missing upstream patches. Can't be so sure without an exhaustive testing. Instead, it would be a good idea to go with the version which officially supports the kernel version in question. Userspace tool common name: makedumpfile The userspace tool has the following bit modes: 64-bit Userspace rpm: makedumpfile Userspace tool obtained from project website: na *Additional Instructions for hbath...@in.ibm.com: -Attach ltrace and strace of userspace application. == Comment: #1 - Hari Krishna Bathini - 2018-01-30 10:49:13 == With kernel version updated to 4.13.0, please update makedumpfile tool version to 1.6.3 which officially supports up to kernel version 4.14.8 [1]. Thanks Hari [1] http://lists.infradead.org/pipermail/kexec/2018-January/019853.html This needs to be tagged for both 16.04.4 & 18.04 releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1746299/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774764] Re: linux-oem: 4.15.0-1008.11 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772927 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Monday, 04. June 2018 13:01 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772927 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Monday, 04. June 2018 13:01 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1774764 Title: linux-oem: 4.15.0-1008.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772927 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1774764/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774793] Re: touchpad not detected
This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug. Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org. Once this bug is reported upstream, please add the tag: 'kernel-bug- reported-upstream'. [0] https://wiki.ubuntu.com/Bugs/Upstream/kernel ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774793 Title: touchpad not detected Status in linux package in Ubuntu: Triaged Bug description: I'm unable to get the name of the touchpad on system. And, I'm unable to copy text as well to support investigation on this bug-report. The following bug-report was the closest to my issue. However, I tried to use the patched kernel (mainline 4.17.0-1-generic) but it didn't fix my problem. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728244 I tried updating the GRUB_CMDLINE_LINUX_DEFAULT wit i8042.reset and i8042.nomux, but it didn't work as well. I'm using Ubuntu 18.08 LTS on a tablet PC that came preloaded with windows 10. The device is called Cherry ZE55L, it's very close to Chuwi products. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-30 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 4.17.0-1.2~lp1728244-generic 4.17.0-rc6 Tags: bionic dist-upgrade Uname: Linux 4.17.0-1-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hussam 1675 F pulseaudio /dev/snd/controlC1: hussam 1675 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-30 (3 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Cherry ZE55 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-1-generic root=UUID=162571f7-a7f2-4cd6-b090-0f4453300b7b ro quiet splash i8042.reset i8042.nomux i8042.nopnp i8042.noloop vt.handoff=1 ProcVersionSignature: Ubuntu 4.17.0-1.2~lp1728244-generic 4.17.0-rc6 RelatedPackageVersions: linux-restricted-modules-4.17.0-1-generic N/A linux-backports-modules-4.17.0-1-generic N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.17.0-1-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: WH-BI-13.3-S133AR100-A54A-036-E dmi.board.asset.tag: Default string dmi.board.name: i1331 dmi.board.vendor: alldocube dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrWH-BI-13.3-S133AR100-A54A-036-E:bd01/18/2018:svnCherry:pnZE55:pvrDefaultstring:rvnalldocube:rni1331:rvrDefaultstring:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZE55 dmi.product.version: Default string dmi.sys.vendor: Cherry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774793/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774817] Re: Temperature sensors on x470 not reporting correctly
Hi Kai-Heng, I am using 2700, specifically because it's a mini-itx and lower power is beneficial for small form factors. Thanks regardless! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774817 Title: Temperature sensors on x470 not reporting correctly Status in linux package in Ubuntu: Triaged Bug description: x470-I ROG strix motherboard and Ryzen 2700 After sudo sensors-detect and answering yes to all the probes the net result is: "Sorry, no sensors were detected. Either your system has no sensors, or they are not supported, or they are connected to an I2C or SMBus adapter that is not supported." sensors output lists: asus-isa- Adapter: ISA adapter cpu_fan:0 RPM nouveau-pci-0900 Adapter: PCI adapter fan1: 0 RPM temp1:+65.0°C (high = +95.0°C, hyst = +3.0°C) (crit = +105.0°C, hyst = +5.0°C) (emerg = +135.0°C, hyst = +5.0°C) k10temp-pci-00c3 Adapter: PCI adapter temp1:+94.2°C (high = +70.0°C) Where the cpu fan is patently wrong and the k10temp likewise. The nouveau-pci-0900 appears to be the actual CPU temperature. May be related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740736 Other info: Description: Ubuntu 18.04 LTS Release: 18.04 version log: Ubuntu 4.15.0-22.24-generic 4.15.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774994] [NEW] Laptop wakes up immediately after suspend or hibernation
Public bug reported: After going into suspend (via command line or lid close), the MacBook Pro (early 2015) wakes up immediately again. Same for hibernation. Running Ubuntu 18.04. extract from dmesg for a lid-close -> suspend -> wake-up -> lid-open cycle: [0.00] Linux version 4.15.0-22-generic (buildd@lgw01-amd64-013) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #24-Ubuntu SMP Wed May 16 12:15:17 UTC 2018 (Ubuntu 4.15.0-22.24-generic 4.15.17) [ ... ] [ 778.968982] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [ 783.011399] PM: suspend entry (deep) [ 783.011400] PM: Syncing filesystems ... done. [ 783.028538] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 783.030844] OOM killer disabled. [ 783.030844] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 783.032193] Suspending console(s) (use no_console_suspend to debug) [ 783.049960] sd 1:0:0:0: [sda] Synchronizing SCSI cache [ 783.054107] sd 1:0:0:0: [sda] Stopping disk [ 783.146124] thunderbolt :07:00.0: suspending... [ 783.146685] thunderbolt :07:00.0: suspend finished [ 783.146689] thunderbolt :07:00.0: stopping RX ring 0 [ 783.146698] thunderbolt :07:00.0: disabling interrupt at register 0x38200 bit 12 (0x1001 -> 0x1) [ 783.146710] thunderbolt :07:00.0: stopping TX ring 0 [ 783.146718] thunderbolt :07:00.0: disabling interrupt at register 0x38200 bit 0 (0x1 -> 0x0) [ 783.146725] thunderbolt :07:00.0: control channel stopped [ 783.246464] ACPI: Preparing to enter system sleep state S3 [ 783.418015] ACPI: EC: event blocked [ 783.418016] ACPI: EC: EC stopped [ 783.418018] PM: Saving platform NVS memory [ 783.418027] Disabling non-boot CPUs ... [ 783.434574] IRQ 65: no longer affine to CPU1 [ 783.435629] smpboot: CPU 1 is now offline [ 783.454574] IRQ 66: no longer affine to CPU2 [ 783.456378] smpboot: CPU 2 is now offline [ 783.478405] IRQ 21: no longer affine to CPU3 [ 783.478414] IRQ 43: no longer affine to CPU3 [ 783.478435] IRQ 71: no longer affine to CPU3 [ 783.479449] smpboot: CPU 3 is now offline [ 783.481656] ACPI: Low-level resume complete [ 783.481733] ACPI: EC: EC started [ 783.481734] PM: Restoring platform NVS memory [ 783.482160] Enabling non-boot CPUs ... [ 783.482240] x86: Booting SMP configuration: [ 783.482241] smpboot: Booting Node 0 Processor 1 APIC 0x2 [ 783.558589] cache: parent cpu1 should not be sleeping [ 783.687159] CPU1 is up [ 783.687212] smpboot: Booting Node 0 Processor 2 APIC 0x1 [ 783.687812] cache: parent cpu2 should not be sleeping [ 783.688001] CPU2 is up [ 783.688028] smpboot: Booting Node 0 Processor 3 APIC 0x3 [ 783.783709] cache: parent cpu3 should not be sleeping [ 783.978233] CPU3 is up [ 783.982020] ACPI: Waking up from system sleep state S3 [ 784.093246] pcieport :06:03.0: quirk: waiting for thunderbolt to reestablish PCI tunnels... [ 784.093249] pcieport :06:04.0: quirk: waiting for thunderbolt to reestablish PCI tunnels... [ 784.093362] pcieport :06:06.0: quirk: waiting for thunderbolt to reestablish PCI tunnels... [ 784.093475] pcieport :06:05.0: quirk: waiting for thunderbolt to reestablish PCI tunnels... [ 784.112655] thunderbolt :07:00.0: control channel starting... [ 784.112660] thunderbolt :07:00.0: starting TX ring 0 [ 784.112673] thunderbolt :07:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) [ 784.112677] thunderbolt :07:00.0: starting RX ring 0 [ 784.112689] thunderbolt :07:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) [ 784.112696] thunderbolt :07:00.0: resuming... [ 784.112699] thunderbolt :07:00.0: resetting switch at 0 [ 784.113249] thunderbolt :07:00.0: 0: resuming switch [ 784.144609] thunderbolt :07:00.0: resume finished [ 784.213878] thunderbolt :07:00.0: resetting error on 0:b. [ 784.213897] thunderbolt :07:00.0: 0:b: hotplug: scanning [ 784.213901] thunderbolt :07:00.0: 0:b: hotplug: no switch found [ 784.213984] thunderbolt :07:00.0: resetting error on 0:c. [ 784.213995] thunderbolt :07:00.0: 0:c: hotplug: scanning [ 784.213999] thunderbolt :07:00.0: 0:c: hotplug: no switch found [ 785.225640] ACPI: EC: event unblocked [ 785.226264] brcmfmac: brcmf_fil_cmd_data: bus is down. we have nothing to do. [ 785.226273] ACPI: button: The lid device is not compliant to SW_LID. [ 785.226276] brcmfmac: brcmf_fil_cmd_data: bus is down. we have nothing to do. [ 785.227145] brcmfmac: brcmf_fil_cmd_data: bus is down. we have nothing to do. [ 785.227149] brcmfmac: brcmf_cfg80211_get_channel: chanspec failed (-5) [ 785.236199] sd 1:0:0:0: [sda] Starting disk [ 785.408582] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43602-pcie.bin for chip 0x00aa52(43602) rev 0x01 [ 785.408703] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2 [ 785.409666] OOM killer
[Kernel-packages] [Bug 1768103] Re: Lancer A0 Asic HBA's won't boot with 18.04
This is what your patch should looking like if you skip the 1st one. @@ -10711,9 +10706,7 @@ lpfc_get_sli4_parameters(struct lpfc_hba *phba, LPFC_MBOXQ_t *mboxq) lpfc_printf_log(phba, KERN_INFO, LOG_INIT | LOG_NVME, "6422 XIB %d: FCP %d %d NVME %d %d %d %d\n", bf_get(cfg_xib, mbx_sli4_parameters), phba->fcp_embed_pbde, phba->fcp_embed_io, phba->nvme_support, phba->nvme_embed_pbde, phba->cfg_nvme_embed_cmd, phba->cfg_suppress_rsp); + if ((bf_get(lpfc_sli_intf_if_type, >sli4_hba.sli_intf) == + LPFC_SLI_INTF_IF_TYPE_2) && + (bf_get(lpfc_sli_intf_sli_family, >sli4_hba.sli_intf) == +LPFC_SLI_INTF_FAMILY_LNCR_A0)) exp_wqcq_pages = false; if ((bf_get(cfg_cqpsize, mbx_sli4_parameters) & LPFC_CQ_16K_PAGE_SZ) && -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768103 Title: Lancer A0 Asic HBA's won't boot with 18.04 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: We have discovered that an early asic model (A0) of our 16/32GB HBA's doesn't boot with the lpfc driver in Ubuntu 18.04. After further review and discussion, this has been deemed a low risk issue since early A0 HBA's were only ever shipped to OEMs for test purposes. These cards were never shipped to end customers. We have been working to replace those cards whenever we discover them. We'll leave it up to Canonical to decide whether they want to pull this in this single patch to an 18.04 subsequent update. Symptom: Ubuntu 18.04 with lpfc driver 12.0.0.0 they can't see LPe16002-M6 but can see LPe16002B-M6 Resolution: new lpfc driver patch update. scsi: lpfc: Fix WQ/CQ creation for older asic's. https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=4.18/scsi-queue=83fae8ca4ae09403bfb99542f1aaa292c06cb111 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770840] Re: My Inspiron-1420 shuts down when waking from Suspended Mode.
The bug seems to be fixed. I closed the lid a couple of times which forced the notebook into sleep mode. Upon opening the lid, the notebook booted to the lock screen. Thanks, Sakib. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770840 Title: My Inspiron-1420 shuts down when waking from Suspended Mode. Status in linux package in Ubuntu: Confirmed Bug description: Hello, I installed Ubuntu Budgie - amd64 on my Inspiron 1420. When I close the lid the Notebook (apparently) goes into suspend mode. Instead of starting-up upon opening the lid, the notebook shuts down. I couldn't find the settings for the lid in the settings menu. I can think of two possible reasons (not necessarily true): 1) My HDD is password protected. When I open my notebook it asks for HD password and then takes to the boot menu. 2) I have two operating systems (Dual Boot) installed on my Notebook: Windows 10 developer edition and Ubuntu Budgie. Please look into this. Thanks, Sakib. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sat May 12 18:34:57 2018 InstallationDate: Installed on 2018-05-10 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: s 1410 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-15 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 1420 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=f689a411-dda2-49d1-a590-1cdb86b27530 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/11/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0KN548 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd07/11/2008:svnDellInc.:pnInspiron1420:pvr:rvnDellInc.:rn0KN548:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1420 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770840/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743529] Re: Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic -not syncing: Out of memory message when crash is triggered.
** Description changed: + [Impact] + Latest kexec-tools is needed to load/kexec recent kernels. For older releases, like xenial, it's needed to support linux-hwe kernels. + + [Regression Potential] + It might fail to load the GA kernels, like a 4.4 kernel on xenial. + + [Test case] + Different kernels on different architectures have been tested. + + == Comment: #0 - INDIRA P. JOGA Problem Description: === System hung with kernel panic Kernel panic - not syncing: Out of memory message when crash is triggered Steps to re-create: == > Installed ubuntu1804 daily build on Witherspoon test system root@whip:~# uname -a Linux whip 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux root@whip:~# uname -r 4.13.0-17-generic > root@whip:~# free -h - totalusedfree shared buff/cache available + totalusedfree shared buff/cache available Mem: 507G2.0G504G 19M728M 503G Swap: 2.0G 0B2.0G - - > Edited the grub /etc/default/grub.d/kexec-tools.cfg file and set the crash kernel parameter=4096M + > Edited the grub /etc/default/grub.d/kexec-tools.cfg file and set the + crash kernel parameter=4096M > Updated grub using update-grub command and reboot system. cat root@whip:~# cat /proc/cmdline root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet crashkernel=4096M > kdump status before triggering crash root@whip:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash - crashkernel addr: -/var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.13.0-17-generic - kdump initrd: -/var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.13.0-17-generic + crashkernel addr: + /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.13.0-17-generic + kdump initrd: + /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.13.0-17-generic current state:ready to kdump kexec command: - /sbin/kexec -p --command-line="root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet irqpoll noirqdistrib nr_cpus=1 nousb systemd.unit=kdump-tools.service ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz + /sbin/kexec -p --command-line="root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet irqpoll noirqdistrib nr_cpus=1 nousb systemd.unit=kdump-tools.service ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@whip:~# kdump-config status current state : ready to kdump > Enabled sysrq root@whip:~# sysctl -w kernel.sysrq=1 kernel.sysrq = 1 > Triggered crash and it hangs with kernel panic- OOM message as below root@whip:~# echo c > /proc/sysrq-trigger [ 85.731415] sysrq: SysRq : Trigger a crash [ 85.731472] Unable to handle kernel paging request for data at address 0x [ 85.731584] Faulting instruction address: 0xc078f588 [ 85.731670] Oops: Kernel access of bad area, sig: 11 [#1] - [ 85.731744] SMP NR_CPUS=2048 - [ 85.731745] NUMA + [ 85.731744] SMP NR_CPUS=2048 + [ 85.731745] NUMA [ 85.731790] PowerNV [ 85.731853] Modules linked in: rpcsec_gss_krb5 nfsv4 nfs fscache sctp_diag sctp dccp_diag dccp tcp_diag udp_diag raw_diag inet_diag unix_diag af_packet_diag netlink_diag binfmt_misc vmx_crypto crct10dif_vpmsum ofpart cmdlinepart idt_89hpesx powernv_flash ipmi_powernv opal_prd ibmpowernv mtd ipmi_devintf ipmi_msghandler at24 uio_pdrv_genirq uio dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua nfsd auth_rpcgss sch_fq_codel nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs xor raid6_pq nouveau bnx2x ast i2c_algo_bit ttm drm_kms_helper mdio libcrc32c crc32c_vpmsum mlx5_core syscopyarea sysfillrect sysimgblt fb_sys_fops tg3 drm ahci mlxfw libahci nvme devlink nvme_core [ 85.732704] CPU: 10 PID: 4316 Comm: bash Not tainted 4.13.0-17-generic #20-Ubuntu [ 85.732764] task: c03fcb141700 task.stack: c03fc2374000 [ 85.732858] NIP: c078f588 LR: c07904b8 CTR: c078f560 [ 85.732977] REGS: c03fc23779f0 TRAP: 0300 Not tainted (4.13.0-17-generic) [ 85.733066] MSR: 90009033 [ 85.733075] CR: 2842 XER: 2004 - [ 85.733201] CFAR: c07904b4 DAR: DSISR: 4200 SOFTE: 1 - [ 85.733201] GPR00: c07904b8 c03fc2377c70 c15f6000 0063 - [ 85.733201] GPR04: c03feedfade8 c03feee12068 90009033 000a - [ 85.733201] GPR08: 0007 0001 90001003 - [ 85.733201] GPR12: c078f560 c7a66900 10180df8
[Kernel-packages] [Bug 1774865] Re: 4.15.0-22 won't boot on Dell XPS 15 9570
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Tags added: bionic kernel-da-key needs-bisect ** Changed in: linux (Ubuntu Bionic) Status: Triaged => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774865 Title: 4.15.0-22 won't boot on Dell XPS 15 9570 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: 4.15.0-22 fails on boot on a Dell XPS 9570 with "not all CPUs entered broadcast exception handler". 4.15.0-20 works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774865/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774875] Re: Internal laptop display defaults to low refresh rate
** Package changed: linux-signed (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Medium Status: Triaged ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Artful) ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774875 Title: Internal laptop display defaults to low refresh rate Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Bug description: It appears that ever since kernel ~4.14, there was a bug in i915 DRM that caused the internal laptop displays connected by eDP to default to 40 Hz screen refresh rate. Affected Ubuntu release: 18.04 Kernel package version: 4.15.0-22.24 What you expected to happen: The refresh rate has a sane default setting What happened instead: The refresh rate defaults to 40 Hz Upstream bug report: https://bugs.freedesktop.org/show_bug.cgi?id=103497 This has already been fixed in drm-tip: https://cgit.freedesktop.org/drm-tip/commit/?id=d93fa1b47b8fcd149b5091f18385304f402a8e15 I do confirm that the latest daily build cod/tip/drm-tip/2018-06-03 (8fdb62e0511e81fa935059c274a2457361fdb679) of drm-tip kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/ indeed fixes this issue for me. Known workarounds: The user can force the display to use other refresh rates close to 60 Hz (59,96 works quite well in my case) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 Uname: Linux 4.17.0-994-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 3 16:53:20 2018 InstallationDate: Installed on 2018-06-03 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774883] Re: GPF using CIFS and ACQ107 under heavy use
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774883 Title: GPF using CIFS and ACQ107 under heavy use Status in linux package in Ubuntu: Incomplete Bug description: using aquanta 10GBE ethernet I get a GPF when scanning CIFS-mounted library, works fine using 1GBE intel nic. GPF follows: Jun 2 12:55:28 klimt kernel: [ 2112.707816] general protection fault: [#1] SMP PTI Jun 2 12:55:28 klimt kernel: [ 2112.709215] Modules linked in: cmac md4 nls_utf8 cifs ccm fscache binfmt_misc snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp ar c4 kvm_intel iwlmvm kvm snd_hda_codec_realtek irqbypass snd_hda_codec_generic mac80211 intel_cstate iwlwifi intel_rapl_perf snd_hda_intel snd_hda_codec snd_hda_core cfg80211 intel_wmi_thunde rbolt mxm_wmi snd_hwdep snd_pcm snd_timer snd soundcore mei_me ioatdma mei shpchp wmi mac_hid nvidia_uvm(POE) sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear r aid1 nvidia_drm(POE) nvidia_modeset(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel Jun 2 12:55:28 klimt kernel: [ 2112.728235] pcbc nvidia(POE) aesni_intel aes_x86_64 crypto_simd glue_helper cryptd drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm ipmi_dev intf ipmi_msghandler igb e1000e nvme dca nvme_core i2c_algo_bit atlantic ptp pps_core ahci libahci Jun 2 12:55:28 klimt kernel: [ 2112.734257] CPU: 8 PID: 1499 Comm: EmbyServer Tainted: P OE4.15.0-22-generic #24-Ubuntu Jun 2 12:55:28 klimt kernel: [ 2112.736705] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X299 Professional Gaming i9 XE, BIOS P1.00 09/28/2017 Jun 2 12:55:28 klimt kernel: [ 2112.739735] RIP: 0010:prefetch_freepointer+0x15/0x30 Jun 2 12:55:28 klimt kernel: [ 2112.741050] RSP: 0018:aa9a0823bd20 EFLAGS: 00010206 Jun 2 12:55:28 klimt kernel: [ 2112.742434] RAX: RBX: 217a77ddff956e69 RCX: 8789 Jun 2 12:55:28 klimt kernel: [ 2112.744329] RDX: 8788 RSI: 217a77ddff956e69 RDI: 9da1d110ab80 Jun 2 12:55:28 klimt kernel: [ 2112.746222] RBP: aa9a0823bd20 R08: ca99fe822eb0 R09: 9da1d31275a0 Jun 2 12:55:28 klimt kernel: [ 2112.748113] R10: 0007fcbd8002 R11: 9da1ca4d9e00 R12: 014000c0 Jun 2 12:55:28 klimt kernel: [ 2112.750006] R13: 9da1ddc04780 R14: 9da1ca4d9000 R15: 9da1d110ab80 Jun 2 12:55:28 klimt kernel: [ 2112.794382] FS: 7fcc33fff700() GS:9da1de40() knlGS: Jun 2 12:55:28 klimt kernel: [ 2112.884578] CS: 0010 DS: ES: CR0: 80050033 Jun 2 12:55:28 klimt kernel: [ 2112.930582] CR2: 7fcc7e5bf000 CR3: 002012cdc006 CR4: 003606e0 Jun 2 12:55:28 klimt kernel: [ 2112.976554] DR0: DR1: DR2: Jun 2 12:55:28 klimt kernel: [ 2113.021459] DR3: DR6: fffe0ff0 DR7: 0400 Jun 2 12:55:28 klimt kernel: [ 2113.064959] Call Trace: Jun 2 12:55:28 klimt kernel: [ 2113.106986] kmem_cache_alloc+0xa2/0x1b0 Jun 2 12:55:28 klimt kernel: [ 2113.148571] ? anon_vma_fork+0x97/0x130 Jun 2 12:55:28 klimt kernel: [ 2113.189139] anon_vma_fork+0x97/0x130 Jun 2 12:55:28 klimt kernel: [ 2113.228632] copy_process.part.35+0xdce/0x1af0 Jun 2 12:55:28 klimt kernel: [ 2113.267459] _do_fork+0xdf/0x400 Jun 2 12:55:28 klimt kernel: [ 2113.305090] ? get_unused_fd_flags+0x30/0x40 Jun 2 12:55:28 klimt kernel: [ 2113.342027] SyS_clone+0x19/0x20 Jun 2 12:55:28 klimt kernel: [ 2113.377704] do_syscall_64+0x73/0x130 Jun 2 12:55:28 klimt kernel: [ 2113.412455] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Jun 2 12:55:28 klimt kernel: [ 2113.446867] RIP: 0033:0x7fcd1de5ab1c Jun 2 12:55:28 klimt kernel: [ 2113.480134] RSP: 002b:7fcc33ffb630 EFLAGS:
[Kernel-packages] [Bug 1774881] Re: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: installed linux-image-4.15.0-20-generic package pre-removal script subprocess returned
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux-signed (Ubuntu) Importance: Undecided => Low ** Changed in: linux-signed (Ubuntu) Status: New => Incomplete ** Package changed: linux-signed (Ubuntu) => linux (Ubuntu) -- 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/1774881 Title: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: installed linux-image-4.15.0-20-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: Incomplete Bug description: Happened after a reboot after a kernel update. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 Date: Sun Jun 3 17:41:51 2018 ErrorMessage: installed linux-image-4.15.0-20-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2018-01-21 (132 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) 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: linux-signed Title: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: installed linux-image-4.15.0-20-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-04-30 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774881/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Incomplete Bug description: I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774797] Re: Trid partial upgrade.
Can you provide some more detail on the bug you are seeing? ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774797 Title: Trid partial upgrade. Status in linux package in Ubuntu: Incomplete Bug description: Failure during inssstall ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-127-generic 4.4.0-127.153 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: john 2399 F pulseaudio /dev/snd/controlC0: john 2399 F pulseaudio /dev/snd/controlC1: john 2399 F pulseaudio CurrentDesktop: Unity Date: Sat Jun 2 17:17:58 2018 HibernationDevice: RESUME=UUID=b75950d0-1553-48fc-83b8-e8c7d0b5d796 InstallationDate: Installed on 2016-08-22 (648 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic root=UUID=440fc4e4-fcb3-495f-a3d3-2a6e46c0dac3 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-127-generic N/A linux-backports-modules-4.4.0-127-generic N/A linux-firmware 1.157.19 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2001 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2001:bd03/09/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774797/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] Re: Thinkpad T450s frequently hangs with black screen on resume
Would it be possible for you to see if this bug was already fixed in the mainline kernel, which is available from: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774771 Title: Thinkpad T450s frequently hangs with black screen on resume Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed 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 1774731] Re: Missing "/sys/module/dummy/parameters/" subdir on dummy module
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774731 Title: Missing "/sys/module/dummy/parameters/" subdir on dummy module Status in linux package in Ubuntu: Incomplete Bug description: Hello, On Ubuntu 18.04 (fully updated), the following configuration does not work: File /etc/modprobe.d/dummy.conf with: options dummy numdummies=12 File /etc/modules dummy The module "dummy" is loaded but, there is no 12 dummies NIC cards! The manual workaround is: --- rmmod dummy modprobe dummy numdummies=12 --- I talked on IRC and someone pointed that the dummy module is missing its "/sys/module/dummy/parameters/" subdir, so, I'm filling this bug report now. Cheers! --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-22-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=26330e04-49ed-11e8-9cae-525400a53f07 ro 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 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774815] Re: Add bpftool to linux-tools-common
** Changed in: linux (Ubuntu) Importance: Undecided => Wishlist ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Also affects: linux (Ubuntu Cosmic) Importance: Wishlist Status: Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774815 Title: Add bpftool to linux-tools-common Status in linux package in Ubuntu: Triaged Status in linux source package in Cosmic: Triaged Bug description: bpftool is a debugging and introspection tool actively developed by the BPF kernel community. It's developed as part of the kernel source tree under tools/: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/bpf/bpftool It would be really great and appreciated if Ubuntu folks could package this as part of linux-tools-common. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17 ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768976 Title: Ubuntu 18.04 is overheating after upgrade from 16.04 Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: Ubuntu is overheating at my laptop. Opening youtube on firefox is enough for critical temperature shutdown. Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C with only firefox or chrome open and doing nothing. On my old 16.04 with same using, the temp varies between 55 and 70°C. First thought was the driver nouveau is the problem, and finally I was able to install by add "nouveau.modeset=0" at livecd boot options, without temp shutdown. After install I disable the nouveau at modprobe blacklist, but the system continues overheating and shutdown with basic usage. I have no idea what's happening with the bionic at my laptop. My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.17 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu May 3 16:22:40 2018 InstallationDate: Installed on 2018-04-27 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptHistorylog: Start-Date: 2018-04-27 15:46:02 End-Date: 2018-04-27 15:46:02 VarLogDistupgradeAptlog: Log time: 2018-04-27 15:45:39.753331 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done Log time: 2018-04-27 15:46:04.859979 VarLogDistupgradeApttermlog: Log started: 2018-04-27 15:46:02 Log ended: 2018-04-27 15:46:02 --- .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: edir 2354 F pulseaudio CompositorRunning: None DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [144d:c0a5] Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5] HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d InstallationDate: Installed on 2018-04-27 (36 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711 NonfreeKernelModules: wl Package: xserver-xorg-video-nouveau 1:1.0.15-2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: bionic ubuntu Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install)
[Kernel-packages] [Bug 1774817] Re: Temperature sensors on x470 not reporting correctly
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774817 Title: Temperature sensors on x470 not reporting correctly Status in linux package in Ubuntu: Triaged Bug description: x470-I ROG strix motherboard and Ryzen 2700 After sudo sensors-detect and answering yes to all the probes the net result is: "Sorry, no sensors were detected. Either your system has no sensors, or they are not supported, or they are connected to an I2C or SMBus adapter that is not supported." sensors output lists: asus-isa- Adapter: ISA adapter cpu_fan:0 RPM nouveau-pci-0900 Adapter: PCI adapter fan1: 0 RPM temp1:+65.0°C (high = +95.0°C, hyst = +3.0°C) (crit = +105.0°C, hyst = +5.0°C) (emerg = +135.0°C, hyst = +5.0°C) k10temp-pci-00c3 Adapter: PCI adapter temp1:+94.2°C (high = +70.0°C) Where the cpu fan is patently wrong and the k10temp likewise. The nouveau-pci-0900 appears to be the actual CPU temperature. May be related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740736 Other info: Description: Ubuntu 18.04 LTS Release: 18.04 version log: Ubuntu 4.15.0-22.24-generic 4.15.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751581] Re: systemd-udevd Process '/sbin/crda' failed with exit code 249
*** This bug is a duplicate of bug 1662003 *** https://bugs.launchpad.net/bugs/1662003 version 18.04 when using ACL option in mounting NTFS partition. juin 04 13:21:21 D1804 ntfs-3g[1154]: Version 2017.3.23 integrated FUSE 28 juin 04 13:21:21 D1804 ntfs-3g[1154]: Mounted /dev/sda15 (Read-Write, label "Commun2", NTFS 3.1) juin 04 13:21:21 D1804 ntfs-3g[1154]: Cmdline options: rw,acl juin 04 13:21:21 D1804 ntfs-3g[1154]: Mount options: rw,allow_other,nonempty,relatime,fsname=/dev/sda15,blkdev,blksize=4096 juin 04 13:21:21 D1804 systemd[1]: Mounted /media/Commun2. -- Subject: L'unité (unit) media-Commun2.mount a terminé son démarrage -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- L'unité (unit) media-Commun2.mount a terminé son démarrage, avec le résultat RESULT. juin 04 13:21:21 D1804 ntfs-3g[1154]: User mapping built, Posix ACLs in use, configuration type 7 juin 04 13:21:21 D1804 systemd-udevd[600]: Process '/sbin/crda' failed with exit code 249. juin 04 13:21:21 D1804 systemd-udevd[600]: Process '/sbin/crda' failed with exit code 249. juin 04 13:21:21 D1804 ntfs-3g[1164]: Version 2017.3.23 integrated FUSE 28 ** Attachment added: "trace of journalctl -xb" https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1751581/+attachment/5148523/+files/TRACE -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crda in Ubuntu. https://bugs.launchpad.net/bugs/1751581 Title: systemd-udevd Process '/sbin/crda' failed with exit code 249 Status in crda package in Ubuntu: Confirmed Bug description: running 18.04 dev and seeing this in my syslog: > systemd-udevd[332]: Process '/sbin/crda' failed with exit code 249. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: crda 3.18-1build1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Feb 25 14:24:11 2018 InstallationDate: Installed on 2013-09-28 (1611 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1) SourcePackage: crda UpgradeStatus: Upgraded to bionic on 2018-01-12 (43 days ago) mtime.conffile..etc.default.crda: 2015-12-16T14:54:18.828473 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1751581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774950] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1774950 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Incomplete Bug description: I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
** 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/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: New Bug description: I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774950] [NEW] Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
You have been subscribed to a public bug: I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment kernel4.15 kubuntu18.04 suspend-resume ubuntu18.04 -- Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) https://bugs.launchpad.net/bugs/1774950 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751581] Re: systemd-udevd Process '/sbin/crda' failed with exit code 249
*** This bug is a duplicate of bug 1662003 *** https://bugs.launchpad.net/bugs/1662003 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: crda (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crda in Ubuntu. https://bugs.launchpad.net/bugs/1751581 Title: systemd-udevd Process '/sbin/crda' failed with exit code 249 Status in crda package in Ubuntu: Confirmed Bug description: running 18.04 dev and seeing this in my syslog: > systemd-udevd[332]: Process '/sbin/crda' failed with exit code 249. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: crda 3.18-1build1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Feb 25 14:24:11 2018 InstallationDate: Installed on 2013-09-28 (1611 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1) SourcePackage: crda UpgradeStatus: Upgraded to bionic on 2018-01-12 (43 days ago) mtime.conffile..etc.default.crda: 2015-12-16T14:54:18.828473 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1751581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774764] Re: linux-oem: 4.15.0-1008.11 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1774764 Title: linux-oem: 4.15.0-1008.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772927 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1774764/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1662003] Re: /sbin/crda failed with exit code 249
Ubuntu 18.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crda in Ubuntu. https://bugs.launchpad.net/bugs/1662003 Title: /sbin/crda failed with exit code 249 Status in crda package in Ubuntu: Confirmed Bug description: /var/log/syslog tells : --- kernel: [0.144719] ACPI: PCI Root Bridge [PCI0] (domain [bus 00-ff]) systemd-udevd: Process '/sbin/crda' failed with exit code 249. kernel: [0.144728] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] --- ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: crda 3.13-1 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Feb 5 20:18:42 2017 InstallationDate: Installed on 2017-02-01 (3 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: crda UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1662003/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774764] Re: linux-oem: 4.15.0-1008.11 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1774764 Title: linux-oem: 4.15.0-1008.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772927 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1774764/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
