[Kernel-packages] [Bug 1799497] Re: 4.15 kernel hard lockup about once a week
Oh and whatever kernel I boot needs to have support for ZFS 0.7 or I won't be able to read my drives. ** Tags added: apport-collected ** Description changed: My main server has been running into hard lockups about once a week ever since I switched to the 4.15 Ubuntu 18.04 kernel. When this happens, nothing is printed to the console, it's effectively stuck showing a login prompt. The system is running with panic=1 on the cmdline but isn't rebooting so the kernel isn't even processing this as a kernel panic. As this felt like a potential hardware issue, I had my hosting provider give me a completely different system, different motherboard, different CPU, different RAM and different storage, I installed that system on 18.04 and moved my data over, a week later, I hit the issue again. We've since also had a LXD user reporting similar symptoms here also on varying hardware: https://github.com/lxc/lxd/issues/5197 My system doesn't have a lot of memory pressure with about 50% of free memory: root@vorash:~# free -m totalusedfree shared buff/cache available Mem: 31819 17574 402 513 13842 13292 Swap: 159092687 13222 I will now try to increase console logging as much as possible on the system in the hopes that next time it hangs we can get a better idea of what happened but I'm not too hopeful given the complete silence on the console when this occurs. System is currently on: Linux vorash 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux - But I've seen this since the GA kernel on 4.15 so it's not a recent - regression. + But I've seen this since the GA kernel on 4.15 so it's not a recent regression. + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Oct 23 16:12 seq + crw-rw 1 root audio 116, 33 Oct 23 16:12 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' + ApportVersion: 2.20.9-0ubuntu7.4 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' + AudioDevicesInUse: + Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Cannot stat file /proc/22822/fd/10: Permission denied + Cannot stat file /proc/22831/fd/10: Permission denied + DistroRelease: Ubuntu 18.04 + HibernationDevice: + RESUME=none + CRYPTSETUP=n + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 002: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: Intel Corporation S1200SP + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 mgadrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=575c878a-0be6-4806-9c83-28f67aedea65 ro biosdevname=0 net.ifnames=0 panic=1 verbose console=tty0 console=ttyS0,115200n8 + ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-38-generic N/A + linux-backports-modules-4.15.0-38-generic N/A + linux-firmware 1.173.1 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' + Tags: bionic + Uname: Linux 4.15.0-38-generic x86_64 + UnreportableReason: This report is about a package that is not installed. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: False + dmi.bios.date: 01/25/2018 + dmi.bios.vendor: Intel Corporation + dmi.bios.version: S1200SP.86B.03.01.1029.012520180838 + dmi.board.asset.tag: Base Board Asset Tag + dmi.board.name: S1200SP + dmi.board.vendor: Intel Corporation + dmi.board.version: H57532-271 + dmi.chassis.asset.tag: + dmi.chassis.type: 23 + dmi.chassis.vendor: ... + dmi.chassis.version: .. + dmi.modalias: dmi:bvnIntelCorporation:bvrS1200SP.86B.03.01.1029.012520180838:bd01/25/2018:svnIntelCorporation:pnS1200SP:pvr:rvnIntelCorporation:rnS1200SP:rvrH57532-271:cvn...:ct23:cvr..: + dmi.product.family: Family + dmi.product.name: S1200SP + dmi.product.version: + dmi.sys.vendor: Intel Corporation -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799497 Title: 4.15 kernel hard lockup about once a week Status in linux package in Ubuntu: Incomplete Status in linux source package in
[Kernel-packages] [Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
Tested bionic-proposed kernel 4.15.0-38.41. There now is no difference between ant_sel=0,1,or 2 BUT compared to 4.15.0-32 ant_sel=2, the reception is 70% as opposed to 100%. Go figure :-) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799102] Re: WARNING on boot in Intel GVT-g guest
** 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/1799102 Title: WARNING on boot in Intel GVT-g guest Status in linux package in Ubuntu: Confirmed Bug description: When booting Ubuntu Cosmic Cuttlefish 18.10 in an Intel GVT-g Virtual Machine, a kernel WARNING appears in dmesg, with the following: [3.563734] WARNING: CPU: 3 PID: 346 at drivers/gpu/drm/i915/i915_irq.c:161 gen3_assert_iir_is_zero+0x38/0xa0 [i915] I have not noticed negative effects in the VM, but a kernel WARNING probably has relevance. While I added a custom EDID to fix resolution, the WARNING happens without custom EDID set too. I will add information about the host in the next message. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: User Name 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1896 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 21 19:44:44 2018 InstallationDate: Installed on 2018-10-18 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IwConfig: lono wireless extensions. ens8 no wireless extensions. Lsusb: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 46f4:0002 Bus 002 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=6cb7fc66-eb2c-4203-9d7d-2aa2665911ac ro quiet splash drm.edid_firmware=EDID_E1941.bin log_buf_len=16M vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-3.0 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.0:cvnQEMU:ct1:cvrpc-i440fx-3.0: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-3.0 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799102/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799082] Re: Returning from suspend exits x session
** 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/1799082 Title: Returning from suspend exits x session Status in linux package in Ubuntu: Incomplete Bug description: Using kernel 4.15.0-36 on my XPS15, suspending (e.g. closing the laptop lid) and reopening will take me to the 'swipe up' screen; upon swiping up, the session ends and I end back at the login screen. Does not reproduce on 4.15.0-34 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-36-generic 4.15.0-36.39 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim4385 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 21 20:07:05 2018 InstallationDate: Installed on 2017-09-16 (399 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9560 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=13c87a4d-94b5-421e-8e39-d6bf0a2b05a5 ro quiet splash acpi_rev_override=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-06-03 (140 days ago) dmi.bios.date: 08/30/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799083] Re: virtual console unavailable with upgrade of cosmic or Ubuntu 18.10
** 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/1799083 Title: virtual console unavailable with upgrade of cosmic or Ubuntu 18.10 Status in linux package in Ubuntu: Incomplete Bug description: Virtual terminal Alt F1-F6 will not display a login prompt. Kernel package 4.18.0-10.11 Using the older release kernel package 4.15.0-33.36, the virtual terminals work as normal. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cp 2209 F pulseaudio /dev/snd/controlC0: cp 2209 F pulseaudio CurrentDesktop: LXQt Date: Sun Oct 21 15:00:23 2018 HibernationDevice: RESUME=UUID=c8402f14-cff8-4ea7-b7c0-e290ac74c235 InstallationDate: Installed on 2018-04-21 (183 days ago) InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. Latitude E6520 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=8943f032-77a1-4075-83a8-648f2115f371 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-20 (1 days ago) dmi.bios.date: 01/16/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.asset.tag: 20KYFS1L dmi.board.name: 0692FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: 20KYFS1L dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd01/16/2012:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0692FT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799235] Re: kworker process starts at 85% of cpu and stays there
** 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/1799235 Title: kworker process starts at 85% of cpu and stays there Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu starts, w/ /sbin/init, a kworker process that never stops running below 85%: pb@pb-tower:~/Downloads$ ps -elf F S UIDPID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD 4 S root 1 0 0 80 0 - 56471 - 18:30 ?00:00:01 /sbin/init splash 1 S root 2 0 0 80 0 - 0 - 18:30 ?00:00:00 [kthreadd] 1 R root85 2 63 80 0 - 0 - 18:30 ? 00:03:03 [kworker/0:1+kac] After a few hours, grep . -r /sys/firmware/acpi/interrupts/ shows tens of millions of interrupts. The following command line stops the kworker process: echo "disable" > /sys/firmware/acpi/interrupts/gpe6F On the other hand, I haven't been able to properly shut down my system after this command (power never goes off except manually). I believe the bug is related to the one discussed here: https://superuser.com/questions/1117992/acpi-exception-ae-not-found- while-evaluating-gpe-method-floods-syslog The dmesg w/ this report may be somewhat confusing because there is an unsigned module. But w/ the module removed, dmesg gives the following: [0.097480] ACPI: Dynamic OEM Table Load: [0.097480] ACPI: SSDT 0xA07F57173000 000317 (v02 PmRef ApHwp 3000 INTL 20160527) [0.097480] ACPI: Executed 1 blocks of module-level executable AML code [0.100180] ACPI: Dynamic OEM Table Load: [0.100186] ACPI: SSDT 0xA07F577EF400 00030A (v02 PmRef ApCst 3000 INTL 20160527) [0.100473] ACPI: Executed 1 blocks of module-level executable AML code [0.102187] ACPI: Interpreter enabled [0.10] ACPI: (supports S0 S3 S4 S5) [0.102223] ACPI: Using IOAPIC for interrupt routing [0.102275] HEST: Table parsing has been initialized. [0.102277] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [0.103580] ACPI: GPE 0x20 active on init [0.104031] ACPI Error: No handler for Region [WST1] ((ptrval)) [GenericSerialBus] (20170831/evregion-166) [0.104035] ACPI Error: Region GenericSerialBus (ID=9) has no handler (20170831/exfldio-299) [0.104040] Initialized Local Variables for Method [PAS1]: [0.104041] Local0: (ptrval)Integer 0001 [0.104045] No Arguments are initialized for method [PAS1] [0.104046] ACPI Error: Method parse/execution failed \_SB.PCI0.I2C0.PAS1, AE_NOT_EXIST (20170831/psparse-550) [0.104052] ACPI Error: Method parse/execution failed \_GPE._L20, AE_NOT_EXIST (20170831/psparse-550) [0.104058] ACPI Exception: AE_NOT_EXIST, while evaluating GPE method [_L20] (20170831/evgpe-646) [0.104005] ACPI: GPE 0x6F active on init [0.104005] ACPI: Enabled 10 GPEs in block 00 to 7F [0.212126] ACPI: Power Resource [USBC] (on) [0.444270] pci :06:00.0: PME# supported from D0 D1 D2 D3hot [0.444270] pci :06:00.1: [1033:00e0] type 00 class 0x0c0320 [0.444270] pci :06:00.1: reg 0x10: [mem 0xa200-0xa2ff] [0.444278] pci :06:00.1: supports D1 D2 [0.444278] pci :06:00.1: PME# supported from D0 D1 D2 D3hot [0.444278] pci :05:00.0: PCI bridge to [bus 06] [0.444278] pci :05:00.0: bridge window [mem 0xa200-0xa20f] [0.456183] ACPI: PCI Interrupt Link [LNKA] (IRQs) *0 [0.456183] ACPI: PCI Interrupt Link [LNKB] (IRQs) *1 [0.456183] ACPI: PCI Interrupt Link [LNKC] (IRQs) *0 [0.456183] ACPI: PCI Interrupt Link [LNKD] (IRQs) *1 [0.456183] ACPI: PCI Interrupt Link [LNKE] (IRQs) *1 [0.456183] ACPI: PCI Interrupt Link [LNKF] (IRQs) *1 [0.456183] ACPI: PCI Interrupt Link [LNKG] (IRQs) *1 [0.456183] ACPI: PCI Interrupt Link [LNKH] (IRQs) *1 [0.464184] SCSI subsystem initialized [0.464186] libata version 3.00 loaded. [0.464186] pci :00:02.0: vgaarb: setting as boot VGA device [1.225495] Scanning for low memory corruption every 60 seconds [1.226265] Initialise system trusted keyrings [1.226271] Key type blacklist registered [1.226399] workingset: timestamp_bits=36 max_order=23 bucket_order=0 [1.227127] zbud: loaded [1.227482] squashfs: version 4.0 (2009/01/31) Phillip Lougher [1.227769] fuse init (API version 7.26) [1.233972] Key type asymmetric registered [1.233973] Asymmetric key parser 'x509' registered [1.233991] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246) [1.234105] io scheduler noop registered [
[Kernel-packages] [Bug 1799181] Re: Can't find my touchpad
** 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/1799181 Title: Can't find my touchpad Status in linux package in Ubuntu: Incomplete Bug description: It seems like Ubuntu 18.04 can't read my touchpad. This problem has been there since i started using ubuntu 18.10 LTS I'm currently using Ubuntu 18.04.1 LTS. Pc model: XPS 15 9560 Touchpad model: Palmrest KKD96 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tin1149 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 22 11:30:01 2018 InstallationDate: Installed on 2018-10-22 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. XPS 15 9560 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=e3ebc230-b8c9-45a6-a3a9-0ab2d8f88fda ro acpi=off quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd08/23/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799181/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799180] Re: Ubuntu 18.10 / Linux 4.19 -rc7/8 - System slows / stops
** 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/1799180 Title: Ubuntu 18.10 / Linux 4.19 -rc7/8 - System slows / stops Status in linux package in Ubuntu: Triaged Bug description: Hi there folks sorry if it's inappropriate to report a bug in an upstream release candidate kernel, but as a suggested test / fix for https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796743 I was told to install an upstream kernel, which I did. When I run with that kernel for any length of time, or do anything involving high CPU (like run Firefox for instance) the system fan begins to whine and the system slows down to the point where it finally hangs. I tried to run 'ubuntu-bug linux' from the terminal, but when I do I get the error seen in the screenshot (attached). I'll go back to running 4.18 for now because not being able to sleep the laptop isn't a show stopper, but it's definitely something I consider important for a fully fledged operating system / work environment :) Thanks and please let me know if there's anything I can do to provide more data / help with testing / etc. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-10-07 (14 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: cosmic Uname: Linux 4.19.0-041900rc8-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/1799180/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799201] Re: slow upload speed to smb / cifs
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1799201 Title: slow upload speed to smb / cifs Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: I've discussed this in the gnome nautilus section: https://gitlab.gnome.org/GNOME/nautilus/issues/695 Is it possible to backport the fix to the 4.15 kernel used in 1804? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799201/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799058] Re: Samsung S7 U3 SDCARD access locks up Nautilus
** 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/1799058 Title: Samsung S7 U3 SDCARD access locks up Nautilus Status in linux package in Ubuntu: Incomplete Bug description: Trying to attach a photo for another bug report I connected my android phone and opened up [SAMSUNG Android][Card][DCIM][Camera] and around 5 minutes of appearing to be locked up (without a single icon showing) Nautilus eventually showed some icons (none with picture thumbnail) initially. Also filed at: https://gitlab.gnome.org/GNOME/nautilus/issues/703 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scott 2470 F pulseaudio /dev/snd/controlC1: scott 2470 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 21 08:06:49 2018 GvfsMonitorError: This tool has been deprecated, use 'gio mount' instead. See 'gio help mount' for more info. HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2018-10-20 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=31f5be02-c37e-43e6-96f2-8c912726514e ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 08:07:01.469: The udisks-daemon is running (name-owner :1.8). UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH Z77 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ77:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU 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/1799058/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799066] Re: Trackpoint/trackpad unusable when trying to install 18.10 on X1 Carbon 6th
** 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/1799066 Title: Trackpoint/trackpad unusable when trying to install 18.10 on X1 Carbon 6th Status in linux package in Ubuntu: Confirmed Bug description: When running the live CD iso from a USB stick on Lenovo X1 Carbon 6th, both the trackpad and trackpoint are unresponsive. xinput reports what seems to be proper input devices: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=11 [slave pointer (2)] ⎜ ↳ TPPS/2 Elan TrackPoint id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Sleep Buttonid=8[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=9[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=10 [slave keyboard (3)] ↳ ThinkPad Extra Buttons id=12 [slave keyboard (3)] After some time of swiping my finger on the trackpad and trying to use the trackpoint, they sometimes start working. The xinput output is then slighly different: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=11 [slave pointer (2)] ⎜ ↳ PS/2 Generic Mouse id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Sleep Buttonid=8[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=9[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=10 [slave keyboard (3)] ↳ ThinkPad Extra Buttons id=12 [slave keyboard (3)] I will include the dmesg output in the comment. I will also see if trackpad and trackpoint survive a suspend (which is an issue in 18.04). I assume it's still an issue, even with 18.10's kernel. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2224 F pulseaudio CasperVersion: 1.399 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 21 16:07:43 2018 LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 13d3:56b2 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed boot=casper quiet splash --- RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006KPB 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:bvrN23ET56W(1.31):bd09/17/2018:svnLENOVO:pn20KH006KPB:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KH006KPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KH006KPB dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
[Kernel-packages] [Bug 1799118] Re: executing ubuntu-bug gives errors
** Package changed: linux (Ubuntu) => apport (Ubuntu) ** Changed in: apport (Ubuntu) Status: Confirmed => 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/1799118 Title: executing ubuntu-bug gives errors Status in apport package in Ubuntu: New Bug description: When I use ubuntu-bug I get the following errors. robert@ASUS-A88XM-A:~/Desktop$ ubuntu-bug linux (apport-gtk:581): Gtk-WARNING **: 01:00:16.903: Theme parsing error: gtk-widgets.css:3135:13: 'max-width' is not a valid property name (apport-gtk:581): Gtk-WARNING **: 01:00:16.904: Theme parsing error: gtk-widgets.css:3136:14: 'max-height' is not a valid property name robert@ASUS-A88XM-A:~/Desktop$ (google-chrome-stable:1222): Gtk-WARNING **: 01:00:33.982: Theme parsing error: gtk-widgets.css:3135:13: 'max-width' is not a valid property name (google-chrome-stable:1222): Gtk-WARNING **: 01:00:33.982: Theme parsing error: gtk-widgets.css:3136:14: 'max-height' is not a valid property name Created new window in existing browser session. Ubuntu MATE 18.04 totally crashed (I had to reinstall 18.04 just to boot). Since I was going to have to reinstall everything, I thought to check and see if 18.04 was the latest. It isn't, so I decided to try 18.10 before reinstalling everything. Unfortunately, its still very buggy. Both the Software Botique and the Software app are buggy. With the Software app down, I can't even try to load Eclipse - which is in the 18.04 Software app. When I try to report bugs with ubuntu-bug, I get yet more bugs. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 3464 F pulseaudio /dev/snd/controlC0: robert 3464 F pulseaudio CurrentDesktop: MATE Date: Mon Oct 22 01:00:17 2018 InstallationDate: Installed on 2018-10-22 (0 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=7057e77c-c1e8-4bf5-9810-7609aceb50a0 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A 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.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1799118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799276] Re: [Bionic] ipmi: Remove ACPI SPMI probing from the SSIF (I2C) driver
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1799276
Title:
[Bionic] ipmi: Remove ACPI SPMI probing from the SSIF (I2C) driver
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Bionic:
Triaged
Bug description:
[Impact]
The IPMI spec states:
The purpose of the SPMI Table is to provide a mechanism that can be
used by the OSPM (an ACPI term for “OS Operating System-directed
configuration and Power Management” essentially meaning an ACPI-aware
OS or OS loader) very early in the boot process, e.g., before the
ability to execute ACPI control methods in the OS is available.
When we are probing IPMI in Linux, ACPI control methods are available,
so we shouldn't be probing using SPMI. It could cause some confusion
during the probing process.
[Fix]
Fixed upstream in 4.17:
commit 4866b1dce0389013a268f0ab63f7229b30c6e5fe
Author: Corey Minyard
Date: Thu Mar 8 15:00:28 2018 -0600
ipmi: Remove ACPI SPMI probing from the SSIF (I2C) driver
[Test]
-- Test case --
for i in {1..500}; do sudo modprobe -r ipmi_ssif; sleep 2s ; sudo modprobe
ipmi_ssif || exit; done
--
-- Before Applying the patch --
Jun 19 18:53:04 starbuck kernel: [ 126.351580] ipmi_ssif 0-000e: Found new
BMC (man_id: 0x00, prod_id: 0x0202, dev_id: 0x20)
Jun 19 18:53:06 starbuck kernel: [ 128.725391] ipmi_ssif: probe of
dmi-ipmi-ssif.1 failed with error -17
-- With patch applied --
Oct 19 19:59:49 starbuck kernel: [ 1501.699109] IPMI SSIF Interface driver
Oct 19 19:59:49 starbuck kernel: [ 1501.730439] ipmi_ssif: Trying
SMBIOS-specified SSIF interface at i2c address 0xe, adapter xlp9xx-i2c, slave
address 0x20
Oct 19 19:59:49 starbuck kernel: [ 1501.862509] ipmi_ssif 0-000e: Found new
BMC (man_id: 0x00, prod_id: 0x0202, dev_id: 0x20)
[Regression Potential]
This patch applies to ipmi_ssif driver and was tested on ARM64 Cavium
ThunderX2 platform and no regressions were found.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799276/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799281] Re: [Bionic][Cosmic] ipmi: Fix timer race with module unload
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Cosmic)
Importance: Critical
Assignee: Canonical Kernel Team (canonical-kernel-team)
Status: Triaged
** Changed in: linux (Ubuntu Bionic)
Status: New => Triaged
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1799281
Title:
[Bionic][Cosmic] ipmi: Fix timer race with module unload
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:
[Impact]
If you attempt to remove and insert the ipmi_ssif module a number of times,
it would result in a kernel panic. This is due to mod_timer from arming a timer
that was already removed by del_timer during module unload.
[Fix]
In linux-next:
0711e8c1b457 ipmi: Fix timer race with module unload
[Test]
-- Test Case --
for i in {1..500}; do sudo modprobe -r ipmi_ssif; sleep 2s ; sudo modprobe
ipmi_ssif || exit; done
After the patch was applied, no kernel panics were obsereved. Tested on
Cavium ThunderX2.
[Regression Risk]
The patch was applied to bionic and tested tested on a Cavium ThunderX2 and
no regressions were found. Risk of regression none.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799281/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798863] Re: 18.10 kernel does not appear to validate kernel module signatures correctly
This could be a duplicate of bug 1798940 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Cosmic) Importance: Medium Status: 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/1798863 Title: 18.10 kernel does not appear to validate kernel module signatures correctly Status in linux package in Ubuntu: Incomplete Status in linux source package in Cosmic: Incomplete Bug description: On a system with Ubuntu 18.10, with secure boot enabled, and a key enrolled in the MOK database, I am observing the following peculiar behaviors: * Signature verification appears to be disabled, and cannot be enabled again. It appeared to be enabled previously, as loading of unsigned modules was failing, and `mokutil --enable-validation` runs without incident; however, upon the next boot when attempting to confirm the change, MokManager prints an error message "Unable to delete Secure Boot state" after completing the password challenge. * As a result of signature verification being disabled, modules signed with untrusted keys taint the kernel instead of failing to load outright. * Regardless of signature verification being enabled or not, it seems that the key enrolled in the MOK is not being used for validating kernel module signatures. Modules signed with the key still fail the signature verification test and taint the kernel, even though the key is visible in the output of `mokutil --list-enrolled`, and testing the key with `mokutil --test-key` shows that it's enrolled. Also, a message acknowledging the key appears in dmesg: Loaded UEFI:MokListRT cert 'nvidia-installer generated signing key: 90c957eb56dfb04d8734d54fb614ef5af6c69318' linked to secondary sys keyring * Also, somewhat strangely, in this state with module signature verification not being enforced, attempting to load a completely unsigned kernel module suceeds, and doesn't even log a kernel message about a missing/invalid signature, or taint the kernel. Apport report attached, which includes dmesg log showing the kernel acknowledging the key enrolled in the MOK database, and a signature verification failure and subsequent successful loading of a module signed with that key: [4.234093] Loaded UEFI:MokListRT cert 'nvidia-installer generated signing key: 90c957eb56dfb04d8734d54fb614ef5af6c69318' linked to secondary sys keyring ... [6.628452] nvidia: module verification failed: signature and/or required key missing - tainting kernel ... [6.637252] nvidia-nvlink: Nvlink Core is being initialized, major device number 238 [6.637507] nvidia :01:00.0: enabling device (0006 -> 0007) [6.637620] nvidia :01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none [6.737216] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 410.66 Wed Oct 10 12:01:53 CDT 2018 (using threaded interrupts) This system dual-boots Ubuntu 18.04 and Ubuntu 18.10: when booted into Ubuntu 18.04, signatures made with the same key are recognized as valid. Hence, I suspect that something changed in the Ubuntu 18.10 kernel which is causing signature verification to function in an unexpected way. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797143] Re: arm64: snapdragon: WARNING: CPU: 0 PID: 1 at drivers/irqchip/irq-gic.c:1016 gic_irq_domain_translate
** Changed in: linux (Ubuntu Cosmic)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1797143
Title:
arm64: snapdragon: WARNING: CPU: 0 PID: 1 at drivers/irqchip/irq-
gic.c:1016 gic_irq_domain_translate
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Bug description:
Impact:
During boot on a Dragonboard410c using a recent Cosmic kernel:
...
[0.071535] WARNING: CPU: 0 PID: 1 at drivers/irqchip/irq-gic.c:1016
gic_irq_domain_translate+0xe4/0xf0
[0.071541] Modules linked in:
[0.071552] CPU: 0 PID: 1 Comm: swapper/0 Tainted: GW
4.18.0-8-snapdragon #9
[0.071558] Hardware name: Qualcomm Technologies, Inc. APQ 8016 SBC (DT)
[0.071566] pstate: 6045 (nZCv daif +PAN -UAO)
[0.071575] pc : gic_irq_domain_translate+0xe4/0xf0
[0.071582] lr : gic_irq_domain_alloc+0x58/0xc0
[0.071588] sp : 080337d0
[0.071594] x29: 080337d0 x28:
[0.071604] x27: 08033938 x26: 0001
[0.071615] x25: 006080c0 x24: 09a6ef70
[0.071625] x23: 09a48708 x22: 0025
[0.071636] x21: 0803384c x20: 08033850
[0.071647] x19: 08033938 x18: 0001
[0.071658] x17: x16:
[0.071668] x15: x14: 09a48708
[0.071679] x13: 80003a4c2703 x12: 0038
[0.071690] x11: 0101010101010101 x10: 0040
[0.071700] x9 : 09a6e9d8 x8 : 80003b0016f8
[0.071710] x7 : x6 : 80003b0016d0
[0.071721] x5 : 80003b001820 x4 : 0857b4f8
[0.071731] x3 : 0803384c x2 :
[0.071741] x1 : 0057 x0 :
[0.071751] Call trace:
[0.071759] gic_irq_domain_translate+0xe4/0xf0
[0.071767] gic_irq_domain_alloc+0x58/0xc0
[0.071777] __irq_domain_alloc_irqs+0x150/0x338
[0.071786] irq_create_fwspec_mapping+0x118/0x318
[0.071794] irq_create_of_mapping+0x7c/0xa8
[0.071803] of_irq_get+0x88/0xe0
[0.071812] of_irq_to_resource+0x48/0x108
[0.071821] of_irq_to_resource_table+0x54/0x70
[0.071829] of_device_alloc+0x110/0x1e0
[0.071837] of_platform_device_create_pdata+0x60/0xe0
[0.071846] of_platform_bus_create+0x2bc/0x4b0
[0.071854] of_platform_bus_create+0x31c/0x4b0
[0.071862] of_platform_populate+0x8c/0x140
[0.071872] of_platform_default_populate_init+0xb4/0xd0
[0.071880] do_one_initcall+0x54/0x1e0
[0.071890] kernel_init_freeable+0x254/0x2f8
[0.071898] kernel_init+0x18/0x110
[0.071907] ret_from_fork+0x10/0x18
[0.071913] ---[ end trace dc768b294fafe4b4 ]---
...
remove the usage of IRQ_TYPE_NONE to fix loud warnings from
patch (83a86fbb5b56b "irqchip/gic: Loudly complain about
the use of IRQ_TYPE_NONE").
The same was done in commit 242579dd0829 ("arm64: dts: msm8996: fix
gic_irq_domain_translate warnings") and commit c16e78b8e862("arm64:
dts: msm8916: fix gic_irq_domain_translate warnings") upstream, so fix
the same issue in our forward-ported Qualcomm BSP code.
Fix:
Apply the attached patch and recompile
How to test:
Boot the patched kernel and check for the above WARNING in dmesg
Regression potential:
None, it's mechanical modification to silence a WARNING
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797143/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798934] Re: Keyboard/tochpad issues
** 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/1798934 Title: Keyboard/tochpad issues Status in linux package in Ubuntu: Incomplete Bug description: I have been running Unbuntu 18 for some time now. Everything works great. But I do have a few issues. Acer Aspire E3-111 with 8MB DDR3 L Memory. #1 Keyboards seems to lose its mapping. Backspace/Del and arrow keys seem to not work sometimes. I might use the "FN' with Arrow up/Volume up. But only sometimes. #2 My Touchpad will stop working all of the sudden. So I have a USB wireless mouse and it always works. From time to time the mouse might start working again. I have wanted to do a clean install to see if the problems continue, however, I am unable to. For some reason after installing Ubuntu, I am not able to access the Bios. Somehow an Admin password has been set. I found a site https://bios-pw.org/ that I can get a key and I can access however it will not let me chance boot options and save. So I am unable to boot from USB or USB-CDRom. I wish I knew how to flash the Bios. The only way that I found is to create a Windows 10 boot USB and upgrade. But I cannot boot from USB :). is there a way to install/Factory Reset, over Ubuntu from with in? Kind of a clean install? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-36-generic 4.15.0-36.39 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benjamin 3908 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Oct 19 23:25:07 2018 InstallationDate: Installed on 2017-11-13 (340 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Acer Aspire E3-111 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=153127f8-254f-4133-975b-4a08f470f5f9 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-05-12 (160 days ago) dmi.bios.date: 04/11/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Roxy dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd04/11/2014:svnAcer:pnAspireE3-111:pvrV1.05:rvnAcer:rnRoxy:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: Aspire E3-111 dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798934/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798880] Re: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1798880 Title: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Status in linux package in Ubuntu: Triaged Bug description: [ 1276.702446] pcieport :00:1c.5: AER: Corrected error received: :00:1c.5 [ 1276.702457] pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 1276.702466] pcieport :00:1c.5: device [8086:a115] error status/mask=0001/2000 [ 1276.702472] pcieport :00:1c.5:[ 0] Receiver Error (First) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lenge 2188 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Oct 20 02:43:17 2018 MachineType: HP OMEN by HP Laptop ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=403be5e5-0af1-478d-a476-d3ba180f4c3c ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.36 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8259 dmi.board.vendor: HP dmi.board.version: 83.46 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.36:bd04/07/2017:svnHP:pnOMENbyHPLaptop:pvrType1ProductConfigId:rvnHP:rn8259:rvr83.46:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Omen dmi.product.name: OMEN by HP Laptop dmi.product.sku: 1DE85PA#AB2 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798880/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798921] Re: sky2 ethernet card don't work after returning from suspension
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 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.19 ** 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/1798921 Title: sky2 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Incomplete Bug description: Bug very similar to #1752772 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772) but affecting the sky2 driver instead of r8169. After system suspend the ethernet connection stops working. The card is still up and the modem can see it is connected, but the card doesn't get an ip address. Ifconfig down/up and restarting network- manager does not solve the issue. Similarly to the other bug, "sudo modprobe sky2 -r" an then "sudo modprobe sky2" solves the issue. Relevant: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/comments/107 Linux 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux *-network description: Ethernet interface product: 88E8040 PCI-E Fast Ethernet Controller vendor: Marvell Technology Group Ltd. physical id: 0 bus info: pci@:09:00.0 logical name: enp9s0 version: 13 serial: 00:23:ae:ea:23:3e size: 100Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.30 duplex=full latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s resources: irq:24 memory:f68fc000-f68f ioport:de00(size=256) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798427] Re: kvm doesn't work on 36 physical bits systems
** Changed in: linux (Ubuntu Cosmic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1798427
Title:
kvm doesn't work on 36 physical bits systems
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Bug description:
[Impact]
A guest will hang while booting under 4.18.0-10.11 because of "kvm: x86: Set
highest physical address bits in non-present/reserved SPTEs", which came in via
4.18.y.
[Test Case]
A guest was booted after applying the patch.
[Regression Potential]
It might break KVM on systems with different physical memory limits, which is
just what upstream might have been testing the most.
A fix is already upstream, and already present in 4.18.14.
This would be upstream commit
daa07cbc9ae3da2d61b7ce900c0b9107d134f2c1 ("KVM: x86: fix L1TF's MMIO GFN
calculation").
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798427/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798940] Re: PKCS#7 signature not signed with a trusted key
This could be a duplicate of bug 1798863 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Cosmic) Importance: Medium Status: 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/1798940 Title: PKCS#7 signature not signed with a trusted key Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: executing: '"/lib/modules/4.18.0-10-generic/build/scripts/sign-file" "sha512" "/var/lib/shim-signed/mok/MOK.priv" "/var/lib/shim-signed/mok/MOK.der" "./kernel/nvidia.ko"'... ... executing: '"/lib/modules/4.18.0-10-generic/build/scripts/sign-file" "sha512" "/var/lib/shim-signed/mok/MOK.priv" "/var/lib/shim-signed/mok/MOK.der" "./kernel/nvidia-uvm.ko"'... nvidia drivers had been signed at install, and lenge@hp-15:/lenge/linux$ mokutil --test-key /var/lib/shim-signed/mok/MOK.der /var/lib/shim-signed/mok/MOK.der is already enrolled ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lenge 2130 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Oct 20 15:55:57 2018 MachineType: HP OMEN by HP Laptop ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=403be5e5-0af1-478d-a476-d3ba180f4c3c ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.36 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8259 dmi.board.vendor: HP dmi.board.version: 83.46 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.36:bd04/07/2017:svnHP:pnOMENbyHPLaptop:pvrType1ProductConfigId:rvnHP:rn8259:rvr83.46:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Omen dmi.product.name: OMEN by HP Laptop dmi.product.sku: 1DE85PA#AB2 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798979] Re: Hama "Slim" USB 3.0 Multi Card Reader doesn't work
** 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/1798979 Title: Hama "Slim" USB 3.0 Multi Card Reader doesn't work Status in linux package in Ubuntu: Confirmed Bug description: I have problems with Hama "Slim" USB 3.0 Multi Card Reader (model number 00114837, https://www.hama.com/00114837/hama-slim-usb-30-multi- card-reader-black) attached to a USB 3.0. After attaching the reader (or booting the system) the device works for some time, about a minute or so. It's blue power led is on. Then CPU load goes up to 30-50% and the power led on the reader starts turning off and on with a several seconds interval. It looks like the device is being repeatedly reinitialized. dmesg shows these lines while this is happening: [ 147.251654] xhci_hcd :05:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state. [ 147.447251] xhci_hcd :05:00.0: WARN Event TRB for slot 1 ep 4 with no TDs queued? [ 220.546280] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [ 220.546283] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [ 220.685727] usb 6-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd [ 251.266583] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [ 251.266584] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [ 251.398028] usb 6-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd [ 284.045003] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [ 284.045006] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [ 284.180500] usb 6-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd [ 314.761869] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [ 314.761873] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [ 314.893338] usb 6-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd and so on. No cards are inserted in the device and no user activity on the system, the problem starts happening "on its own". I tried plugging the device in a different USB 3.0 slot, it doesn't help. The device worked on the same system in Kubuntu 18.04, linux kernel 4.15. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-generic 4.18.0.10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: lastique 3112 F pulseaudio /dev/snd/controlC1: lastique 3112 F pulseaudio CurrentDesktop: KDE Date: Sat Oct 20 19:31:35 2018 InstallationDate: Installed on 2015-05-01 (1267 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: System manufacturer System Product Name ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf nomdmonisw vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-20 (0 days ago) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU 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/1798979/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Dd-series) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: High Status: Triaged ** Changed in: linux (Ubuntu Dd-series) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Dd-series) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798961 Title: Random unrecoverable freezes on Ubuntu 18.10 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Status in linux source package in DD-Series: Triaged Bug description: First thing I notice is that the mouse cursor freezes as I'm using it, then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then I try the "REISUB" command, but it doesn't do anything either. Only a hard reset works, pressing down the power button for a few seconds. How to reproduce? I couldn't figure out a consistent method. It is still random to me. Version: Ubuntu 4.18.0-10.11-generic 4.18.12 System information attached. Also happens under Arch Linux and Fedora. I've talked to another user on IRC who seems to be having the same freezes. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dsilva 1213 F pulseaudio /dev/snd/controlC0: dsilva 1213 F pulseaudio CurrentDesktop: XFCE Date: Sat Oct 20 09:54:50 2018 InstallationDate: Installed on 2018-10-20 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Dell Inc. Inspiron 5458 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 09WGNT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799049] Re: [bionic]mlx5: reading SW stats through ifstat cause kernel crash
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799049 Title: [bionic]mlx5: reading SW stats through ifstat cause kernel crash Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Description of problem: Attempting to read SW stats (ifstat -x cpu_hit) on a system with probed VFs will crash the system. How reproducible: Always Steps to Reproduce: 1. Create a VF echo 1 > /sys/bus/pci/devices/\:82\:00.0/sriov_numvfs 2. read SW stats: ifstat -x cpu_hit Actual results: System will crash Expected results: No system crash Additional info: The reason for the crash is insufficient check on the helper that determines if a netdev is vf rep. will crash: $ ifstat -x cpu_hit will not crash: $ ifstat -x cpu_hit $VF_REP $ ifstat -x cpu_hit $UPLINK_REP We already have a fix for this issue, and it is accepted upstream. https://patchwork.ozlabs.org/patch/935193/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799049/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799039] Re: Apple Facetime HD PCI (Broadcom 1570) not accessible
** 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/1799039 Title: Apple Facetime HD PCI (Broadcom 1570) not accessible Status in linux package in Ubuntu: Incomplete Bug description: This is a reopened bug report related to #1716673: Apple Facetime HD PCI (Broadcom 1570) not accessible The camera still is not accessible. In the old report some suggested that I should try the latest kernel. Well, with 18.10 the kernel is even newer than the one available at the time of reporting. If no one writes a driver for the camera, there will never be a module for it. The module that ships with Ubuntu is not working. I do understand that rolling out a new version is tedious. But it should be possible to a) not permanently produce regressions and b) include some improvements beyond some irrelevant GUI overhauls. btw. My machine was purchased in 2015. I don't think that PCIe is such a new technology. (sorry for my serious frustration about 18.10. I thought with 18.04 onward Canonical might have cought on) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolf 1914 F pulseaudio /dev/snd/controlC0: wolf 1914 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 21 12:00:56 2018 HibernationDevice: RESUME=UUID=539744c7-33c6-44da-a8b5-8bcf95f7845d InstallationDate: Installed on 2018-04-30 (174 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-20 (0 days ago) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799039/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799445] Re: linux: 4.18.0-11.12 -proposed tracker
** Summary changed: - linux: -proposed tracker + linux: 4.18.0-11.12 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799445 Title: linux: 4.18.0-11.12 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: Invalid 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 1799447 (linux-hwe-edge), bug 1799448 (linux-azure-edge) derivatives: bug 1799449 (linux-raspi2), bug 1799450 (linux-aws), bug 1799451 (linux-azure), bug 1799452 (linux-gcp), bug 1799453 (linux-kvm) To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799445/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)
Found something that can help. But it needs to be proved on 9370. 9360 has been added to btusb reset table right in kernel module. https://patchwork.ozlabs.org/cover/926955/ https://github.com/torvalds/linux/blob/master/drivers/bluetooth/btusb.c -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766825 Title: Bluetooth issues with Dell XPS 13 (9370) Status in Dell Sputnik: Triaged Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in linux package in Arch Linux: New Bug description: I have the following problem with my Bluetooth module on my new Dell XPS 13 (9370) with Ubuntu preinstalled. The bluetooth module gets disabled for some reason. The bluetooth devices (keyboard and mouse) just stop working in the middle of the work, the Bluetooth indicator goes away and the module is also gone in the rfkill list. To get it back working I need to reboot the machine, start the BIOS, disable the Bluetooth module and re-enable it or I have to turn the machine completely off and on again. After that, the bluetooth module is available again. That's pretty annoying. My syslog when this happens: Apr 11 12:25:45 visyu-albatross kernel: [ 2513.913725] usb 1-7: USB disconnect, device number 3 Apr 11 12:25:45 visyu-albatross acpid: input device has been disconnected, fd 22 Apr 11 12:25:46 visyu-albatross systemd[1]: Starting Load/Save RF Kill Switch Status... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Load/Save RF Kill Switch Status. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c9 of user root. Apr 11 12:25:46 visyu-albatross acpid: input device has been disconnected, fd 21 Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Startup finished in 15ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSource Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSink Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c10 of user root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Received SIGRTMIN+24 from PID 12120 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Startup finished in 14ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12123]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Received SIGRTMIN+24 from PID 12133 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11
[Kernel-packages] [Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
It would be the 4.15 based Bionic proposed kernel, which is at version: 4.15.0-38.41 Bionic proposed now has the following commit: c4748a936d6c rtlwifi: cleanup 8723be ant_sel definition That would rule out that commit as being the fix. If the bug still happens with proposed, we can continue the reverse bisect with has about 2-3 more kernels to test. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799415] Re: linux-azure: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package 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 -- kernel-stable-master-bug: 1799411 + kernel-stable-phase:Packaging + kernel-stable-phase-changed:Tuesday, 23. October 2018 16:31 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 -- kernel-stable-master-bug: 1799411 - kernel-stable-phase:Packaging - kernel-stable-phase-changed:Tuesday, 23. October 2018 16:31 UTC + phase: Packaging -- 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/1799415 Title: linux-azure: -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: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow stakeholder-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-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 -- kernel-stable-master-bug: 1799411 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799415/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799424] Re: linux-gcp: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package 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 -- kernel-stable-master-bug: 1799411 + kernel-stable-phase:Packaging + kernel-stable-phase-changed:Tuesday, 23. October 2018 16:30 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 -- kernel-stable-master-bug: 1799411 - kernel-stable-phase:Packaging - kernel-stable-phase-changed:Tuesday, 23. October 2018 16:30 UTC + phase: Packaging -- 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/1799424 Title: linux-gcp: -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: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New 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 -- kernel-stable-master-bug: 1799411 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799424/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799497] Re: 4.15 kernel hard lockup about once a week
Would you be able to test some kernels? A bisect can be done if we can identify what kernel version introduced this issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799497 Title: 4.15 kernel hard lockup about once a week Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: My main server has been running into hard lockups about once a week ever since I switched to the 4.15 Ubuntu 18.04 kernel. When this happens, nothing is printed to the console, it's effectively stuck showing a login prompt. The system is running with panic=1 on the cmdline but isn't rebooting so the kernel isn't even processing this as a kernel panic. As this felt like a potential hardware issue, I had my hosting provider give me a completely different system, different motherboard, different CPU, different RAM and different storage, I installed that system on 18.04 and moved my data over, a week later, I hit the issue again. We've since also had a LXD user reporting similar symptoms here also on varying hardware: https://github.com/lxc/lxd/issues/5197 My system doesn't have a lot of memory pressure with about 50% of free memory: root@vorash:~# free -m totalusedfree shared buff/cache available Mem: 31819 17574 402 513 13842 13292 Swap: 159092687 13222 I will now try to increase console logging as much as possible on the system in the hopes that next time it hangs we can get a better idea of what happened but I'm not too hopeful given the complete silence on the console when this occurs. System is currently on: Linux vorash 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux But I've seen this since the GA kernel on 4.15 so it's not a recent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799497/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799497] 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 1799497 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 ** Changed in: linux (Ubuntu Bionic) 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/1799497 Title: 4.15 kernel hard lockup about once a week Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: My main server has been running into hard lockups about once a week ever since I switched to the 4.15 Ubuntu 18.04 kernel. When this happens, nothing is printed to the console, it's effectively stuck showing a login prompt. The system is running with panic=1 on the cmdline but isn't rebooting so the kernel isn't even processing this as a kernel panic. As this felt like a potential hardware issue, I had my hosting provider give me a completely different system, different motherboard, different CPU, different RAM and different storage, I installed that system on 18.04 and moved my data over, a week later, I hit the issue again. We've since also had a LXD user reporting similar symptoms here also on varying hardware: https://github.com/lxc/lxd/issues/5197 My system doesn't have a lot of memory pressure with about 50% of free memory: root@vorash:~# free -m totalusedfree shared buff/cache available Mem: 31819 17574 402 513 13842 13292 Swap: 159092687 13222 I will now try to increase console logging as much as possible on the system in the hopes that next time it hangs we can get a better idea of what happened but I'm not too hopeful given the complete silence on the console when this occurs. System is currently on: Linux vorash 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux But I've seen this since the GA kernel on 4.15 so it's not a recent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799497/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799497] Re: 4.15 kernel hard lockup about once a week
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Tags added: bionic kernel-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/1799497 Title: 4.15 kernel hard lockup about once a week Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: My main server has been running into hard lockups about once a week ever since I switched to the 4.15 Ubuntu 18.04 kernel. When this happens, nothing is printed to the console, it's effectively stuck showing a login prompt. The system is running with panic=1 on the cmdline but isn't rebooting so the kernel isn't even processing this as a kernel panic. As this felt like a potential hardware issue, I had my hosting provider give me a completely different system, different motherboard, different CPU, different RAM and different storage, I installed that system on 18.04 and moved my data over, a week later, I hit the issue again. We've since also had a LXD user reporting similar symptoms here also on varying hardware: https://github.com/lxc/lxd/issues/5197 My system doesn't have a lot of memory pressure with about 50% of free memory: root@vorash:~# free -m totalusedfree shared buff/cache available Mem: 31819 17574 402 513 13842 13292 Swap: 159092687 13222 I will now try to increase console logging as much as possible on the system in the hopes that next time it hangs we can get a better idea of what happened but I'm not too hopeful given the complete silence on the console when this occurs. System is currently on: Linux vorash 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux But I've seen this since the GA kernel on 4.15 so it's not a recent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799497/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781879] Re: Latest ASUS trackpad doesn't work in Ubuntu
Added kernel-fixed-upstream as it now is with the released 4.19 ** Tags added: kernel-fixed-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/1781879 Title: Latest ASUS trackpad doesn't work in Ubuntu Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: It seems there might be a new hardware variant of the elan trackpad in the newer ASUS machines. The issue is the shown here with some reasonably deep investigation. Is this something that I can do or am I reduced to having to find out a mouse if I want to use Linux? https://www.asus.com/us/Laptops/ASUS-TUF-Gaming-FX504/specifications/ user@TUF-GAMING-FX504GD-FX80GD:~$ xinput Virtual core pointer id=2[master pointer (3)] ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ↳ Logitech USB Receiver id=12 [slave pointer (2)] ↳ Logitech USB Receiver id=13 [slave pointer (2)] Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Asus Wireless Radio Control id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Video Bus id=9[slave keyboard (3)] ↳ Power Button id=10 [slave keyboard (3)] ↳ Sleep Button id=11 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=14 [slave keyboard (3)] ↳ Asus WMI hotkeys id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=16 [slave keyboard (3)] ↳ Logitech USB Receiver id=17 [slave keyboard (3)] To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1781879/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)
Kai-Heng Feng, I have XPS 9370. It uses Killer 1435 Anthony Wong, I've already tried. No success :( Still experiencing the same issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766825 Title: Bluetooth issues with Dell XPS 13 (9370) Status in Dell Sputnik: Triaged Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in linux package in Arch Linux: New Bug description: I have the following problem with my Bluetooth module on my new Dell XPS 13 (9370) with Ubuntu preinstalled. The bluetooth module gets disabled for some reason. The bluetooth devices (keyboard and mouse) just stop working in the middle of the work, the Bluetooth indicator goes away and the module is also gone in the rfkill list. To get it back working I need to reboot the machine, start the BIOS, disable the Bluetooth module and re-enable it or I have to turn the machine completely off and on again. After that, the bluetooth module is available again. That's pretty annoying. My syslog when this happens: Apr 11 12:25:45 visyu-albatross kernel: [ 2513.913725] usb 1-7: USB disconnect, device number 3 Apr 11 12:25:45 visyu-albatross acpid: input device has been disconnected, fd 22 Apr 11 12:25:46 visyu-albatross systemd[1]: Starting Load/Save RF Kill Switch Status... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Load/Save RF Kill Switch Status. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c9 of user root. Apr 11 12:25:46 visyu-albatross acpid: input device has been disconnected, fd 21 Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Startup finished in 15ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSource Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSink Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c10 of user root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Received SIGRTMIN+24 from PID 12120 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Startup finished in 14ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12123]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Received SIGRTMIN+24 from PID 12133 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c11 of user root. Apr 11 12:25:46 visyu-albatross
[Kernel-packages] [Bug 1799235] Re: kworker process starts at 85% of cpu and stays there
There's a BIOS update for this system, it might solve the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799235 Title: kworker process starts at 85% of cpu and stays there Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu starts, w/ /sbin/init, a kworker process that never stops running below 85%: pb@pb-tower:~/Downloads$ ps -elf F S UIDPID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD 4 S root 1 0 0 80 0 - 56471 - 18:30 ?00:00:01 /sbin/init splash 1 S root 2 0 0 80 0 - 0 - 18:30 ?00:00:00 [kthreadd] 1 R root85 2 63 80 0 - 0 - 18:30 ? 00:03:03 [kworker/0:1+kac] After a few hours, grep . -r /sys/firmware/acpi/interrupts/ shows tens of millions of interrupts. The following command line stops the kworker process: echo "disable" > /sys/firmware/acpi/interrupts/gpe6F On the other hand, I haven't been able to properly shut down my system after this command (power never goes off except manually). I believe the bug is related to the one discussed here: https://superuser.com/questions/1117992/acpi-exception-ae-not-found- while-evaluating-gpe-method-floods-syslog The dmesg w/ this report may be somewhat confusing because there is an unsigned module. But w/ the module removed, dmesg gives the following: [0.097480] ACPI: Dynamic OEM Table Load: [0.097480] ACPI: SSDT 0xA07F57173000 000317 (v02 PmRef ApHwp 3000 INTL 20160527) [0.097480] ACPI: Executed 1 blocks of module-level executable AML code [0.100180] ACPI: Dynamic OEM Table Load: [0.100186] ACPI: SSDT 0xA07F577EF400 00030A (v02 PmRef ApCst 3000 INTL 20160527) [0.100473] ACPI: Executed 1 blocks of module-level executable AML code [0.102187] ACPI: Interpreter enabled [0.10] ACPI: (supports S0 S3 S4 S5) [0.102223] ACPI: Using IOAPIC for interrupt routing [0.102275] HEST: Table parsing has been initialized. [0.102277] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [0.103580] ACPI: GPE 0x20 active on init [0.104031] ACPI Error: No handler for Region [WST1] ((ptrval)) [GenericSerialBus] (20170831/evregion-166) [0.104035] ACPI Error: Region GenericSerialBus (ID=9) has no handler (20170831/exfldio-299) [0.104040] Initialized Local Variables for Method [PAS1]: [0.104041] Local0: (ptrval)Integer 0001 [0.104045] No Arguments are initialized for method [PAS1] [0.104046] ACPI Error: Method parse/execution failed \_SB.PCI0.I2C0.PAS1, AE_NOT_EXIST (20170831/psparse-550) [0.104052] ACPI Error: Method parse/execution failed \_GPE._L20, AE_NOT_EXIST (20170831/psparse-550) [0.104058] ACPI Exception: AE_NOT_EXIST, while evaluating GPE method [_L20] (20170831/evgpe-646) [0.104005] ACPI: GPE 0x6F active on init [0.104005] ACPI: Enabled 10 GPEs in block 00 to 7F [0.212126] ACPI: Power Resource [USBC] (on) [0.444270] pci :06:00.0: PME# supported from D0 D1 D2 D3hot [0.444270] pci :06:00.1: [1033:00e0] type 00 class 0x0c0320 [0.444270] pci :06:00.1: reg 0x10: [mem 0xa200-0xa2ff] [0.444278] pci :06:00.1: supports D1 D2 [0.444278] pci :06:00.1: PME# supported from D0 D1 D2 D3hot [0.444278] pci :05:00.0: PCI bridge to [bus 06] [0.444278] pci :05:00.0: bridge window [mem 0xa200-0xa20f] [0.456183] ACPI: PCI Interrupt Link [LNKA] (IRQs) *0 [0.456183] ACPI: PCI Interrupt Link [LNKB] (IRQs) *1 [0.456183] ACPI: PCI Interrupt Link [LNKC] (IRQs) *0 [0.456183] ACPI: PCI Interrupt Link [LNKD] (IRQs) *1 [0.456183] ACPI: PCI Interrupt Link [LNKE] (IRQs) *1 [0.456183] ACPI: PCI Interrupt Link [LNKF] (IRQs) *1 [0.456183] ACPI: PCI Interrupt Link [LNKG] (IRQs) *1 [0.456183] ACPI: PCI Interrupt Link [LNKH] (IRQs) *1 [0.464184] SCSI subsystem initialized [0.464186] libata version 3.00 loaded. [0.464186] pci :00:02.0: vgaarb: setting as boot VGA device [1.225495] Scanning for low memory corruption every 60 seconds [1.226265] Initialise system trusted keyrings [1.226271] Key type blacklist registered [1.226399] workingset: timestamp_bits=36 max_order=23 bucket_order=0 [1.227127] zbud: loaded [1.227482] squashfs: version 4.0 (2009/01/31) Phillip Lougher [1.227769] fuse init (API version 7.26) [1.233972] Key type asymmetric registered [1.233973] Asymmetric key parser 'x509' registered [1.233991] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246) [1.234105] io scheduler noop registered [
[Kernel-packages] [Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
Do you mean linux-image-4.18.0-8-generic/bionic-proposed 4.18.0-8.9~18.04.1 amd64 ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799411] Re: linux: 4.15.0-39.42 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1799421 (linux-azure), bug 1799422 (linux-azure), bug 1799423 (linux-azure-edge), bug 1799424 (linux-gcp), bug 1799425 (linux-hwe), bug 1799426 (linux-hwe-edge) derivatives: bug 1799412 (linux-raspi2), bug 1799413 (linux-oem), bug 1799414 (linux-aws), bug 1799415 (linux-azure), bug 1799416 (linux-gcp), bug 1799417 (linux-kvm) + kernel-stable-phase-changed:Tuesday, 23. October 2018 16:06 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1799421 (linux-azure), bug 1799422 (linux-azure), bug 1799423 (linux-azure-edge), bug 1799424 (linux-gcp), bug 1799425 (linux-hwe), bug 1799426 (linux-hwe-edge) derivatives: bug 1799412 (linux-raspi2), bug 1799413 (linux-oem), bug 1799414 (linux-aws), bug 1799415 (linux-azure), bug 1799416 (linux-gcp), bug 1799417 (linux-kvm) kernel-stable-phase-changed:Tuesday, 23. October 2018 16:06 UTC kernel-stable-phase:Uploaded + + -- swm properties -- + phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799411 Title: linux: 4.15.0-39.42 -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: New 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux 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 backports: bug 1799421 (linux-azure), bug 1799422 (linux-azure), bug 1799423 (linux-azure-edge), bug 1799424 (linux-gcp), bug 1799425 (linux-hwe), bug 1799426 (linux-hwe-edge) derivatives: bug 1799412 (linux-raspi2), bug 1799413 (linux-oem), bug 1799414 (linux-aws), bug 1799415 (linux-azure), bug 1799416 (linux-gcp), bug 1799417 (linux-kvm) kernel-stable-phase-changed:Tuesday, 23. October 2018 16:06 UTC kernel-stable-phase:Uploaded -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799414] Re: linux-aws: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package 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 -- kernel-stable-master-bug: 1799411 + kernel-stable-phase-changed:Tuesday, 23. October 2018 16:07 UTC + kernel-stable-phase:Packaging ** 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 -- kernel-stable-master-bug: 1799411 - kernel-stable-phase-changed:Tuesday, 23. October 2018 16:07 UTC - kernel-stable-phase:Packaging + phase: Packaging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1799414 Title: linux-aws: -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: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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 -- kernel-stable-master-bug: 1799411 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799414/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799413] Re: linux-oem: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package 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 -- kernel-stable-master-bug: 1799411 + kernel-stable-phase-changed:Tuesday, 23. October 2018 16:10 UTC + kernel-stable-phase:Packaging ** 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 -- kernel-stable-master-bug: 1799411 - kernel-stable-phase-changed:Tuesday, 23. October 2018 16:10 UTC - kernel-stable-phase:Packaging + phase: Packaging -- 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/1799413 Title: linux-oem: -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New 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 -- kernel-stable-master-bug: 1799411 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799413/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799421] Re: linux-azure: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package 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 -- kernel-stable-master-bug: 1799411 + kernel-stable-phase-changed:Tuesday, 23. October 2018 16:09 UTC + kernel-stable-phase:Packaging ** 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 -- kernel-stable-master-bug: 1799411 - kernel-stable-phase-changed:Tuesday, 23. October 2018 16:09 UTC - kernel-stable-phase:Packaging + phase: Packaging -- 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/1799421 Title: linux-azure: -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: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New 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 stakeholder-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-azure package in Ubuntu: Invalid Status in linux-azure 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 -- swm properties -- kernel-stable-master-bug: 1799411 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799421/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799417] Re: linux-kvm: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package 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 -- kernel-stable-master-bug: 1799411 + kernel-stable-phase-changed:Tuesday, 23. October 2018 16:08 UTC + kernel-stable-phase:Packaging ** 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 -- kernel-stable-master-bug: 1799411 - kernel-stable-phase-changed:Tuesday, 23. October 2018 16:08 UTC - kernel-stable-phase:Packaging + phase: Packaging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1799417 Title: linux-kvm: -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: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New 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-kvm package in Ubuntu: Invalid Status in linux-kvm 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 -- kernel-stable-master-bug: 1799411 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799417/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799416] Re: linux-gcp: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package 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 -- kernel-stable-master-bug: 1799411 + kernel-stable-phase-changed:Tuesday, 23. October 2018 16:08 UTC + kernel-stable-phase:Packaging ** 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 -- kernel-stable-master-bug: 1799411 - kernel-stable-phase-changed:Tuesday, 23. October 2018 16:08 UTC - kernel-stable-phase:Packaging + phase: Packaging -- 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/1799416 Title: linux-gcp: -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: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp 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 -- kernel-stable-master-bug: 1799411 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799422] Re: linux-azure: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package 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 -- kernel-stable-master-bug: 1799411 + kernel-stable-phase-changed:Tuesday, 23. October 2018 16:09 UTC + kernel-stable-phase:Packaging ** 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 -- kernel-stable-master-bug: 1799411 - kernel-stable-phase-changed:Tuesday, 23. October 2018 16:09 UTC - kernel-stable-phase:Packaging + phase: Packaging -- 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/1799422 Title: linux-azure: -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: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow stakeholder-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-azure package in Ubuntu: Invalid Status in linux-azure 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 -- kernel-stable-master-bug: 1799411 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799422/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799497] [NEW] 4.15 kernel hard lockup about once a week
Public bug reported: My main server has been running into hard lockups about once a week ever since I switched to the 4.15 Ubuntu 18.04 kernel. When this happens, nothing is printed to the console, it's effectively stuck showing a login prompt. The system is running with panic=1 on the cmdline but isn't rebooting so the kernel isn't even processing this as a kernel panic. As this felt like a potential hardware issue, I had my hosting provider give me a completely different system, different motherboard, different CPU, different RAM and different storage, I installed that system on 18.04 and moved my data over, a week later, I hit the issue again. We've since also had a LXD user reporting similar symptoms here also on varying hardware: https://github.com/lxc/lxd/issues/5197 My system doesn't have a lot of memory pressure with about 50% of free memory: root@vorash:~# free -m totalusedfree shared buff/cache available Mem: 31819 17574 402 513 13842 13292 Swap: 159092687 13222 I will now try to increase console logging as much as possible on the system in the hopes that next time it hangs we can get a better idea of what happened but I'm not too hopeful given the complete silence on the console when this occurs. System is currently on: Linux vorash 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux But I've seen this since the GA kernel on 4.15 so it's not a recent regression. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799497 Title: 4.15 kernel hard lockup about once a week Status in linux package in Ubuntu: New Bug description: My main server has been running into hard lockups about once a week ever since I switched to the 4.15 Ubuntu 18.04 kernel. When this happens, nothing is printed to the console, it's effectively stuck showing a login prompt. The system is running with panic=1 on the cmdline but isn't rebooting so the kernel isn't even processing this as a kernel panic. As this felt like a potential hardware issue, I had my hosting provider give me a completely different system, different motherboard, different CPU, different RAM and different storage, I installed that system on 18.04 and moved my data over, a week later, I hit the issue again. We've since also had a LXD user reporting similar symptoms here also on varying hardware: https://github.com/lxc/lxd/issues/5197 My system doesn't have a lot of memory pressure with about 50% of free memory: root@vorash:~# free -m totalusedfree shared buff/cache available Mem: 31819 17574 402 513 13842 13292 Swap: 159092687 13222 I will now try to increase console logging as much as possible on the system in the hopes that next time it hangs we can get a better idea of what happened but I'm not too hopeful given the complete silence on the console when this occurs. System is currently on: Linux vorash 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux But I've seen this since the GA kernel on 4.15 so it's not a recent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799497/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792957] Re: Provide mode where all vCPUs on a core must be the same VM
Hi Breno,
That is correct.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1792957
Title:
Provide mode where all vCPUs on a core must be the same VM
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
Status in linux source package in Cosmic:
In Progress
Bug description:
== SRU Justification ==
This patch has been requested by IBM. It provides a mode where all vCPUs
on a core must be the same VM. This is intended for use in
security-conscious settings where users are concerned about possible
side-channel attacks between threads which could perhaps enable one VM
to attack another VM on the same core, or the host.
== Fix ==
linux-next commit:
aa2278644ae5 ("KVM: PPC: Book3S HV: Provide mode where all vCPUs on a core
must be the same VM")
== Regression Potential ==
Low. Changes limited to powerpc.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Comment: #0 - Leonardo Augusto Guimaraes Garcia -
2018-09-13 07:12:48 ==
+++ This bug was initially created as a clone of Bug #171443 +++
Please, add the following patch:
http://patchwork.ozlabs.org/patch/968786/
which adds a mode where all vCPUs on a core must be the same VM on
POWER8 and POWER9.
This is intended for use in security-conscious settings where users
are concerned about possible side-channel attacks between threads
which could perhaps enable one VM to attack another VM on the same
core, or the host.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1792957/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799490] 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 1799490 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799490 Title: Kernel 4.15 boot error on XenServer Status in linux package in Ubuntu: Incomplete Bug description: I recently upgraded an ubuntu VM from 16.04.1 to 18.04.1 running on XenServer 7.1. The upgrade itself was fine, but several kernel updates after the upgrade have caused the VM to fail to boot. All kernels that fail to boot seem to be from 4.15. Current, the latest kernel I've tried is 4.15.0-38, though, day-to-day I'm running a 4.4 kernel since the VM is necessary to my environment. The error message on boot is: unchecked MSR access error: RDMSR from 0xc90 at rIP: 0x9806c04a (native_read_msr+0xa/0x30) The trace is attached as a screenshot. I haven't been able to get a log containing the output. user@host:~$ cat /proc/version_signature Ubuntu 4.4.0-112.135-generic 4.4.98 user@host:~$ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02) Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100] Physical Slot: 0 Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- [disabled] 00:03.0 SCSI storage controller [0100]: XenSource, Inc. Xen Platform Device [5853:0001] (rev 02) Subsystem: XenSource, Inc. Xen Platform Device [5853:0001] Physical Slot: 3 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799102] Re: WARNING on boot in Intel GVT-g guest
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799102 Title: WARNING on boot in Intel GVT-g guest Status in linux package in Ubuntu: Confirmed Bug description: When booting Ubuntu Cosmic Cuttlefish 18.10 in an Intel GVT-g Virtual Machine, a kernel WARNING appears in dmesg, with the following: [3.563734] WARNING: CPU: 3 PID: 346 at drivers/gpu/drm/i915/i915_irq.c:161 gen3_assert_iir_is_zero+0x38/0xa0 [i915] I have not noticed negative effects in the VM, but a kernel WARNING probably has relevance. While I added a custom EDID to fix resolution, the WARNING happens without custom EDID set too. I will add information about the host in the next message. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: User Name 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1896 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 21 19:44:44 2018 InstallationDate: Installed on 2018-10-18 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IwConfig: lono wireless extensions. ens8 no wireless extensions. Lsusb: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 46f4:0002 Bus 002 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=6cb7fc66-eb2c-4203-9d7d-2aa2665911ac ro quiet splash drm.edid_firmware=EDID_E1941.bin log_buf_len=16M vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-3.0 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.0:cvnQEMU:ct1:cvrpc-i440fx-3.0: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-3.0 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799102/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799490] Re: Kernel 4.15 boot error on XenServer
Also, I misspoke, the server is running XenServer 7.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/1799490 Title: Kernel 4.15 boot error on XenServer Status in linux package in Ubuntu: Incomplete Bug description: I recently upgraded an ubuntu VM from 16.04.1 to 18.04.1 running on XenServer 7.1. The upgrade itself was fine, but several kernel updates after the upgrade have caused the VM to fail to boot. All kernels that fail to boot seem to be from 4.15. Current, the latest kernel I've tried is 4.15.0-38, though, day-to-day I'm running a 4.4 kernel since the VM is necessary to my environment. The error message on boot is: unchecked MSR access error: RDMSR from 0xc90 at rIP: 0x9806c04a (native_read_msr+0xa/0x30) The trace is attached as a screenshot. I haven't been able to get a log containing the output. user@host:~$ cat /proc/version_signature Ubuntu 4.4.0-112.135-generic 4.4.98 user@host:~$ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02) Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100] Physical Slot: 0 Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- [disabled] 00:03.0 SCSI storage controller [0100]: XenSource, Inc. Xen Platform Device [5853:0001] (rev 02) Subsystem: XenSource, Inc. Xen Platform Device [5853:0001] Physical Slot: 3 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797139] Re: arm64: snapdragon: WARNING: CPU: 0 PID: 1 arch/arm64/kernel/setup.c:271 reserve_memblock_reserved_regions
** Changed in: linux (Ubuntu Bionic)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1797139
Title:
arm64: snapdragon: WARNING: CPU: 0 PID: 1
arch/arm64/kernel/setup.c:271 reserve_memblock_reserved_regions
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Confirmed
Bug description:
Impact:
Upon boot on a dragonboard410c using a recent Bionic or Cosmic kernel:
...
[0.049776] WARNING: CPU: 0 PID: 1 at arch/arm64/kernel/setup.c:271
reserve_memblock_reserved_regions+0xe0/0x148
[0.049783] Modules linked in:
[0.049797] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.18.0-8-snapdragon
#9
[0.049803] Hardware name: Qualcomm Technologies, Inc. APQ 8016 SBC (DT)
[0.049813] pstate: 8045 (Nzcv daif +PAN -UAO)
[0.049821] pc : reserve_memblock_reserved_regions+0xe0/0x148
[0.049829] lr : reserve_memblock_reserved_regions+0xd8/0x148
[0.049836] sp : 08033d40
[0.049841] x29: 08033d40 x28:
[0.049852] x27: 09410584 x26: 09577018
[0.049863] x25: x24: 00488020
[0.049874] x23: bfff x22: 090e8928
[0.049885] x21: 08ffb578 x20: 09a48708
[0.049896] x19: 80003a409280 x18:
[0.049906] x17: x16:
[0.049917] x15: x14: 09a48708
[0.049927] x13: x12: 0028
[0.049938] x11: 0101010101010101 x10: 7f7f7f7f7f7f7f7f
[0.049949] x9 : x8 : 80003a409300
[0.049959] x7 : x6 : 003f
[0.049969] x5 : 0040 x4 : 80003d9ffc70
[0.049980] x3 : bd9f x2 : 09c241b0
[0.049990] x1 : x0 :
[0.050001] Call trace:
[0.050010] reserve_memblock_reserved_regions+0xe0/0x148
[0.050021] do_one_initcall+0x54/0x1e0
[0.050031] kernel_init_freeable+0x254/0x2f8
[0.050043] kernel_init+0x18/0x110
[0.050052] ret_from_fork+0x10/0x18
[0.050063] ---[ end trace dc768b294fafe4aa ]---
...
commit 50d7ba36b916 upstream ("arm64: export memblock_reserve()d regions via
/proc/iomem") backported in commit 62289841 in bionic/master, wrongly assumed
that memblock_reserve() would not be used to reserve regions that aren't
memory. It turns out, this is exactly what early_init_dt_reserve_memory_arch()
will do if it finds a reservation
that was also carved out of the memory node.
Fix:
Apply the attached patch and recompile
The fix wad discussed here: https://www.spinics.net/lists/arm-
kernel/msg675580.html
How to test:
Boot the patched kernel and check for the above WARNING in dmesg
Regression potential:
The patch didn't make it upstream yet, but the fix is very small and
was tested on the lkml.
Proposing for Bionic and Cosmic.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797139/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797200] Re: [Bionic] ACPI / PPTT: use ACPI ID whenever ACPI_PPTT_ACPI_PROCESSOR_ID_VALID is set
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1797200
Title:
[Bionic] ACPI / PPTT: use ACPI ID whenever
ACPI_PPTT_ACPI_PROCESSOR_ID_VALID is set
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Committed
Bug description:
[Impact]
Currently, we use the ACPI processor ID only for the leaf/processor nodes as
the specification states it must match the value of the ACPI processor ID field
in the processor’s entry in the MADT.
However, if a PPTT structure represents a processors group, it matches
a processor container UID in the namespace and the
ACPI_PPTT_ACPI_PROCESSOR_ID_VALID flag indicates whether the ACPI
processor ID is valid.
Let's use UID whenever ACPI_PPTT_ACPI_PROCESSOR_ID_VALID is set to be
consistent instead of using table offset as it's currently done for
non-leaf nodes.
Fixes: 2bd00bcd73e5 (ACPI/PPTT: Add Processor Properties Topology
Table parsing)
[Fix]
This patch in is 4.18:
30998033f62a ACPI / PPTT: use ACPI ID whenever
ACPI_PPTT_ACPI_PROCESSOR_ID_VALID is set
[Test]
-- testcase --
#!/bin/bash
stress-ng -q --vm 100 --vm-bytes 1G --cpu 210 --timeout 2400s --metrics-brief
&
pid=$!
for i in {1..210}; do
num=$((RANDOM%10+$i))
echo "Offline CPU $num"
echo 0 > /sys/devices/system/cpu/cpu$num/online || exit 1
sleep 3s
echo "Online CPU $num"
echo 1 > /sys/devices/system/cpu/cpu$num/online || exit 1
done
kill -9 $pid
Executed the test case with stock Bionic kernel and with Bionic kernel with
patches applied. No system hang or crash was observed. On Cavium CN99XX Thunder
X2 system.
[Regression Potential]
Regression tested on Cavium Thunder X2 CN99XX system, and none were found.
Regression risk is low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797200/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797154] Re: arm64: snapdragon: reduce boot noise
** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797154 Title: arm64: snapdragon: reduce boot noise Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Incomplete Bug description: Impact: During boot on a Dragonboard410c using a recent Bionic or Cosmic kernel, there's some noise like: ... [3.665431] msm_dsi_phy 1a98300.dsi-phy: Failed to get supply 'vddio': -517 [3.669243] msm_dsi_phy 1a98300.dsi-phy: dsi_phy_regulator_init: failed to init regulator, ret=-517 [3.676180] msm_dsi_phy 1a98300.dsi-phy: dsi_phy_driver_probe: failed to init regulator ... or ... [4.192280] qcom,pm8916-wcd-spmi-codec 200f000.spmi:pm8916@1:codec@f000: Failed to get supply 'vdd-cdc-io': -517 [4.195660] qcom,pm8916-wcd-spmi-codec 200f000.spmi:pm8916@1:codec@f000: Failed to get regulator supplies -517 ... and similar. This is mainly due to DRM_MSM* and SND_QCOM_MSM* that were built-in, and tries to initialize before the voltage regulators are ready to work, resulting in a noisy bootlog. These patches factor out some code as modules, so when the kmods are loaded and initialized, regulators are already present and ready to attach - all these config changes shave around ~3K bytes from dmesg, making the bootlog easir to parse. Fix: Apply the attached patches and recompile How to test: Boot a patched kernel and check for the above noise in dmesg Regression potential: None, we are just turning some code into kmods, and turning off a couple of not used feature for this flavour - all the other flavours are untouched. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773165] Re: openvswitch-datapath-dkms kernel module is not getting loaded
Also, do you recall where you got that openvswitch-datapath-dkms from. Rmadison only reports trusty and precise versions for openvswitch- datapath-dkms. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773165 Title: openvswitch-datapath-dkms kernel module is not getting loaded Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Distributor ID: Ubuntu Description: Ubuntu 16.04.4 LTS Release: 16.04 Codename: xenial Kernel version: 4.4.0-127-generic OVS version: 2.7.0 # Issue description openvswitch-datapath-dkms kernelmodule is not getting loaded # Error from dmesg [10863.380564] openvswitch: module verification failed: signature and/or required key missing - tainting kernel [10863.381804] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) [10863.517173] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) [10878.094250] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) #Error from syslog May 24 08:37:06 dev65 kernel: [76508.361496] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) May 24 08:37:06 dev65 openvswitch-switch[18336]: modprobe: ERROR: could not insert 'openvswitch': Exec format error May 24 08:37:06 dev65 openvswitch-switch[18336]: * Inserting openvswitch module #installation logs: Selecting previously unselected package openvswitch-datapath-dkms. (Reading database ... 84707 files and directories currently installed.) Preparing to unpack openvswitch-datapath-dkms_2.7.0-1_all.deb ... Unpacking openvswitch-datapath-dkms (2.7.0-1) ... Setting up openvswitch-datapath-dkms (2.7.0-1) ... Creating symlink /var/lib/dkms/openvswitch/2.7.0/source -> /usr/src/openvswitch-2.7.0 DKMS: add completed. Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area(bad exit status: 2) ./configure --with-linux='/lib/modules/4.4.0-127-generic/build' && make -C datapath/linux.. cleaning build area(bad exit status: 2) DKMS: build completed. openvswitch: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-geneve.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-gre.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-lisp.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-stt.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-vxlan.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ depmod DKMS: install completed. #Dpkg status dpkg -l | grep openvswitch ii openvswitch-common 2.7.0-1 amd64Open vSwitch common components ii openvswitch-datapath-dkms2.7.0-1 all Open vSwitch datapath module source - DKMS version ii openvswitch-switch 2.7.0-1 amd64Open vSwitch switch implementations ii python-openvswitch 2.6.1-0ubuntu5.2~cloud0 all Python bindings for Open vSwitch #lsmod status No modules are listing for openvswitch-datapath-dkms #modprobe error modprobe openvswitch modprobe: ERROR: could not insert 'openvswitch': Exec format error --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-127-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory 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 Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: 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
[Kernel-packages] [Bug 1773165] Re: openvswitch-datapath-dkms kernel module is not getting loaded
I built a Xenial test kernel with a revert of the following commit: cc62065b735f openvswitch: Delete conntrack entry clashing with an expectation. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1773165 Can you test this kernel and see if it resolves this bug? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773165 Title: openvswitch-datapath-dkms kernel module is not getting loaded Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Distributor ID: Ubuntu Description: Ubuntu 16.04.4 LTS Release: 16.04 Codename: xenial Kernel version: 4.4.0-127-generic OVS version: 2.7.0 # Issue description openvswitch-datapath-dkms kernelmodule is not getting loaded # Error from dmesg [10863.380564] openvswitch: module verification failed: signature and/or required key missing - tainting kernel [10863.381804] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) [10863.517173] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) [10878.094250] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) #Error from syslog May 24 08:37:06 dev65 kernel: [76508.361496] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) May 24 08:37:06 dev65 openvswitch-switch[18336]: modprobe: ERROR: could not insert 'openvswitch': Exec format error May 24 08:37:06 dev65 openvswitch-switch[18336]: * Inserting openvswitch module #installation logs: Selecting previously unselected package openvswitch-datapath-dkms. (Reading database ... 84707 files and directories currently installed.) Preparing to unpack openvswitch-datapath-dkms_2.7.0-1_all.deb ... Unpacking openvswitch-datapath-dkms (2.7.0-1) ... Setting up openvswitch-datapath-dkms (2.7.0-1) ... Creating symlink /var/lib/dkms/openvswitch/2.7.0/source -> /usr/src/openvswitch-2.7.0 DKMS: add completed. Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area(bad exit status: 2) ./configure --with-linux='/lib/modules/4.4.0-127-generic/build' && make -C datapath/linux.. cleaning build area(bad exit status: 2) DKMS: build completed. openvswitch: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-geneve.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-gre.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-lisp.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-stt.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-vxlan.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ depmod DKMS: install completed. #Dpkg status dpkg -l | grep openvswitch ii openvswitch-common 2.7.0-1 amd64Open vSwitch common components ii openvswitch-datapath-dkms2.7.0-1 all Open vSwitch datapath module source - DKMS version ii openvswitch-switch 2.7.0-1 amd64Open vSwitch switch implementations ii python-openvswitch 2.6.1-0ubuntu5.2~cloud0 all Python bindings for Open vSwitch #lsmod status No modules are listing for openvswitch-datapath-dkms #modprobe error modprobe openvswitch modprobe: ERROR: could not insert 'openvswitch': Exec format error --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-127-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory 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 Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux
[Kernel-packages] [Bug 1798328] Re: USB cardreader (0bda:0328) make the system can't enter s3 or hang
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798328 Title: USB cardreader (0bda:0328) make the system can't enter s3 or hang Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: [Impact] We have a couple o lenovo laptops, they have the realtek cardreader (0bda:0328), this cardreader is the latest product from realtek, and it uses the common usb-to-scsi driver UAS. When the system suspend and resume, the USB host will print some errors like can't disable the device under this USB bus and reset-and-verify fails, after that the system can't suspend anymore and hang randomly. [Fix] the mainline build v4.17-rc1 doesn't have this issue, so through bisecting, we found this patch can fix the problem. [Test Case] suspend and resume 30 times, and plug sd storage card into the cardreader, everything worked well. [Regression Potential] Low, we tested this patch on 7 different lenovo laptops. After suspending and resuming for 30 times, the system still worked well, and plug a usb storage, it still worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1798328/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799471] Re: nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed to build
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1799471 Title: nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: 系统更改了gcc 版本后就n卡不能启动了 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-dkms-390 390.77-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 DKMSKernelVersion: 4.15.0-34-generic Date: Tue Oct 23 21:47:56 2018 DuplicateSignature: dkms:nvidia-dkms-390:390.77-0ubuntu0.18.04.1:cc1: error: unrecognized command line option "-fstack-protector-strong" InstallationDate: Installed on 2018-09-20 (33 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageVersion: 390.77-0ubuntu0.18.04.1 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: nvidia-graphics-drivers-390 Title: nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1799471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799490] Re: Kernel 4.15 boot error on XenServer
Please note, I'm not using this VM as DOM0. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799490 Title: Kernel 4.15 boot error on XenServer Status in linux package in Ubuntu: New Bug description: I recently upgraded an ubuntu VM from 16.04.1 to 18.04.1 running on XenServer 7.1. The upgrade itself was fine, but several kernel updates after the upgrade have caused the VM to fail to boot. All kernels that fail to boot seem to be from 4.15. Current, the latest kernel I've tried is 4.15.0-38, though, day-to-day I'm running a 4.4 kernel since the VM is necessary to my environment. The error message on boot is: unchecked MSR access error: RDMSR from 0xc90 at rIP: 0x9806c04a (native_read_msr+0xa/0x30) The trace is attached as a screenshot. I haven't been able to get a log containing the output. user@host:~$ cat /proc/version_signature Ubuntu 4.4.0-112.135-generic 4.4.98 user@host:~$ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02) Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100] Physical Slot: 0 Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- [disabled] 00:03.0 SCSI storage controller [0100]: XenSource, Inc. Xen Platform Device [5853:0001] (rev 02) Subsystem: XenSource, Inc. Xen Platform Device [5853:0001] Physical Slot: 3 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792580] Re: Mounting SOFS SMB shares fails
I built one more test kernel with only commit:
395a2076b406 cifs: connect to servername instead of IP for IPC$ share
The test kernel can also be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1792580
Can you test this kernel and see if it resolves this bug?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1792580
Title:
Mounting SOFS SMB shares fails
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
Ubuntu 18.04.1 LTS 4.15.0-33.36-generic
cifs-utils 2:6.8-1
Mounting scale-out SMB shares is failing.
mount -t cifs -o
credentials=/tmp/creds,domain=cbs.com,uid=114,gid=119,vers=3.0,_netdev,nodfs
//s2dscaleout.cbs.com/glance-images /tmp/test_mount
mount error(5): Input/output error
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
What works:
* mounting the share from a 16.04 host
* mounting standalone smb3 shares
Relevant error from the log (full logs attached separately):
Sep 14 11:12:05 r07-u13 kernel: Status code returned 0xc0c9
STATUS_NETWORK_NAME_DELETED
Sep 14 11:12:05 r07-u13 kernel:
/build/linux-81MBYC/linux-4.15.0/fs/cifs/smb2maperror.c: Mapping SMB2 status
code 0xc0c9 to POSIX err -5
Share server os: Windows Server 2016 10.0.14393
PS C:\Users\jujuadmin> get-smbshare glance-images | fl *
ShareState: Online
AvailabilityType : ScaleOut
ShareType : FileSystemDirectory
FolderEnumerationMode : Unrestricted
CachingMode : Manual
SmbInstance : Default
CATimeout : 0
ConcurrentUserLimit : 0
ContinuouslyAvailable : True
CurrentUsers : 2
Description :
EncryptData : False
Name : glance-images
Path : C:\ClusterStorage\Volume1\GLANCE-IMAGES
Scoped: True
ScopeName : S2DSCALEOUT
ShadowCopy: False
Special : False
Temporary : False
Volume: \\?\Volume{5faf880d-d308-4058-9ec2-d19d48089495}\
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Sep 7 16:51 seq
crw-rw 1 root audio 116, 33 Sep 7 16:51 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: Dell Inc. PowerEdge R710
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 mgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic
root=UUID=ba74e4cf-9634-4049-abd8-0ed721836a41 ro
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-33-generic N/A
linux-backports-modules-4.15.0-33-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-33-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: False
dmi.bios.date: 07/23/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 6.4.0
dmi.board.name: 0YDJK3
dmi.board.vendor: Dell Inc.
dmi.board.version: A14
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr6.4.0:bd07/23/2013:svnDellInc.:pnPowerEdgeR710:pvr:rvnDellInc.:rn0YDJK3:rvrA14:cvnDellInc.:ct23:cvr:
dmi.product.name: PowerEdge R710
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792580/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799411] Re: linux: 4.15.0-39.42 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-stable 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/1799411 Title: linux: 4.15.0-39.42 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux 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 backports: bug 1799421 (linux-azure), bug 1799422 (linux-azure), bug 1799423 (linux-azure-edge), bug 1799424 (linux-gcp), bug 1799425 (linux-hwe), bug 1799426 (linux-hwe-edge) derivatives: bug 1799412 (linux-raspi2), bug 1799413 (linux-oem), bug 1799414 (linux-aws), bug 1799415 (linux-azure), bug 1799416 (linux-gcp), bug 1799417 (linux-kvm) To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799490] [NEW] Kernel 4.15 boot error on XenServer
Public bug reported: I recently upgraded an ubuntu VM from 16.04.1 to 18.04.1 running on XenServer 7.1. The upgrade itself was fine, but several kernel updates after the upgrade have caused the VM to fail to boot. All kernels that fail to boot seem to be from 4.15. Current, the latest kernel I've tried is 4.15.0-38, though, day-to-day I'm running a 4.4 kernel since the VM is necessary to my environment. The error message on boot is: unchecked MSR access error: RDMSR from 0xc90 at rIP: 0x9806c04a (native_read_msr+0xa/0x30) The trace is attached as a screenshot. I haven't been able to get a log containing the output. user@host:~$ cat /proc/version_signature Ubuntu 4.4.0-112.135-generic 4.4.98 user@host:~$ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02) Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100] Physical Slot: 0 Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- [disabled] 00:03.0 SCSI storage controller [0100]: XenSource, Inc. Xen Platform Device [5853:0001] (rev 02) Subsystem: XenSource, Inc. Xen Platform Device [5853:0001] Physical Slot: 3 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/bugs/1799490/+attachment/5204565/+files/booterror.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799490 Title: Kernel 4.15 boot error on XenServer Status in linux package in Ubuntu: New Bug description: I recently upgraded an ubuntu VM from 16.04.1 to 18.04.1 running on XenServer 7.1. The upgrade itself was fine, but several kernel updates after the upgrade have caused the VM to fail to boot. All kernels that fail to boot seem to be from 4.15. Current, the latest kernel I've tried is 4.15.0-38, though, day-to-day I'm running a 4.4 kernel since the VM is necessary to my environment. The error message on boot is: unchecked MSR access error: RDMSR from 0xc90 at rIP: 0x9806c04a (native_read_msr+0xa/0x30) The trace is attached as a screenshot. I haven't been able to get a log containing the output. user@host:~$ cat /proc/version_signature Ubuntu 4.4.0-112.135-generic 4.4.98 user@host:~$ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02) Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100] Physical Slot: 0 Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- [disabled] 00:03.0 SCSI storage controller [0100]: XenSource, Inc. Xen Platform Device [5853:0001] (rev 02) Subsystem: XenSource, Inc. Xen Platform Device [5853:0001] Physical Slot: 3 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's
I don't have the hw to test it. For the kernel it was easy to just check that the entries are found in module.alias for i915. I don't see how to verify that for the xserver, the strings don't seem to be greppable from any of the binaries. ** Tags removed: verification-done ** Tags added: verification-needed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: Fix Committed Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795653] Re: 87cdf3148b11 was never backported to 4.15
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1795653
Title:
87cdf3148b11 was never backported to 4.15
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
Commit 87cdf3148b11 fixes a regression introduced by commit
5efec5c655dd. However, it has not never landed in Bionic. Requesting
this commit in Bionic, so we don't have to wait for it to come down from
upstream stable.
== Fix ==
87cdf3148b11 ("xfrm: Verify MAC header exists before overwriting
eth_hdr(skb)->h_proto")
== Regression Potential ==
Low. This commit fixes and existing regression by making sure teh MAC
header exists.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
Hello,
After a few days of troubleshooting a problem with L2TP and IPSec a
fellow from ServerFault pointed out that my problem is a known bug
fixed by 87cdf3148b11 commit which wasn't backported on 4.15 kernel.
Ubuntu 4.15.0-36.39-generic 4.15.18
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795653/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792957] Re: Provide mode where all vCPUs on a core must be the same VM
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1792957
Title:
Provide mode where all vCPUs on a core must be the same VM
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
Status in linux source package in Cosmic:
In Progress
Bug description:
== SRU Justification ==
This patch has been requested by IBM. It provides a mode where all vCPUs
on a core must be the same VM. This is intended for use in
security-conscious settings where users are concerned about possible
side-channel attacks between threads which could perhaps enable one VM
to attack another VM on the same core, or the host.
== Fix ==
linux-next commit:
aa2278644ae5 ("KVM: PPC: Book3S HV: Provide mode where all vCPUs on a core
must be the same VM")
== Regression Potential ==
Low. Changes limited to powerpc.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Comment: #0 - Leonardo Augusto Guimaraes Garcia -
2018-09-13 07:12:48 ==
+++ This bug was initially created as a clone of Bug #171443 +++
Please, add the following patch:
http://patchwork.ozlabs.org/patch/968786/
which adds a mode where all vCPUs on a core must be the same VM on
POWER8 and POWER9.
This is intended for use in security-conscious settings where users
are concerned about possible side-channel attacks between threads
which could perhaps enable one VM to attack another VM on the same
core, or the host.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1792957/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798332] Re: Support Edge Gateway's Bluetooth LED
** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798332 Title: Support Edge Gateway's Bluetooth LED Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: In Progress Bug description: == Impact == The Bluetooth LED of Marvell 88W8897 is not enabled by default (there's no code for controlling LED). It is requested to be ON and OFF when the radio is on and off accordingly. == Fix == The LEDs are connected to GPIO pins on the Marvell WiFi/Bluetooth combo module, thus they can only be controlled via firmware. == Test Case == # hciconfig hci0 [on|off] and see if the LEDs work properly. == Risk of Regression == PCI sub IDs of the host bridge are used to determine if we're really running on an Edge Gateway, and we already have these patches in Xenial kernels quite a while. Risk should be reasonably low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798332/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792195] Re: Signal 7 error when running GPFS tracing in cluster
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1792195
Title:
Signal 7 error when running GPFS tracing in cluster
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
Status in linux source package in Cosmic:
In Progress
Bug description:
== SRU Justification ==
IBM is requesting these commits in bionic and cosmic. These commits
also rely on commit 7acf50e4efa6, which was SRU'd in bug 1792102.
Description of bug:
GPFS mmfsd daemon is mapping shared tracing buffer(allocated from kernel
driver using vmalloc) and then writing trace records from user space threads
in parallel. While the SIGBUS happened, the access virtual memory address
is in the mapped range, no overflow on access.
The root cause is that for PTEs created by a driver at mmap time (ie, that
aren't created dynamically at fault time), it's not legit for
ptep_set_access_flags()
to make them invalid even temporarily. A concurrent access while they are
invalid will be unable to service the page fault and will cause as SIGBUS.
== Fixes ==
bd0dbb73e013 ("powerpc/mm/books3s: Add new pte bit to mark pte temporarily
invalid.")
f08d08f3db55 ("powerpc/mm/radix: Only need the Nest MMU workaround for R ->
RW transition")
== Regression Potential ==
Low. Limited to powerpc.
== Test Case ==
A test kernel was built with these patches and tested by IBM.
IBM states the test kernel resolved the bug.
-- Problem Description --
GPFS mmfsd daemon is mapping shared tracing buffer(allocated from kernel
driver using vmalloc) and then writing trace records from user space threads in
parallel. While the SIGBUS happened, the access virtual memory address is in
the mapped range, no overflow on access.
Worked with Benjamin Herrenschmidt on GPFS tracing kernel driver code
and he made a suggestion as workaround on the driver code to bypass
the problem, and it works
the workaround code change as below:
- rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, PAGE_SHARED);
+ rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE,
__pgprot(pgprot_val(PAGE_SHARED)|_PAGE_DIRTY);
As Benjamin mentioned, this is a Linux kernel bug and this is just a
workaround. He will give the details about the kernel bug and why this
workaround works
The root cause is that for PTEs created by a driver at mmap time (ie,
that aren't created dynamically at fault time), it's not legit for
ptep_set_access_flags() to make them invalid even temporarily. A
concurrent access while they are invalid will be unable to service the
page fault and will cause as SIGBUS.
Thankfully such PTEs shouldn't normally be the subject of a RO->RW
privilege escalation.
What happens is that the GPFS driver creates the PTEs using
remap_pfn_range(...,PAGE_SHARED).
PAGE_SHARED has _PAGE_ACCESSED (R) but not _PAGE_DIRTY (C) set.
Thus on the first write, we try set C and while doing so, hit the
above workaround, which causes the problem described earlier.
The proposed patch will ensure we only do the Nest MMU hack when
changing _PAGE_RW and not for normal R/C updates.
The workaround tested by the GPFS team consists of adding _PAGE_DIRTY
to the mapping created by remap_pfn_range() to avoid the RC update
fault completely.
This is fixed by these:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd0dbb73e01306a1060e56f81e5fe287be936477
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f08d08f3db55452d31ba4a37c702da6245876b96
Since DD1 support is still in (ie,
2bf1071a8d50928a4ae366bb3108833166c2b70c is not applied) the second
doesn't apply cleanly. Did you want that attached?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1792195/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790832] Re: crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1790832
Title:
crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Released
Bug description:
== SRU Justification ==
IBM is requesting this patch in all releases order to fix the sleep-in-atomic
bugs in AES-CBC and AES-XTS VMX implementations.
This patch is a clean cherry pick and has already been applied to
Cosmic. It is also needed in Xenial, but there was a minor context
diff, so the Xenial SRU will be sent separatly.
== Fix ==
0522236d4f9c ("crypto: vmx - Fix sleep-in-atomic bugs")
== Regression Potential ==
Low. This patch has also been cc'd to upstream stable, so it has had
additional upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Comment: #0 - Paulo Flabiano Smorigo
Please include the following commit in order to fix the sleep-in-atomic bugs
in AES-CBC and AES-XTS VMX implementations [1]:
0522236 crypto: vmx - Fix sleep-in-atomic bugs
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=0522236d4f9c5ab2e79889cb020d1acbe5da416e
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790832/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792501] Re: [Ubuntu18.04][Power9][DD2.2]package installation segfaults inside debian chroot env in P9 KVM guest with HTM enabled (kvm)
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1792501
Title:
[Ubuntu18.04][Power9][DD2.2]package installation segfaults inside
debian chroot env in P9 KVM guest with HTM enabled (kvm)
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Bug description:
== SRU Justification ==
IBM is requesting this commit in Bionic. It fixes a regression
introduced by upstream commit 4bb3c7a020.
Without this patch, package installation segfaults inside debian chroot
env in P9 KVM guest with HTM enabled.
The fix has already landed in Cosmic master-next.
== Fix ==
f14040bca892 ("KVM: PPC: Book3S HV: Fix guest r11 corruption with POWER9 TM
workarounds")
== Regression Potential ==
Low. This commit fixes an existing regrssion and is specific to powerpc. It
has been cc'd to
upstream stable, so has had additional upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Comment: #0 - Satheesh Rajendran - 2018-09-11
04:10:09 ==
---Problem Description---
package installation segfaults inside debian chroot env in P9 KVM guest with
HTM enabled
---Additional Hardware Info---
FW with tm-suspend-mode enabled
#cd /sys/firmware/devicetree/base/ibm,opal/fw-features/
#ls -1 tm-suspend-mode
enabled
name
phandle
qemu-kvm 1:2.11+dfsg-1ubuntu7.4
Machine Type = Power9 DD2.2
---Steps to Reproduce---
1. Boot a P9 KVM guest Ubuntu 18.04 (with cap-htm=on, bydefault it is on)
tried with upstream kernel aswell(same results)
create tap device in host
# tunctl -t tap1 -u `whoami`;brctl addif virbr0 tap1;ifconfig tap1 up
#qemu-system-ppc64 -enable-kvm -M pseries -m 8192 -smp 4 -drive
file=/home/sath/ubuntu-18.04-ppc64le.qcow2,format=qcow2,if=none,id=drive-scsi0
-device virtio-scsi-pci,id=drive-scsi0 -device scsi-hd,drive=drive-scsi0
-serial mon:stdio -enable-kvm -vga none -nographic -kernel
/home/sath/vmlinux_4.19 -append root=/dev/sda2 rw console=tty0
console=ttyS0,115200 init=/sbin/init initcall_debug -netdev
tap,id=mynet1,ifname=tap1,script=no,downscript=no -device
virtio-net,netdev=mynet1,mac=52:55:00:d1:55:42
run dhclient inside guest.
2. # mkdir -p stretch
# debootstrap stretch /stretch http://httpredir.debian.org/debian
# chroot /stretch
/# apt-get update && apt-get install -y make gcc ruby python
...
[ 32.029474] random: crng init done
[ 32.029477] random: 7 urandom warning(s) missed due to ratelimiting
[ 500.300835] dpkg-deb[8704]: segfault (11) at c00037fa nip
7fffac2d098c lr 7fffac2d08c4 code 1 in libc-2.24.so[7fffac17+19]
[ 500.300863] dpkg-deb[8704]: code: 4828 eb090010 2eb8 4096006c
419e0074 85270004 394a0001 794a0020
[ 500.300881] dpkg-deb[8704]: code: 71280001 408200a0 1d2a0018 7d2b4a14
2ea8 40960010 e9090008
---uname output---
4.15.0-34,4.19.0-rc3
---Debugger---
A debugger is not configured
Contact Information = sathe...@in.ibm.com
Userspace tool common name:
KVM Guest: Ubuntu GLIBC 2.27-3ubuntu1) stable release version 2.27,
Chroot inside KVM Guest: Debian GLIBC 2.24-11+deb9u3) stable release version
2.24
Userspace rpm:
KVM Guest: Ubuntu GLIBC 2.27-3ubuntu1) stable release version 2.27,
Chroot inside KVM Guest: Debian GLIBC 2.24-11+deb9u3) stable release version
2.24
The userspace tool has the following bit modes: both
Userspace tool obtained from project website: na
*Additional Instructions for sathe...@in.ibm.com:
-Post a private note with access information to the machine that the bug is
occuring on.
-Attach ltrace and strace of userspace application.
So latest update taken from https://github.ibm.com/powercloud/icp-
ppc64le/issues/470
was able to recreate segfault using TM test cases
/linux/tools/testing/selftests/powerpc/tm
# ./tm-vmxcopy
test: tm_vmxcopy
tags: git_version:v4.19-rc3-0-g11da3a7f84f1-dirty
!! child died by signal 11
failure: tm_vmxcopy
this particular test on being run gets a signal 11
[267132.434651] tm-vmxcopy[641]: unhandled signal 11 at 0001 nip
000104ba122c lr 000104ba11e4 code 30001
[267253.708795] tm-vmxcopy[7861]: unhandled signal 11 at 0001 nip
00012a31122c lr 00012a3111e4 code 30001
[267385.064533] tm-vmxcopy[13314]: unhandled signal 11 at 0001
nip 0001235f122c lr 0001235f11e4 code 30001
== Comment: #12 - Michael Neuling - 2018-09-13
00:34:16 ==
Fixes r11 corruption.
== Comment: #14 -
[Kernel-packages] [Bug 1792102] Re: Ubuntu18.04: GPU total memory is reduced
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1792102
Title:
Ubuntu18.04: GPU total memory is reduced
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 ==
Due to a recent change for powernv, now the total GPU memory is no longer
available. This impacts performance for any application/benchmark has a
large GPU memory utilization.
IBM is requesting mainlien commit 7acf50e4efa6 in Bionic, which reverts
mainline commit 4b5d62ca17a1.
== Fix ==
7acf50e4efa6 ("Revert "powerpc/powernv: Increase memory block size to 1GB on
radix"")
== Regression Potential ==
Low. This is a revert that was also done upstream due to a regression.
Limited to powerpc.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Comment: #0 - Michael Ranweiler - 2018-09-10
19:26:14 ==
Due to a recent change for powernv, now the total GPU memory is no
longer available. This impacts performance for any
application/benchmark has a large GPU memory utilization.
Previous amount of memory : 16128MiB
Current amount of available memory : 15360MiB
From Anton, describing the recent change.:
powerpc/powernv: Increase memory block size to 1GB on radix
Memory hot unplug on PowerNV radix hosts is broken. Our memory block
size is 256MB but since we map the linear region with very large
pages, each pte we tear down maps 1GB.
A hot unplug of one 256MB memory block results in 768MB of memory
getting unintentionally unmapped. At this point we are likely to oops.
Fix this by increasing our memory block size to 1GB on PowerNV radix
hosts.
Fixes: 4b5d62ca17a1 ("powerpc/mm: add
radix__remove_section_mapping()")
This is fixed with:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7acf50e4efa6
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1792102/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773165] Re: openvswitch-datapath-dkms kernel module is not getting loaded
Apologies for the late response. I am still seeing the issue with the latest kernel that is (4.4.0-134) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773165 Title: openvswitch-datapath-dkms kernel module is not getting loaded Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Distributor ID: Ubuntu Description: Ubuntu 16.04.4 LTS Release: 16.04 Codename: xenial Kernel version: 4.4.0-127-generic OVS version: 2.7.0 # Issue description openvswitch-datapath-dkms kernelmodule is not getting loaded # Error from dmesg [10863.380564] openvswitch: module verification failed: signature and/or required key missing - tainting kernel [10863.381804] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) [10863.517173] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) [10878.094250] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) #Error from syslog May 24 08:37:06 dev65 kernel: [76508.361496] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) May 24 08:37:06 dev65 openvswitch-switch[18336]: modprobe: ERROR: could not insert 'openvswitch': Exec format error May 24 08:37:06 dev65 openvswitch-switch[18336]: * Inserting openvswitch module #installation logs: Selecting previously unselected package openvswitch-datapath-dkms. (Reading database ... 84707 files and directories currently installed.) Preparing to unpack openvswitch-datapath-dkms_2.7.0-1_all.deb ... Unpacking openvswitch-datapath-dkms (2.7.0-1) ... Setting up openvswitch-datapath-dkms (2.7.0-1) ... Creating symlink /var/lib/dkms/openvswitch/2.7.0/source -> /usr/src/openvswitch-2.7.0 DKMS: add completed. Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area(bad exit status: 2) ./configure --with-linux='/lib/modules/4.4.0-127-generic/build' && make -C datapath/linux.. cleaning build area(bad exit status: 2) DKMS: build completed. openvswitch: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-geneve.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-gre.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-lisp.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-stt.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-vxlan.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ depmod DKMS: install completed. #Dpkg status dpkg -l | grep openvswitch ii openvswitch-common 2.7.0-1 amd64Open vSwitch common components ii openvswitch-datapath-dkms2.7.0-1 all Open vSwitch datapath module source - DKMS version ii openvswitch-switch 2.7.0-1 amd64Open vSwitch switch implementations ii python-openvswitch 2.6.1-0ubuntu5.2~cloud0 all Python bindings for Open vSwitch #lsmod status No modules are listing for openvswitch-datapath-dkms #modprobe error modprobe openvswitch modprobe: ERROR: could not insert 'openvswitch': Exec format error --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-127-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory 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 Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: 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
[Kernel-packages] [Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
Would it be possible for you to test the proposed kernel and post back if it resolves this bug? See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1794280] Re: gdm doesn't start on a fresh installation of Cosmic Desktop
the bug got fixed in xorg, there is no need to target an xorg fix to cosmic ** Changed in: xorg-server (Ubuntu Cosmic) Status: Confirmed => 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/1794280 Title: gdm doesn't start on a fresh installation of Cosmic Desktop Status in gdm3 package in Ubuntu: Fix Released Status in kmod package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev package in Ubuntu: Fix Released Status in gdm3 source package in Cosmic: Fix Released Status in kmod source package in Cosmic: Invalid Status in linux source package in Cosmic: Invalid Status in xorg-server source package in Cosmic: Invalid Status in xserver-xorg-video-fbdev source package in Cosmic: Fix Released Bug description: ubuntu cosmic desktop 20180925 After installation gdm fails to start and there is only a black screen with a blinking cursor on the top left of the screen. gdm3 can be started manually from a tty. Switching to another tty then back also starts gdm. It happens on bare metal and VM. Originally, when this issue happened there was a plymouth crash reported in bug 1794292 but this issue is still happening without the plymouth crash. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 Date: Tue Sep 25 13:54:45 2018 InstallationDate: Installed on 2018-09-25 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180925) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2018-09-25T13:49:41.053012 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1794280/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797292] Re: The front MIC can't work on the Lenovo M715
** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797292 Title: The front MIC can't work on the Lenovo M715 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Incomplete Bug description: [Impact] On the machine of Lenovo M715, there are 2 audio jacks on the front panel, one of them is microphone jack. When we plug a micrphone into it, the system can't detect this microphone and can't record sound via this microphone too. [Fix] Apply the quirk of ALC294_FIXUP_LENOVO_MIC_LOCATION, the alsa driver will assign a different name to this audio jack, then pulseaudio can handle this jack and everything works well. [Test Case] plug a microphone to this jack and record sound, system can detect the microphone and can record sound. [Regression Potential] Very low, this pin configuration is specific to the machine of M715 so far, will not affect other machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1797292/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798330] Re: Support Edge Gateway's WIFI LED
** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798330 Title: Support Edge Gateway's WIFI LED Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: In Progress Bug description: == Impact == The WIFI LED of Marvell 88W8897 is not enabled by default (there's no code for controlling LED in mwifiex). It is requested to be ON and OFF when the radio is on and off accordingly. == Fix == The LEDs are connected to GPIO pins on the Marvell WiFi/Bluetooth combo module, thus they can only be controlled via firmware. == Test Case == # ifconfig wlan0 [on|off] and see if the LEDs work properly. == Risk of Regression == PCI sub IDs of the host bridge are used to determine if we're really running on an Edge Gateway, and we already have these patches in Xenial kernels quite a while. Risk should be reasonably low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798330/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797314] Re: fscache: bad refcounting in fscache_op_complete leads to OOPS
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797314 Title: fscache: bad refcounting in fscache_op_complete leads to OOPS Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: In Progress Bug description: SRU Justification - [Impact] A kernel BUG is sometimes observed when using fscache: [4740718.880898] FS-Cache: [4740718.880920] FS-Cache: Assertion failed [4740718.880934] FS-Cache: 0 > 0 is false [4740718.881001] [ cut here ] [4740718.881017] kernel BUG at /usr/src/linux-4.4.0/fs/fscache/operation.c:449! [4740718.881040] invalid opcode: [#1] SMP [4740718.892659] Call Trace: [4740718.893506] [] cachefiles_read_copier+0x3a9/0x410 [cachefiles] [4740718.894374] [] fscache_op_work_func+0x22/0x50 [fscache] [4740718.895180] [] process_one_work+0x150/0x3f0 [4740718.895966] [] worker_thread+0x11a/0x470 [4740718.896753] [] ? __schedule+0x359/0x980 [4740718.897783] [] ? rescuer_thread+0x310/0x310 [4740718.898581] [] kthread+0xd6/0xf0 [4740718.899469] [] ? kthread_park+0x60/0x60 [4740718.900477] [] ret_from_fork+0x3f/0x70 [4740718.901514] [] ? kthread_park+0x60/0x60 [Problem] In include/linux/fscache-cache.h, fscache_retrieval_complete reads, in part: atomic_sub(n_pages, >n_pages); if (atomic_read(>n_pages) <= 0) fscache_op_complete(>op, true); The code is using atomic_sub followed by an atomic_read. This causes two threads doing a decrement of pages to race with each other seeing the op->refcount <= 0 at same time, and end up calling fscache_op_complete in both the threads leading to the OOPS. [Fix] The fix is trivial to use atomic_sub_return instead of two calls. [Testcase] I believe the user has tested the patch successfully on their fscache/cachefiles setup. [Regression Potential] Limited to fscache. Small, comprehensible change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797314/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797654] Re: hns3: autoneg settings get lost on down/up
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797654 Title: hns3: autoneg settings get lost on down/up Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Bug description: [Impact] If a user manually disables autonegotiation, that setting will be lost if the link is toggled. [Test Case] sudo ethtool -s enp125s0f2 speed 100 duplex half autoneg off After this, "ethtool enp125s0f2" will show: Advertised auto-negotiation: No If you then run: sudo ifconfig enp125s0f2 down; sudo ifconfig enp125s0f2 up, then ethtool will show: Advertised auto-negotiation: Yes [Fix] b01b7cf19bf4a net: hns3: Fix for information of phydev lost problem when down/up [Regression Risk] Restricted to a single SoC on which the fix was explicitly tested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797654/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797406] Re: rpi3b+: ethernet not working
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1797406
Title:
rpi3b+: ethernet not working
Status in linux package in Ubuntu:
Incomplete
Status in linux-raspi2 package in Ubuntu:
New
Status in linux source package in Bionic:
Fix Committed
Status in linux-raspi2 source package in Bionic:
New
Bug description:
Impact:
Since the release of Ubuntu-raspi2_4.15.0-1022.24, the ethernet port
of the RaspberryPi 3B+ has stopped to work: no phy interrupts are
generated when a cable is inserted, so it's like the ethernet port is
always disconnected.
The problem lies in commit 72eff2505735 ("lan78xx: Connect phy
early"), that was backported into Bionic/master (and then percolated
down into Bionic/raspi2):
"Commit 92571a1aae40 ("lan78xx: Connect phy early") moves the PHY
initialisation into lan78xx_probe, but lan78xx_open subsequently calls
lan78xx_reset. As well as forcing a second round of link negotiation,
this reset frequently prevents the phy interrupt from being generated
(even though the link is up), rendering the interface unusable.
Fix this issue by removing the lan78xx_reset call from lan78xx_open.
"
Fix:
Apply the attached patch and recompile
How to test:
Boot a patched kernel and checks if the ethernet port is working
Regression potential:
None, the attached patch is a fix for the aforementioned patch, and
fixes exactly this issue - it's upstream already and was backported
into gregkh's stable branches 4.17+.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797406/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797202] Re: [Bionic] arm64: topology: Avoid checking numa mask for scheduler MC selection
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1797202
Title:
[Bionic] arm64: topology: Avoid checking numa mask for scheduler MC
selection
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Committed
Bug description:
[Impact]
The numa mask subset check can often lead to system hang or crash during CPU
hotplug and system suspend operation if NUMA is disabled. This is mostly
observed on HMP systems where the CPU compute capacities are different and ends
up in different scheduler domains. Since cpumask_of_node is returned instead
core_sibling, the scheduler is confused with incorrect cpumasks(e.g. one CPU in
two different sched domains at the same time) on CPU hotplug.
[Fix]
The following patch fixes this issue:
e156ab71a974 arm64: topology: Avoid checking numa mask for scheduler MC
selection
[Test]
-- testcase --
#!/bin/bash
stress-ng -q --vm 100 --vm-bytes 1G --cpu 210 --timeout 2400s --metrics-brief
&
pid=$!
for i in {1..210}; do
num=$((RANDOM%10+$i))
echo "Offline CPU $num"
echo 0 > /sys/devices/system/cpu/cpu$num/online || exit 1
sleep 3s
echo "Online CPU $num"
echo 1 > /sys/devices/system/cpu/cpu$num/online || exit 1
done
kill -9 $pid
Executed the test case with stock Bionic kernel and with Bionic kernel with
patches applied. No system hang or crash was observed. On Cavium CN99XX Thunder
X2 system.
[Regression Potential]
Regression tested on Cavium Thunder X2 CN99XX system, and none were found.
Regression risk is low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797202/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796748] Re: regression in 'ip --family bridge neigh' since linux v4.12
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1796748
Title:
regression in 'ip --family bridge neigh' since linux v4.12
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Bionic:
Fix Committed
Bug description:
[Impact]
* Netlink RTM_GETNEIGH requests for PF_BRIDGE are broken since linux
v4.12.
* Users, tools (e.g., iproute2), and libraries (e.g., go netlink) that use
such request/family currently receive nothing back in the kernel response.
* The upstream fix resolves the breakage in the userspace-kernel interface
by explicitly checking for the old/broken request to ensure it's replied.
[Test Case]
* The command 'ip --family bridge neigh' returns nothing on broken kernels,
and matches 'bridge fdb show' on fixed kernels.
* Before:
$ ip --family bridge neigh
$
* After:
$ ip --family bridge neigh
dev ens3 lladdr 33:33:00:00:00:01 PERMANENT
dev ens3 lladdr 01:00:5e:00:00:01 PERMANENT
dev ens3 lladdr 33:33:ff:e9:9d:60 PERMANENT
* Reference:
$ bridge fdb show
33:33:00:00:00:01 dev ens3 self permanent
01:00:5e:00:00:01 dev ens3 self permanent
33:33:ff:e9:9d:60 dev ens3 self permanent
[Regression Potential]
* Low, for three reasons:
* The fix is fairly contained (RTM_GETNEIGH request for PF_BRIDGE
family).
* The checks introduced by the fix are conservative, based on the size
of the old request (the size of the old/new requests are different),
and it does nothing different in case the (old) size doesn't match.
* Given the above, only applications with message length and contents
specially hand-crafted (and likely not valid nor useful) might fail.
To the best of my knowledge, this is not the common case out there.
[Other Info]
* The patch is only applicable to v4.12+ (so not Trusty nor Xenial).
* The patch is the same for Bionic, Cosmic, and unstable.
* Upstream commit: bd961c9bc664 ("rtnetlink: fix rtnl_fdb_dump() for ndmsg
header")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd961c9bc66497f0c63f4ba1d02900bb85078366
* I'll submit the patch shortly to the kernel-team mailing list.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796748/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796786] Re: screen displays abnormally on the lenovo M715 with the AMD GPU (Radeon Vega 8 Mobile, rev ca, 1002:15dd)
** Changed in: linux (Ubuntu Bionic) 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/1796786 Title: screen displays abnormally on the lenovo M715 with the AMD GPU (Radeon Vega 8 Mobile, rev ca, 1002:15dd) Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: New Bug description: [Impact] On the machine of Lenovo M715, there is an AMD GPU (1022:15dd rev ca), when it switchs to amdgpufb, the screen displays abnormally, we tested with a couple monitors, all of them can reproduce this issue. [Fix] Backported 3 patches from mainline kernel, all of them focus on the change of disable_vga(). After applying these 3 patches, the issue disappears. [Test Case] boot the system, run glxgears, everything works well [Regression Potential] Very low, these patches come from upstream, and I have tested them on at least 6 different lenovo machines and those machines have different AMD GPUs on them, all of them worked as well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1796786/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777600] Re: chzdev can't find modprobe
Successfully verified on bionic - adjusting tags accordingly. ** Attachment added: "verification_on_bionic.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777600/+attachment/5204557/+files/verification_on_bionic.txt ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777600 Title: chzdev can't find modprobe Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Invalid Status in s390-tools package in Ubuntu: Fix Released Status in s390-tools source package in Xenial: Fix Committed Status in s390-tools source package in Bionic: Fix Committed Status in s390-tools source package in Cosmic: Fix Released Bug description: [Impact] * chzdev fails to load additional kernel modules at runtime, resulting in failure to activate devices. [Test Case] $ chzdev zfcp --type datarouter=0 dbflevel=5 Should succeed, instead of erroring out / not able to find modprobe. [Regression Potential] * This corrects compiled-in path to /sbin/modprobe, thus making available previously a broken codepath of chzdev. [Other Info] * Original bug report Description: only when trying to change some attributes chzdev fails because it cant find modprobe under Ubuntu 18.04 root@m83lp09:~# chzdev zfcp --type datarouter=0 dbflevel=5 sh: 1: /usr/sbin/modprobe: not found zfcp device type configure failed Error: Command failed (exit code 127): /usr/sbin/modprobe -r zfcp root@m83lp09:~# whereis modprobe modprobe: /sbin/modprobe /etc/modprobe.d /lib/modprobe.d /usr/share/man/man8/modprobe.8.gz Potential solution ? : adding a symlink is a workaround, is this path hardcoded? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1777600/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773165] Re: openvswitch-datapath-dkms kernel module is not getting loaded
fwiw the 4.4 intree openvswitch module is recent and up-to-date so use of a ovs supplied dkms module should not be required. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773165 Title: openvswitch-datapath-dkms kernel module is not getting loaded Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Distributor ID: Ubuntu Description: Ubuntu 16.04.4 LTS Release: 16.04 Codename: xenial Kernel version: 4.4.0-127-generic OVS version: 2.7.0 # Issue description openvswitch-datapath-dkms kernelmodule is not getting loaded # Error from dmesg [10863.380564] openvswitch: module verification failed: signature and/or required key missing - tainting kernel [10863.381804] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) [10863.517173] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) [10878.094250] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) #Error from syslog May 24 08:37:06 dev65 kernel: [76508.361496] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) May 24 08:37:06 dev65 openvswitch-switch[18336]: modprobe: ERROR: could not insert 'openvswitch': Exec format error May 24 08:37:06 dev65 openvswitch-switch[18336]: * Inserting openvswitch module #installation logs: Selecting previously unselected package openvswitch-datapath-dkms. (Reading database ... 84707 files and directories currently installed.) Preparing to unpack openvswitch-datapath-dkms_2.7.0-1_all.deb ... Unpacking openvswitch-datapath-dkms (2.7.0-1) ... Setting up openvswitch-datapath-dkms (2.7.0-1) ... Creating symlink /var/lib/dkms/openvswitch/2.7.0/source -> /usr/src/openvswitch-2.7.0 DKMS: add completed. Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area(bad exit status: 2) ./configure --with-linux='/lib/modules/4.4.0-127-generic/build' && make -C datapath/linux.. cleaning build area(bad exit status: 2) DKMS: build completed. openvswitch: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-geneve.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-gre.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-lisp.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-stt.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-vxlan.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ depmod DKMS: install completed. #Dpkg status dpkg -l | grep openvswitch ii openvswitch-common 2.7.0-1 amd64Open vSwitch common components ii openvswitch-datapath-dkms2.7.0-1 all Open vSwitch datapath module source - DKMS version ii openvswitch-switch 2.7.0-1 amd64Open vSwitch switch implementations ii python-openvswitch 2.6.1-0ubuntu5.2~cloud0 all Python bindings for Open vSwitch #lsmod status No modules are listing for openvswitch-datapath-dkms #modprobe error modprobe openvswitch modprobe: ERROR: could not insert 'openvswitch': Exec format error --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-127-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory 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 Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: 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
[Kernel-packages] [Bug 1773165] Re: openvswitch-datapath-dkms kernel module is not getting loaded
Where is the openvswitch-switch-dkms package coming from? I don't recognise the package version as anything that's being shipped in 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/1773165 Title: openvswitch-datapath-dkms kernel module is not getting loaded Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Distributor ID: Ubuntu Description: Ubuntu 16.04.4 LTS Release: 16.04 Codename: xenial Kernel version: 4.4.0-127-generic OVS version: 2.7.0 # Issue description openvswitch-datapath-dkms kernelmodule is not getting loaded # Error from dmesg [10863.380564] openvswitch: module verification failed: signature and/or required key missing - tainting kernel [10863.381804] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) [10863.517173] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) [10878.094250] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) #Error from syslog May 24 08:37:06 dev65 kernel: [76508.361496] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) May 24 08:37:06 dev65 openvswitch-switch[18336]: modprobe: ERROR: could not insert 'openvswitch': Exec format error May 24 08:37:06 dev65 openvswitch-switch[18336]: * Inserting openvswitch module #installation logs: Selecting previously unselected package openvswitch-datapath-dkms. (Reading database ... 84707 files and directories currently installed.) Preparing to unpack openvswitch-datapath-dkms_2.7.0-1_all.deb ... Unpacking openvswitch-datapath-dkms (2.7.0-1) ... Setting up openvswitch-datapath-dkms (2.7.0-1) ... Creating symlink /var/lib/dkms/openvswitch/2.7.0/source -> /usr/src/openvswitch-2.7.0 DKMS: add completed. Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area(bad exit status: 2) ./configure --with-linux='/lib/modules/4.4.0-127-generic/build' && make -C datapath/linux.. cleaning build area(bad exit status: 2) DKMS: build completed. openvswitch: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-geneve.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-gre.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-lisp.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-stt.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-vxlan.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ depmod DKMS: install completed. #Dpkg status dpkg -l | grep openvswitch ii openvswitch-common 2.7.0-1 amd64Open vSwitch common components ii openvswitch-datapath-dkms2.7.0-1 all Open vSwitch datapath module source - DKMS version ii openvswitch-switch 2.7.0-1 amd64Open vSwitch switch implementations ii python-openvswitch 2.6.1-0ubuntu5.2~cloud0 all Python bindings for Open vSwitch #lsmod status No modules are listing for openvswitch-datapath-dkms #modprobe error modprobe openvswitch modprobe: ERROR: could not insert 'openvswitch': Exec format error --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-127-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory 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 Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: 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
[Kernel-packages] [Bug 1777600] Re: chzdev can't find modprobe
Successfully verified on xenial - adjusting tags accordingly. ** Attachment added: "verification_on_xenial.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777600/+attachment/5204556/+files/verification_on_xenial.txt ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777600 Title: chzdev can't find modprobe Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Invalid Status in s390-tools package in Ubuntu: Fix Released Status in s390-tools source package in Xenial: Fix Committed Status in s390-tools source package in Bionic: Fix Committed Status in s390-tools source package in Cosmic: Fix Released Bug description: [Impact] * chzdev fails to load additional kernel modules at runtime, resulting in failure to activate devices. [Test Case] $ chzdev zfcp --type datarouter=0 dbflevel=5 Should succeed, instead of erroring out / not able to find modprobe. [Regression Potential] * This corrects compiled-in path to /sbin/modprobe, thus making available previously a broken codepath of chzdev. [Other Info] * Original bug report Description: only when trying to change some attributes chzdev fails because it cant find modprobe under Ubuntu 18.04 root@m83lp09:~# chzdev zfcp --type datarouter=0 dbflevel=5 sh: 1: /usr/sbin/modprobe: not found zfcp device type configure failed Error: Command failed (exit code 127): /usr/sbin/modprobe -r zfcp root@m83lp09:~# whereis modprobe modprobe: /sbin/modprobe /etc/modprobe.d /lib/modprobe.d /usr/share/man/man8/modprobe.8.gz Potential solution ? : adding a symlink is a workaround, is this path hardcoded? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1777600/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799471] Re: nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed to build
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1799471 Title: nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: 系统更改了gcc 版本后就n卡不能启动了 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-dkms-390 390.77-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 DKMSKernelVersion: 4.15.0-34-generic Date: Tue Oct 23 21:47:56 2018 DuplicateSignature: dkms:nvidia-dkms-390:390.77-0ubuntu0.18.04.1:cc1: error: unrecognized command line option "-fstack-protector-strong" InstallationDate: Installed on 2018-09-20 (33 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageVersion: 390.77-0ubuntu0.18.04.1 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: nvidia-graphics-drivers-390 Title: nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1799471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799235] Re: kworker process starts at 85% of cpu and stays there
I've now tested with 4.19-rc8. The kworker process remains at about 65% continuously. Not quite sure how to mark this as confirmed, but will try. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799235 Title: kworker process starts at 85% of cpu and stays there Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu starts, w/ /sbin/init, a kworker process that never stops running below 85%: pb@pb-tower:~/Downloads$ ps -elf F S UIDPID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD 4 S root 1 0 0 80 0 - 56471 - 18:30 ?00:00:01 /sbin/init splash 1 S root 2 0 0 80 0 - 0 - 18:30 ?00:00:00 [kthreadd] 1 R root85 2 63 80 0 - 0 - 18:30 ? 00:03:03 [kworker/0:1+kac] After a few hours, grep . -r /sys/firmware/acpi/interrupts/ shows tens of millions of interrupts. The following command line stops the kworker process: echo "disable" > /sys/firmware/acpi/interrupts/gpe6F On the other hand, I haven't been able to properly shut down my system after this command (power never goes off except manually). I believe the bug is related to the one discussed here: https://superuser.com/questions/1117992/acpi-exception-ae-not-found- while-evaluating-gpe-method-floods-syslog The dmesg w/ this report may be somewhat confusing because there is an unsigned module. But w/ the module removed, dmesg gives the following: [0.097480] ACPI: Dynamic OEM Table Load: [0.097480] ACPI: SSDT 0xA07F57173000 000317 (v02 PmRef ApHwp 3000 INTL 20160527) [0.097480] ACPI: Executed 1 blocks of module-level executable AML code [0.100180] ACPI: Dynamic OEM Table Load: [0.100186] ACPI: SSDT 0xA07F577EF400 00030A (v02 PmRef ApCst 3000 INTL 20160527) [0.100473] ACPI: Executed 1 blocks of module-level executable AML code [0.102187] ACPI: Interpreter enabled [0.10] ACPI: (supports S0 S3 S4 S5) [0.102223] ACPI: Using IOAPIC for interrupt routing [0.102275] HEST: Table parsing has been initialized. [0.102277] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [0.103580] ACPI: GPE 0x20 active on init [0.104031] ACPI Error: No handler for Region [WST1] ((ptrval)) [GenericSerialBus] (20170831/evregion-166) [0.104035] ACPI Error: Region GenericSerialBus (ID=9) has no handler (20170831/exfldio-299) [0.104040] Initialized Local Variables for Method [PAS1]: [0.104041] Local0: (ptrval)Integer 0001 [0.104045] No Arguments are initialized for method [PAS1] [0.104046] ACPI Error: Method parse/execution failed \_SB.PCI0.I2C0.PAS1, AE_NOT_EXIST (20170831/psparse-550) [0.104052] ACPI Error: Method parse/execution failed \_GPE._L20, AE_NOT_EXIST (20170831/psparse-550) [0.104058] ACPI Exception: AE_NOT_EXIST, while evaluating GPE method [_L20] (20170831/evgpe-646) [0.104005] ACPI: GPE 0x6F active on init [0.104005] ACPI: Enabled 10 GPEs in block 00 to 7F [0.212126] ACPI: Power Resource [USBC] (on) [0.444270] pci :06:00.0: PME# supported from D0 D1 D2 D3hot [0.444270] pci :06:00.1: [1033:00e0] type 00 class 0x0c0320 [0.444270] pci :06:00.1: reg 0x10: [mem 0xa200-0xa2ff] [0.444278] pci :06:00.1: supports D1 D2 [0.444278] pci :06:00.1: PME# supported from D0 D1 D2 D3hot [0.444278] pci :05:00.0: PCI bridge to [bus 06] [0.444278] pci :05:00.0: bridge window [mem 0xa200-0xa20f] [0.456183] ACPI: PCI Interrupt Link [LNKA] (IRQs) *0 [0.456183] ACPI: PCI Interrupt Link [LNKB] (IRQs) *1 [0.456183] ACPI: PCI Interrupt Link [LNKC] (IRQs) *0 [0.456183] ACPI: PCI Interrupt Link [LNKD] (IRQs) *1 [0.456183] ACPI: PCI Interrupt Link [LNKE] (IRQs) *1 [0.456183] ACPI: PCI Interrupt Link [LNKF] (IRQs) *1 [0.456183] ACPI: PCI Interrupt Link [LNKG] (IRQs) *1 [0.456183] ACPI: PCI Interrupt Link [LNKH] (IRQs) *1 [0.464184] SCSI subsystem initialized [0.464186] libata version 3.00 loaded. [0.464186] pci :00:02.0: vgaarb: setting as boot VGA device [1.225495] Scanning for low memory corruption every 60 seconds [1.226265] Initialise system trusted keyrings [1.226271] Key type blacklist registered [1.226399] workingset: timestamp_bits=36 max_order=23 bucket_order=0 [1.227127] zbud: loaded [1.227482] squashfs: version 4.0 (2009/01/31) Phillip Lougher [1.227769] fuse init (API version 7.26) [1.233972] Key type asymmetric registered [1.233973] Asymmetric key parser 'x509'
[Kernel-packages] [Bug 1799235] Re: kworker process starts at 85% of cpu and stays there
I should add that I issued the following last night: echo "enable" > /sys/firmware/acpi/interrupts/gpe6F And then tried to shut down my system. After 8 minutes, the system had not shut down, so I did so manually. Either the interrupts from the bug are preventing the shutdown or this is a separate problem. I have on occasion been able to complete a shutdown without holding the power key, but this was always with the interrupts enabled. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799235 Title: kworker process starts at 85% of cpu and stays there Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu starts, w/ /sbin/init, a kworker process that never stops running below 85%: pb@pb-tower:~/Downloads$ ps -elf F S UIDPID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD 4 S root 1 0 0 80 0 - 56471 - 18:30 ?00:00:01 /sbin/init splash 1 S root 2 0 0 80 0 - 0 - 18:30 ?00:00:00 [kthreadd] 1 R root85 2 63 80 0 - 0 - 18:30 ? 00:03:03 [kworker/0:1+kac] After a few hours, grep . -r /sys/firmware/acpi/interrupts/ shows tens of millions of interrupts. The following command line stops the kworker process: echo "disable" > /sys/firmware/acpi/interrupts/gpe6F On the other hand, I haven't been able to properly shut down my system after this command (power never goes off except manually). I believe the bug is related to the one discussed here: https://superuser.com/questions/1117992/acpi-exception-ae-not-found- while-evaluating-gpe-method-floods-syslog The dmesg w/ this report may be somewhat confusing because there is an unsigned module. But w/ the module removed, dmesg gives the following: [0.097480] ACPI: Dynamic OEM Table Load: [0.097480] ACPI: SSDT 0xA07F57173000 000317 (v02 PmRef ApHwp 3000 INTL 20160527) [0.097480] ACPI: Executed 1 blocks of module-level executable AML code [0.100180] ACPI: Dynamic OEM Table Load: [0.100186] ACPI: SSDT 0xA07F577EF400 00030A (v02 PmRef ApCst 3000 INTL 20160527) [0.100473] ACPI: Executed 1 blocks of module-level executable AML code [0.102187] ACPI: Interpreter enabled [0.10] ACPI: (supports S0 S3 S4 S5) [0.102223] ACPI: Using IOAPIC for interrupt routing [0.102275] HEST: Table parsing has been initialized. [0.102277] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [0.103580] ACPI: GPE 0x20 active on init [0.104031] ACPI Error: No handler for Region [WST1] ((ptrval)) [GenericSerialBus] (20170831/evregion-166) [0.104035] ACPI Error: Region GenericSerialBus (ID=9) has no handler (20170831/exfldio-299) [0.104040] Initialized Local Variables for Method [PAS1]: [0.104041] Local0: (ptrval)Integer 0001 [0.104045] No Arguments are initialized for method [PAS1] [0.104046] ACPI Error: Method parse/execution failed \_SB.PCI0.I2C0.PAS1, AE_NOT_EXIST (20170831/psparse-550) [0.104052] ACPI Error: Method parse/execution failed \_GPE._L20, AE_NOT_EXIST (20170831/psparse-550) [0.104058] ACPI Exception: AE_NOT_EXIST, while evaluating GPE method [_L20] (20170831/evgpe-646) [0.104005] ACPI: GPE 0x6F active on init [0.104005] ACPI: Enabled 10 GPEs in block 00 to 7F [0.212126] ACPI: Power Resource [USBC] (on) [0.444270] pci :06:00.0: PME# supported from D0 D1 D2 D3hot [0.444270] pci :06:00.1: [1033:00e0] type 00 class 0x0c0320 [0.444270] pci :06:00.1: reg 0x10: [mem 0xa200-0xa2ff] [0.444278] pci :06:00.1: supports D1 D2 [0.444278] pci :06:00.1: PME# supported from D0 D1 D2 D3hot [0.444278] pci :05:00.0: PCI bridge to [bus 06] [0.444278] pci :05:00.0: bridge window [mem 0xa200-0xa20f] [0.456183] ACPI: PCI Interrupt Link [LNKA] (IRQs) *0 [0.456183] ACPI: PCI Interrupt Link [LNKB] (IRQs) *1 [0.456183] ACPI: PCI Interrupt Link [LNKC] (IRQs) *0 [0.456183] ACPI: PCI Interrupt Link [LNKD] (IRQs) *1 [0.456183] ACPI: PCI Interrupt Link [LNKE] (IRQs) *1 [0.456183] ACPI: PCI Interrupt Link [LNKF] (IRQs) *1 [0.456183] ACPI: PCI Interrupt Link [LNKG] (IRQs) *1 [0.456183] ACPI: PCI Interrupt Link [LNKH] (IRQs) *1 [0.464184] SCSI subsystem initialized [0.464186] libata version 3.00 loaded. [0.464186] pci :00:02.0: vgaarb: setting as boot VGA device [1.225495] Scanning for low memory corruption every 60 seconds [1.226265] Initialise system trusted keyrings [1.226271] Key type blacklist registered [1.226399] workingset: timestamp_bits=36 max_order=23 bucket_order=0 [
[Kernel-packages] [Bug 1799411] Re: linux: 4.15.0-39.42 -proposed tracker
** Summary changed: - linux: -proposed tracker + linux: 4.15.0-39.42 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799411 Title: linux: 4.15.0-39.42 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux 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 backports: bug 1799421 (linux-azure), bug 1799422 (linux-azure), bug 1799423 (linux-azure-edge), bug 1799424 (linux-gcp), bug 1799425 (linux-hwe), bug 1799426 (linux-hwe-edge) derivatives: bug 1799412 (linux-raspi2), bug 1799413 (linux-oem), bug 1799414 (linux-aws), bug 1799415 (linux-azure), bug 1799416 (linux-gcp), bug 1799417 (linux-kvm) To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799102] Re: WARNING on boot in Intel GVT-g guest
dmesg with 4.19.0-041900-generic is attached. 4.19-rc8 has the same WARNING on boot. ** Attachment added: "dmesg with 4.19.0-041900-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799102/+attachment/5204537/+files/dmesg ** Tags added: 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/1799102 Title: WARNING on boot in Intel GVT-g guest Status in linux package in Ubuntu: Incomplete Bug description: When booting Ubuntu Cosmic Cuttlefish 18.10 in an Intel GVT-g Virtual Machine, a kernel WARNING appears in dmesg, with the following: [3.563734] WARNING: CPU: 3 PID: 346 at drivers/gpu/drm/i915/i915_irq.c:161 gen3_assert_iir_is_zero+0x38/0xa0 [i915] I have not noticed negative effects in the VM, but a kernel WARNING probably has relevance. While I added a custom EDID to fix resolution, the WARNING happens without custom EDID set too. I will add information about the host in the next message. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: User Name 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1896 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 21 19:44:44 2018 InstallationDate: Installed on 2018-10-18 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IwConfig: lono wireless extensions. ens8 no wireless extensions. Lsusb: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 46f4:0002 Bus 002 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=6cb7fc66-eb2c-4203-9d7d-2aa2665911ac ro quiet splash drm.edid_firmware=EDID_E1941.bin log_buf_len=16M vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-3.0 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.0:cvnQEMU:ct1:cvrpc-i440fx-3.0: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-3.0 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799102/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722478] Re: Two-finger scrolling no longer works after resuming from suspend
Same problem on Thinkpad X1 Carbon 5th Gen with Ubuntu 18.04 Currently using kernel 4.15.0-38-generic Commands in comment #16 resolve the problem until next suspend. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1722478 Title: Two-finger scrolling no longer works after resuming from suspend Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I own a Thinkpad T440p onto which I have had Debian 9 running without hardware issues. I have recently installed Ubuntu 17.10 final beta to test it out, but two-finger scrolling does not work at the moment. It used to work out-of-the-box from the final beta iso, but a subsequent update broke it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghislain 10620 F pulseaudio /dev/snd/controlC0: ghislain 10620 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 09:20:01 2017 HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 20AN00C1UK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET83WW (2.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AN00C1UK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AN00C1UK dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1722478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
what if I can't boot from Ubuntu again and what if I reprogrammed my bios. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Bug description: An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI drivers results in a serial flash that is read only in Intel Broadwell and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set. Symptoms: * BIOS settings cannot be saved * USB Boot impossible * EFI entries read-only. --- Fix: The issue was fixed in kernel version 4.13.0-21 by configuring the kernel so it is not compiled with Intel SPI support. But previous affected machines still suffered from a broken BIOS. Repair: If you still can boot into Ubuntu, you can recover your BIOS with the following steps: 1. Boot into Ubuntu 2. Download http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 3. Install the downloaded package: $ sudo dpkg -i linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 4. Make sure the kernel is installed without any error. Once installed, reboot. 5. At grub, choose the newly installed kernel. You can choose the "recovery" mode. 6. Reboot and go to BIOS settings to confirm your BIOS has been recovered. 7. In case your BIOS is not recovered, reboot to the new kernel, then reboot *once again* to the new kernel, do not enter BIOS settings before the reboot. After the second reboot, check BIOS. 8. If your BIOS issue remains, download another kernel from http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb, and use dpkg to install it, then repeat steps 4 to 6. After your BIOS is fixed, the kernel packages you just installed are no longer needed, you can remove it by running 'sudo dpkg -r linux- image-4.15.0-041500rc6-generic'. The patch used to build the linux v4.15 kernel in step 8 can be found at https://goo.gl/xUKJFR. --- Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Affected Machines: Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Yoga 3 11" Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you)) Acer TravelMate B113 Acer Swift SF314-52 (Fixed by 4.14.9) Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Toshiba Satellite L70-A-13M Dell Inspiron 15-3531 Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix) Acer Aspire E3-111-C0UM HP 14-r012la --- Affected serial flash devices by manufacturer part number, JEDEC ID (SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c) /* ESMT */ f25l32pa, 0x8c2016 f25l32qa, 0x8c4116 f25l64qa, 0x8c4117 /* GigaDevice */ gd25q16, 0xc84015 gd25q32, 0xc84016 gd25lq32, 0xc86016 gd25q64, 0xc84017 gd25lq64c, 0xc86017 gd25q128, 0xc84018 gd25q256, 0xc84019 /* Winbond */ w25q16dw, 0xef6015 w25q32dw, 0xef6016 w25q64dw, 0xef6017 w25q128fw, 0xef6018 --- Original Description: Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766857] Re: [Hyper-V] KVP daemon fails to start
Hi Chris, I added a Cosmic 18.10 bug task. Does this bug only happen in Cosmic, or is it still happening in Bionic? ** Also affects: linux (Ubuntu Cosmic) Importance: High Assignee: Joseph Salisbury (jsalisbury) Status: In Progress ** Also affects: linux-azure (Ubuntu Cosmic) Importance: High Status: Invalid -- 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/1766857 Title: [Hyper-V] KVP daemon fails to start Status in linux package in Ubuntu: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux-azure source package in Bionic: Invalid Status in linux source package in Cosmic: In Progress Status in linux-azure source package in Cosmic: Invalid Bug description: While testing Bionic daily build with kernel 4.15.0-20-generic we saw that there are 2 issues with the KVP daemon: 1. KVP daemon crash after boot. Opened a different bug for this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779640 2. After the KVP daemon is being started the following messages appear: Apr 25 04:45:25 bionicDaily hv_kvp_daemon[1895]: sh: 1: /usr/libexec/hypervkvpd/hv_get_dns_info: not found Apr 25 04:45:25 bionicDaily hv_kvp_daemon[1895]: sh: 1: /usr/libexec/hypervkvpd/hv_get_dhcp_info: not found The above binaries are present on the system, but the their actual path is /usr/sbin/hv_get_dns_info and /usr/sbin/hv_get_dhcp_info. Either the hv_get_dhcp_info and hv_get_dns_info binaries should be placed in the location where the daemon is looking for (/usr/libexec/hypervkvpd/), or the daemon should be set to search for the binaries in the /usr/sbin directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797367] Re: Ubuntu 18.04.1 - [s390x] Kernel panic while stressing network bonding
** Changed in: linux (Ubuntu) Status: Triaged => In Progress ** Changed in: ubuntu-z-systems Status: Confirmed => 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/1797367 Title: Ubuntu 18.04.1 - [s390x] Kernel panic while stressing network bonding Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: == Comment: #0 - Athira Rajeev ---Problem Description--- While running a series of stress tests for network bonding on UBUNTU 18.04.1 with kernel 4.15.0-36.39, kernel panic is observed. There are two instance of panic experienced with the same test procedures one of which indicates to be a kernel BUG. Contact Information = Athira Rajeev , Waiki Wright < wa...@us.ibm.com > ---uname output--- #39-Ubuntu SMP Mon Sep 24 16:13:24 UTC 2018 4.15.0-36.39 Machine Type = This issue is observed on z13 system ---Debugger--- A debugger was configured, ---Steps to Reproduce--- This happens while running stress tests for network bonding. kernel memory exposure attempt is detected and the BUG() is called from the code snippet: mm/usercopy.c:72 dump was configured and crash dump is available. Results of few crash commands like bt, log are added in Attachment Relevant part of dmesg pointing to kernel BUG <<>> [14746.977364] kernel BUG at /build/linux-PABIrW/linux-4.15.0/mm/usercopy.c:72! [14746.977377] illegal operation: 0001 ilc:1 [#1] SMP [14746.977378] Modules linked in: macsec vsock_diag vsock sctp_diag sctp dccp_diag dccp tcp_diag udp_diag raw_diag inet_diag unix_diag af_packet_diag netlink_diag bonding binfmt_misc qeth_l3 8021q garp mrp stp llc xt_tcpudp qeth_l2 nf_conntrack_ipv6 nf_defrag_ipv6 scsi_dh_rdac scsi_dh_emc scsi_dh_alua s390_trng ghash_s390 prng sha512_s390 sha256_s390 sha1_s390 sha_common chsc_sch eadm_sch nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c crc32_vx_s390 qeth ccwgroup ip6table_filter ip6_tables vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio iptable_filter sch_fq_codel ip_tables x_tables aes_s390 des_s390 des_generic dm_crypt dm_service_time dm_multipath zfcp scsi_transport_fc qdio dasd_eckd_mod dasd_mod btrfs xor zstd_compress raid6_pq zlib_deflate [14746.977401] CPU: 1 PID: 20905 Comm: dump2tar Tainted: G OE 4.15.0-36-generic #39-Ubuntu [14746.977403] Hardware name: IBM 3906 M02 757 (LPAR) [14746.977404] Krnl PSW : 0f2d230d 6abe14d5 (__check_object_size+0x15a/0x1e0) [14746.977408]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [14746.977410] Krnl GPRS: 0002 00e95334 0064 0001e6518828 [14746.977412]0037cc8e 00a9577c [14746.977413]647b 0001d8c120a8 0001 8088 [14746.977433]0001d8c0a020 0090da38 0037cc8e 00016fdfbcd0 [14746.977440] Krnl Code: 0037cc82: c0200038ef69larl %r2,a9ab54 0037cc88: c0e5fff32838brasl %r14,1e1cf8 #0037cc8e: a7f40001brc 15,37cc90 >0037cc92: e330d0080004lg %r3,8(%r13) 0037cc98: e320d004lg %r2,0(%r13) 0037cc9e: ecc2001a4065clgrj %r12,%r2,4,37ccd2 0037cca4: b9040013lgr %r1,%r3 0037cca8: ec31ff868064cgrj %r3,%r1,8,37cbb4 [14746.977458] Call Trace: [14746.977460] ([<0037cc8e>] __check_object_size+0x156/0x1e0) [14746.977462] [<0010ac40>] debug_output+0x150/0x2f8 [14746.977464] [<004e02c0>] full_proxy_read+0x80/0xe0 [14746.977466] [<00382592>] vfs_read+0x8a/0x150 [14746.977467] [<00382b2e>] SyS_read+0x66/0xe0 [14746.977469] [<008e3c94>] system_call+0xd8/0x2c8 [14746.977470] Last Breaking-Event-Address: [14746.977472] [<0037cc8e>] __check_object_size+0x156/0x1e0 [14746.977473] <<>> Adding one more occurrence of panic_on_oops below which appears to correlate to above . Stack trace output: Available traces added below Oops output: [ 2140.467261] 8021q: adding VLAN 0 to HW filter on device bond0 [ 2140.467979] IPv6: ADDRCONF(NETDEV_UP): bond0: link is not ready [ 2140.471609] IPv6: ADDRCONF(NETDEV_UP): bond0: link is not ready [ 2140.471610] 8021q: adding VLAN 0 to HW filter on device bond0 [ 2140.472797] IPv6: ADDRCONF(NETDEV_UP): bond0: link is not ready [ 2143.278986] Unable to handle kernel pointer
[Kernel-packages] [Bug 1799470] 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/1799470 Title: slow boot in kubuntu 18.04 Status in linux package in Ubuntu: Confirmed Bug description: I have the bug with the Kubuntu 18.04 sb_release -rd: Description:Ubuntu 18.04.1 LTS Release:18.04 Before, i was using the 16 (LTS) version and the boot was quick. I have first try un update and i have the problem, with a fresh install, i have also the same problem. In the boot, i have a long time (33s) without message and action In this extract of the dmesg, you can see the 33 seconds without messages [5.434266] sdc: sdc1 sdc2 [5.434268] sd 11:0:0:0: [sdd] 537234768 512-byte logical blocks: (275 GB/256 GiB) [5.434288] sd 11:0:0:0: [sdd] Write Protect is off [5.434290] sd 11:0:0:0: [sdd] Mode Sense: 00 3a 00 00 [5.434312] sd 11:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [5.434404] ata12.00: Enabling discard_zeroes_data [5.434436] sd 5:0:0:0: [sdc] Attached SCSI disk [5.435541] sdd: sdd1 sdd2 [5.435661] ata12.00: Enabling discard_zeroes_data [5.435893] sd 11:0:0:0: [sdd] supports TCG Opal [5.435895] sd 11:0:0:0: [sdd] Attached SCSI disk [ 38.317233] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null) [ 38.439463] ip_tables: (C) 2000-2006 Netfilter Core Team [ 38.548456] systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid) [ 38.568547] systemd[1]: Detected architecture x86-64. [ 38.572697] systemd[1]: Set hostname to . [ 38.649301] systemd[1]: Created slice User and Session Slice. [ 38.649610] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. [ 38.649680] systemd[1]: Created slice System Slice. [ 38.649716] systemd[1]: Listening on fsck to fsckd communication Socket. [ 38.649740] systemd[1]: Listening on Device-mapper event daemon FIFOs. [ 38.649760] systemd[1]: Listening on udev Kernel Socket. [ 38.649768] systemd[1]: Reached target Slices. [ 38.667706] EXT4-fs (dm-0): re-mounted. Opts: errors=remount-ro With the command sudo systemd-analyze time [sudo] Mot de passe de jacky : Startup finished in 12.351s (firmware) + 11.414s (loader) + 38.418s (kernel) + 1.902s (userspace) = 1min 4.086s graphical.target reached after 1.898s in userspace You can see the 38 seconds in the kernel mode In the blame, there is any long action sudo systemd-analyze blame 352ms disk-tera.mount 321ms NetworkManager.service 273ms dev-mapper-kubuntu\x2d\x2dvg\x2droot.device 264ms udisks2.service 236ms networkd-dispatcher.service 234ms snapd.service 201ms systemd-logind.service 196ms mpd.service 192ms ModemManager.service 170ms disk-sdb.mount 157ms systemd-timesyncd.service 132ms systemd-resolved.service 130ms accounts-daemon.service 84ms thermald.service 79ms alsa-restore.service 76ms pppd-dns.service 74ms keyboard-setup.service 74ms plymouth-quit.service 71ms systemd-journal-flush.service 68ms wpa_supplicant.service 61ms lvm2-pvscan@8:50.service 58ms gpu-manager.service 57ms colord.service 56ms systemd-udev-trigger.service 53ms systemd-udevd.service 52ms upower.service 51ms packagekit.service 49ms lvm2-monitor.service 49ms apparmor.service 46ms rsyslog.service 44ms user@119.service 42ms systemd-journald.service 41ms grub-common.service 39ms polkit.service 27ms systemd-modules-load.service 27ms plymouth-start.service 26ms user@1000.service 26ms apport.service 23ms systemd-tmpfiles-setup-dev.service 21ms avahi-daemon.service 17ms systemd-remount-fs.service 14ms plymouth-read-write.service 14ms sys-kernel-debug.mount 12ms dev-mqueue.mount 11ms systemd-tmpfiles-clean.service 11ms systemd-tmpfiles-setup.service 10ms dev-hugepages.mount 9ms lvm2-pvscan@8:34.service 9ms systemd-sysctl.service 8ms kerneloops.service
[Kernel-packages] [Bug 1788844] Re: -Excessive undersized/giant packets with intel nic's
** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu) 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/1788844 Title: -Excessive undersized/giant packets with intel nic's Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: With new kernel we get on our switch the following error: W 08/24/18 12:34:47 00327 FFI: ST2-CMDR: port 2/31-Excessive undersized/giant packets. See help. W 08/24/18 12:35:28 00327 FFI: ST2-CMDR: port 2/34-Excessive undersized/giant packets. See help. W 08/24/18 12:37:10 00327 FFI: ST2-CMDR: port 2/33-Excessive undersized/giant packets. See help. The problem is resolved by booting back to kernel 4.15.0-32-generic These are network specifications: root@lb1:~# lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 06) 00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31) 00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31) 00:16.1 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #2 (rev 31) 00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] (rev 31) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #5 (rev f1) 00:1c.5 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #6 (rev f1) 00:1c.6 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #7 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31) 00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31) 01:00.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200e [Pilot] ServerEngines (SEP1) (rev 05) 01:00.1 Co-processor: Emulex Corporation ServerView iRMC HTI 02:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03) 03:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03) 04:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) 04:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) 04:00.2 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) 04:00.3 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-headers-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 24 12:39 seq crw-rw 1 root audio 116, 33 Aug 24 12:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Aug 24 12:57:11 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: FUJITSU PRIMERGY RX1330 M3 PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=d69c3457-31e5-4daf-8d31-1d2022f93c25 ro text RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2018 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V5.0.0.11 R1.18.0 for D3375-B1x dmi.board.name: D3375-B1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3375-B12 WGS03 GS01 dmi.chassis.asset.tag: LB1 dmi.chassis.type: 23 dmi.chassis.vendor: FUJITSU dmi.chassis.version: RX1330M3R6 dmi.modalias:
[Kernel-packages] [Bug 1799470] [NEW] slow boot in kubuntu 18.04
Public bug reported: I have the bug with the Kubuntu 18.04 sb_release -rd: Description:Ubuntu 18.04.1 LTS Release:18.04 Before, i was using the 16 (LTS) version and the boot was quick. I have first try un update and i have the problem, with a fresh install, i have also the same problem. In the boot, i have a long time (33s) without message and action In this extract of the dmesg, you can see the 33 seconds without messages [5.434266] sdc: sdc1 sdc2 [5.434268] sd 11:0:0:0: [sdd] 537234768 512-byte logical blocks: (275 GB/256 GiB) [5.434288] sd 11:0:0:0: [sdd] Write Protect is off [5.434290] sd 11:0:0:0: [sdd] Mode Sense: 00 3a 00 00 [5.434312] sd 11:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [5.434404] ata12.00: Enabling discard_zeroes_data [5.434436] sd 5:0:0:0: [sdc] Attached SCSI disk [5.435541] sdd: sdd1 sdd2 [5.435661] ata12.00: Enabling discard_zeroes_data [5.435893] sd 11:0:0:0: [sdd] supports TCG Opal [5.435895] sd 11:0:0:0: [sdd] Attached SCSI disk [ 38.317233] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null) [ 38.439463] ip_tables: (C) 2000-2006 Netfilter Core Team [ 38.548456] systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid) [ 38.568547] systemd[1]: Detected architecture x86-64. [ 38.572697] systemd[1]: Set hostname to . [ 38.649301] systemd[1]: Created slice User and Session Slice. [ 38.649610] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. [ 38.649680] systemd[1]: Created slice System Slice. [ 38.649716] systemd[1]: Listening on fsck to fsckd communication Socket. [ 38.649740] systemd[1]: Listening on Device-mapper event daemon FIFOs. [ 38.649760] systemd[1]: Listening on udev Kernel Socket. [ 38.649768] systemd[1]: Reached target Slices. [ 38.667706] EXT4-fs (dm-0): re-mounted. Opts: errors=remount-ro With the command sudo systemd-analyze time [sudo] Mot de passe de jacky : Startup finished in 12.351s (firmware) + 11.414s (loader) + 38.418s (kernel) + 1.902s (userspace) = 1min 4.086s graphical.target reached after 1.898s in userspace You can see the 38 seconds in the kernel mode In the blame, there is any long action sudo systemd-analyze blame 352ms disk-tera.mount 321ms NetworkManager.service 273ms dev-mapper-kubuntu\x2d\x2dvg\x2droot.device 264ms udisks2.service 236ms networkd-dispatcher.service 234ms snapd.service 201ms systemd-logind.service 196ms mpd.service 192ms ModemManager.service 170ms disk-sdb.mount 157ms systemd-timesyncd.service 132ms systemd-resolved.service 130ms accounts-daemon.service 84ms thermald.service 79ms alsa-restore.service 76ms pppd-dns.service 74ms keyboard-setup.service 74ms plymouth-quit.service 71ms systemd-journal-flush.service 68ms wpa_supplicant.service 61ms lvm2-pvscan@8:50.service 58ms gpu-manager.service 57ms colord.service 56ms systemd-udev-trigger.service 53ms systemd-udevd.service 52ms upower.service 51ms packagekit.service 49ms lvm2-monitor.service 49ms apparmor.service 46ms rsyslog.service 44ms user@119.service 42ms systemd-journald.service 41ms grub-common.service 39ms polkit.service 27ms systemd-modules-load.service 27ms plymouth-start.service 26ms user@1000.service 26ms apport.service 23ms systemd-tmpfiles-setup-dev.service 21ms avahi-daemon.service 17ms systemd-remount-fs.service 14ms plymouth-read-write.service 14ms sys-kernel-debug.mount 12ms dev-mqueue.mount 11ms systemd-tmpfiles-clean.service 11ms systemd-tmpfiles-setup.service 10ms dev-hugepages.mount 9ms lvm2-pvscan@8:34.service 9ms systemd-sysctl.service 8ms kerneloops.service 8ms ufw.service 8ms blk-availability.service 8ms snapd.seeded.service 7ms systemd-random-seed.service 6ms kmod-static-nodes.service 5ms ureadahead-stop.service 4ms systemd-update-utmp.service 4ms rtkit-daemon.service 4ms dev-mapper-kubuntu\x2d\x2dvg\x2dswap_1.swap 3ms systemd-user-sessions.service 2ms systemd-update-utmp-runlevel.service 2ms console-setup.service ProblemType: Bug
[Kernel-packages] [Bug 1777600] Re: chzdev can't find modprobe
** Changed in: ubuntu-z-systems Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777600 Title: chzdev can't find modprobe Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Invalid Status in s390-tools package in Ubuntu: Fix Released Status in s390-tools source package in Xenial: Fix Committed Status in s390-tools source package in Bionic: Fix Committed Status in s390-tools source package in Cosmic: Fix Released Bug description: [Impact] * chzdev fails to load additional kernel modules at runtime, resulting in failure to activate devices. [Test Case] $ chzdev zfcp --type datarouter=0 dbflevel=5 Should succeed, instead of erroring out / not able to find modprobe. [Regression Potential] * This corrects compiled-in path to /sbin/modprobe, thus making available previously a broken codepath of chzdev. [Other Info] * Original bug report Description: only when trying to change some attributes chzdev fails because it cant find modprobe under Ubuntu 18.04 root@m83lp09:~# chzdev zfcp --type datarouter=0 dbflevel=5 sh: 1: /usr/sbin/modprobe: not found zfcp device type configure failed Error: Command failed (exit code 127): /usr/sbin/modprobe -r zfcp root@m83lp09:~# whereis modprobe modprobe: /sbin/modprobe /etc/modprobe.d /lib/modprobe.d /usr/share/man/man8/modprobe.8.gz Potential solution ? : adding a symlink is a workaround, is this path hardcoded? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1777600/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798185] Re: Enable CONFIG_INFINIBAND_USER_MAD
We are also setting CONFIG_INFINIBAND_IPOIB=y. -- 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/1798185 Title: Enable CONFIG_INFINIBAND_USER_MAD Status in linux-azure package in Ubuntu: Triaged Status in linux-azure source package in Bionic: Fix Committed Bug description: Please enable CONFIG_INFINIBAND_USER_MAD in the linux-azure kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1798185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777600] Please test proposed package
Hello bugproxy, or anyone else affected, Accepted s390-tools into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/s390-tools/2.3.0-0ubuntu3.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. 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 for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777600 Title: chzdev can't find modprobe Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Invalid Status in s390-tools package in Ubuntu: Fix Released Status in s390-tools source package in Xenial: Fix Committed Status in s390-tools source package in Bionic: Fix Committed Status in s390-tools source package in Cosmic: Fix Released Bug description: [Impact] * chzdev fails to load additional kernel modules at runtime, resulting in failure to activate devices. [Test Case] $ chzdev zfcp --type datarouter=0 dbflevel=5 Should succeed, instead of erroring out / not able to find modprobe. [Regression Potential] * This corrects compiled-in path to /sbin/modprobe, thus making available previously a broken codepath of chzdev. [Other Info] * Original bug report Description: only when trying to change some attributes chzdev fails because it cant find modprobe under Ubuntu 18.04 root@m83lp09:~# chzdev zfcp --type datarouter=0 dbflevel=5 sh: 1: /usr/sbin/modprobe: not found zfcp device type configure failed Error: Command failed (exit code 127): /usr/sbin/modprobe -r zfcp root@m83lp09:~# whereis modprobe modprobe: /sbin/modprobe /etc/modprobe.d /lib/modprobe.d /usr/share/man/man8/modprobe.8.gz Potential solution ? : adding a symlink is a workaround, is this path hardcoded? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1777600/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777600] Re: chzdev can't find modprobe
Hello bugproxy, or anyone else affected, Accepted s390-tools into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/s390-tools/1.34.0-0ubuntu8.8 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 for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: s390-tools (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial ** Changed in: s390-tools (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777600 Title: chzdev can't find modprobe Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Invalid Status in s390-tools package in Ubuntu: Fix Released Status in s390-tools source package in Xenial: Fix Committed Status in s390-tools source package in Bionic: Fix Committed Status in s390-tools source package in Cosmic: Fix Released Bug description: [Impact] * chzdev fails to load additional kernel modules at runtime, resulting in failure to activate devices. [Test Case] $ chzdev zfcp --type datarouter=0 dbflevel=5 Should succeed, instead of erroring out / not able to find modprobe. [Regression Potential] * This corrects compiled-in path to /sbin/modprobe, thus making available previously a broken codepath of chzdev. [Other Info] * Original bug report Description: only when trying to change some attributes chzdev fails because it cant find modprobe under Ubuntu 18.04 root@m83lp09:~# chzdev zfcp --type datarouter=0 dbflevel=5 sh: 1: /usr/sbin/modprobe: not found zfcp device type configure failed Error: Command failed (exit code 127): /usr/sbin/modprobe -r zfcp root@m83lp09:~# whereis modprobe modprobe: /sbin/modprobe /etc/modprobe.d /lib/modprobe.d /usr/share/man/man8/modprobe.8.gz Potential solution ? : adding a symlink is a workaround, is this path hardcoded? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1777600/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762385] Re: dell_wmi: Unknown key codes
Tested xenial live session with stock systemd/udev and upgraded one from proposed. My dell laptop is not affected by this issue. But at least rfkill keys still work for me with both old and new systemd/udevd and there are no error messages in dmesg. ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762385 Title: dell_wmi: Unknown key codes Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * Bogus keycode messages produced by the kernel / user annoyance * rfkill keyboard shortcuts not working as intended on some Dell machines [Test Case] * check that there are no spurious kernel messages about unknown keys in journalctl upon RFKill key presses * check that RFKill key presses work correctly and kill/restore RF capabilities [Regression Potential] * The change is scoped to particular SKUs and thus should only affect them * It is related to matching gsd support, which is in-place on xenial and up [Solution] Cherrypick upstream commit https://github.com/systemd/systemd/commit/cab01e9ecf1c69656785e64f5fc94cd4ed09e57f [Original Bug report] RFKill key produces these messages in kernel log: dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed This key code is a notification and should be added as KEY_IGNORE here: https://github.com/torvalds/linux/blob/master/drivers/platform/x86 /dell-wmi.c#L263 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-generic 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmig 2737 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 18:09:03 2018 InstallationDate: Installed on 2018-03-27 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: Dell Inc. Inspiron 5379 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0C6J64 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1762385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
