[Kernel-packages] [Bug 1796443]
https://marc.info/?l=linux-edac&m=154331383121359&w=2 [PATCH] x86/mce/AMD: Make sure banks were initialized before accessing them -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796443 Title: HP EliteBook 745 G5 (Ryzen 2500U) fails to boot unless `mce=off` is set on command line Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: My new Elitebook, with the latest bios 1.03.01, refuses to boot any kernel later than 4.10 unless mce=off is appended to the kernel command line. As in, there are no kernel messages at all after grub (yes, quiet and splash were removed from the command line). Perhaps it crashes before the efifb kicks in? System operates fine if mce=off is added to the kernel command line (and iommu=soft, but that's a separate issue, and fails with kernel output in that case). I opened upstream bug here : https://bugzilla.kernel.org/show_bug.cgi?id=201291 I bisected the problem down to this commit (and the few before it, which also added extra MCE output, but didn't actually crash): 18807ddb7f88d4ac3797302bafb18143d573e66f is the first bad commit commit 18807ddb7f88d4ac3797302bafb18143d573e66f Author: Yazen Ghannam Date: Tue Nov 15 15:13:53 2016 -0600 x86/mce/AMD: Reset Threshold Limit after logging error The error count field in MCA_MISC does not get reset by hardware when the threshold has been reached. Software is expected to reset it. Currently, the threshold limit only gets reset during init or when a user writes to sysfs. If the user is not monitoring threshold interrupts and resetting the limit then the user will only see 1 interrupt when the limit is first hit. So if, for example, the limit is set to 10 then only 1 interrupt will be recorded after 10 errors even if 100 errors have occurred. The user may then assume that only 10 errors have occurred. There are threads online about this being related to the latest bios. The upstream bug has acpidump attached. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2015 F pulseaudio /dev/snd/pcmC1D0p: john 2015 F...m pulseaudio /dev/snd/controlC0: john 2015 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Oct 5 23:24:45 2018 InstallationDate: Installed on 2018-09-30 (5 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) Lsusb: Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteBook 745 G5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=5cf73665-d2a3-4203-80fd-659faf1afea4 ro quiet splash iommu=soft mce=off RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: r8822be UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2018 dmi.bios.vendor: HP dmi.bios.version: Q81 Ver. 01.03.01 dmi.board.name: 83D5 dmi.board.vendor: HP dmi.board.version: KBC Version 08.47.00 dmi.chassis.asset.tag: 5CG838305Y dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ81Ver.01.03.01:bd07/26/2018:svnHP:pnHPEliteBook745G5:pvr:rvnHP:rn83D5:rvrKBCVersion08.47.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 745 G5 dmi.product.sku: 2MG23AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796443/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered
Mainline 4.20-rc2 has the bug.
I went back and tested mainline 4.18-rc1 and mainline 4.18 a few more
times, and they actually do have the bug. So it appears that the bug is
not fixed upstream after all.
Shall we go back to bisecting for the change that introduced the bug?
--
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/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Artful:
Won't Fix
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
See attached dmesg outputs for booting kernels 4.11.x (working) and
4.13.x (not working).
dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x.
btrfs scans for devices after all 4 (sda, sdb, sdc, sdd) of the devices have
been discovered by the kernel. The btrfs RAID1 filesystem mounts, and
everything is good.
dmesg-4.13.0-36-fail.txt shows the dmesg output when booting kernel 4.13.x.
btrfs scans for devices after only 2 (sda, sdb) of the devices have been
discovered by the kernel. The btrfs RAID1 filesystem fails to mount ("failed
to read the system array: -5"). The remaining 2 devices (sdc, sdd) are
discovered by the kernel immediately afterward. At the end of the log, I run
`btrfs device scan` and mount the filesystem manually.
Hardware:
HP ProLiant MicroServer Gen8
4x WDC WD20EFRX
---
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: aplay: device_list:270: no soundcards found...
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
ArecordDevices: arecord: device_list:270: no soundcards found...
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2015-10-15 (933 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
MachineType: HP ProLiant MicroServer Gen8
Package: linux (not installed)
ProcEnviron:
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic
root=UUID=d976ab07-8377-46dd-ac6c-f5f7312a8305 ro rootflags=subvol=@
rootdelay=10
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Tags: bionic apport-hook-error
Uname: Linux 4.15.0-20-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 07/16/2015
dmi.bios.vendor: HP
dmi.bios.version: J06
dmi.chassis.type: 7
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrJ06:bd07/16/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:
dmi.product.family: ProLiant
dmi.product.name: ProLiant MicroServer Gen8
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752961/+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 1758942] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1758942 Title: [i915_bpo] écran noir au démarrage Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: New Bug description: écran noir, impossible de rentrer mon mot de passe au démarrage, lecteur video ne fonctionne pas, impossible de supprimer des logiciels, plantage en cours de session ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Mar 26 16:53:16 2018 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:078c] InstallationDate: Installed on 2018-03-15 (11 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 15-3567 ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=fbcd4cac-8cb9-4527-af8f-a07d69322204 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.0.3 dmi.board.name: 0FGN4M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.0.3:bd08/25/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0FGN4M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 15-3567 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Mar 26 16:32:28 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5574 vendor CMN xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758942/+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 1758942] Re: écran noir au démarrage
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Summary changed: - écran noir au démarrage + [i915_bpo] écran noir au démarrage ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1758942 Title: [i915_bpo] écran noir au démarrage Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: New Bug description: écran noir, impossible de rentrer mon mot de passe au démarrage, lecteur video ne fonctionne pas, impossible de supprimer des logiciels, plantage en cours de session ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Mar 26 16:53:16 2018 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:078c] InstallationDate: Installed on 2018-03-15 (11 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 15-3567 ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=fbcd4cac-8cb9-4527-af8f-a07d69322204 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.0.3 dmi.board.name: 0FGN4M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.0.3:bd08/25/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0FGN4M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 15-3567 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Mar 26 16:32:28 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5574 vendor CMN xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758942/+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 1805122] Re: One of two monitor work after 18.10 update
Sorry for another comment. Just restarted the computer again and had no troubles with the screens. When the problem appears again, I will inform you here. -- 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/1805122 Title: One of two monitor work after 18.10 update Status in linux package in Ubuntu: Confirmed Bug description: Hi ! I just upgraded 18.04 to 18.10. I got two monitor connected on motherboard. One in VGA, the other in hdmi. Both screens works until i log in. After this, the vga screen become black and display nothing. The only solution i found was to unplug vga cable and re plug it after desktop charged completely. Any suggestion? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805122/+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 1804991] Re: Front panel HeadPhone Jack undetectable
Select HeadPhones manually can use the front HeadPhones port. ** Attachment added: "Output Devices.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804991/+attachment/5216939/+files/Output%20Devices.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804991 Title: Front panel HeadPhone Jack undetectable Status in linux package in Ubuntu: Confirmed Bug description: Runing Ubuntu 18.10 x86_64 with kernel Ubuntu 4.18.0-11.12-generic 4.18.12. Found front panel audio jack detection issue. Front panel HeadPhone Jack shows unplugged in the Output Devices tab of PulseAudio Volume Control despite headphones plugged in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804991/+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 1804991] Re: Front panel HeadPhone Jack undetectable
aplay -L default Playback/recording through the PulseAudio sound server null Discard all samples (playback) or generate zero samples (capture) pulse PulseAudio Sound Server hdmi:CARD=Generic,DEV=0 HD-Audio Generic, HDMI 0 HDMI Audio Output hdmi:CARD=Generic,DEV=1 HD-Audio Generic, HDMI 1 HDMI Audio Output dmix:CARD=Generic,DEV=3 HD-Audio Generic, HDMI 0 Direct sample mixing device dmix:CARD=Generic,DEV=7 HD-Audio Generic, HDMI 1 Direct sample mixing device dsnoop:CARD=Generic,DEV=3 HD-Audio Generic, HDMI 0 Direct sample snooping device dsnoop:CARD=Generic,DEV=7 HD-Audio Generic, HDMI 1 Direct sample snooping device hw:CARD=Generic,DEV=3 HD-Audio Generic, HDMI 0 Direct hardware device without any conversions hw:CARD=Generic,DEV=7 HD-Audio Generic, HDMI 1 Direct hardware device without any conversions plughw:CARD=Generic,DEV=3 HD-Audio Generic, HDMI 0 Hardware device with all software conversions plughw:CARD=Generic,DEV=7 HD-Audio Generic, HDMI 1 Hardware device with all software conversions sysdefault:CARD=Generic_1 HD-Audio Generic, ALC887-VD Analog Default Audio Device front:CARD=Generic_1,DEV=0 HD-Audio Generic, ALC887-VD Analog Front speakers surround21:CARD=Generic_1,DEV=0 HD-Audio Generic, ALC887-VD Analog 2.1 Surround output to Front and Subwoofer speakers surround40:CARD=Generic_1,DEV=0 HD-Audio Generic, ALC887-VD Analog 4.0 Surround output to Front and Rear speakers surround41:CARD=Generic_1,DEV=0 HD-Audio Generic, ALC887-VD Analog 4.1 Surround output to Front, Rear and Subwoofer speakers surround50:CARD=Generic_1,DEV=0 HD-Audio Generic, ALC887-VD Analog 5.0 Surround output to Front, Center and Rear speakers surround51:CARD=Generic_1,DEV=0 HD-Audio Generic, ALC887-VD Analog 5.1 Surround output to Front, Center, Rear and Subwoofer speakers surround71:CARD=Generic_1,DEV=0 HD-Audio Generic, ALC887-VD Analog 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers dmix:CARD=Generic_1,DEV=0 HD-Audio Generic, ALC887-VD Analog Direct sample mixing device dsnoop:CARD=Generic_1,DEV=0 HD-Audio Generic, ALC887-VD Analog Direct sample snooping device hw:CARD=Generic_1,DEV=0 HD-Audio Generic, ALC887-VD Analog Direct hardware device without any conversions plughw:CARD=Generic_1,DEV=0 HD-Audio Generic, ALC887-VD Analog Hardware device with all software conversions ** Attachment removed: "alsamixer.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804991/+attachment/5216943/+files/alsamixer.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804991 Title: Front panel HeadPhone Jack undetectable Status in linux package in Ubuntu: Confirmed Bug description: Runing Ubuntu 18.10 x86_64 with kernel Ubuntu 4.18.0-11.12-generic 4.18.12. Found front panel audio jack detection issue. Front panel HeadPhone Jack shows unplugged in the Output Devices tab of PulseAudio Volume Control despite headphones plugged in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804991/+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 1804991] Re: Front panel HeadPhone Jack undetectable
** Attachment added: "alsamixer.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804991/+attachment/5216945/+files/alsamixer.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804991 Title: Front panel HeadPhone Jack undetectable Status in linux package in Ubuntu: Confirmed Bug description: Runing Ubuntu 18.10 x86_64 with kernel Ubuntu 4.18.0-11.12-generic 4.18.12. Found front panel audio jack detection issue. Front panel HeadPhone Jack shows unplugged in the Output Devices tab of PulseAudio Volume Control despite headphones plugged in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804991/+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 1804991] Re: Front panel HeadPhone Jack undetectable
When manually selected the HeadPhones in the Output Devices menu, I can use the front headphone and the alsamixer shows below. ** Attachment added: "alsamixer.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804991/+attachment/5216943/+files/alsamixer.png ** 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/1804991 Title: Front panel HeadPhone Jack undetectable Status in linux package in Ubuntu: Confirmed Bug description: Runing Ubuntu 18.10 x86_64 with kernel Ubuntu 4.18.0-11.12-generic 4.18.12. Found front panel audio jack detection issue. Front panel HeadPhone Jack shows unplugged in the Output Devices tab of PulseAudio Volume Control despite headphones plugged in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804991/+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 1804991] Re: Front panel HeadPhone Jack undetectable
dmesg of kernel 4.18.0-11-generic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589/+attachment/5216936/+files/4.18.0-11-generic%20dmesg dmesg of kernel 4.20.0-rc4-generic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589/+attachment/5216937/+files/4.20-rc4%20dmesg -- 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/1804991 Title: Front panel HeadPhone Jack undetectable Status in linux package in Ubuntu: Confirmed Bug description: Runing Ubuntu 18.10 x86_64 with kernel Ubuntu 4.18.0-11.12-generic 4.18.12. Found front panel audio jack detection issue. Front panel HeadPhone Jack shows unplugged in the Output Devices tab of PulseAudio Volume Control despite headphones plugged in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804991/+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 1804991] Re: Front panel HeadPhone Jack undetectable
Output without headphone plugged in. Pin 0x11 (Not connected): present = No Pin 0x12 (Not connected): present = No Pin 0x14 (Green Line Out, Rear side): present = No Pin 0x15 (Not connected): present = No Pin 0x16 (Not connected): present = No Pin 0x17 (Not connected): present = No Pin 0x18 (Pink Mic, Rear side): present = No Pin 0x19 (Pink Mic, Front side): present = No Pin 0x1a (Blue Line In, Rear side): present = No Pin 0x1b (Green Headphone, Front side): present = No Pin 0x1c (Not connected): present = No Pin 0x1d (Not connected): present = No Pin 0x1e (Not connected): present = No Pin 0x1f (Not connected): present = No Output with headphone plugged in. Pin 0x11 (Not connected): present = No Pin 0x12 (Not connected): present = No Pin 0x14 (Green Line Out, Rear side): present = No Pin 0x15 (Not connected): present = No Pin 0x16 (Not connected): present = No Pin 0x17 (Not connected): present = No Pin 0x18 (Pink Mic, Rear side): present = No Pin 0x19 (Pink Mic, Front side): present = No Pin 0x1a (Blue Line In, Rear side): present = No Pin 0x1b (Green Headphone, Front side): present = No Pin 0x1c (Not connected): present = No Pin 0x1d (Not connected): present = No Pin 0x1e (Not connected): present = No Pin 0x1f (Not connected): present = No -- 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/1804991 Title: Front panel HeadPhone Jack undetectable Status in linux package in Ubuntu: Confirmed Bug description: Runing Ubuntu 18.10 x86_64 with kernel Ubuntu 4.18.0-11.12-generic 4.18.12. Found front panel audio jack detection issue. Front panel HeadPhone Jack shows unplugged in the Output Devices tab of PulseAudio Volume Control despite headphones plugged in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804991/+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
dmesg of kernel 4.18.0-11-generic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589/+attachment/5216936/+files/4.18.0-11-generic%20dmesg dmesg of kernel 4.20.0-rc4-generic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589/+attachment/5216937/+files/4.20-rc4%20dmesg -- 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: Confirmed 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 1804577] Re: ACPI BIOS Error (bug): Failure creating [\_SB.SMIC], AE_ALREADY_EXISTS
** Attachment added: "4.20-rc4 dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804577/+attachment/5216935/+files/4.20-rc4%20dmesg -- 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] Re: ACPI BIOS Error (bug): Failure creating [\_SB.SMIC], AE_ALREADY_EXISTS
** Attachment removed: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804577/+attachment/5215199/+files/dmesg.txt ** Attachment added: "4.18.0-11-generic dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804577/+attachment/5216934/+files/4.18.0-11-generic%20dmesg -- 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 1804589] Re: AMD-Vi write error
** Attachment added: "4.20-rc4 dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589/+attachment/5216937/+files/4.20-rc4%20dmesg -- 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: Confirmed 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 1804589] Re: AMD-Vi write error
** Attachment removed: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589/+attachment/5216070/+files/dmesg.txt ** Attachment added: "4.18.0-11-generic dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589/+attachment/5216936/+files/4.18.0-11-generic%20dmesg -- 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: Confirmed 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
dmesg of kernel 4.18.0-11-generic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589/+attachment/5216936/+files/4.18.0-11-generic%20dmesg dmesg of kernel 4.20.0-rc4-generic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589/+attachment/5216937/+files/4.20-rc4%20dmesg ** Attachment removed: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804590/+attachment/5216920/+files/dmesg.txt ** Attachment removed: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804590/+attachment/5216047/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804590 Title: kgd2kfd_probe failed DID 15dd is missing in supported_devices Status in linux package in Ubuntu: Confirmed 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 1804592] Re: usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
dmesg of kernel 4.18.0-11-generic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589/+attachment/5216936/+files/4.18.0-11-generic%20dmesg dmesg of kernel 4.20.0-rc4-generic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589/+attachment/5216937/+files/4.20-rc4%20dmesg ** Attachment removed: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804592/+attachment/5216060/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804592 Title: usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. Status in linux package in Ubuntu: Confirmed 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 1804591] Re: tsc: Fast TSC calibration failed
dmesg of kernel 4.18.0-11-generic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589/+attachment/5216936/+files/4.18.0-11-generic%20dmesg dmesg of kernel 4.20.0-rc4-generic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589/+attachment/5216937/+files/4.20-rc4%20dmesg -- 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: Confirmed 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 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: 1438 F pulseaudio /dev/snd/controlC0: 1438 F pulseaudio CurrentDesktop: LXQt DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-11-22 (2 days ago) InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Micro-Star International Co., Ltd. MS-7A39 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=x ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 Tags: cosmic Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 09/28/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.I0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M GAMING PRO (MS-7A39) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.I0:bd09/28/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A39:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350MGAMINGPRO(MS-7A39):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A39 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/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 1804991] Re: Front panel HeadPhone Jack undetectable
** Attachment removed: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804991/+attachment/5216061/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804991 Title: Front panel HeadPhone Jack undetectable Status in linux package in Ubuntu: Incomplete Bug description: Runing Ubuntu 18.10 x86_64 with kernel Ubuntu 4.18.0-11.12-generic 4.18.12. Found front panel audio jack detection issue. Front panel HeadPhone Jack shows unplugged in the Output Devices tab of PulseAudio Volume Control despite headphones plugged in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804991/+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
** Attachment removed: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589/+attachment/5216918/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804589 Title: AMD-Vi write error Status in linux package in Ubuntu: Confirmed 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 1804591] Re: tsc: Fast TSC calibration failed
** Attachment removed: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804591/+attachment/5216921/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804591 Title: tsc: Fast TSC calibration failed Status in linux package in Ubuntu: Confirmed 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 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: 1438 F pulseaudio /dev/snd/controlC0: 1438 F pulseaudio CurrentDesktop: LXQt DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-11-22 (2 days ago) InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Micro-Star International Co., Ltd. MS-7A39 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=x ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 Tags: cosmic Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 09/28/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.I0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M GAMING PRO (MS-7A39) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.I0:bd09/28/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A39:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350MGAMINGPRO(MS-7A39):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A39 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/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 1804590] Re: kgd2kfd_probe failed DID 15dd is missing in supported_devices
The kgd2kfd_probe failed error seems gone with mainline kernel v4.20-rc4, here is the warnings during the installation. Processing triggers for linux-image-unsigned-4.20.0-042000rc4-generic (4.20.0-042000rc4.201811252331) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.20.0-042000rc4-generic cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries nor crypto modules. If that's on purpose, you may want to uninstall the 'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs integration and avoid this warning. W: Possible missing firmware /lib/firmware/amdgpu/raven2_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_uvd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_uvd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_vce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_vce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_dmcu.bin for module amdgpu /etc/kernel/postinst.d/zz-update-grub: Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.20.0-042000rc4-generic Found initrd image: /boot/initrd.img-4.20.0-042000rc4-generic Found linux image: /boot/vmlinuz-4.18.0-11-generic Found initrd image: /boot/initrd.img-4.18.0-11-generic Found linux image: /boot/vmlinuz-4.18.0-10-generic Found initrd image: /boot/initrd.img-4.18.0-10-generic
[Kernel-packages] [Bug 1804590] Re: kgd2kfd_probe failed DID 15dd is missing in supported_devices
Just install mainline kernel v4.20-rc4, here is the warnings during the installation. kgd2kfd_probe failed error seems gone with the new kernel. Processing triggers for linux-image-unsigned-4.20.0-042000rc4-generic (4.20.0-042000rc4.201811252331) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.20.0-042000rc4-generic cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries nor crypto modules. If that's on purpose, you may want to uninstall the 'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs integration and avoid this warning. W: Possible missing firmware /lib/firmware/amdgpu/raven2_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_uvd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_uvd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_vce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_vce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_dmcu.bin for module amdgpu /etc/kernel/postinst.d/zz-update-grub: Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.20.0-042000rc4-generic Found initrd image: /boot/initrd.img-4.20.0-042000rc4-generic Found linux image: /boot/vmlinuz-4.18.0-11-generic Found initrd image: /boot/initrd.img-4.18.0-11-generic Found linux image: /boot/vmlinuz-4.18.0-10-generic Found initrd image: /boot/init
[Kernel-packages] [Bug 1804591] Re: tsc: Fast TSC calibration failed
4.20.0-042000rc4-generic ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804591/+attachment/5216921/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804591 Title: tsc: Fast TSC calibration failed Status in linux package in Ubuntu: Confirmed 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 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: 1438 F pulseaudio /dev/snd/controlC0: 1438 F pulseaudio CurrentDesktop: LXQt DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-11-22 (2 days ago) InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Micro-Star International Co., Ltd. MS-7A39 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=x ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 Tags: cosmic Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 09/28/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.I0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M GAMING PRO (MS-7A39) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.I0:bd09/28/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A39:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350MGAMINGPRO(MS-7A39):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A39 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/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 1804591] Re: tsc: Fast TSC calibration failed
The issue remains with mainline kernel v4.20-rc4, here is the warnings during the installation. kgd2kfd_probe failed error seems gone with the new kernel. Processing triggers for linux-image-unsigned-4.20.0-042000rc4-generic (4.20.0-042000rc4.201811252331) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.20.0-042000rc4-generic cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries nor crypto modules. If that's on purpose, you may want to uninstall the 'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs integration and avoid this warning. W: Possible missing firmware /lib/firmware/amdgpu/raven2_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_uvd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_uvd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_vce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_vce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_dmcu.bin for module amdgpu /etc/kernel/postinst.d/zz-update-grub: Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.20.0-042000rc4-generic Found initrd image: /boot/initrd.img-4.20.0-042000rc4-generic Found linux image: /boot/vmlinuz-4.18.0-11-generic Found initrd image: /boot/initrd.img-4.18.0-11-generic Found linux image: /boot/vmlinuz-4.18.0-10-generic Found initrd image:
[Kernel-packages] [Bug 1804589] Re: AMD-Vi write error
The issue remains with mainline kernel v4.20-rc4, here is the warnings during the installation. kgd2kfd_probe failed error seems gone with the new kernel. Processing triggers for linux-image-unsigned-4.20.0-042000rc4-generic (4.20.0-042000rc4.201811252331) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.20.0-042000rc4-generic cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries nor crypto modules. If that's on purpose, you may want to uninstall the 'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs integration and avoid this warning. W: Possible missing firmware /lib/firmware/amdgpu/raven2_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_uvd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_uvd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_vce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_vce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_dmcu.bin for module amdgpu /etc/kernel/postinst.d/zz-update-grub: Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.20.0-042000rc4-generic Found initrd image: /boot/initrd.img-4.20.0-042000rc4-generic Found linux image: /boot/vmlinuz-4.18.0-11-generic Found initrd image: /boot/initrd.img-4.18.0-11-generic Found linux image: /boot/vmlinuz-4.18.0-10-generic Found initrd image:
[Kernel-packages] [Bug 1804592] Re: usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804592 Title: usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. Status in linux package in Ubuntu: Confirmed 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 1804590] Re: kgd2kfd_probe failed DID 15dd is missing in supported_devices
4.20.0-042000rc4-generic ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804590/+attachment/5216920/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804590 Title: kgd2kfd_probe failed DID 15dd is missing in supported_devices Status in linux package in Ubuntu: Confirmed 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 1804577] Re: ACPI BIOS Error (bug): Failure creating [\_SB.SMIC], AE_ALREADY_EXISTS
The issue remains with mainline kernel v4.20-rc4, here is the warnings during the installation. kgd2kfd_probe failed error seems gone with the new kernel. Processing triggers for linux-image-unsigned-4.20.0-042000rc4-generic (4.20.0-042000rc4.201811252331) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.20.0-042000rc4-generic cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries nor crypto modules. If that's on purpose, you may want to uninstall the 'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs integration and avoid this warning. W: Possible missing firmware /lib/firmware/amdgpu/raven2_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_uvd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_uvd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_vce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_vce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_dmcu.bin for module amdgpu /etc/kernel/postinst.d/zz-update-grub: Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.20.0-042000rc4-generic Found initrd image: /boot/initrd.img-4.20.0-042000rc4-generic Found linux image: /boot/vmlinuz-4.18.0-11-generic Found initrd image: /boot/initrd.img-4.18.0-11-generic Found linux image: /boot/vmlinuz-4.18.0-10-generic Found initrd image:
[Kernel-packages] [Bug 1804593] Re: thermal thermal_zone0: failed to read out thermal zone
The issue remains with mainline kernel v4.20-rc4, here is the warnings during the installation. kgd2kfd_probe failed error seems gone with the new kernel. Processing triggers for linux-image-unsigned-4.20.0-042000rc4-generic (4.20.0-042000rc4.201811252331) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.20.0-042000rc4-generic cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries nor crypto modules. If that's on purpose, you may want to uninstall the 'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs integration and avoid this warning. W: Possible missing firmware /lib/firmware/amdgpu/raven2_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_uvd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_uvd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_vce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_vce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_dmcu.bin for module amdgpu /etc/kernel/postinst.d/zz-update-grub: Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.20.0-042000rc4-generic Found initrd image: /boot/initrd.img-4.20.0-042000rc4-generic Found linux image: /boot/vmlinuz-4.18.0-11-generic Found initrd image: /boot/initrd.img-4.18.0-11-generic Found linux image: /boot/vmlinuz-4.18.0-10-generic Found initrd image:
[Kernel-packages] [Bug 1804592] Re: usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
The issue remains with mainline kernel v4.20-rc4, here is the warnings during the installation. kgd2kfd_probe failed error seems gone with the new kernel. Processing triggers for linux-image-unsigned-4.20.0-042000rc4-generic (4.20.0-042000rc4.201811252331) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.20.0-042000rc4-generic cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries nor crypto modules. If that's on purpose, you may want to uninstall the 'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs integration and avoid this warning. W: Possible missing firmware /lib/firmware/amdgpu/raven2_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_uvd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_uvd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_vce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_vce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_dmcu.bin for module amdgpu /etc/kernel/postinst.d/zz-update-grub: Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.20.0-042000rc4-generic Found initrd image: /boot/initrd.img-4.20.0-042000rc4-generic Found linux image: /boot/vmlinuz-4.18.0-11-generic Found initrd image: /boot/initrd.img-4.18.0-11-generic Found linux image: /boot/vmlinuz-4.18.0-10-generic Found initrd image:
[Kernel-packages] [Bug 1804577] Re: ACPI BIOS Error (bug): Failure creating [\_SB.SMIC], AE_ALREADY_EXISTS
4.20.0-042000rc4-generic ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804577/+attachment/5216919/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 1801305] Re: Restore request-based mode to xen-blkfront for AWS kernels
I've checked that the proposed Xenial AWS kernel works - it boots successfully and uses the deadline scheduler by default on a t2.micro instance. Regards, Daniel -- 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/1801305 Title: Restore request-based mode to xen-blkfront for AWS kernels Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Triaged Bug description: In current Ubuntu kernels, PV blkfront drivers have blk-mq enabled by default and cannot use the old I/O scheduler. [Impact] blk-mq is not as fast as the old request-based scheduler for some workloads on HDD disks. [Fix] Amazon Linux has a commit which reintroduces the request-based mode. It disables blk-mq by default but allows it to be switched back on with a kernel parameter. For X this needs a small patch from upstream for error handling. For B/C this patchset is bigger as it includes the suspend/resume patches already in X, and a new fixup. These are desirable as the request mode patch assumes their presence. [Regression Potential] Could potentially break xen based disks on AWS. For B/C, the patches also add some code to the xen core around suspend and resume, this code is much smaller and also mirrors code already in Xenial. [Tests] Tested by AWS for Xenial, and their kernel engineers vetted the patches. I tested the Bionic and Cosmic patchsets with fio, the system appears stable and the IOPS promised for EBS Provisioned IOPS disks were met in my testing. I did an apt update/upgrade and everything worked (no hash-sum mismatches). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801305/+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
Just install mainline kernel v4.20-rc4, here is the warnings during the installation. Processing triggers for linux-image-unsigned-4.20.0-042000rc4-generic (4.20.0-042000rc4.201811252331) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.20.0-042000rc4-generic cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries nor crypto modules. If that's on purpose, you may want to uninstall the 'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs integration and avoid this warning. W: Possible missing firmware /lib/firmware/amdgpu/raven2_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_uvd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_uvd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_vce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_vce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_dmcu.bin for module amdgpu /etc/kernel/postinst.d/zz-update-grub: Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.20.0-042000rc4-generic Found initrd image: /boot/initrd.img-4.20.0-042000rc4-generic Found linux image: /boot/vmlinuz-4.18.0-11-generic Found initrd image: /boot/initrd.img-4.18.0-11-generic Found linux image: /boot/vmlinuz-4.18.0-10-generic Found initrd image: /boot/initrd.img-4.18.0-10-generic Found Windows Boot Manager on /dev
[Kernel-packages] [Bug 1804589] Re: AMD-Vi write error
dmesg info with kernel 4.20.0-042000rc4-generic ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589/+attachment/5216918/+files/dmesg.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804589 Title: AMD-Vi write error Status in linux package in Ubuntu: Confirmed 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 1804589] Re: AMD-Vi write error
Just install mainline kernel v4.20-rc4, here is the warnings during the installation. Processing triggers for linux-image-unsigned-4.20.0-042000rc4-generic (4.20.0-042000rc4.201811252331) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.20.0-042000rc4-generic cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries nor crypto modules. If that's on purpose, you may want to uninstall the 'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs integration and avoid this warning. W: Possible missing firmware /lib/firmware/amdgpu/raven2_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_uvd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_uvd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_vce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_vce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven2_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/picasso_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega12_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_dmcu.bin for module amdgpu /etc/kernel/postinst.d/zz-update-grub: Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.20.0-042000rc4-generic Found initrd image: /boot/initrd.img-4.20.0-042000rc4-generic Found linux image: /boot/vmlinuz-4.18.0-11-generic Found initrd image: /boot/initrd.img-4.18.0-11-generic Found linux image: /boot/vmlinuz-4.18.0-10-generic Found initrd image: /boot/initrd.img-4.18.0-10-generic Found Windows Boot Manager on /
[Kernel-packages] [Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
The attachment "cosmic_hwdata_0.290-1ubuntu1.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- 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: Incomplete Status in unity-settings-daemon package in Ubuntu: Fix Released Status in unity-settings-daemon source package in Xenial: Fix Committed Status in unity-settings-daemon source package in Bionic: Fix Released Status in unity-settings-daemon source package in Cosmic: Fix Released 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 1787904] Re: [radeon] machine crash after GPU reset
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787904 Title: [radeon] machine crash after GPU reset Status in linux package in Ubuntu: Expired Bug description: I showed up to work today (after being away for a couple of weeks) and my machine had crashed. I'm not sure why it happened this morning at 7am. My only guess is that a janitor came in and touched the mouse which woke the screen up after a couple of weeks of sleep. (I have been using the machine remotely for computations, which had finished yesterday, but the building was closed so I'm guessing this is the first time the screen has come on in a while). The first unusual entries in my kern.log are: Aug 20 07:02:43 winters kernel: [2218007.668454] radeon :03:00.0: ring 0 stalled for more than 10248msec Aug 20 07:02:43 winters kernel: [2218007.668465] radeon :03:00.0: GPU lockup (current fence id 0x000799d4 last fence id 0x000799d6 on ring 0) They are plentiful, and are mixed with other messages (see attached log file) such as: Aug 20 07:03:00 winters kernel: [2218025.438173] radeon :03:00.0: failed VCE resume (-110). Aug 20 07:03:01 winters kernel: [2218025.721068] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x850C)=0xCAFEDEAD) Aug 20 07:03:01 winters kernel: [2218025.721085] [drm:si_resume [radeon]] *ERROR* si startup failed on resume Aug 20 07:03:01 winters kernel: [2218025.722887] WARNING: CPU: 18 PID: 3715 at /build/linux-60XibS/linux-4.15.0/drivers/gpu/drm/radeon/radeon_object.c:84 radeon_ttm_bo_destroy+0xfb/0x100 [radeon] . . . Aug 20 07:03:38 winters kernel: [2218062.876285] [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting Aug 20 07:03:38 winters kernel: [2218062.876298] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing BBC8 (len 237, WS 0, PS 4) @ 0xBBD6 Aug 20 07:03:38 winters kernel: [2218062.876309] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing B3EE (len 78, WS 12, PS 8) @ 0xB427 The last message before death appears to be: Aug 20 07:10:02 winters kernel: [2218447.006362] radeon :03:00.0: GPU reset succeeded, trying to resume ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-radeon 1:18.0.1-1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 20 10:18:42 2018 DistUpgraded: 2018-05-02 12:54:58,714 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-30-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland GL [FirePro W2100] [1002:6608] (prog-if 00 [VGA controller]) Subsystem: Dell Oland GL [FirePro W2100] [1028:2120] InstallationDate: Installed on 2018-01-05 (226 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. Precision Tower 7810 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=90d43be7-a2f7-4500-8b88-9bd7a549d96d ro quiet splash vt.handoff=1 SourcePackage: xserver-xorg-video-ati UpgradeStatus: Upgraded to bionic on 2018-05-02 (109 days ago) dmi.bios.date: 06/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A27 dmi.board.name: 0KJCC5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA27:bd06/25/2018:svnDellInc.:pnPrecisionTower7810:pvr:rvnDellInc.:rn0KJCC5:rvrA00:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 7810 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nou
[Kernel-packages] [Bug 1793584] Re: i2c_hid module randomly dies and needs to be restarted
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793584 Title: i2c_hid module randomly dies and needs to be restarted Status in linux package in Ubuntu: Expired Bug description: From 4.15.0-24 (not in 4.15.0-23) i2c_hid spams the log with messages like this: [ 6079.727465] i2c_hid i2c-ELAN0630:00: i2c_hid_get_input: incomplete report (14/65535) [ 6079.733692] i2c_hid i2c-ELAN0630:00: i2c_hid_get_input: incomplete report (14/65535) It then randomly stops working (and stops spamming the log), and there is no trackpad response until I reload the module. Again, this was introduced in 4.15.0-24. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793584/+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 1805556] [NEW] package nvidia-utils-390 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-340 340.1
Public bug reported: I'm trying to get 2nd video card to work GT710B Nvidia card. I'm trying everything that I can find on te Internet from Google. Lots of info - just can't seem to get it to work. Sometimes it has worked on other installations that I have done from scratch - just not from my main Ubuntu that I have been upgrading from 14.04, 16.04, 18.04 etc. not including a valid xorg.conf has helped in some situations. When I load the driver from Other Drivers, it loadsa, and ten doesn't sart up until I go into repair mode and delete the nvidia drives completely. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-utils-390 (not installed) ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: libcuda1-340:amd64: Remove nvidia-opencl-icd-340:amd64: Remove libnvidia-compute-390:amd64: Install nvidia-utils-390:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Nov 27 22:49:53 2018 ErrorMessage: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-340 340.107-0ubuntu0.18.04.1 InstallationDate: Installed on 2018-05-18 (193 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-utils-390 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-340 340.107-0ubuntu0.18.04.1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1805556 Title: package nvidia-utils-390 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-340 340.107-0ubuntu0.18.04.1 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: I'm trying to get 2nd video card to work GT710B Nvidia card. I'm trying everything that I can find on te Internet from Google. Lots of info - just can't seem to get it to work. Sometimes it has worked on other installations that I have done from scratch - just not from my main Ubuntu that I have been upgrading from 14.04, 16.04, 18.04 etc. not including a valid xorg.conf has helped in some situations. When I load the driver from Other Drivers, it loadsa, and ten doesn't sart up until I go into repair mode and delete the nvidia drives completely. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-utils-390 (not installed) ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: libcuda1-340:amd64: Remove nvidia-opencl-icd-340:amd64: Remove libnvidia-compute-390:amd64: Install nvidia-utils-390:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Nov 27 22:49:53 2018 ErrorMessage: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-340 340.107-0ubuntu0.18.04.1 InstallationDate: Installed on 2018-05-18 (193 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-utils-390 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-340 340.107-0ubuntu0.18.04.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1805556/+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 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs
v4.13 shows the same search_free stack as 4.14, but doesn't appear to be fatal (it doesn't result in a hung process nor a block device that cannot be wiped. I suspect we've got a new upstream issue since 4.20 didn't fix things. Re-running 4.20 to see if we had a stack trace, we don't NULL pointer oops, but there is a stuck worker queue: [ 242.887966] kworker/0:47D0 2165 2 0x8000 [ 242.888014] Workqueue: events cache_set_flush [bcache] [ 242.888027] Call Trace: [ 242.888084] __schedule+0x2a2/0x880 [ 242.888097] ? __switch_to+0xfc/0x4f0 [ 242.888105] schedule+0x2c/0x80 [ 242.888113] schedule_timeout+0x246/0x350 [ 242.888122] wait_for_completion+0xb7/0x140 [ 242.888141] ? wake_up_q+0x80/0x80 [ 242.888151] kthread_stop+0x49/0x110 [ 242.888176] cache_set_flush+0xdb/0x190 [bcache] [ 242.888186] process_one_work+0x20f/0x410 [ 242.888194] worker_thread+0x34/0x400 [ 242.888202] kthread+0x120/0x140 [ 242.888209] ? process_one_work+0x410/0x410 [ 242.888216] ? kthread_park+0x90/0x90 [ 242.888236] ret_from_fork+0x35/0x40 [ 242.888435] INFO: task bcache_allocato:9015 blocked for more than 120 seconds. [ 242.893786] Not tainted 4.20.0-042000rc3-generic #201811182231 [ 242.896669] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.900428] bcache_allocato D0 9015 2 0x8000 [ 242.900434] Call Trace: [ 242.900448] __schedule+0x2a2/0x880 [ 242.900455] ? __schedule+0x2aa/0x880 [ 242.900462] schedule+0x2c/0x80 [ 242.900480] bch_bucket_alloc+0x19d/0x380 [bcache] [ 242.900503] ? wait_woken+0x80/0x80 [ 242.900519] bch_prio_write+0x190/0x340 [bcache] [ 242.900530] bch_allocator_thread+0x482/0xd10 [bcache] [ 242.900535] kthread+0x120/0x140 [ 242.900546] ? bch_invalidate_one_bucket+0x80/0x80 [bcache] [ 242.900549] ? kthread_park+0x90/0x90 [ 242.900554] ret_from_fork+0x35/0x40 -- 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/1784665 Title: mkfs.ext4 over /dev/bcache0 hangs Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: $ cat /proc/version_signature Ubuntu 4.15.0-29.31-generic 4.15.18 $ lsb_release -rd Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 $ apt-cache policy linux-image-`uname -r` linux-image-4.15.0-29-generic: Installed: 4.15.0-29.31 Candidate: 4.15.0-29.31 Version table: *** 4.15.0-29.31 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 3) mkfs.ext4 /dev/bcache0 returns successful creating an ext4 filesystem on top of a bcache device 4) mkfs.ext4 doesn't return and kernel prints hung process info [ 58.018099] cloud-init[920]: Running command ['mkfs.ext4', '-F', '-L', 'root-fs', '-U', 'f01aec97-9457-11e8-b8d6-525400123401', '/dev/bcache0'] with allowed return codes [0] (capture=True) [ 242.652018] INFO: task kworker/u4:0:5 blocked for more than 120 seconds. [ 242.653767] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.655391] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.657397] INFO: task kworker/0:2:410 blocked for more than 120 seconds. [ 242.659126] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.660980] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.663000] INFO: task bcache_allocato:2326 blocked for more than 120 seconds. [ 242.664807] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.666516] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.668503] INFO: task bcache_writebac:2345 blocked for more than 120 seconds. [ 242.670301] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.671936] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.673909] INFO: task mkfs.ext4:2803 blocked for more than 120 seconds. [ 242.675414] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.677038] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.483998] INFO: task kworker/u4:0:5 blocked for more than 120 seconds. [ 363.488441] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.489598] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.491043] INFO: task kworker/0:2:410 blocked for more than 120 seconds. [ 363.492252] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.494085] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.495659] INFO: task bcache_allocato:2326 blocked for more than 120 seconds. [ 363.496957] Tain
[Kernel-packages] [Bug 1781533] Re: SATA device is not going to DEVSLP
** Description changed: [Impact] Any of the platforms we’ve been seeing SATA problems not going to deepest state leading to other devices not getting there during long idle or s2idle. And it also prevents the system from entering deeper PC state other than PC3. - [Test] - Verified the power consumption on some new platforms, it doesn't do too much difference to the numbers, but it improves. [Fix] - Suggested from Intel and Dell to contains the 2 commits + Suggested from Intel and Dell to contains the following 4 commits, + and all of 4 commits are in v4.19-rc1 https://patchwork.kernel.org/patch/10502285/ https://patchwork.kernel.org/patch/10502287/ + https://patchwork.kernel.org/patch/10535781/ + https://patchwork.kernel.org/patch/10535783/ + + [Test] + Verified the power consumption on some new platforms, it improves the SATA HDD power consumption around 0.5w during long idle. [Regression Potential] - Low, the production machines with suspend-to-idle enabled should have the DEVSLP function been validated. - - [Misc] - Those commits do not show up in any public git tree yet, so let's verify - them in oem kernel first, and then will submit to bionic kernel later. + Low, the DEVSLP function is already validated when shipped with SLP_S0 + support. ** Description changed: [Impact] - Any of the platforms we’ve been seeing SATA problems not going to deepest state leading to other devices not getting there during long idle or s2idle. And it also prevents the system from entering deeper PC state other than PC3. - + Any of the platforms we’ve been seeing SATA problems not going to deepest state leads to other devices not getting there during long idle or s2idle. And it also prevents the system from entering deeper PC state other than PC3. [Fix] Suggested from Intel and Dell to contains the following 4 commits, and all of 4 commits are in v4.19-rc1 https://patchwork.kernel.org/patch/10502285/ https://patchwork.kernel.org/patch/10502287/ https://patchwork.kernel.org/patch/10535781/ https://patchwork.kernel.org/patch/10535783/ [Test] Verified the power consumption on some new platforms, it improves the SATA HDD power consumption around 0.5w during long idle. [Regression Potential] - Low, the DEVSLP function is already validated when shipped with SLP_S0 + Low, the DEVSLP function is already validated when shipped with SLP_S0 support. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1781533 Title: SATA device is not going to DEVSLP Status in HWE Next: Triaged Status in OEM Priority Project: Triaged Status in linux-oem package in Ubuntu: Triaged Bug description: [Impact] Any of the platforms we’ve been seeing SATA problems not going to deepest state leads to other devices not getting there during long idle or s2idle. And it also prevents the system from entering deeper PC state other than PC3. [Fix] Suggested from Intel and Dell to contains the following 4 commits, and all of 4 commits are in v4.19-rc1 https://patchwork.kernel.org/patch/10502285/ https://patchwork.kernel.org/patch/10502287/ https://patchwork.kernel.org/patch/10535781/ https://patchwork.kernel.org/patch/10535783/ [Test] Verified the power consumption on some new platforms, it improves the SATA HDD power consumption around 0.5w during long idle. [Regression Potential] Low, the DEVSLP function is already validated when shipped with SLP_S0 support. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1781533/+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 1782177] Re: Screen sometimes jumps to full brightness on resume from suspend
** Changed in: linux Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782177 Title: Screen sometimes jumps to full brightness on resume from suspend Status in Linux: Won't Fix Status in linux package in Ubuntu: Incomplete Bug description: At night, I usually turn my brightness down as far as it will go using the brightness keys. This makes it dim, but visible and not off. When I walk away for a while, the screen goes to sleep, and when I come back and move the mouse, the screen jumps to full brightness, which is very unpleasant at night. Investigating, it seems that the brightness in intel_backlight is getting reset to 4437, but the one in acpi_video0 reads 0. $ for file in brightness max_brightness actual_brightness; > do > for directory in /sys/class/backlight/intel_backlight/ /sys/class/backlight/acpi_video0/ > do > echo $directory$file : $(cat $directory$file) > done > done /sys/class/backlight/intel_backlight/brightness : 4437 /sys/class/backlight/acpi_video0/brightness : 0 /sys/class/backlight/intel_backlight/max_brightness : 4437 /sys/class/backlight/acpi_video0/max_brightness : 15 /sys/class/backlight/intel_backlight/actual_brightness : 4437 /sys/class/backlight/acpi_video0/actual_brightness : 0 After I press the button to increase the brightness one notch, they are back in sync, and then I can turn it back down as well. $ for file in brightness max_brightness actual_brightness; > do >for directory in /sys/class/backlight/intel_backlight/ /sys/class/backlight/acpi_video0/ > do > echo $directory$file : $(cat $directory$file) > done > done /sys/class/backlight/intel_backlight/brightness : 53 /sys/class/backlight/acpi_video0/brightness : 1 /sys/class/backlight/intel_backlight/max_brightness : 4437 /sys/class/backlight/acpi_video0/max_brightness : 15 /sys/class/backlight/intel_backlight/actual_brightness : 53 /sys/class/backlight/acpi_video0/actual_brightness : 1 This is on a fresh install of xubuntu 18.04. Seems like a regression from 16.04, which I ran on the same laptop without this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1782177/+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 1782177]
What's the distinction between acpi_video0 and intel_backlight? It seems like a bug to me that those don't match, even if we decide that for legacy reasons the bugged behavior of triggering max brightness is necessary. -- 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/1782177 Title: Screen sometimes jumps to full brightness on resume from suspend Status in Linux: Won't Fix Status in linux package in Ubuntu: Incomplete Bug description: At night, I usually turn my brightness down as far as it will go using the brightness keys. This makes it dim, but visible and not off. When I walk away for a while, the screen goes to sleep, and when I come back and move the mouse, the screen jumps to full brightness, which is very unpleasant at night. Investigating, it seems that the brightness in intel_backlight is getting reset to 4437, but the one in acpi_video0 reads 0. $ for file in brightness max_brightness actual_brightness; > do > for directory in /sys/class/backlight/intel_backlight/ /sys/class/backlight/acpi_video0/ > do > echo $directory$file : $(cat $directory$file) > done > done /sys/class/backlight/intel_backlight/brightness : 4437 /sys/class/backlight/acpi_video0/brightness : 0 /sys/class/backlight/intel_backlight/max_brightness : 4437 /sys/class/backlight/acpi_video0/max_brightness : 15 /sys/class/backlight/intel_backlight/actual_brightness : 4437 /sys/class/backlight/acpi_video0/actual_brightness : 0 After I press the button to increase the brightness one notch, they are back in sync, and then I can turn it back down as well. $ for file in brightness max_brightness actual_brightness; > do >for directory in /sys/class/backlight/intel_backlight/ /sys/class/backlight/acpi_video0/ > do > echo $directory$file : $(cat $directory$file) > done > done /sys/class/backlight/intel_backlight/brightness : 53 /sys/class/backlight/acpi_video0/brightness : 1 /sys/class/backlight/intel_backlight/max_brightness : 4437 /sys/class/backlight/acpi_video0/max_brightness : 15 /sys/class/backlight/intel_backlight/actual_brightness : 53 /sys/class/backlight/acpi_video0/actual_brightness : 1 This is on a fresh install of xubuntu 18.04. Seems like a regression from 16.04, which I ran on the same laptop without this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1782177/+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 1782177]
Luke, any updates here? If not a kernel bug, I would like to close this bug. -- 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/1782177 Title: Screen sometimes jumps to full brightness on resume from suspend Status in Linux: Won't Fix Status in linux package in Ubuntu: Incomplete Bug description: At night, I usually turn my brightness down as far as it will go using the brightness keys. This makes it dim, but visible and not off. When I walk away for a while, the screen goes to sleep, and when I come back and move the mouse, the screen jumps to full brightness, which is very unpleasant at night. Investigating, it seems that the brightness in intel_backlight is getting reset to 4437, but the one in acpi_video0 reads 0. $ for file in brightness max_brightness actual_brightness; > do > for directory in /sys/class/backlight/intel_backlight/ /sys/class/backlight/acpi_video0/ > do > echo $directory$file : $(cat $directory$file) > done > done /sys/class/backlight/intel_backlight/brightness : 4437 /sys/class/backlight/acpi_video0/brightness : 0 /sys/class/backlight/intel_backlight/max_brightness : 4437 /sys/class/backlight/acpi_video0/max_brightness : 15 /sys/class/backlight/intel_backlight/actual_brightness : 4437 /sys/class/backlight/acpi_video0/actual_brightness : 0 After I press the button to increase the brightness one notch, they are back in sync, and then I can turn it back down as well. $ for file in brightness max_brightness actual_brightness; > do >for directory in /sys/class/backlight/intel_backlight/ /sys/class/backlight/acpi_video0/ > do > echo $directory$file : $(cat $directory$file) > done > done /sys/class/backlight/intel_backlight/brightness : 53 /sys/class/backlight/acpi_video0/brightness : 1 /sys/class/backlight/intel_backlight/max_brightness : 4437 /sys/class/backlight/acpi_video0/max_brightness : 15 /sys/class/backlight/intel_backlight/actual_brightness : 53 /sys/class/backlight/acpi_video0/actual_brightness : 1 This is on a fresh install of xubuntu 18.04. Seems like a regression from 16.04, which I ran on the same laptop without this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1782177/+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 1782177]
I agree that it was probably a userspace change. -- 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/1782177 Title: Screen sometimes jumps to full brightness on resume from suspend Status in Linux: Won't Fix Status in linux package in Ubuntu: Incomplete Bug description: At night, I usually turn my brightness down as far as it will go using the brightness keys. This makes it dim, but visible and not off. When I walk away for a while, the screen goes to sleep, and when I come back and move the mouse, the screen jumps to full brightness, which is very unpleasant at night. Investigating, it seems that the brightness in intel_backlight is getting reset to 4437, but the one in acpi_video0 reads 0. $ for file in brightness max_brightness actual_brightness; > do > for directory in /sys/class/backlight/intel_backlight/ /sys/class/backlight/acpi_video0/ > do > echo $directory$file : $(cat $directory$file) > done > done /sys/class/backlight/intel_backlight/brightness : 4437 /sys/class/backlight/acpi_video0/brightness : 0 /sys/class/backlight/intel_backlight/max_brightness : 4437 /sys/class/backlight/acpi_video0/max_brightness : 15 /sys/class/backlight/intel_backlight/actual_brightness : 4437 /sys/class/backlight/acpi_video0/actual_brightness : 0 After I press the button to increase the brightness one notch, they are back in sync, and then I can turn it back down as well. $ for file in brightness max_brightness actual_brightness; > do >for directory in /sys/class/backlight/intel_backlight/ /sys/class/backlight/acpi_video0/ > do > echo $directory$file : $(cat $directory$file) > done > done /sys/class/backlight/intel_backlight/brightness : 53 /sys/class/backlight/acpi_video0/brightness : 1 /sys/class/backlight/intel_backlight/max_brightness : 4437 /sys/class/backlight/acpi_video0/max_brightness : 15 /sys/class/backlight/intel_backlight/actual_brightness : 53 /sys/class/backlight/acpi_video0/actual_brightness : 1 This is on a fresh install of xubuntu 18.04. Seems like a regression from 16.04, which I ran on the same laptop without this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1782177/+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 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
I was rather shouty above, for which I apologise, but it is hard to remain calm when things such as the following happen. I tried up update the trackpad firmware, hoping this would help with the S3 sleep / touchpad problem. I had use a Window pre-boot environment to do to that. The new trackpad firmware would not install previously because of a bug. A BIOS update was meant to allow it to install. It will should not install - but then I remembered I have the trackpoint disabled in BIOS. (The firmware updater did not mention this.) I enabled the trackpoint in the BIOS. The firmware updater seemed to flash alright - but then re-flashed, twice, taking ages each time, giving no message, and making me think my machine was in an infinite loop and that aborting - if I could; the trackpad and touchpoint were not working - would cause serious problems. Eventually the flasher gave an error message and aborted. Possibly the problem was that the flasher needs a Synaptics driver installed and a reboot; in the pre-boot environment I could install that driver but after the reboot it seemed that the driver was no longer install. What a total nightmare. -- 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 Foundat
[Kernel-packages] [Bug 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs
I also tested v4.15-rc5, which failed with the same stack trace. Then I returned to 4.14 mainline, and got this one: [ 953.659489] BUG: unable to handle kernel NULL pointer dereference at 0d40 [ 953.668707] IP: search_free+0x31/0x40 [bcache] [ 953.674872] PGD 0 P4D 0 [ 953.677680] Oops: [#34] SMP [ 953.678796] Modules linked in: nls_utf8 isofs nls_iso8859_1 ppdev kvm_intel kvm irqbypass parport_pc joydev input_leds parport serio_raw mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi virtio_rng ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear bcache psmouse virtio_scsi virtio_blk virtio_net i2c_piix4 floppy pata_acpi [ 953.700549] CPU: 1 PID: 3132 Comm: kworker/1:229 Tainted: G D 4.14.0-041400-generic #201711122031 [ 953.704522] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014 [ 953.707128] Workqueue: bcache bch_data_insert_keys [bcache] [ 953.708986] task: 985fe605 task.stack: c01402c4c000 [ 953.711147] RIP: 0010:search_free+0x31/0x40 [bcache] [ 953.712997] RSP: 0018:c01402c4fdf8 EFLAGS: 00010282 [ 953.714287] RAX: RBX: 985ffb385e78 RCX: e83580d58e00 [ 953.716883] RDX: 0007 RSI: 0001f540 RDI: 985ffb385e78 [ 953.718731] RBP: c01402c4fe00 R08: 985ff8121800 R09: 0001801f [ 953.720269] R10: c01402c4fd70 R11: 0001 R12: 985fe3670010 [ 953.721583] R13: 985ffb386000 R14: 985fffc9bb40 R15: 985ff83eab40 [ 953.723315] FS: () GS:985fffc8() knlGS: [ 953.725738] CS: 0010 DS: ES: CR0: 80050033 [ 953.727401] CR2: 0d40 CR3: 28c09000 CR4: 06e0 [ 953.729737] Call Trace: [ 953.730687] cached_dev_cache_miss_done+0x38/0x80 [bcache] [ 953.732939] closure_put+0x8b/0xc0 [bcache] [ 953.734647] closure_sub+0x6f/0xc0 [bcache] [ 953.736104] bch_data_insert_keys+0xd8/0x130 [bcache] [ 953.737311] process_one_work+0x1e7/0x410 [ 953.738233] worker_thread+0x32/0x410 [ 953.739246] kthread+0x125/0x140 [ 953.740231] ? process_one_work+0x410/0x410 [ 953.741407] ? kthread_create_on_node+0x70/0x70 [ 953.742631] ret_from_fork+0x25/0x30 [ 953.743431] Code: 48 89 e5 53 48 89 fb e8 0e ff ff ff 48 8b bb 68 01 00 00 48 85 ff 74 05 e8 cd f7 2d e7 48 8b 83 e8 00 00 00 48 89 df 48 8b 40 70 <48> 8b b0 40 0d 00 00 e8 33 51 07 e7 5b 5d c3 0f 1f 44 00 00 55 [ 953.747654] RIP: search_free+0x31/0x40 [bcache] RSP: c01402c4fdf8 [ 953.749962] CR2: 0d40 [ 953.751475] ---[ end trace c40c3beab1ff3af1 ]--- Retesting 4.13 mainline as well. -- 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/1784665 Title: mkfs.ext4 over /dev/bcache0 hangs Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: $ cat /proc/version_signature Ubuntu 4.15.0-29.31-generic 4.15.18 $ lsb_release -rd Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 $ apt-cache policy linux-image-`uname -r` linux-image-4.15.0-29-generic: Installed: 4.15.0-29.31 Candidate: 4.15.0-29.31 Version table: *** 4.15.0-29.31 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 3) mkfs.ext4 /dev/bcache0 returns successful creating an ext4 filesystem on top of a bcache device 4) mkfs.ext4 doesn't return and kernel prints hung process info [ 58.018099] cloud-init[920]: Running command ['mkfs.ext4', '-F', '-L', 'root-fs', '-U', 'f01aec97-9457-11e8-b8d6-525400123401', '/dev/bcache0'] with allowed return codes [0] (capture=True) [ 242
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
If fresh install used SynPS/2 touchpad, it should be that kmod add i2c_i801 in blacklist. In a newer kmod version, i2c_i801 is removed from blacklist. You can check /etc/modprobe.d/blacklist.conf. Please add i2c_i801 in this blacklist. and update-initramfs -u -k . "lsmod |grep i2c" to check if i2c_i801 is loaded. either blacklist i2c_i801 or "psmouse.synaptics_intertouch=0" will enforce PS/2 mode. -- 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 dm
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
Booting with "psmouse.synaptics_intertouch=0" will enforce PS/2 mode. Please try. If you have issues, please upload dmesg. -- 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.type: 10 dmi.chassis.vendor: LENOV
[Kernel-packages] [Bug 1805527] 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 1805527 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/1805527 Title: [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted (as of a few weeks ago) Status in linux package in Ubuntu: Incomplete Bug description: I use audio via DisplayPort. Until a few weeks ago, I got good quality audio. Now, I get really bad 8-bit-ish distorted audio. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mikel 2276 F pulseaudio /dev/snd/pcmC1D3p: mikel 2276 F...m pulseaudio /dev/snd/controlC1: mikel 2276 F pulseaudio CurrentDesktop: XFCE Date: Tue Nov 27 17:18:56 2018 InstallationDate: Installed on 2015-10-05 (1149 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed Symptom_Card: Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] - HDA ATI HDMI Symptom_Jack: Digital Out, HDMI Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd10/21/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805527/+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 1585434] Re: ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]
I have been having this problem for a VERY LONG TIME! I have had this problem with kernel 4.17.*, 4.18.*, 4.19.* possibly 4.16.* This has been an issue with 18.04 and 18.10 probably 17.10 also lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.10 Release:18.10 Codename: cosmic [74451.298932] ecryptfs_encrypt_page: Error attempting to write lower page; rc = [-28] [74451.298942] ecryptfs_write: Error encrypting page; rc = [-28] [74451.298946] ecryptfs_write_begin: Error on attempt to truncate to (higher) offset [3179048960]; rc = [-28] [74454.709932] ecryptfs_write_metadata_to_contents: Error attempting to write header information to lower file; rc = [-28] [74454.709941] ecryptfs_write_metadata: Error writing metadata out to lower file; rc = [-28] [74455.186859] ecryptfs_write_metadata_to_contents: Error attempting to write header information to lower file; rc = [-28] [74455.186866] ecryptfs_write_metadata: Error writing metadata out to lower file; rc = [-28] [74455.187222] ecryptfs_write_metadata_to_contents: Error attempting to write header information to lower file; rc = [-28] [74455.187225] ecryptfs_write_metadata: Error writing metadata out to lower file; rc = [-28] [74455.187400] ecryptfs_encrypt_page: Error attempting to write lower page; rc = [-28] [74455.187404] ecryptfs_write_end: Error encrypting page (upper index [0x0001]) [74455.187450] ecryptfs_encrypt_page: Error attempting to write lower page; rc = [-28] [74455.187453] ecryptfs_write_end: Error encrypting page (upper index [0x0001]) [74455.189048] ecryptfs_write_metadata_to_contents: Error attempting to write header information to lower file; rc = [-28] [74455.189056] ecryptfs_write_metadata: Error writing metadata out to lower file; rc = [-28] [74455.213908] ecryptfs_write_metadata_to_contents: Error attempting to write header information to lower file; rc = [-28] [74455.213917] ecryptfs_write_metadata: Error writing metadata out to lower file; rc = [-28] [74455.214185] ecryptfs_encrypt_page: Error attempting to write lower page; rc = [-28] [74455.214189] ecryptfs_write_end: Error encrypting page (upper index [0x0001]) [74455.214243] ecryptfs_encrypt_page: Error attempting to write lower page; rc = [-28] [74455.214246] ecryptfs_write_end: Error encrypting page (upper index [0x0001]) [74455.214505] ecryptfs_write_metadata_to_contents: Error attempting to write header information to lower file; rc = [-28] [74455.214509] ecryptfs_write_metadata: Error writing metadata out to lower file; rc = [-28] [74455.215231] ecryptfs_write_metadata_to_contents: Error attempting to write header information to lower file; rc = [-28] [74455.215239] ecryptfs_write_metadata: Error writing metadata out to lower file; rc = [-28] [74455.218017] ecryptfs_write_metadata_to_contents: Error attempting to write header information to lower file; rc = [-28] [74455.218025] ecryptfs_write_metadata: Error writing metadata out to lower file; rc = [-28] [74455.291740] ecryptfs_write_metadata_to_contents: Error attempting to write header information to lower file; rc = [-28] [74455.291748] ecryptfs_write_metadata: Error writing metadata out to lower file; rc = [-28] [74455.292049] ecryptfs_encrypt_page: Error attempting to write lower page; rc = [-28] [74455.292054] ecryptfs_write_end: Error encrypting page (upper index [0x0001]) [74455.292101] ecryptfs_encrypt_page: Error attempting to write lower page; rc = [-28] [74455.292105] ecryptfs_write_end: Error encrypting page (upper index [0x0001]) [74455.370910] ecryptfs_write_metadata_to_contents: Error attempting to write header information to lower file; rc = [-28] [74455.370919] ecryptfs_write_metadata: Error writing metadata out to lower file; rc = [-28] [74455.417671] ecryptfs_encrypt_page: Error attempting to write lower page; rc = [-28] [74455.417682] ecryptfs_write_end: Error encrypting page (upper index [0x0001]) [74455.417758] ecryptfs_encrypt_page: Error attempting to write lower page; rc = [-28] [74455.417764] ecryptfs_write_end: Error encrypting page (upper index [0x0001]) [74455.480691] ecryptfs_write_metadata_to_contents: Error attempting to write header information to lower file; rc = [-28] [74455.480699] ecryptfs_write_metadata: Error writing metadata out to lower file; rc = [-28] [74455.581288] ecryptfs_encrypt_page: Error attempting to write lower page; rc = [-28] [74455.581296] ecryptfs_write_end: Error encrypting page (upper index [0x]) [74455.636272] ecryptfs_encrypt_page: Error attempting to write lower page; rc = [-28] [74455.636281] ecryptfs_write_end: Error encrypting page (upper index [0x]) [74459.146536] ecryptfs_write_metadata_to_contents: Error attempting to write header information to lower file; rc = [-28] [74459.146546] ecryptfs_write_metadata: Error writing metadata o
[Kernel-packages] [Bug 1805527] Re: [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted
alsa-driver hasn't changed in over a year, and pulseaudio hasn't changed since June. So it doesn't sound like a regression in either of those. Maybe a kernel regression? ** Summary changed: - [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted + [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted (as of a few weeks ago) ** Package changed: alsa-driver (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/1805527 Title: [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted (as of a few weeks ago) Status in linux package in Ubuntu: New Bug description: I use audio via DisplayPort. Until a few weeks ago, I got good quality audio. Now, I get really bad 8-bit-ish distorted audio. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mikel 2276 F pulseaudio /dev/snd/pcmC1D3p: mikel 2276 F...m pulseaudio /dev/snd/controlC1: mikel 2276 F pulseaudio CurrentDesktop: XFCE Date: Tue Nov 27 17:18:56 2018 InstallationDate: Installed on 2015-10-05 (1149 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed Symptom_Card: Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] - HDA ATI HDMI Symptom_Jack: Digital Out, HDMI Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd10/21/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805527/+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 1805527] [NEW] [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted (as of a few weeks ago)
You have been subscribed to a public bug: I use audio via DisplayPort. Until a few weeks ago, I got good quality audio. Now, I get really bad 8-bit-ish distorted audio. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mikel 2276 F pulseaudio /dev/snd/pcmC1D3p: mikel 2276 F...m pulseaudio /dev/snd/controlC1: mikel 2276 F pulseaudio CurrentDesktop: XFCE Date: Tue Nov 27 17:18:56 2018 InstallationDate: Installed on 2015-10-05 (1149 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed Symptom_Card: Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] - HDA ATI HDMI Symptom_Jack: Digital Out, HDMI Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd10/21/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted (as of a few weeks ago) https://bugs.launchpad.net/bugs/1805527 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 1797625] Re: Missing the 'Call Trace' with the cases of 'KernelOops'
This actually looks like an issue with kerneloops which parses dmesg for Call Trace. ** Also affects: kerneloops (Ubuntu) Importance: Undecided Status: New ** Changed in: kerneloops (Ubuntu) Importance: Undecided => High ** Changed in: kerneloops (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kerneloops in Ubuntu. https://bugs.launchpad.net/bugs/1797625 Title: Missing the 'Call Trace' with the cases of 'KernelOops' Status in apport package in Ubuntu: New Status in kerneloops package in Ubuntu: Triaged Bug description: Hello, I am working with these two reports: * watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] https://bugs.launchpad.net/bugs/1796385 * watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] https://bugs.launchpad.net/bugs/1797538 And the file: 'OopsText.txt' does not appear in the 'Call Trace'. Others: https://bugzilla.kernel.org/show_bug.cgi?id=201379#c3 "The bug in lauchpad, unless I am missing something, provides not a single actionable traceback. I don't think it is even possible to identify where exactly the CPU hangs unless additional information is provided. There is no traceback in dmesg, and OopsText doesn't include it either. Given that, it is not possible to identify the responsible subsystem, much less to fix the underlying problem. The only thing we can say for sure is that it is _not_ a watchdog driver problem." Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu11 Uname: Linux 4.18.13-gnu x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 12 16:12:58 2018 InstallationDate: Installed on 2017-10-13 (364 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1797625/+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
I see an hwdata upload for Xenial but I don't see the change to GSM / Goldstar Company as having been done in Disco. Is there a reason it hasn't been updated there too? ** Changed in: hwdata (Ubuntu) Status: Fix Released => Incomplete -- 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: Incomplete Status in unity-settings-daemon package in Ubuntu: Fix Released Status in unity-settings-daemon source package in Xenial: Fix Committed Status in unity-settings-daemon source package in Bionic: Fix Released Status in unity-settings-daemon source package in Cosmic: Fix Released 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 1793458] Re: Overlayfs in user namespace leaks directory content of inaccessible directories
I've verified the fix in 4.18.0-12.13-generic from cosmic-proposed. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-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/1793458 Title: Overlayfs in user namespace leaks directory content of inaccessible directories Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: In Progress Bug description: Summary: With a combination of overlayfs and user namespaces, regular users can see the content of directories that would otherwise be inaccessible to them because of directory permissions (e.g., all users can see content of "/root"). Details: For the exploit it is necessary to create user and mount namespaces and mount an overlayfs inside it. Ubuntu allows this for regular users. The lower dir of the overlay would be "/", and the upper dir an attacker-controlled temporary directory. If the attacker wants to see the content of "/root", they would create a directory "root" in the upper dir of the overlay. Overlays seems to get confused about the permissions, and instead of applying the restrictive permissions of "root" from the lower dir, it applies more relaxed restrictions of "root" from the upper dir, granting the attacker the possibility to list the directory contents of "/root". To reproduce, simply run the attached script as regular user. It will show the content of "/root", on my system the output is this: ``` /bin/ls: cannot access '/root/.cache': Permission denied /bin/ls: cannot access '/root/.bashrc': Permission denied /bin/ls: cannot access '/root/snap': Permission denied /bin/ls: cannot access '/root/.gnupg': Permission denied /bin/ls: cannot access '/root/.aptitude': Permission denied /bin/ls: cannot access '/root/.bash_history': Permission denied /bin/ls: cannot access '/root/.profile': Permission denied /bin/ls: cannot access '/root/.hplip': Permission denied total 8 drwxr-xr-x 1 nobody nogroup 4096 Sep 20 09:02 . drwxr-xr-x 1 nobody nogroup 4096 Sep 20 09:02 .. d? ? ? ? ?? .aptitude -? ? ? ? ?? .bash_history -? ? ? ? ?? .bashrc d? ? ? ? ?? .cache d? ? ? ? ?? .gnupg d? ? ? ? ?? .hplip -? ? ? ? ?? .profile d? ? ? ? ?? snap ``` The script also has some comments that explain the necessary steps in more details. I tested on Ubuntu 18.04 with Linux 4.15.0-34-generic, but the bug probably affects all Ubuntu versions of the last years. Other distributions and the vanilla kernel should not be affected because AFAIK only Ubuntu allows mounting of overlayfs inside user namespaces. But of course it would be good to apply a potential fix upstream. So far I did not succeed in doing more than leaking the directory content, but of course that is no guarantee that it is not possible to do worse things. 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/controlC1: wendler3414 F pulseaudio /dev/snd/controlC0: wendler3414 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Sep 20 08:56:01 2018 HibernationDevice: RESUME=UUID=f9d1a1f9-50d2-4b7c-b7e4-66dc78d38062 InstallationDate: Installed on 2016-12-12 (646 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20FXS1B700 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash resume=/dev/mapper/ubuntu--vg-swap_1 swapaccount=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-09-04 (15 days ago) dmi.bios.date: 09/26/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET71W (2.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FXS1B700 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET71W(2.11):bd09/26/2016:svnLENOVO:pn20FXS1B700:pvrThinkP
[Kernel-packages] [Bug 1786139] Re: [GLK/CLX] Enhanced IBRS
I've verified the [Test Case] for older processors that do not support Enhanced IBRS. I've asked Intel if they'd be able to verify the this fix on the latest processors that support Enhanced IBRS but I don't feel like that should be a blocker. ** Tags removed: verification-needed-bionic verification-needed-cosmic verification-needed-xenial ** Tags added: verification-done-bionic verification-done-cosmic verification-done-xenial ** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Disco) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786139 Title: [GLK/CLX] Enhanced IBRS Status in intel: Triaged Status in linux package in Ubuntu: Fix Committed Status in linux source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: Description: [Impact] Future Intel CPU's like Cascade Lake and GLK+ support Enhanced IBRS. Enhanced IBRS is a H/W mitigation technique for Spectre V2 bug. So, it's important for us to make sure that all the OSV's are using this feature. The patch that enables kernel support for this feature has been taken by Thomas and it's in TIP tree. So, please back port it to all the OSV's. Please find the patch here: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=x86/pti&id=706d51681d636a0c4a5ef53395ec3b803e45ed4d [Test Case] For processors that don't support Enhanced IBRS, the test is to ensure that /sys/devices/system/cpu/vulnerabilities/spectre_v2 doesn't change state after applying the patches. This will typically be the string when running on Intel processors that don't support Enhanced IBRS: "Mitigation: Full generic retpoline, IBPB, IBRS_FW" New Intel processors that do support Enhanced IBRS will display "Enhanced IBRS" in place of "Full generic retpoline" [Regression Potential] Pretty low. The patches are fairly simple and they should only affect new processors. The main concern is around the possibility of regressing IBRS support on processors that don't support Enhanced IBRS Target Kernel:TBD Target Release: 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1786139/+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 1787405] Re: [FEAT] Guest-dedicated Crypto Adapters
This bug was fixed in the package qemu - 1:2.12+dfsg-3ubuntu9 --- qemu (1:2.12+dfsg-3ubuntu9) disco; urgency=medium [ Marc Deslauriers ] * SECURITY UPDATE: integer overflow in NE2000 NIC emulation - debian/patches/CVE-2018-10839.patch: use proper type in hw/net/ne2000.c. - CVE-2018-10839 * SECURITY UPDATE: integer overflow via crafted QMP command - debian/patches/CVE-2018-12617.patch: check bytes count read by guest-file-read in qga/commands-posix.c. - CVE-2018-12617 * SECURITY UPDATE: OOB heap buffer r/w access in NVM Express Controller - debian/patches/CVE-2018-16847.patch: check size in hw/block/nvme.c. - CVE-2018-16847 * SECURITY UPDATE: buffer overflow in rtl8139 - debian/patches/CVE-2018-17958.patch: use proper type in hw/net/rtl8139.c. - CVE-2018-17958 * SECURITY UPDATE: buffer overflow in pcnet - debian/patches/CVE-2018-17962.patch: use proper type in hw/net/pcnet.c. - CVE-2018-17962 * SECURITY UPDATE: DoS via large packet sizes - debian/patches/CVE-2018-17963.patch: check size in net/net.c. - CVE-2018-17963 * SECURITY UPDATE: DoS in lsi53c895a - debian/patches/CVE-2018-18849.patch: check message length value is valid in hw/scsi/lsi53c895a.c. - CVE-2018-18849 * SECURITY UPDATE: Out-of-bounds r/w stack access in ppc64 - debian/patches/CVE-2018-18954.patch: check size before data buffer access in hw/ppc/pnv_lpc.c. - CVE-2018-18954 * SECURITY UPDATE: race condition in 9p - debian/patches/CVE-2018-19364-1.patch: use write lock in hw/9pfs/cofile.c. - debian/patches/CVE-2018-19364-2.patch: use write lock in hw/9pfs/9p.c. - CVE-2018-19364 [ Christian Ehrhardt] * debian/patches/ubuntu/lp1787405-*: Support guest dedicated Crypto Adapters on s390x (LP: #1787405) * enable opengl for vfio-MDEV support (LP: #1804766) - d/control-in: set --enable-opengl - d/control-in: add gl related build-dependencies -- Christian Ehrhardt Wed, 21 Nov 2018 13:17:01 -0500 ** Changed in: qemu (Ubuntu) Status: In Progress => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-10839 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-12617 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-16847 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-17958 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-17962 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-17963 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-18849 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-18954 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-19364 -- 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/1787405 Title: [FEAT] Guest-dedicated Crypto Adapters Status in Ubuntu on IBM z Systems: In Progress Status in libvirt package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Bionic: Triaged Status in linux source package in Bionic: Fix Committed Status in qemu source package in Bionic: Triaged Status in libvirt source package in Cosmic: Triaged Status in linux source package in Cosmic: Fix Committed Status in qemu source package in Cosmic: Triaged Status in linux source package in Disco: Fix Committed Bug description: [Impact] * The ability to pass through more cryptographic capabilities is a very important feature for users of s390x as virtualization platform. Its availability upstream now and its backport in this bug allows to exploit the crypto cards as new HW for these virtualization use cases. * This falls under both "other safe cases" SRU exceptions: - For Long Term Support releases we regularly want to enable new hardware ... - For Long Term Support releases we sometimes want to introduce new features. They must not change the behaviour on existing installations ... * This bug has three main components: - kernel (ability to do all of this) - qemu (add feature to exploit the new code) - libvirt (make the feature user consumable) [Test Case] * In general this consists of a few steps - get the updated kernel/qemu/libvirt - mask the card & domains from the usual driver - load vfio-ap - assign card&domain to vfio-ap - prepare a guest - configure a guest to use the card * See comment #66 how to do all of that in detail https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787405/comments/66 [Regression Potential] * The changes are mostly s390x only and adding a new feature so regressions to existing components should be low. But to backport
[Kernel-packages] [Bug 1784501] Re: libvirtd is unable to configure bridge devices inside of LXD containers
I've verified [Test Case] using 4.15.0-42.45-generic. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784501 Title: libvirtd is unable to configure bridge devices inside of LXD containers Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: [Impact] libvirtd cannot properly configure the default bridge device when installed inside of unprivileged LXD containers. 'systemctl status libvirtd' shows the following error: error : virNetDevBridgeSet:140 : Unable to set bridge virbr0 forward_delay: Permission denied This is caused due to the files under /sys/class/net/ being owned by init namespace root rather than container root even when the bridge device is created inside of the container. Here's an example from inside of an unprivileged container: # brctl addbr testbr0 # ls -al /sys/class/net/testbr0/bridge/forward_delay -rw-r--r-- 1 nobody nogroup 4096 Jul 30 22:33 /sys/class/net/testbr0/bridge/forward_delay libvirt cannot open this file for writing even though it created the device. Where safe, files under /sys/class/net/ should be owned by container root. [Test Case] A simple kernel test is to verify that you can write to the /sys/class/net// files as root inside of an unprivileged LXD container. Unpatched kernels will see a Permission denied error: $ lxc exec c1 -- sh -c 'brctl addbr testbr && \ echo 1 > /sys/class/net/testbr/bridge/flush' sh: 1: cannot create /sys/class/net/testbr/bridge/flush: Permission denied The echo command will succeed when using a patched kernel. You can also install libvirt inside of a an unprivileged LXD container, restart the container, and verify that the default bridge (virbr0) is up. Unpatched kernels will not see the virbr0 bridge: $ lxc exec c1 -- sh -c 'brctl show virbr0' bridge name bridge id STP enabled interfaces virbr0 can't get info No such device The brctl command will show a valid device when using a patched kerne: $ lxc exec c1 -- sh -c 'brctl show virbr0' bridge name bridge id STP enabled interfaces virbr0 8000.5254005451e8 yes virbr0-nic [Regression Potential] The biggest concern with these patches is that they could cause a sensitive /sys/class/net/** file to be read from or written to inside of an unprivileged container. I've (tyhicks) audited all on the in- tree objects exposed to unprivileged containers by this patch set and I don't see any concerns. I did find one file (tx_maxrate) that I couldn't make heads or tails of so I added a CAP_NET_ADMIN check against the init namespace so that it couldn't be modified inside of a container. These patches were released in 4.19 and also in the Ubuntu 18.10 release kernel. No issues have been reported in those releases. [Other info] The following upstream patches have been merged into linux-next which fix this bug: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=c59e18b876da3e466abe5fa066aa69050f5be17c https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=d1753390274f7760e5b593cb657ea34f0617e559 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784501/+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 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
Yes manjaro 18.0 -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+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 1805474] Re: linux-azure: 4.15.0-1034.35~14.04.2 -proposed tracker
** Description changed: This bug is for tracking the 4.15.0-1034.35~14.04.2 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1803592 phase: Uploaded phase-changed: Tuesday, 27. November 2018 18:08 UTC reason: - promote-to-proposed: Builds not complete + promote-to-proposed: Another kernel is currently pending in proposed stakeholder-signoff: Waiting for signoff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1805474 Title: linux-azure: 4.15.0-1034.35~14.04.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug is for tracking the 4.15.0-1034.35~14.04.2 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1803592 phase: Uploaded phase-changed: Tuesday, 27. November 2018 18:08 UTC reason: promote-to-proposed: Another kernel is currently pending in proposed stakeholder-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs
It took a while, but v4.15-rc6 fails; so we need to move back a bit. [ 2541.139904] bcache: bcache_device_free() bcache0 stopped [ 2541.141848] BUG: unable to handle kernel NULL pointer dereference at 0d38 [ 2541.143813] IP: search_free+0ex01-b6435-e1/5f0x40 [bcache] [ 2541.145676] PGD 0 P4D 0 [ 2541.146493] Oops: [#58] SMP [ 2541.147509] Modules linked in: bcache nls_utf8 isofs nls_iso8859_1 ppdev kvm_intel kvm irqbypass joydev input_leds parport_pc parport mac_hid serio_raw sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi virtio_rng ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear psmouse virtio_net virtio_scsi virtio_blk i2c_piix4 pata_acpi floppy [ 2541.154248] CPU: 3 PID: 13332 Comm: kworker/3:200 Tainted: G D 4.15.0-041500rc6-generic #201712312330 [ 2541.156921] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014 [ 2541.159381] Workqueue: bcache bch_data_insert_keys [bcache] [ 2541.160566] RIP: 0010:search_free+0x31/0x40 [bcache] [ 2541.161300] RSP: 0018:b04e45b6bdf8 EFLAGS: 00010282 [ 2541.162098] RAX: RBX: 942c22b3b390 RCX: 00018016 [ 2541.163791] RDX: 00018017 RSI: ded4c086a7c0 RDI: 942c22b3b390 [ 2541.165486] RBP: b04e45b6be00 R08: 942c21a9fc00 R09: 00018016 [ 2541.167191] R10: b04e45b6bd70 R11: 942c3ffb4000 R12: 942c39610010 [ 2541.168897] R13: 942c22b3b518 R14: 942c3fda3080 R15: 942c26b526c0 [ 2541.170637] FS: () GS:942c3fd8() knlGS: [ 2541.172574] CS: 0010 DS: ES: CR0: 80050033 [ 2541.174043] CR2: 0d38 CR3: 11409000 CR4: 06e0 [ 2541.175847] Call Trace: [ 2541.176349] cached_dev_cache_miss_done+0x38/0x80 [bcache] [ 2541.177131] closure_put+0x8b/0xc0 [bcache] [ 2541.177791] closure_sub+0x6f/0xc0 [bcache] [ 2541.178924] bch_data_insert_keys+0xd8/0x130 [bcache] [ 2541.180107] process_one_work+0x1ea/0x410 [ 2541.181176] worker_thread+0x32/0x410 [ 2541.182157] kthread+0x11e/0x140 [ 2541.183043] ? process_one_work+0x410/0x410 [ 2541.184154] ? kthread_create_worker_on_cpu+0x70/0x70 [ 2541.185460] ret_from_fork+0x1f/0x30 [ 2541.186397] Code: 48 89 e5 53 48 89 fb e8 0e ff ff ff 48 8b bb 68 01 00 00 48 85 ff 74 05 e8 cd 0b d0 f5 48 8b 83 e8 00 00 00 48 89 df 48 8b 40 70 <48> 8b b0 38 0d 00 00 e8 c3 18 a9 f5 5b 5d c3 0f 1f 44 00 00 55 [ 2541.189920] RIP: search_free+0x31/0x40 [bcache] RSP: b04e45b6bdf8 [ 2541.191636] CR2: 0d38 [ 2541.192503] ---[ end trace e2b7818e7472ac25 ]--- On Mon, Nov 26, 2018 at 8:26 PM Joseph Salisbury wrote: > > Can you confirm that v4.15-rc6 does not exhibit the bug? That will > ensure I'm reviewing the correct commits: > > http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc6/ > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1784665 > > Title: > mkfs.ext4 over /dev/bcache0 hangs > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784665/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784665 Title: mkfs.ext4 over /dev/bcache0 hangs Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: $ cat /proc/version_signature Ubuntu 4.15.0-29.31-generic 4.15.18 $ lsb_release -rd Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 $ apt-cache policy linux-image-`uname -r` linux-image-4.15.0-29-generic: Installed: 4.15.0-29.31 Candidate: 4.15.0-29.31 Version table: *** 4.15.0-29.31 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 3) mkfs.ext4 /dev/bcache0 returns successful creating an ext4 filesystem on top of a bcache device 4) mkfs.ext4 doesn't return and kernel prints hung process info [ 58.018099] cloud-init[920]: Running command ['mkfs.ext4', '-F', '-L', 'root-fs', '-U', 'f01aec97-9457-11e8-b8d6-525400123401', '/dev/bcache0'] with allowed return codes [0] (capture=True) [ 242.652018] INFO: task kworker/u4:0:5 blocked for more than 120 seconds. [ 242.653767] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.655391] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.657397] INFO: task kworker/0:2:410 blocked for more than 120 seconds. [ 242.659126] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.660980] "echo 0 > /proc/sys/ke
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
Also affecting 2nd gen X1 Carbon. -- 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.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET55W(1.30):bd08/31/201
[Kernel-packages] [Bug 1805304] Re: [Hyper-V] Additional patches for Lv2 storage performance
** Changed in: linux-azure (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1805304
Title:
[Hyper-V] Additional patches for Lv2 storage performance
Status in linux-azure package in Ubuntu:
Confirmed
Status in linux-azure source package in Bionic:
Fix Committed
Bug description:
After analysis of the first 4.15 kernel for Lv2 performance, and while
we are delayed getting to 4.18, we have identified and backported the
following patches for the 4.15 linux-azure kernel:
commit 1268ed0c474a5c8f165ef386f3310521b5e00e27
Author: K. Y. Srinivasan
Date: Tue Jul 3 16:01:55 2018 -0700
x86/hyper-v: Fix the circular dependency in IPI enlightenment
linux-next:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181126&id=1268ed0c474a5c8f165ef386f3310521b5e00e27
commit 366f03b0cf90ef55f063d4a54cf62b0ac9b6da9d
Author: K. Y. Srinivasan
Date: Wed May 16 14:53:32 2018 -0700
X86/Hyper-V: Enhanced IPI enlightenment
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181126&id=366f03b0cf90ef55f063d4a54cf62b0ac9b6da9d
commit 68bb7bfb7985df2bd15c2dc975cb68b7a901488a
Author: K. Y. Srinivasan
Date: Wed May 16 14:53:31 2018 -0700
X86/Hyper-V: Enable IPI enlightenments
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181126&id=68bb7bfb7985df2bd15c2dc975cb68b7a901488a
commit 6b48cb5f8347bc0153ff1d7b075db92e6723ffdb
Author: K. Y. Srinivasan
Date: Wed May 16 14:53:30 2018 -0700
X86/Hyper-V: Enlighten APIC access
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181126&id=6b48cb5f8347bc0153ff1d7b075db92e6723ffdb
commit 68d1eb72ee99e26576913aa6824f7a703ca06b90
Author: Vitaly Kuznetsov
Date: Tue Mar 20 15:02:09 2018 +0100
x86/hyper-v: define struct hv_enlightened_vmcs and clean field bits
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181126&id=68d1eb72ee99e26576913aa6824f7a703ca06b90
commit a46d15cc1ae5af905afac2af4cc0c188c2eb59b0
Author: Vitaly Kuznetsov
Date: Tue Mar 20 15:02:08 2018 +0100
x86/hyper-v: allocate and use Virtual Processor Assist Pages
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181126&id=a46d15cc1ae5af905afac2af4cc0c188c2eb59b0
commit 415bd1cd3a42897f61a92cda0a9f9d7b04c28fb7
Author: Vitaly Kuznetsov
Date: Tue Mar 20 15:02:06 2018 +0100
x86/hyper-v: move definitions from TLFS to hyperv-tlfs.h
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181126&id=415bd1cd3a42897f61a92cda0a9f9d7b04c28fb7
commit 5a485803221777013944cbd1a7cd5c62efba3ffa
Author: Vitaly Kuznetsov
Date: Tue Mar 20 15:02:05 2018 +0100
x86/hyper-v: move hyperv.h out of uapi
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181126&id=5a485803221777013944cbd1a7cd5c62efba3ffa
commit e7c4e36c447daca2b7df49024f6bf230871cb155
Author: Vitaly Kuznetsov
Date: Wed Jan 24 14:23:34 2018 +0100
x86/hyperv: Redirect reenlightment notifications on CPU offlining
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181126&id=e7c4e36c447daca2b7df49024f6bf230871cb155
commit 93286261de1b46339aa27cd4c639b21778f6cade
Author: Vitaly Kuznetsov
Date: Wed Jan 24 14:23:33 2018 +0100
x86/hyperv: Reenlightenment notifications support
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181126&id=93286261de1b46339aa27cd4c639b21778f6cade
commit e2768eaa1ca4fbb7b778da5615cce3dd310352e6
Author: Vitaly Kuznetsov
Date: Wed Jan 24 14:23:32 2018 +0100
x86/hyperv: Add a function to read both TSC and TSC page value
simulateneously
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181126&id=e2768eaa1ca4fbb7b778da5615cce3dd310352e6
commit 4a5f3cde4d51c7afce859aed9d74d197751896d5
Author: Michael Kelley
Date: Fri Dec 22 11:19:02 2017 -0700
Drivers: hv: vmbus: Remove x86-isms from arch independent drivers
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/hv?h=next-20181126&id=4a5f3cde4d51c7afce859aed9d74d197751896d5
From: Dexuan Cui
We can concurrently try to open the same sub-channel from 2 paths:
path #1: vmbus_onoffer() -> vmbus_process_offer() -> handle_sc_creation().
path #2: storvsc_probe() -> storvsc_connect_to_vsp() ->
-> storvsc_channel_init() -> handle_multichannel_storage() ->
-> vmbus_are_subchannels_present() -> handle_sc_creation().
They conflict with each other, but it was not an issue before the recent
commit ae6935ed7d42 ("vmbus: spli
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
I think it just got a point update, from 4.15.0-36 to 4.15.0-39. I'll check later what happens if I run the previous version and will let you know here. -- 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.type: 1
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
Was the kernel updated? Trying running an older kernel and see if it might just be a regression in our kernel.. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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.type: 10 dmi.chassis.vendor: LENOVO dmi.cha
[Kernel-packages] [Bug 1802341] Re: crash in ENA driver on removing an interface
** Changed in: linux-aws (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: linux-aws (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux-aws (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Changed in: linux-aws (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1802341 Title: crash in ENA driver on removing an interface Status in linux package in Ubuntu: Fix Committed Status in linux-aws package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux-aws source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux-aws source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux-aws source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux-aws source package in Disco: Fix Committed Bug description: Bug present in ENA since driver version 1.6; manifests as a crash only under some conditions. In ena_remove() we have the following stack call: ena_remove() unregister_netdev() ena_destroy_device() netif_carrier_off() Calling netif_carrier_off() causes linkwatch to try to handle the link change event on the already unregistered netdev, which leads to a read from an unreadable memory address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802341/+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 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
An interesting observation: I've nuked my installation again with a new Ubuntu install (I've also updated the BIOS and brought back factory settings - I just enabled S3, disabled secure boot and turned Thunderbolt support). A fresh install (WITHOUT ANY UPDATES) detects the touchpad as SynPS/2 Touchpad. As long as it stays like this, S3 and resume work fine, without issues. When I do apt update and upgrade, after restart the touchpad is detected as Synaptics Touchpad (so a bit different than before), it starts acting weird again after resume. Does anyone know a way to enforce this PS/2 mode? -- 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-
[Kernel-packages] [Bug 1805414] Re: [Ubuntu] kernel: zcrypt: reinit ap queue state machine
It looks like the following commit is a prereq:
f1b0a4343c418 ("s390/zcrypt: Integrate ap_asm.h into include/asm/ap.h")
This would define ap_zapq, which is used in commit 104f708fd1241b. Can
you confirm this?
--
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/1805414
Title:
[Ubuntu] kernel: zcrypt: reinit ap queue state machine
Status in Ubuntu on IBM z Systems:
Triaged
Status in linux package in Ubuntu:
Triaged
Bug description:
Description: kernel: zcrypt: reinit ap queue state machine
Symptom: Zcrypt ap queue device not operational at host level after a
kvm guest used it.
Problem: The vfio device driver when receiving an ap queue device does
additional resets thereby removing the registration for
interrupts for the ap device done by the ap bus core
code. So when later the vfio driver releases the device and
one of the default zcrypt drivers takes care of the device
the interrupt registration needs to get renewed. The current
code does no renew and result is that requests send into such
a queue will never see a reply processed - the application
hangs.
Solution: This patch adds a function which resets the aq queue state
machine for the ap queue device and triggers the walk through
the initial states (which are reset and registration for
interrupts). This function is now called before the driver's
probe function is invoked.
When the association between driver and device is released,
the driver's remove function is called. The current
implementation calls a ap queue function
ap_queue_remove(). This invokation has been moved to the ap
bus function to make the probe / remove pair for ap bus and
drivers more symmetric.
Reproduction: Set up an kvm guest to use one or more ap queues in
pass-through mode. Start the guest. Stop the guest. Reassign
the ap resources back to the host system. Run an application
which uses exactly this ap resources. Without the fix, the
application hangs; with the fix the application should run
fine.
Upstream commit(s):
104f708fd1241b22f808bdf066ab67dc5a051de5
Available on kernel.org
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1805414/+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
This bug was fixed in the package unity-settings-daemon - 15.04.1+18.04.20180413-0ubuntu3 --- unity-settings-daemon (15.04.1+18.04.20180413-0ubuntu3) cosmic; urgency=medium [ Dariusz Gadomski ] * gnome-settings-daemon/display-name.c: - some vendors record the screen ratio (e.g 16/9) in the EDID instead of including the screen size, detect those cases and display the product name instead of the screen diagonal. (lp: #1755490) -- Sebastien Bacher Tue, 20 Nov 2018 16:07:31 +0100 ** Changed in: unity-settings-daemon (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- 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 Xenial: Fix Committed Status in unity-settings-daemon source package in Bionic: Fix Released Status in unity-settings-daemon source package in Cosmic: Fix Released 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 1802341] Re: crash in ENA driver on removing an interface
** Tags removed: verification-needed-bionic verification-needed-cosmic verification-needed-xenial ** Tags added: verification-done-bionic verification-done-cosmic verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1802341 Title: crash in ENA driver on removing an interface Status in linux package in Ubuntu: Fix Committed Status in linux-aws package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux-aws source package in Xenial: In Progress Status in linux source package in Bionic: Fix Committed Status in linux-aws source package in Bionic: In Progress Status in linux source package in Cosmic: Fix Committed Status in linux-aws source package in Cosmic: In Progress Status in linux source package in Disco: Fix Committed Status in linux-aws source package in Disco: In Progress Bug description: Bug present in ENA since driver version 1.6; manifests as a crash only under some conditions. In ena_remove() we have the following stack call: ena_remove() unregister_netdev() ena_destroy_device() netif_carrier_off() Calling netif_carrier_off() causes linkwatch to try to handle the link change event on the already unregistered netdev, which leads to a read from an unreadable memory address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802341/+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 1798182] Re: Update ENA driver to version 2.0.1K
** Tags removed: verification-needed-bionic verification-needed-cosmic verification-needed-xenial ** Tags added: verification-done-bionic verification-done-cosmic verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798182 Title: Update ENA driver to version 2.0.1K Status in linux package in Ubuntu: In Progress Status in linux-aws package in Ubuntu: Fix Released Status in linux source package in Trusty: Invalid Status in linux-aws source package in Trusty: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux-aws source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-aws source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-aws source package in Cosmic: Fix Released Bug description: The following commits from mainline, linux-next, and net-next: Arthur Kiyanovski (18): net: ena: fix warning in rmmod caused by double iounmap net: ena: fix rare bug when failed restart/resume is followed by driver removal net: ena: fix NULL dereference due to untimely napi initialization net: ena: fix auto casting to boolean net: ena: minor performance improvement net: ena: complete host info to match latest ENA spec net: ena: introduce Low Latency Queues data structures according to ENA spec net: ena: add functions for handling Low Latency Queues in ena_com net: ena: add functions for handling Low Latency Queues in ena_netdev net: ena: use CSUM_CHECKED device indication to report skb's checksum status net: ena: explicit casting and initialization, and clearer error handling net: ena: limit refill Rx threshold to 256 to avoid latency issues net: ena: change rx copybreak default to reduce kernel memory pressure net: ena: remove redundant parameter in ena_com_admin_init() net: ena: update driver version to 2.0.1 net: ena: fix indentations in ena_defs for better readability net: ena: enable Low Latency Queues net: ena: fix compilation error in xtensa architecture Eric Dumazet (1): net: ena: remove ndo_poll_controller Netanel Belgazal (1): net: ena: Fix Kconfig dependency on X86 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798182/+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 1803246] Re: Ubuntu 18.10 is Unable to Suspend When Closing Lenovo E531 Laptop Lid
This issue only occurred after upgrading from 18.04 to 18.10. I installed Ukuu and managed to update my kernel from 4.18.0-11-generic to 4.19.5-041905-generic. To test: - I updated the kernel - Rebooted - Logged in - Closed the lid of the laptop Expected result: - Trackpad should work after the laptop went into suspend mode Actual result: - Trackpad stopped working and the laptop did not go into suspend mode This issue does not occur if I press the power button to suspend the laptop. Thanks for getting back! Much appreciated. What else can I try? -- 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/1803246 Title: Ubuntu 18.10 is Unable to Suspend When Closing Lenovo E531 Laptop Lid Status in linux package in Ubuntu: Incomplete Bug description: The trackpad of my Lenovo E531 Thinkpad Edge works when logged into 18.10. When you close the lid the laptop normally goes into suspend (in 18.04), but fails to suspend in 18.10. The trackpad becomes unresponsive after the lid has been closed and the lid is opened again. See the response from dmesg below. Funny thing: This error does not occur when the power button is pressed and the trackpad is responsive (because a suspend was not attempted via the lid). I am using version: Ubuntu 4.18.0-10.11-generic 4.18.12 According to dmesg: [ 650.163700] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 650.165107] Suspending console(s) (use no_console_suspend to debug) [ 650.165646] rmi4_f03 rmi4-00.fn03: rmi_f03_pt_write: Failed to write to F03 TX register (-6). [ 650.165649] psmouse serio2: Failed to disable mouse on rmi4-00.fn03/serio0 [ 650.165966] rmi4_f03 rmi4-00.fn03: rmi_f03_pt_write: Failed to write to F03 TX register (-6). [ 650.166282] rmi4_f03 rmi4-00.fn03: rmi_f03_pt_write: Failed to write to F03 TX register (-6). [ 650.166814] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6. [ 650.166816] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6. [ 650.166820] rmi4_physical rmi4-00: Failed to suspend functions: -6 I have tried the following: - Update grub - Reinstalled xserver-xorg-input-synaptics - Disabled the trackpad via Gnome - Updated the BIOS to the latest available version This issue has only occured since I upgraded from 18.04 to 18.10. It would be great if 18.10 could suspend when the lid is closed. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anthony5917 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-06-24 (142 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 68853EM NonfreeKernelModules: nvidia_modeset nvidia wl Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=40873332-4c5a-4f82-b0a4-c88bb092b9c6 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 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 Tags: wayland-session cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-11-04 (9 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 06/21/2018 dmi.bios.vendor: LENOVO dmi.bios.version: HEET52WW (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 68853EM dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrHEET52WW(1.33):bd06/21/2018:svnLENOVO:pn68853EM:pvrThinkPadEdgeE531:rvnLENOVO:rn68853EM:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad Edge E531 dmi.product.name: 68853EM dmi.product.sku: LENOVO_MT_6885_BU_Think_FM_ThinkPad Edge E531 dmi.product.version: ThinkPad Edge E531 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803246/+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] Update Released
The verification of the Stable Release Update for unity-settings-daemon has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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 Xenial: Fix Committed Status in unity-settings-daemon source package in Bionic: Fix Released 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 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
This bug was fixed in the package unity-settings-daemon - 15.04.1+18.04.20180413-0ubuntu1.2 --- unity-settings-daemon (15.04.1+18.04.20180413-0ubuntu1.2) bionic; urgency=medium [ Dariusz Gadomski ] * gnome-settings-daemon/display-name.c: - some vendors record the screen ratio (e.g 16/9) in the EDID instead of including the screen size, detect those cases and display the product name instead of the screen diagonal. (lp: #1755490) -- Sebastien Bacher Tue, 20 Nov 2018 16:07:31 +0100 ** Changed in: unity-settings-daemon (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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 Xenial: Fix Committed Status in unity-settings-daemon source package in Bionic: Fix Released 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 1805011] Re: USB E-MU 0202/0404 reset and disconnect
I'm tested sound card Lubuntu 16.04 live usb. Kernel 4.15.0.39. All okey. The problem is not in kernel. Ubuntu 18.04 broken. -- 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/1805011 Title: USB E-MU 0202/0404 reset and disconnect Status in linux package in Ubuntu: Confirmed Bug description: Used ubuntu 18.04. Sound card permanently disabled and freezes. Different laptops were used, the problem has not changed. Used different cable. [ 23.456082] usb 4-1: new full-speed USB device number 2 using uhci_hcd [ 23.620103] usb 4-1: not running at top speed; connect to a high speed hub [ 23.655112] usb 4-1: New USB device found, idVendor=041e, idProduct=3f02 [ 23.655117] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 23.655122] usb 4-1: Product: E-MU 0202 | USB [ 23.655126] usb 4-1: Manufacturer: E-MU Systems, Inc. [ 23.655130] usb 4-1: SerialNumber: E-MU-03-3F02-07DA0C14-0E730-8740T2A [ 24.029429] usb 1-3: USB disconnect, device number 4 [ 62.156059] usb 1-3: new high-speed USB device number 5 using ehci-pci [ 62.314540] usb 1-3: New USB device found, idVendor=041e, idProduct=3f02 [ 62.314544] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 62.314547] usb 1-3: Product: E-MU 0202 | USB [ 62.314550] usb 1-3: Manufacturer: E-MU Systems, Inc. [ 62.314552] usb 1-3: SerialNumber: E-MU-03-3F02-07DA0C14-0E730-8740T2A [ 62.516964] usb 4-1: USB disconnect, device number 2 [ 147.904012] ehci-pci :00:1a.7: port 3 reset error -110 [ 149.068094] usb 4-1: new full-speed USB device number 3 using uhci_hcd [ 149.226189] usb 4-1: not running at top speed; connect to a high speed hub [ 149.260214] usb 4-1: New USB device found, idVendor=041e, idProduct=3f02 [ 149.260219] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 149.260224] usb 4-1: Product: E-MU 0202 | USB [ 149.260228] usb 4-1: Manufacturer: E-MU Systems, Inc. [ 149.260232] usb 4-1: SerialNumber: E-MU-03-3F02-07DA0C14-0E730-8740T2A [ 149.636378] usb 1-3: USB disconnect, device number 5 [ 314.216062] usb 1-3: new high-speed USB device number 6 using ehci-pci [ 314.374729] usb 1-3: New USB device found, idVendor=041e, idProduct=3f02 [ 314.374735] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 314.374739] usb 1-3: Product: E-MU 0202 | USB [ 314.374743] usb 1-3: Manufacturer: E-MU Systems, Inc. [ 314.374747] usb 1-3: SerialNumber: E-MU-03-3F02-07DA0C14-0E730-8740T2A [ 314.576366] usb 4-1: USB disconnect, device number 3 [ 314.580951] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.581159] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.581362] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.581839] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.582271] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.584189] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.584439] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.584626] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.585109] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.585880] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.598231] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.598331] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.598422] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.598731] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.598970] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.599867] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.599960] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.600112] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.600322] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.600540] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.601171] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.601261] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.601353] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.601545] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.601756] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.602345] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.602436] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.602528] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.602716] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.602927] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.603494] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.603584] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.603676] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.603864] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.604211] usb 1-3: 4:0: cannot get min/max values for control 2 (id 4) [ 314.605094] usb 1-3: USB disconnect, device number 6 [ 314.884054] usb 1-3: new high-speed USB devi
[Kernel-packages] [Bug 1803179] Re: System does not reliably come out of suspend
** Also affects: linux Importance: Undecided Status: New ** No longer affects: linux ** Also affects: nvidia-graphics-drivers-410 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in nvidia-graphics-drivers-410 package in Ubuntu: New Bug description: Dell XPS 15 (9750); it might eventually manage to suspend when the lid is closed, but more often than not will not wake up again when the lid is opened. Waking up using the power button often results in a system that is apparently frozen (graphics displayed are the last on screen before suspend, clock seconds do not change) System is unresponsive to the keyboard at that time (can't switch to a VT or otherwise interact with the system other than holding the power button for a few seconds to shut it down). ProblemType: Bug DistroRelease: Ubuntu 19.04 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mtrudel2516 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Nov 13 10:42:08 2018 InstallationDate: Installed on 2018-11-02 (10 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=UUID=14900847-323c-4427-b59e-89210ec1c8ec 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803179/+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 1803179] Re: System does not reliably come out of suspend
Some added info. This bug is present in: driver : nvidia-driver-415 - third-party free recommended driver : nvidia-driver-410 - third-party free driver : nvidia-driver-390 - distro non-free GPU info: == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd1C8Csv1028sd087Cbc03sc02i00 vendor : NVIDIA Corporation model: GP107M [GeForce GTX 1050 Ti Mobile] When in the faulty state `nvidia-smi` displays a 100% GPU Utilization. Using `prime-select intel` to switch GPU and killing X gives back your display environment using onboard GPU. ** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Dell XPS 15 (9750); it might eventually manage to suspend when the lid is closed, but more often than not will not wake up again when the lid is opened. Waking up using the power button often results in a system that is apparently frozen (graphics displayed are the last on screen before suspend, clock seconds do not change) System is unresponsive to the keyboard at that time (can't switch to a VT or otherwise interact with the system other than holding the power button for a few seconds to shut it down). ProblemType: Bug DistroRelease: Ubuntu 19.04 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mtrudel2516 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Nov 13 10:42:08 2018 InstallationDate: Installed on 2018-11-02 (10 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=UUID=14900847-323c-4427-b59e-89210ec1c8ec 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803179/+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 1805434] Re: linux-azure: 4.15.0-1034.35~16.04.1 -proposed tracker
** Description changed: This bug is for tracking the 4.15.0-1034.35~16.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1803592 phase: Uploaded phase-changed: Tuesday, 27. November 2018 16:12 UTC reason: - promote-to-proposed: Builds not complete + promote-to-proposed: Another kernel is currently pending in proposed stakeholder-signoff: Waiting for signoff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1805434 Title: linux-azure: 4.15.0-1034.35~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.15.0-1034.35~16.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1803592 phase: Uploaded phase-changed: Tuesday, 27. November 2018 16:12 UTC reason: promote-to-proposed: Another kernel is currently pending in proposed stakeholder-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805434/+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 1805011] Re: USB E-MU 0202/0404 reset and disconnect
Install the kernel 4.4 nothing has changed. I failed to install kernel 3 versions. 3.20 version work no problem in Ubuntu 12.04. I tested the sound card in Linux Mint 18. kernel 4.4v. All okay and work only 44.1 khz. I think something is broken in the version of Ubuntu 18.04. Need to do tests at Ubuntu 16.04 -- 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/1805011 Title: USB E-MU 0202/0404 reset and disconnect Status in linux package in Ubuntu: Confirmed Bug description: Used ubuntu 18.04. Sound card permanently disabled and freezes. Different laptops were used, the problem has not changed. Used different cable. [ 23.456082] usb 4-1: new full-speed USB device number 2 using uhci_hcd [ 23.620103] usb 4-1: not running at top speed; connect to a high speed hub [ 23.655112] usb 4-1: New USB device found, idVendor=041e, idProduct=3f02 [ 23.655117] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 23.655122] usb 4-1: Product: E-MU 0202 | USB [ 23.655126] usb 4-1: Manufacturer: E-MU Systems, Inc. [ 23.655130] usb 4-1: SerialNumber: E-MU-03-3F02-07DA0C14-0E730-8740T2A [ 24.029429] usb 1-3: USB disconnect, device number 4 [ 62.156059] usb 1-3: new high-speed USB device number 5 using ehci-pci [ 62.314540] usb 1-3: New USB device found, idVendor=041e, idProduct=3f02 [ 62.314544] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 62.314547] usb 1-3: Product: E-MU 0202 | USB [ 62.314550] usb 1-3: Manufacturer: E-MU Systems, Inc. [ 62.314552] usb 1-3: SerialNumber: E-MU-03-3F02-07DA0C14-0E730-8740T2A [ 62.516964] usb 4-1: USB disconnect, device number 2 [ 147.904012] ehci-pci :00:1a.7: port 3 reset error -110 [ 149.068094] usb 4-1: new full-speed USB device number 3 using uhci_hcd [ 149.226189] usb 4-1: not running at top speed; connect to a high speed hub [ 149.260214] usb 4-1: New USB device found, idVendor=041e, idProduct=3f02 [ 149.260219] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 149.260224] usb 4-1: Product: E-MU 0202 | USB [ 149.260228] usb 4-1: Manufacturer: E-MU Systems, Inc. [ 149.260232] usb 4-1: SerialNumber: E-MU-03-3F02-07DA0C14-0E730-8740T2A [ 149.636378] usb 1-3: USB disconnect, device number 5 [ 314.216062] usb 1-3: new high-speed USB device number 6 using ehci-pci [ 314.374729] usb 1-3: New USB device found, idVendor=041e, idProduct=3f02 [ 314.374735] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 314.374739] usb 1-3: Product: E-MU 0202 | USB [ 314.374743] usb 1-3: Manufacturer: E-MU Systems, Inc. [ 314.374747] usb 1-3: SerialNumber: E-MU-03-3F02-07DA0C14-0E730-8740T2A [ 314.576366] usb 4-1: USB disconnect, device number 3 [ 314.580951] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.581159] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.581362] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.581839] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.582271] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.584189] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.584439] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.584626] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.585109] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.585880] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.598231] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.598331] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.598422] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.598731] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.598970] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.599867] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.599960] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.600112] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.600322] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.600540] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.601171] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.601261] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.601353] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.601545] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.601756] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.602345] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.602436] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.602528] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.602716] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.602927] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.603494] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.603584] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.603676] usb 4-1: 1:1: usb_set_interface failed (-19) [ 314.603864] usb 4-1: 1:1: usb_set_interface failed (-19)
[Kernel-packages] [Bug 1805412] Re: linux-azure: 4.15.0-1034.35 -proposed tracker
** Description changed: This bug is for tracking the 4.15.0-1034.35 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1803592 phase: Uploaded phase-changed: Tuesday, 27. November 2018 16:07 UTC reason: - promote-to-proposed: Builds not complete + promote-to-proposed: Another kernel is currently pending in proposed + stakeholder-signoff: Waiting for signoff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1805412 Title: linux-azure: 4.15.0-1034.35 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.15.0-1034.35 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1803592 phase: Uploaded phase-changed: Tuesday, 27. November 2018 16:07 UTC reason: promote-to-proposed: Another kernel is currently pending in proposed stakeholder-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805412/+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 1801924] Re: CVE-2018-18955: nested user namespaces with more than five extents incorrectly grant privileges over inode
** Changed in: linux (Ubuntu Disco) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801924 Title: CVE-2018-18955: nested user namespaces with more than five extents incorrectly grant privileges over inode Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: Jann Horn reported that nested user namespaces with more than five mappings allow gaining privilege over an inode. Here is my write up of how this happens: Currently, the forward map and reverse map are copied and sorted at the same time before necessary updates to the forward map have been performed. This has the consequence that the forward map receives the necessary updates while the reverse map does not leaving it with invalid data. Specifically, this means that the lower ids of the forward mapping will be correctly mapped to appropriate kernel ids, while the lower ids of the reverse mapping will not. This breaks inode_owner_or_capable() and privileged_wrt_inode_uidgid() which call helpers that need to access the reverse mapping. Thus, a process can incorrectly appear to be capable relative to an inode. Note that the sorting logic is only triggered when more than five extents are specified and when user namespaces are nested. Hence, only containers with complex mappings in nested user namespaces are affected. To fix this issue we need to ensures that the translation happens for both the forward and reverse mappings. First, the forward mappings are sorted and its lower ids translated into kernel ids. After this the forward mapping is copied and into the reverse mapping and the reverse mappings sorted. A proposed patch is appended here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801924/+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 1805434] Re: linux-azure: 4.15.0-1034.35~16.04.1 -proposed tracker
** Description changed: This bug is for tracking the 4.15.0-1034.35~16.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1803592 phase: Uploaded phase-changed: Tuesday, 27. November 2018 16:12 UTC reason: promote-to-proposed: Builds not complete + stakeholder-signoff: Waiting for signoff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1805434 Title: linux-azure: 4.15.0-1034.35~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.15.0-1034.35~16.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1803592 phase: Uploaded phase-changed: Tuesday, 27. November 2018 16:12 UTC reason: promote-to-proposed: Builds not complete stakeholder-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805434/+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 1805474] Re: linux-azure: 4.15.0-1034.35~14.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug is for tracking the 4.15.0-1034.35~14.04.2 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1803592 + phase: Uploaded + phase-changed: Tuesday, 27. November 2018 18:08 UTC reason: - prepare-package: Package not yet uploaded - prepare-package-meta: Package not yet uploaded - prepare-package-signed: Package not yet uploaded + promote-to-proposed: Builds not complete + stakeholder-signoff: Waiting for signoff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1805474 Title: linux-azure: 4.15.0-1034.35~14.04.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug is for tracking the 4.15.0-1034.35~14.04.2 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1803592 phase: Uploaded phase-changed: Tuesday, 27. November 2018 18:08 UTC reason: promote-to-proposed: Builds not complete stakeholder-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805474/+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 1805412] Re: linux-azure: 4.15.0-1034.35 -proposed tracker
Watching for build. ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1805412 Title: linux-azure: 4.15.0-1034.35 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.15.0-1034.35 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1803592 phase: Uploaded phase-changed: Tuesday, 27. November 2018 16:07 UTC reason: promote-to-proposed: Builds not complete To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805412/+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 1805474] Re: linux-azure: 4.15.0-1034.35~14.04.2 -proposed tracker
Watching for build. ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1805474 Title: linux-azure: 4.15.0-1034.35~14.04.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug is for tracking the 4.15.0-1034.35~14.04.2 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1803592 phase: Uploaded phase-changed: Tuesday, 27. November 2018 18:08 UTC reason: promote-to-proposed: Builds not complete stakeholder-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805474/+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 1805434] Re: linux-azure: 4.15.0-1034.35~16.04.1 -proposed tracker
Watching for build. ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1805434 Title: linux-azure: 4.15.0-1034.35~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.15.0-1034.35~16.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1803592 phase: Uploaded phase-changed: Tuesday, 27. November 2018 16:12 UTC reason: promote-to-proposed: Builds not complete To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805434/+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 1805474] Re: linux-azure: 4.15.0-1034.35~14.04.2 -proposed tracker
** Description changed: This bug is for tracking the 4.15.0-1034.35~14.04.2 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1803592 + reason: + prepare-package: Package not yet uploaded + prepare-package-meta: Package not yet uploaded + prepare-package-signed: Package not yet uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1805474 Title: linux-azure: 4.15.0-1034.35~14.04.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug is for tracking the 4.15.0-1034.35~14.04.2 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1803592 reason: prepare-package: Package not yet uploaded prepare-package-meta: Package not yet uploaded prepare-package-signed: Package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805474/+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 1805105] 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 1805105 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 ** Changed in: linux (Ubuntu Cosmic) 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/1805105 Title: /proc/self/stack does not exist in kvm kernel, causing failures in kernel security test Status in QA Regression Testing: Fix Released Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux source package in Xenial: Invalid Status in linux-kvm source package in Xenial: New Status in linux source package in Bionic: Invalid Status in linux-kvm source package in Bionic: New Status in linux source package in Cosmic: Incomplete Status in linux-kvm source package in Cosmic: New Status in linux source package in Disco: Incomplete Status in linux-kvm source package in Disco: New Bug description: Linux larry 4.18.0-1005-kvm #5-Ubuntu SMP Thu Nov 15 20:22:03 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # ls /proc/self/stack ls: cannot access '/proc/self/stack': No such file or directory Thus: FAIL: test_095_kernel_symbols_missing_proc_self_stack (__main__.KernelSecurityTest) kernel addresses in /proc/self/stack are zeroed out -- Traceback (most recent call last): File "./test-kernel-security.py", line 1352, in test_095_kernel_symbols_missing_proc_self_stack self._check_pK_files(self._095_kernel_symbols_missing_proc_self_stack, expected=expected) File "./test-kernel-security.py", line 1199, in _check_pK_files test_function(expected_restricted) File "./test-kernel-security.py", line 1296, in _095_kernel_symbols_missing_proc_self_stack '/proc/self/stack does not exist') AssertionError: /proc/self/stack does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1805105/+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 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
Did you try latest version of Manjaro? -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+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 1805105] Re: /proc/self/stack does not exist in kvm kernel, causing failures in kernel security test
By the way, on 4.19, this is now only readable by root. So, now returns EACCESS when user tries to read it. $ cat /proc/self/stack cat: /proc/self/stack: Permission denied f8a00cef17206ecd1b30d3d9f99e10d9fa707aa7 proc: restrict kernel stack dumps to root ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux (Ubuntu Bionic) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1805105 Title: /proc/self/stack does not exist in kvm kernel, causing failures in kernel security test Status in QA Regression Testing: Fix Released Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux source package in Xenial: Invalid Status in linux-kvm source package in Xenial: New Status in linux source package in Bionic: Invalid Status in linux-kvm source package in Bionic: New Status in linux source package in Cosmic: Incomplete Status in linux-kvm source package in Cosmic: New Status in linux source package in Disco: Incomplete Status in linux-kvm source package in Disco: New Bug description: Linux larry 4.18.0-1005-kvm #5-Ubuntu SMP Thu Nov 15 20:22:03 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # ls /proc/self/stack ls: cannot access '/proc/self/stack': No such file or directory Thus: FAIL: test_095_kernel_symbols_missing_proc_self_stack (__main__.KernelSecurityTest) kernel addresses in /proc/self/stack are zeroed out -- Traceback (most recent call last): File "./test-kernel-security.py", line 1352, in test_095_kernel_symbols_missing_proc_self_stack self._check_pK_files(self._095_kernel_symbols_missing_proc_self_stack, expected=expected) File "./test-kernel-security.py", line 1199, in _check_pK_files test_function(expected_restricted) File "./test-kernel-security.py", line 1296, in _095_kernel_symbols_missing_proc_self_stack '/proc/self/stack does not exist') AssertionError: /proc/self/stack does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1805105/+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 1801540] Re: Microphone distorted sound on ALC892
Tried all those values through HDAAnalyzer, but nothing relevant changed, the noise is still there. A note: In Windows or FreeBSD i was not using any echo cancel software, the noise is just not present. There is still tjhe normal environmental one, but not the robotic one only present on Linux. Here is a recording, amplified so you can easily hear the noise in question. If I don't amplify the input, the noise is still there, just the volume is low. ** Attachment added: "recording.ogg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801540/+attachment/5216803/+files/recording.ogg -- 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/1801540 Title: Microphone distorted sound on ALC892 Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801540/+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 1802787] Re: linux-gcp-edge: 4.18.0-1004.5~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1802750 - phase: Uploaded + phase: Promoted to proposed + phase-changed: Tuesday, 27. November 2018 17:10 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Packages waiting in -proposed for mirror sync + automated-testing: Testing FAILED + certification-testing: Testing in progress + regression-testing: Testing in progress + security-signoff: Waiting for signoff + verification-testing: Testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802787 Title: linux-gcp-edge: 4.18.0-1004.5~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1802750 phase: Promoted to proposed phase-changed: Tuesday, 27. November 2018 17:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED certification-testing: Testing in progress regression-testing: Testing in progress security-signoff: Waiting for signoff verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802787/+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 1805105] Re: /proc/self/stack does not exist in kvm kernel, causing failures in kernel security test
The qa-regression-testing side of things is fixed in commit https://git.launchpad.net/qa-regression- testing/commit/?id=b5cea2f0466f932a86fe31ac3a3ff51dcb99c95e . Thanks! ** Changed in: qa-regression-testing Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1805105 Title: /proc/self/stack does not exist in kvm kernel, causing failures in kernel security test Status in QA Regression Testing: Fix Released Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: Linux larry 4.18.0-1005-kvm #5-Ubuntu SMP Thu Nov 15 20:22:03 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # ls /proc/self/stack ls: cannot access '/proc/self/stack': No such file or directory Thus: FAIL: test_095_kernel_symbols_missing_proc_self_stack (__main__.KernelSecurityTest) kernel addresses in /proc/self/stack are zeroed out -- Traceback (most recent call last): File "./test-kernel-security.py", line 1352, in test_095_kernel_symbols_missing_proc_self_stack self._check_pK_files(self._095_kernel_symbols_missing_proc_self_stack, expected=expected) File "./test-kernel-security.py", line 1199, in _check_pK_files test_function(expected_restricted) File "./test-kernel-security.py", line 1296, in _095_kernel_symbols_missing_proc_self_stack '/proc/self/stack does not exist') AssertionError: /proc/self/stack does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1805105/+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 1805465] Re: linux: 4.19.0-7.8 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: -- swm properties -- reason: - prepare-package: Version not specified + prepare-package: Package not yet uploaded + prepare-package-meta: Package not yet uploaded + prepare-package-signed: Package not yet uploaded + promote-to-release: Testing not complete -- 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/1805465 Title: linux: 4.19.0-7.8 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: -- swm properties -- reason: prepare-package: Package not yet uploaded prepare-package-meta: Package not yet uploaded prepare-package-signed: Package not yet uploaded promote-to-release: Testing not complete To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805465/+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 1805474] [NEW] linux-azure: 4.15.0-1034.35~14.04.2 -proposed tracker
Public bug reported: This bug is for tracking the 4.15.0-1034.35~14.04.2 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1803592 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Marcelo Cerri (mhcerri) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Marcelo Cerri (mhcerri) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Marcelo Cerri (mhcerri) Status: In Progress ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/stakeholder-signoff Importance: Medium Assignee: linux-azure stakeholder signoff (linux-azure-signoff) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-azure (Ubuntu Trusty) Importance: Medium Status: Confirmed ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2018.11.12-7 trusty ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-azure (Ubuntu Trusty) Importance: Undecided Status: New ** Tags added: trusty ** Changed in: linux-azure (Ubuntu Trusty) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/stakeholder-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kerne
[Kernel-packages] [Bug 1805105] Re: /proc/self/stack does not exist in kvm kernel, causing failures in kernel security test
Regardless of whether the linux-kvm maintainer decides to enable this option, the test should not fail if the option is disabled. I'll fix qrt to check for CONFIG_STACKTRACE. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1805105 Title: /proc/self/stack does not exist in kvm kernel, causing failures in kernel security test Status in QA Regression Testing: New Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: Linux larry 4.18.0-1005-kvm #5-Ubuntu SMP Thu Nov 15 20:22:03 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # ls /proc/self/stack ls: cannot access '/proc/self/stack': No such file or directory Thus: FAIL: test_095_kernel_symbols_missing_proc_self_stack (__main__.KernelSecurityTest) kernel addresses in /proc/self/stack are zeroed out -- Traceback (most recent call last): File "./test-kernel-security.py", line 1352, in test_095_kernel_symbols_missing_proc_self_stack self._check_pK_files(self._095_kernel_symbols_missing_proc_self_stack, expected=expected) File "./test-kernel-security.py", line 1199, in _check_pK_files test_function(expected_restricted) File "./test-kernel-security.py", line 1296, in _095_kernel_symbols_missing_proc_self_stack '/proc/self/stack does not exist') AssertionError: /proc/self/stack does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1805105/+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 1805360] Re: linux-aws: 4.18.0-1006.7 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa (kamalmostafa) ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1802743 - phase: Promoted to proposed - phase-changed: Tuesday, 27. November 2018 12:59 UTC + phase: Uploaded + phase-changed: Tuesday, 27. November 2018 16:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Testing in progress - prepare-package-meta: Package tag not yet published + automated-testing: Testing FAILED regression-testing: Testing in progress security-signoff: Waiting for signoff verification-testing: Testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1805360 Title: linux-aws: 4.18.0-1006.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1802743 phase: Uploaded phase-changed: Tuesday, 27. November 2018 16:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED regression-testing: Testing in progress security-signoff: Waiting for signoff verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805360/+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
