[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
After upgrading to kernel 5.19.0-42 hdmi sound work. A (very) little issue: in Preference Panel-Audio-Output, not work the audio "test"! Processor: AMD® Ryzen 5 3600 6-core processor × 12 Graphic: AMD® Radeon rx 580 series OS Name: Ubuntu 22.04.2 LTS 64-bit GNOME version: 42.5 Graphic System: Wayland -- 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/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Committed Bug description: [Impact] For amdgpu/i915, hdmi audio output device has disappeared. [Fix] The latest fix for the non-contiguous memalloc helper changed the allocation method for a non-IOMMU system to use only the fallback allocator. This should have worked, but it caused a problem sometimes when too many non-contiguous pages are allocated that can't be treated by HD-audio controller. As a quirk workaround, go back to the original strategy: use dma_alloc_noncontiguous() at first, and apply the fallback only when it fails, but only for non-IOMMU case [Test Case] 1. boot with kernel applied the patches. 2. check the cards in /proc/asound/cards. Get the hdmi cards. 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xe232 irq 137 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xe226 irq 134 [Where problems could occur] Low, this is just workaround and may have a better solution in the future. [Misc] All patches has been landed on OEM-6.1 and lunar. ~~ CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. Currently known affected cards: * HD 7700 (comment 8) * R9 290 (comment 21) * RX 550 (LP: #2012141, and comment 27) * RX 570 (mine) * RX 580 (LP: #2009276, and comment 28) * WX 3200 (comment 29) * RX 6600 (LP: #2009542) * RX 6700 (LP: #2009275) [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
The "problem" is inside of kernel-modules. Probably there is some conflict between the snd modules (snd-hda-intel?) and hardware. This is a historical problem of all linux distributions that has been repeating cyclically for many years. -- 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/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Released Bug description: [Impact] For amdgpu/i915, hdmi audio output device has disappeared. [Fix] The latest fix for the non-contiguous memalloc helper changed the allocation method for a non-IOMMU system to use only the fallback allocator. This should have worked, but it caused a problem sometimes when too many non-contiguous pages are allocated that can't be treated by HD-audio controller. As a quirk workaround, go back to the original strategy: use dma_alloc_noncontiguous() at first, and apply the fallback only when it fails, but only for non-IOMMU case [Test Case] 1. boot with kernel applied the patches. 2. check the cards in /proc/asound/cards. Get the hdmi cards. 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xe232 irq 137 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xe226 irq 134 [Where problems could occur] Low, this is just workaround and may have a better solution in the future. [Misc] All patches has been landed on OEM-6.1 and lunar. ~~ CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. Currently known affected cards: * HD 7700 (comment 8) * R9 290 (comment 21) * RX 550 (LP: #2012141, and comment 27) * RX 570 (mine) * RX 580 (LP: #2009276, and comment 28) * WX 3200 (comment 29) * RX 6600 (LP: #2009542) * RX 6700 (LP: #2009275) [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 2009276] [NEW] Audio Hdmi (Radeon rx580) not recognized
Public bug reported: After kernel upgrade, from 5.19.0-32 to 5.19.0-35 the audio don't work. At boot appears the message: hdaudio_hdaudioC0D0: no AFG or MFG node found snd_hda-intel :26:00.1: no codecs initialized Processor: AMD® Ryzen 5 3600 6-core processor × 12 Graphic: AMD® Radeon rx 580 series OS Name: Ubuntu 22.04.2 LTS 64-bit GNOME version: 42.5 Graphic System: Wayland ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 4 19:17:19 2023 InstallationDate: Installed on 2022-05-07 (301 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009276 Title: Audio Hdmi (Radeon rx580) not recognized Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: After kernel upgrade, from 5.19.0-32 to 5.19.0-35 the audio don't work. At boot appears the message: hdaudio_hdaudioC0D0: no AFG or MFG node found snd_hda-intel :26:00.1: no codecs initialized Processor: AMD® Ryzen 5 3600 6-core processor × 12 Graphic: AMD® Radeon rx 580 series OS Name: Ubuntu 22.04.2 LTS 64-bit GNOME version: 42.5 Graphic System: Wayland ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 4 19:17:19 2023 InstallationDate: Installed on 2022-05-07 (301 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009276/+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 1947361] [NEW] 1930783
Public bug reported: for install ubuntu on the Acer nitro 5 515 55 78 arrive the problem loading x.509 certificate - 65 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 15 13:38:53 2021 InstallationDate: Installed on 2021-08-28 (47 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1947361 Title: 1930783 Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: for install ubuntu on the Acer nitro 5 515 55 78 arrive the problem loading x.509 certificate - 65 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 15 13:38:53 2021 InstallationDate: Installed on 2021-08-28 (47 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1947361/+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 1944752] Re: AER PCIe Bus Error for Asus X541UVK
Hi, I currently do not have access to a running linux system to compile and test the patch with, since the only pc that I have is my laptop affected by this bug, and I also really need windows on it for some windows-specific software for my university. So, It's not possible for me right now to test the patch. I'll leave some more specific info about my system (hoping that somebody else has the same exact machine) for anyone that is willing to test this (I'm copying this from System Information). System ModelX541UVK Processor Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz Adapter Description Intel(R) HD Graphics 620 Adapter Description NVIDIA GeForce 920MX BIOS Version/Date American Megatrends Inc. X541UVK.308, 30-Jan-18 Thanks to everyone for the help, I'll keep in touch. Riccardo -- 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/1944752 Title: AER PCIe Bus Error for Asus X541UVK Status in linux package in Ubuntu: Incomplete Bug description: I already posted this on the Ubuntu Forums and I'm revisiting it now with more information and accuracy. Whenever I try to install any flavor of *buntu, I always run into this problem; a process taking up all of my CPU and after a while, it crashes the system and the whole screen goes black with text spamming. It shows some PCI errors non-stop, and following some guides online i tried to fix it but never actually succeeded. The distro I was trying to install this time was the default 20.04.2 Ubuntu. My PC is a laptop, it's an ASUS X541UVK with an i7 7500U and Geforce 920MX. At first I thought that there was a problem with the Nvidia GPU but it appears to be with the Realtek BT card. I went to follow this guide: https://forums.linuxmint.com/viewtopic.php?t=305970 (since using pci=nomsi once solved the issue some time ago) And the reproduced steps from the guide above are here (from the live usb): https://imgur.com/a/enq5UCt However this still doesn't solve my problems. I submitted my information at the time on this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173 But now I made a duplicate of the bug since my pc has slightly different hardware. Also, I have a little bit more free time now. So, this time, I tried again with Ubuntu 20.04.3 and the results were pretty much the same; after booting up Ubuntu reported an "internal error" and I just managed to open the Gnome System Monitor (and sort the processes by CPU usage) just before the entire pc froze. Here are some pictures: https://imgur.com/a/Sd7TO4y Then, as suggested in the original bug report ( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/comments/139 ), I tried booting using the "pci=noaer" option, and the desktop at first booted fine, much quicker than before also, but for a few seconds the screen went black and these appeared on screen: https://imgur.com/a/Ppq2D0W Then after that it just went back to normal, and I didn't notice any anomaly. Also here (again, as suggested in the other bug report) I copy-pasted the results of "lspci -nn" and "dmesg": https://pastebin.com/HMvdhvnz https://pastebin.com/pnjPNcWr I really hope this helps towards finding the issue :) for anything else for me to try, feel free to suggest and I'll try it and report the results. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944752/+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 1944752] Re: AER PCIe Bus Error for Asus X541UVK
Ok great! If there is anything else I can do or try let me know. -- 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/1944752 Title: AER PCIe Bus Error for Asus X541UVK Status in linux package in Ubuntu: Incomplete Bug description: I already posted this on the Ubuntu Forums and I'm revisiting it now with more information and accuracy. Whenever I try to install any flavor of *buntu, I always run into this problem; a process taking up all of my CPU and after a while, it crashes the system and the whole screen goes black with text spamming. It shows some PCI errors non-stop, and following some guides online i tried to fix it but never actually succeeded. The distro I was trying to install this time was the default 20.04.2 Ubuntu. My PC is a laptop, it's an ASUS X541UVK with an i7 7500U and Geforce 920MX. At first I thought that there was a problem with the Nvidia GPU but it appears to be with the Realtek BT card. I went to follow this guide: https://forums.linuxmint.com/viewtopic.php?t=305970 (since using pci=nomsi once solved the issue some time ago) And the reproduced steps from the guide above are here (from the live usb): https://imgur.com/a/enq5UCt However this still doesn't solve my problems. I submitted my information at the time on this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173 But now I made a duplicate of the bug since my pc has slightly different hardware. Also, I have a little bit more free time now. So, this time, I tried again with Ubuntu 20.04.3 and the results were pretty much the same; after booting up Ubuntu reported an "internal error" and I just managed to open the Gnome System Monitor (and sort the processes by CPU usage) just before the entire pc froze. Here are some pictures: https://imgur.com/a/Sd7TO4y Then, as suggested in the original bug report ( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/comments/139 ), I tried booting using the "pci=noaer" option, and the desktop at first booted fine, much quicker than before also, but for a few seconds the screen went black and these appeared on screen: https://imgur.com/a/Ppq2D0W Then after that it just went back to normal, and I didn't notice any anomaly. Also here (again, as suggested in the other bug report) I copy-pasted the results of "lspci -nn" and "dmesg": https://pastebin.com/HMvdhvnz https://pastebin.com/pnjPNcWr I really hope this helps towards finding the issue :) for anything else for me to try, feel free to suggest and I'll try it and report the results. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944752/+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 1521173] Re: AER: Corrected error received: id=00e0
I just created the new bug report as suggested, here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944752 -- 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/1521173 Title: AER: Corrected error received: id=00e0 Status in Linux: Confirmed Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: WORKAROUND: add pci=noaer to your kernel command line: 1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer" 2) run "sudo update-grub" 3) reboot My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot. [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5315.995674] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.002826] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.009979] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error ProblemType: BugDistroRelease: Ubuntu 16.04 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: boot/vmlinuz-4.2.0-19-generic] ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 1502 F...m pulseaudio /dev/snd/controlC0: david 1502 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 30 13:19:00 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.153SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0NT3WX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+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 1944752] [NEW] AER PCIe Bus Error for Asus X541UVK
Public bug reported: I already posted this on the Ubuntu Forums and I'm revisiting it now with more information and accuracy. Whenever I try to install any flavor of *buntu, I always run into this problem; a process taking up all of my CPU and after a while, it crashes the system and the whole screen goes black with text spamming. It shows some PCI errors non-stop, and following some guides online i tried to fix it but never actually succeeded. The distro I was trying to install this time was the default 20.04.2 Ubuntu. My PC is a laptop, it's an ASUS X541UVK with an i7 7500U and Geforce 920MX. At first I thought that there was a problem with the Nvidia GPU but it appears to be with the Realtek BT card. I went to follow this guide: https://forums.linuxmint.com/viewtopic.php?t=305970 (since using pci=nomsi once solved the issue some time ago) And the reproduced steps from the guide above are here (from the live usb): https://imgur.com/a/enq5UCt However this still doesn't solve my problems. I submitted my information at the time on this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173 But now I made a duplicate of the bug since my pc has slightly different hardware. Also, I have a little bit more free time now. So, this time, I tried again with Ubuntu 20.04.3 and the results were pretty much the same; after booting up Ubuntu reported an "internal error" and I just managed to open the Gnome System Monitor (and sort the processes by CPU usage) just before the entire pc froze. Here are some pictures: https://imgur.com/a/Sd7TO4y Then, as suggested in the original bug report ( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/comments/139 ), I tried booting using the "pci=noaer" option, and the desktop at first booted fine, much quicker than before also, but for a few seconds the screen went black and these appeared on screen: https://imgur.com/a/Ppq2D0W Then after that it just went back to normal, and I didn't notice any anomaly. Also here (again, as suggested in the other bug report) I copy- pasted the results of "lspci -nn" and "dmesg": https://pastebin.com/HMvdhvnz https://pastebin.com/pnjPNcWr I really hope this helps towards finding the issue :) for anything else for me to try, feel free to suggest and I'll try it and report the results. ** Affects: linux (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/1944752 Title: AER PCIe Bus Error for Asus X541UVK Status in linux package in Ubuntu: New Bug description: I already posted this on the Ubuntu Forums and I'm revisiting it now with more information and accuracy. Whenever I try to install any flavor of *buntu, I always run into this problem; a process taking up all of my CPU and after a while, it crashes the system and the whole screen goes black with text spamming. It shows some PCI errors non-stop, and following some guides online i tried to fix it but never actually succeeded. The distro I was trying to install this time was the default 20.04.2 Ubuntu. My PC is a laptop, it's an ASUS X541UVK with an i7 7500U and Geforce 920MX. At first I thought that there was a problem with the Nvidia GPU but it appears to be with the Realtek BT card. I went to follow this guide: https://forums.linuxmint.com/viewtopic.php?t=305970 (since using pci=nomsi once solved the issue some time ago) And the reproduced steps from the guide above are here (from the live usb): https://imgur.com/a/enq5UCt However this still doesn't solve my problems. I submitted my information at the time on this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173 But now I made a duplicate of the bug since my pc has slightly different hardware. Also, I have a little bit more free time now. So, this time, I tried again with Ubuntu 20.04.3 and the results were pretty much the same; after booting up Ubuntu reported an "internal error" and I just managed to open the Gnome System Monitor (and sort the processes by CPU usage) just before the entire pc froze. Here are some pictures: https://imgur.com/a/Sd7TO4y Then, as suggested in the original bug report ( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/comments/139 ), I tried booting using the "pci=noaer" option, and the desktop at first booted fine, much quicker than before also, but for a few seconds the screen went black and these appeared on screen: https://imgur.com/a/Ppq2D0W Then after that it just went back to normal, and I didn't notice any anomaly. Also here (again, as suggested in the other bug report) I copy-pasted the results of "lspci -nn" and "dmesg": https://pastebin.com/HMvdhvnz https://pastebin.com/pnjPNcWr I really hope this helps towards finding the issue :) for anything else for me to try, feel free
[Kernel-packages] [Bug 1874194] Re: Ubuntu 20.04 HDMI connected, no boot
*** This bug is a duplicate of bug 1872159 *** https://bugs.launchpad.net/bugs/1872159 Same issue on my Dell 5520 When I REBOOT and the HDMI 2nd monitor is connected, splash screen freezes. _ Specs: Xubuntu 20.04 uname -r 5.8.0-59-generic lspci -vvv Graphics: :00:02.0 VGA compatible controller: Intel Corporation Device 9a49 (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device 0a21 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: i915 Kernel modules: i915 dmesg --level=err,warn [1.039745] Missing case (clock == 539440) [1.039795] WARNING: CPU: 3 PID: 193 at drivers/gpu/drm/i915/display/intel_dpll_mgr.c:2967 icl_calc_dpll_state.isra.0+0x21d/0x280 [i915] [1.039828] RIP: 0010:icl_calc_dpll_state.isra.0+0x21d/0x280 [i915] [1.039829] Code: 4c 63 c2 39 cf 74 55 48 83 c2 01 48 83 fa 08 75 e5 48 63 d7 48 c7 c6 ee b5 7f c0 48 c7 c7 e3 b4 7f c0 88 45 bf e8 ab 32 5e c8 <0f> 0b 0f b6 45 bf e9 ea fe ff ff 31 d2 be 54 00 60 00 e9 9b fe ff [1.039830] RSP: 0018:b460805eb6c8 EFLAGS: 00010282 [1.039830] RAX: RBX: a00c5795a490 RCX: 03bb [1.039831] RDX: 0001 RSI: 0086 RDI: 0247 [1.039831] RBP: b460805eb710 R08: 03bb R09: 0004 [1.039831] R10: R11: 0001 R12: a00c5795a000 [1.039832] R13: a00c5882 R14: a00c68dea800 R15: a00c5795c000 [1.039832] FS: 7f60162cc880() GS:a00c6f6c() knlGS: [1.039833] CS: 0010 DS: ES: CR0: 80050033 [1.039833] CR2: 7fff1750bec0 CR3: 00085902a002 CR4: 00760ee0 [1.039833] PKRU: 5554 [1.039834] Call Trace: [1.039857] icl_get_dplls+0x34b/0x840 [i915] [1.039870] ? drm_mode_object_get+0x2a/0x60 [drm] [1.039877] ? drm_connector_list_iter_next+0x8e/0xb0 [drm] [1.039898] intel_reserve_shared_dplls+0x24/0x60 [i915] [1.039920] hsw_crtc_compute_clock+0x5a/0x90 [i915] [1.039941] intel_atomic_check_crtcs+0x3ba/0x620 [i915] [1.039961] ? icl_put_dplls+0x6c/0xb0 [i915] [1.039980] intel_atomic_check+0xa22/0xb60 [i915] [1.039982] ? __kmalloc_track_caller+0x271/0x280 [1.040004] ? intel_crtc_duplicate_state+0x27/0xb0 [i915] [1.040011] drm_atomic_check_only+0x2c7/0x450 [drm] [1.040017] drm_atomic_commit+0x18/0x50 [drm] [1.040037] intel_modeset_init+0x456/0xae0 [i915] [1.040055] i915_driver_probe+0x275/0x500 [i915] [1.040058] ? _cond_resched+0x19/0x30 [1.040059] ? mutex_lock+0x13/0x40 [1.040077] i915_pci_probe+0x5a/0x140 [i915] [1.040080] local_pci_probe+0x48/0x80 [1.040081] pci_device_probe+0x10f/0x1b0 [1.040083] really_probe+0x159/0x3d0 [1.040084] driver_probe_device+0xe9/0x160 [1.040085] device_driver_attach+0x5d/0x70 [1.040086] __driver_attach+0x8f/0x150 [1.040087] ? device_driver_attach+0x70/0x70 [1.040087] bus_for_each_dev+0x7e/0xc0 [1.040088] driver_attach+0x1e/0x20 [1.040089] bus_add_driver+0x152/0x1f0 [1.040089] driver_register+0x74/0xd0 [1.040090] __pci_register_driver+0x54/0x60 [1.040109] i915_init+0x61/0x75 [i915] [1.040110] ? 0xc089 [1.040112] do_one_initcall+0x4a/0x200 [1.040113] ? vfree+0x2c/0x40 [1.040114] ? _cond_resched+0x19/0x30 [1.040115] ? kmem_cache_alloc_trace+0x1b0/0x240 [1.040116] do_init_module+0x62/0x250 [1.040117] load_module+0x1185/0x1390 [1.040119] ? ima_post_read_file+0x108/0x120 [1.040120] __do_sys_finit_module+0xc9/0x130 [1.040121] ? __do_sys_finit_module+0xc9/0x130 [1.040122] __x64_sys_finit_module+0x1a/0x20 [1.040123] do_syscall_64+0x49/0xc0 [1.040124] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1.040124] RIP: 0033:0x7f601684e89d -- 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/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida p
[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0
Hello to all. I have the same problem, and this has affected me for a long time now. I described it in detail here, with output, videos, photos etc: https://ubuntuforums.org/showthread.php?t=2460318 I hope this adds useful information to draw attention to the bug in question. -- 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/1521173 Title: AER: Corrected error received: id=00e0 Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: WORKAROUND: add pci=noaer to your kernel command line: 1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer" 2) run "sudo update-grub" 3) reboot My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot. [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5315.995674] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.002826] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.009979] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error ProblemType: BugDistroRelease: Ubuntu 16.04 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: boot/vmlinuz-4.2.0-19-generic] ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 1502 F...m pulseaudio /dev/snd/controlC0: david 1502 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 30 13:19:00 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.153SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0NT3WX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+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 1888151] [NEW] Touchpad not detected in Obsidian N141ZU
Public bug reported: Touchpad not detected in Obsidian N141ZU after fresh install of Ubuntu 20.04. Touchpad does not show up in /proc/bus/input/devices (file attached). USB Mouse works correctly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: riccardo 1454 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 21:29:26 2020 InstallationDate: Installed on 2020-07-19 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b649 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: OBSIDIAN-PC N13_N140ZU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=bfa60060-8b72-4cea-a496-e88f2b99bdb7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: N13_N140ZU dmi.board.vendor: OBSIDIAN-PC dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OBSIDIAN-PC dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04:bd12/21/2018:svnOBSIDIAN-PC:pnN13_N140ZU:pvrNotApplicable:rvnOBSIDIAN-PC:rnN13_N140ZU:rvrNotApplicable:cvnOBSIDIAN-PC:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N13_N140ZU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: OBSIDIAN-PC ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "devices" https://bugs.launchpad.net/bugs/1888151/+attachment/5394167/+files/devices -- 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/1888151 Title: Touchpad not detected in Obsidian N141ZU Status in linux package in Ubuntu: New Bug description: Touchpad not detected in Obsidian N141ZU after fresh install of Ubuntu 20.04. Touchpad does not show up in /proc/bus/input/devices (file attached). USB Mouse works correctly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: riccardo 1454 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 21:29:26 2020 InstallationDate: Installed on 2020-07-19 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b649 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: OBSIDIAN-PC N13_N140ZU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=bfa60060-8b72-4cea-a496-e88f2b99bdb7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: N13_N140ZU dmi.board.vendor: OBSIDIAN-PC dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OBSIDIAN-PC dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04:bd12/21/2018:svnOBSIDIAN-PC:pnN13_N140ZU:pvrNotApplicable:rvnOBSIDIAN-PC:rnN13_N140ZU:rvrNotApplicable:cvnOBSIDIAN-PC:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N13_N140ZU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.
[Kernel-packages] [Bug 1875672] Re: lubuntu 20.04 lts can't find touchpad
orporation MCP79 SATA Controller [10de:0ab4] (rev b1) (prog-if 85 [PCI native mode-only controller, supports bus mastering]) Subsystem: ASUSTeK Computer Inc. MCP79 SATA Controller [1043:1a87] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ahci Kernel modules: ahci, pata_acpi 00:10.0 PCI bridge [0604]: NVIDIA Corporation MCP79 PCI Express Bridge [10de:0aa0] (rev b1) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: 00:15.0 PCI bridge [0604]: NVIDIA Corporation MCP79 PCI Express Bridge [10de:0ac6] (rev b1) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:16.0 PCI bridge [0604]: NVIDIA Corporation MCP79 PCI Express Bridge [10de:0ac7] (rev b1) (prog-if 00 [Normal decode]) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:17.0 PCI bridge [0604]: NVIDIA Corporation MCP79 PCI Express Bridge [10de:0ac7] (rev b1) (prog-if 00 [Normal decode]) Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:18.0 PCI bridge [0604]: NVIDIA Corporation MCP79 PCI Express Bridge [10de:0ac7] (rev b1) (prog-if 00 [Normal decode]) Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 02:00.0 VGA compatible controller [0300]: NVIDIA Corporation MCP79 [GeForce 8200M G] [10de:086f] (rev b1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. MCP79 [GeForce 8200M G] [1043:16b2] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia 06:00.0 Network controller [0280]: Qualcomm Atheros AR928X Wireless Network Adapter (PCI-Express) [168c:002a] (rev 01) Subsystem: AzureWave AW-NE771 802.11bgn Wireless Mini PCIe Card [AR9281] [1a3b:1067] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ath9k Kernel modules: ath9k ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: riccardo891 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Tue Apr 28 17:32:19 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 001 Device 003: ID 04f2:b012 Chicony Electronics Co., Ltd 1.3 MPixel UVC Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c247 Logitech, Inc. G100S Optical Gaming Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/8p, 12M |__ Port 2: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehc
[Kernel-packages] [Bug 1785731] Re: Linux Mint 19
kernel-fixed-upstream ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Riccardo Casa (rikmac) -- 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/1785731 Title: Linux Mint 19 Status in linux package in Ubuntu: Incomplete Bug description: Last kernel update 4.15.0-30 CPU1 idle after kernel update. System:Host: iw5dgq-K53SC Kernel: 4.15.0-30-generic x86_64 bits: 64 gcc: 7.3.0 Desktop: Cinnamon 3.8.8 (Gtk 3.22.30-1ubuntu1) dm: lightdm Distro: Linux Mint 19 Tara Machine: Device: laptop System: ASUSTeK product: K53SC v: 1.0 serial: N/A Mobo: ASUSTeK model: K53SC v: 1.0 serial: N/A BIOS: American Megatrends v: K53SC.204 date: 05/30/2011 BatteryBAT0: charge: 48.9 Wh 96.7% condition: 50.6/56.2 Wh (90%) volts: 12.4/10.8 model: [MKF_CUSTOMER] [MKF_BASEBOARD_ID] serial: N/A status: N/A CPU: Dual core Intel Core i5-2410M (-MT-MCP-) arch: Sandy Bridge rev.7 cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9179 clock speeds: min/max: 800/2900 MHz 1: 2693 MHz 2: 2694 MHz 3: 2693 MHz 4: 2694 MHz Graphics: Card-1: Intel 2nd Generation Core Integrated Graphics Controller bus-ID: 00:02.0 chip-ID: 8086:0116 Card-2: NVIDIA GF119M [GeForce GT 520MX] bus-ID: 01:00.0 chip-ID: 10de:1051 Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting (unloaded: fbdev,vesa) Resolution: 1366x768@60.00hz OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile version: 3.3 Mesa 18.0.5 (compat-v: 3.0) Direct Render: Yes Audio: Card Intel 6 Series/C200 Series Family High Def. Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0 chip-ID: 8086:1c20 Sound: Advanced Linux Sound Architecture v: k4.15.0-30-generic Network: Card-1: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) driver: ath9k bus-ID: 03:00.0 chip-ID: 168c:002b IF: wlp3s0 state: up mac: Card-2: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169 v: 2.3LK-NAPI port: 9000 bus-ID: 05:00.0 chip-ID: 10ec:8168 IF: enp5s0 state: down mac: Drives:HDD Total Size: 240.1GB (17.9% used) ID-1: /dev/sda model: KINGSTON_SV300S3 size: 240.1GB serial: Partition: ID-1: / size: 220G used: 41G (20%) fs: ext4 dev: /dev/sda1 RAID: System: supported: N/A No RAID devices: /proc/mdstat, md_mod kernel module present Unused Devices: none Sensors: System Temperatures: cpu: 84.0C mobo: N/A Fan Speeds (in rpm): cpu: N/A Repos: Active apt sources in file: /etc/apt/sources.list.d/google-chrome.list deb [arch=amd64] http: //dl.google.com/linux/chrome/deb/ stable main Active apt sources in file: /etc/apt/sources.list.d/official-package-repositories.list deb http: //mirrors.evowise.com/linuxmint/packages tara main upstream import backport deb http: //mirror.csclub.uwaterloo.ca/ubuntu bionic main restricted universe multiverse deb http: //mirror.csclub.uwaterloo.ca/ubuntu bionic-updates main restricted universe multiverse deb http: //mirror.csclub.uwaterloo.ca/ubuntu bionic-backports main restricted universe multiverse deb http: //security.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse deb http: //archive.canonical.com/ubuntu/ bionic partner Info: Processes: 210 Uptime: 2:20 Memory: 1566.4/7885.5MB Init: systemd v: 237 runlevel: 5 Gcc sys: 7.3.0 Client: Unknown python3.6 client inxi: 2.3.56 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785731/+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 1785731] Re: Linux Mint 19
ok, I try that wen I go home from work and let you know. tnx. Il mar 7 ago 2018, 11:11 AM Joseph Salisbury ha scritto: > Would it be possible for you to test the latest upstream kernel? Refer > to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest > v4.18 kernel[0]. > > If this bug is fixed in the mainline kernel, please add the following > tag 'kernel-fixed-upstream'. > > If the mainline kernel does not fix this bug, please add the tag: > 'kernel-bug-exists-upstream'. > > Once testing of the upstream kernel is complete, please mark this bug as > "Confirmed". > > > Thanks in advance. > > [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc8 > > ** Changed in: linux (Ubuntu) >Importance: Undecided => Medium > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1785731 > > Title: > Linux Mint 19 > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > Last kernel update 4.15.0-30 > CPU1 idle after kernel update. > > System:Host: iw5dgq-K53SC Kernel: 4.15.0-30-generic x86_64 bits: 64 > gcc: 7.3.0 > Desktop: Cinnamon 3.8.8 (Gtk 3.22.30-1ubuntu1) dm: lightdm > Distro: Linux Mint 19 Tara > Machine: Device: laptop System: ASUSTeK product: K53SC v: 1.0 serial: > N/A > Mobo: ASUSTeK model: K53SC v: 1.0 serial: N/A > BIOS: American Megatrends v: K53SC.204 date: 05/30/2011 > BatteryBAT0: charge: 48.9 Wh 96.7% condition: 50.6/56.2 Wh (90%) > volts: 12.4/10.8 > model: [MKF_CUSTOMER] [MKF_BASEBOARD_ID] serial: N/A status: > N/A > CPU: Dual core Intel Core i5-2410M (-MT-MCP-) arch: Sandy Bridge > rev.7 cache: 3072 KB > flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: > 9179 > clock speeds: min/max: 800/2900 MHz 1: 2693 MHz 2: 2694 MHz > 3: 2693 MHz 4: 2694 MHz > Graphics: Card-1: Intel 2nd Generation Core Integrated Graphics > Controller > bus-ID: 00:02.0 chip-ID: 8086:0116 > Card-2: NVIDIA GF119M [GeForce GT 520MX] bus-ID: 01:00.0 > chip-ID: 10de:1051 > Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting > (unloaded: fbdev,vesa) > Resolution: 1366x768@60.00hz > OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile > version: 3.3 Mesa 18.0.5 (compat-v: 3.0) Direct Render: Yes > Audio: Card Intel 6 Series/C200 Series Family High Def. Audio > Controller > driver: snd_hda_intel bus-ID: 00:1b.0 chip-ID: 8086:1c20 > Sound: Advanced Linux Sound Architecture v: k4.15.0-30-generic > Network: Card-1: Qualcomm Atheros AR9285 Wireless Network Adapter > (PCI-Express) > driver: ath9k bus-ID: 03:00.0 chip-ID: 168c:002b > IF: wlp3s0 state: up mac: > Card-2: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet > Controller > driver: r8169 v: 2.3LK-NAPI port: 9000 bus-ID: 05:00.0 > chip-ID: 10ec:8168 > IF: enp5s0 state: down mac: > Drives:HDD Total Size: 240.1GB (17.9% used) > ID-1: /dev/sda model: KINGSTON_SV300S3 size: 240.1GB serial: > > Partition: ID-1: / size: 220G used: 41G (20%) fs: ext4 dev: /dev/sda1 > RAID: System: supported: N/A > No RAID devices: /proc/mdstat, md_mod kernel module present > Unused Devices: none > Sensors: System Temperatures: cpu: 84.0C mobo: N/A > Fan Speeds (in rpm): cpu: N/A > Repos: Active apt sources in file: > /etc/apt/sources.list.d/google-chrome.list > deb [arch=amd64] http: //dl.google.com/linux/chrome/deb/ > stable main > Active apt sources in file: > /etc/apt/sources.list.d/official-package-repositories.list > deb http: //mirrors.evowise.com/linuxmint/packages tara main > upstream import backport > deb http: //mirror.csclub.uwaterloo.ca/ubuntu bionic main > restricted universe multiverse > deb http: //mirror.csclub.uwaterloo.ca/ubuntu bionic-updates > main restricted universe multiverse > deb http: //mirror.csclub.uwaterloo.ca/ubuntu > bionic-backports main restricted universe multiverse > deb http: //security.ubuntu.com/ubuntu/ bionic-security main > restricted universe multiverse > deb http: //archive.canonical.com/ubuntu/ bionic partner > Info: Processes: 210 Uptime: 2:20 Memory: 1566.4/7885.5MB > Init: systemd v: 237 runlevel: 5 Gcc sys: 7.3.0 Client: > Unknown python3.6 client inxi: 2.3.56 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785731/+subscriptions > -- 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/1785731 Title: Linux Mint 19 Status in linux package in Ubuntu: Incomplete Bug description: Last ker
[Kernel-packages] [Bug 1785731] [NEW] Linux Mint 19
Public bug reported: Last kernel update 4.15.0-30 CPU1 idle after kernel update. System:Host: iw5dgq-K53SC Kernel: 4.15.0-30-generic x86_64 bits: 64 gcc: 7.3.0 Desktop: Cinnamon 3.8.8 (Gtk 3.22.30-1ubuntu1) dm: lightdm Distro: Linux Mint 19 Tara Machine: Device: laptop System: ASUSTeK product: K53SC v: 1.0 serial: N/A Mobo: ASUSTeK model: K53SC v: 1.0 serial: N/A BIOS: American Megatrends v: K53SC.204 date: 05/30/2011 BatteryBAT0: charge: 48.9 Wh 96.7% condition: 50.6/56.2 Wh (90%) volts: 12.4/10.8 model: [MKF_CUSTOMER] [MKF_BASEBOARD_ID] serial: N/A status: N/A CPU: Dual core Intel Core i5-2410M (-MT-MCP-) arch: Sandy Bridge rev.7 cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9179 clock speeds: min/max: 800/2900 MHz 1: 2693 MHz 2: 2694 MHz 3: 2693 MHz 4: 2694 MHz Graphics: Card-1: Intel 2nd Generation Core Integrated Graphics Controller bus-ID: 00:02.0 chip-ID: 8086:0116 Card-2: NVIDIA GF119M [GeForce GT 520MX] bus-ID: 01:00.0 chip-ID: 10de:1051 Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting (unloaded: fbdev,vesa) Resolution: 1366x768@60.00hz OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile version: 3.3 Mesa 18.0.5 (compat-v: 3.0) Direct Render: Yes Audio: Card Intel 6 Series/C200 Series Family High Def. Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0 chip-ID: 8086:1c20 Sound: Advanced Linux Sound Architecture v: k4.15.0-30-generic Network: Card-1: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) driver: ath9k bus-ID: 03:00.0 chip-ID: 168c:002b IF: wlp3s0 state: up mac: Card-2: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169 v: 2.3LK-NAPI port: 9000 bus-ID: 05:00.0 chip-ID: 10ec:8168 IF: enp5s0 state: down mac: Drives:HDD Total Size: 240.1GB (17.9% used) ID-1: /dev/sda model: KINGSTON_SV300S3 size: 240.1GB serial: Partition: ID-1: / size: 220G used: 41G (20%) fs: ext4 dev: /dev/sda1 RAID: System: supported: N/A No RAID devices: /proc/mdstat, md_mod kernel module present Unused Devices: none Sensors: System Temperatures: cpu: 84.0C mobo: N/A Fan Speeds (in rpm): cpu: N/A Repos: Active apt sources in file: /etc/apt/sources.list.d/google-chrome.list deb [arch=amd64] http: //dl.google.com/linux/chrome/deb/ stable main Active apt sources in file: /etc/apt/sources.list.d/official-package-repositories.list deb http: //mirrors.evowise.com/linuxmint/packages tara main upstream import backport deb http: //mirror.csclub.uwaterloo.ca/ubuntu bionic main restricted universe multiverse deb http: //mirror.csclub.uwaterloo.ca/ubuntu bionic-updates main restricted universe multiverse deb http: //mirror.csclub.uwaterloo.ca/ubuntu bionic-backports main restricted universe multiverse deb http: //security.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse deb http: //archive.canonical.com/ubuntu/ bionic partner Info: Processes: 210 Uptime: 2:20 Memory: 1566.4/7885.5MB Init: systemd v: 237 runlevel: 5 Gcc sys: 7.3.0 Client: Unknown python3.6 client inxi: 2.3.56 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bionic ** Attachment added: "sistem monitor." https://bugs.launchpad.net/bugs/1785731/+attachment/5172357/+files/Schermata%20del%202018-08-06%2021-07-31.png -- 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/1785731 Title: Linux Mint 19 Status in linux package in Ubuntu: Incomplete Bug description: Last kernel update 4.15.0-30 CPU1 idle after kernel update. System:Host: iw5dgq-K53SC Kernel: 4.15.0-30-generic x86_64 bits: 64 gcc: 7.3.0 Desktop: Cinnamon 3.8.8 (Gtk 3.22.30-1ubuntu1) dm: lightdm Distro: Linux Mint 19 Tara Machine: Device: laptop System: ASUSTeK product: K53SC v: 1.0 serial: N/A Mobo: ASUSTeK model: K53SC v: 1.0 serial: N/A BIOS: American Megatrends v: K53SC.204 date: 05/30/2011 BatteryBAT0: charge: 48.9 Wh 96.7% condition: 50.6/56.2 Wh (90%) volts: 12.4/10.8 model: [MKF_CUSTOMER] [MKF_BASEBOARD_ID] serial: N/A status: N/A CPU: Dual core Intel Core i5-2410M (-MT-MCP-) arch: Sandy Bridge rev.7 cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9179 clock speeds: min/max: 800/2900 MHz 1: 2693 MHz 2: 2694 MHz 3: 2693 MHz 4: 2694 MHz Graphics: Card-1: Intel 2nd Generation Core Integrated Graphics Controller bus-ID: 00:02.0 chip-ID: 8086:0116 Card-2: NVIDIA GF119M [GeForce GT 52
[Kernel-packages] [Bug 1510570] Re: BLE pairing fail
Hi Nahum Rozen (nahum), in Ubuntu 16.04Lts Desktop Edition that ppa doesn't work, it gves this error: W: The repository 'http://ppa.launchpad.net/guilhem-fr/bluez-autoenable/ubuntu xenial Release' does not have a Release file. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details. W: http://dl.google.com/linux/chrome/deb/dists/stable/Release.gpg: Signature by key 4CCA1EAF950CEE4AB83976DCA040830F7FAC5991 uses weak digest algorithm (SHA1) E: Failed to fetch http://ppa.launchpad.net/guilhem-fr/bluez-autoenable/ubuntu/dists/xenial/main/binary-amd64/Packages 404 Not Found [IP: 91.189.95.83 80] E: Failed to fetch http://ppa.launchpad.net/guilhem-fr/bluez-autoenable/ubuntu/dists/xenial/main/binary-i386/Packages 404 Not Found [IP: 91.189.95.83 80] E: Some index files failed to download. They have been ignored, or old ones used instead. any idea? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1510570 Title: BLE pairing fail Status in bluez package in Ubuntu: Confirmed Bug description: On 15.10 we now have bluez 5 so we can pair BLE devices like the Microsoft Arc Touch Bluetooth Mouse. But this pairing doesn't work very well. Mouse is seen but pairing fail. More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5 This is due to udev rule that use "hcitool" to power on device. Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used instead of udev rules. here is a commit with this parameter: http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138 And a ppa to test it: https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1510570/+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 1259829] Re: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name
Hello, yesterday I installed trusty on my Kingston 60GB SSD (Model=KINGSTON SV300S37A60G, FwRev=525ABBF0) After running the simple test with no error I added --no-model-check to /etc/cron.weekly/fstrim...so far so good -- 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/1259829 Title: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 Status in “linux” package in Ubuntu: Triaged Bug description: fs goes into read-only mode while building LibreOffice. WORKAROUND: Disable discard option - /dev/mapper/volumegroup-root/ ext4discard,noatime,nodiratime,errors=remount-ro01 disabling ncq has no effect. $ dmesg ... [ 2045.473249] virbr0: port 1(vnet0) entered forwarding state [ 2045.473283] IPv6: ADDRCONF(NETDEV_CHANGE): virbr0: link becomes ready [10660.961381] perf samples too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 5 [11822.935891] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 [11822.935896] Aborting journal on device dm-1-8. [11822.935998] EXT4-fs (dm-1): Remounting filesystem read-only [11822.960425] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629605: block 214443466: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2707156714, rec_len=19312, name_len=162 [11850.985003] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629557: block 214443458: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=512948573, rec_len=8858, name_len=176 [11850.985276] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629465: block 214443455: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=160939375, rec_len=26085, name_len=126 [11850.985499] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629325: block 214443451: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2322664969, rec_len=33791, name_len=132 [11850.985927] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629467: block 214443456: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=954332768, rec_len=21653, name_len=30 [11850.986409] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629074: block 214443433: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2061605548, rec_len=4984, name_len=3 [11850.986831] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53628835: block 214443432: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=3523041938, rec_len=53167, name_len=41 [11850.987001] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629098: block 214443436: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4225920287, rec_len=35138, name_len=75 [11850.987466] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629275: block 214443449: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=923253145, rec_len=44001, name_len=144 [11850.988115] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629270: block 214443448: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1892288796, rec_len=55247, name_len=58 [11851.042303] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629300: block 214443450: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=1809316884, rec_len=4208, name_len=195 [11851.042938] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629401: block 214443453: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4223616103, rec_len=36326, name_len=130 [11851.045745] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629406: block 214443454: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=415237227, rec_len=24702, name_len=59 [11851.125849] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629101: block 214443437: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=23292377, rec_len=28820, name_len=135 [11851.126086] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629543: block 214443457: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2624043515, rec_len=58633, name_len=250 [11851.126292] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629244: block 214443446: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=19483
Re: [Kernel-packages] [Bug 587136] Re: 2nd Resume from Suspend results in reboot on Toshiba Satellite U400. Fixed in 2.6.34 Mainline.
Hi, sorry, but I don't use that machine anymore. Riccardo On 29 September 2013 00:39, Christopher M. Penalver < christopher.m.penal...@gmail.com> wrote: > Riccardo Poli, this bug was reported a while ago and there hasn't been > any activity in it recently. We were wondering if this is still an > issue? If so, could you please test for this with the latest development > release of Ubuntu? ISO images are available from > http://cdimage.ubuntu.com/daily-live/current/ . > > If it remains an issue, could you please run the following command in > the development release from a Terminal > (Applications->Accessories->Terminal), as it will automatically gather > and attach updated debug information to this report: > > apport-collect -p linux > > Also, could you please test the latest upstream kernel available following > https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional > upstream developers to examine the issue. Please do not test the daily > kernel folder, but the one all the way at the bottom. Once you've tested > the upstream kernel, please comment on which kernel version specifically > you tested. If this bug is fixed in the mainline kernel, please add the > following tags: > kernel-fixed-upstream > kernel-fixed-upstream-VERSION-NUMBER > > where VERSION-NUMBER is the version number of the kernel you tested. For > example: > kernel-fixed-upstream-v3.12-rc2 > > This can be done by clicking on the yellow circle with a black pencil icon > next to the word Tags located at the bottom of the bug description. As > well, please remove the tag: > needs-upstream-testing > > If the mainline kernel does not fix this bug, please add the following > tags: > kernel-bug-exists-upstream > kernel-bug-exists-upstream-VERSION-NUMBER > > As well, please remove the tag: > needs-upstream-testing > > Once testing of the upstream kernel is complete, please mark this bug's > Status as Confirmed. Please let us know your results. Thank you for your > understanding. > > ** Changed in: linux (Ubuntu) >Status: Triaged => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/587136 > > Title: > 2nd Resume from Suspend results in reboot on Toshiba Satellite U400. > Fixed in 2.6.34 Mainline. > > Status in “linux” package in Ubuntu: > Incomplete > > Bug description: > 2.6.32-22: > Regardless of suspend method (lid-close, selecting "Suspend" in shutdown > menu, "pm-suspend" in a TTY), the laptop suspends correctly, resumes > correctly, suspends correctly a second time, and then once the second > resume is initiated, the system reboots. > > This issue is tested and confirmed as fixed in the 2.6.34 mainline > (2.6.34-020634-generic). > > ProblemType: Bug > DistroRelease: Ubuntu 10.04 > Package: xorg 1:7.5+5ubuntu1 > ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 > Uname: Linux 2.6.32-22-generic x86_64 > Architecture: amd64 > Date: Sat May 29 07:11:38 2010 > DkmsStatus: >vboxnetflt, 3.2.0, 2.6.32-22-generic, x86_64: installed >vboxnetadp, 3.2.0, 2.6.32-22-generic, x86_64: installed >vboxdrv, 3.2.0, 2.6.32-22-generic, x86_64: installed > MachineType: TOSHIBA Satellite U400 > ProcCmdLine: nomodeset pci=use_crs > root=UUID=4f3c9dfc-c762-423c-b1cd-81110c0b011d ro quiet splash > ProcEnviron: >PATH=(custom, user) >LANG=en_GB.utf8 >SHELL=/bin/bash > SourcePackage: xorg > Symptom: display > dmi.bios.date: 02/12/2009 > dmi.bios.vendor: TOSHIBA > dmi.bios.version: V3.30 > dmi.board.name: Satellite U400 > dmi.board.vendor: TOSHIBA > dmi.board.version: Not Applicable > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: TOSHIBA > dmi.chassis.version: N/A > dmi.modalias: > dmi:bvnTOSHIBA:bvrV3.30:bd02/12/2009:svnTOSHIBA:pnSatelliteU400:pvrPSU44E-00T017EN:rvnTOSHIBA:rnSatelliteU400:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: > dmi.product.name: Satellite U400 > dmi.product.version: PSU44E-00T017EN > dmi.sys.vendor: TOSHIBA > system: >distro: Ubuntu >codename: lucid >architecture: x86_64 >kernel: 2.6.32-22-generic > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/587136/+subscriptions > -- -- -- Prof Riccardo Poli E-mail: rp...@essex.ac.uk School of