[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions
Hi Joseph, We're continuing the investigation into this issue, and I was wondering if you and Nabuto could provide what the last point you had reached was, and/or next step you were going to do. >From what I can summarize (please confirm/correct): * Artful (4.13.*) kernels (with any Artful config) is good * Artful (4.13.*) kernels (with any Xenial config) is also bad * 4.12-rc4 - relatively good (1.x%) but still not 0% (<5%) * 4.12-rc3 - also bad (~ 27%) * Xenial (4.4.*) kernels (with any Xenial config) is bad * Xenial (4.4.*) kernels (with any Artful config) is still bad [data point: 4.12-rc4 with Artful configs is good. 4.12-rc4 with Xenial configs is bad.] So a kernel change + config change results in masked/fixed behavior, I guess? Is the remaining bisect window basically 4.12-rc4 -> 4.13 ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+subscriptions
[Kernel-packages] [Bug 1775764] 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/1775764 Title: Unable to switch VTs - screen frozen Status in linux package in Ubuntu: Confirmed Bug description: Prior to doing any Gnome Shell development I always disable the existing instance by dropping back to a non-graphical runlevel: sudo systemctl start multi-user.target At least half the time this works. But the other half the time the screen freezes and I am not able to interact with it or switch VTs. Even a remote login can't force a VT switch: sudo chvt 4 # just hangs The kernel log shows no errors at all. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.10-0ubuntu3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Jun 8 13:21:38 2018 InstallationDate: Installed on 2018-05-26 (12 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 17ef:6009 Lenovo ThinkPad Keyboard with TrackPoint Bus 001 Device 003: ID 045e:0047 Microsoft Corp. IntelliMouse Explorer 3.0 Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 10M7CTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d7ecc709-02c2-4413-b7e7-dfce1d2b3703 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.174 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: M16KT47A dmi.board.name: 3102 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN 3259627060530 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone: dmi.product.family: ThinkCentre M710s dmi.product.name: 10M7CTO1WW dmi.product.version: ThinkCentre M710s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775764/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775764] [NEW] Unable to switch VTs - screen frozen
Public bug reported: Prior to doing any Gnome Shell development I always disable the existing instance by dropping back to a non-graphical runlevel: sudo systemctl start multi-user.target At least half the time this works. But the other half the time the screen freezes and I am not able to interact with it or switch VTs. Even a remote login can't force a VT switch: sudo chvt 4 # just hangs The kernel log shows no errors at all. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.10-0ubuntu3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Jun 8 13:21:38 2018 InstallationDate: Installed on 2018-05-26 (12 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 17ef:6009 Lenovo ThinkPad Keyboard with TrackPoint Bus 001 Device 003: ID 045e:0047 Microsoft Corp. IntelliMouse Explorer 3.0 Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 10M7CTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d7ecc709-02c2-4413-b7e7-dfce1d2b3703 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.174 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: M16KT47A dmi.board.name: 3102 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN 3259627060530 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone: dmi.product.family: ThinkCentre M710s dmi.product.name: 10M7CTO1WW dmi.product.version: ThinkCentre M710s dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug cosmic ** Description changed: - Prior to doing any Gnome Shell work I always disable the existing + Prior to doing any Gnome Shell development I always disable the existing instance by dropping back to a non-graphical runlevel: - sudo systemctl start multi-user.target + sudo systemctl start multi-user.target At least half the time this works. But the other half the time the screen freezes and I am not able to interact with it or switch VTs. Even a remote login can't force a VT switch: - sudo chvt 4 # just hangs + sudo chvt 4 # just hangs ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.10-0ubuntu3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Jun 8 13:21:38 2018 InstallationDate: Installed on 2018-05-26 (12 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 004: ID 17ef:6009 Lenovo ThinkPad Keyboard with TrackPoint - Bus 001 Device 003: ID 045e:0047 Microsoft Corp. IntelliMouse Explorer 3.0 - Bus 001 Device 002: ID 8087:0a2b Intel Corp. - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 17ef:6009 Lenovo ThinkPad Keyboard with TrackPoint + Bus 001 Device 003: ID 045e:0047 Microsoft Corp. IntelliMouse Explorer 3.0 + Bus 001 Device 002: ID 8087:0a2b Intel Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 10M7CTO1WW ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) -
[Kernel-packages] [Bug 1772927] Re: linux: 4.15.0-23.25 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Taihsiang Ho (taihsiangho) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772927 Title: linux: 4.15.0-23.25 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: 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 1772935 (linux-hwe-edge), bug 1772940 (linux-azure), bug 1772942 (linux-azure-edge) derivatives: bug 1772929 (linux-raspi2), bug 1772930 (linux-azure), bug 1772931 (linux-aws), bug 1772932 (linux-kvm), bug 1772933 (linux-oem), bug 1772934 (linux-gcp) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1760172] Re: Not Work: usb 3-1.3: New USB device found, idVendor=0bda, idProduct=a811
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1760172 Title: Not Work: usb 3-1.3: New USB device found, idVendor=0bda, idProduct=a811 Status in linux package in Ubuntu: Expired Bug description: Hello dmesg: [ 75.043376] usb 3-1.3: new high-speed USB device number 5 using xhci_hcd [ 75.155709] usb 3-1.3: New USB device found, idVendor=0bda, idProduct=a811 [ 75.155715] usb 3-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 75.155719] usb 3-1.3: Product: 802.11ac WLAN Adapter [ 75.155722] usb 3-1.3: Manufacturer: Realtek [ 75.155726] usb 3-1.3: SerialNumber: 00e04c01 Regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1817 F pulseaudio CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Fri Mar 30 15:12:03 2018 InstallationDate: Installed on 2017-10-13 (168 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-13-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760172/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775583] 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 1775583 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-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1775583 Title: Wifi drops out, takes 5 mins to recover Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: New Bug description: My wifi used to be solid, but recently it's started dropping out 2-3 times a day. Looking in the logs the only thing I see that may be relevant is: Jun 07 11:57:07 laptop kernel: brcmfmac: brcmf_msgbuf_query_dcmd: Timeout on response for query command Jun 07 11:57:07 laptop kernel: brcmfmac: brcmf_run_escan: error (-5) Jun 07 11:57:07 laptop kernel: brcmfmac: brcmf_cfg80211_scan: scan error (-5) Jun 07 11:57:10 laptop kernel: brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -21 Jun 07 11:57:14 laptop kernel: brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 Jun 07 11:57:56 laptop kernel: brcmfmac: brcmf_cfg80211_escan_handler: scan not ready, bsscfgidx=0 Jun 07 11:57:56 laptop kernel: brcmfmac: brcmf_fweh_event_worker: event handler failed (69) Jun 07 11:58:17 laptop kernel: brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 I was wondering if it's similar to https://bugzilla.redhat.com/show_bug.cgi?id=1528291 Other info: $ lspci -vnn | grep -i net 02:00.0 Network controller [0280]: Broadcom Limited BCM43602 802.11ac Wireless LAN SoC [14e4:43ba] (rev 01) $ lsmod | grep brcmfmac brcmfmac 315392 0 brcmutil 16384 1 brcmfmac cfg80211 622592 1 brcmfmac $ uname -a Linux laptop 4.15.0-22-generic #24-Ubuntu SMP Wed May 16 12:15:17 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 Date: Thu Jun 7 12:01:23 2018 Dependencies: InstallationDate: Installed on 2018-04-07 (61 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775583] Re: Wifi drops out, takes 5 mins to recover
** Also 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-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1775583 Title: Wifi drops out, takes 5 mins to recover Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: New Bug description: My wifi used to be solid, but recently it's started dropping out 2-3 times a day. Looking in the logs the only thing I see that may be relevant is: Jun 07 11:57:07 laptop kernel: brcmfmac: brcmf_msgbuf_query_dcmd: Timeout on response for query command Jun 07 11:57:07 laptop kernel: brcmfmac: brcmf_run_escan: error (-5) Jun 07 11:57:07 laptop kernel: brcmfmac: brcmf_cfg80211_scan: scan error (-5) Jun 07 11:57:10 laptop kernel: brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -21 Jun 07 11:57:14 laptop kernel: brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 Jun 07 11:57:56 laptop kernel: brcmfmac: brcmf_cfg80211_escan_handler: scan not ready, bsscfgidx=0 Jun 07 11:57:56 laptop kernel: brcmfmac: brcmf_fweh_event_worker: event handler failed (69) Jun 07 11:58:17 laptop kernel: brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 I was wondering if it's similar to https://bugzilla.redhat.com/show_bug.cgi?id=1528291 Other info: $ lspci -vnn | grep -i net 02:00.0 Network controller [0280]: Broadcom Limited BCM43602 802.11ac Wireless LAN SoC [14e4:43ba] (rev 01) $ lsmod | grep brcmfmac brcmfmac 315392 0 brcmutil 16384 1 brcmfmac cfg80211 622592 1 brcmfmac $ uname -a Linux laptop 4.15.0-22-generic #24-Ubuntu SMP Wed May 16 12:15:17 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 Date: Thu Jun 7 12:01:23 2018 Dependencies: InstallationDate: Installed on 2018-04-07 (61 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775586] Re: after S3 bt icon shows disable
** Tags added: lp1775169 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem in Ubuntu. https://bugs.launchpad.net/bugs/1775586 Title: after S3 bt icon shows disable Status in OEM Priority Project: New Status in linux-meta-oem package in Ubuntu: New Bug description: machine: WHN7-DVT2-C7 (201803-26164) Bus 001 Device 005: ID 8087:0025 Intel Corp. the steps to reproduce: 1. flash install whole system 2. install latest linux-oem and linux-firmware 3. reboot 4. press wireless key to disable wireless/bt 5. press wireless key to enable wireless/bt 6. trigger S3 by clicking right top icon 7. bluetooth get disabled after S3 resume. <= issue 8. bluetooth could be re-enabled by clicking UI. but if you install latest mainline kernel 4.17.0-rc7, this issue can not be reproduced. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-oem 4.13.0.1028.33 ProcVersionSignature: Ubuntu 4.13.0-1028.31-oem 4.13.16 Uname: Linux 4.13.0-1028-oem x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 7 19:11:10 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-osp1-20171027-1 InstallationDate: Installed on 2018-06-07 (0 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20171027-10:57 SourcePackage: linux-meta-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1775586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773940] Re: Enable AMD PCIe MP2 for AMDI0011
I can confirm the AMDI0011 is enabled and touchpad works. ** 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-oem in Ubuntu. https://bugs.launchpad.net/bugs/1773940 Title: Enable AMD PCIe MP2 for AMDI0011 Status in HWE Next: New Status in linux-oem package in Ubuntu: New Bug description: ===SRU Justification=== [Impact] Touchpad doesn't work on Latitude 5495. [Test] I can confirm the driver from AMD works. All issues found by us should be fixed. [Fix] The touchpad connects to AMDI0011, which doesn't have any driver until now. I'll backport the patch to A/B/C once it's in mainline and gets thoroughly tested. [Regression Potential] Low. It's a new driver, shouldn't affect any other device. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1773940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767088] Re: regression Aquantia Corp. AQC107 4.15.0-13-generic -> 4.15.0-20-generic ?
For linux-oem, it's a vendor request, I don't have a reproducer but the driver is newer. Mark as done. ** 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-oem in Ubuntu. https://bugs.launchpad.net/bugs/1767088 Title: regression Aquantia Corp. AQC107 4.15.0-13-generic -> 4.15.0-20-generic ? Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: New Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Invalid Bug description: Anyone can confirm the atlantic kernel driver is not working with bionic 4.15.0-20-generic? The only thing I changed is installing kernel and modules 4.15.0-13-generic to get it working with the same packages and software. ethtool gives me this info: # ethtool diff 4.15.0-13-generic -> 4.15.0-20-generic 19c19 < Speed: 1Mb/s --- > Speed: Unknown! 26c26 < Link detected: yes --- > Link detected: no # ethtool -d diff 4.15.0-13-generic -> 4.15.0-20-generic 4,12c4,12 < 0x0010: 00 00 00 00 00 c0 64 c8 07 00 00 00 00 04 00 80 < 0x0020: 00 00 00 00 ff 03 00 00 08 00 00 00 04 00 00 00 < 0x0030: 00 00 00 00 00 80 0c d9 07 00 00 00 00 04 00 80 < 0x0040: 00 00 00 00 ff 03 00 00 08 00 00 00 04 00 00 00 < 0x0050: 00 00 00 00 00 40 68 c8 07 00 00 00 00 04 00 80 < 0x0060: 00 00 00 00 ff 03 00 00 08 00 00 00 04 00 00 00 < 0x0070: 00 00 00 00 00 80 c6 cc 07 00 00 00 00 04 00 80 < 0x0080: 00 00 00 00 ff 03 00 00 08 00 00 00 04 00 00 00 < 0x0090: 00 00 00 00 00 00 7e c8 07 00 00 00 00 10 00 80 --- > 0x0010: 00 00 00 00 00 c0 ae fc 07 00 00 00 00 04 00 80 > 0x0020: 00 00 00 00 ff 03 00 00 0b 00 00 00 04 00 00 00 > 0x0030: 00 00 00 00 00 00 b6 fc 07 00 00 00 00 04 00 80 > 0x0040: 00 00 00 00 ff 03 00 00 0b 00 00 00 04 00 00 00 > 0x0050: 00 00 00 00 00 40 b6 fc 07 00 00 00 00 04 00 80 > 0x0060: 00 00 00 00 ff 03 00 00 0b 00 00 00 04 00 00 00 > 0x0070: 00 00 00 00 00 00 be fc 07 00 00 00 00 04 00 80 > 0x0080: 00 00 00 00 ff 03 00 00 0b 00 00 00 04 00 00 00 > 0x0090: 00 00 00 00 00 00 af fc 07 00 00 00 00 10 00 80 14c14 < 0x00b0: 00 00 00 00 00 00 00 00 00 00 33 dc 07 00 00 00 --- > 0x00b0: 00 00 00 00 00 00 00 00 00 00 b3 fc 07 00 00 00 16c16 < 0x00d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 86 d6 --- > 0x00d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b7 fc 19c19 < 0x0100: 00 00 2b dd 07 00 00 00 00 10 00 80 00 00 00 00 --- > 0x0100: 00 00 bb fc 07 00 00 00 00 10 00 80 00 00 00 00 24c24 < 0x0150: 02 00 01 00 0e 5a de d2 00 be b0 1f 00 00 00 00 --- > 0x0150: 02 00 00 00 00 00 00 00 00 be b0 1f 00 00 00 00 Thanks. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-04 (22 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=ZFS=tank/root ro root=ZFS=tank/root boot=zfs zfs.zfs_arc_max=19327352832 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/14/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: C226M WS dmi.board.vendor: ASRockRack dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias:
[Kernel-packages] [Bug 1772626] Re: [Redpine] HCI command timeout after resume from S4
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1772626 Title: [Redpine] HCI command timeout after resume from S4 Status in HWE Next: Confirmed Status in linux-oem package in Ubuntu: Confirmed Status in linux-oem source package in Bionic: Fix Committed Bug description: Redpine BT stops working after resume from S4. Symptoms: - The device list is increasing after resume. - Error after command "hciconfig -a" which as: Can't read local name on hci0: Connection timed out (110) The reproduce steps: 1) Go to hibernate mode $ sudo systemctl hibernate 2) Wakeup system by power recycle 3) Check the bluetooth list $ hciconfig -a hci1: Type: Primary Bus: SDIO BD Address: 00:23:A7:BF:34:F8 ACL MTU: 540:2 SCO MTU: 30:1 DOWN RX bytes:574 acl:0 sco:0 events:30 errors:0 TX bytes:0 acl:0 sco:0 commands:30 errors:0 Features: 0x3f 0x02 0x04 0x4e 0xc8 0x0d 0x5b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 Link policy: RSWITCH Link mode: SLAVE ACCEPT hci0: Type: Primary Bus: SDIO BD Address: 00:23:A7:BF:34:F8 ACL MTU: 540:2 SCO MTU: 30:1 UP RUNNING RX bytes:1238 acl:0 sco:0 events:75 errors:0 TX bytes:0 acl:0 sco:0 commands:75 errors:0 Features: 0x3f 0x02 0x04 0x4e 0xc8 0x0d 0x5b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 Link policy: RSWITCH Link mode: SLAVE ACCEPT Can't read local name on hci0: Connection timed out (110) 4) Go to hibernate and wake again(as step 1-2) 5) Try ifconfig command to check wifi device Result: command no response This bug is for tracking purposes only, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1772626/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774606] Re: [Redpine] Wifi AP does not work
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1774606 Title: [Redpine] Wifi AP does not work Status in HWE Next: New Status in linux-oem package in Ubuntu: Confirmed Status in linux-oem source package in Bionic: Fix Committed Bug description: WiFi AP can not be enabled in Ubuntu Server 18.04 with Redpine driver for 4.15 kernel. Several issues were observed in Redpine driver which supports RS9113 Wifi+BT combo chip: 1. 40Mhz connection issue 2. Mode 1,13,14,4,6 change issue 3. SoftAP failure issue This bug is of tracking purposes only, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1774606/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1753510] Re: Cannot boot/install AMD Ryzen 2400G
with 4.17 (is that what is meant by "mainline" ) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1753510 Title: Cannot boot/install AMD Ryzen 2400G Status in linux package in Ubuntu: Confirmed Bug description: Did a motherboard swap on a trusty old computer that ran ubuntu for 10 years or so. Now it only runs windows (same hardware fresh installs windows with no issue). brand new ryzen 2nd gen with graphics. I know about graphics drivers issues, wasn't expecting that to be dealt with. Just trying to use it as a cpu. So I put in an older (RADEON HD 7850 pitcairn) video card to get some functionality. Without the video card, it boots, but the display is unusable. I can ssh in and see that it works fine as a server, but cannot use terminal or graphical display. With the video card, Put daily ubuntu Bionic image, and "Try Ubuntu", and it goes into an infinite loop. photo attached. I tried 16.04.4 and I think it just went into a blank screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753510/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices
There hasn't been a bluez update to 16.04 since last year. And here hasn't been a kernel update to 16.04 since last month; the same goes for linux-firmware. So I'm not sure what changed for you Zero. Are you using 16.04? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1745828 Title: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: It is ON and VISIBLE in the control panel. My iPhone can see two other devices but it can't see the computer, and the computer can't see anything, even if left searching for tens of minutes. The previous answers listed below suggest the following diagnostics Bluetooth not working after update How can I make my bluetooth works on Ubuntu 16.04? Ubuntu 16.04 bluetooth not working (Dell XPS13) Bluetooth (Atheros AR3012) not working on Ubuntu 16.04 Bluetooth not working on Ubuntu 16.04 LTS Bluetooth cannot find any devices Stuck on a bluetooth problem The service seems to be running /home >sudo service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago Docs: man:bluetoothd(8) Main PID: 790 (bluetoothd) Status: "Running" CGroup: /system.slice/bluetooth.service └─790 /usr/lib/bluetooth/bluetoothd Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.87 Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.87 Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for Headset Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.12 Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.12 Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for Headset Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. and not blocked /home >rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no I have edited /etc/bluetooth/main.conf to include AutoEnable=true but I noted that the entire file was commented out. The kernel seems reasonably up to date >uname -a Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I wonder if I need a device driver, but I have no idea how to find out. The following diagnostics may help some of you knowledgeable people find out. >hcitool dev Devices: hci0 24:0A:64:F5:EE:86 and the output of dmsg is >dmesg | grep Blue [2.030855] usb 1-1.4: Product: Bluetooth Radio [ 13.806355] Bluetooth: Core ver 2.22 [ 13.806369] Bluetooth: HCI device and connection manager initialized [ 13.806372] Bluetooth: HCI socket layer initialized [ 13.806373] Bluetooth: L2CAP socket layer initialized [ 13.806377] Bluetooth: SCO socket layer initialized [ 13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a lmp_ver=06 lmp_subver=8821 [ 13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin [ 13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin [ 13.877382] Bluetooth: hci0: rom_version status=0 version=1 [ 13.877387] Bluetooth: cfg_sz 0, total size 17428 [ 16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 16.550281] Bluetooth: BNEP filters: protocol multicast [ 16.550284] Bluetooth: BNEP socket layer initialized [ 27.868345] Bluetooth: RFCOMM TTY layer initialized [ 27.868350] Bluetooth: RFCOMM socket layer initialized [ 27.868354] Bluetooth: RFCOMM ver 1.11 and of lsusb is >lsusb Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 13d3:3414 IMC Networks Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001
[Kernel-packages] [Bug 1753510] Re: Cannot boot/install AMD Ryzen 2400G
OK updated firmware, including amdgpu. now it does this: ** Attachment added: "IMG_20180607_204918.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753510/+attachment/5150033/+files/IMG_20180607_204918.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1753510 Title: Cannot boot/install AMD Ryzen 2400G Status in linux package in Ubuntu: Confirmed Bug description: Did a motherboard swap on a trusty old computer that ran ubuntu for 10 years or so. Now it only runs windows (same hardware fresh installs windows with no issue). brand new ryzen 2nd gen with graphics. I know about graphics drivers issues, wasn't expecting that to be dealt with. Just trying to use it as a cpu. So I put in an older (RADEON HD 7850 pitcairn) video card to get some functionality. Without the video card, it boots, but the display is unusable. I can ssh in and see that it works fine as a server, but cannot use terminal or graphical display. With the video card, Put daily ubuntu Bionic image, and "Try Ubuntu", and it goes into an infinite loop. photo attached. I tried 16.04.4 and I think it just went into a blank screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753510/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772931] Re: linux-aws: 4.15.0-1010.10 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- 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/1772931 Title: linux-aws: 4.15.0-1010.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed 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 -- boot-testing-requested: true kernel-stable-master-bug: 1772927 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772931/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772932] Re: linux-kvm: 4.15.0-1011.11 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- 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/1772932 Title: linux-kvm: 4.15.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed 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 -- boot-testing-requested: true kernel-stable-master-bug: 1772927 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772932/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772930] Re: linux-azure: 4.15.0-1013.13 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1772930 Title: linux-azure: 4.15.0-1013.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772927 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775732] 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/1775732 Title: arm64 soft lock crashes on nova-compute charm running Status in linux package in Ubuntu: Confirmed Bug description: Discovered on bionic, arm64 (Moonshot, verified on multiple swirlix cartridges), 4.15.0-22-generic. After deploying the nova-compute Juju charm, on subsequent reboots, within a few seconds after complete boot, everything will freeze and eventually display on the serial console (just these, no traces): [ 188.010510] watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [juju-log:2272] [ 216.010292] watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [juju-log:2272] (From here on, "lock up" refers to that sequence: boot a kernel, it completes boot to login prompt, then everything freezes a few seconds later, then BUGs.) It's usually but not always juju-log, sometimes a relation-ids or similar. I was able to briefly notice that it was in its startup config-changed hook. I've separated out and tested nearly everything it does during its startup config-changed (sets up bridging, writes some config files, restarts libvirtd/nova-compute/etc) without being able to trigger the bug, but I suspect proximity to boot is a factor. If I disable jujud- unit-nova-compute startup, boot, log in, re-enable and start (by which time over a minute or so has elapsed from boot finish), it will not lock up. Similarly, if I wrap the jujud startup in a `strace -Ff -o /var/log/strace.log` (which slows it down massively), it will not lock up. Watched pot syndrome. I've tried kernels from http://kernel.ubuntu.com/~kernel-ppa/mainline/ . I noticed most of the recent arm64 mainline kernels had failed builds, notified the kernel team channel and apw fixed the issue and started some rebuilds. What I've discovered (after many dead ends and a futile bisection) is that mainline builds before the rebuilds lock up, but fixed mainline builds initiated by apw DO NOT lock up. e.g. 4.16.3-041603.201804190730 locks up, but 4.16.6-041606.201806042022 does not lock up. (4.16.4 and 4.16.5 appear to have never been rebuilt and don't have arm64 debs, and that period is what I tried to bisect after figuring a fix must be in there.) But when I try to compile any of these recent kernels myself, they lock up when booted. Same kernel configs, tried on both bionic and in a cosmic chroot, tried both native arm64 compile and cross-compile from amd64. e.g. 4.16.6-041606.201806042022 from k.u.c does not lock up, but when I build it myself, it does. TBC, I've verified lock ups on the following kernels (all assume kernel configs from their respective Ubuntu or k.u.c mainline builds): - 4.15.0-22-generic from bionic (both Ubuntu-provided and my own recompile) - v4.16 (and all point releases) - v4.17 As I write this, my compiled v4.10 DOES NOT appear to lock up. I will attempt to bisect at a macro level from 4.10..4.15 and dig deeper. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 2 04:22 seq crw-rw 1 root audio 116, 33 Jun 2 04:22 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Jun 8 00:13:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775732/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775732] [NEW] arm64 soft lock crashes on nova-compute charm running
Public bug reported: Discovered on bionic, arm64 (Moonshot, verified on multiple swirlix cartridges), 4.15.0-22-generic. After deploying the nova-compute Juju charm, on subsequent reboots, within a few seconds after complete boot, everything will freeze and eventually display on the serial console (just these, no traces): [ 188.010510] watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [juju-log:2272] [ 216.010292] watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [juju-log:2272] (From here on, "lock up" refers to that sequence: boot a kernel, it completes boot to login prompt, then everything freezes a few seconds later, then BUGs.) It's usually but not always juju-log, sometimes a relation-ids or similar. I was able to briefly notice that it was in its startup config-changed hook. I've separated out and tested nearly everything it does during its startup config-changed (sets up bridging, writes some config files, restarts libvirtd/nova-compute/etc) without being able to trigger the bug, but I suspect proximity to boot is a factor. If I disable jujud- unit-nova-compute startup, boot, log in, re-enable and start (by which time over a minute or so has elapsed from boot finish), it will not lock up. Similarly, if I wrap the jujud startup in a `strace -Ff -o /var/log/strace.log` (which slows it down massively), it will not lock up. Watched pot syndrome. I've tried kernels from http://kernel.ubuntu.com/~kernel-ppa/mainline/ . I noticed most of the recent arm64 mainline kernels had failed builds, notified the kernel team channel and apw fixed the issue and started some rebuilds. What I've discovered (after many dead ends and a futile bisection) is that mainline builds before the rebuilds lock up, but fixed mainline builds initiated by apw DO NOT lock up. e.g. 4.16.3-041603.201804190730 locks up, but 4.16.6-041606.201806042022 does not lock up. (4.16.4 and 4.16.5 appear to have never been rebuilt and don't have arm64 debs, and that period is what I tried to bisect after figuring a fix must be in there.) But when I try to compile any of these recent kernels myself, they lock up when booted. Same kernel configs, tried on both bionic and in a cosmic chroot, tried both native arm64 compile and cross-compile from amd64. e.g. 4.16.6-041606.201806042022 from k.u.c does not lock up, but when I build it myself, it does. TBC, I've verified lock ups on the following kernels (all assume kernel configs from their respective Ubuntu or k.u.c mainline builds): - 4.15.0-22-generic from bionic (both Ubuntu-provided and my own recompile) - v4.16 (and all point releases) - v4.17 As I write this, my compiled v4.10 DOES NOT appear to lock up. I will attempt to bisect at a macro level from 4.10..4.15 and dig deeper. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 2 04:22 seq crw-rw 1 root audio 116, 33 Jun 2 04:22 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Jun 8 00:13:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug arm64 bionic uec-images -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775732 Title: arm64 soft lock crashes on nova-compute charm running Status in linux package in Ubuntu: Confirmed Bug description: Discovered on bionic, arm64 (Moonshot, verified on multiple swirlix cartridges), 4.15.0-22-generic. After deploying the nova-compute Juju charm, on subsequent reboots, within a few seconds after complete boot, everything will freeze and eventually display on the serial console (just these, no traces): [ 188.010510] watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [juju-log:2272] [ 216.010292] watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [juju-log:2272] (From here on, "lock up" refers to that
[Kernel-packages] [Bug 1775477] Re: Xenial update to 4.4.133 stable release
** Changed in: linux (Ubuntu Xenial)
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/1775477
Title:
Xenial update to 4.4.133 stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The 4.4.133 upstream stable
patch set is now available. It should be included in the Ubuntu
kernel as well.
git://git.kernel.org/
TEST CASE: TBD
The following patches from the 4.4.133 stable release shall be applied:
* 8139too: Use disable_irq_nosync() in rtl8139_poll_controller()
* bridge: check iface upper dev when setting master via ioctl
* dccp: fix tasklet usage
* ipv4: fix memory leaks in udp_sendmsg, ping_v4_sendmsg
* llc: better deal with too small mtu
* net: ethernet: sun: niu set correct packet size in skb
* net/mlx4_en: Verify coalescing parameters are in range
* net_sched: fq: take care of throttled flows before reuse
* net: support compat 64-bit time in {s,g}etsockopt
* openvswitch: Don't swap table in nlattr_set() after OVS_ATTR_NESTED is found
* qmi_wwan: do not steal interfaces from class drivers
* r8169: fix powering up RTL8168h
* sctp: handle two v4 addrs comparison in sctp_inet6_cmp_addr
* sctp: use the old asoc when making the cookie-ack chunk in dupcook_d
* tg3: Fix vunmap() BUG_ON() triggered from tg3_free_consistent().
* bonding: do not allow rlb updates to invalid mac
* tcp: ignore Fast Open on repair mode
* sctp: fix the issue that the cookie-ack with auth can't get processed
* sctp: delay the authentication for the duplicated cookie-echo chunk
* ALSA: timer: Call notifier in the same spinlock
* audit: move calcs after alloc and check when logging set loginuid
* arm64: introduce mov_q macro to move a constant into a 64-bit register
* arm64: Add work around for Arm Cortex-A55 Erratum 1024718
* futex: Remove unnecessary warning from get_futex_key
* futex: Remove duplicated code and fix undefined behaviour
* xfrm: fix xfrm_do_migrate() with AEAD e.g(AES-GCM)
* lockd: lost rollback of set_grace_period() in lockd_down_net()
* Revert "ARM: dts: imx6qdl-wandboard: Fix audio channel swap"
* l2tp: revert "l2tp: fix missing print session offset info"
* pipe: cap initial pipe capacity according to pipe-max-size limit
* futex: futex_wake_op, fix sign_extend32 sign bits
* kernel/exit.c: avoid undefined behaviour when calling wait4()
* usbip: usbip_host: refine probe and disconnect debug msgs to be useful
* usbip: usbip_host: delete device from busid_table after rebind
* usbip: usbip_host: run rebind from exit when module is removed
* usbip: usbip_host: fix NULL-ptr deref and use-after-free errors
* usbip: usbip_host: fix bad unlock balance during stub_probe()
* ALSA: usb: mixer: volume quirk for CM102-A+/102S+
* ALSA: hda: Add Lenovo C50 All in one to the power_save blacklist
* ALSA: control: fix a redundant-copy issue
* spi: pxa2xx: Allow 64-bit DMA
* powerpc/powernv: panic() on OPAL < V3
* powerpc/powernv: Remove OPALv2 firmware define and references
* powerpc/powernv: remove FW_FEATURE_OPALv3 and just use FW_FEATURE_OPAL
* cpuidle: coupled: remove unused define cpuidle_coupled_lock
* powerpc: Don't preempt_disable() in show_cpuinfo()
* vmscan: do not force-scan file lru if its absolute size is small
* mm: filemap: remove redundant code in do_read_cache_page
* mm: filemap: avoid unnecessary calls to lock_page when waiting for IO to
complete
during a read
* signals: avoid unnecessary taking of sighand->siglock
* tracing/x86/xen: Remove zero data size trace events
trace_xen_mmu_flush_tlb{_all}
* proc read mm's {arg,env}_{start,end} with mmap semaphore taken.
* powerpc/powernv: Fix NVRAM sleep in invalid context when crashing
* mm: don't allow deferred pages with NEED_PER_CPU_KM
* s390/qdio: fix access to uninitialized qdio_q fields
* s390/qdio: don't release memory in qdio_setup_irq()
* s390: remove indirect branch from do_softirq_own_stack
* efi: Avoid potential crashes, fix the 'struct efi_pci_io_protocol_32'
definition
for mixed mode
* ARM: 8771/1: kprobes: Prohibit kprobes on do_undefinstr
* tick/broadcast: Use for_each_cpu() specially on UP kernels
* ARM: 8769/1: kprobes: Fix to use get_kprobe_ctlblk after irq-disabed
* ARM: 8770/1: kprobes: Prohibit probing on optimized_callback
* ARM: 8772/1: kprobes: Prohibit kprobes on get_user
[Kernel-packages] [Bug 1772966] Re: linux-aws: 4.4.0-1061.70 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released -- 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/1772966 Title: linux-aws: 4.4.0-1061.70 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772960 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772940] Re: linux-azure: 4.15.0-1013.13~16.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released -- 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/1772940 Title: linux-azure: 4.15.0-1013.13~16.04.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Invalid 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 -- boot-testing-requested: true kernel-stable-master-bug: 1772927 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772960] Re: linux: 4.4.0-128.154 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772960 Title: linux: 4.4.0-128.154 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released 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: Fix Released Status in linux package in Ubuntu: Invalid Status in linux 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 backports: bug 1772962 (linux-lts-xenial), bug 1772963 (linux-aws) derivatives: bug 1772964 (linux-kvm), bug 1772965 (linux-snapdragon), bug 1772966 (linux-aws), bug 1772968 (linux-raspi2), bug 1772969 (linux-euclid) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772960/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774127] Re: linux-gcp: 4.13.0-1019.23 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1774127 Title: linux-gcp: 4.13.0-1019.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1774124 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1774127/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772610] Re: Adding back alx WoL feature
** 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/1772610 Title: Adding back alx WoL feature Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Bug description: [Impact] The WoL feature is a must to pass Energy Star 6.1 and above. The power consumption will be measured during S3 with WoL is enabled. [Test case] Verified pass on new Dell machines without the wake up issue. [Regression potential] No regression. We disable this feature by default, so the driver behavior will be the same. We'll leave this feature disabled by default before we can fix the unintentional wake up issue. [Misc] Upstream maintainer insists to fix the wake up issue before we can add this feature back to the driver, so make the patch stay in Ubuntu kernel only. We'll verify WoL on every new machines and try to fix this issue when we encounter it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1772610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771844] Re: powerpc/livepatch: Implement reliable stack tracing for the consistency model
** 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/1771844
Title:
powerpc/livepatch: Implement reliable stack tracing for the
consistency model
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 ==
Livepatch has a consistency model which is a hybrid of kGraft and kpatch:
it uses kGraft's per-task consistency and syscall barrier switching
combined with kpatch's stack trace switching. The current approach is
stack checking of sleeping tasks. If no affected functions are on the
stack of a given task, the task is patched. In most cases this will patch
most or all of the tasks on the first try. Otherwise, it'll keep trying
periodically. This patch implements the reliable stack tracing for
consistency model a.k.a HAVE_RELIABLE_STACKTRACE.
This will help in switching livepatching implementation to basic per-task
consistency model. It is the foundation, which will help us enable
security patches changing function or data semantics. This is the biggest
remaining piece needed on ppc64le to make livepatch more generally useful.
== Fix ==
df78d3f61480 ("powerpc/livepatch: Implement reliable stack tracing for the
consistency model")
== Regression Potential ==
Low. 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.
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=df78d3f6148092d33a9a24c7a9cfac
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1771844/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772610] Re: Adding back alx WoL feature
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772610 Title: Adding back alx WoL feature Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Bug description: [Impact] The WoL feature is a must to pass Energy Star 6.1 and above. The power consumption will be measured during S3 with WoL is enabled. [Test case] Verified pass on new Dell machines without the wake up issue. [Regression potential] No regression. We disable this feature by default, so the driver behavior will be the same. We'll leave this feature disabled by default before we can fix the unintentional wake up issue. [Misc] Upstream maintainer insists to fix the wake up issue before we can add this feature back to the driver, so make the patch stay in Ubuntu kernel only. We'll verify WoL on every new machines and try to fix this issue when we encounter it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1772610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770244] Re: Decode ARM CPER records in kernel
** 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/1770244
Title:
Decode ARM CPER records in kernel
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Bug description:
[Impact]
When an ARM-specific platform error (CPER) comes occurs, the kernel will emit
an error with an opaque hex error type. The user would then need to consult the
UEFI specification to decode it. It is far easier for the kernel to do the
decoding itself, and just tell the user what the problem is.
[Test Case]
On a server that supports EINJ, generate a fake CE (thanks to Tyler Baicar
for this example):
modprobe einj
echo 0x12345000 > /sys/kernel/debug/apei/einj/param1
echo $((-1 << 12)) > /sys/kernel/debug/apei/einj/param2
echo 5 > /sys/kernel/debug/apei/einj/param3
echo 0x3 > /sys/kernel/debug/apei/einj/flags
echo 0x1 > /sys/kernel/debug/apei/einj/error_type
echo 1 > /sys/kernel/debug/apei/einj/error_inject
In the output, look for a decoded message. Without this fix, you'll see:
[ 388.094304] {2}[Hardware Error]:error_info: 0x04c6007f
[ 388.094341] {2}[Hardware Error]:physical fault address:
0x12345000
But with the fix, you'll see:
[ 388.094304] {2}[Hardware Error]:error_info: 0x04c6007f
[ 388.094317] {2}[Hardware Error]: transaction type: Generic
[ 388.094322] {2}[Hardware Error]: operation type: Generic read (type of
instruction or data request cannot be determined)
[ 388.094326] {2}[Hardware Error]: cache level: 3
[ 388.094330] {2}[Hardware Error]: processor context not corrupted
[ 388.094333] {2}[Hardware Error]: the error has been corrected
[ 388.094337] {2}[Hardware Error]: PC is imprecise
[ 388.094341] {2}[Hardware Error]:physical fault address:
0x12345000
[Fix]
These upstream fixes add ARM decoding support:
c6d8c8ef1d0d94fdae9f5d72982963db89f9cdad efi: Move ARM CPER code to new
file
301f55b1a9177132d2b9ce8a90bf0ae4b37bb850 efi: Parse ARM error
information value
[Regression Risk]
The code changed is specific to ARM, and has been tested there. There's a
small change to arch-independent code, but it just involves renaming an array
and adding the obviously correct const attribute.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770244/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768143] Re: vmxnet3: update to latest ToT
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
** 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/1768143
Title:
vmxnet3: update to latest ToT
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
Recently, a couple of fixes went in vmxnet3 driver related to LRO, transmit
reset and rxvlan disabled fix. VMWare is requesting these fixes in
Bionic and Xenial.
A backport was needed to update version info in vmxnet3_int.h
== Fixes ==
7a4c003d6921 ("vmxnet3: avoid xmit reset due to a race in vmxnet3)"
034f40579389 ("vmxnet3: use correct flag to indicate LRO feature")
65ec0bd1c7c1 ("vmxnet3: fix incorrect dereference when rxvlan is disabled")
== Regression Potential ==
Low. Limited to vmxnet3 driver.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
Recently, a couple of fixes went in vmxnet3 driver related to LRO, transmit
reset and rxvlan disabled fix. Below are the commits:
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=7a4c003d6921e2af215f4790aa43a292bdc78be0
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=034f405793897a3c8f642935f5494b86c340cde7
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=65ec0bd1c7c14522670a5294de35710fb577a7fd
This is a request to bring Ubuntu vmxnet3 driver up to date with ToT
Linux kernel. Could you please backport it to 16.04 and 18.04 LTS releases?
Thanks,
Ronak
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768143/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768103] Re: Lancer A0 Asic HBA's won't boot with 18.04
** 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/1768103
Title:
Lancer A0 Asic HBA's won't boot with 18.04
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
It was reported by Broadcom that an early asic model (A0) of their 16/32GB
HBA's doesn't boot with the lpfc driver in Ubuntu 18.04.
Bionic with the lpfc driver 12.0.0.0 can't see LPe16002-M6 but can see
LPe16002B-M6.
This bug is fixed by commits bf316c78517d and c221768bd49a, which are
both still in linux-next. Broadcom tested with this two commits and
confirmed they resolve the bug and allow the system to boot.
== Fixes ==
Currently in linux-next:
bf316c78517d ("scsi: lpfc: Fix WQ/CQ creation for older asic's.")
c221768bd49a ("scsi: lpfc: Fix 16gb hbas failing cq create.")
== Regression Potential ==
Low. Patches fix a current regression and are limited to lpfc.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
We have discovered that an early asic model (A0) of our 16/32GB HBA's doesn't
boot with the lpfc driver in Ubuntu 18.04.
After further review and discussion, this has been deemed a low risk
issue since early A0 HBA's were only ever shipped to OEMs for test
purposes. These cards were never shipped to end customers. We have
been working to replace those cards whenever we discover them.
We'll leave it up to Canonical to decide whether they want to pull
this in this single patch to an 18.04 subsequent update.
Symptom: Ubuntu 18.04 with lpfc driver 12.0.0.0 they can't see LPe16002-M6
but can see LPe16002B-M6
Resolution: new lpfc driver patch update.
scsi: lpfc: Fix WQ/CQ creation for older asic's.
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=4.18/scsi-queue=83fae8ca4ae09403bfb99542f1aaa292c06cb111
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768103/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773162] Re: 4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec supported)
** 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/1773162 Title: 4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec supported) 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: Upgrading from 16.04 to 18.04 on a IBM S822LC the system does not boot with 4.15.0-22-generic and is in a reboot cycle. ``` Exiting petitboot. Type 'exit' to return. The system is going down NOW! Sent SIGTERM to all processes Sent SIGKILL to all processes [31775213631,3] OPAL: Trying a CPU re-init with flags: 0x1 [32097001879,3] OPAL: Trying a CPU re-init with flags: 0x2 [2.660186] Bad kernel stack pointer 7fffcd511100 at c000b9ec [2.660382] Oops: Bad kernel stack pointer, sig: 6 [#1] [2.660422] LE SMP NR_CPUS=2048 NUMA PowerNV [2.660462] Modules linked in: [2.660494] CPU: 63 PID: 1201 Comm: modprobe Not tainted 4.15.0-22-generic #24-Ubuntu [2.660549] NIP: c000b9ec LR: CTR: [2.660603] REGS: c0003fd0bd40 TRAP: 0300 Not tainted (4.15.0-22-generic) [2.660657] MSR: 90001031 CR: XER: [2.660713] CFAR: c000b934 DAR: 000200f0 DSISR: 4000 SOFTE: -4611686018408771536 [2.660713] GPR00: 7fffcd511100 [2.660713] GPR04: [2.660713] GPR08: [2.660713] GPR12: 75501b231700 000200f0 [2.660713] GPR16: [2.660713] GPR20: [2.660713] GPR24: [2.660713] GPR28: [2.661203] NIP [c000b9ec] fast_exception_return+0x9c/0x184 [2.661249] LR [] (null) [2.661285] Call Trace: [2.661303] Instruction dump: [2.661331] e84101a0 7c4ff120 e8410170 7c5a03a6 e8010070 e8410080 e8610088 e8810090 [2.661387] e8210078 7db243a6 7db142a6 7c0004ac 63ff 7db242a6 4810 [2.661445] ---[ end trace b607b09fe6490607 ]--- […] ``` Please find the full log attached. Selecting Linux 4.4.0-124-generic works. ``` $ uname -a Linux flughafenberlinbrandenburgwillybrandt 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:02:22 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux $ dpkg -l linux-image-4.15.0-22-generic Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-==-==-= ii linux-image-4.15.0-22-generic 4.15.0-22.24 ppc64elSigned kernel image generic $ more /etc/os-release NAME="Ubuntu" VERSION="18.04 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic ``` --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 23 16:40 seq crw-rw 1 root audio 116, 33 May 23 16:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7 Architecture: ppc64el 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' Package: linux (not installed) PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=2c3dd738-785a-469b-843e-9f0ba8b47b0d ro rootflags=subvol=@ quiet splash ProcLoadAvg: 0.01 0.08 0.04 2/1373 28071 ProcSwaps:
[Kernel-packages] [Bug 1771344] Re: Fix enabling bridge MMIO windows
** Changed in: linux (Ubuntu Artful)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1771344
Title:
Fix enabling bridge MMIO windows
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Artful:
Fix Committed
Status in linux source package in Bionic:
Invalid
Status in linux source package in Cosmic:
In Progress
Bug description:
== SRU Justification ==
IBM is requesting this patch in Bionic and Artful to fix a regression. The
regression was introduced in v3.11-rc1. The patch fixes enabling bridge
MMIO windows. Commit 13a83eac373c was also cc'd to upstream stable, and
has already landed in Xenial via upstream stable updates.
== Fix ==
13a83eac373c ("powerpc/eeh: Fix enabling bridge MMIO windows")
== Regression Potential ==
Low. Limited to powerpc and fixes a current regression.
== 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 - Breno Leitao
On boot we save the configuration space of PCIe bridges. We do this so
when we get an EEH event and everything gets reset that we can restore
them.
Unfortunately we save this state before we've enabled the MMIO space
on the bridges. Hence if we have to reset the bridge when we come back
MMIO is not enabled and we end up taking an PE freeze when the driver
starts accessing again.
This patch forces the memory/MMIO and bus mastering on when restoring
bridges on EEH. Ideally we'd do this correctly by saving the
configuration space writes later, but that will have to come later in
a larger EEH rewrite. For now we have this simple fix.
The original bug can be triggered on a boston machine by doing:
echo 0x8000 >
/sys/kernel/debug/powerpc/PCI0001/err_injct_outbound
On boston, this PHB has a PCIe switch on it. Without this patch,
you'll see two EEH events, 1 expected and 1 the failure we are fixing
here. The second EEH event causes the anything under the PHB to
disappear (i.e. the i40e eth).
With this patch, only 1 EEH event occurs and devices properly recover.
This is commit id 13a83eac373c49c0a081cbcd137e79210fe78acd and should
be part of Ubuntu 18.04 kernel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1771344/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774563] Re: Support SocketCAN over USB on Dell IoT 300x Gateways
** Changed in: linux (Ubuntu Xenial) 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/1774563 Title: Support SocketCAN over USB on Dell IoT 300x Gateways Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Bug description: This driver is from IXXAT and supports SocketCAN over USB. (https://www.ixxat.com) == SRU Justification == Dell IoT 300x gateways support USB-CAN peripherals. Dell expects these devices also support the SocketCAN over USB and is working with HMS to develop and upstream the driver. Meanwhile, we'll have to carry this driver as a SAUCE patch to support our Ubuntu Core 16 release. == Fix == UBUNTU: SAUCE: (no-up) Support IXXAT USB SocketCAN device == Regression Potential == Low. The driver will be built only for amd64 kernels and attach itself to IXXAT USB-CAN adapters with VID 0x08d8. This bug is for tracking purposes only, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771780] Re: [LTCTest][OPAL][OP920] cpupower idle-info is not listing stop4 and stop5 idle states when all CORES are guarded
** 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/1771780 Title: [LTCTest][OPAL][OP920] cpupower idle-info is not listing stop4 and stop5 idle states when all CORES are guarded Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Fix Committed Bug description: == SRU Justification == During testing, IBM found that cpupower idle-info is not listing stop4 and stop5 idle states when all CORES are guarded. A patch has been submitted upstream by IBM. However, the patch has not landed in linux-next or mainline as of yet. For that reason, this SRU request is being sent as a SAUCE patch request. == Fix == UBUNTU: SAUCE: cpuidle/powernv : init all present cpus for deep states == Regression Potential == Low. 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 - PAVAMAN SUBRAMANIYAM - 2018-05-16 04:07:59 == ---Problem Description--- cpupower idle-info is not listing stop4 and stop5 idle states when all CORES are guarded ---uname output--- Linux ltc-wspoon11 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = P9 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install a P9 Open Power Hardware with Ubuntu 18.04 OS. root@ltc-wspoon11:~# uname -a Linux ltc-wspoon11 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@ltc-wspoon11:~# cat /etc/os-release NAME="Ubuntu" VERSION="18.04 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic Then guard an entire processor and also guard all the CORES in the processor 0 except for 1 single core. root@ltc-wspoon11:~# opal-gard list ID | Error| Type | Path --- 0001 | | Manual | /Sys0/Node0/Proc0/EQ1/EX0/Core0 0002 | | Manual | /Sys0/Node0/Proc0/EQ1/EX0/Core1 0003 | | Manual | /Sys0/Node0/Proc1 0004 | | Manual | /Sys0/Node0/Proc0/EQ2/EX0/Core1 0005 | | Manual | /Sys0/Node0/Proc0/EQ2/EX0/Core0 0006 | | Manual | /Sys0/Node0/Proc0/EQ2/EX1/Core0 0007 | | Manual | /Sys0/Node0/Proc0/EQ2/EX1/Core1 0008 | | Manual | /Sys0/Node0/Proc0/EQ3/EX0/Core0 0009 | | Manual | /Sys0/Node0/Proc0/EQ3/EX0/Core1 000a | | Manual | /Sys0/Node0/Proc0/EQ3/EX1/Core0 000b | | Manual | /Sys0/Node0/Proc0/EQ3/EX1/Core1 000c | | Manual | /Sys0/Node0/Proc0/EQ4/EX0/Core0 000d | | Manual | /Sys0/Node0/Proc0/EQ4/EX0/Core1 000e | | Manual | /Sys0/Node0/Proc0/EQ4/EX1/Core0 000f | | Manual | /Sys0/Node0/Proc0/EQ4/EX1/Core1 0010 | | Manual | /Sys0/Node0/Proc0/EQ5/EX0/Core0 0011 | | Manual | /Sys0/Node0/Proc0/EQ5/EX0/Core1 0012 | | Manual | /Sys0/Node0/Proc0/EQ5/EX1/Core0 0013 | | Manual | /Sys0/Node0/Proc0/EQ5/EX1/Core1 0014 | | Manual | /Sys0/Node0/Proc0/EQ1/EX1/Core0 0015 | | Manual | /Sys0/Node0/Proc0/EQ1/EX1/Core1 0016 | | Manual | /Sys0/Node0/Proc0/EQ0/EX1/Core1 0017 | | Manual | /Sys0/Node0/Proc0/EQ0/EX1/Core0 === Then execute the cpupower idle-info command to check the idle states being shown in the OS. root@ltc-wspoon11:~# cpupower idle-info CPUidle driver: powernv_idle CPUidle governor: menu analyzing CPU 0: Number of idle states: 7 Available idle states: snooze stop0_lite stop0 stop1_lite stop1 stop2_lite stop2 snooze: Flags/Description: snooze Latency: 0 Usage: 774653 Duration: 7698954 stop0_lite: Flags/Description: stop0_lite Latency: 1 Usage: 2751 Duration: 11363825 stop0: Flags/Description: stop0 Latency: 2 Usage: 2343 Duration: 915084 stop1_lite: Flags/Description: stop1_lite Latency: 5 Usage: 20 Duration: 1533 stop1: Flags/Description:
[Kernel-packages] [Bug 1770970] Re: Huawei 25G/100G Network Adapters Unsupported
** 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/1770970 Title: Huawei 25G/100G Network Adapters Unsupported Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Huawei 25G/100G network adapters are not usable with Ubuntu. [Test Case] On a system with one of these adapters, the hinic driver should load and enumerate devices. [Fix] We just need to teach the driver about these new PCI IDs. [Regression Risk] These are previously unsupported devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775137] Re: Prevent speculation on user controlled pointer
** Changed in: linux (Ubuntu Xenial)
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/1775137
Title:
Prevent speculation on user controlled pointer
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Precise:
New
Status in linux source package in Trusty:
New
Status in linux source package in Xenial:
Fix Committed
Bug description:
== SRU Justification ==
Upstream's Spectre v1 mitigation prevents speculation on a user controlled
pointer. This part of the Spectre v1 patchset was never backported to 4.4 (for
unknown reasons) so Xenial/Trusty/Precise are lacking it as well. All the other
stable upstream kernels include it, so add it to our older kernels.
== Fix ==
Backport the following patches:
x86/uaccess: Use __uaccess_begin_nospec() and uaccess_try_nospec
x86/usercopy: Replace open coded stac/clac with __uaccess_{begin, end}
x86: Introduce __uaccess_begin_nospec() and uaccess_try_nospec
== Regression Potential ==
Low. Patches have been in upstream (and other distro kernels) for quite a
while now and the changes only introduce a barrier on copy_from_user operations.
== Test Case ==
TBD.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775137/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775717] 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 1775717
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Tags added: 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/1775717
Title:
CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
Status in linux package in Ubuntu:
Incomplete
Bug description:
After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
GPU fans suddenly go full throttle. It doesn't seem to depend on
temperature, could happen when 32 °C reported, sometimes the laptop
can work for day or two without this issue, but eventually it happens.
The only way to stop fans is to power off the laptop, power on (fans
go 100% at this point again), power off during BIOS splash screen and
power on again. Seems to happen more often after waking up from a
sleep.
Things tried:
Upgrading BIOS to latest available on ASUS site to the date of
writing. No change.
asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
does not seem to control it and does not prevent going full throttle.
4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
issue.
Userspace fan control software (https://github.com/hirschmann/nbfc).
Can control speed of both fans to the point where they go full
throttle, after that has no effect on them.
System info:
$ lsb_release -rd
Description: Ubuntu 18.04 LTS
Release: 18.04
$ cat /proc/version
Linux version 4.17.0-041700-generic (kernel@kathleen) (gcc version 7.3.0
(Ubuntu 7.3.0-20ubuntu1)) #201806041953 SMP Mon Jun 4 19:55:25 UTC 2018
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775717/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775717] [NEW] CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
Public bug reported:
After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
GPU fans suddenly go full throttle. It doesn't seem to depend on
temperature, could happen when 32 °C reported, sometimes the laptop can
work for day or two without this issue, but eventually it happens. The
only way to stop fans is to power off the laptop, power on (fans go 100%
at this point again), power off during BIOS splash screen and power on
again. Seems to happen more often after waking up from a sleep.
Things tried:
Upgrading BIOS to latest available on ASUS site to the date of writing.
No change.
asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
does not seem to control it and does not prevent going full throttle.
4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
issue.
Userspace fan control software (https://github.com/hirschmann/nbfc). Can
control speed of both fans to the point where they go full throttle,
after that has no effect on them.
System info:
$ lsb_release -rd
Description:Ubuntu 18.04 LTS
Release:18.04
$ cat /proc/version
Linux version 4.17.0-041700-generic (kernel@kathleen) (gcc version 7.3.0
(Ubuntu 7.3.0-20ubuntu1)) #201806041953 SMP Mon Jun 4 19:55:25 UTC 2018
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: hw-specific
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/bugs/1775717/+attachment/5149995/+files/lspci-vnvn.log
** Summary changed:
- COU.Fan suddenly goes 100% RPM on Asus ROG G752VT
+ CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1775717
Title:
CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
Status in linux package in Ubuntu:
New
Bug description:
After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
GPU fans suddenly go full throttle. It doesn't seem to depend on
temperature, could happen when 32 °C reported, sometimes the laptop
can work for day or two without this issue, but eventually it happens.
The only way to stop fans is to power off the laptop, power on (fans
go 100% at this point again), power off during BIOS splash screen and
power on again. Seems to happen more often after waking up from a
sleep.
Things tried:
Upgrading BIOS to latest available on ASUS site to the date of
writing. No change.
asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
does not seem to control it and does not prevent going full throttle.
4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
issue.
Userspace fan control software (https://github.com/hirschmann/nbfc).
Can control speed of both fans to the point where they go full
throttle, after that has no effect on them.
System info:
$ lsb_release -rd
Description: Ubuntu 18.04 LTS
Release: 18.04
$ cat /proc/version
Linux version 4.17.0-041700-generic (kernel@kathleen) (gcc version 7.3.0
(Ubuntu 7.3.0-20ubuntu1)) #201806041953 SMP Mon Jun 4 19:55:25 UTC 2018
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775717/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772940] Re: linux-azure: 4.15.0-1013.13~16.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => 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/1772940 Title: linux-azure: 4.15.0-1013.13~16.04.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Invalid 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 -- boot-testing-requested: true kernel-stable-master-bug: 1772927 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774127] Re: linux-gcp: 4.13.0-1019.23 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1774127 Title: linux-gcp: 4.13.0-1019.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1774124 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1774127/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772964] Re: linux-kvm: 4.4.0-1027.32 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released -- 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/1772964 Title: linux-kvm: 4.4.0-1027.32 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772960 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772964/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772963] Re: linux-aws: 4.4.0-1023.23 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released -- 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/1772963 Title: linux-aws: 4.4.0-1023.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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 -- boot-testing-requested: true kernel-stable-master-bug: 1772960 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772963/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772966] Re: linux-aws: 4.4.0-1061.70 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released -- 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/1772966 Title: linux-aws: 4.4.0-1061.70 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772960 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
This bug also affects the Dell XPS 13 9370. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Confirmed Bug description: I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767927] Re: ISST-LTE:pKVM:Ubuntu1804: rcu_sched self-detected stall on CPU follow by CPU ATTEMPT TO RE-ENTER FIRMWARE!
** Tags added: triage-g -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767927 Title: ISST-LTE:pKVM:Ubuntu1804: rcu_sched self-detected stall on CPU follow by CPU ATTEMPT TO RE-ENTER FIRMWARE! Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: == Comment: #0 - Application Cdeadmin - 2018-03-20 14:10:53 == == Comment: #1 - Application Cdeadmin - 2018-03-20 14:10:54 == == Comment: #2 - Application Cdeadmin - 2018-03-20 14:10:56 == --- Comment From dougmill-ibm 2018-03-20 13:51:47 EDT --- This problem is not tied to a Linux distro. It will be fixed in firmware, as I understand it. Let us close any redundant issues for this same problem. Mark them as duplicate. == Comment: #3 - Application Cdeadmin - 2018-03-20 15:50:54 == --- Comment From mzipse 2018-03-20 15:44:26 EDT --- @stewart-ibm @svaidy , I need to you take a first look. The stop fixes that Vaidy had previously highlighted in a recent note are included in the 3/15 PNOR. == Comment: #5 - Application Cdeadmin - 2018-04-04 16:10:56 == --- Comment From haochanh 2018-04-04 16:04:07 EDT --- We update to 0330, bmc=1.18, then we hit bug 1134. Currently we are running with disable stop5 but still see the watchdog: hard lockup. After 2 hours of test run, I am seeing the "Watchdog: Lockup' and "became unstuck" [Wed Apr 4 13:38:25 2018] Watchdog CPU:42 Hard LOCKUP [Wed Apr 4 13:38:25 2018] Modules linked in: vhost_net vhost macvtap macvlan tap xfs xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter rpcsec_gss_krb5 nfsv4 nfs fscache rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx5_ib(OE) mlx5_core(OE) mlxfw(OE) cxl pnv_php mlx4_en(OE) mlx4_ib(OE) ib_core(OE) mlx4_core(OE) devlink mlx_compat(OE) kvm_hv kvm binfmt_misc dm_service_time dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua input_leds joydev mac_hid idt_89hpesx ipmi_powernv [Wed Apr 4 13:38:25 2018] vmx_crypto ipmi_devintf at24 ofpart uio_pdrv_genirq cmdlinepart uio powernv_flash ipmi_msghandler mtd crct10dif_vpmsum opal_prd ibmpowernv nfsd sch_fq_codel auth_rpcgss nfs_acl lockd grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq ses enclosure scsi_transport_sas hid_generic usbhid hid lpfc ast i2c_algo_bit ttm drm_kms_helper nvmet_fc syscopyarea sysfillrect nvmet sysimgblt fb_sys_fops nvme_fc nvme_fabrics crc32c_vpmsum drm i40e scsi_transport_fc aacraid [last unloaded: mlxfw] [Wed Apr 4 13:38:25 2018] CPU: 42 PID: 0 Comm: swapper/42 Tainted: G OE4.15.0-12-generic #13 [Wed Apr 4 13:38:25 2018] NIP: c00a3ca4 LR: c00a3ca4 CTR: c0008000 [Wed Apr 4 13:38:25 2018] REGS: c00ff596fc40 TRAP: 0100 Tainted: G OE (4.15.0-12-generic) [Wed Apr 4 13:38:25 2018] MSR: 90001033 CR: 24004482 XER: 2004 [Wed Apr 4 13:38:25 2018] CFAR: c00ff596fda0 SOFTE: 42 GPR00: c00a3ca4 c00ff596fda0 c16eb200 c00ff596fc40 GPR04: b0001033 c00a3690 24004484 000ffa45 GPR08: 0001 c0d10ed8 00ff GPR12: 90121033 c7a3ce00 c00ff596ff90 GPR16: c0047840 c0047810 c11b5380 GPR20: 0800 c1722484 002a GPR24: 00a8 0007 0007 GPR28: c161d270 c00ffb666fd8 c161d528 0007 [Wed Apr 4 13:38:25 2018] NIP [c00a3ca4] power9_idle_type+0x24/0x40 [Wed Apr 4 13:38:25 2018] LR [c00a3ca4] power9_idle_type+0x24/0x40 [Wed Apr 4 13:38:25 2018] Call Trace: [Wed Apr 4 13:38:25 2018] [c00ff596fda0] [c00a3ca4] power9_idle_type+0x24/0x40 (unreliable) [Wed Apr 4 13:38:25 2018] [c00ff596fdc0] [c0ad1240] stop_loop+0x40/0x5c [Wed Apr 4 13:38:25 2018] [c00ff596fdf0] [c0acd9a4] cpuidle_enter_state+0xa4/0x450 [Wed Apr 4 13:38:25 2018] [c00ff596fe50] [c017195c] call_cpuidle+0x4c/0x90 [Wed Apr 4 13:38:25 2018]
[Kernel-packages] [Bug 1772960] Re: linux: 4.4.0-128.154 -proposed tracker
All done with one pending/withdrawn (needs a follow up to be complete) ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772960 Title: linux: 4.4.0-128.154 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux 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 backports: bug 1772962 (linux-lts-xenial), bug 1772963 (linux-aws) derivatives: bug 1772964 (linux-kvm), bug 1772965 (linux-snapdragon), bug 1772966 (linux-aws), bug 1772968 (linux-raspi2), bug 1772969 (linux-euclid) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772960/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767927] Comment bridged from LTC Bugzilla
--- Comment From gwal...@br.ibm.com 2018-06-07 16:54 EDT--- Hi, I have looking for a machine to reproduce then update all of thing to validate it. Tomorrow I hope a boston LC available for testing back. sorry for delay. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767927 Title: ISST-LTE:pKVM:Ubuntu1804: rcu_sched self-detected stall on CPU follow by CPU ATTEMPT TO RE-ENTER FIRMWARE! Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: == Comment: #0 - Application Cdeadmin - 2018-03-20 14:10:53 == == Comment: #1 - Application Cdeadmin - 2018-03-20 14:10:54 == == Comment: #2 - Application Cdeadmin - 2018-03-20 14:10:56 == --- Comment From dougmill-ibm 2018-03-20 13:51:47 EDT --- This problem is not tied to a Linux distro. It will be fixed in firmware, as I understand it. Let us close any redundant issues for this same problem. Mark them as duplicate. == Comment: #3 - Application Cdeadmin - 2018-03-20 15:50:54 == --- Comment From mzipse 2018-03-20 15:44:26 EDT --- @stewart-ibm @svaidy , I need to you take a first look. The stop fixes that Vaidy had previously highlighted in a recent note are included in the 3/15 PNOR. == Comment: #5 - Application Cdeadmin - 2018-04-04 16:10:56 == --- Comment From haochanh 2018-04-04 16:04:07 EDT --- We update to 0330, bmc=1.18, then we hit bug 1134. Currently we are running with disable stop5 but still see the watchdog: hard lockup. After 2 hours of test run, I am seeing the "Watchdog: Lockup' and "became unstuck" [Wed Apr 4 13:38:25 2018] Watchdog CPU:42 Hard LOCKUP [Wed Apr 4 13:38:25 2018] Modules linked in: vhost_net vhost macvtap macvlan tap xfs xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter rpcsec_gss_krb5 nfsv4 nfs fscache rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx5_ib(OE) mlx5_core(OE) mlxfw(OE) cxl pnv_php mlx4_en(OE) mlx4_ib(OE) ib_core(OE) mlx4_core(OE) devlink mlx_compat(OE) kvm_hv kvm binfmt_misc dm_service_time dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua input_leds joydev mac_hid idt_89hpesx ipmi_powernv [Wed Apr 4 13:38:25 2018] vmx_crypto ipmi_devintf at24 ofpart uio_pdrv_genirq cmdlinepart uio powernv_flash ipmi_msghandler mtd crct10dif_vpmsum opal_prd ibmpowernv nfsd sch_fq_codel auth_rpcgss nfs_acl lockd grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq ses enclosure scsi_transport_sas hid_generic usbhid hid lpfc ast i2c_algo_bit ttm drm_kms_helper nvmet_fc syscopyarea sysfillrect nvmet sysimgblt fb_sys_fops nvme_fc nvme_fabrics crc32c_vpmsum drm i40e scsi_transport_fc aacraid [last unloaded: mlxfw] [Wed Apr 4 13:38:25 2018] CPU: 42 PID: 0 Comm: swapper/42 Tainted: G OE4.15.0-12-generic #13 [Wed Apr 4 13:38:25 2018] NIP: c00a3ca4 LR: c00a3ca4 CTR: c0008000 [Wed Apr 4 13:38:25 2018] REGS: c00ff596fc40 TRAP: 0100 Tainted: G OE (4.15.0-12-generic) [Wed Apr 4 13:38:25 2018] MSR: 90001033 CR: 24004482 XER: 2004 [Wed Apr 4 13:38:25 2018] CFAR: c00ff596fda0 SOFTE: 42 GPR00: c00a3ca4 c00ff596fda0 c16eb200 c00ff596fc40 GPR04: b0001033 c00a3690 24004484 000ffa45 GPR08: 0001 c0d10ed8 00ff GPR12: 90121033 c7a3ce00 c00ff596ff90 GPR16: c0047840 c0047810 c11b5380 GPR20: 0800 c1722484 002a GPR24: 00a8 0007 0007 GPR28: c161d270 c00ffb666fd8 c161d528 0007 [Wed Apr 4 13:38:25 2018] NIP [c00a3ca4] power9_idle_type+0x24/0x40 [Wed Apr 4 13:38:25 2018] LR [c00a3ca4] power9_idle_type+0x24/0x40 [Wed Apr 4 13:38:25 2018] Call Trace: [Wed Apr 4 13:38:25 2018] [c00ff596fda0] [c00a3ca4] power9_idle_type+0x24/0x40 (unreliable) [Wed Apr 4 13:38:25 2018] [c00ff596fdc0] [c0ad1240] stop_loop+0x40/0x5c [Wed Apr 4
[Kernel-packages] [Bug 1773137] Re: USB2 keep resetting. kernel: usb 2-1: USB disconnect
When I using Linux kernel 4.13 it's not happening, here I attached dmesg on 4.13. ** Attachment added: "dmesg on Linux kernel 4.13.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773137/+attachment/5149954/+files/dmesg%20on%20Linux%20kernel%204.13.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773137 Title: USB2 keep resetting. kernel: usb 2-1: USB disconnect Status in linux package in Ubuntu: Confirmed Status in linux-signed package in Ubuntu: New Bug description: Hello, I have found a bug. This bug is related to USB2, I have DVD RW external that using USB2 port. I using the kernel 4.15.0-22. I also attached the error log from dmesg. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Thu May 24 17:26:01 2018 InstallationDate: Installed on 2018-04-14 (40 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-04-27 (26 days ago) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1622 F pulseaudio /dev/snd/pcmC1D0p: mate 1622 F...m pulseaudio /dev/snd/controlC1: mate 1622 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-14 (41 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20369 Package: linux-signed ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=a14e83f1-8214-4bdd-a01d-d6cebd312997 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-27 (27 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 4A2 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G40-70 dmi.modalias: dmi:bvnLENOVO:bvr9ACN29WW:bd10/20/2014:svnLENOVO:pn20369:pvrLenovoG40-70:rvnLENOVO:rnLancer4A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG40-70: dmi.product.family: IDEAPAD dmi.product.name: 20369 dmi.product.version: Lenovo G40-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773137/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774964] Re: [LTCTest][OPAL][OP910.20] WARNING: CPU: 97 PID: 11965 at /build/linux-0zaMZw/linux-4.15.0/kernel/sched/core.c:1189 set_task_cpu+0x240/0x250
** Changed in: ubuntu-power-systems
Status: 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/1774964
Title:
[LTCTest][OPAL][OP910.20] WARNING: CPU: 97 PID: 11965 at /build/linux-
0zaMZw/linux-4.15.0/kernel/sched/core.c:1189 set_task_cpu+0x240/0x250
Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
IBM reports seeing the following during their testing:
WARNING: CPU: 97 PID: 11965 at
/build/linux-0zaMZw/linux-4.15.0/kernel/sched/core.c:1189
set_task_cpu+0x240/0x250
This is a regression and was introduced by the following two commits in
v4.15-rc1:
01eaac2b0591 ("powerpc/mce: Hookup ierror (instruction) UE errors")
ba41e1e1ccb9 ("powerpc/mce: Hookup derror (load/store) UE errors")
This regression is fixed by commit 75ecfb49516c in v4.17-rc3. The
commit was also cc'd to upstream stable, but it is being SRU'd to get
the fix into Ubuntu without waiting for it to come down via stable
updates.
== Fix ==
75ecfb49516c ("powerpc/mce: Fix a bug where mce loops on memory UE.")
== Regression Potential ==
Low. Limited to powerpc. The commit was also cc'd to upstream stable
so it will recieve additional upstream stable 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.
== Original Bug Descriptions ==
== Comment: #0 - PAVAMAN SUBRAMANIYAM <> - 2018-04-25 01:59:10 ==
---Problem Description---
WARNING: CPU: 97 PID: 11965 at
/build/linux-0zaMZw/linux-4.15.0/kernel/sched/core.c:1189
set_task_cpu+0x240/0x250
---uname output---
Linux ltc-wspoon8 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC
2018 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = P9
---Debugger---
A debugger is not configured
---Steps to Reproduce---
Install a P9 Open Power Hardware with the latest OP910.20 Firmware images.
root@witherspoon:~# cat /etc/os-release
ID="openbmc-phosphor"
NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"
VERSION="ibm-v2.0"
VERSION_ID="ibm-v2.0-0-r46-0-gbed584c"
PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)
ibm-v2.0"
BUILD_ID="ibm-v2.0-0-r46"
root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION
open-power-witherspoon-v1.21.2-251-ge2e9363-dirty
buildroot-2017.11-5-g65679be
skiboot-v5.10.3-op910-1-p240231e
hostboot-0aa5bed
linux-4.14.24-openpower1-p3e84190
petitboot-v1.6.6-pd7224b4
machine-xml-4af
occ-8c5b727
hostboot-binaries-9bd4056
capp-ucode-p9-dd2-v3
sbe-7e02c23
Then we have installed the Ubuntu 18.04 OS on the machine.
root@ltc-wspoon8:~# uname -a
Linux ltc-wspoon8 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC
2018 ppc64le ppc64le ppc64le GNU/Linux
root@ltc-wspoon8:~# cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
root@ltc-wspoon8:~# cat /proc/cpuinfo | tail
cpu : POWER9, altivec supported
clock : 2300.00MHz
revision: 2.1 (pvr 004e 1201)
timebase: 51200
platform: PowerNV
model : 8335-GTC
machine : PowerNV 8335-GTC
firmware: OPAL
MMU : Radix
root@ltc-wspoon8:~# kdump-config show
DUMP_MODE:kdump
USE_KDUMP:1
KDUMP_SYSCTL: kernel.panic_on_oops=1
KDUMP_COREDIR:/var/crash
crashkernel addr:
/var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-20-generic
kdump initrd:
/var/lib/kdump/initrd.img: symbolic link to
/var/lib/kdump/initrd.img-4.15.0-20-generic
current state:ready to kdump
kexec command:
/sbin/kexec -p
--command-line="root=UUID=a2cd572c-9047-4f0a-843b-6996fae3e999 ro quiet splash
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb"
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
root@ltc-wspoon8:~# ps -ef | grep opal
root880 2 0 01:25 ?00:00:00 [kopald]
root 3604 1 2 01:25 ?00:00:03 /usr/sbin/opal-prd
root 4858 4278 0 01:28 pts/000:00:00 grep --color=auto opal
root@ltc-wspoon8:~# service opal-prd status
? opal-prd.service - OPAL PRD daemon
[Kernel-packages] [Bug 1753954] Re: Intel Whiskey Lake (WHL) graphics support
Hello Timo, or anyone else affected, Accepted libdrm into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libdrm/2.4.91-2~16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: libdrm (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- 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/1753954 Title: Intel Whiskey Lake (WHL) graphics support Status in libdrm package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libdrm source package in Xenial: Fix Committed Status in linux-oem source package in Xenial: Won't Fix Status in mesa source package in Xenial: New Status in xorg-server source package in Xenial: Invalid Status in xorg-server-hwe-16.04 source package in Xenial: New Status in libdrm source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Fix Released Status in xorg-server-hwe-16.04 source package in Bionic: Invalid Bug description: [Impact] WHL is basically CFL-U with new PCI-ID's that are needed in the kernel, libdrm, mesa and xserver. [Test Case] Test the installation on a WHL machine, the graphical session should have full acceleration after these updates. [Regression Potential] None, just adds PCI-ID's to existing drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1753954/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775326] Re: The kernel NULL pointer dereference happens when accessing the task_struct by task_cpu() in function cpuacct_charge()
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1775326
Title:
The kernel NULL pointer dereference happens when accessing the
task_struct by task_cpu() in function cpuacct_charge()
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Xenial:
In Progress
Bug description:
[Impact]
In function cpuacct_charge(), the NULL pointer dereference happens
with the stack pointer being zero inside the task_struct when the
task_cpu() is trying to access the member CPU of the struct
thread_info inside the stack. It's a use-after-free corruption
happening in the situation that the task_struct is released almost
concurrently before accessing the task_struct->stack.
void cpuacct_charge(struct task_struct *tsk, u64 cputime)
{
struct cpuacct *ca;
int cpu;
cpu = task_cpu(tsk);
rcu_read_lock();
ca = task_ca(tsk);
while (true) {
u64 *cpuusage = per_cpu_ptr(ca->cpuusage, cpu);
*cpuusage += cputime;
ca = parent_ca(ca);
if (!ca)
break;
}
rcu_read_unlock();
}
BUG: unable to handle kernel NULL pointer dereference at 0010
IP: [] cpuacct_charge+0x14/0x40
PGD 0
Oops: [#1] SMP
CPU: 10 PID: 148614 Comm: qemu-system-x86 Tainted: PW OE
4.4.0-45-generic #66~14.04.1-Ubuntu
Hardware name: Dell Inc. PowerEdge R630/02C2CP, BIOS 2.1.7 06/16/2016
task: 881ff0f01b80 ti: 88018fd7 task.ti: 88018fd7
RIP: 0010:[] [] cpuacct_charge+0x14/0x40
RSP: 0018:88018fd73d10 EFLAGS: 00010246
RAX: RBX: 8801931e8000 RCX: 88010caff200
RDX: 880124508000 RSI: 0066f757398831d6 RDI: 8801931e7fa0
RBP: 88018fd73d10 R08: c04b8320 R09: 0001
R10: 0001 R11: R12: 0066f757398831d6
R13: 0066f757398b8997 R14: 8801931e7fa0 R15: 0001
FS: 7f162aaf7700() GS:881ffe74() knlGS:
CS: 0010 DS: ES: CR0: 80050033
CR2: 0010 CR3: 00011d86e000 CR4: 003426e0
DR0: DR1: DR2:
DR3: DR6: fffe0ff0 DR7: 0400
Stack:
88018fd73d28 810b1a9f 8801931e8000 88018fd73d40
c069df72 8801931e8000 88018fd73da8 c069f121
881ff0f01b80 881ff0f01b80 810bddc0
Call Trace:
[] update_curr+0xdf/0x170
[] kvm_vcpu_check_block+0x12/0x60 [kvm]
[] kvm_vcpu_block+0x191/0x2d0 [kvm]
[] ? prepare_to_wait_event+0xf0/0xf0
[] kvm_arch_vcpu_ioctl_run+0x17e/0x3d0 [kvm]
[] kvm_vcpu_ioctl+0x2ab/0x640 [kvm]
[] ? perf_event_context_sched_in+0x87/0xa0
[] do_vfs_ioctl+0x2dd/0x4c0
[] ? __audit_syscall_entry+0xaf/0x100
[] ? do_audit_syscall_entry+0x66/0x70
[] SyS_ioctl+0x79/0x90
[] entry_SYSCALL_64_fastpath+0x16/0x75
Code: 9a 11 00 5b 48 c7 c0 f4 ff ff ff 5d eb df 66 0f 1f 84 00 00 00 00 00 0f
1f 44 00 00 55 48 8b 47 08 48 8b 97 78 07 00 00 48 89 e5 <48> 63 48 10 48 8b 52
60 48 8b 82 b8 00 00 00 48 03 04 cd c0 7a
RIP [] cpuacct_charge+0x14/0x40
RSP
CR2: 0010
---[ end trace 419a30375d0e4622 ]---
[Fix]
The patch uses this_cpu_ptr() instead of getting the CPU number by
task_cpu() and proceeds to get the cpu_usage by per_cpu_ptr(). And
that can avoid accessing the thread_info inside the stack.
commit 73e6aafd9ea81498d31361f01db84a0118da2d1c
Author: Zhao Lei
Date: Thu Mar 17 12:19:43 2016 +0800
sched/cpuacct: Simplify the cpuacct code
- Use for() instead of while() loop in some functions
to make the code simpler.
- Use this_cpu_ptr() instead of per_cpu_ptr() to make the code
cleaner and a bit faster.
Suggested-by: Peter Zijlstra
Signed-off-by: Zhao Lei
Signed-off-by: Peter Zijlstra (Intel)
Cc: Linus Torvalds
Cc: Tejun Heo
Cc: Thomas Gleixner
Link:
http://lkml.kernel.org/r/d8a7ef9592f55224630cb26dea239f05b6398a4e.1458187654.git.zhao...@cn.fujitsu.com
Signed-off-by: Ingo Molnar
[Test]
The test kernel has been tested by the Qemu and cannot be reproduced.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775326/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774964] Re: [LTCTest][OPAL][OP910.20] WARNING: CPU: 97 PID: 11965 at /build/linux-0zaMZw/linux-4.15.0/kernel/sched/core.c:1189 set_task_cpu+0x240/0x250
** Changed in: linux (Ubuntu 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/1774964
Title:
[LTCTest][OPAL][OP910.20] WARNING: CPU: 97 PID: 11965 at /build/linux-
0zaMZw/linux-4.15.0/kernel/sched/core.c:1189 set_task_cpu+0x240/0x250
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
IBM reports seeing the following during their testing:
WARNING: CPU: 97 PID: 11965 at
/build/linux-0zaMZw/linux-4.15.0/kernel/sched/core.c:1189
set_task_cpu+0x240/0x250
This is a regression and was introduced by the following two commits in
v4.15-rc1:
01eaac2b0591 ("powerpc/mce: Hookup ierror (instruction) UE errors")
ba41e1e1ccb9 ("powerpc/mce: Hookup derror (load/store) UE errors")
This regression is fixed by commit 75ecfb49516c in v4.17-rc3. The
commit was also cc'd to upstream stable, but it is being SRU'd to get
the fix into Ubuntu without waiting for it to come down via stable
updates.
== Fix ==
75ecfb49516c ("powerpc/mce: Fix a bug where mce loops on memory UE.")
== Regression Potential ==
Low. Limited to powerpc. The commit was also cc'd to upstream stable
so it will recieve additional upstream stable 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.
== Original Bug Descriptions ==
== Comment: #0 - PAVAMAN SUBRAMANIYAM <> - 2018-04-25 01:59:10 ==
---Problem Description---
WARNING: CPU: 97 PID: 11965 at
/build/linux-0zaMZw/linux-4.15.0/kernel/sched/core.c:1189
set_task_cpu+0x240/0x250
---uname output---
Linux ltc-wspoon8 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC
2018 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = P9
---Debugger---
A debugger is not configured
---Steps to Reproduce---
Install a P9 Open Power Hardware with the latest OP910.20 Firmware images.
root@witherspoon:~# cat /etc/os-release
ID="openbmc-phosphor"
NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"
VERSION="ibm-v2.0"
VERSION_ID="ibm-v2.0-0-r46-0-gbed584c"
PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)
ibm-v2.0"
BUILD_ID="ibm-v2.0-0-r46"
root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION
open-power-witherspoon-v1.21.2-251-ge2e9363-dirty
buildroot-2017.11-5-g65679be
skiboot-v5.10.3-op910-1-p240231e
hostboot-0aa5bed
linux-4.14.24-openpower1-p3e84190
petitboot-v1.6.6-pd7224b4
machine-xml-4af
occ-8c5b727
hostboot-binaries-9bd4056
capp-ucode-p9-dd2-v3
sbe-7e02c23
Then we have installed the Ubuntu 18.04 OS on the machine.
root@ltc-wspoon8:~# uname -a
Linux ltc-wspoon8 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC
2018 ppc64le ppc64le ppc64le GNU/Linux
root@ltc-wspoon8:~# cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
root@ltc-wspoon8:~# cat /proc/cpuinfo | tail
cpu : POWER9, altivec supported
clock : 2300.00MHz
revision: 2.1 (pvr 004e 1201)
timebase: 51200
platform: PowerNV
model : 8335-GTC
machine : PowerNV 8335-GTC
firmware: OPAL
MMU : Radix
root@ltc-wspoon8:~# kdump-config show
DUMP_MODE:kdump
USE_KDUMP:1
KDUMP_SYSCTL: kernel.panic_on_oops=1
KDUMP_COREDIR:/var/crash
crashkernel addr:
/var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-20-generic
kdump initrd:
/var/lib/kdump/initrd.img: symbolic link to
/var/lib/kdump/initrd.img-4.15.0-20-generic
current state:ready to kdump
kexec command:
/sbin/kexec -p
--command-line="root=UUID=a2cd572c-9047-4f0a-843b-6996fae3e999 ro quiet splash
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb"
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
root@ltc-wspoon8:~# ps -ef | grep opal
root880 2 0 01:25 ?00:00:00 [kopald]
root 3604 1 2 01:25 ?00:00:03 /usr/sbin/opal-prd
root 4858 4278 0 01:28 pts/000:00:00 grep --color=auto opal
root@ltc-wspoon8:~# service opal-prd status
? opal-prd.service - OPAL PRD daemon
[Kernel-packages] [Bug 1770236] Re: The RoCE driver for HiSilicon HNS doesn't autoload
*** This bug is a duplicate of bug 1770974 *** https://bugs.launchpad.net/bugs/1770974 ** This bug has been marked a duplicate of bug 1770974 Fix several bugs in RDMA/hns driver -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770236 Title: The RoCE driver for HiSilicon HNS doesn't autoload Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: [Impact] The user has to manually load the driver before they can use the RoCE function of these NICs. [Test Case] On a HiSilicon D06 node: $ lsmod | grep hns-roce-hw-v2 [Fix] The module is missing the MODULE_DEVICE_TABLE() macro, which exposes the PCI IDs it is associated with to userspace (udev). [Regression Risk] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1760173] Re: zfs, zpool commands hangs for 10 seconds without a /dev/zfs
Not really, no. You can use systemd-detect-virt which is systemd specific but should work as a regular user, otherwise you can try to add some specialized checks like looking if /dev in the mount table is devtmpfs or not. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1760173 Title: zfs, zpool commands hangs for 10 seconds without a /dev/zfs Status in lxd package in Ubuntu: Invalid Status in zfs-linux package in Ubuntu: Triaged Status in zfs-linux source package in Xenial: Fix Committed Status in zfs-linux source package in Artful: Fix Committed Status in zfs-linux source package in Bionic: Fix Committed Status in zfs-linux source package in Cosmic: Triaged Bug description: == SRU Justification, Xenial, Artful, Bionic == When outside a lxd container with zfs storage, zfs list or zpool status either returns or reports what's going on. When inside a lxd container with zfs storage, zfs list or zpool status appears to hang, no output for 10 seconds. == Fix == Inside a container we don't need the 10 seconds timeout, so check for this scenario and set the timeout to default to 0 seconds. == Regression Potential == Minimal, this caters for a corner case inside a containerized environment, the fix will not alter the behaviour for other cases. - 1. # lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 2. # apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.6.5.6-0ubuntu19 Candidate: 0.6.5.6-0ubuntu19 Version table: *** 0.6.5.6-0ubuntu19 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 3. When inside a lxd container with zfs storage, zfs list or zpool status either return or report what's going on. 4. When inside a lxd container with zfs storage, zfs list or zpool status appears to hang, no output for 10 seconds. strace reveals that without a /dev/zfs the tools wait for it to appear for 10 seconds but do not provide a command line switch to disable or make it more verbose. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: zfsutils-linux 0.6.5.6-0ubuntu19 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Mar 30 18:09:29 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1760173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775527] Re: Ubuntu16.04:KVM - xfs_log_force: error -5 returned after stress test running after a day #345
I'm personally not an xfs expert, but let me leave those two comments:
- The test was unfortunately done on an old and outdated kernel from 16.04.1:
4.4.0-36
which got already replaced by several newer kernels
Today we are already on level: 4.4.0.127.133
(and an even newer one is in the 'pipe' - in proposed: 4.4.0.128.134)
$ rmadison --arch=ppc64el linux-generic | grep xenial
linux-generic | 4.4.0.21.22| xenial | ppc64el
linux-generic | 4.4.0.127.133 | xenial-security | ppc64el
linux-generic | 4.4.0.127.133 | xenial-updates | ppc64el
linux-generic | 4.4.0.128.134 | xenial-proposed | ppc64el
So please always update the kernel to the latest version from
-updates
(or even proposed) before running such kinds of tests.
Just make sure you have access to the updates (Ubuntu archive mirror) and do
(something like):
sudo apt update && sudo apt full-upgrade && sudo apt autoremove
(and in case a kernel update was installed, reboot to activate it)
So please re-run this test on the latest 4.4.0 version (today either
4.4.0.127.133
or even 4.4.0.128.134 from proposed.)
- Does this problem also happen with the (latest) upstream 4.4 kernel?
Knowing this would help to narrow down the issue.
** Changed in: ubuntu-power-systems
Status: New => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1775527
Title:
Ubuntu16.04:KVM - xfs_log_force: error -5 returned after stress test
running after a day #345
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
New
Bug description:
== Comment: #0 - Chanh H. Nguyen - 2016-09-08 15:01:30
==
We have installed 16.04.1 on our guest and running IO stress test against via
virtual qlogic disk. After running around 8 hrs, this error popping up
"xfs_imap_to_bp: xfs_trans_read_buf() returned error -5" then with all of these
errors "xfs_log_force: error -5 returned" fill up all the log.
Jul 19 19:03:41 tinyg2 kernel: [65047.974604] XFS (vdb9): metadata I/O error:
block 0x2f140 ("xfs_trans_read_buf_map") error 5 numblks 32
Jul 19 19:03:41 tinyg2 kernel: [65047.975885] XFS (vdb9): xfs_imap_to_bp:
xfs_trans_read_buf() returned error -5.
Jul 19 19:03:41 tinyg2 kernel: [65047.976069] XFS (vdb9):
xfs_do_force_shutdown(0x8) called from line 3433 of file
/build/linux-JQcyrX/linux-4.4.0/fs/xfs/xfs_inode.c. Return address =
0xd37951f4
Jul 19 19:03:41 tinyg2 kernel: [65047.976457] XFS (vdb9): metadata I/O error:
block 0x703d54 ("xlog_iodone") error 5 numblks 64
Jul 19 19:03:41 tinyg2 kernel: [65047.976662] XFS (vdb9):
xfs_do_force_shutdown(0x2) called from line 1197 of file
/build/linux-JQcyrX/linux-4.4.0/fs/xfs/xfs_log.c. Return address =
0xd37a4c00
Jul 19 19:03:41 tinyg2 kernel: [65047.976995] XFS (vdb9): Log I/O Error
Detected. Shutting down filesystem
Jul 19 19:03:41 tinyg2 kernel: [65047.977114] XFS (vdb9): Please umount the
filesystem and rectify the problem(s)
follow with all of these error that quickly fill up dmesg log
Jul 19 19:04:37 tinyg2 kernel: [65103.515386] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:05:07 tinyg2 kernel: [65133.595369] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:05:37 tinyg2 kernel: [65163.679358] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:06:07 tinyg2 kernel: [65193.755383] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:06:37 tinyg2 kernel: [65223.835396] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:06:51 tinyg2 kernel: [65237.091455] EXT4-fs (loop1): mounting ext2
file system using the ext4 subsystem
Jul 19 19:06:51 tinyg2 kernel: [65237.093219] EXT4-fs (loop1): mounted
filesystem without journal. Opts: (null)
Jul 19 19:06:51 tinyg2 kernel: [65237.623893] Process accounting resumed
Jul 19 19:07:07 tinyg2 kernel: [65253.919361] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:07:37 tinyg2 kernel: [65283.995393] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:08:08 tinyg2 kernel: [65314.075378] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:08:38 tinyg2 kernel: [65344.155397] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:09:08 tinyg2 kernel: [65374.235367] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:09:38 tinyg2 kernel: [65404.319354] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:10:08 tinyg2 kernel: [65434.395368] XFS (vdb9): xfs_log_force:
error -5 returned.
== Comment: #1 - Chanh H. Nguyen - 2016-09-08 15:02:27
==
We recently re-created this bug on our new system "cressg2" which is using a
different SAN on kernel -36.
My Ubuntu 16.04.1 guest, cressg2, are running the IO and other stress test,
and it is hitting "xfs_log_force: error -5 returned" problem after it runs the
tests for 15 hours. It is using our lab
[Kernel-packages] [Bug 1760173] Re: zfs, zpool commands hangs for 10 seconds without a /dev/zfs
OK, I hadn't realized that, so much for my trivial testing. So, is there any simple way for any process inside a container to detect if one is inside a containerized environment without any special root privileges? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1760173 Title: zfs, zpool commands hangs for 10 seconds without a /dev/zfs Status in lxd package in Ubuntu: Invalid Status in zfs-linux package in Ubuntu: Triaged Status in zfs-linux source package in Xenial: Fix Committed Status in zfs-linux source package in Artful: Fix Committed Status in zfs-linux source package in Bionic: Fix Committed Status in zfs-linux source package in Cosmic: Triaged Bug description: == SRU Justification, Xenial, Artful, Bionic == When outside a lxd container with zfs storage, zfs list or zpool status either returns or reports what's going on. When inside a lxd container with zfs storage, zfs list or zpool status appears to hang, no output for 10 seconds. == Fix == Inside a container we don't need the 10 seconds timeout, so check for this scenario and set the timeout to default to 0 seconds. == Regression Potential == Minimal, this caters for a corner case inside a containerized environment, the fix will not alter the behaviour for other cases. - 1. # lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 2. # apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.6.5.6-0ubuntu19 Candidate: 0.6.5.6-0ubuntu19 Version table: *** 0.6.5.6-0ubuntu19 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 3. When inside a lxd container with zfs storage, zfs list or zpool status either return or report what's going on. 4. When inside a lxd container with zfs storage, zfs list or zpool status appears to hang, no output for 10 seconds. strace reveals that without a /dev/zfs the tools wait for it to appear for 10 seconds but do not provide a command line switch to disable or make it more verbose. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: zfsutils-linux 0.6.5.6-0ubuntu19 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Mar 30 18:09:29 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1760173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761674] Re: [Ubuntu 16.04] kernel: fix rwlock implementation
This is already verified - see also #8.
Changing the tags accordingly ...
** Tags removed: verification-needed-artful verification-needed-xenial
** Tags added: verification-done-artful 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/1761674
Title:
[Ubuntu 16.04] kernel: fix rwlock implementation
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Artful:
Fix Committed
Status in linux source package in Bionic:
Fix Released
Bug description:
== SRU Justification ==
IBM reported this bug due to a regression introduced by mainline commit
94232a4332de. IBM has requested this SAUCE backport to resolve this
regression in Artful and Xenial.
With Bionic and v4.15, the rwlock code has been rewritten. See upstream
gitcommit:
eb3b7b848fb3 ("s390/rwlock: introduce rwlock wait queueing").
Since the upstream code has been rewritten there also won't be an upstream
git commit id available which contains the attached fix.
== Fix ==
UBUNTU: SAUCE: (no-up) s390: fix rwlock implementation
== Regression Potential ==
Low. The backport was written and tested by IBM. It is specific to s390.
== 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.
Description: kernel: fix rwlock implementation
Symptom: Kernel hangs, due to deadlock on an rwlock.
Problem: With upstream commit 94232a4332de ("s390/rwlock: improve writer
fairness") rwlock writer fairness was supposed to be
implemented. If a writer tries to take an rwlock it sets
unconditionally the writer bit within the lock word and waits
until all readers have released the lock. This however can lead
to a deadlock since rwlocks can be taken recursively by readers.
If e.g. CPU 0 holds the lock as a reader, and CPU 1 wants to
write-lock the lock, then CPU 1 sets the writer bit and
afterwards busy waits for CPU 0 to release the lock. If now CPU 0
tries to read-lock the lock again (recursively) it will also
busy
wait until CPU 1 removes the writer bit, which will never
happen,
since it waits for the first reader on CPU 0 to release the
lock.
Solution: Revert the rwlock writer fairness semantics again.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1761674/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774181] Re: Update to upstream's implementation of Spectre v1 mitigation
** Changed in: linux (Ubuntu Xenial) 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/1774181 Title: Update to upstream's implementation of Spectre v1 mitigation Status in linux package in Ubuntu: Incomplete Status in linux source package in Precise: New Status in linux source package in Trusty: New Status in linux source package in Xenial: Fix Committed Bug description: Xenial/Trusty/Precise are currently lacking full support of upstream's Spectre v1 mitigation. Add the missing patches and merge them with Ubuntu's current implementation. == SRU Justification == Ubuntu's Spectre v1 mitigation is based on the original embargoed patchset which introduced a barrier macro to prevent speculation beyond array boundaries for user controlled indices. What eventually landed in upstream is slightly different and uses a barrier macro in combination with a masking solution (plus syscall table and user pointer sanitation). During the updates to newer stable upstream versions, all those patches were skipped. After reviewing them, we want to bring them back and merge them with the current implementation which brings us back in sync with upstream stable. == Fix == Add all the missing Spectre v1 patches from upstream stable 4.4.118 to 4.4.131. Where appropriate, replace Ubuntu's additional barriers with the masking macro. == Regression Potential == Low. The patches have been in upstream for quite a while now and we keep the speculation barriers that are currently in Ubuntu but not in upstream. == Test Case == TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774181/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1760173] Re: zfs, zpool commands hangs for 10 seconds without a /dev/zfs
That's because an attached process ("lxc-attach" or "lxc exec") isn't a
child of init, it's spawned directly by liblxc and so does have our env
variable set.
Any process which is a direct or indirect child of PID1 in the container
will be inheriting its environment through that path and as init systems
strip any inherited environment, the container env variable will not be
set for those.
So for example, sshing into your container will not have the env
variable set, same goes for any systemd unit.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1760173
Title:
zfs, zpool commands hangs for 10 seconds without a /dev/zfs
Status in lxd package in Ubuntu:
Invalid
Status in zfs-linux package in Ubuntu:
Triaged
Status in zfs-linux source package in Xenial:
Fix Committed
Status in zfs-linux source package in Artful:
Fix Committed
Status in zfs-linux source package in Bionic:
Fix Committed
Status in zfs-linux source package in Cosmic:
Triaged
Bug description:
== SRU Justification, Xenial, Artful, Bionic ==
When outside a lxd container with zfs storage, zfs list or zpool
status either returns or reports what's going on.
When inside a lxd container with zfs storage, zfs list or zpool status
appears to hang, no output for 10 seconds.
== Fix ==
Inside a container we don't need the 10 seconds timeout, so check for
this scenario and set the timeout to default to 0 seconds.
== Regression Potential ==
Minimal, this caters for a corner case inside a containerized
environment, the fix will not alter the behaviour for other cases.
-
1. # lsb_release -rd
Description: Ubuntu 16.04.4 LTS
Release: 16.04
2. # apt-cache policy zfsutils-linux
zfsutils-linux:
Installed: 0.6.5.6-0ubuntu19
Candidate: 0.6.5.6-0ubuntu19
Version table:
*** 0.6.5.6-0ubuntu19 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
100 /var/lib/dpkg/status
3. When inside a lxd container with zfs storage, zfs list or zpool
status either return or report what's going on.
4. When inside a lxd container with zfs storage, zfs list or zpool
status appears to hang, no output for 10 seconds.
strace reveals that without a /dev/zfs the tools wait for it to appear
for 10 seconds but do not provide a command line switch to disable or
make it more verbose.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: zfsutils-linux 0.6.5.6-0ubuntu19
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Fri Mar 30 18:09:29 2018
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1760173/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772593] Re: cpum_sf: ensure sample freq is non-zero
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
** 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/1772593
Title:
cpum_sf: ensure sample freq is non-zero
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Artful:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
A regression was introduced by commit 8c069ff4bd606 in v3.14-rc1. IBM
is requested commit 4bbaf2584b86 in all Ubuntu kernels to resolve this
isue.
Bug Description: cpum_sf: ensure sample freq is non-zero
Symptom: A kernel crash might occur.
Problem: An FP divide exception during the sample rate
initialization for the hardware sampling facility.
Solution: Ensure that the sample frequency of the perf
event attribute is non-zero.
== Fix ==
4bbaf2584b86 ("s390/cpum_sf: ensure sample frequency of perf event attributes
is non-zero")
== Regression Potential ==
Low. Fix is specific to s390.
== 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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1772593/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770974] Re: Fix several bugs in RDMA/hns driver
** Description changed: [Impact] - Several issues in the RDMA/hns driver for HiSilicon network adapters have recently landed upstream. - - TBD: Summarize. + Several issues and features in the RDMA/hns driver for HiSilicon network adapters have recently landed upstream. This includes fixes for crashes and endianness issues, among others. [Test Case] - TBD + Server side: + ubuntu@d06-1:~$ ib_write_bw -n 5 -d hns_2 + + + * Waiting for client to connect... * + + hr_qp->port_num= 0x1 + --- + RDMA_Write BW Test + Dual-port : OFFDevice : hns_2 + Number of qps : 1 Transport type : IB + Connection type : RC Using SRQ : OFF + CQ Moderation : 5 + Mtu : 1024[B] + Link type : Ethernet + GID index : 2 + Max inline data : 0[B] + rdma_cm QPs : OFF + Data ex. method : Ethernet + --- + local address: LID QPN 0x000c PSN 0x368fa8 RKey 0x000200 VAddr 0x00be39 + GID: 00:00:00:00:00:00:00:00:00:00:255:255:10:228:68:237 + remote address: LID QPN 0x000c PSN 0x19f3aa RKey 0x000200 VAddr 0x008338 + GID: 00:00:00:00:00:00:00:00:00:00:255:255:10:228:68:192 + --- + #bytes #iterationsBW peak[MB/sec]BW average[MB/sec] MsgRate[Mpps] + 65536 5108.08 108.08 0.001729 + --- + + Client side: + ubuntu@d06-2:~$ ib_write_bw -n 5 -d hns_2 10.228.68.237 + hr_qp->port_num= 0x1 + --- + RDMA_Write BW Test + Dual-port : OFFDevice : hns_2 + Number of qps : 1 Transport type : IB + Connection type : RC Using SRQ : OFF + TX depth: 5 + CQ Moderation : 5 + Mtu : 1024[B] + Link type : Ethernet + GID index : 2 + Max inline data : 0[B] + rdma_cm QPs : OFF + Data ex. method : Ethernet + --- + local address: LID QPN 0x000c PSN 0x19f3aa RKey 0x000200 VAddr 0x008338 + GID: 00:00:00:00:00:00:00:00:00:00:255:255:10:228:68:192 + remote address: LID QPN 0x000c PSN 0x368fa8 RKey 0x000200 VAddr 0x00be39 + GID: 00:00:00:00:00:00:00:00:00:00:255:255:10:228:68:237 + --- + #bytes #iterationsBW peak[MB/sec]BW average[MB/sec] MsgRate[Mpps] + 65536 5108.08 108.08 0.001729 + --- [Regression Risk] - TBD + TLDR; this driver isn't usable today, so changes to it carry negligible regression risk. + + These patches are localized to the hns/RDMA driver. This driver is for + hardware in the hip07/hip08 SoCs, which Ubuntu supports in the D05 and + D06 servers respectively. D05 firmware has intentionally disabled this + feature by not exposing the ACPI ID for it. The driver therefore doesn't + find the device on that platform, so there is no regression risk. + + D06 *does* enable this device in firmware. However, the current bionic + kernel crashes when loading the base ethernet driver (hns3 - LP: + #1768670) on this platform, so this feature is also currently unusable + there. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770974 Title: Fix several bugs in RDMA/hns driver Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: [Impact] Several issues and features in the RDMA/hns driver for HiSilicon network adapters have recently landed upstream. This includes fixes for crashes and endianness issues, among others. [Test Case] Server side: ubuntu@d06-1:~$ ib_write_bw -n 5 -d hns_2 * Waiting for client to connect... * hr_qp->port_num= 0x1 --- RDMA_Write BW Test Dual-port : OFFDevice : hns_2 Number of qps : 1 Transport type : IB Connection type : RC Using SRQ : OFF CQ Moderation : 5 Mtu : 1024[B] Link type : Ethernet GID index
[Kernel-packages] [Bug 1772991] Re: [Ubuntu 18.04.1] POWER9 - Nvidia Volta - Kernel changes to enable Nvidia driver on bare metal
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed ** Changed in: ubuntu-power-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/1772991 Title: [Ubuntu 18.04.1] POWER9 - Nvidia Volta - Kernel changes to enable Nvidia driver on bare metal Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: == SRU Justification == 12 kernel patches have been identified as needed to support Nvidia Volta on bare metal. All are accepted upstream in 4.17. Three of those are already in bionic, leaving a total of 9 remaining commits needed in bionic. This pull request is for those other 9 commits. == Regression Potential == All of the commits are specific to powerpc. == Test Case == A test kernel was built with these patches and tested by IBM. == Comment: #0 - Barry B. Arndt - 2018-05-23 13:40:33 == 12 kernel patches have been identified as needed to support Nvidia Volta on bare metal. All are accepted upstream in 4.17. Three of those are already in bionic, leaving a total of 9 remaining commits needed in bionic. Those 9 commits are: 720c84046c26 powerpc/npu-dma.c: Fix crash after __mmu_notifier_register failure 2b74e2a9b39d powerpc/powernv/npu: Fix deadlock in mmio_invalidate() 5ee573e8ef03 powerpc/powernv/mce: Don't silently restart the machine fb5924fddf9e powerpc/mm: Flush cache on memory hot(un)plug 7fd6641de28f powerpc/powernv/memtrace: Let the arch hotunplug code flush cache 28a5933e8d36 powerpc/powernv/npu: Add lock to prevent race in concurrent context init/destroy a1409adac748 powerpc/powernv/npu: Prevent overwriting of pnv_npu2_init_contex() callback parameters d0cf9b561ca9 powerpc/powernv/npu: Do a PID GPU TLB flush when invalidating a large address range 75ecfb49516c powerpc/mce: Fix a bug where mce loops on memory UE. We cherry-picked the commits, and all applied cleanly. The resultant kernel built successfully and loaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1772991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773509] Re: ELANPAD ELAN0612 does not work, patch available
Thanks for accepting this. Any idea when this will be available in the packages? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773509 Title: ELANPAD ELAN0612 does not work, patch available Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: == SRU Justification == Seems there is a new version of the ELANPAD touchpad with identifier ELAN0612 that is being included in newer laptops. The kernel itself doesn't have support for this touchpad yet. However, the patch to get this working is trivial. Since people start being affected by this, this patch is being sent as a SAUCE patch until it lands upstream. The upstream bug at the Kernel project, including the patch is here: https://bugzilla.kernel.org/show_bug.cgi?id=199253 == Fix == UBUNTU: SAUCE: Input: elan_i2c - add ELAN0612 to the ACPI table == Regression Potential == Low. One liner to add a device id. == 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773509/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774636] Re: Lenovo V330 needs patch in ideapad_laptop module for rfkill
Sorry for the delay. Yes, this seems to work as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774636 Title: Lenovo V330 needs patch in ideapad_laptop module for rfkill Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: The quite new Lenovo V330 is not yet completely supported by the ideapad_laptop module. Without an explicit rule, this module assumes that a hardware kill switch for wireless devices exists and thus sometimes boots up with all devices hard blocked and no way to reenable them at runtime. I have provided a patch to the kernel developers upstream: https://bugzilla.kernel.org/show_bug.cgi?id=199855 However, there is not much activity at the moment. Since this laptop is available now and the bug is a real blocker for unexperienced users, would it be possible to add the (quite simple) fix to the ubuntu kernel until it is accepted upstream? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1760173] Re: zfs, zpool commands hangs for 10 seconds without a /dev/zfs
I'm confused too then, how is that when I start a process inside the container, such as from a shell it can access this environment variable and my fix works? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1760173 Title: zfs, zpool commands hangs for 10 seconds without a /dev/zfs Status in lxd package in Ubuntu: Invalid Status in zfs-linux package in Ubuntu: Triaged Status in zfs-linux source package in Xenial: Fix Committed Status in zfs-linux source package in Artful: Fix Committed Status in zfs-linux source package in Bionic: Fix Committed Status in zfs-linux source package in Cosmic: Triaged Bug description: == SRU Justification, Xenial, Artful, Bionic == When outside a lxd container with zfs storage, zfs list or zpool status either returns or reports what's going on. When inside a lxd container with zfs storage, zfs list or zpool status appears to hang, no output for 10 seconds. == Fix == Inside a container we don't need the 10 seconds timeout, so check for this scenario and set the timeout to default to 0 seconds. == Regression Potential == Minimal, this caters for a corner case inside a containerized environment, the fix will not alter the behaviour for other cases. - 1. # lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 2. # apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.6.5.6-0ubuntu19 Candidate: 0.6.5.6-0ubuntu19 Version table: *** 0.6.5.6-0ubuntu19 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 3. When inside a lxd container with zfs storage, zfs list or zpool status either return or report what's going on. 4. When inside a lxd container with zfs storage, zfs list or zpool status appears to hang, no output for 10 seconds. strace reveals that without a /dev/zfs the tools wait for it to appear for 10 seconds but do not provide a command line switch to disable or make it more verbose. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: zfsutils-linux 0.6.5.6-0ubuntu19 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Mar 30 18:09:29 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1760173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774181] Re: Update to upstream's implementation of Spectre v1 mitigation
** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774181 Title: Update to upstream's implementation of Spectre v1 mitigation Status in linux package in Ubuntu: Incomplete Status in linux source package in Precise: New Status in linux source package in Trusty: New Status in linux source package in Xenial: New Bug description: Xenial/Trusty/Precise are currently lacking full support of upstream's Spectre v1 mitigation. Add the missing patches and merge them with Ubuntu's current implementation. == SRU Justification == Ubuntu's Spectre v1 mitigation is based on the original embargoed patchset which introduced a barrier macro to prevent speculation beyond array boundaries for user controlled indices. What eventually landed in upstream is slightly different and uses a barrier macro in combination with a masking solution (plus syscall table and user pointer sanitation). During the updates to newer stable upstream versions, all those patches were skipped. After reviewing them, we want to bring them back and merge them with the current implementation which brings us back in sync with upstream stable. == Fix == Add all the missing Spectre v1 patches from upstream stable 4.4.118 to 4.4.131. Where appropriate, replace Ubuntu's additional barriers with the masking macro. == Regression Potential == Low. The patches have been in upstream for quite a while now and we keep the speculation barriers that are currently in Ubuntu but not in upstream. == Test Case == TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774181/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775477] Re: Xenial update to 4.4.133 stable release
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+ by originating either directly from a mainline/stable Linux tree or
+ a minimally backported form of that patch. The 4.4.133 upstream stable
+ patch set is now available. It should be included in the Ubuntu
+ kernel as well.
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The 4.4.133 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+ git://git.kernel.org/
-git://git.kernel.org/
+ TEST CASE: TBD
- TEST CASE: TBD
-
-The following patches from the 4.4.133 stable release shall be
- applied:
+ The following patches from the 4.4.133 stable release shall be applied:
+ * 8139too: Use disable_irq_nosync() in rtl8139_poll_controller()
+ * bridge: check iface upper dev when setting master via ioctl
+ * dccp: fix tasklet usage
+ * ipv4: fix memory leaks in udp_sendmsg, ping_v4_sendmsg
+ * llc: better deal with too small mtu
+ * net: ethernet: sun: niu set correct packet size in skb
+ * net/mlx4_en: Verify coalescing parameters are in range
+ * net_sched: fq: take care of throttled flows before reuse
+ * net: support compat 64-bit time in {s,g}etsockopt
+ * openvswitch: Don't swap table in nlattr_set() after OVS_ATTR_NESTED is found
+ * qmi_wwan: do not steal interfaces from class drivers
+ * r8169: fix powering up RTL8168h
+ * sctp: handle two v4 addrs comparison in sctp_inet6_cmp_addr
+ * sctp: use the old asoc when making the cookie-ack chunk in dupcook_d
+ * tg3: Fix vunmap() BUG_ON() triggered from tg3_free_consistent().
+ * bonding: do not allow rlb updates to invalid mac
+ * tcp: ignore Fast Open on repair mode
+ * sctp: fix the issue that the cookie-ack with auth can't get processed
+ * sctp: delay the authentication for the duplicated cookie-echo chunk
+ * ALSA: timer: Call notifier in the same spinlock
+ * audit: move calcs after alloc and check when logging set loginuid
+ * arm64: introduce mov_q macro to move a constant into a 64-bit register
+ * arm64: Add work around for Arm Cortex-A55 Erratum 1024718
+ * futex: Remove unnecessary warning from get_futex_key
+ * futex: Remove duplicated code and fix undefined behaviour
+ * xfrm: fix xfrm_do_migrate() with AEAD e.g(AES-GCM)
+ * lockd: lost rollback of set_grace_period() in lockd_down_net()
+ * Revert "ARM: dts: imx6qdl-wandboard: Fix audio channel swap"
+ * l2tp: revert "l2tp: fix missing print session offset info"
+ * pipe: cap initial pipe capacity according to pipe-max-size limit
+ * futex: futex_wake_op, fix sign_extend32 sign bits
+ * kernel/exit.c: avoid undefined behaviour when calling wait4()
+ * usbip: usbip_host: refine probe and disconnect debug msgs to be useful
+ * usbip: usbip_host: delete device from busid_table after rebind
+ * usbip: usbip_host: run rebind from exit when module is removed
+ * usbip: usbip_host: fix NULL-ptr deref and use-after-free errors
+ * usbip: usbip_host: fix bad unlock balance during stub_probe()
+ * ALSA: usb: mixer: volume quirk for CM102-A+/102S+
+ * ALSA: hda: Add Lenovo C50 All in one to the power_save blacklist
+ * ALSA: control: fix a redundant-copy issue
+ * spi: pxa2xx: Allow 64-bit DMA
+ * powerpc/powernv: panic() on OPAL < V3
+ * powerpc/powernv: Remove OPALv2 firmware define and references
+ * powerpc/powernv: remove FW_FEATURE_OPALv3 and just use FW_FEATURE_OPAL
+ * cpuidle: coupled: remove unused define cpuidle_coupled_lock
+ * powerpc: Don't preempt_disable() in show_cpuinfo()
+ * vmscan: do not force-scan file lru if its absolute size is small
+ * mm: filemap: remove redundant code in do_read_cache_page
+ * mm: filemap: avoid unnecessary calls to lock_page when waiting for IO to
complete
+ during a read
+ * signals: avoid unnecessary taking of sighand->siglock
+ * tracing/x86/xen: Remove zero data size trace events
trace_xen_mmu_flush_tlb{_all}
+ * proc read mm's {arg,env}_{start,end} with mmap semaphore taken.
+ * powerpc/powernv: Fix NVRAM sleep in invalid context when crashing
+ * mm: don't allow deferred pages with NEED_PER_CPU_KM
+ * s390/qdio: fix access to uninitialized qdio_q fields
+ * s390/qdio: don't release memory in qdio_setup_irq()
+ * s390: remove indirect branch from do_softirq_own_stack
+ * efi: Avoid potential crashes, fix the 'struct efi_pci_io_protocol_32'
definition
+ for mixed mode
+ * ARM: 8771/1: kprobes: Prohibit kprobes on do_undefinstr
+ *
[Kernel-packages] [Bug 1720930] Re: wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)
** Changed in: linux (Ubuntu Artful) Status: New => Fix Committed ** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: plymouth (Ubuntu Artful) Status: New => Invalid ** Changed in: plymouth (Ubuntu Bionic) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720930 Title: wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22) Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in linux source package in Artful: Fix Committed Status in plymouth source package in Artful: Invalid Status in linux source package in Bionic: Fix Committed Status in plymouth source package in Bionic: Invalid Bug description: ===SRU Justification=== [Impact] Message "wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)" showed when the system shutdown. [Test] Users confirmed the patch fixes their issue. [Regression Potential] Low. It's in mainline Linux, limited to iwlwifi, trivial change. Sara Sharon (1): iwlwifi: mvm: fix "failed to remove key" message ==Original Bug Report=== When running artful on a new Zenbook Pro (uses Intel Wireless 8265), I get a hung shutdown with the message "wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)". The kernel is also trying to load firmware versions that do not exist on the system i.e. versions 33 then 32 of the firmware. It then seems to load version 31 of the firmware. Wireless features seem to work normally. The issues are just at shutdown time. 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 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dylan 1621 F pulseaudio CurrentDesktop: GNOME Date: Tue Oct 3 06:12:13 2017 HibernationDevice: RESUME=UUID=2b6908b4-d463-4170-9be5-556145c71a0e InstallationDate: Installed on 2017-10-02 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5755 IMC Networks Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX550VE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=aa3dfd29-caf8-4882-906e-1b31b672d2c2 ro quiet splash threadirqs acpi_osi=! acpi_osi=Linux acpi_backlight=native 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.168 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550VE.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550VE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX550VE.300:bd06/05/2017:svnASUSTeKCOMPUTERINC.:pnUX550VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX550VE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1720930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1760173] Re: zfs, zpool commands hangs for 10 seconds without a /dev/zfs
I'm confused, how is this change going to work when the "container" environment variable is only present in PID1's environment but not in any of its descendants? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1760173 Title: zfs, zpool commands hangs for 10 seconds without a /dev/zfs Status in lxd package in Ubuntu: Invalid Status in zfs-linux package in Ubuntu: Triaged Status in zfs-linux source package in Xenial: Fix Committed Status in zfs-linux source package in Artful: Fix Committed Status in zfs-linux source package in Bionic: Fix Committed Status in zfs-linux source package in Cosmic: Triaged Bug description: == SRU Justification, Xenial, Artful, Bionic == When outside a lxd container with zfs storage, zfs list or zpool status either returns or reports what's going on. When inside a lxd container with zfs storage, zfs list or zpool status appears to hang, no output for 10 seconds. == Fix == Inside a container we don't need the 10 seconds timeout, so check for this scenario and set the timeout to default to 0 seconds. == Regression Potential == Minimal, this caters for a corner case inside a containerized environment, the fix will not alter the behaviour for other cases. - 1. # lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 2. # apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.6.5.6-0ubuntu19 Candidate: 0.6.5.6-0ubuntu19 Version table: *** 0.6.5.6-0ubuntu19 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 3. When inside a lxd container with zfs storage, zfs list or zpool status either return or report what's going on. 4. When inside a lxd container with zfs storage, zfs list or zpool status appears to hang, no output for 10 seconds. strace reveals that without a /dev/zfs the tools wait for it to appear for 10 seconds but do not provide a command line switch to disable or make it more verbose. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: zfsutils-linux 0.6.5.6-0ubuntu19 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Mar 30 18:09:29 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1760173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720930] Re: wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)
** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: plymouth (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: plymouth (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720930 Title: wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22) Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in linux source package in Artful: Fix Committed Status in plymouth source package in Artful: Invalid Status in linux source package in Bionic: Fix Committed Status in plymouth source package in Bionic: Invalid Bug description: ===SRU Justification=== [Impact] Message "wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)" showed when the system shutdown. [Test] Users confirmed the patch fixes their issue. [Regression Potential] Low. It's in mainline Linux, limited to iwlwifi, trivial change. Sara Sharon (1): iwlwifi: mvm: fix "failed to remove key" message ==Original Bug Report=== When running artful on a new Zenbook Pro (uses Intel Wireless 8265), I get a hung shutdown with the message "wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)". The kernel is also trying to load firmware versions that do not exist on the system i.e. versions 33 then 32 of the firmware. It then seems to load version 31 of the firmware. Wireless features seem to work normally. The issues are just at shutdown time. 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 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dylan 1621 F pulseaudio CurrentDesktop: GNOME Date: Tue Oct 3 06:12:13 2017 HibernationDevice: RESUME=UUID=2b6908b4-d463-4170-9be5-556145c71a0e InstallationDate: Installed on 2017-10-02 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5755 IMC Networks Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX550VE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=aa3dfd29-caf8-4882-906e-1b31b672d2c2 ro quiet splash threadirqs acpi_osi=! acpi_osi=Linux acpi_backlight=native 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.168 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550VE.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550VE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX550VE.300:bd06/05/2017:svnASUSTeKCOMPUTERINC.:pnUX550VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX550VE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1720930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773295] Re: False positive ACPI _PRS error messages
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773295 Title: False positive ACPI _PRS error messages Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Bug description: New platforms have hardware registers for routing table implemented as "write once". Once set by UEFI firmware during POST, OS will not be able to modify the routing table, and ACPI _PRS method are removed according to ACPI spec. As a result, generating the error messages "ACPI Exception: AE_NOT_FOUND, Evaluating _PRS" in kernel by default does not make sense, and they should be muted by default. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1773295/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774173] Re: Xenial update to 4.4.132 stable release
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) 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/1774173 Title: Xenial update to 4.4.132 stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.132 upstream stable stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.132 stable release shall be applied: * Linux 4.4.132 * perf/x86: Fix possible Spectre-v1 indexing for x86_pmu::event_map() * perf/core: Fix possible Spectre-v1 indexing for ->aux_pages[] * perf/x86/msr: Fix possible Spectre-v1 indexing in the MSR driver * perf/x86/cstate: Fix possible Spectre-v1 indexing for pkg_msr * perf/x86: Fix possible Spectre-v1 indexing for hw_perf_event cache_* * tracing/uprobe_event: Fix strncpy corner case * Revert "Bluetooth: btusb: Fix quirk for Atheros 1525/QCA6174" * atm: zatm: Fix potential Spectre v1 * net: atm: Fix potential Spectre v1 * can: kvaser_usb: Increase correct stats counter in kvaser_usb_rx_can_msg() * tracing: Fix regex_match_front() to not over compare the test string * libata: Apply NOLPM quirk for SanDisk SD7UB3Q*G1001 SSDs * rfkill: gpio: fix memory leak in probe error path * xfrm_user: fix return value from xfrm_user_rcv_msg * f2fs: fix a dead loop in f2fs_fiemap() * bdi: Fix oops in wb_workfn() * tcp: fix TCP_REPAIR_QUEUE bound checking * perf: Remove superfluous allocation error check * soreuseport: initialise timewait reuseport field * dccp: initialize ireq->ir_mark * net: fix uninit-value in __hw_addr_add_ex() * net: initialize skb->peeked when cloning * net: fix rtnh_ok() * netlink: fix uninit-value in netlink_sendmsg * crypto: af_alg - fix possible uninit-value in alg_bind() * ipvs: fix rtnl_lock lockups caused by start_sync_thread * usb: musb: host: fix potential NULL pointer dereference * USB: serial: option: adding support for ublox R410M * USB: serial: option: reimplement interface masking * USB: Accept bulk endpoints with 1024-byte maxpacket * USB: serial: visor: handle potential invalid device configuration * test_firmware: fix setting old custom fw path back on exit, second try * drm/vmwgfx: Fix a buffer object leak * IB/mlx5: Use unlimited rate when static rate is not supported * NET: usb: qmi_wwan: add support for ublox R410M PID 0x90b2 * RDMA/mlx5: Protect from shift operand overflow * RDMA/ucma: Allow resolving address w/o specifying source address * xfs: prevent creating negative-sized file via INSERT_RANGE * Input: atmel_mxt_ts - add touchpad button mapping for Samsung Chromebook Pro * Input: leds - fix out of bound access * tracepoint: Do not warn on ENOMEM * ALSA: aloop: Add missing cable lock to ctl API callbacks * ALSA: aloop: Mark paused device as inactive * ALSA: seq: Fix races at MIDI encoding in snd_virmidi_output_trigger() * ALSA: pcm: Check PCM state at xfern compat ioctl * USB: serial: option: Add support for Quectel EP06 * gpmi-nand: Handle ECC Errors in erased pages * ath10k: rebuild crypto header in rx data frames * ath10k: fix rfc1042 header retrieval in QCA4019 with eth decap mode * mac80211: Add RX flag to indicate ICV stripped * mac80211: allow same PN for AMSDU sub-frames * mac80211: allow not sending MIC up from driver for HW crypto * percpu: include linux/sched.h for cond_resched() * KVM: s390: Enable all facility bits that are known good for passthrough * bpf: map_get_next_key to return first key on NULL * perf/core: Fix the perf_cpu_time_max_percent check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774336] Re: FS-Cache: Assertion failed: FS-Cache: 6 == 5 is false
** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774336 Title: FS-Cache: Assertion failed: FS-Cache: 6 == 5 is false Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: New Status in linux source package in Xenial: New Status in linux source package in Artful: New Status in linux source package in Bionic: New Bug description: == SRU Justification == [Impact] Oops during heavy NFS + FSCache use: [81738.886634] FS-Cache: [81738.888281] FS-Cache: Assertion failed [81738.889461] FS-Cache: 6 == 5 is false [81738.890625] [ cut here ] [81738.891706] kernel BUG at /build/linux-hVVhWi/linux-4.4.0/fs/fscache/operation.c:494! 6 == 5 represents an operation being DEAD when it was not expected to be. [Cause] There is a race in fscache and cachefiles. One thread is in cachefiles_read_waiter: 1) object->work_lock is taken. 2) the operation is added to the to_do list. 3) the work lock is dropped. 4) fscache_enqueue_retrieval is called, which takes a reference. Another thread is in cachefiles_read_copier: 1) object->work_lock is taken 2) an item is popped off the to_do list. 3) object->work_lock is dropped. 4) some processing is done on the item, and fscache_put_retrieval() is called, dropping a reference. Now if the this process in cachefiles_read_copier takes place *between* steps 3 and 4 in cachefiles_read_waiter, a reference will be dropped before it is taken, which leads to the objects reference count hitting zero, which leads to lifecycle events for the object happening too soon, leading to the assertion failure later on. (This is simplified and clarified from the original upstream analysis for this patch at https://www.redhat.com/archives/linux- cachefs/2018-February/msg1.html and from a similar patch with a different approach to fixing the bug at https://www.redhat.com/archives/linux-cachefs/2017-June/msg2.html) [Fix] Move fscache_enqueue_retrieval under the lock in cachefiles_read_waiter. This means that the object cannot be popped off the to_do list until it is in a fully consistent state with the reference taken. [Testcase] A user has run ~100 hours of NFS stress tests and not seen this bug recur. [Regression Potential] - Limited to fscache/cachefiles. - The change makes things more conservative (doing more under lock) so that's reassuring. - There may be performance impacts but none have been observed so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774336/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775527] Re: Ubuntu16.04:KVM - xfs_log_force: error -5 returned after stress test running after a day #345
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Tags added: triage-g
** Changed in: ubuntu-power-systems
Importance: Undecided => High
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1775527
Title:
Ubuntu16.04:KVM - xfs_log_force: error -5 returned after stress test
running after a day #345
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
New
Bug description:
== Comment: #0 - Chanh H. Nguyen - 2016-09-08 15:01:30
==
We have installed 16.04.1 on our guest and running IO stress test against via
virtual qlogic disk. After running around 8 hrs, this error popping up
"xfs_imap_to_bp: xfs_trans_read_buf() returned error -5" then with all of these
errors "xfs_log_force: error -5 returned" fill up all the log.
Jul 19 19:03:41 tinyg2 kernel: [65047.974604] XFS (vdb9): metadata I/O error:
block 0x2f140 ("xfs_trans_read_buf_map") error 5 numblks 32
Jul 19 19:03:41 tinyg2 kernel: [65047.975885] XFS (vdb9): xfs_imap_to_bp:
xfs_trans_read_buf() returned error -5.
Jul 19 19:03:41 tinyg2 kernel: [65047.976069] XFS (vdb9):
xfs_do_force_shutdown(0x8) called from line 3433 of file
/build/linux-JQcyrX/linux-4.4.0/fs/xfs/xfs_inode.c. Return address =
0xd37951f4
Jul 19 19:03:41 tinyg2 kernel: [65047.976457] XFS (vdb9): metadata I/O error:
block 0x703d54 ("xlog_iodone") error 5 numblks 64
Jul 19 19:03:41 tinyg2 kernel: [65047.976662] XFS (vdb9):
xfs_do_force_shutdown(0x2) called from line 1197 of file
/build/linux-JQcyrX/linux-4.4.0/fs/xfs/xfs_log.c. Return address =
0xd37a4c00
Jul 19 19:03:41 tinyg2 kernel: [65047.976995] XFS (vdb9): Log I/O Error
Detected. Shutting down filesystem
Jul 19 19:03:41 tinyg2 kernel: [65047.977114] XFS (vdb9): Please umount the
filesystem and rectify the problem(s)
follow with all of these error that quickly fill up dmesg log
Jul 19 19:04:37 tinyg2 kernel: [65103.515386] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:05:07 tinyg2 kernel: [65133.595369] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:05:37 tinyg2 kernel: [65163.679358] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:06:07 tinyg2 kernel: [65193.755383] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:06:37 tinyg2 kernel: [65223.835396] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:06:51 tinyg2 kernel: [65237.091455] EXT4-fs (loop1): mounting ext2
file system using the ext4 subsystem
Jul 19 19:06:51 tinyg2 kernel: [65237.093219] EXT4-fs (loop1): mounted
filesystem without journal. Opts: (null)
Jul 19 19:06:51 tinyg2 kernel: [65237.623893] Process accounting resumed
Jul 19 19:07:07 tinyg2 kernel: [65253.919361] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:07:37 tinyg2 kernel: [65283.995393] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:08:08 tinyg2 kernel: [65314.075378] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:08:38 tinyg2 kernel: [65344.155397] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:09:08 tinyg2 kernel: [65374.235367] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:09:38 tinyg2 kernel: [65404.319354] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:10:08 tinyg2 kernel: [65434.395368] XFS (vdb9): xfs_log_force:
error -5 returned.
== Comment: #1 - Chanh H. Nguyen - 2016-09-08 15:02:27
==
We recently re-created this bug on our new system "cressg2" which is using a
different SAN on kernel -36.
My Ubuntu 16.04.1 guest, cressg2, are running the IO and other stress test,
and it is hitting "xfs_log_force: error -5 returned" problem after it runs the
tests for 15 hours. It is using our lab storage (SVC SAN storage configuation
with access to DS8000 Volume) and switch, compare to tinyg3, so it is using
different storage and fabric switch.
root@cressg2:~# uname -a
Linux cressg2 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:00:57 UTC 2016
ppc64le ppc64le ppc64le GNU/Linux
[Wed Sep 7 10:26:48 2016] XFS (vdb8): xfs_log_force: error -5 returned.
[Wed Sep 7 10:27:18 2016] XFS (vdb8): xfs_log_force: error -5 returned.
[Wed Sep 7 10:27:32 2016] XFS (vdb8): xfs_log_force: error -5 returned.
[Wed Sep 7 10:27:33 2016] XFS (vdb8): xfs_log_force: error -5 returned.
[Wed Sep 7 10:27:33 2016] XFS (vdb8): xfs_log_force: error -5 returned.
[Wed Sep 7 10:27:48 2016] XFS (vdb8): xfs_log_force: error -5 returned.
[Wed Sep 7 10:27:48 2016] XFS (vdb8): xfs_log_force: error -5 returned.
[Wed Sep 7 10:27:49 2016] XFS (vdb8): xfs_log_force: error -5 returned.
[Wed Sep 7 10:27:56 2016] XFS (vdb8): xfs_log_force: error -5 returned.
[Wed Sep 7 10:28:18 2016] XFS (vdb8): xfs_log_force: error -5 returned.
[Kernel-packages] [Bug 1769792] Re: Keyboard and Touchpad do not work after suspend/resume
I have this bug, at least partially. My keyboard keeps working, but touchpad doesn't work after reboot. I originally commented in this report: https://bugs.launchpad.net/ubuntu/artful/+source/linux/+bug/1723799 but they asked to create a new report. This is what I said there: I too am affected now. After suspend+resume, my touchpad isn't found. Rebooting doesn't help: I really have to turn the machine off and on again. I can attach mouse, and then if I try to open touchpad settings in Input Devices settings (I use Kubuntu), it says that Touchpad isn't found, and xinput doesn't show it either. - Fujitsu E556 laptop - 4.15.0-20-generic #21-Ubuntu I still have Ubuntu 16.04 on one SSD with the kernel 4.4.0-119-generic, and the issue doesn't appear there. I think the issue didn't appear on Kubuntu 17.04 either. I didn't try 17.10. The workaround mentioned in the original post didn't work for me. When I ran sudo modprobe i2c-hid, I got this message: rmmod: ERROR: Module i2c_hid is not currently loaded The command sudo modprobe i2c-hid completed, but the touchpad didn't start working. == As was asked by jsalisphury, I tested this with the latest mainline kernel (generic) too: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17/ The problem wasn't affected – the touchpad doesn't resume. I hope this helps. I'm not sure if *I* should add the 'kernel-bug- exists-upstream' tag though, because I'm not OP, and my problem is slightly different. I hope this helps -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769792 Title: Keyboard and Touchpad do not work after suspend/resume Status in linux package in Ubuntu: Incomplete Bug description: My laptop is a Toshiba Satellite C850D with updated 18.04 installed. When resuming from suspend, I have no keyboard and touchpad. dmesg shows "i8042: Can't reactivate KBD port" This looks like a recurring problem, and is just like these: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1014240 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1142118 Here's the dmesg output from before and after suspending. https://paste.ubuntu.com/p/rsFX9Yw7Xh/ This post also talks about this bit failing for a lot of people! http://lightrush.ndoytchev.com/random-1/i8042quirkoptions Some of the function keys work, such as changing the screen brightness, but the key (fn+F5) does not turn the touchpad back on. I have not yet tried any of the suggested options, as results have been mixed, but I will. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon May 7 22:01:26 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768431] Re: Request to revert SAUCE patches in the 18.04 SRU and update with upstream version
** 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/1768431
Title:
Request to revert SAUCE patches in the 18.04 SRU and update with
upstream version
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 ==
This SRU was requested by IBM. It contains one SAUCE patch and three
commits from linux.next.
IBM requested that we revert a set of SAUCE patches from 18.04 and
replace them with patches from linux-next. Based on review comments,
there has been minor changes from the original SAUCE patches and the
versions in linux-next.
The first SAUCE patch contains all the changes between the current version
of SAUCE patches for latest cxlflash patches in bionic and the latest
version accepted by the community. This only has the needed changes and
makes it so we don't have to revert and re-apply a high number of patches.
In addition to the SAUCE patch, IBM requested the 3 additional new patches
from the linux-next tree.
== Fixes ==
UBUNTU: SAUCE: (no-up) cxlflash: OCXL diff between v2 and v3
a3feb6ef50de ("scsi: cxlflash: Synchronize reset and remove ops")
9a597cd4c0ce ("scsi: cxlflash: Remove commmands from pending list on timeout)"
d2d354a606d5 ("scsi: cxlflash: Handle spurious interrupts")
== Regression Potential ==
Medium. All the patches are specific to the cxlflash driver, but there
are four of them and one is a SAUCE patch.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Comment: #0 - UMA KRISHNAN - 2018-04-30 14:41:30 ==
---Problem Description---
Request to revert SAUCE patches from 18.04 and apply the patches from
next/master.
Below set of cxlflash patches were submitted to Canonical after they
were sent to the community. Based on review comments, there has been
minor changes from that version. This BZ is to request reverting those
SAUCE patches with the ones that are queued in next/master tree for
4.18.
- SAUCE: cxlflash: Preserve number of interrupts for master contexts
- SAUCE: cxlflash: Avoid clobbering context control register value
- SAUCE: cxlflash: Add argument identifier names
- SAUCE: cxlflash: Introduce OCXL backend
- SAUCE: cxlflash: Hardware AFU for OCXL
- SAUCE: cxlflash: Read host function configuration
- SAUCE: cxlflash: Setup function acTag range
- SAUCE: cxlflash: Read host AFU configuration
- SAUCE: cxlflash: Setup AFU acTag range
- SAUCE: cxlflash: Setup AFU PASID
- SAUCE: cxlflash: Adapter context support for OCXL
- SAUCE: cxlflash: Use IDR to manage adapter contexts
- SAUCE: cxlflash: Support adapter file descriptors for OCXL
- SAUCE: cxlflash: Support adapter context discovery
- SAUCE: cxlflash: Support image reload policy modification
- SAUCE: cxlflash: MMIO map the AFU
- SAUCE: cxlflash: Support starting an adapter context
- SAUCE: cxlflash: Support process specific mappings
- SAUCE: cxlflash: Support AFU state toggling
- SAUCE: cxlflash: Support reading adapter VPD data
- SAUCE: cxlflash: Setup function OCXL link
- SAUCE: cxlflash: Setup OCXL transaction layer
- SAUCE: cxlflash: Support process element lifecycle
- SAUCE: cxlflash: Support AFU interrupt management
- SAUCE: cxlflash: Support AFU interrupt mapping and registration
- SAUCE: cxlflash: Support starting user contexts
- SAUCE: cxlflash: Support adapter context polling
- SAUCE: cxlflash: Support adapter context reading
- SAUCE: cxlflash: Support adapter context mmap and release
- SAUCE: cxlflash: Support file descriptor mapping
- SAUCE: cxlflash: Introduce object handle fop
- SAUCE: cxlflash: Setup LISNs for user contexts
- SAUCE: cxlflash: Setup LISNs for master contexts
- SAUCE: cxlflash: Update synchronous interrupt status bits
- SAUCE: cxlflash: Introduce OCXL context state machine
- SAUCE: cxlflash: Register for translation errors
- SAUCE: cxlflash: Support AFU reset
- SAUCE: cxlflash: Enable OCXL operations
Also, there are 3 additional patches added to end of this series that we
would like to request being pulled into the SRU stream. These 3 patches address
bug fixes.
The commit ids for the patches queued in next/master tree are,
768999d6b1eadc6a13b1fba1886f1708f433d82b scsi: cxlflash: Preserve number of
interrupts for master contexts
6c2b116dd38e3fbda10c3e3d5ac80ea7442e4f4d scsi: cxlflash: Avoid clobbering
context control register value
fcace1d5e11f518c6f91dd245fa1ac37393b47d3 scsi: cxlflash: Add argument
identifier names
863dbdc0552f8bc100df48bb231089c382b89004 scsi: cxlflash: Introduce OCXL
[Kernel-packages] [Bug 1770231] Re: Expose arm64 CPU topology to userspace
** 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/1770231 Title: Expose arm64 CPU topology to userspace Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Applications, particularly those in the HPC domain (e.g. openmpi), can be optimized for the processor and cache topology. However, the ARM CPU topology isn't correctly exposed to userspace. The kernel's scheduler also uses this information to optimize task placement. [Fix] The ACPI 6.2 specification introduced a Processor Properties Topology Table (PPTT). This is what ARM server vendors are using to expose their topology. The linux kernel needs support for parsing this table, and exposing the parsed topology to userspace. [Test Case] A HiSilicon D06 without the fix. Note that it thinks I'm on a 24-socket system with 4 cores each. I'm not. I'm on a 2 socket system w/ 48 cores each. An HPC app that optimized for this (bogus) topology would therefore suffer a performance penalty. ubuntu@d06-1:~$ lscpu Architecture:aarch64 Byte Order: Little Endian CPU(s): 96 On-line CPU(s) list: 0-95 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 24 NUMA node(s):4 Vendor ID: 0x48 Model: 0 Stepping:0x0 BogoMIPS:200.00 NUMA node0 CPU(s): 0-23 NUMA node1 CPU(s): 24-47 NUMA node2 CPU(s): 48-71 NUMA node3 CPU(s): 72-95 Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics cpuid asimdrdm dcpop With the fix (and this is correct): ubuntu@d06-1:~$ lscpu Architecture:aarch64 Byte Order: Little Endian CPU(s): 96 On-line CPU(s) list: 0-95 Thread(s) per core: 1 Core(s) per socket: 48 Socket(s): 2 NUMA node(s):4 Vendor ID: 0x48 Model: 0 Stepping:0x0 BogoMIPS:200.00 L1d cache: 64K L1i cache: 64K L2 cache:512K L3 cache:32768K NUMA node0 CPU(s): 0-23 NUMA node1 CPU(s): 24-47 NUMA node2 CPU(s): 48-71 NUMA node3 CPU(s): 72-95 Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics cpuid asimdrdm dcpop [Regression Risk] Here's a patch-by patch risk analysis of the changeset: 0001-ACPICA-ACPI-6.2-Additional-PPTT-flags.patch Just adds new #defines. No functional change. 0002-drivers-base-cacheinfo-move-cache_setup_of_node.patch Moves code down in a file. No functional change. (I double-checked that the moved code is the same). 0003-drivers-base-cacheinfo-setup-DT-cache-properties-ear.patch The code this touches is all #ifdef CONFIG_OF, which only applies to the ARM & Power ports of Ubuntu. I've tested on arm64 and regression tested on ppc64el (POWER9). POWER booted fine, and there was no change to lscpu output. 0004-cacheinfo-rename-of_node-to-fw_token.patch Renames a variable, and changes it's type from "struct device_node *" to "void *". No functional change. 0005-arm64-acpi-Create-arch-specific-cpu-to-acpi-id-helpe.patch Adds a new function (but doesn't use it yet). 0006-ACPI-PPTT-Add-Processor-Properties-Topology-Table-pa.patch Adds new code that isn't called yet. 0007-UBUNTU-Config-CONFIG_ACPI_PPTT-y.patch Configures on the new code. 0008-ACPI-Enable-PPTT-support-on-ARM64.patch Kconfig/Makefile bits for the new code. 0009-drivers-base-cacheinfo-Add-support-for-ACPI-based-fi.patch Finally, we call the new code during initialization, so let's go back and look at that code. The first thing it does is to check for the presence of a PPTT table before proceeding, so the regression risk to systems *without* a PPTT table is negligible. The PPTT table was introduced in the ACPI 6.2 specification, which was released in May 2017. Regression risk should therefore be restricted to systems manufactured (or firmware updated) after that time that happened to include a PPTT table. I don't know of anyone other than ARM licensees doing this - but it's possible there are others. And, it's possible that there's a table out there that tickles a bug in the parsing code. Should that be the case, a hotfix would be to use an initrd to override/strip[*] the PPTT from the XSDT table until a suitable fix is put in place. 0010-arm64-Add-support-for-ACPI-based-firmware-tables.patch 0011-arm64-topology-rename-cluster_id.patch 0012-arm64-topology-enable-ACPI-PPTT-based-CPU-topology.patch These patches only touch arm64 code. I explicitly tested on an arm64 server. 0013-ACPI-Add-PPTT-to-injectable-table-list.patch Allows users to override the PPTT table. No change to default
[Kernel-packages] [Bug 1773299] Re: Dell systems crash when disabling Nvidia dGPU
** 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/1773299 Title: Dell systems crash when disabling Nvidia dGPU Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: Some Dell systems crash when disabling Nvidia dGPU with I+N configurations As NV Linux driver doesn't now support RTD3, BIOS removed the code to prevent system crashes as a short-term solution This is for Linux as Nvidia's Windows driver supports RTD3. In this workaround an _OSI string, Linux-Dell-Video, was used in BIOS as a workaround in Linux. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1773299/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773407] Re: linux-crashdump isn't built for arm64
** Changed in: linux-meta (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: linux-meta (Ubuntu Artful) Status: In Progress => Fix Committed ** Changed in: linux-meta (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-meta in Ubuntu. https://bugs.launchpad.net/bugs/1773407 Title: linux-crashdump isn't built for arm64 Status in linux-meta package in Ubuntu: In Progress Status in linux-meta source package in Xenial: Fix Committed Status in linux-meta source package in Artful: Fix Committed Status in linux-meta source package in Bionic: Fix Committed Bug description: [Impact] kdump works fine on arm64 these days, but end users have to manually install the various packages to make it work vs. just installing linux-crashdump like on other architectures. [Test Case] On an arm64 system: sudo apt install linux-crashdump [Fix] Add the necessary debian/control bits to build this package on arm64. [Regression Risk] We're making a package available on arm64 that wasn't previously - if that package is broken for some reason, it won't be a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1773407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773520] Re: After update to 4.13-43 Intel Graphics are Laggy
** Changed in: linux (Ubuntu Artful) Status: In Progress => Fix Committed ** 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/1773520 Title: After update to 4.13-43 Intel Graphics are Laggy Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: == SRU Justification == The bug reporter states that after update to Kernel 4.13-43 the intel graphics seem to really lag - especially noticeable in apps which are using vsync, which, at least on his system, locks to 40fps unlike the previous kernel. See https://askubuntu.com/questions/1039189/today-i-got-an-update-and- graphics-are-not-working-right-on-ubuntu-16-04/1040545#1040545 for some other users with the same issue This regression was introduced by upstream commit dc911f5bd8aa. A revert of this commit fixes this bug. Upstream has already reverted this commit in drm-tip tree and cc'd it to upstream stable. However, the revert has not landed in mainline or stable yet, so it is being sent as a SAUCE patch. The revert is also needed in Bionic. However, the Bionic revert is slightly differant, so it will be SRU'd separately. == Fix == UBUNTU: SAUCE: Revert "drm/i915/edp: Allow alternate fixed mode for eDP if available." == Regression Potential == Low. This revert is to fix a current regression. == 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. After update to Kernel 4.13-43 the intel graphics seem to really lag - especially noticeable in apps which are using vsync, which, at least on my system, locks to 40fps unlike the previous kernel I have installed (4.13-41) which locks at a steady 60fps. See https://askubuntu.com/questions/1039189/today-i-got-an-update-and- graphics-are-not-working-right-on-ubuntu-16-04/1040545#1040545 for some other users with the same issue In short 4.13-41 doesn't have the problem 4.13-43 has the laggy problem --- ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: james 2835 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ac1331a0-15f2-4832-aebc-48e3ad655add InstallationDate: Installed on 2016-05-31 (724 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 04f2:b50d Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Gaming Notebook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-43-generic N/A linux-backports-modules-4.13.0-43-generic N/A linux-firmware 1.157.18 Tags: xenial Uname: Linux 4.13.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker libvirtd lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/16/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.53 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80A9 dmi.board.vendor: HP dmi.board.version: 91.18 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.53:bd09/16/2015:svnHP:pnHPPavilionGamingNotebook:pvrType1ProductConfigId:rvnHP:rn80A9:rvr91.18:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion Gaming Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773520/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772031] Re: kernel backtrace when receiving large UDP packages
** Changed in: linux (Ubuntu Artful)
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/1772031
Title:
kernel backtrace when receiving large UDP packages
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Artful:
Fix Committed
Bug description:
== SRU Justification ==
Artful is missing commit a90bcb86ae70, which was sent
to upstream stable. Since upstream 4.13 is EOL, Artful never got it.
Because Artful does not have this commit when receiving large UDP packages
with a small MTU there are backtraces, examples posted in the bug.
Commit a90bcb86ae70 is in mainline as ov v4.14-rc2 and is only needed in
Artful.
== Fix ==
a90bcb86ae70 ("iov_iter: fix page_copy_sane for compound pages")
== Regression Potential ==
Low. This commit fixes a current regression in Artful. It was also
cc'd to 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.
kernel 4.13.0-41-generic is missing commit a90bcb86ae70:
Author: Petar Penkov
Date: Tue Aug 29 11:20:32 2017 -0700
iov_iter: fix page_copy_sane for compound pages
Issue is that if the data crosses a page boundary inside a compound
page, this check will incorrectly trigger a WARN_ON.
To fix this, compute the order using the head of the compound page and
adjust the offset to be relative to that head.
Fixes: 72e809ed81ed ("iov_iter: sanity checks for copy to/from page
primitives")
Signed-off-by: Petar Penkov
CC: Al Viro
CC: Eric Dumazet
Signed-off-by: Al Viro
Commit 72e809ed81ed is in kernel 4.13.0-41-generic.
As a result, when receiving large UDP packages with a small MTU we get
backtraces like:
[ 361.260969] [ cut here ]
[ 361.260974] WARNING: CPU: 4 PID: 2541 at
/build/linux-hwe-v6kHHF/linux-hwe-4.13.0/lib/iov_iter.c:693
copy_page_to_iter+0x194/0x2d0
[ 361.260975] Modules linked in: cmdlinepart sfc(OE) hwmon_vid crc32_generic
mii rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache 8021q garp mrp
stp llc intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm
i]
[ 361.261002] CPU: 4 PID: 2541 Comm: udp_recv Tainted: G OE
4.13.0-39-generic #44~16.04.1-Ubuntu
[ 361.261003] Hardware name: Dell Inc. PowerEdge R220/05Y15N, BIOS 1.4.0
10/23/2014
[ 361.261004] task: 91630b2bae80 task.stack: bb19c2bfc000
[ 361.261005] RIP: 0010:copy_page_to_iter+0x194/0x2d0
[ 361.261006] RSP: 0018:bb19c2bffc60 EFLAGS: 00010202
[ 361.261007] RAX: 1000 RBX: 00df RCX:
0017c000
[ 361.261008] RDX: 00df RSI: 0f8e RDI:
f666895279c0
[ 361.261009] RBP: bb19c2bffca0 R08: 106d R09:
1024
[ 361.261009] R10: R11: 91630ccc9b00 R12:
91630d27a300
[ 361.261010] R13: bb19c2bffde0 R14: 00df R15:
0175
[ 361.261011] FS: 7fb8e7649700() GS:91631fd0()
knlGS:
[ 361.261012] CS: 0010 DS: ES: CR0: 80050033
[ 361.261013] CR2: 14588da85624 CR3: 00024bad2002 CR4:
001606e0
[ 361.261013] Call Trace:
[ 361.261017] ? proto_init_net+0x40/0x40
[ 361.261019] skb_copy_datagram_iter+0x171/0x270
[ 361.261022] udp_recvmsg+0x108/0x490
[ 361.261024] inet_recvmsg+0x51/0xc0
[ 361.261026] sock_recvmsg+0x43/0x50
[ 361.261028] sock_read_iter+0x90/0xe0
[ 361.261030] new_sync_read+0xe2/0x130
[ 361.261032] __vfs_read+0x29/0x40
[ 361.261033] vfs_read+0x93/0x130
[ 361.261034] SyS_read+0x55/0xc0
[ 361.261037] entry_SYSCALL_64_fastpath+0x24/0xab
[ 361.261038] RIP: 0033:0x7fb8e7160260
[ 361.261039] RSP: 002b:7ffed9dd9e38 EFLAGS: 0246 ORIG_RAX:
[ 361.261040] RAX: ffda RBX: RCX:
7fb8e7160260
[ 361.261041] RDX: ffe3 RSI: 5622ad02f0a0 RDI:
0003
[ 361.261041] RBP: 7ffed9dd9e70 R08: R09:
0011
[ 361.261042] R10: R11: 0246 R12:
5622ace2e800
[ 361.261043] R13: 7ffed9dd9f50 R14: R15:
[ 361.261044] Code: de 4c 89 e7 e8 be fa ff ff 41 83 af a0 12 00 00 01 48 83
c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 8b 4f 6c 48 d3 e0 e9 9d fe ff ff <0f> ff
48 83 c4 18 31 c0 5b 41 5c 41 5d 41 5e 41 5f 5d c3 49 83
[ 361.261064] ---[ end trace c0b23bf37be9874d ]---
This is a request to pull in commit a90bcb86ae70.
# lsb_release -rd
Description: Ubuntu 17.10
Release: 17.10
# uname -a
Linux c6320f
[Kernel-packages] [Bug 1773509] Re: ELANPAD ELAN0612 does not work, patch available
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Artful) Status: In Progress => Fix Committed ** 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/1773509 Title: ELANPAD ELAN0612 does not work, patch available Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: == SRU Justification == Seems there is a new version of the ELANPAD touchpad with identifier ELAN0612 that is being included in newer laptops. The kernel itself doesn't have support for this touchpad yet. However, the patch to get this working is trivial. Since people start being affected by this, this patch is being sent as a SAUCE patch until it lands upstream. The upstream bug at the Kernel project, including the patch is here: https://bugzilla.kernel.org/show_bug.cgi?id=199253 == Fix == UBUNTU: SAUCE: Input: elan_i2c - add ELAN0612 to the ACPI table == Regression Potential == Low. One liner to add a device id. == 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773509/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772991] Re: [Ubuntu 18.04.1] POWER9 - Nvidia Volta - Kernel changes to enable Nvidia driver on bare metal
** 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/1772991 Title: [Ubuntu 18.04.1] POWER9 - Nvidia Volta - Kernel changes to enable Nvidia driver on bare metal Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Bug description: == SRU Justification == 12 kernel patches have been identified as needed to support Nvidia Volta on bare metal. All are accepted upstream in 4.17. Three of those are already in bionic, leaving a total of 9 remaining commits needed in bionic. This pull request is for those other 9 commits. == Regression Potential == All of the commits are specific to powerpc. == Test Case == A test kernel was built with these patches and tested by IBM. == Comment: #0 - Barry B. Arndt - 2018-05-23 13:40:33 == 12 kernel patches have been identified as needed to support Nvidia Volta on bare metal. All are accepted upstream in 4.17. Three of those are already in bionic, leaving a total of 9 remaining commits needed in bionic. Those 9 commits are: 720c84046c26 powerpc/npu-dma.c: Fix crash after __mmu_notifier_register failure 2b74e2a9b39d powerpc/powernv/npu: Fix deadlock in mmio_invalidate() 5ee573e8ef03 powerpc/powernv/mce: Don't silently restart the machine fb5924fddf9e powerpc/mm: Flush cache on memory hot(un)plug 7fd6641de28f powerpc/powernv/memtrace: Let the arch hotunplug code flush cache 28a5933e8d36 powerpc/powernv/npu: Add lock to prevent race in concurrent context init/destroy a1409adac748 powerpc/powernv/npu: Prevent overwriting of pnv_npu2_init_contex() callback parameters d0cf9b561ca9 powerpc/powernv/npu: Do a PID GPU TLB flush when invalidating a large address range 75ecfb49516c powerpc/mce: Fix a bug where mce loops on memory UE. We cherry-picked the commits, and all applied cleanly. The resultant kernel built successfully and loaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1772991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772593] Re: cpum_sf: ensure sample freq is non-zero
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Artful)
Status: In Progress => Fix Committed
** 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/1772593
Title:
cpum_sf: ensure sample freq is non-zero
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Artful:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
A regression was introduced by commit 8c069ff4bd606 in v3.14-rc1. IBM
is requested commit 4bbaf2584b86 in all Ubuntu kernels to resolve this
isue.
Bug Description: cpum_sf: ensure sample freq is non-zero
Symptom: A kernel crash might occur.
Problem: An FP divide exception during the sample rate
initialization for the hardware sampling facility.
Solution: Ensure that the sample frequency of the perf
event attribute is non-zero.
== Fix ==
4bbaf2584b86 ("s390/cpum_sf: ensure sample frequency of perf event attributes
is non-zero")
== Regression Potential ==
Low. Fix is specific to s390.
== 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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1772593/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771480] Re: WARNING: CPU: 28 PID: 34085 at /build/linux-90Gc2C/linux-3.13.0/net/core/dev.c:1433 dev_disable_lro+0x87/0x90()
** Changed in: linux (Ubuntu Trusty) 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/1771480 Title: WARNING: CPU: 28 PID: 34085 at /build/linux- 90Gc2C/linux-3.13.0/net/core/dev.c:1433 dev_disable_lro+0x87/0x90() Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Fix Committed Bug description: [impact] with a specific network configuration, a kernel WARNING is issued. [test case] configure a trusty system with e/n/i like this: auto bond0.2004 iface bond0.2004 inet manual mtu 9100 vlan-raw-device bond0 auto bond0 iface bond0 inet manual mtu 9100 bond-slaves eth1 eth2 bond-mode 802.3ad bond-miimon 100 bond-use-carrier 1 bond-lacp-rate fast bond-updelay 3000 bond-downdelay 1000 bond-ad-select bandwidth bond-xmit-hash-policy layer3+4 post-up sleep 45 auto br-mesh iface br-mesh inet static bridge_ports bond0.2004 address 192.168.210.3/24 auto eth1 iface eth1 inet manual mtu 9100 bond-master bond0 auto eth2 iface eth2 inet manual mtu 9100 bond-master bond0 adjusting the interface names as needed, of course. then reboot, and the kernel WARNING will appear in the dmesg. [regression potential] the kernel patch has the potential to incorrectly set, or incorrectly not set, features on devices. [other info] previous bug description: I have multiple instances of this dev_disable_lro error in kern.log. Also seeing this: systemd-udevd[1452]: timeout: killing 'bridge-network-interface' [2765] <4>May 1 22:56:42 xxx kernel: [ 404.520990] bonding: bond0: Warning: No 802.3ad response from the link partner for any adapters in the bond <4>May 1 22:56:44 xxx kernel: [ 406.926429] bonding: bond0: Warning: No 802.3ad response from the link partner for any adapters in the bond <4>May 1 22:56:45 xxx kernel: [ 407.569020] [ cut here ] <4>May 1 22:56:45 xxx kernel: [ 407.569029] WARNING: CPU: 28 PID: 34085 at /build/linux-90Gc2C/linux-3.13.0/net/core/dev.c:1433 dev_disable_lro+0x87/0x90() <4>May 1 22:56:45 xxx kernel: [ 407.569032] netdevice: bond0.2004 <4>May 1 22:56:45 xxx kernel: [ 407.569032] failed to disable LRO! <4>May 1 22:56:45 xxx kernel: [ 407.569035] Modules linked in: 8021q garp mrp bridge stp llc bonding iptable_filter ip_tables x_tables nf_conntrack_proto_gre nf_conntrack_ipv6 nf_defrag_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack ipmi_devintf mxm_wmi dcdbas x86_pkg_temp_thermal coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd lpc_ich mei_me mei ipmi_si shpchp wmi acpi_power_meter mac_hid xfs libcrc32c raid10 usb_storage raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 igb ixgbe i2c_algo_bit multipath ahci dca ptp libahci pps_core linear megaraid_sas mdio dm_multipath scsi_dh <4>May 1 22:56:45 xxx kernel: [ 407.569112] CPU: 28 PID: 34085 Comm: brctl Not tainted 3.13.0-142-generic #191-Ubuntu <4>May 1 22:56:45 xxx kernel: [ 407.569115] Hardware name: Dell Inc. PowerEdge R730xd/072T6D, BIOS 2.7.1 001/22/2018 <4>May 1 22:56:45 xxx kernel: [ 407.569118] 881fcc753c70 8172e7fc 881fcc753cb8 <4>May 1 22:56:45 xxx kernel: [ 407.569129] 0009 881fcc753ca8 8106afad 883fcc6f8000 <4>May 1 22:56:45 xxx kernel: [ 407.569139] 883fcc696880 883fcc6f8000 881fce82dd40 <4>May 1 22:56:45 xxx kernel: [ 407.569150] Call Trace: <4>May 1 22:56:45 xxx kernel: [ 407.569160] [] dump_stack+0x64/0x82 <4>May 1 22:56:45 xxx kernel: [ 407.569168] [] warn_slowpath_common+0x7d/0xa0 <4>May 1 22:56:45 xxx kernel: [ 407.569175] [] warn_slowpath_fmt+0x4c/0x50 <4>May 1 22:56:45 xxx kernel: [ 407.569183] [] dev_disable_lro+0x87/0x90 <4>May 1 22:56:45 xxx kernel: [ 407.569195] [] br_add_if+0x1f3/0x430 [bridge] <4>May 1 22:56:45 xxx kernel: [ 407.569205] [] add_del_if+0x5d/0x90 [bridge] <4>May 1 22:56:45 xxx kernel: [ 407.569215] [] br_dev_ioctl+0x5b/0x90 [bridge] <4>May 1 22:56:45 xxx kernel: [ 407.569223] [] dev_ifsioc+0x313/0x360 <4>May 1 22:56:45 xxx kernel: [ 407.569230] [] ? dev_get_by_name_rcu+0x69/0x90 <4>May 1 22:56:45 xxx kernel: [ 407.569237] [] dev_ioctl+0xe9/0x590 <4>May 1 22:56:45 xxx kernel: [ 407.569245] [] sock_do_ioctl+0x45/0x50 <4>May 1 22:56:45 xxx kernel: [ 407.569252] [] sock_ioctl+0x1f0/0x2c0 <4>May 1 22:56:45 xxx kernel: [ 407.569260] [] do_vfs_ioctl+0x2e0/0x4c0 <4>May 1 22:56:45 xxx kernel: [ 407.569267] [] ? fput+0xe/0x10 <4>May 1 22:56:45 xxx kernel: [ 407.569273] [] SyS_ioctl+0x81/0xa0 <4>May 1 22:56:45 xxx kernel: [ 407.569283] [] system_call_fastpath+0x2f/0x34 <4>May 1 22:56:45 xxx kernel: [
[Kernel-packages] [Bug 1768670] Re: hns3 driver updates
** 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/1768670 Title: hns3 driver updates Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Bug description: [Impact] The hns3 driver is still under active development upstream, with a number of bug fixes and features that are not yet available in Ubuntu. [Test Case] Smoke testing on a HiSilicon D06 board. [Regression Risk] The code changes here are restricted to the hns3 driver. hns3 drive the NICs in the Hi1620 SoC, which itself is still pre-release. Regressions would therefore be restricted to users doing early evaluation or enablement with the D06 board, upon which these changes were directly tested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768670/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773233] Re: Bionic update: upstream stable patchset 2018-05-24
** 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/1773233 Title: Bionic update: upstream stable patchset 2018-05-24 Status in linux package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2018-05-24 (ported from v4.14.36 and v4.16.4) from git://git.kernel.org/ HID: i2c-hid: fix inverted return value from i2c_hid_command() device-dax: allow MAP_SYNC to succeed libnvdimm, dimm: handle EACCES failures from label reads drm/i915: Fix hibernation with ACPI S0 target state s390: add support for IBM z14 Model ZR1 HID: i2c-hid: Fix resume issue on Raydium touchscreen device pwm: mediatek: Improve precision in rate calculation pwm: mediatek: Fix up PWM4 and PWM5 malfunction on MT7623 clk: tegra: Mark HCLK, SCLK and EMC as critical trace_uprobe: Use %lx to display offset drm/amd/display: HDMI has no sound after Panel power off/on mmc: core: Prevent bus reference leak in mmc_blk_init() drivers/infiniband/ulp/srpt/ib_srpt.c: fix build with gcc-4.4.4 drivers/infiniband/core/verbs.c: fix build with gcc-4.4.4 IB/srpt: Fix an out-of-bounds stack access in srpt_zerolength_write() xprtrdma: Fix corner cases when handling device removal xprtrdma: Fix latency regression on NUMA NFS/RDMA clients RDMA/core: Avoid that ib_drain_qp() triggers an out-of-bounds stack access ext4: force revalidation of directory pointer after seekdir(2) ext4: fix offset overflow on 32-bit archs in ext4_iomap_begin() ceph: always update atime/mtime/ctime for new inode powerpc/64s: Fix pkey support in dt_cpu_ftrs, add CPU_FTR_PKEY bit acpi, nfit: rework NVDIMM leaf method detection media: rc: oops in ir_timer_keyup after device unplug mm: hwpoison: disable memory error handling on 1GB hugepage Bluetooth: hci_bcm: Add irq_polarity module option writeback: safer lock nesting media: staging: lirc_zilog: incorrect reference counting Revert "media: lirc_zilog: driver only sends LIRCCODE" mm/filemap.c: fix NULL pointer in page_cache_tree_insert() autofs: mount point create should honour passed in mode Don't leak MNT_INTERNAL away from internal mounts rpc_pipefs: fix double-dput() orangefs_kill_sb(): deal with allocation failures hypfs_kill_super(): deal with failed allocations jffs2_kill_sb(): deal with failed allocations drm/i915: Correctly handle limited range YCbCr data on VLV/CHV mmc: sdhci-pci: Only do AMD tuning for HS200 fanotify: fix logic of events on child udf: Fix leak of UTF-16 surrogates into encoded strings powerpc/lib: Fix off-by-one in alternate feature patching powerpc/eeh: Fix enabling bridge MMIO windows MIPS: memset.S: Fix clobber of v1 in last_fixup MIPS: memset.S: Fix return of __clear_user from Lpartial_fixup MIPS: memset.S: EVA & fault support for small_memset MIPS: uaccess: Add micromips clobbers to bzero invocation HID: wacom: bluetooth: send exit report for recent Bluetooth devices HID: hidraw: Fix crash on HIDIOCGFEATURE with a destroyed device HID: input: fix battery level reporting on BT mice random: add new ioctl RNDRESEEDCRNG random: crng_reseed() should lock the crng instance that it is modifying random: use a different mixing algorithm for add_device_randomness() random: fix crng_ready() test ALSA: hda - New VIA controller suppor no-snoop path ALSA: rawmidi: Fix missing input substream checks in compat ioctls ALSA: line6: Use correct endpoint type for midi output drm/radeon: Fix PCIe lane width calculation drm/radeon: add PX quirk for Asus K73TK drm/rockchip: Clear all interrupts before requesting the IRQ drm/amdgpu/si: implement get/set pcie_lanes asic callback drm/amdgpu: Fix PCIe lane width calculation drm/amdgpu/sdma: fix mask in emit_pipeline_sync drm/amdgpu: Fix always_valid bos multiple LRU insertions. drm/amdgpu: Add an ATPX quirk for hybrid laptop ALSA: pcm: Fix endless loop for XRUN recovery in OSS emulation ALSA: pcm: Fix mutex unbalance in OSS emulation ioctls ALSA: pcm: Return -EBUSY for OSS ioctls changing busy streams ALSA: pcm: Avoid potential races between OSS ioctls and read/write ALSA: pcm: Use ERESTARTSYS instead of EINTR in OSS emulation watchdog: f71808e_wdt: Fix WD_EN register read dt-bindings: clock: mediatek: add binding for
[Kernel-packages] [Bug 1774063] Re: Bionic update: upstream stable patchset 2018-05-29
** 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/1774063 Title: Bionic update: upstream stable patchset 2018-05-29 Status in linux package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2018-05-29 (ported from v4.14.37 and v4.16.5) from git://git.kernel.org/ mm,vmscan: Allow preallocating memory for register_shrinker(). btrfs: Fix race condition between delayed refs and blockgroup removal mac80211_hwsim: fix use-after-free bug in hwsim_exit_net Revert "KVM: X86: Fix SMRAM accessing even if VM is shutdown" RDMA/mlx5: Fix NULL dereference while accessing XRC_TGT QPs perf: Return proper values for user stack errors perf: Fix sample_max_stack maximum check netfilter: x_tables: limit allocation requests for blob rule heads netfilter: compat: reject huge allocation requests netfilter: compat: prepare xt_compat_init_offsets to return errors netfilter: x_tables: add counters allocation wrapper netfilter: x_tables: cap allocations at 512 mbyte alarmtimer: Init nanosleep alarm timer on stack RDMA/core: Reduce poll batch for direct cq polling irqchip/gic-v3: Change pr_debug message to pr_devel cpumask: Make for_each_cpu_wrap() available on UP as well irqchip/gic-v3: Ignore disabled ITS nodes perf test: Fix test trace+probe_libc_inet_pton.sh for s390x powerpc/powernv: IMC fix out of bounds memory access at shutdown locking/qspinlock: Ensure node->count is updated before initialising node x86/platform/UV: Fix GAM Range Table entries less than 1GB powerpc/mm/hash64: Zero PGD pages on allocation vfs/proc/kcore, x86/mm/kcore: Fix SMAP fault when dumping vsyscall user page PM / wakeirq: Fix unbalanced IRQ enable for wakeirq ACPI / EC: Restore polling during noirq suspend/resume phases bpf: fix rlimit in reuseport net selftest net: stmmac: discard disabled flags in interrupt status register SUNRPC: Don't call __UDPX_INC_STATS() from a preemptible context tools/libbpf: handle issues with bpf ELF objects containing .eh_frames net: Extra '_get' in declaration of arch_get_platform_mac_address svcrdma: Fix Read chunk round-up rxrpc: Don't put crypto buffers on the stack selftests/ftrace: Add some missing glob checks cpufreq: intel_pstate: Enable HWP during system resume on CPU0 bcache: return attach error when no cache set exist bcache: fix for data collapse after re-attaching an attached device bcache: fix for allocator and register thread race bcache: properly set task state in bch_writeback_thread() cifs: silence compiler warnings showing up with gcc-8.0.0 PM / domains: Fix up domain-idle-states OF parsing proc: fix /proc/*/map_files lookup arm64: spinlock: Fix theoretical trylock() A-B-A with LSE atomics RDS: IB: Fix null pointer issue bpf: sockmap, fix leaking maps with attached but not detached progs xen/grant-table: Use put_page instead of free_page xen-netfront: Fix race between device setup and open perf evsel: Fix period/freq terms setup MIPS: Generic: Support GIC in EIC mode perf record: Fix period option handling MIPS: TXx9: use IS_BUILTIN() for CONFIG_LEDS_CLASS ACPI / scan: Use acpi_bus_get_status() to initialize ACPI_TYPE_DEVICE devs ACPI / bus: Do not call _STA on battery devices with unmet dependencies ACPI: processor_perflib: Do not send _PPC change notification if not ready firmware: dmi_scan: Fix handling of empty DMI strings x86/dumpstack: Avoid uninitlized variable x86/power: Fix swsusp_arch_resume prototype netfilter: ipv6: nf_defrag: Kill frag queue on RFC2460 failure s390/eadm: fix CONFIG_BLOCK include dependency drm/nouveau/pmu/fuc: don't use movw directly anymore IB/core: Map iWarp AH type to undefined in rdma_ah_find_type IB/ipoib: Fix for potential no-carrier state IB/hfi1: Fix for potential refcount leak in hfi1_open_file() IB/hfi1: Re-order IRQ cleanup to address driver cleanup race blk-mq: fix discard merge with scheduler attached openvswitch: Remove padding from packet before L3+ conntrack processing mm/fadvise: discard partial page if endbyte is also EOF mm: pin address_space before dereferencing it while isolating an LRU page mm: thp: use down_read_trylock() in khugepaged to avoid long block sparc64: update pmdp_invalidate()
[Kernel-packages] [Bug 1775483] Re: Bionic update: upstream stable patchset 2018-06-06
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1775483
Title:
Bionic update: upstream stable patchset 2018-06-06
Status in linux package in Ubuntu:
New
Status in linux source package in Bionic:
In Progress
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
upstream stable patchset 2018-06-06 (ported from v4.14.38 and v4.16.6)
from git://git.kernel.org/
kprobes: Fix random address output of blacklist file
s390/cpum_cf: rename IBM z13/z14 counter names
hwmon: (k10temp) Add support for AMD Ryzen w/ Vega graphics
hwmon: (k10temp) Add temperature offset for Ryzen 2700X
VSOCK: make af_vsock.ko removable again
virtio-net: add missing virtqueue kick when flushing packets
bnxt_en: Fix memory fault in bnxt_ethtool_init()
s390/qeth: handle failure on workqueue creation
s390/qeth: avoid control IO completion stalls
s390/qeth: fix error handling in adapter command callbacks
l2tp: fix {pppol2tp, l2tp_dfs}_seq_stop() in case of seq_file overflow
l2tp: hold reference on tunnels printed in l2tp/tunnels debugfs file
l2tp: hold reference on tunnels printed in pppol2tp proc file
l2tp: hold reference on tunnels in netlink dumps
vmxnet3: fix incorrect dereference when rxvlan is disabled
net: stmmac: Disable ACS Feature for GMAC >= 4
net: mvpp2: Fix DMA address mask size
docs: ip-sysctl.txt: fix name of some ipv6 variables
ACPI / video: Only default only_lcd to true on Win8-ready _desktops_
s390/uprobes: implement arch_uretprobe_is_alive()
s390/dasd: fix IO error for newly defined devices
s390/cio: update chpid descriptor after resource accessibility event
tracing: Fix missing tab for hwlat_detector print format
block/swim: Fix IO error at end of medium
block/swim: Fix array bounds check
block/swim: Select appropriate drive on device open
block/swim: Rename macros to avoid inconsistent inverted logic
block/swim: Remove extra put_disk() call from error path
block/swim: Don't log an error message for an invalid ioctl
block/swim: Check drive type
m68k/mac: Don't remap SWIM MMIO region
cdrom: information leak in cdrom_ioctl_media_changed()
scsi: mptsas: Disable WRITE SAME
commoncap: Handle memory allocation failure.
microblaze: Setup dependencies for ASM optimized lib functions
s390: correct module section names for expoline code revert
KVM: s390: force bp isolation for VSIE
virtio_net: fix adding vids on big-endian
virtio_net: split out ctrl buffer
net: ethernet: ti: cpsw: fix tx vlan priority mapping
llc: fix NULL pointer deref for SOCK_ZAPPED
llc: hold llc_sap before release_sock()
net: sched: ife: check on metadata length
net: sched: ife: handle malformed tlv length
tcp: clear tp->packets_out when purging write queue
net: sched: ife: signal not finding metaid
strparser: Fix incorrect strp->need_bytes value.
amd-xgbe: Only use the SFP supported transceiver signals
strparser: Do not call mod_delayed_work with a timeout of LONG_MAX
amd-xgbe: Improve KR auto-negotiation and training
sctp: do not check port in sctp_inet6_cmp_addr
amd-xgbe: Add pre/post auto-negotiation phy hooks
vlan: Fix reading memory beyond skb->tail in skb_vlan_tagged_multi
pppoe: check sockaddr length in pppoe_connect()
tipc: add policy for TIPC_NLA_NET_ADDR
packet: fix bitfield update race
team: fix netconsole setup over team
net/smc: fix shutdown in state SMC_LISTEN
team: avoid adding twice the same option to the event list
net: fix deadlock while clearing neighbor proxy table
tcp: md5: reject TCP_MD5SIG or TCP_MD5SIG_EXT on established sockets
net: af_packet: fix race in PACKET_{R|T}X_RING
tcp: don't read out-of-bounds opsize
llc: delete timers synchronously in llc_sk_free()
net: validate attribute sizes in neigh_dump_table()
l2tp: check sockaddr length in pppol2tp_connect()
KEYS: DNS: limit the length of option strings
ipv6: sr: fix NULL pointer dereference in seg6_do_srh_encap()- v4 pkts
ipv6: add RTA_TABLE and RTA_PREFSRC to rtm_ipv6_policy
bonding: do not set slave_dev npinfo before slave_enable_netpoll in
bond_enslave
Revert "ath10k: send (re)assoc peer command when NSS changed"
tpm: add retry logic
tpm: tpm-interface: fix tpm_transmit/_cmd kdoc
tpm: cmd_ready command can be issued
[Kernel-packages] [Bug 1762554] Re: [Hyper-V] IB/mlx5: Respect new UMR capabilities
@Marcelo, I have a reply from Madhuri: Created By: Madhuri Kaniganti (portal) (07/06/2018 11:40 AM) Just these two fixes needed: IB/mlx5: Respect new UMR capabilities https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20180409=c8d75a980fab886a9c716567e6b47cc414ad84ee IB/mlx5: Enable ECN capable bits for UD RoCE v2 QPs https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/infiniband/hw/mlx5?id=ea8af0d2f2b5b16da4553205ddaf225e0a057e03 -- 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/1762554 Title: [Hyper-V] IB/mlx5: Respect new UMR capabilities Status in linux-azure package in Ubuntu: Confirmed Status in linux-azure source package in Bionic: Confirmed Bug description: In some firmware configuration, UMR usage from Virtual Functions is restricted. This information is published to the driver using new capability bits. Avoid using UMRs in these cases and use the Firmware slow-path flow to create mkeys and populate them with Virtual to Physical address translation. Older drivers that do not have this patch, will end up using memory keys that aren't populated with Virtual to Physical address translation that is done part of the UMR work. https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?h=next-20180409=c8d75a980fab886a9c716567e6b47cc414ad84ee and pull this patch as well IB/mlx5: Enable ECN capable bits for UD RoCE v2 QPs https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/infiniband/hw/mlx5?id=ea8af0d2f2b5b16da4553205ddaf225e0a057e03 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1762554/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772991] Re: [Ubuntu 18.04.1] POWER9 - Nvidia Volta - Kernel changes to enable Nvidia driver on bare metal
These patches are now applied to the Bionic master-next repo. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772991 Title: [Ubuntu 18.04.1] POWER9 - Nvidia Volta - Kernel changes to enable Nvidia driver on bare metal Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: == SRU Justification == 12 kernel patches have been identified as needed to support Nvidia Volta on bare metal. All are accepted upstream in 4.17. Three of those are already in bionic, leaving a total of 9 remaining commits needed in bionic. This pull request is for those other 9 commits. == Regression Potential == All of the commits are specific to powerpc. == Test Case == A test kernel was built with these patches and tested by IBM. == Comment: #0 - Barry B. Arndt - 2018-05-23 13:40:33 == 12 kernel patches have been identified as needed to support Nvidia Volta on bare metal. All are accepted upstream in 4.17. Three of those are already in bionic, leaving a total of 9 remaining commits needed in bionic. Those 9 commits are: 720c84046c26 powerpc/npu-dma.c: Fix crash after __mmu_notifier_register failure 2b74e2a9b39d powerpc/powernv/npu: Fix deadlock in mmio_invalidate() 5ee573e8ef03 powerpc/powernv/mce: Don't silently restart the machine fb5924fddf9e powerpc/mm: Flush cache on memory hot(un)plug 7fd6641de28f powerpc/powernv/memtrace: Let the arch hotunplug code flush cache 28a5933e8d36 powerpc/powernv/npu: Add lock to prevent race in concurrent context init/destroy a1409adac748 powerpc/powernv/npu: Prevent overwriting of pnv_npu2_init_contex() callback parameters d0cf9b561ca9 powerpc/powernv/npu: Do a PID GPU TLB flush when invalidating a large address range 75ecfb49516c powerpc/mce: Fix a bug where mce loops on memory UE. We cherry-picked the commits, and all applied cleanly. The resultant kernel built successfully and loaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1772991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766052] Re: Incorrect blacklist of bcm2835_wdt
At least the images that generally get generated are raspi2 ones (so armhf) but since the modification is done in a shared part of the build scripts this is done for all kernels based on the bionic (4.15) tree. Looking at the raspi2 build: wget https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/14930811/+files/linux-modules-4.15.0-1012-raspi2_4.15.0-1012.13_armhf.deb dpkg -x linux-modules-4.15.0-1012-raspi2_4.15.0-1012.13_armhf.deb unpack grep bcm unpack/lib/modprobe.d/blacklist_linux-raspi2_4.15.0-1012-raspi2.conf -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766052 Title: Incorrect blacklist of bcm2835_wdt Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Status in linux source package in Bionic: Fix Committed Bug description: Without bcm2835_wdt loaded, Raspberry Pi systems cannot reboot or shut down. This needs to be removed from the automatic blacklist generated by the kernel build that ends up in /lib/modprobe.d/blacklist_linux_$(uname -r).conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775641] Re: [Comm] IBM JDK 8.0.5.16 integration into Ubuntu
** Package changed: linux (Ubuntu) => ibm-java71 (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/1775641 Title: [Comm] IBM JDK 8.0.5.16 integration into Ubuntu Status in ibm-java71 package in Ubuntu: New Bug description: foreman@cit7r02:~/sandbox/binary$ ftp archive.admin.canonical.com Connected to archive.admin.canonical.com. 220 youngberry.canonical.com FTP server (Poppy Upload Server) ready. Name (archive.admin.canonical.com:foreman): anonymous 331 Password required Password: 230 Login Successful. Remote system type is UNIX. Using binary mode to transfer files. ftp> bin 200 Type set to Binary. ftp> prompt off Interactive mode off. ftp> put 80sr5fp16_20180524_01_ocdc.tar.gz local: 80sr5fp16_20180524_01_ocdc.tar.gz remote: 80sr5fp16_20180524_01_ocdc.tar.gz 200 PORT command successful. 150 Opening Binary connection for /80sr5fp16_20180524_01_ocdc.tar.gz 226 Transfer successful. 651496332 bytes sent in 377.03 secs (1687.5 kB/s) ftp> quit 221 Goodbye. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibm-java71/+bug/1775641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775641] [NEW] [Comm] IBM JDK 8.0.5.16 integration into Ubuntu
Public bug reported: foreman@cit7r02:~/sandbox/binary$ ftp archive.admin.canonical.com Connected to archive.admin.canonical.com. 220 youngberry.canonical.com FTP server (Poppy Upload Server) ready. Name (archive.admin.canonical.com:foreman): anonymous 331 Password required Password: 230 Login Successful. Remote system type is UNIX. Using binary mode to transfer files. ftp> bin 200 Type set to Binary. ftp> prompt off Interactive mode off. ftp> put 80sr5fp16_20180524_01_ocdc.tar.gz local: 80sr5fp16_20180524_01_ocdc.tar.gz remote: 80sr5fp16_20180524_01_ocdc.tar.gz 200 PORT command successful. 150 Opening Binary connection for /80sr5fp16_20180524_01_ocdc.tar.gz 226 Transfer successful. 651496332 bytes sent in 377.03 secs (1687.5 kB/s) ftp> quit 221 Goodbye. ** Affects: ibm-java71 (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-168695 severity-high targetmilestone-inin--- ** Tags added: architecture-s39064 bugnameltc-168695 severity-high targetmilestone-inin--- ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775641 Title: [Comm] IBM JDK 8.0.5.16 integration into Ubuntu Status in ibm-java71 package in Ubuntu: New Bug description: foreman@cit7r02:~/sandbox/binary$ ftp archive.admin.canonical.com Connected to archive.admin.canonical.com. 220 youngberry.canonical.com FTP server (Poppy Upload Server) ready. Name (archive.admin.canonical.com:foreman): anonymous 331 Password required Password: 230 Login Successful. Remote system type is UNIX. Using binary mode to transfer files. ftp> bin 200 Type set to Binary. ftp> prompt off Interactive mode off. ftp> put 80sr5fp16_20180524_01_ocdc.tar.gz local: 80sr5fp16_20180524_01_ocdc.tar.gz remote: 80sr5fp16_20180524_01_ocdc.tar.gz 200 PORT command successful. 150 Opening Binary connection for /80sr5fp16_20180524_01_ocdc.tar.gz 226 Transfer successful. 651496332 bytes sent in 377.03 secs (1687.5 kB/s) ftp> quit 221 Goodbye. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibm-java71/+bug/1775641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775641] [NEW] [Comm] IBM JDK 8.0.5.16 integration into Ubuntu
You have been subscribed to a public bug: foreman@cit7r02:~/sandbox/binary$ ftp archive.admin.canonical.com Connected to archive.admin.canonical.com. 220 youngberry.canonical.com FTP server (Poppy Upload Server) ready. Name (archive.admin.canonical.com:foreman): anonymous 331 Password required Password: 230 Login Successful. Remote system type is UNIX. Using binary mode to transfer files. ftp> bin 200 Type set to Binary. ftp> prompt off Interactive mode off. ftp> put 80sr5fp16_20180524_01_ocdc.tar.gz local: 80sr5fp16_20180524_01_ocdc.tar.gz remote: 80sr5fp16_20180524_01_ocdc.tar.gz 200 PORT command successful. 150 Opening Binary connection for /80sr5fp16_20180524_01_ocdc.tar.gz 226 Transfer successful. 651496332 bytes sent in 377.03 secs (1687.5 kB/s) ftp> quit 221 Goodbye. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-168695 severity-high targetmilestone-inin--- -- [Comm] IBM JDK 8.0.5.16 integration into Ubuntu https://bugs.launchpad.net/bugs/1775641 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759723] Comment bridged from LTC Bugzilla
--- Comment From lagar...@br.ibm.com 2018-06-07 10:38 EDT--- Hello Frank, Just to reinforce what Ziviani told in some comments before, the issue being discussed here, even though affecting CPU hot plug on Power, is not specifically related to Power. The issue we are seeing with CPU hot plug is just a side effect of a more serious bug in blk_mq. The blk_mq problem that the patches pointed in this issue fix is a general blk_mq issue affecting all platforms that use this infrastructure. My understanding is that there has been lots of bug fixing in this area upstream lately. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759723 Title: ISST-LTE:KVM:Ubuntu18.04:BostonLC:boslcp3:boslcp3g3:Guest conosle hangs after hotplug CPU add operation. Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: Problem Description: === Performed HOTPLUG cpu attach operation for the guest and guest console becomes unresponsive. Steps to re-create: == 1. updated boslcp3 host BMC :116 & PNOR: 20180302 levels 2. Installed Ubuntu1804 on boslcp3 host & guests with trap issue fixes root@boslcp3:/home# uname -a Linux boslcp3 4.15.0-12-generic #13+leo20180320 SMP Tue Mar 20 13:10:42 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3:/home# uname -r 4.15.0-12-generic root@boslcp3g3:/kte/tools/setup.d# uname -a Linux boslcp3g3 4.15.0-12-generic #13+leo20180320 SMP Tue Mar 20 13:10:42 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3g3:/kte/tools/setup.d# uname -r 4.15.0-12-generic 3. Started HTX & stress-ng for on guest for 10-15 min 4. Cleaned up the tests to perform hot-plug and ensure enough memory and cpu was there (killed all Process using kill) 5. Performed cpu hot-plug and guest went into hung state Before Hotplug: root@boslcp3:~# virsh dumpxml boslcp3g3 | grep vcpu 64 root@boslcp3:~# 6. After this operation, guest becomes unrepsonsive as below root@boslcp3g3:~# [ 3626.140773] INFO: task jbd2/vda2-8:584 blocked for more than 120 seconds. [ 3626.146375] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.146457] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.146624] INFO: task systemd-journal:665 blocked for more than 120 seconds. [ 3626.146699] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.146768] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.146939] INFO: task rs:main Q:Reg:1995 blocked for more than 120 seconds. [ 3626.147016] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.147088] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.147285] INFO: task kworker/u128:2:57691 blocked for more than 120 seconds. [ 3626.147361] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.147434] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.147622] INFO: task smbd:1449 blocked for more than 120 seconds. [ 3626.147686] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.147760] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.147875] INFO: task smbd:1452 blocked for more than 120 seconds. [ 3626.147937] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.148010] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.148110] INFO: task smbd:1454 blocked for more than 120 seconds. [ 3626.148173] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.148245] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.148344] INFO: task cron:1461 blocked for more than 120 seconds. [ 3626.148406] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.148488] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. root@boslcp3g3:~# root@boslcp3g3:~# ps -ef | grep stress-ng [ 3746.978098] INFO: task jbd2/vda2-8:584 blocked for more than 120 seconds. [ 3746.978221] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3746.978301] "echo
[Kernel-packages] [Bug 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices
Not sure if this is the same problem. Everything was working perfectly until the massive update that came out last night. Now cannot find internal Atheros BT adapter in Blueman-applet. It appears to allow me to enable BT. Lights on but no one home. Linux firmware looks borked. user@UX32VD:~$ rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no 2: asus-wlan: Wireless LAN Soft blocked: no Hard blocked: no 3: asus-bluetooth: Bluetooth Soft blocked: no Hard blocked: no user@UX32VD:~$ dmesg | grep Blue [2.999406] Bluetooth: Core ver 2.21 [2.999422] Bluetooth: HCI device and connection manager initialized [2.999425] Bluetooth: HCI socket layer initialized [2.999428] Bluetooth: L2CAP socket layer initialized [2.999434] Bluetooth: SCO socket layer initialized [3.020951] Bluetooth: hci0: don't support firmware rome 0x1102 [3.028458] Bluetooth: hci0: don't support firmware rome 0x1102 [4.600699] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [4.600704] Bluetooth: BNEP filters: protocol multicast [4.600709] Bluetooth: BNEP socket layer initialized user@UX32VD:~$ lspci -knn | grep Net -A2; lsusb 03:00.0 Network controller [0280]: Qualcomm Atheros AR9462 Wireless Network Adapter [168c:0034] (rev 01) Subsystem: Bigfoot Networks, Inc. Killer Wireless-N 1202 Half-size Mini PCIe Card [1a56:2003] Kernel driver in use: ath9k Kernel modules: ath9k Bus 002 Device 004: ID 0cf3:3004 Atheros Communications, Inc. AR3012 Bluetooth 4.0 Bus 002 Device 003: ID 04f2:b330 Chicony Electronics Co., Ltd Asus 720p CMOS webcam Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0bda:0139 Realtek Semiconductor Corp. RTS5139 Card Reader Controller Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1745828 Title: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: It is ON and VISIBLE in the control panel. My iPhone can see two other devices but it can't see the computer, and the computer can't see anything, even if left searching for tens of minutes. The previous answers listed below suggest the following diagnostics Bluetooth not working after update How can I make my bluetooth works on Ubuntu 16.04? Ubuntu 16.04 bluetooth not working (Dell XPS13) Bluetooth (Atheros AR3012) not working on Ubuntu 16.04 Bluetooth not working on Ubuntu 16.04 LTS Bluetooth cannot find any devices Stuck on a bluetooth problem The service seems to be running /home >sudo service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago Docs: man:bluetoothd(8) Main PID: 790 (bluetoothd) Status: "Running" CGroup: /system.slice/bluetooth.service └─790 /usr/lib/bluetooth/bluetoothd Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.87 Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.87 Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for Headset Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.12 Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.12 Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for Headset Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. and not blocked /home >rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no I have edited /etc/bluetooth/main.conf to include AutoEnable=true but I noted that the entire file was commented out. The kernel seems reasonably up to date >uname -a Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I wonder if I
[Kernel-packages] [Bug 1685442] Re: Errors: flip_done timed out during boot-up; slow boot
I also have a Dell Latitude D630 and this problem with Ubuntu LTS 18.04 x64. Adding "video=SVIDEO-1:d" to the kernel line solves it completely. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1685442 Title: Errors: flip_done timed out during boot-up; slow boot Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I had been running Ubuntu 16.04 LTS on many laptop computers (especially Dell D620, D630, E6400) with no problem. I created a Live USB with Ubuntu 16.04.2 LTS and tried it on a Dell D630. It was very slow to boot up (about 90 seconds) as opposed to the 30-45 seconds it usually takes. For a few seconds there were error messages that included the phrase "flip_done timed out". When the Ubuntu desktop appeared, the mouse cursor hung for a while, but then came back to life. I didn't do much testing from there. I did a Live session with the 16.04.2 LTS on a different D630 laptop, and the same problem occureed. I Googled the problem, and found several hits. - On an Arch forum, someone reported the problem on a Dell D630, like mine. It also occured on other laptops: https://bbs.archlinux.org/viewtopic.php?id=218581 The suggestion was that the bug was related to kernel version 4.8.x and the 965GM chipset, which is what the D630 has. So I tried Ubuntu Mate 16.04.2 on a Dell D620 (with a 945GM chipset) and the problem DID NOT occur. --- For a similar boot-up problem, Ubuntu Forum suggested going back to an earlier version of Ubuntu. https://ubuntuforums.org/showthread.php?t=2348892 I tried Ubuntu Mate 16.04.1 (with the 4.4.0-31-generic kernel), and the problem did NOT occur. So I'm solving the problem for myself by using Ubuntu Mate 16.04.1 LTS rather than 16.04.2. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: test 2194 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d InstallationDate: Installed on 2017-07-19 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude D630 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.8.0-36-generic N/A linux-backports-modules-4.8.0-36-generic N/A linux-firmware1.157.8 Tags: xenial Uname: Linux 4.8.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0KU184 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: test 2194 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d InstallationDate: Installed on 2017-07-19 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude D630 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.8.0-36-generic N/A
[Kernel-packages] [Bug 1738259] Re: need to ensure microcode updates are available to all bare-metal installs of Ubuntu
@rlaager, for the VM case, considering that QEMU/KVM only supports a few
watchdog devices, I think it would make sense to ship this i6300esb
driver in linux-image-virtual directly.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1738259
Title:
need to ensure microcode updates are available to all bare-metal
installs of Ubuntu
Status in linux-meta package in Ubuntu:
Triaged
Status in linux-meta-hwe package in Ubuntu:
New
Status in linux-meta-hwe-edge package in Ubuntu:
New
Status in linux-meta-lts-xenial package in Ubuntu:
Fix Released
Status in linux-meta-oem package in Ubuntu:
Fix Released
Status in linux-meta source package in Precise:
New
Status in linux-meta source package in Trusty:
Fix Released
Status in linux-meta source package in Xenial:
Fix Released
Status in linux-meta-hwe source package in Xenial:
Fix Released
Status in linux-meta-hwe-edge source package in Xenial:
Fix Released
Status in linux-meta-lts-xenial source package in Xenial:
Fix Committed
Status in linux-meta-oem source package in Xenial:
Fix Released
Status in linux-meta source package in Zesty:
Invalid
Status in linux-meta source package in Artful:
Fix Released
Status in linux-meta source package in Bionic:
Fix Committed
Bug description:
From time to time, CPU vendors release updates to microcode that can
be loaded into the CPU from the OS. For x86, we have these updates
available in the archive as amd64-microcode and intel-microcode.
Sometimes, these microcode updates have addressed security issues with
the CPU. They almost certainly will again in the future.
We should ensure that all users of Ubuntu on baremetal x86 receive
these security updates, and have them applied to the CPU in early boot
where at all feasible.
Because these are hardware-dependent packages which we don't want to
install except on baremetal (so: not in VMs or containers), the
logical place to pull them into the system is via the kernel, so that
only the kernel baremetal flavors pull them in. This is analogous to
linux-firmware, which is already a dependency of the linux-
image-{lowlatency,generic} metapackages, and whose contents are
applied to the hardware by the kernel similar to microcode.
So, please update the linux-image-{lowlatency,generic} metapackages to
add a dependency on amd64-microcode [amd64], intel-microcode [amd64],
and the corresponding hwe metapackages also.
Please time this change to coincide with the next updates of the
microcode packages in the archive.
I believe we will also need to promote the *-microcode packages to
main from restricted as part of this (again, by analogy with linux-
firmware).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1738259/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
