[Kernel-packages] [Bug 1861595] Status changed to Confirmed
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: 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/1861595
Title:
Laptop does not resume after suspend. OK plugged-in, fails with
battery
Status in linux package in Ubuntu:
Confirmed
Bug description:
This replicated in 18.10, 19.04 and 19.10.
If I suspend the laptop by turning the lid of, or by
#echo mem > /sys/power/state
The nvme disk I have:
# nvme list
Node SN Model
Namespace Usage Format FW Rev
- --
/dev/nvme0n1 03F107951E4452173098 Sabrent
1 1.02 TB / 1.02 TB512 B + 0 B ECFM12.2
Make it to fails= the resume process.
Everything works fine while plugged in.
If in battery it fails to resume (attached dmesg file). It gets stuck into
the desktop but it's dysfunctional without disk operation.
If I suspend in battery mode and then resume (dysfunctionally) and then plug
in the power supply the disk resumes perfectly and everything comes back to
normal.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861595/+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 1861595] Re: Laptop does not resume after suspend. OK plugged-in, fails with battery
lspci-vnvn.log
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861595/+attachment/5324738/+files/lspci-vnvn.log
--
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/1861595
Title:
Laptop does not resume after suspend. OK plugged-in, fails with
battery
Status in linux package in Ubuntu:
New
Bug description:
This replicated in 18.10, 19.04 and 19.10.
If I suspend the laptop by turning the lid of, or by
#echo mem > /sys/power/state
The nvme disk I have:
# nvme list
Node SN Model
Namespace Usage Format FW Rev
- --
/dev/nvme0n1 03F107951E4452173098 Sabrent
1 1.02 TB / 1.02 TB512 B + 0 B ECFM12.2
Make it to fails= the resume process.
Everything works fine while plugged in.
If in battery it fails to resume (attached dmesg file). It gets stuck into
the desktop but it's dysfunctional without disk operation.
If I suspend in battery mode and then resume (dysfunctionally) and then plug
in the power supply the disk resumes perfectly and everything comes back to
normal.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861595/+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 1861595] Re: Laptop does not resume after suspend. OK plugged-in, fails with battery
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861595/+attachment/5324739/+files/version.log
--
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/1861595
Title:
Laptop does not resume after suspend. OK plugged-in, fails with
battery
Status in linux package in Ubuntu:
New
Bug description:
This replicated in 18.10, 19.04 and 19.10.
If I suspend the laptop by turning the lid of, or by
#echo mem > /sys/power/state
The nvme disk I have:
# nvme list
Node SN Model
Namespace Usage Format FW Rev
- --
/dev/nvme0n1 03F107951E4452173098 Sabrent
1 1.02 TB / 1.02 TB512 B + 0 B ECFM12.2
Make it to fails= the resume process.
Everything works fine while plugged in.
If in battery it fails to resume (attached dmesg file). It gets stuck into
the desktop but it's dysfunctional without disk operation.
If I suspend in battery mode and then resume (dysfunctionally) and then plug
in the power supply the disk resumes perfectly and everything comes back to
normal.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861595/+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 1861595] Re: Laptop does not resume after suspend. OK plugged-in, fails with battery
I tried
echo 0 > /sys/bus/pci/devices/\:00\:14.3/d3cold_allowed
It did not work.
--
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/1861595
Title:
Laptop does not resume after suspend. OK plugged-in, fails with
battery
Status in linux package in Ubuntu:
New
Bug description:
This replicated in 18.10, 19.04 and 19.10.
If I suspend the laptop by turning the lid of, or by
#echo mem > /sys/power/state
The nvme disk I have:
# nvme list
Node SN Model
Namespace Usage Format FW Rev
- --
/dev/nvme0n1 03F107951E4452173098 Sabrent
1 1.02 TB / 1.02 TB512 B + 0 B ECFM12.2
Make it to fails= the resume process.
Everything works fine while plugged in.
If in battery it fails to resume (attached dmesg file). It gets stuck into
the desktop but it's dysfunctional without disk operation.
If I suspend in battery mode and then resume (dysfunctionally) and then plug
in the power supply the disk resumes perfectly and everything comes back to
normal.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861595/+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 1861595] [NEW] Laptop does not resume after suspend. OK plugged-in, fails with battery
Public bug reported:
This replicated in 18.10, 19.04 and 19.10.
If I suspend the laptop by turning the lid of, or by
#echo mem > /sys/power/state
The nvme disk I have:
# nvme list
Node SN Model
Namespace Usage Format FW Rev
- --
/dev/nvme0n1 03F107951E4452173098 Sabrent
1 1.02 TB / 1.02 TB512 B + 0 B ECFM12.2
Make it to fails= the resume process.
Everything works fine while plugged in.
If in battery it fails to resume (attached dmesg file). It gets stuck into the
desktop but it's dysfunctional without disk operation.
If I suspend in battery mode and then resume (dysfunctionally) and then plug in
the power supply the disk resumes perfectly and everything comes back to normal.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "Dmesg"
https://bugs.launchpad.net/bugs/1861595/+attachment/5324737/+files/bugbatterysyspend.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/1861595
Title:
Laptop does not resume after suspend. OK plugged-in, fails with
battery
Status in linux package in Ubuntu:
New
Bug description:
This replicated in 18.10, 19.04 and 19.10.
If I suspend the laptop by turning the lid of, or by
#echo mem > /sys/power/state
The nvme disk I have:
# nvme list
Node SN Model
Namespace Usage Format FW Rev
- --
/dev/nvme0n1 03F107951E4452173098 Sabrent
1 1.02 TB / 1.02 TB512 B + 0 B ECFM12.2
Make it to fails= the resume process.
Everything works fine while plugged in.
If in battery it fails to resume (attached dmesg file). It gets stuck into
the desktop but it's dysfunctional without disk operation.
If I suspend in battery mode and then resume (dysfunctionally) and then plug
in the power supply the disk resumes perfectly and everything comes back to
normal.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861595/+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 810791] Re: Softreset failed (device not ready) with Gigabyte motherboard
I had a similar problem. It turned out to be a bad cd-rom drive (or a bad IDE-to-SATA adapter that the drive was using). I disconnected both. The problem disappeared. I installed a new SATA drive. The problem has not re-appeared. -- 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/810791 Title: Softreset failed (device not ready) with Gigabyte motherboard Status in linux package in Ubuntu: Fix Released Bug description: I originally reported this in Bug 285392. However, I'm not sure that this is the same bug, or a different one with the same symptom. I am seeing this problem on a Gigabyte GA-MA74GM-S2 motherboard. I have tried changing the BIOS setting for both AHCI and IDE modes. I get the same error upon boot. After a reboot I have been seeing this error randomly all the time. Sometimes it seems to work ok, sometimes not. I have done 2 dist-upgrades from Lucid (10.04.2 LTS ) to Maverick ( 10.10 ) to Natty ( 11.04 ). This bug has been present in all of these versions of Ubuntu. Boot messages follow: The disk drive for / is not ready yet or not present Continue to wait; or Press S to skip mounting or M for manual recovery [ 1.740026] ata3: softreset failed (device not ready) [ 1.740032] ata6: softreset failed (device not ready) [ 1.740058] ata5: softreset failed (device not ready) [ 1.740062] ata4: softreset failed (device not ready) init: udevtrigger main process (467) terminated with status 1 init: udevtrigger post-stop process (471) terminated with status 1 init: udevmonitor main process (466) killed by TERM signal udevd[453]: specified group 'camera' unknown Ever since Lucid, there are 2 problems with this motherboard that I've been having: 1) It doesn't seem to boot correctly from the first HDD if USB-HDD or CDROM are anywhere above in the boot priority list 2) Every so often I still get the "softreset" and "The disk drive for /home is not ready yet or not present" errors (This is random.. it's usually /home, /, or whatever other partition happens to complain). AHCI vs IDE modes in the BIOS don't change anything. I'm guessing it's a Gigabyte motherboard issue, or something to do with the ATI SB7x0 chipset. So far I haven't tried compiling a new kernel with "CONFIG_SATA_PMP=n" yet... but that seems like it might work... References: https://bugzilla.redhat.com/show_bug.cgi?id=468800 http://kerneltrap.org/mailarchive/git-commits-head/2008/6/14/2122314 http://ubuntuforums.org/archive/index.php/t-1052987.html http://lime-technology.com/forum/index.php?topic=2642.msg33590#msg33590 --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. AplayDevices: aplay: device_list:240: no soundcards found... Architecture: amd64 ArecordDevices: arecord: device_list:240: no soundcards found... AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: trinitronx 2433 F pulseaudio /dev/snd/controlC0: trinitronx 2433 F pulseaudio CRDA: Error: [Errno 2] No such file or directory CheckboxSubmission: d6dd0471f36d4aed9362bfdc71eb18b9 CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2 DistroRelease: Ubuntu 11.04 HibernationDevice: RESUME=UUID=19b226f0-b1dc-4c53-99c8-c585ffe9d167 InstallationMedia: Mythbuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-MA74GM-S2 NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: LC_COLLATE=en_US.utf8 PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=fcd55128-66e2-41ad-ab3a-606c165b2102 ro quiet splash noacpi noapm vt.handoff=7 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 RelatedPackageVersions: linux-restricted-modules-2.6.38-8-generic N/A linux-backports-modules-2.6.38-8-generic N/A linux-firmware1.52 RfKill: Tags: natty running-unity Uname: Linux 2.6.38-8-generic x86_64 UpgradeStatus: Upgraded to natty on 2011-06-30 (19 days ago) UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare video WifiSyslog: Jul 19 12:52:53 saturn kernel: [260899.520036] TCP: Peer 77.114.168.45:54569/49317 unexpectedly shrunk window 1213338602:1213342756 (repaired) Jul 19 12:54:01 saturn kernel: [260967.520038] TCP: Peer 77.114.168.45:54569/49317 unexpectedly shrunk window 1213338602:1213342756 (repaired) Jul 19 12:56:02 saturn kernel: [261087.840039] TCP: Peer 77.114.168.45:54569/49317 unexpectedly shrunk window 1213338602:1213342756 (repaired) dmi.bios.date: 04/17/2008 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F1 dmi.board.name: GA-MA74GM-S2 dmi.board.vendor:
[Kernel-packages] [Bug 1851947] Re: nvidia
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851947 Title: nvidia Status in linux package in Ubuntu: Expired Bug description: I have a bug which affects me every day. Gnome 3.28.2 shakespeare@RYZEN:~$ uname -r 5.0.0-33-generic I have a 4K display with a ROG 1060 using NVIDIA driver metapackage from nvidia-driver-435 (proprietary, tested). I have no other additional drivers. My CPU is an AMD Ryzen 7 1700X Eight-Core Processor. family(23) model(1) stepping(1) I have 32GB RAM and 15GB swap total. My lsb_release is shakespeare@RYZEN:~$ lsb_release -rd Description: Ubuntu 18.04.3 Release:18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shakespeare 5127 F pulseaudio /dev/snd/controlC1: shakespeare 5127 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-25 (45 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-33-generic root=UUID=d54a3591-810b-4e60-bc6b-a70fcda75a38 ro scsi_mod.scan=sync quiet splash nouveau.modeset=0 vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-33.35~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-33-generic N/A linux-backports-modules-5.0.0-33-generic N/A linux-firmware1.173.11 RfKill: Tags: bionic Uname: Linux 5.0.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B350-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB350-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shakespeare 2093 F pulseaudio /dev/snd/controlC1: shakespeare 2093 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-25 (57 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=d54a3591-810b-4e60-bc6b-a70fcda75a38 ro scsi_mod.scan=sync quiet splash nouveau.modeset=0 vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-37-generic N/A linux-backports-modules-5.0.0-37-generic N/A linux-firmware1.173.12 RfKill: Tags: bionic Uname: Linux 5.0.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B350-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Kernel-packages] [Bug 1655280] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore
** Changed in: makedumpfile (Ubuntu Xenial) Importance: Undecided => High ** Changed in: makedumpfile (Ubuntu Bionic) Importance: Undecided => High -- 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: Fix Released Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Fix Released Status in makedumpfile source package in Bionic: Fix Released Status in makedumpfile source package in Cosmic: Fix Released 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 1651635] Re: XPS 13 9360 trackpad locks into scroll mode
I'm affected by this bug. My laptop is a relatively new Lenovo X1. OS is Ubuntu 19.10, kernel is 5.3.0-29-generic (both with all upgrades), all available firmware upgrades are installed (using fwupdmgr). Occasionally my touchpad stops working after resume from sleep. I have to boot the laptop, and 100% of the times when I boot the laptop without power adapter plugged in, the problem reappears and the touchpad is not usable after reboot. The following error messages appears in the logfile: Feb 1 10:05:52 diamond kernel: [ 23.628092] i2c_designware i2c_designware.1: controller timed out Feb 1 10:05:53 diamond kernel: [ 24.651920] i2c_designware i2c_designware.1: controller timed out Feb 1 10:05:54 diamond kernel: [ 25.675991] i2c_designware i2c_designware.1: controller timed out One message per second - which by itself is too much, because it generates I/O activity all the time. If I plugin the power cord and reboot, the touchpad is working 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/1651635 Title: XPS 13 9360 trackpad locks into scroll mode Status in Dell Sputnik: Invalid Status in Linux: Unknown Status in linux package in Ubuntu: Invalid Bug description: Hello, I'm running Linux on a Dell XPS 13 (9360) laptop. I find that upwards of 10 times per day, my trackpad gets stuck in "scrolling" mode. Moving the trackpad won't move the X windows pointer, but will send scrolling events to the foreground window. When the trackpad is locked in this mode, the touchscreen will still let me move the mouse cursor, as will an external mouse. On Ubuntu 16.04 freshly restored from the Dell recovery image, I find that it's often difficult to get the trackpad to recover. I do find that the issue happens less frequently on Dell's build of Ubuntu 16.04 than on other linux distributions and versions, but it still happens enough to significantly impact my ability to do productive work. The issue does not occur when running Windows 10 on the same device. I suspect that the issue may be related to palm detection or misdetecting the user's palm as a gesture to enable scrolling mode, but have no proof for this. It seems that I'm often able to reproduce the issue by brushing the trackpad with my right palm. On Ubuntu 16.10, with the latest shipped 4.8 kernel (Linux szx 4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux), with the extra xinput configuration below, I am able to get the trackpad to recover, simply by clicking the trackpad: /usr/share/X11/xorg.conf.d/99-libinput.conf: Section "InputClass" Identifier "libinput touchpad catchall" Driver "libinput" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Option "Tapping" "True" Option "DisableWhileTyping" "True" Option "NaturalScrolling" "False" Option "AccelProfile" "adaptive" Option "AccelSpeed" "0.05" Option "MiddleEmulation" "True" Option "ScrollMethod" "twofinger" # Option "ClickMethod" "clickfinger" Option "ClickMethod" "buttonareas" EndSection In my experience, the problem manifests using both the Xorg synaptics driver and the Xorg libinput driver. root@szx:/etc/modprobe.d# xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech M570 id=10 [slave pointer (2)] ⎜ ↳ DLL075B:01 06CB:76AF Touchpad id=13 [slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_HDid=12 [slave keyboard (3)] ↳ Intel Virtual Button driver id=14 [slave keyboard (3)] ↳ Intel HID eventsid=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] ↳ Dell WMI hotkeysid=17 [slave keyboard (3)] root@szx:/etc/modprobe.d# To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1651635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1861573] Re: Mutliple ACPI errors on HP Omen 15 2019 with hp-wmi module
This commit is also needed: https://github.com/torvalds/linux/commit/133b2acee3871ae6bf123b8fe34be14464aa3d2c -- 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/1861573 Title: Mutliple ACPI errors on HP Omen 15 2019 with hp-wmi module Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: Hi! I've recently got an HP Omen 15. When loading the hp-wmi module dmesg returns a lot of errors: [28511.704962] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.704971] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705032] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190703/dsopcode-198) [28511.705037] No Local Variables are initialized for Method [HWMC] [28511.705038] Initialized Arguments for Method [HWMC]: (2 arguments defined for method invocation) [28511.705039] Arg0: c8a6cf34Integer 0002 [28511.705042] Arg1: bc018096Buffer(20) 53 45 43 55 01 00 00 00 [28511.705047] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705053] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705110] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190703/dsopcode-198) [28511.705115] No Local Variables are initialized for Method [HWMC] [28511.705116] Initialized Arguments for Method [HWMC]: (2 arguments defined for method invocation) [28511.705116] Arg0: c8a6cf34Integer 0002 [28511.705118] Arg1: 548250c2Buffer(20) 53 45 43 55 01 00 00 00 [28511.705123] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705129] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705174] input: HP WMI hotkeys as /devices/virtual/input/input17 [28511.705280] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190703/dsopcode-198) [28511.705283] No Local Variables are initialized for Method [HWMC] [28511.705284] Initialized Arguments for Method [HWMC]: (2 arguments defined for method invocation) [28511.705284] Arg0: c8a6cf34Integer 0002 [28511.705286] Arg1: bc018096Buffer(20) 53 45 43 55 01 00 00 00 [28511.705289] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705307] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705365] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190703/dsopcode-198) [28511.705368] No Local Variables are initialized for Method [HWMC] [28511.705368] Initialized Arguments for Method [HWMC]: (2 arguments defined for method invocation) [28511.705369] Arg0: c8a6cf34Integer 0003 [28511.705370] Arg1: 548250c2Buffer(20) 53 45 43 55 01 00 00 00 [28511.705373] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705377] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28527.803070] hp_wmi: bad event value 0x80 status 0x5 [29245.461839] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190703/dsopcode-198) [29245.461859] No Local Variables are initialized for Method [HWMC] [29245.461860] Initialized Arguments for Method [HWMC]: (2 arguments defined for method invocation) [29245.461860] Arg0: 94a8091cInteger 0002 [29245.461862] Arg1: a7ff2e53Buffer(20) 53 45 43 55 01 00 00 00 [29245.461866] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [29245.461871] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [29245.461950] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190703/dsopcode-198) [29245.461953] No Local Variables are initialized for Method [HWMC]
[Kernel-packages] [Bug 1861573] Re: Mutliple ACPI errors on HP Omen 15 2019 with hp-wmi module
Launchpad has imported 18 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=201981. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2018-12-13T08:35:02+00:00 luya wrote: I brought a brand new HP Envy x360 laptop and install a distribution. The issue occurred on both with the following error: mesg | grep Error [1.275414] RAS: Correctable Errors collector initialized. [4.957640] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20180810/dsopcode-201) [4.957647] ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20180810/psparse-516) [4.957655] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20180810/psparse-516) [4.957701] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20180810/dsopcode-201) [4.957705] ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20180810/psparse-516) [4.957710] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20180810/psparse-516) [4.957755] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20180810/dsopcode-201) [4.957759] ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20180810/psparse-516) [4.957764] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20180810/psparse-516) [4.958354] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20180810/dsopcode-201) [4.958358] ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20180810/psparse-516) [4.958365] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20180810/psparse-516) [4.958513] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20180810/dsopcode-201) [4.958517] ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20180810/psparse-516) [4.958523] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20180810/psparse-516) With some researches, it looks like all HP laptops are affected by this issue https://bugzilla.kernel.org/show_bug.cgi?id=200999 https://h30434.www3.hp.com/t5/Notebook-Operating-System-and-Recovery/acpi-error-with-linux/td-p/6021489 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861573/comments/0 On 2018-12-14T02:29:14+00:00 luya wrote: Additional link to related bug: https://bugzilla.redhat.com/show_bug.cgi?id=1520703 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861573/comments/1 On 2018-12-20T04:07:10+00:00 serdar2005 wrote: Hi Hp Amd A10 9600p [3.546921] RAS: Correctable Errors collector initialized. [9.979321] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20180531/dsopcode-201) [9.979438] ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20180531/psparse-516) [9.979484] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20180531/psparse-516) [9.979764] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20180531/dsopcode-201) [9.979872] ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20180531/psparse-516) [9.988903] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20180531/psparse-516) [9.989220] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20180531/dsopcode-201) [9.989318] ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20180531/psparse-516) [9.989358] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20180531/psparse-516) [9.990180] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20180531/dsopcode-201) [9.990274] ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20180531/psparse-516) [9.990312] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20180531/psparse-516) [9.990557] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20180531/dsopcode-201) [9.990646] ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20180531/psparse-516) [9.990682] ACPI Error: Method
[Kernel-packages] [Bug 1861470] Re: BIOS logo reappears mid-boot after the purple screen
There will always be cases where grub needs to display a menu, in which case it's going to change the background. Having the kernel switch back from the purple screen to the bios logo after this is going to look odd. I'm dubious that this design was thought all the way through. -- 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/1861470 Title: BIOS logo reappears mid-boot after the purple screen Status in grub2 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-signed-5.4 package in Ubuntu: Confirmed Status in plymouth package in Ubuntu: New Bug description: BIOS logo (the ACPI BGRT graphic) reappears mid-boot after the purple screen. This seems to be happening reliably on multiple focal machines: 0. Turn on or reboot the machine. 1. See the BIOS logo. 2. See a blank purple screen (grub) 3. See the BIOS logo again (this bug) 4. See the purple screen with Ubuntu logo (plymouth) 5. See the login screen I believe this is related to ACPI BGRT changes in the kernel. And I guess it wouldn't even need fixing if we just eliminated the blank purple grub screen (step 2)... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Fri Jan 31 11:31:44 2020 InstallationDate: Installed on 2020-01-30 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan1316 F pulseaudio DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-30 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) MachineType: LENOVO 20KFCTO1WW Package: linux-signed-5.4 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=50f3b272-d351-4a2a-9661-d39e9fcf2195 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 RelatedPackageVersions: linux-restricted-modules-5.4.0-12-generic N/A linux-backports-modules-5.4.0-12-generic N/A linux-firmware1.185 Tags: focal Uname: Linux 5.4.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N20ET51W (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KFCTO1WW 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:bvrN20ET51W(1.36):bd01/10/2020:svnLENOVO:pn20KFCTO1WW:pvrThinkPadX280:rvnLENOVO:rn20KFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X280 dmi.product.name: 20KFCTO1WW dmi.product.sku: LENOVO_MT_20KF_BU_Think_FM_ThinkPad X280 dmi.product.version: ThinkPad X280 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1861470/+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 1861070] Re: Raspberry Pi 4B: USB OTG is not working
For me I would still prefer using "dtoverlay=dwc2,dr_mode=peripheral" as it is more reliable at the moment: if pi4 is rebooted remotely, it will come up with the necessary interface as I added g_cdc to /etc/modprobe.d/modules. On my setup it should not be power related, as I'm using a cable that should provide <=0.9A from PC's USB-A and <=2.1A from an external PSU = 2.5~3A in total. Based on my test before out of curiosity, my pi4 uses ~0.6A when idle, and up to 1.5A during CPU stress test. -- 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/1861070 Title: Raspberry Pi 4B: USB OTG is not working Status in linux-raspi2 package in Ubuntu: New Bug description: I am using Raspberry Pi 4B (4GB) and want to make use of the OTG functionality (g_ether). I cross checked with Raspbian to make sure it is not a hardware issue. Extract from dmesg of Ubuntu 19.10.1 with latest updates applied as of Jan 26th, 2020 via "apt-get update" and "apt-get full-upgrade": ... [1.514262] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) [1.517365] dwc_otg: FIQ enabled [1.517376] dwc_otg: NAK holdoff enabled [1.517386] dwc_otg: FIQ split-transaction FSM enabled [1.517399] Module dwc_common_port init ... [6.358332] dwc2 fe98.usb: fe98.usb supply vusb_d not found, using dummy regulator [6.358388] dwc2 fe98.usb: fe98.usb supply vusb_a not found, using dummy regulator [6.358545] dwc2 fe98.usb: Configuration mismatch. dr_mode forced to host [6.409098] dwc2 fe98.usb: DWC OTG Controller [6.409399] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 [6.409432] dwc2 fe98.usb: irq 23, io mem 0xfe98 ... [ 111.796714] udc-core: couldn't find an available UDC - added [g_ether] to list of pending drivers I think it is that "Configuration mismatch. dr_mode forced to host" log entry telling me that the port is acting as HOST mode instead of OTG mode. I have try putting these in usercfg.txt "dtoverlay=dwc2" "dtoverlay=dwc2,dr_mode=otg" "dtoverlay=dwc2,dr_mode=peripheral" and it will give the same result, no OTG functionality. On the same hardware running Raspbian Buster, it initialise successfully. Corresponding dmesg: ... [0.567531] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) [0.570391] dwc_otg: FIQ enabled [0.570400] dwc_otg: NAK holdoff enabled [0.570409] dwc_otg: FIQ split-transaction FSM enabled [0.570421] Module dwc_common_port init ... [2.507634] dwc2 fe98.usb: fe98.usb supply vusb_d not found, using dummy regulator [2.511011] dwc2 fe98.usb: Linked as a consumer to regulator.0 [2.514450] dwc2 fe98.usb: fe98.usb supply vusb_a not found, using dummy regulator [2.731860] dwc2 fe98.usb: dwc2_check_params: Invalid parameter lpm=1 [2.735511] dwc2 fe98.usb: dwc2_check_params: Invalid parameter lpm_clock_gating=1 [2.735522] dwc2 fe98.usb: dwc2_check_params: Invalid parameter besl=1 [2.735533] dwc2 fe98.usb: dwc2_check_params: Invalid parameter hird_threshold_en=1 [2.735582] dwc2 fe98.usb: EPs: 8, dedicated fifos, 4080 entries in SPRAM [2.752511] dwc2 fe98.usb: DWC OTG Controller [2.752554] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 [2.752601] dwc2 fe98.usb: irq 36, io mem 0xfe98 ... [2.848843] g_ether gadget: Ethernet Gadget, version: Memorial Day 2008 [2.851601] g_ether gadget: g_ether ready [2.854580] dwc2 fe98.usb: bound driver g_ether [2.998525] dwc2 fe98.usb: new device is high-speed [3.075025] dwc2 fe98.usb: new device is high-speed [3.139338] dwc2 fe98.usb: new address 10 [3.154010] g_ether gadget: high-speed config #1: CDC Ethernet (ECM) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861070/+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 1861070] Re: Raspberry Pi 4B: USB OTG is not working
sorry, typo above: /etc/modules instead of /etc/modprobe.d/modules. -- 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/1861070 Title: Raspberry Pi 4B: USB OTG is not working Status in linux-raspi2 package in Ubuntu: New Bug description: I am using Raspberry Pi 4B (4GB) and want to make use of the OTG functionality (g_ether). I cross checked with Raspbian to make sure it is not a hardware issue. Extract from dmesg of Ubuntu 19.10.1 with latest updates applied as of Jan 26th, 2020 via "apt-get update" and "apt-get full-upgrade": ... [1.514262] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) [1.517365] dwc_otg: FIQ enabled [1.517376] dwc_otg: NAK holdoff enabled [1.517386] dwc_otg: FIQ split-transaction FSM enabled [1.517399] Module dwc_common_port init ... [6.358332] dwc2 fe98.usb: fe98.usb supply vusb_d not found, using dummy regulator [6.358388] dwc2 fe98.usb: fe98.usb supply vusb_a not found, using dummy regulator [6.358545] dwc2 fe98.usb: Configuration mismatch. dr_mode forced to host [6.409098] dwc2 fe98.usb: DWC OTG Controller [6.409399] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 [6.409432] dwc2 fe98.usb: irq 23, io mem 0xfe98 ... [ 111.796714] udc-core: couldn't find an available UDC - added [g_ether] to list of pending drivers I think it is that "Configuration mismatch. dr_mode forced to host" log entry telling me that the port is acting as HOST mode instead of OTG mode. I have try putting these in usercfg.txt "dtoverlay=dwc2" "dtoverlay=dwc2,dr_mode=otg" "dtoverlay=dwc2,dr_mode=peripheral" and it will give the same result, no OTG functionality. On the same hardware running Raspbian Buster, it initialise successfully. Corresponding dmesg: ... [0.567531] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) [0.570391] dwc_otg: FIQ enabled [0.570400] dwc_otg: NAK holdoff enabled [0.570409] dwc_otg: FIQ split-transaction FSM enabled [0.570421] Module dwc_common_port init ... [2.507634] dwc2 fe98.usb: fe98.usb supply vusb_d not found, using dummy regulator [2.511011] dwc2 fe98.usb: Linked as a consumer to regulator.0 [2.514450] dwc2 fe98.usb: fe98.usb supply vusb_a not found, using dummy regulator [2.731860] dwc2 fe98.usb: dwc2_check_params: Invalid parameter lpm=1 [2.735511] dwc2 fe98.usb: dwc2_check_params: Invalid parameter lpm_clock_gating=1 [2.735522] dwc2 fe98.usb: dwc2_check_params: Invalid parameter besl=1 [2.735533] dwc2 fe98.usb: dwc2_check_params: Invalid parameter hird_threshold_en=1 [2.735582] dwc2 fe98.usb: EPs: 8, dedicated fifos, 4080 entries in SPRAM [2.752511] dwc2 fe98.usb: DWC OTG Controller [2.752554] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 [2.752601] dwc2 fe98.usb: irq 36, io mem 0xfe98 ... [2.848843] g_ether gadget: Ethernet Gadget, version: Memorial Day 2008 [2.851601] g_ether gadget: g_ether ready [2.854580] dwc2 fe98.usb: bound driver g_ether [2.998525] dwc2 fe98.usb: new device is high-speed [3.075025] dwc2 fe98.usb: new device is high-speed [3.139338] dwc2 fe98.usb: new address 10 [3.154010] g_ether gadget: high-speed config #1: CDC Ethernet (ECM) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861070/+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 1804577] Re: ACPI BIOS Error (bug): Failure creating [\_SB.SMIC], AE_ALREADY_EXISTS
~esserre This is not the same bug - please report it separately (run "ubuntu-bug linux"). -- 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/1804577 Title: ACPI BIOS Error (bug): Failure creating [\_SB.SMIC], AE_ALREADY_EXISTS Status in linux package in Ubuntu: Confirmed Bug description: I`m using Ubuntu 18.10 on my B350M GAMING PRO motherboard and AMD 2400G CPU. See some error in dmesg. Hope a fix in the upcoming update. Linux version 4.18.0-10-generic [0.076193] ACPI: Added _OSI(Module Device) [0.076193] ACPI: Added _OSI(Processor Device) [0.076194] ACPI: Added _OSI(3.0 _SCP Extensions) [0.076194] ACPI: Added _OSI(Processor Aggregator Device) [0.076195] ACPI: Added _OSI(Linux-Dell-Video) [0.076196] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio) [0.086490] ACPI BIOS Error (bug): Failure creating [\_SB.SMIC], AE_ALREADY_EXISTS (20180531/dswload2-316) [0.086497] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180531/psobject-221) [0.086501] ACPI BIOS Error (bug): Failure creating [\_SB.SMIB], AE_ALREADY_EXISTS (20180531/dsfield-594) [0.086582] ACPI: 8 ACPI AML tables successfully acquired and loaded [0.088710] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [0.090528] ACPI: Interpreter enabled [0.090541] ACPI: (supports S0 S3 S4 S5) [0.090542] ACPI: Using IOAPIC for interrupt routing [0.090886] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [0.091196] ACPI: Enabled 2 GPEs in block 00 to 1F [0.093761] ACPI: Power Resource [P0ST] (on) [0.093793] ACPI: Power Resource [P3ST] (on) [0.100120] ACPI: PCI Root Bridge [PCI0] (domain [bus 00-ff]) [0.100125] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [0.100360] acpi PNP0A08:00: _OSC: platform does not support [SHPCHotplug LTR] [0.100583] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability] [0.100596] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain [bus 00-3f] only partially covers this bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804577/+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 1861573] Re: Mutliple ACPI errors on HP Omen 15 2019 with hp-wmi module
Related links: https://lore.kernel.org/patchwork/project/lkml/list/?series=419906=* https://github.com/torvalds/linux/blob/master/drivers/platform/x86/hp-wmi.c https://wiki.ubuntu.com/Kernel/Reference/WMI https://lwn.net/Articles/391230/ ** Bug watch added: Linux Kernel Bug Tracker #201981 https://bugzilla.kernel.org/show_bug.cgi?id=201981 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=201981 Importance: Unknown Status: Unknown -- 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/1861573 Title: Mutliple ACPI errors on HP Omen 15 2019 with hp-wmi module Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Hi! I've recently got an HP Omen 15. When loading the hp-wmi module dmesg returns a lot of errors: [28511.704962] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.704971] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705032] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190703/dsopcode-198) [28511.705037] No Local Variables are initialized for Method [HWMC] [28511.705038] Initialized Arguments for Method [HWMC]: (2 arguments defined for method invocation) [28511.705039] Arg0: c8a6cf34Integer 0002 [28511.705042] Arg1: bc018096Buffer(20) 53 45 43 55 01 00 00 00 [28511.705047] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705053] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705110] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190703/dsopcode-198) [28511.705115] No Local Variables are initialized for Method [HWMC] [28511.705116] Initialized Arguments for Method [HWMC]: (2 arguments defined for method invocation) [28511.705116] Arg0: c8a6cf34Integer 0002 [28511.705118] Arg1: 548250c2Buffer(20) 53 45 43 55 01 00 00 00 [28511.705123] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705129] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705174] input: HP WMI hotkeys as /devices/virtual/input/input17 [28511.705280] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190703/dsopcode-198) [28511.705283] No Local Variables are initialized for Method [HWMC] [28511.705284] Initialized Arguments for Method [HWMC]: (2 arguments defined for method invocation) [28511.705284] Arg0: c8a6cf34Integer 0002 [28511.705286] Arg1: bc018096Buffer(20) 53 45 43 55 01 00 00 00 [28511.705289] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705307] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705365] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190703/dsopcode-198) [28511.705368] No Local Variables are initialized for Method [HWMC] [28511.705368] Initialized Arguments for Method [HWMC]: (2 arguments defined for method invocation) [28511.705369] Arg0: c8a6cf34Integer 0003 [28511.705370] Arg1: 548250c2Buffer(20) 53 45 43 55 01 00 00 00 [28511.705373] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705377] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28527.803070] hp_wmi: bad event value 0x80 status 0x5 [29245.461839] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190703/dsopcode-198) [29245.461859] No Local Variables are initialized for Method [HWMC] [29245.461860] Initialized Arguments for Method [HWMC]: (2 arguments defined for method invocation) [29245.461860] Arg0: 94a8091cInteger 0002 [29245.461862] Arg1: a7ff2e53Buffer(20) 53 45 43 55 01 00 00 00 [29245.461866] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [29245.461871]
[Kernel-packages] [Bug 1861573] Re: Mutliple ACPI errors on HP Omen 15 2019 with hp-wmi module
The patches: https://lore.kernel.org/stable/20191122185641.60711-1-hdego...@redhat.com/ https://lore.kernel.org/stable/20191122185641.60711-2-hdego...@redhat.com/ Fix this issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861573 Title: Mutliple ACPI errors on HP Omen 15 2019 with hp-wmi module Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Hi! I've recently got an HP Omen 15. When loading the hp-wmi module dmesg returns a lot of errors: [28511.704962] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.704971] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705032] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190703/dsopcode-198) [28511.705037] No Local Variables are initialized for Method [HWMC] [28511.705038] Initialized Arguments for Method [HWMC]: (2 arguments defined for method invocation) [28511.705039] Arg0: c8a6cf34Integer 0002 [28511.705042] Arg1: bc018096Buffer(20) 53 45 43 55 01 00 00 00 [28511.705047] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705053] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705110] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190703/dsopcode-198) [28511.705115] No Local Variables are initialized for Method [HWMC] [28511.705116] Initialized Arguments for Method [HWMC]: (2 arguments defined for method invocation) [28511.705116] Arg0: c8a6cf34Integer 0002 [28511.705118] Arg1: 548250c2Buffer(20) 53 45 43 55 01 00 00 00 [28511.705123] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705129] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705174] input: HP WMI hotkeys as /devices/virtual/input/input17 [28511.705280] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190703/dsopcode-198) [28511.705283] No Local Variables are initialized for Method [HWMC] [28511.705284] Initialized Arguments for Method [HWMC]: (2 arguments defined for method invocation) [28511.705284] Arg0: c8a6cf34Integer 0002 [28511.705286] Arg1: bc018096Buffer(20) 53 45 43 55 01 00 00 00 [28511.705289] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705307] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705365] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190703/dsopcode-198) [28511.705368] No Local Variables are initialized for Method [HWMC] [28511.705368] Initialized Arguments for Method [HWMC]: (2 arguments defined for method invocation) [28511.705369] Arg0: c8a6cf34Integer 0003 [28511.705370] Arg1: 548250c2Buffer(20) 53 45 43 55 01 00 00 00 [28511.705373] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705377] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28527.803070] hp_wmi: bad event value 0x80 status 0x5 [29245.461839] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190703/dsopcode-198) [29245.461859] No Local Variables are initialized for Method [HWMC] [29245.461860] Initialized Arguments for Method [HWMC]: (2 arguments defined for method invocation) [29245.461860] Arg0: 94a8091cInteger 0002 [29245.461862] Arg1: a7ff2e53Buffer(20) 53 45 43 55 01 00 00 00 [29245.461866] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [29245.461871] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [29245.461950] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190703/dsopcode-198)
[Kernel-packages] [Bug 1861573] 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/1861573 Title: Mutliple ACPI errors on HP Omen 15 2019 with hp-wmi module Status in linux package in Ubuntu: Confirmed Bug description: Hi! I've recently got an HP Omen 15. When loading the hp-wmi module dmesg returns a lot of errors: [28511.704962] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.704971] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705032] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190703/dsopcode-198) [28511.705037] No Local Variables are initialized for Method [HWMC] [28511.705038] Initialized Arguments for Method [HWMC]: (2 arguments defined for method invocation) [28511.705039] Arg0: c8a6cf34Integer 0002 [28511.705042] Arg1: bc018096Buffer(20) 53 45 43 55 01 00 00 00 [28511.705047] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705053] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705110] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190703/dsopcode-198) [28511.705115] No Local Variables are initialized for Method [HWMC] [28511.705116] Initialized Arguments for Method [HWMC]: (2 arguments defined for method invocation) [28511.705116] Arg0: c8a6cf34Integer 0002 [28511.705118] Arg1: 548250c2Buffer(20) 53 45 43 55 01 00 00 00 [28511.705123] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705129] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705174] input: HP WMI hotkeys as /devices/virtual/input/input17 [28511.705280] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190703/dsopcode-198) [28511.705283] No Local Variables are initialized for Method [HWMC] [28511.705284] Initialized Arguments for Method [HWMC]: (2 arguments defined for method invocation) [28511.705284] Arg0: c8a6cf34Integer 0002 [28511.705286] Arg1: bc018096Buffer(20) 53 45 43 55 01 00 00 00 [28511.705289] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705307] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705365] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190703/dsopcode-198) [28511.705368] No Local Variables are initialized for Method [HWMC] [28511.705368] Initialized Arguments for Method [HWMC]: (2 arguments defined for method invocation) [28511.705369] Arg0: c8a6cf34Integer 0003 [28511.705370] Arg1: 548250c2Buffer(20) 53 45 43 55 01 00 00 00 [28511.705373] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705377] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28527.803070] hp_wmi: bad event value 0x80 status 0x5 [29245.461839] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190703/dsopcode-198) [29245.461859] No Local Variables are initialized for Method [HWMC] [29245.461860] Initialized Arguments for Method [HWMC]: (2 arguments defined for method invocation) [29245.461860] Arg0: 94a8091cInteger 0002 [29245.461862] Arg1: a7ff2e53Buffer(20) 53 45 43 55 01 00 00 00 [29245.461866] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [29245.461871] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [29245.461950] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190703/dsopcode-198) [29245.461953] No Local Variables are initialized for Method [HWMC] [29245.461953] Initialized Arguments for Method [HWMC]:
[Kernel-packages] [Bug 1861573] [NEW] Mutliple ACPI errors on HP Omen 15 2019 with hp-wmi module
Public bug reported: Hi! I've recently got an HP Omen 15. When loading the hp-wmi module dmesg returns a lot of errors: [28511.704962] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.704971] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705032] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190703/dsopcode-198) [28511.705037] No Local Variables are initialized for Method [HWMC] [28511.705038] Initialized Arguments for Method [HWMC]: (2 arguments defined for method invocation) [28511.705039] Arg0: c8a6cf34Integer 0002 [28511.705042] Arg1: bc018096Buffer(20) 53 45 43 55 01 00 00 00 [28511.705047] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705053] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705110] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190703/dsopcode-198) [28511.705115] No Local Variables are initialized for Method [HWMC] [28511.705116] Initialized Arguments for Method [HWMC]: (2 arguments defined for method invocation) [28511.705116] Arg0: c8a6cf34Integer 0002 [28511.705118] Arg1: 548250c2Buffer(20) 53 45 43 55 01 00 00 00 [28511.705123] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705129] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705174] input: HP WMI hotkeys as /devices/virtual/input/input17 [28511.705280] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190703/dsopcode-198) [28511.705283] No Local Variables are initialized for Method [HWMC] [28511.705284] Initialized Arguments for Method [HWMC]: (2 arguments defined for method invocation) [28511.705284] Arg0: c8a6cf34Integer 0002 [28511.705286] Arg1: bc018096Buffer(20) 53 45 43 55 01 00 00 00 [28511.705289] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705307] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705365] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190703/dsopcode-198) [28511.705368] No Local Variables are initialized for Method [HWMC] [28511.705368] Initialized Arguments for Method [HWMC]: (2 arguments defined for method invocation) [28511.705369] Arg0: c8a6cf34Integer 0003 [28511.705370] Arg1: 548250c2Buffer(20) 53 45 43 55 01 00 00 00 [28511.705373] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28511.705377] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [28527.803070] hp_wmi: bad event value 0x80 status 0x5 [29245.461839] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190703/dsopcode-198) [29245.461859] No Local Variables are initialized for Method [HWMC] [29245.461860] Initialized Arguments for Method [HWMC]: (2 arguments defined for method invocation) [29245.461860] Arg0: 94a8091cInteger 0002 [29245.461862] Arg1: a7ff2e53Buffer(20) 53 45 43 55 01 00 00 00 [29245.461866] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [29245.461871] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [29245.461950] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190703/dsopcode-198) [29245.461953] No Local Variables are initialized for Method [HWMC] [29245.461953] Initialized Arguments for Method [HWMC]: (2 arguments defined for method invocation) [29245.461954] Arg0: 94a8091cInteger 0002 [29245.461955] Arg1: 63349e08Buffer(20) 53 45 43 55 01 00 00 00 [29245.461958] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529) [29245.461962] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190703/psparse-529)
[Kernel-packages] [Bug 1861165] Re: bionic/linux: 4.15.0-87.87 -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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Proposed phase-changed: Saturday, 01. February 2020 03:31 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Stalled -- ready for review trackers: bionic/linux-aws: bug 1861141 bionic/linux-fips: bug 1861152 bionic/linux-gke-4.15: bug 1861145 bionic/linux-ibm-gt: bug 1861149 bionic/linux-kvm: bug 1861146 bionic/linux-oem: bug 1861137 bionic/linux-oracle: bug 1861151 bionic/linux-raspi2: bug 1861134 bionic/linux-snapdragon: bug 1861136 bionic/linux/pc-kernel: bug 1861130 bionic/linux/pc-lowlatency-kernel: bug 1861132 xenial/linux-azure: bug 1861156 xenial/linux-gcp: bug 1861160 xenial/linux-hwe: bug 1861164 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/1861165 Title: bionic/linux: 4.15.0-87.87 -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 package in Ubuntu: Invalid Status in linux 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Proposed phase-changed: Saturday, 01. February 2020 03:31 UTC reason: promote-to-proposed: Stalled -- ready for review trackers: bionic/linux-aws: bug 1861141 bionic/linux-fips: bug 1861152 bionic/linux-gke-4.15: bug 1861145 bionic/linux-ibm-gt: bug 1861149 bionic/linux-kvm: bug 1861146 bionic/linux-oem: bug 1861137 bionic/linux-oracle: bug 1861151 bionic/linux-raspi2: bug 1861134 bionic/linux-snapdragon: bug 1861136 bionic/linux/pc-kernel: bug 1861130 bionic/linux/pc-lowlatency-kernel: bug 1861132 xenial/linux-azure: bug 1861156 xenial/linux-gcp: bug 1861160 xenial/linux-hwe: bug 1861164 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861165/+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 1861532] Re: brightness control not working
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-435 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1861532 Title: brightness control not working Status in nvidia-graphics-drivers-435 package in Ubuntu: New Bug description: after selecting nvidia-driver-435 in livepatch- additional drivers the brightness control stops working after the first reboot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 31 22:00:02 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 4.15.0-76-generic, x86_64: installed nvidia, 435.21, 5.3.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation Device [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3ffc] InstallationDate: Installed on 2020-01-31 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 81Q4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=084301b5-fdae-4c92-811e-0536a3b7555b ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN35WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y540-17IRH dmi.modalias: dmi:bvnLENOVO:bvrBHCN35WW:bd11/23/2019:svnLENOVO:pn81Q4:pvrLegionY540-17IRH:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLegionY540-17IRH: dmi.product.family: Legion Y540-17IRH dmi.product.name: 81Q4 dmi.product.sku: LENOVO_MT_81Q4_BU_idea_FM_Legion Y540-17IRH dmi.product.version: Legion Y540-17IRH dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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/nvidia-graphics-drivers-435/+bug/1861532/+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 1861532] [NEW] brightness control not working
You have been subscribed to a public bug: after selecting nvidia-driver-435 in livepatch- additional drivers the brightness control stops working after the first reboot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 31 22:00:02 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 4.15.0-76-generic, x86_64: installed nvidia, 435.21, 5.3.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation Device [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3ffc] InstallationDate: Installed on 2020-01-31 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 81Q4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=084301b5-fdae-4c92-811e-0536a3b7555b ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN35WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y540-17IRH dmi.modalias: dmi:bvnLENOVO:bvrBHCN35WW:bd11/23/2019:svnLENOVO:pn81Q4:pvrLegionY540-17IRH:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLegionY540-17IRH: dmi.product.family: Legion Y540-17IRH dmi.product.name: 81Q4 dmi.product.sku: LENOVO_MT_81Q4_BU_idea_FM_Legion Y540-17IRH dmi.product.version: Legion Y540-17IRH dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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 ** Affects: nvidia-graphics-drivers-435 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- brightness control not working https://bugs.launchpad.net/bugs/1861532 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 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 1859958] Re: kvm clients receive lots auf segfaults
@ ben980: can you post the required logs? i can't from this system sorry @ all -- 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/1859958 Title: kvm clients receive lots auf segfaults Status in linux package in Ubuntu: Incomplete Bug description: Kubuntu 19.10 on a Z420 Workstation with 32GB ECC RAM / CPU E5-2690 (v0) looks like the same problem as the redhat bug https://bugzilla.redhat.com/show_bug.cgi?id=1738386 symptoms are two different kernel WARNINGS; but kvm guests receive lots of segfaults; this is for windows oder linux guests even bluescreens happens: looks like it always happens on CPU 11; no syslog messages about bad ram (ecc errors) and memtest shows no bad ram: there a two types of warnings: journalctl | grep WARNING:.CPU Dec 17 20:53:22 XYZXYZ kernel: WARNING: CPU: 11 PID: 4391 at arch/x86/kvm/x86.c:8056 vcpu_enter_guest+0xd2b/0xf00 [kvm] Dec 23 23:10:40 XYZXYZ kernel: WARNING: CPU: 11 PID: 4391 at arch/x86/kernel/fpu/core.c:360 fpregs_assert_state_consistent+0x36/0x50 Jan 04 09:35:35 XYZXYZ kernel: WARNING: CPU: 11 PID: 7357 at arch/x86/kvm/x86.c:8056 vcpu_enter_guest+0xd2b/0xf00 [kvm] Jan 06 20:21:16 XYZXYZ kernel: WARNING: CPU: 11 PID: 7357 at arch/x86/kernel/fpu/core.c:360 fpregs_assert_state_consistent+0x36/0x50 Jan 16 09:26:22 XYZXYZ kernel: WARNING: CPU: 11 PID: 16621 at arch/x86/kvm/x86.c:8056 vcpu_enter_guest+0xd2b/0xf00 [kvm] # first type: vmlinuz-5.3.0-24-generic Dec 23 23:10:40 XYZXYZ kernel: WARNING: CPU: 11 PID: 4391 at arch/x86/kernel/fpu/core.c:360 fpregs_assert_state_consistent+0x36/0x50 Dec 23 23:10:40 XYZXYZ kernel: Modules linked in: nls_utf8 isofs xt_policy chacha_x86_64 chacha_generic poly1305_x86_64 poly1305_generic chacha20poly1305 vhost Dec 23 23:10:40 XYZXYZ kernel: snd_seq_midi_emul snd_cmipci sb_edac snd_hda_codec snd_mpu401_uart snd_hda_core snd_opl3_lib x86_pkg_temp_thermal intel_powercl Dec 23 23:10:40 XYZXYZ kernel: firewire_ohci isci vfio_pci ahci drm firewire_core vfio_virqfd e1000e libsas i2c_i801 libahci lpc_ich vfio_iommu_type1 crc_itu_ Dec 23 23:10:40 XYZXYZ kernel: CPU: 11 PID: 4391 Comm: CPU 0/KVM Tainted: G W 5.3.0-24-generic #26-Ubuntu Dec 23 23:10:40 XYZXYZ kernel: Hardware name: Hewlett-Packard HP Z420 Workstation/1589, BIOS J61 v03.95 06/13/2019 Dec 23 23:10:40 XYZXYZ kernel: RIP: 0010:fpregs_assert_state_consistent+0x36/0x50 Dec 23 23:10:40 XYZXYZ kernel: Code: 6b 01 00 48 8b 10 48 89 e5 80 e6 40 75 1e 48 8d 90 80 13 00 00 65 8b 35 d8 25 bd 7a 65 48 8b 0c 25 40 6b 01 00 48 39 d1 74 Dec 23 23:10:40 XYZXYZ kernel: RSP: 0018:a4ad021fbd40 EFLAGS: 00010203 Dec 23 23:10:40 XYZXYZ kernel: RAX: 8e92e33adc00 RBX: 8e92c7af8000 RCX: Dec 23 23:10:40 XYZXYZ kernel: RDX: 8e92e33aef80 RSI: 000b RDI: 01d9 Dec 23 23:10:40 XYZXYZ kernel: RBP: a4ad021fbd40 R08: 8e92c7b2d200 R09: 0014 Dec 23 23:10:40 XYZXYZ kernel: R10: 8e928863fbc0 R11: R12: 000b Dec 23 23:10:40 XYZXYZ kernel: R13: 000b R14: 8e92c7af8058 R15: 8e92c7af8000 Dec 23 23:10:40 XYZXYZ kernel: FS: 7f2b854bd700() GS:8e932fac() knlGS: Dec 23 23:10:40 XYZXYZ kernel: CS: 0010 DS: ES: CR0: 80050033 Dec 23 23:10:40 XYZXYZ kernel: CR2: 0448 CR3: 0007e6a44003 CR4: 000626e0 Dec 23 23:10:40 XYZXYZ kernel: Call Trace: Dec 23 23:10:40 XYZXYZ kernel: kvm_arch_vcpu_load+0x6f/0x290 [kvm] Dec 23 23:10:40 XYZXYZ kernel: vcpu_load+0x2c/0x40 [kvm] Dec 23 23:10:40 XYZXYZ kernel: kvm_arch_vcpu_ioctl_run+0x1b/0x590 [kvm] Dec 23 23:10:40 XYZXYZ kernel: kvm_vcpu_ioctl+0x24b/0x610 [kvm] Dec 23 23:10:40 XYZXYZ kernel: ? __seccomp_filter+0x7e/0x680 Dec 23 23:10:40 XYZXYZ kernel: ? futex_wake+0x8b/0x190 Dec 23 23:10:40 XYZXYZ kernel: do_vfs_ioctl+0x407/0x670 Dec 23 23:10:40 XYZXYZ kernel: ? __secure_computing+0x42/0xe0 Dec 23 23:10:40 XYZXYZ kernel: ksys_ioctl+0x67/0x90 Dec 23 23:10:40 XYZXYZ kernel: __x64_sys_ioctl+0x1a/0x20 Dec 23 23:10:40 XYZXYZ kernel: do_syscall_64+0x5a/0x130 Dec 23 23:10:40 XYZXYZ kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Dec 23 23:10:40 XYZXYZ kernel: RIP: 0033:0x7f2b87ae667b Dec 23 23:10:40 XYZXYZ kernel: Code: 0f 1e fa 48 8b 05 15 28 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f Dec 23 23:10:40 XYZXYZ kernel: RSP: 002b:7f2b854bc5f8 EFLAGS: 0246 ORIG_RAX: 0010 Dec 23 23:10:40 XYZXYZ kernel: RAX: ffda RBX: ae80 RCX: 7f2b87ae667b Dec 23 23:10:40 XYZXYZ kernel: RDX: RSI: ae80 RDI: 0014 Dec 23 23:10:40 XYZXYZ kernel: RBP: 55712b5fde30 R08: 55712add7e70 R09:
[Kernel-packages] [Bug 1859958] Re: kvm clients receive lots auf segfaults
@ ben980: are you using vfio gpu pass-through? first i thought it was bad hardware (cpu11) but it changes between boots; i got in on cpu9 on another boot and nothing on cpu11 this time; segfaults in the vm are not visible on the host, no entry in dmesg is there a debug option for kvm to show more about this? -- 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/1859958 Title: kvm clients receive lots auf segfaults Status in linux package in Ubuntu: Incomplete Bug description: Kubuntu 19.10 on a Z420 Workstation with 32GB ECC RAM / CPU E5-2690 (v0) looks like the same problem as the redhat bug https://bugzilla.redhat.com/show_bug.cgi?id=1738386 symptoms are two different kernel WARNINGS; but kvm guests receive lots of segfaults; this is for windows oder linux guests even bluescreens happens: looks like it always happens on CPU 11; no syslog messages about bad ram (ecc errors) and memtest shows no bad ram: there a two types of warnings: journalctl | grep WARNING:.CPU Dec 17 20:53:22 XYZXYZ kernel: WARNING: CPU: 11 PID: 4391 at arch/x86/kvm/x86.c:8056 vcpu_enter_guest+0xd2b/0xf00 [kvm] Dec 23 23:10:40 XYZXYZ kernel: WARNING: CPU: 11 PID: 4391 at arch/x86/kernel/fpu/core.c:360 fpregs_assert_state_consistent+0x36/0x50 Jan 04 09:35:35 XYZXYZ kernel: WARNING: CPU: 11 PID: 7357 at arch/x86/kvm/x86.c:8056 vcpu_enter_guest+0xd2b/0xf00 [kvm] Jan 06 20:21:16 XYZXYZ kernel: WARNING: CPU: 11 PID: 7357 at arch/x86/kernel/fpu/core.c:360 fpregs_assert_state_consistent+0x36/0x50 Jan 16 09:26:22 XYZXYZ kernel: WARNING: CPU: 11 PID: 16621 at arch/x86/kvm/x86.c:8056 vcpu_enter_guest+0xd2b/0xf00 [kvm] # first type: vmlinuz-5.3.0-24-generic Dec 23 23:10:40 XYZXYZ kernel: WARNING: CPU: 11 PID: 4391 at arch/x86/kernel/fpu/core.c:360 fpregs_assert_state_consistent+0x36/0x50 Dec 23 23:10:40 XYZXYZ kernel: Modules linked in: nls_utf8 isofs xt_policy chacha_x86_64 chacha_generic poly1305_x86_64 poly1305_generic chacha20poly1305 vhost Dec 23 23:10:40 XYZXYZ kernel: snd_seq_midi_emul snd_cmipci sb_edac snd_hda_codec snd_mpu401_uart snd_hda_core snd_opl3_lib x86_pkg_temp_thermal intel_powercl Dec 23 23:10:40 XYZXYZ kernel: firewire_ohci isci vfio_pci ahci drm firewire_core vfio_virqfd e1000e libsas i2c_i801 libahci lpc_ich vfio_iommu_type1 crc_itu_ Dec 23 23:10:40 XYZXYZ kernel: CPU: 11 PID: 4391 Comm: CPU 0/KVM Tainted: G W 5.3.0-24-generic #26-Ubuntu Dec 23 23:10:40 XYZXYZ kernel: Hardware name: Hewlett-Packard HP Z420 Workstation/1589, BIOS J61 v03.95 06/13/2019 Dec 23 23:10:40 XYZXYZ kernel: RIP: 0010:fpregs_assert_state_consistent+0x36/0x50 Dec 23 23:10:40 XYZXYZ kernel: Code: 6b 01 00 48 8b 10 48 89 e5 80 e6 40 75 1e 48 8d 90 80 13 00 00 65 8b 35 d8 25 bd 7a 65 48 8b 0c 25 40 6b 01 00 48 39 d1 74 Dec 23 23:10:40 XYZXYZ kernel: RSP: 0018:a4ad021fbd40 EFLAGS: 00010203 Dec 23 23:10:40 XYZXYZ kernel: RAX: 8e92e33adc00 RBX: 8e92c7af8000 RCX: Dec 23 23:10:40 XYZXYZ kernel: RDX: 8e92e33aef80 RSI: 000b RDI: 01d9 Dec 23 23:10:40 XYZXYZ kernel: RBP: a4ad021fbd40 R08: 8e92c7b2d200 R09: 0014 Dec 23 23:10:40 XYZXYZ kernel: R10: 8e928863fbc0 R11: R12: 000b Dec 23 23:10:40 XYZXYZ kernel: R13: 000b R14: 8e92c7af8058 R15: 8e92c7af8000 Dec 23 23:10:40 XYZXYZ kernel: FS: 7f2b854bd700() GS:8e932fac() knlGS: Dec 23 23:10:40 XYZXYZ kernel: CS: 0010 DS: ES: CR0: 80050033 Dec 23 23:10:40 XYZXYZ kernel: CR2: 0448 CR3: 0007e6a44003 CR4: 000626e0 Dec 23 23:10:40 XYZXYZ kernel: Call Trace: Dec 23 23:10:40 XYZXYZ kernel: kvm_arch_vcpu_load+0x6f/0x290 [kvm] Dec 23 23:10:40 XYZXYZ kernel: vcpu_load+0x2c/0x40 [kvm] Dec 23 23:10:40 XYZXYZ kernel: kvm_arch_vcpu_ioctl_run+0x1b/0x590 [kvm] Dec 23 23:10:40 XYZXYZ kernel: kvm_vcpu_ioctl+0x24b/0x610 [kvm] Dec 23 23:10:40 XYZXYZ kernel: ? __seccomp_filter+0x7e/0x680 Dec 23 23:10:40 XYZXYZ kernel: ? futex_wake+0x8b/0x190 Dec 23 23:10:40 XYZXYZ kernel: do_vfs_ioctl+0x407/0x670 Dec 23 23:10:40 XYZXYZ kernel: ? __secure_computing+0x42/0xe0 Dec 23 23:10:40 XYZXYZ kernel: ksys_ioctl+0x67/0x90 Dec 23 23:10:40 XYZXYZ kernel: __x64_sys_ioctl+0x1a/0x20 Dec 23 23:10:40 XYZXYZ kernel: do_syscall_64+0x5a/0x130 Dec 23 23:10:40 XYZXYZ kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Dec 23 23:10:40 XYZXYZ kernel: RIP: 0033:0x7f2b87ae667b Dec 23 23:10:40 XYZXYZ kernel: Code: 0f 1e fa 48 8b 05 15 28 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f Dec 23 23:10:40 XYZXYZ kernel: RSP: 002b:7f2b854bc5f8 EFLAGS: 0246 ORIG_RAX: 0010 Dec 23 23:10:40 XYZXYZ kernel: RAX: ffda RBX:
[Kernel-packages] [Bug 1861470] Re: BIOS logo reappears mid-boot after the purple screen
This is an improvement! Previously, during that time period the whole display (at least on laptops) would be powered off and people saw a temporary backlight flicker. With this in place we might be able to to implement a flickerfree boot! I will double check what we need to change in the theme to ensure our boot now has less flicker. Please keep the kernel as is, and we will tweak the themes to behave better. ** Also affects: plymouth (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861470 Title: BIOS logo reappears mid-boot after the purple screen Status in grub2 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-signed-5.4 package in Ubuntu: Confirmed Status in plymouth package in Ubuntu: New Bug description: BIOS logo (the ACPI BGRT graphic) reappears mid-boot after the purple screen. This seems to be happening reliably on multiple focal machines: 0. Turn on or reboot the machine. 1. See the BIOS logo. 2. See a blank purple screen (grub) 3. See the BIOS logo again (this bug) 4. See the purple screen with Ubuntu logo (plymouth) 5. See the login screen I believe this is related to ACPI BGRT changes in the kernel. And I guess it wouldn't even need fixing if we just eliminated the blank purple grub screen (step 2)... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Fri Jan 31 11:31:44 2020 InstallationDate: Installed on 2020-01-30 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan1316 F pulseaudio DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-30 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) MachineType: LENOVO 20KFCTO1WW Package: linux-signed-5.4 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=50f3b272-d351-4a2a-9661-d39e9fcf2195 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 RelatedPackageVersions: linux-restricted-modules-5.4.0-12-generic N/A linux-backports-modules-5.4.0-12-generic N/A linux-firmware1.185 Tags: focal Uname: Linux 5.4.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N20ET51W (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KFCTO1WW 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:bvrN20ET51W(1.36):bd01/10/2020:svnLENOVO:pn20KFCTO1WW:pvrThinkPadX280:rvnLENOVO:rn20KFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X280 dmi.product.name: 20KFCTO1WW dmi.product.sku: LENOVO_MT_20KF_BU_Think_FM_ThinkPad X280 dmi.product.version: ThinkPad X280 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1861470/+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 1856103] Re: [CML] New device IDs for CMP-V
** Description changed: new device IDs are required for CMP-V, whether they are published or not. Once that is clarified, documentations and device drivers need to update accordingly. ControllerKernel Version Commit Approved to be published Comments GPIO INT3451| Same as for Sunrisepoint-H https://lore.kernel.org/linux-gpio/20200116110951.31644-1-andriy.shevche...@linux.intel.com/ SPI NOR 0xa3a4 NPK 0xa3a6v5.5-rc3e4de2a5d51f9 HS UART 0xa3a7 0xa3a8 0xa3e6 https://lore.kernel.org/lkml/20200113125729.8576-1-andriy.shevche...@linux.intel.com/ - SPI 0xa3a9 0xa3aa https://lore.kernel.org/lkml/20200113125729.8576-1-andriy.shevche...@linux.intel.com/ + SPI 0xa3a9 0xa3aa https://lore.kernel.org/lkml/20200113125729.8576-1-andriy.shevche...@linux.intel.com/ I²C 0xa3e0 0xa3e1 0xa3e2 0xa3e3 Next https://lore.kernel.org/lkml/20200113125729.8576-1-andriy.shevche...@linux.intel.com/ - SMBus 0xa3a3 + SMBus 0xa3a3 f53938d2c79a USB Device Controller 0xa3b0 Target Kernel: 5.5 Target Release: 20.04 -- 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/1856103 Title: [CML] New device IDs for CMP-V Status in intel: New Status in linux package in Ubuntu: Triaged Bug description: new device IDs are required for CMP-V, whether they are published or not. Once that is clarified, documentations and device drivers need to update accordingly. ControllerKernel Version Commit Approved to be published Comments GPIO INT3451| Same as for Sunrisepoint-H https://lore.kernel.org/linux-gpio/20200116110951.31644-1-andriy.shevche...@linux.intel.com/ SPI NOR 0xa3a4 NPK 0xa3a6v5.5-rc3e4de2a5d51f9 HS UART 0xa3a7 0xa3a8 0xa3e6 https://lore.kernel.org/lkml/20200113125729.8576-1-andriy.shevche...@linux.intel.com/ SPI 0xa3a9 0xa3aa https://lore.kernel.org/lkml/20200113125729.8576-1-andriy.shevche...@linux.intel.com/ I²C 0xa3e0 0xa3e1 0xa3e2 0xa3e3 Next https://lore.kernel.org/lkml/20200113125729.8576-1-andriy.shevche...@linux.intel.com/ SMBus 0xa3a3 f53938d2c79a USB Device Controller 0xa3b0 Target Kernel: 5.5 Target Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1856103/+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 1861554] Re: Radeon mobility HD3450 (RV620) heavy screen flickering after trying to upgrade kernel 4.15.0-54
Finally I was able to generate an apport file, here it is: ** Attachment added: "apport.linux.kyoh30em.apport" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861554/+attachment/5324636/+files/apport.linux.kyoh30em.apport ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Description changed: laptop Asus x50sl with graphic card AMD rv620 / Mobility Radeon HD3450. - Distro: Linux Mint 19.2 Tinabase: Ubuntu 18.04 bionic. + Distro: Linux Mint 19.2 Tina base: Ubuntu 18.04 bionic. This happen trying any distro. I tried Ubuntu, Manjaro, Debian, Deepin, MX and so on. I'm stuck with Kernel 4.15.0-54 and 5.0.0-20 (and the contemporary 5.3 kernel). I cannot upgrade to newer kernels. Seems that the fixes for bug #1791312 broke my kind of card. here is a video: https://youtu.be/9Rez7s0V6iA here is another user with same problem: https://forums.linuxmint.com/viewtopic.php?p=1702005#p1702005 -- 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/1861554 Title: Radeon mobility HD3450 (RV620) heavy screen flickering after trying to upgrade kernel 4.15.0-54 Status in linux package in Ubuntu: Confirmed Bug description: laptop Asus x50sl with graphic card AMD rv620 / Mobility Radeon HD3450. Distro: Linux Mint 19.2 Tina base: Ubuntu 18.04 bionic. This happen trying any distro. I tried Ubuntu, Manjaro, Debian, Deepin, MX and so on. I'm stuck with Kernel 4.15.0-54 and 5.0.0-20 (and the contemporary 5.3 kernel). I cannot upgrade to newer kernels. Seems that the fixes for bug #1791312 broke my kind of card. here is a video: https://youtu.be/9Rez7s0V6iA here is another user with same problem: https://forums.linuxmint.com/viewtopic.php?p=1702005#p1702005 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861554/+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 1861554] Re: Radeon mobility HD3450 (RV620) heavy screen flickering after trying to upgrade kernel 4.15.0-54
** Description changed: laptop Asus x50sl with graphic card AMD rv620 / Mobility Radeon HD3450. + Distro: Linux Mint 19.2 Tinabase: Ubuntu 18.04 bionic. I'm stuck with Kernel 4.15.0-54 and 5.0.0-20 (and the contemporary 5.3 kernel). I cannot upgrade to newer kernels. Seems that the fixes for bug #1791312 broke my kind of card. here is a video: https://youtu.be/9Rez7s0V6iA here is another user with same problem: https://forums.linuxmint.com/viewtopic.php?p=1702005#p1702005 ** Description changed: laptop Asus x50sl with graphic card AMD rv620 / Mobility Radeon HD3450. Distro: Linux Mint 19.2 Tinabase: Ubuntu 18.04 bionic. + This happen trying any distro. I tried Ubuntu, Manjaro, Debian, Deepin and so on. I'm stuck with Kernel 4.15.0-54 and 5.0.0-20 (and the contemporary 5.3 kernel). I cannot upgrade to newer kernels. Seems that the fixes for bug #1791312 broke my kind of card. here is a video: https://youtu.be/9Rez7s0V6iA here is another user with same problem: https://forums.linuxmint.com/viewtopic.php?p=1702005#p1702005 ** Description changed: laptop Asus x50sl with graphic card AMD rv620 / Mobility Radeon HD3450. Distro: Linux Mint 19.2 Tinabase: Ubuntu 18.04 bionic. - This happen trying any distro. I tried Ubuntu, Manjaro, Debian, Deepin and so on. + This happen trying any distro. I tried Ubuntu, Manjaro, Debian, Deepin, MX and so on. I'm stuck with Kernel 4.15.0-54 and 5.0.0-20 (and the contemporary 5.3 kernel). I cannot upgrade to newer kernels. Seems that the fixes for bug #1791312 broke my kind of card. here is a video: https://youtu.be/9Rez7s0V6iA here is another user with same problem: https://forums.linuxmint.com/viewtopic.php?p=1702005#p1702005 -- 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/1861554 Title: Radeon mobility HD3450 (RV620) heavy screen flickering after trying to upgrade kernel 4.15.0-54 Status in linux package in Ubuntu: Incomplete Bug description: laptop Asus x50sl with graphic card AMD rv620 / Mobility Radeon HD3450. Distro: Linux Mint 19.2 Tinabase: Ubuntu 18.04 bionic. This happen trying any distro. I tried Ubuntu, Manjaro, Debian, Deepin, MX and so on. I'm stuck with Kernel 4.15.0-54 and 5.0.0-20 (and the contemporary 5.3 kernel). I cannot upgrade to newer kernels. Seems that the fixes for bug #1791312 broke my kind of card. here is a video: https://youtu.be/9Rez7s0V6iA here is another user with same problem: https://forums.linuxmint.com/viewtopic.php?p=1702005#p1702005 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861554/+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 1861554] 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 1861554 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/1861554 Title: Radeon mobility HD3450 (RV620) heavy screen flickering after trying to upgrade kernel 4.15.0-54 Status in linux package in Ubuntu: Incomplete Bug description: laptop Asus x50sl with graphic card AMD rv620 / Mobility Radeon HD3450. Distro: Linux Mint 19.2 Tinabase: Ubuntu 18.04 bionic. This happen trying any distro. I tried Ubuntu, Manjaro, Debian, Deepin, MX and so on. I'm stuck with Kernel 4.15.0-54 and 5.0.0-20 (and the contemporary 5.3 kernel). I cannot upgrade to newer kernels. Seems that the fixes for bug #1791312 broke my kind of card. here is a video: https://youtu.be/9Rez7s0V6iA here is another user with same problem: https://forums.linuxmint.com/viewtopic.php?p=1702005#p1702005 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861554/+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 1861554] Re: Radeon mobility HD3450 (RV620) heavy screen flickering after kernel 4.15.0-54
please tell me what other docs I can provide. I tried to generate an apport log but my distro uses systemd-coredump and I don't know how to generate a log. I tried to install apport removing coredump but does not complete the log generation. ** Summary changed: - Radeon mobility HD3450 (RV620) heavy screen flickering after kernel 4.15.0-54 + Radeon mobility HD3450 (RV620) heavy screen flickering after trying to upgrade kernel 4.15.0-54 -- 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/1861554 Title: Radeon mobility HD3450 (RV620) heavy screen flickering after trying to upgrade kernel 4.15.0-54 Status in linux package in Ubuntu: Incomplete Bug description: laptop Asus x50sl with graphic card AMD rv620 / Mobility Radeon HD3450. Distro: Linux Mint 19.2 Tinabase: Ubuntu 18.04 bionic. This happen trying any distro. I tried Ubuntu, Manjaro, Debian, Deepin, MX and so on. I'm stuck with Kernel 4.15.0-54 and 5.0.0-20 (and the contemporary 5.3 kernel). I cannot upgrade to newer kernels. Seems that the fixes for bug #1791312 broke my kind of card. here is a video: https://youtu.be/9Rez7s0V6iA here is another user with same problem: https://forums.linuxmint.com/viewtopic.php?p=1702005#p1702005 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861554/+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 1861554] Re: Radeon mobility HD3450 (RV620) heavy screen flickering after kernel 4.15.0-54
** Attachment added: "synth4.15.0-54.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861554/+attachment/5324633/+files/synth4.15.0-54.txt ** Description changed: laptop Asus x50sl with graphic card AMD rv620 / Mobility Radeon HD3450. I'm stuck with Kernel 4.15.0-54 and 5.0.0-20 (and the contemporary 5.3 kernel). I cannot upgrade to newer kernels. Seems that the fixes for bug #1791312 broke my kind of card. + + here is a video: + https://youtu.be/9Rez7s0V6iA + + here is another user with same problem: + https://forums.linuxmint.com/viewtopic.php?p=1702005#p1702005 -- 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/1861554 Title: Radeon mobility HD3450 (RV620) heavy screen flickering after trying to upgrade kernel 4.15.0-54 Status in linux package in Ubuntu: Incomplete Bug description: laptop Asus x50sl with graphic card AMD rv620 / Mobility Radeon HD3450. Distro: Linux Mint 19.2 Tinabase: Ubuntu 18.04 bionic. I'm stuck with Kernel 4.15.0-54 and 5.0.0-20 (and the contemporary 5.3 kernel). I cannot upgrade to newer kernels. Seems that the fixes for bug #1791312 broke my kind of card. here is a video: https://youtu.be/9Rez7s0V6iA here is another user with same problem: https://forums.linuxmint.com/viewtopic.php?p=1702005#p1702005 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861554/+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 1861554] Re: Radeon mobility HD3450 (RV620) heavy screen flickering after kernel 4.15.0-54
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1861554 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- 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/1861554 Title: Radeon mobility HD3450 (RV620) heavy screen flickering after trying to upgrade kernel 4.15.0-54 Status in linux package in Ubuntu: Incomplete Bug description: laptop Asus x50sl with graphic card AMD rv620 / Mobility Radeon HD3450. Distro: Linux Mint 19.2 Tinabase: Ubuntu 18.04 bionic. I'm stuck with Kernel 4.15.0-54 and 5.0.0-20 (and the contemporary 5.3 kernel). I cannot upgrade to newer kernels. Seems that the fixes for bug #1791312 broke my kind of card. here is a video: https://youtu.be/9Rez7s0V6iA here is another user with same problem: https://forums.linuxmint.com/viewtopic.php?p=1702005#p1702005 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861554/+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 1861554] [NEW] Radeon mobility HD3450 (RV620) heavy screen flickering after trying to upgrade kernel 4.15.0-54
Public bug reported: laptop Asus x50sl with graphic card AMD rv620 / Mobility Radeon HD3450. Distro: Linux Mint 19.2 Tinabase: Ubuntu 18.04 bionic. I'm stuck with Kernel 4.15.0-54 and 5.0.0-20 (and the contemporary 5.3 kernel). I cannot upgrade to newer kernels. Seems that the fixes for bug #1791312 broke my kind of card. here is a video: https://youtu.be/9Rez7s0V6iA here is another user with same problem: https://forums.linuxmint.com/viewtopic.php?p=1702005#p1702005 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Attachment added: "lspci-vnvn4.15.0-54.log" https://bugs.launchpad.net/bugs/1861554/+attachment/5324632/+files/lspci-vnvn4.15.0-54.log -- 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/1861554 Title: Radeon mobility HD3450 (RV620) heavy screen flickering after trying to upgrade kernel 4.15.0-54 Status in linux package in Ubuntu: Incomplete Bug description: laptop Asus x50sl with graphic card AMD rv620 / Mobility Radeon HD3450. Distro: Linux Mint 19.2 Tinabase: Ubuntu 18.04 bionic. I'm stuck with Kernel 4.15.0-54 and 5.0.0-20 (and the contemporary 5.3 kernel). I cannot upgrade to newer kernels. Seems that the fixes for bug #1791312 broke my kind of card. here is a video: https://youtu.be/9Rez7s0V6iA here is another user with same problem: https://forums.linuxmint.com/viewtopic.php?p=1702005#p1702005 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861554/+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 1861214] Re: eoan/linux: 5.3.0-40.32 -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 -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Saturday, 01. February 2020 07:36 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa meta:failed,signed:depwait + promote-to-proposed: Pending -- builds not complete in ppa meta:failed trackers: bionic/linux-hwe: bug 1861212 eoan/linux-aws: bug 1861199 eoan/linux-azure: bug 1861201 eoan/linux-gcp: bug 1861205 eoan/linux-kvm: bug 1861206 eoan/linux-oracle: bug 1861208 eoan/linux-raspi2: bug 1861197 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/1861214 Title: eoan/linux: 5.3.0-40.32 -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 package in Ubuntu: Invalid 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 -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Saturday, 01. February 2020 07:36 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa meta:failed trackers: bionic/linux-hwe: bug 1861212 eoan/linux-aws: bug 1861199 eoan/linux-azure: bug 1861201 eoan/linux-gcp: bug 1861205 eoan/linux-kvm: bug 1861206 eoan/linux-oracle: bug 1861208 eoan/linux-raspi2: bug 1861197 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861214/+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
