[Kernel-packages] [Bug 1757202] Re: xubuntu / bionic / nvidia-driver-390 can only be used by one user at a time
Drat, I meant to add this too: Search keywords: linux mint switch user wrong resolution -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1757202 Title: xubuntu / bionic / nvidia-driver-390 can only be used by one user at a time Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: In XUbuntu 18.04 bionic, with the nvidia-driver-390, ony one user can use the nvidia driver at a time. A second user logged-in gets stuck at 640x480 and llvmpipe for OpenGL. Before the update around 11-12 March 2018, it was possible for multiple users to use the nvidia driver. First User == For the first user to log in, they get this: lsb_release -a: Distributor ID: Ubuntu Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 Codename: bionic apt-cache policy nvidia-driver-390: nvidia-driver-390: Installed: 390.42-0ubuntu1+gpu18.04.1 Candidate: 390.42-0ubuntu1+gpu18.04.1 Version table: *** 390.42-0ubuntu1+gpu18.04.1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 390.42-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages lscpi: 07:00.0 VGA compatible controller: NVIDIA Corporation GK106 [GeForce GTX 660] (rev a1) glxinfo | grep renderer: OpenGL renderer string: GeForce GTX 660/PCIe/SSE2 xrandr: Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384 DVI-I-0 disconnected (normal left inverted right x axis y axis) DVI-I-1 disconnected (normal left inverted right x axis y axis) HDMI-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 819mm x 461mm 1920x1080 60.00*+ 60.0059.9450.0023.9860.0050.04 1280x1024 75.02 1280x720 60.0059.9450.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.32 720x576 50.00 720x480 59.94 640x480 75.0059.9459.93 DP-0 disconnected (normal left inverted right x axis y axis) DVI-D-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) After switching to a second user glxinfo | grep renderer: OpenGL renderer string: llvmpipe (LLVM 5.0, 128 bits) xrandr: Screen 0: minimum 640 x 480, current 640 x 480, maximum 640 x 480 default connected 640x480+0+0 0mm x 0mm 640x480 73.00* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1757202/+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 1757202] Re: xubuntu / bionic / nvidia-driver-390 can only be used by one user at a time
I just had this problem on a Mint-19.3 XFCE upgraded from 18.3. For me, the fix was: * `sudo nvidia-xconfig` * `sudo vi /etc/X11/xorg.conf` The 'Section "Files"..EndSection' block already existed but was empty. I added this: Section "Files" ModulePath "/usr/lib/nvidia-340/xorg" ModulePath "/usr/lib/xorg/modules" EndSection * Then `sudo systemctl restart lightdm.service` which logged me out of my sessions! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1757202 Title: xubuntu / bionic / nvidia-driver-390 can only be used by one user at a time Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: In XUbuntu 18.04 bionic, with the nvidia-driver-390, ony one user can use the nvidia driver at a time. A second user logged-in gets stuck at 640x480 and llvmpipe for OpenGL. Before the update around 11-12 March 2018, it was possible for multiple users to use the nvidia driver. First User == For the first user to log in, they get this: lsb_release -a: Distributor ID: Ubuntu Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 Codename: bionic apt-cache policy nvidia-driver-390: nvidia-driver-390: Installed: 390.42-0ubuntu1+gpu18.04.1 Candidate: 390.42-0ubuntu1+gpu18.04.1 Version table: *** 390.42-0ubuntu1+gpu18.04.1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 390.42-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages lscpi: 07:00.0 VGA compatible controller: NVIDIA Corporation GK106 [GeForce GTX 660] (rev a1) glxinfo | grep renderer: OpenGL renderer string: GeForce GTX 660/PCIe/SSE2 xrandr: Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384 DVI-I-0 disconnected (normal left inverted right x axis y axis) DVI-I-1 disconnected (normal left inverted right x axis y axis) HDMI-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 819mm x 461mm 1920x1080 60.00*+ 60.0059.9450.0023.9860.0050.04 1280x1024 75.02 1280x720 60.0059.9450.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.32 720x576 50.00 720x480 59.94 640x480 75.0059.9459.93 DP-0 disconnected (normal left inverted right x axis y axis) DVI-D-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) After switching to a second user glxinfo | grep renderer: OpenGL renderer string: llvmpipe (LLVM 5.0, 128 bits) xrandr: Screen 0: minimum 640 x 480, current 640 x 480, maximum 640 x 480 default connected 640x480+0+0 0mm x 0mm 640x480 73.00* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1757202/+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 1798400] Re: [upstream] Regression: cannot use impress remote over bluetooth with ubuntu bionic
** Summary changed: - Regression: cannot use impress remote over bluetooth with ubuntu bionic + [upstream] Regression: cannot use impress remote over bluetooth with ubuntu bionic -- 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/1798400 Title: [upstream] Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: Confirmed Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+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 1841841] Re: disk stress test extremely slow progress after cpu offline/online
[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/1841841 Title: disk stress test extremely slow progress after cpu offline/online Status in linux package in Ubuntu: Expired Bug description: One of the test systems we use for testing snap updates is: Dell Inspiron 5759 Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz Advanced Micro Devices, Inc. [AMD/ATI] - 1002:6660, Intel - 8086:1916 We picked this one, some time ago from a pool of hardware to use for one of the test systems to test amd64/i386 snaps in beta. One of the tests in the test suite does some disk stress testing using: bonnie++ -d /var/lib/snapd/hostfs/writable -u root -r 8000 Looking back through our results, I see that it has often taken from 20-40 min. to complete the test, and sometimes hit our timeout threshold. More recently, it seems to always just timeout, but as far back as our history goes with testing on this platform, it's always seemed bad to some extent. I tried the exact same test on another similar system, and it completed in only 11min. so we suspected a bad disk. After replacing the disk with a new one, it still has the same problem. We only see this problem on the core18 i386 images though, not on core16, and not on core18-amd64. Looking into it some more, I discovered that it was easily reproducible outside the test suite, but *only* if I tried running it after the full test suite without rebooting. If I reboot the system, and run the bonnie++ command above without the rest of the tests, it completes in about 13 min. I divided up the other tests and narrowed it down to a cpu offlining test - when that test runs, followed by this disk stress test, that's when it gets so horribly slow. This was all done using checkbox-snappy as the test suite, but if you have another way to get bonnie++ on here, it can be reproduced without it (or you can use bonnie++ from checkbox-snappy easily by doing 'sudo /snap/bin/checkbox-snappy.shell') Here's the basic instructions to reproduce (on core18-i386): $ sudo bash -c "echo 0 > /sys/devices/system/cpu/cpu1/online" $ sudo bash -c "echo 0 > /sys/devices/system/cpu/cpu2/online" $ sudo bash -c "echo 0 > /sys/devices/system/cpu/cpu3/online" $ sudo bash -c "echo 1 > /sys/devices/system/cpu/cpu1/online" $ sudo bash -c "echo 1 > /sys/devices/system/cpu/cpu2/online" $ sudo bash -c "echo 1 > /sys/devices/system/cpu/cpu3/online" $ sudo /snap/bin/checkbox-snappy.shell # bonnie++ -d /var/lib/snapd/hostfs/writable -u root -r 8000 Nothing particularly interesting in dmesg during all of this other than the NOHZ messages during cpu offline: [ 189.085026] smpboot: CPU 1 is now offline [ 199.371529] smpboot: CPU 2 is now offline [ 203.291835] NOHZ: local_softirq_pending 282 [ 203.293167] NOHZ: local_softirq_pending 282 [ 203.294581] smpboot: CPU 3 is now offline [ 247.521569] x86: Booting SMP configuration: [ 247.521576] smpboot: Booting Node 0 Processor 1 APIC 0x2 [ 247.522892] Initializing CPU#1 [ 252.127965] smpboot: Booting Node 0 Processor 2 APIC 0x1 [ 252.129533] Initializing CPU#2 [ 255.632004] smpboot: Booting Node 0 Processor 3 APIC 0x3 [ 255.633565] Initializing CPU#3 History I have for the past few kernels: 4.15.0-52.56-226 - passed - 41m 4.15.0-54.58-241 - passed - 36m 4.15.0-55.60-246 - passed after some timeouts/retries, took 41m though 4.15.0-55.60-253 - passed in 20min 4.15.0-56.62-263 - fails - seems to take much much longer from this point on *These results were from that test as part of the full test run, including the cpu offlining test. When the test is run by itself on the same system, it takes only around 13min To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841841/+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 1849927] Re: Installation failed when choose iommu in VMware Player
[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/1849927 Title: Installation failed when choose iommu in VMware Player Status in linux package in Ubuntu: Expired Bug description: Host OS: Windows 10 VMware Workstation Player version: 15.5.0 build-14665864 Virtualization engine: Virtualize IOMMU (IO memory managment unit) Virtual OS: Ubuntu 19.10 Step: 1. Choose Virtualize IOMMU in virtualization engine of VMware 2. Boot the virtual machine 3. Stuck on Boot Animation And the log shows as the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849927/+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 1834771] Re: No HDMI-audio after kernel 4.15.-0.50
I can confirm that this script also works for me using an ATI/Radeon RS780 HDMI, after adjusting the GREP line appropriately. Thank you :-) One other thing: in order to make it work reliably as a "Startup application", I had to change the "sleep 2" to "sleep 10". Presumably this is because the system is busy starting stuff just after login. -- 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/1834771 Title: No HDMI-audio after kernel 4.15.-0.50 Status in linux package in Ubuntu: Confirmed Bug description: I've got no HDMI-audio. Latest kernel with working HDMI-audio is 4.15.-0.50. In pavucontrol HDMI-audio shows unplugged. And also internal audio shows unplugged, but it still works. I'm on linux mint 18.3. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jouni 1859 F pulseaudio /dev/snd/controlC1: jouni 1859 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=9e8d7bf3-dc5f-4c72-b875-6dbe81a36c36 InstallationDate: Installed on 2017-01-28 (883 days ago) InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=f167a2b0-3b30-4a5a-907f-6b97c95b7a91 ro quiet iommu=soft splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-54.58~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-54-generic N/A linux-backports-modules-4.15.0-54-generic N/A linux-firmware 1.157.21 RfKill: Tags: sylvia Uname: Linux 4.15.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 02/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/26/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771/+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 1847937] Re: 'gpu has fallen off the bus' after return from suspend
Unfortunately upon investigation of the fix Andrés mentioned in #18, I found that my system (Eoan, 5.3.0-24, Lenovo W540) was already configured for deep and not s2idle and is still affected by the 'gpu has fallen off the bus' issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1847937 Title: 'gpu has fallen off the bus' after return from suspend Status in linux package in Ubuntu: Triaged Bug description: With this message the only way to resume work is to reboot the system using power button. With kernel linux-image-5.3.0-13-generic everything is OK. Problem appeared afer upgrade to linux-image-5.3.0-17-generic and still happens in linux-image-5.3.0-18-generic. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: player 4451 F pulseaudio /dev/snd/controlC1: player 4451 F pulseaudio /dev/snd/controlC0: player 4451 F pulseaudio CurrentDesktop: KDE Date: Mon Oct 14 01:27:04 2019 HibernationDevice: RESUME=UUID=a58bb700-5818-4ca6-8351-fd4e5e28ea9e MachineType: LENOVO 20BG0016US ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=d0c33b75-6f04-4d53-bc3b-91924e3bcf91 ro quiet splash vga=current loglevel=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-13-generic N/A linux-backports-modules-5.3.0-13-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-08 (5 days ago) WifiSyslog: dmi.bios.date: 05/30/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GNET88WW (2.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BG0016US dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET88WW(2.36):bd05/30/2018:svnLENOVO:pn20BG0016US:pvrThinkPadW540:rvnLENOVO:rn20BG0016US:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W540 dmi.product.name: 20BG0016US dmi.product.sku: LENOVO_MT_20BG dmi.product.version: ThinkPad W540 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847937/+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 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic
@albertpool - it only impacts (as reported) 16.04 LTS WHEN using the 18.04/HWE kernel. To my knowledge there are no reports of it impacting xenial users using 16.04's 4.4 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/1854798 Title: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: SRU justification = [Impact] Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic [Fix] After applied commit "Input: synaptics-rmi4 - avoid processing unknown IRQs", no irq response from touchpad. This commit is depended on commit: "Input: synaptics-rmi4 - convert irq distribution to irq_domain" [Test] Verified on hardware, tests results are good. [Regression Potential] Low. Fix bug that introduced by stable release update. 2nd and 3rd patches are fixes for the 1st patch. These commits are already included by eoan kernel, so bionic 4.15 only. Original reports === environment: Dell Laptop XPS-9333 Device: # xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SYNAPTICS Synaptics Large Touch Screen id=9[slave pointer (2)] ⎜ ↳ Synaptics s3203 id=12 [slave pointer (2)] ⎜ ↳ Ultrathin Touch Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Dell WMI hotkeysid=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=14 [slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=10 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] # xinput --list-props 12 Device 'Synaptics s3203': Device Enabled (142):1 Coordinate Transformation Matrix (144): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (270): 1 Device Accel Constant Deceleration (271):2.50 Device Accel Adaptive Deceleration (272):1.00 Device Accel Velocity Scaling (273): 9.712231 Synaptics Edges (304): 162, 3908, 133, 2339 Synaptics Finger (305): 25, 30, 0 Synaptics Tap Time (306):180 Synaptics Tap Move (307):209 Synaptics Tap Durations (308): 180, 180, 100 Synaptics ClickPad (309):1 Synaptics Middle Button Timeout (310): 0 Synaptics Two-Finger Pressure (311): 282 Synaptics Two-Finger Width (312):7 Synaptics Scrolling Distance (313): -95, 95 Synaptics Edge Scrolling (314): 0, 0, 0 Synaptics Two-Finger Scrolling (315):1, 1 Synaptics Move Speed (316): 1.00, 1.75, 0.042008, 0.00 Synaptics Off (317): 0 Synaptics Locked Drags (318):0 Synaptics Locked Drags Timeout (319):5000 Synaptics Tap Action (320): 0, 0, 0, 0, 1, 3, 2 Synaptics Click Action (321):1, 3, 2 Synaptics Circular Scrolling (322): 0 Synaptics Circular Scrolling Distance (323): 0.10 Synaptics Circular Scrolling Trigger (324): 0 Synaptics Circular Pad (325):0 Synaptics Palm Detection (326): 1 Synaptics Palm Dimensions (327): 10, 200 Synaptics Coasting Speed (328): 20.00, 50.00 Synaptics Pressure Motion (329): 30, 160 Synaptics Pressure Motion Factor (330): 1.00, 1.00 Synaptics Resolution Detect (331): 1 Synaptics Grab Event Device (332): 0 Synaptics Gestures (333):1 Synaptics Capabilities (334):1, 0, 0, 1, 1, 1, 0 Synaptics Pad Resolution (335): 42, 42 Synaptics Area (336):0, 0, 0, 0 Synaptics Soft Button Areas (337): 0, 0, 0, 0, 0, 0, 0, 0 Synaptics Noise Cancellation (338): 23, 23 Device Product ID (262): 1739, 10036 Device Node (263): "/dev/input/event5" # lspci 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 09)
[Kernel-packages] [Bug 1857178] Re: GPU hang
Hi. I can confirm that the hang issue seems to be solved with this newer kernel. However, there are at least two issues I could detect that were not a problem before: 1) Audio drivers are not recognized and I get the "Dummy audio" output. I've reinstalling pulse in several ways, but the problem remains. 2) Certain programs like GIMP fail to lunch. In particular, the error I get is: >> cannot self-bind mount /run/snapd/ns: Cannot allocate memory Finally, I get an error message right after the kernel is loaded. I am sending a picture attached. Sorry for the quality, but the duration is very brief and I have not been able to find it printed in some log file. Also, sometimes I get messages when shutting down the machine, but those are to quick for me to read. In case you or someone has any advice they would be much appreciated. Thank you again for your help. ** Attachment added: "IMG_20191227_184426.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857178/+attachment/5315943/+files/IMG_20191227_184426.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857178 Title: GPU hang Status in linux package in Ubuntu: Confirmed Bug description: System randomly hangs for 5-15 seconds. It has been occurring for about a week. Please let me know if there is any further information that can be of use. Thank you in advance for your help. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sebjr 1357 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Dec 20 17:40:03 2019 InstallationDate: Installed on 2019-12-05 (15 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20Q0002EUS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=dc41f3d8-af4c-4d77-965f-c77f918ac63e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2JET73W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q0002EUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2JET73W(1.51):bd07/18/2019:svnLENOVO:pn20Q0002EUS:pvrThinkPadX390:rvnLENOVO:rn20Q0002EUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X390 dmi.product.name: 20Q0002EUS dmi.product.sku: LENOVO_MT_20Q0_BU_Think_FM_ThinkPad X390 dmi.product.version: ThinkPad X390 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857178/+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 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic
Can someone with the right permissions mark at the top that the bug equally affects Xenial? -- 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/1854798 Title: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: SRU justification = [Impact] Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic [Fix] After applied commit "Input: synaptics-rmi4 - avoid processing unknown IRQs", no irq response from touchpad. This commit is depended on commit: "Input: synaptics-rmi4 - convert irq distribution to irq_domain" [Test] Verified on hardware, tests results are good. [Regression Potential] Low. Fix bug that introduced by stable release update. 2nd and 3rd patches are fixes for the 1st patch. These commits are already included by eoan kernel, so bionic 4.15 only. Original reports === environment: Dell Laptop XPS-9333 Device: # xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SYNAPTICS Synaptics Large Touch Screen id=9[slave pointer (2)] ⎜ ↳ Synaptics s3203 id=12 [slave pointer (2)] ⎜ ↳ Ultrathin Touch Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Dell WMI hotkeysid=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=14 [slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=10 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] # xinput --list-props 12 Device 'Synaptics s3203': Device Enabled (142):1 Coordinate Transformation Matrix (144): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (270): 1 Device Accel Constant Deceleration (271):2.50 Device Accel Adaptive Deceleration (272):1.00 Device Accel Velocity Scaling (273): 9.712231 Synaptics Edges (304): 162, 3908, 133, 2339 Synaptics Finger (305): 25, 30, 0 Synaptics Tap Time (306):180 Synaptics Tap Move (307):209 Synaptics Tap Durations (308): 180, 180, 100 Synaptics ClickPad (309):1 Synaptics Middle Button Timeout (310): 0 Synaptics Two-Finger Pressure (311): 282 Synaptics Two-Finger Width (312):7 Synaptics Scrolling Distance (313): -95, 95 Synaptics Edge Scrolling (314): 0, 0, 0 Synaptics Two-Finger Scrolling (315):1, 1 Synaptics Move Speed (316): 1.00, 1.75, 0.042008, 0.00 Synaptics Off (317): 0 Synaptics Locked Drags (318):0 Synaptics Locked Drags Timeout (319):5000 Synaptics Tap Action (320): 0, 0, 0, 0, 1, 3, 2 Synaptics Click Action (321):1, 3, 2 Synaptics Circular Scrolling (322): 0 Synaptics Circular Scrolling Distance (323): 0.10 Synaptics Circular Scrolling Trigger (324): 0 Synaptics Circular Pad (325):0 Synaptics Palm Detection (326): 1 Synaptics Palm Dimensions (327): 10, 200 Synaptics Coasting Speed (328): 20.00, 50.00 Synaptics Pressure Motion (329): 30, 160 Synaptics Pressure Motion Factor (330): 1.00, 1.00 Synaptics Resolution Detect (331): 1 Synaptics Grab Event Device (332): 0 Synaptics Gestures (333):1 Synaptics Capabilities (334):1, 0, 0, 1, 1, 1, 0 Synaptics Pad Resolution (335): 42, 42 Synaptics Area (336):0, 0, 0, 0 Synaptics Soft Button Areas (337): 0, 0, 0, 0, 0, 0, 0, 0 Synaptics Noise Cancellation (338): 23, 23 Device Product ID (262): 1739, 10036 Device Node (263): "/dev/input/event5" # lspci 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 09) 00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04) 00:16.0
[Kernel-packages] [Bug 1857398] Re: ubiquity should support encryption by default with zfsroot, with users able to opt in to running change-key after install
I put these questions to Tom Caputi, who wrote the ZFS encryption. The quoted text below is what I asked him, and the unquoted text is his response: > 1. Does ZFS rewrite the wrapped/encrypted master key in place? If >not, the old master key could be retrieved off disk, decrypted >with the known passphrase, and used to decrypt at least >_existing_ data. 1) No. This is definitely an attack vector (although a very minor one). At the time we had said that we would revisit the idea of overwriting old keys when TRIM was added. That was several years ago and TRIM is now in. I will talk to Brian about it after I am back from the holiday. > 2. Does a "zfs change-key" create a new master key? If not, the old >master key could be used to decrypt _new_ data as well, at least >until the master key is rotated. 2) zfs change-key does not create a new master key. It simply re-wraps the existing master key. The master keys are never rotated. The key rotation is done by using the master keys to generate new keys. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1857398 Title: ubiquity should support encryption by default with zfsroot, with users able to opt in to running change-key after install Status in ubiquity package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Bug description: zfs supports built-in encryption support, but the decision of whether a pool is encrypted or not must be made at pool creation time; it is possible to add encrypted datasets on top of an unencrypted pool but it is not possible to do an online change of a dataset (or a whole pool) to toggle encryption. We should therefore always install with encryption enabled on zfs systems, with a non-secret key by default, and allow the user to use 'zfs change-key -o keylocation=prompt' after install to take ownership of the encryption and upgrade the security. This is also the simplest way to allow users to avoid having to choose between the security of full-disk encryption, and the advanced filesystem features of zfs since it requires no additional UX work in ubiquity. We should make sure that https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857040 is fixed first in the kernel so that enabling zfs encryption does not impose an unreasonable performance penalty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1857398/+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 1851340] Re: [mgag200] Ubuntu 19.10 upgrade results in invisible mouse cursor on Matrox G200eR2
Hi Po-Hsu Lin, for for building update of 5.3 I have installed and verified that cursor is working on both console and remote. $ cat /etc/*-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=19.10 DISTRIB_CODENAME=eoan DISTRIB_DESCRIPTION="Ubuntu 19.10" NAME="Ubuntu" VERSION="19.10 (Eoan Ermine)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 19.10" VERSION_ID="19.10" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=eoan UBUNTU_CODENAME=eoan $ uname -a Linux green 5.3.0-26-generic #28 SMP Fri Dec 27 06:29:53 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Regards, John. -- 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/1851340 Title: [mgag200] Ubuntu 19.10 upgrade results in invisible mouse cursor on Matrox G200eR2 Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Confirmed Bug description: Following in place upgrade of Ubuntu 19.04 -> 19.10 I no longer have visible cursor with my Gnone desktop. I have found the same problem when upgrading 2 machines from Ubuntu 19.04 -> 19.10. Reproducing problem is easy: 1. Open Ubuntu Update Window 2. Select "Upgrade" 3. On completion of update (after reboot) cursor is no longer visible. 4. This applies to display connected to VGA port on host with USB Keyboard + Mouse While the connected display has no visible cursor and so is usable, I have always used X11VNC Server to provide network GUI access. On the remote X11VNC display I see and can use the cursor. This bug report is being sent via Remote X11VNC window, as I cannot use the main VGA display window (due to lack of visible cursor) I have done search online and thought that maybe issue was with my USB Mighty Mouse, so I also tried with Logitech M100R USB Mouse. Same result, no visible mouse cursor. I have done: "grep usb /var/log/syslog" and can see many USB events, including both Apple and Logitech mouse detection events. NOTE: Due to compatibility issue with X11VNC, I have disable Wayland on both machines by adding the following option to: /etc/gdm3/custom.conf WaylandEnable=false Regards, John Hartley. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 5 18:25:23 2019 DistUpgraded: 2019-11-05 15:20:04,402 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu GraphicsCard: Matrox Electronics Systems Ltd. G200eR2 [102b:0534] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo G200eR2 [1d49:0a01] InstallationDate: Installed on 2018-12-17 (322 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO System x3650 M5: -[8871AC1]- ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=3b8f415b-7e78-461c-83df-64f1f1a7826a ro ipv6.disable=1 quiet splash iommu=1 intel_iommu=on ipv6.disable=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-11-05 (0 days ago) dmi.bios.date: 06/03/2019 dmi.bios.vendor: LENOVO dmi.bios.version: -[TCE140H-2.91]- dmi.board.asset.tag: (none) dmi.board.name: 01KN179 dmi.board.vendor: LENOVO dmi.board.version: NULL dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: LENOVO dmi.chassis.version: none dmi.modalias: dmi:bvnLENOVO:bvr-[TCE140H-2.91]-:bd06/03/2019:svnLENOVO:pnSystemx3650M5-[8871AC1]-:pvr13:rvnLENOVO:rn01KN179:rvrNULL:cvnLENOVO:ct23:cvrnone: dmi.product.family: System X dmi.product.name: System x3650 M5: -[8871AC1]- dmi.product.sku: (none) dmi.product.version: 13 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1857616] Re: Cannot collect dump due to "Can't get a valid pmd_pte" error
This proved not to be the case; in fact, the issue was caused by a
change in kernel that changed a bit and hence, the vmcore collection
failed.
The culprit was kernel commit 326e1b8f83a4 ("mm/sparsemem: introduce a
SECTION_IS_EARLY flag"), introduced in kernel 5.3.
The makedumpfile fix for this comes in commit 7bdb468c2c ("Increase
SECTION_MAP_LAST_BIT to 4").
The PPA launchpad.net/~gpiccoli/+archive/ubuntu/lp1857616 contains a build with
this fix for testing purposes.
Cheers,
Guilherme
** Also affects: makedumpfile (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: makedumpfile (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: makedumpfile (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: makedumpfile (Ubuntu Focal)
Importance: High
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Confirmed
** Also affects: makedumpfile (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: makedumpfile (Ubuntu Xenial)
Status: New => Invalid
** Changed in: makedumpfile (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: makedumpfile (Ubuntu Disco)
Status: New => Invalid
--
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/1857616
Title:
Cannot collect dump due to "Can't get a valid pmd_pte" error
Status in makedumpfile package in Ubuntu:
Confirmed
Status in makedumpfile source package in Xenial:
Invalid
Status in makedumpfile source package in Bionic:
Confirmed
Status in makedumpfile source package in Disco:
Invalid
Status in makedumpfile source package in Eoan:
New
Status in makedumpfile source package in Focal:
Confirmed
Bug description:
Due to an issue in the kaslr address resolution in makedumpfile, we
may get the following error when collecting a dump:
Excluding unnecessary pages : [ 46.3 %] / __vtop4_x86_64[ 39.341233]: Can't
get a valid pmd_pte.
readmem: Can't convert a virtual address(e05cb400) to physical
address.
readmem: type_addr: 0, addr:e05cb400, size:32768
__exclude_unnecessary_pages: Can't read the buffer of struct page.
create_2nd_bitmap: Can't exclude unnecessary pages.
This is believed to be fixed by commit: 3222d4ad04c6 ("x86_64: fix
get_kaslr_offset_x86_64() to return kaslr_offset correctly"). This LP
keeps track of Test/SRU for this commit.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1857616/+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 1270676] Re: SD Card Reader broken on UX302LG
@Alexey that's because you have AU9540, according to another post of yours. The driver having been mainlined only supports 6601 and 6621 instead for the time being. I also know 6625 exists. -- 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/1270676 Title: SD Card Reader broken on UX302LG Status in linux package in Ubuntu: Triaged Bug description: SD card reader (controller Alcor Micro AU6601) is dysfunctional in UX302LG laptop. USB readers work without problem. Nothing happens when pluggin SD/mSD/SDHC/mSDHC cards in the reader (might as well use a piece of wood). Nothing is listed in lsusb -v that could be the reader. Nohting is listed in lspci -k -vv -nnn. Nothing in acpi_listen. Nothing in kern.log etc. According to (select "Windows 8" then "Card Reader") : http://support.asus.com/download.aspx?SLanguage=en=3=597=UX302LG==GEZaY8oaj8oSlQ3U Reader vendor is : Alcor Multi-Card Reader Driver http://www.pcidatabase.com/vendor_details.php?id=1672 There is only one device that is "Unassigned class" 1aea:6601 but searching this online only pops up my other bug reports (sigh) and vendor is unassigned on pcidatabase.com. But...Downloading the 14M Win driver for the reader, vendor id 1aea and device id 6601 is present at multiple instances : [DeviceList.NTamd64] ; For XP and later %AMPCIECR% = DriverInstall_6601, PCI\VEN_1aea_6601 Also there is mention of _Gen instance in the .inf, might point to a "Generic" alternative ? [DeviceList_Gen.NTamd64] ; For XP and later %AMPCIECR_GEN% = DriverInstall_Gen, PCI\VEN_105b_0ef6 This does point to something totally different online 105b:0ef6 points to some Realtek HD Audio device. A proposed patch was submitted upstream as per: http://www.spinics.net/lists/linux-mmc/msg29230.html --- ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=e6458b44-fdb9-4db5-8cac-40ee0bbf9cf6 InstallationDate: Installed on 2013-12-31 (21 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131231) MachineType: ASUSTeK COMPUTER INC. UX302LG Package: linux (not installed) ProcFB: 0 simple ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-4-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi= nomodeset plymouth:debug vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 RelatedPackageVersions: linux-restricted-modules-3.13.0-4-generic N/A linux-backports-modules-3.13.0-4-generic N/A linux-firmware1.121 Tags: trusty Uname: Linux 3.13.0-4-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 10/30/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX302LG.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX302LG 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.:bvrUX302LG.207:bd10/30/2013:svnASUSTeKCOMPUTERINC.:pnUX302LG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX302LG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX302LG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270676/+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 1857706] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857706 Title: Bluetooth is not working Status in linux package in Ubuntu: Confirmed Bug description: Unable to turn on bluetooth or connect to any bluetooth devices. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: satish 1181 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Dec 27 22:02:19 2019 InstallationDate: Installed on 2019-12-26 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN Adapter Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15q-ds0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=af9acdc4-5e0c-4043-bd77-5cdf6eba0e1f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A6 dmi.board.vendor: HP dmi.board.version: 80.43 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.22:bd08/28/2019:svnHP:pnHPLaptop15q-ds0xxx:pvrType1ProductConfigId:rvnHP:rn84A6:rvr80.43:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15q-ds0xxx dmi.product.sku: 4ZD80PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857706/+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 1857706] [NEW] Bluetooth is not working
Public bug reported: Unable to turn on bluetooth or connect to any bluetooth devices. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: satish 1181 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Dec 27 22:02:19 2019 InstallationDate: Installed on 2019-12-26 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN Adapter Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15q-ds0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=af9acdc4-5e0c-4043-bd77-5cdf6eba0e1f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A6 dmi.board.vendor: HP dmi.board.version: 80.43 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.22:bd08/28/2019:svnHP:pnHPLaptop15q-ds0xxx:pvrType1ProductConfigId:rvnHP:rn84A6:rvr80.43:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15q-ds0xxx dmi.product.sku: 4ZD80PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857706 Title: Bluetooth is not working Status in linux package in Ubuntu: New Bug description: Unable to turn on bluetooth or connect to any bluetooth devices. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: satish 1181 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Dec 27 22:02:19 2019 InstallationDate: Installed on 2019-12-26 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN Adapter Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15q-ds0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=af9acdc4-5e0c-4043-bd77-5cdf6eba0e1f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A6 dmi.board.vendor: HP dmi.board.version: 80.43 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.22:bd08/28/2019:svnHP:pnHPLaptop15q-ds0xxx:pvrType1ProductConfigId:rvnHP:rn84A6:rvr80.43:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15q-ds0xxx dmi.product.sku: 4ZD80PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857706/+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 1823076] Re: System wakes up immediately after suspend if Bluetooth is still enabled
Please power off your laptop completely and power it on again after 1 minute. Paste dmesg log since boot and your linux-firmware version, then we may know which file to fix. smartman <1823...@bugs.launchpad.net> 於 2019年12月27日 週五 00:55 寫道： > I am having this issue also. Turning off bluetooth with bluez (Bluetooth > Manager) applet icon and manually stopping bluetooth service the suspend > works. Otherwise I have seen suspends but usually just wakes up in a few > seconds. Lenovo P53 with Ubuntu 19.10 and kernel 5.3.0-24-generic > > -- > You received this bug notification because you are subscribed to linux > in Ubuntu. > https://bugs.launchpad.net/bugs/1823076 > > Title: > System wakes up immediately after suspend if Bluetooth is still > enabled > > Status in bluez package in Ubuntu: > Confirmed > Status in linux package in Ubuntu: > Confirmed > > Bug description: > After replacing my USB mouse with a BT mouse, I noticed my machine > would no longer suspend without immediately waking up. i.e. I suspend > and see the light go into the slow fade in and out for one cycle and > then goes solid and the display wakes up again. If I disable BT (via > blueman applet) suspend works fine. > > I've fixed this by shutting down the BT service before suspend, and > starting it back up on wake, as indicated here: > https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately- > after-suspend > > Perhaps this script should be included in blueZ as suspend issues seem > very hard to debug and the immediate wake after suspend could be > caused many any number of things. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: bluez 5.48-0ubuntu3.1 [modified: > lib/systemd/system/bluetooth.service] > ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 > Uname: Linux 4.15.0-46-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.6 > Architecture: amd64 > CurrentDesktop: XFCE > Date: Wed Apr 3 13:16:14 2019 > InstallationDate: Installed on 2019-02-09 (53 days ago) > InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 > (20180725) > InterestingModules: rfcomm bnep btusb bluetooth > MachineType: Intel(R) Client Systems NUC8i3BEH > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic > root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=1 > SourcePackage: bluez > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 10/15/2018 > dmi.bios.vendor: Intel Corp. > dmi.bios.version: BECFL357.86A.0051.2018.1015.1513 > dmi.board.name: NUC8BEB > dmi.board.vendor: Intel Corporation > dmi.board.version: J72693-304 > dmi.chassis.type: 3 > dmi.chassis.vendor: Intel Corporation > dmi.chassis.version: 2.0 > dmi.modalias: > dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: > dmi.product.family: Intel NUC > dmi.product.name: NUC8i3BEH > dmi.product.version: J72753-303 > dmi.sys.vendor: Intel(R) Client Systems > hciconfig: >hci0:Type: Primary Bus: USB > BD Address: 00:BB:60:50:92:5D ACL MTU: 1021:4 SCO MTU: 96:6 > UP RUNNING > RX bytes:1912660 acl:106009 sco:0 events:337 errors:0 > TX bytes:12331 acl:74 sco:0 commands:204 errors:0 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1823076/+subscriptions > -- 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/1823076 Title: System wakes up immediately after suspend if Bluetooth is still enabled Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After replacing my USB mouse with a BT mouse, I noticed my machine would no longer suspend without immediately waking up. i.e. I suspend and see the light go into the slow fade in and out for one cycle and then goes solid and the display wakes up again. If I disable BT (via blueman applet) suspend works fine. I've fixed this by shutting down the BT service before suspend, and starting it back up on wake, as indicated here: https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately- after-suspend Perhaps this script should be included in blueZ as suspend issues seem very hard to debug and the immediate wake after suspend could be caused many any number of things. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Apr 3 13:16:14 2019 InstallationDate: Installed on
[Kernel-packages] [Bug 1833281]
(In reply to ValdikSS from comment #58) > I have an idea why this bug is much worse with BTRFS than with EXT4: BTRFS > has much bigger read/write amplification, up to 10x higher than EXT4. You mean that when e.g. Chromium browser writes its cache, it loads IO "up to 10x higher than EXT4", and, when IO is also loaded by swapping, it causes microfreezes? Are you sure that operations that cause write amplifications are not done in background? -- 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/1833281 Title: System freeze when memory is put on SWAP in Linux >4.10.x Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I'm reporting this since it's reproduceable the 70% of the time. Summary: In different circumstances, when the systems starts to swap out RAM memory, even small amounts, the system becomes completely unusuable and the screen freezes up, no mouse movement, no TTY access or SSH access can be made, only SYSRQ keys seem to do something (only reboot, so REISUB worked so far though, OOM is useless since the memory/swap is not even full) The I/O Disk led is stuck to 100% in ALL the following cases when this happens. So far: - This happens even when only ZRAM is enabled, and no swap partition is used. - Happens when ZSWAP is used with a swap partition - Happens also when a partition without zram or zswap is used - Maybe it's AMD specific? However, I'm not experiencing this on my laptop using the same tests. My laptop is an Intel one, while my desktop is an AMD Ryzen platform. Here are the specs: CPU: AMD Ryzen 5 1600 no OC GPU: AMD RX 580 8GB SSD: Crucial MX500 500GB MOBO: MSI B350M Grenade RAM: 8GB HyperX Kingston 2667Mhz Ubuntu version: 18.04 LTS, backports repo enabled Kernel version: 4.18.0-18, official ubuntu repo Bios settings: Default Additional info: Maybe I'm not 100% sure, but I noticed when using the 5.0.0-17 generic kernel, the lockups seem to still happen, but they recover eventually. Happened only a few times though... But will always be frozen for at least 30 seconds, differently from my intel laptop where those do occur. The SSD make is the same. I bought two of these, they got also the same amount of RAM. In my laptop those do not occur at all. Swapping memory even huge quantities like 1GB or more, do not produce any issues. Tests made: For testing this behaviour I tried: - Compiling the chromium-browser source code (takes up a lot of system RAM) - Used the "stress" command, using a specific amount of memory to decide how many it will be swapped, and here I noticed that even small quantities like a couple of megabytes will cause the system to freeze the 70% of the times Example: "stress --vm 1 --vm-bytes=7G" What should happen: I expect system slowdowns when swapping out memory since I do not have enough RAM, but unlikely when using Windows or my laptop with the same Linux version, not a completely unusuable environment. The swap partition is in both cases on an SSD. Reproduceability: 70% of the times Additional info again: I'm not sure this is due to any hardware failure, my SSD health is fine, as my CPU and RAM. As I said swapping in Windows works fine... --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: haru 2076 F pulseaudio /dev/snd/controlC2: haru 2076 F pulseaudio /dev/snd/controlC0: haru 2076 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: enp24s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-17-generic root=UUID=75d45574-7169-4653-aea3-9f95087f0806 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-17-generic N/A linux-backports-modules-5.0.0-17-generic N/A linux-firmware1.173.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo video WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.K0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR (MS-7A37) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4
[Kernel-packages] [Bug 1833281]
(In reply to Mikhail Novosyolov from comment #59) > You mean that when e.g. Chromium browser writes its cache, it loads IO "up > to 10x higher than EXT4" Yes. This is also true for read operations, not only for write. > and, when IO is also loaded by swapping, it causes > microfreezes? Yes, probably > Are you sure that operations that cause write amplifications > are not done in background? I'm not sure, but people on Rosa forum blamed BTRFS for this bug. I'm pretty sure it's not directly tight with BTRFS, but write and read amplification may explain why lags are more severe with this FS. Check https://arxiv.org/pdf/1707.08514.pdf and https://habr.com/ru/post/476414/ -- 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/1833281 Title: System freeze when memory is put on SWAP in Linux >4.10.x Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I'm reporting this since it's reproduceable the 70% of the time. Summary: In different circumstances, when the systems starts to swap out RAM memory, even small amounts, the system becomes completely unusuable and the screen freezes up, no mouse movement, no TTY access or SSH access can be made, only SYSRQ keys seem to do something (only reboot, so REISUB worked so far though, OOM is useless since the memory/swap is not even full) The I/O Disk led is stuck to 100% in ALL the following cases when this happens. So far: - This happens even when only ZRAM is enabled, and no swap partition is used. - Happens when ZSWAP is used with a swap partition - Happens also when a partition without zram or zswap is used - Maybe it's AMD specific? However, I'm not experiencing this on my laptop using the same tests. My laptop is an Intel one, while my desktop is an AMD Ryzen platform. Here are the specs: CPU: AMD Ryzen 5 1600 no OC GPU: AMD RX 580 8GB SSD: Crucial MX500 500GB MOBO: MSI B350M Grenade RAM: 8GB HyperX Kingston 2667Mhz Ubuntu version: 18.04 LTS, backports repo enabled Kernel version: 4.18.0-18, official ubuntu repo Bios settings: Default Additional info: Maybe I'm not 100% sure, but I noticed when using the 5.0.0-17 generic kernel, the lockups seem to still happen, but they recover eventually. Happened only a few times though... But will always be frozen for at least 30 seconds, differently from my intel laptop where those do occur. The SSD make is the same. I bought two of these, they got also the same amount of RAM. In my laptop those do not occur at all. Swapping memory even huge quantities like 1GB or more, do not produce any issues. Tests made: For testing this behaviour I tried: - Compiling the chromium-browser source code (takes up a lot of system RAM) - Used the "stress" command, using a specific amount of memory to decide how many it will be swapped, and here I noticed that even small quantities like a couple of megabytes will cause the system to freeze the 70% of the times Example: "stress --vm 1 --vm-bytes=7G" What should happen: I expect system slowdowns when swapping out memory since I do not have enough RAM, but unlikely when using Windows or my laptop with the same Linux version, not a completely unusuable environment. The swap partition is in both cases on an SSD. Reproduceability: 70% of the times Additional info again: I'm not sure this is due to any hardware failure, my SSD health is fine, as my CPU and RAM. As I said swapping in Windows works fine... --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: haru 2076 F pulseaudio /dev/snd/controlC2: haru 2076 F pulseaudio /dev/snd/controlC0: haru 2076 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: enp24s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-17-generic root=UUID=75d45574-7169-4653-aea3-9f95087f0806 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-17-generic N/A linux-backports-modules-5.0.0-17-generic N/A linux-firmware1.173.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo video WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.K0
[Kernel-packages] [Bug 1833281]
I have an idea why this bug is much worse with BTRFS than with EXT4: BTRFS has much bigger read/write amplification, up to 10x higher than EXT4. -- 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/1833281 Title: System freeze when memory is put on SWAP in Linux >4.10.x Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I'm reporting this since it's reproduceable the 70% of the time. Summary: In different circumstances, when the systems starts to swap out RAM memory, even small amounts, the system becomes completely unusuable and the screen freezes up, no mouse movement, no TTY access or SSH access can be made, only SYSRQ keys seem to do something (only reboot, so REISUB worked so far though, OOM is useless since the memory/swap is not even full) The I/O Disk led is stuck to 100% in ALL the following cases when this happens. So far: - This happens even when only ZRAM is enabled, and no swap partition is used. - Happens when ZSWAP is used with a swap partition - Happens also when a partition without zram or zswap is used - Maybe it's AMD specific? However, I'm not experiencing this on my laptop using the same tests. My laptop is an Intel one, while my desktop is an AMD Ryzen platform. Here are the specs: CPU: AMD Ryzen 5 1600 no OC GPU: AMD RX 580 8GB SSD: Crucial MX500 500GB MOBO: MSI B350M Grenade RAM: 8GB HyperX Kingston 2667Mhz Ubuntu version: 18.04 LTS, backports repo enabled Kernel version: 4.18.0-18, official ubuntu repo Bios settings: Default Additional info: Maybe I'm not 100% sure, but I noticed when using the 5.0.0-17 generic kernel, the lockups seem to still happen, but they recover eventually. Happened only a few times though... But will always be frozen for at least 30 seconds, differently from my intel laptop where those do occur. The SSD make is the same. I bought two of these, they got also the same amount of RAM. In my laptop those do not occur at all. Swapping memory even huge quantities like 1GB or more, do not produce any issues. Tests made: For testing this behaviour I tried: - Compiling the chromium-browser source code (takes up a lot of system RAM) - Used the "stress" command, using a specific amount of memory to decide how many it will be swapped, and here I noticed that even small quantities like a couple of megabytes will cause the system to freeze the 70% of the times Example: "stress --vm 1 --vm-bytes=7G" What should happen: I expect system slowdowns when swapping out memory since I do not have enough RAM, but unlikely when using Windows or my laptop with the same Linux version, not a completely unusuable environment. The swap partition is in both cases on an SSD. Reproduceability: 70% of the times Additional info again: I'm not sure this is due to any hardware failure, my SSD health is fine, as my CPU and RAM. As I said swapping in Windows works fine... --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: haru 2076 F pulseaudio /dev/snd/controlC2: haru 2076 F pulseaudio /dev/snd/controlC0: haru 2076 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: enp24s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-17-generic root=UUID=75d45574-7169-4653-aea3-9f95087f0806 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-17-generic N/A linux-backports-modules-5.0.0-17-generic N/A linux-firmware1.173.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo video WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.K0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR (MS-7A37) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias:
[Kernel-packages] [Bug 1857394] Re: [Firmware Bug]: reg 0x1c: invalid BAR (can't size)
** Description changed: 1) Ubuntu 19.10 2) kernel 5.3.0-23-generic 3) No error. 4) Error in Ubuntu Logs App. Message: 4:47:59 PM kernel: pci :00:14.4: bridge window [mem 0xd000-0xfebf window] (subtractive decode) 4:47:59 PM kernel: pci_bus :04: extended config space not accessible 4:47:59 PM kernel: pci :00:0a.0: bridge window [mem 0xfdd0-0xfddf 64bit pref] 4:47:59 PM kernel: pci :00:0a.0: bridge window [mem 0xfdd0-0xfddf 64bit pref] 4:47:59 PM kernel: pci :00:0a.0: bridge window [mem 0xfde0-0xfdef] 4:47:59 PM kernel: pci :00:0a.0: bridge window [io 0xc000-0xcfff] 4:47:59 PM kernel: pci :00:0a.0: PCI bridge to [bus 03] 4:47:59 PM kernel: pci :03:00.0: PME# supported from D0 D1 D2 D3hot D3cold 4:47:59 PM kernel: pci :03:00.0: supports D1 D2 4:47:59 PM kernel: pci :03:00.0: reg 0x30: [mem 0x-0x pref] 4:47:59 PM kernel: pci :03:00.0: reg 0x20: [mem 0xfdde-0xfdde 64bit pref] 4:47:59 PM kernel: pci :03:00.0: reg 0x18: [mem 0xfddff000-0xfddf 64bit pref] 4:47:59 PM kernel: pci :03:00.0: reg 0x10: [io 0xce00-0xceff] 4:47:59 PM kernel: pci :03:00.0: [10ec:8168] type 00 class 0x02 4:47:59 PM kernel: pci :00:06.0: bridge window [mem 0xfa00-0xfbff 64bit pref] 4:47:59 PM kernel: pci :00:06.0: bridge window [mem 0xfdf0-0xfdff] 4:47:59 PM kernel: pci :00:06.0: bridge window [io 0xd000-0xdfff] 4:47:59 PM kernel: pci :00:06.0: PCI bridge to [bus 02] 4:47:59 PM kernel: pci :02:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force' 4:47:59 PM kernel: pci :02:00.0: enabling Extended Tags 4:47:59 PM kernel: pci :02:00.0: reg 0x18: [mem 0xfa00-0xfbff 64bit pref] 4:47:59 PM kernel: pci :02:00.0: reg 0x10: [mem 0xfdf0-0xfdff 64bit] 4:47:59 PM kernel: pci :02:00.0: [1002:4d51] type 00 class 0x048000 4:47:59 PM kernel: pci :00:02.0: bridge window [mem 0xd000-0xdfff 64bit pref] 4:47:59 PM kernel: pci :00:02.0: bridge window [mem 0xfda0-0xfdaf] 4:47:59 PM kernel: pci :00:02.0: bridge window [io 0xe000-0xefff] 4:47:59 PM kernel: pci :00:02.0: PCI bridge to [bus 01] 4:47:59 PM kernel: pci :01:00.1: supports D1 D2 4:47:59 PM kernel: pci :01:00.1: enabling Extended Tags 4:47:59 PM kernel: pci :01:00.1: reg 0x10: [mem 0xfdafc000-0xfdaf 64bit] 4:47:59 PM kernel: pci :01:00.1: [1002:aa38] type 00 class 0x040300 4:47:59 PM kernel: pci :01:00.0: supports D1 D2 4:47:59 PM kernel: pci :01:00.0: enabling Extended Tags 4:47:59 PM kernel: pci :01:00.0: reg 0x30: [mem 0x-0x0001 pref] 4:47:59 PM kernel: pci :01:00.0: reg 0x20: [io 0xee00-0xeeff] 4:47:59 PM kernel: pci :01:00.0: reg 0x18: [mem 0xfdae-0xfdae 64bit] 4:47:59 PM kernel: pci :01:00.0: reg 0x10: [mem 0xd000-0xdfff 64bit pref] 4:47:59 PM kernel: pci :01:00.0: [1002:9540] type 00 class 0x03 4:47:59 PM kernel: pci :00:18.3: [1022:1103] type 00 class 0x06 4:47:59 PM kernel: pci :00:18.2: [1022:1102] type 00 class 0x06 4:47:59 PM kernel: pci :00:18.1: [1022:1101] type 00 class 0x06 4:47:59 PM kernel: pci :00:18.0: [1022:1100] type 00 class 0x06 4:47:59 PM kernel: pci :00:14.5: reg 0x10: [mem 0xfe028000-0xfe028fff] 4:47:59 PM kernel: pci :00:14.5: [1002:4399] type 00 class 0x0c0310 4:47:59 PM kernel: pci :00:14.4: [1002:4384] type 01 class 0x060401 4:47:59 PM kernel: pci :00:14.3: [1002:439d] type 00 class 0x060100 4:47:59 PM kernel: pci :00:14.2: PME# supported from D0 D3hot D3cold 4:47:59 PM kernel: pci :00:14.2: reg 0x10: [mem 0xfe024000-0xfe027fff 64bit] 4:47:59 PM kernel: pci :00:14.2: [1002:4383] type 00 class 0x040300 4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x1c: [io 0x0376] 4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x18: [io 0x0170-0x0177] 4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x14: [io 0x03f6] 4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x10: [io 0x01f0-0x01f7] 4:47:59 PM kernel: pci :00:14.1: reg 0x20: [io 0xfa00-0xfa0f] 4:47:59 PM kernel: pci :00:14.1: reg 0x1c: [io 0x-0x0003] 4:47:59 PM kernel: pci :00:14.1: reg 0x18: [io 0x-0x0007] 4:47:59 PM kernel: pci :00:14.1: reg 0x14: [io 0x-0x0003] 4:47:59 PM kernel: pci :00:14.1: reg 0x10: [io 0x-0x0007] 4:47:59 PM kernel: pci :00:14.1: [1002:439c] type 00 class 0x01018a 4:47:59 PM kernel: pci :00:14.0: [1002:4385] type 00 class 0x0c0500 4:47:59 PM kernel: pci :00:13.2: PME# supported from D0 D1 D2 D3hot 4:47:59 PM kernel: pci :00:13.2: supports D1 D2 4:47:59 PM kernel: pci
[Kernel-packages] [Bug 1857394] Re: [Firmware Bug]: reg 0x1c: invalid BAR (can't size)
** Tags added: apport-collected eoan wayland-session -- 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/1857394 Title: [Firmware Bug]: reg 0x1c: invalid BAR (can't size) Status in linux package in Ubuntu: Incomplete Bug description: 1) Ubuntu 19.10 2) kernel 5.3.0-23-generic 3) No error. 4) Error in Ubuntu Logs App. Message: 4:47:59 PM kernel: pci :00:14.4: bridge window [mem 0xd000-0xfebf window] (subtractive decode) 4:47:59 PM kernel: pci_bus :04: extended config space not accessible 4:47:59 PM kernel: pci :00:0a.0: bridge window [mem 0xfdd0-0xfddf 64bit pref] 4:47:59 PM kernel: pci :00:0a.0: bridge window [mem 0xfdd0-0xfddf 64bit pref] 4:47:59 PM kernel: pci :00:0a.0: bridge window [mem 0xfde0-0xfdef] 4:47:59 PM kernel: pci :00:0a.0: bridge window [io 0xc000-0xcfff] 4:47:59 PM kernel: pci :00:0a.0: PCI bridge to [bus 03] 4:47:59 PM kernel: pci :03:00.0: PME# supported from D0 D1 D2 D3hot D3cold 4:47:59 PM kernel: pci :03:00.0: supports D1 D2 4:47:59 PM kernel: pci :03:00.0: reg 0x30: [mem 0x-0x pref] 4:47:59 PM kernel: pci :03:00.0: reg 0x20: [mem 0xfdde-0xfdde 64bit pref] 4:47:59 PM kernel: pci :03:00.0: reg 0x18: [mem 0xfddff000-0xfddf 64bit pref] 4:47:59 PM kernel: pci :03:00.0: reg 0x10: [io 0xce00-0xceff] 4:47:59 PM kernel: pci :03:00.0: [10ec:8168] type 00 class 0x02 4:47:59 PM kernel: pci :00:06.0: bridge window [mem 0xfa00-0xfbff 64bit pref] 4:47:59 PM kernel: pci :00:06.0: bridge window [mem 0xfdf0-0xfdff] 4:47:59 PM kernel: pci :00:06.0: bridge window [io 0xd000-0xdfff] 4:47:59 PM kernel: pci :00:06.0: PCI bridge to [bus 02] 4:47:59 PM kernel: pci :02:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force' 4:47:59 PM kernel: pci :02:00.0: enabling Extended Tags 4:47:59 PM kernel: pci :02:00.0: reg 0x18: [mem 0xfa00-0xfbff 64bit pref] 4:47:59 PM kernel: pci :02:00.0: reg 0x10: [mem 0xfdf0-0xfdff 64bit] 4:47:59 PM kernel: pci :02:00.0: [1002:4d51] type 00 class 0x048000 4:47:59 PM kernel: pci :00:02.0: bridge window [mem 0xd000-0xdfff 64bit pref] 4:47:59 PM kernel: pci :00:02.0: bridge window [mem 0xfda0-0xfdaf] 4:47:59 PM kernel: pci :00:02.0: bridge window [io 0xe000-0xefff] 4:47:59 PM kernel: pci :00:02.0: PCI bridge to [bus 01] 4:47:59 PM kernel: pci :01:00.1: supports D1 D2 4:47:59 PM kernel: pci :01:00.1: enabling Extended Tags 4:47:59 PM kernel: pci :01:00.1: reg 0x10: [mem 0xfdafc000-0xfdaf 64bit] 4:47:59 PM kernel: pci :01:00.1: [1002:aa38] type 00 class 0x040300 4:47:59 PM kernel: pci :01:00.0: supports D1 D2 4:47:59 PM kernel: pci :01:00.0: enabling Extended Tags 4:47:59 PM kernel: pci :01:00.0: reg 0x30: [mem 0x-0x0001 pref] 4:47:59 PM kernel: pci :01:00.0: reg 0x20: [io 0xee00-0xeeff] 4:47:59 PM kernel: pci :01:00.0: reg 0x18: [mem 0xfdae-0xfdae 64bit] 4:47:59 PM kernel: pci :01:00.0: reg 0x10: [mem 0xd000-0xdfff 64bit pref] 4:47:59 PM kernel: pci :01:00.0: [1002:9540] type 00 class 0x03 4:47:59 PM kernel: pci :00:18.3: [1022:1103] type 00 class 0x06 4:47:59 PM kernel: pci :00:18.2: [1022:1102] type 00 class 0x06 4:47:59 PM kernel: pci :00:18.1: [1022:1101] type 00 class 0x06 4:47:59 PM kernel: pci :00:18.0: [1022:1100] type 00 class 0x06 4:47:59 PM kernel: pci :00:14.5: reg 0x10: [mem 0xfe028000-0xfe028fff] 4:47:59 PM kernel: pci :00:14.5: [1002:4399] type 00 class 0x0c0310 4:47:59 PM kernel: pci :00:14.4: [1002:4384] type 01 class 0x060401 4:47:59 PM kernel: pci :00:14.3: [1002:439d] type 00 class 0x060100 4:47:59 PM kernel: pci :00:14.2: PME# supported from D0 D3hot D3cold 4:47:59 PM kernel: pci :00:14.2: reg 0x10: [mem 0xfe024000-0xfe027fff 64bit] 4:47:59 PM kernel: pci :00:14.2: [1002:4383] type 00 class 0x040300 4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x1c: [io 0x0376] 4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x18: [io 0x0170-0x0177] 4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x14: [io 0x03f6] 4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x10: [io 0x01f0-0x01f7] 4:47:59 PM kernel: pci :00:14.1: reg 0x20: [io 0xfa00-0xfa0f] 4:47:59 PM kernel: pci :00:14.1: reg 0x1c: [io 0x-0x0003] 4:47:59 PM kernel: pci :00:14.1: reg 0x18: [io 0x-0x0007] 4:47:59 PM kernel: pci :00:14.1: reg 0x14: [io 0x-0x0003] 4:47:59 PM kernel: pci :00:14.1: reg 0x10: [io
[Kernel-packages] [Bug 1857626] Re: Kernel Linux version 5.3.0-24.26 et Realtek RTL822BE 802.11a/b/g/n/ac
apport information ** Tags added: apport-collected ** Description changed: No wifi connexion by using the kernels 5.3.0. A problem was solved with the kernel 5.0.0.21 avait été résolu (voir), but it starts again. Please find some information lspci -nnk | grep 0280 -A3 03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter [10ec:b822] Subsystem: AzureWave RTL8822BE 802.11a/b/g/n/ac WiFi adapter [1a3b:2950] Kernel driver in use: rtw_pci Kernel modules: rtwpci dmesg -lerr | tail -50 [5.917496] rtw_pci :03:00.0: failed to send h2c command [6.558933] sep5_10: Driver loading... [ 10.219360] rtw_pci :03:00.0: failed to send h2c command [ 10.219401] rtw_pci :03:00.0: failed to send h2c command [ 18.674133] rtw_pci :03:00.0: failed to send h2c command [ 18.674221] rtw_pci :03:00.0: failed to send h2c command [ 18.674305] rtw_pci :03:00.0: failed to send h2c command [ 18.674719] rtw_pci :03:00.0: failed to send h2c command [ 19.197448] rtw_pci :03:00.0: failed to send h2c command [ 20.246203] rtw_pci :03:00.0: failed to send h2c command [ 23.507151] rtw_pci :03:00.0: failed to send h2c command [ 23.507189] rtw_pci :03:00.0: failed to send h2c command [ 31.958087] rtw_pci :03:00.0: failed to send h2c command [ 31.958176] rtw_pci :03:00.0: failed to send h2c command [ 31.958247] rtw_pci :03:00.0: failed to send h2c command [ 31.958374] rtw_pci :03:00.0: failed to send h2c command [ 32.561597] rtw_pci :03:00.0: failed to send h2c command dmesg reports also a problem with the driver [ 10.236063] rtw_pci :03:00.0: failed to send h2c command [ 10.236107] rtw_pci :03:00.0: failed to send h2c command [ 10.236112] rtw_pci :03:00.0: sta 54:64:d9:4e:01:df joined with macid 0 [ 10.738280] [ cut here ] [ 10.738300] purge skb(s) not reported by firmware [ 10.738392] WARNING: CPU: 2 PID: 0 at drivers/net/wireless/realtek/rtw88/tx.c:156 rtw_tx_report_purge_timer+0x25/0x60 [rtw88] [ 10.738395] Modules linked in: sep5(OE) socperf3(OE) pax(OE) cmac bnep binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_hda_codec_realtek snd_compress ac97_bus x86_pkg_temp_thermal snd_hda_codec_generic intel_powerclamp ledtrig_audio snd_pcm_dmaengine coretemp kvm_intel snd_hda_intel snd_hda_codec kvm snd_hda_core irqbypass snd_hwdep snd_pcm mei_hdcp snd_seq_midi snd_seq_midi_event intel_rapl_msr snd_rawmidi crct10dif_pclmul crc32_pclmul joydev ghash_clmulni_intel i915 snd_seq aesni_intel rtwpci rtw88 aes_x86_64 uvcvideo btusb crypto_simd snd_seq_device snd_timer videobuf2_vmalloc drm_kms_helper btrtl cryptd glue_helper videobuf2_memops mac80211 videobuf2_v4l2 btbcm intel_cstate drm snd videobuf2_common btintel bluetooth intel_rapl_perf videodev cfg80211 asus_nb_wmi i2c_algo_bit processor_thermal_device spi_pxa2xx_platform fb_sys_fops asus_wmi [ 10.738473] input_leds mei_me syscopyarea intel_rapl_common idma64 mc ecdh_generic sysfillrect dw_dmac intel_xhci_usb_role_switch sparse_keymap serio_raw wmi_bmof soundcore mxm_wmi ecc libarc4 8250_dw dw_dmac_core hid_multitouch mei roles sysimgblt virt_dma intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone int3400_thermal mac_hid acpi_thermal_rel acpi_pad asus_wireless sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj usbhid hid_generic i2c_hid hid r8169 i2c_i801 ahci intel_lpss_pci realtek libahci intel_lpss video wmi pinctrl_sunrisepoint pinctrl_intel [ 10.738546] CPU: 2 PID: 0 Comm: swapper/2 Tainted: G OE 5.3.0-24-generic #26-Ubuntu [ 10.738549] Hardware name: ASUSTeK COMPUTER INC. X705UDR/X705UDR, BIOS X705UDR.302 09/27/2017 [ 10.738568] RIP: 0010:rtw_tx_report_purge_timer+0x25/0x60 [rtw88] [ 10.738574] Code: 00 00 00 00 00 0f 1f 44 00 00 8b 47 f0 85 c0 75 01 c3 55 48 89 e5 41 55 41 54 53 48 89 fb 48 c7 c7 f0 bd c8 c0 e8 f6 0a 87 f2 <0f> 0b 4c 8d 6b d8 4c 89 ef e8 ed 4e 27 f3 48 8d 7b e0 49 89 c4 e8 [ 10.738577] RSP: 0018:b6c480170e48 EFLAGS: 00010286 [ 10.738582] RAX: RBX: 96afd3c8d848 RCX: 083f [ 10.738585] RDX: RSI: 00f6 RDI: 083f [ 10.738587] RBP: b6c480170e60 R08: 96afdea97448 R09: 0004 [ 10.738591] R10: R11: 0001 R12: 96afdea9b600 [ 10.738594] R13: 96afd3c8d848 R14: c0c2a7d0 R15: 96afd3c8d848 [ 10.738598] FS: () GS:96afdea8() knlGS: [ 10.738602] CS: 0010 DS: ES: CR0: 80050033 [
[Kernel-packages] [Bug 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic
Hi Lewi S. Kristianto, this works for me... thanks ... and sorry for the questions and all the support etc. I'm making a mistake here, i will know for the next time ... -- 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/1854798 Title: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: SRU justification = [Impact] Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic [Fix] After applied commit "Input: synaptics-rmi4 - avoid processing unknown IRQs", no irq response from touchpad. This commit is depended on commit: "Input: synaptics-rmi4 - convert irq distribution to irq_domain" [Test] Verified on hardware, tests results are good. [Regression Potential] Low. Fix bug that introduced by stable release update. 2nd and 3rd patches are fixes for the 1st patch. These commits are already included by eoan kernel, so bionic 4.15 only. Original reports === environment: Dell Laptop XPS-9333 Device: # xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SYNAPTICS Synaptics Large Touch Screen id=9[slave pointer (2)] ⎜ ↳ Synaptics s3203 id=12 [slave pointer (2)] ⎜ ↳ Ultrathin Touch Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Dell WMI hotkeysid=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=14 [slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=10 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] # xinput --list-props 12 Device 'Synaptics s3203': Device Enabled (142):1 Coordinate Transformation Matrix (144): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (270): 1 Device Accel Constant Deceleration (271):2.50 Device Accel Adaptive Deceleration (272):1.00 Device Accel Velocity Scaling (273): 9.712231 Synaptics Edges (304): 162, 3908, 133, 2339 Synaptics Finger (305): 25, 30, 0 Synaptics Tap Time (306):180 Synaptics Tap Move (307):209 Synaptics Tap Durations (308): 180, 180, 100 Synaptics ClickPad (309):1 Synaptics Middle Button Timeout (310): 0 Synaptics Two-Finger Pressure (311): 282 Synaptics Two-Finger Width (312):7 Synaptics Scrolling Distance (313): -95, 95 Synaptics Edge Scrolling (314): 0, 0, 0 Synaptics Two-Finger Scrolling (315):1, 1 Synaptics Move Speed (316): 1.00, 1.75, 0.042008, 0.00 Synaptics Off (317): 0 Synaptics Locked Drags (318):0 Synaptics Locked Drags Timeout (319):5000 Synaptics Tap Action (320): 0, 0, 0, 0, 1, 3, 2 Synaptics Click Action (321):1, 3, 2 Synaptics Circular Scrolling (322): 0 Synaptics Circular Scrolling Distance (323): 0.10 Synaptics Circular Scrolling Trigger (324): 0 Synaptics Circular Pad (325):0 Synaptics Palm Detection (326): 1 Synaptics Palm Dimensions (327): 10, 200 Synaptics Coasting Speed (328): 20.00, 50.00 Synaptics Pressure Motion (329): 30, 160 Synaptics Pressure Motion Factor (330): 1.00, 1.00 Synaptics Resolution Detect (331): 1 Synaptics Grab Event Device (332): 0 Synaptics Gestures (333):1 Synaptics Capabilities (334):1, 0, 0, 1, 1, 1, 0 Synaptics Pad Resolution (335): 42, 42 Synaptics Area (336):0, 0, 0, 0 Synaptics Soft Button Areas (337): 0, 0, 0, 0, 0, 0, 0, 0 Synaptics Noise Cancellation (338): 23, 23 Device Product ID (262): 1739, 10036 Device Node (263): "/dev/input/event5" # lspci 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 09) 00:14.0 USB
[Kernel-packages] [Bug 1856653] Re: CVE-2019-0154 caused major power problem, pls backport upstream's fix
** Information type changed from Public to Public Security ** Information type changed from Public Security to Private Security -- 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/1856653 Title: CVE-2019-0154 caused major power problem, pls backport upstream's fix Status in linux package in Ubuntu: Confirmed Bug description: https://gitlab.freedesktop.org/drm/intel/issues/614 the fix released as CVE-2019-0154 increases idle power consumption on intel i915 6th gen and later. That's because the GPU does not enter RC6 any more. For example, my Thinkpad P50 (6th gen) idles at 9w with current 5.3 kernels. Previously, it idled at 5W. Effects on a T480 (8th gen) are less dramatic but still significant. 5.5RC1 has the maintainer's second pass at this, which restores RC6 idling The maintainer's patch for 5.3 is here: https://gitlab.freedesktop.org/drm/intel/issues/614#note_366057 I have applied this to tag Ubuntu-hwe-5.3.0-25.27~18.04.2 and it builds. I am testing it now. I think it would be very helpful to backport this if you can. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856653/+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 1857695] Re: TouchPad stop working
*** This bug is a duplicate of bug 1854798 *** https://bugs.launchpad.net/bugs/1854798 Hi, this appears to be a duplicate of bug 1854798. Please find last few comments there for work-arounds before new kernel release. ** This bug has been marked a duplicate of bug 1854798 Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic -- 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/1857695 Title: TouchPad stop working Status in linux package in Ubuntu: New Bug description: The touchpad (and buttons) stop working. If I understand it well, it is a kernel problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: stef 1474 F...m pulseaudio /dev/snd/controlC0: stef 1474 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Dec 27 11:55:27 2019 InstallationDate: Installed on 2019-10-29 (58 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5664 IMC Networks Bus 001 Device 008: ID 275d:0ba6 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80MK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=b9d5ca94-17c0-4897-90b3-01265a547939 ro quiet splash acpi_osi=Linux vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.14 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2015 dmi.bios.vendor: LENOVO dmi.bios.version: C6CN34WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 900-13ISK dmi.modalias: dmi:bvnLENOVO:bvrC6CN34WW:bd10/29/2015:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK: dmi.product.family: IDEAPAD dmi.product.name: 80MK dmi.product.version: Lenovo YOGA 900-13ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857695/+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 1857673] Re: System will auto resume from sleep on receiving LE ADV after paired with BT LE devices (Intel 9560 HrP)
PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1857673 WIP: https://code.launchpad.net/~vicamo/ubuntu/+source/linux-firmware/+git/linux-firmware/+ref/bug-1857673/update-ibt-17-16-1/bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1857673 Title: System will auto resume from sleep on receiving LE ADV after paired with BT LE devices (Intel 9560 HrP) Status in HWE Next: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: In Progress Status in linux-firmware source package in Disco: Won't Fix Bug description: Similar to bug 1849779, on systems with Intel 9560 Bluetooth fw ver REL0450, deep suspend will be interrupted and resume automatically once it has been paired with a BLE device. The device doesn't have to remain connected, as long as there are BLE devices near by broadcasting LE ADV. This can be fixed by updating intel/ibt-17-16-1.sfi from upstream commit https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=b6427bf4faae9b8864e303d88c3ec8d0df017dac. Steps to reproduce: 1. pair with BLE device and turn off the device. It should be listed as Disconnected in System Bluetooth settings. Close the settings app as well. 2. run `sudo btmon -t` in the background, make sure LE ADV packets pop up. 3. run `sudo btmon -t` on another host to make sure there are LE ADV packets during the suspend period. 3. trigger system deep suspend (S3) on DUT. 4. wait for around 1 minutes (depending on the surrounding environment) and see if the DUT is resumed unsolicitedly. Expects: DUT only resumes when power button pressed or on other explicit requests. Actual: DUT resumes unsolicitedly within 1 minutes. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Dependencies: DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.14 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-1066.76-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1066-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1857673/+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 1857695] [NEW] TouchPad stop working
Public bug reported: The touchpad (and buttons) stop working. If I understand it well, it is a kernel problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: stef 1474 F...m pulseaudio /dev/snd/controlC0: stef 1474 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Dec 27 11:55:27 2019 InstallationDate: Installed on 2019-10-29 (58 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5664 IMC Networks Bus 001 Device 008: ID 275d:0ba6 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80MK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=b9d5ca94-17c0-4897-90b3-01265a547939 ro quiet splash acpi_osi=Linux vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.14 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2015 dmi.bios.vendor: LENOVO dmi.bios.version: C6CN34WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 900-13ISK dmi.modalias: dmi:bvnLENOVO:bvrC6CN34WW:bd10/29/2015:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK: dmi.product.family: IDEAPAD dmi.product.name: 80MK dmi.product.version: Lenovo YOGA 900-13ISK dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "result from cat /proc/bus/input/devices > ~/devices" https://bugs.launchpad.net/bugs/1857695/+attachment/5315831/+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/1857695 Title: TouchPad stop working Status in linux package in Ubuntu: New Bug description: The touchpad (and buttons) stop working. If I understand it well, it is a kernel problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: stef 1474 F...m pulseaudio /dev/snd/controlC0: stef 1474 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Dec 27 11:55:27 2019 InstallationDate: Installed on 2019-10-29 (58 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5664 IMC Networks Bus 001 Device 008: ID 275d:0ba6 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80MK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=b9d5ca94-17c0-4897-90b3-01265a547939 ro quiet splash acpi_osi=Linux vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.14 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2015 dmi.bios.vendor: LENOVO dmi.bios.version: C6CN34WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 900-13ISK dmi.modalias: dmi:bvnLENOVO:bvrC6CN34WW:bd10/29/2015:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK: dmi.product.family: IDEAPAD dmi.product.name: 80MK dmi.product.version: Lenovo YOGA 900-13ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857695/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1831710] Re: Touchpad not working (Lenevo Ideapad 330 series)
Hello Sumneet Kaur Bamrah, You will need to file a new bug report for your new wifi issue. If you're not sure where did the out-of-tree module came from, I would say a clean install of your OS might be easier to debug this touchpad issue. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831710 Title: Touchpad not working (Lenevo Ideapad 330 series) Status in linux package in Ubuntu: Confirmed Bug description: The touch pad has not been used since the purchase of the product. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-21-generic 4.18.0-21.22~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 5 13:41:22 2019 InstallationDate: Installed on 2019-06-05 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: athena 1232 F pulseaudio /dev/snd/pcmC1D0p: athena 1232 F...m pulseaudio /dev/snd/controlC0: athena 1232 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-06-05 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 81D2 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic root=UUID=29a08da7-0f52-4ee8-8424-f2b37885999f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-21-generic N/A linux-backports-modules-4.18.0-21-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.18.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/10/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7VCN46WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7VCN46WW:bd12/10/2018:svnLENOVO:pn81D2:pvrLenovoideapad330-15ARR:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15ARR: dmi.product.family: ideapad 330-15ARR dmi.product.name: 81D2 dmi.product.sku: LENOVO_MT_81D2_BU_idea_FM_ideapad 330-15ARR dmi.product.version: Lenovo ideapad 330-15ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831710/+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 732641] Re: Resume from suspend fails on new FireWire stack (TSB43AB22/A IEEE-1394a-2000 Controller)
Hello, I will close this bug as it's really old, please feel free to open a new one if you're still experiencing this issue with a newer release. Thanks. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/732641 Title: Resume from suspend fails on new FireWire stack (TSB43AB22/A IEEE- 1394a-2000 Controller) Status in linux package in Ubuntu: Invalid Bug description: Since upgrade to 10.10/kernel 2.6.35 kernel doesn't complete resume from suspend. $ uname -a Linux sendell 2.6.35-27-generic #48-Ubuntu SMP Tue Feb 22 20:25:46 UTC 2011 x86_64 GNU/Linux Xorg vty is blank, I can change to other vtys but when i return to the one with Xorg, switching no longer works. Only manual reset remedies this situation. Tried https://wiki.ubuntu.com/DebuggingKernelSuspend#%22resume- trace%22%20debugging%20procedure%20for%20finding%20buggy%20drivers [0.714873] PM: Resume from disk failed. [0.714886] registered taskstats version 1 [0.715167] Magic number: 0:608:476 [0.715170] hash matches /build/buildd/linux-2.6.35/drivers/base/power/main.c:545 [0.715213] pci :03:05.0: hash matches [0.715281] rtc_cmos 00:05: setting system clock to 1980-09-08 10:27:51 UTC (337256871) $ lspci | grep 03:05 03:05.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) $ dmesg|grep fire [0.380065] pci :03:05.0: reg 10: [mem 0xfdeff000-0xfdeff7ff] [0.380071] pci :03:05.0: reg 14: [mem 0xfdef8000-0xfdefbfff] [0.380105] pci :03:05.0: supports D1 D2 [0.380107] pci :03:05.0: PME# supported from D0 D1 D2 D3hot [0.380111] pci :03:05.0: PME# disabled [0.715213] pci :03:05.0: hash matches [0.893472] firewire_ohci :03:05.0: PCI INT A -> Link[APC4] -> GSI 19 (level, low) -> IRQ 19 [0.950061] firewire_ohci: Added fw-ohci device :03:05.0, OHCI v1.10, 4 IR + 8 IT contexts, quirks 0x2 $ lsmod|grep fire firewire_ohci 24839 0 firewire_core 54327 1 firewire_ohci crc_itu_t 1739 1 firewire_core $sudo modprobe -r firewire_core firewire_ohci And then resuming from suspend works. I've browsed https://ieee1394.wiki.kernel.org/index.php/Source_Repositories to see if any recent fixes were made and this one sticks out: http://git.kernel.org/?p=linux/kernel/git/ieee1394/linux1394-2.6.git;a=commit;h=dd23736e092035b71df1117482b71fdfb5634239 I'll shortly try http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.38-rc8-natty/ to see if the mentioned commit or perhaps another one helped with this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/732641/+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 1729256] Re: Invalid btree pointer causes the kernel NULL pointer dereference
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1729256 Title: Invalid btree pointer causes the kernel NULL pointer dereference Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Zesty: Fix Released Status in linux source package in Artful: Won't Fix Bug description: [Impact] The frequent kernel errors can be seen inside the XFS based OSD processes and it causes to crash and restart. BUG: unable to handle kernel NULL pointer dereference at 00a0 IP: [] xfs_da3_node_read+0x30/0xb0 [xfs] CPU: 8 PID: 2855031 Comm: tp_fstore_op Not tainted 4.4.0-78-generic #99-Ubuntu Hardware name: HP ProLiant DL380 Gen9/ProLiant DL380 Gen9, BIOS P89 09/13/2016 task: 880620f38e00 ti: 880678228000 task.ti: 880678228000 RIP: 0010:[] [] xfs_da3_node_read+0x30/0xb0 [xfs] RSP: 0018:88067822bd00 EFLAGS: 00010286 RAX: RBX: 88078abff3f0 RCX: 0001 RDX: RSI: RDI: 88067822bcb0 RBP: 88067822bd20 R08: 0001 R09: fffe R10: ea001e2aff80 R11: 0001 R12: 88067822bd50 R13: 8805a37f R14: 0001 R15: 8d180e3e FS: 7f7573c01700() GS:88103fa0()knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 00a0 CR3: 001686f3d000 CR4: 003406e0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 Stack: c03cfb50 c03b0ecc 88067822bde0 0001 88067822bd98 c038c8b3 00020008 88081cb06040 0002d8723bf8 880fc142ae80 Call Trace: [] ? xfs_trans_roll+0x2c/0x50 [xfs] [] xfs_attr3_node_inactive+0x183/0x220 [xfs] [] xfs_attr3_root_inactive+0xac/0x100 [xfs] [] xfs_attr_inactive+0x14c/0x1a0 [xfs] [] xfs_inactive+0x85/0x120 [xfs] [] xfs_fs_evict_inode+0xa5/0x100 [xfs] [] evict+0xbe/0x190 [] iput+0x1c1/0x240 [] do_unlinkat+0x199/0x2d0 [] SyS_unlink+0x16/0x20 [] entry_SYSCALL_64_fastpath+0x16/0x71 [Fix] commit e678a63e6c95f140befe6fcd81b49075ecb3c701 Author: Brian Foster Date: Mon Oct 9 11:38:56 2017 -0700 xfs: reinit btree pointer on attr tree inactivation walk xfs_attr3_root_inactive() walks the attr fork tree to invalidate the associated blocks. xfs_attr3_node_inactive() recursively descends from internal blocks to leaf blocks, caching block address values along the way to revisit parent blocks, locate the next entry and descend down that branch of the tree. The code that attempts to reread the parent block is unsafe because it assumes that the local xfs_da_node_entry pointer remains valid after an xfs_trans_brelse() and re-read of the parent buffer. Under heavy memory pressure, it is possible that the buffer has been reclaimed and reallocated by the time the parent block is reread. This means that 'btree' can point to an invalid memory address, lead to a random/garbage value for child_fsb and cause the subsequent read of the attr fork to go off the rails and return a NULL buffer for an attr fork offset that is most likely not allocated. Note that this problem can be manufactured by setting XFS_ATTR_BTREE_REF to 0 to prevent LRU caching of attr buffers, creating a file with a multi-level attr fork and removing it to trigger inactivation. To address this problem, reinit the node/btree pointers to the parent buffer after it has been re-read. This ensures btree points to a valid record and allows the walk to proceed. [Test] The patch has been tested on the production system. [Regression Risk] Clean cherry-pick queued for stable, so we'll be picking it up anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729256/+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 1831846] Re: [raven] fix screen corruption on modprobe
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831846 Title: [raven] fix screen corruption on modprobe Status in linux package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux-oem-osp1 source package in Disco: Fix Released Bug description: [Impact] These patches (or a squashed commit) are needed to fix screen corruption during modprobe on raven: 02122753f1 drm/amdgpu: reserve stollen vram for raven series 379109351f drm/amdgpu: keep stolen memory on picasso [Test case] test modprobe on affected hw [Regression potential] shouldn't be any To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831846/+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 1771252] Re: [ICL] Enable intel_rapl driver for Icelake
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1771252 Title: [ICL] Enable intel_rapl driver for Icelake Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Bug description: Desription: This feature is intended to track intel_rapl driver enabling for IceLake. Commit:Powercap/intel_rapl driver enabling for Icelake Target Release: 19.10 Target Kernel: 5.1 SRU Justification [Impact] New CPU is required to be listed in Intel RAPL (Running Average Power Limit) driver. [Fix] From Intel's suggestion, below 2 commits are required ba6f3ec198d5 powercap/intel_rapl: add Ice Lake mobile df7f8e00a50f powercap: intel_rapl: add support for Jacobsville [Test] Boot up Intel ICL-Y SDP with the patched kernel, nothing abnormal, but I'm unable to distinguish the difference. [Regression Potential] Low, the 2 commits add new ID to the table, should affect new CPU only. To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1771252/+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 1819504] Re: tcmu user space crash results in kernel module hang.
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1819504 Title: tcmu user space crash results in kernel module hang. Status in linux package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-gcp source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-gcp source package in Cosmic: Fix Released Bug description: With the 4.15.0 kernel version used in bionic GCP/GKE, if the tcmu user space code crashes while handling a netlink message from the kernel, the kernel module will be stuck waiting for the response. This situation can only be resolved with a server reboot. === SRU Justification === [Impact] With this particular user-space crash in the current Ubuntu image it results in a hang hobbles the entire physical server. [Fix] The request is for Canonical to backport the patch https://patchwork.kernel.org/patch/10319623/ to the bionic 4.15.0 kernel [** CORRECTION: See comment #2 ***] There were a number of mainline upstream commits to apply as part of the backport [Test] unavailable [Regression Potential] Low. it's all mainline commits, and affects only that driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819504/+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 1845046] Re: Bluetooth headphones/speaker default to low quality headset mode and fails to switch to A2DP when selected
Same problem with Sony WH-1000XM2 My workaround is 1. Turn on headphone, wait to connect with low quality sink 2. Turn off bluetooth, wait couple of seconds and turn on 3. Reconnect headphones. Works all the time. Ubuntu: 18.04 Sony WH-1000XM2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1845046 Title: Bluetooth headphones/speaker default to low quality headset mode and fails to switch to A2DP when selected Status in bluez package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Whenever I turn on my headphones theyll connect to my computer but im able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: litleck1398 F pulseaudio /dev/snd/controlC0: litleck1398 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 17:07:59 2019 InstallationDate: Installed on 2019-09-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: WH-1000XM3 Symptom_Type: High background noise, or volume is too low Title: [WH-1000XM3, playback] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.19 dmi.board.name: 01NYPT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R5 dmi.product.sku: 0729 dmi.product.version: 1.0.19 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1696165] Re: [SRU][Zesty] fix soft lockup on overcommited hugepages
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1696165 Title: [SRU][Zesty] fix soft lockup on overcommited hugepages Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: [Impact] On failing to migrate a page, soft_offline_huge_page() performs the necessary update to the hugepage ref-count. But when !hugepage_migration_supported() , unmap_and_move_hugepage() also decrements the page ref-count for the hugepage. The combined behaviour leaves the ref-count in an inconsistent state. This leads to soft lockups when running the overcommitted hugepage test from mce-tests suite [Testing] Run the mce-test/cases/function/hwpoison/run_hugepage_overcommit.sh and you should see softlock up if hugepage migration support is not enabled. [Fix] upstream commit: 30809f559a0d mm/migrate: fix refcount handling when !hugepage_migration_supported() [Regression Potential] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1696165/+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 1737890] Re: QCA Rome bluetooth can not wakeup after USB runtime suspended.
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1737890 Title: QCA Rome bluetooth can not wakeup after USB runtime suspended. Status in linux package in Ubuntu: Invalid Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux-oem source package in Artful: Invalid Bug description: == SRU Justification == [Impact] Some QCA ROME bluetooth devices does not work after runtime suspended. [Fix] Latest mainline does not have this issue. The bisected commit is a0085f2510e8976614ad8f766b209448b385492f "Bluetooth: btusb: driver to enable the usb-wakeup feature". With this commit, the BT device now can wake host controller up. [Test] Cherry-picked the commit into Artful/OEM kernel and the issue is fixed. [Regression Potential] Low. usb-wakeup support shouldn't affect the driver's function. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737890/+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 1746019] Re: [Artful SRU] Fix capsule update regression
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1746019
Title:
[Artful SRU] Fix capsule update regression
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Artful:
Fix Released
Bug description:
[IMPACT]
Commit 82c3768b8d68 ("efi/capsule-loader: Use a cached copy of the
capsule header") refactored the capsule loading code that maps the
capsule header, to avoid having to map it several times. However,
as it turns out, the vmap() call we ended up removing did not just
map the header, but the entire capsule image, and dropping this
virtual mapping breaks capsules that are processed by the firmware
immediately (i.e., without a reboot).
[FIX]
The following patch fixes the issue
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/firmware/efi/capsule-loader.c?id=f24c4d478013d82bd1b943df566fff3561d52864
[TEST]
Please see comments below for testing information and details.
[REGRESSION POTENTIAL]
This patch fixes a regression in 4.13 and onward.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746019/+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 1383921] Re: kipmi0 process hangs with ipmitool
** Changed in: linux (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1383921 Title: kipmi0 process hangs with ipmitool Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Bug description: we're in the process of migrating from 12.04 to 14.04 and are noticing a problem apparently related to the kernel and ipmi. after an indeterminate period of regular ipmi queries (e.g., nagios checks using ipmitool) the kipmi0 process pegs a cpu to ~100% usage and further ipmitool commands hang. the former is not a huge problem as the process is niced and its cpu usage can be limited using the /sys/module/ipmi_si/parameters/kipmid_max_busy_us interface. however, ipmitool's hanging severely degrades hardware monitoring. this problem initially reared its head in our enviroment on a handful of 12.04 hosts on which hwe kernels were installed. of the dozen deployed 14.04 hosts, four have started displaying these symptoms in the past week. all of the 12.04+hwe hosts were eventually affected; i believe that given enough time all of the 14.04 hosts would be, as well. a reboot clears it up until its recurrence. red hat has a bug logged that appears to match this: https://bugzilla.redhat.com/show_bug.cgi?id=1090619 unfortunately the work-around and proposed fix (from a duplicate bug) are currently non- public. it does look like they were able to identify the "ipmi: simplify locking" patch from commit id f60adf42ad55405d1b17e9e5c33fdb63f1eb8861 as the culprit. i have just finished building a kernel from linux-source-3.13.0=3.13.0-37.64 w/this patch reversed and will deploy it to see if the problem is alleviated. thank you for your time and effort. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 18 13:11 seq crw-rw 1 root audio 116, 33 Oct 18 13:11 timer AplayDevices: aplay: device_list:268: no soundcards found... ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 ArecordDevices: arecord: device_list:268: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Tue Oct 21 12:55:43 2014 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro X8DT6 PciMultimedia: ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=/dev/md0 ro consoleblank=0 console=tty0 console=ttyS2,115200n8 nomdmonddf nomdmonisw bootdegraded=true RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0c dmi.board.asset.tag: 1234567890 dmi.board.name: X8DT6 dmi.board.vendor: Supermicro dmi.board.version: 1234567890 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 1234567890 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0c:bd05/15/2012:svnSupermicro:pnX8DT6:pvr1234567890:rvnSupermicro:rnX8DT6:rvr1234567890:cvnSupermicro:ct17:cvr1234567890: dmi.product.name: X8DT6 dmi.product.version: 1234567890 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383921/+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 1426043] Re: kernel 3.13.0-46.75 and 3.16.0-31.41 fails to boot on arm64
** Changed in: linux (Ubuntu)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1426043
Title:
kernel 3.13.0-46.75 and 3.16.0-31.41 fails to boot on arm64
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Trusty:
Fix Released
Bug description:
The failure is:
BUG: failure at
/build/buildd/linux-3.13.0/arch/arm64/include/asm/arch_timer.h:143/arch_counter_get_cntpct()!
which comes from this code:
static inline u64 arch_counter_get_cntpct(void)
{
/*
* AArch64 kernel and user space mandate the use of CNTVCT.
*/
BUG();
return 0;
}
The -46 kernel includes commit 800a366 (corresponding to upstream
commit 0b46b8a) clocksource: arch_timer: Fix code to use physical
timers when requested. This was added to fix clock problems on certain
ARMv7 systems. Unfortunately, it also appears to break ARMv8 systems.
The upstream commit which fixes the ARMv8 breakage from commit 0b46b8a
is d6ad369 clocksource: arch_timer: Only use the virtual counter
(CNTVCT) on arm64. This commit appears not to have been backported to
Trusty.
Here is a full boot log of the failure:
Starting kernel ...
L3C: 8MB
[ 0.00] Initializing cgroup subsys cpuset
[ 0.00] Initializing cgroup subsys cpu
[ 0.00] Initializing cgroup subsys cpuacct
[ 0.00] Linux version 3.13.0-46-generic (buildd@templar) (gcc version
4.8.2 (Ubuntu/Linaro 4.8.2-19ubuntu1) ) #75-Ubuntu SMP Tue Feb 10 21:12:09 UTC
2015 (Ubuntu 3.13.0-46.75-generic 3.13.11-ckt15)
[ 0.00] CPU: AArch64 Processor [500f0001] revision 1
[ 0.00] bootconsole [earlycon0] enabled
[ 0.00] On node 0 totalpages: 16777216
[ 0.00] Normal zone: 229376 pages used for memmap
[ 0.00] Normal zone: 16777216 pages, LIFO batch:31
[ 0.00] PERCPU: Embedded 12 pages/cpu @ffc72000 s17088 r8192
d23872 u49152
[ 0.00] pcpu-alloc: s17088 r8192 d23872 u49152 alloc=12*4096
[ 0.00] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5 [0] 6 [0] 7
[ 0.00] Built 1 zonelists in Zone order, mobility grouping on. Total
pages: 16547840
[ 0.00] Kernel command line: console=ttyS0,9600n8r ro
earlyprintk=uart8250-32bit,0x1c021000 debug
[ 0.00] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.00] Dentry cache hash table entries: 8388608 (order: 14, 67108864
bytes)
[ 0.00] Inode-cache hash table entries: 4194304 (order: 13, 33554432
bytes)
[ 0.00] software IO TLB [mem 0x4fbc80-0x4fc080] (64MB) mapped at
[ffcfbc80-ffcfc07f]
[ 0.00] Memory: 65994264K/67108864K available (5718K kernel code, 590K
rwdata, 2536K rodata, 304K init, 538K bss, 1114600K reserved)
[ 0.00] Virtual kernel memory layout:
[ 0.00] vmalloc : 0xff80 - 0xffbb (245759 MB)
[ 0.00] vmemmap : 0xffbce000 - 0xffbd1800 ( 896 MB)
[ 0.00] modules : 0xffbffc00 - 0xffc0 ( 64 MB)
[ 0.00] memory : 0xffc0 - 0xffd0 ( 65536 MB)
[ 0.00] .init : 0xffc000891000 - 0xffc0008dd2c0 ( 305 kB)
[ 0.00] .text : 0xffc8 - 0xffc0008909b4 ( 8259 kB)
[ 0.00] .data : 0xffc0008de000 - 0xffc000971848 ( 591 kB)
[ 0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
[ 0.00] Hierarchical RCU implementation.
[ 0.00] RCU dyntick-idle grace-period acceleration is enabled.
[ 0.00] NR_IRQS:64 nr_irqs:64 0
[ 0.00] Architected cp15 timer(s) running at 50.00MHz (phys).
[ 0.00] BUG: failure at
/build/buildd/linux-3.13.0/arch/arm64/include/asm/arch_timer.h:143/arch_counter_get_cntpct()!
[ 0.00] Kernel panic - not syncing: BUG!
[ 0.00] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.13.0-46-generic
#75-Ubuntu
[ 0.00] Call trace:
[ 0.00] [] dump_backtrace+0x0/0x16c
[ 0.00] [] show_stack+0x10/0x1c
[ 0.00] [] dump_stack+0x74/0x94
[ 0.00] [] panic+0xe0/0x20c
[ 0.00] [] arch_counter_get_cntpct+0x30/0x34
[ 0.00] [] arch_timer_common_init+0x1d4/0x244
[ 0.00] [] arch_timer_init+0x244/0x260
[ 0.00] [] clocksource_of_init+0x44/0x6c
[ 0.00] [] time_init+0x8/0x38
[ 0.00] [] start_kernel+0x200/0x360
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1426043/+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 1720867] Re: Trusty NVMe boot fails on some systems
** Changed in: linux (Ubuntu) Status: In Progress => 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/1720867 Title: Trusty NVMe boot fails on some systems Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Bug description: Trusty linux (3.13) fails to boot on some NVMe-based cloud instance types. [Impact] * Ubuntu trusty images can't be used on some NVMe-based cloud instance types. * Mainline commit a522905 "NVMe: Always use MSI/MSI-x interrupts" fixes the issue; application of this to 3.13 requires a set of prerequisite patches, and a minor backport. a522905 NVMe: Always use MSI/MSI-x interrupts e32efbf NVMe: make setup work for devices that don't do INTx be577fa nvme: Use pci_enable_msi_range() and pci_enable_msix_range() 42f6142 NVMe: per-cpu io queues 4f5099a NVMe: IOCTL path RCU protect queue access 5a92e70 NVMe: RCU protected access to io queues [Test Case] * Verify that a trusty-based image can boot on the affected instance type. [Regression Potential] * This change set affects all users of the NVMe driver, so regression potential is moderate to high. Additional soak testing may be warranted before merging this patch set. * The patched NVMe driver has been exercised by Dan Streetman, and given the thumbs-up. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720867/+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 1835350] Re: Hang / zombie process from Xarray page-fault conversion
Both of these two commits were applied in Ubuntu Eoan 5.3 kernel. Closing this bug. ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Committed ** 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/1835350 Title: Hang / zombie process from Xarray page-fault conversion Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Description: We're seeing a case where RocksDB hangs and becomes defunct when trying to kill the process. v4.19 succeeds and v4.20 fails. Robert was able to bisect this to commit b15cd800682f "dax: Convert page fault handlers to XArray". Target Release: 19.10 Target Kernel: 5.3 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1835350/+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 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
** 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/1777338
Title:
Linux 4.15.0-23 crashes during the boot process with a "Unable to
handle kernel NULL pointer dereference" message
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
== SRU Justification ==
Mainline commit 1f50ddb4f418 introduced a regression. That commit added
speculative_store_bypass_ht_init() to the per-CPU initialization sequence.
However, speculative_store_bypass_ht_init() needs to be called on each CPU for
PV guests, as well.
The regresssion prevents systems from booting.
The patch to fix this regression has also been cc'd to upstream stable,
but it has not landed in Bionic as of yet.
== Fix ==
74899d92e666 ("x86/xen: Add call of speculative_store_bypass_ht_init() to PV
paths")
== Regression Potential ==
Low. This patch fixes a current regressionThis patch has also been
submitted to upstream stable, so it has had additional upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
I went to boot my computer today and it wouldn't boot.
I get an "Unable to handle kernel NULL pointer dereference" message
during the boot process, and, a bit after that, a message from the
kernel watchdog about CPU #0 being stuck. Then the boot process stops
completely.
I was able to boot the system by telling Grub to load 4.15.0-22, which
works perfectly fine, so there has been a regression.
I am running Ubuntu as a Xen dom0, if that matters. I haven't tried
booting the offending kernel version without Xen.
I'm not sure where, if anywhere, these messages go on disk, for
posting.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-23-generic 4.15.0-23.25
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun 17 10:12:58 2018
InstallationDate: Installed on 2017-08-06 (314 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed
UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+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 1639810] Re: igb i210 probe of pci device failed with error -2
** Changed in: linux (Ubuntu) Status: In Progress => 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/1639810 Title: igb i210 probe of pci device failed with error -2 Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: [Impact] Intel I210 NIC may show: 'igb: probe of :07:00.0 failed with error -2' Upon boot after power has been completely disconnected. I was able to bisect it down to commit 2a3cdead8b408351fa1e3079b220fa331480ffbc Upon further investigation it was determined that firmware may not properly initialize I347AT4_PAGE_SELECT causing the probe of an igb i210 NIC to fail. This also happens with the linux 4.9-rc4. [Fix] https://patchwork.ozlabs.org/patch/690464/ This patch adds an addition zeroing of this register during igb_get_phy_id to workaround this issue. [Test Case] Completely power down machine with intel igb 210 NIC. Power on and ensure igb device is properly probed and initialized. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1639810/+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 1747769] Re: Cherry pick c96f5471ce7d for delayacct fix
c96f5471ce7d and its following fix has been applied to Bionic.
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu Bionic)
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/1747769
Title:
Cherry pick c96f5471ce7d for delayacct fix
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Artful:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
== SRU Justification ==
Mainline commit e33a9bba85a8 introduced a regression in v4.11-rc1. This
regression
caused delayacct_blkio_end() to be called by try_to_wake_up().
However, the call was made before we have context-switched. This patch is now
correct, in that
the delay accounting ends when the I/O is complete.
Commit c96f5471ce7 is in mainline as fo v4.15-rc9.
== Fix ==
commit c96f5471ce7d2aefd0dda560cc23f08ab00bc65d
Author: Josh Snyder
Date: Mon Dec 18 16:15:10 2017 +
delayacct: Account blkio completion on the correct task
== Regression Potential ==
Low. This commit has also been cc'd to stable, so it has had additional
upstream
review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
Please cherry pick upstream commit c96f5471ce7d ("delayacct: Account
blkio completion on the correct task") into the Ubuntu 4.13 kernel. It
has also been accepted into the Linux stable branch as 4.14.15.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747769/+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 1836816] Re: Fix nf_conntrack races when dealing with same origin requests in NAT environments
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836816 Title: Fix nf_conntrack races when dealing with same origin requests in NAT environments Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Won't Fix Bug description: BugLink: https://bugs.launchpad.net/bugs/1836816 [Impact] There are a number of races in nf_conntrack when multiple packets are sent from the same origin to the same destination at the same time, where there is no pre-existing confirmed conntrack entry, in a NAT environment. This is most frequently seen in users with kubernetes workloads, where dns requests are sent from the same socket at the same time, from different threads. One request is for a A record, the other . A conntrack race happens, which leads to one request being dropped, which leads to 5 second dns timeouts. This problem is not specific to kubernetes, as any multi-threaded process which sends UDP packets from the same socket at the same time from different threads is affected. Note that since UDP is connectionless, no packet is sent when connect() is called, so no conntrack entries are created until a packet is first sent. In the scenario where two UDP packets are sent at the same time from the same socket on different threads, there are the following possible races: 1.) Neither of the packets find a confirmed conntrack entry. This leads to two conntrack entries being created with the same tuples. 2.) Same as 1), but a conntrack entry is confirmed for one of the packets before the other calls get_unique_tuple(). The other packet gets a different reply tuple with the source port changed. The outcomes of the races are the same, one of the packets is dropped when it comes time to confirm conntrack entries with __nf_conntrack_confirm(). For more information, read the technical blog post: https://www.weave.works/blog/racy-conntrack-and-dns-lookup-timeouts [Fix] The fix to race 1) was included in 4.19 upstream by this commit: netfilter: nf_conntrack: resolve clash for matching conntracks commit ed07d9a021df6da53456663a76999189badc432a Author: Martynas Pumputis Date: Mon Jul 2 16:52:14 2018 +0200 This commit adds an extra check to see if the two entries are the same and to merge the entries if they are. The fix to race 2) was included in 5.0 upstream by this commit: netfilter: nf_nat: skip nat clash resolution for same-origin entries commit 4e35c1cb9460240e983a01745b5f29fe3a4d8e39 Author: Martynas Pumputis Date: Tue Jan 29 15:51:42 2019 +0100 This commit ensures that a new source port is not allocated to a duplicated entry, and forwards the duplicated entries to be resolved later on. Note that 4e35c1cb9460240e983a01745b5f29fe3a4d8e39 was also backported to stable releases 4.9.163, 4.14.106, 4.19.29, 4.20.16. Both commits cherry-pick to 4.15 bionic cleanly. Please cherry-pick both commits to all bionic kernels. [Testcase] The reproducer has been provided by the author of the fixes, and is best viewed here: https://github.com/brb/conntrack-race The dmesg logs and packet traces in the above github repo are best viewed while reading upstream discussion: https://patchwork.ozlabs.org/patch/937963/ I have built a test kernel for xenial HWE, which can be found here: https://launchpad.net/~mruffell/+archive/ubuntu/sf00227747-test-kernel The test kernel has been tested with a kubernetes workload and aided with resolution of kubernetes problems. [Regression Potential] As noted previously, 4e35c1cb9460240e983a01745b5f29fe3a4d8e39 has been backported to stable releases 4.9.163, 4.14.106, 4.19.29, 4.20.16 and has no changes to the primary commit. This commit is well tested and considered stable by the community. Both commits have also been present in the -azure kernels since 4.15.0-1030.31 and 4.18.0-1004.4, as per LP #1795493, http://bugs.launchpad.net/bugs/1795493 They have received wide testing, and no problems have been reported. The changes are specifically limited to resolving clashes between duplicate conntrack entries, and any regressions will be limited to that scenario. The overall risk of regression is very low. [Notes] The commits in the -azure kernels will need to be reverted before importing the generic bionic updates, since they are the pre-upstream commits, and have had several revisions since they were imported. Replacing them with the actual upstream commits will make things easier in the future to maintain. http://bugs.launchpad.net/bugs/1795493 For race 1): Azure: https://patchwork.ozlabs.org/patch/937963/ Upstream: ed07d9a021df6da53456663a76999189badc432a
[Kernel-packages] [Bug 1834465] Re: ipv6: fix neighbour resolution with raw socket
** Changed in: linux (Ubuntu) Status: In Progress => 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/1834465 Title: ipv6: fix neighbour resolution with raw socket Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Bug description: [SRU Justification] == Impact == IPv6 packets may be dropped during the neighbor resolution when a userspace program uses IPv6 raw sockets. The commit that introduces this bug has not been identified, but it's here at least from Xenial (4.4). This was fixed in the requested backport (from 5.2). == Fix == Backport the requested patches to Disco (5.0), Bionic (4.15) and Xenial (4.4). == Risk of Regregression == The change slightly modifies the target IPv6 address in neighbor resolution engine. Risk should be low and limited to ipv6. --- With an IPv6 raw socket, packets may be dropped during the neighbour resolution. It is fixed upstream by these patches: 9b1c1ef13b35 ipv6: constify rt6_nexthop() 2c6b55f45d53 ipv6: fix neighbour resolution with raw socket https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=9b1c1ef13b35fa35051b635ca9fbda39fe6bbc70 https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=2c6b55f45d53420d8310d41310e0e2cd41fe073f The detail of the bug is explained in the second patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834465/+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 1833698] Re: Bluetooth regressions with Xenial kernel 4.4.0-152.179
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1833698 Title: Bluetooth regressions with Xenial kernel 4.4.0-152.179 Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: [Impact] The Certification Team is reporting regressions with the Bluetooth testcases with all Xenial kernels derivatives of 4.4.0-152.179. The suspected commit is "d5bb334a8e17 Bluetooth: Align minimum encryption key size for LE and BR/EDR connections". https://www.spinics.net/lists/linux-bluetooth/msg80148.html https://lkml.org/lkml/2019/6/13/1037 [Test Case] Certification Team test suite. [Fix] Revert the introducing commit, as done upstream on stable branch linux-5.1.y by Greg K-H: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.1.y=b528880e8b0167c34cb36c1b4e6165192f76267c [Regression Risk] Low. Reverts a commit that's known to have cause problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833698/+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 1809224] Re: To support Intel Wireless-AX 22000 series
** Changed in: linux (Ubuntu) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809224 Title: To support Intel Wireless-AX 22000 series Status in linux package in Ubuntu: Won't Fix Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Won't Fix Status in linux-oem-osp1 source package in Disco: Fix Released Status in linux source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Invalid Bug description: [Impact] New Intel Cyclone Peak Wifi doesn't work without newly added driver. [Fix] Cherry pick iwlwifi commits from v5.0 to v5.1, and confirmed with proper firmware the wifi works. [Test] Verified on AX200NGW & 22560NGW chips & Killer 1653 card, wifi works well. [Regression Potential] Medium, it affects the whole iwlwifi driver, but I've verified it with fwst S3 test, and the wifi is still working after S3 test 30 times. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809224/+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 1841483] Re: Additional regression in CMA allocation rework
** 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/1841483 Title: Additional regression in CMA allocation rework Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Bug description: Introduced by the fixes for bug 1823753. Also related - bug 1839395. [Impact] There is an upstream report that the CMA allocation rework we backported to disco is breaking the ath10k wireless driver - and possibly other drivers - in certain configs. It is not clear if Ubuntu users have been impacted by this regression, I just noticed that it has a Fixes: reference in the git commit. [Test Case] Regression tested only. [Fix] 90ae409f9eb3b dma-direct: fix zone selection after an unaddressable CMA allocation [Regression Risk] Regressions in this code generally cause drivers to fail due to unavailable memory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841483/+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 1857673] Re: System will auto resume from sleep on receiving LE ADV after paired with BT LE devices (Intel 9560 HrP)
** Attachment added: "dmesg.4.15.0-1066-oem.REL0482" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1857673/+attachment/5315803/+files/dmesg.4.15.0-1066-oem.REL0482 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1857673 Title: System will auto resume from sleep on receiving LE ADV after paired with BT LE devices (Intel 9560 HrP) Status in HWE Next: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: In Progress Status in linux-firmware source package in Disco: Won't Fix Bug description: Similar to bug 1849779, on systems with Intel 9560 Bluetooth fw ver REL0450, deep suspend will be interrupted and resume automatically once it has been paired with a BLE device. The device doesn't have to remain connected, as long as there are BLE devices near by broadcasting LE ADV. This can be fixed by updating intel/ibt-17-16-1.sfi from upstream commit https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=b6427bf4faae9b8864e303d88c3ec8d0df017dac. Steps to reproduce: 1. pair with BLE device and turn off the device. It should be listed as Disconnected in System Bluetooth settings. Close the settings app as well. 2. run `sudo btmon -t` in the background, make sure LE ADV packets pop up. 3. run `sudo btmon -t` on another host to make sure there are LE ADV packets during the suspend period. 3. trigger system deep suspend (S3) on DUT. 4. wait for around 1 minutes (depending on the surrounding environment) and see if the DUT is resumed unsolicitedly. Expects: DUT only resumes when power button pressed or on other explicit requests. Actual: DUT resumes unsolicitedly within 1 minutes. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Dependencies: DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.14 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-1066.76-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1066-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1857673/+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 1857673] Re: System will auto resume from sleep on receiving LE ADV after paired with BT LE devices (Intel 9560 HrP)
https://lists.ubuntu.com/archives/kernel-team/2019-December/106557.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1857673 Title: System will auto resume from sleep on receiving LE ADV after paired with BT LE devices (Intel 9560 HrP) Status in HWE Next: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: In Progress Status in linux-firmware source package in Disco: Won't Fix Bug description: Similar to bug 1849779, on systems with Intel 9560 Bluetooth fw ver REL0450, deep suspend will be interrupted and resume automatically once it has been paired with a BLE device. The device doesn't have to remain connected, as long as there are BLE devices near by broadcasting LE ADV. This can be fixed by updating intel/ibt-17-16-1.sfi from upstream commit https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=b6427bf4faae9b8864e303d88c3ec8d0df017dac. Steps to reproduce: 1. pair with BLE device and turn off the device. It should be listed as Disconnected in System Bluetooth settings. Close the settings app as well. 2. run `sudo btmon -t` in the background, make sure LE ADV packets pop up. 3. run `sudo btmon -t` on another host to make sure there are LE ADV packets during the suspend period. 3. trigger system deep suspend (S3) on DUT. 4. wait for around 1 minutes (depending on the surrounding environment) and see if the DUT is resumed unsolicitedly. Expects: DUT only resumes when power button pressed or on other explicit requests. Actual: DUT resumes unsolicitedly within 1 minutes. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Dependencies: DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.14 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-1066.76-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1066-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1857673/+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 1843487] Re: UIO: mutex used in interrupt handler causes crash
** Changed in: linux (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1843487 Title: UIO: mutex used in interrupt handler causes crash Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Bug description: Running: Bionic Beaver Ubuntu 4.15.0-62.69-generic 4.15.18 Problem since: Ubuntu-4.15.0-59.66 In commit 725bbc87 on 2/13/2019 in uio.c a mutex_lock was added to uio_interrupt. This results in a "scheduling while atomic" error if someone else owns the mutex at the time it is invoked. The following commit in the kernel mainline appears to fix this issue: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3d27c4de8d4fb2d4099ff324671792aa2578c6f9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843487/+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 1842502] Re: TC filters are broken on Mellanox after upstream stable updates
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1842502
Title:
TC filters are broken on Mellanox after upstream stable updates
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Released
Bug description:
[Impact]
Mellanox TC filters don't work for some key rules after the Bionic
4.15 stable patchset 2019-07-12 update (LP: #1836426). The offending
commit is ("net/mlx5e: Set vlan masks for all offloaded TC rules").
This causes fatal network connectivity issues for projects that use
the Mellanox ConnectX 5 NIC.
[Test Case]
TBD.
[Fix]
Backport the following upstream commit (which fixes the offending commit) and
its prerequisites:
d3a80bb5a3ea ("net/mlx5e: Don't match on vlan non-existence if ethertype is
wildcarded")
[Regression Potential]
Low. Changes are isolated and limited to the mlx5_core driver and all
commits are in upstream stable v4.19.y.
[Original description]
The following upstream fix was missing from the latest upstream stable
update (LP: # and LP1839376: #1839213):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d3a80bb5a3eac311ddf28387402593977574460d
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842502/+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 1836971] Re: sched: Prevent CPU lockups when task groups take longer than the period
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1836971 Title: sched: Prevent CPU lockups when task groups take longer than the period Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/1836971 [Impact] On machines with extremely high CPU usage, parent task groups which have a large number of children can make the for loop in sched_cfs_period_timer() run until the watchdog fires when the cfs_period_us setting is too short. In this particular case, it is unlikely that the call to hrtimer_forward_now() will return 0, meaning the for loop is never left, and tasks are never rescheduled. The large number of children makes do_sched_cfs_period_timer() take longer than the period, which impacts calls to hrtimer_forward_now(). The kernel will produce this call trace: CPU: 51 PID: 0 Comm: swapper/51 Tainted: P OELK 4.15.0-50-generic #54-Ubuntu Call Trace: ? sched_clock+0x9/0x10 walk_tg_tree_from+0x61/0xd0 ? task_rq_unlock+0x30/0x30 unthrottle_cfs_rq+0xcb/0x1a0 distribute_cfs_runtime+0xd7/0x100 sched_cfs_period_timer+0xd9/0x1a0 ? sched_cfs_slack_timer+0xe0/0xe0 __hrtimer_run_queues+0xdf/0x230 hrtimer_interrupt+0xa0/0x1d0 smp_apic_timer_interrupt+0x6f/0x130 apic_timer_interrupt+0x84/0x90 This has been hit in production in a particularly highly utilised hadoop cluster which is powering an analytics platform. About 30% of the cluster experiences this issue every week, and the machines need a manual reboot to get back online. [Fix] This was fixed in 5.1 upstream with the below commit: commit 2e8e19226398db8265a8e675fcc0118b9e80c9e8 Author: Phil Auld Date: Tue Mar 19 09:00:05 2019 -0400 subject: sched/fair: Limit sched_cfs_period_timer() loop to avoid hard lockup This commit adds a check to see if the loop has run too many times, and if it has, scales up the period and quota, so the timer can complete before the next period expires, which enables the task to be rescheduled normally. Note, 2e8e19226398db8265a8e675fcc0118b9e80c9e8 was included in upstream stable versions 4.4.179, 4.9.171, 4.14.114, 4.19.37, 5.0.10. This patch requires minor backporting for 4.15, so please cherry pick d069fe4844f8d799d771659a745fe91870c93fda from upstream stable 4.14.y, where the backport has been done by the original author, to all bionic kernels. [Testcase] Kind of hard to reproduce, so this was tested on a production hadoop cluster with extremely high CPU load. I built a test kernel, which is available here: https://launchpad.net/~mruffell/+archive/ubuntu/sf232784-test For unpatched kernels, expect the machine to lockup and print the call trace in the impact section. For patched kernels, if the machine hits the condition, it will print a warning to the kernel log with the new period and quota which has been used: Example from the same hadoop cluster with a machine running the test kernel: % uname -a 4.15.0-50-generic #54+hf232784v20190626b1-Ubuntu % sudo grep cfs /var/log/kern.log.* cfs_period_timer[cpu40]: period too short, scaling up (new cfs_period_us 67872, cfs_quota_us = 3475091) cfs_period_timer[cpu48]: period too short, scaling up (new cfs_period_us 22430, cfs_quota_us = 1148437) cfs_period_timer[cpu48]: period too short, scaling up (new cfs_period_us 25759, cfs_quota_us = 1318908) cfs_period_timer[cpu68]: period too short, scaling up (new cfs_period_us 29583, cfs_quota_us = 1514684) cfs_period_timer[cpu49]: period too short, scaling up (new cfs_period_us 33974, cfs_quota_us = 1739519) cfs_period_timer[cpu3]: period too short, scaling up (new cfs_period_us 39017, cfs_quota_us = 1997729) cfs_period_timer[cpu10]: period too short, scaling up (new cfs_period_us 44809, cfs_quota_us = 2294267) cfs_period_timer[cpu3]: period too short, scaling up (new cfs_period_us 51460, cfs_quota_us = 2634823) cfs_period_timer[cpu3]: period too short, scaling up (new cfs_period_us 59099, cfs_quota_us = 3025929) cfs_period_timer[cpu3]: period too short, scaling up (new cfs_period_us 67872, cfs_quota_us = 3475091) [Regression Potential] This patch was accepted into upstream stable versions 4.4.179, 4.9.171, 4.14.114, 4.19.37, 5.0.10, and is thus treated as stable and trusted by the community. Xenial received this patch in 4.4.0-150.176, as per LP #1828420 Disco will receive this patch in the next version, as per LP #1830922 Eoan already has the patch, being based on 5.2. While this does effect a core part of the kernel, the scheduler, the patch has been extensively tested, and it has been proven in production environments, so the overall risk is low. To manage
[Kernel-packages] [Bug 1857673] Re: System will auto resume from sleep on receiving LE ADV after paired with BT LE devices (Intel 9560 HrP)
** Attachment added: "dmesg.4.15.0-1066-oem.REL0450" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1857673/+attachment/5315802/+files/dmesg.4.15.0-1066-oem.REL0450 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1857673 Title: System will auto resume from sleep on receiving LE ADV after paired with BT LE devices (Intel 9560 HrP) Status in HWE Next: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: In Progress Status in linux-firmware source package in Disco: Won't Fix Bug description: Similar to bug 1849779, on systems with Intel 9560 Bluetooth fw ver REL0450, deep suspend will be interrupted and resume automatically once it has been paired with a BLE device. The device doesn't have to remain connected, as long as there are BLE devices near by broadcasting LE ADV. This can be fixed by updating intel/ibt-17-16-1.sfi from upstream commit https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=b6427bf4faae9b8864e303d88c3ec8d0df017dac. Steps to reproduce: 1. pair with BLE device and turn off the device. It should be listed as Disconnected in System Bluetooth settings. Close the settings app as well. 2. run `sudo btmon -t` in the background, make sure LE ADV packets pop up. 3. run `sudo btmon -t` on another host to make sure there are LE ADV packets during the suspend period. 3. trigger system deep suspend (S3) on DUT. 4. wait for around 1 minutes (depending on the surrounding environment) and see if the DUT is resumed unsolicitedly. Expects: DUT only resumes when power button pressed or on other explicit requests. Actual: DUT resumes unsolicitedly within 1 minutes. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Dependencies: DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.14 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-1066.76-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1066-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1857673/+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 1851446] Re: Backport MPLS patches from 5.3 to 4.15
5dc9520b has landed in Eoan / Focal. Please give the following B/D kernel a try: https://people.canonical.com/~phlin/kernel/lp-1851446-MPLS/ They both contains: * 5dc9520b (net/mlx5e: Report netdevice MPLS features) * 8b6912a5 (net: vlan: Inherit MPLS features from parent device) * 2e770b50 (net: bonding: Inherit MPLS features from slave devices) Commit 600bb0318c18e9616d97ad123caaa7c5f7bf222c is a merge for the 2 commits above, and thus ignored. -- 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/1851446 Title: Backport MPLS patches from 5.3 to 4.15 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Disco: New Bug description: Mellanox is requesting a backport of the following commit IDs from 5.3 back to 4.15. Netdevice HW MPLS features are not passed from device driver's netdevice to upper netdevice, specifically VLAN and bonding netdevice which are created by the kernel when needed. This prevents enablement and usage of HW offloads, such as TSO and checksumming for MPLS tagged traffic when running via VLAN or bonding interface. The patches introduce changes to the initialization steps of the VLAN and bonding netdevices to inherit the MPLS features from lower netdevices to allow the HW offloads. Ariel Levkovich (2): net: bonding: Inherit MPLS features from slave devices net: vlan: Inherit MPLS features from parent device drivers/net/bonding/bond_main.c | 11 +++ net/8021q/vlan_dev.c| 1 + 2 files changed, 12 insertions(+) https://www.mail-archive.com/netdev@vger.kernel.org/msg299084.html Commit IDs (All landed in 5.3) 600bb0318c18e9616d97ad123caaa7c5f7bf222c 8b6912a5019356d7adb1b8a146c9eef5e679bf98 2e770b507ccde8eedc129946e4b78ceed0a22df2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851446/+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 1857673] Re: System will auto resume from sleep on receiving LE ADV after paired with BT LE devices (Intel 9560 HrP)
** Also affects: linux-firmware (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Bionic) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-firmware (Ubuntu) Status: In Progress => Invalid ** Also affects: linux-firmware (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Disco) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1857673 Title: System will auto resume from sleep on receiving LE ADV after paired with BT LE devices (Intel 9560 HrP) Status in HWE Next: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: In Progress Status in linux-firmware source package in Disco: Won't Fix Bug description: Similar to bug 1849779, on systems with Intel 9560 Bluetooth fw ver REL0450, deep suspend will be interrupted and resume automatically once it has been paired with a BLE device. The device doesn't have to remain connected, as long as there are BLE devices near by broadcasting LE ADV. This can be fixed by updating intel/ibt-17-16-1.sfi from upstream commit https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=b6427bf4faae9b8864e303d88c3ec8d0df017dac. Steps to reproduce: 1. pair with BLE device and turn off the device. It should be listed as Disconnected in System Bluetooth settings. Close the settings app as well. 2. run `sudo btmon -t` in the background, make sure LE ADV packets pop up. 3. run `sudo btmon -t` on another host to make sure there are LE ADV packets during the suspend period. 3. trigger system deep suspend (S3) on DUT. 4. wait for around 1 minutes (depending on the surrounding environment) and see if the DUT is resumed unsolicitedly. Expects: DUT only resumes when power button pressed or on other explicit requests. Actual: DUT resumes unsolicitedly within 1 minutes. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Dependencies: DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.14 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-1066.76-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1066-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1857673/+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 1857673] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1857673/+attachment/5315801/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1857673 Title: System will auto resume from sleep on receiving LE ADV after paired with BT LE devices (Intel 9560 HrP) Status in HWE Next: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: In Progress Status in linux-firmware source package in Disco: Won't Fix Bug description: Similar to bug 1849779, on systems with Intel 9560 Bluetooth fw ver REL0450, deep suspend will be interrupted and resume automatically once it has been paired with a BLE device. The device doesn't have to remain connected, as long as there are BLE devices near by broadcasting LE ADV. This can be fixed by updating intel/ibt-17-16-1.sfi from upstream commit https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=b6427bf4faae9b8864e303d88c3ec8d0df017dac. Steps to reproduce: 1. pair with BLE device and turn off the device. It should be listed as Disconnected in System Bluetooth settings. Close the settings app as well. 2. run `sudo btmon -t` in the background, make sure LE ADV packets pop up. 3. run `sudo btmon -t` on another host to make sure there are LE ADV packets during the suspend period. 3. trigger system deep suspend (S3) on DUT. 4. wait for around 1 minutes (depending on the surrounding environment) and see if the DUT is resumed unsolicitedly. Expects: DUT only resumes when power button pressed or on other explicit requests. Actual: DUT resumes unsolicitedly within 1 minutes. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Dependencies: DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.14 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-1066.76-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1066-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1857673/+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 1857673] Re: System will auto resume from sleep on receiving LE ADV after paired with BT LE devices (Intel 9560 HrP)
apport information ** Tags added: apport-collected bionic ** Description changed: Similar to bug 1849779, on systems with Intel 9560 Bluetooth fw ver REL0450, deep suspend will be interrupted and resume automatically once it has been paired with a BLE device. The device doesn't have to remain connected, as long as there are BLE devices near by broadcasting LE ADV. This can be fixed by updating intel/ibt-17-16-1.sfi from upstream commit https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=b6427bf4faae9b8864e303d88c3ec8d0df017dac. Steps to reproduce: 1. pair with BLE device and turn off the device. It should be listed as Disconnected in System Bluetooth settings. Close the settings app as well. 2. run `sudo btmon -t` in the background, make sure LE ADV packets pop up. 3. run `sudo btmon -t` on another host to make sure there are LE ADV packets during the suspend period. 3. trigger system deep suspend (S3) on DUT. 4. wait for around 1 minutes (depending on the surrounding environment) and see if the DUT is resumed unsolicitedly. Expects: DUT only resumes when power button pressed or on other explicit requests. Actual: DUT resumes unsolicitedly within 1 minutes. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.7 + Architecture: amd64 + Dependencies: + + DistroRelease: Ubuntu 18.04 + Package: linux-firmware 1.173.14 + PackageArchitecture: all + ProcVersionSignature: Ubuntu 4.15.0-1066.76-oem 4.15.18 + Tags: bionic + Uname: Linux 4.15.0-1066-oem x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1857673/+attachment/5315800/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1857673 Title: System will auto resume from sleep on receiving LE ADV after paired with BT LE devices (Intel 9560 HrP) Status in HWE Next: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: In Progress Status in linux-firmware source package in Disco: Won't Fix Bug description: Similar to bug 1849779, on systems with Intel 9560 Bluetooth fw ver REL0450, deep suspend will be interrupted and resume automatically once it has been paired with a BLE device. The device doesn't have to remain connected, as long as there are BLE devices near by broadcasting LE ADV. This can be fixed by updating intel/ibt-17-16-1.sfi from upstream commit https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=b6427bf4faae9b8864e303d88c3ec8d0df017dac. Steps to reproduce: 1. pair with BLE device and turn off the device. It should be listed as Disconnected in System Bluetooth settings. Close the settings app as well. 2. run `sudo btmon -t` in the background, make sure LE ADV packets pop up. 3. run `sudo btmon -t` on another host to make sure there are LE ADV packets during the suspend period. 3. trigger system deep suspend (S3) on DUT. 4. wait for around 1 minutes (depending on the surrounding environment) and see if the DUT is resumed unsolicitedly. Expects: DUT only resumes when power button pressed or on other explicit requests. Actual: DUT resumes unsolicitedly within 1 minutes. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Dependencies: DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.14 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-1066.76-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1066-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1857673/+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 1851340] Re: [mgag200] Ubuntu 19.10 upgrade results in invisible mouse cursor on Matrox G200eR2
Hello John,
thanks for the quick test, now we can confirm that this issue only exist in
Eoan 5.3.
Can you help us to test this kernel on Eoan?
https://people.canonical.com/~phlin/kernel/lp-1851340-mgag200-cursor/
It contains the following fixes:
a9c342ab drm/mgag200: Don't unpin the current cursor image's buffer.
cf578c8c drm/mgag200: Set cursor scanout address to correct BO
a0fd72d2 drm/mgag200: Pin displayed cursor BO to video memory
e61576c4 drm/mgag200: add in missing { } around if block
Thank you.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu Eoan)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1851340
Title:
[mgag200] Ubuntu 19.10 upgrade results in invisible mouse cursor on
Matrox G200eR2
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Eoan:
Confirmed
Bug description:
Following in place upgrade of Ubuntu 19.04 -> 19.10 I no longer have
visible cursor with my Gnone desktop.
I have found the same problem when upgrading 2 machines from Ubuntu
19.04 -> 19.10.
Reproducing problem is easy:
1. Open Ubuntu Update Window
2. Select "Upgrade"
3. On completion of update (after reboot) cursor is no longer visible.
4. This applies to display connected to VGA port on host with USB Keyboard +
Mouse
While the connected display has no visible cursor and so is usable, I
have always used X11VNC Server to provide network GUI access. On the
remote X11VNC display I see and can use the cursor.
This bug report is being sent via Remote X11VNC window, as I cannot
use the main VGA display window (due to lack of visible cursor)
I have done search online and thought that maybe issue was with my USB
Mighty Mouse, so I also tried with Logitech M100R USB Mouse. Same
result, no visible mouse cursor.
I have done: "grep usb /var/log/syslog" and can see many USB events,
including both Apple and Logitech mouse detection events.
NOTE:
Due to compatibility issue with X11VNC, I have disable Wayland on both
machines by adding the following option to: /etc/gdm3/custom.conf
WaylandEnable=false
Regards,
John Hartley.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 5 18:25:23 2019
DistUpgraded: 2019-11-05 15:20:04,402 ERROR got error from PostInstallScript
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: eoan
DistroVariant: ubuntu
GraphicsCard:
Matrox Electronics Systems Ltd. G200eR2 [102b:0534] (rev 01) (prog-if 00
[VGA controller])
Subsystem: Lenovo G200eR2 [1d49:0a01]
InstallationDate: Installed on 2018-12-17 (322 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
MachineType: LENOVO System x3650 M5: -[8871AC1]-
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic
root=UUID=3b8f415b-7e78-461c-83df-64f1f1a7826a ro ipv6.disable=1 quiet splash
iommu=1 intel_iommu=on ipv6.disable=1 vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to eoan on 2019-11-05 (0 days ago)
dmi.bios.date: 06/03/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: -[TCE140H-2.91]-
dmi.board.asset.tag: (none)
dmi.board.name: 01KN179
dmi.board.vendor: LENOVO
dmi.board.version: NULL
dmi.chassis.asset.tag: none
dmi.chassis.type: 23
dmi.chassis.vendor: LENOVO
dmi.chassis.version: none
dmi.modalias:
dmi:bvnLENOVO:bvr-[TCE140H-2.91]-:bd06/03/2019:svnLENOVO:pnSystemx3650M5-[8871AC1]-:pvr13:rvnLENOVO:rn01KN179:rvrNULL:cvnLENOVO:ct23:cvrnone:
dmi.product.family: System X
dmi.product.name: System x3650 M5: -[8871AC1]-
dmi.product.sku: (none)
dmi.product.version: 13
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851340/+subscriptions
--
Mailing list:
[Kernel-packages] [Bug 1851340] Re: [mgag200] Ubuntu 19.10 upgrade results in invisible mouse cursor on Matrox G200eR2
** Also affects: linux (Ubuntu Eoan) 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/1851340 Title: [mgag200] Ubuntu 19.10 upgrade results in invisible mouse cursor on Matrox G200eR2 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: New Bug description: Following in place upgrade of Ubuntu 19.04 -> 19.10 I no longer have visible cursor with my Gnone desktop. I have found the same problem when upgrading 2 machines from Ubuntu 19.04 -> 19.10. Reproducing problem is easy: 1. Open Ubuntu Update Window 2. Select "Upgrade" 3. On completion of update (after reboot) cursor is no longer visible. 4. This applies to display connected to VGA port on host with USB Keyboard + Mouse While the connected display has no visible cursor and so is usable, I have always used X11VNC Server to provide network GUI access. On the remote X11VNC display I see and can use the cursor. This bug report is being sent via Remote X11VNC window, as I cannot use the main VGA display window (due to lack of visible cursor) I have done search online and thought that maybe issue was with my USB Mighty Mouse, so I also tried with Logitech M100R USB Mouse. Same result, no visible mouse cursor. I have done: "grep usb /var/log/syslog" and can see many USB events, including both Apple and Logitech mouse detection events. NOTE: Due to compatibility issue with X11VNC, I have disable Wayland on both machines by adding the following option to: /etc/gdm3/custom.conf WaylandEnable=false Regards, John Hartley. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 5 18:25:23 2019 DistUpgraded: 2019-11-05 15:20:04,402 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu GraphicsCard: Matrox Electronics Systems Ltd. G200eR2 [102b:0534] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo G200eR2 [1d49:0a01] InstallationDate: Installed on 2018-12-17 (322 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO System x3650 M5: -[8871AC1]- ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=3b8f415b-7e78-461c-83df-64f1f1a7826a ro ipv6.disable=1 quiet splash iommu=1 intel_iommu=on ipv6.disable=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-11-05 (0 days ago) dmi.bios.date: 06/03/2019 dmi.bios.vendor: LENOVO dmi.bios.version: -[TCE140H-2.91]- dmi.board.asset.tag: (none) dmi.board.name: 01KN179 dmi.board.vendor: LENOVO dmi.board.version: NULL dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: LENOVO dmi.chassis.version: none dmi.modalias: dmi:bvnLENOVO:bvr-[TCE140H-2.91]-:bd06/03/2019:svnLENOVO:pnSystemx3650M5-[8871AC1]-:pvr13:rvnLENOVO:rn01KN179:rvrNULL:cvnLENOVO:ct23:cvrnone: dmi.product.family: System X dmi.product.name: System x3650 M5: -[8871AC1]- dmi.product.sku: (none) dmi.product.version: 13 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851340/+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 1857673] Re: System will auto resume from sleep on receiving LE ADV after paired with BT LE devices (Intel 9560 HrP)
** Tags added: oem-priority originate-from-1856797 stella ** Changed in: linux-firmware (Ubuntu) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-firmware (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1857673 Title: System will auto resume from sleep on receiving LE ADV after paired with BT LE devices (Intel 9560 HrP) Status in HWE Next: New Status in linux-firmware package in Ubuntu: In Progress Bug description: Similar to bug 1849779, on systems with Intel 9560 Bluetooth fw ver REL0450, deep suspend will be interrupted and resume automatically once it has been paired with a BLE device. The device doesn't have to remain connected, as long as there are BLE devices near by broadcasting LE ADV. This can be fixed by updating intel/ibt-17-16-1.sfi from upstream commit https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=b6427bf4faae9b8864e303d88c3ec8d0df017dac. Steps to reproduce: 1. pair with BLE device and turn off the device. It should be listed as Disconnected in System Bluetooth settings. Close the settings app as well. 2. run `sudo btmon -t` in the background, make sure LE ADV packets pop up. 3. run `sudo btmon -t` on another host to make sure there are LE ADV packets during the suspend period. 3. trigger system deep suspend (S3) on DUT. 4. wait for around 1 minutes (depending on the surrounding environment) and see if the DUT is resumed unsolicitedly. Expects: DUT only resumes when power button pressed or on other explicit requests. Actual: DUT resumes unsolicitedly within 1 minutes. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1857673/+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
