[Kernel-packages] [Bug 1724317] Re: Shutdown hangs / no standby - possible Wifi-bug in the kernel
Power cycling does not appear to trigger the bug, as well as attempting to recreate the original circumstances (turning off wireless through system tray + shutdown). Specs: Dell Inspiron 17 3000 (Reg Model P35E) Ubuntu 18.04.1, kernel 5.0.0-36-generic Qualcomm Atheros QCA9377 wireless adapter -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1724317 Title: Shutdown hangs / no standby - possible Wifi-bug in the kernel Status in linux package in Ubuntu: Confirmed Bug description: The Shutdown-process hangs. After about two minutes the following message is displayed: Oct 17 18:47:06 Kahlan kernel: [ 363.170588] INFO: task kworker/u8:2:186 blocked for more than 120 seconds. Oct 17 18:47:06 Kahlan kernel: [ 363.170592] Tainted: P OE 4.13.0-12-generic #13-Ubuntu Oct 17 18:47:06 Kahlan kernel: [ 363.170593] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Two Minutes later this message is displayed: Oct 17 18:49:07 Kahlan kernel: [ 484.008650] INFO: task kworker/u8:2:186 blocked for more than 120 seconds. Oct 17 18:49:07 Kahlan kernel: [ 484.008659] Tainted: P OE 4.13.0-12-generic #13-Ubuntu Oct 17 18:49:07 Kahlan kernel: [ 484.008662] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. This message repeates itself. If I am lucky, my laptop shuts down after some time. Also standby does not work. I think my wifi-adapter causes this problem. With Ubuntu 17.04 or Suse 42.3 I cannot reproduce this problem. I found a bug report in the Arch Bug System (https://bugs.archlinux.org/task/55872 In my laptop I have also a Qualcomm Atheros Adapter. Perhaps the linuxkernel has a bug? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompositorRunning: None CurrentDesktop: KDE Date: Tue Oct 17 19:08:32 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: kubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-12-generic, x86_64: installed bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed nvidia-384, 384.90, 4.13.0-12-generic, x86_64: installed nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] HD Graphics 5500 [1025:0962] InstallationDate: Installed on 2017-10-07 (10 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: Acer Aspire VN7-571G ProcEnviron: LANGUAGE=de PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=d5a4b134-b39a-4764-99bd-208c9e504fa8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.14 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-571G dmi.board.vendor: Acer dmi.board.version: V1.14 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.14 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.14:bd01/08/2015:svnAcer:pnAspireVN7-571G:pvrV1.14:rvnAcer:rnAspireVN7-571G:rvrV1.14:cvnAcer:ct10:cvrV1.14: dmi.product.family: Broadwell System dmi.product.name: Aspire VN7-571G dmi.product.version: V1.14 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724317/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1724317] Re: Shutdown hangs / no standby - possible Wifi-bug in the kernel
Bug also possibly found on 18.04, kernel 5.0.0-36-generic; will need confirmation. (First occurrence) ** Attachment added: "20191201_012839.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724317/+attachment/5309037/+files/20191201_012839.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1724317 Title: Shutdown hangs / no standby - possible Wifi-bug in the kernel Status in linux package in Ubuntu: Confirmed Bug description: The Shutdown-process hangs. After about two minutes the following message is displayed: Oct 17 18:47:06 Kahlan kernel: [ 363.170588] INFO: task kworker/u8:2:186 blocked for more than 120 seconds. Oct 17 18:47:06 Kahlan kernel: [ 363.170592] Tainted: P OE 4.13.0-12-generic #13-Ubuntu Oct 17 18:47:06 Kahlan kernel: [ 363.170593] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Two Minutes later this message is displayed: Oct 17 18:49:07 Kahlan kernel: [ 484.008650] INFO: task kworker/u8:2:186 blocked for more than 120 seconds. Oct 17 18:49:07 Kahlan kernel: [ 484.008659] Tainted: P OE 4.13.0-12-generic #13-Ubuntu Oct 17 18:49:07 Kahlan kernel: [ 484.008662] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. This message repeates itself. If I am lucky, my laptop shuts down after some time. Also standby does not work. I think my wifi-adapter causes this problem. With Ubuntu 17.04 or Suse 42.3 I cannot reproduce this problem. I found a bug report in the Arch Bug System (https://bugs.archlinux.org/task/55872 In my laptop I have also a Qualcomm Atheros Adapter. Perhaps the linuxkernel has a bug? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompositorRunning: None CurrentDesktop: KDE Date: Tue Oct 17 19:08:32 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: kubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-12-generic, x86_64: installed bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed nvidia-384, 384.90, 4.13.0-12-generic, x86_64: installed nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] HD Graphics 5500 [1025:0962] InstallationDate: Installed on 2017-10-07 (10 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: Acer Aspire VN7-571G ProcEnviron: LANGUAGE=de PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=d5a4b134-b39a-4764-99bd-208c9e504fa8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.14 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-571G dmi.board.vendor: Acer dmi.board.version: V1.14 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.14 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.14:bd01/08/2015:svnAcer:pnAspireVN7-571G:pvrV1.14:rvnAcer:rnAspireVN7-571G:rvrV1.14:cvnAcer:ct10:cvrV1.14: dmi.product.family: Broadwell System dmi.product.name: Aspire VN7-571G dmi.product.version: V1.14 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724317/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices
*** This bug is a duplicate of bug 1848790 *** https://bugs.launchpad.net/bugs/1848790 About the problem of "there is no /dev/mmcblk0* device", I checked your dmesg, there are two places are weird the 1st one is about the raspberrypi-firmware, on my board, the dmesg will show: [0.100540] raspberrypi-firmware soc:firmware: Attached to firmware from 2019-08-15 12:03, variant start [0.110122] raspberrypi-firmware soc:firmware: Firmware hash is 9f8431fb7839c7f00f52b81f5822ddab2b31d0db And there are not errors about firmware, but your dmesg is different. the 2nd one is about mmc-bcm2835 driver, your kernel always report: mmc-bcm2835 fe30.mmcnr: could not get clk, deferring probe That is different from my board, on my board, it only reports that message once, Then the driver could get the clk successfully. -- 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/1848703 Title: Raspberry Pi 4 - USB Bus not detecting any devices Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: Pi 4 new install. System boots up but USB bus is not working. Tried 3 keyboards no key presses detected, 2 usb memory drives don't show up in lsblk. output of $lspci 00:00.0 PCI bridge: Broadcom Inc. and subsidiaries Device 2711 (rev 10) 01:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) output of $dmesg on pastebin here http://pastebin.com/h7A3n9xa or attached to this bug report. Not the only one experiencing bug. Another user created a post on the ubuntu forums: https://ubuntuforums.org/showthread.php?t=2429396=01a0c4b0cb4c05e605cbf9d41f660e08=13898142#post13898142 64bit raspberry pi 4&4 image pulled from https://ubuntu.com/download/iot/raspberry-pi page. Specifically http://cdimage.ubuntu.com/releases/19.10/release/ubuntu-19.10 -preinstalled-server-arm64+raspi3.img.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04
There is only one PLL (Phase Locked Loop) in the processor, all CPUs get the resulting clock. When they go into deep idle states (deeper than C1, at least for my processor) then they give up their vote into the PLL as to what the frequency should be. Your single 100% task is dedicating the CPU frequency for all, for when they are active. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768976 Title: Ubuntu 18.04 is overheating after upgrade from 16.04 Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: Ubuntu is overheating at my laptop. Opening youtube on firefox is enough for critical temperature shutdown. Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C with only firefox or chrome open and doing nothing. On my old 16.04 with same using, the temp varies between 55 and 70°C. First thought was the driver nouveau is the problem, and finally I was able to install by add "nouveau.modeset=0" at livecd boot options, without temp shutdown. After install I disable the nouveau at modprobe blacklist, but the system continues overheating and shutdown with basic usage. I have no idea what's happening with the bionic at my laptop. My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.17 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu May 3 16:22:40 2018 InstallationDate: Installed on 2018-04-27 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptHistorylog: Start-Date: 2018-04-27 15:46:02 End-Date: 2018-04-27 15:46:02 VarLogDistupgradeAptlog: Log time: 2018-04-27 15:45:39.753331 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done Log time: 2018-04-27 15:46:04.859979 VarLogDistupgradeApttermlog: Log started: 2018-04-27 15:46:02 Log ended: 2018-04-27 15:46:02 --- .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: edir 2354 F pulseaudio CompositorRunning: None DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [144d:c0a5] Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5] HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d InstallationDate: Installed on 2018-04-27 (36 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711 NonfreeKernelModules: wl Package: xserver-xorg-video-nouveau 1:1.0.15-2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: bionic ubuntu Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 10HX.M034.20110426.SSH dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: RF511/RF411/RF711 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: 10HX dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias:
[Kernel-packages] [Bug 1774711] Re: excessive seccomp audit logs
Will the required pat set be backported to older kernel, such as Ubuntu 4.15.0-70.79-generic 4.15.18? Will the patches be in 20.04 LTS (kernel >= 4.18), which is around the corner? NOTE: Unfortunately with issue #1774711 the use of "auditd" has become problematic on systems with SSDs, since systemd allows in-memory configuration (Storage=volatile; SplitMode=none), but auditd does not support such a complex configuration (write_logs = no; log_file = /var/log/audit/audit.log). That means with the excessive SECCOMP lines (i.e. tens/hundreds of thousands a day) we cannot re-enable auditd (sudo systemctl start|enable auditd.service) until this issue is resolved, UNLESS there is a way to make auditd not to write logs to disk but continue to function properly. We need auditd for enforcing audit.rules (complex ISO 27001, PCI-DSS, etc. compliant rulesets) and statistics (sudo aureport (-n)), which require log data stored (dmesg kernel bugger is insufficient for ISO compliant store and analysis of events and stats). Our tests show, that up to several hundred MiB of logs are written to the SSDs per pay, which accumulates to approx 0.5 TiB over the course of 4 years. With in avg. 50% of the SSD cells occupied and given the models, this translates to a slightly increased wear-out of our SSDs, even when a good wear-leveling algorithm and background garbage collector is in use (our desktop models: Samsung Enterprise SSD with super capacitor mod. SM/PM863(a)). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774711 Title: excessive seccomp audit logs Status in linux package in Ubuntu: Triaged Bug description: Hello, my audit logs are currently filled with messages from Firefox's seccomp filters which looks like this: type=SECCOMP msg=audit(1527882167.659:223316): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=257 compat=0 ip=0x7f4329623d19 code=0x3 type=SECCOMP msg=audit(1527882167.659:223317): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=4 compat=0 ip=0x7f4329623775 code=0x3 type=SECCOMP msg=audit(1527882167.659:223318): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=87 compat=0 ip=0x7f4329625d47 code=0x3 type=SECCOMP msg=audit(1527882167.687:223319): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=257 compat=0 ip=0x7f4329623d19 code=0x3 type=SECCOMP msg=audit(1527882167.687:223320): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=4 compat=0 ip=0x7f4329623775 code=0x3 type=SECCOMP msg=audit(1527882167.687:223321): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=87 compat=0 ip=0x7f4329625d47 code=0x3 type=SECCOMP msg=audit(1527882167.691:223322): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=257 compat=0 ip=0x7f4329623d19 code=0x3 type=SECCOMP msg=audit(1527882167.691:223323): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=4 compat=0 ip=0x7f4329623775 code=0x3 type=SECCOMP msg=audit(1527882167.691:223324): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=87 compat=0 ip=0x7f4329625d47 code=0x3 $ aa-decode 57656220436F6E74656E74 Decoded: Web Content $ aa-decode 2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 Decoded: /usr/lib/firefox/firefox (deleted) Over a recent 48 hour stretch it averaged out to nearly one message per second. My current audit rules are: ## This file is automatically generated from /etc/audit/rules.d -D -b 8192 --loginuid-immutable -a always,exit -F arch=b32 -S adjtimex,settimeofday,stime -F key=time-change -a always,exit -F arch=b64 -S adjtimex,settimeofday -F key=time-change -a always,exit -F arch=b32 -S clock_settime -F a0=0x0 -F key=time-change -a always,exit -F arch=b64 -S clock_settime -F a0=0x0 -F key=time-change -w
[Kernel-packages] [Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04
@Doug Smythies: thanks for the reply. I'm sampling every second. Anyway, just to better understand. When my system is idle all cores spend in C0 less than 10% of the time and the frequency of each core reported by i7z is different and below 2.2GHz. When I run a single core (and single thread) task, there is just core "0" which is 100% of the time in C0 state (as it should) but I would have expected only such core to reach ~2.9GHz and the other to remain in below. Instead all cores goes to ~2.9GHz. https://www.youtube.com/watch?v=HBKfkiOgIv4 (sorry for the oversimplified reference) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768976 Title: Ubuntu 18.04 is overheating after upgrade from 16.04 Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: Ubuntu is overheating at my laptop. Opening youtube on firefox is enough for critical temperature shutdown. Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C with only firefox or chrome open and doing nothing. On my old 16.04 with same using, the temp varies between 55 and 70°C. First thought was the driver nouveau is the problem, and finally I was able to install by add "nouveau.modeset=0" at livecd boot options, without temp shutdown. After install I disable the nouveau at modprobe blacklist, but the system continues overheating and shutdown with basic usage. I have no idea what's happening with the bionic at my laptop. My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.17 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu May 3 16:22:40 2018 InstallationDate: Installed on 2018-04-27 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptHistorylog: Start-Date: 2018-04-27 15:46:02 End-Date: 2018-04-27 15:46:02 VarLogDistupgradeAptlog: Log time: 2018-04-27 15:45:39.753331 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done Log time: 2018-04-27 15:46:04.859979 VarLogDistupgradeApttermlog: Log started: 2018-04-27 15:46:02 Log ended: 2018-04-27 15:46:02 --- .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: edir 2354 F pulseaudio CompositorRunning: None DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [144d:c0a5] Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5] HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d InstallationDate: Installed on 2018-04-27 (36 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711 NonfreeKernelModules: wl Package: xserver-xorg-video-nouveau 1:1.0.15-2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: bionic ubuntu Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 10HX.M034.20110426.SSH dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: RF511/RF411/RF711
[Kernel-packages] [Bug 1853977] Re: nvidia-340 dpkg: error: version '-' has bad syntax: revision number is empty
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers (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/1853977 Title: nvidia-340 dpkg: error: version '-' has bad syntax: revision number is empty Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Bug description: Hello, When installing `nvidia-340` there is an error is the postinst script: philippe@pv-desktop:~$ sudo apt install --reinstall nvidia-340 Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 7 not to upgrade. Need to get 0 B/51.9 MB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 309892 files and directories currently installed.) Preparing to unpack .../nvidia-340_340.107-0ubuntu0.18.04.4_amd64.deb ... Stopping nvidia-persistenced nvidia-persistenced: no process found Done. (snip) Setting up nvidia-340 (340.107-0ubuntu0.18.04.4) ... dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty update-initramfs: deferring update (trigger activated) INFO:Enable nvidia-340 DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude Loading new nvidia-340-340.107 DKMS files... Building for 4.15.0-70-generic Building for architecture x86_64 Building initial module for 4.15.0-70-generic Done. The comment at https://askubuntu.com/questions/969352/uninstalling- and-then-reinstalling-nvidia-384-kills-colord tells us that /var/lib/dpkg/info/nvidia-340.postinst has a typo: replace $KERNELS with $CURRENT_KERNEL then `dpkg-reconfigure nvidia-340` works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853977/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854592] 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/1854592 Title: kern.log flooded by ACPI error messages Status in linux package in Ubuntu: Confirmed Bug description: I use Ubuntu 19.10 AMD64 (completely up to date) on a Lenovo Thinkpad S1 Yoga 12, and I've just noticed that /var/log/kern.log is flooded by messages like : Nov 30 21:12:44 yoga kernel: [ 526.471259] ACPI: \_SB.PCI0.LPCB.EC0.ECRD: 1 arguments were passed to a non-method ACPI object (RegionField) (20190703/nsarguments-204) Every about two seconds, 18 messages of this kind are recorded. What could I do to provide more informations ? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-23-generic 5.3.0-23.25 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tley 1650 F pulseaudio /dev/snd/controlC1: tley 1650 F pulseaudio /dev/snd/pcmC1D0p: tley 1650 F...m pulseaudio Date: Sat Nov 30 21:18:09 2019 InstallationDate: Installed on 2019-11-17 (13 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20DKS1MA00 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=6662e662-b3da-478c-bf6b-ea7d12495e6e ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JEET69WW (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20DKS1MA00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJEET69WW(1.18):bd07/24/2015:svnLENOVO:pn20DKS1MA00:pvrThinkPadS1Yoga12:rvnLENOVO:rn20DKS1MA00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad S1 Yoga 12 dmi.product.name: 20DKS1MA00 dmi.product.sku: LENOVO_MT_20DK_BU_Think_FM_ThinkPad S1 Yoga 12 dmi.product.version: ThinkPad S1 Yoga 12 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854592] [NEW] kern.log flooded by ACPI error messages
Public bug reported: I use Ubuntu 19.10 AMD64 (completely up to date) on a Lenovo Thinkpad S1 Yoga 12, and I've just noticed that /var/log/kern.log is flooded by messages like : Nov 30 21:12:44 yoga kernel: [ 526.471259] ACPI: \_SB.PCI0.LPCB.EC0.ECRD: 1 arguments were passed to a non-method ACPI object (RegionField) (20190703/nsarguments-204) Every about two seconds, 18 messages of this kind are recorded. What could I do to provide more informations ? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-23-generic 5.3.0-23.25 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tley 1650 F pulseaudio /dev/snd/controlC1: tley 1650 F pulseaudio /dev/snd/pcmC1D0p: tley 1650 F...m pulseaudio Date: Sat Nov 30 21:18:09 2019 InstallationDate: Installed on 2019-11-17 (13 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20DKS1MA00 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=6662e662-b3da-478c-bf6b-ea7d12495e6e ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JEET69WW (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20DKS1MA00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJEET69WW(1.18):bd07/24/2015:svnLENOVO:pn20DKS1MA00:pvrThinkPadS1Yoga12:rvnLENOVO:rn20DKS1MA00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad S1 Yoga 12 dmi.product.name: 20DKS1MA00 dmi.product.sku: LENOVO_MT_20DK_BU_Think_FM_ThinkPad S1 Yoga 12 dmi.product.version: ThinkPad S1 Yoga 12 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854592 Title: kern.log flooded by ACPI error messages Status in linux package in Ubuntu: Confirmed Bug description: I use Ubuntu 19.10 AMD64 (completely up to date) on a Lenovo Thinkpad S1 Yoga 12, and I've just noticed that /var/log/kern.log is flooded by messages like : Nov 30 21:12:44 yoga kernel: [ 526.471259] ACPI: \_SB.PCI0.LPCB.EC0.ECRD: 1 arguments were passed to a non-method ACPI object (RegionField) (20190703/nsarguments-204) Every about two seconds, 18 messages of this kind are recorded. What could I do to provide more informations ? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-23-generic 5.3.0-23.25 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tley 1650 F pulseaudio /dev/snd/controlC1: tley 1650 F pulseaudio /dev/snd/pcmC1D0p: tley 1650 F...m pulseaudio Date: Sat Nov 30 21:18:09 2019 InstallationDate: Installed on 2019-11-17 (13 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20DKS1MA00 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=6662e662-b3da-478c-bf6b-ea7d12495e6e ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JEET69WW (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20DKS1MA00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias:
[Kernel-packages] [Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04
@Davide Sangalli: What you describe and show in your comment #80 is correct and exactly what should happen. Your processor is spending an extraordinary amount of time in C1 as opposed to deeper idle states. At what sampling frequency do you run i7z? I would suggest once every 15 seconds or so, so that you don't wake up CPUs just to ask them status stuff. Everyone with this problem: If you don't bisect the kernel to isolate the offending commit, as has been asked for a couple of times now, then there will never be any progress for this bug report. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768976 Title: Ubuntu 18.04 is overheating after upgrade from 16.04 Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: Ubuntu is overheating at my laptop. Opening youtube on firefox is enough for critical temperature shutdown. Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C with only firefox or chrome open and doing nothing. On my old 16.04 with same using, the temp varies between 55 and 70°C. First thought was the driver nouveau is the problem, and finally I was able to install by add "nouveau.modeset=0" at livecd boot options, without temp shutdown. After install I disable the nouveau at modprobe blacklist, but the system continues overheating and shutdown with basic usage. I have no idea what's happening with the bionic at my laptop. My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.17 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu May 3 16:22:40 2018 InstallationDate: Installed on 2018-04-27 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptHistorylog: Start-Date: 2018-04-27 15:46:02 End-Date: 2018-04-27 15:46:02 VarLogDistupgradeAptlog: Log time: 2018-04-27 15:45:39.753331 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done Log time: 2018-04-27 15:46:04.859979 VarLogDistupgradeApttermlog: Log started: 2018-04-27 15:46:02 Log ended: 2018-04-27 15:46:02 --- .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: edir 2354 F pulseaudio CompositorRunning: None DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [144d:c0a5] Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5] HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d InstallationDate: Installed on 2018-04-27 (36 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711 NonfreeKernelModules: wl Package: xserver-xorg-video-nouveau 1:1.0.15-2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: bionic ubuntu Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 10HX.M034.20110426.SSH dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: RF511/RF411/RF711 dmi.board.vendor: SAMSUNG ELECTRONICS CO.,
[Kernel-packages] [Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04
I also mention that, monitoring with i7z the clock of my CPU, when intel turbo is not working I get different freqs for each core Core [core-id] :Actual Freq (Mult.) C0% Halt(C1)% C3 % C6 % Temp VCore Core 1 [0]: 1126.19 (11.23x) 7.9993.9 1 1 40 0.6274 Core 2 [1]: 1239.87 (12.36x) 3.295.1 12.11 41 0.6208 Core 3 [2]: 1577.66 (15.73x) 3.795.4 1 1 38 0.6257 Core 4 [3]: 1316.89 (13.13x) 7.2381.9 112.8 39 0.6257 Core 5 [4]: 1572.58 (15.68x) 10.2 87 14.73 39 0.6257 Core 6 [5]: 1916.98 (19.11x) 8.0290.6 11.44 39 0.6266 However, as soon as I load 1 core to 100%, all goes at the maximum frequency (here I'm limiting the maximum and also the core is under-volted to keep the temperature stable. Core [core-id] :Actual Freq (Mult.) C0% Halt(C1)% C3 % C6 % Temp VCore Core 1 [0]: 2891.95 (28.83x) 100 0 0 0 52 0.8234 Core 2 [1]: 2891.77 (28.83x) 2.4192.2 1 3.6 47 0.8229 Core 3 [2]: 2891.72 (28.83x) 1.7394.4 12.37 44 0.8225 Core 4 [3]: 2891.81 (28.83x) 191.5 16.46 44 0.8230 Core 5 [4]: 2892.39 (28.83x) 196.9 11.37 44 0.8242 Core 6 [5]: 2891.94 (28.83x)2562.9 1 3.3 43 0.8243 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768976 Title: Ubuntu 18.04 is overheating after upgrade from 16.04 Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: Ubuntu is overheating at my laptop. Opening youtube on firefox is enough for critical temperature shutdown. Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C with only firefox or chrome open and doing nothing. On my old 16.04 with same using, the temp varies between 55 and 70°C. First thought was the driver nouveau is the problem, and finally I was able to install by add "nouveau.modeset=0" at livecd boot options, without temp shutdown. After install I disable the nouveau at modprobe blacklist, but the system continues overheating and shutdown with basic usage. I have no idea what's happening with the bionic at my laptop. My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.17 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu May 3 16:22:40 2018 InstallationDate: Installed on 2018-04-27 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptHistorylog: Start-Date: 2018-04-27 15:46:02 End-Date: 2018-04-27 15:46:02 VarLogDistupgradeAptlog: Log time: 2018-04-27 15:45:39.753331 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done Log time: 2018-04-27 15:46:04.859979 VarLogDistupgradeApttermlog: Log started: 2018-04-27 15:46:02 Log ended: 2018-04-27 15:46:02 --- .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: edir 2354 F pulseaudio CompositorRunning: None DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [144d:c0a5] Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5] HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d InstallationDate: Installed on 2018-04-27 (36 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711
[Kernel-packages] [Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices
*** This bug is a duplicate of bug 1848790 *** https://bugs.launchpad.net/bugs/1848790 Hi @hui.wang, the RPi4 boots off the sdcard normally but then I use a USB3 enclosure with disks to assemble a RAID1 BTRFS device to be used as rootfs. At the end of the boot, there is no /dev/mmcblk0* device: #> ls -ld /dev/m* drwxr-xr-x 2 root root 80 Nov 30 15:42 /dev/mapper crw--- 1 root root 10, 227 Nov 30 15:42 /dev/mcelog crw-r- 1 root kmem 1, 1 Nov 30 15:42 /dev/mem crw--- 1 root root 10, 56 Nov 30 15:42 /dev/memory_bandwidth drwxrwxrwt 2 root root 40 Nov 30 15:41 /dev/mqueue Anyway, this is just "an annoyance" that makes just a bit harder to switch kernel, the real problem is this one: Nov 29 10:36:05 raspippa kernel: [39364.240711] xhci_hcd :01:00.0: WARN Cannot submit Set TR Deq Ptr Nov 29 10:36:05 raspippa kernel: [39364.240725] xhci_hcd :01:00.0: A Set TR Deq Ptr command is pending. Nov 29 10:36:05 raspippa kernel: [39364.373694] usb 2-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd Nov 29 10:36:05 raspippa kernel: [39364.396405] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Nov 29 10:36:35 raspippa kernel: [39394.961204] xhci_hcd :01:00.0: WARN Cannot submit Set TR Deq Ptr Nov 29 10:36:35 raspippa kernel: [39394.961218] xhci_hcd :01:00.0: A Set TR Deq Ptr command is pending. Nov 29 10:36:36 raspippa kernel: [39395.324521] usb 2-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd Nov 29 10:36:36 raspippa kernel: [39395.344764] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK Nov 29 10:36:36 raspippa kernel: [39395.344789] sd 0:0:0:0: [sda] tag#0 CDB: Read(16) 88 00 00 00 00 01 e1 20 4d 00 00 00 04 00 00 00 Nov 29 10:36:36 raspippa kernel: [39395.344813] blk_update_request: I/O error, dev sda, sector 8071957760 op 0x0:(READ) flags 0x80700 phys_seg 128 prio class 0 According to this thread (https://bugzilla.kernel.org/show_bug.cgi?id=202541) every kernel >= 4.20 is affected and there's still no patch in 5.3. I'll try to go back to some 4.19.y kernel, I'm even prepared to lower the memory to 1 Gb, cause so far this raspberry hasn't had more than a day of consecutive uptime. ** Bug watch added: Linux Kernel Bug Tracker #202541 https://bugzilla.kernel.org/show_bug.cgi?id=202541 ** Attachment added: "dmesg-raspippa-fresh-boot.txt" https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/+attachment/5308946/+files/dmesg-raspippa-fresh-boot.txt -- 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/1848703 Title: Raspberry Pi 4 - USB Bus not detecting any devices Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: Pi 4 new install. System boots up but USB bus is not working. Tried 3 keyboards no key presses detected, 2 usb memory drives don't show up in lsblk. output of $lspci 00:00.0 PCI bridge: Broadcom Inc. and subsidiaries Device 2711 (rev 10) 01:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) output of $dmesg on pastebin here http://pastebin.com/h7A3n9xa or attached to this bug report. Not the only one experiencing bug. Another user created a post on the ubuntu forums: https://ubuntuforums.org/showthread.php?t=2429396=01a0c4b0cb4c05e605cbf9d41f660e08=13898142#post13898142 64bit raspberry pi 4&4 image pulled from https://ubuntu.com/download/iot/raspberry-pi page. Specifically http://cdimage.ubuntu.com/releases/19.10/release/ubuntu-19.10 -preinstalled-server-arm64+raspi3.img.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854581] [NEW] Bluetooth disconnect on 16.04
Public bug reported: Bluetooth disconnect randomly and is out of order since I restart the computer. Stop and restart BT service doesn't change the issue. This happen on Asus M70V computer. sudo service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since sam. 2019-11-30 16:57:58 CET; 2s ago Docs: man:bluetoothd(8) Main PID: 21551 (bluetoothd) Status: "Running" CGroup: /system.slice/bluetooth.service └─21551 /usr/lib/bluetooth/bluetoothd bluetoothd[21551]: Not enough free handles to register service bluetoothd[21551]: Not enough free handles to register service bluetoothd[21551]: Current Time Service could not be registered bluetoothd[21551]: gatt-time-server: Input/output error (5) bluetoothd[21551]: Not enough free handles to register service bluetoothd[21551]: Not enough free handles to register service bluetoothd[21551]: Sap driver initialization failed. bluetoothd[21551]: sap-server: Operation not permitted (1) bluetoothd[21551]: Endpoint registered: sender=:1.153 path=/MediaEndpoint/A2DPSource nov. 30 16:57:58 happy-buntu bluetoothd[21551]: Endpoint registered: sender=:1.153 path=/MediaEndpoint/A2DPSink Thanks for help ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.4.0-169.198-generic 4.4.197 Uname: Linux 4.4.0-169-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Nov 30 17:00:50 2019 InstallationDate: Installed on 2018-04-16 (593 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK Computer Inc. M70Vn ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-169-generic root=UUID=d3601bac-5eb3-4f24-a402-9211b2c74282 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M70Vn dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr206:bd12/21/2009:svnASUSTeKComputerInc.:pnM70Vn:pvr1.0:rvnASUSTeKComputerInc.:rnM70Vn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: M70Vn dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. hciconfig: hci0: Type: BR/EDR Bus: USB BD Address: 00:22:43:C5:84:05 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:5002654 acl:731390 sco:0 events:294427 errors:0 TX bytes:507962830 acl:587355 sco:0 commands:258 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1854581 Title: Bluetooth disconnect on 16.04 Status in bluez package in Ubuntu: New Bug description: Bluetooth disconnect randomly and is out of order since I restart the computer. Stop and restart BT service doesn't change the issue. This happen on Asus M70V computer. sudo service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since sam. 2019-11-30 16:57:58 CET; 2s ago Docs: man:bluetoothd(8) Main PID: 21551 (bluetoothd) Status: "Running" CGroup: /system.slice/bluetooth.service └─21551 /usr/lib/bluetooth/bluetoothd bluetoothd[21551]: Not enough free handles to register service bluetoothd[21551]: Not enough free handles to register service bluetoothd[21551]: Current Time Service could not be registered bluetoothd[21551]: gatt-time-server: Input/output error (5) bluetoothd[21551]: Not enough free handles to register service bluetoothd[21551]: Not enough free handles to register service bluetoothd[21551]: Sap driver initialization failed. bluetoothd[21551]: sap-server: Operation not permitted (1) bluetoothd[21551]: Endpoint registered: sender=:1.153 path=/MediaEndpoint/A2DPSource nov. 30 16:57:58 happy-buntu bluetoothd[21551]: Endpoint registered: sender=:1.153 path=/MediaEndpoint/A2DPSink Thanks for help ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.4.0-169.198-generic 4.4.197 Uname: Linux 4.4.0-169-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Nov 30 17:00:50 2019 InstallationDate: Installed on 2018-04-16 (593 days ago)
[Kernel-packages] [Bug 1854574] [NEW] Seccomp generated SIGSYS has wrong return address if x0 = -513
Public bug reported: The seccomp man page states the for signals generated by SECCOMP_RET_TRAP, "The program counter will be as though the system call happened (i.e., the program counter will not point to the system call instruction)." However if x0 (first argument and return value) contains the value -513 (-ERESTARTNOINTR), or if SA_RESTART is enabled on the signal handler and x0 contains -512 (-ERESTARTSYS) the saved program counter value points to the system call instruction. I can reproduce this bug on upstream AArch32 kernels, but not on current x86-64 kernels. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-1007-aws 5.3.0-1007.8 ProcVersionSignature: User Name 5.3.0-1007.8-aws 5.3.7 Uname: Linux 5.3.0-1007-aws aarch64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: arm64 Date: Sat Nov 30 14:10:31 2019 Ec2AMI: ami-0e88d70910be26319 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1b Ec2InstanceType: a1.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-aws UpgradeStatus: Upgraded to eoan on 2019-11-09 (21 days ago) ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 ec2-images eoan ** Attachment added: "sigsys_test.c" https://bugs.launchpad.net/bugs/1854574/+attachment/5308878/+files/sigsys_test.c -- 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/1854574 Title: Seccomp generated SIGSYS has wrong return address if x0 = -513 Status in linux-aws package in Ubuntu: New Bug description: The seccomp man page states the for signals generated by SECCOMP_RET_TRAP, "The program counter will be as though the system call happened (i.e., the program counter will not point to the system call instruction)." However if x0 (first argument and return value) contains the value -513 (-ERESTARTNOINTR), or if SA_RESTART is enabled on the signal handler and x0 contains -512 (-ERESTARTSYS) the saved program counter value points to the system call instruction. I can reproduce this bug on upstream AArch32 kernels, but not on current x86-64 kernels. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-1007-aws 5.3.0-1007.8 ProcVersionSignature: User Name 5.3.0-1007.8-aws 5.3.7 Uname: Linux 5.3.0-1007-aws aarch64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: arm64 Date: Sat Nov 30 14:10:31 2019 Ec2AMI: ami-0e88d70910be26319 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1b Ec2InstanceType: a1.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-aws UpgradeStatus: Upgraded to eoan on 2019-11-09 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1854574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854573] Re: Seccomp check skipped for syscall -1 in straced process and PTRACE_SYSEMU broken
** Attachment added: "Test case for skipped syscall" https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1854573/+attachment/5308877/+files/sysemu_test.c -- 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/1854573 Title: Seccomp check skipped for syscall -1 in straced process and PTRACE_SYSEMU broken Status in linux-aws package in Ubuntu: New Bug description: If system call number -1 is called and the process is being traced with PTRACE_SYSCALL, for example by strace, the seccomp check is skipped and -ENOSYS is returned unconditionally (unless altered by the tracer), rather than carrying out action specified in the seccomp filter. The consequence of this is that it is not possible to reliably strace a seccomp based implementation of a foreign system call interface in which r7/x8 is permitted to be -1 on entry to a system call. I have traced this bug to commit f086f67485c5c126bcec4b0e96ac7319a2e59ab8 which attempts to implement PTRACE_SYSEMU. Contrary to x86-64 and the man ptrace page which states "For PTRACE_SYSEMU, continue and stop on entry to the next system call, which will not be executed.", on PTRACE_SYSEMU skips the current system call and stops on entry to the next system call. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-1007-aws 5.3.0-1007.8 ProcVersionSignature: User Name 5.3.0-1007.8-aws 5.3.7 Uname: Linux 5.3.0-1007-aws aarch64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: arm64 Date: Sat Nov 30 13:38:28 2019 Ec2AMI: ami-0e88d70910be26319 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1b Ec2InstanceType: a1.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-aws UpgradeStatus: Upgraded to eoan on 2019-11-09 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1854573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854573] [NEW] Seccomp check skipped for syscall -1 in straced process and PTRACE_SYSEMU broken
Public bug reported: If system call number -1 is called and the process is being traced with PTRACE_SYSCALL, for example by strace, the seccomp check is skipped and -ENOSYS is returned unconditionally (unless altered by the tracer), rather than carrying out action specified in the seccomp filter. The consequence of this is that it is not possible to reliably strace a seccomp based implementation of a foreign system call interface in which r7/x8 is permitted to be -1 on entry to a system call. I have traced this bug to commit f086f67485c5c126bcec4b0e96ac7319a2e59ab8 which attempts to implement PTRACE_SYSEMU. Contrary to x86-64 and the man ptrace page which states "For PTRACE_SYSEMU, continue and stop on entry to the next system call, which will not be executed.", on PTRACE_SYSEMU skips the current system call and stops on entry to the next system call. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-1007-aws 5.3.0-1007.8 ProcVersionSignature: User Name 5.3.0-1007.8-aws 5.3.7 Uname: Linux 5.3.0-1007-aws aarch64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: arm64 Date: Sat Nov 30 13:38:28 2019 Ec2AMI: ami-0e88d70910be26319 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1b Ec2InstanceType: a1.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-aws UpgradeStatus: Upgraded to eoan on 2019-11-09 (21 days ago) ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 ec2-images eoan ** Attachment added: "Test case for skipped syscall" https://bugs.launchpad.net/bugs/1854573/+attachment/5308874/+files/sigsys_skip_test.c -- 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/1854573 Title: Seccomp check skipped for syscall -1 in straced process and PTRACE_SYSEMU broken Status in linux-aws package in Ubuntu: New Bug description: If system call number -1 is called and the process is being traced with PTRACE_SYSCALL, for example by strace, the seccomp check is skipped and -ENOSYS is returned unconditionally (unless altered by the tracer), rather than carrying out action specified in the seccomp filter. The consequence of this is that it is not possible to reliably strace a seccomp based implementation of a foreign system call interface in which r7/x8 is permitted to be -1 on entry to a system call. I have traced this bug to commit f086f67485c5c126bcec4b0e96ac7319a2e59ab8 which attempts to implement PTRACE_SYSEMU. Contrary to x86-64 and the man ptrace page which states "For PTRACE_SYSEMU, continue and stop on entry to the next system call, which will not be executed.", on PTRACE_SYSEMU skips the current system call and stops on entry to the next system call. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-1007-aws 5.3.0-1007.8 ProcVersionSignature: User Name 5.3.0-1007.8-aws 5.3.7 Uname: Linux 5.3.0-1007-aws aarch64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: arm64 Date: Sat Nov 30 13:38:28 2019 Ec2AMI: ami-0e88d70910be26319 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1b Ec2InstanceType: a1.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-aws UpgradeStatus: Upgraded to eoan on 2019-11-09 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1854573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849484] Re: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only]
** Changed in: linux Status: Confirmed => Unknown ** Bug watch added: gitlab.freedesktop.org/drm/intel/issues #91 https://gitlab.freedesktop.org/drm/intel/issues/91 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849484 Title: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I have an LG ultra-wide (2560x1080) monitor. Sometimes when I plug it into my laptop, whose screen was working fine before I plugged it in, both screens go black but nothing else happens. I can still see the mouse cursor and move it between the two monitors (sometimes in the correct location configuration I've configured, sometimes not), but nothing is rendered on the screens. Sometimes when I plug the monitor in, it comes on, but the resolution is wrong. Sometimes it is actually recognized and configured correctly. Frequently I have to unplug the monitor and plug it back in three times or more before it is recognized correctly. I wish it just worked right the first time. :-/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 23 08:34:07 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-12 (40 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago) --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jik3196 F pulseaudio /dev/snd/pcmC1D0p: jik3196 F...m pulseaudio /dev/snd/controlC0: jik3196 F pulseaudio 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: ubuntu:GNOME DistUpgraded: 2019-09-20 10:09:14,777 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroRelease: Ubuntu 19.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292] InstallationDate: Installed on 2019-09-12 (45 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20QD001VUS NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: xorg-server (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.1 Tags: eoan ubuntu Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-09-20 (38 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 07/04/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET30W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QD001VUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QD001VUS dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
[Kernel-packages] [Bug 1849484]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/91. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849484 Title: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I have an LG ultra-wide (2560x1080) monitor. Sometimes when I plug it into my laptop, whose screen was working fine before I plugged it in, both screens go black but nothing else happens. I can still see the mouse cursor and move it between the two monitors (sometimes in the correct location configuration I've configured, sometimes not), but nothing is rendered on the screens. Sometimes when I plug the monitor in, it comes on, but the resolution is wrong. Sometimes it is actually recognized and configured correctly. Frequently I have to unplug the monitor and plug it back in three times or more before it is recognized correctly. I wish it just worked right the first time. :-/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 23 08:34:07 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-12 (40 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago) --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jik3196 F pulseaudio /dev/snd/pcmC1D0p: jik3196 F...m pulseaudio /dev/snd/controlC0: jik3196 F pulseaudio 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: ubuntu:GNOME DistUpgraded: 2019-09-20 10:09:14,777 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroRelease: Ubuntu 19.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292] InstallationDate: Installed on 2019-09-12 (45 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20QD001VUS NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: xorg-server (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.1 Tags: eoan ubuntu Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-09-20 (38 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 07/04/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET30W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QD001VUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QD001VUS dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
[Kernel-packages] [Bug 1845046] Re: Bluetooth headphones/speaker default to low quality headset mode and fails to switch to A2DP when selected
I sometimes trying to fix this for minutes, without any luck. But also realized that when reconnecting there should be connected another headphones, even if usb c one. Will be watching bwhaviour. Having issues with Sone 1000xm3. -- 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/1845046 Title: Bluetooth headphones/speaker default to low quality headset mode and fails to switch to A2DP when selected Status in bluez package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Whenever I turn on my headphones theyll connect to my computer but im able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: litleck1398 F pulseaudio /dev/snd/controlC0: litleck1398 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 17:07:59 2019 InstallationDate: Installed on 2019-09-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: WH-1000XM3 Symptom_Type: High background noise, or volume is too low Title: [WH-1000XM3, playback] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.19 dmi.board.name: 01NYPT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R5 dmi.product.sku: 0729 dmi.product.version: 1.0.19 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
