[Bug 1851749] Re: Frequently getting thermal warnings and cpu throttling messages in syslog
I am affected as well on a Dell P74G Inspiron 7460 with an i7-7500U CPU @ 2.70GHz and an integrated GPU + an Nvidia GPU using the NVidia drivers. According from information I found here https://icecat.biz/p/dell/w56752561pth-gld/inspiron- notebooks-7460-33552288.html the TDPs of my CPU are: Thermal Design Power (TDP) 15 W Configurable TDP-up frequency 2.9 GHz Configurable TDP-up25 W Configurable TDP-down 7.5 W CPU version as read from /proc/cpuinfo: vendor_id : GenuineIntel cpu family : 6 model : 142 model name : Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz stepping: 9 microcode : 0xde >From lspci, detail of the GPUs: 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02) 01:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 940MX] (rev a2) My Kernel: uname -a Linux [redacted] 5.4.0-66-generic #74-Ubuntu SMP Wed Jan 27 22:54:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Output of the commands recommended above: dmidecode looks odd returning info about WiFi: sudo dmidecode -H 11 # dmidecode 3.2 Getting SMBIOS data from sysfs. SMBIOS 2.8 present. 85 structures occupying 5497 bytes. Table at 0x000E9CA0. Handle 0x000B, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JNGFF1 - WLAN/BT/Wigig CONN Internal Connector Type: None External Reference Designator: Not Specified External Connector Type: None Port Type: Other sudo modprobe msr sudo rdmsr -f 29:24 -d 0x1a2 2 Reproducing the issue: stress -c 8 stress: info: [48012] dispatching hogs: 8 cpu, 0 io, 0 vm, 0 hdd Dmesg output: [17674.962910] mce: CPU3: Core temperature above threshold, cpu clock throttled (total events = 3987) [17674.962910] mce: CPU1: Core temperature above threshold, cpu clock throttled (total events = 3986) [17674.962912] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 7491) [17674.962913] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 7491) [17674.962914] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 7487) [17674.962915] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 7491) [17674.966955] mce: CPU1: Core temperature/speed normal [17674.966956] mce: CPU3: Core temperature/speed normal [17674.966957] mce: CPU2: Package temperature/speed normal [17674.966958] mce: CPU0: Package temperature/speed normal [17674.966958] mce: CPU3: Package temperature/speed normal [17674.966960] mce: CPU1: Package temperature/speed normal Turbostat line being used (NOTE: 100 milliseconds interval): turbostat --quiet --Summary --show Busy%,Bzy_MHz,PkgTmp,PkgWatt,CorWatt,GFXWatt,Time_Of_Day_Seconds --interval 0.1 Output of turbostat across the beginning of stress: Time_Of_Day_Seconds Busy% Bzy_MHz PkgTmp PkgWatt CorWatt GFXWatt 1622157712.441769 9.23795 51 1.750.200.11 1622157712.542624 10.77 711 52 1.840.210.12 1622157712.643427 8.98708 51 1.800.170.07 1622157712.744178 12.97 746 51 1.900.240.13 1622157712.850717 13.32 712 51 1.680.200.11 <--- START STRESS 1622157712.951114 95.99 258775 12.69 10.76 0.17 1622157713.051319 99.59 350082 19.36 17.56 0.14 1622157713.151571 99.65 350085 19.54 17.66 0.18 1622157713.252241 99.65 350088 19.76 17.82 0.14 1622157713.352490 99.59 350090 19.66 17.76 0.17 1622157713.452694 99.65 350090 19.22 17.54 0.08 1622157713.552947 99.59 350091 20.09 18.09 0.14 Output of turbostat across the throttle trigger event: Time_Of_Day_Seconds Busy% Bzy_MHz PkgTmp PkgWatt CorWatt GFXWatt 1622157718.567121 99.65 350095 19.97 17.94 0.16 1622157718.667327 99.68 350095 19.79 18.05 0.13 1622157718.767572 99.62 350095 19.76 17.94 0.13 1622157718.867776 99.65 350096 19.81 18.00 0.16 1622157718.968029 99.65 350095 20.01 17.98 0.17 1622157719.068238 99.65 350096 20.13 18.29 0.17 1622157719.169153 99.65 350097 20.35 18.44 0.21 1622157719.269796 99.65 350097 20.12 18.24 0.20 <--- THRESHOLD TRIGGERED 1622157719.370056 99.59 335590 18.04 15.99 0.18 1622157719.470352 99.53 311786 14.53 12.69 0.17 1622157719.572124 99.61 311786 14.33 12.56 0.09 1622157719.672498 99.61 310385 14.67 12.78 0.16 1622157719.772984 99.63 311885 14.46 12.71 0.13 1622157719.873219 99.62 311384 14.63 12.71 0.14 1622157719.973515 99.60 312585 14.54 12.74 0.13 --
[Bug 1848797] Re: After upgrading to 19.10, boot screen shows: "Error: symbol 'grub_file_filters' not found."
I also experienced the issue after upgrading from Kubuntu 19.04 to 19.10. I am also using LVM as other posters here. I solved the issue with the usual boot from live ISO + mount/chroot + grub-install. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848797 Title: After upgrading to 19.10, boot screen shows: "Error: symbol 'grub_file_filters' not found." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1848797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521173] Re: AER: Corrected error received: id=00e0
Dell Inspiron P74G, Kubuntu 19.04 Disco, kernel 5.0.0-13-generic. I'm affected as well by this bug, with ~50 lines per minute of errors in the syslog. I noticed only recently the issue on my Kubuntu 18.04 LTS setup (say, this October 2019). Since then I upgraded to 19.04, but with no improvement. My errors in dmesg are of the same form as stated above, with two recurring types of error statuses: pcieport :00:1c.4: AER: Corrected error received: :00:1c.4 pcieport :00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) pcieport :00:1c.4: device [8086:9d14] error status/mask=1000/2000 pcieport :00:1c.4:[12] Timeout pcieport :00:1c.4: AER: Corrected error received: :00:1c.4 pcieport :00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) pcieport :00:1c.4: device [8086:9d14] error status/mask=3000/2000 pcieport :00:1c.4:[12] Timeout That pcie port is shown to be connected to the Atheros WiFi of the laptop: +-1c.4-[02]00.0 Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter The output of lshw for it is: *-pci:1 description: PCI bridge product: Sunrise Point-LP PCI Express Root Port #5 vendor: Intel Corporation physical id: 1c.4 bus info: pci@:00:1c.4 version: f1 width: 32 bits clock: 33MHz capabilities: pci pciexpress msi pm normal_decode bus_master cap_list configuration: driver=pcieport resources: irq:123 memory:d500-d51f *-network description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 32 serial: [edited for privacy] width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=RM.4.4.1.c2-00057-QCARMSWP-1 ip=192.168.0.71 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:131 memory:d500-d51f I cannot find an APSM disable option in my BIOS setup. A guy named Dennis E. Mungai digged into the issue last year (link below), and his temporary fix (turning off the report bit for AER Corrected errors) worked for me, without the need to turn off AER for the whole system. https://gist.github.com/Brainiarc7/3179144393747f35e5155fdbfd675554 I find interesting that for most of us this issue affects laptop WiFi cards from different vendors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521173 Title: AER: Corrected error received: id=00e0 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1423151] Re: openafs-modules-dkms 1.6.7-1: openafs kernel module failed to build
Achim fix works for me. I'm running 3.13.0-46-generic on Trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1423151 Title: openafs-modules-dkms 1.6.7-1: openafs kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openafs/+bug/1423151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1325987] Re: shuffled keys in keyboard buffer
Likely this is a problem upstream of Lubuntu. I am running Kubuntu 14.04, updated as of 09/09/2014 (kernel: 3.13.0-35-generic) and also experiencing this problem at least both in Thunderbird and Chromium. When the machine is under load and the GUI is lagging keystrokes are shuffled, missed or even transformed into others: it even happened to me that by keeping backspace pressed in the Thunderbird search bar I was getting random keystrokes being input into the latter searchbar. Should I open a bug on kubuntu-meta or this bug can be reassigned to an upstream package? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325987 Title: shuffled keys in keyboard buffer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1325987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1325987] Re: shuffled keys in keyboard buffer
This Lubuntu user had the same problem, identified it as ibus-related and fixed it by replacing ibus with SCIM. http://ubuntuforums.org/showthread.php?t=2230701 I removed ibus and installed scim, will see if the problem resurfaces. sudo apt-get remove ibus && sudo apt-get install scim -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325987 Title: shuffled keys in keyboard buffer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1325987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 932177] Re: XFCE (and other non-GNOME) desktops do not initialise gnome-keyring correctly / WARNING: gnome-keyring:: couldn't connect to PKCS11
I can confirm the bug in Kubuntu 13.04, where the upgrade from 12.10 overwrote the file /etc/xdg/autostart/gnome-keyring-pkcs11.desktop in which I had previously applied a fix as the one described by RichardNeill, i.e. appending "KDE;" to the line "OnlyShowIn=GNOME;Unity;MATE;" -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-workspace in Ubuntu. https://bugs.launchpad.net/bugs/932177 Title: XFCE (and other non-GNOME) desktops do not initialise gnome-keyring correctly / WARNING: gnome-keyring:: couldn't connect to PKCS11 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/932177/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
