[Kernel-packages] [Bug 1917446] Re: screen becomes green and haze
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1917446 Title: screen becomes green and haze Status in linux package in Ubuntu: Expired Bug description: screen of ubuntu becomes green and haze. the screen is not clearly visible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917446/+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 1879214] Re: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported
** Changed in: makedumpfile (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1879214 Title: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Bionic: Fix Committed Status in makedumpfile source package in Focal: Fix Committed Status in makedumpfile source package in Groovy: Fix Committed Status in makedumpfile source package in Hirsute: Fix Released Status in makedumpfile package in Debian: Fix Released Bug description: [Impact] On arm64 and kernels 5.4+ makedumpfile fails. Upstream patches solve this bug : [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage option https://github.com/makedumpfile/makedumpfile/commit/d8b701796f0491f2ac4b06c7a5b795c29399efab [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo https://github.com/makedumpfile/makedumpfile/commit/67d0e1d68f28c567a704fd6b9b8fd696ad3df183 [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA https://github.com/makedumpfile/makedumpfile/commit/a0216b678a95f099a16172cc4a67ad5aa6a89583 [Test Case] OS: Ubuntu 20.04 LTS kernel: 5.4.0-21-generic arch:arm64 Description: When testing kdump on Ubuntu 20.04 LTS (arm64), makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The error logs are as follows: [ 26.599161] kdump-tools[653]: Starting kdump-tools: [ 26.612761] kdump-tools[659]: Starting kdump-tools: [ 26.628565] kdump-tools[659]: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/2020050 [ 26.648621] kdump-tools[676]: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/2020050 [ 26.668445] kdump-tools[676]: calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported [ 26.678199] kdump-tools[676]: get_machdep_info_arm64 [ 26.692518] kdump-tools[659]: get_machdep_info_arm64 [ 26.852221] hns3 :7d:00.0: get link status cmd failed -16 [ 94.351303] kdump-tools[659]: * kdump-tools: makedumpfile failed, * kdump-tools: saved vmcore in /var/crash/202005061048 [ 94.435510] kdump-tools[659]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/202005061048/dmesg.202005061048 [ 94.457103] kdump-tools[688]: calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported [ 94.476228] kdump-tools[688]: get_machdep_info_arm64: Can't determine platform config values [ 94.485912] kdump-tools[688]: makedumpfile Failed. [ 94.500760] kdump-tools[659]: * kdump-tools: makedumpfile --dump-dmesg failed. dmesg content will be unavailable [ 94.520225] kdump-tools[659]: * kdump-tools: failed to save dmesg content in /var/crash/202005061048 [ 94.544205] kdump-tools[691]: Wed, 06 May 2020 10:49:42 -0400 [ 94.564597] kdump-tools[692]: Rebooting. [ 94.678709] reboot: Restarting systemlpc uart init Done [Regression Potential] Patch 1 : [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage option removes get_elf_loads function this function was only used with --mem-usage option , since kernel commit kernel commit 23c85094fe18 (kernel versions >4.19) the information needed is in vmcoreinfo Any regression potential would affect the --mem-usage only Patch 2 : [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo arm64 only make use of NUMBER(VA_BITS) in vmcoreinfo as the current way of guessing VA_BITS does not work on Linux 5.4 and later. Before this commit VA_BITS would be calculated in get_versiondep_info_arm64, however this way of calculation breaks after 5.4. This commit gets the VA_BITS from vmcoreinfo and as a safeguard it uses the old way of deriving VA_BITS only if reading from vmcoreinfo doesn't work. From the kernel side VA_BITS is in vmcoreinfo since kernel 4.12, F and later use later kernel so not great regression potentional and if any it would only affect arm64. Patch 3 : [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA arm64 only Linux 5.4 and later kernels for arm64 changed the kernel VA space arrangement and introduced 52-bit kernel VAs by merging branch commit b333b0ba2346. Support 5.9+ kernels with vmcoreinfo entries and 5.4+ kernels with best guessing. This patch makes adjustemnt to properly calculate vabits_actual, max_physmem_bits, page_offset Any regression potential would affect only arm64 and the calculation of the above variables. [Other] For H only the 3 commits are needed and they cherry-pick. For G and F the 3rd commit does not apply and an extra commit is needed : commit da0d25ffa585c9a1adb94562c815daa393b1ee5e [PATCH] arm64: Add
[Kernel-packages] [Bug 1924970] Re: Add soundwire sdca codec support
** Changed in: alsa-ucm-conf (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: alsa-ucm-conf (Ubuntu Hirsute) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1924970 Title: Add soundwire sdca codec support Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: In Progress Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Committed Bug description: [Impact] * The output device in sound settings will non-functional. Sound input device will be empty. An upstream commit add supports for SDW sdca codec support. [Test Plan] * Open settings and select Sound column. Testing speaker won't have any sound output. * Try to update files mentioned here https://github.com/alsa-project/alsa-ucm-conf/pull/71/commits/a7f348bb37d2b3254801702299ab2c76833a3c16 https://github.com/alsa-project/alsa-ucm-conf/pull/71/commits/651c2c851bf17a1d76e0a046eb33eccbcf98845f * alsactl init * Open settings and select Sound column and test output device again. Sound devices work properly. [Where problems could occur] * This change adds new hardware support. * The change only adds new hardware support, it will not affect other codec device. [Other Info] * The change has been verified on Dell machine with sdca codec. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1924970/+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 1842785] Re: Freeze after waking up from suspend on a Ryzen 3000 based system
This bug effects Ubuntu 21.04 and even the mainline kernel 5.12 too. My system: CPU: AMD Ryzen 5 4500U with Radeon Graphics (6) @ 2.375GHz GPU: AMD ATI 03:00.0 Renoir Model: Acer Swift 3 (SF314-42-R2UX) OS: Ubuntu 21.04 Could not make it work by compiling a patched kernel as described here till now: https://gitlab.freedesktop.org/drm/amd/-/issues/1230#note_580057 -- 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/1842785 Title: Freeze after waking up from suspend on a Ryzen 3000 based system Status in linux package in Ubuntu: Confirmed Bug description: My system is a newly build Ryzen 3600 based system with Vega 56 graphics. On suspend wakeup, the entire system locks up. A workaround is booting with linux kernel version 4.19.69. Using newer linux versions (5.3-rc7) did not fix the issue. The motherboard is an MSI B450I gaming plus ac board; I've loaded up both the official non-beta BIOS (7A40vA8) and the newest beta BIOS (7A40vA91) and both have this issue. No dmesg logs are available after the suspend wakeup (last message is putting the system to sleep) I have a r8169 and iwlwifi based ethernet and wifi cards, but I've tentatively isolated that those two are not an issue by blacklisting the respective modules. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-27-generic 5.0.0-27.28 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hatsu 2282 F pulseaudio /dev/snd/controlC2: hatsu 2282 F pulseaudio /dev/snd/controlC0: hatsu 2282 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Sep 4 23:14:34 2019 InstallationDate: Installed on 2019-08-27 (9 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Micro-Star International Co., Ltd. MS-7A40 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic root=UUID=4b8b9e96-fd23-4ade-bcd2-19b9795bd4e6 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-08-27 (9 days ago) dmi.bios.date: 08/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.91 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450I GAMING PLUS AC (MS-7A40) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.91:bd08/19/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A40:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450IGAMINGPLUSAC(MS-7A40):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A40 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842785/+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 1926845] [NEW] Unable to store nvidia-settings
Public bug reported: Since focal a casual unprivileged user cannot save the current X Server Display Configuration, no matter which location is used. I.e. even for e.g. /tmp/xorg.conf or /home/$LOGNAME/xorg.conf the user gets asked for the root password. This really stupid '"AUTHENTICATING FOR com.ubuntu.screen-resolution- extra.root-display" "Authenticating as: root"' bug needs to be fixed. An unprivileged user should be able to store the config wherever he wants to, as long as he has write permission for the related file/directory. ** Affects: nvidia-settings (Ubuntu) Importance: Undecided Status: New ** Package changed: nvidia-settings-updates (Ubuntu) => nvidia-settings (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1926845 Title: Unable to store nvidia-settings Status in nvidia-settings package in Ubuntu: New Bug description: Since focal a casual unprivileged user cannot save the current X Server Display Configuration, no matter which location is used. I.e. even for e.g. /tmp/xorg.conf or /home/$LOGNAME/xorg.conf the user gets asked for the root password. This really stupid '"AUTHENTICATING FOR com.ubuntu.screen-resolution- extra.root-display" "Authenticating as: root"' bug needs to be fixed. An unprivileged user should be able to store the config wherever he wants to, as long as he has write permission for the related file/directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1926845/+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 1926845] [NEW] Unable to store nvidia-settings
You have been subscribed to a public bug: Since focal a casual unprivileged user cannot save the current X Server Display Configuration, no matter which location is used. I.e. even for e.g. /tmp/xorg.conf or /home/$LOGNAME/xorg.conf the user gets asked for the root password. This really stupid '"AUTHENTICATING FOR com.ubuntu.screen-resolution- extra.root-display" "Authenticating as: root"' bug needs to be fixed. An unprivileged user should be able to store the config wherever he wants to, as long as he has write permission for the related file/directory. ** Affects: nvidia-settings (Ubuntu) Importance: Undecided Status: New -- Unable to store nvidia-settings https://bugs.launchpad.net/bugs/1926845 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings 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 269954] Re: ssh -X breaks Xauthority on NFS mounted home dir
** Changed in: debian Status: Confirmed => Fix Released -- 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/269954 Title: ssh -X breaks Xauthority on NFS mounted home dir Status in linux package in Ubuntu: Incomplete Status in Debian: Fix Released Bug description: When using an nfs mounted home directory, using ssh to connect and run a X11 app from the nfs server causes X applications to break. Steps to reproduct the problem 1) have to computers(A and B) with ubuntu 8.04 installed 2) Export /home from computer A, and mount it on computer B 3) Create a user that has the same username, home directory, and UID on both computers 4) Log into computer B with the user that was just created, and ssh into box A and run an X application (ssh -X boxa xterm) 5) In another terminal, try to run another X app on box b as the same user. What is supposed to happen: The X app on box B runs properly What actually happens: The X app will fail with an error like "Xlib: connection to ":0.0" refused by server" about 50% of the time This can be fixed by running "cat ~/.Xauthority". Also sometimes running "ls -al ~/.Xauthority" will result in a "stale nfs file handle" error. I assume this is because the Xauthority file is removed, and then a new one is created when ssh sets up credentials on computer A. This causes the file inode number to change, causing the stale file handle errors on computer B. However, this problem did not occur in ubuntu feisty. I havn't tried it with gutsy. I've tried installing the packages for xauth and libxau6 from feisty, but it did not fix the problem. So I'm guessing its an ssh issue, but i could be wrong. Someone reported the same issue on the ubuntu mailing list, but didn't seem to file a bug report that i could find. https://lists.ubuntu.com/archives/ubuntu-users/2008-July/152242.html I'm using ubuntu 8.04.1, also had the same problem with 8.04.0. It worked fine in ubuntu 7.04. Package Versions == openssh-client: 1:4.7p1-8ubuntu1.2 openssh-server: 1:4.7p1-8ubuntu1.2 xauth: 1:1.0.2-2 libxau6: 1:1.0.3-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/269954/+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 1923150] Re: unexpected error pop-up after 'apt install nvidia-driver-455'
** Changed in: oem-priority Status: Confirmed => Won't Fix ** Changed in: oem-priority Assignee: Alex Tu (alextu) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-455 in Ubuntu. https://bugs.launchpad.net/bugs/1923150 Title: unexpected error pop-up after 'apt install nvidia-driver-455' Status in OEM Priority Project: Won't Fix Status in apt package in Ubuntu: Invalid Status in nvidia-graphics-drivers-455 package in Ubuntu: Invalid Bug description: Ubuntu info: $ lsb_release -rd Description:Ubuntu 20.04.1 LTS (fossa-spark-cml X52) Release 20.04 Full reproduce step 1. nvidia-driver-455 455.45.01-0ubuntu0.20.04.1 is installed in the first place, without all i386 pkg installed. 2. run update-manager to do upgrade. 3. it will show error after download deb and didn't upgrade anything. Per test with the command to do the upgrade, it will have an extra error message, but it will just upgrade and install recommended i386 debs. The error msgs are: E: Could not configure 'libc6:i386'. E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) Short way to get the error: # apt-get install libgcc-s1:i386 --dry-run Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: apt-clone archdetect-deb dctrl-tools dmraid gir1.2-timezonemap-1.0 gir1.2-xkl-1.0 kpartx kpartx-boot libdebian-installer4 libdmraid1.0.0.rc16 libtimezonemap-data libtimezonemap1 python3-icu python3-pam rdate Use 'apt autoremove' to remove them. The following additional packages will be installed: gcc-10-base:i386 libc6 libc6:i386 libcrypt1:i386 libidn2-0:i386 libunistring2:i386 Suggested packages: glibc-doc glibc-doc:i386 locales:i386 The following NEW packages will be installed: gcc-10-base:i386 libc6:i386 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386 libunistring2:i386 The following packages will be upgraded: libc6 1 upgraded, 6 newly installed, 0 to remove and 235 not upgraded. Inst libc6 [2.31-0ubuntu9.1] (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) Inst libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) [] Conf libc6 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) [] Inst libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Conf gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) Conf libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) Inst libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Inst libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) Conf libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Conf libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) E: Could not configure 'libc6:i386'. E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) For now, we think the above Error is the root cause of update-manager failure. --- This happens as upgrade package nvidia-driver-455 from 455.45.01-0ubuntu0.20.04.1 to 460.39-0ubuntu0.20.04.1. for more detail, please check the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923150/+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 1922651] Re: r8152 tx status -71
> So, the k option, while improving the situation, doesn't seem to solve it fully. Or maybe the new kernel enabled link power management for the "Lenovo USB3.1 Hub" devices? The devices in question (excerpt from `lsusb`): Bus 005 Device 003: ID 17ef:a393 Lenovo USB3.1 Hub Bus 005 Device 004: ID 17ef:a387 Lenovo USB-C Dock Ethernet Bus 005 Device 002: ID 17ef:a391 Lenovo USB3.1 Hub I've therefore started using usbcore.quirks=17ef:a387:k,17ef:a393:k,17ef:a391:k , I'll test and post more. -- 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/1922651 Title: r8152 tx status -71 Status in linux package in Ubuntu: Confirmed Bug description: I've bought ThinkPad T14s with a USB-based docking station. Everything is working marvelously, but from time to time the ethernet port on the docking station won't connect. I've discovered the following messages in my dmesg: [ 400.597506] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 401.164370] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 463.168412] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 465.314415] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 529.409871] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 533.718163] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 591.168537] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 594.335383] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 Rebooting the machine doesn't seem to work, turning the ethernet connection off and on doesn't seem to work. I have a dualboot Linux+Windows (one wants to play games from time to time :-p ) and it could be that rebooting from Win to Lin causes this issue, but this needs to be confirmed yet. I will try to power off the computer and/or the docking station, to see whether that would help. I've found numerous bug reports, but they are rather old or may not apply to this situation, therefore I figured it's best to open a new bug report. Thank you so much for your hard work! ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-48-generic 5.8.0-48.54 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 6 10:00:29 2021 InstallationDate: Installed on 2021-03-24 (12 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20UH001QMX ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-48-generic root=UUID=14a0-0947-4e58-ade1-ad9963053d85 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-48-generic N/A linux-backports-modules-5.8.0-48-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2020 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET61W(1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UH001QMX dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.30 dmi.modalias: dmi:bvnLENOVO:bvrR1CET61W(1.30):bd12/21/2020:br1.30:efr1.30:svnLENOVO:pn20UH001QMX:pvrThinkPadT14sGen1:rvnLENOVO:rn20UH001QMX:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14s Gen 1 dmi.product.name: 20UH001QMX dmi.product.sku: LENOVO_MT_20UH_BU_Think_FM_ThinkPad T14s Gen 1 dmi.product.version: ThinkPad T14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922651/+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 1926755] Re: Support Auvidea B101 (TC358743)
** Also affects: linux-raspi (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Hirsute) Status: New => Confirmed ** Changed in: linux-raspi (Ubuntu Groovy) Status: New => Confirmed ** Changed in: linux-raspi (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1926755 Title: Support Auvidea B101 (TC358743) Status in linux-raspi package in Ubuntu: New Status in linux-raspi source package in Focal: Confirmed Status in linux-raspi source package in Groovy: Confirmed Status in linux-raspi source package in Hirsute: Confirmed Bug description: [Impact] The Auvidea B101 module doesn't work on raspberry pi 4 with 20.04.2 LTS ubuntu server image. [Test Plan] With enabling CONFIG_VIDEO_TC358743 [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1926755/+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 1909457] Re: Support CML-S CPU + TGP PCH
sudo patch -p0 /lib/modules/5.12.0-051200-generic/kernel/drivers/gpu/drm/i915/i915.ko < i915.patch patching file /lib/modules/5.12.0-051200-generic/kernel/drivers/gpu/drm/i915/i915.ko Hunk #1 FAILED at 1263. 1 out of 1 hunk FAILED -- saving rejects to file /lib/modules/5.12.0-051200-generic/kernel /drivers/gpu/drm/i915/i915.ko.rej -- 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/1909457 Title: Support CML-S CPU + TGP PCH Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: [Impact] i915 driver gives below warnings that CML-S GPU doesn't work with TGL/RKL PCH, and the screen is blank. kernel: i915 :00:02.0: drm_WARN_ON(!IS_PLATFORM(dev_priv, INTEL_TIGERLAKE) && !IS_PLATFORM(dev_priv, INTEL_ROCKETLAKE)) [Fix] Intel provides us a new patch for this issue https://patchwork.freedesktop.org/patch/412664/ [Test] Verified on new Dell platforms. [Where problems could occur] The first commit reverts the patch that didn't find its way to upstream. The second to forth commits are to enable DG1 which applied for solving conflicts. The fifth and sixth commit splits code for EHL and JSL. The seventh and eighth commits rename enums, no function changes. The ninth commit is newer version of the first reverted commit. The tenth commit adds CML CPU support on TGP PCH which fixes this issue. According to the above explanation, 1. the DG1 in newly enabled by commits 2 to 4, no regression could occur, 2. the EHL and JSL commits are pretty simple and straightforward, should be safe to include, 3. the first commit is equivalence to the ninth commit 4. the tenth commit is pretty simple to add GEN9 into flow control, so I think there should be no problems could occur from this patchset. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1909457/+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 1909457] Re: Support CML-S CPU + TGP PCH
Some release notes or a readme would be very helpful. I tried several ways to run patch to install the intel patch and no luck. It seems many are being affected by this and currently the only work around is to use the 20.04b OEM kernel. -- 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/1909457 Title: Support CML-S CPU + TGP PCH Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: [Impact] i915 driver gives below warnings that CML-S GPU doesn't work with TGL/RKL PCH, and the screen is blank. kernel: i915 :00:02.0: drm_WARN_ON(!IS_PLATFORM(dev_priv, INTEL_TIGERLAKE) && !IS_PLATFORM(dev_priv, INTEL_ROCKETLAKE)) [Fix] Intel provides us a new patch for this issue https://patchwork.freedesktop.org/patch/412664/ [Test] Verified on new Dell platforms. [Where problems could occur] The first commit reverts the patch that didn't find its way to upstream. The second to forth commits are to enable DG1 which applied for solving conflicts. The fifth and sixth commit splits code for EHL and JSL. The seventh and eighth commits rename enums, no function changes. The ninth commit is newer version of the first reverted commit. The tenth commit adds CML CPU support on TGP PCH which fixes this issue. According to the above explanation, 1. the DG1 in newly enabled by commits 2 to 4, no regression could occur, 2. the EHL and JSL commits are pretty simple and straightforward, should be safe to include, 3. the first commit is equivalence to the ninth commit 4. the tenth commit is pretty simple to add GEN9 into flow control, so I think there should be no problems could occur from this patchset. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1909457/+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 1926809] Re: WD19 dock stops working in Ubuntu 21.04
I used the mainline tool to install kernel 5.12. The dock is back again and everything appears to work. ``` mulhollandd@mulhollandd-XPS-13-9360:~$ uname -a Linux mulhollandd-XPS-13-9360 5.12.0-051200-generic #202104252130 SMP Sun Apr 25 21:33:13 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux mulhollandd@mulhollandd-XPS-13-9360:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 21.04 Release:21.04 Codename: hirsute mulhollandd@mulhollandd-XPS-13-9360:~$ sudo dmesg --level=err [sudo] password for mulhollandd: [0.011338] efi: Failed to lookup EFI memory descriptor for 0x7b014000 [ 14.615560] xhci_hcd :39:00.0: xHCI host controller not responding, assume dead [ 14.615574] xhci_hcd :39:00.0: HC died; cleaning up [ 15.030088] usb 4-1.3: device not accepting address 3, error -108 [ 15.030150] usb 4-1-port3: couldn't allocate usb_device [ 15.030198] usb 3-1-port5: couldn't allocate usb_device [ 112.758908] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb b3a810eb port 3: DPCD read on addr 0x4b0 for 1 bytes NAKed mulhollandd@mulhollandd-XPS-13-9360:~$ ``` -- 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/1926809 Title: WD19 dock stops working in Ubuntu 21.04 Status in linux package in Ubuntu: Confirmed Bug description: This morning I upgraded to Kubuntu 21.04. I use two external monitors connected to my Dell XPS laptop via a Dell WD19 dock. Post-upgrade the monitors and also network functionality through the dock appear to have completely stopped functioning. When the dock is plugged in and the computer is booted the monitors do not enable. When the dock is not plugged in the computer boots normally. When I look at the dmesg output there appears to be some notable errors when I plug the dock in: [ 516.173451] xhci_hcd :39:00.0: xHCI host controller not responding, assume dead [ 516.207480] xhci_hcd :39:00.0: HC died; cleaning up [ 521.313422] pcieport :02:00.0: can't change power state from D3cold to D0 (config space inaccessible) [ 555.140320] xhci_hcd :39:00.0: xHCI host controller not responding, assume dead [ 555.140343] xhci_hcd :39:00.0: HC died; cleaning up [ 560.291086] pcieport :02:00.0: can't change power state from D3cold to D0 (config space inaccessible) [ 850.385934] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb eaa106e4 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 850.499763] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb eaa106e4 port 3: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 851.717630] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 851.815190] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 856.231021] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb eaa106e4 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 856.301269] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb eaa106e4 port 3: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 856.320487] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 856.343208] i915 :00:02.0: [drm] *ERROR* CPU pipe B FIFO underrun [ 856.382831] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 860.704920] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 860.765138] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 860.894454] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 860.965337] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 861.115198] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 861.182111] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 866.232326] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb eaa106e4 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 866.351715] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 866.454536] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb eaa106e4 port 3: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 866.473097] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 866.534697] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful With the dock plugged in: * neither monitor displays although they are present under display configuration * since my laptop screen is not usually on if both monitors are present on the dock the immediate result was no display at all under the dock was detached * network connectivity is not established although the network device appears under networks Unfortunately I lack the skills to diagnose this further without assistance or to install a more recent kernel to see if it is resolved there. It appears that communications between the laptop and the
[Kernel-packages] [Bug 1921995] Re: hirsute kernels 5.11 do not boot on AMD STONEY hardware
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- 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/1921995 Title: hirsute kernels 5.11 do not boot on AMD STONEY hardware Status in Kernel SRU Workflow: New Status in linux package in Ubuntu: Fix Released Bug description: latest 5.11-0-11 and 5.11.0-13 kernels do not boot on my hardware (ASUS X505BA), hanging after boot, without displaying any errors. attaching apport-collect from latest 5.10.0-14 kernel which boots correctly --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1816 F pulseaudio /dev/snd/controlC0: eugene 1816 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 RelatedPackageVersions: linux-restricted-modules-5.10.0-14-generic N/A linux-backports-modules-5.10.0-14-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 1877 F pulseaudio /dev/snd/controlC0: eugene 1877 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-11-20 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7 iommu=soft ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 RelatedPackageVersions: linux-restricted-modules-5.11.0-13-generic N/A linux-backports-modules-5.11.0-13-generic N/A linux-firmware 1.195 Tags: hirsute wayland-session Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1921995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
