Re: [Kernel-packages] [Bug 1796730] Re: Ubuntu 18.10 regression: nvidia driver does not work
@NiBu what do you mean by: "Booting in recovery mode and resuming normal start works."? On Tue, 9 Oct 2018, 22:15 NiBu, <1796...@bugs.launchpad.net> wrote: > Booting in recovery mode and resuming normal start works. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1796730 > > Title: > Ubuntu 18.10 regression: nvidia driver does not work > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796730/+subscriptions > -- 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/1796730 Title: Ubuntu 18.10 regression: nvidia driver does not work Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: Problems started after upgrade to 18.10 and first reboot. Symptoms: * Login screen appears * After providing credentials desktop does not start --- Extra info for Bug 1796433 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Oct 8 20:01:33 2018 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (1005 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-05 (2 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796730/+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 1794110] Re: MPS (Max Payload Size) is not correctly programmed upon Hot Insertion NVMe PCIe SSD
@jsalisbury - Unfortunately we do not have that info in hand. I'll check if we can try getting it. I see the patches in HWE 4.18 kernel of 18.04.2. Thanks for including them in it. -- 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/1794110 Title: MPS (Max Payload Size) is not correctly programmed upon Hot Insertion NVMe PCIe SSD Status in The Dell-poweredge project: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: Max Payload Size for the NVMe device is not getting programmed correctly. The OS is trying to set the device MPS to match Root Port which is greater than Capability of Device, instead of looking for lowest common denominator. This is fixed in upstream kernel version 4.19. Below are the commits that fix the issue. Please help include them in Ubuntu releases. PCI: Skip MPS logic for Virtual Functions (VFs) https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2&id=3dbe97efe8bf450b183d6dee2305cbc032e6b8a4 PCI: Match Root Port's MPS to endpoint's MPSS as necessary https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2&id=9f0e89359775ee21fe1ea732e34edb52aef5addf To manage notifications about this bug go to: https://bugs.launchpad.net/dell-poweredge/+bug/1794110/+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 566914] Re: Bluetooth HID barcode reader drops digits (code128)
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- 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/566914 Title: Bluetooth HID barcode reader drops digits (code128) Status in bluez package in Ubuntu: Expired Bug description: Binary package hint: bluez I apologize is if this the wrong place or format for the report. This is my first bug report. An HID bluetooth barcode reader scanning Code128 barcodes (and possibly other symbologies) will drop repeating digits if they are less than 8 digits apart. This does NOT happen if the repeating digits are back to back. Example the number encoded in a code128 barcode then scanned with a bluetooth HID barcode reader: -"1234567890" will properly return "1234567890" -"10" will properly return "10" -"100" will properly return 100 (the repeating zero's are back to back, so no problem) -"1010" will IMPROPERLY return "10" -"10101" will IMPROPERLY return "10" -"101010" will IMPROPERLY return "10" -"1010101" will IMPROPERLY return "10" -"10101010" will IMPROPERLY return "100" (yes 100) The test system has a USB (Anycom or Trendnet) bluetooth USB dongles with an Intermec sf51 bluetooth HID barcode scanner successfully paired (as HID profile) to the Ubuntu system. Using USBMON in debug I can see the all of the proper digits coming across in hex. There are no dropped digits. I then used HCIDump and again saw all the digits coming across without loss. Using Showkey shows the problem I believe. Scanning the barcode "1010" shows this in showkey: keycode 2 press keycode 11 press keycode 2 release keycode 11 release Keycode 2 is "1" and Keycode 11 is "0". More complex numbers better illustrate the problem: Scanning the barcode "L003184192" returns "L00318492". The "1" is missing.This is what appears in showkey (I've added the ASCII letter after the "press" or "release" statement from showkey for this example text): keycode 42 press (shift) keycode 38 press (L) keycode 42 release (shift) keycode 38 release (L) keycode 11 press (0) keycode 11 release (0) keycode 11 press (0) keycode 4 press (3) keycode 2 press (1) keycode 9 press (8) keycode 5 press (4) keycode 10 press (10) keycode 11 release (0) keycode 4 release (3) keycode 2 release (1) keycode 9 release (8) keycode 5 release (4) keycode 10 release (9) keycode 3 press (2) keycode 3 release (2) What looks to be happening is that the missing "1" key is "pressed" at the beginning of the input and is not "released" in time to be "pressed" again. This bug has existed in Ubuntu in all versions I've tried back to 7.10 (and confirmed in 8.10, 9.04 and 10.2 beta). --- Architecture: i386 DistroRelease: Ubuntu 10.04 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318) InterestingModules: rfcomm sco bnep l2cap btusb bluetooth MachineType: Dell Computer Corporation Dimension 4550 Package: bluez 4.60-0ubuntu8 [modified: lib/udev/rules.d/97-bluetooth.rules] PackageArchitecture: i386 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-16-generic root=UUID=5e6ab2fa-2a8c-430a-89f3-63ffc056c7f8 ro quiet splash ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-16.25-generic Tags: lucid Uname: Linux 2.6.32-16-generic i686 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 09/23/2003 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A08 dmi.board.vendor: Dell Computer Corp. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA08:bd09/23/2003:svnDellComputerCorporation:pnDimension4550:pvr:rvnDellComputerCorp.:rn:rvr:cvnDellComputerCorporation:ct6:cvr: dmi.product.name: Dimension 4550 dmi.sys.vendor: Dell Computer Corporation hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:16:38:C9:95:4C ACL MTU: 1017:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:1863 acl:29 sco:0 events:45 errors:0 TX bytes:612 acl:10 sco:0 commands:33 errors:0 rfkill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/566914/+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 1797031] 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/1797031 Title: Touchscreen/stylus always reports 1% battery [patch] Status in linux package in Ubuntu: Confirmed Bug description: I have a Dell 5379 with a touchscreen that always reports 1% battery with the stylus. This pops up a low battery notification the first time I use the stylus after booting. The attached patch tells the kernel to ignore the battery on this particular device, since it appears to not report information correctly anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-36-generic 4.15.0-36.39 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trent 1734 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 9 22:42:47 2018 HibernationDevice: RESUME=UUID=aef6a948-4599-4581-99a2-44b7944d2d58 InstallationDate: Installed on 2018-05-10 (153 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:2361 Elan Microelectronics Corp. Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 0bda:5696 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5379 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 05G60G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn05G60G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797031/+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 1049266] Re: pairing Wii Balance Board not supported in 4.101
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]
** Changed in: bluez (Ubuntu)
Status: Incomplete => Expired
--
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/1049266
Title:
pairing Wii Balance Board not supported in 4.101
Status in bluez package in Ubuntu:
Expired
Bug description:
The following code in 4.101 checks whether a device should receive the
special Wii passkey:
vendor = btd_device_get_vendor(device);
product = btd_device_get_product(device);
device_get_name(device, name, sizeof(name));
name[sizeof(name) - 1] = 0;
if (g_str_equal(name, "Nintendo RVL-CNT-01") ||
(vendor == 0x057e && product == 0x0306)) {
However, this does not work for the Wii Balance Board, which reports
its name as "Nintendo RVL-WBC-01". I'd suggest to add a second
comparison with this string.
P.S. I haven't found any working upstream bug tracker, which is why I
report this here, hoping that somebody from upstream will pick it up.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1049266/+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 1797031] [NEW] Touchscreen/stylus always reports 1% battery [patch]
Public bug reported: I have a Dell 5379 with a touchscreen that always reports 1% battery with the stylus. This pops up a low battery notification the first time I use the stylus after booting. The attached patch tells the kernel to ignore the battery on this particular device, since it appears to not report information correctly anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-36-generic 4.15.0-36.39 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trent 1734 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 9 22:42:47 2018 HibernationDevice: RESUME=UUID=aef6a948-4599-4581-99a2-44b7944d2d58 InstallationDate: Installed on 2018-05-10 (153 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:2361 Elan Microelectronics Corp. Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 0bda:5696 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5379 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 05G60G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn05G60G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Patch added: "Ignore battery on a particular bad behaving touchscreen" https://bugs.launchpad.net/bugs/1797031/+attachment/5199355/+files/elan.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797031 Title: Touchscreen/stylus always reports 1% battery [patch] Status in linux package in Ubuntu: New Bug description: I have a Dell 5379 with a touchscreen that always reports 1% battery with the stylus. This pops up a low battery notification the first time I use the stylus after booting. The attached patch tells the kernel to ignore the battery on this particular device, since it appears to not report information correctly anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-36-generic 4.15.0-36.39 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trent 1734 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 9 22:42:47 2018 HibernationDevice: RESUME=UUID=aef6a948-4599-4581-99a2-44b7944d2d58 InstallationDate: Installed on 2018-05-10 (153 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:2361 Elan Microelectronics Corp. Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 0bda:5696 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5379 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 05G60G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn05G60G:rvrA00:cvnDe
[Kernel-packages] [Bug 1203565] Re: 045e:009c [H87-PRO] Microsoft Keyboard Elite for Bluetooth dead keys problem
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- 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/1203565 Title: 045e:009c [H87-PRO] Microsoft Keyboard Elite for Bluetooth dead keys problem Status in bluez package in Ubuntu: Expired Bug description: In Precise with 4.60 version of bluez I can pair my keyboard and mouse perfectly. === The problem is that dead keys of my keyboard (I mean -L or R- CTRL, ALT, SUPER, -L or R- SHIFT, ALT-GR) doesn't work with my current motherboard (whether application I opened, console included). It does work correctly with other motherboards. The new motherboard is an 1150 Haswell one from Asus. What I can say is : 1/ When booting, my BIOS recognize perfectly the dead keys of my keyboard, meaning that the bluetooth dongle or the motherboard is not directly concerned. 2/ When doing a second installation of Ubuntu, same problem. 3/ When trying the option 'keyboard layout' (whatever layout I choose), I don't see those dead keys flashing, meaning the system doesn't react at all when pressing them. 4/ By chance, I found another keyboard (same model, same brand), same problem, meaning the keyboard is not concerned (it works on the older motherboard, then it was poor chance that the keyboard broked just before reinstalling). 5/ Tried the setxkbmap command (with sudo or without), nothing's better 6/ Tried the xmodmap command, I see the 0x codes for Left SHIFT, all dead keys are there (see attachment) 7/ Normal keyboard (no wireless) works perfectly 8/ Put the dongle on an other usb slot doesn't change anything 9/ Command xev doesn't makes changes when pressing dead keys. For me it's clearly a Ubuntu's system bug, with my motherboard (Asus H87-PRO socket 1150). --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: syl4375 F...m rhythmbox CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'PAD'/'RME Digi96/8 PAD at 0xf400, irq 19' Mixer name : '' Components : '' Controls : 10 Simple ctrls : 6 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xf308 irq 17' Mixer name : 'Nvidia GPU 14 HDMI/DP' Components : 'HDA:10de0014,10de0101,00100100' Controls : 24 Simple ctrls : 4 Card2.Amixer.info: Card hw:2 'NVidia_1'/'HDA NVidia at 0xe308 irq 16' Mixer name : 'Nvidia GPU 0a HDMI/DP' Components : 'HDA:10de000a,10de0101,00100100' Controls : 24 Simple ctrls : 4 DistroRelease: Ubuntu 12.04 MachineType: ASUS All Series MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-36-generic root=UUID=d2f8f163-a1ee-4332-a910-d593309cd2a6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.5.0-36.57~precise1-generic 3.5.7.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.5.0-36-generic N/A linux-backports-modules-3.5.0-36-generic N/A linux-firmware1.79.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: precise running-unity Uname: Linux 3.5.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio bluetooth boinc cdrom dip lp lpadmin netdev plugdev sambashare scanner sudo video dmi.bios.date: 04/08/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd04/08/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87-PRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1203565/+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 1159358] Re: 04a9:1736 [HP Pavillion dm3-1109TU] USB Printer needs replug to work after boot
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (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/1159358 Title: 04a9:1736 [HP Pavillion dm3-1109TU] USB Printer needs replug to work after boot Status in cups package in Ubuntu: Expired Status in linux package in Ubuntu: Incomplete Bug description: While working a moment on LibreOffice Calc found that facts: - Print job was pending (printer not printing). Found that the printer was not working. Usually if the problem persists, plug out the USB cable and then plug in again. I don't find any solution other than replugging printer USB cable to wake up the printer. HP Pavillion dm3-1109TU Printer: Canon Pixma MX328 (driver: Canon PIXMA MX300 - CUPS+Gutenprint v5.2.8-pre1) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-39.62-generic-pae 3.2.39 Uname: Linux 3.2.0-39-generic-pae i686 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.1 Architecture: i386 CompizPlugins: [core,composite,opengl,imgjpeg,decor,imgpng,snap,obs,gnomecompat,vpswitch,compiztoolbox,resize,regex,dbus,mousepoll,grid,place,animation,move,session,workarounds,switcher,expo,wall,fade,scale] CompositorRunning: compiz Date: Sun Mar 24 15:55:26 2013 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, even including gdb or git bisection work if needed GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:3649] Subsystem: Hewlett-Packard Company Device [103c:3649] InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) MachineType: Hewlett-Packard HP Pavilion dm3 Notebook PC MarkForUpload: True ProcEnviron: PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-39-generic-pae root=UUID=2E2462FD2462C783 loop=/hostname/disks/root.disk ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2010 dmi.bios.vendor: Insyde Corp. dmi.bios.version: F.19 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3649 dmi.board.vendor: Hewlett-Packard dmi.board.version: 41.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrF.19:bd11/16/2010:svnHewlett-Packard:pnHPPaviliondm3NotebookPC:pvr048711241F1011012:rvnHewlett-Packard:rn3649:rvr41.3D:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dm3 Notebook PC dmi.product.version: 048711241F1011012 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.7.12-0ubuntu1 version.libdrm2: libdrm2 2.4.39-0ubuntu0.1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.4 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.12 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1159358/+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 1796443] Re: HP EliteBook 745 G5 (Ryzen 2500U) fails to boot unless `mce=off` is set on command line
Kernel linux-image-unsigned-4.19.0-999-generic_4.19.0-999.201810062200_amd64 still has this issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796443 Title: HP EliteBook 745 G5 (Ryzen 2500U) fails to boot unless `mce=off` is set on command line Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: My new Elitebook, with the latest bios 1.03.01, refuses to boot any kernel later than 4.10 unless mce=off is appended to the kernel command line. As in, there are no kernel messages at all after grub (yes, quiet and splash were removed from the command line). Perhaps it crashes before the efifb kicks in? System operates fine if mce=off is added to the kernel command line (and iommu=soft, but that's a separate issue, and fails with kernel output in that case). I opened upstream bug here : https://bugzilla.kernel.org/show_bug.cgi?id=201291 I bisected the problem down to this commit (and the few before it, which also added extra MCE output, but didn't actually crash): 18807ddb7f88d4ac3797302bafb18143d573e66f is the first bad commit commit 18807ddb7f88d4ac3797302bafb18143d573e66f Author: Yazen Ghannam Date: Tue Nov 15 15:13:53 2016 -0600 x86/mce/AMD: Reset Threshold Limit after logging error The error count field in MCA_MISC does not get reset by hardware when the threshold has been reached. Software is expected to reset it. Currently, the threshold limit only gets reset during init or when a user writes to sysfs. If the user is not monitoring threshold interrupts and resetting the limit then the user will only see 1 interrupt when the limit is first hit. So if, for example, the limit is set to 10 then only 1 interrupt will be recorded after 10 errors even if 100 errors have occurred. The user may then assume that only 10 errors have occurred. There are threads online about this being related to the latest bios. The upstream bug has acpidump attached. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2015 F pulseaudio /dev/snd/pcmC1D0p: john 2015 F...m pulseaudio /dev/snd/controlC0: john 2015 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Oct 5 23:24:45 2018 InstallationDate: Installed on 2018-09-30 (5 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) Lsusb: Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteBook 745 G5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=5cf73665-d2a3-4203-80fd-659faf1afea4 ro quiet splash iommu=soft mce=off RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: r8822be UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2018 dmi.bios.vendor: HP dmi.bios.version: Q81 Ver. 01.03.01 dmi.board.name: 83D5 dmi.board.vendor: HP dmi.board.version: KBC Version 08.47.00 dmi.chassis.asset.tag: 5CG838305Y dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ81Ver.01.03.01:bd07/26/2018:svnHP:pnHPEliteBook745G5:pvr:rvnHP:rn83D5:rvrKBCVersion08.47.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 745 G5 dmi.product.sku: 2MG23AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796443/+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 1796443] Re: HP EliteBook 745 G5 (Ryzen 2500U) fails to boot unless `mce=off` is set on command line
Changing as requested. ** Changed in: linux (Ubuntu) Status: Triaged => Confirmed ** Tags added: kernel-bug-exists-upstream -- 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/1796443 Title: HP EliteBook 745 G5 (Ryzen 2500U) fails to boot unless `mce=off` is set on command line Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: My new Elitebook, with the latest bios 1.03.01, refuses to boot any kernel later than 4.10 unless mce=off is appended to the kernel command line. As in, there are no kernel messages at all after grub (yes, quiet and splash were removed from the command line). Perhaps it crashes before the efifb kicks in? System operates fine if mce=off is added to the kernel command line (and iommu=soft, but that's a separate issue, and fails with kernel output in that case). I opened upstream bug here : https://bugzilla.kernel.org/show_bug.cgi?id=201291 I bisected the problem down to this commit (and the few before it, which also added extra MCE output, but didn't actually crash): 18807ddb7f88d4ac3797302bafb18143d573e66f is the first bad commit commit 18807ddb7f88d4ac3797302bafb18143d573e66f Author: Yazen Ghannam Date: Tue Nov 15 15:13:53 2016 -0600 x86/mce/AMD: Reset Threshold Limit after logging error The error count field in MCA_MISC does not get reset by hardware when the threshold has been reached. Software is expected to reset it. Currently, the threshold limit only gets reset during init or when a user writes to sysfs. If the user is not monitoring threshold interrupts and resetting the limit then the user will only see 1 interrupt when the limit is first hit. So if, for example, the limit is set to 10 then only 1 interrupt will be recorded after 10 errors even if 100 errors have occurred. The user may then assume that only 10 errors have occurred. There are threads online about this being related to the latest bios. The upstream bug has acpidump attached. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2015 F pulseaudio /dev/snd/pcmC1D0p: john 2015 F...m pulseaudio /dev/snd/controlC0: john 2015 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Oct 5 23:24:45 2018 InstallationDate: Installed on 2018-09-30 (5 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) Lsusb: Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteBook 745 G5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=5cf73665-d2a3-4203-80fd-659faf1afea4 ro quiet splash iommu=soft mce=off RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: r8822be UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2018 dmi.bios.vendor: HP dmi.bios.version: Q81 Ver. 01.03.01 dmi.board.name: 83D5 dmi.board.vendor: HP dmi.board.version: KBC Version 08.47.00 dmi.chassis.asset.tag: 5CG838305Y dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ81Ver.01.03.01:bd07/26/2018:svnHP:pnHPEliteBook745G5:pvr:rvnHP:rn83D5:rvrKBCVersion08.47.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 745 G5 dmi.product.sku: 2MG23AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796443/+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 1797002] 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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1797002 Title: all my bluetooth headsets skips terribly after todays update Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: all my bluetooth headsets skips terribly after today's system update. it is heavy noticeable even on audio setting test form. it work just fine today before i applied updates. even reinstall ubuntu from scratch - didn't help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) 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: ubuntu:GNOME Date: Tue Oct 9 18:40:44 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-09 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.66 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1968 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.52 dmi.chassis.asset.tag: 5CG32907G7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 088510305B0610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:17:29:62:BE:6A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:16831 acl:64 sco:0 events:1798 errors:0 TX bytes:688571 acl:2399 sco:0 commands:125 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1797002/+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 1797002] Re: all my bluetooth headsets skips terribly after todays update
The last bluez update was 3 months ago, so whatever changed for you recently it's not bluez. It's also not pulseaudio (4 months ago). Most likely this is related to the kernel update that was released 8 days ago. ** Changed in: bluez (Ubuntu) Status: New => Invalid ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1797002 Title: all my bluetooth headsets skips terribly after todays update Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: all my bluetooth headsets skips terribly after today's system update. it is heavy noticeable even on audio setting test form. it work just fine today before i applied updates. even reinstall ubuntu from scratch - didn't help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) 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: ubuntu:GNOME Date: Tue Oct 9 18:40:44 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-09 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.66 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1968 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.52 dmi.chassis.asset.tag: 5CG32907G7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 088510305B0610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:17:29:62:BE:6A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:16831 acl:64 sco:0 events:1798 errors:0 TX bytes:688571 acl:2399 sco:0 commands:125 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1797002/+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 713556] Re: Sharkoon Fireglider mouse is wrongly detected as a joystick
** Merge proposal unlinked: https://code.launchpad.net/~newell-jensen/maas/+git/maas/+merge/343053 -- 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/713556 Title: Sharkoon Fireglider mouse is wrongly detected as a joystick Status in udev: New Status in linux package in Ubuntu: Incomplete Bug description: Binary package hint: xserver-xorg-input-evdev I've been programming a game in SDL and I was surprised that SDL was reporting that 1 joystick was connected when there were none. SDL provides the name as "A4Tech USB Full Speed". "ls /dev/input" shows one joystick connected: by-idevent0 event2 event4 event6 event8 micemouse1 by-path event1 event3 event5 event7 js0 mouse0 lsusb shows my mouse as: Bus 003 Device 003: ID 09da:8090 A4 Tech Co., Ltd Unplugging the mouse makes /dev/input/js0 disappear. --- Architecture: amd64 DistroRelease: Ubuntu 10.10 InstallationMedia: elementary 0.2 Jupiter - Release i386 NonfreeKernelModules: fglrx Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash Tags: maverick Uname: Linux 2.6.37-02063706-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/udev/+bug/713556/+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 713556] Re: Sharkoon Fireglider mouse is wrongly detected as a joystick
** Merge proposal linked: https://code.launchpad.net/~newell-jensen/maas/+git/maas/+merge/343053 -- 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/713556 Title: Sharkoon Fireglider mouse is wrongly detected as a joystick Status in udev: New Status in linux package in Ubuntu: Incomplete Bug description: Binary package hint: xserver-xorg-input-evdev I've been programming a game in SDL and I was surprised that SDL was reporting that 1 joystick was connected when there were none. SDL provides the name as "A4Tech USB Full Speed". "ls /dev/input" shows one joystick connected: by-idevent0 event2 event4 event6 event8 micemouse1 by-path event1 event3 event5 event7 js0 mouse0 lsusb shows my mouse as: Bus 003 Device 003: ID 09da:8090 A4 Tech Co., Ltd Unplugging the mouse makes /dev/input/js0 disappear. --- Architecture: amd64 DistroRelease: Ubuntu 10.10 InstallationMedia: elementary 0.2 Jupiter - Release i386 NonfreeKernelModules: fglrx Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash Tags: maverick Uname: Linux 2.6.37-02063706-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/udev/+bug/713556/+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 713556] Re: Sharkoon Fireglider mouse is wrongly detected as a joystick
** Merge proposal unlinked: https://code.launchpad.net/~newell-jensen/maas/+git/maas/+merge/343053 -- 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/713556 Title: Sharkoon Fireglider mouse is wrongly detected as a joystick Status in udev: New Status in linux package in Ubuntu: Incomplete Bug description: Binary package hint: xserver-xorg-input-evdev I've been programming a game in SDL and I was surprised that SDL was reporting that 1 joystick was connected when there were none. SDL provides the name as "A4Tech USB Full Speed". "ls /dev/input" shows one joystick connected: by-idevent0 event2 event4 event6 event8 micemouse1 by-path event1 event3 event5 event7 js0 mouse0 lsusb shows my mouse as: Bus 003 Device 003: ID 09da:8090 A4 Tech Co., Ltd Unplugging the mouse makes /dev/input/js0 disappear. --- Architecture: amd64 DistroRelease: Ubuntu 10.10 InstallationMedia: elementary 0.2 Jupiter - Release i386 NonfreeKernelModules: fglrx Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash Tags: maverick Uname: Linux 2.6.37-02063706-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/udev/+bug/713556/+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 713556] Re: Sharkoon Fireglider mouse is wrongly detected as a joystick
** Merge proposal linked: https://code.launchpad.net/~newell-jensen/maas/+git/maas/+merge/343053 -- 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/713556 Title: Sharkoon Fireglider mouse is wrongly detected as a joystick Status in udev: New Status in linux package in Ubuntu: Incomplete Bug description: Binary package hint: xserver-xorg-input-evdev I've been programming a game in SDL and I was surprised that SDL was reporting that 1 joystick was connected when there were none. SDL provides the name as "A4Tech USB Full Speed". "ls /dev/input" shows one joystick connected: by-idevent0 event2 event4 event6 event8 micemouse1 by-path event1 event3 event5 event7 js0 mouse0 lsusb shows my mouse as: Bus 003 Device 003: ID 09da:8090 A4 Tech Co., Ltd Unplugging the mouse makes /dev/input/js0 disappear. --- Architecture: amd64 DistroRelease: Ubuntu 10.10 InstallationMedia: elementary 0.2 Jupiter - Release i386 NonfreeKernelModules: fglrx Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash Tags: maverick Uname: Linux 2.6.37-02063706-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/udev/+bug/713556/+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 1796895] Re: Kernel 4.15.0-36 network performance regression
Ok - for anyone that isn't used to installing kernels from proposed. It helps to install linux-image-generic and not linux-image-X-generic in order to pull in the modules package. Tested and verified - network speeds are back to normal in -37. -- 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/1796895 Title: Kernel 4.15.0-36 network performance regression Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: Hardware: HP DL380 Gen 7 server with Gigabit interface. Ubuntu release: 18.04.1 Since upgrading from 4.15.0-33 to 4.15.0-36, I have noticed a dramatic slowdown in TCP over IPv6. Set up: two servers, Server A in US on Ubuntu 18.04.1, Server B in Europe. Test: Sending 400MB over TCP from Server B to Server A. With 4.15.0-33 on Server A, the transfer is completed in 24 seconds, with average speed of 139 mbps. With 4.15.0-36 on Server A, the same amount of data is transferred in 369 seconds, average speed less than 9 mbps. Looking at the result from tcpdump, I see that the there is a big difference in the TCP Window size. With 3.15-0.33 the TCP window size is around 3. But with 3.15-0.36, the window size is only 734. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796895/+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 1793394] Re: hns3: enable ethtool rx-vlan-filter on supported hw
Verification (regression test only - we don't yet have the hw that supports the feature): ubuntu@d06-3:~$ cat /proc/version Linux version 4.15.0-37-generic (buildd@bos02-arm64-015) (gcc version 7.3.0 (Ubuntu/Linaro 7.3.0-16ubuntu3)) #40-Ubuntu SMP Tue Oct 2 15:36:22 UTC 2018 $ sudo ethtool -K enp125s0f2 rx-vlan-filter off Could not change any device features ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1793394 Title: hns3: enable ethtool rx-vlan-filter on supported hw Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: [Impact] Newer revisions of hns3 support toggling the rx-vlan-filter feature, but the driver does not allow it. [Test Case] Currently the command: $ sudo ethtool -K rx-vlan-filter off reports: Could not change any device features Even on hardware that supports this feature. [Fix] Apply this upstream commit: 3e85af6a6812d net: hns3: Add vlan filter setting by ethtool command -K [Regression Risk] I've regression tested on hns3 hardware that does not support this feature, and it worked as it should. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793394/+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 1797002] Re: all my bluetooth headsets skips terribly after todays update
Also side comment: `Architecture: amd64` - though i am using: Intel(R) Core(TM) i7-4702MQ CPU @ 2.20GHz -- 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/1797002 Title: all my bluetooth headsets skips terribly after todays update Status in bluez package in Ubuntu: New Bug description: all my bluetooth headsets skips terribly after today's system update. it is heavy noticeable even on audio setting test form. it work just fine today before i applied updates. even reinstall ubuntu from scratch - didn't help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) 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: ubuntu:GNOME Date: Tue Oct 9 18:40:44 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-09 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.66 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1968 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.52 dmi.chassis.asset.tag: 5CG32907G7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 088510305B0610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:17:29:62:BE:6A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:16831 acl:64 sco:0 events:1798 errors:0 TX bytes:688571 acl:2399 sco:0 commands:125 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1797002/+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 1796895] Re: Kernel 4.15.0-36 network performance regression
For whatever reason, after installing linux-image-4.15.0-37-generic the system boots up fine but doesn't appear to initialize the motherboard's built in realtek network adapter so there is no network connectivity to test. Is there a missing dependency in the package that needs to be installed to ensure that network connectivity works? -- 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/1796895 Title: Kernel 4.15.0-36 network performance regression Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: Hardware: HP DL380 Gen 7 server with Gigabit interface. Ubuntu release: 18.04.1 Since upgrading from 4.15.0-33 to 4.15.0-36, I have noticed a dramatic slowdown in TCP over IPv6. Set up: two servers, Server A in US on Ubuntu 18.04.1, Server B in Europe. Test: Sending 400MB over TCP from Server B to Server A. With 4.15.0-33 on Server A, the transfer is completed in 24 seconds, with average speed of 139 mbps. With 4.15.0-36 on Server A, the same amount of data is transferred in 369 seconds, average speed less than 9 mbps. Looking at the result from tcpdump, I see that the there is a big difference in the TCP Window size. With 3.15-0.33 the TCP window size is around 3. But with 3.15-0.36, the window size is only 734. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796895/+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 1797002] [NEW] all my bluetooth headsets skips terribly after todays update
Public bug reported: all my bluetooth headsets skips terribly after today's system update. it is heavy noticeable even on audio setting test form. it work just fine today before i applied updates. even reinstall ubuntu from scratch - didn't help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) 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: ubuntu:GNOME Date: Tue Oct 9 18:40:44 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-09 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.66 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1968 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.52 dmi.chassis.asset.tag: 5CG32907G7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 088510305B0610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0: Type: Primary Bus: USB BD Address: 68:17:29:62:BE:6A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:16831 acl:64 sco:0 events:1798 errors:0 TX bytes:688571 acl:2399 sco:0 commands:125 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1797002 Title: all my bluetooth headsets skips terribly after todays update Status in bluez package in Ubuntu: New Bug description: all my bluetooth headsets skips terribly after today's system update. it is heavy noticeable even on audio setting test form. it work just fine today before i applied updates. even reinstall ubuntu from scratch - didn't help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) 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: ubuntu:GNOME Date: Tue Oct 9 18:40:44 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-09 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.66 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1968 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.52 dmi.chassis.asset.tag: 5CG32907G7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 088510305B0610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:17:29:62:BE:6A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:16831 acl:64 sco:0 events:1798 errors:0 TX bytes:688571 acl:2399 sco:0 commands:125 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1797002/+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/Li
[Kernel-packages] [Bug 713556] Re: Sharkoon Fireglider mouse is wrongly detected as a joystick
** Merge proposal unlinked: https://code.launchpad.net/~newell-jensen/maas/+git/maas/+merge/343053 -- 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/713556 Title: Sharkoon Fireglider mouse is wrongly detected as a joystick Status in udev: New Status in linux package in Ubuntu: Incomplete Bug description: Binary package hint: xserver-xorg-input-evdev I've been programming a game in SDL and I was surprised that SDL was reporting that 1 joystick was connected when there were none. SDL provides the name as "A4Tech USB Full Speed". "ls /dev/input" shows one joystick connected: by-idevent0 event2 event4 event6 event8 micemouse1 by-path event1 event3 event5 event7 js0 mouse0 lsusb shows my mouse as: Bus 003 Device 003: ID 09da:8090 A4 Tech Co., Ltd Unplugging the mouse makes /dev/input/js0 disappear. --- Architecture: amd64 DistroRelease: Ubuntu 10.10 InstallationMedia: elementary 0.2 Jupiter - Release i386 NonfreeKernelModules: fglrx Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash Tags: maverick Uname: Linux 2.6.37-02063706-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/udev/+bug/713556/+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 713556] Re: Sharkoon Fireglider mouse is wrongly detected as a joystick
** Merge proposal linked: https://code.launchpad.net/~newell-jensen/maas/+git/maas/+merge/343053 -- 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/713556 Title: Sharkoon Fireglider mouse is wrongly detected as a joystick Status in udev: New Status in linux package in Ubuntu: Incomplete Bug description: Binary package hint: xserver-xorg-input-evdev I've been programming a game in SDL and I was surprised that SDL was reporting that 1 joystick was connected when there were none. SDL provides the name as "A4Tech USB Full Speed". "ls /dev/input" shows one joystick connected: by-idevent0 event2 event4 event6 event8 micemouse1 by-path event1 event3 event5 event7 js0 mouse0 lsusb shows my mouse as: Bus 003 Device 003: ID 09da:8090 A4 Tech Co., Ltd Unplugging the mouse makes /dev/input/js0 disappear. --- Architecture: amd64 DistroRelease: Ubuntu 10.10 InstallationMedia: elementary 0.2 Jupiter - Release i386 NonfreeKernelModules: fglrx Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash Tags: maverick Uname: Linux 2.6.37-02063706-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/udev/+bug/713556/+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 1796250] Re: sysfs test ubuntu_stress_smoke_test will cause kernel oops on X-lowlatency
The number of prerequisite fixes before we can apply the fix
748935eeb72c343 makes this a rather overly involved fix. I doubt it
will be SRU'able. Since this *only* occurs when accessing two TPM
related interfaces in a fast multiple multi-threaded race on a few
specific x86 devices as root makes this a very risky set of backport
changes for such a corner case.
For now, I'm going to force stress-ng sysfs test to skip the tpm files
for older kernels to workaround this issue. (Ugh).
Workaround committed in stress-ng:
http://kernel.ubuntu.com/git/cking/stress-
ng.git/commit/?id=c7fcb4112b97188c8fcba6138b29b5c5a82938ea
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
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/1796250
Title:
sysfs test ubuntu_stress_smoke_test will cause kernel oops on
X-lowlatency
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Fix Committed
Bug description:
This is found on a SRU testing node "gonzo", with 4.4 amd64 lowlatency
kernel.
This issue cannot be reproduced with the kernel 4.4.0-137 in -updates (a bit
random, see comment #4)
And cannot be reproduced with the AMD64 generic kernel in -proposed
(4.4.0-138) as well
16:50:01 DEBUG| [stdout] timer STARTING
16:50:05 ERROR| [stderr]
/home/ubuntu/autotest/client/tests/ubuntu_stress_smoke_test/ubuntu_stress_smoke_test.sh:
line 111: 39506 Killed ./stress-ng -v -t ${DURATION} --${s}
${INSTANCES} ${STRESS_OPTIONS} &> ${TMP_FILE}
16:50:05 DEBUG| [stdout] timer RETURNED 137
16:50:05 DEBUG| [stdout] timer FAILED (kernel oopsed)
16:50:05 DEBUG| [stdout] [ 1418.982110] BUG: unable to handle kernel paging
request at 00010001
16:50:05 DEBUG| [stdout] [ 1419.065329] IP: []
kmem_cache_alloc+0x77/0x1f0
16:50:05 DEBUG| [stdout] [ 1419.137102] PGD 16f6dd067 PUD 0
16:50:05 DEBUG| [stdout] [ 1419.175602] Oops: [#6] SMP
16:50:05 DEBUG| [stdout] [ 1419.214101] Modules linked in: unix_diag
binfmt_misc vhost_net vhost macvtap cuse macvlan dccp_ipv4 dccp
jitterentropy_rng algif_rng ghash_generic salsa20_generic salsa20_x86_64
camellia_generic camellia_aesni_avx_x86_64 camellia_x86_64 cast6_avx_x86_64
cast6_generic cast_common serpent_avx_x86_64 serpent_sse2_x86_64
serpent_generic twofish_generic twofish_avx_x86_64 twofish_x86_64_3way
twofish_x86_64 twofish_common xts algif_skcipher tgr192 wp512 rmd320 rmd256
rmd160 rmd128 md4 algif_hash af_alg aufs kvm_amd kvm ipmi_devintf ipmi_ssif
irqbypass dcdbas ipmi_si fam15h_power acpi_power_meter joydev input_leds
ipmi_msghandler serio_raw i2c_piix4 k10temp amd64_edac_mod 8250_fintek mac_hid
shpchp edac_mce_amd edac_core ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core
ib_addr iscsi_tcp libiscsi_tcp libiscsi
16:50:05 DEBUG| [stdout] [ 1420.062172] scsi_transport_iscsi autofs4 btrfs
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor
raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul
ghash_clmulni_intel mptsas mptscsih pata_acpi hid_generic aesni_intel
aes_x86_64 mptbase lrw gf128mul glue_helper psmouse ahci ablk_helper usbhid
cryptd pata_atiixp libahci scsi_transport_sas bnx2 hid
16:50:05 DEBUG| [stdout] [ 1420.472200] CPU: 3 PID: 39506 Comm:
ubuntu_stress_s Tainted: G D 4.4.0-138-generic #164-Ubuntu
16:50:05 DEBUG| [stdout] [ 1420.588693] Hardware name: Dell Inc. PowerEdge
R415/08WNM9, BIOS 1.9.3 04/26/2012
16:50:05 DEBUG| [stdout] [ 1420.678138] task: 880177823800 ti:
88016a5b task.ti: 88016a5b
16:50:05 DEBUG| [stdout] [ 1420.767584] RIP: 0010:[]
[] kmem_cache_alloc+0x77/0x1f0
16:50:05 DEBUG| [stdout] [ 1420.868478] RSP: 0018:88016a5b3bd0 EFLAGS:
00010202
16:50:05 DEBUG| [stdout] [ 1420.931924] RAX: RBX:
024000c0 RCX: 0129e216
16:50:05 DEBUG| [stdout] [ 1421.017209] RDX: 0129e215 RSI:
024000c0 RDI: 0001a5c0
16:50:05 DEBUG| [stdout] [ 1421.102496] RBP: 88016a5b3c00 R08:
8802156da5c0 R09: 00010001
16:50:05 DEBUG| [stdout] [ 1421.187782] R10: 88000ff0 R11:
0ff0 R12: 024000c0
16:50:05 DEBUG| [stdout] [ 1421.273070] R13: 811d53e8 R14:
880215003b00 R15: 880215003b00
16:50:05 DEBUG| [stdout] [ 1421.358354] FS: 7f1323076700()
GS:8802156c() knlGS:
16:50:05 DEBUG| [stdout] [ 1421.455081] CS: 0010 DS: ES: CR0:
80050033
16:50:05 DEBUG| [stdout] [ 1421.523728] CR2: 00010001 CR3:
00016f6dc000 CR4: 000406f0
16:50:05 DEBUG| [stdout] [ 1421.609013] Stack:
16:50:05 DEBUG| [stdout] [ 1421.632941] 88019c080a28
cfff
16:50:05 DEBUG| [stdout] [ 1421.721371] 7fffefec 88020ff29000
88016a5b3c38 f
[Kernel-packages] [Bug 1796647] Re: Shared folders cannot be mounted in ubuntu/cosmic64 due to missing vbox modules
The box certainly needs to be fixed. (In the meantime, a workaround if you _really_ need a cosmic box is probably to manually install the virtualbox-guest-dkms package; I haven't tested this locally though.) -- 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/1796647 Title: Shared folders cannot be mounted in ubuntu/cosmic64 due to missing vbox modules Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: In bionic, the vboxsf module was included in linux- modules-...-generic: $ dpkg -c linux-modules-4.15.0-36-generic_4.15.0-36.39_amd64.deb | grep vboxsf.ko -rw-r--r-- root/root 63238 2018-09-24 10:08 ./lib/modules/4.15.0-36-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko In cosmic, it isn't: $ dpkg -c ~/Downloads/linux- modules-4.18.0-9-generic_4.18.0-9.10_amd64.deb | grep vboxsf.ko This results in shared folders no longer being mountable in Ubuntu Vagrant boxes (and, as the other vbox modules are also missing, probably has other effects that haven't yet been reported). [Original Report] Just tried to test out the new cosmic64 vagrant box and get the following error; ``` Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available. This filesystem is made available via the VirtualBox Guest Additions and kernel module. Please verify that these guest additions are properly installed in the guest. This is not a bug in Vagrant and is usually caused by a faulty Vagrant box. For context, the command attempted was: mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant The error output from the command was: /sbin/mount.vboxsf: mounting failed with the error: No such device ``` I tried with ubuntu/bionic64 and it worked fine. I've got; $ vagrant version Installed Version: 2.1.5 Latest Version: 2.1.5 You're running an up-to-date version of Vagrant! $ VBoxManage --version 5.2.18r124319 $ To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1796647/+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 1763817] Re: [SRU][BIONIC] after enabling cppc dmesg fills with "ACPI CPPC: PCC check channel failed. Status=0"
>From playing around it appears about 300 seconds after boot. I was able to recreate this with kernel 4.15.0-29-generic but no longer after running apt upgrade and rebooting to the 4.15.0-36-generic 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/1763817 Title: [SRU][BIONIC] after enabling cppc dmesg fills with "ACPI CPPC: PCC check channel failed. Status=0" Status in linux package in Ubuntu: Incomplete Bug description: [Impact] On ARM64 systems enabling cppccontrol=1 in firmware, the dmesg fills with messages like: [ 4083.960332] ACPI CPPC: PCC check channel failed. Status=0 [ 4085.546975] ACPI CPPC: PCC check channel failed. Status=0 [ 4113.939921] ACPI CPPC: PCC check channel failed. Status=0 [ 4115.531777] ACPI CPPC: PCC check channel failed. Status=0 We lose any useful data in dmesg and on the console. [Fix] upstream commit fixes this issue: commit 3d41386d556db9f720e00de3e11e45f39cb5071c Author: George Cherian Date: Fri Mar 23 03:30:31 2018 -0700 cpufreq: CPPC: Use transition_delay_us depending transition_latency [Testing] -- before kernel patch -- Both console output and dmesg are filled with the message ACPI CPPC: PCC check channel failed. Status=0 [ 85.969952] ACPI CPPC: PCC check channel failed. Status=0 [ 81.888445] cloud-init[4810]: Cloud-init v. 18.2 running 'modules:final' at Fri, 13 Apr 2018 19:11:57 +. Up 80.71 seconds. [ 81.888625] cloud-init[4810]: Cloud-init v. 18.2 finished at Fri, 13 Apr 2018 19:11:58 +. Datasource DataSourceMAAS [http://10.228.68.5:5240/MAAS/metadata/]. Up 81.69 seconds [ OK ] Started Execute cloud user/final scripts. [ OK ] Reached target Cloud-init target. [ 86.230432] ACPI CPPC: PCC check channel failed. Status=0 [ 86.701943] ACPI CPPC: PCC check channel failed. Status=0 [ 86.773668] ACPI CPPC: PCC check channel failed. Status=0 [ 87.369958] ACPI CPPC: PCC check channel failed. Status=0 [ 87.733361] ACPI CPPC: PCC check channel failed. Status=0 [ 88.207372] ACPI CPPC: PCC check channel failed. Status=0 ubuntu@starbuck:~$ uname -a Linux starbuck 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:44:36 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux -- after kernel patch -- OK ] Started Apply the settings specified in cloud-config. Starting Execute cloud user/final scripts... [ 67.178425] cloud-init[3688]: Cloud-init v. 18.2 running 'modules:final' at Fri, 13 Apr 2018 20:41:15 +. Up 65.98 seconds. [ 67.200190] cloud-init[3688]: Cloud-init v. 18.2 finished at Fri, 13 Apr 2018 20:41:15 +. Datasource DataSourceMAAS [http://10.228.68.5:5240/MAAS/metadata/]. Up 66.83 seconds [ OK ] Started Execute cloud user/final scripts. [ OK ] Reached target Cloud-init target. Ubuntu Bionic Beaver (development branch) starbuck ttyAMA0 starbuck login: ubuntu@starbuck:~$ uname -a Linux starbuck 4.15.0-15-generic #16~lp1763817+build.1 SMP Fri Apr 13 19:54:10 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux [Regression Potential] None. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763817/+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 1796647] Re: Shared folders cannot be mounted in ubuntu/cosmic64 due to missing vbox modules
So I just go "vagrant init ubuntu/cosmic64 && vagrant up"... which works for all other vagrant I'm wanting to use. Does this mean the cosmic64 box needs to be fixed, or are you suggesting everyone needs to do custom config in their Vagrantfile to get it working? -- 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/1796647 Title: Shared folders cannot be mounted in ubuntu/cosmic64 due to missing vbox modules Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: In bionic, the vboxsf module was included in linux- modules-...-generic: $ dpkg -c linux-modules-4.15.0-36-generic_4.15.0-36.39_amd64.deb | grep vboxsf.ko -rw-r--r-- root/root 63238 2018-09-24 10:08 ./lib/modules/4.15.0-36-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko In cosmic, it isn't: $ dpkg -c ~/Downloads/linux- modules-4.18.0-9-generic_4.18.0-9.10_amd64.deb | grep vboxsf.ko This results in shared folders no longer being mountable in Ubuntu Vagrant boxes (and, as the other vbox modules are also missing, probably has other effects that haven't yet been reported). [Original Report] Just tried to test out the new cosmic64 vagrant box and get the following error; ``` Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available. This filesystem is made available via the VirtualBox Guest Additions and kernel module. Please verify that these guest additions are properly installed in the guest. This is not a bug in Vagrant and is usually caused by a faulty Vagrant box. For context, the command attempted was: mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant The error output from the command was: /sbin/mount.vboxsf: mounting failed with the error: No such device ``` I tried with ubuntu/bionic64 and it worked fine. I've got; $ vagrant version Installed Version: 2.1.5 Latest Version: 2.1.5 You're running an up-to-date version of Vagrant! $ VBoxManage --version 5.2.18r124319 $ To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1796647/+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 1796253] Re: With one flash drive connected other flash drive doesn't connect anymore
I have installed linux-image-4.19-rc7 along with linux-modules but with no result. The problem still exists. ** Tags added: kernel-bug-exists-upstream -- 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/1796253 Title: With one flash drive connected other flash drive doesn't connect anymore Status in linux package in Ubuntu: Incomplete Bug description: I have a Toshiba L855 laptop at home. When I connect any usb device to a USB3 port before boot then no other USB device doesn't work and even detected after boot. This concern even USB mouse and keyboard. But when I reconnect all USB devices to laptop then they started to work. I see this behaviour on every ubuntu 16.04.5 linux kernel i.e. version 4.15, so I suspect that it is due to some linux-extra-module. I have also windows 7 OS on the same laptop and I have never struck such a problem there. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-modules-extra-4.15.0-36-generic 4.15.0-36.39~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Fri Oct 5 12:17:20 2018 SourcePackage: linux-hwe UpgradeStatus: Upgraded to xenial on 2018-05-25 (132 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796253/+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 1796895] Re: Kernel 4.15.0-36 network performance regression
I installed the proposed kernel on a remote host and rebooted but of course the host didn't come back online for who only knows what reason. I'll post an update in a few hours once I have a chance to get my hands on it. -- 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/1796895 Title: Kernel 4.15.0-36 network performance regression Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: Hardware: HP DL380 Gen 7 server with Gigabit interface. Ubuntu release: 18.04.1 Since upgrading from 4.15.0-33 to 4.15.0-36, I have noticed a dramatic slowdown in TCP over IPv6. Set up: two servers, Server A in US on Ubuntu 18.04.1, Server B in Europe. Test: Sending 400MB over TCP from Server B to Server A. With 4.15.0-33 on Server A, the transfer is completed in 24 seconds, with average speed of 139 mbps. With 4.15.0-36 on Server A, the same amount of data is transferred in 369 seconds, average speed less than 9 mbps. Looking at the result from tcpdump, I see that the there is a big difference in the TCP Window size. With 3.15-0.33 the TCP window size is around 3. But with 3.15-0.36, the window size is only 734. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796895/+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 1763817] Re: [SRU][BIONIC] after enabling cppc dmesg fills with "ACPI CPPC: PCC check channel failed. Status=0"
I did a clean install of BIONIC via ubuntu-18.04.1-server-arm64.iso on an ARM system and encountered this on first boot. I am happy to send logs but apport-collect states that I am not the owner -- 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/1763817 Title: [SRU][BIONIC] after enabling cppc dmesg fills with "ACPI CPPC: PCC check channel failed. Status=0" Status in linux package in Ubuntu: Incomplete Bug description: [Impact] On ARM64 systems enabling cppccontrol=1 in firmware, the dmesg fills with messages like: [ 4083.960332] ACPI CPPC: PCC check channel failed. Status=0 [ 4085.546975] ACPI CPPC: PCC check channel failed. Status=0 [ 4113.939921] ACPI CPPC: PCC check channel failed. Status=0 [ 4115.531777] ACPI CPPC: PCC check channel failed. Status=0 We lose any useful data in dmesg and on the console. [Fix] upstream commit fixes this issue: commit 3d41386d556db9f720e00de3e11e45f39cb5071c Author: George Cherian Date: Fri Mar 23 03:30:31 2018 -0700 cpufreq: CPPC: Use transition_delay_us depending transition_latency [Testing] -- before kernel patch -- Both console output and dmesg are filled with the message ACPI CPPC: PCC check channel failed. Status=0 [ 85.969952] ACPI CPPC: PCC check channel failed. Status=0 [ 81.888445] cloud-init[4810]: Cloud-init v. 18.2 running 'modules:final' at Fri, 13 Apr 2018 19:11:57 +. Up 80.71 seconds. [ 81.888625] cloud-init[4810]: Cloud-init v. 18.2 finished at Fri, 13 Apr 2018 19:11:58 +. Datasource DataSourceMAAS [http://10.228.68.5:5240/MAAS/metadata/]. Up 81.69 seconds [ OK ] Started Execute cloud user/final scripts. [ OK ] Reached target Cloud-init target. [ 86.230432] ACPI CPPC: PCC check channel failed. Status=0 [ 86.701943] ACPI CPPC: PCC check channel failed. Status=0 [ 86.773668] ACPI CPPC: PCC check channel failed. Status=0 [ 87.369958] ACPI CPPC: PCC check channel failed. Status=0 [ 87.733361] ACPI CPPC: PCC check channel failed. Status=0 [ 88.207372] ACPI CPPC: PCC check channel failed. Status=0 ubuntu@starbuck:~$ uname -a Linux starbuck 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:44:36 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux -- after kernel patch -- OK ] Started Apply the settings specified in cloud-config. Starting Execute cloud user/final scripts... [ 67.178425] cloud-init[3688]: Cloud-init v. 18.2 running 'modules:final' at Fri, 13 Apr 2018 20:41:15 +. Up 65.98 seconds. [ 67.200190] cloud-init[3688]: Cloud-init v. 18.2 finished at Fri, 13 Apr 2018 20:41:15 +. Datasource DataSourceMAAS [http://10.228.68.5:5240/MAAS/metadata/]. Up 66.83 seconds [ OK ] Started Execute cloud user/final scripts. [ OK ] Reached target Cloud-init target. Ubuntu Bionic Beaver (development branch) starbuck ttyAMA0 starbuck login: ubuntu@starbuck:~$ uname -a Linux starbuck 4.15.0-15-generic #16~lp1763817+build.1 SMP Fri Apr 13 19:54:10 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux [Regression Potential] None. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763817/+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 1784878] Re: Backlight Not Functional - Origin EVO 15-S (Clevo)
Updated to 4.19-rc7 (uname -r = `4.19.0-041900rc7-generic`) with 'Ubuntu Kernel Update Utility'. Without any boot parameters, brightness still doesn't function (but UI shows it changing). Are there any other things you want me to try on this kernel? Unfortunately a lot of other things seemed to break on this kernel, including Nvidia modules, which didn't seem to compile. -- 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/1784878 Title: Backlight Not Functional - Origin EVO 15-S (Clevo) Status in linux package in Ubuntu: Triaged Bug description: Backlight slider moves, and values updated in /sys/class/backlight/intel_backlight/actual_brightness however, backlight does not actually change. Following https://wiki.ubuntu.com/Kernel/Debugging/Backlight attaching results of the procedure. Link to laptop in question: https://www.originpc.com/gaming/laptops/evo15-s/ I believe Origin uses Clevo laptops. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: dan2150 F...m pulseaudio /dev/snd/pcmC0D0p: dan2150 F...m pulseaudio /dev/snd/controlC0: dan2150 F pulseaudio /dev/snd/controlC1: dan2150 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Aug 1 10:26:58 2018 InstallationDate: Installed on 2018-07-30 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Notebook P95_HR ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=a800497f-73b5-4cd0-8555-3b66c8a3248a ro quiet splash nouveau.runpm=0 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_HR dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd07/14/2017:svnNotebook:pnP95_HR:pvrNotApplicable:rvnNotebook:rnP95_HR:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P95_HR dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784878/+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 1796730] Re: Ubuntu 18.10 regression: nvidia driver does not work
Booting in recovery mode and resuming normal start works. -- 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/1796730 Title: Ubuntu 18.10 regression: nvidia driver does not work Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: Problems started after upgrade to 18.10 and first reboot. Symptoms: * Login screen appears * After providing credentials desktop does not start --- Extra info for Bug 1796433 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Oct 8 20:01:33 2018 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (1005 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-05 (2 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796730/+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 1795292] Re: ELAN469D touch pad not working
Same here, touchpad not working in Ubuntu 18.04... on every kernel i tried curious facts: sudo acpidump | grep -C3 ELAN 5B10: 39 5F 48 49 44 00 A0 13 93 54 43 50 44 0A 02 A4 9_HIDTCPD... 5B20: 0D 53 59 4E 41 33 32 35 35 00 A0 13 93 54 43 50 .SYNA3255TCP 5B30: 44 0A 03 A4 0D 41 4C 50 53 31 32 31 45 00 A4 0D DALPS121E... 5B40: 45 4C 41 4E 34 36 39 44 00 08 45 49 43 30 11 21 ELAN469D..EIC0.! 5B50: 0A 1E 8E 19 00 01 00 01 02 00 00 01 06 00 80 1A 5B60: 06 00 15 00 5C 5F 53 42 2E 49 32 43 44 00 79 00 \_SB.I2CD.y. 5B70: 08 53 49 43 30 11 21 0A 1E 8E 19 00 01 00 01 02 .SIC0.!. You can see something related to ALPS In windows 10 it was not working too but installing Alps drivers solved the problem, dmesg | grep i2c [1.290277] i2c /dev entries driver [2.164938] i2c_hid i2c-ALPS121E:00: i2c-ALPS121E:00 supply vdd not found, using dummy regulator [3.196351] i2c_designware AMDI0010:01: controller timed out -- 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/1795292 Title: ELAN469D touch pad not working Status in linux package in Ubuntu: Confirmed Bug description: I installed Bionic Beaver and now upgraded to Cosmic Cuttlefish on this Lenovo Ideapad 330S-15ARR laptop. The touch pad doesn't work in either. Some possibly relevant info from dmesg: i2c_hid i2c-ELAN469D:00: i2c-ELAN469D:00 supply vdd not found, using dummy regulator i2c_designware AMDI0010:01: controller timed out ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-7-generic 4.18.0-7.8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xorbit 2086 F pulseaudio /dev/snd/pcmC1D0p: xorbit 2086 F...m pulseaudio /dev/snd/controlC0: xorbit 2086 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 30 23:14:26 2018 InstallationDate: Installed on 2018-09-20 (10 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81FB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic processor.max_cstate=1 rcu_nocbs=0-7 pcie_aspm=off pci=noaer quiet splash vt.handoff=1 elan_i2c.dyndbg=+p RelatedPackageVersions: linux-restricted-modules-4.18.0-7-generic N/A linux-backports-modules-4.18.0-7-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-09-30 (0 days ago) dmi.bios.date: 06/08/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7WCN22WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7WCN22WW:bd06/08/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR: dmi.product.family: ideapad 330S-15ARR dmi.product.name: 81FB dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR dmi.product.version: Lenovo ideapad 330S-15ARR dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-20 (13 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: cosmic Uname: Linux 4.19.0-041900rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to cosmic on 2018-09-30 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795292/+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 1796743] Re: Ubuntu 18.10 - Alienware 17 R5 crashes on sleep
Excellent! Thank you... -- Cristian Aravena Romero (caravena) -- 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/1796743 Title: Ubuntu 18.10 - Alienware 17 R5 crashes on sleep Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: If the machine goes to sleep, either because I close the lid or because it idles too long, it ends up in a weird state when I try to resume. If I press the power/Alien button, the fan runs and the keyboard/trackpad light up but nothing happens. Ultimately I need to hard power off the laptop (by holding the power button in for three seconds) which causes it to boot from scratch. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: feoh 2895 F pulseaudio CurrentDesktop: GNOME Date: Mon Oct 8 14:25:16 2018 InstallationDate: Installed on 2018-10-07 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) MachineType: Alienware Alienware 17 R5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=c3d3798c-6179-472a-ba82-55ef94f4d382 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2018 dmi.bios.vendor: Alienware dmi.bios.version: 1.5.0 dmi.board.name: Alienware 17 R5 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.5.0:bd08/10/2018:svnAlienware:pnAlienware17R5:pvr1.5.0:rvnAlienware:rnAlienware17R5:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware 17 R5 dmi.product.sku: 0877 dmi.product.version: 1.5.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796743/+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 1796730] Re: Ubuntu 18.10 regression: nvidia driver does not work
installation log of nvidia-driver-390 ** Attachment added: "Nvidia-driver-installation.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796730/+attachment/5199235/+files/Nvidia-driver-installation.log -- 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/1796730 Title: Ubuntu 18.10 regression: nvidia driver does not work Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: Problems started after upgrade to 18.10 and first reboot. Symptoms: * Login screen appears * After providing credentials desktop does not start --- Extra info for Bug 1796433 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Oct 8 20:01:33 2018 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (1005 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-05 (2 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796730/+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 1796730] Re: Ubuntu 18.10 regression: nvidia driver does not work
I have a very similar issue after upgrade to 18.10 (the system hangs after gdm login). -- 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/1796730 Title: Ubuntu 18.10 regression: nvidia driver does not work Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: Problems started after upgrade to 18.10 and first reboot. Symptoms: * Login screen appears * After providing credentials desktop does not start --- Extra info for Bug 1796433 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Oct 8 20:01:33 2018 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (1005 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-05 (2 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796730/+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 1796743] Re: Ubuntu 18.10 - Alienware 17 R5 crashes on sleep
Yay this is in fact fixed in 4.19-rc7! Thanks very much this was a real show stopper :) ** Tags added: kernel-fixed-upstream ** Changed in: linux (Ubuntu) Status: Triaged => 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/1796743 Title: Ubuntu 18.10 - Alienware 17 R5 crashes on sleep Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: If the machine goes to sleep, either because I close the lid or because it idles too long, it ends up in a weird state when I try to resume. If I press the power/Alien button, the fan runs and the keyboard/trackpad light up but nothing happens. Ultimately I need to hard power off the laptop (by holding the power button in for three seconds) which causes it to boot from scratch. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: feoh 2895 F pulseaudio CurrentDesktop: GNOME Date: Mon Oct 8 14:25:16 2018 InstallationDate: Installed on 2018-10-07 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) MachineType: Alienware Alienware 17 R5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=c3d3798c-6179-472a-ba82-55ef94f4d382 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2018 dmi.bios.vendor: Alienware dmi.bios.version: 1.5.0 dmi.board.name: Alienware 17 R5 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.5.0:bd08/10/2018:svnAlienware:pnAlienware17R5:pvr1.5.0:rvnAlienware:rnAlienware17R5:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware 17 R5 dmi.product.sku: 0877 dmi.product.version: 1.5.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796743/+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 1796895] Re: Kernel 4.15.0-36 network performance regression
Thanks for all the testing. If this bug is fixed in -proposed, then the fix is already applied to the Ubuntu kernel and will be released in the next round of updates on November 12th. The fix will be in the 4.15.0-37 or newer kernel. Can others affected by this bug confirm that the proposed kernel resolves the bug as well? ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796895 Title: Kernel 4.15.0-36 network performance regression Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: Hardware: HP DL380 Gen 7 server with Gigabit interface. Ubuntu release: 18.04.1 Since upgrading from 4.15.0-33 to 4.15.0-36, I have noticed a dramatic slowdown in TCP over IPv6. Set up: two servers, Server A in US on Ubuntu 18.04.1, Server B in Europe. Test: Sending 400MB over TCP from Server B to Server A. With 4.15.0-33 on Server A, the transfer is completed in 24 seconds, with average speed of 139 mbps. With 4.15.0-36 on Server A, the same amount of data is transferred in 369 seconds, average speed less than 9 mbps. Looking at the result from tcpdump, I see that the there is a big difference in the TCP Window size. With 3.15-0.33 the TCP window size is around 3. But with 3.15-0.36, the window size is only 734. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796895/+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 1783957] Re: Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no login screen in a normal sequence
I built the next test kernel, up to the following commit: 34cc0aa2545603560c79aaea3340d8ff3a71bd10 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1783957 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- 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/1783957 Title: Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no login screen in a normal sequence Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Bug description: I have a MacBook Air laptop which is running Linux (Kubuntu 16.04.5 LTS) with NVidia Graphics Card, KDE, Xorg, SDDM, and so on... Clean and natural install, no funky custom kernel or drivers or anything... Everything worked fine (with the 4.13.* kernel) until I've upgraded all my packages (which included the "wonderful" 4.15.0-29 kernel, which broke my system). Now, everytime I try to boot normally, it asks me for my disk password (I have an encrypted LVM) and after that, guess what ?: blank screen. The login screen does not appear. I can switch the Terminals with Ctrl+Alt+Fx, however. However, the same kernel, if I boot it in recovery mode and then I select "Resume", the login screen appears, but it lags a little bit... Needless to say, if I boot the older kernel (4.13), everything works perfectly. I dug up some logs and found something like "sddm-greeter" segmentation fault in nouveau_dri.so or something like this. So, it looks like the new kernel doesn't quite seem to look eye-to-eye with nouveau drivers... And no, I don't want the NVidia proprietary drivers because I get along just perfectly with Nouveau on other machines, and I don't want to reinstall nvidia drivers everytime I'm upgrading the kernel. And yes, I already have "haveged" installed, to provide sufficient entropy (I saw that the possible lack of entropy might be a problem in some cases)... If I boot in recovery mode and then select "resume", everything works. So, what is going on ? Any help would be appreciated... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: KDE Date: Fri Jul 27 10:40:31 2018 InstallationDate: Installed on 2018-07-04 (22 days ago) InstallationMedia: Kubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783957/+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 1792044] Re: update ENA driver to latest mainline version
This was erroneously marked as released. Verification is not yet done. ** Changed in: linux (Ubuntu) Status: Fix Released => Fix Committed -- 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/1792044 Title: update ENA driver to latest mainline version Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: Update ENA driver to latest mainline version as of this commit: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=0e1f4c76be241377d282e34ebea6d16ff7829747 For Bionic, the following commits: net: ena: fix incorrect usage of memory barriers net: ena: fix missing calls to READ_ONCE net: ena: fix missing lock during device destruction net: ena: fix potential double ena_destroy_device() net: ena: fix device destruction to gracefully free resources net: ena: fix driver when PAGE_SIZE == 64kB net: ena: fix surprise unplug NULL dereference kernel crash net: ena: Fix use of uninitialized DMA address bits field UBUNTU: SAUCE: ena: devm_kzalloc() -> devm_kcalloc() net: ena: Eliminate duplicate barriers on weakly-ordered archs net: ena: increase ena driver version to 1.5.0 net: ena: add detection and recovery mechanism for handling missed/misrouted MSI-X For Xenial, the following commits: net: ena: fix incorrect usage of memory barriers net: ena: fix missing calls to READ_ONCE net: ena: fix missing lock during device destruction net: ena: fix potential double ena_destroy_device() net: ena: fix device destruction to gracefully free resources net: ena: fix driver when PAGE_SIZE == 64kB net: ena: fix surprise unplug NULL dereference kernel crash net: ena: Fix use of uninitialized DMA address bits field UBUNTU: SAUCE: ena: devm_kzalloc() -> devm_kcalloc() net: ena: Eliminate duplicate barriers on weakly-ordered archs net: ena: fix error handling in ena_down() sequence net: ena: increase ena driver version to 1.5.0 net: ena: add detection and recovery mechanism for handling missed/misrouted MSI-X net: ena: fix race condition between device reset and link up setup net: ena: increase ena driver version to 1.3.0 net: ena: add new admin define for future support of IPv6 RSS net: ena: add statistics for missed tx packets net: ena: add power management ops to the ENA driver net: ena: remove legacy suspend suspend/resume support net: ena: improve ENA driver boot time. net: ena: fix wrong max Tx/Rx queues on ethtool net: ena: fix rare kernel crash when bar memory remap fails net: ena: reduce the severity of some printouts net: ena: Remove redundant unlikely() *Note that some of these were already present in the linux-aws variants (the remainder will be picked up on their next rebase cycles). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792044/+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 1796895] Re: Kernel 4.15.0-36 network performance regression
Tested the first bisected version, on commit 003ae88ae88d48643e71dc69c18d4eda598339d5, problem still present. -- 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/1796895 Title: Kernel 4.15.0-36 network performance regression Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: Hardware: HP DL380 Gen 7 server with Gigabit interface. Ubuntu release: 18.04.1 Since upgrading from 4.15.0-33 to 4.15.0-36, I have noticed a dramatic slowdown in TCP over IPv6. Set up: two servers, Server A in US on Ubuntu 18.04.1, Server B in Europe. Test: Sending 400MB over TCP from Server B to Server A. With 4.15.0-33 on Server A, the transfer is completed in 24 seconds, with average speed of 139 mbps. With 4.15.0-36 on Server A, the same amount of data is transferred in 369 seconds, average speed less than 9 mbps. Looking at the result from tcpdump, I see that the there is a big difference in the TCP Window size. With 3.15-0.33 the TCP window size is around 3. But with 3.15-0.36, the window size is only 734. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796895/+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 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
Do you have the full logs of "/var/log/unattended-upgrades" and "/var/log/apt" handy ? - Eric -- 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/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode Status in linux package in Ubuntu: Confirmed Bug description: Since the following linux-cloud-tools-common package versions : Xenial : 4.4.0-135.161 Bionic : 4.15.0-34.37 the Systemd service unit file for hv-kvp-daemon has been modified with new dependencies that make the package unable to be upgraded with unattended-upgrades on shutdown mode. Unattended-upgrades hangs with the linux-cloud-tools-common package during "Preparing to unpack". The server restarts after the unattended-upgrades service timeout expires. - Package state after reboot : iFR linux-cloud-tools-common 4.15.0-34.37 all Linux kernel version specific cloud tools for version 4.15.0 - Unattended-upgrades dpkg logs : Log started: 2018-10-05 17:59:04 (Reading database ... 52043 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ... Log ended: 2018-10-05 18:00:54 - Impact : The current impact is very important as all security updates are blocked until you manually fix each server with : dpkg --configure -a apt install --only-upgrade linux-cloud-tools-common - Workaround/Fix : As a simple straightforward fix, replacing : Before=shutdown.target cloud-init-local.service walinuxagent.service with : Before=shutdown.target walinuxagent.service makes the package upgradable during shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+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 1796944] Re: linux-aws: 4.18.0-1002.3 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri (mhcerri) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri (mhcerri) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1796944 Title: linux-aws: 4.18.0-1002.3 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws source package in Cosmic: Confirmed Bug description: This bug is for tracking the 4.18.0-1002.3 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1796346 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1796944/+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 1796949] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1796949 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: bionic -- 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/1796949 Title: [Bionic] CPPC bug fixes Status in linux package in Ubuntu: Incomplete Bug description: [Impact] [Fix] [Test] [Regression Potential] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796949/+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 1796949] [NEW] [Bionic] CPPC bug fixes
Public bug reported: [Impact] [Fix] [Test] [Regression Potential] ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: cavium -- 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/1796949 Title: [Bionic] CPPC bug fixes Status in linux package in Ubuntu: New Bug description: [Impact] [Fix] [Test] [Regression Potential] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796949/+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 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
Does this workaround also work with the current 4.15.0-36 kernel available in updates: modprobe rtl8723be ant_sel=1 Are does it only work with the test kernel I posed in comment #41? -- 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/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+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 1795653] Re: 87cdf3148b11 was never backported to 4.15
Thanks for testing. I'll submit a Bionic SRU request to include that commit. -- 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/1795653 Title: 87cdf3148b11 was never backported to 4.15 Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: Hello, After a few days of troubleshooting a problem with L2TP and IPSec a fellow from ServerFault pointed out that my problem is a known bug fixed by 87cdf3148b11 commit which wasn't backported on 4.15 kernel. Ubuntu 4.15.0-36.39-generic 4.15.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795653/+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 1794110] Re: MPS (Max Payload Size) is not correctly programmed upon Hot Insertion NVMe PCIe SSD
Do you happen to know which commits are also needed in Bionic? -- 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/1794110 Title: MPS (Max Payload Size) is not correctly programmed upon Hot Insertion NVMe PCIe SSD Status in The Dell-poweredge project: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: Max Payload Size for the NVMe device is not getting programmed correctly. The OS is trying to set the device MPS to match Root Port which is greater than Capability of Device, instead of looking for lowest common denominator. This is fixed in upstream kernel version 4.19. Below are the commits that fix the issue. Please help include them in Ubuntu releases. PCI: Skip MPS logic for Virtual Functions (VFs) https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2&id=3dbe97efe8bf450b183d6dee2305cbc032e6b8a4 PCI: Match Root Port's MPS to endpoint's MPSS as necessary https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2&id=9f0e89359775ee21fe1ea732e34edb52aef5addf To manage notifications about this bug go to: https://bugs.launchpad.net/dell-poweredge/+bug/1794110/+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 1794067] Re: Bug in selinux on ubuntu 16.04 with kernel 4.15.0-34
We may have to test some prior kernel to have a starting version for a
bisect. Before starting a bisect, would it be possible for you to test
the proposed kernel and post back if it resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed.
--
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/1794067
Title:
Bug in selinux on ubuntu 16.04 with kernel 4.15.0-34
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
Hello, just found a bug in selinux.
Whats going wrong:
Copy a link with "-a" option while selinux is on.
steps to reproduce:
~$ mkdir -p a/b
~$ ln -s b a/c
~$ cp -a a b
cp: failed to restore the default file creation context: Invalid argument
Results of my investigation:
The "cp" of coreutils is calling "setfscreatecon (NULL)" to restore
the default file creation context (coreutils-8.30/src/copy.c:1771) as
it is stated in the selinux api
(/libselinux/include/selinux/selinux.h:71).
As we see in the result of strace below, the kernel returns an -1 on
try to restore the default file creation context. So in my opinion is
the bug has to be in the selinux_setprocattr method in the
security/selinux/hooks.c file.
Part of "strace cp -a a b"
lgetxattr("a/c", "security.selinux", "system_u:object_r:user_home_dir_t:s0",
255) = 37
readlink("a/c", "b", 2) = 1
symlink("b", "b/a/c") = 0
open("/proc/self/task/2136/attr/fscreate", O_RDWR|O_CLOEXEC) = 3
write(3, NULL, 0) = -1 EINVAL (Invalid argument)
close(3) = 0
open("/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=2995, ...}) = 0
read(3, "# Locale name alias data base.\n#"..., 4096) = 2995
read(3, "", 4096) = 0
close(3)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794067/+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 1796895] Re: Kernel 4.15.0-36 network performance regression
I started a kernel bisect between 4.15.0-34 and 4.15.0-36. The kernel bisect will require testing of about 7-10 test kernels. I built the first test kernel, up to the following commit: 003ae88ae88d48643e71dc69c18d4eda598339d5 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1796895 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- 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/1796895 Title: Kernel 4.15.0-36 network performance regression Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Hardware: HP DL380 Gen 7 server with Gigabit interface. Ubuntu release: 18.04.1 Since upgrading from 4.15.0-33 to 4.15.0-36, I have noticed a dramatic slowdown in TCP over IPv6. Set up: two servers, Server A in US on Ubuntu 18.04.1, Server B in Europe. Test: Sending 400MB over TCP from Server B to Server A. With 4.15.0-33 on Server A, the transfer is completed in 24 seconds, with average speed of 139 mbps. With 4.15.0-36 on Server A, the same amount of data is transferred in 369 seconds, average speed less than 9 mbps. Looking at the result from tcpdump, I see that the there is a big difference in the TCP Window size. With 3.15-0.33 the TCP window size is around 3. But with 3.15-0.36, the window size is only 734. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796895/+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 1796944] Re: linux-aws: 4.18.0-1002.3 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug is for tracking the 4.18.0-1002.3 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1796346 + kernel-phase:Packaging + kernel-phase-changed:Tuesday, 09. October 2018 18:31 UTC ** Description changed: This bug is for tracking the 4.18.0-1002.3 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1796346 - kernel-phase:Packaging - kernel-phase-changed:Tuesday, 09. October 2018 18:31 UTC + phase: Packaging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1796944 Title: linux-aws: 4.18.0-1002.3 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws source package in Cosmic: Confirmed Bug description: This bug is for tracking the 4.18.0-1002.3 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1796346 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1796944/+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 1796895] Re: Kernel 4.15.0-36 network performance regression
Just tested with the proposed build, the problem is fixed with the proposed kernel 4.15.0-37 on my server. Does this mean the problem is Ubuntu specific? When will the proposed version be released? Do you still think it's necessary to test against the mainline? -- 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/1796895 Title: Kernel 4.15.0-36 network performance regression Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Hardware: HP DL380 Gen 7 server with Gigabit interface. Ubuntu release: 18.04.1 Since upgrading from 4.15.0-33 to 4.15.0-36, I have noticed a dramatic slowdown in TCP over IPv6. Set up: two servers, Server A in US on Ubuntu 18.04.1, Server B in Europe. Test: Sending 400MB over TCP from Server B to Server A. With 4.15.0-33 on Server A, the transfer is completed in 24 seconds, with average speed of 139 mbps. With 4.15.0-36 on Server A, the same amount of data is transferred in 369 seconds, average speed less than 9 mbps. Looking at the result from tcpdump, I see that the there is a big difference in the TCP Window size. With 3.15-0.33 the TCP window size is around 3. But with 3.15-0.36, the window size is only 734. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796895/+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 1796720] Re: High GPU temperature after kernel 4.18.0.9.10 on AMD RX460
Help Joseph! :) -- Cristian Aravena Romero (caravena) -- 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/1796720 Title: High GPU temperature after kernel 4.18.0.9.10 on AMD RX460 Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: Hello, Today I have received an update for Linux kernel which upgraded the kernel on my Ubuntu 18.10 installation to 4.18.0.9.10! Immediately after restart I noticed that the GPU temperature is abnormally High... Before Update: - GPU fan set to off on idle - GPU idle temperature: 29-32 C After Update: - GPU fan set to off on idle - GPU idle temperature: 47-50 C (which I have to put the fans on 50% to keep it on 33 C) I have also tried to boot from the older kernel (4.18.0.8) and everything is normal there! System spec: - MB: ASUS Prime x299-deluxe - CPU: Intel Corei7 7820x skylake-x - GPU: AMD RX460 glxinfo | grep OpenGL: OpenGL vendor string: X.Org OpenGL renderer string: AMD Radeon (TM) RX 460 Graphics (POLARIS11, DRM 3.26.0, 4.18.0-9-generic, LLVM 7.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.2.1 OpenGL core profile shading language version string: 4.50 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.2.1 OpenGL shading language version string: 4.40 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.2.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions: sudo cat /sys/kernel/debug/dri/0/amdgpu_pm_info: Clock Gating Flags Mask: 0x37bcf Graphics Medium Grain Clock Gating: On Graphics Medium Grain memory Light Sleep: On Graphics Coarse Grain Clock Gating: On Graphics Coarse Grain memory Light Sleep: On Graphics Coarse Grain Tree Shader Clock Gating: Off Graphics Coarse Grain Tree Shader Light Sleep: Off Graphics Command Processor Light Sleep: On Graphics Run List Controller Light Sleep: On Graphics 3D Coarse Grain Clock Gating: Off Graphics 3D Coarse Grain memory Light Sleep: Off Memory Controller Light Sleep: On Memory Controller Medium Grain Clock Gating: On System Direct Memory Access Light Sleep: Off System Direct Memory Access Medium Grain Clock Gating: On Bus Interface Medium Grain Clock Gating: Off Bus Interface Light Sleep: On Unified Video Decoder Medium Grain Clock Gating: On Video Compression Engine Medium Grain Clock Gating: On Host Data Path Light Sleep: Off Host Data Path Medium Grain Clock Gating: On Digital Right Management Medium Grain Clock Gating: Off Digital Right Management Light Sleep: Off Rom Medium Grain Clock Gating: On Data Fabric Medium Grain Clock Gating: Off GFX Clocks and Power: 1750 MHz (MCLK) 1212 MHz (SCLK) 214 MHz (PSTATE_SCLK) 300 MHz (PSTATE_MCLK) 1081 mV (VDDGFX) 18.65 W (average GPU) GPU Temperature: 39 C GPU Load: 0 % UVD: Disabled VCE: Disabled ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-9-generic 4.18.0-9.10 ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12 Uname: Linux 4.18.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shadowfax 3078 F pulseaudio /dev/snd/controlC0: shadowfax 3078 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 8 20:27:13 2018 InstallationDate: Installed on 2018-09-26 (11 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180925.1) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-9-generic root=UUID=a58662c7-39e2-4f05-9da6-d63173c94d53 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-9-generic N/A linux-backports-modules-4.18.0-9-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1503 dmi.board.asset.tag: Default string dmi.board.name: PRIME X299-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1503:bd08/03/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstr
[Kernel-packages] [Bug 1796647] Re: Shared folders cannot be mounted in ubuntu/cosmic64 due to missing vbox modules
My understanding of the issue after an IRC conversation with sforshee is that the modules were intentionally dropped from the kernel packages, but the corresponding Provides of virtualbox-guest-modules was _not_ dropped from the kernel packaging. This means that when we install virtualbox-guest-utils during image build, it sees the modules as already available so does nothing. (Instead, it should have to fulfil the dependency some other way, probably by installing the DKMS packages which build the drivers). -- 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/1796647 Title: Shared folders cannot be mounted in ubuntu/cosmic64 due to missing vbox modules Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: In bionic, the vboxsf module was included in linux- modules-...-generic: $ dpkg -c linux-modules-4.15.0-36-generic_4.15.0-36.39_amd64.deb | grep vboxsf.ko -rw-r--r-- root/root 63238 2018-09-24 10:08 ./lib/modules/4.15.0-36-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko In cosmic, it isn't: $ dpkg -c ~/Downloads/linux- modules-4.18.0-9-generic_4.18.0-9.10_amd64.deb | grep vboxsf.ko This results in shared folders no longer being mountable in Ubuntu Vagrant boxes (and, as the other vbox modules are also missing, probably has other effects that haven't yet been reported). [Original Report] Just tried to test out the new cosmic64 vagrant box and get the following error; ``` Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available. This filesystem is made available via the VirtualBox Guest Additions and kernel module. Please verify that these guest additions are properly installed in the guest. This is not a bug in Vagrant and is usually caused by a faulty Vagrant box. For context, the command attempted was: mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant The error output from the command was: /sbin/mount.vboxsf: mounting failed with the error: No such device ``` I tried with ubuntu/bionic64 and it worked fine. I've got; $ vagrant version Installed Version: 2.1.5 Latest Version: 2.1.5 You're running an up-to-date version of Vagrant! $ VBoxManage --version 5.2.18r124319 $ To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1796647/+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 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers with DVD
Could you please download and install https://launchpad.net/ubuntu/+source/finalrd/3/+build/15227702/+files/finalrd_3_all.deb (this is a link from https://launchpad.net/ubuntu/+source/finalrd/3/+build/15227702 ) And check if that helps with reboots? This should perform pivot-root from rootfs to initramfs, and generally improve shutdown reliability. However, I do suspect this to be a kernel issue. If ahci is really identified as a kernel shutdown culprit, we might want to ship an executable script in /lib/systemd/system-shutdown/yank-modules.sh or somesuch which would rmmod ahci if possible. So far I do not have any indications that it is indeed systemd holding up reboot, and not the 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/1777674 Title: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers with DVD Status in dellserver: New Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers when under graceful reboot stress for 12hrs. * This hand is observed only when Onboard SATA DVD Drive is connected. * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13) * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic) Steps: Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and start reboot stress After a few reboots, observe that the machine hangs at "kvm: exiting hardware virtualization" and does not proceed with reboot cycles. Only physical reset helps in continuing the reboot test. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1777674/+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 1796585] Re: package linux-image-extra-4.10.0-35-generic 4.10.0-35.39~16.04.1 failed to install/upgrade: package linux-image-extra-4.10.0-35-generic is not ready for configurati
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796585 Title: package linux-image-extra-4.10.0-35-generic 4.10.0-35.39~16.04.1 failed to install/upgrade: package linux-image-extra-4.10.0-35-generic is not ready for configuration cannot configure (current status 'half-installed') Status in linux package in Ubuntu: Incomplete Bug description: Errors were encountered while processing: linux-image-extra-4.10.0-35-generic E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.10.0-35-generic 4.10.0-35.39~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Oct 7 20:12:25 2018 DuplicateSignature: package:linux-image-extra-4.10.0-35-generic:4.10.0-35.39~16.04.1 Processing triggers for doc-base (0.10.7) ... Processing 3 changed doc-base files... dpkg: error processing package linux-image-extra-4.10.0-35-generic (--configure): package linux-image-extra-4.10.0-35-generic is not ready for configuration ErrorMessage: package linux-image-extra-4.10.0-35-generic is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-08-28 (404 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: linux-hwe Title: package linux-image-extra-4.10.0-35-generic 4.10.0-35.39~16.04.1 failed to install/upgrade: package linux-image-extra-4.10.0-35-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: Upgraded to xenial on 2018-10-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796585/+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 1796582] Re: Internal microphone not working on Lenovo Ideapad 330S-15ARR
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796582 Title: Internal microphone not working on Lenovo Ideapad 330S-15ARR Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: The internal microphone on this troublesome laptop stopped working after upgrading from Bionic to Cosmic. There is no signal from the microphone with kernel 4.18.0-7 or 4.18.0-8. This DOES work correctly with kernel 4.15.0-34 that is still present on Cosmic after the upgrade. I recommend Canonical gets this laptop for testing since a ton of stuff is troublesome on this Raven Ridge laptop. Would be a good specimen to get support for this platform improved. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xorbit 2295 F pulseaudio /dev/snd/controlC0: xorbit 2295 F pulseaudio CurrentDesktop: GNOME Date: Sun Oct 7 12:02:45 2018 InstallationDate: Installed on 2018-09-20 (17 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81FB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic rcu_nocbs=0-7 quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-09-30 (6 days ago) dmi.bios.date: 09/05/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7WCN26WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7WCN26WW:bd09/05/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR: dmi.product.family: ideapad 330S-15ARR dmi.product.name: 81FB dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR dmi.product.version: Lenovo ideapad 330S-15ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796582/+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 1796720] Re: High GPU temperature after kernel 4.18.0.9.10 on AMD RX460
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags added: kernel-da-key ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged -- 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/1796720 Title: High GPU temperature after kernel 4.18.0.9.10 on AMD RX460 Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: Hello, Today I have received an update for Linux kernel which upgraded the kernel on my Ubuntu 18.10 installation to 4.18.0.9.10! Immediately after restart I noticed that the GPU temperature is abnormally High... Before Update: - GPU fan set to off on idle - GPU idle temperature: 29-32 C After Update: - GPU fan set to off on idle - GPU idle temperature: 47-50 C (which I have to put the fans on 50% to keep it on 33 C) I have also tried to boot from the older kernel (4.18.0.8) and everything is normal there! System spec: - MB: ASUS Prime x299-deluxe - CPU: Intel Corei7 7820x skylake-x - GPU: AMD RX460 glxinfo | grep OpenGL: OpenGL vendor string: X.Org OpenGL renderer string: AMD Radeon (TM) RX 460 Graphics (POLARIS11, DRM 3.26.0, 4.18.0-9-generic, LLVM 7.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.2.1 OpenGL core profile shading language version string: 4.50 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.2.1 OpenGL shading language version string: 4.40 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.2.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions: sudo cat /sys/kernel/debug/dri/0/amdgpu_pm_info: Clock Gating Flags Mask: 0x37bcf Graphics Medium Grain Clock Gating: On Graphics Medium Grain memory Light Sleep: On Graphics Coarse Grain Clock Gating: On Graphics Coarse Grain memory Light Sleep: On Graphics Coarse Grain Tree Shader Clock Gating: Off Graphics Coarse Grain Tree Shader Light Sleep: Off Graphics Command Processor Light Sleep: On Graphics Run List Controller Light Sleep: On Graphics 3D Coarse Grain Clock Gating: Off Graphics 3D Coarse Grain memory Light Sleep: Off Memory Controller Light Sleep: On Memory Controller Medium Grain Clock Gating: On System Direct Memory Access Light Sleep: Off System Direct Memory Access Medium Grain Clock Gating: On Bus Interface Medium Grain Clock Gating: Off Bus Interface Light Sleep: On Unified Video Decoder Medium Grain Clock Gating: On Video Compression Engine Medium Grain Clock Gating: On Host Data Path Light Sleep: Off Host Data Path Medium Grain Clock Gating: On Digital Right Management Medium Grain Clock Gating: Off Digital Right Management Light Sleep: Off Rom Medium Grain Clock Gating: On Data Fabric Medium Grain Clock Gating: Off GFX Clocks and Power: 1750 MHz (MCLK) 1212 MHz (SCLK) 214 MHz (PSTATE_SCLK) 300 MHz (PSTATE_MCLK) 1081 mV (VDDGFX) 18.65 W (average GPU) GPU Temperature: 39 C GPU Load: 0 % UVD: Disabled VCE: Disabled ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-9-generic 4.18.0-9.10 ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12 Uname: Linux 4.18.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shadowfax 3078 F pulseaudio /dev/snd/controlC0: shadowfax 3078 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 8 20:27:13 2018 InstallationDate: Installed on 2018-09-26 (11 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180925.1) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-9-generic root=UUID=a58662c7-39e2-4f05-9da6-d63173c94d53 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-9-generic N/A linux-backports-modules-4.18.0-9-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1503 dmi.board.asset.tag: Default string dmi.board.name: PRIME X299-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1503:bd08/03/2018:svnSystemmanufacturer:pnSystemProductNam
[Kernel-packages] [Bug 1794074] 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/1794074 Title: xhci_hcd :25:00.0: ERROR unknown event type 15 Status in linux package in Ubuntu: Confirmed Bug description: Using Ubuntu 18.04 as a bare-metal VM server via libvirtd qemu-kvm, after some time with the guests running, xhci freaks out and thinks the server died and disables all USB devices. xhci_hcd :25:00.0: ERROR unknown event type 15 xhci_hcd :25:00.0: xHCI host not responding to stop endpoint command. xhci_hcd :25:00.0: xHCI host controller not responding, assume dead xhci_hcd :25:00.0: HC died; cleaning up --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-34-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jimmy 6534 F pulseaudio /dev/snd/controlC3: jimmy 6534 F pulseaudio /dev/snd/controlC1: jimmy 6534 F pulseaudio Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card3.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card3.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Micro-Star International Co., Ltd. MS-7A33 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=9195c88f-be47-11e8-b927-309c2327f349 ro ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt libvirt-dnsmasq lxd plugdev sudo video _MarkForUpload: True dmi.bios.date: 07/11/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.D0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X370 SLI PLUS (MS-7A33) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.D0:bd07/11/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A33:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnX370SLIPLUS(MS-7A33):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A33 dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794074/+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 1796576] Re: rtl8723be cannot connect to wifi since Kernel version 4.15.0-33-generic
Would it be possible for you to test the proposed kernel and post back if it resolves this bug? See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance! ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: needs-bisect -- 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/1796576 Title: rtl8723be cannot connect to wifi since Kernel version 4.15.0-33-generic Status in linux package in Ubuntu: Incomplete Bug description: Starting from Kernel version linux-image-4.15.0-33-generic I cannot connect anymore to wifi network. The problem occurs also with linux-image-4.15.0-34-generic. Kernel version linux-headers-4.15.0-32-generic is working fine. My current configuration for rtl8723be is /etc/modprobe.d/rtlbtcoex.conf: options rtl8723be ant_sel=2 ips=0 I'm using these parameters with for rtl8723be module in order to get the correct gain for Wifi antenna. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-modules-extra-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alessio1778 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 7 19:16:55 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=9d050d63-7a5d-443b-9210-3f51da9bf26f InstallationDate: Installed on 2017-02-20 (593 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b008 Realtek Semiconductor Corp. Bus 001 Device 003: ID 1bcf:2c87 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=6c5ccef4-fabc-435b-a40b-c3d11c52cbfe ro quiet splash pci=noaer vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-21 (46 days ago) dmi.bios.date: 12/12/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.25 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8216 dmi.board.vendor: HP dmi.board.version: 83.14 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.25:bd12/12/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.14:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796576/+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 1796720] Re: High GPU temperature after kernel 4.18.0.9.10 on AMD RX460
@Cristian thank you for the heads up...so this the upstream mainline kernel bug? >From the link you have posted I can see that the latest 4.19-rc doesn't seem >to affected! Do you still need me to install the latest kernel and confirm whether this fixed or not using the following instruction you have mentioned earlier? - If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. - If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. - Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Regards, -- 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/1796720 Title: High GPU temperature after kernel 4.18.0.9.10 on AMD RX460 Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: Hello, Today I have received an update for Linux kernel which upgraded the kernel on my Ubuntu 18.10 installation to 4.18.0.9.10! Immediately after restart I noticed that the GPU temperature is abnormally High... Before Update: - GPU fan set to off on idle - GPU idle temperature: 29-32 C After Update: - GPU fan set to off on idle - GPU idle temperature: 47-50 C (which I have to put the fans on 50% to keep it on 33 C) I have also tried to boot from the older kernel (4.18.0.8) and everything is normal there! System spec: - MB: ASUS Prime x299-deluxe - CPU: Intel Corei7 7820x skylake-x - GPU: AMD RX460 glxinfo | grep OpenGL: OpenGL vendor string: X.Org OpenGL renderer string: AMD Radeon (TM) RX 460 Graphics (POLARIS11, DRM 3.26.0, 4.18.0-9-generic, LLVM 7.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.2.1 OpenGL core profile shading language version string: 4.50 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.2.1 OpenGL shading language version string: 4.40 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.2.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions: sudo cat /sys/kernel/debug/dri/0/amdgpu_pm_info: Clock Gating Flags Mask: 0x37bcf Graphics Medium Grain Clock Gating: On Graphics Medium Grain memory Light Sleep: On Graphics Coarse Grain Clock Gating: On Graphics Coarse Grain memory Light Sleep: On Graphics Coarse Grain Tree Shader Clock Gating: Off Graphics Coarse Grain Tree Shader Light Sleep: Off Graphics Command Processor Light Sleep: On Graphics Run List Controller Light Sleep: On Graphics 3D Coarse Grain Clock Gating: Off Graphics 3D Coarse Grain memory Light Sleep: Off Memory Controller Light Sleep: On Memory Controller Medium Grain Clock Gating: On System Direct Memory Access Light Sleep: Off System Direct Memory Access Medium Grain Clock Gating: On Bus Interface Medium Grain Clock Gating: Off Bus Interface Light Sleep: On Unified Video Decoder Medium Grain Clock Gating: On Video Compression Engine Medium Grain Clock Gating: On Host Data Path Light Sleep: Off Host Data Path Medium Grain Clock Gating: On Digital Right Management Medium Grain Clock Gating: Off Digital Right Management Light Sleep: Off Rom Medium Grain Clock Gating: On Data Fabric Medium Grain Clock Gating: Off GFX Clocks and Power: 1750 MHz (MCLK) 1212 MHz (SCLK) 214 MHz (PSTATE_SCLK) 300 MHz (PSTATE_MCLK) 1081 mV (VDDGFX) 18.65 W (average GPU) GPU Temperature: 39 C GPU Load: 0 % UVD: Disabled VCE: Disabled ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-9-generic 4.18.0-9.10 ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12 Uname: Linux 4.18.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shadowfax 3078 F pulseaudio /dev/snd/controlC0: shadowfax 3078 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 8 20:27:13 2018 InstallationDate: Installed on 2018-09-26 (11 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180925.1) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-9-generic root=UUID=a58662c7-39e2-4f05-9da6-d63173c94d53 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-9-generic N/A linux-backports-modules-4.18.0-9-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2
[Kernel-packages] [Bug 1796228] Re: BUG: scheduling while atomic: irq/51-iwlwifi/408/0x7ffffc00
https://bugzilla.kernel.org/show_bug.cgi?id=201297 -- Cristian Aravena Romero (caravena) ** Bug watch added: Linux Kernel Bug Tracker #201297 https://bugzilla.kernel.org/show_bug.cgi?id=201297 ** Changed in: linux Remote watch: Linux Kernel Bug Tracker #201355 => Linux Kernel Bug Tracker #201297 -- 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/1796228 Title: BUG: scheduling while atomic: irq/51-iwlwifi/408/0x7c00 Status in Linux: Unknown Status in linux package in Ubuntu: Incomplete Bug description: I was playing some audio files, the following message appears, ALSA lib pcm.c:8424:(snd_pcm_recover) underrun occurred And the WIFI is disconnected. I have experienced problems, (1)The gnome-sound-recorder sometime works sometime doesn't. (2) Click the LibreOffice Calc, after the empty worksheet loads, when i try to open another document by using "File->Open" on the menu, the application is not responding at all and I have to force it quit ProblemType: KernelOops DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dcansheng 2110 F pulseaudio /dev/snd/controlC1: dcansheng 2110 F pulseaudio Date: Fri Oct 5 10:56:26 2018 Failure: oops HibernationDevice: RESUME=UUID=2bbccbb3-89de-4207-9146-7a829c7e83a8 InstallationDate: Installed on 2018-08-29 (36 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20392 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=0bcc11bd-c39c-4a17-9eb3-67098d0bca7f ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: BUG: scheduling while atomic: irq/51-iwlwifi/408/0x7c00 UpgradeStatus: Upgraded to cosmic on 2018-08-30 (35 days ago) dmi.bios.date: 11/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9DCN29WW(V2.09) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo B40-70 dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo B40-70 dmi.modalias: dmi:bvnLENOVO:bvr9DCN29WW(V2.09):bd11/21/2014:svnLENOVO:pn20392:pvrLenovoB40-70:rvnLENOVO:rnLenovoB40-70:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoB40-70: dmi.product.family: IDEAPAD dmi.product.name: 20392 dmi.product.sku: LENOVO_MT_20392_BU_idea_FM_Lenovo B40-70 dmi.product.version: Lenovo B40-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796228/+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 1796641] Re: linux-oem: 4.15.0-1023.26 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1795564 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Tuesday, 09. October 2018 17:33 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1795564 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Tuesday, 09. October 2018 17:33 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- 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/1796641 Title: linux-oem: 4.15.0-1023.26 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1795564 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1796641/+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 1796944] [NEW] linux-aws: 4.18.0-1002.3 -proposed tracker
Public bug reported: This bug is for tracking the 4.18.0-1002.3 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1796346 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-aws (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux-aws (Ubuntu Cosmic) Importance: Medium Status: Confirmed ** Tags: cosmic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2018.10.05 ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-aws (Ubuntu Cosmic) Importance: Undecided Status: New ** Tags added: cosmic ** Changed in: linux-aws (Ubuntu Cosmic) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux-aws (Ubuntu) Importance: Undecided => Medium ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Tags added: kernel-sru-cycle-2018.10.05 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1796944 Title: linux-aws: 4.18.0-1002.3 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws source package in Cosmic: Confirmed Bug description: This bug is for tracking the 4.18.0-1002.3 upload package. This bug will contain status and testing re
[Kernel-packages] [Bug 1796647] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1796647/+attachment/5199149/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796647 Title: Shared folders cannot be mounted in ubuntu/cosmic64 due to missing vbox modules Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: In bionic, the vboxsf module was included in linux- modules-...-generic: $ dpkg -c linux-modules-4.15.0-36-generic_4.15.0-36.39_amd64.deb | grep vboxsf.ko -rw-r--r-- root/root 63238 2018-09-24 10:08 ./lib/modules/4.15.0-36-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko In cosmic, it isn't: $ dpkg -c ~/Downloads/linux- modules-4.18.0-9-generic_4.18.0-9.10_amd64.deb | grep vboxsf.ko This results in shared folders no longer being mountable in Ubuntu Vagrant boxes (and, as the other vbox modules are also missing, probably has other effects that haven't yet been reported). [Original Report] Just tried to test out the new cosmic64 vagrant box and get the following error; ``` Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available. This filesystem is made available via the VirtualBox Guest Additions and kernel module. Please verify that these guest additions are properly installed in the guest. This is not a bug in Vagrant and is usually caused by a faulty Vagrant box. For context, the command attempted was: mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant The error output from the command was: /sbin/mount.vboxsf: mounting failed with the error: No such device ``` I tried with ubuntu/bionic64 and it worked fine. I've got; $ vagrant version Installed Version: 2.1.5 Latest Version: 2.1.5 You're running an up-to-date version of Vagrant! $ VBoxManage --version 5.2.18r124319 $ To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1796647/+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 1796743] Re: Ubuntu 18.10 - Alienware 17 R5 crashes on sleep
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged -- 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/1796743 Title: Ubuntu 18.10 - Alienware 17 R5 crashes on sleep Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: If the machine goes to sleep, either because I close the lid or because it idles too long, it ends up in a weird state when I try to resume. If I press the power/Alien button, the fan runs and the keyboard/trackpad light up but nothing happens. Ultimately I need to hard power off the laptop (by holding the power button in for three seconds) which causes it to boot from scratch. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: feoh 2895 F pulseaudio CurrentDesktop: GNOME Date: Mon Oct 8 14:25:16 2018 InstallationDate: Installed on 2018-10-07 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) MachineType: Alienware Alienware 17 R5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=c3d3798c-6179-472a-ba82-55ef94f4d382 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2018 dmi.bios.vendor: Alienware dmi.bios.version: 1.5.0 dmi.board.name: Alienware 17 R5 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.5.0:bd08/10/2018:svnAlienware:pnAlienware17R5:pvr1.5.0:rvnAlienware:rnAlienware17R5:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware 17 R5 dmi.product.sku: 0877 dmi.product.version: 1.5.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796743/+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 1796585] [NEW] package linux-image-extra-4.10.0-35-generic 4.10.0-35.39~16.04.1 failed to install/upgrade: package linux-image-extra-4.10.0-35-generic is not ready for configura
You have been subscribed to a public bug: Errors were encountered while processing: linux-image-extra-4.10.0-35-generic E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.10.0-35-generic 4.10.0-35.39~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Oct 7 20:12:25 2018 DuplicateSignature: package:linux-image-extra-4.10.0-35-generic:4.10.0-35.39~16.04.1 Processing triggers for doc-base (0.10.7) ... Processing 3 changed doc-base files... dpkg: error processing package linux-image-extra-4.10.0-35-generic (--configure): package linux-image-extra-4.10.0-35-generic is not ready for configuration ErrorMessage: package linux-image-extra-4.10.0-35-generic is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-08-28 (404 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: linux-hwe Title: package linux-image-extra-4.10.0-35-generic 4.10.0-35.39~16.04.1 failed to install/upgrade: package linux-image-extra-4.10.0-35-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: Upgraded to xenial on 2018-10-07 (0 days ago) ** Affects: linux (Ubuntu) Importance: Medium Status: Incomplete ** Tags: amd64 apport-package xenial -- package linux-image-extra-4.10.0-35-generic 4.10.0-35.39~16.04.1 failed to install/upgrade: package linux-image-extra-4.10.0-35-generic is not ready for configuration cannot configure (current status 'half-installed') https://bugs.launchpad.net/bugs/1796585 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796659] Re: ubuntu freezes compleet
Do you have a way to reproduce this bug, or was it a one time event? ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796659 Title: ubuntu freezes compleet Status in linux package in Ubuntu: Incomplete Bug description: computer freezes, no more movement, force to power of and restart,,, ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-36-generic 4.15.0-36.39 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jan1347 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 8 10:28:08 2018 HibernationDevice: RESUME=UUID=a3218aa4-b21a-499d-8464-e926cb2d27c6 InstallationDate: Installed on 2018-10-01 (6 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 003: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd (Foxlink) Webcam Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP 15 Notebook PC ProcEnviron: LANG=nl_NL.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.17 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2213 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.17:bd05/07/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097313405F0620180:rvnHewlett-Packard:rn2213:rvr57.24:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 Notebook PC dmi.product.version: 097313405F0620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796659/+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 1796573] Re: Keyboard backlight not working on ubuntu 18.10, but works on 18.04
** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- 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/1796573 Title: Keyboard backlight not working on ubuntu 18.10, but works on 18.04 Status in Linux: Unknown Status in linux package in Ubuntu: Incomplete Bug description: 1) 18.10 2) 3) keyboard backlight turns on 4) nothing I have ASUS s14 s406ua laptop and I can't turn my keyboard backlight on... ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nadavshabtai 2215 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 7 19:21:02 2018 InstallationDate: Installed on 2018-09-28 (9 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 003: ID 13d3:3500 IMC Networks Bus 001 Device 002: ID 13d3:56a2 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X406UAR ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=35bafd0c-f18c-4cc0-9146-d0f9f77447ff ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-09-28 (9 days ago) dmi.bios.date: 04/24/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X406UAR.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X406UAR 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.:bvrX406UAR.309:bd04/24/2018:svnASUSTeKCOMPUTERINC.:pnX406UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX406UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X406UAR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796573/+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 1796647] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1796647/+attachment/5199147/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796647 Title: Shared folders cannot be mounted in ubuntu/cosmic64 due to missing vbox modules Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: In bionic, the vboxsf module was included in linux- modules-...-generic: $ dpkg -c linux-modules-4.15.0-36-generic_4.15.0-36.39_amd64.deb | grep vboxsf.ko -rw-r--r-- root/root 63238 2018-09-24 10:08 ./lib/modules/4.15.0-36-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko In cosmic, it isn't: $ dpkg -c ~/Downloads/linux- modules-4.18.0-9-generic_4.18.0-9.10_amd64.deb | grep vboxsf.ko This results in shared folders no longer being mountable in Ubuntu Vagrant boxes (and, as the other vbox modules are also missing, probably has other effects that haven't yet been reported). [Original Report] Just tried to test out the new cosmic64 vagrant box and get the following error; ``` Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available. This filesystem is made available via the VirtualBox Guest Additions and kernel module. Please verify that these guest additions are properly installed in the guest. This is not a bug in Vagrant and is usually caused by a faulty Vagrant box. For context, the command attempted was: mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant The error output from the command was: /sbin/mount.vboxsf: mounting failed with the error: No such device ``` I tried with ubuntu/bionic64 and it worked fine. I've got; $ vagrant version Installed Version: 2.1.5 Latest Version: 2.1.5 You're running an up-to-date version of Vagrant! $ VBoxManage --version 5.2.18r124319 $ To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1796647/+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 1795698] Re: Cannot communicate with bitbucket repo through ssh
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: needs-bisect -- 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/1795698 Title: Cannot communicate with bitbucket repo through ssh Status in linux package in Ubuntu: Incomplete Bug description: After upgrading to kernal 4.15.0-36.39~16.04.1 this morning (2018-10-02) I am no longer able to communicate with remote repos using ssh keys. Reverting back to the previous kernal ( 4.15.0-34.37~16.04.1 ) fixes this issue. Git version is 2.19.0 1) Description: Ubuntu 16.04.5 LTS Release: 16.04 2) Unsure of the specific package that is the issue. There is something different between the two kernals mentioned. The latest kernal is causing the issue. 3) When performing any git commands that require communication with the remote I expect that I will get some communication back from the remote about the success or failure of the request. 4) What actually happens is any action that requires interaction with the remote simply hangs indefinitely. There is no success or failure. It simply hangs until I kill the process with crtl+c. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795698/+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 1796647] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1796647/+attachment/5199148/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796647 Title: Shared folders cannot be mounted in ubuntu/cosmic64 due to missing vbox modules Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: In bionic, the vboxsf module was included in linux- modules-...-generic: $ dpkg -c linux-modules-4.15.0-36-generic_4.15.0-36.39_amd64.deb | grep vboxsf.ko -rw-r--r-- root/root 63238 2018-09-24 10:08 ./lib/modules/4.15.0-36-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko In cosmic, it isn't: $ dpkg -c ~/Downloads/linux- modules-4.18.0-9-generic_4.18.0-9.10_amd64.deb | grep vboxsf.ko This results in shared folders no longer being mountable in Ubuntu Vagrant boxes (and, as the other vbox modules are also missing, probably has other effects that haven't yet been reported). [Original Report] Just tried to test out the new cosmic64 vagrant box and get the following error; ``` Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available. This filesystem is made available via the VirtualBox Guest Additions and kernel module. Please verify that these guest additions are properly installed in the guest. This is not a bug in Vagrant and is usually caused by a faulty Vagrant box. For context, the command attempted was: mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant The error output from the command was: /sbin/mount.vboxsf: mounting failed with the error: No such device ``` I tried with ubuntu/bionic64 and it worked fine. I've got; $ vagrant version Installed Version: 2.1.5 Latest Version: 2.1.5 You're running an up-to-date version of Vagrant! $ VBoxManage --version 5.2.18r124319 $ To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1796647/+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 1796580] Re: Touchscreen breaks after suspend on Acer Aspire Switch 11
** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- 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/1796580 Title: Touchscreen breaks after suspend on Acer Aspire Switch 11 Status in linux package in Ubuntu: Incomplete Bug description: I'm not entirely sure this bug belongs in package xinput, but I'm following the lead of https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1275416, which describes the same symptoms (but on other hardware, so likely a different underlying problem). On this notebook, the touchscreen works well out of the box. But as soon as I suspend (by pressing the power button or closing the lid) and resume again, the touch screen no longer works. Kernel and Xorg logs show no indication of any problem, xinput still lists the touchscreen, but it just no longer works. The touchscreen can be made to work again by reloading the hid_multitouch module (that works by unloading and reloading after a resume, or by unloading the module before suspend and reloading it after resume). I tried updating the bios from v1.03 to the latest v1.04 (no changelog available), but that did not change the problem. I'm attaching a dmesg.txt in addition to the stuff ubuntu-bug collected. In this dmesg log, I've shown a full boot, a suspend (breaking the touchscreen), a module reload (fixing the touchscreen), then a module unload, suspend and module reload, after which the touchscreen also works (I've added annotations to the log to indicate what happens when). The log also shows some USB-related errors after suspend, but that seems to be about the bluetooth adapter (looking at the usb ids), so I think these are unrelated. The touchscreen in question seems to be connected through I2c, according to dmesg: [4.561527] input: SYNA7508:00 06CB:77B2 Pen as /devices/pci:00/INT33C3:00/i2c-1/i2c-SYNA7508:00/0018:06CB:77B2.0002/input/input8 [4.561741] input: SYNA7508:00 06CB:77B2 as /devices/pci:00/INT33C3:00/i2c-1/i2c-SYNA7508:00/0018:06CB:77B2.0002/input/input9 [4.561917] hid-multitouch 0018:06CB:77B2.0002: input,hidraw1: I2C HID v1.00 Mouse [SYNA7508:00 06CB:77B2] on i2c-SYNA7508:00 I realize that this is not enough information to diagnose and fix the problem, but I'd gladly receive some suggestions on debug strategies to dig into this issue. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xinput 1.6.2-1build1 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 7 19:40:05 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:0a1e] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0930] InstallationDate: Installed on 2018-10-06 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Acer Aspire SW5-171P ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=4893a2e6-84af-4d45-8e31-773e622c36c6 ro quiet splash vt.handoff=1 SourcePackage: xinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/7/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Longchamp_S dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd11/7/2014:svnAcer:pnAspireSW5-171P:pvrV1.04:rvnAcer:rnLongchamp_S:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Haswell-Y System dmi.product.name: Aspire SW5-171P dmi.product.version: V1.04 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796580/+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/Li
[Kernel-packages] [Bug 1790652] Re: Oracle cosmic image does not find broadcom network device in Shape VMStandard2.1
Seth, I've installed your kernel in an image that wasn't booting on the instance type and validated that the test kernel from comment #12 does fix boot. $ sudo ethtool -i ens3 driver: bnxt_en version: 1.9.1 firmware-version: 20.8.172.0/pkg 20.8.29.0 expansion-rom-version: bus-info: :00:03.0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no $ uname -a Linux rcj-lp1790652-21 4.18.0-8-generic #9+lp1790652v201809170859 SMP Mon Sep 17 07:01:34 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ dmesg|grep bnx [2.366526] Broadcom NetXtreme-C/E driver bnxt_en v1.9.1 [2.384175] bnxt_en :00:03.0 (unnamed net_device) (uninitialized): hwrm req_type 0xf seq id 0x5 error 0x [2.394757] bnxt_en :00:03.0 eth0: Broadcom NetXtreme-E Ethernet Virtual Function found at mem 200010, node addr 00:00:17:02:42:58 [2.401353] bnxt_en :00:03.0: 0.000 Gb/s available PCIe bandwidth, limited by Unknown speed x0 link at :00:03.0 (capable of 63.008 Gb/s with 8 GT/s x8 link) [2.474211] bnxt_en :00:03.0 ens3: renamed from eth0 [4.379763] bnxt_en :00:03.0 ens3: NIC Link is Up, 25000 Mbps full duplex, Flow control: none [4.382846] bnxt_en :00:03.0 ens3: FEC autoneg off encodings: None -- 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/1790652 Title: Oracle cosmic image does not find broadcom network device in Shape VMStandard2.1 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: I tried to register and boot a cosmic image to verify new changes in it and in cloud-init. The image failed to bring up networking in the initramfs, and thus failed to find iscsi root. this could be user error. Here is what I did to publish the image. - use oci build tool [1]. following https://docs.cloud.oracle.com/iaas/Content/Compute/Tasks/imageimportexport.htm#ImportinganImage - Download a livefs build from cloudware https://launchpad.net/~cloudware/+livefs/ubuntu/cosmic/cpc/ example: livecd.ubuntu-cpc.oracle_bare_metal.img My image had version 20180821.1 - oci os bucket create --name=smoser-devel - oci os object put \ --parallel-upload-count=4 \ --part-size=10 \ --bucket-name=smoser-devel \ --file=/tmp/livecd.ubuntu-cpc.oracle_bare_metal.img \ --name=cosmic-20180821.1.img - import the object $ oci compute image import from-object \ --display-name=smoser-cosmic-20180821.1.img \ --launch-mode=NATIVE \ --namespace=intcanonical \ --bucket-name=smoser-devel \ --name=cosmic-20180821.1.img \ --source-image-type=QCOW2 Then I launched from the web UI a VM.Standard2.1. -- https://docs.cloud.oracle.com/iaas/Content/API/Concepts/cliconcepts.htm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790652/+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 1792195] Comment bridged from LTC Bugzilla
--- Comment From mranw...@us.ibm.com 2018-10-09 13:31 EDT--- We can recreate this without GPFS using a modified version of the tests here: https://github.com/NVIDIA/gdrcopy Working on the DD1 removal backport. -- 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/1792195 Title: Signal 7 error when running GPFS tracing in cluster Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: -- Problem Description -- GPFS mmfsd daemon is mapping shared tracing buffer(allocated from kernel driver using vmalloc) and then writing trace records from user space threads in parallel. While the SIGBUS happened, the access virtual memory address is in the mapped range, no overflow on access. Worked with Benjamin Herrenschmidt on GPFS tracing kernel driver code and he made a suggestion as workaround on the driver code to bypass the problem, and it works the workaround code change as below: - rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, PAGE_SHARED); + rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, __pgprot(pgprot_val(PAGE_SHARED)|_PAGE_DIRTY); As Benjamin mentioned, this is a Linux kernel bug and this is just a workaround. He will give the details about the kernel bug and why this workaround works The root cause is that for PTEs created by a driver at mmap time (ie, that aren't created dynamically at fault time), it's not legit for ptep_set_access_flags() to make them invalid even temporarily. A concurrent access while they are invalid will be unable to service the page fault and will cause as SIGBUS. Thankfully such PTEs shouldn't normally be the subject of a RO->RW privilege escalation. What happens is that the GPFS driver creates the PTEs using remap_pfn_range(...,PAGE_SHARED). PAGE_SHARED has _PAGE_ACCESSED (R) but not _PAGE_DIRTY (C) set. Thus on the first write, we try set C and while doing so, hit the above workaround, which causes the problem described earlier. The proposed patch will ensure we only do the Nest MMU hack when changing _PAGE_RW and not for normal R/C updates. The workaround tested by the GPFS team consists of adding _PAGE_DIRTY to the mapping created by remap_pfn_range() to avoid the RC update fault completely. This is fixed by these: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd0dbb73e01306a1060e56f81e5fe287be936477 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f08d08f3db55452d31ba4a37c702da6245876b96 Since DD1 support is still in (ie, 2bf1071a8d50928a4ae366bb3108833166c2b70c is not applied) the second doesn't apply cleanly. Did you want that attached? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1792195/+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 1796542] Re: Silent data corruption in Linux kernel 4.15
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => In Progress
--
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/1796542
Title:
Silent data corruption in Linux kernel 4.15
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
In Progress
Bug description:
== SRU Justification [BIONIC] ==
A silent data corruption was introduced in v4.10-rc1 with commit
72ecad22d9f198aafee64218512e02ffa7818671 and was fixed in v4.18-rc7
with commit 17d51b10d7773e4618bcac64648f30f12d4078fb. It affects
users of O_DIRECT, in our case a KVM virtual machine with drives
which use qemu's "cache=none" option.
== Fix ==
Upstream commits:
0aa69fd32a5f766e997ca8ab4723c5a1146efa8b
block: add a lower-level bio_add_page interface
b403ea2404889e1227812fa9657667a1deb9c694
block: bio_iov_iter_get_pages: fix size of last iovec
9362dd1109f87a9d0a798fbc890cb339c171ed35
blkdev: __blkdev_direct_IO_simple: fix leak in error case
17d51b10d7773e4618bcac64648f30f12d4078fb
block: bio_iov_iter_get_pages: pin more pages for multi-segment IOs
The first 3 patches are required for a clean application of the final
patch that actually addresses the problem with a fix to this known
issue.
== Regression Potential ==
This touches the block layer, so there is risk potential in data
corruption. The fixes have several weeks in the upstream kernel and
so far, I see no subsequent fixes required.
== Test Case ==
Build the program listed below [1]
kudos to Jan Kara, and run with:
dd if=/dev/zero if=loop.img bs=1M count=2048
sudo losetup /dev/loop0 loop.img
./blkdev-dio-test /dev/loop0 0 &
./blkdev-dio-test /dev/loop0 2048 &
Without the fix, ones lost writes fairly soon. Without the fix, this
runs without any losy write messages.
blkdev-dio-test.c:
#define _GNU_SOURCE
#include
#include
#include
#include
#include
#include
#define PAGE_SIZE 4096
#define SECT_SIZE 512
#define BUF_OFF (2*SECT_SIZE)
int main(int argc, char **argv)
{
int fd = open(argv[1], O_RDWR | O_DIRECT);
int ret;
char *buf;
loff_t off;
struct iovec iov[2];
unsigned int seq;
if (fd < 0) {
perror("open");
return 1;
}
off = strtol(argv[2], NULL, 10);
buf = aligned_alloc(PAGE_SIZE, PAGE_SIZE);
iov[0].iov_base = buf;
iov[0].iov_len = SECT_SIZE;
iov[1].iov_base = buf + BUF_OFF;
iov[1].iov_len = SECT_SIZE;
seq = 0;
memset(buf, 0, PAGE_SIZE);
while (1) {
*(unsigned int *)buf = seq;
*(unsigned int *)(buf + BUF_OFF) = seq;
ret = pwritev(fd, iov, 2, off);
if (ret < 0) {
perror("pwritev");
return 1;
}
if (ret != 2*SECT_SIZE) {
fprintf(stderr, "Short pwritev: %d\n", ret);
return 1;
}
ret = pread(fd, buf, PAGE_SIZE, off);
if (ret < 0) {
perror("pread");
return 1;
}
if (ret != PAGE_SIZE) {
fprintf(stderr, "Short read: %d\n", ret);
return 1;
}
if (*(unsigned int *)buf != seq ||
*(unsigned int *)(buf + SECT_SIZE) != seq) {
printf("Lost write %u: %u %u\n", seq, *(unsigned int *)buf, *(unsigned int
*)(buf + SECT_SIZE));
return 1;
}
seq++;
}
return 0;
}
References:
[1] https://www.spinics.net/lists/linux-block/msg28507.html
TLDR: commit 72ecad22d9f198aafee64218512e02ffa7818671 (in v4.10)
introduced silent data corruption for O_DIRECT uses, it's fixed in
17d51b10d7773e4618bcac64648f30f12d4078fb (in v4.18)
A silent data corruption was introduced in v4.10-rc1 with commit
72ecad22d9f198aafee64218512e02ffa7818671 and was fixed in v4.18-rc7
with commit 17d51b10d7773e4618bcac64648f30f12d4078fb. It affects users
of O_DIRECT, in our case a KVM virtual machine with drives which use
qemu's "cache=none" option.
This is the commit which fixes the issue:
-
commit 17d51b10d7773e4618bcac64648f30f12d4078fb
Author: Martin Wilck
Date: Wed Jul 25 23:15:09 2018 +0200
block: bio_iov_iter_get_pages: pin more pages for multi-segment
IOs
bio_iov_iter_get_pages() currently only adds pages for the next non-zero
segment from the iov_iter to the bio. That's suboptimal for callers,
which typically try to pin as many pages as fit into the bio. This patch
converts the current bio_iov_iter_get_pages() into a static helper, and
introduces a new helper that allocates as many pages as
1) fit into the bio,
2) are present in the iov_iter,
3) and can be pinned by MM.
Error is returned only if zero pages could be pinned. Because of 3), a
zero return value doesn't necessarily mean all pages have been pinned.
Callers that have to pin every page in the iov_iter must still call this
function in a loop (this is currently the case).
[Kernel-packages] [Bug 1796574] Re: Black screen on boot with AMD Radeon HD 7970/8970 OEM / R9 280X
** Changed in: linux (Ubuntu) Importance: Undecided => High ** 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/1796574 Title: Black screen on boot with AMD Radeon HD 7970/8970 OEM / R9 280X Status in linux package in Ubuntu: Invalid Bug description: [1] Using the default "radeon" driver result in black screen on boot. Waiting until what looks like X finish initializing, putting the computer to sleep and awake it again almost always works as a workaround. dmesg: [5.165441] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed: 5 tries [5.165453] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed And it looks like the DisplayPort is not initialized correctly. "Black screen" in this context means nothing works (no TTY:s). [2] Disabling si_support (GCN 1.0) in grub results in system always boot correct from a shutdown state but awake from sleep doesn't work. [3] Switching to the experimental (for GCN 1.0 cards) amdgpu driver result in the same behavior as in [2]. [xrandr] DisplayPort-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 59.95*+ 1280x720 59.86 [lshw -c display] *-display description: VGA compatible controller product: Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:02:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:57 memory:c000-cfff memory:fbe0-fbe3 ioport:e000(size=256) memory:c-d --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: andreas2086 F pulseaudio /dev/snd/controlC0: andreas2086 F pulseaudio /dev/snd/controlC1: andreas2086 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=fa1b42ae-604b-448d-a294-6578ef07f7fe InstallationDate: Installed on 2018-10-06 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=/dev/mapper/ubuntu--vg-root ro splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-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: 12/25/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3305 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3305:bd12/25/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796574/+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 1796659] Re: ubuntu freezes compleet
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc7 -- 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/1796659 Title: ubuntu freezes compleet Status in linux package in Ubuntu: Incomplete Bug description: computer freezes, no more movement, force to power of and restart,,, ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-36-generic 4.15.0-36.39 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jan1347 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 8 10:28:08 2018 HibernationDevice: RESUME=UUID=a3218aa4-b21a-499d-8464-e926cb2d27c6 InstallationDate: Installed on 2018-10-01 (6 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 003: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd (Foxlink) Webcam Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP 15 Notebook PC ProcEnviron: LANG=nl_NL.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.17 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2213 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.17:bd05/07/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097313405F0620180:rvnHewlett-Packard:rn2213:rvr57.24:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 Notebook PC dmi.product.version: 097313405F0620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796659/+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 1796582] Re: Internal microphone not working on Lenovo Ideapad 330S-15ARR
** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- 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/1796582 Title: Internal microphone not working on Lenovo Ideapad 330S-15ARR Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: The internal microphone on this troublesome laptop stopped working after upgrading from Bionic to Cosmic. There is no signal from the microphone with kernel 4.18.0-7 or 4.18.0-8. This DOES work correctly with kernel 4.15.0-34 that is still present on Cosmic after the upgrade. I recommend Canonical gets this laptop for testing since a ton of stuff is troublesome on this Raven Ridge laptop. Would be a good specimen to get support for this platform improved. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xorbit 2295 F pulseaudio /dev/snd/controlC0: xorbit 2295 F pulseaudio CurrentDesktop: GNOME Date: Sun Oct 7 12:02:45 2018 InstallationDate: Installed on 2018-09-20 (17 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81FB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic rcu_nocbs=0-7 quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-09-30 (6 days ago) dmi.bios.date: 09/05/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7WCN26WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7WCN26WW:bd09/05/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR: dmi.product.family: ideapad 330S-15ARR dmi.product.name: 81FB dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR dmi.product.version: Lenovo ideapad 330S-15ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796582/+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 1794074] Re: xhci_hcd 0000:25:00.0: ERROR unknown event type 15
** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1794074 Title: xhci_hcd :25:00.0: ERROR unknown event type 15 Status in linux package in Ubuntu: New Bug description: Using Ubuntu 18.04 as a bare-metal VM server via libvirtd qemu-kvm, after some time with the guests running, xhci freaks out and thinks the server died and disables all USB devices. xhci_hcd :25:00.0: ERROR unknown event type 15 xhci_hcd :25:00.0: xHCI host not responding to stop endpoint command. xhci_hcd :25:00.0: xHCI host controller not responding, assume dead xhci_hcd :25:00.0: HC died; cleaning up --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-34-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jimmy 6534 F pulseaudio /dev/snd/controlC3: jimmy 6534 F pulseaudio /dev/snd/controlC1: jimmy 6534 F pulseaudio Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card3.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card3.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Micro-Star International Co., Ltd. MS-7A33 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=9195c88f-be47-11e8-b927-309c2327f349 ro ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt libvirt-dnsmasq lxd plugdev sudo video _MarkForUpload: True dmi.bios.date: 07/11/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.D0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X370 SLI PLUS (MS-7A33) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.D0:bd07/11/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A33:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnX370SLIPLUS(MS-7A33):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A33 dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794074/+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 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
Hi Guillaume, would it be possible to provide step-by-step instructions to reproduce this issue? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode Status in linux package in Ubuntu: Confirmed Bug description: Since the following linux-cloud-tools-common package versions : Xenial : 4.4.0-135.161 Bionic : 4.15.0-34.37 the Systemd service unit file for hv-kvp-daemon has been modified with new dependencies that make the package unable to be upgraded with unattended-upgrades on shutdown mode. Unattended-upgrades hangs with the linux-cloud-tools-common package during "Preparing to unpack". The server restarts after the unattended-upgrades service timeout expires. - Package state after reboot : iFR linux-cloud-tools-common 4.15.0-34.37 all Linux kernel version specific cloud tools for version 4.15.0 - Unattended-upgrades dpkg logs : Log started: 2018-10-05 17:59:04 (Reading database ... 52043 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ... Log ended: 2018-10-05 18:00:54 - Impact : The current impact is very important as all security updates are blocked until you manually fix each server with : dpkg --configure -a apt install --only-upgrade linux-cloud-tools-common - Workaround/Fix : As a simple straightforward fix, replacing : Before=shutdown.target cloud-init-local.service walinuxagent.service with : Before=shutdown.target walinuxagent.service makes the package upgradable during shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+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 1795585] Re: linux-aws: 4.4.0-1070.80 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1795585 Title: linux-aws: 4.4.0-1070.80 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1795582 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795585/+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 1796839] Re: Only 64 Memory regions or dimms supported for Hotplug.
** Tags added: kernel-da-key -- 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/1796839 Title: Only 64 Memory regions or dimms supported for Hotplug. Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: == Comment: #0 - HARIHARAN T. SUNDARESH REDDY - 2018-10-03 01:29:59 == Description : Hotplug is supported only for 64 dimms and the same is controlled by the sysfs parameter # cat /sys/module/vhost/parameters/max_mem_regions 64 However qemu supports 256 slots max. In my opinion max_mem_regions must be >= 256. log : 63 Device attached successfully<--- 63 times devices attached successfully, later all attach failed. 64 error: Failed to attach device from hp_mem.xml error: internal error: unable to execute QEMU command 'device_add': a used vhost backend has no free memory slots left 65 error: Failed to attach device from hp_mem.xml error: internal error: unable to execute QEMU command 'device_add': a used vhost backend has no free memory slots left 66 error: Failed to attach device from hp_mem.xml error: internal error: unable to execute QEMU command 'device_add': a used vhost backend has no free memory slots left System Details : uname -a Linux ltc-fvttest 4.18.5-custom #1 SMP Wed Sep 26 12:11:51 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@ltc-fvttest:/home/hariharan# cat /etc/os-release NAME="Ubuntu" VERSION="18.10 (Cosmic Cuttlefish)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu Cosmic Cuttlefish (development branch)" VERSION_ID="18.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=cosmic UBUNTU_CODENAME=cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1796839/+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 1796748] Re: regression in 'ip --family bridge neigh' since linux v4.12
** Changed in: linux (Ubuntu Bionic)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
--
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/1796748
Title:
regression in 'ip --family bridge neigh' since linux v4.12
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Bionic:
Triaged
Bug description:
[Impact]
* Netlink RTM_GETNEIGH requests for PF_BRIDGE are broken since linux
v4.12.
* Users, tools (e.g., iproute2), and libraries (e.g., go netlink) that use
such request/family currently receive nothing back in the kernel response.
* The upstream fix resolves the breakage in the userspace-kernel interface
by explicitly checking for the old/broken request to ensure it's replied.
[Test Case]
* The command 'ip --family bridge neigh' returns nothing on broken kernels,
and matches 'bridge fdb show' on fixed kernels.
* Before:
$ ip --family bridge neigh
$
* After:
$ ip --family bridge neigh
dev ens3 lladdr 33:33:00:00:00:01 PERMANENT
dev ens3 lladdr 01:00:5e:00:00:01 PERMANENT
dev ens3 lladdr 33:33:ff:e9:9d:60 PERMANENT
* Reference:
$ bridge fdb show
33:33:00:00:00:01 dev ens3 self permanent
01:00:5e:00:00:01 dev ens3 self permanent
33:33:ff:e9:9d:60 dev ens3 self permanent
[Regression Potential]
* Low, for three reasons:
* The fix is fairly contained (RTM_GETNEIGH request for PF_BRIDGE
family).
* The checks introduced by the fix are conservative, based on the size
of the old request (the size of the old/new requests are different),
and it does nothing different in case the (old) size doesn't match.
* Given the above, only applications with message length and contents
specially hand-crafted (and likely not valid nor useful) might fail.
To the best of my knowledge, this is not the common case out there.
[Other Info]
* The patch is only applicable to v4.12+ (so not Trusty nor Xenial).
* The patch is the same for Bionic, Cosmic, and unstable.
* Upstream commit: bd961c9bc664 ("rtnetlink: fix rtnl_fdb_dump() for ndmsg
header")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd961c9bc66497f0c63f4ba1d02900bb85078366
* I'll submit the patch shortly to the kernel-team mailing list.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796748/+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 1796895] Re: Kernel 4.15.0-36 network performance regression
I'm seeing similar behavior on multiple physical hosts running 4.15.0-36-generic. The TCP window size only appears to grow very slightly (from initial of 224 to around 1400) during the entire length of the transfer. Downgrading to 4.15.0-34-generic fixes the issue for me - TCP window size continues to grow until it is around 24k. -- 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/1796895 Title: Kernel 4.15.0-36 network performance regression Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Hardware: HP DL380 Gen 7 server with Gigabit interface. Ubuntu release: 18.04.1 Since upgrading from 4.15.0-33 to 4.15.0-36, I have noticed a dramatic slowdown in TCP over IPv6. Set up: two servers, Server A in US on Ubuntu 18.04.1, Server B in Europe. Test: Sending 400MB over TCP from Server B to Server A. With 4.15.0-33 on Server A, the transfer is completed in 24 seconds, with average speed of 139 mbps. With 4.15.0-36 on Server A, the same amount of data is transferred in 369 seconds, average speed less than 9 mbps. Looking at the result from tcpdump, I see that the there is a big difference in the TCP Window size. With 3.15-0.33 the TCP window size is around 3. But with 3.15-0.36, the window size is only 734. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796895/+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 1796647] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1796647/+attachment/5199150/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796647 Title: Shared folders cannot be mounted in ubuntu/cosmic64 due to missing vbox modules Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: In bionic, the vboxsf module was included in linux- modules-...-generic: $ dpkg -c linux-modules-4.15.0-36-generic_4.15.0-36.39_amd64.deb | grep vboxsf.ko -rw-r--r-- root/root 63238 2018-09-24 10:08 ./lib/modules/4.15.0-36-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko In cosmic, it isn't: $ dpkg -c ~/Downloads/linux- modules-4.18.0-9-generic_4.18.0-9.10_amd64.deb | grep vboxsf.ko This results in shared folders no longer being mountable in Ubuntu Vagrant boxes (and, as the other vbox modules are also missing, probably has other effects that haven't yet been reported). [Original Report] Just tried to test out the new cosmic64 vagrant box and get the following error; ``` Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available. This filesystem is made available via the VirtualBox Guest Additions and kernel module. Please verify that these guest additions are properly installed in the guest. This is not a bug in Vagrant and is usually caused by a faulty Vagrant box. For context, the command attempted was: mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant The error output from the command was: /sbin/mount.vboxsf: mounting failed with the error: No such device ``` I tried with ubuntu/bionic64 and it worked fine. I've got; $ vagrant version Installed Version: 2.1.5 Latest Version: 2.1.5 You're running an up-to-date version of Vagrant! $ VBoxManage --version 5.2.18r124319 $ To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1796647/+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 1796895] Re: Kernel 4.15.0-36 network performance regression
It might also be good to test the latest mainline kernel to see if this issue also exists upstream, if it is fixed upstream and/or if this regression is Ubuntu specific. The mainline kernel is available from: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc7 Some documentation regarding mainline is available here: https://wiki.ubuntu.com/KernelMainlineBuilds -- 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/1796895 Title: Kernel 4.15.0-36 network performance regression Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Hardware: HP DL380 Gen 7 server with Gigabit interface. Ubuntu release: 18.04.1 Since upgrading from 4.15.0-33 to 4.15.0-36, I have noticed a dramatic slowdown in TCP over IPv6. Set up: two servers, Server A in US on Ubuntu 18.04.1, Server B in Europe. Test: Sending 400MB over TCP from Server B to Server A. With 4.15.0-33 on Server A, the transfer is completed in 24 seconds, with average speed of 139 mbps. With 4.15.0-36 on Server A, the same amount of data is transferred in 369 seconds, average speed less than 9 mbps. Looking at the result from tcpdump, I see that the there is a big difference in the TCP Window size. With 3.15-0.33 the TCP window size is around 3. But with 3.15-0.36, the window size is only 734. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796895/+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 1796647] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1796647/+attachment/5199143/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796647 Title: Shared folders cannot be mounted in ubuntu/cosmic64 due to missing vbox modules Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: In bionic, the vboxsf module was included in linux- modules-...-generic: $ dpkg -c linux-modules-4.15.0-36-generic_4.15.0-36.39_amd64.deb | grep vboxsf.ko -rw-r--r-- root/root 63238 2018-09-24 10:08 ./lib/modules/4.15.0-36-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko In cosmic, it isn't: $ dpkg -c ~/Downloads/linux- modules-4.18.0-9-generic_4.18.0-9.10_amd64.deb | grep vboxsf.ko This results in shared folders no longer being mountable in Ubuntu Vagrant boxes (and, as the other vbox modules are also missing, probably has other effects that haven't yet been reported). [Original Report] Just tried to test out the new cosmic64 vagrant box and get the following error; ``` Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available. This filesystem is made available via the VirtualBox Guest Additions and kernel module. Please verify that these guest additions are properly installed in the guest. This is not a bug in Vagrant and is usually caused by a faulty Vagrant box. For context, the command attempted was: mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant The error output from the command was: /sbin/mount.vboxsf: mounting failed with the error: No such device ``` I tried with ubuntu/bionic64 and it worked fine. I've got; $ vagrant version Installed Version: 2.1.5 Latest Version: 2.1.5 You're running an up-to-date version of Vagrant! $ VBoxManage --version 5.2.18r124319 $ To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1796647/+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 1796647] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1796647/+attachment/5199144/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796647 Title: Shared folders cannot be mounted in ubuntu/cosmic64 due to missing vbox modules Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: In bionic, the vboxsf module was included in linux- modules-...-generic: $ dpkg -c linux-modules-4.15.0-36-generic_4.15.0-36.39_amd64.deb | grep vboxsf.ko -rw-r--r-- root/root 63238 2018-09-24 10:08 ./lib/modules/4.15.0-36-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko In cosmic, it isn't: $ dpkg -c ~/Downloads/linux- modules-4.18.0-9-generic_4.18.0-9.10_amd64.deb | grep vboxsf.ko This results in shared folders no longer being mountable in Ubuntu Vagrant boxes (and, as the other vbox modules are also missing, probably has other effects that haven't yet been reported). [Original Report] Just tried to test out the new cosmic64 vagrant box and get the following error; ``` Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available. This filesystem is made available via the VirtualBox Guest Additions and kernel module. Please verify that these guest additions are properly installed in the guest. This is not a bug in Vagrant and is usually caused by a faulty Vagrant box. For context, the command attempted was: mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant The error output from the command was: /sbin/mount.vboxsf: mounting failed with the error: No such device ``` I tried with ubuntu/bionic64 and it worked fine. I've got; $ vagrant version Installed Version: 2.1.5 Latest Version: 2.1.5 You're running an up-to-date version of Vagrant! $ VBoxManage --version 5.2.18r124319 $ To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1796647/+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 1796647] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1796647/+attachment/5199146/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796647 Title: Shared folders cannot be mounted in ubuntu/cosmic64 due to missing vbox modules Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: In bionic, the vboxsf module was included in linux- modules-...-generic: $ dpkg -c linux-modules-4.15.0-36-generic_4.15.0-36.39_amd64.deb | grep vboxsf.ko -rw-r--r-- root/root 63238 2018-09-24 10:08 ./lib/modules/4.15.0-36-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko In cosmic, it isn't: $ dpkg -c ~/Downloads/linux- modules-4.18.0-9-generic_4.18.0-9.10_amd64.deb | grep vboxsf.ko This results in shared folders no longer being mountable in Ubuntu Vagrant boxes (and, as the other vbox modules are also missing, probably has other effects that haven't yet been reported). [Original Report] Just tried to test out the new cosmic64 vagrant box and get the following error; ``` Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available. This filesystem is made available via the VirtualBox Guest Additions and kernel module. Please verify that these guest additions are properly installed in the guest. This is not a bug in Vagrant and is usually caused by a faulty Vagrant box. For context, the command attempted was: mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant The error output from the command was: /sbin/mount.vboxsf: mounting failed with the error: No such device ``` I tried with ubuntu/bionic64 and it worked fine. I've got; $ vagrant version Installed Version: 2.1.5 Latest Version: 2.1.5 You're running an up-to-date version of Vagrant! $ VBoxManage --version 5.2.18r124319 $ To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1796647/+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 1796647] Re: Shared folders cannot be mounted in ubuntu/cosmic64 due to missing vbox modules
ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 9 16:18 seq crw-rw 1 root audio 116, 33 Oct 9 16:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcEnviron: LC_CTYPE=C.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic uec-images Uname: Linux 4.18.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Tags added: apport-collected cosmic uec-images -- 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/1796647 Title: Shared folders cannot be mounted in ubuntu/cosmic64 due to missing vbox modules Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: In bionic, the vboxsf module was included in linux- modules-...-generic: $ dpkg -c linux-modules-4.15.0-36-generic_4.15.0-36.39_amd64.deb | grep vboxsf.ko -rw-r--r-- root/root 63238 2018-09-24 10:08 ./lib/modules/4.15.0-36-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko In cosmic, it isn't: $ dpkg -c ~/Downloads/linux- modules-4.18.0-9-generic_4.18.0-9.10_amd64.deb | grep vboxsf.ko This results in shared folders no longer being mountable in Ubuntu Vagrant boxes (and, as the other vbox modules are also missing, probably has other effects that haven't yet been reported). [Original Report] Just tried to test out the new cosmic64 vagrant box and get the following error; ``` Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available. This filesystem is made available via the VirtualBox Guest Additions and kernel module. Please verify that these guest additions are properly installed in the guest. This is not a bug in Vagrant and is usually caused by a faulty Vagrant box. For context, the command attempted was: mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant The error output from the command was: /sbin/mount.vboxsf: mounting failed with the error: No such device ``` I tried with ubuntu/bionic64 and it worked fine. I've got; $ vagrant version Installed Version: 2.1.5 Latest Version: 2.1.5 You're running an up-to-date version of Vagrant! $ VBoxManage --version 5.2.18r124319 $ To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1796647/+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 1796647] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1796647/+attachment/5199151/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796647 Title: Shared folders cannot be mounted in ubuntu/cosmic64 due to missing vbox modules Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: In bionic, the vboxsf module was included in linux- modules-...-generic: $ dpkg -c linux-modules-4.15.0-36-generic_4.15.0-36.39_amd64.deb | grep vboxsf.ko -rw-r--r-- root/root 63238 2018-09-24 10:08 ./lib/modules/4.15.0-36-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko In cosmic, it isn't: $ dpkg -c ~/Downloads/linux- modules-4.18.0-9-generic_4.18.0-9.10_amd64.deb | grep vboxsf.ko This results in shared folders no longer being mountable in Ubuntu Vagrant boxes (and, as the other vbox modules are also missing, probably has other effects that haven't yet been reported). [Original Report] Just tried to test out the new cosmic64 vagrant box and get the following error; ``` Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available. This filesystem is made available via the VirtualBox Guest Additions and kernel module. Please verify that these guest additions are properly installed in the guest. This is not a bug in Vagrant and is usually caused by a faulty Vagrant box. For context, the command attempted was: mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant The error output from the command was: /sbin/mount.vboxsf: mounting failed with the error: No such device ``` I tried with ubuntu/bionic64 and it worked fine. I've got; $ vagrant version Installed Version: 2.1.5 Latest Version: 2.1.5 You're running an up-to-date version of Vagrant! $ VBoxManage --version 5.2.18r124319 $ To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1796647/+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 1796647] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1796647/+attachment/5199145/+files/PciMultimedia.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796647 Title: Shared folders cannot be mounted in ubuntu/cosmic64 due to missing vbox modules Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: In bionic, the vboxsf module was included in linux- modules-...-generic: $ dpkg -c linux-modules-4.15.0-36-generic_4.15.0-36.39_amd64.deb | grep vboxsf.ko -rw-r--r-- root/root 63238 2018-09-24 10:08 ./lib/modules/4.15.0-36-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko In cosmic, it isn't: $ dpkg -c ~/Downloads/linux- modules-4.18.0-9-generic_4.18.0-9.10_amd64.deb | grep vboxsf.ko This results in shared folders no longer being mountable in Ubuntu Vagrant boxes (and, as the other vbox modules are also missing, probably has other effects that haven't yet been reported). [Original Report] Just tried to test out the new cosmic64 vagrant box and get the following error; ``` Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available. This filesystem is made available via the VirtualBox Guest Additions and kernel module. Please verify that these guest additions are properly installed in the guest. This is not a bug in Vagrant and is usually caused by a faulty Vagrant box. For context, the command attempted was: mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant The error output from the command was: /sbin/mount.vboxsf: mounting failed with the error: No such device ``` I tried with ubuntu/bionic64 and it worked fine. I've got; $ vagrant version Installed Version: 2.1.5 Latest Version: 2.1.5 You're running an up-to-date version of Vagrant! $ VBoxManage --version 5.2.18r124319 $ To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1796647/+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 1796895] Re: Kernel 4.15.0-36 network performance regression
I can perform a kernel bisect to identify the commit that introduced this regression. Before starting the bisect, can you test the -proposed kernel: See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Tags added: bionic performing-bisect ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- 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/1796895 Title: Kernel 4.15.0-36 network performance regression Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Hardware: HP DL380 Gen 7 server with Gigabit interface. Ubuntu release: 18.04.1 Since upgrading from 4.15.0-33 to 4.15.0-36, I have noticed a dramatic slowdown in TCP over IPv6. Set up: two servers, Server A in US on Ubuntu 18.04.1, Server B in Europe. Test: Sending 400MB over TCP from Server B to Server A. With 4.15.0-33 on Server A, the transfer is completed in 24 seconds, with average speed of 139 mbps. With 4.15.0-36 on Server A, the same amount of data is transferred in 369 seconds, average speed less than 9 mbps. Looking at the result from tcpdump, I see that the there is a big difference in the TCP Window size. With 3.15-0.33 the TCP window size is around 3. But with 3.15-0.36, the window size is only 734. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796895/+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 1796350] Re: linux-azure: 4.18.0-1003.3 -proposed tracker
** Summary changed: - linux-azure: -proposed tracker + linux-azure: 4.18.0-1003.3 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri (mhcerri) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri (mhcerri) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri (mhcerri) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1796350 Title: linux-azure: 4.18.0-1003.3 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in linux-azure package in Ubuntu: Confirmed Status in linux-azure source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1796346 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1796350/+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 1796582] Re: Internal microphone not working on Lenovo Ideapad 330S-15ARR
Confirmed on kernel 4.19-rc7. ** Tags added: kernel-bug-exists-upstream -- 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/1796582 Title: Internal microphone not working on Lenovo Ideapad 330S-15ARR Status in Linux: Unknown Status in linux package in Ubuntu: Incomplete Bug description: The internal microphone on this troublesome laptop stopped working after upgrading from Bionic to Cosmic. There is no signal from the microphone with kernel 4.18.0-7 or 4.18.0-8. This DOES work correctly with kernel 4.15.0-34 that is still present on Cosmic after the upgrade. I recommend Canonical gets this laptop for testing since a ton of stuff is troublesome on this Raven Ridge laptop. Would be a good specimen to get support for this platform improved. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xorbit 2295 F pulseaudio /dev/snd/controlC0: xorbit 2295 F pulseaudio CurrentDesktop: GNOME Date: Sun Oct 7 12:02:45 2018 InstallationDate: Installed on 2018-09-20 (17 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81FB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic rcu_nocbs=0-7 quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-09-30 (6 days ago) dmi.bios.date: 09/05/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7WCN26WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7WCN26WW:bd09/05/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR: dmi.product.family: ideapad 330S-15ARR dmi.product.name: 81FB dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR dmi.product.version: Lenovo ideapad 330S-15ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796582/+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 1796647] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1796647 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: bionic -- 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/1796647 Title: Shared folders cannot be mounted in ubuntu/cosmic64 due to missing vbox modules Status in cloud-images: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: In bionic, the vboxsf module was included in linux- modules-...-generic: $ dpkg -c linux-modules-4.15.0-36-generic_4.15.0-36.39_amd64.deb | grep vboxsf.ko -rw-r--r-- root/root 63238 2018-09-24 10:08 ./lib/modules/4.15.0-36-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko In cosmic, it isn't: $ dpkg -c ~/Downloads/linux- modules-4.18.0-9-generic_4.18.0-9.10_amd64.deb | grep vboxsf.ko This results in shared folders no longer being mountable in Ubuntu Vagrant boxes (and, as the other vbox modules are also missing, probably has other effects that haven't yet been reported). [Original Report] Just tried to test out the new cosmic64 vagrant box and get the following error; ``` Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available. This filesystem is made available via the VirtualBox Guest Additions and kernel module. Please verify that these guest additions are properly installed in the guest. This is not a bug in Vagrant and is usually caused by a faulty Vagrant box. For context, the command attempted was: mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant The error output from the command was: /sbin/mount.vboxsf: mounting failed with the error: No such device ``` I tried with ubuntu/bionic64 and it worked fine. I've got; $ vagrant version Installed Version: 2.1.5 Latest Version: 2.1.5 You're running an up-to-date version of Vagrant! $ VBoxManage --version 5.2.18r124319 $ To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1796647/+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 1795585] Re: linux-aws: 4.4.0-1070.80 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1795582 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Tuesday, 09. October 2018 17:00 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1795582 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Tuesday, 09. October 2018 17:00 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1795585 Title: linux-aws: 4.4.0-1070.80 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1795582 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795585/+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 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers with DVD
reboot is triggered using #systemctl reboot. systemd timeout of 30min does not help, system stays hung. Needs a manual power-reset. -- 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/1777674 Title: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers with DVD Status in dellserver: New Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers when under graceful reboot stress for 12hrs. * This hand is observed only when Onboard SATA DVD Drive is connected. * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13) * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic) Steps: Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and start reboot stress After a few reboots, observe that the machine hangs at "kvm: exiting hardware virtualization" and does not proceed with reboot cycles. Only physical reset helps in continuing the reboot test. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1777674/+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 1796904] Re: [Bionic] Update ThunderX2 implementation defined pmu core events
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796904 Title: [Bionic] Update ThunderX2 implementation defined pmu core events Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: [IMPACT] === The ARM architecture defines several events as part of the Performance Monitor Unit (PMU) Extension. In addition, Cavium has added "implementation defined" pmu core events, which Cavium deems most useful for analyzing performance. Currently perf does not list these "implementation defined" events. [FIX] b9b77222d4ff perf vendor events arm64: Update ThunderX2 implementation defined pmu core events [TEST] With the patch applied perf lists the additional PMU events. ubuntu@starbuck:~$ perf list List of pre-defined events (to be used in -e): armv8_pmuv3_0/br_immed_retired/[Kernel PMU event] armv8_pmuv3_0/br_mis_pred/ [Kernel PMU event] armv8_pmuv3_0/br_mis_pred_retired/ [Kernel PMU event] armv8_pmuv3_0/br_pred/ [Kernel PMU event] armv8_pmuv3_0/br_retired/ [Kernel PMU event] armv8_pmuv3_0/br_return_retired/ [Kernel PMU event] armv8_pmuv3_0/bus_access/ [Kernel PMU event] armv8_pmuv3_0/bus_cycles/ [Kernel PMU event] armv8_pmuv3_0/cid_write_retired/ [Kernel PMU event] armv8_pmuv3_0/cpu_cycles/ [Kernel PMU event] armv8_pmuv3_0/exc_return/ [Kernel PMU event] armv8_pmuv3_0/exc_taken/ [Kernel PMU event] armv8_pmuv3_0/inst_retired/[Kernel PMU event] armv8_pmuv3_0/inst_spec/ [Kernel PMU event] armv8_pmuv3_0/l1d_cache/ [Kernel PMU event] armv8_pmuv3_0/l1d_cache_allocate/ [Kernel PMU event] armv8_pmuv3_0/l1d_cache_refill/[Kernel PMU event] armv8_pmuv3_0/l1d_cache_wb/[Kernel PMU event] armv8_pmuv3_0/l1d_tlb/ [Kernel PMU event] armv8_pmuv3_0/l1d_tlb_refill/ [Kernel PMU event] armv8_pmuv3_0/l1i_cache/ [Kernel PMU event] armv8_pmuv3_0/l1i_cache_refill/[Kernel PMU event] armv8_pmuv3_0/l1i_tlb/ [Kernel PMU event] armv8_pmuv3_0/l1i_tlb_refill/ [Kernel PMU event] armv8_pmuv3_0/l2d_cache/ [Kernel PMU event] armv8_pmuv3_0/l2d_cache_allocate/ [Kernel PMU event] armv8_pmuv3_0/l2d_cache_refill/[Kernel PMU event] armv8_pmuv3_0/l2d_cache_wb/[Kernel PMU event] armv8_pmuv3_0/l2d_tlb/ [Kernel PMU event] armv8_pmuv3_0/l2d_tlb_refill/ [Kernel PMU event] armv8_pmuv3_0/ld_retired/ [Kernel PMU event] armv8_pmuv3_0/mem_access/ [Kernel PMU event] armv8_pmuv3_0/st_retired/ [Kernel PMU event] armv8_pmuv3_0/stall_backend/ [Kernel PMU event] armv8_pmuv3_0/stall_frontend/ [Kernel PMU event] armv8_pmuv3_0/sw_incr/ [Kernel PMU event] armv8_pmuv3_0/ttbr_write_retired/ [Kernel PMU event] armv8_pmuv3_0/unaligned_ldst_retired/ [Kernel PMU event] core imp def: bus_access_rd [Bus access read] bus_access_wr [Bus access write] exc_dabort [Exception taken, Data Abort and SError] exc_fiq [Exception taken, FIQ] exc_hvc [Exception taken, Hypervisor Call] exc_irq [Exception taken, IRQ] exc_pabort [Exception taken, Instruction Abort] exc_smc [Exception taken, Secure Monitor Call] exc_svc [Exception taken, Supervisor Call] exc_trap_dabort [Exception taken, Data Abort or SError not taken locally] exc_trap_fiq [Exception taken, FIQ not taken locally] exc_trap_irq [Exception taken, IRQ not taken locally] exc_trap_other [Exception taken, Other traps not taken locally] exc_trap_pabort [Exception taken, Instruction Abort not taken locally] exc_undef [Exception taken, Other synchronous]
