[Kernel-packages] [Bug 1840066] Re: DELL DA300 adaptor's Ethernet port not working after update
I think the latest TBT firmware isn't in default fwupd repo yet. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840066 Title: DELL DA300 adaptor's Ethernet port not working after update Status in linux package in Ubuntu: Incomplete Bug description: DELL DA300 adapter's Ethernet port stopped working after recent update. Whenever the cable is plugged in to the adapter, network manager would show the cable connecting icon and immediately drop the connection. I am able to get Ethernet connection through the DA300 with another Ethernet-USBc adapter by plugging the cable to the adaptor and use DA300's USBc port though. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-03-26 (142 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IpRoute: default via 131.215.195.254 dev enx00e04c680c21 proto dhcp metric 100 default via 10.6.41.254 dev wlp2s0 proto dhcp metric 600 10.6.40.0/23 dev wlp2s0 proto kernel scope link src 10.6.41.210 metric 600 131.215.195.0/24 dev enx00e04c680c21 proto kernel scope link src 131.215.195.209 metric 100 169.254.0.0/16 dev wlp2s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.14-0ubuntu2 [origin: unknown] PackageArchitecture: amd64 Tags: third-party-packages bionic Uname: Linux 5.2.5-050205-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2019-08-13T09:56:21.009087 nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enx00e04c680c21 ethernet connected /org/freedesktop/NetworkManager/Devices/6 Wired connection 1 483df49a-2e78-38c0-a084-58e621ab7527 /org/freedesktop/NetworkManager/ActiveConnection/6 wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/3 eduroam f7c3132c-f44a-4f36-ba26-88e67487dddb /org/freedesktop/NetworkManager/ActiveConnection/5 enxc8f7509d89c6 ethernet unavailable /org/freedesktop/NetworkManager/Devices/5 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.14 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840066/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840066] Re: DELL DA300 adaptor's Ethernet port not working after update
It should land to the default repo soon. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840066 Title: DELL DA300 adaptor's Ethernet port not working after update Status in linux package in Ubuntu: Incomplete Bug description: DELL DA300 adapter's Ethernet port stopped working after recent update. Whenever the cable is plugged in to the adapter, network manager would show the cable connecting icon and immediately drop the connection. I am able to get Ethernet connection through the DA300 with another Ethernet-USBc adapter by plugging the cable to the adaptor and use DA300's USBc port though. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-03-26 (142 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IpRoute: default via 131.215.195.254 dev enx00e04c680c21 proto dhcp metric 100 default via 10.6.41.254 dev wlp2s0 proto dhcp metric 600 10.6.40.0/23 dev wlp2s0 proto kernel scope link src 10.6.41.210 metric 600 131.215.195.0/24 dev enx00e04c680c21 proto kernel scope link src 131.215.195.209 metric 100 169.254.0.0/16 dev wlp2s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.14-0ubuntu2 [origin: unknown] PackageArchitecture: amd64 Tags: third-party-packages bionic Uname: Linux 5.2.5-050205-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2019-08-13T09:56:21.009087 nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enx00e04c680c21 ethernet connected /org/freedesktop/NetworkManager/Devices/6 Wired connection 1 483df49a-2e78-38c0-a084-58e621ab7527 /org/freedesktop/NetworkManager/ActiveConnection/6 wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/3 eduroam f7c3132c-f44a-4f36-ba26-88e67487dddb /org/freedesktop/NetworkManager/ActiveConnection/5 enxc8f7509d89c6 ethernet unavailable /org/freedesktop/NetworkManager/Devices/5 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.14 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840066/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1840454] Re: kernel 5.2 disallows thermald's direct MSR writes
On Sat, Aug 17, 2019 at 1:05 AM Srinivas Pandruvada < srinivas.pandruv...@linux.intel.com> wrote: > The patch for changing TCC offset can only be in for 5.4 kernel. Then > there will be no MSR access. > Is it https://lkml.org/lkml/2019/7/22/1286? Should it work when system is locked down? > So the option is to take out of mainline kernel patch to avoid this or > avoid workaround option. > Isn't the workaround option no longer applies to TCC offset adjustment? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1840454 Title: kernel 5.2 disallows thermald's direct MSR writes Status in linux package in Ubuntu: Confirmed Status in thermald package in Ubuntu: New Bug description: thermald/kernel are spamming dmesg now because MSR write is disallowed. jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | wc -l 8688 jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | tail Aug 16 14:48:57 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:48:57 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:05 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:05 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:13 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:13 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:21 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:21 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5499 F pulseaudio /dev/snd/controlC1: jak5499 F pulseaudio /dev/snd/controlC0: jak5499 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (520 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: thermald 1.9.0-1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-10-generic root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 RelatedPackageVersions: linux-restricted-modules-5.2.0-10-generic N/A linux-backports-modules-5.2.0-10-generic N/A linux-firmware1.181 Tags: eoan third-party-packages Uname: Linux 5.2.0-10-generic x86_64 UpgradeStatus: Upgraded to eoan on 2018-11-20 (269 days ago) UserGroups: adm cdrom dip fax input kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 04/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET54W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET54W(1.31):bd04/22/2019:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840514] 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 1840514 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840514 Title: amdgpu on RX 460 in 18.04.3 does not change state Status in linux package in Ubuntu: Incomplete Bug description: Upgrading from 18.04 to 18.04.3 on a Mac Pro 5,1, the Polaris 11 AMD card, RX 460 began being very slow to display gdm3; screens would come on black then go back to sleep in a cycle. Logging into Gnome takes anywhere between 60 and 90 seconds. If the screen is allowed to go black from inactivity, it takes a long time to return to usability. From experimenting, setting dpm=0 in the grub boot options makes this particular problem go away at the cost of extremely poor 3D performance. 3D performance was already much weaker than it should have be. I have tried the newest mainline kernel and it there is no difference. I also have an AMD Firepro W5100 which is a Polaris 10 card. It operates perfectly. Even before this particular problem, the W5100 out performed the RX 460 which should not be the case. The RX 460 was tested in a spare Windows 10 computer and works fine. It was also tested in each of the PCIex16 slots of the Mac Pro 5,1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840514/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840514] Re: amdgpu on RX 460 in 18.04.3 does not change state
** 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/1840514 Title: amdgpu on RX 460 in 18.04.3 does not change state Status in linux package in Ubuntu: New Bug description: Upgrading from 18.04 to 18.04.3 on a Mac Pro 5,1, the Polaris 11 AMD card, RX 460 began being very slow to display gdm3; screens would come on black then go back to sleep in a cycle. Logging into Gnome takes anywhere between 60 and 90 seconds. If the screen is allowed to go black from inactivity, it takes a long time to return to usability. From experimenting, setting dpm=0 in the grub boot options makes this particular problem go away at the cost of extremely poor 3D performance. 3D performance was already much weaker than it should have be. I have tried the newest mainline kernel and it there is no difference. I also have an AMD Firepro W5100 which is a Polaris 10 card. It operates perfectly. Even before this particular problem, the W5100 out performed the RX 460 which should not be the case. The RX 460 was tested in a spare Windows 10 computer and works fine. It was also tested in each of the PCIex16 slots of the Mac Pro 5,1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840514/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840514] [NEW] amdgpu on RX 460 in 18.04.3 does not change state
You have been subscribed to a public bug: Upgrading from 18.04 to 18.04.3 on a Mac Pro 5,1, the Polaris 11 AMD card, RX 460 began being very slow to display gdm3; screens would come on black then go back to sleep in a cycle. Logging into Gnome takes anywhere between 60 and 90 seconds. If the screen is allowed to go black from inactivity, it takes a long time to return to usability. >From experimenting, setting dpm=0 in the grub boot options makes this particular problem go away at the cost of extremely poor 3D performance. 3D performance was already much weaker than it should have be. I have tried the newest mainline kernel and it there is no difference. I also have an AMD Firepro W5100 which is a Polaris 10 card. It operates perfectly. Even before this particular problem, the W5100 out performed the RX 460 which should not be the case. The RX 460 was tested in a spare Windows 10 computer and works fine. It was also tested in each of the PCIex16 slots of the Mac Pro 5,1. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- amdgpu on RX 460 in 18.04.3 does not change state https://bugs.launchpad.net/bugs/1840514 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 1840521] [NEW] Disco update: upstream stable patchset 2019-08-16
Public bug reported: 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 2019-08-16 Ported from the following upstream stable releases: v4.19.57, v5.1.16 from git://git.kernel.org/ arm64: Don't unconditionally add -Wno-psabi to KBUILD_CFLAGS Revert "x86/uaccess, ftrace: Fix ftrace_likely_update() vs. SMAP" qmi_wwan: Fix out-of-bounds read fs/proc/array.c: allow reporting eip/esp for all coredumping threads mm/mempolicy.c: fix an incorrect rebind node in mpol_rebind_nodemask fs/binfmt_flat.c: make load_flat_shared_library() work clk: socfpga: stratix10: fix divider entry for the emac clocks mm: soft-offline: return -EBUSY if set_hwpoison_free_buddy_page() fails mm: hugetlb: soft-offline: dissolve_free_huge_page() return zero on !PageHuge dm log writes: make sure super sector log updates are written in order scsi: vmw_pscsi: Fix use-after-free in pvscsi_queue_lck() x86/speculation: Allow guests to use SSBD even if host does not x86/microcode: Fix the microcode load on CPU hotplug for real x86/resctrl: Prevent possible overrun during bitmap operations NFS/flexfiles: Use the correct TCP timeout for flexfiles I/O cpu/speculation: Warn on unsupported mitigations= parameter irqchip/mips-gic: Use the correct local interrupt map registers af_packet: Block execution of tasks waiting for transmit to complete in AF_PACKET bonding: Always enable vlan tx offload ipv4: Use return value of inet_iif() for __raw_v4_lookup in the while loop net/packet: fix memory leak in packet_set_ring() net: remove duplicate fetch in sock_getsockopt net: stmmac: fixed new system time seconds value calculation net: stmmac: set IC bit when transmitting frames with HW timestamp sctp: change to hold sk after auth shkey is created successfully team: Always enable vlan tx offload tipc: change to use register_pernet_device tipc: check msg->req data len in tipc_nl_compat_bearer_disable tun: wake up waitqueues after IFF_UP is set bpf: simplify definition of BPF_FIB_LOOKUP related flags bpf: lpm_trie: check left child of last leftmost node for NULL bpf: fix nested bpf tracepoints with per-cpu data bpf: fix unconnected udp hooks bpf: udp: Avoid calling reuseport's bpf_prog from udp_gro bpf: udp: ipv6: Avoid running reuseport's bpf_prog from __udp6_lib_err arm64: futex: Avoid copying out uninitialised stack in failed cmpxchg() bpf, arm64: use more scalable stadd over ldxr / stxr loop in xadd futex: Update comments and docs about return values of arch futex code RDMA: Directly cast the sockaddr union to sockaddr tipc: pass tunnel dev as NULL to udp_tunnel(6)_xmit_skb arm64: insn: Fix ldadd instruction encoding clk: tegra210: Fix default rates for HDA clocks mm, swap: fix THP swap out mm: fix page cache convergence regression efi/memreserve: deal with memreserve entries in unmapped memory net: aquantia: fix vlans not working over bridged network UBUNTU: upstream stable to v4.19.57, v5.1.16 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Disco) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** 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 following upstream + stable patches should be included in the Ubuntu kernel: - 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 2019-08-16 -
[Kernel-packages] [Bug 1839977] Re: bionic/linux-raspi2: 4.15.0-1044.47 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839976 (pi-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840006 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Saturday, 17. August 2019 00:20 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-raspi2/pi-kernel: bug 1839976 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1839977 Title: bionic/linux-raspi2: 4.15.0-1044.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839976 (pi-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840006 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Saturday, 17. August 2019 00:20 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-raspi2/pi-kernel: bug 1839976 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839977/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811819] Re: please include the kernel module VXLAN
Both of those, B and D, are confirmed to work. -- 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/1811819 Title: please include the kernel module VXLAN Status in linux-kvm package in Ubuntu: Incomplete Status in linux-kvm source package in Xenial: New Status in linux-kvm source package in Bionic: New Status in linux-kvm source package in Disco: New Bug description: The kernel built with this packages does have VXLAN compiled. It would be nice if this could be fixed since VXLAN is used by Flannel and maybe other CNI plugins for Kubernetes. $ grep -i vxlan /boot/config-4.4.0-1039-kvm # CONFIG_VXLAN is not set When running a kubernetes cluster with Flannel with this image: $ kubectl logs kube-flannel-ds-amd64-jfkc8 -n kube-system --kubeconfig=case1-admin.conf I0116 11:35:34.176962 1 main.go:475] Determining IP address of default interface I0116 11:35:34.177231 1 main.go:488] Using interface with name ens3 and address 10.32.192.14 I0116 11:35:34.177259 1 main.go:505] Defaulting external address to interface address (10.32.192.14) I0116 11:35:34.191358 1 kube.go:131] Waiting 10m0s for node controller to sync I0116 11:35:34.273844 1 kube.go:294] Starting kube subnet manager I0116 11:35:35.274075 1 kube.go:138] Node controller sync successful I0116 11:35:35.274106 1 main.go:235] Created subnet manager: Kubernetes Subnet Manager - node-1-case1 I0116 11:35:35.274113 1 main.go:238] Installing signal handlers I0116 11:35:35.274233 1 main.go:353] Found network config - Backend type: vxlan I0116 11:35:35.274292 1 vxlan.go:120] VXLAN config: VNI=1 Port=0 GBP=false DirectRouting=false E0116 11:35:35.275803 1 main.go:280] Error registering network: operation not supported I0116 11:35:35.275860 1 main.go:333] Stopping shutdownHandler... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1811819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840520] [NEW] Bionic update: upstream stable patchset 2019-08-16
Public bug reported: 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 2019-08-16 Ported from the following upstream stable releases: v4.14.139, v4.19.67 from git://git.kernel.org/ iio: adc: max9611: Fix misuse of GENMASK macro crypto: ccp - Fix oops by properly managing allocated structures crypto: ccp - Ignore tag length when decrypting GCM ciphertext usb: usbfs: fix double-free of usb memory upon submiturb error usb: iowarrior: fix deadlock on disconnect sound: fix a memory leak bug mmc: cavium: Set the correct dma max segment size for mmc_host mmc: cavium: Add the missing dma unmap when the dma has finished. loop: set PF_MEMALLOC_NOIO for the worker thread Input: synaptics - enable RMI mode for HP Spectre X360 lkdtm: support llvm-objcopy crypto: ccp - Validate buffer lengths for copy operations crypto: ccp - Add support for valid authsize values less than 16 perf annotate: Fix s390 gap between kernel end and module start perf db-export: Fix thread__exec_comm() perf record: Fix module size on s390 usb: host: xhci-rcar: Fix timeout in xhci_suspend() usb: yurex: Fix use-after-free in yurex_delete can: rcar_canfd: fix possible IRQ storm on high load can: peak_usb: fix potential double kfree_skb() netfilter: nfnetlink: avoid deadlock due to synchronous request_module vfio-ccw: Set pa_nr to 0 if memory allocation fails for pa_iova_pfn netfilter: Fix rpfilter dropping vrf packets by mistake netfilter: nft_hash: fix symhash with modulus one scripts/sphinx-pre-install: fix script for RHEL/CentOS iscsi_ibft: make ISCSI_IBFT dependson ACPI instead of ISCSI_IBFT_FIND mac80211: don't warn about CW params when not using them hwmon: (nct6775) Fix register address and added missed tolerance for nct6106 drm: silence variable 'conn' set but not used cpufreq/pasemi: fix use-after-free in pas_cpufreq_cpu_init() s390/qdio: add sanity checks to the fast-requeue path ALSA: compress: Fix regression on compressed capture streams ALSA: compress: Prevent bypasses of set_params ALSA: compress: Don't allow paritial drain operations on capture streams ALSA: compress: Be more restrictive about when a drain is allowed perf tools: Fix proper buffer size for feature processing perf probe: Avoid calling freeing routine multiple times for same pointer drbd: dynamically allocate shash descriptor ACPI/IORT: Fix off-by-one check in iort_dev_find_its_id() ARM: davinci: fix sleep.S build error on ARMv4 scsi: megaraid_sas: fix panic on loading firmware crashdump scsi: ibmvfc: fix WARN_ON during event pool release scsi: scsi_dh_alua: always use a 2 second delay before retrying RTPG test_firmware: fix a memory leak bug tty/ldsem, locking/rwsem: Add missing ACQUIRE to read_failed sleep loop perf/core: Fix creating kernel counters for PMUs that override event->cpu HID: sony: Fix race condition between rumble and device remove. can: peak_usb: pcan_usb_pro: Fix info-leaks to USB devices can: peak_usb: pcan_usb_fd: Fix info-leaks to USB devices hwmon: (nct7802) Fix wrong detection of in4 presence drm/i915: Fix wrong escape clock divisor init for GLK ALSA: firewire: fix a memory leak bug ALSA: hda - Don't override global PCM hw info flag ALSA: hda - Workaround for crackled sound on AMD controller (1022:1457) mac80211: don't WARN on short WMM parameters from AP SMB3: Fix deadlock in validate negotiate hits reconnect smb3: send CAP_DFS capability during session setup NFSv4: Only pass the delegation to setattr if we're sending a truncate NFSv4: Fix an Oops in nfs4_do_setattr KVM: Fix leak vCPU's VMCS value into other pCPU mwifiex: fix 802.11n/WPA detection iwlwifi: don't unmap as page memory that was mapped as single iwlwifi: mvm: fix an out-of-bound access iwlwifi: mvm: don't send GEO_TX_POWER_LIMIT on version < 41 iwlwifi: mvm: fix version check for GEO_TX_POWER_LIMIT support iio: cros_ec_accel_legacy: Fix incorrect channel setting staging: android: ion: Bail out upon SIGKILL when allocating memory. x86/purgatory: Use CFLAGS_REMOVE rather than reset KBUILD_CFLAGS usb: typec: tcpm: free log buf memory when remove debug file usb: typec: tcpm: remove tcpm dir if no children usb: typec: tcpm: Add NULL check before dereferencing config netfilter: conntrack: always store window size un-scaled drm/amd/display: Wait for backlight programming completion in set backlight level drm/amd/display: use encoder's engine id to find matched free audio device drm/amd/display: Fix dc_create failure handling and 666 color depths drm/amd/display: Only enable audio if speaker allocation exists
[Kernel-packages] [Bug 1839977] Re: bionic/linux-raspi2: 4.15.0-1044.47 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839976 (pi-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840006 packages: main: linux-raspi2 meta: linux-meta-raspi2 - phase: Promote to Proposed - phase-changed: Friday, 16. August 2019 22:40 UTC + phase: Testing + phase-changed: Saturday, 17. August 2019 00:20 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + certification-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress trackers: bionic/linux-raspi2/pi-kernel: bug 1839976 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1839977 Title: bionic/linux-raspi2: 4.15.0-1044.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839976 (pi-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840006 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Saturday, 17. August 2019 00:20 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-raspi2/pi-kernel: bug 1839976 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839977/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840017] Re: xenial/linux-fips: 4.4.0-1018.23 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1840021 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Promote to Proposed phase-changed: Thursday, 15. August 2019 16:38 UTC reason: - promote-to-proposed: Pending -- package copied to Signing signed:retry-needed + promote-to-proposed: Ongoing -- package copied to Signing signed:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840017 Title: xenial/linux-fips: 4.4.0-1018.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: 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-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1840021 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Promote to Proposed phase-changed: Thursday, 15. August 2019 16:38 UTC reason: promote-to-proposed: Ongoing -- package copied to Signing signed:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840261] Re: eoan/linux: 5.2.0-13.14 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1840259 (bionic/linux-hwe-edge) -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Friday, 16. August 2019 19:11 UTC reason: - promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait + promote-to-proposed: Ongoing -- package copied to Proposed signed:building trackers: bionic/linux-hwe-edge: bug 1840259 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840261 Title: eoan/linux: 5.2.0-13.14 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1840259 (bionic/linux-hwe-edge) -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Friday, 16. August 2019 19:11 UTC reason: promote-to-proposed: Ongoing -- package copied to Proposed signed:building trackers: bionic/linux-hwe-edge: bug 1840259 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840261/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1833617] Re: [amdgpu] screen freeze after suspend
Kai-hengthe attached is the latest system Log. in case the previous one did not open thanksLevi On Friday, August 16, 2019, 6:20:43 AM PDT, Kai-Heng Feng wrote: Please test latest mainline kernel again: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc4/ And attach `journalctl -b -1 -k` once the issue happens. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1833617 Title: [amdgpu] screen freeze after suspend Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: It's most likely amdgup driver needs an upgrade. Problem occurs since kernel upgrade to 5.0 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12 Uname: Linux 5.0.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Thu Jun 20 13:46:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev eb) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] InstallationDate: Installed on 2019-06-06 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Inspiron 3180 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-18-generic root=UUID=a16bd163-e82f-4ec1-9c5f-c9bd32e225fa ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833617/+subscriptions ** Attachment added: "=?UTF-8?b?Z25vbWUtc3lzdGVtLWxvZy5kZXNrdG9w?=" https://bugs.launchpad.net/bugs/1833617/+attachment/5282948/+files/%3D%3FUTF-8%3Fb%3FZ25vbWUtc3lzdGVtLWxvZy5kZXNrdG9w%3F%3D -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833617 Title: [amdgpu] screen freeze after suspend Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: It's most likely amdgup driver needs an upgrade. Problem occurs since kernel upgrade to 5.0 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12 Uname: Linux 5.0.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Thu Jun 20 13:46:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev eb) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] InstallationDate: Installed on 2019-06-06 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Inspiron 3180 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-18-generic root=UUID=a16bd163-e82f-4ec1-9c5f-c9bd32e225fa ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0: dmi.product.family: Inspiron
[Kernel-packages] [Bug 1839977] Re: bionic/linux-raspi2: 4.15.0-1044.47 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839976 (pi-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840006 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Promote to Proposed phase-changed: Friday, 16. August 2019 22:40 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: bionic/linux-raspi2/pi-kernel: bug 1839976 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1839977 Title: bionic/linux-raspi2: 4.15.0-1044.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839976 (pi-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840006 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Promote to Proposed phase-changed: Friday, 16. August 2019 22:40 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: bionic/linux-raspi2/pi-kernel: bug 1839976 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839977/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839977] Re: bionic/linux-raspi2: 4.15.0-1044.47 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839976 (pi-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840006 packages: main: linux-raspi2 meta: linux-meta-raspi2 - phase: Ready for Promote to Proposed - phase-changed: Thursday, 15. August 2019 17:41 UTC + phase: Promote to Proposed + phase-changed: Friday, 16. August 2019 22:40 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress trackers: bionic/linux-raspi2/pi-kernel: bug 1839976 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1839977 Title: bionic/linux-raspi2: 4.15.0-1044.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839976 (pi-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840006 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Promote to Proposed phase-changed: Friday, 16. August 2019 22:40 UTC reason: promote-to-proposed: Ongoing -- review in progress trackers: bionic/linux-raspi2/pi-kernel: bug 1839976 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839977/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839977] Re: bionic/linux-raspi2: 4.15.0-1044.47 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1839977 Title: bionic/linux-raspi2: 4.15.0-1044.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839976 (pi-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840006 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Promote to Proposed phase-changed: Friday, 16. August 2019 22:40 UTC reason: promote-to-proposed: Ongoing -- review in progress trackers: bionic/linux-raspi2/pi-kernel: bug 1839976 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839977/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795292] Re: ELAN469D touch pad not working
Success! I am typing from kernel 5.3.0-6 without the ivrs_ioapic edit in grub. That did it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1795292 Title: ELAN469D touch pad not working Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I installed Bionic Beaver and now upgraded to Cosmic Cuttlefish on this Lenovo Ideapad 330S-15ARR laptop. The touch pad doesn't work in either. Some possibly relevant info from dmesg: i2c_hid i2c-ELAN469D:00: i2c-ELAN469D:00 supply vdd not found, using dummy regulator i2c_designware AMDI0010:01: controller timed out ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-7-generic 4.18.0-7.8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xorbit 2086 F pulseaudio /dev/snd/pcmC1D0p: xorbit 2086 F...m pulseaudio /dev/snd/controlC0: xorbit 2086 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 30 23:14:26 2018 InstallationDate: Installed on 2018-09-20 (10 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81FB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic processor.max_cstate=1 rcu_nocbs=0-7 pcie_aspm=off pci=noaer quiet splash vt.handoff=1 elan_i2c.dyndbg=+p RelatedPackageVersions: linux-restricted-modules-4.18.0-7-generic N/A linux-backports-modules-4.18.0-7-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-09-30 (0 days ago) dmi.bios.date: 06/08/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7WCN22WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7WCN22WW:bd06/08/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR: dmi.product.family: ideapad 330S-15ARR dmi.product.name: 81FB dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR dmi.product.version: Lenovo ideapad 330S-15ARR dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-20 (13 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: cosmic Uname: Linux 4.19.0-041900rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to cosmic on 2018-09-30 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1795292/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838601] Re: kernel update 5.0.0-23 breaks scroll mouse in xorg
Mouse touch-wheel scrolls intermittently and very slowly. It is essentially unusable. This occurred after the latest kernel update and the behavior is reproducible on two identical mice. MOdel affected: Microsoft Sculpt Touch Mouse. ~$ xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS GlidePoint id=13 [slave pointer (2)] ⎜ ↳ Microsoft Sculpt Touch Mouse Consumer Control id=16 [slave pointer (2)] ⎜ ↳ Microsoft Sculpt Touch Mouse id=18 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Button id=8[slave keyboard (3)] ↳ Sleep Button id=9[slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=10 [slave keyboard (3)] ↳ Dell WMI hotkeys id=11 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=14 [slave keyboard (3)] ↳ Microsoft Sculpt Touch Mouse Keyboard id=15 [slave keyboard (3)] ↳ Microsoft Sculpt Touch Mouse Consumer Control id=17 [slave keyboard (3)] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838601 Title: kernel update 5.0.0-23 breaks scroll mouse in xorg Status in linux package in Ubuntu: Confirmed Bug description: Just updated 18.04 to kernel 5.0.0-23 and scrolling with mouse wheel does not work or works very slowly. Mouse is Microsoft Wireless Optical Mouse 3000 connected via USB to wireless receiver. Rebooting system into kernel 4.18.0-25 and everything works correctly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE Date: Wed Jul 31 22:53:44 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.18.0-24-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3] InstallationDate: Installed on 2019-04-05 (118 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 2347GBU ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=UUID=c840a596-f648-4a82-98f4-70137859c633 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/19/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G1ET73WW (2.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 2347GBU dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ET73WW(2.09):bd10/19/2012:svnLENOVO:pn2347GBU:pvrThinkPadT430:rvnLENOVO:rn2347GBU:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2347GBU dmi.product.sku: LENOVO_MT_2347 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838601/+subscriptions --
[Kernel-packages] [Bug 1840498] 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/1840498 Title: WARNING: CPU: 4 PID: 0 at net/mac80211/rx.c:4568 ieee80211_rx_napi+0x2e6/0x580 [mac80211] Status in linux package in Ubuntu: Confirmed Bug description: dmesg: [ 4249.706469] [ cut here ] [ 4249.706474] Rate marked as an HT rate but passed status->rate_idx is not an MCS index [0-76]: 127 (0x7f) [ 4249.706596] WARNING: CPU: 4 PID: 0 at net/mac80211/rx.c:4568 ieee80211_rx_napi+0x2e6/0x580 [mac80211] [ 4249.706597] Modules linked in: snd_seq_dummy ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs rfcomm hidp pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm cmac bnep snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio arc4 nls_iso8859_1 mei_hdcp snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core intel_rapl snd_soc_skl_ipc x86_pkg_temp_thermal intel_powerclamp snd_soc_sst_ipc coretemp snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi kvm_intel snd_soc_core kvm snd_compress irqbypass ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep crct10dif_pclmul snd_pcm crc32_pclmul ghash_clmulni_intel uvcvideo videobuf2_vmalloc videobuf2_memops ath9k_htc videobuf2_v4l2 ath9k_common videobuf2_common ath9k_hw videodev ath media snd_seq_midi mac80211 aesni_intel snd_seq_midi_event snd_rawmidi joydev cfg80211 aes_x86_64 btusb crypto_simd btrtl cryptd glue_helper btbcm snd_seq btintel intel_cstate input_leds i915 bluetooth snd_seq_device [ 4249.706657] intel_rapl_perf snd_timer ecdh_generic ecc hp_wmi drm_kms_helper snd serio_raw hid_sensor_accel_3d drm hid_sensor_magn_3d hid_sensor_gyro_3d hid_sensor_incl_3d hid_sensor_rotation spi_pxa2xx_platform hid_sensor_trigger industrialio_triggered_buffer kfifo_buf hid_sensor_iio_common mei_me dw_dmac i2c_algo_bit idma64 intel_xhci_usb_role_switch soundcore dw_dmac_core 8250_dw wmi_bmof mei hid_multitouch virt_dma processor_thermal_device fb_sys_fops intel_wmi_thunderbolt industrialio intel_pch_thermal roles intel_soc_dts_iosf syscopyarea sysfillrect sysimgblt int3403_thermal int340x_thermal_zone soc_button_array intel_vbtn sparse_keymap hp_accel int3400_thermal acpi_thermal_rel hp_wireless lis3lv02d input_polldev acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport sunrpc ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq libcrc32c hid_sensor_custom hid_sensor_hub intel_ishtp_loader intel_ishtp_hid hid_generic psmouse intel_ish_ipc ahci intel_ishtp i2c_i801 sdhci_pci [ 4249.706714] libahci cqhci intel_lpss_pci sdhci i2c_hid intel_lpss wmi hid video pinctrl_sunrisepoint pinctrl_intel [ 4249.706730] CPU: 4 PID: 0 Comm: swapper/4 Tainted: G OE 5.2.0-10-generic #11-Ubuntu [ 4249.706732] Hardware name: HP HP Pavilion x360 Convertible 14-cd0xxx/8486, BIOS F.34 04/29/2019 [ 4249.706785] RIP: 0010:ieee80211_rx_napi+0x2e6/0x580 [mac80211] [ 4249.706792] Code: 42 18 0f 8d 76 cc 04 00 48 8b 42 08 48 8d 0c 49 48 8d 14 88 e9 fb fd ff ff 0f b6 f1 48 c7 c7 c8 4f 11 c1 89 f2 e8 16 de 3d ee <0f> 0b 4c 89 e7 e8 a0 98 c1 ee eb a4 80 f9 0b 0f 86 5e 01 00 00 80 [ 4249.706794] RSP: 0018:b16b01aa0dd8 EFLAGS: 00010286 [ 4249.706798] RAX: RBX: 89061a9b47a0 RCX: 0006 [ 4249.706800] RDX: 0007 RSI: 0086 RDI: 890625d17440 [ 4249.706802] RBP: b16b01aa0e68 R08: 03fb R09: 0004 [ 4249.706804] R10: R11: 0001 R12: 89060ba6ef00 [ 4249.706805] R13: R14: R15: 0292 [ 4249.706808] FS: () GS:890625d0() knlGS: [ 4249.706811] CS: 0010 DS: ES: CR0: 80050033 [ 4249.706813] CR2: 152dba73 CR3: 000316c0a001 CR4: 003606e0 [ 4249.706815] Call Trace: [ 4249.706819] [ 4249.706831] ? ath9k_rx_prepare.isra.0+0x242/0x290 [ath9k_htc] [ 4249.706841] ath9k_rx_tasklet+0x106/0x1c0 [ath9k_htc] [ 4249.706852] tasklet_action_common.isra.0+0x60/0x110 [ 4249.706858] tasklet_action+0x22/0x30 [ 4249.706866] __do_softirq+0xe1/0x2f4 [ 4249.706872] irq_exit+0xb6/0xc0 [ 4249.706878] do_IRQ+0x86/0xe0 [ 4249.706883] common_interrupt+0xf/0xf [ 4249.706885] [ 4249.706893] RIP: 0010:cpuidle_enter_state+0xc5/0x420 [ 4249.706897] Code: ff e8 0f 3c 84 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 3d 03 00 00 31 ff e8 c2 90 8a ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 89 d1 01 00 00 41 c7 44 24 10 00 00 00 00 48 83 c4 18 [ 4249.706899] RSP: 0018:b16b019afe38 EFLAGS: 0246 ORIG_RAX: ffdc [ 4249.706902] RAX: 890625d2b2c0 RBX: b0b57b60 RCX: 001f [
[Kernel-packages] [Bug 1840498] [NEW] WARNING: CPU: 4 PID: 0 at net/mac80211/rx.c:4568 ieee80211_rx_napi+0x2e6/0x580 [mac80211]
Public bug reported: dmesg: [ 4249.706469] [ cut here ] [ 4249.706474] Rate marked as an HT rate but passed status->rate_idx is not an MCS index [0-76]: 127 (0x7f) [ 4249.706596] WARNING: CPU: 4 PID: 0 at net/mac80211/rx.c:4568 ieee80211_rx_napi+0x2e6/0x580 [mac80211] [ 4249.706597] Modules linked in: snd_seq_dummy ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs rfcomm hidp pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm cmac bnep snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio arc4 nls_iso8859_1 mei_hdcp snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core intel_rapl snd_soc_skl_ipc x86_pkg_temp_thermal intel_powerclamp snd_soc_sst_ipc coretemp snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi kvm_intel snd_soc_core kvm snd_compress irqbypass ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep crct10dif_pclmul snd_pcm crc32_pclmul ghash_clmulni_intel uvcvideo videobuf2_vmalloc videobuf2_memops ath9k_htc videobuf2_v4l2 ath9k_common videobuf2_common ath9k_hw videodev ath media snd_seq_midi mac80211 aesni_intel snd_seq_midi_event snd_rawmidi joydev cfg80211 aes_x86_64 btusb crypto_simd btrtl cryptd glue_helper btbcm snd_seq btintel intel_cstate input_leds i915 bluetooth snd_seq_device [ 4249.706657] intel_rapl_perf snd_timer ecdh_generic ecc hp_wmi drm_kms_helper snd serio_raw hid_sensor_accel_3d drm hid_sensor_magn_3d hid_sensor_gyro_3d hid_sensor_incl_3d hid_sensor_rotation spi_pxa2xx_platform hid_sensor_trigger industrialio_triggered_buffer kfifo_buf hid_sensor_iio_common mei_me dw_dmac i2c_algo_bit idma64 intel_xhci_usb_role_switch soundcore dw_dmac_core 8250_dw wmi_bmof mei hid_multitouch virt_dma processor_thermal_device fb_sys_fops intel_wmi_thunderbolt industrialio intel_pch_thermal roles intel_soc_dts_iosf syscopyarea sysfillrect sysimgblt int3403_thermal int340x_thermal_zone soc_button_array intel_vbtn sparse_keymap hp_accel int3400_thermal acpi_thermal_rel hp_wireless lis3lv02d input_polldev acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport sunrpc ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq libcrc32c hid_sensor_custom hid_sensor_hub intel_ishtp_loader intel_ishtp_hid hid_generic psmouse intel_ish_ipc ahci intel_ishtp i2c_i801 sdhci_pci [ 4249.706714] libahci cqhci intel_lpss_pci sdhci i2c_hid intel_lpss wmi hid video pinctrl_sunrisepoint pinctrl_intel [ 4249.706730] CPU: 4 PID: 0 Comm: swapper/4 Tainted: G OE 5.2.0-10-generic #11-Ubuntu [ 4249.706732] Hardware name: HP HP Pavilion x360 Convertible 14-cd0xxx/8486, BIOS F.34 04/29/2019 [ 4249.706785] RIP: 0010:ieee80211_rx_napi+0x2e6/0x580 [mac80211] [ 4249.706792] Code: 42 18 0f 8d 76 cc 04 00 48 8b 42 08 48 8d 0c 49 48 8d 14 88 e9 fb fd ff ff 0f b6 f1 48 c7 c7 c8 4f 11 c1 89 f2 e8 16 de 3d ee <0f> 0b 4c 89 e7 e8 a0 98 c1 ee eb a4 80 f9 0b 0f 86 5e 01 00 00 80 [ 4249.706794] RSP: 0018:b16b01aa0dd8 EFLAGS: 00010286 [ 4249.706798] RAX: RBX: 89061a9b47a0 RCX: 0006 [ 4249.706800] RDX: 0007 RSI: 0086 RDI: 890625d17440 [ 4249.706802] RBP: b16b01aa0e68 R08: 03fb R09: 0004 [ 4249.706804] R10: R11: 0001 R12: 89060ba6ef00 [ 4249.706805] R13: R14: R15: 0292 [ 4249.706808] FS: () GS:890625d0() knlGS: [ 4249.706811] CS: 0010 DS: ES: CR0: 80050033 [ 4249.706813] CR2: 152dba73 CR3: 000316c0a001 CR4: 003606e0 [ 4249.706815] Call Trace: [ 4249.706819] [ 4249.706831] ? ath9k_rx_prepare.isra.0+0x242/0x290 [ath9k_htc] [ 4249.706841] ath9k_rx_tasklet+0x106/0x1c0 [ath9k_htc] [ 4249.706852] tasklet_action_common.isra.0+0x60/0x110 [ 4249.706858] tasklet_action+0x22/0x30 [ 4249.706866] __do_softirq+0xe1/0x2f4 [ 4249.706872] irq_exit+0xb6/0xc0 [ 4249.706878] do_IRQ+0x86/0xe0 [ 4249.706883] common_interrupt+0xf/0xf [ 4249.706885] [ 4249.706893] RIP: 0010:cpuidle_enter_state+0xc5/0x420 [ 4249.706897] Code: ff e8 0f 3c 84 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 3d 03 00 00 31 ff e8 c2 90 8a ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 89 d1 01 00 00 41 c7 44 24 10 00 00 00 00 48 83 c4 18 [ 4249.706899] RSP: 0018:b16b019afe38 EFLAGS: 0246 ORIG_RAX: ffdc [ 4249.706902] RAX: 890625d2b2c0 RBX: b0b57b60 RCX: 001f [ 4249.706904] RDX: RSI: 471c71c7 RDI: [ 4249.706906] RBP: b16b019afe78 R08: 03dd763d738c R09: 890625d36600 [ 4249.706908] R10: 890625d2a064 R11: 890625d2a044 R12: 890625d36600 [ 4249.706910] R13: 0004 R14: 0004 R15: 890625d36600 [ 4249.706918] ? cpuidle_enter_state+0xa1/0x420 [ 4249.706924] cpuidle_enter+0x2e/0x40 [ 4249.706931] call_cpuidle+0x23/0x40 [ 4249.706936] do_idle+0x1eb/0x280
[Kernel-packages] [Bug 1681909] Re: kdump is not captured in remote host when kdump over ssh is configured
After updating the package for eaon-proposed with the fix for ppc64 (thanks Eric!), I've manually tested that version and it's working fine, being able to collect the kernel crash dump. The version I've tested is: $ rmadison makedumpfile | grep eoan-proposed makedumpfile | 1:1.6.6-2ubuntu1 | eoan-proposed| source, amd64, arm64, armhf, i386, ppc64el, s390x Even with my positive test results, the autopkgtest is broken and keep failing for ppc64, according to: http://autopkgtest.ubuntu.com/packages/m/makedumpfile/eoan/ppc64el According to the above test, we can see 2 important things: a) The last time it succeeded was : "makedumpfile/1:1.6.5-1ubuntu2 2019-06-20". And we can see in fact the ppc64 test was Skipped, that's the reason it succeeded. b) Even the current released version for eoan, 1:1.6.5-1ubuntu2, is failing according to the autopkgtest that ran on: "makedumpfile/1:1.6.5-1ubuntu2 2019-07-25". This test was triggered due to makedumpfile being a reverse dependency of "file". Also, I've try to replicate the test in one local powerpc64 server, using autopkgtest. My command-line was: https://pastebin.ubuntu.com/p/y4KyRvJVmz/ I've switched 2 parameters, having 4 tests results: 1) With "--apt-pocket=proposed=src:makedumpfile" (to test -proposed version) and "--nova-reboot": http://paste.ubuntu.com/p/Z8dr6ssF2J/ 2) With "--apt-pocket=proposed=src:makedumpfile" (to test -proposed version) only http://paste.ubuntu.com/p/qxDRy5xPSZ/ 3) Without both parameters above (testing the released version) http://paste.ubuntu.com/p/cYdMrWHPsR/ 4) Only with "--nova-reboot": http://paste.ubuntu.com/p/xYC4KG9DZr/ In all cases I've failed, with "Broken Pipe" in a late part of the test. During the failure, I could even SSH into the testbed, so something clearly is wrong with the test. I'd like to ask hereby an exemption from this test, marking it as "badtest" in ppc64. Cascardo, do you agree? I think we could release this package before the Eoan freeze, which is sane (based on manual tests made by a colleague and I), we shouldn't block based on a test that was always skipped. We still plan to continue investigating the test failure, until we can fix it. Thanks, Guilherme -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1681909 Title: kdump is not captured in remote host when kdump over ssh is configured Status in The Ubuntu-power-systems project: In Progress Status in makedumpfile package in Ubuntu: Fix Committed Status in makedumpfile source package in Xenial: Won't Fix Status in makedumpfile source package in Bionic: In Progress Status in makedumpfile source package in Cosmic: Won't Fix Status in makedumpfile source package in Disco: In Progress Status in makedumpfile source package in Eoan: Fix Committed Bug description: [Impact] * Kdump over network (like NFS mount or SSH dump) relies on network- online target from systemd. Even so, there are some NICs that report "Link Up" state but aren't ready to transmit packets. This is a generally bad behavior that is credited probably to NIC firmware delays, usually not fixable from drivers. Some adapters known to act like this are bnx2x, tg3 and ixgbe. * Kdump is a mechanism that may be a last resort to debug complex/hard to reproduce issues, so it's interesting to increase its reliability / resilience. We then propose here a solution/quirk to this issue on network dump by adding a retry/delay mechanism; if it's a network dump, kdump will retry some times and sleep between the attempts in order to exclude the case of NICs that aren't ready yet but will soon be able to transmit packets. * Although first reported by IBM in PowerPC arch, the scope for this issue is the NIC, and it was later reported in x86 arch too. [Test case] Usually it's difficult to naturally reproduce this issue in a deterministic way, but we have an artificial test case on comment #24 of this LP. Also, we have a report from this bug in which the user managed to reproduce the problem consistently - it's fixed after testing our solution. [Regression potential] There's not a clear regression potential here since it's just a retry/delay mechanism. Some potential problems may come from bad coding in the script. The delay between attempts is only 3 sec per iteration, so it shouldn't block the kdump progress for a high amount of time at once. [Other information] Salsa Debian commit: https://salsa.debian.org/debian/makedumpfile/commit/d63ba95337988be1eac8c8c76d90825ff5c6d17f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1681909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1838133] Re: realtek r8822be kernel module fails after update to linux kernel-headers 5.0.0-21
Please test this kernel: https://people.canonical.com/~khfeng/lp1838133-disco/ It's based on Linux v5.0. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838133 Title: realtek r8822be kernel module fails after update to linux kernel- headers 5.0.0-21 Status in linux package in Ubuntu: Triaged Bug description: On July 24th I upgraded to the latest linux-headers-5.0.0-21 as part of the dist-upgrade for latest packages in Disco Dingo 19.04. I didn't notice that wifi was no longer working because at work I exclusively use a wired Ethernet connection. Today, however, when I tried to use my realtek r8822be wireless card, I discovered that it was totally unresponsive and did not work with wpa_supplicant / wpa_cli even when invoked manually from the command line (let alone with NetworkManager). When the problem occurred, I was using 19.04's latest kernel 5.0.0-21. I then rebooted and selected kernel 5.0.0-20 from GRUB menu. "uname -a" shows that I am using the previous kernel version: Linux pj 5.0.0-20-generic #21-Ubuntu SMP Mon Jun 24 09:32:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux With this kernel version as well as linux-headers-5.0.0.20, linux- headers-5.0.0-20-generic, my realtek wireless card works fine. While booted into 5.0.0-20 kernel, here are the realtek kernel modules that are loaded: # lsmod | grep r8 r8822be 692224 0 mac80211 806912 1 r8822be cfg80211 671744 2 mac80211,r8822be r8169 81920 0 Hopefully this realtek wireless regression can get fixed in the next minor kernel version. Let me know if you need any more information. Best Regards, Jun To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840261] Re: eoan/linux: 5.2.0-13.14 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1840259 (bionic/linux-hwe-edge) -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Ready for Promote to Proposed - phase-changed: Friday, 16. August 2019 00:05 UTC + phase: Promote to Proposed + phase-changed: Friday, 16. August 2019 19:11 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait trackers: bionic/linux-hwe-edge: bug 1840259 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840261 Title: eoan/linux: 5.2.0-13.14 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1840259 (bionic/linux-hwe-edge) -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Friday, 16. August 2019 19:11 UTC reason: promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait trackers: bionic/linux-hwe-edge: bug 1840259 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840261/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840454] 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 thermald in Ubuntu. https://bugs.launchpad.net/bugs/1840454 Title: kernel 5.2 disallows thermald's direct MSR writes Status in linux package in Ubuntu: Confirmed Status in thermald package in Ubuntu: New Bug description: thermald/kernel are spamming dmesg now because MSR write is disallowed. jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | wc -l 8688 jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | tail Aug 16 14:48:57 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:48:57 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:05 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:05 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:13 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:13 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:21 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:21 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5499 F pulseaudio /dev/snd/controlC1: jak5499 F pulseaudio /dev/snd/controlC0: jak5499 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (520 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: thermald 1.9.0-1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-10-generic root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 RelatedPackageVersions: linux-restricted-modules-5.2.0-10-generic N/A linux-backports-modules-5.2.0-10-generic N/A linux-firmware1.181 Tags: eoan third-party-packages Uname: Linux 5.2.0-10-generic x86_64 UpgradeStatus: Upgraded to eoan on 2018-11-20 (269 days ago) UserGroups: adm cdrom dip fax input kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 04/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET54W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET54W(1.31):bd04/22/2019:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832144] Re: Ubuntu 19.04 suspend freeze on Dell inspiron 7373
Hi kaihengfeng, thanks for your help, I had installed the last mainline version: Linux cccaballero-Inspiron-7373 5.3.0-050300rc4-generic #201908111734 SMP Sun Aug 11 21:37:12 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux And this is what happened: - first boot after the kernel was installed: I click suspend and it works ok, the device entered in suspend state, and recovered ok. Afther the first successful suspension, I tried to suspend again and the device rebooted - second boot after the kernel was installed: I click suspend and it works ok, the device entered in suspend state, and recovered ok. Afther the first successful suspension, I tried to suspend again and the device freezed just like in the bug description. - third boot after the kernel was installed: I click suspend and the device freezed just like in the bug description. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832144 Title: Ubuntu 19.04 suspend freeze on Dell inspiron 7373 Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 19.04 in my Dell Inspiron 7373 and I am getting issues with suspend. When I lock the case or write the "systemctl suspend" command, the screen turn off, the system freeze and the laptop keeps turned on. I need to force the laptop turn off and on again. There are some cases when it suspends without issues, but most of the time it freezes. There are some workarounds for issues like this one but they are mostly for laptops using nvidia graphics. I am not sure how to provide debug information about this issue, but I can give it if someone tells me how to do it. "lsb_release -rd" output: Description:Ubuntu 19.04 Release:19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832144/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840454] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1840454/+attachment/5282903/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1840454 Title: kernel 5.2 disallows thermald's direct MSR writes Status in linux package in Ubuntu: New Status in thermald package in Ubuntu: New Bug description: thermald/kernel are spamming dmesg now because MSR write is disallowed. jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | wc -l 8688 jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | tail Aug 16 14:48:57 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:48:57 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:05 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:05 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:13 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:13 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:21 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:21 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5499 F pulseaudio /dev/snd/controlC1: jak5499 F pulseaudio /dev/snd/controlC0: jak5499 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (520 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: thermald 1.9.0-1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-10-generic root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 RelatedPackageVersions: linux-restricted-modules-5.2.0-10-generic N/A linux-backports-modules-5.2.0-10-generic N/A linux-firmware1.181 Tags: eoan third-party-packages Uname: Linux 5.2.0-10-generic x86_64 UpgradeStatus: Upgraded to eoan on 2018-11-20 (269 days ago) UserGroups: adm cdrom dip fax input kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 04/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET54W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET54W(1.31):bd04/22/2019:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840454] Re: kernel 5.2 disallows thermald's direct MSR writes
Noteworthy maybe is that this did not seem to happen in 5.2.0-9, but that one complained about 1b0 Jul 27 16:44:16 jak-t480s kernel: msr: Direct access to MSR 1b0 but far less often :D ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1840454 Title: kernel 5.2 disallows thermald's direct MSR writes Status in linux package in Ubuntu: New Status in thermald package in Ubuntu: New Bug description: thermald/kernel are spamming dmesg now because MSR write is disallowed. jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | wc -l 8688 jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | tail Aug 16 14:48:57 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:48:57 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:05 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:05 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:13 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:13 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:21 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:21 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5499 F pulseaudio /dev/snd/controlC1: jak5499 F pulseaudio /dev/snd/controlC0: jak5499 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (520 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: thermald 1.9.0-1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-10-generic root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 RelatedPackageVersions: linux-restricted-modules-5.2.0-10-generic N/A linux-backports-modules-5.2.0-10-generic N/A linux-firmware1.181 Tags: eoan third-party-packages Uname: Linux 5.2.0-10-generic x86_64 UpgradeStatus: Upgraded to eoan on 2018-11-20 (269 days ago) UserGroups: adm cdrom dip fax input kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 04/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET54W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET54W(1.31):bd04/22/2019:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840454] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1840454/+attachment/5282905/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1840454 Title: kernel 5.2 disallows thermald's direct MSR writes Status in linux package in Ubuntu: New Status in thermald package in Ubuntu: New Bug description: thermald/kernel are spamming dmesg now because MSR write is disallowed. jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | wc -l 8688 jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | tail Aug 16 14:48:57 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:48:57 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:05 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:05 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:13 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:13 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:21 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:21 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5499 F pulseaudio /dev/snd/controlC1: jak5499 F pulseaudio /dev/snd/controlC0: jak5499 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (520 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: thermald 1.9.0-1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-10-generic root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 RelatedPackageVersions: linux-restricted-modules-5.2.0-10-generic N/A linux-backports-modules-5.2.0-10-generic N/A linux-firmware1.181 Tags: eoan third-party-packages Uname: Linux 5.2.0-10-generic x86_64 UpgradeStatus: Upgraded to eoan on 2018-11-20 (269 days ago) UserGroups: adm cdrom dip fax input kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 04/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET54W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET54W(1.31):bd04/22/2019:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840454] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1840454/+attachment/5282904/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1840454 Title: kernel 5.2 disallows thermald's direct MSR writes Status in linux package in Ubuntu: New Status in thermald package in Ubuntu: New Bug description: thermald/kernel are spamming dmesg now because MSR write is disallowed. jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | wc -l 8688 jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | tail Aug 16 14:48:57 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:48:57 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:05 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:05 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:13 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:13 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:21 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:21 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5499 F pulseaudio /dev/snd/controlC1: jak5499 F pulseaudio /dev/snd/controlC0: jak5499 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (520 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: thermald 1.9.0-1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-10-generic root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 RelatedPackageVersions: linux-restricted-modules-5.2.0-10-generic N/A linux-backports-modules-5.2.0-10-generic N/A linux-firmware1.181 Tags: eoan third-party-packages Uname: Linux 5.2.0-10-generic x86_64 UpgradeStatus: Upgraded to eoan on 2018-11-20 (269 days ago) UserGroups: adm cdrom dip fax input kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 04/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET54W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET54W(1.31):bd04/22/2019:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840454] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1840454/+attachment/5282899/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1840454 Title: kernel 5.2 disallows thermald's direct MSR writes Status in linux package in Ubuntu: New Status in thermald package in Ubuntu: New Bug description: thermald/kernel are spamming dmesg now because MSR write is disallowed. jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | wc -l 8688 jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | tail Aug 16 14:48:57 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:48:57 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:05 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:05 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:13 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:13 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:21 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:21 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5499 F pulseaudio /dev/snd/controlC1: jak5499 F pulseaudio /dev/snd/controlC0: jak5499 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (520 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: thermald 1.9.0-1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-10-generic root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 RelatedPackageVersions: linux-restricted-modules-5.2.0-10-generic N/A linux-backports-modules-5.2.0-10-generic N/A linux-firmware1.181 Tags: eoan third-party-packages Uname: Linux 5.2.0-10-generic x86_64 UpgradeStatus: Upgraded to eoan on 2018-11-20 (269 days ago) UserGroups: adm cdrom dip fax input kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 04/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET54W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET54W(1.31):bd04/22/2019:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840454] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1840454/+attachment/5282897/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1840454 Title: kernel 5.2 disallows thermald's direct MSR writes Status in linux package in Ubuntu: New Status in thermald package in Ubuntu: New Bug description: thermald/kernel are spamming dmesg now because MSR write is disallowed. jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | wc -l 8688 jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | tail Aug 16 14:48:57 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:48:57 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:05 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:05 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:13 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:13 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:21 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:21 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5499 F pulseaudio /dev/snd/controlC1: jak5499 F pulseaudio /dev/snd/controlC0: jak5499 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (520 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: thermald 1.9.0-1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-10-generic root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 RelatedPackageVersions: linux-restricted-modules-5.2.0-10-generic N/A linux-backports-modules-5.2.0-10-generic N/A linux-firmware1.181 Tags: eoan third-party-packages Uname: Linux 5.2.0-10-generic x86_64 UpgradeStatus: Upgraded to eoan on 2018-11-20 (269 days ago) UserGroups: adm cdrom dip fax input kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 04/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET54W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET54W(1.31):bd04/22/2019:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840454] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1840454/+attachment/5282892/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1840454 Title: kernel 5.2 disallows thermald's direct MSR writes Status in linux package in Ubuntu: New Status in thermald package in Ubuntu: New Bug description: thermald/kernel are spamming dmesg now because MSR write is disallowed. jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | wc -l 8688 jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | tail Aug 16 14:48:57 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:48:57 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:05 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:05 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:13 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:13 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:21 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:21 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5499 F pulseaudio /dev/snd/controlC1: jak5499 F pulseaudio /dev/snd/controlC0: jak5499 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (520 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: thermald 1.9.0-1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-10-generic root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 RelatedPackageVersions: linux-restricted-modules-5.2.0-10-generic N/A linux-backports-modules-5.2.0-10-generic N/A linux-firmware1.181 Tags: eoan third-party-packages Uname: Linux 5.2.0-10-generic x86_64 UpgradeStatus: Upgraded to eoan on 2018-11-20 (269 days ago) UserGroups: adm cdrom dip fax input kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 04/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET54W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET54W(1.31):bd04/22/2019:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840454] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1840454/+attachment/5282893/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1840454 Title: kernel 5.2 disallows thermald's direct MSR writes Status in linux package in Ubuntu: New Status in thermald package in Ubuntu: New Bug description: thermald/kernel are spamming dmesg now because MSR write is disallowed. jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | wc -l 8688 jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | tail Aug 16 14:48:57 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:48:57 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:05 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:05 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:13 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:13 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:21 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:21 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5499 F pulseaudio /dev/snd/controlC1: jak5499 F pulseaudio /dev/snd/controlC0: jak5499 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (520 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: thermald 1.9.0-1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-10-generic root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 RelatedPackageVersions: linux-restricted-modules-5.2.0-10-generic N/A linux-backports-modules-5.2.0-10-generic N/A linux-firmware1.181 Tags: eoan third-party-packages Uname: Linux 5.2.0-10-generic x86_64 UpgradeStatus: Upgraded to eoan on 2018-11-20 (269 days ago) UserGroups: adm cdrom dip fax input kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 04/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET54W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET54W(1.31):bd04/22/2019:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840454] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1840454/+attachment/5282900/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1840454 Title: kernel 5.2 disallows thermald's direct MSR writes Status in linux package in Ubuntu: New Status in thermald package in Ubuntu: New Bug description: thermald/kernel are spamming dmesg now because MSR write is disallowed. jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | wc -l 8688 jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | tail Aug 16 14:48:57 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:48:57 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:05 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:05 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:13 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:13 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:21 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:21 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5499 F pulseaudio /dev/snd/controlC1: jak5499 F pulseaudio /dev/snd/controlC0: jak5499 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (520 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: thermald 1.9.0-1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-10-generic root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 RelatedPackageVersions: linux-restricted-modules-5.2.0-10-generic N/A linux-backports-modules-5.2.0-10-generic N/A linux-firmware1.181 Tags: eoan third-party-packages Uname: Linux 5.2.0-10-generic x86_64 UpgradeStatus: Upgraded to eoan on 2018-11-20 (269 days ago) UserGroups: adm cdrom dip fax input kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 04/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET54W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET54W(1.31):bd04/22/2019:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840454] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1840454/+attachment/5282898/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1840454 Title: kernel 5.2 disallows thermald's direct MSR writes Status in linux package in Ubuntu: New Status in thermald package in Ubuntu: New Bug description: thermald/kernel are spamming dmesg now because MSR write is disallowed. jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | wc -l 8688 jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | tail Aug 16 14:48:57 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:48:57 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:05 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:05 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:13 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:13 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:21 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:21 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5499 F pulseaudio /dev/snd/controlC1: jak5499 F pulseaudio /dev/snd/controlC0: jak5499 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (520 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: thermald 1.9.0-1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-10-generic root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 RelatedPackageVersions: linux-restricted-modules-5.2.0-10-generic N/A linux-backports-modules-5.2.0-10-generic N/A linux-firmware1.181 Tags: eoan third-party-packages Uname: Linux 5.2.0-10-generic x86_64 UpgradeStatus: Upgraded to eoan on 2018-11-20 (269 days ago) UserGroups: adm cdrom dip fax input kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 04/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET54W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET54W(1.31):bd04/22/2019:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840454] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1840454/+attachment/5282894/+files/Dependencies.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1840454 Title: kernel 5.2 disallows thermald's direct MSR writes Status in linux package in Ubuntu: New Status in thermald package in Ubuntu: New Bug description: thermald/kernel are spamming dmesg now because MSR write is disallowed. jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | wc -l 8688 jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | tail Aug 16 14:48:57 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:48:57 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:05 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:05 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:13 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:13 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:21 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:21 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5499 F pulseaudio /dev/snd/controlC1: jak5499 F pulseaudio /dev/snd/controlC0: jak5499 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (520 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: thermald 1.9.0-1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-10-generic root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 RelatedPackageVersions: linux-restricted-modules-5.2.0-10-generic N/A linux-backports-modules-5.2.0-10-generic N/A linux-firmware1.181 Tags: eoan third-party-packages Uname: Linux 5.2.0-10-generic x86_64 UpgradeStatus: Upgraded to eoan on 2018-11-20 (269 days ago) UserGroups: adm cdrom dip fax input kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 04/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET54W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET54W(1.31):bd04/22/2019:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840454] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1840454/+attachment/5282902/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1840454 Title: kernel 5.2 disallows thermald's direct MSR writes Status in linux package in Ubuntu: New Status in thermald package in Ubuntu: New Bug description: thermald/kernel are spamming dmesg now because MSR write is disallowed. jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | wc -l 8688 jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | tail Aug 16 14:48:57 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:48:57 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:05 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:05 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:13 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:13 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:21 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:21 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5499 F pulseaudio /dev/snd/controlC1: jak5499 F pulseaudio /dev/snd/controlC0: jak5499 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (520 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: thermald 1.9.0-1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-10-generic root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 RelatedPackageVersions: linux-restricted-modules-5.2.0-10-generic N/A linux-backports-modules-5.2.0-10-generic N/A linux-firmware1.181 Tags: eoan third-party-packages Uname: Linux 5.2.0-10-generic x86_64 UpgradeStatus: Upgraded to eoan on 2018-11-20 (269 days ago) UserGroups: adm cdrom dip fax input kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 04/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET54W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET54W(1.31):bd04/22/2019:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840454] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1840454/+attachment/5282895/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1840454 Title: kernel 5.2 disallows thermald's direct MSR writes Status in linux package in Ubuntu: New Status in thermald package in Ubuntu: New Bug description: thermald/kernel are spamming dmesg now because MSR write is disallowed. jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | wc -l 8688 jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | tail Aug 16 14:48:57 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:48:57 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:05 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:05 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:13 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:13 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:21 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:21 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5499 F pulseaudio /dev/snd/controlC1: jak5499 F pulseaudio /dev/snd/controlC0: jak5499 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (520 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: thermald 1.9.0-1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-10-generic root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 RelatedPackageVersions: linux-restricted-modules-5.2.0-10-generic N/A linux-backports-modules-5.2.0-10-generic N/A linux-firmware1.181 Tags: eoan third-party-packages Uname: Linux 5.2.0-10-generic x86_64 UpgradeStatus: Upgraded to eoan on 2018-11-20 (269 days ago) UserGroups: adm cdrom dip fax input kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 04/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET54W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET54W(1.31):bd04/22/2019:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840454] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1840454/+attachment/5282901/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1840454 Title: kernel 5.2 disallows thermald's direct MSR writes Status in linux package in Ubuntu: New Status in thermald package in Ubuntu: New Bug description: thermald/kernel are spamming dmesg now because MSR write is disallowed. jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | wc -l 8688 jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | tail Aug 16 14:48:57 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:48:57 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:05 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:05 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:13 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:13 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:21 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:21 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5499 F pulseaudio /dev/snd/controlC1: jak5499 F pulseaudio /dev/snd/controlC0: jak5499 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (520 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: thermald 1.9.0-1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-10-generic root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 RelatedPackageVersions: linux-restricted-modules-5.2.0-10-generic N/A linux-backports-modules-5.2.0-10-generic N/A linux-firmware1.181 Tags: eoan third-party-packages Uname: Linux 5.2.0-10-generic x86_64 UpgradeStatus: Upgraded to eoan on 2018-11-20 (269 days ago) UserGroups: adm cdrom dip fax input kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 04/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET54W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET54W(1.31):bd04/22/2019:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840454] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1840454/+attachment/5282896/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1840454 Title: kernel 5.2 disallows thermald's direct MSR writes Status in linux package in Ubuntu: New Status in thermald package in Ubuntu: New Bug description: thermald/kernel are spamming dmesg now because MSR write is disallowed. jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | wc -l 8688 jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | tail Aug 16 14:48:57 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:48:57 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:05 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:05 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:13 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:13 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:21 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:21 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5499 F pulseaudio /dev/snd/controlC1: jak5499 F pulseaudio /dev/snd/controlC0: jak5499 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (520 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: thermald 1.9.0-1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-10-generic root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 RelatedPackageVersions: linux-restricted-modules-5.2.0-10-generic N/A linux-backports-modules-5.2.0-10-generic N/A linux-firmware1.181 Tags: eoan third-party-packages Uname: Linux 5.2.0-10-generic x86_64 UpgradeStatus: Upgraded to eoan on 2018-11-20 (269 days ago) UserGroups: adm cdrom dip fax input kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 04/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET54W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET54W(1.31):bd04/22/2019:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840454] Re: kernel 5.2 disallows thermald's direct MSR writes
apport information ** Tags added: apport-collected eoan third-party-packages ** Description changed: thermald/kernel are spamming dmesg now because MSR write is disallowed. jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | wc -l 8688 jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | tail Aug 16 14:48:57 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:48:57 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:05 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:05 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:13 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:13 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:21 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:21 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu7 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC2: jak5499 F pulseaudio + /dev/snd/controlC1: jak5499 F pulseaudio + /dev/snd/controlC0: jak5499 F pulseaudio + CurrentDesktop: GNOME + DistroRelease: Ubuntu 19.10 + HibernationDevice: RESUME=none + InstallationDate: Installed on 2018-03-14 (520 days ago) + InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) + MachineType: LENOVO 20L8S02D00 + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: thermald 1.9.0-1 + PackageArchitecture: amd64 + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-10-generic root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ + ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 + RelatedPackageVersions: + linux-restricted-modules-5.2.0-10-generic N/A + linux-backports-modules-5.2.0-10-generic N/A + linux-firmware1.181 + Tags: eoan third-party-packages + Uname: Linux 5.2.0-10-generic x86_64 + UpgradeStatus: Upgraded to eoan on 2018-11-20 (269 days ago) + UserGroups: adm cdrom dip fax input kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo + _MarkForUpload: True + dmi.bios.date: 04/22/2019 + dmi.bios.vendor: LENOVO + dmi.bios.version: N22ET54W (1.31 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20L8S02D00 + dmi.board.vendor: LENOVO + dmi.board.version: Not Defined + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: None + dmi.modalias: dmi:bvnLENOVO:bvrN22ET54W(1.31):bd04/22/2019:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: + dmi.product.family: ThinkPad T480s + dmi.product.name: 20L8S02D00 + dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s + dmi.product.version: ThinkPad T480s + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1840454/+attachment/5282891/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1840454 Title: kernel 5.2 disallows thermald's direct MSR writes Status in linux package in Ubuntu: New Status in thermald package in Ubuntu: New Bug description: thermald/kernel are spamming dmesg now because MSR write is disallowed. jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | wc -l 8688 jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | tail Aug 16 14:48:57 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:48:57 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:05 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:05 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:13 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:13 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:21 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:21 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5499 F pulseaudio /dev/snd/controlC1: jak5499 F pulseaudio /dev/snd/controlC0: jak5499 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (520 days ago)
[Kernel-packages] [Bug 1840066] Re: DELL DA300 adaptor's Ethernet port not working after update
Hey thanks a lot for the help! I am running on 1.6.0 BIOS. I am not sure how to check Thunderbolt firmware version separately, but I have already updated to the latest "updates" from software center when I ran into the bug. Also just now I followed https://itsfoss.com/update-firmware- ubuntu/ again and got "No upgrades for XPS 13 9380 System Firmware, current is 0.1.6.0: 0.1.6.0=same, 0.1.5.0=older, 0.1.4.0=older, 0.1.3.2=older, 0.1.2.1=older" from "sudo fwupdmgr update" at the last step in the article. Thanks again for the help. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840066 Title: DELL DA300 adaptor's Ethernet port not working after update Status in linux package in Ubuntu: Incomplete Bug description: DELL DA300 adapter's Ethernet port stopped working after recent update. Whenever the cable is plugged in to the adapter, network manager would show the cable connecting icon and immediately drop the connection. I am able to get Ethernet connection through the DA300 with another Ethernet-USBc adapter by plugging the cable to the adaptor and use DA300's USBc port though. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-03-26 (142 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IpRoute: default via 131.215.195.254 dev enx00e04c680c21 proto dhcp metric 100 default via 10.6.41.254 dev wlp2s0 proto dhcp metric 600 10.6.40.0/23 dev wlp2s0 proto kernel scope link src 10.6.41.210 metric 600 131.215.195.0/24 dev enx00e04c680c21 proto kernel scope link src 131.215.195.209 metric 100 169.254.0.0/16 dev wlp2s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.14-0ubuntu2 [origin: unknown] PackageArchitecture: amd64 Tags: third-party-packages bionic Uname: Linux 5.2.5-050205-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2019-08-13T09:56:21.009087 nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enx00e04c680c21 ethernet connected /org/freedesktop/NetworkManager/Devices/6 Wired connection 1 483df49a-2e78-38c0-a084-58e621ab7527 /org/freedesktop/NetworkManager/ActiveConnection/6 wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/3 eduroam f7c3132c-f44a-4f36-ba26-88e67487dddb /org/freedesktop/NetworkManager/ActiveConnection/5 enxc8f7509d89c6 ethernet unavailable /org/freedesktop/NetworkManager/Devices/5 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.14 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840066/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1385245] Re: Beats Studio wireless bluetooth headphones wont pair w/ ubuntu 14.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: blueman (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1385245 Title: Beats Studio wireless bluetooth headphones wont pair w/ ubuntu 14.04 Status in blueman package in Ubuntu: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: I have Beats Studio wireless bluetooth headphones and when adding device (pair bluetooth device) it wont pair w/ ubuntu 14.04 system. Closest thing I've found is this: https://code.google.com/p/chromium/issues/detail?id=379126 It looks like it's working on ChromeOS so I'm hoping it's possible it will work w/ ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1385245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1385245] Re: Beats Studio wireless bluetooth headphones wont pair w/ ubuntu 14.04
** Also affects: blueman (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1385245 Title: Beats Studio wireless bluetooth headphones wont pair w/ ubuntu 14.04 Status in blueman package in Ubuntu: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: I have Beats Studio wireless bluetooth headphones and when adding device (pair bluetooth device) it wont pair w/ ubuntu 14.04 system. Closest thing I've found is this: https://code.google.com/p/chromium/issues/detail?id=379126 It looks like it's working on ChromeOS so I'm hoping it's possible it will work w/ ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1385245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1655280] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore
This has been blocked because we need to get changes on the development release first, and recent changes on testing has caused ppc64el testing failures. Those changes allowed tests to be run on VMs with more memory, which allow the test to run instead of being skipped. So now we are detecting a failure, though I couldn't be able to reproduce it so far, which is what is blocking progress here. I will try other approaches to try to reproduce and investigate. Cascardo. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1655280 Title: ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in makedumpfile source package in Xenial: New Status in linux source package in Bionic: Invalid Status in makedumpfile source package in Bionic: Fix Released Status in linux source package in Cosmic: Invalid Status in makedumpfile source package in Cosmic: Fix Released Status in linux source package in Disco: Invalid Status in makedumpfile source package in Disco: Fix Released Bug description: [Impact] After a DLPAR memory/CPU add/remove operation, kdump tools need to be restarted or else kdump tools will fail to capture the crash. [Test] == Comment: #0 - Ping Tian Han - 2017-01-09 02:51:00 == ---Problem Description--- Vmcore cannot be saved when triggering bug 150353 on roselp4: Copying data : [ 2.0 %] \/usr/sbin/kdump-config: line 591: 5502 Bus error makedumpfile $MAKEDUMP_ARGS $vmcore_file $KDUMP_CORETEMP [ 512.833872] kdump-tools[5450]: * kdump-tools: makedumpfile failed, falling back to 'cp' [ 573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad address [ 573.605717] kdump-tools[5450]: * kdump-tools: failed to save vmcore in /var/crash/201701090223 [ 573.765417] kdump-tools[5450]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/201701090223/dmesg.201701090223 [ 574.285506] kdump-tools[5450]: The kernel version is not supported. [ 574.285672] kdump-tools[5450]: The makedumpfile operation may be incomplete. [ 574.285767] kdump-tools[5450]: The dmesg log is saved to /var/crash/201701090223/dmesg.201701090223. [ 574.305422] kdump-tools[5450]: makedumpfile Completed. [ 574.315363] kdump-tools[5450]: * kdump-tools: saved dmesg content in /var/crash/201701090223 [ 574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600 [ 574.705384] kdump-tools[5450]: Rebooting. Stopping ifup for ib0... [ OK ] Stopped ifup for ib0. [ 1008.579897] reboot: Restarting system Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie Mitsuyoshi/carri...@us.ibm.com ---uname output--- Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = lpar ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. config kdump on roselp4 2. try to trigger bug 150353 *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie Mitsuyoshi/carri...@us.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. == Comment: #3 - Brahadambal Srinivasan - 2017-01-10 02:42:25 == root@roselp4:~# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet crashkernel=384M-:512M root@roselp4:~# dmesg | grep Reser [0.00] Reserving 512MB of memory at 128MB for crashkernel (System RAM: 21760MB) [Regression Potential] The fix applies to makedumpfile, and could impact dump capture. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1655280/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840488] [NEW] Disable Bluetooth in cloud kernels
Public bug reported: [Impact] Some cloud-focused kernels have CONFIG_BT enabled but cloud instances shouldn't need bluetooth support. Disabling the bluetooth subsystem reduces the amount of security-sensitive code we have to worry about in the cloud kernels and also has the nice side effect of minimizing build times and kernel sizes. The cloud kernels known to have bluetooth enabled include: * [B/D/E] linux-aws (arm64 only) * [X/B/D/E] linux-gcp * [B] linux-gke-4.15 * [B] linux-gke-5.0 * [X/B/D/E] linux-oracle [Test Case] 1. Install patched kernel and reboot into it 2. Ensure that the following command does NOT display any output: $ grep CONFIG_BT=[my] /boot/config-$(uname -r) [Regression Potential] There could be an unexpected dependence on bluetooth within one of the clouds but I think it is highly unlikely. ** Affects: linux-aws (Ubuntu) Importance: High Status: Triaged ** Affects: linux-gcp (Ubuntu) Importance: High Status: Triaged ** Affects: linux-gke-4.15 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-gke-5.0 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oracle (Ubuntu) Importance: High Status: Triaged ** Affects: linux-aws (Ubuntu Xenial) Importance: Undecided Status: Invalid ** Affects: linux-gcp (Ubuntu Xenial) Importance: High Status: Triaged ** Affects: linux-gke-4.15 (Ubuntu Xenial) Importance: Undecided Status: Invalid ** Affects: linux-gke-5.0 (Ubuntu Xenial) Importance: Undecided Status: Invalid ** Affects: linux-oracle (Ubuntu Xenial) Importance: High Status: Triaged ** Affects: linux-aws (Ubuntu Bionic) Importance: Undecided Status: Triaged ** Affects: linux-gcp (Ubuntu Bionic) Importance: High Status: Triaged ** Affects: linux-gke-4.15 (Ubuntu Bionic) Importance: High Status: Triaged ** Affects: linux-gke-5.0 (Ubuntu Bionic) Importance: High Status: Triaged ** Affects: linux-oracle (Ubuntu Bionic) Importance: High Status: Triaged ** Affects: linux-aws (Ubuntu Disco) Importance: Undecided Status: Triaged ** Affects: linux-gcp (Ubuntu Disco) Importance: High Status: Triaged ** Affects: linux-gke-4.15 (Ubuntu Disco) Importance: Undecided Status: Invalid ** Affects: linux-gke-5.0 (Ubuntu Disco) Importance: Undecided Status: Invalid ** Affects: linux-oracle (Ubuntu Disco) Importance: High Status: Triaged ** Affects: linux-aws (Ubuntu Eoan) Importance: High Status: Triaged ** Affects: linux-gcp (Ubuntu Eoan) Importance: High Status: Triaged ** Affects: linux-gke-4.15 (Ubuntu Eoan) Importance: Undecided Status: Invalid ** Affects: linux-gke-5.0 (Ubuntu Eoan) Importance: Undecided Status: Invalid ** Affects: linux-oracle (Ubuntu Eoan) Importance: High Status: Triaged ** Also affects: linux-aws (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Eoan) Importance: High Status: Triaged ** Also affects: linux-aws (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Disco) Status: New => Triaged ** Changed in: linux-aws (Ubuntu Bionic) Status: New => Triaged ** Description changed: [Impact] Some cloud-focused kernels have CONFIG_BT enabled but cloud instances shouldn't need bluetooth support. Disabling the bluetooth subsystem reduces the amount of security-sensitive code we have to worry about in the cloud kernels and also has the nice side effect of minimizing build times and kernel sizes. + The cloud kernels known to have bluetooth enabled include: + + * [B/D/E] linux-aws (arm64 only) + + [Test Case] 1. Install patched kernel and reboot into it 2. Ensure that the following command does NOT display any output: -$ grep CONFIG_BT=[my] /boot/config-$(uname -r) + $ grep CONFIG_BT=[my] /boot/config-$(uname -r) [Regression Potential] There could be an unexpected dependence on bluetooth within one of the clouds but I think it is highly unlikely. ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Xenial) Status: New => Invalid ** Also affects: linux-gke-4.15 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-gke-5.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-gke-4.15 (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-gke-4.15 (Ubuntu Disco) Status: New => Invalid ** Changed in: linux-gke-4.15 (Ubuntu Eoan)
[Kernel-packages] [Bug 1840328] Re: Regression in overlayfs between 4.4.0-157 and 4.4.0-159
I also confirmed that using a 'dir' backed (no overlay) LXC container does not exhibit this broken behavior. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840328 Title: Regression in overlayfs between 4.4.0-157 and 4.4.0-159 Status in linux package in Ubuntu: Confirmed Bug description: My xenial gate jobs began failing after the nodes began running 4.4.0-159. The gist of this bug is that a file sitting in /posix.ini for example, copied there by ucf from /usr/share/php7.2-common/common/posix.ini, cannot be read by non-root users despite its permission bits being 0644. chmodding 0644 on top of the file fixes this, also rebooting the lxc container solves it as well. After downgrading the same test node to 4.4.0-157 and re-running the same tests, the broken behavior does not occur. Please see the attachments for the exact commands used to reproduce this. --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: N/A DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lspci: Error: [Errno 2] No such file or directory Lsusb: Error: [Errno 2] No such file or directory MachineType: OpenStack Foundation OpenStack Nova Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-159-generic root=LABEL=cloudimg-rootfs ro console=tty0 console=ttyS0,115200 no_timer_check nofb nomodeset vga=normal ProcVersionSignature: Ubuntu 4.4.0-159.187-generic 4.4.185 RelatedPackageVersions: linux-restricted-modules-4.4.0-159-generic N/A linux-backports-modules-4.4.0-159-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial UdevDb: Error: [Errno 2] No such file or directory Uname: Linux 4.4.0-159-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1~cloud0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1~cloud0:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr18.2.0:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: OpenStack Nova dmi.product.version: 18.2.0 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840328/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840454] Re: kernel 5.2 disallows thermald's direct MSR writes
The patch for changing TCC offset can only be in for 5.4 kernel. Then there will be no MSR access. So the option is to take out of mainline kernel patch to avoid this or avoid workaround option. I don't know if there are any other options. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840454 Title: kernel 5.2 disallows thermald's direct MSR writes Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: New Bug description: thermald/kernel are spamming dmesg now because MSR write is disallowed. jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | wc -l 8688 jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | tail Aug 16 14:48:57 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:48:57 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:05 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:05 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:13 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:13 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:21 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:21 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833617] Re: [amdgpu] screen freeze after suspend
Unfortunately it's not a log file. Please attach `journalctl -b -1 -k`.`` -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833617 Title: [amdgpu] screen freeze after suspend Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: It's most likely amdgup driver needs an upgrade. Problem occurs since kernel upgrade to 5.0 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12 Uname: Linux 5.0.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Thu Jun 20 13:46:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev eb) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] InstallationDate: Installed on 2019-06-06 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Inspiron 3180 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-18-generic root=UUID=a16bd163-e82f-4ec1-9c5f-c9bd32e225fa ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833617/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840484] Re: can not suspend to idle
** Attachment added: "dmesg.log" https://bugs.launchpad.net/oem-priority/+bug/1840484/+attachment/5282882/+files/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem in Ubuntu. https://bugs.launchpad.net/bugs/1840484 Title: can not suspend to idle Status in OEM Priority Project: New Status in linux-signed-oem package in Ubuntu: New Bug description: it somehow s2i failed, from message , it seems the s2i process be blocked by thunderbolt device. dmesg: [193139.391652] pciehp :04:04.0:pcie204: pcie_do_write_cmd: no response from device [193139.391703] pciehp :04:01.0:pcie204: pcie_do_write_cmd: no response from device [193141.012736] PM: noirq suspend of devices failed [193141.772467] ath10k_pci :02:00.0: Unknown eventid: 118809 [193141.775359] ath10k_pci :02:00.0: Unknown eventid: 90118 [193141.872317] thunderbolt :05:00.0: control channel starting... Not sure is it relative that I hot plug out WD19 docking before suspend. reproduce rate: random ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1045-oem 4.15.0-1045.50 ProcVersionSignature: Ubuntu 4.15.0-1045.50-oem 4.15.18 Uname: Linux 4.15.0-1045-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 17 00:02:08 2019 InstallationDate: Installed on 2019-08-11 (5 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1840484/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840484] Re: can not suspend to idle
the latest suspend is what I tried by pm_test, so when the issue happens, the issue always there even by pm_test before I reboot it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem in Ubuntu. https://bugs.launchpad.net/bugs/1840484 Title: can not suspend to idle Status in OEM Priority Project: New Status in linux-signed-oem package in Ubuntu: New Bug description: it somehow s2i failed, from message , it seems the s2i process be blocked by thunderbolt device. dmesg: [193139.391652] pciehp :04:04.0:pcie204: pcie_do_write_cmd: no response from device [193139.391703] pciehp :04:01.0:pcie204: pcie_do_write_cmd: no response from device [193141.012736] PM: noirq suspend of devices failed [193141.772467] ath10k_pci :02:00.0: Unknown eventid: 118809 [193141.775359] ath10k_pci :02:00.0: Unknown eventid: 90118 [193141.872317] thunderbolt :05:00.0: control channel starting... Not sure is it relative that I hot plug out WD19 docking before suspend. reproduce rate: random ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1045-oem 4.15.0-1045.50 ProcVersionSignature: Ubuntu 4.15.0-1045.50-oem 4.15.18 Uname: Linux 4.15.0-1045-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 17 00:02:08 2019 InstallationDate: Installed on 2019-08-11 (5 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1840484/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840484] [NEW] can not suspend to idle
Public bug reported: it somehow s2i failed, from message , it seems the s2i process be blocked by thunderbolt device. dmesg: [193139.391652] pciehp :04:04.0:pcie204: pcie_do_write_cmd: no response from device [193139.391703] pciehp :04:01.0:pcie204: pcie_do_write_cmd: no response from device [193141.012736] PM: noirq suspend of devices failed [193141.772467] ath10k_pci :02:00.0: Unknown eventid: 118809 [193141.775359] ath10k_pci :02:00.0: Unknown eventid: 90118 [193141.872317] thunderbolt :05:00.0: control channel starting... Not sure is it relative that I hot plug out WD19 docking before suspend. reproduce rate: random ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1045-oem 4.15.0-1045.50 ProcVersionSignature: Ubuntu 4.15.0-1045.50-oem 4.15.18 Uname: Linux 4.15.0-1045-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 17 00:02:08 2019 InstallationDate: Installed on 2019-08-11 (5 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed-oem UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: oem-priority Importance: High Assignee: Alex Tu (alextu) Status: New ** Affects: linux-signed-oem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Alex Tu (alextu) ** Changed in: oem-priority Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem in Ubuntu. https://bugs.launchpad.net/bugs/1840484 Title: can not suspend to idle Status in OEM Priority Project: New Status in linux-signed-oem package in Ubuntu: New Bug description: it somehow s2i failed, from message , it seems the s2i process be blocked by thunderbolt device. dmesg: [193139.391652] pciehp :04:04.0:pcie204: pcie_do_write_cmd: no response from device [193139.391703] pciehp :04:01.0:pcie204: pcie_do_write_cmd: no response from device [193141.012736] PM: noirq suspend of devices failed [193141.772467] ath10k_pci :02:00.0: Unknown eventid: 118809 [193141.775359] ath10k_pci :02:00.0: Unknown eventid: 90118 [193141.872317] thunderbolt :05:00.0: control channel starting... Not sure is it relative that I hot plug out WD19 docking before suspend. reproduce rate: random ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1045-oem 4.15.0-1045.50 ProcVersionSignature: Ubuntu 4.15.0-1045.50-oem 4.15.18 Uname: Linux 4.15.0-1045-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 17 00:02:08 2019 InstallationDate: Installed on 2019-08-11 (5 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1840484/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1833617] Re: [amdgpu] screen freeze after suspend
kai-hengthanks for the follow-up. The problem still persists. When I close the lead, the screen remains blanks. However, when I Press "suspend" the display does show up but the keyboard is disabled Attached is the latest journal. It is automatically generated and stored on my desktop. ThanksLevi On Friday, August 16, 2019, 6:20:43 AM PDT, Kai-Heng Feng wrote: Please test latest mainline kernel again: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc4/ And attach `journalctl -b -1 -k` once the issue happens. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1833617 Title: [amdgpu] screen freeze after suspend Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: It's most likely amdgup driver needs an upgrade. Problem occurs since kernel upgrade to 5.0 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12 Uname: Linux 5.0.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Thu Jun 20 13:46:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev eb) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] InstallationDate: Installed on 2019-06-06 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Inspiron 3180 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-18-generic root=UUID=a16bd163-e82f-4ec1-9c5f-c9bd32e225fa ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833617/+subscriptions ** Attachment added: "org.kde.ksystemlog.desktop" https://bugs.launchpad.net/bugs/1833617/+attachment/5282878/+files/org.kde.ksystemlog.desktop -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833617 Title: [amdgpu] screen freeze after suspend Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: It's most likely amdgup driver needs an upgrade. Problem occurs since kernel upgrade to 5.0 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12 Uname: Linux 5.0.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Thu Jun 20 13:46:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev eb) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] InstallationDate: Installed on 2019-06-06 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Inspiron 3180 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-18-generic root=UUID=a16bd163-e82f-4ec1-9c5f-c9bd32e225fa ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias:
[Kernel-packages] [Bug 1828166] Re: perf top problem on z with Ubuntu 18.04
Hello IBM, I have built test kernels for Bionic and Disco with the patches mentioned: b9c0a64 perf annotate: Fix s390 gap between kernel end and module start 12a6d29 perf record: Fix module size on s390 For Disco, I have also backported the following, which seemed to be a pre-req: 3376b6b7fb57 perf record: Fix s390 missing module symbol and warning for non-root users The debian packages can be found at: Bionic (4.15.0-59.66+lp1828166.20190814): https://people.canonical.com/~ksouza/lp1828166/20190814/bionic/ Disco (5.0.0-26.27+lp1828166.20190814): https://people.canonical.com/~ksouza/lp1828166/20190814/disco/ I have tested these kernels locally and I was not able to reproduce the issue anymore. Could you please test them to confirm the issue is fixed? Thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828166 Title: perf top problem on z with Ubuntu 18.04 Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Invalid Status in linux source package in Disco: In Progress Bug description: SRU Justification: == [Impact] * The perf top tool hangs and shows error messages, like 'Not enough memory for annotating' [Fix] * b9c0a64901d5bdec6eafd38d1dc8fa0e2974fccb b9c0a64 "perf annotate: Fix s390 gap between kernel end and module start" * 12a6d2940b5f02b4b9f71ce098e3bb02bc24a9ea 12a6d29 "perf record: Fix module size on s390" [Test Case] * start a benchmark (mem_alloc, but it doesn't really matter what) * execute perf top in a second terminal * the output of perf top is correct * now stop the benchmark * and perf top shows an error message, like "Not enough memory for annotating '__irf_end' symbol!)" * and perf top can't be exited anymore [Regression Potential] * The regression potential can be considered as medium since this happens only while using the perf top tool * and just 3 files are changed, and one of them is arch/s390/util/machine.c * but symbol and machine header in /tools/perf/util modified and several loc added [Other Info] * cherry-pick was possible to bionic-master-next and to disco-master- next (but used '--strategy=recursive -X theirs' for disco) * adding the patches to disco is to avoid regressions _ perf top hangs and shows error messages ---uname output--- Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- I start a benchmark (mem_alloc, but it really doesn't matter) and then issue perf top in a second terminal, the output from perf top is correct. Now I stop the benchmark: perf top shows a error message (Not enough memory for annotating '__irf_end' symbol!) and I can't quit from perf top anymore Following analyse took place: No problem with current kernel . Bi-Secting of perf tool took place and following commit was found: commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad) Author: Arnaldo Carvalho de Melo Date: Tue Oct 16 17:08:29 2018 -0300 perf tools: Stop fallbacking to kallsyms for vdso symbols lookup When you apply this patch the issue is gone, however it is contained in these versions: git tag --contains edeb0c90df3581b821 v4.19 v4.20 The level I was debugging was kernel 4.15 which does not contain this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1828166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839985] Re: bionic/linux-aws: 4.15.0-1046.48 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839983 (xenial/linux-aws-hwe) derivatives: bug 1839981 (aws-kernel) -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1840006 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws - phase: Holding before Promote to Proposed - phase-changed: Friday, 16. August 2019 10:30 UTC + phase: Ready for Promote to Proposed + phase-changed: Friday, 16. August 2019 16:05 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building + promote-to-proposed: Pending -- ready for review trackers: bionic/linux-aws/aws-kernel: bug 1839981 xenial/linux-aws-hwe: bug 1839983 variant: debs -- 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/1839985 Title: bionic/linux-aws: 4.15.0-1046.48 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839983 (xenial/linux-aws-hwe) derivatives: bug 1839981 (aws-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840006 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Ready for Promote to Proposed phase-changed: Friday, 16. August 2019 16:05 UTC reason: promote-to-proposed: Pending -- ready for review trackers: bionic/linux-aws/aws-kernel: bug 1839981 xenial/linux-aws-hwe: bug 1839983 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840454] 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 1840454 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840454 Title: kernel 5.2 disallows thermald's direct MSR writes Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: New Bug description: thermald/kernel are spamming dmesg now because MSR write is disallowed. jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | wc -l 8688 jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | tail Aug 16 14:48:57 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:48:57 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:05 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:05 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:13 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:13 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:21 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:21 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840454] Re: kernel 5.2 disallows thermald's direct MSR writes
Good point. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840454 Title: kernel 5.2 disallows thermald's direct MSR writes Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: New Bug description: thermald/kernel are spamming dmesg now because MSR write is disallowed. jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | wc -l 8688 jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | tail Aug 16 14:48:57 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:48:57 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:05 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:05 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:13 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:13 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:21 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:21 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
I had "ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2" on 18.04.03LTS with BIOS v1.13 on A315-41-R909 Just flashed v1.15 and now it boots ok without any extra parameters I share some info from /var/kernel.log It is better to keep "ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2" for better performance (see below related Firmware Bug lines)? If someone needs some more logs in order to improve the solution, just ask Thanks in advance In boot without extra parameters, and: -New lines with "Firmware Bug" Aug 16 17:13:20 enrique-Aspire-A315-41 kernel: [0.123596] AMD-Vi: [Firmware Bug]: : IOAPIC[4] not in IVRS table Aug 16 17:13:20 enrique-Aspire-A315-41 kernel: [0.123598] AMD-Vi: [Firmware Bug]: : IOAPIC[5] not in IVRS table Aug 16 17:13:20 enrique-Aspire-A315-41 kernel: [0.123599] AMD-Vi: [Firmware Bug]: : No southbridge IOAPIC found -This line with "Firmware Bug" does not disappear, but it seems not critical (it was booting before and it boots now) Aug 16 17:13:20 enrique-Aspire-A315-41 kernel: [0.179342] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored -New line appears (it wasn't before) which shows something new about iommu Aug 16 17:13:20 enrique-Aspire-A315-41 kernel: [1.314978] perf/amd_iommu: Detected AMD IOMMU #0 (2 banks, 4 counters/bank). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Fix Released Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828166] Re: perf top problem on z with Ubuntu 18.04
** Changed in: ubuntu-z-systems Status: Triaged => 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/1828166 Title: perf top problem on z with Ubuntu 18.04 Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Invalid Status in linux source package in Disco: In Progress Bug description: SRU Justification: == [Impact] * The perf top tool hangs and shows error messages, like 'Not enough memory for annotating' [Fix] * b9c0a64901d5bdec6eafd38d1dc8fa0e2974fccb b9c0a64 "perf annotate: Fix s390 gap between kernel end and module start" * 12a6d2940b5f02b4b9f71ce098e3bb02bc24a9ea 12a6d29 "perf record: Fix module size on s390" [Test Case] * start a benchmark (mem_alloc, but it doesn't really matter what) * execute perf top in a second terminal * the output of perf top is correct * now stop the benchmark * and perf top shows an error message, like "Not enough memory for annotating '__irf_end' symbol!)" * and perf top can't be exited anymore [Regression Potential] * The regression potential can be considered as medium since this happens only while using the perf top tool * and just 3 files are changed, and one of them is arch/s390/util/machine.c * but symbol and machine header in /tools/perf/util modified and several loc added [Other Info] * cherry-pick was possible to bionic-master-next and to disco-master- next (but used '--strategy=recursive -X theirs' for disco) * adding the patches to disco is to avoid regressions _ perf top hangs and shows error messages ---uname output--- Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- I start a benchmark (mem_alloc, but it really doesn't matter) and then issue perf top in a second terminal, the output from perf top is correct. Now I stop the benchmark: perf top shows a error message (Not enough memory for annotating '__irf_end' symbol!) and I can't quit from perf top anymore Following analyse took place: No problem with current kernel . Bi-Secting of perf tool took place and following commit was found: commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad) Author: Arnaldo Carvalho de Melo Date: Tue Oct 16 17:08:29 2018 -0300 perf tools: Stop fallbacking to kallsyms for vdso symbols lookup When you apply this patch the issue is gone, however it is contained in these versions: git tag --contains edeb0c90df3581b821 v4.19 v4.20 The level I was debugging was kernel 4.15 which does not contain this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1828166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829399] Re: Lid switch triggered suspend takes much longer than UI triggered suspend
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Expired => 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/1829399 Title: Lid switch triggered suspend takes much longer than UI triggered suspend Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Bug description: IBM T460 5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux When triggering a suspend even from the lid switch of my Lenovo T460 it takes 30 seconds to reach suspend state. Several others with different models of Lenovo laptops have also reproduced this issue. It seems this is isolated to the lid switch as UI triggered suspend (alt+power icon) is far faster. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829399/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840454] Re: kernel 5.2 disallows thermald's direct MSR writes
No I think it's because kernel lockdown: commit 708822cdbcd3faab40e83a79b71617e1812a1b06 Author: Matthew Garrett Date: Mon Feb 18 12:44:59 2019 + UBUNTU: SAUCE: (efi-lockdown) x86/msr: Restrict MSR access when the kernel is locked down Writing to MSRs should not be allowed if the kernel is locked down, since it could lead to execution of arbitrary code in kernel mode. Based on a patch by Kees Cook. MSR accesses are logged for the purposes of building up a whitelist as per Alan Cox's suggestion. Signed-off-by: Matthew Garrett Signed-off-by: David Howells Acked-by: Kees Cook Reviewed-by: Thomas Gleixner cc: x...@kernel.org Signed-off-by: Matthew Garrett (cherry picked from commit 323bd1cb92e03558ae3f3a11dd683dcbb23eeaea git://git.kernel.org/pub/scm/linux/kernel/git/jwboyer/fedora.git) Signed-off-by: Seth Forshee ** 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 thermald in Ubuntu. https://bugs.launchpad.net/bugs/1840454 Title: kernel 5.2 disallows thermald's direct MSR writes Status in linux package in Ubuntu: New Status in thermald package in Ubuntu: New Bug description: thermald/kernel are spamming dmesg now because MSR write is disallowed. jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | wc -l 8688 jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | tail Aug 16 14:48:57 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:48:57 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:05 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:05 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:13 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:13 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:21 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:21 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840454] Re: kernel 5.2 disallows thermald's direct MSR writes
I wonder if the msr module is not loaded. Try sudo modprobe msr -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1840454 Title: kernel 5.2 disallows thermald's direct MSR writes Status in thermald package in Ubuntu: New Bug description: thermald/kernel are spamming dmesg now because MSR write is disallowed. jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | wc -l 8688 jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | tail Aug 16 14:48:57 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:48:57 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:05 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:05 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:13 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:13 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:21 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:21 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1840454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839773] Re: MicroSD not mounted when inserted, used to work correctly
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839773 Title: MicroSD not mounted when inserted, used to work correctly Status in linux package in Ubuntu: Invalid Bug description: Using Ubuntu+1 (19.10 Eoan), I inserted my Sandisk 32GB microSD with an adaptor in my laptop's SD slot, but it was not mounted nor apparently detected. I'm certain that until few weeks ago it was working correctly, so I suppose the cause to be an update regression. I tested the same card on another laptop using Ubuntu 18.04 LTS and it works correctly. Also, I have tested another card (16GB) on the 19.10 laptop, and it's detected and mounted correctly. Summary: - 16GB SD card, FAT32 - Works with all Ubuntu versions - 32GB microSD with adaptor, FAT32 - Works in 18.04, stopped working with 19.10, at least 2 weeks ago was still working. I'd be happy to help debugging this issue. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-10-generic 5.2.0-10.11 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fabio 2086 F pulseaudio /dev/snd/controlC0: fabio 2086 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Aug 11 19:50:53 2019 GvfsMonitorError: This tool has been deprecated, use 'gio mount' instead. See 'gio help mount' for more info. GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HibernationDevice: RESUME=UUID=0e34c56e-8605-499f-9588-f09829ff1e81 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2019-02-03 (188 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:57b4 Realtek Semiconductor Corp. USB Camera Bus 001 Device 006: ID 13d3:3408 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-10-generic root=UUID=3eab3ace-7b67-4e6a-aea7-d31b73cc4819 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.2.0-10-generic N/A linux-backports-modules-5.2.0-10-generic N/A linux-firmware1.181 SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 19:51:12.078: The udisks-daemon is running (name-owner :1.10). UpgradeStatus: Upgraded to eoan on 2019-07-21 (21 days ago) dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550JK dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839773/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828166] Re: perf top problem on z with Ubuntu 18.04
** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Disco) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828166 Title: perf top problem on z with Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Invalid Status in linux source package in Disco: In Progress Bug description: SRU Justification: == [Impact] * The perf top tool hangs and shows error messages, like 'Not enough memory for annotating' [Fix] * b9c0a64901d5bdec6eafd38d1dc8fa0e2974fccb b9c0a64 "perf annotate: Fix s390 gap between kernel end and module start" * 12a6d2940b5f02b4b9f71ce098e3bb02bc24a9ea 12a6d29 "perf record: Fix module size on s390" [Test Case] * start a benchmark (mem_alloc, but it doesn't really matter what) * execute perf top in a second terminal * the output of perf top is correct * now stop the benchmark * and perf top shows an error message, like "Not enough memory for annotating '__irf_end' symbol!)" * and perf top can't be exited anymore [Regression Potential] * The regression potential can be considered as medium since this happens only while using the perf top tool * and just 3 files are changed, and one of them is arch/s390/util/machine.c * but symbol and machine header in /tools/perf/util modified and several loc added [Other Info] * cherry-pick was possible to bionic-master-next and to disco-master- next (but used '--strategy=recursive -X theirs' for disco) * adding the patches to disco is to avoid regressions _ perf top hangs and shows error messages ---uname output--- Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- I start a benchmark (mem_alloc, but it really doesn't matter) and then issue perf top in a second terminal, the output from perf top is correct. Now I stop the benchmark: perf top shows a error message (Not enough memory for annotating '__irf_end' symbol!) and I can't quit from perf top anymore Following analyse took place: No problem with current kernel . Bi-Secting of perf tool took place and following commit was found: commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad) Author: Arnaldo Carvalho de Melo Date: Tue Oct 16 17:08:29 2018 -0300 perf tools: Stop fallbacking to kallsyms for vdso symbols lookup When you apply this patch the issue is gone, however it is contained in these versions: git tag --contains edeb0c90df3581b821 v4.19 v4.20 The level I was debugging was kernel 4.15 which does not contain this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1828166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840454] Re: kernel 5.2 disallows thermald's direct MSR writes
Can you try 5.3rc kernel such as https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.3-rc4/? I believe the patchset https://lore.kernel.org/linux- pm/1562766278-7099-1-git-send-email-rui.zh...@intel.com/T/#t is needed, which got merged in 5.3. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1840454 Title: kernel 5.2 disallows thermald's direct MSR writes Status in thermald package in Ubuntu: New Bug description: thermald/kernel are spamming dmesg now because MSR write is disallowed. jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | wc -l 8688 jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | tail Aug 16 14:48:57 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:48:57 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:05 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:05 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:13 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:13 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:21 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:21 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1840454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681909] Re: kdump is not captured in remote host when kdump over ssh is configured
** Tags added: sts-sponsor-slashd -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1681909 Title: kdump is not captured in remote host when kdump over ssh is configured Status in The Ubuntu-power-systems project: In Progress Status in makedumpfile package in Ubuntu: Fix Committed Status in makedumpfile source package in Xenial: Won't Fix Status in makedumpfile source package in Bionic: In Progress Status in makedumpfile source package in Cosmic: Won't Fix Status in makedumpfile source package in Disco: In Progress Status in makedumpfile source package in Eoan: Fix Committed Bug description: [Impact] * Kdump over network (like NFS mount or SSH dump) relies on network- online target from systemd. Even so, there are some NICs that report "Link Up" state but aren't ready to transmit packets. This is a generally bad behavior that is credited probably to NIC firmware delays, usually not fixable from drivers. Some adapters known to act like this are bnx2x, tg3 and ixgbe. * Kdump is a mechanism that may be a last resort to debug complex/hard to reproduce issues, so it's interesting to increase its reliability / resilience. We then propose here a solution/quirk to this issue on network dump by adding a retry/delay mechanism; if it's a network dump, kdump will retry some times and sleep between the attempts in order to exclude the case of NICs that aren't ready yet but will soon be able to transmit packets. * Although first reported by IBM in PowerPC arch, the scope for this issue is the NIC, and it was later reported in x86 arch too. [Test case] Usually it's difficult to naturally reproduce this issue in a deterministic way, but we have an artificial test case on comment #24 of this LP. Also, we have a report from this bug in which the user managed to reproduce the problem consistently - it's fixed after testing our solution. [Regression potential] There's not a clear regression potential here since it's just a retry/delay mechanism. Some potential problems may come from bad coding in the script. The delay between attempts is only 3 sec per iteration, so it shouldn't block the kdump progress for a high amount of time at once. [Other information] Salsa Debian commit: https://salsa.debian.org/debian/makedumpfile/commit/d63ba95337988be1eac8c8c76d90825ff5c6d17f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1681909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840324] Re: bionic/linux-azure: 5.0.0-1017.18~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1840323 (azure-kernel), bug 1840365 (linux-azure-edge) -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1840326 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Thursday, 15. August 2019 21:19 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building + promote-to-proposed: Holding -- master bug not ready for proposed trackers: bionic/linux-azure-edge: bug 1840365 bionic/linux-azure/azure-kernel: bug 1840323 variant: debs -- 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/1840324 Title: bionic/linux-azure: 5.0.0-1017.18~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1840323 (azure-kernel), bug 1840365 (linux-azure- edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840326 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Thursday, 15. August 2019 21:19 UTC reason: promote-to-proposed: Holding -- master bug not ready for proposed trackers: bionic/linux-azure-edge: bug 1840365 bionic/linux-azure/azure-kernel: bug 1840323 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839773] Re: MicroSD not mounted when inserted, used to work correctly
I'm not sure, you can close it, I'll eventually file a new one if this behaviour happens again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839773 Title: MicroSD not mounted when inserted, used to work correctly Status in linux package in Ubuntu: Confirmed Bug description: Using Ubuntu+1 (19.10 Eoan), I inserted my Sandisk 32GB microSD with an adaptor in my laptop's SD slot, but it was not mounted nor apparently detected. I'm certain that until few weeks ago it was working correctly, so I suppose the cause to be an update regression. I tested the same card on another laptop using Ubuntu 18.04 LTS and it works correctly. Also, I have tested another card (16GB) on the 19.10 laptop, and it's detected and mounted correctly. Summary: - 16GB SD card, FAT32 - Works with all Ubuntu versions - 32GB microSD with adaptor, FAT32 - Works in 18.04, stopped working with 19.10, at least 2 weeks ago was still working. I'd be happy to help debugging this issue. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-10-generic 5.2.0-10.11 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fabio 2086 F pulseaudio /dev/snd/controlC0: fabio 2086 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Aug 11 19:50:53 2019 GvfsMonitorError: This tool has been deprecated, use 'gio mount' instead. See 'gio help mount' for more info. GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HibernationDevice: RESUME=UUID=0e34c56e-8605-499f-9588-f09829ff1e81 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2019-02-03 (188 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:57b4 Realtek Semiconductor Corp. USB Camera Bus 001 Device 006: ID 13d3:3408 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-10-generic root=UUID=3eab3ace-7b67-4e6a-aea7-d31b73cc4819 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.2.0-10-generic N/A linux-backports-modules-5.2.0-10-generic N/A linux-firmware1.181 SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 19:51:12.078: The udisks-daemon is running (name-owner :1.10). UpgradeStatus: Upgraded to eoan on 2019-07-21 (21 days ago) dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550JK dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839773/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840001] Re: trusty/linux-azure: 4.15.0-1056.61~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-trusty ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1840002 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Holding before Promote to Proposed - phase-changed: Friday, 16. August 2019 12:31 UTC + phase: Ready for Promote to Proposed + phase-changed: Friday, 16. August 2019 14:41 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait + promote-to-proposed: Pending -- ready for review variant: debs -- 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/1840001 Title: trusty/linux-azure: 4.15.0-1056.61~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1840002 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Promote to Proposed phase-changed: Friday, 16. August 2019 14:41 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840324] Re: bionic/linux-azure: 5.0.0-1017.18~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1840323 (azure-kernel), bug 1840365 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1840326 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Thursday, 15. August 2019 21:19 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa lrm:failed + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building trackers: bionic/linux-azure-edge: bug 1840365 bionic/linux-azure/azure-kernel: bug 1840323 variant: debs -- 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/1840324 Title: bionic/linux-azure: 5.0.0-1017.18~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1840323 (azure-kernel), bug 1840365 (linux-azure- edge) -- swm properties -- kernel-stable-master-bug: 1840326 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Thursday, 15. August 2019 21:19 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building trackers: bionic/linux-azure-edge: bug 1840365 bionic/linux-azure/azure-kernel: bug 1840323 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839980] Re: bionic/linux-oem: 4.15.0-1051.60 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1840006 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem - phase: Holding before Promote to Proposed - phase-changed: Friday, 16. August 2019 08:31 UTC + phase: Ready for Promote to Proposed + phase-changed: Friday, 16. August 2019 14:41 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,meta:depwait,signed:depwait + promote-to-proposed: Pending -- ready for review variant: debs -- 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/1839980 Title: bionic/linux-oem: 4.15.0-1051.60 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1840006 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Ready for Promote to Proposed phase-changed: Friday, 16. August 2019 14:41 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838133] Re: realtek r8822be kernel module fails after update to linux kernel-headers 5.0.0-21
I get other errors that cause my desktop to freeze a few seconds after login on that kernel as I did when I tried 5.3.0-rc4 mainline, but I was able to at least see that the wifi did say it was connected with the kernel you provided. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838133 Title: realtek r8822be kernel module fails after update to linux kernel- headers 5.0.0-21 Status in linux package in Ubuntu: Triaged Bug description: On July 24th I upgraded to the latest linux-headers-5.0.0-21 as part of the dist-upgrade for latest packages in Disco Dingo 19.04. I didn't notice that wifi was no longer working because at work I exclusively use a wired Ethernet connection. Today, however, when I tried to use my realtek r8822be wireless card, I discovered that it was totally unresponsive and did not work with wpa_supplicant / wpa_cli even when invoked manually from the command line (let alone with NetworkManager). When the problem occurred, I was using 19.04's latest kernel 5.0.0-21. I then rebooted and selected kernel 5.0.0-20 from GRUB menu. "uname -a" shows that I am using the previous kernel version: Linux pj 5.0.0-20-generic #21-Ubuntu SMP Mon Jun 24 09:32:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux With this kernel version as well as linux-headers-5.0.0.20, linux- headers-5.0.0-20-generic, my realtek wireless card works fine. While booted into 5.0.0-20 kernel, here are the realtek kernel modules that are loaded: # lsmod | grep r8 r8822be 692224 0 mac80211 806912 1 r8822be cfg80211 671744 2 mac80211,r8822be r8169 81920 0 Hopefully this realtek wireless regression can get fixed in the next minor kernel version. Let me know if you need any more information. Best Regards, Jun To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840001] Re: trusty/linux-azure: 4.15.0-1056.61~14.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1840002 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Friday, 16. August 2019 12:31 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait variant: debs -- 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/1840001 Title: trusty/linux-azure: 4.15.0-1056.61~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1840002 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Friday, 16. August 2019 12:31 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839980] Re: bionic/linux-oem: 4.15.0-1051.60 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1840006 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Holding before Promote to Proposed phase-changed: Friday, 16. August 2019 08:31 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:depwait,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,meta:depwait,signed:depwait variant: debs -- 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/1839980 Title: bionic/linux-oem: 4.15.0-1051.60 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1840006 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Holding before Promote to Proposed phase-changed: Friday, 16. August 2019 08:31 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,meta:depwait,signed:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795292] Re: ELAN469D touch pad not working
I've uploaded new kernel to the same address, please give it a try. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1795292 Title: ELAN469D touch pad not working Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I installed Bionic Beaver and now upgraded to Cosmic Cuttlefish on this Lenovo Ideapad 330S-15ARR laptop. The touch pad doesn't work in either. Some possibly relevant info from dmesg: i2c_hid i2c-ELAN469D:00: i2c-ELAN469D:00 supply vdd not found, using dummy regulator i2c_designware AMDI0010:01: controller timed out ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-7-generic 4.18.0-7.8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xorbit 2086 F pulseaudio /dev/snd/pcmC1D0p: xorbit 2086 F...m pulseaudio /dev/snd/controlC0: xorbit 2086 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 30 23:14:26 2018 InstallationDate: Installed on 2018-09-20 (10 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81FB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic processor.max_cstate=1 rcu_nocbs=0-7 pcie_aspm=off pci=noaer quiet splash vt.handoff=1 elan_i2c.dyndbg=+p RelatedPackageVersions: linux-restricted-modules-4.18.0-7-generic N/A linux-backports-modules-4.18.0-7-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-09-30 (0 days ago) dmi.bios.date: 06/08/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7WCN22WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7WCN22WW:bd06/08/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR: dmi.product.family: ideapad 330S-15ARR dmi.product.name: 81FB dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR dmi.product.version: Lenovo ideapad 330S-15ARR dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-20 (13 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: cosmic Uname: Linux 4.19.0-041900rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to cosmic on 2018-09-30 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1795292/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833617] Re: [amdgpu] screen freeze after suspend
Please test latest mainline kernel again: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc4/ And attach `journalctl -b -1 -k` once the issue happens. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833617 Title: [amdgpu] screen freeze after suspend Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: It's most likely amdgup driver needs an upgrade. Problem occurs since kernel upgrade to 5.0 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12 Uname: Linux 5.0.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Thu Jun 20 13:46:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev eb) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] InstallationDate: Installed on 2019-06-06 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Inspiron 3180 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-18-generic root=UUID=a16bd163-e82f-4ec1-9c5f-c9bd32e225fa ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833617/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815214] Re: Lenovo ThinkPad T480/T480s/X1: Throttling CPU issue
*** This bug is a duplicate of bug 1763144 *** https://bugs.launchpad.net/bugs/1763144 AFAICT, this bug report is a duplicate of bug 1763144. Investigation and inquiries have shown that Linux is behaving correctly here. ** This bug has been marked a duplicate of bug 1763144 Significantly lower power and thermal limits on ThinkPad T480s (and probably others) than on Windows -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1815214 Title: Lenovo ThinkPad T480/T480s/X1: Throttling CPU issue Status in linux package in Ubuntu: Confirmed Status in thermald package in Ubuntu: Confirmed Status in thermald package in Arch Linux: New Bug description: On Linux OS the CPU package power limit (PL1/2) is set wrong reducing drastically CPU performance under load. Apparently many Lenovo laptops (certified for Ubuntu) are affected. The problem is described in details here: https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/ There is "hacky" workaround (not compatible with SecureBoot, a Python script writing MSR registers periodically) : https://github.com/erpalma/throttled There is also a thread on Lenovo forum: https://forums.lenovo.com/t5 /Linux-Discussion/X1C6-T480s-low-cTDP-and-trip-temperature-in- Linux/td-p/4028489 I confirm the issue affect my machine running the latest kernel (4.15.0-45-generic, although bug affects previous releases as well) and using the latest firmware from Lenovo (1.19). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-45-generic 4.15.0-45.48 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: afiergol 4050 F pulseaudio /dev/snd/pcmC0D0p: afiergol 4050 F...m pulseaudio /dev/snd/controlC0: afiergol 4050 F pulseaudio CurrentDesktop: GNOME Date: Fri Feb 8 17:14:17 2019 HibernationDevice: RESUME=UUID=7b4a9d17-f6d7-42ed-8f12-34f46c41cc6c InstallationDate: Installed on 2018-04-05 (309 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: LENOVO 20L6S04200 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nogpumanager intel_iommu=on,igfx_off iommu=pt kvm.ignore_msrs=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-22 (170 days ago) dmi.bios.date: 11/07/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET44W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L6S04200 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET44W(1.19):bd11/07/2018:svnLENOVO:pn20L6S04200:pvrThinkPadT480:rvnLENOVO:rn20L6S04200:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L6S04200 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840454] [NEW] kernel 5.2 disallows thermald's direct MSR writes
Public bug reported: thermald/kernel are spamming dmesg now because MSR write is disallowed. jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | wc -l 8688 jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | tail Aug 16 14:48:57 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:48:57 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:05 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:05 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:13 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:13 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:21 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:21 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr ** Affects: thermald (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1840454 Title: kernel 5.2 disallows thermald's direct MSR writes Status in thermald package in Ubuntu: New Bug description: thermald/kernel are spamming dmesg now because MSR write is disallowed. jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | wc -l 8688 jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | tail Aug 16 14:48:57 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:48:57 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:05 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:05 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:13 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:13 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:21 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:21 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1840454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840001] Re: trusty/linux-azure: 4.15.0-1056.61~14.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1840002 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Friday, 16. August 2019 12:31 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:depwait variant: debs -- 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/1840001 Title: trusty/linux-azure: 4.15.0-1056.61~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1840002 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Friday, 16. August 2019 12:31 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840122] Re: System fails to reboot from live session or ubiquity-dm - squashfs_read_data failed to read block
** Tags added: id-5d557981385f317578944153 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840122 Title: System fails to reboot from live session or ubiquity-dm - squashfs_read_data failed to read block Status in casper package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Last known good image: Eoan Ubuntu Desktop 20190715 Test Case: 1. Boot eoan desktop to a live session 2. Wait a couple of minutes until snapd settles 3. Reboot the system from the system menu or from the command line Expected result: The system reboots Actual result: The systems fails to reboot or shutdown and displays some errors about failing to unmount /cdrom and squashfs errors in a loop. Unmounting /cdrom... [FAILED] Failed unmounting /cdrom. [ OK ] Started Shuts down the "li…" preinstalled system cleanly. [ OK ] Reached target Final Step. [ OK ] Started Reboot. [ OK ] Reached target Reboot. [ 115.744188] print_req_error: I/O error, dev sr0, sector 1508872 flags 80700 [ 115.768139] print_req_error: I/O error, dev sr0, sector 1508872 flags 0 [ 115.771469] print_req_error: I/O error, dev loop0, sector 1501550 flags 0 [ 115.775824] SQUASHFS error: squashfs_read_data failed to read block 0x2dd2d998 This also causes daily tests to fail. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: casper 1.414 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 14 08:31:30 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190813) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: casper UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190814) Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Tags: eoan Uname: Linux 5.2.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1788 F pulseaudio CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 IwConfig: lono wireless extensions. ens3 no wireless extensions. LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190814) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd --- keyboard-configuration/layoutcode=fr keyboard-configuration/variantcode=oss ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 RelatedPackageVersions: linux-restricted-modules-5.2.0-10-generic N/A linux-backports-modules-5.2.0-10-generic N/A linux-firmware1.181 RfKill: Tags: eoan Uname: Linux 5.2.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-disco dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-disco:cvnQEMU:ct1:cvrpc-i440fx-disco: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-disco dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1788 F pulseaudio CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME
[Kernel-packages] [Bug 1839985] Re: bionic/linux-aws: 4.15.0-1046.48 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839983 (xenial/linux-aws-hwe) derivatives: bug 1839981 (aws-kernel) -- swm properties -- kernel-stable-master-bug: 1840006 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Holding before Promote to Proposed phase-changed: Friday, 16. August 2019 10:30 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building,main:building + promote-to-proposed: Ongoing -- builds not complete in ppa main:building trackers: bionic/linux-aws/aws-kernel: bug 1839981 xenial/linux-aws-hwe: bug 1839983 variant: debs -- 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/1839985 Title: bionic/linux-aws: 4.15.0-1046.48 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839983 (xenial/linux-aws-hwe) derivatives: bug 1839981 (aws-kernel) -- swm properties -- kernel-stable-master-bug: 1840006 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Holding before Promote to Proposed phase-changed: Friday, 16. August 2019 10:30 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building trackers: bionic/linux-aws/aws-kernel: bug 1839981 xenial/linux-aws-hwe: bug 1839983 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840001] Re: trusty/linux-azure: 4.15.0-1056.61~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1840002 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Packaging - phase-changed: Friday, 16. August 2019 10:25 UTC + phase: Holding before Promote to Proposed + phase-changed: Friday, 16. August 2019 12:31 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building,signed:depwait variant: debs -- 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/1840001 Title: trusty/linux-azure: 4.15.0-1056.61~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1840002 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Friday, 16. August 2019 12:31 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building,signed:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)
** Changed in: linux-oem-osp1 (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/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) Status in DRI: Fix Released Status in HWE Next: New Status in X.Org X server: Unknown Status in linux package in Ubuntu: Triaged Status in linux-oem-osp1 package in Ubuntu: New Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Invalid Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi WORKAROUND (UBUNTU 18.04+): Log in to "Ubuntu on Wayland" instead of "Ubuntu". --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839980] Re: bionic/linux-oem: 4.15.0-1051.60 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1840006 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Holding before Promote to Proposed phase-changed: Friday, 16. August 2019 08:31 UTC + reason: + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:depwait,signed:depwait variant: debs -- 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/1839980 Title: bionic/linux-oem: 4.15.0-1051.60 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1840006 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Holding before Promote to Proposed phase-changed: Friday, 16. August 2019 08:31 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:depwait,signed:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1811730] Re: Thermald does not set max CPU after reseting the voltage using RAPL
That was tested on 4.15, which is the default kernel in ubuntu 18.04. When tested on 5.3rc4, without dptfxtract seems to be good enough [1], although after using dptfxtract, the system is more consistent [2]. So do you suggest users to always have dptfxtract installed? It shouldn't make the system perform worse, am I right? [1] https://docs.google.com/spreadsheets/d/1sSZe2gqfM8NWqaDyUfXx-Q2iGUkKvrREjJsobHfIZiQ/edit#gid=1910979586 [2] https://docs.google.com/spreadsheets/d/1sSZe2gqfM8NWqaDyUfXx-Q2iGUkKvrREjJsobHfIZiQ/edit#gid=907221455 On Fri, Aug 16, 2019 at 12:56 AM Srinivas Pandruvada < srinivas.pandruv...@linux.intel.com> wrote: > Correct. > I think you are using with 5.3 kernel or using workaround option. > Without dptfxtract output or user manually created thermal-conf.xml or > using aurogenerated, this is risky to play with power as the skin will > hit limit. > > Thanks, > Srinivas > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1811730 Title: Thermald does not set max CPU after reseting the voltage using RAPL Status in thermald package in Ubuntu: Confirmed Status in thermald source package in Bionic: Fix Committed Bug description: Hi, I was using Ubuntu 18.10 thermald package, but I noted that, after few seconds at max CPU usage (max temp), thermald send the signal to RALP to reduce the voltage of the CPU. It set the freq to minimum (800MHz in my case). But when the CPU is idle and temp is lowered (35-40ºC) it did not send the signal to resume normal operation of the CPU. I compiled the latest version of thermald from git (https://github.com/intel/thermal_daemon) and now everything works fine. I started to thought that the problem was the hardware or BIOS problem, as I disabled the CPU scaling on the BIOS, but intel_pstate continued doing freq scaling (I think for Turbo mode). But the real problem was Thermald. The latest version from git works really fine and it automatically disables and enable the Intel Turbo state and balance the freqs and fan control fine. My hardware is a Lenovo Thinkpad P52 with i7-8850H. I tested it using Ubuntu kernel and Kernel 4.20 optimized for i7 processor but with Ubuntu default config (except processor family="Core2/newer Xeon", Preemption Model="Preemptible Kernel (Low- Latency Desktop)" and Timer frequency="1000HZ". (Only changed those settings from make oldconfig and make deb-pkg). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: thermald (not installed) ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 14 23:45:01 2019 InstallationDate: Installed on 2018-12-11 (34 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: thermald UpgradeStatus: No upgrade log present (probably fresh install) - SRU Justification == [Impact] * As described by the original bug reporter, CPU usage of Lenovo P52 is sub-optimal under heavy load. * My observation is the machine exhibits a sharp drop of power usage and CPU frequency and takes time to slowly ramp up again (refer to the chart at https://bit.ly/2OJphB8) * Fixed by bisecting and backporting fixes from thermald project. [Test Case] * One can stress the CPU load of the machine and collect the CPU frequency and power usage over time to check for any anamoly. The script at https://people.canonical.com/~ypwong/p52_test_cpu.sh can help with this. * With the fix, the behaviour should be like this: https://bit.ly/2KA9EXB, a consistent power usage can be maintained. [Regression Potential] * Medium. The fix consists of 7 commits cherry-picked from upstream, these changes will affect any machines using RAPL cooling device. The impact may not be obvious in normal daily usage but will be manifested during heavy load, suggest a longer verification period so that more people can discover any adverse effect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1811730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839985] Re: bionic/linux-aws: 4.15.0-1046.48 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839983 (xenial/linux-aws-hwe) derivatives: bug 1839981 (aws-kernel) -- swm properties -- kernel-stable-master-bug: 1840006 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Holding before Promote to Proposed phase-changed: Friday, 16. August 2019 10:30 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building,main:building trackers: bionic/linux-aws/aws-kernel: bug 1839981 xenial/linux-aws-hwe: bug 1839983 variant: debs -- 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/1839985 Title: bionic/linux-aws: 4.15.0-1046.48 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839983 (xenial/linux-aws-hwe) derivatives: bug 1839981 (aws-kernel) -- swm properties -- kernel-stable-master-bug: 1840006 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Holding before Promote to Proposed phase-changed: Friday, 16. August 2019 10:30 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building,main:building trackers: bionic/linux-aws/aws-kernel: bug 1839981 xenial/linux-aws-hwe: bug 1839983 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840438] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1840438/+attachment/5282842/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840438 Title: linux-image-4.4.0-159-generic BUG on bcache Status in linux package in Ubuntu: Confirmed Bug description: linux-image-4.4.0-159-generic produces "BUG unable to handle kernel NULL pointer dereference" with bcache module the kernel never boots then. blacklisting the bcache module resolves the problem. For more strings please see attached image Ubuntu 4.4.0-159.187-generic 4.4.185 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 16 13:18 seq crw-rw 1 root audio 116, 33 Aug 16 13:18 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ade296a6-5255-4839-9cee-fde7af090c42 InstallationDate: Installed on 2016-06-08 (1163 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant SE316M1 Package: linux (not installed) PciMultimedia: ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-159-generic root=UUID=051b7186-7bab-4cff-af27-325b58e7f8a7 ro ipv6.disable=1 modprobe.blacklist=bcache ProcVersionSignature: Ubuntu 4.4.0-159.187-generic 4.4.185 RelatedPackageVersions: linux-restricted-modules-4.4.0-159-generic N/A linux-backports-modules-4.4.0-159-generic N/A linux-firmware 1.157.22 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial Uname: Linux 4.4.0-159-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 07/02/2013 dmi.bios.vendor: HP dmi.bios.version: R02 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR02:bd07/02/2013:svnHP:pnProLiantSE316M1:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant SE316M1 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840438/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840438] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1840438/+attachment/5282841/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840438 Title: linux-image-4.4.0-159-generic BUG on bcache Status in linux package in Ubuntu: Confirmed Bug description: linux-image-4.4.0-159-generic produces "BUG unable to handle kernel NULL pointer dereference" with bcache module the kernel never boots then. blacklisting the bcache module resolves the problem. For more strings please see attached image Ubuntu 4.4.0-159.187-generic 4.4.185 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 16 13:18 seq crw-rw 1 root audio 116, 33 Aug 16 13:18 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ade296a6-5255-4839-9cee-fde7af090c42 InstallationDate: Installed on 2016-06-08 (1163 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant SE316M1 Package: linux (not installed) PciMultimedia: ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-159-generic root=UUID=051b7186-7bab-4cff-af27-325b58e7f8a7 ro ipv6.disable=1 modprobe.blacklist=bcache ProcVersionSignature: Ubuntu 4.4.0-159.187-generic 4.4.185 RelatedPackageVersions: linux-restricted-modules-4.4.0-159-generic N/A linux-backports-modules-4.4.0-159-generic N/A linux-firmware 1.157.22 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial Uname: Linux 4.4.0-159-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 07/02/2013 dmi.bios.vendor: HP dmi.bios.version: R02 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR02:bd07/02/2013:svnHP:pnProLiantSE316M1:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant SE316M1 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840438/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840438] HookError_generic.txt
apport information ** Attachment added: "HookError_generic.txt" https://bugs.launchpad.net/bugs/1840438/+attachment/5282840/+files/HookError_generic.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/1840438 Title: linux-image-4.4.0-159-generic BUG on bcache Status in linux package in Ubuntu: Confirmed Bug description: linux-image-4.4.0-159-generic produces "BUG unable to handle kernel NULL pointer dereference" with bcache module the kernel never boots then. blacklisting the bcache module resolves the problem. For more strings please see attached image Ubuntu 4.4.0-159.187-generic 4.4.185 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 16 13:18 seq crw-rw 1 root audio 116, 33 Aug 16 13:18 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ade296a6-5255-4839-9cee-fde7af090c42 InstallationDate: Installed on 2016-06-08 (1163 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant SE316M1 Package: linux (not installed) PciMultimedia: ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-159-generic root=UUID=051b7186-7bab-4cff-af27-325b58e7f8a7 ro ipv6.disable=1 modprobe.blacklist=bcache ProcVersionSignature: Ubuntu 4.4.0-159.187-generic 4.4.185 RelatedPackageVersions: linux-restricted-modules-4.4.0-159-generic N/A linux-backports-modules-4.4.0-159-generic N/A linux-firmware 1.157.22 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial Uname: Linux 4.4.0-159-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 07/02/2013 dmi.bios.vendor: HP dmi.bios.version: R02 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR02:bd07/02/2013:svnHP:pnProLiantSE316M1:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant SE316M1 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840438/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840438] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1840438/+attachment/5282845/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840438 Title: linux-image-4.4.0-159-generic BUG on bcache Status in linux package in Ubuntu: Confirmed Bug description: linux-image-4.4.0-159-generic produces "BUG unable to handle kernel NULL pointer dereference" with bcache module the kernel never boots then. blacklisting the bcache module resolves the problem. For more strings please see attached image Ubuntu 4.4.0-159.187-generic 4.4.185 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 16 13:18 seq crw-rw 1 root audio 116, 33 Aug 16 13:18 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ade296a6-5255-4839-9cee-fde7af090c42 InstallationDate: Installed on 2016-06-08 (1163 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant SE316M1 Package: linux (not installed) PciMultimedia: ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-159-generic root=UUID=051b7186-7bab-4cff-af27-325b58e7f8a7 ro ipv6.disable=1 modprobe.blacklist=bcache ProcVersionSignature: Ubuntu 4.4.0-159.187-generic 4.4.185 RelatedPackageVersions: linux-restricted-modules-4.4.0-159-generic N/A linux-backports-modules-4.4.0-159-generic N/A linux-firmware 1.157.22 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial Uname: Linux 4.4.0-159-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 07/02/2013 dmi.bios.vendor: HP dmi.bios.version: R02 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR02:bd07/02/2013:svnHP:pnProLiantSE316M1:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant SE316M1 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840438/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840438] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1840438/+attachment/5282844/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840438 Title: linux-image-4.4.0-159-generic BUG on bcache Status in linux package in Ubuntu: Confirmed Bug description: linux-image-4.4.0-159-generic produces "BUG unable to handle kernel NULL pointer dereference" with bcache module the kernel never boots then. blacklisting the bcache module resolves the problem. For more strings please see attached image Ubuntu 4.4.0-159.187-generic 4.4.185 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 16 13:18 seq crw-rw 1 root audio 116, 33 Aug 16 13:18 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ade296a6-5255-4839-9cee-fde7af090c42 InstallationDate: Installed on 2016-06-08 (1163 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant SE316M1 Package: linux (not installed) PciMultimedia: ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-159-generic root=UUID=051b7186-7bab-4cff-af27-325b58e7f8a7 ro ipv6.disable=1 modprobe.blacklist=bcache ProcVersionSignature: Ubuntu 4.4.0-159.187-generic 4.4.185 RelatedPackageVersions: linux-restricted-modules-4.4.0-159-generic N/A linux-backports-modules-4.4.0-159-generic N/A linux-firmware 1.157.22 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial Uname: Linux 4.4.0-159-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 07/02/2013 dmi.bios.vendor: HP dmi.bios.version: R02 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR02:bd07/02/2013:svnHP:pnProLiantSE316M1:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant SE316M1 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840438/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840438] Re: linux-image-4.4.0-159-generic BUG on bcache
apport information ** Tags added: apport-collected ** Description changed: linux-image-4.4.0-159-generic produces "BUG unable to handle kernel NULL pointer dereference" with bcache module the kernel never boots then. blacklisting the bcache module resolves the problem. For more strings please see attached image Ubuntu 4.4.0-159.187-generic 4.4.185 + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Aug 16 13:18 seq + crw-rw 1 root audio 116, 33 Aug 16 13:18 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.20.1-0ubuntu2.19 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=ade296a6-5255-4839-9cee-fde7af090c42 + InstallationDate: Installed on 2016-06-08 (1163 days ago) + InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) + IwConfig: Error: [Errno 2] No such file or directory + MachineType: HP ProLiant SE316M1 + Package: linux (not installed) + PciMultimedia: + + ProcFB: 0 radeondrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-159-generic root=UUID=051b7186-7bab-4cff-af27-325b58e7f8a7 ro ipv6.disable=1 modprobe.blacklist=bcache + ProcVersionSignature: Ubuntu 4.4.0-159.187-generic 4.4.185 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-159-generic N/A + linux-backports-modules-4.4.0-159-generic N/A + linux-firmware 1.157.22 + RfKill: Error: [Errno 2] No such file or directory + Tags: xenial xenial + Uname: Linux 4.4.0-159-generic x86_64 + UnreportableReason: The report belongs to a package that is not installed. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: False + dmi.bios.date: 07/02/2013 + dmi.bios.vendor: HP + dmi.bios.version: R02 + dmi.chassis.type: 23 + dmi.chassis.vendor: HP + dmi.modalias: dmi:bvnHP:bvrR02:bd07/02/2013:svnHP:pnProLiantSE316M1:pvr:cvnHP:ct23:cvr: + dmi.product.name: ProLiant SE316M1 + dmi.sys.vendor: HP ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1840438/+attachment/5282838/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840438 Title: linux-image-4.4.0-159-generic BUG on bcache Status in linux package in Ubuntu: Confirmed Bug description: linux-image-4.4.0-159-generic produces "BUG unable to handle kernel NULL pointer dereference" with bcache module the kernel never boots then. blacklisting the bcache module resolves the problem. For more strings please see attached image Ubuntu 4.4.0-159.187-generic 4.4.185 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 16 13:18 seq crw-rw 1 root audio 116, 33 Aug 16 13:18 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ade296a6-5255-4839-9cee-fde7af090c42 InstallationDate: Installed on 2016-06-08 (1163 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant SE316M1 Package: linux (not installed) PciMultimedia: ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-159-generic root=UUID=051b7186-7bab-4cff-af27-325b58e7f8a7 ro ipv6.disable=1 modprobe.blacklist=bcache ProcVersionSignature: Ubuntu 4.4.0-159.187-generic 4.4.185 RelatedPackageVersions: linux-restricted-modules-4.4.0-159-generic N/A linux-backports-modules-4.4.0-159-generic N/A linux-firmware 1.157.22 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial Uname: Linux 4.4.0-159-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 07/02/2013 dmi.bios.vendor: HP dmi.bios.version: R02 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR02:bd07/02/2013:svnHP:pnProLiantSE316M1:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant SE316M1 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840438/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1840438] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1840438/+attachment/5282843/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840438 Title: linux-image-4.4.0-159-generic BUG on bcache Status in linux package in Ubuntu: Confirmed Bug description: linux-image-4.4.0-159-generic produces "BUG unable to handle kernel NULL pointer dereference" with bcache module the kernel never boots then. blacklisting the bcache module resolves the problem. For more strings please see attached image Ubuntu 4.4.0-159.187-generic 4.4.185 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 16 13:18 seq crw-rw 1 root audio 116, 33 Aug 16 13:18 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ade296a6-5255-4839-9cee-fde7af090c42 InstallationDate: Installed on 2016-06-08 (1163 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant SE316M1 Package: linux (not installed) PciMultimedia: ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-159-generic root=UUID=051b7186-7bab-4cff-af27-325b58e7f8a7 ro ipv6.disable=1 modprobe.blacklist=bcache ProcVersionSignature: Ubuntu 4.4.0-159.187-generic 4.4.185 RelatedPackageVersions: linux-restricted-modules-4.4.0-159-generic N/A linux-backports-modules-4.4.0-159-generic N/A linux-firmware 1.157.22 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial Uname: Linux 4.4.0-159-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 07/02/2013 dmi.bios.vendor: HP dmi.bios.version: R02 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR02:bd07/02/2013:svnHP:pnProLiantSE316M1:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant SE316M1 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840438/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840438] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1840438/+attachment/5282847/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840438 Title: linux-image-4.4.0-159-generic BUG on bcache Status in linux package in Ubuntu: Confirmed Bug description: linux-image-4.4.0-159-generic produces "BUG unable to handle kernel NULL pointer dereference" with bcache module the kernel never boots then. blacklisting the bcache module resolves the problem. For more strings please see attached image Ubuntu 4.4.0-159.187-generic 4.4.185 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 16 13:18 seq crw-rw 1 root audio 116, 33 Aug 16 13:18 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ade296a6-5255-4839-9cee-fde7af090c42 InstallationDate: Installed on 2016-06-08 (1163 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant SE316M1 Package: linux (not installed) PciMultimedia: ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-159-generic root=UUID=051b7186-7bab-4cff-af27-325b58e7f8a7 ro ipv6.disable=1 modprobe.blacklist=bcache ProcVersionSignature: Ubuntu 4.4.0-159.187-generic 4.4.185 RelatedPackageVersions: linux-restricted-modules-4.4.0-159-generic N/A linux-backports-modules-4.4.0-159-generic N/A linux-firmware 1.157.22 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial Uname: Linux 4.4.0-159-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 07/02/2013 dmi.bios.vendor: HP dmi.bios.version: R02 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR02:bd07/02/2013:svnHP:pnProLiantSE316M1:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant SE316M1 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840438/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840438] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1840438/+attachment/5282846/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840438 Title: linux-image-4.4.0-159-generic BUG on bcache Status in linux package in Ubuntu: Confirmed Bug description: linux-image-4.4.0-159-generic produces "BUG unable to handle kernel NULL pointer dereference" with bcache module the kernel never boots then. blacklisting the bcache module resolves the problem. For more strings please see attached image Ubuntu 4.4.0-159.187-generic 4.4.185 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 16 13:18 seq crw-rw 1 root audio 116, 33 Aug 16 13:18 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ade296a6-5255-4839-9cee-fde7af090c42 InstallationDate: Installed on 2016-06-08 (1163 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant SE316M1 Package: linux (not installed) PciMultimedia: ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-159-generic root=UUID=051b7186-7bab-4cff-af27-325b58e7f8a7 ro ipv6.disable=1 modprobe.blacklist=bcache ProcVersionSignature: Ubuntu 4.4.0-159.187-generic 4.4.185 RelatedPackageVersions: linux-restricted-modules-4.4.0-159-generic N/A linux-backports-modules-4.4.0-159-generic N/A linux-firmware 1.157.22 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial Uname: Linux 4.4.0-159-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 07/02/2013 dmi.bios.vendor: HP dmi.bios.version: R02 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR02:bd07/02/2013:svnHP:pnProLiantSE316M1:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant SE316M1 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840438/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840438] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1840438/+attachment/5282839/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840438 Title: linux-image-4.4.0-159-generic BUG on bcache Status in linux package in Ubuntu: Confirmed Bug description: linux-image-4.4.0-159-generic produces "BUG unable to handle kernel NULL pointer dereference" with bcache module the kernel never boots then. blacklisting the bcache module resolves the problem. For more strings please see attached image Ubuntu 4.4.0-159.187-generic 4.4.185 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 16 13:18 seq crw-rw 1 root audio 116, 33 Aug 16 13:18 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ade296a6-5255-4839-9cee-fde7af090c42 InstallationDate: Installed on 2016-06-08 (1163 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant SE316M1 Package: linux (not installed) PciMultimedia: ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-159-generic root=UUID=051b7186-7bab-4cff-af27-325b58e7f8a7 ro ipv6.disable=1 modprobe.blacklist=bcache ProcVersionSignature: Ubuntu 4.4.0-159.187-generic 4.4.185 RelatedPackageVersions: linux-restricted-modules-4.4.0-159-generic N/A linux-backports-modules-4.4.0-159-generic N/A linux-firmware 1.157.22 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial Uname: Linux 4.4.0-159-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 07/02/2013 dmi.bios.vendor: HP dmi.bios.version: R02 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR02:bd07/02/2013:svnHP:pnProLiantSE316M1:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant SE316M1 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840438/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840438] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1840438/+attachment/5282848/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840438 Title: linux-image-4.4.0-159-generic BUG on bcache Status in linux package in Ubuntu: Confirmed Bug description: linux-image-4.4.0-159-generic produces "BUG unable to handle kernel NULL pointer dereference" with bcache module the kernel never boots then. blacklisting the bcache module resolves the problem. For more strings please see attached image Ubuntu 4.4.0-159.187-generic 4.4.185 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 16 13:18 seq crw-rw 1 root audio 116, 33 Aug 16 13:18 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ade296a6-5255-4839-9cee-fde7af090c42 InstallationDate: Installed on 2016-06-08 (1163 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant SE316M1 Package: linux (not installed) PciMultimedia: ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-159-generic root=UUID=051b7186-7bab-4cff-af27-325b58e7f8a7 ro ipv6.disable=1 modprobe.blacklist=bcache ProcVersionSignature: Ubuntu 4.4.0-159.187-generic 4.4.185 RelatedPackageVersions: linux-restricted-modules-4.4.0-159-generic N/A linux-backports-modules-4.4.0-159-generic N/A linux-firmware 1.157.22 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial Uname: Linux 4.4.0-159-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 07/02/2013 dmi.bios.vendor: HP dmi.bios.version: R02 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR02:bd07/02/2013:svnHP:pnProLiantSE316M1:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant SE316M1 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840438/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839980] Re: bionic/linux-oem: 4.15.0-1051.60 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1840006 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Holding before Promote to Proposed phase-changed: Friday, 16. August 2019 08:31 UTC - reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:depwait,signed:depwait variant: debs -- 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/1839980 Title: bionic/linux-oem: 4.15.0-1051.60 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1840006 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Holding before Promote to Proposed phase-changed: Friday, 16. August 2019 08:31 UTC variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839980] Re: bionic/linux-oem: 4.15.0-1051.60 -proposed tracker
** Summary changed: - bionic/linux-oem: 4.15.0-1051.59 -proposed tracker + bionic/linux-oem: 4.15.0-1051.60 -proposed tracker -- 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/1839980 Title: bionic/linux-oem: 4.15.0-1051.60 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1840006 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Holding before Promote to Proposed phase-changed: Friday, 16. August 2019 08:31 UTC variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
