[Kernel-packages] [Bug 1920707] [NEW] AMD Trinity HDMI Audio Controller: no sound
Public bug reported: Starting with linux-4.15.0-137-generic, there is no sound at all on a system with an AMD A4-5300. >From a working kernel: Mar 22 05:00:29 richie kernel: [ 33.029621] snd_hda_intel :00:01.1: Force to non-snoop mode [...] Mar 22 05:00:29 richie kernel: [ 33.589291] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:01.1/sound/card0/input5 Mar 22 05:00:29 richie kernel: [ 33.601773] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC887-VD: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line Mar 22 05:00:29 richie kernel: [ 33.601776] snd_hda_codec_realtek hdaudioC1D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) Mar 22 05:00:29 richie kernel: [ 33.601779] snd_hda_codec_realtek hdaudioC1D0:hp_outs=1 (0x1b/0x0/0x0/0x0/0x0) Mar 22 05:00:29 richie kernel: [ 33.601781] snd_hda_codec_realtek hdaudioC1D0:mono: mono_out=0x0 Mar 22 05:00:29 richie kernel: [ 33.601782] snd_hda_codec_realtek hdaudioC1D0:inputs: Mar 22 05:00:29 richie kernel: [ 33.601784] snd_hda_codec_realtek hdaudioC1D0: Front Mic=0x19 Mar 22 05:00:29 richie kernel: [ 33.601786] snd_hda_codec_realtek hdaudioC1D0: Rear Mic=0x18 Mar 22 05:00:29 richie kernel: [ 33.601787] snd_hda_codec_realtek hdaudioC1D0: Line=0x1a Mar 22 05:00:29 richie kernel: [ 33.614365] input: HD-Audio Generic Front Mic as /devices/pci:00/:00:14.2/sound/card1/input6 Mar 22 05:00:29 richie kernel: [ 33.614426] input: HD-Audio Generic Rear Mic as /devices/pci:00/:00:14.2/sound/card1/input7 Mar 22 05:00:29 richie kernel: [ 33.614481] input: HD-Audio Generic Line as /devices/pci:00/:00:14.2/sound/card1/input8 Mar 22 05:00:29 richie kernel: [ 33.614536] input: HD-Audio Generic Line Out as /devices/pci:00/:00:14.2/sound/card1/input9 Mar 22 05:00:29 richie kernel: [ 33.614597] input: HD-Audio Generic Front Headphone as /devices/pci:00/:00:14.2/sound/card1/input10 $ lsmod | grep -F snd snd81920 21 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm,snd_rawmidi snd_hda_codec 126976 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek snd_hda_codec_generic73728 1 snd_hda_codec_realtek snd_hda_codec_hdmi 49152 1 snd_hda_codec_realtek 106496 1 snd_hda_core 81920 5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek snd_hda_intel 45056 5 snd_hwdep 20480 1 snd_hda_codec snd_pcm98304 4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core snd_rawmidi32768 1 snd_seq_midi snd_seq65536 2 snd_seq_midi,snd_seq_midi_event snd_seq_device 16384 3 snd_seq,snd_seq_midi,snd_rawmidi snd_seq_midi 16384 0 snd_seq_midi_event 16384 1 snd_seq_midi snd_timer 32768 2 snd_seq,snd_pcm On a broken kernel, dmesg contains no information about the snd_* modules, and lsmod shows that none have loaded. In both cases lspci -v gives the same details: 00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Trinity HDMI Audio Controller Subsystem: Micro-Star International Co., Ltd. [MSI] Trinity HDMI Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 5 Memory at feb44000 (32-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 Kernel modules: snd_hda_intel `sudo modprobe snd_hda_intel` loads all the correct modules and brings sound back. For some reason the newer kernels aren't loading snd_hda_intel (or something related) when it should be. Will update after testing mainline kernels, etc. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-139-generic 4.15.0-139.143 ProcVersionSignature: Ubuntu 4.15.0-139.143-generic 4.15.18 Uname: Linux 4.15.0-139-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 Date: Mon Mar 22 04:42:26 2021 HibernationDevice: RESUME=UUID=5d6634dd-fb1b-49f6-b17a-4197a3814382 InstallationDate: Installed on 2015-11-28 (1940 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7721 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-139-generic root=UUID=6c84fef8-256e-4a5c-9033-28e0b9342a56 ro zswap.enabled=1 quiet splash zswap.compressor=lz4hc zswap.max_pool_percent=20 zswap.zpool=z3fold vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions:
Re: [Kernel-packages] [Bug 1917138] Re: Bionic kernel 4.15.0-136 causes dosemu2 (with kvm mode) freezes due to lack of KVM patch
Dear Guilherme,
I just want to inform you . Today my kernel is upgraded to
version 4.15.0-139-generic, but the bug is still there.
Thank you.
On Fri, Mar 5, 2021 at 4:50 PM Stefan Bader <1917...@bugs.launchpad.net>
wrote:
> ** Changed in: linux (Ubuntu Bionic)
>Status: In Progress => Fix Committed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1917138
>
> Title:
> Bionic kernel 4.15.0-136 causes dosemu2 (with kvm mode) freezes due to
> lack of KVM patch
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/dosemu2/+bug/1917138/+subscriptions
>
--
Bambang P
http://bpranoto.blogspot.com
--
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/1917138
Title:
Bionic kernel 4.15.0-136 causes dosemu2 (with kvm mode) freezes due to
lack of KVM patch
Status in Dosemu2:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Committed
Bug description:
[Impact]
* Since kernel 4.15.0-136, Bionic kernel included a very complex KVM fix for
a kind of "race" in interrupt window with irqchip-split (reported in [0]). The
fix was proposed in the form of a patch series containing 2 patches [1] - this
was merged in Ubuntu though the stable tree, in the form of the following
commit:
71cc849b7093 ("KVM: x86: Fix split-irqchip vs interrupt injection window
request") [2]
* The problem is that such commit has a companion required commit,
which was not proposed in the stable tree. In fact, there was a
confusion among KVM community and the stable maintainer [3], due to
the lack of such missing commit - because of that, the series was
removed from stable trees 4.14.y and 4.9.y, but the solo commit was
merged alone in Ubuntu kernel.
* Without the companion patch, we might have a KVM infinite "loop" condition
in the core IRQ handling, since the merged commit requires an extra check in
kvm_cpu_has_extint() and a condition "inversion" in kvm_cpu_get_extint(), only
present in the missing companion patch. Users reported that this manifested as
dosemu2 (running in KVM mode) to be stuck in kernel 4.15.0-136 and -137, while
works fine in 4.15.0-135 and the
-137 plus the companion patch.
* So, we hereby backport the companion commit, originally upstream
patch: 72c3bcdcda ("KVM: x86: handle !lapic_in_kernel case in
kvm_cpu_*_extint") [4]
[Test Case]
* The test case proposed was the reported bug: try running dosemu2 (with kvm
mode enabled) and it fails without the companion commit.
* In order to test the correctness of both fixes together, we could
rely in the test proposed in [0] (running a guest with "noapic"), but
it wasn't consistent and the VMM wasn't mentioned, so we might have a
workaround mechanism in qemu, for example, preventing such test to
reproduce the issue.
[Where problems could occur]
* Since this is a KVM core modification, it could affect interrupt handling
in KVM but without the fix, we are already experiencing a bug. Also, both
commits were backported to 5.4.y and 4.19.y, so Focal and subsequent released
are already running with them.
[0]
https://lore.kernel.org/kvm/62918f65ec78f8990278a6a0db0567968fa23e49.ca...@infradead.org/
[1]
https://lore.kernel.org/kvm/20201127112114.3219360-1-pbonz...@redhat.com/
[2] http://git.kernel.org/linus/71cc849b70
[3]
https://lore.kernel.org/stable/d29c4b25-33f6-8d99-7a45-8f4e06f5a...@redhat.com/
[4] http://git.kernel.org/linus/72c3bcdcda
With the latest kernel 4.15.0-136 updates on ubuntu 18.04 and ubuntu
16.04, dosemu2 with kvm freezes boot.
dosemu2 source: https://github.com/dosemu2/dosemu2
dosemu2 package can be obtained from
https://launchpad.net/~dosemu2/+archive/ubuntu/ppa
1. ubuntu version
lsb_release -rd
Description: Ubuntu 18.04.5 LTS
Release: 18.04
2. package version
$ apt-cache policy dosemu2
dosemu2:
Installed: (none)
Candidate: (none)
Version table:
2.0~pre8-2 -1
100 /var/lib/dpkg/status
3. What is expected to happen: The dosemu program runs fine as in previous
kernel version
4. What happened instead: The dosemu freezes on loading
I have also reported this problem to dosemu2 developer, here is my bug report:
https://github.com/dosemu2/dosemu2/issues/1404
To manage notifications about this bug go to:
https://bugs.launchpad.net/dosemu2/+bug/1917138/+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 1917245] Re: HP and Canon support ubuntu LTS linux systems
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1917245 Title: HP and Canon support ubuntu LTS linux systems Status in linux package in Ubuntu: Invalid Bug description: HP and Canon and epson printers and scanners support ubuntu LTS linux systems --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: snowden1435 F pulseaudio /dev/snd/controlC0: snowden1435 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-15 (13 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: MSI MS-7817 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 RelatedPackageVersions: linux-restricted-modules-5.4.0-66-generic N/A linux-backports-modules-5.4.0-66-generic N/A linux-firmware1.187.9 RfKill: Tags: focal Uname: Linux 5.4.0-66-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: 04/21/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917245/+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 1917110] Re: deus ex mankind divide working too slow linux ubuntu 20.04 LTS
What makes you think that this is a Linux bug? Did you bother reporting this to Steam? ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1917110 Title: deus ex mankind divide working too slow linux ubuntu 20.04 LTS Status in linux package in Ubuntu: Incomplete Bug description: deus ex mankind divide working too slow my linux ubuntu 20.04 LTS desktop openGL 3.0 and openGL 2.1 working too slow linux ubuntu 20.04 LTS desktop MSI MS 7817 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: snowden1430 F pulseaudio /dev/snd/controlC0: snowden1430 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-15 (11 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: MSI MS-7817 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 RelatedPackageVersions: linux-restricted-modules-5.4.0-66-generic N/A linux-backports-modules-5.4.0-66-generic N/A linux-firmware1.187.9 RfKill: Tags: focal Uname: Linux 5.4.0-66-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: 04/21/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tessetessu 1400 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-20 (7 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Hewlett-Packard HP Compaq 6000 Pro MT PC Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=2a4fb579-9676-4e2a-8293-120b9188db54 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.187.9 RfKill: Tags: focal Uname: Linux 5.8.0-44-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: 08/25/2009 dmi.bios.release: 1.9 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786G2 v01.09 dmi.board.asset.tag: CZC0195QPD dmi.board.name: 3048h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC0195QPD dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786G2v01.09:bd08/25/2009:br1.9:svnHewlett-Packard:pnHPCompaq6000ProMTPC:pvr:rvnHewlett-Packard:rn3048h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq 6000 Pro MT PC dmi.product.sku: VN784ET#UUW dmi.sys.vendor: Hewlett-Packard --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tessetessu 1414 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-20 (7 days
[Kernel-packages] [Bug 1917112] Re: deus ex human revolution director cut working too slow steam proton
What makes you think that this is a Linux bug? Did you bother reporting this to Steam? ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1917112 Title: deus ex human revolution director cut working too slow steam proton Status in linux package in Ubuntu: Incomplete Bug description: deus ex human revolution director cut working too slow steam proton experimental same is deus ex the fall and deus mandkind divide all deus ex games working too slow working too slow linux kernels 5.4 and linux kernels 5.8 working too slow Computer Information: Manufacturer: Unknown Model: Unknown Form Factor: Desktop No Touch Input Detected Processor Information: CPU Vendor: GenuineIntel CPU Brand: Intel(R) Pentium(R) CPU G3420 @ 3.20GHz CPU Family: 0x6 CPU Model: 0x3c CPU Stepping: 0x3 CPU Type: 0x0 Speed: 3200 Mhz 2 logical processors 2 physical processors HyperThreading: Unsupported FCMOV: Supported SSE2: Supported SSE3: Supported SSSE3: Supported SSE4a: Unsupported SSE41: Supported SSE42: Supported AES: Unsupported AVX: Unsupported AVX2: Unsupported AVX512F: Unsupported AVX512PF: Unsupported AVX512ER: Unsupported AVX512CD: Unsupported AVX512VNNI: Unsupported SHA: Unsupported CMPXCHG16B: Supported LAHF/SAHF: Supported PrefetchW: Unsupported Operating System Version: Ubuntu 20.04.2 LTS (64 bit) Kernel Name: Linux Kernel Version: 5.4.0-66-generic X Server Vendor: The X.Org Foundation X Server Release: 12009000 X Window Manager: GNOME Shell Steam Runtime Version: steam-runtime_0.20201203.1 Video Card: Driver: Intel Open Source Technology Center Mesa DRI Intel(R) HD Graphics (HSW GT1) Driver Version: 3.0 Mesa 20.2.6 OpenGL Version: 3.0 Desktop Color Depth: 24 bits per pixel Monitor Refresh Rate: 60 Hz VendorID: 0x8086 DeviceID: 0x402 Revision Not Detected Number of Monitors: 1 Number of Logical Video Cards: 1 Primary Display Resolution: 1280 x 1024 Desktop Resolution: 1280 x 1024 Primary Display Size: 13.39" x 10.63" (17.09" diag) 34.0cm x 27.0cm (43.4cm diag) Primary VRAM Not Detected Sound card: Audio device: Intel Haswell HDMI Memory: RAM: 3798 Mb VR Hardware: VR Headset: None detected Miscellaneous: UI Language: English LANG: fi_FI.UTF-8 Total Hard Disk Space Available: 937366 Mb Largest Free Hard Disk Block: 851473 Mb The runtime information tool is preparing a report, please wait... --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: snowden1430 F pulseaudio /dev/snd/controlC0: snowden1430 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-15 (11 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: MSI MS-7817 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 RelatedPackageVersions: linux-restricted-modules-5.4.0-66-generic N/A linux-backports-modules-5.4.0-66-generic N/A linux-firmware1.187.9 RfKill: Tags: focal Uname: Linux 5.4.0-66-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: 04/21/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version:
[Kernel-packages] [Bug 1917264] Re: HP and Canon and Epson printers inks status
What debugging have you done to determine that this is a Linux bug, because I very much doubt it is? ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1917264 Title: HP and Canon and Epson printers inks status Status in linux package in Ubuntu: Incomplete Bug description: HP and Canon and Epson printers inks status information how much is colours and black inks status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: snowden1435 F pulseaudio /dev/snd/controlC0: snowden1435 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-15 (13 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: MSI MS-7817 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 RelatedPackageVersions: linux-restricted-modules-5.4.0-66-generic N/A linux-backports-modules-5.4.0-66-generic N/A linux-firmware1.187.9 RfKill: Tags: focal Uname: Linux 5.4.0-66-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: 04/21/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tessetessu 1381 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-20 (8 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUSTeK COMPUTER INC. E402SA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=32c14ba7-6abd-49ad-b9b6-25073031646a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.187.9 Tags: focal Uname: Linux 5.8.0-44-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: 12/14/2015 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E402SA.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E402SA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE402SA.208:bd12/14/2015:br5.6:svnASUSTeKCOMPUTERINC.:pnE402SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE402SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: E dmi.product.name: E402SA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tessetessu 1398 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-20 (8 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" -
[Kernel-packages] [Bug 1920180] Re: Can't detect intel wifi 6235
** Changed in: linux (Ubuntu) Status: Fix Committed => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Alex Hung (alexhung) -- 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/1920180 Title: Can't detect intel wifi 6235 Status in linux package in Ubuntu: In Progress Bug description: Can't detect Wireless intel advance 6235 03:00.0 Network controller [0280]: Intel Corporation Centrino Advanced-N 6235 [8086:088f] (rev 24) Subsystem: Intel Corporation Centrino Advanced-N 6235 [8086:526a] Flags: fast devsel, IRQ 255 Memory at e040 (64-bit, non-prefetchable) [size=8K] Capabilities: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sgo1245 F pulseaudio /dev/snd/controlC0: sgo1245 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-03-15 (4 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: enp0s25 no wireless extensions. lono wireless extensions. MachineType: LENOVO 20AWS0DS0T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic root=UUID=7bbc36d4-b65d-4291-a3b9-dc840a88f20a ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94 RelatedPackageVersions: linux-restricted-modules-5.4.0-67-generic N/A linux-backports-modules-5.4.0-67-generic N/A linux-firmware1.187.10 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no Tags: ulyssa Uname: Linux 5.4.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: GLETA1WW (2.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AWS0DS0T dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLETA1WW(2.55):bd04/20/2020:svnLENOVO:pn20AWS0DS0T:pvrThinkPadT440p:rvnLENOVO:rn20AWS0DS0T:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AWS0DS0T dmi.product.sku: LENOVO_MT_20AW_BU_Think_FM_ThinkPad T440p dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920180/+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 1920660] Re: Missing Commit for 5.4-Kernel breaks xen Dom0
** Tags added: bionic focal regression-update -- 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/1920660 Title: Missing Commit for 5.4-Kernel breaks xen Dom0 Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.4 package in Ubuntu: New Bug description: You commited "xen: Fix event channel callback via INTX/GSI" for kernel 5.4.0-67 for HWE 18.04 and 20.04. This commit is incomplete and breaks Ubuntu as Dom0 for xen. You need also Commit "xen: Fix XenStore initialisation for XS_LOCAL" See https://lkml.org/lkml/2021/1/28/1235 See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 Upstream: Commit: 3499ba8198cad47b731792e5e56b9ec2a78a83a2 Fixing Commit: 5f46400f7a6a4fad635d5a79e2aa5a04a30ffea1 5.10: Commit: fa5f2e04daa44961a1026e93f0cc88caa3c27d3d (5.10.11) Fixing Commit: 5f3d54c00f1f2682cee9c590c22655b0330ffd18 (5.10.13) 5.4: Commit: a09d4e7acdbf276b2096661ee82454ae3dd24d2b (5.4.93) Fixing commit 2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f (5.4.95) Without this patch you cannot start guests (DomU) on this machine! Error message while creating DomU: libxl: error: libxl_device.c:1105:device_backend_callback: Domain X:unable to add device with path / libxl: error: libxl_create.c:1452:domcreate_launch_dm: Domain X:unable to add disk devices See: - https://lkml.org/lkml/2021/1/28/1231 and https://lkml.org/lkml/2021/1/29/14 - https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.107=2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.95 - http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-hwe-5.4/linux-hwe-5.4_5.4.0-67.75~18.04.1/changelog - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920660/+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 1836169] Re: cpuhotplug04 in cpuhotplug from ubuntu_ltp failed on ARM64
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Cosmic) Status: Confirmed => Won't Fix -- 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/1836169 Title: cpuhotplug04 in cpuhotplug from ubuntu_ltp failed on ARM64 Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Status in linux source package in Cosmic: Won't Fix Status in linux source package in Disco: Won't Fix Status in linux source package in Focal: New Bug description: This issue can be found on both ThunderX and Moonshot ARM64 <<>> incrementing stop Name: cpuhotplug04 Date: Thu Jul 11 08:34:50 UTC 2019 Desc: Does it prevent us from offlining the last CPU? sh: echo: I/O error cpuhotplug04 1 TFAIL: Could not offline cpu0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=9 cstime=4 <<>> Steps to run this test: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "cpuhotplug04 cpuhotplug04.sh -l 1" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-25-generic 4.18.0-25.26 ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20 Uname: Linux 4.18.0-25-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 11 06:57 seq crw-rw 1 root audio 116, 33 Jul 11 06:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.4 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jul 11 08:28:42 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.18.0-25-generic N/A linux-backports-modules-4.18.0-25-generic N/A linux-firmware 1.175.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836169/+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 1667750] Re: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13
** Changed in: linux Status: Unknown => Confirmed ** Changed in: linux Importance: Unknown => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1667750 Title: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Status in HWE Next: Fix Released Status in Linux: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Zesty: Fix Released Status in linux source package in Artful: Fix Released Status in linux package in Arch Linux: New Status in linux package in Debian: New Status in linux package in Fedora: Confirmed Bug description: [SRU Justification] [Impact] Dell TB16 docking station has issue to use gigabit ethernet. The ethernet will disconnect unless it's changed to 100Mb/s. [Test Case] Download some big files from the web. User confirms the patch fixes the issue. [Regression Potential] This patch only effects ASMEDIA's ASM1042A. The regression potential is low, also limited to the specific device. --- My system contains a Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter which is on usb3 bus in my docking station (Dell TB16) which is attached to my laptop (Dell XPS9550) via Thunderbolt 3. I get usb related kernel error messages when I initiate a high speed transfer (by issuing wget http://cdimage.ubuntu.com/daily-live/current /zesty-desktop-amd64.iso) and the download fails. This does not happened when the Ethernet adapter is connected to a 100Mb/s switch, but only when connected to 1000Mb/s. It also does not happened with slow traffic (e.g. web page browsing). This is not a new bug with kernel 4.10, but has been going on since at least 4.7 and maybe (probably?) since forever. I'm aware of several others with this configuration (RTL8153 on usb3 behind thunderbolt 3) that have the same issue. This bug is also not specific to Ubuntu; I also get it on Arch Linux. I've also tested and seen this bug with several different models of thunderbolt 3 docks. Here are the relevant kernel log messages: Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9010 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9020 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9030 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9040 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9050 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9060 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9070 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9080 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24
[Kernel-packages] [Bug 1749961] Re: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller
** Changed in: linux Status: Unknown => Confirmed ** Changed in: linux Importance: Unknown => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749961 Title: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller Status in Linux: Confirmed Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: Won't Fix Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux package in Debian: Confirmed Bug description: It was observed that while trying to use a 4K USB webcam connected to USB port provided by ASMedia ASM1142 USB 3.1 Controller, the webcam does not work and kernel log shows the following messages: [431.928016] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928021] xhci_hcd :12:00.0: Looking for event-dma 003f3330e020 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928024] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928026] xhci_hcd :12:00.0: Looking for event-dma 003f3330e030 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928027] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928029] xhci_hcd :12:00.0: Looking for event-dma 003f3330e050 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928386] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 A similar issue was already reported on Launchpad: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667750 The fix to this issue seems to be the following patch: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9da5a109 Tests in our scenario with this patch proved still broken. Our next approach is to modify the patch a bit and re-test. This LP will be used to document our progress in the investigation. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1749961/+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 1914411] Re: Fix broken efifb on graphics device without driver
** Changed in: linux-oem-5.10 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Groovy) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1914411 Title: Fix broken efifb on graphics device without driver Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Status in linux-oem-5.10 source package in Groovy: Invalid Bug description: [Impact] EFIFB stops working after graphics device is runtime suspended in D3cold. [Fix] Prevent the graphics device from being runtime suspended. [Test] With the patch applied, using efifb on graphics device without driver always work, because the device stays at D0 all the time. [Where problems could occur] Potentially this can affect power consumption, if user expects to put graphics device to D3cold, and is fine to get a broken efifb. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1914411/+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 1917674] 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 1917674 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/1917674 Title: [amdgpu] kernel crash when resuming from automatic suspension to RAM (started in 5.7.0, not in 5.6.19) Status in linux package in Ubuntu: Incomplete Status in linux-hwe-5.8 package in Ubuntu: New Bug description: Automatic suspension causes the system to freeze on resume. This doesn't happen if I suspend it manually by opening the system menu and pressing the suspend button. Suspension works flawlessly when it is triggered manually. When the system resumes from automatic suspension, the lock screen is visible but does not respond. It's frozen. A notification says something like "system will suspend shortly due to inactivity". It never goes away. The keyboard responds during this (at least for a while). The CAPS LOCK LED turns on and off as I press it (with no delay). Sometimes I can even switch to another TTY and kill the X server, which is why I'm reporting it against gnome-shell. When switching TTY is impossible, I use the "REISUB" combination to shut down. Either way, I always lose the running session. This is reproducible about 60% of the time. Eventually I ended up disabling it and relying only on manual suspension. # Additional information: 1) Ubuntu 20.04.2 LTS / Release: 20.04 2) gnome-shell 3.36.4-1ubuntu1~20.04.2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 3 16:56:01 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-01-31 (31 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917674/+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 1742302] Re: Kernel 4.13.0-25 broke nvidia driver
4.13 EOL. Closing this bug. ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- 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/1742302 Title: Kernel 4.13.0-25 broke nvidia driver Status in Linux: New Status in linux package in Ubuntu: Won't Fix Bug description: After updating to linux-image-4.13.0-25-generic the binary nvidia driver 387.22 cannot be built. As a result the system does not boot into the desktop environment (in my case, KDE). I've attached the driver build log. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lastique 3049 F pulseaudio /dev/snd/controlC2: lastique 3049 F pulseaudio /dev/snd/controlC3: lastique 3049 F pulseaudio /dev/snd/controlC1: lastique 3049 F pulseaudio CurrentDesktop: KDE Date: Wed Jan 10 02:00:46 2018 InstallationDate: Installed on 2015-05-01 (984 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.13.0-21-generic N/A linux-backports-modules-4.13.0-21-generic N/A linux-firmware 1.169.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-11-03 (67 days ago) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1742302/+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 1667750] Re: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13
** Bug watch added: Linux Kernel Bug Tracker #202541 https://bugzilla.kernel.org/show_bug.cgi?id=202541 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=202541 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/1667750 Title: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Status in HWE Next: Fix Released Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Zesty: Fix Released Status in linux source package in Artful: Fix Released Status in linux package in Arch Linux: New Status in linux package in Debian: New Status in linux package in Fedora: Confirmed Bug description: [SRU Justification] [Impact] Dell TB16 docking station has issue to use gigabit ethernet. The ethernet will disconnect unless it's changed to 100Mb/s. [Test Case] Download some big files from the web. User confirms the patch fixes the issue. [Regression Potential] This patch only effects ASMEDIA's ASM1042A. The regression potential is low, also limited to the specific device. --- My system contains a Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter which is on usb3 bus in my docking station (Dell TB16) which is attached to my laptop (Dell XPS9550) via Thunderbolt 3. I get usb related kernel error messages when I initiate a high speed transfer (by issuing wget http://cdimage.ubuntu.com/daily-live/current /zesty-desktop-amd64.iso) and the download fails. This does not happened when the Ethernet adapter is connected to a 100Mb/s switch, but only when connected to 1000Mb/s. It also does not happened with slow traffic (e.g. web page browsing). This is not a new bug with kernel 4.10, but has been going on since at least 4.7 and maybe (probably?) since forever. I'm aware of several others with this configuration (RTL8153 on usb3 behind thunderbolt 3) that have the same issue. This bug is also not specific to Ubuntu; I also get it on Arch Linux. I've also tested and seen this bug with several different models of thunderbolt 3 docks. Here are the relevant kernel log messages: Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9010 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9020 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9030 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9040 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9050 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9060 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9070 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma
[Kernel-packages] [Bug 1889342] Re: Thunderbolt Dock Loses Monitors
@rhpot1991, would you please share the link about dell forums post? thanks -- 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/1889342 Title: Thunderbolt Dock Loses Monitors Status in linux package in Ubuntu: In Progress Bug description: After a suspend or locking the only way to regain external monitors is to unplug and replug the thunderbolt dock back in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2682 F pulseaudio /dev/snd/controlC0: john 2682 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 00:22:26 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2020-07-13 (15 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9300 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5e141eb0-e03b-4c39-b826-f94e0d2715ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+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 1749961] Re: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller
** Bug watch added: Linux Kernel Bug Tracker #202541 https://bugzilla.kernel.org/show_bug.cgi?id=202541 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=202541 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/1749961 Title: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: Won't Fix Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux package in Debian: Confirmed Bug description: It was observed that while trying to use a 4K USB webcam connected to USB port provided by ASMedia ASM1142 USB 3.1 Controller, the webcam does not work and kernel log shows the following messages: [431.928016] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928021] xhci_hcd :12:00.0: Looking for event-dma 003f3330e020 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928024] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928026] xhci_hcd :12:00.0: Looking for event-dma 003f3330e030 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928027] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928029] xhci_hcd :12:00.0: Looking for event-dma 003f3330e050 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928386] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 A similar issue was already reported on Launchpad: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667750 The fix to this issue seems to be the following patch: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9da5a109 Tests in our scenario with this patch proved still broken. Our next approach is to modify the patch a bit and re-test. This LP will be used to document our progress in the investigation. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1749961/+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 1917674] Re: [amdgpu] kernel crash when resuming from automatic suspension to RAM
** Tags added: regression-release ** Summary changed: - [amdgpu] kernel crash when resuming from automatic suspension to RAM + [amdgpu] kernel crash when resuming from automatic suspension to RAM (started in 5.7.0, not in 5.6.19) ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: linux-hwe-5.8 (Ubuntu) Status: Incomplete => 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/1917674 Title: [amdgpu] kernel crash when resuming from automatic suspension to RAM (started in 5.7.0, not in 5.6.19) Status in linux package in Ubuntu: New Status in linux-hwe-5.8 package in Ubuntu: New Bug description: Automatic suspension causes the system to freeze on resume. This doesn't happen if I suspend it manually by opening the system menu and pressing the suspend button. Suspension works flawlessly when it is triggered manually. When the system resumes from automatic suspension, the lock screen is visible but does not respond. It's frozen. A notification says something like "system will suspend shortly due to inactivity". It never goes away. The keyboard responds during this (at least for a while). The CAPS LOCK LED turns on and off as I press it (with no delay). Sometimes I can even switch to another TTY and kill the X server, which is why I'm reporting it against gnome-shell. When switching TTY is impossible, I use the "REISUB" combination to shut down. Either way, I always lose the running session. This is reproducible about 60% of the time. Eventually I ended up disabling it and relying only on manual suspension. # Additional information: 1) Ubuntu 20.04.2 LTS / Release: 20.04 2) gnome-shell 3.36.4-1ubuntu1~20.04.2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 3 16:56:01 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-01-31 (31 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917674/+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 1749961] Re: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller
Btw - I just checked 20.10 even using kernel 5.11.8 (latest via "mainline --install 5.11.8" and that current kernel shows the same problem and error message "ERROR Transfer event TRB DMA ptr not part of current TD ep_index 1" Test hardware: Lenovo Thunderbolt Dock Gen 2" shows these same problems with a high speed USB (Samsung SSD T7) disk on Ubuntu 20.10. No need to involve the gige port to see the problem. This is probably still a bug in the kernel but I'm not sure how you want to report it upstream so it is linked here... -- 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/1749961 Title: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: Won't Fix Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux package in Debian: Confirmed Bug description: It was observed that while trying to use a 4K USB webcam connected to USB port provided by ASMedia ASM1142 USB 3.1 Controller, the webcam does not work and kernel log shows the following messages: [431.928016] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928021] xhci_hcd :12:00.0: Looking for event-dma 003f3330e020 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928024] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928026] xhci_hcd :12:00.0: Looking for event-dma 003f3330e030 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928027] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928029] xhci_hcd :12:00.0: Looking for event-dma 003f3330e050 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928386] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 A similar issue was already reported on Launchpad: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667750 The fix to this issue seems to be the following patch: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9da5a109 Tests in our scenario with this patch proved still broken. Our next approach is to modify the patch a bit and re-test. This LP will be used to document our progress in the investigation. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1749961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1919408] Re: General protection fault, kernel panics on ASUS M5A99FX PRO R2.0
I already started it to run this morning, I am going to check later, and let you know. On Sun, Mar 21, 2021 at 10:25 PM Daniel van Vugt <1919...@bugs.launchpad.net> wrote: > A full memory test takes hours or even days, but running it overnight > should be enough time usually. Please try the tools mentioned in comment > #7. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1919408 > > Title: > General protection fault, kernel panics on ASUS M5A99FX PRO R2.0 > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > After copied (dd copy) old disk /home to bigger one then reboot xorg > start to freeze it seems kernel crash rather than only Xorg, because all > input devices (keyboard, mouse) turned off completely. only option is hard > reboot. > I upgrade distro from 20.04 to 20.10, the situation remain the same > after every login to desktop the system freeze completely and need it to do > hard reboot. > > ProblemType: Bug > DistroRelease: Ubuntu 20.10 > Package: xorg 1:7.7+19ubuntu15 > ProcVersionSignature: Ubuntu 5.8.0-45.51-lowlatency 5.8.18 > Uname: Linux 5.8.0-45-lowlatency x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > .tmp.unity_support_test.0: > > ApportVersion: 2.20.11-0ubuntu50.5 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompizPlugins: > [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] > CompositorRunning: None > CurrentDesktop: MATE > Date: Wed Mar 17 01:11:19 2021 > DistUpgraded: 2021-03-15 02:52:49,427 INFO cache.commit() > DistroCodename: groovy > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes > GconfCompiz: >/apps/compiz-1/general: > /apps/compiz-1/general/screen0: > /apps/compiz-1/general/screen0/options: >active_plugins = > [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] > GpuHangFrequency: Continuously > GpuHangReproducibility: Occurs more often under certain circumstances > GpuHangStarted: Within the last week or two > GraphicsCard: >Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX > 470/480/570/570X/580/580X/590] [1002:67df] (rev ef) (prog-if 00 [VGA > controller]) > Subsystem: XFX Pine Group Inc. Radeon RX 570 [1682:c570] > InstallationDate: Installed on 2018-05-05 (1046 days ago) > InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 > (20180426) > MachineType: To be filled by O.E.M. To be filled by O.E.M. > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-45-lowlatency > root=UUID=17faa721-1006-4426-b460-57b94bfebefa ro threadirqs > crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M > crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M > crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M > crashkernel=512M-:192M > SourcePackage: xorg > Symptom: display > Title: Xorg freeze > UpgradeStatus: Upgraded to groovy on 2021-03-15 (1 days ago) > dmi.bios.date: 04/10/2013 > dmi.bios.release: 4.6 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 1708 > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: M5A99FX PRO R2.0 > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: Rev 1.xx > dmi.chassis.asset.tag: To Be Filled By O.E.M. > dmi.chassis.type: 3 > dmi.chassis.vendor: To Be Filled By O.E.M. > dmi.chassis.version: To Be Filled By O.E.M. > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr1708:bd04/10/2013:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99FXPROR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: > dmi.product.family: To be filled by O.E.M. > dmi.product.name: To be filled by O.E.M. > dmi.product.sku: SKU > dmi.product.version: To be filled by O.E.M. > dmi.sys.vendor: To be filled by O.E.M. > version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu1 > version.libdrm2: libdrm2 2.4.102-1ubuntu1 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 > version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1 > version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20200714-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: >
[Kernel-packages] [Bug 1919408] Re: General protection fault, kernel panics on ASUS M5A99FX PRO R2.0
A full memory test takes hours or even days, but running it overnight should be enough time usually. Please try the tools mentioned in comment #7. -- 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/1919408 Title: General protection fault, kernel panics on ASUS M5A99FX PRO R2.0 Status in linux package in Ubuntu: Incomplete Bug description: After copied (dd copy) old disk /home to bigger one then reboot xorg start to freeze it seems kernel crash rather than only Xorg, because all input devices (keyboard, mouse) turned off completely. only option is hard reboot. I upgrade distro from 20.04 to 20.10, the situation remain the same after every login to desktop the system freeze completely and need it to do hard reboot. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-45.51-lowlatency 5.8.18 Uname: Linux 5.8.0-45-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: None CurrentDesktop: MATE Date: Wed Mar 17 01:11:19 2021 DistUpgraded: 2021-03-15 02:52:49,427 INFO cache.commit() DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GpuHangFrequency: Continuously GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev ef) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Radeon RX 570 [1682:c570] InstallationDate: Installed on 2018-05-05 (1046 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-45-lowlatency root=UUID=17faa721-1006-4426-b460-57b94bfebefa ro threadirqs crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=512M-:192M SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to groovy on 2021-03-15 (1 days ago) dmi.bios.date: 04/10/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1708 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A99FX PRO R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1708:bd04/10/2013:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99FXPROR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919408/+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 1916971] Re: After fresh Ubuntu 20.04 install, downgrading Nvidia driver doesn't update nvidia modules in kernel
I don't understand. I currently have nvidia-driver-460 and linux kernel versions 5.8.0-43 to 45 installed (45 is being used). But I have no linux-modules-nvidia-460 packages installed. E.g. I don't have linux- modules-nvidia-460-5.8.0-45-generic and neither for 44 and 43. Is this ok or should I install linux-modules-nvidia-460-5.8.0-XY-generic. If the linux-modules-nvidia-460-5.8.0-XY-generic packages are not necessary for my system then why were they pre-installed in the first place, especially since they caused problems for me when I wanted to downgrade nvidia-driver-450? Please if you can answer my questions here and if you don't regard these as issues then close this bug report. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1916971 Title: After fresh Ubuntu 20.04 install, downgrading Nvidia driver doesn't update nvidia modules in kernel Status in nvidia-graphics-drivers-460 package in Ubuntu: New Status in ubiquity package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: New Bug description: SYSTEM: Laptop: ASUS ROG GL552VW OS: Ubuntu 20.04.2 LTS GRAPHICS: Nvidia Geforce GTX 960m AND Intel HD Graphics Linux kernel version: 5.8.0-44-generic SUMMARY: From a fresh working install of Ubuntu 20.04, I downgraded from nvidia-driver-460 by installing nvidia-driver-440 (which actually is a transitional package to nvidia-driver-450 but I didn't know this). After reboot I couldn't reach login-screen and instead got a black screen. Problem was that sudo apt-get install nvidia-driver-440 did not insert nvidia modules v450 in kernel since never versions v460 were found. This was solved by uninstalling linux-modules-nvidia-460 packages and instead installing linux-modules-nvidia-450 packages (see WORKAROUND below for instructions). STEPS TO REPRODUCE: Install Ubuntu 20.04. During installation, allow for the installation of proprietary drivers. Once Ubuntu 20.04 has started, open a terminal and run the following: sudo add-apt-repository ppa:graphics-drivers/ppa sudo apt-get update sudo apt-get install nvidia-driver-440 sudo shutdown reboot now PROBLEM: After reboot, you can't reach login screen. Instead you get stuck during bootup. WORKAROUND: WARNING: BETTER WORKAROUND PROBABLY EXISTS! DON'T JUST COPY-PASTE INSTRUCTIONS. PAY ATTENTION TO WHAT NVIDIA DRVER AND LINUX KERNEL VERSIONS ARE RELEVANT FOR YOU! Run dpkg --list | grep linux-image to see what linux kenrel versions you have installed. Remove the linux-modules-nvidia-460 packages and install the corresponding linux-modules-nvidia-450 packages. In my case I had Linux kernel versions 5.8.0-44-generic and 5.8.0-43-generic installed so I did as follows from recovery mode with network (instead of entering recovery mode, you should be able to press CTRL+ALT+F1 from the blank screen after bootup, login with username and password and then running these commands): sudo apt-get autoremove --purge linux-modules-nvidia-460-5.8.0-44-generic linux-modules-nvidia-460-5.8.0-43-generic sudo apt-get install linux-modules-nvidia-450-5.8.0-44-generic linux-modules-nvidia-450-5.8.0-43-generic sudo shutdown reboot now QUESTION: Why was the linux-modules-nvidia-460 packages installed by the Ubuntu installer to begin with? I ask since I later removed the linux- modules-nvidia-450 packages (OBSERVE: 450, not 460) and used the Additional Drivers GUI to update back to nvidia-driver-460. Now linux- modules-nvidia-460 packages are NOT installed but the following still outputs 460: modinfo nvidia | grep -i version LOG: This is a relevant part of /var/log/apt/term.log for when I installed nvidia-driver-440 nvidia.ko: Running module version sanity check. Error! Module version 450.102.04 for nvidia.ko is not newer than what is already found in kernel 5.8.0-44-generic (460.39). You may override by specifying --force. nvidia-modeset.ko: Running module version sanity check. Error! Module version 450.102.04 for nvidia-modeset.ko is not newer than what is already found in kernel 5.8.0-44-generic (460.39). You may override by specifying --force. nvidia-drm.ko: Running module version sanity check. Error! Module version 450.102.04 for nvidia-drm.ko is not newer than what is already found in kernel 5.8.0-44-generic (460.39). You may override by specifying --force. nvidia-uvm.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.8.0-44-generic/updates/dkms/ This is a relevant part of /var/log/apt/term.log for when I installed packages linux-modules-nvidia-450-5.8.0-44-generic and linux-modules- nvidia-450-5.8.0-43-generic Building module: cleaning build
[Kernel-packages] [Bug 1916971] Re: After fresh Ubuntu 20.04 install, downgrading Nvidia driver doesn't update nvidia modules in kernel
Sorry for my late reply. What do you mean by "... in the live session"? Instead I executed that command from my Ubuntu installation (where I observed the bug) and the output is here further below. @Dimitri are you saying that securedboot devices should avoid using the device drivers PPA? Also I'm currently on nvidia-driver-460 but I have no linux-modules-nvidia-460 packages installed. My system seems to work correctly. Is it OK that I don't have the linux-modules-nvidia-460 packages installed? Output of "sudo ubuntu-drivers list": nvidia-driver-418-server, (kernel modules provided by linux-modules-nvidia-418-server-generic-hwe-20.04) nvidia-driver-450-server, (kernel modules provided by linux-modules-nvidia-450-server-generic-hwe-20.04) nvidia-driver-460, (kernel modules provided by linux-modules-nvidia-460-generic-hwe-20.04) nvidia-driver-450, (kernel modules provided by linux-modules-nvidia-450-generic-hwe-20.04) nvidia-driver-390, (kernel modules provided by linux-modules-nvidia-390-generic-hwe-20.04) nvidia-driver-460-server, (kernel modules provided by linux-modules-nvidia-460-server-generic-hwe-20.04) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1916971 Title: After fresh Ubuntu 20.04 install, downgrading Nvidia driver doesn't update nvidia modules in kernel Status in nvidia-graphics-drivers-460 package in Ubuntu: New Status in ubiquity package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: New Bug description: SYSTEM: Laptop: ASUS ROG GL552VW OS: Ubuntu 20.04.2 LTS GRAPHICS: Nvidia Geforce GTX 960m AND Intel HD Graphics Linux kernel version: 5.8.0-44-generic SUMMARY: From a fresh working install of Ubuntu 20.04, I downgraded from nvidia-driver-460 by installing nvidia-driver-440 (which actually is a transitional package to nvidia-driver-450 but I didn't know this). After reboot I couldn't reach login-screen and instead got a black screen. Problem was that sudo apt-get install nvidia-driver-440 did not insert nvidia modules v450 in kernel since never versions v460 were found. This was solved by uninstalling linux-modules-nvidia-460 packages and instead installing linux-modules-nvidia-450 packages (see WORKAROUND below for instructions). STEPS TO REPRODUCE: Install Ubuntu 20.04. During installation, allow for the installation of proprietary drivers. Once Ubuntu 20.04 has started, open a terminal and run the following: sudo add-apt-repository ppa:graphics-drivers/ppa sudo apt-get update sudo apt-get install nvidia-driver-440 sudo shutdown reboot now PROBLEM: After reboot, you can't reach login screen. Instead you get stuck during bootup. WORKAROUND: WARNING: BETTER WORKAROUND PROBABLY EXISTS! DON'T JUST COPY-PASTE INSTRUCTIONS. PAY ATTENTION TO WHAT NVIDIA DRVER AND LINUX KERNEL VERSIONS ARE RELEVANT FOR YOU! Run dpkg --list | grep linux-image to see what linux kenrel versions you have installed. Remove the linux-modules-nvidia-460 packages and install the corresponding linux-modules-nvidia-450 packages. In my case I had Linux kernel versions 5.8.0-44-generic and 5.8.0-43-generic installed so I did as follows from recovery mode with network (instead of entering recovery mode, you should be able to press CTRL+ALT+F1 from the blank screen after bootup, login with username and password and then running these commands): sudo apt-get autoremove --purge linux-modules-nvidia-460-5.8.0-44-generic linux-modules-nvidia-460-5.8.0-43-generic sudo apt-get install linux-modules-nvidia-450-5.8.0-44-generic linux-modules-nvidia-450-5.8.0-43-generic sudo shutdown reboot now QUESTION: Why was the linux-modules-nvidia-460 packages installed by the Ubuntu installer to begin with? I ask since I later removed the linux- modules-nvidia-450 packages (OBSERVE: 450, not 460) and used the Additional Drivers GUI to update back to nvidia-driver-460. Now linux- modules-nvidia-460 packages are NOT installed but the following still outputs 460: modinfo nvidia | grep -i version LOG: This is a relevant part of /var/log/apt/term.log for when I installed nvidia-driver-440 nvidia.ko: Running module version sanity check. Error! Module version 450.102.04 for nvidia.ko is not newer than what is already found in kernel 5.8.0-44-generic (460.39). You may override by specifying --force. nvidia-modeset.ko: Running module version sanity check. Error! Module version 450.102.04 for nvidia-modeset.ko is not newer than what is already found in kernel 5.8.0-44-generic (460.39). You may override by specifying --force. nvidia-drm.ko: Running module version sanity check. Error! Module version 450.102.04 for nvidia-drm.ko is not newer than what is already found in kernel 5.8.0-44-generic (460.39). You may override by
[Kernel-packages] [Bug 1920699] Re: package nvidia-dkms-460-server (not installed) failed to install/upgrade: installed nvidia-dkms-460-server package post-installation script subprocess returned erro
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1920699 Title: package nvidia-dkms-460-server (not installed) failed to install/upgrade: installed nvidia-dkms-460-server package post- installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-460-server package in Ubuntu: New Bug description: I'm currently trying to fix my NVIDIA drivers and can't seem to do it as it crashes when I tried to run it. I already tried reinstalling the drivers, but I can't fix it ;( ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-460-server (not installed) ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Mar 21 22:23:02 2021 ErrorMessage: installed nvidia-dkms-460-server package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2021-03-20 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: nvidia-graphics-drivers-460-server Title: package nvidia-dkms-460-server (not installed) failed to install/upgrade: installed nvidia-dkms-460-server package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460-server/+bug/1920699/+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 1920699] [NEW] package nvidia-dkms-460-server (not installed) failed to install/upgrade: installed nvidia-dkms-460-server package post-installation script subprocess returned er
Public bug reported: I'm currently trying to fix my NVIDIA drivers and can't seem to do it as it crashes when I tried to run it. I already tried reinstalling the drivers, but I can't fix it ;( ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-460-server (not installed) ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Mar 21 22:23:02 2021 ErrorMessage: installed nvidia-dkms-460-server package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2021-03-20 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: nvidia-graphics-drivers-460-server Title: package nvidia-dkms-460-server (not installed) failed to install/upgrade: installed nvidia-dkms-460-server package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-460-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1920699 Title: package nvidia-dkms-460-server (not installed) failed to install/upgrade: installed nvidia-dkms-460-server package post- installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-460-server package in Ubuntu: New Bug description: I'm currently trying to fix my NVIDIA drivers and can't seem to do it as it crashes when I tried to run it. I already tried reinstalling the drivers, but I can't fix it ;( ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-460-server (not installed) ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Mar 21 22:23:02 2021 ErrorMessage: installed nvidia-dkms-460-server package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2021-03-20 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: nvidia-graphics-drivers-460-server Title: package nvidia-dkms-460-server (not installed) failed to install/upgrade: installed nvidia-dkms-460-server package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460-server/+bug/1920699/+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 1850702] Re: [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone sound is faint and distorted (but works fine in Windows)
The command sudo hda-verb /dev/snd/hwC0D0 0x1a 0x707 0x05 works for me, but the patch proposed (I added the files), do not seem to be working after reboots. Currently I have to run the command above everytime I reboot. -- 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/1850702 Title: [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone sound is faint and distorted (but works fine in Windows) Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I can't get sound of my laptop (Samsung Notebook 7 Force) through the headphone jack. The speakers work fine. When I plug a headphone, I can hear the sound being played very faintly. If I bump the volume to the maximum, that is. The sound is very distorted, like a buzz effect being applied over it. I noticed that if I delete /.config/pulse the distortion goes away, but the sound remains very low. After some time, the buzzing effect comes back. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Wed Oct 30 16:03:41 2019 InstallationDate: Installed on 2019-10-29 (1 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filipe 1294 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-29 (1 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.1 Tags: eoan Uname: Linux 5.3.0-19-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: 06/10/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02REZ.040.190610.FL dmi.board.asset.tag: No Asset Tag dmi.board.name: NP760XBE-XW1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.family: Notebook 7 Series dmi.product.name: 760XBE dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ dmi.product.version: P02REZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filipe 1294 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-29 (1 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.1 Tags: eoan Uname: Linux 5.3.0-19-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: 06/10/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02REZ.040.190610.FL
[Kernel-packages] [Bug 1920660] Re: Missing Commit for 5.4-Kernel breaks xen Dom0
** Also affects: linux-hwe-5.4 (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/1920660 Title: Missing Commit for 5.4-Kernel breaks xen Dom0 Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.4 package in Ubuntu: New Bug description: You commited "xen: Fix event channel callback via INTX/GSI" for kernel 5.4.0-67 for HWE 18.04 and 20.04. This commit is incomplete and breaks Ubuntu as Dom0 for xen. You need also Commit "xen: Fix XenStore initialisation for XS_LOCAL" See https://lkml.org/lkml/2021/1/28/1235 See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 Upstream: Commit: 3499ba8198cad47b731792e5e56b9ec2a78a83a2 Fixing Commit: 5f46400f7a6a4fad635d5a79e2aa5a04a30ffea1 5.10: Commit: fa5f2e04daa44961a1026e93f0cc88caa3c27d3d (5.10.11) Fixing Commit: 5f3d54c00f1f2682cee9c590c22655b0330ffd18 (5.10.13) 5.4: Commit: a09d4e7acdbf276b2096661ee82454ae3dd24d2b (5.4.93) Fixing commit 2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f (5.4.95) Without this patch you cannot start guests (DomU) on this machine! Error message while creating DomU: libxl: error: libxl_device.c:1105:device_backend_callback: Domain X:unable to add device with path / libxl: error: libxl_create.c:1452:domcreate_launch_dm: Domain X:unable to add disk devices See: - https://lkml.org/lkml/2021/1/28/1231 and https://lkml.org/lkml/2021/1/29/14 - https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.107=2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.95 - http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-hwe-5.4/linux-hwe-5.4_5.4.0-67.75~18.04.1/changelog - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920660/+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 1920674] 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/1920674 Title: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation Status in linux package in Ubuntu: Confirmed Bug description: Dear developers, please let me thank you for all your hard work first of all, I'm a big fan of yours! On my desktop PC with AMD A8-7680 APU, I'm facing 2 problems which seem to be connected to the amdgpu kernel module: 1. Amdgpu kernel module loads correctly during boot, but VESA Xorg module is loaded instead of AMDGPU Xorg module during X startup. This results in non-accelerated X and high CPU load. - This situation is always reproducible. - I'm experiencing it with all kernel versions in between 5.4.0-47-generic and 5.4.0-67-generic inclusive. - The situation escalates more with newer kernel version. For 5.8.0-45-generic and 5.11.8-051108-generic, X even does not start and I just get black screen. - I have found a workaround after many days of googling and testing. AMDGPU Xorg module is loaded correctly if and only if I disable AMD ACP by means of the following kernel boot parameter: amdgpu.ip_block_mask=0xfdff - Acceleration is ok with kernels where AMD ACP is disabled by default (linux-image-linuxlite-5.6.0 for example) 2. The 2nd problem I'm facing is with non functioning hibernation after I "fixed" the X acceleration. Hibernation image does not seem to get created, screen goes black, PC freezes but never turns off whenever AMDGPU Xorg module is loaded. Hibernation and subsequent resume is all ok if I disable AMDGPU by means of "nomodeset" and go just with VESA module. - always reproducible but tested only with 5.4.0-67-generic Thank you and best regards, Radek ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-67-generic 5.4.0-67.75 ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94 Uname: Linux 5.4.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: radek 1513 F pulseaudio /dev/snd/controlC0: radek 1513 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Mar 21 15:22:29 2021 HibernationDevice: RESUME=/dev/disk/by-label/SSD_LinuxSwap IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic root=UUID=1cc747ae-f2db-4733-aa04-be8d4bde050a ro ipv6.disable=1 net.ifnames=0 nmi_watchdog=0 resume=LABEL=SSD_LinuxSwap amdgpu.ip_block_mask=0xfdff no_console_suspend RelatedPackageVersions: linux-restricted-modules-5.4.0-67-generic N/A linux-backports-modules-5.4.0-67-generic N/A linux-firmware1.187.10 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.20 dmi.board.name: FM2A68M-HD+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.20:bd02/13/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A68M-HD+:rvr:cvnTobefilledbyO.E.M.:ct3:cvrTobefilledbyO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920674/+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 1920674] Re: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1920674 Title: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation Status in linux package in Ubuntu: New Bug description: Dear developers, please let me thank you for all your hard work first of all, I'm a big fan of yours! On my desktop PC with AMD A8-7680 APU, I'm facing 2 problems which seem to be connected to the amdgpu kernel module: 1. Amdgpu kernel module loads correctly during boot, but VESA Xorg module is loaded instead of AMDGPU Xorg module during X startup. This results in non-accelerated X and high CPU load. - This situation is always reproducible. - I'm experiencing it with all kernel versions in between 5.4.0-47-generic and 5.4.0-67-generic inclusive. - The situation escalates more with newer kernel version. For 5.8.0-45-generic and 5.11.8-051108-generic, X even does not start and I just get black screen. - I have found a workaround after many days of googling and testing. AMDGPU Xorg module is loaded correctly if and only if I disable AMD ACP by means of the following kernel boot parameter: amdgpu.ip_block_mask=0xfdff - Acceleration is ok with kernels where AMD ACP is disabled by default (linux-image-linuxlite-5.6.0 for example) 2. The 2nd problem I'm facing is with non functioning hibernation after I "fixed" the X acceleration. Hibernation image does not seem to get created, screen goes black, PC freezes but never turns off whenever AMDGPU Xorg module is loaded. Hibernation and subsequent resume is all ok if I disable AMDGPU by means of "nomodeset" and go just with VESA module. - always reproducible but tested only with 5.4.0-67-generic Thank you and best regards, Radek ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-67-generic 5.4.0-67.75 ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94 Uname: Linux 5.4.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: radek 1513 F pulseaudio /dev/snd/controlC0: radek 1513 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Mar 21 15:22:29 2021 HibernationDevice: RESUME=/dev/disk/by-label/SSD_LinuxSwap IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic root=UUID=1cc747ae-f2db-4733-aa04-be8d4bde050a ro ipv6.disable=1 net.ifnames=0 nmi_watchdog=0 resume=LABEL=SSD_LinuxSwap amdgpu.ip_block_mask=0xfdff no_console_suspend RelatedPackageVersions: linux-restricted-modules-5.4.0-67-generic N/A linux-backports-modules-5.4.0-67-generic N/A linux-firmware1.187.10 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.20 dmi.board.name: FM2A68M-HD+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.20:bd02/13/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A68M-HD+:rvr:cvnTobefilledbyO.E.M.:ct3:cvrTobefilledbyO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920674/+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 1920674] [NEW] AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation
You have been subscribed to a public bug: Dear developers, please let me thank you for all your hard work first of all, I'm a big fan of yours! On my desktop PC with AMD A8-7680 APU, I'm facing 2 problems which seem to be connected to the amdgpu kernel module: 1. Amdgpu kernel module loads correctly during boot, but VESA Xorg module is loaded instead of AMDGPU Xorg module during X startup. This results in non-accelerated X and high CPU load. - This situation is always reproducible. - I'm experiencing it with all kernel versions in between 5.4.0-47-generic and 5.4.0-67-generic inclusive. - The situation escalates more with newer kernel version. For 5.8.0-45-generic and 5.11.8-051108-generic, X even does not start and I just get black screen. - I have found a workaround after many days of googling and testing. AMDGPU Xorg module is loaded correctly if and only if I disable AMD ACP by means of the following kernel boot parameter: amdgpu.ip_block_mask=0xfdff - Acceleration is ok with kernels where AMD ACP is disabled by default (linux-image-linuxlite-5.6.0 for example) 2. The 2nd problem I'm facing is with non functioning hibernation after I "fixed" the X acceleration. Hibernation image does not seem to get created, screen goes black, PC freezes but never turns off whenever AMDGPU Xorg module is loaded. Hibernation and subsequent resume is all ok if I disable AMDGPU by means of "nomodeset" and go just with VESA module. - always reproducible but tested only with 5.4.0-67-generic Thank you and best regards, Radek ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-67-generic 5.4.0-67.75 ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94 Uname: Linux 5.4.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: radek 1513 F pulseaudio /dev/snd/controlC0: radek 1513 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Mar 21 15:22:29 2021 HibernationDevice: RESUME=/dev/disk/by-label/SSD_LinuxSwap IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic root=UUID=1cc747ae-f2db-4733-aa04-be8d4bde050a ro ipv6.disable=1 net.ifnames=0 nmi_watchdog=0 resume=LABEL=SSD_LinuxSwap amdgpu.ip_block_mask=0xfdff no_console_suspend RelatedPackageVersions: linux-restricted-modules-5.4.0-67-generic N/A linux-backports-modules-5.4.0-67-generic N/A linux-firmware1.187.10 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.20 dmi.board.name: FM2A68M-HD+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.20:bd02/13/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A68M-HD+:rvr:cvnTobefilledbyO.E.M.:ct3:cvrTobefilledbyO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation https://bugs.launchpad.net/bugs/1920674 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1920179] Re: System freezes when using Wacom tablet after upgrading to linux-image-5.8.0-45-generic
Luis Llana Díaz, can you confirm that the upgrade to kernel version 5.8.0-45 is the cause and that reverting back to 5.8.0-44 is a work- around? -- 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/1920179 Title: System freezes when using Wacom tablet after upgrading to linux- image-5.8.0-45-generic Status in linux package in Ubuntu: Confirmed Bug description: I have an Lenovo Thinkpad Yoga 260 with a built-in Wacom digitizer. After the latest Kernel update my system freezes as soon as I put the pen on the screen. Nothing else but a forced power-off is possible. Reverting back to 5.8.0-44 is a work-around, so this seems to be a regression. The relevant entry from /var/log/apt/history.log: Start-Date: 2021-03-17 11:37:43 Commandline: apt dist-upgrade Install: linux-image-5.8.0-45-generic:amd64 (5.8.0-45.51, automatic), linux-headers-5.8.0-45:amd64 (5.8.0-45.51, automatic), linux-modules-extra-5.8.0-45-generic:amd64 (5.8.0-45.51, automatic), linux-headers-5.8.0-45-generic:amd64 (5.8.0-45.51, automatic), linux-modules-5.8.0-45-generic:amd64 (5.8.0-45.51, automatic), dctrl-tools:amd64 (2.24-3, automatic) Upgrade: update-manager-core:amd64 (1:20.10.4, 1:20.10.5), linux-headers-generic:amd64 (5.8.0.44.49, 5.8.0.45.50), linux-libc-dev:amd64 (5.8.0-44.50, 5.8.0-45.51), linux-image-generic:amd64 (5.8.0.44.49, 5.8.0.45.50), update-manager:amd64 (1:20.10.4, 1:20.10.5), dkms:amd64 (2.8.3-4, 2.8.3-4ubuntu0.1), python3-update-manager:amd64 (1:20.10.4, 1:20.10.5), libglib2.0-bin:amd64 (2.66.1-2ubuntu0.1, 2.66.1-2ubuntu0.2), libglib2.0-data:amd64 (2.66.1-2ubuntu0.1, 2.66.1-2ubuntu0.2), linux-generic:amd64 (5.8.0.44.49, 5.8.0.45.50), libglib2.0-0:amd64 (2.66.1-2ubuntu0.1, 2.66.1-2ubuntu0.2), libglib2.0-0:i386 (2.66.1-2ubuntu0.1, 2.66.1-2ubuntu0.2) End-Date: 2021-03-17 11:38:44 Apport is enabled but no crash report is generated. BTW, I found a similar bug report for Manjaro: https://forum.manjaro.org/t/system-freezes-when-using-wacom-tablet-on-5-10/50339 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.14 [origin: unknown] ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Fri Mar 19 12:41:12 2021 InstallationDate: Installed on 2020-04-14 (338 days ago) InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-11-12 (127 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920179/+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 1332824] Re: [Samsung XE700T1C-A01FR] Smartpad not properly recognised
Bug still exists in ubuntu 20.04 LTS. -- 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/1332824 Title: [Samsung XE700T1C-A01FR] Smartpad not properly recognised Status in linux package in Ubuntu: Confirmed Bug description: Expecting at least the smartpad to be properly recognised with the bare minimum multi-touch gesture: two-fingers right click, side scrolling, two-fingers scrolling, mouse speed. xinput -list gives: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Wacom ISDv4 EC Pen stylus id=9[slave pointer (2)] ⎜ ↳ Atmel Atmel maXTouch Digitizer id=10 [slave pointer (2)] ⎜ ↳ USB Keyboard+SmartPad id=13 [slave pointer (2)] ⎜ ↳ Wacom ISDv4 EC Pen eraser id=16 [slave pointer (2)] ⎜ ↳ Asus gaming Mouse (G112)id=19 [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)] ↳ WebCam SC-50AFL11C54N id=11 [slave keyboard (3)] ↳ USB Keyboard+SmartPad id=12 [slave keyboard (3)] ↳ WebCam SC-20HDM12347N id=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=15 [slave keyboard (3)] ↳ Chicony USB Keyboardid=17 [slave keyboard (3)] ↳ Chicony USB Keyboardid=18 [slave keyboard (3)] ↳ Acer Crystal Eye Webcam id=20 [slave keyboard (3)] Note that "USB Keyboard+SmartPad" is present twice (id 12 and 13) Also note that running xinput test 13 doesn't detect any multitouch on the smartpad. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Jun 21 15:52:14 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c0e1] InstallationDate: Installed on 2014-06-18 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: SAMSUNG ELECTRONICS CO., LTD. 700T1C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic.efi.signed root=UUID=1fdb1c66-705c-4c1a-8d6c-d363ad0e53b9 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P10AAT.050.140215.dg dmi.board.asset.tag: No Asset Tag dmi.board.name: XE700T1C-A01FR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 8 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP10AAT.050.140215.dg:bd02/15/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn700T1C:pvrP10AAT:rvnSAMSUNGELECTRONICSCO.,LTD.:rnXE700T1C-A01FR:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct8:cvrN/A: dmi.product.name: 700T1C dmi.product.version: P10AAT dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel:
[Kernel-packages] [Bug 1908139] Re: ThinkPad T14s external display not working on ThinkPad USB-C Dock Gen2
@Andre Plötze As described in the bug report I have observed the following that make me think that a hardware issue can be excluded: > All above modes of connection work as expected with the same laptop, dock, > and display on Windows 10 (installed as dual boot along side Ubuntu). > All above modes of connection also work as expected with an older laptop > (ThinkPad T470s - Ubuntu 20.04 - kernel 5.4.0), and the same dock and display. > This leads me to believe that this is not a hardware issue. My main operating system is Ubuntu and I only use Windows on rare occasion, so I do not have months of usage under Windows that I can report on. However, whenever I test with the T14s on Windows the monitor connection through the dock works immediately and reliably, while it never works on Linux with the T14s. So, even if there was an underlying hardware issue somewhere, it would still seem that there is a software issue as well which makes me not encounter any issues on Windows, while consistently observing an issue on Linux. You report that you are using Ubuntu 20.04 LTS, I am using Ubuntu 20.10. The corresponding difference in kernel may well be relevant here. Also, just to be sure, do you have the same laptop model (ThinkPad T14s Gen 1 - AMD Ryzen 7 PRO 4750U) or a different one? -- 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/1908139 Title: ThinkPad T14s external display not working on ThinkPad USB-C Dock Gen2 Status in linux package in Ubuntu: Confirmed Bug description: laptop: ThinkPad T14s Gen 1 - AMD Ryzen 7 PRO 4750U docking station: ThinkPad USB-C Dock 2. Gen. external display: NE MultiSync EA275UHD OS: Ubuntu 20.10 - kernel 5.8.0 Plugging the external display into one of the docking station's two DisplayPort connectors leads to the screen resolution changing on the laptop's builtin display and the external display waking up but showing no picture and displaying "no-signal" after a bit. Plugging the external display into the docking station's HDMI connector leads to no visible reaction on either the external nor the builtin display. Plugging the external display into the laptop's builtin HDMI connector works as expected. The external display is recognized and shows an image. I have recorded the output on `dmesg` during the steps mentioned above and inserted explanations using `echo MSG >/dev/kmsg`. The output follows at the end of the message. I believe `ubuntu-bug` should also attach the full log. All above modes of connection work as expected with the same laptop, dock, and display on Windows 10 (installed as dual boot along side Ubuntu). All above modes of connection also work as expected with an older laptop (ThinkPad T470s - Ubuntu 20.04 - kernel 5.4.0), and the same dock and display. This leads me to believe that this is not a hardware issue. The following bug seems related, but seems to have been observed on faulty hardware according to its author. Therefore, I decided to open a separate bug report. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899336 ``` [ 343.372511] plugging DisplayPort into dock port 1 [ 352.666113] [drm] DP Alt mode state on HPD: 1 [ 352.749192] [drm] DM_MST: starting TM on aconnector: 2105a317 [id: 75] [ 352.858482] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.888400] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.892555] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.896719] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.900876] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.905596] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.910323] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.914485] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 377.353566] plugged in - no signal [ 396.728970] unplugging [ 403.001418] [drm] DM_MST: stopping TM on aconnector: 2105a317 [id: 75] [ 415.576397] unplugged [ 431.500729] plugging DisplayPort into dock port 2 [ 437.607724] [drm] DP Alt mode state on HPD: 1 [ 437.681116] [drm] DM_MST: starting TM on aconnector: 2105a317 [id: 75] [ 437.790303] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.820138] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.824305] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.828462] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.832619] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.837029] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.841984] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.846144] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 458.999849] plugged in - no signal [ 465.702949] unplugging [ 476.127418] [drm] DM_MST: stopping TM on aconnector: 2105a317 [id: 75] [ 476.956491] [drm] Failed to add display
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
I have this issue on Hirsuite. Is this only fixed in 5.8 and 5.10 but not 5.11? $ uname -a Linux example 5.11.8-051108-generic #202103200636 SMP Sat Mar 20 11:17:32 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux I got the 5.11.8 kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11.8/ because 5.11.0 caused GPU hangs for me on Intel 4770K Haswell. -- 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/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in grub2 source package in Focal: Invalid Status in initramfs-tools source package in Focal: Invalid Status in linux source package in Focal: Fix Released Status in grub2 source package in Groovy: Invalid Status in initramfs-tools source package in Groovy: Invalid Status in linux source package in Groovy: Fix Released Status in grub2 source package in Hirsute: Invalid Status in initramfs-tools source package in Hirsute: Invalid Status in linux source package in Hirsute: Fix Released Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. [Impact] * Decoding failure messages in dmsg with a single lz4 initrd * Multiple lz4 compressed initrds cannot be decompressed by kernel, when loaded by grub * Multiple lz4 compressed initrds cannot be decompressed by kernel, when there is padding between them [Test Case] * Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4 * Create an lz4 compressed initrd with a single test-file in it with some content. I.e. echo "second-initrd" > test-file, and then pack that with cpio hewc owned by root & lz4 -l. * Create a combined padded initrd of stock initrd, pad4, and the test-marker initrd created above. * Boot above with "break=top" kernel command line. * With broken kernels, there should be dmesg error message that decoding failed, and one will observe that /test-file does not exist in the shell. * With fixed kernel, /test-file in the initrd shell should exist, and should have the expected content "second-initrd". * The alignment and padding in the above test case depends on the size of the first initrd => if a given padded initrd does not reproduce the problem, try varying the size of the first initrd or that of the padding between 0..4. [Where problems could occur] * This changes compatible lz4 decompressor in the kernel, which can also be used by other kernel modules such as cryptography, squashfs, zram, f2fs, comprssed kernel image, pstore. For example, previously rejected files with "bogus" length and extra padding may now be accepted, whereas they were previously getting rejected by the decompressor. * Ideally kernel should switch to the stable lz4 format which has better specification of end of stream. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+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 1912935] Re: battery drain while notebook off / shutdown
@asgard2 and @Kai-Heng Feng Thank you for working this out. I have the same type of notebook as asgard2 has and the same problem, using Manjaro though. The notebook is seemingly powered off and looses 10% battery charge over night. I tried 5.4, 5.10 and 5.11 kernels. Hopefully an ACPI-specific patch will arrive at lore.kernel.org soon. The patch for the preliminary fix seems to consist of one line of code only and is contained in the thread Kai-Heng cited in #22. May be it is time for a bit of private enterprise. -- 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/1912935 Title: battery drain while notebook off / shutdown Status in linux package in Ubuntu: Confirmed Bug description: Hello, my battery drains around 15 to 20 percent a day when shutdown on linux ubuntu. It is an HP notebook HP 15s-eq0355ng , Ryzen 5 3500U , Vega8 . Tested: - with ubuntu 20.04 - Kernel 5.4, 5.8 (hwe) and the current mainline kernel 5.11 (rc4) - no usb devices are plugged in - no wake ob lan available - no USB power when off (checked with optical mouse) - no visible LEDs are on when shutdown I reinstalled window 10, when shutdown from windows there is no (visible) battery drain (or significantly lower). Linux is unusable on this device, if the battery drains in a short time to 0% percent. This cause battery damage ... --- Tested TLP with default settings and activated DEVICES_TO_DISABLE_ON_SHUTDOWN (bluetooth wifi wwan), same power consumption after shutdown. Same power consumption on 20.10 (Groovy Gorilla). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test953 F pulseaudio /dev/snd/controlC0: test953 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-24 (0 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP Laptop 15s-eq0xxx Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=17ad50f6-ec98-46b2-8c2e-c169f9baace8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.8 Tags: focal Uname: Linux 5.4.0-64-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: 11/18/2020 dmi.bios.vendor: AMI dmi.bios.version: F.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FD dmi.board.vendor: HP dmi.board.version: 99.40 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.30:bd11/18/2020:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.40:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-eq0xxx dmi.product.sku: 20T63EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912935/+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 1850654] Re: update-initramfs complains of missing amdgpu firmware files
I searched https://git.kernel.org/pub/scm/linux/kernel/git/firmware /linux-firmware.git/tree/amdgpu for navi10_mes.bin and there is no such file. There is no *_mes.bin too. Only *_mec.bin files. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1850654 Title: update-initramfs complains of missing amdgpu firmware files Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-firmware source package in Bionic: Fix Released Status in linux source package in Eoan: Confirmed Status in linux-firmware source package in Eoan: Fix Released Bug description: SRU Justification Impact: With 5.3 update-initramfs reports several missing amdgpu firmware files: update-initramfs: Generating /boot/initrd.img-5.3.0-19-generic W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_kicker_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu Of these, only raven_kicker_rlc.bin has been added to upstream linux- firmware. Fix: Add raven_kicker_rlc.bin to linux firmware, and remove the other files from modinfo for amdgpu. Test Case: Once fixed, the warnings from update-initramfs should be gone. Regression Potential: Adding a missing firmware is unlikely to break any working hardware. Removing the other missing files from modinfo will not cause regressions either, however if the firmware is added later update-initramfs will not add the files to the initramfs until the firmware is added back to modinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850654/+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 1920660] Re: Missing Commit for 5.4-Kernel breaks xen Dom0
The commit is missing so you do not need not our server data. => Confirmed ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1920660 Title: Missing Commit for 5.4-Kernel breaks xen Dom0 Status in linux package in Ubuntu: Confirmed Bug description: You commited "xen: Fix event channel callback via INTX/GSI" for kernel 5.4.0-67 for HWE 18.04 and 20.04. This commit is incomplete and breaks Ubuntu as Dom0 for xen. You need also Commit "xen: Fix XenStore initialisation for XS_LOCAL" See https://lkml.org/lkml/2021/1/28/1235 See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 Upstream: Commit: 3499ba8198cad47b731792e5e56b9ec2a78a83a2 Fixing Commit: 5f46400f7a6a4fad635d5a79e2aa5a04a30ffea1 5.10: Commit: fa5f2e04daa44961a1026e93f0cc88caa3c27d3d (5.10.11) Fixing Commit: 5f3d54c00f1f2682cee9c590c22655b0330ffd18 (5.10.13) 5.4: Commit: a09d4e7acdbf276b2096661ee82454ae3dd24d2b (5.4.93) Fixing commit 2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f (5.4.95) Without this patch you cannot start guests (DomU) on this machine! Error message while creating DomU: libxl: error: libxl_device.c:1105:device_backend_callback: Domain X:unable to add device with path / libxl: error: libxl_create.c:1452:domcreate_launch_dm: Domain X:unable to add disk devices See: - https://lkml.org/lkml/2021/1/28/1231 and https://lkml.org/lkml/2021/1/29/14 - https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.107=2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.95 - http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-hwe-5.4/linux-hwe-5.4_5.4.0-67.75~18.04.1/changelog - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920660/+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 1920660] 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 1920660 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/1920660 Title: Missing Commit for 5.4-Kernel breaks xen Dom0 Status in linux package in Ubuntu: Incomplete Bug description: You commited "xen: Fix event channel callback via INTX/GSI" for kernel 5.4.0-67 for HWE 18.04 and 20.04. This commit is incomplete and breaks Ubuntu as Dom0 for xen. You need also Commit "xen: Fix XenStore initialisation for XS_LOCAL" See https://lkml.org/lkml/2021/1/28/1235 See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 Upstream: Commit: 3499ba8198cad47b731792e5e56b9ec2a78a83a2 Fixing Commit: 5f46400f7a6a4fad635d5a79e2aa5a04a30ffea1 5.10: Commit: fa5f2e04daa44961a1026e93f0cc88caa3c27d3d (5.10.11) Fixing Commit: 5f3d54c00f1f2682cee9c590c22655b0330ffd18 (5.10.13) 5.4: Commit: a09d4e7acdbf276b2096661ee82454ae3dd24d2b (5.4.93) Fixing commit 2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f (5.4.95) Without this patch you cannot start guests (DomU) on this machine! Error message while creating DomU: libxl: error: libxl_device.c:1105:device_backend_callback: Domain X:unable to add device with path / libxl: error: libxl_create.c:1452:domcreate_launch_dm: Domain X:unable to add disk devices See: - https://lkml.org/lkml/2021/1/28/1231 and https://lkml.org/lkml/2021/1/29/14 - https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.107=2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.95 - http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-hwe-5.4/linux-hwe-5.4_5.4.0-67.75~18.04.1/changelog - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920660/+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 1920660] [NEW] Missing Commit for 5.4-Kernel breaks xen Dom0
Public bug reported: You commited "xen: Fix event channel callback via INTX/GSI" for kernel 5.4.0-67 for HWE 18.04 and 20.04. This commit is incomplete and breaks Ubuntu as Dom0 for xen. You need also Commit "xen: Fix XenStore initialisation for XS_LOCAL" See https://lkml.org/lkml/2021/1/28/1235 See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 Upstream: Commit: 3499ba8198cad47b731792e5e56b9ec2a78a83a2 Fixing Commit: 5f46400f7a6a4fad635d5a79e2aa5a04a30ffea1 5.10: Commit: fa5f2e04daa44961a1026e93f0cc88caa3c27d3d (5.10.11) Fixing Commit: 5f3d54c00f1f2682cee9c590c22655b0330ffd18 (5.10.13) 5.4: Commit: a09d4e7acdbf276b2096661ee82454ae3dd24d2b (5.4.93) Fixing commit 2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f (5.4.95) Without this patch you cannot start guests (DomU) on this machine! Error message while creating DomU: libxl: error: libxl_device.c:1105:device_backend_callback: Domain X:unable to add device with path / libxl: error: libxl_create.c:1452:domcreate_launch_dm: Domain X:unable to add disk devices See: - https://lkml.org/lkml/2021/1/28/1231 and https://lkml.org/lkml/2021/1/29/14 - https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.107=2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.95 - http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-hwe-5.4/linux-hwe-5.4_5.4.0-67.75~18.04.1/changelog - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Missing Commit for 5.4-Kernel breaks dom0 + Missing Commit for 5.4-Kernel breaks xen Dom0 ** Description changed: - Your commited "xen: Fix event channel callback via INTX/GSI" for kernel 5.4.0-67 for HWE 18.04 and 20.04. + You commited "xen: Fix event channel callback via INTX/GSI" for kernel 5.4.0-67 for HWE 18.04 and 20.04. This commit is incomplete and breaks Ubuntu as Dom0 for xen. You need also Commit "xen: Fix XenStore initialisation for XS_LOCAL" + See https://lkml.org/lkml/2021/1/28/1235 See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 Upstream: Commit: 3499ba8198cad47b731792e5e56b9ec2a78a83a2 - Fixing Commit: 5f46400f7a6a4fad635d5a79e2aa5a04a30ffea1 + Fixing Commit: 5f46400f7a6a4fad635d5a79e2aa5a04a30ffea1 5.10: Commit: fa5f2e04daa44961a1026e93f0cc88caa3c27d3d (5.10.11) Fixing Commit: 5f3d54c00f1f2682cee9c590c22655b0330ffd18 (5.10.13) 5.4: Commit: a09d4e7acdbf276b2096661ee82454ae3dd24d2b (5.4.93) Fixing commit 2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f (5.4.95) - Without this patch you cannot start guests (DomU) on this machine! Error message while creating DomU: libxl: error: libxl_device.c:1105:device_backend_callback: Domain X:unable to add device with path / libxl: error: libxl_create.c:1452:domcreate_launch_dm: Domain X:unable to add disk devices - See: - https://lkml.org/lkml/2021/1/28/1231 and https://lkml.org/lkml/2021/1/29/14 - https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.107=2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.95 - http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-hwe-5.4/linux-hwe-5.4_5.4.0-67.75~18.04.1/changelog - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 -- 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/1920660 Title: Missing Commit for 5.4-Kernel breaks xen Dom0 Status in linux package in Ubuntu: New Bug description: You commited "xen: Fix event channel callback via INTX/GSI" for kernel 5.4.0-67 for HWE 18.04 and 20.04. This commit is incomplete and breaks Ubuntu as Dom0 for xen. You need also Commit "xen: Fix XenStore initialisation for XS_LOCAL" See https://lkml.org/lkml/2021/1/28/1235 See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 Upstream: Commit: 3499ba8198cad47b731792e5e56b9ec2a78a83a2 Fixing Commit: 5f46400f7a6a4fad635d5a79e2aa5a04a30ffea1 5.10: Commit: fa5f2e04daa44961a1026e93f0cc88caa3c27d3d (5.10.11) Fixing Commit: 5f3d54c00f1f2682cee9c590c22655b0330ffd18 (5.10.13) 5.4: Commit: a09d4e7acdbf276b2096661ee82454ae3dd24d2b (5.4.93) Fixing commit 2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f (5.4.95) Without this patch you cannot start guests (DomU) on this machine! Error message while creating DomU: libxl: error: libxl_device.c:1105:device_backend_callback: Domain X:unable to add device with path / libxl: error: libxl_create.c:1452:domcreate_launch_dm: Domain X:unable to add disk devices See: - https://lkml.org/lkml/2021/1/28/1231 and https://lkml.org/lkml/2021/1/29/14 - https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.107=2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f -
[Kernel-packages] [Bug 1903964] Re: The installer encountered an unrecoverable error
*** This bug is a duplicate of bug 1903378 *** https://bugs.launchpad.net/bugs/1903378 bug #1903378 has been reported as fixed on 2021-01-14 however this bug is present at Kubuntu daily build 2021-03-21 05:49 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1903964 Title: The installer encountered an unrecoverable error Status in linux-meta package in Ubuntu: Confirmed Bug description: Attempting to install Kubuntu Hirsute daily ISO http://cdimage.ubuntu.com/kubuntu/daily-live/20201112/hirsute-desktop-amd64.iso the installer failed with the following error message: The installer encountered an unrecoverable error.A desktop session will now be run so that you may investgate the problem or try installing again. This error occurred immediately after booting and the running of the file checks before entering the installer. The machine invlved were : 1. Dell [Inspiron] 3521, (i3-3217U, 4GB, Intel HD Graphics 4000, Intel HM76 chipset 10/100 Mbps ethernet controller integrated on system board, WiFi 802.11 b/g/N, Bluetooth 4.0, 500 GB hd) This machine was in UEFI+secure boot mode. 2. InWin BL641 i5-10400,32GB,Intel UHD Graphics 630,Ethernet,Intel 660p 512GB M.2 NVMe hd - this install was in a VIrtualBox machine in BIOS mode. Attached is the dmesg log file from the USB media that booted the Dell Inspirion machine (#1 above ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1903964/+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 1903964] Re: The installer encountered an unrecoverable error
*** This bug is a duplicate of bug 1903378 *** https://bugs.launchpad.net/bugs/1903378 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1903964 Title: The installer encountered an unrecoverable error Status in linux-meta package in Ubuntu: Confirmed Bug description: Attempting to install Kubuntu Hirsute daily ISO http://cdimage.ubuntu.com/kubuntu/daily-live/20201112/hirsute-desktop-amd64.iso the installer failed with the following error message: The installer encountered an unrecoverable error.A desktop session will now be run so that you may investgate the problem or try installing again. This error occurred immediately after booting and the running of the file checks before entering the installer. The machine invlved were : 1. Dell [Inspiron] 3521, (i3-3217U, 4GB, Intel HD Graphics 4000, Intel HM76 chipset 10/100 Mbps ethernet controller integrated on system board, WiFi 802.11 b/g/N, Bluetooth 4.0, 500 GB hd) This machine was in UEFI+secure boot mode. 2. InWin BL641 i5-10400,32GB,Intel UHD Graphics 630,Ethernet,Intel 660p 512GB M.2 NVMe hd - this install was in a VIrtualBox machine in BIOS mode. Attached is the dmesg log file from the USB media that booted the Dell Inspirion machine (#1 above ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1903964/+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
