[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
Hi dr_strangehate: If you have updated touchpad fw, Could you test your laptop with passing "psmouse.synaptics_intertouch=0" in kernel cmdline? Thanks, Aaron -- 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/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 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 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006KPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis
[Kernel-packages] [Bug 1789214] Re: Clevo N850EL crashes / freezes under Ubuntu 18.04.1
Just for information, that trying out Ubuntu 18.10 kernel 4.18.0-10-generic booting from USB pen, the problem remains (and the intel_idle.max_cstate=1 workaround still 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/1789214 Title: Clevo N850EL crashes / freezes under Ubuntu 18.04.1 Status in linux package in Ubuntu: Confirmed Bug description: The details of what I've attempted so far are in https://askubuntu.com/questions/1068161/clevo-n850el-crashes-freezes- ubuntu-18-04-1-frequently Any workaround help greatly appreciated. (I do not need NVIDIA graphics, but I do need VirtualBox). Regards, ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jpsl 1955 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Aug 27 14:56:57 2018 InstallationDate: Installed on 2018-08-22 (4 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 002: ID 5986:2110 Acer, Inc Bus 001 Device 004: ID 0461:4de3 Primax Electronics, Ltd Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N8xxEL ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=60daf8a6-ead0-4dc1-9b51-e7fa0fd7304c ro text crashkernel=384M-:4096M 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.004 dmi.board.asset.tag: Tag 12345 dmi.board.name: N8xxEL dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.004:bd04/27/2018:svnNotebook:pnN8xxEL:pvrNotApplicable:rvnNotebook:rnN8xxEL:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N8xxEL 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/1789214/+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 1803442] Re: Thermal and power monitoring issues: CPU overheats and fan control broken/strange
I was testing with mainline/v4.20-rc3 but it was unusable on my machine: running the Quadro P3200 with the nouveau driver created a completely broken display (the nVidia 390 drivers are fine, though). At least this behavior is is identical between 4.18.0-11 and mainline/v4.20-rc3 So unless I have a way to run mainline/v4.20-rc3 with the Ubuntu nVidia package I can't test. ** 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/1803442 Title: Thermal and power monitoring issues: CPU overheats and fan control broken/strange Status in linux package in Ubuntu: Confirmed Bug description: On my ThinkPad P72 with i7-8850H CPU (Coffee Lake) the thermal setup is horrible: it runs very hot (you can feel it on the keyboard as well as the air exhausted by the fan) even when idle, the fan speeds up and gets silent after a a short time for no obvious load reasons when the system is idle. (Definition of idle: quite a few browser tabs open in firefox and chrome sitting in the background untouched since a longish time, no interaction by the user with the machine) The reported CPU temperature rises to an average of 60°C during idle with sporadic peaks well over 80°C (e.g. 95°C) for a single CPU. With slight work (browsing the web) temperature rises with more often temperature peaks rising high - expected due to the higher work load. But still far too much for the little work load for such a high end machine. Chances are high that after a short while the CPU frequency gets hard locked at 800 MHz with no way I could figure out to get out of that apart from rebooting. A cross check with Windows 10 (dual boot) showed a much better thermal behavior there. Temperatures stayed lower and under high load the fan is running on a moderate level with the CPUs averaging at about 3 GHz. Actually it showed the behavior that I expected for Linux... During my search for causes and ways to fix it I tried so far: - disabling hardware P-states or even the pstate driver - no improvement (actually I felt it was even slightly worse) - switching from laptop-mode-tools to tlp (no change) - activating everything from powertop (no change) - running powerstat was very interesting: * $ powerstat Running for 300.0 seconds (30 samples at 10.0 second intervals). Power measurements will start in 180 seconds time. TimeUser Nice Sys IdleIO Run Ctxt/s IRQ/s Watts [...] - - - - - -- -- -- Average 6.9 0.0 2.0 91.0 0.0 1.4 6732.7 3615.9 41.71 GeoMean 6.8 0.0 2.0 91.0 0.0 1.3 6129.6 3566.7 41.63 StdDev 1.1 0.0 0.5 1.5 0.1 0.9 4380.3 668.7 2.55 - - - - - -- -- -- Minimum 5.3 0.0 1.4 86.9 0.0 1.0 4508.5 2859.7 37.65 Maximum 10.4 0.0 4.2 93.0 0.4 5.0 28301.5 6420.4 47.85 - - - - - -- -- -- Summary: System: 41.71 Watts on average with standard deviation 2.55 * but * $ powerstat -R Running for 60.0 seconds (60 samples at 1.0 second intervals). Power measurements will start in 0 seconds time. TimeUser Nice Sys IdleIO Run Ctxt/s IRQ/s Watts [...] - - - - - -- -- -- Average 6.4 0.0 1.7 91.9 0.0 1.7 4966.6 3426.7 5.18 GeoMean 4.5 0.0 1.1 91.5 0.0 1.5 4158.6 2173.9 4.40 StdDev 6.1 0.0 1.8 7.8 0.1 1.0 3324.3 3723.3 4.00 - - - - - -- -- -- Minimum 1.2 0.0 0.3 71.9 0.0 1.0 1565.0 791.0 2.84 Maximum 23.1 0.0 6.2 98.4 0.3 6.0 13108.0 15195.0 21.91 - - - - - -- -- -- Summary: CPU: 5.18 Watts on average with standard deviation 4.00 Note: power read from RAPL domains: dram, package-0, core, psys. These readings do not cover all the hardware in this device. * ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cm 2134 F pulseaudio /dev/snd/controlC0: cm 2134 F pulseaudio CurrentDesktop: KDE Date: Wed Nov 14 22:07:52 2018 HibernationDevice: #RESUME=UUID=9cd06200-ed0e-4f66-9baa-a3977c6b59e0 RESUME=/dev/mapper/GROUP-SWAP InstallationDate: Installed on 2018-10-10 (35 days ago) InstallationMedia: Kubuntu 18.04.1 LTS
[Kernel-packages] [Bug 1797862] Re: Cannot turn off keyboard backlight
Bug #1791372 was fixed by update in Bug #1796550 -- 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/1797862 Title: Cannot turn off keyboard backlight Status in linux package in Ubuntu: Confirmed Bug description: /sys/class/leds $ ls asus-wireless::airplane input10::capslock input10::compose input10::kana input10::numlock input10::scrolllock input4::capslock input4::numlock input4::scrolllock phy0-led There isn't any asus kbd backlight folder. `xset led off` doesn't work for me. And I can only use fn to control volume (f1/f2/f3). The leds kills my battery $ sudo dmidecode -t 1; lsb_release -a # dmidecode 3.1 Getting SMBIOS data from sysfs. SMBIOS 3.0.0 present. Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: ASUSTeK COMPUTER INC. Product Name: FX503VD Version: 1.0 Serial Number: H9NRCX00M803374 UUID: 524E3948-5843-3030-4D38-30373441 Wake-up Type: Power Switch SKU Number: Family: FX No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 Codename: cosmic ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 15 17:13:35 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-10-generic, x86_64: installed nvidia, 390.87, 4.18.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1b90] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1b90] InstallationDate: Installed on 2018-10-10 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0b05:1869 ASUSTek Computer, Inc. Bus 001 Device 003: ID 13d3:5666 IMC Networks Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. FX503VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=ad490863-aaf6-49d0-8508-514c07335e07 ro nouveau.runpm=0 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX503VD.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX503VD 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.:bvrFX503VD.302:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: FX dmi.product.name: FX503VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797862/+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 1796550] Re: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8)
The update fixed the issue on the Asus ZenBook UX561UD mentioned in comment #10 (i.e. Bug #1791372) -- 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/1796550 Title: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8) Status in linux package in Ubuntu: Invalid Status in upower package in Ubuntu: Fix Released Status in upower source package in Cosmic: Fix Released Bug description: * Impact keyboard backlight control keys don't work in cosmic * Test case On a laptop with keyboard backlight and keys to control the level, try using the keys, they should change the level * Regression potential The change is to lift some systemd process restriction, have extra access shouldn't create issue but check that other features like suspend, battery pourcentage report, etc keep working --- https://gitlab.freedesktop.org/upower/upower/issues/73 --- On laptops with two separate (down,up) keys to control the backlit keyboard, both keys seem to do nothing. The OSD for the backlit keyboard is displayed but no progress bar and no actual effect to the backlight. Almost as if the shell only understands laptops with a single key for controlling the keyboard backlight... Bug verified in cosmic on: * Asus UX331UAL * Apple Macbook Pro 12,1 * Apple Macbook Air All of them have these keys and they all fail in the same way. However it is not a kernel bug. The kernel interface (/sys/class/leds/*::kbd_backlight/*) works when I write to it directly. This seems to be a problem with Gnome Shell only. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.0-3ubuntu1 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 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 7 13:41:50 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (25 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796550/+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 1791372] Re: Keyboard backlight not working on Asus ZenBook Flip UX561UD laptop in Cosmic 18.10, works with 18.04.1 desktop installer live image
This bug was fixed in the package upower - 0.99.8-2ubuntu0.1 from Bug #1796550 -- 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/1791372 Title: Keyboard backlight not working on Asus ZenBook Flip UX561UD laptop in Cosmic 18.10, works with 18.04.1 desktop installer live image Status in acpid package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Repro: 1. Press Fn+F3/F4 in fresh install from current Cosmic desktop image, fully updated -> Keyboard backlight should come on or change but doesn't. The gnome-shell pop-up icon for the keyboard backlight appears for both keys, but the icon's "progress" bar is not visible. Kernel version is linux-image-4.17.0-9-generic This is the same in X and Wayland session. In case it matters, Nvidia binary drivers are installed but Nvidia is switched off via Prime setting in nvidia-settings. Running with Intel drivers The keyboard backlight works perfectly when booting from the 18.04.1 desktop live image. When turning on light with 18.04.1, it is off again after rebooting into 18.10. (However 18.04.1 seems to freeze when shutting down from menu, I have to hard-shut it off). Most other important Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound) except for the airplane mode key. However the airplane mode key only fails in gnome-shell but works on the console (this is filed as https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791367) (Not working are a key that seems to mean "display off" and another of unclear purpose that never worked on any laptop I ever saw, maybe "presentation mode" as it seems to depict a flip chart or projection screen). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.17.0-9-generic 4.17.0-9.10 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: angela16196 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 22:08:12 2018 InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.17.0-9-generic N/A linux-backports-modules-4.17.0-9-generic N/A linux-firmware1.174 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1791372/+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 1790454] Re: Bluetooth (btintel) stops working after suspend/resume
I'm still planning to run a bisect to find the offending commit, but havne't found the time yet. -- 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/1790454 Title: Bluetooth (btintel) stops working after suspend/resume Status in linux package in Ubuntu: Confirmed Bug description: I run cosmic on my Dell Latitude E7470, which has an intel usb bluetooth device (8087:0a2b). Sometimes (not every time) after a suspend/resume cycle, my laptop's bluetooth stops working. hciconfig shows: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 and dmesg tells me (various combinations of): [237660.728312] Bluetooth: hci0: command tx timeout [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout [237925.202500] Bluetooth: hci0: Reading Intel version information failed (-110) Trying to reinitialize the device by reloading the driver has no effect: ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe btusb shows in dmesg: [237938.219190] usbcore: deregistering interface driver btusb [237938.601731] usbcore: registered new interface driver btusb [237940.626392] Bluetooth: hci0: Reading Intel version information failed (-110) [237940.626426] Bluetooth: hci0: command tx timeout Strangely enough, reloading the module sometimes does work, upon which the kernel tells me : aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download to complete aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Looking further back in the kernel log, the difference between failed and successful resumes seems to be this: Resume with broken bt: [236481.370814] Restarting tasks ... [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110) Resume with working bt: [16562.706263] Restarting tasks ... [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [16562.716050] Bluetooth: hci0: Device revision is 5 [16562.716052] Bluetooth: hci0: Secure boot is enabled [16562.716053] Bluetooth: hci0: OTP lock is enabled [16562.716054] Bluetooth: hci0: API lock is enabled [16562.716055] Bluetooth: hci0: Debug lock is disabled [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs [16564.203091] Bluetooth: hci0: Waiting for device to boot [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed and everything works fine after that. The first kernel on which this error occurred was 4.17.0-6-generic. Before that, I used 4.15.0-25-generic which works perfectly. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: bas4871 F...m pulseaudio /dev/snd/controlC0: bas4871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93 #RESUME=/dev/dm-2 #RESUME=/dev/mapper/regan-swap InstallationDate: Installed on 2016-12-22 (619 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Latitude E7470 Package: linux (not installed) ProcFB:
[Kernel-packages] [Bug 1791372] Re: Keyboard backlight not working on Asus ZenBook Flip UX561UD laptop in Cosmic 18.10, works with 18.04.1 desktop installer live image
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: acpid (Ubuntu) Status: Confirmed => Invalid ** Package changed: linux (Ubuntu) => upower (Ubuntu) ** Changed in: upower (Ubuntu) Status: Invalid => 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/1791372 Title: Keyboard backlight not working on Asus ZenBook Flip UX561UD laptop in Cosmic 18.10, works with 18.04.1 desktop installer live image Status in acpid package in Ubuntu: Invalid Status in upower package in Ubuntu: Fix Released Bug description: Repro: 1. Press Fn+F3/F4 in fresh install from current Cosmic desktop image, fully updated -> Keyboard backlight should come on or change but doesn't. The gnome-shell pop-up icon for the keyboard backlight appears for both keys, but the icon's "progress" bar is not visible. Kernel version is linux-image-4.17.0-9-generic This is the same in X and Wayland session. In case it matters, Nvidia binary drivers are installed but Nvidia is switched off via Prime setting in nvidia-settings. Running with Intel drivers The keyboard backlight works perfectly when booting from the 18.04.1 desktop live image. When turning on light with 18.04.1, it is off again after rebooting into 18.10. (However 18.04.1 seems to freeze when shutting down from menu, I have to hard-shut it off). Most other important Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound) except for the airplane mode key. However the airplane mode key only fails in gnome-shell but works on the console (this is filed as https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791367) (Not working are a key that seems to mean "display off" and another of unclear purpose that never worked on any laptop I ever saw, maybe "presentation mode" as it seems to depict a flip chart or projection screen). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.17.0-9-generic 4.17.0-9.10 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: angela16196 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 22:08:12 2018 InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.17.0-9-generic N/A linux-backports-modules-4.17.0-9-generic N/A linux-firmware1.174 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1791372/+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 1775065] Re: No brightness controls and /sys/class/backlight empty after upgrade to Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter acpi_osi= is a workaround)
Got a similar problem on a HP Zbook G5. I have 2 graphics cards: Intel + Nvidia. I use the Nvidia proprietary drivers 415. The difference in my case is that I have an entry in "/sys/class/backlight", namely: "intel_backlight" and that I can control the display brightness using the gnome GUI slider, but also my backlight hotkeys are not working and none of the following kernel parameters solved the issue: "acpi_backlight=vendor" "acpi_backlight=video" "acpi_backlight=video0" "acpi_backlight=none" "acpi_osi=Linux" Since many people are experiencing this annoying bug, it would really be great if it could be solved. Anyhow, thanks for any of your efforts to solve 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/1775065 Title: No brightness controls and /sys/class/backlight empty after upgrade to Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter acpi_osi= is a workaround) Status in linux package in Ubuntu: Confirmed Bug description: This is a case of "Backlight control does not work, and there are no entries in /sys/class/backlight" for what lspci reports as "NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)" where the kernel parameter acpi_osi= is a workaround. (The workaround is also recorded on Ask Ubuntu at https://askubuntu.com/questions/1030526 /brightness-on-laptop-msi-gt72vr-in-ubuntu-18-04-with-nvidia-gtx-1060 -mobile-does/1043598#1043598.) The problem is new for me after upgrade to Bionic, although the cause might be the corresponding update to the NVIDIA drivers. I will add attachments following the instructions at https://wiki.ubuntu.com/Kernel/Debugging/Backlight, though most of them seem to be uninteresting. If I can provide further information, please let me know. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 4 14:20:34 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-06-04 (0 days ago) --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bgarvin2442 F pulseaudio /dev/snd/controlC0: bgarvin2442 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=1b60cccb-eea7-4d0b-a32b-97d236a5177f Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b5a7 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76, Inc. Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color 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-22-generic root=UUID=557ebdfc-3380-4721-a494-65c34cb70b2f ro i8042.nomux i8042.reset acpi_osi= ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-06-04 (1 days ago) UserGroups: adm lpadmin sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 09/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.03RSA dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76, Inc. dmi.board.version: oryp2 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.03RSA:bd09/08/2016:svnSystem76,Inc.:pnOryxPro:pvroryp2:rvnSystem76,Inc.:rnOryxPro:rvroryp2:cvnSystem76,Inc.:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.version: oryp2 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775065/+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.laun
[Kernel-packages] [Bug 1775065] Re: No brightness controls and /sys/class/backlight empty after upgrade to Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter acpi_osi= is a workaround)
Forgot my setup infos: ## lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic dmidecode: System Information Manufacturer: HP Product Name: HP ZBook 15 G5 uname -a: 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- 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/1775065 Title: No brightness controls and /sys/class/backlight empty after upgrade to Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter acpi_osi= is a workaround) Status in linux package in Ubuntu: Confirmed Bug description: This is a case of "Backlight control does not work, and there are no entries in /sys/class/backlight" for what lspci reports as "NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)" where the kernel parameter acpi_osi= is a workaround. (The workaround is also recorded on Ask Ubuntu at https://askubuntu.com/questions/1030526 /brightness-on-laptop-msi-gt72vr-in-ubuntu-18-04-with-nvidia-gtx-1060 -mobile-does/1043598#1043598.) The problem is new for me after upgrade to Bionic, although the cause might be the corresponding update to the NVIDIA drivers. I will add attachments following the instructions at https://wiki.ubuntu.com/Kernel/Debugging/Backlight, though most of them seem to be uninteresting. If I can provide further information, please let me know. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 4 14:20:34 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-06-04 (0 days ago) --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bgarvin2442 F pulseaudio /dev/snd/controlC0: bgarvin2442 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=1b60cccb-eea7-4d0b-a32b-97d236a5177f Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b5a7 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76, Inc. Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color 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-22-generic root=UUID=557ebdfc-3380-4721-a494-65c34cb70b2f ro i8042.nomux i8042.reset acpi_osi= ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-06-04 (1 days ago) UserGroups: adm lpadmin sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 09/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.03RSA dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76, Inc. dmi.board.version: oryp2 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.03RSA:bd09/08/2016:svnSystem76,Inc.:pnOryxPro:pvroryp2:rvnSystem76,Inc.:rnOryxPro:rvroryp2:cvnSystem76,Inc.:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.version: oryp2 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775065/+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 1802283] Re: system freezes
It freezed again. This time without an external monitor connected. The system was running for quite some time with suspends/resumes in between and I ran a pytest test suite. Directly after the tests being finished the system didn't respond to any keyboard input whatsoever. Only a reboot via the power button helped. There hasn't been any entry in /var/log/kern.log nor /var/log/syslog. Any idea how to get at least some info out of the system why it is crashing? And I see that this issue is still marked as incomplete. What more info is needed to don't have this issue marked for expiration? -- 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/1802283 Title: system freezes Status in linux package in Ubuntu: Incomplete Bug description: My system freezes once every second day or so. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jnns 2519 F pulseaudio /dev/snd/controlC0: jnns 2519 F pulseaudio CurrentDesktop: GNOME Date: Thu Nov 8 12:07:32 2018 HibernationDevice: RESUME=UUID=18edd09d-0a58-4464-accb-11ff57fc4327 InstallationDate: Installed on 2018-08-05 (95 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20KGS5DU00 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-10 (29 days ago) dmi.bios.date: 09/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KGS5DU00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET56W(1.31):bd09/17/2018:svnLENOVO:pn20KGS5DU00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS5DU00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KGS5DU00 dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802283/+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 1787775] Re: touchpad not working on lenovo yoga 530
I am just compiling na fresh vanilla kernel (4.20) and will then try this: https://github.com/Syniurge/i2c-amd-mp2 I am compiling this new kernel, because the repository says, that the dkms on the stock kernel may not work. I tried the installation an indeed, touchpad and touchscreen stayed dead. I can confirm, that blacklisting ideapad-laptop and installing https://github.com/tomaspinho/rtl8821ce makes wifi/bluetooth work as expected. But this is a "touchscreen" thread isnt it? :) So lets get this done! -- 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/1787775 Title: touchpad not working on lenovo yoga 530 Status in linux package in Ubuntu: Confirmed Bug description: The touchpad is not working and does not show up in cat /proc/bus/input/devices on multiple kernels. I've tried the newest kernel to date (19.08.18) and a few others. The touchpad works on windows. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-08-18 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) Package: linux (not installed) Tags: bionic Uname: Linux 4.18.3-041803-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to bionic on 2018-08-18 (0 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/1787775/+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 1800238] Re: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18
I think this is caused by commit 1a0c10ed7bb191bccf6f1e2d16203886a5ce76c8 media: dvb-usb-v2: stop using coherent memory for URBs Reverting this should restore normal operation. -- 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/1800238 Title: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18 Status in linux package in Ubuntu: Incomplete Bug description: Dear developer(s), I used a vdr-installation on Debian testing, before. Switched over to Ubuntu since the release of cosmic because of problems with GPU/steam under Debian. Now, I have problems to configure vdr because my TV stick doesn't seem to work with kernel 4.18. This is what I did: Installed Ubuntu, upgraded via aptitude to the latest packages, got the firmware "dvb-demod-si2168-b40-01.fw" and "dvb-tuner-si2158-a20-01.fw" (as it was recommended by *I guess it was* openelec.org and the modinfo output of si2168 and si2157), tried w_scan and failed (w_scan *can* find some signals but failes in getting the channels). That looks like this, f.e.: […} Scanning DVB-T2... 474000: (time: 01:38.796) 482000: (time: 01:43.155) 49: (time: 01:45.163) signal ok: QAM_AUTO f = 49 kHz I999B8C999D999T999G999Y999P0 (0:0:0) Info: no data from PAT after 2 seconds deleting (QAM_AUTO f = 49 kHz I999B8C999D999T999G999Y999P0 (0:0:0)) […] Now, I tried an older kernel - 4.15, because it's still in the cosmics' repository and tried w_scan again: Success, although the TV- Stick doesn't find all the channels I found with Debian Testing. So, maybe there's a regression in the latest kernel regarding the TV- Stick-driver or there is another firmware which will work better with 4.18…? Would be glad if someone could help to work that out… Greets! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarosch1516 F pulseaudio /dev/snd/controlC0: jarosch1516 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Oct 26 23:32:50 2018 InstallationDate: Installed on 2018-10-24 (2 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: BIOSTAR Group Hi-Fi A88S3+ ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-10-generic root=UUID=e5ad9e21-ba9d-4f5e-9100-374ea87d4eba ro rootflags=subvol=@ pti=off spectre_v2=off l1tf=off nospec_store_bypass_disable no_stf_barrier quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: None dmi.board.name: Hi-Fi A88S3+ dmi.board.vendor: BIOSTAR Group dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd03/18/2015:svnBIOSTARGroup:pnHi-FiA88S3+:pvr:rvnBIOSTARGroup:rnHi-FiA88S3+:rvr:cvnBIOSTARGroup:ct3:cvr: dmi.product.family: None dmi.product.name: Hi-Fi A88S3+ dmi.product.sku: None dmi.sys.vendor: BIOSTAR Group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800238/+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 1800238] Re: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18
** 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/1800238 Title: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18 Status in linux package in Ubuntu: Incomplete Bug description: Dear developer(s), I used a vdr-installation on Debian testing, before. Switched over to Ubuntu since the release of cosmic because of problems with GPU/steam under Debian. Now, I have problems to configure vdr because my TV stick doesn't seem to work with kernel 4.18. This is what I did: Installed Ubuntu, upgraded via aptitude to the latest packages, got the firmware "dvb-demod-si2168-b40-01.fw" and "dvb-tuner-si2158-a20-01.fw" (as it was recommended by *I guess it was* openelec.org and the modinfo output of si2168 and si2157), tried w_scan and failed (w_scan *can* find some signals but failes in getting the channels). That looks like this, f.e.: […} Scanning DVB-T2... 474000: (time: 01:38.796) 482000: (time: 01:43.155) 49: (time: 01:45.163) signal ok: QAM_AUTO f = 49 kHz I999B8C999D999T999G999Y999P0 (0:0:0) Info: no data from PAT after 2 seconds deleting (QAM_AUTO f = 49 kHz I999B8C999D999T999G999Y999P0 (0:0:0)) […] Now, I tried an older kernel - 4.15, because it's still in the cosmics' repository and tried w_scan again: Success, although the TV- Stick doesn't find all the channels I found with Debian Testing. So, maybe there's a regression in the latest kernel regarding the TV- Stick-driver or there is another firmware which will work better with 4.18…? Would be glad if someone could help to work that out… Greets! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarosch1516 F pulseaudio /dev/snd/controlC0: jarosch1516 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Oct 26 23:32:50 2018 InstallationDate: Installed on 2018-10-24 (2 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: BIOSTAR Group Hi-Fi A88S3+ ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-10-generic root=UUID=e5ad9e21-ba9d-4f5e-9100-374ea87d4eba ro rootflags=subvol=@ pti=off spectre_v2=off l1tf=off nospec_store_bypass_disable no_stf_barrier quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: None dmi.board.name: Hi-Fi A88S3+ dmi.board.vendor: BIOSTAR Group dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd03/18/2015:svnBIOSTARGroup:pnHi-FiA88S3+:pvr:rvnBIOSTARGroup:rnHi-FiA88S3+:rvr:cvnBIOSTARGroup:ct3:cvr: dmi.product.family: None dmi.product.name: Hi-Fi A88S3+ dmi.product.sku: None dmi.sys.vendor: BIOSTAR Group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800238/+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 1800238] Re: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18
** 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/1800238 Title: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18 Status in linux package in Ubuntu: Confirmed Bug description: Dear developer(s), I used a vdr-installation on Debian testing, before. Switched over to Ubuntu since the release of cosmic because of problems with GPU/steam under Debian. Now, I have problems to configure vdr because my TV stick doesn't seem to work with kernel 4.18. This is what I did: Installed Ubuntu, upgraded via aptitude to the latest packages, got the firmware "dvb-demod-si2168-b40-01.fw" and "dvb-tuner-si2158-a20-01.fw" (as it was recommended by *I guess it was* openelec.org and the modinfo output of si2168 and si2157), tried w_scan and failed (w_scan *can* find some signals but failes in getting the channels). That looks like this, f.e.: […} Scanning DVB-T2... 474000: (time: 01:38.796) 482000: (time: 01:43.155) 49: (time: 01:45.163) signal ok: QAM_AUTO f = 49 kHz I999B8C999D999T999G999Y999P0 (0:0:0) Info: no data from PAT after 2 seconds deleting (QAM_AUTO f = 49 kHz I999B8C999D999T999G999Y999P0 (0:0:0)) […] Now, I tried an older kernel - 4.15, because it's still in the cosmics' repository and tried w_scan again: Success, although the TV- Stick doesn't find all the channels I found with Debian Testing. So, maybe there's a regression in the latest kernel regarding the TV- Stick-driver or there is another firmware which will work better with 4.18…? Would be glad if someone could help to work that out… Greets! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarosch1516 F pulseaudio /dev/snd/controlC0: jarosch1516 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Oct 26 23:32:50 2018 InstallationDate: Installed on 2018-10-24 (2 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: BIOSTAR Group Hi-Fi A88S3+ ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-10-generic root=UUID=e5ad9e21-ba9d-4f5e-9100-374ea87d4eba ro rootflags=subvol=@ pti=off spectre_v2=off l1tf=off nospec_store_bypass_disable no_stf_barrier quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: None dmi.board.name: Hi-Fi A88S3+ dmi.board.vendor: BIOSTAR Group dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd03/18/2015:svnBIOSTARGroup:pnHi-FiA88S3+:pvr:rvnBIOSTARGroup:rnHi-FiA88S3+:rvr:cvnBIOSTARGroup:ct3:cvr: dmi.product.family: None dmi.product.name: Hi-Fi A88S3+ dmi.product.sku: None dmi.sys.vendor: BIOSTAR Group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800238/+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 1793960] Re: Lenovo Ideapad 320-15IAP trackpad spams kernel errors in syslog
The same problem to me with the same model of computer. -- 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/1793960 Title: Lenovo Ideapad 320-15IAP trackpad spams kernel errors in syslog Status in linux package in Ubuntu: Confirmed Bug description: The trackpad is working, but syslog is full of kernel errors regarding "kernel: [ 1228.364151] elan_i2c i2c-ELAN0609:00: invalid report id data (ff)" if the trackpad is touched. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-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.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mlku 1269 F pulseaudio CurrentDesktop: KDE Date: Sun Sep 23 15:48:36 2018 HibernationDevice: RESUME=UUID=83c21341-9f8a-4b04-8696-ba03f48c8561 InstallationDate: Installed on 2018-09-23 (0 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 80XR ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash 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: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 5RCN36WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IAP dmi.modalias: dmi:bvnLENOVO:bvr5RCN36WW:bd08/06/2018:svnLENOVO:pn80XR:pvrLenovoideapad320-15IAP:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IAP: dmi.product.family: ideapad 320-15IAP dmi.product.name: 80XR dmi.product.version: Lenovo ideapad 320-15IAP dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793960/+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 1804968] [NEW] package linux-firmware 1.157.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 137
Public bug reported: . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.21 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sat Nov 24 17:27:37 2018 Dependencies: ErrorMessage: subprocess installed post-installation script returned error exit status 137 InstallationDate: Installed on 2018-05-05 (203 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 SourcePackage: linux-firmware Title: package linux-firmware 1.157.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 137 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1804968 Title: package linux-firmware 1.157.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 137 Status in linux-firmware package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.21 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sat Nov 24 17:27:37 2018 Dependencies: ErrorMessage: subprocess installed post-installation script returned error exit status 137 InstallationDate: Installed on 2018-05-05 (203 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 SourcePackage: linux-firmware Title: package linux-firmware 1.157.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 137 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1804968/+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 1804968] Re: package linux-firmware 1.157.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 137
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1804968 Title: package linux-firmware 1.157.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 137 Status in linux-firmware package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.21 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sat Nov 24 17:27:37 2018 Dependencies: ErrorMessage: subprocess installed post-installation script returned error exit status 137 InstallationDate: Installed on 2018-05-05 (203 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 SourcePackage: linux-firmware Title: package linux-firmware 1.157.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 137 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1804968/+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 1581088] Re: Middle mouse (wheel-click) button stopped working after upgrade to 16.04
In my case, same thing than above: Logitech M310 middle button not working on Ubuntu 18.04 => issued "xev | grep button" on a terminal, checked the left, then the right and finally the middle/wheel buttons: # xev | grep button state 0x0, button 1, same_screen YES state 0x100, button 1, same_screen YES state 0x0, button 3, same_screen YES state 0x400, button 3, same_screen YES state 0x0, button 2, same_screen YES state 0x200, button 2, same_screen YES state 0x0, button 2, same_screen YES state 0x200, button 2, same_screen YES Then, just after closing the xev window, noticed the "middle mouse button click/paste" suddenly started to work again. Weird... -- 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/1581088 Title: Middle mouse (wheel-click) button stopped working after upgrade to 16.04 Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 16.04 clicking the middle mouse button (scroll wheel) on my Logitech M185 stopped working. xev does not even show the event for clicking the wheel, while it shows other button clicks and scroll wheel up/down events. xinput list shows the USB receiver 2 times: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=9[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=10 [slave pointer (2)] ⎜ ↳ HID 046a:0023 id=13 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=16 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=17 [slave pointer (2)] Listing the capabilities looks like this: $ xinput list 9 Logitech USB Receiver id=9[slave pointer (2)] Reporting 7 classes: Class originated from: 9. Type: XIButtonClass Buttons supported: 24 Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" "Button Side" "Button Extra" "Button Forward" "Button Back" "Button Task" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" Button state: Class originated from: 9. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 3: Label: Rel Vert Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIScrollClass Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.00 flags: 0x0 Class originated from: 9. Type: XIScrollClass Scroll info for Valuator 3 type: 1 (vertical) increment: -1.00 flags: 0x2 ( preferred ) $ xinput list 10 Logitech USB Receiver id=10 [slave pointer (2)] Reporting 6 classes: Class originated from: 10. Type: XIButtonClass Buttons supported: 7 Button labels: "Button 0" "Button Unknown" "Button Unknown" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" Button state: Class originated from: 10. Type: XIKeyClass Keycodes supported: 248 Class originated from: 10. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIValuatorClass Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIScrollClass Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.00 flags: 0x0 Does anyone have an idea how I can attempt to further debug that issue? Or maybe even a solution? Should I consider this issue a bug? Can I provide more info? --- Apport
[Kernel-packages] [Bug 1798863] Re: 18.10 kernel does not appear to validate kernel module signatures correctly
** Changed in: linux (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798863 Title: 18.10 kernel does not appear to validate kernel module signatures correctly Status in linux package in Ubuntu: In Progress Status in shim package in Ubuntu: Invalid Status in linux source package in Cosmic: Fix Released Status in shim source package in Cosmic: Invalid Bug description: SRU Justification Impact: An bug in the secure boot lockdown patches in the 18.10 kernel causes the results of module signature verification to be ignored, allowing modules with no signature or an invalid signature to be loaded. A second bug results in the MOK not being trusted for signing modules, but this bug has been masked by the first bug. Fix: These bugs should be fixed together to avoid regressions in dkms module loading under secure boot. First, fix the latter bug by trusting keys in the kernel's secondary keyring for module signing. Then fix the former bug by removing code related to trusting IMA signatures for loading modules under kernel lockdown. Test Case: Confirm the following behavior under kernel lockdown: 1) Unsigned modules cannot be loaded. 2) Modules signed with an untrusted key cannot be loaded. 3) Modules signed with the kernel's ephemeral build-time key can be loaded. 4) Modules signed with a MOK which has been enrolled with shim can be loaded. I have tested to verify these conditions with the proposed fixes. Regression Potential: This restores the behavior from previous Ubuntu releases, so no regressions are expected wrt those releases. In some cases modules that were loading under lockdown might no longer load, but this is the intended behavior. --- On a system with Ubuntu 18.10, with secure boot enabled, and a key enrolled in the MOK database, I am observing the following peculiar behaviors: * Signature verification appears to be disabled, and cannot be enabled again. It appeared to be enabled previously, as loading of unsigned modules was failing, and `mokutil --enable-validation` runs without incident; however, upon the next boot when attempting to confirm the change, MokManager prints an error message "Unable to delete Secure Boot state" after completing the password challenge. * As a result of signature verification being disabled, modules signed with untrusted keys taint the kernel instead of failing to load outright. * Regardless of signature verification being enabled or not, it seems that the key enrolled in the MOK is not being used for validating kernel module signatures. Modules signed with the key still fail the signature verification test and taint the kernel, even though the key is visible in the output of `mokutil --list-enrolled`, and testing the key with `mokutil --test-key` shows that it's enrolled. Also, a message acknowledging the key appears in dmesg: Loaded UEFI:MokListRT cert 'nvidia-installer generated signing key: 90c957eb56dfb04d8734d54fb614ef5af6c69318' linked to secondary sys keyring * Also, somewhat strangely, in this state with module signature verification not being enforced, attempting to load a completely unsigned kernel module suceeds, and doesn't even log a kernel message about a missing/invalid signature, or taint the kernel. Apport report attached, which includes dmesg log showing the kernel acknowledging the key enrolled in the MOK database, and a signature verification failure and subsequent successful loading of a module signed with that key: [4.234093] Loaded UEFI:MokListRT cert 'nvidia-installer generated signing key: 90c957eb56dfb04d8734d54fb614ef5af6c69318' linked to secondary sys keyring ... [6.628452] nvidia: module verification failed: signature and/or required key missing - tainting kernel ... [6.637252] nvidia-nvlink: Nvlink Core is being initialized, major device number 238 [6.637507] nvidia :01:00.0: enabling device (0006 -> 0007) [6.637620] nvidia :01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none [6.737216] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 410.66 Wed Oct 10 12:01:53 CDT 2018 (using threaded interrupts) This system dual-boots Ubuntu 18.04 and Ubuntu 18.10: when booted into Ubuntu 18.04, signatures made with the same key are recognized as valid. Hence, I suspect that something changed in the Ubuntu 18.10 kernel which is causing signature verification to function in an unexpected way. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: danix 1729 F pulseaudio DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-10-23 (0 days ago) Installati
[Kernel-packages] [Bug 1771764] Re: iproute2: unable to add ip lwt mpls route on xenial
** Changed in: iproute2 (Ubuntu)
Importance: Medium => Wishlist
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/1771764
Title:
iproute2: unable to add ip lwt mpls route on xenial
Status in iproute2 package in Ubuntu:
Triaged
Bug description:
The following command does not work:
$ ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev ntfp2
Error: "nexthop" or end of line is expected instead of "encap"
In fact, iproute2 version points to v4.3.0, but the xenial kernel is a 4.4.
$ ip -V
ip utility, iproute2-ss151103
=>
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=6720eceff7b4
With an iproute2 v4.4.0 (iproute2-ss160111), that command works:
$ modprobe mpls_iptunnel
$ ./ip/ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev
ntfp2
$ ./ip/ip r
[snip]
10.201.0.0/24 encap mpls 300 via 10.200.0.1 dev ntfp2
At least, this patch is missing:
1e5293056a02 ("lwtunnel: Add encapsulation support to ip route")
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=1e5293056a02
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771764/+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 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
** Changed in: unity-settings-daemon (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: unity-settings-daemon (Ubuntu Cosmic) Importance: Undecided => Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in gnome/unity-control- center Status in hwdata package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Status in unity-settings-daemon source package in Bionic: Fix Committed Status in unity-settings-daemon source package in Cosmic: Fix Committed Bug description: [Impact] * There is a number of display devices that misuse the width & height field in EDID. Instead of real size in centimeters it contains encoded aspect ratio (e.g. 1600x900, 16x10, 160x90). This leads to incorrect calculation of diagonal for the purpose of e.g. Unity settings app. [Test Case] 1. Connect a display device that provides incorrect EDID data (e.g. LG 49UB850T-DA TV). 2. Open the Displays section of Unity settings. 3. Look for the name of the newly connected display in the settings window. Expected result: Display name should contain its real diagonal or model name (if dimensions are not availabe). Actual result: Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" display). [Regression Potential] * This affects the way the display name will be formatted for any software using unity-settings-daemon. If anything is testing/comparing display names - it may fail. [Other Info] * Original bug description: After connecting a LG 49UB850T-DA TV the following information is displayed in the unity-control-center: Goldstar Company Ltd 72" It's misleading since neither the company name nor the diagonal matches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+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 1792813] Re: iio-sensor-proxy says: "Could not find any supported sensors" on Dell XPS 15 9575 2-in-1 on Cosmic 18.10
This seems to be the kernel bug report for the missing sensors: https://bugzilla.kernel.org/show_bug.cgi?id=200655 and the patch mentioned there: https://lore.kernel.org/patchwork/patch/975429/ Kernel bug status is resolved. Last comment from 2018-09-10 says that it would be merged in 4.10, but apparently this happened in 4.19-rc4 (see my above comments) ** Bug watch added: Linux Kernel Bug Tracker #200655 https://bugzilla.kernel.org/show_bug.cgi?id=200655 -- 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/1792813 Title: iio-sensor-proxy says: "Could not find any supported sensors" on Dell XPS 15 9575 2-in-1 on Cosmic 18.10 Status in linux package in Ubuntu: Triaged Status in linux source package in Cosmic: Triaged Bug description: On Cosmic, iio-sensor-proxy 2.4, with default 4.18 kernel as well as latest mainline 4.19.0-041900rc3-generic. There is no rotation lock button in the gnome-shell panel menu. Gnome Settings > Device Display shows rotation buttons There is no directory /sys/bus/iio Reproduction: 1. Rotate device, fold display back to tent and tablet modes: -> Rotation is not detected. When folding to tablet mode, device goes to suspend as if display had been closed normally. iio-sensor-proxy finds no sensors: ~$ systemctl status iio-sensor-proxy.service ● iio-sensor-proxy.service - IIO Sensor Proxy service Loaded: loaded (/lib/systemd/system/iio-sensor-proxy.service; static; vendor preset: enabled) Active: inactive (dead) I reported issue as https://github.com/hadess/iio-sensor- proxy/issues/236 and was advised: "Looks like there's no supported sensors, or just no sensors inside this machine. Nothing that we can do about it, except asking your vendor for support (eg. is there one or multiple sensors, and if so, why aren't they supported in the kernel)" I posted the issue in Dell's Project Sputnik's Google+ community 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-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mario 2139 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Sep 16 20:20:48 2018 InstallationDate: Installed on 2018-09-13 (2 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=26ff4c95-5f68-4121-b7d0-989fa705fcc8 ro quiet splash pcie_aspm=force drm.vblankoffdelay=1 i915.fastboot=1 vt.handoff=1 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: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.9 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.9:bd08/08/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792813/+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 1792813] Re: iio-sensor-proxy says: "Could not find any supported sensors" on Dell XPS 15 9575 2-in-1 on Cosmic 18.10
"... would be merged in 4.20" (not 4.10) of course -- 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/1792813 Title: iio-sensor-proxy says: "Could not find any supported sensors" on Dell XPS 15 9575 2-in-1 on Cosmic 18.10 Status in linux package in Ubuntu: Triaged Status in linux source package in Cosmic: Triaged Bug description: On Cosmic, iio-sensor-proxy 2.4, with default 4.18 kernel as well as latest mainline 4.19.0-041900rc3-generic. There is no rotation lock button in the gnome-shell panel menu. Gnome Settings > Device Display shows rotation buttons There is no directory /sys/bus/iio Reproduction: 1. Rotate device, fold display back to tent and tablet modes: -> Rotation is not detected. When folding to tablet mode, device goes to suspend as if display had been closed normally. iio-sensor-proxy finds no sensors: ~$ systemctl status iio-sensor-proxy.service ● iio-sensor-proxy.service - IIO Sensor Proxy service Loaded: loaded (/lib/systemd/system/iio-sensor-proxy.service; static; vendor preset: enabled) Active: inactive (dead) I reported issue as https://github.com/hadess/iio-sensor- proxy/issues/236 and was advised: "Looks like there's no supported sensors, or just no sensors inside this machine. Nothing that we can do about it, except asking your vendor for support (eg. is there one or multiple sensors, and if so, why aren't they supported in the kernel)" I posted the issue in Dell's Project Sputnik's Google+ community 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-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mario 2139 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Sep 16 20:20:48 2018 InstallationDate: Installed on 2018-09-13 (2 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=26ff4c95-5f68-4121-b7d0-989fa705fcc8 ro quiet splash pcie_aspm=force drm.vblankoffdelay=1 i915.fastboot=1 vt.handoff=1 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: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.9 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.9:bd08/08/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792813/+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 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10
Related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802283 -- 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/1798961 Title: Random unrecoverable freezes on Ubuntu 18.10 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Status in linux source package in Disco: Triaged Bug description: First thing I notice is that the mouse cursor freezes as I'm using it, then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then I try the "REISUB" command, but it doesn't do anything either. Only a hard reset works, pressing down the power button for a few seconds. How to reproduce? I couldn't figure out a consistent method. It is still random to me. Version: Ubuntu 4.18.0-10.11-generic 4.18.12 System information attached. Also happens under Arch Linux and Fedora. I've talked to another user on IRC who seems to be having the same freezes. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dsilva 1213 F pulseaudio /dev/snd/controlC0: dsilva 1213 F pulseaudio CurrentDesktop: XFCE Date: Sat Oct 20 09:54:50 2018 InstallationDate: Installed on 2018-10-20 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Dell Inc. Inspiron 5458 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 09WGNT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961/+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 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10
I also have had random system freezes ever since I upgraded from 18.04 to 18.10, Linux 4.18.0-10-generic, solved by always booting into 4.15.0-36-generic. When the freezes happen, the screen simply stops, and no input is accepted, not even the usual REISUB. teresaejunior@laptop ~> inxi -Fz System:Host: laptop Kernel: 4.15.0-36-generic x86_64 bits: 64 Desktop: Xfce 4.13.2 Distro: Ubuntu 18.10 (Cosmic Cuttlefish) Machine: Type: Laptop System: LENOVO product: 80JE v: Lenovo G40-80 serial: Mobo: LENOVO model: Lancer 4A1 v: SDK0E50515 STD serial: UEFI: LENOVO v: B0CN79WW date: 05/07/2015 Battery: ID-1: BAT0 charge: 26.4 Wh condition: 26.4/28.5 Wh (93%) CPU: Topology: Dual Core model: Intel Core i5-5200U bits: 64 type: MT MCP L2 cache: 3072 KiB Speed: 1397 MHz min/max: 500/2700 MHz Core speeds (MHz): 1: 1146 2: 1000 3: 1079 4: 1039 Graphics: Device-1: Intel HD Graphics 5500 driver: i915 v: kernel Display: x11 server: X.Org 1.20.1 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 5500 (Broadwell GT2) v: 4.5 Mesa 18.2.2 Audio: Device-1: Intel Broadwell-U Audio driver: snd_hda_intel Device-2: Intel Wildcat Point-LP High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k4.15.0-36-generic Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 IF: enp2s0 state: down mac: Device-2: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter driver: ath9k IF: wlp3s0 state: up mac: Device-3: Atheros AR3012 Bluetooth 4.0 type: USB driver: btusb IF-ID-1: docker0 state: down mac: Drives:Local Storage: total: 931.51 GiB used: 411.53 GiB (44.2%) ID-1: /dev/sda vendor: Seagate model: ST1000LM024 HN-M101MBB size: 931.51 GiB Partition: ID-1: / size: 915.71 GiB used: 411.52 GiB (44.9%) fs: ext4 dev: /dev/sda2 Sensors: System Temperatures: cpu: 41.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 267 Uptime: 7h 12m Memory: 11.64 GiB used: 3.45 GiB (29.7%) Shell: fish inxi: 3.0.24 -- 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/1798961 Title: Random unrecoverable freezes on Ubuntu 18.10 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Status in linux source package in Disco: Triaged Bug description: First thing I notice is that the mouse cursor freezes as I'm using it, then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then I try the "REISUB" command, but it doesn't do anything either. Only a hard reset works, pressing down the power button for a few seconds. How to reproduce? I couldn't figure out a consistent method. It is still random to me. Version: Ubuntu 4.18.0-10.11-generic 4.18.12 System information attached. Also happens under Arch Linux and Fedora. I've talked to another user on IRC who seems to be having the same freezes. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dsilva 1213 F pulseaudio /dev/snd/controlC0: dsilva 1213 F pulseaudio CurrentDesktop: XFCE Date: Sat Oct 20 09:54:50 2018 InstallationDate: Installed on 2018-10-20 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Dell Inc. Inspiron 5458 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 09WGNT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961/+
[Kernel-packages] [Bug 1804591] [NEW] tsc: Fast TSC calibration failed
You have been subscribed to a public bug: [0.00] APIC: Switch to symmetric I/O mode setup [0.004000] Switched APIC routing to physical flat. [0.004000] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 [0.024000] tsc: Fast TSC calibration failed [0.032000] tsc: PIT calibration matches HPET. 1 loops [0.032000] tsc: Detected 3600.039 MHz processor [0.032000] clocksource: tsc-early: mask: 0x max_cycles: 0x33e47874cac, max_idle_ns: 440795311274 ns [0.032000] Calibrating delay loop (skipped), value calculated using timer frequency.. 7200.07 BogoMIPS (lpj=14400156) [0.032000] pid_max: default: 32768 minimum: 301 [0.032000] Security Framework initialized [0.032000] Yama: becoming mindful. [0.032000] AppArmor: AppArmor initialized ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- tsc: Fast TSC calibration failed https://bugs.launchpad.net/bugs/1804591 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 1804590] [NEW] kgd2kfd_probe failed DID 15dd is missing in supported_devices
You have been subscribed to a public bug: dmesg [1.456816] Console: switching to colour dummy device 80x25 [1.457058] [drm] initializing kernel modesetting (RAVEN 0x1002:0x15DD 0x1462:0x7A39 0xC6). [1.457068] [drm] register mmio base: 0xFE40 [1.457069] [drm] register mmio size: 524288 [1.457084] [drm] probing gen 2 caps for device 1022:15db = 700d03/e [1.457086] [drm] probing mlw for device 1022:15db = 700d03 [1.457088] [drm] add ip block number 0 [1.457089] [drm] add ip block number 1 [1.457090] [drm] add ip block number 2 [1.457090] [drm] add ip block number 3 [1.457091] [drm] add ip block number 4 [1.457091] [drm] add ip block number 5 [1.457092] [drm] add ip block number 6 [1.457093] [drm] add ip block number 7 [1.457093] [drm] add ip block number 8 [1.457110] kfd kfd: DID 15dd is missing in supported_devices [1.457111] kfd kfd: kgd2kfd_probe failed ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- kgd2kfd_probe failed DID 15dd is missing in supported_devices https://bugs.launchpad.net/bugs/1804590 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 1804592] [NEW] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
You have been subscribed to a public bug: [0.876087] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. [0.876099] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.18 [0.876100] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [0.876101] usb usb2: Product: xHCI Host Controller [0.876102] usb usb2: Manufacturer: Linux 4.18.0-10-generic xhci-hcd [0.876103] usb usb2: SerialNumber: :15:00.0 [0.876206] hub 2-0:1.0: USB hub found [0.876215] hub 2-0:1.0: 4 ports detected ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. https://bugs.launchpad.net/bugs/1804592 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 1804593] [NEW] thermal thermal_zone0: failed to read out thermal zone
You have been subscribed to a public bug: thermal thermal_zone0: failed to read out thermal zone (-61) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- thermal thermal_zone0: failed to read out thermal zone https://bugs.launchpad.net/bugs/1804593 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 1804589] [NEW] AMD-Vi write error
You have been subscribed to a public bug: AMD-Vi write error. [0.777408] AMD-Vi: Unable to write to IOMMU perf counter. [0.777529] pci :00:00.2: can't derive routing for PCI INT A [0.777530] pci :00:00.2: PCI INT A: not connected [0.778000] iommu: Adding device :00:01.0 to group 0 [0.778231] iommu: Adding device :00:01.2 to group 1 [0.778463] iommu: Adding device :00:01.6 to group 2 [0.778690] iommu: Adding device :00:08.0 to group 3 [0.778914] iommu: Adding device :00:08.1 to group 4 [0.778940] iommu: Adding device :00:08.2 to group 3 [0.779154] iommu: Adding device :00:14.0 to group 5 [0.779176] iommu: Adding device :00:14.3 to group 5 [0.779444] iommu: Adding device :00:18.0 to group 6 [0.779474] iommu: Adding device :00:18.1 to group 6 [0.779495] iommu: Adding device :00:18.2 to group 6 [0.779516] iommu: Adding device :00:18.3 to group 6 [0.779544] iommu: Adding device :00:18.4 to group 6 [0.779566] iommu: Adding device :00:18.5 to group 6 [0.779586] iommu: Adding device :00:18.6 to group 6 [0.779606] iommu: Adding device :00:18.7 to group 6 [0.779835] iommu: Adding device :15:00.0 to group 7 [0.779869] iommu: Adding device :15:00.1 to group 7 [0.779903] iommu: Adding device :15:00.2 to group 7 [0.779933] iommu: Adding device :16:04.0 to group 7 [0.779956] iommu: Adding device :16:05.0 to group 7 [0.779977] iommu: Adding device :16:06.0 to group 7 [0.77] iommu: Adding device :16:07.0 to group 7 [0.780031] iommu: Adding device :1b:00.0 to group 7 [0.780058] iommu: Adding device :1c:00.0 to group 7 [0.780296] iommu: Adding device :2e:00.0 to group 8 [0.780592] iommu: Adding device :38:00.0 to group 9 [0.780672] iommu: Using direct mapping for device :38:00.0 [0.780767] iommu: Adding device :38:00.1 to group 10 [0.780807] iommu: Adding device :38:00.2 to group 10 [0.780847] iommu: Adding device :38:00.3 to group 10 [0.780887] iommu: Adding device :38:00.4 to group 10 [0.780934] iommu: Adding device :38:00.6 to group 10 [0.780965] iommu: Adding device :39:00.0 to group 3 [0.781307] AMD-Vi: Found IOMMU at :00:00.2 cap 0x40 [0.781308] AMD-Vi: Extended features (0x4f77ef22294ada): [0.781308] PPR NX GT IA GA PC GA_vAPIC [0.781311] AMD-Vi: Interrupt remapping enabled [0.781311] AMD-Vi: virtual APIC enabled [0.781534] AMD-Vi: Lazy IO/TLB flushing enabled ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- AMD-Vi write error https://bugs.launchpad.net/bugs/1804589 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 1804577] [NEW] ACPI BIOS Error (bug): Failure creating [\_SB.SMIC], AE_ALREADY_EXISTS
You have been subscribed to a public bug: I`m using Ubuntu 18.10 on my B350M GAMING PRO motherboard and AMD 2400G CPU. See some error in dmesg. Hope a fix in the upcoming update. Linux version 4.18.0-10-generic [0.076193] ACPI: Added _OSI(Module Device) [0.076193] ACPI: Added _OSI(Processor Device) [0.076194] ACPI: Added _OSI(3.0 _SCP Extensions) [0.076194] ACPI: Added _OSI(Processor Aggregator Device) [0.076195] ACPI: Added _OSI(Linux-Dell-Video) [0.076196] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio) [0.086490] ACPI BIOS Error (bug): Failure creating [\_SB.SMIC], AE_ALREADY_EXISTS (20180531/dswload2-316) [0.086497] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180531/psobject-221) [0.086501] ACPI BIOS Error (bug): Failure creating [\_SB.SMIB], AE_ALREADY_EXISTS (20180531/dsfield-594) [0.086582] ACPI: 8 ACPI AML tables successfully acquired and loaded [0.088710] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [0.090528] ACPI: Interpreter enabled [0.090541] ACPI: (supports S0 S3 S4 S5) [0.090542] ACPI: Using IOAPIC for interrupt routing [0.090886] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [0.091196] ACPI: Enabled 2 GPEs in block 00 to 1F [0.093761] ACPI: Power Resource [P0ST] (on) [0.093793] ACPI: Power Resource [P3ST] (on) [0.100120] ACPI: PCI Root Bridge [PCI0] (domain [bus 00-ff]) [0.100125] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [0.100360] acpi PNP0A08:00: _OSC: platform does not support [SHPCHotplug LTR] [0.100583] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability] [0.100596] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain [bus 00-3f] only partially covers this bridge ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: acpi bios bot-comment -- ACPI BIOS Error (bug): Failure creating [\_SB.SMIC], AE_ALREADY_EXISTS https://bugs.launchpad.net/bugs/1804577 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 1804591] Re: tsc: Fast TSC calibration failed
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804591 Title: tsc: Fast TSC calibration failed Status in linux package in Ubuntu: New Bug description: [0.00] APIC: Switch to symmetric I/O mode setup [0.004000] Switched APIC routing to physical flat. [0.004000] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 [0.024000] tsc: Fast TSC calibration failed [0.032000] tsc: PIT calibration matches HPET. 1 loops [0.032000] tsc: Detected 3600.039 MHz processor [0.032000] clocksource: tsc-early: mask: 0x max_cycles: 0x33e47874cac, max_idle_ns: 440795311274 ns [0.032000] Calibrating delay loop (skipped), value calculated using timer frequency.. 7200.07 BogoMIPS (lpj=14400156) [0.032000] pid_max: default: 32768 minimum: 301 [0.032000] Security Framework initialized [0.032000] Yama: becoming mindful. [0.032000] AppArmor: AppArmor initialized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804591/+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 1804593] Re: thermal thermal_zone0: failed to read out thermal zone
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804593 Title: thermal thermal_zone0: failed to read out thermal zone Status in linux package in Ubuntu: New Bug description: thermal thermal_zone0: failed to read out thermal zone (-61) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804593/+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 1804592] Re: usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
** Package changed: libusb (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804592 Title: usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. Status in linux package in Ubuntu: New Bug description: [0.876087] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. [0.876099] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.18 [0.876100] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [0.876101] usb usb2: Product: xHCI Host Controller [0.876102] usb usb2: Manufacturer: Linux 4.18.0-10-generic xhci-hcd [0.876103] usb usb2: SerialNumber: :15:00.0 [0.876206] hub 2-0:1.0: USB hub found [0.876215] hub 2-0:1.0: 4 ports detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804592/+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 1804589] Re: AMD-Vi write error
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804589 Title: AMD-Vi write error Status in linux package in Ubuntu: New Bug description: AMD-Vi write error. [0.777408] AMD-Vi: Unable to write to IOMMU perf counter. [0.777529] pci :00:00.2: can't derive routing for PCI INT A [0.777530] pci :00:00.2: PCI INT A: not connected [0.778000] iommu: Adding device :00:01.0 to group 0 [0.778231] iommu: Adding device :00:01.2 to group 1 [0.778463] iommu: Adding device :00:01.6 to group 2 [0.778690] iommu: Adding device :00:08.0 to group 3 [0.778914] iommu: Adding device :00:08.1 to group 4 [0.778940] iommu: Adding device :00:08.2 to group 3 [0.779154] iommu: Adding device :00:14.0 to group 5 [0.779176] iommu: Adding device :00:14.3 to group 5 [0.779444] iommu: Adding device :00:18.0 to group 6 [0.779474] iommu: Adding device :00:18.1 to group 6 [0.779495] iommu: Adding device :00:18.2 to group 6 [0.779516] iommu: Adding device :00:18.3 to group 6 [0.779544] iommu: Adding device :00:18.4 to group 6 [0.779566] iommu: Adding device :00:18.5 to group 6 [0.779586] iommu: Adding device :00:18.6 to group 6 [0.779606] iommu: Adding device :00:18.7 to group 6 [0.779835] iommu: Adding device :15:00.0 to group 7 [0.779869] iommu: Adding device :15:00.1 to group 7 [0.779903] iommu: Adding device :15:00.2 to group 7 [0.779933] iommu: Adding device :16:04.0 to group 7 [0.779956] iommu: Adding device :16:05.0 to group 7 [0.779977] iommu: Adding device :16:06.0 to group 7 [0.77] iommu: Adding device :16:07.0 to group 7 [0.780031] iommu: Adding device :1b:00.0 to group 7 [0.780058] iommu: Adding device :1c:00.0 to group 7 [0.780296] iommu: Adding device :2e:00.0 to group 8 [0.780592] iommu: Adding device :38:00.0 to group 9 [0.780672] iommu: Using direct mapping for device :38:00.0 [0.780767] iommu: Adding device :38:00.1 to group 10 [0.780807] iommu: Adding device :38:00.2 to group 10 [0.780847] iommu: Adding device :38:00.3 to group 10 [0.780887] iommu: Adding device :38:00.4 to group 10 [0.780934] iommu: Adding device :38:00.6 to group 10 [0.780965] iommu: Adding device :39:00.0 to group 3 [0.781307] AMD-Vi: Found IOMMU at :00:00.2 cap 0x40 [0.781308] AMD-Vi: Extended features (0x4f77ef22294ada): [0.781308] PPR NX GT IA GA PC GA_vAPIC [0.781311] AMD-Vi: Interrupt remapping enabled [0.781311] AMD-Vi: virtual APIC enabled [0.781534] AMD-Vi: Lazy IO/TLB flushing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589/+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 1804590] Re: kgd2kfd_probe failed DID 15dd is missing in supported_devices
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804590 Title: kgd2kfd_probe failed DID 15dd is missing in supported_devices Status in linux package in Ubuntu: New Bug description: dmesg [1.456816] Console: switching to colour dummy device 80x25 [1.457058] [drm] initializing kernel modesetting (RAVEN 0x1002:0x15DD 0x1462:0x7A39 0xC6). [1.457068] [drm] register mmio base: 0xFE40 [1.457069] [drm] register mmio size: 524288 [1.457084] [drm] probing gen 2 caps for device 1022:15db = 700d03/e [1.457086] [drm] probing mlw for device 1022:15db = 700d03 [1.457088] [drm] add ip block number 0 [1.457089] [drm] add ip block number 1 [1.457090] [drm] add ip block number 2 [1.457090] [drm] add ip block number 3 [1.457091] [drm] add ip block number 4 [1.457091] [drm] add ip block number 5 [1.457092] [drm] add ip block number 6 [1.457093] [drm] add ip block number 7 [1.457093] [drm] add ip block number 8 [1.457110] kfd kfd: DID 15dd is missing in supported_devices [1.457111] kfd kfd: kgd2kfd_probe failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804590/+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 1804593] 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 1804593 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804593 Title: thermal thermal_zone0: failed to read out thermal zone Status in linux package in Ubuntu: Incomplete Bug description: thermal thermal_zone0: failed to read out thermal zone (-61) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804593/+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 1804590] 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 1804590 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804590 Title: kgd2kfd_probe failed DID 15dd is missing in supported_devices Status in linux package in Ubuntu: Incomplete Bug description: dmesg [1.456816] Console: switching to colour dummy device 80x25 [1.457058] [drm] initializing kernel modesetting (RAVEN 0x1002:0x15DD 0x1462:0x7A39 0xC6). [1.457068] [drm] register mmio base: 0xFE40 [1.457069] [drm] register mmio size: 524288 [1.457084] [drm] probing gen 2 caps for device 1022:15db = 700d03/e [1.457086] [drm] probing mlw for device 1022:15db = 700d03 [1.457088] [drm] add ip block number 0 [1.457089] [drm] add ip block number 1 [1.457090] [drm] add ip block number 2 [1.457090] [drm] add ip block number 3 [1.457091] [drm] add ip block number 4 [1.457091] [drm] add ip block number 5 [1.457092] [drm] add ip block number 6 [1.457093] [drm] add ip block number 7 [1.457093] [drm] add ip block number 8 [1.457110] kfd kfd: DID 15dd is missing in supported_devices [1.457111] kfd kfd: kgd2kfd_probe failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804590/+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 1804591] 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 1804591 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804591 Title: tsc: Fast TSC calibration failed Status in linux package in Ubuntu: Incomplete Bug description: [0.00] APIC: Switch to symmetric I/O mode setup [0.004000] Switched APIC routing to physical flat. [0.004000] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 [0.024000] tsc: Fast TSC calibration failed [0.032000] tsc: PIT calibration matches HPET. 1 loops [0.032000] tsc: Detected 3600.039 MHz processor [0.032000] clocksource: tsc-early: mask: 0x max_cycles: 0x33e47874cac, max_idle_ns: 440795311274 ns [0.032000] Calibrating delay loop (skipped), value calculated using timer frequency.. 7200.07 BogoMIPS (lpj=14400156) [0.032000] pid_max: default: 32768 minimum: 301 [0.032000] Security Framework initialized [0.032000] Yama: becoming mindful. [0.032000] AppArmor: AppArmor initialized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804591/+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 1804592] 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 1804592 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: cosmic -- 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/1804592 Title: usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. Status in linux package in Ubuntu: Incomplete Bug description: [0.876087] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. [0.876099] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.18 [0.876100] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [0.876101] usb usb2: Product: xHCI Host Controller [0.876102] usb usb2: Manufacturer: Linux 4.18.0-10-generic xhci-hcd [0.876103] usb usb2: SerialNumber: :15:00.0 [0.876206] hub 2-0:1.0: USB hub found [0.876215] hub 2-0:1.0: 4 ports detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804592/+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 1804589] 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 1804589 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804589 Title: AMD-Vi write error Status in linux package in Ubuntu: Incomplete Bug description: AMD-Vi write error. [0.777408] AMD-Vi: Unable to write to IOMMU perf counter. [0.777529] pci :00:00.2: can't derive routing for PCI INT A [0.777530] pci :00:00.2: PCI INT A: not connected [0.778000] iommu: Adding device :00:01.0 to group 0 [0.778231] iommu: Adding device :00:01.2 to group 1 [0.778463] iommu: Adding device :00:01.6 to group 2 [0.778690] iommu: Adding device :00:08.0 to group 3 [0.778914] iommu: Adding device :00:08.1 to group 4 [0.778940] iommu: Adding device :00:08.2 to group 3 [0.779154] iommu: Adding device :00:14.0 to group 5 [0.779176] iommu: Adding device :00:14.3 to group 5 [0.779444] iommu: Adding device :00:18.0 to group 6 [0.779474] iommu: Adding device :00:18.1 to group 6 [0.779495] iommu: Adding device :00:18.2 to group 6 [0.779516] iommu: Adding device :00:18.3 to group 6 [0.779544] iommu: Adding device :00:18.4 to group 6 [0.779566] iommu: Adding device :00:18.5 to group 6 [0.779586] iommu: Adding device :00:18.6 to group 6 [0.779606] iommu: Adding device :00:18.7 to group 6 [0.779835] iommu: Adding device :15:00.0 to group 7 [0.779869] iommu: Adding device :15:00.1 to group 7 [0.779903] iommu: Adding device :15:00.2 to group 7 [0.779933] iommu: Adding device :16:04.0 to group 7 [0.779956] iommu: Adding device :16:05.0 to group 7 [0.779977] iommu: Adding device :16:06.0 to group 7 [0.77] iommu: Adding device :16:07.0 to group 7 [0.780031] iommu: Adding device :1b:00.0 to group 7 [0.780058] iommu: Adding device :1c:00.0 to group 7 [0.780296] iommu: Adding device :2e:00.0 to group 8 [0.780592] iommu: Adding device :38:00.0 to group 9 [0.780672] iommu: Using direct mapping for device :38:00.0 [0.780767] iommu: Adding device :38:00.1 to group 10 [0.780807] iommu: Adding device :38:00.2 to group 10 [0.780847] iommu: Adding device :38:00.3 to group 10 [0.780887] iommu: Adding device :38:00.4 to group 10 [0.780934] iommu: Adding device :38:00.6 to group 10 [0.780965] iommu: Adding device :39:00.0 to group 3 [0.781307] AMD-Vi: Found IOMMU at :00:00.2 cap 0x40 [0.781308] AMD-Vi: Extended features (0x4f77ef22294ada): [0.781308] PPR NX GT IA GA PC GA_vAPIC [0.781311] AMD-Vi: Interrupt remapping enabled [0.781311] AMD-Vi: virtual APIC enabled [0.781534] AMD-Vi: Lazy IO/TLB flushing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589/+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 1804577] Re: ACPI BIOS Error (bug): Failure creating [\_SB.SMIC], AE_ALREADY_EXISTS
** Package changed: acpi (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804577 Title: ACPI BIOS Error (bug): Failure creating [\_SB.SMIC], AE_ALREADY_EXISTS Status in linux package in Ubuntu: Confirmed Bug description: I`m using Ubuntu 18.10 on my B350M GAMING PRO motherboard and AMD 2400G CPU. See some error in dmesg. Hope a fix in the upcoming update. Linux version 4.18.0-10-generic [0.076193] ACPI: Added _OSI(Module Device) [0.076193] ACPI: Added _OSI(Processor Device) [0.076194] ACPI: Added _OSI(3.0 _SCP Extensions) [0.076194] ACPI: Added _OSI(Processor Aggregator Device) [0.076195] ACPI: Added _OSI(Linux-Dell-Video) [0.076196] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio) [0.086490] ACPI BIOS Error (bug): Failure creating [\_SB.SMIC], AE_ALREADY_EXISTS (20180531/dswload2-316) [0.086497] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180531/psobject-221) [0.086501] ACPI BIOS Error (bug): Failure creating [\_SB.SMIB], AE_ALREADY_EXISTS (20180531/dsfield-594) [0.086582] ACPI: 8 ACPI AML tables successfully acquired and loaded [0.088710] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [0.090528] ACPI: Interpreter enabled [0.090541] ACPI: (supports S0 S3 S4 S5) [0.090542] ACPI: Using IOAPIC for interrupt routing [0.090886] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [0.091196] ACPI: Enabled 2 GPEs in block 00 to 1F [0.093761] ACPI: Power Resource [P0ST] (on) [0.093793] ACPI: Power Resource [P3ST] (on) [0.100120] ACPI: PCI Root Bridge [PCI0] (domain [bus 00-ff]) [0.100125] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [0.100360] acpi PNP0A08:00: _OSC: platform does not support [SHPCHotplug LTR] [0.100583] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability] [0.100596] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain [bus 00-3f] only partially covers this bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804577/+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 1804577] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: cosmic -- 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/1804577 Title: ACPI BIOS Error (bug): Failure creating [\_SB.SMIC], AE_ALREADY_EXISTS Status in linux package in Ubuntu: Confirmed Bug description: I`m using Ubuntu 18.10 on my B350M GAMING PRO motherboard and AMD 2400G CPU. See some error in dmesg. Hope a fix in the upcoming update. Linux version 4.18.0-10-generic [0.076193] ACPI: Added _OSI(Module Device) [0.076193] ACPI: Added _OSI(Processor Device) [0.076194] ACPI: Added _OSI(3.0 _SCP Extensions) [0.076194] ACPI: Added _OSI(Processor Aggregator Device) [0.076195] ACPI: Added _OSI(Linux-Dell-Video) [0.076196] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio) [0.086490] ACPI BIOS Error (bug): Failure creating [\_SB.SMIC], AE_ALREADY_EXISTS (20180531/dswload2-316) [0.086497] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180531/psobject-221) [0.086501] ACPI BIOS Error (bug): Failure creating [\_SB.SMIB], AE_ALREADY_EXISTS (20180531/dsfield-594) [0.086582] ACPI: 8 ACPI AML tables successfully acquired and loaded [0.088710] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [0.090528] ACPI: Interpreter enabled [0.090541] ACPI: (supports S0 S3 S4 S5) [0.090542] ACPI: Using IOAPIC for interrupt routing [0.090886] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [0.091196] ACPI: Enabled 2 GPEs in block 00 to 1F [0.093761] ACPI: Power Resource [P0ST] (on) [0.093793] ACPI: Power Resource [P3ST] (on) [0.100120] ACPI: PCI Root Bridge [PCI0] (domain [bus 00-ff]) [0.100125] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [0.100360] acpi PNP0A08:00: _OSC: platform does not support [SHPCHotplug LTR] [0.100583] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability] [0.100596] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain [bus 00-3f] only partially covers this bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804577/+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
