[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension
I have the same problem. *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:04:00.0 logical name: enp4s0 version: 06 serial: 8c:89:a5:a4:74:87 size: 10Mbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl8168e-3_0.0.4 03/27/12 latency=0 link=no multicast=yes port=MII speed=10Mbit/s resources: irq:17 ioport:d000(size=256) memory:da104000-da104fff memory:da10-da103fff *-network description: Wireless interface physical id: 3 bus info: usb@2:1.6 logical name: wlx0008ca2fb98d serial: 00:08:ca:2f:b9:8d capabilities: ethernet physical wireless configuration: broadcast=yes driver=r8712u ip=192.168.178.36 multicast=yes wireless=IEEE 802.11bg -- 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/1752772 Title: r8169 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: ===SRU Justification=== [Impact] Ethernet r8169 stops working after system resumed from suspend. [Test] User confirmed these patches fix the issue. r8169 continues to work after resume from suspend. [Regression Potential] Medium. The fix is limited to one device, all patches are in mainline. The WOL default change might cause regression for users that depend on BIOS settings. We can advice them to use userspace tool (systemd, ethtool, etc.) instead. ===Original Bug Report=== I have noticed that the network stopped working on my desktop after I've suspended the system and woke it up. On dmesg there are messages like: [ 150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready [ 150.944101] do_IRQ: 3.37 No irq handler for vector [ 150.944105] r8169 :01:00.0 enp1s0: link down [ 150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready When using Xenial (from a different install), this problem is not happening. This is happening on Bionic. There are only two ways to restore connectivity: 1) Reboot the system; 2) Remove the r8169 module and reinsert it with modprobe. The motherboard is a AsRock H55M-LE and the Ethernet controller is: 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.172 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Mar 2 00:21:57 2018 Dependencies: InstallationDate: Installed on 2018-02-26 (3 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-10-generic. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1153 F pulseaudio /dev/snd/controlC1: usuario1153 F pulseaudio Card0.Amixer.info: Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26' Mixer name : 'VIA VT1818S' Components : 'HDA:11060440,18492818,0010' Controls : 40 Simple ctrls : 17 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 7 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] CurrentDesktop: LXDE Dependencies: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f InstallationDate: Installed on 2018-02-26 (3 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux-firmware 1.172 PackageArchitecture: all ProcFB: 0
[Kernel-packages] [Bug 1788098] 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 1788098 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/1788098 Title: Avoid migration issues with aligned 2MB THB Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: Invalid Status in linux source package in Bionic: New Status in linux source package in Cosmic: Incomplete Bug description: --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT--- Hi, in some environments it was observed that this qemu patch to enable THP made it more likely to hit guest migration issues, however the following kernel patch resolves those migration issues: https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15 KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix() Once merged upstream, it would be good to include that change as well to avoid potential migration problems. Should I open a new bug for that or is it better to track here? Note Paelzer: I have not seen related migration issues myself, but it seems reasonable and confirmed by IBM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788098/+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 1788098] Re: Avoid migration issues with aligned 2MB THB
Oh, I just realized while initially reported against qemu in bug 1781526 that this is a kernel, and not a qemu patch. That spreads the timeline a bit: - this should be in Cosmic before Release to avoid issues due to the fix of 1781526. - since that is kind of short I'll bump priority there. - This has to be in Bionic before a fix for bug 1781526 (I'll wait with a qemu change until this one is complete) I'm marking the qemu task invalid (no action there other than to track the Bionic release of this which will finally unblock the SRU of bug 1781526 to Bionic). I'm adding a kernel task to reflect that this is a kernel change that is needed. Finally I'm adding a Cosmic and Bionic Task. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu) Status: New => Invalid ** Also affects: qemu (Ubuntu Cosmic) Importance: Undecided Status: Invalid ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: qemu (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: qemu (Ubuntu Bionic) ** No longer affects: qemu (Ubuntu Cosmic) ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788098 Title: Avoid migration issues with aligned 2MB THB Status in linux package in Ubuntu: New Status in qemu package in Ubuntu: Invalid Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Bug description: --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT--- Hi, in some environments it was observed that this qemu patch to enable THP made it more likely to hit guest migration issues, however the following kernel patch resolves those migration issues: https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15 KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix() Once merged upstream, it would be good to include that change as well to avoid potential migration problems. Should I open a new bug for that or is it better to track here? Note Paelzer: I have not seen related migration issues myself, but it seems reasonable and confirmed by IBM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788098/+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 1788097] [NEW] performance drop with ATS enabled
Public bug reported: == Comment: #0 - Michael Ranweiler - 2018-08-16 09:58:02 == Witherspoon cluster now has ATS enabled with driver 396.42, CUDA version 9.2.148. They are running the CORAL benchmark LULESH with and without ATS, and they see a significant performance drop with ATS enabled. Below is the run with ATS: Run completed: Problem size = 160 MPI tasks = 8 Iteration count = 100 Final Origin Energy = 1.605234e+09 Testing Plane 0 of Energy Array on rank 0: MaxAbsDiff = 2.384186e-07 TotalAbsDiff = 5.300015e-07 MaxRelDiff = 1.631916e-12 Elapsed time = 153.00 (s) Grind time (us/z/c) = 0.37352393 (per dom) (0.046690491 overall) FOM = 21417.637 (z/s) Here is the run without ATS: Run completed: Problem size = 160 MPI tasks = 8 Iteration count = 100 Final Origin Energy = 1.605234e+09 Testing Plane 0 of Energy Array on rank 0: MaxAbsDiff = 2.384186e-07 TotalAbsDiff = 5.300015e-07 MaxRelDiff = 1.631916e-12 Elapsed time = 13.27 (s) Grind time (us/z/c) = 0.032394027 (per dom) (0.0040492534 overall) FOM = 246959.11 (z/s) Using ATS on a single node slows down the OpenACC version more than 10 times, and for the version with OpenMP 4.5 and managed memory, they observe a 2x slowdown. Last comment from NVIDIA (Javier Cabezas - 07/29/2018 11:30 AM): We think we have found where's the issue. This behavior reproduces for any two concurrent processes that create CUDA contexts on the GPUs and heavily unmap memory (no need to launch any work on the GPUs). When the problem repros, perf shows that most of the time is spent in mmio_invalidate. However, this only happens when processes register GPUs attached to the same NPU. Thus, if process A, initializes GPU 0 and/or 1, and process B, initializes GPU 2 and/or 3, we don't see the slowdown. This makes sense, because ATSDs on different NPUs are issued independently. After some code inspection in npu-dma.c (powerpc backend in the Linux kernel), Mark noticed that the problem could be in the utilization of test_and_set_bit_lock in get_mmio_atsd_reg. The implementation of test_and_set_bit_lock in powerpc relies on the ldarx/stdcx instructions (PPC_LLARX/PPC_STLCX in the snippet below): #define DEFINE_TESTOP(fn, op, prefix, postfix, eh)\ static __inline__ unsigned long fn( \ unsigned long mask, \ volatile unsigned long *_p) \ { \ unsigned long old, t; \ unsigned long *p = (unsigned long *)_p; \ __asm__ __volatile__ (\ prefix\ "1:"PPC_LLARX(%0,0,%3,eh) "\n"\ stringify_in_c(op) "%1,%0,%2\n" \ PPC405_ERR77(0,%3)\ PPC_STLCX "%1,0,%3\n" \ "bne- 1b\n" \ postfix \ : "=" (old), "=" (t) \ : "r" (mask), "r" (p) \ : "cc", "memory");\ return (old & mask); \ } According to the PowerPC manual, ldarx creates a memory reservation and a subsequent stwcx instruction from the same processor ensures an atomic read-modify-write operation. However, the reservation can be lost if a different processor executes any store instruction on the same address. That's why "bne- 1b" checks wether stwcx was successful and jumps back to retry, otherwise. Since DEFINE_TESTOP doesn't implement any back-off mechanism, two different processors trying to get an ATSD register can starve each other. Mark compiled a custom kernel which surrounds the calls to test_and_set_bit_lock in get_mmio_atsd_reg with a spinlock and I verified that it solves the issue. These are the execution times for LULESH: ATS OFF Elapsed time = 16.87 (s) ATS ON Elapsed time = 215.56 (s) ATS ON + Spinlock Elapsed time = 18.14 (s) Fixed with the following patch in the powerpc tree: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=9eab9901b015 == Comment: #1 - Michael Ranweiler - 2018-08-20 14:56:52 == This is now in mainline, too: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/powerpc/platforms/powernv/npu-dma.c?id=9eab9901b015f489199105c470de1ffc337cfabb It has some small fuzz to apply to 4.15.0.32-35: diff --git a/arch/powerpc/platforms/powernv/npu-dma.c b/arch/powerpc/platforms/powernv/npu-dma.c index 6c8e168e6571..18226895681e 100644 --- a/arch/powerpc/platforms/powernv/npu-dma.c +++ b/arch/powerpc/platforms/powernv/npu-dma.c @@ -434,8 +434,9 @@ static int get_mmio_atsd_reg(struct npu *npu) int i; for (i = 0; i < npu->mmio_atsd_count; i++) { - if (!test_and_set_bit_lock(i,
[Kernel-packages] [Bug 1788097] [NEW] performance drop with ATS enabled
You have been subscribed to a public bug: == Comment: #0 - Michael Ranweiler - 2018-08-16 09:58:02 == Witherspoon cluster now has ATS enabled with driver 396.42, CUDA version 9.2.148. They are running the CORAL benchmark LULESH with and without ATS, and they see a significant performance drop with ATS enabled. Below is the run with ATS: Run completed: Problem size = 160 MPI tasks = 8 Iteration count = 100 Final Origin Energy = 1.605234e+09 Testing Plane 0 of Energy Array on rank 0: MaxAbsDiff = 2.384186e-07 TotalAbsDiff = 5.300015e-07 MaxRelDiff = 1.631916e-12 Elapsed time = 153.00 (s) Grind time (us/z/c) = 0.37352393 (per dom) (0.046690491 overall) FOM = 21417.637 (z/s) Here is the run without ATS: Run completed: Problem size = 160 MPI tasks = 8 Iteration count = 100 Final Origin Energy = 1.605234e+09 Testing Plane 0 of Energy Array on rank 0: MaxAbsDiff = 2.384186e-07 TotalAbsDiff = 5.300015e-07 MaxRelDiff = 1.631916e-12 Elapsed time = 13.27 (s) Grind time (us/z/c) = 0.032394027 (per dom) (0.0040492534 overall) FOM = 246959.11 (z/s) Using ATS on a single node slows down the OpenACC version more than 10 times, and for the version with OpenMP 4.5 and managed memory, they observe a 2x slowdown. Last comment from NVIDIA (Javier Cabezas - 07/29/2018 11:30 AM): We think we have found where's the issue. This behavior reproduces for any two concurrent processes that create CUDA contexts on the GPUs and heavily unmap memory (no need to launch any work on the GPUs). When the problem repros, perf shows that most of the time is spent in mmio_invalidate. However, this only happens when processes register GPUs attached to the same NPU. Thus, if process A, initializes GPU 0 and/or 1, and process B, initializes GPU 2 and/or 3, we don't see the slowdown. This makes sense, because ATSDs on different NPUs are issued independently. After some code inspection in npu-dma.c (powerpc backend in the Linux kernel), Mark noticed that the problem could be in the utilization of test_and_set_bit_lock in get_mmio_atsd_reg. The implementation of test_and_set_bit_lock in powerpc relies on the ldarx/stdcx instructions (PPC_LLARX/PPC_STLCX in the snippet below): #define DEFINE_TESTOP(fn, op, prefix, postfix, eh)\ static __inline__ unsigned long fn( \ unsigned long mask, \ volatile unsigned long *_p) \ { \ unsigned long old, t; \ unsigned long *p = (unsigned long *)_p; \ __asm__ __volatile__ (\ prefix\ "1:"PPC_LLARX(%0,0,%3,eh) "\n"\ stringify_in_c(op) "%1,%0,%2\n" \ PPC405_ERR77(0,%3)\ PPC_STLCX "%1,0,%3\n" \ "bne- 1b\n" \ postfix \ : "=" (old), "=" (t) \ : "r" (mask), "r" (p) \ : "cc", "memory");\ return (old & mask); \ } According to the PowerPC manual, ldarx creates a memory reservation and a subsequent stwcx instruction from the same processor ensures an atomic read-modify-write operation. However, the reservation can be lost if a different processor executes any store instruction on the same address. That's why "bne- 1b" checks wether stwcx was successful and jumps back to retry, otherwise. Since DEFINE_TESTOP doesn't implement any back-off mechanism, two different processors trying to get an ATSD register can starve each other. Mark compiled a custom kernel which surrounds the calls to test_and_set_bit_lock in get_mmio_atsd_reg with a spinlock and I verified that it solves the issue. These are the execution times for LULESH: ATS OFF Elapsed time = 16.87 (s) ATS ON Elapsed time = 215.56 (s) ATS ON + Spinlock Elapsed time = 18.14 (s) Fixed with the following patch in the powerpc tree: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=9eab9901b015 == Comment: #1 - Michael Ranweiler - 2018-08-20 14:56:52 == This is now in mainline, too: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/powerpc/platforms/powernv/npu-dma.c?id=9eab9901b015f489199105c470de1ffc337cfabb It has some small fuzz to apply to 4.15.0.32-35: diff --git a/arch/powerpc/platforms/powernv/npu-dma.c b/arch/powerpc/platforms/powernv/npu-dma.c index 6c8e168e6571..18226895681e 100644 --- a/arch/powerpc/platforms/powernv/npu-dma.c +++ b/arch/powerpc/platforms/powernv/npu-dma.c @@ -434,8 +434,9 @@ static int get_mmio_atsd_reg(struct npu *npu) int i; for (i = 0; i < npu->mmio_atsd_count; i++) { - if
[Kernel-packages] [Bug 1788073] 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 1788073 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788073 Title: Wifi adapter not found after suspend (iwlwifi) Status in linux package in Ubuntu: Incomplete Bug description: Hello, I am finding that the network adapter " Network controller: Intel Corporation Wireless 7260 (rev bb) " (iwlwifi) is reported as disabled, or not present after a lengthy suspend. This is an identical issue to those reported for Realtek, but I have not found an existing report for Intel. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817 This was no a problem in 16.04 or 17.10 with the identical hardware. 18.04 was installed clean. Happy to provide more information, however, I am not exactly sure what information to provide? Thanks in advance, Description: Ubuntu 18.04.1 LTS Release: 18.04 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev bb) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:4070] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788073/+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 1778021] Re: could not shut down properly. the computer is sounding loudly near the end of shutting down process.
[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/1778021 Title: could not shut down properly. the computer is sounding loudly near the end of shutting down process. Status in linux package in Ubuntu: Expired Bug description: my computer could not shutdown properly everytime i shut it down. nearing the end of shutting down process, when the screen turns into black, the computer will make loud noise (strong fan sound) and does not shut down. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: grub (not installed) ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 21 12:32:51 2018 InstallationDate: Installed on 2018-06-11 (9 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: grub UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778021/+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 1778039] Re: suspend/resume crash with virtualbox VM
[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/1778039 Title: suspend/resume crash with virtualbox VM Status in linux package in Ubuntu: Expired Bug description: Laptop crashes on suspend/resume when a virtualbox VM is running. Observed in 3.13.0-151-generic and -149-generic. Using latest virtualbox package 5.2.12-122591~Ubuntu~trusty from download.virtualbox.org. Same behaviour occurred in 5.2.10 and 5.2.8. Tried kernel versions -147 -145 -144 and -143. Of these, -147 -145 and -144 exhibited problems with suspend/resume without virtualbox running (would suspend once and then subsequently fail to suspend at all). Currently stuck on using kernel version 3.13.0-143 due to this issue. Ubuntu 14.04 latest. --- ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: avdd 2262 F pulseaudio /dev/snd/controlC0: avdd 2262 F pulseaudio CRDA: country AU: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (3, 23) (5250 - 5330 @ 40), (3, 23), DFS (5735 - 5835 @ 40), (3, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-05-03 (1509 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 20CMCTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-143-generic root=UUID=e616202b-b92a-4320-a7e7-e6ec2ee05c7e ro video.use_native_backlight=1 ProcVersionSignature: Ubuntu 3.13.0-143.192-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-143-generic N/A linux-backports-modules-3.13.0-143-generic N/A linux-firmware 1.127.24 Tags: trusty Uname: Linux 3.13.0-143-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/19/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET36W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CMCTO1WW 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:bvrN10ET36W(1.15):bd06/19/2015:svnLENOVO:pn20CMCTO1WW:pvrThinkPadX250:rvnLENOVO:rn20CMCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20CMCTO1WW dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778039/+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 1788073] Re: Wifi adapter not found after suspend (iwlwifi)
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788073 Title: Wifi adapter not found after suspend (iwlwifi) Status in linux package in Ubuntu: New Bug description: Hello, I am finding that the network adapter " Network controller: Intel Corporation Wireless 7260 (rev bb) " (iwlwifi) is reported as disabled, or not present after a lengthy suspend. This is an identical issue to those reported for Realtek, but I have not found an existing report for Intel. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817 This was no a problem in 16.04 or 17.10 with the identical hardware. 18.04 was installed clean. Happy to provide more information, however, I am not exactly sure what information to provide? Thanks in advance, Description: Ubuntu 18.04.1 LTS Release: 18.04 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev bb) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:4070] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788073/+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 1760647] Re: Unable to build lttng module on 4.4/4.15 KVM kernel
http://kernel.ubuntu.com/git/ubuntu/autotest-client- tests.git/commit/?id=488830175f870139fcbe4a3d3ff4bb61668e8cc1 ** Changed in: ubuntu-kernel-tests Status: In Progress => 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/1760647 Title: Unable to build lttng module on 4.4/4.15 KVM kernel Status in ubuntu-kernel-tests: Fix Released Status in linux-kvm package in Ubuntu: Won't Fix Status in linux-kvm source package in Xenial: Won't Fix Bug description: Tested with the lttng module in -proposed (2.8.0-1ubuntu1~16.04.5), it looks like this is the CONFIG issue. Build log: DKMS make.log for lttng-modules-2.8.0 for kernel 4.4.0-1019-kvm (x86_64) Mon Apr 2 17:05:48 UTC 2018 make: Entering directory '/usr/src/linux-headers-4.4.0-1019-kvm' /var/lib/dkms/lttng-modules/2.8.0/build/Makefile:12: *** The option CONFIG_TRACEPOINTS needs to be enabled in your kernel configuration. Stop. Makefile:1423: recipe for target '_module_/var/lib/dkms/lttng-modules/2.8.0/build' failed make: *** [_module_/var/lib/dkms/lttng-modules/2.8.0/build] Error 2 make: Leaving directory '/usr/src/linux-headers-4.4.0-1019-kvm' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24 ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98 Uname: Linux 4.4.0-1019-kvm x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Mon Apr 2 16:38:25 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1760647/+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 1788073] [NEW] Wifi adapter not found after suspend (iwlwifi)
You have been subscribed to a public bug: Hello, I am finding that the network adapter " Network controller: Intel Corporation Wireless 7260 (rev bb) " (iwlwifi) is reported as disabled, or not present after a lengthy suspend. This is an identical issue to those reported for Realtek, but I have not found an existing report for Intel. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817 This was no a problem in 16.04 or 17.10 with the identical hardware. 18.04 was installed clean. Happy to provide more information, however, I am not exactly sure what information to provide? Thanks in advance, Description:Ubuntu 18.04.1 LTS Release:18.04 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev bb) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:4070] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Wifi adapter not found after suspend (iwlwifi) https://bugs.launchpad.net/bugs/1788073 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 1781533] Re: SATA device is not going to DEVSLP
** Changed in: hwe-next Status: In Progress => Triaged ** Changed in: linux-oem (Ubuntu) Status: In Progress => Triaged -- 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 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 https://patchwork.kernel.org/patch/10502285/ https://patchwork.kernel.org/patch/10502287/ [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. 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 1787904] 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/1787904 Title: [radeon] machine crash after GPU reset Status in linux package in Ubuntu: Confirmed 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-nouveau 1:1.0.15-2 xserver.bootTime: Fri Jan 5
[Kernel-packages] [Bug 1787904] Re: machine crash after GPU reset
Indeed the problem appears to be low level, so reassigning to the kernel. ** Package changed: xserver-xorg-video-ati (Ubuntu) => linux (Ubuntu) ** Summary changed: - machine crash after GPU reset + [radeon] machine crash after GPU reset ** Tags added: radeon -- 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: New 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
[Kernel-packages] [Bug 1787904] [NEW] machine crash after GPU reset
You have been subscribed to a public bug: 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-nouveau 1:1.0.15-2 xserver.bootTime: Fri Jan 5 15:01:43 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1.3 xserver.video_driver: radeon ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- machine crash after GPU reset https://bugs.launchpad.net/bugs/1787904 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. --
[Kernel-packages] [Bug 1787571] Re: Bluetooth keyboard won't connect again after connection was lost
Sorry, I don't have any more expertise on the matter. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1787571 Title: Bluetooth keyboard won't connect again after connection was lost Status in bluez package in Ubuntu: New Bug description: After my Bluetooth keyboard from Logitech (K380) looses its connection, either after a Ubuntu restart or by manually turning the keyboard off an on, it won't connect any more. Additionally, while the keyboard tries to reestablish the connection, my Logitech Bluetooth mouse (M590) looses its connection too! After that I can't establish any Bluetooth connection at all. Only a "sudo service bluetooth restart" helps. Then my mouse reconnects easily, if it's not disrupted by my keyboard. So I'm only possible to use my mouse and not the keyboard, because while it tries to reconnect, it kills the connection of my mouse and everything starts over again. I've also tried to reconnect the keyboard through "bluetoothctl", but without success: $ bluetoothctl paired-devices Device 34:88:5D:42:7E:03 Keyboard K380 Device FA:6A:9E:DA:2B:30 M585/M590 $ bluetoothctl connect 34:88:5D:42:7E:03 Attempting to connect to 34:88:5D:42:7E:03 Failed to connect: org.bluez.Error.Failed Both devices are "trusted": $ bluetoothctl info 34:88:5D:42:7E:03 Device 34:88:5D:42:7E:03 (public) Name: Keyboard K380 Alias: Keyboard K380 Class: 0x2540 Icon: input-keyboard Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb) UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) Modalias: usb:v046DpB342d4200 $ bluetoothctl info FA:6A:9E:DA:2B:30 Device FA:6A:9E:DA:2B:30 (random) Name: M585/M590 Alias: M585/M590 Appearance: 0x03c2 Icon: input-mouse Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Device Information(180a--1000-8000-00805f9b34fb) UUID: Battery Service (180f--1000-8000-00805f9b34fb) UUID: Human Interface Device(1812--1000-8000-00805f9b34fb) UUID: Vendor specific (0001--1000-8000-011f246d) Modalias: usb:v046DpB01Bd0007 $ bluetoothctl show Controller 2C:6F:C9:44:57:E0 (public) Name: mir Alias: mir Class: 0x000c010c Powered: yes Discoverable: yes Pairable: yes UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0532 Discovering: no The only way to use my Bluetooth keyboard is to pair it again, f.i. by doing: bluetoothctl remove XX:XX:XX:XX:XX:XX exit sudo service bluetooth restart bluetoothctl scan on trust XX:XX:XX:XX:XX:XX pair XX:XX:XX:XX:XX:XX connect XX:XX:XX:XX:XX:XX exit This keyboard works flawlessly with my Android device and also on a MacBook Pro with macOS. It also worked well with another notebook (Toshiba Satellite Pro C850-1HL) from 17.04 to 18.04, which I don't own anymore. I've updated my BlueZ stack with ppa:bluetooth/bluez, but reverted back by purging it, because it didn't help. I also have some debug info FROM LAST WEEK. This was collected after a system restart and while the keyboard tried to reestablish the connection. At this time my BlueZ packages were from the PPA mentioned above: $ dpkg -l | grep blue ii bluez 5.50-0ubuntu0ppa1 amd64Bluetooth tools and daemons ii bluez-cups 5.50-0ubuntu0ppa1 amd64Bluetooth printer driver for CUPS ii bluez-obexd5.50-0ubuntu0ppa1 amd64bluez obex daemon ii
[Kernel-packages] [Bug 1787571] Re: Bluetooth keyboard won't connect again after connection was lost
If something is "crashing" then please follow the instructions for reporting crashes: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1787571 Title: Bluetooth keyboard won't connect again after connection was lost Status in bluez package in Ubuntu: New Bug description: After my Bluetooth keyboard from Logitech (K380) looses its connection, either after a Ubuntu restart or by manually turning the keyboard off an on, it won't connect any more. Additionally, while the keyboard tries to reestablish the connection, my Logitech Bluetooth mouse (M590) looses its connection too! After that I can't establish any Bluetooth connection at all. Only a "sudo service bluetooth restart" helps. Then my mouse reconnects easily, if it's not disrupted by my keyboard. So I'm only possible to use my mouse and not the keyboard, because while it tries to reconnect, it kills the connection of my mouse and everything starts over again. I've also tried to reconnect the keyboard through "bluetoothctl", but without success: $ bluetoothctl paired-devices Device 34:88:5D:42:7E:03 Keyboard K380 Device FA:6A:9E:DA:2B:30 M585/M590 $ bluetoothctl connect 34:88:5D:42:7E:03 Attempting to connect to 34:88:5D:42:7E:03 Failed to connect: org.bluez.Error.Failed Both devices are "trusted": $ bluetoothctl info 34:88:5D:42:7E:03 Device 34:88:5D:42:7E:03 (public) Name: Keyboard K380 Alias: Keyboard K380 Class: 0x2540 Icon: input-keyboard Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb) UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) Modalias: usb:v046DpB342d4200 $ bluetoothctl info FA:6A:9E:DA:2B:30 Device FA:6A:9E:DA:2B:30 (random) Name: M585/M590 Alias: M585/M590 Appearance: 0x03c2 Icon: input-mouse Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Device Information(180a--1000-8000-00805f9b34fb) UUID: Battery Service (180f--1000-8000-00805f9b34fb) UUID: Human Interface Device(1812--1000-8000-00805f9b34fb) UUID: Vendor specific (0001--1000-8000-011f246d) Modalias: usb:v046DpB01Bd0007 $ bluetoothctl show Controller 2C:6F:C9:44:57:E0 (public) Name: mir Alias: mir Class: 0x000c010c Powered: yes Discoverable: yes Pairable: yes UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0532 Discovering: no The only way to use my Bluetooth keyboard is to pair it again, f.i. by doing: bluetoothctl remove XX:XX:XX:XX:XX:XX exit sudo service bluetooth restart bluetoothctl scan on trust XX:XX:XX:XX:XX:XX pair XX:XX:XX:XX:XX:XX connect XX:XX:XX:XX:XX:XX exit This keyboard works flawlessly with my Android device and also on a MacBook Pro with macOS. It also worked well with another notebook (Toshiba Satellite Pro C850-1HL) from 17.04 to 18.04, which I don't own anymore. I've updated my BlueZ stack with ppa:bluetooth/bluez, but reverted
[Kernel-packages] [Bug 1782347] Re: [radeon] GDM3 fails to load without nomodeset
No problem. Just wait until it happens again and eventually one of the crash reports will be more usable. -- 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/1782347 Title: [radeon] GDM3 fails to load without nomodeset Status in gdm3 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Both with the livecd (usb drive) and the installed version, I must boot with the 'nomodeset' kernel parameter at GRUB; otherwise GDM3 will not boot (the screen will keep on flashing in semi-textual mode, with a white mouse arrow stuck). This, however, prevents me from using the 'radeon' video driver, dropping me to a very basic 1024x768 vesa mode. The bug did NOT occur on Ubuntu 12.04, so it is a regression. Also, the bug does NOT occur on XUbuntu/XFCE 18.04, so it is a GDM3-Gnome related thing. Thanks, MZ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 18 12:18:06 2018 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2018-07-18T12:14:53.871895 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2018-07-19T11:39:06.027905 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-12 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+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 1585434] Re: ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]
yes i think it is when selecting encrypted home. On Monday, August 20, 2018, 7:55:31 PM EDT, Denisa Rucaj <1585...@bugs.launchpad.net> wrote: I am experiencing the same error after upgrading from Ubuntu 17.10 to ubuntu 18.4.1 TLS ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4] ecryptfs_readpage: Error decrypting page; rc = [-4] -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1585434 Title: ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4] Status in linux package in Ubuntu: Confirmed Bug description: ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4] ecryptfs_readpage: Error decrypting page; rc = [-4] I dont' have this issue showing in dmesg when using 3.19 kernel, only with later kernels. Is it related to selecting encrypted home on install or something? I don't notice any issues with performance because of it or have any other error messages. I am using default ubuntu xenial 16.04 with unity. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: cooloutac 2054 F pulseaudio /dev/snd/pcmC0D0p: cooloutac 2054 F...m pulseaudio /dev/snd/controlC0: cooloutac 2054 F pulseaudio CurrentDesktop: Unity Date: Tue May 24 22:38:44 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0118ec29-2bd5-4cbc-9800-9c04bbe083d1 InstallationDate: Installed on 2016-05-20 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp2s0 no wireless extensions. lo no wireless extensions. MachineType: Dell Inc. Studio XPS 7100 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=fcd92967-7d59-44bf-bb88-06efa6fac5f7 ro ipv6.disable=1 quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware 1.157 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0NWWY0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd09/10/2010:svnDellInc.:pnStudioXPS7100:pvr:rvnDellInc.:rn0NWWY0:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 7100 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1585434/+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/1585434 Title: ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4] Status in linux package in Ubuntu: Confirmed Bug description: ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4] ecryptfs_readpage: Error decrypting page; rc = [-4] I dont' have this issue showing in dmesg when using 3.19 kernel, only with later kernels. Is it related to selecting encrypted home on install or something? I don't notice any issues with performance because of it or have any other error messages. I am using default ubuntu xenial 16.04 with unity. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cooloutac 2054 F pulseaudio /dev/snd/pcmC0D0p: cooloutac 2054 F...m pulseaudio /dev/snd/controlC0: cooloutac 2054 F pulseaudio CurrentDesktop: Unity Date: Tue May 24 22:38:44 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0118ec29-2bd5-4cbc-9800-9c04bbe083d1 InstallationDate: Installed on 2016-05-20 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Studio XPS 7100 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=fcd92967-7d59-44bf-bb88-06efa6fac5f7 ro ipv6.disable=1 quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware
[Kernel-packages] [Bug 1585434] Re: ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]
I am experiencing the same error after upgrading from Ubuntu 17.10 to ubuntu 18.4.1 TLS ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4] ecryptfs_readpage: Error decrypting page; rc = [-4] -- 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/1585434 Title: ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4] Status in linux package in Ubuntu: Confirmed Bug description: ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4] ecryptfs_readpage: Error decrypting page; rc = [-4] I dont' have this issue showing in dmesg when using 3.19 kernel, only with later kernels. Is it related to selecting encrypted home on install or something? I don't notice any issues with performance because of it or have any other error messages. I am using default ubuntu xenial 16.04 with unity. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cooloutac 2054 F pulseaudio /dev/snd/pcmC0D0p: cooloutac 2054 F...m pulseaudio /dev/snd/controlC0: cooloutac 2054 F pulseaudio CurrentDesktop: Unity Date: Tue May 24 22:38:44 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0118ec29-2bd5-4cbc-9800-9c04bbe083d1 InstallationDate: Installed on 2016-05-20 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Studio XPS 7100 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=fcd92967-7d59-44bf-bb88-06efa6fac5f7 ro ipv6.disable=1 quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0NWWY0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd09/10/2010:svnDellInc.:pnStudioXPS7100:pvr:rvnDellInc.:rn0NWWY0:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 7100 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1585434/+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 1787188] Re: linux-lts-trusty: 3.13.0-156.206~precise1 -proposed tracker
The package has been published and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow/promote-to-security Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** 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: 1787187 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true + kernel-stable-phase-changed:Monday, 20. August 2018 23:03 UTC + kernel-stable-phase:Released ** 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: 1787187 - phase: Promoted to proposed + phase: Released proposed-announcement-sent: true proposed-testing-requested: true - kernel-stable-phase-changed:Monday, 20. August 2018 23:03 UTC - kernel-stable-phase:Released ** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1787188 Title: linux-lts-trusty: 3.13.0-156.206~precise1 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Invalid 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: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: 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: 1787187 phase: Released proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787188/+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 1787188] Re: linux-lts-trusty: 3.13.0-156.206~precise1 -proposed tracker
** Tags added: regression-testing-passed ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-precise ** Tags removed: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1787188 Title: linux-lts-trusty: 3.13.0-156.206~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: 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: 1787187 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787188/+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 1787618] Re: since 3.13.0.153 doesnt wakeup from suspension
im not sure if everything is done as it was supposed to be done. i opened in the browser the "authorize application to...", i confirmed to access but it stuck on "almost finished" state for around 10mins... -- 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/1787618 Title: since 3.13.0.153 doesnt wakeup from suspension Status in linux package in Ubuntu: Confirmed Bug description: hey all, since a couple of updates after kernel 3.13.0.145 the laptop doesnt wake up from suspension. i just need to hard boot by keep pressing the power button and restart. in case i boot in the older 3.13.0.145 kernel all works fine. last kernel update hasnt solved it. i suppose the updates should include this kind of services or make them better not the opposite... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787618/+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 1787618] Re: since 3.13.0.153 doesnt wakeup from suspension
** 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/1787618 Title: since 3.13.0.153 doesnt wakeup from suspension Status in linux package in Ubuntu: Confirmed Bug description: hey all, since a couple of updates after kernel 3.13.0.145 the laptop doesnt wake up from suspension. i just need to hard boot by keep pressing the power button and restart. in case i boot in the older 3.13.0.145 kernel all works fine. last kernel update hasnt solved it. i suppose the updates should include this kind of services or make them better not the opposite... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787618/+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 1788049] 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/1788049 Title: Kernel 4.15.0-32 disables touchscreen in tablet mode on X1 Yoga Status in linux package in Ubuntu: Confirmed Bug description: After a linux kernel update to 4.15.0-32 the touchscreen on my X1 Yoga is disabled when rotated into tablet mode. This is a major regression since my laptop is unusable in tablet mode now. The touchscreen will work fine up until I rotate the screen 180 degrees and table mode is enabled. Rebooting with kernel 4.15.0-30 restores the laptop to the correct behaviour. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: calum 2459 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Aug 20 22:28:50 2018 InstallationDate: Installed on 2017-10-20 (304 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20JDCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=4f03289b-2cac-4bfb-bc59-47e041629a44 ro quiet splash resume=UUID=4f03289b-2cac-4bfb-bc59-47e041629a44 resume_offset=757760 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1NET42W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1NET42W(1.29):bd07/06/2018:svnLENOVO:pn20JDCTO1WW:pvrThinkPadX1Yoga2nd:rvnLENOVO:rn20JDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 2nd dmi.product.name: 20JDCTO1WW dmi.product.version: ThinkPad X1 Yoga 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788049/+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 1788049] [NEW] Kernel 4.15.0-32 disables touchscreen in tablet mode on X1 Yoga
Public bug reported: After a linux kernel update to 4.15.0-32 the touchscreen on my X1 Yoga is disabled when rotated into tablet mode. This is a major regression since my laptop is unusable in tablet mode now. The touchscreen will work fine up until I rotate the screen 180 degrees and table mode is enabled. Rebooting with kernel 4.15.0-30 restores the laptop to the correct behaviour. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: calum 2459 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Aug 20 22:28:50 2018 InstallationDate: Installed on 2017-10-20 (304 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20JDCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=4f03289b-2cac-4bfb-bc59-47e041629a44 ro quiet splash resume=UUID=4f03289b-2cac-4bfb-bc59-47e041629a44 resume_offset=757760 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1NET42W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1NET42W(1.29):bd07/06/2018:svnLENOVO:pn20JDCTO1WW:pvrThinkPadX1Yoga2nd:rvnLENOVO:rn20JDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 2nd dmi.product.name: 20JDCTO1WW dmi.product.version: ThinkPad X1 Yoga 2nd dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788049 Title: Kernel 4.15.0-32 disables touchscreen in tablet mode on X1 Yoga Status in linux package in Ubuntu: New Bug description: After a linux kernel update to 4.15.0-32 the touchscreen on my X1 Yoga is disabled when rotated into tablet mode. This is a major regression since my laptop is unusable in tablet mode now. The touchscreen will work fine up until I rotate the screen 180 degrees and table mode is enabled. Rebooting with kernel 4.15.0-30 restores the laptop to the correct behaviour. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: calum 2459 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Aug 20 22:28:50 2018 InstallationDate: Installed on 2017-10-20 (304 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20JDCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=4f03289b-2cac-4bfb-bc59-47e041629a44 ro quiet splash resume=UUID=4f03289b-2cac-4bfb-bc59-47e041629a44 resume_offset=757760 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1NET42W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1NET42W(1.29):bd07/06/2018:svnLENOVO:pn20JDCTO1WW:pvrThinkPadX1Yoga2nd:rvnLENOVO:rn20JDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 2nd dmi.product.name: 20JDCTO1WW dmi.product.version: ThinkPad X1 Yoga 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788049/+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 1788044] 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/1788044 Title: task kworker blocked for more than 120 seconds nouveau Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: I was using chromium when the whole system GUI stopped responding at 15:42. This corresponds to the system journal at that point: Aug 20 15:42:56 dh3930 kernel: nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Aug 20 15:42:56 dh3930 kernel: nouveau :01:00.0: fifo: runlist 0: scheduled for recovery Aug 20 15:42:56 dh3930 kernel: nouveau :01:00.0: fifo: channel 15: killed Aug 20 15:42:56 dh3930 kernel: nouveau :01:00.0: fifo: engine 0: scheduled for recovery Aug 20 15:42:56 dh3930 kernel: nouveau :01:00.0: compiz[7682]: channel 15 killed! Aug 20 15:45:50 dh3930 kernel: INFO: task kworker/u24:4:14623 blocked for more than 120 seconds. Aug 20 15:45:50 dh3930 kernel: Not tainted 4.15.0-32-generic #35-Ubuntu Aug 20 15:45:50 dh3930 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Aug 20 15:45:50 dh3930 kernel: kworker/u24:4 D0 14623 2 0x8000 Aug 20 15:45:50 dh3930 kernel: Workqueue: events_unbound nv50_disp_atomic_commit_work [nouveau] Aug 20 15:45:50 dh3930 kernel: Call Trace: Aug 20 15:45:50 dh3930 kernel: __schedule+0x291/0x8a0 Aug 20 15:45:50 dh3930 kernel: schedule+0x2c/0x80 Aug 20 15:45:50 dh3930 kernel: schedule_timeout+0x1cf/0x350 Aug 20 15:45:50 dh3930 kernel: ? nvif_object_ioctl+0x47/0x50 [nouveau] Aug 20 15:45:50 dh3930 kernel: ? nouveau_bo_rd32+0x2a/0x30 [nouveau] Aug 20 15:45:50 dh3930 kernel: ? nv84_fence_read+0x2e/0x30 [nouveau] Aug 20 15:45:50 dh3930 kernel: ? nouveau_fence_no_signaling+0x2a/0x80 [nouveau] Aug 20 15:45:50 dh3930 kernel: dma_fence_default_wait+0x1c7/0x260 Aug 20 15:45:50 dh3930 kernel: ? dma_fence_release+0xa0/0xa0 Aug 20 15:45:50 dh3930 kernel: dma_fence_wait_timeout+0x3e/0xf0 Aug 20 15:45:50 dh3930 kernel: drm_atomic_helper_wait_for_fences+0x63/0xc0 [drm_kms_helper] Aug 20 15:45:50 dh3930 kernel: nv50_disp_atomic_commit_tail+0x55/0x3b10 [nouveau] Aug 20 15:45:50 dh3930 kernel: nv50_disp_atomic_commit_work+0x12/0x20 [nouveau] Aug 20 15:45:50 dh3930 kernel: process_one_work+0x1de/0x410 Aug 20 15:45:50 dh3930 kernel: worker_thread+0x32/0x410 Aug 20 15:45:50 dh3930 kernel: kthread+0x121/0x140 Aug 20 15:45:50 dh3930 kernel: ? process_one_work+0x410/0x410 Aug 20 15:45:50 dh3930 kernel: ? kthread_create_worker_on_cpu+0x70/0x70 Aug 20 15:45:50 dh3930 kernel: ret_from_fork+0x35/0x40 The 'blocked for more than 120 seconds' message and call trace repeated every ~121 seconds until I rebooted. At that point, the following additional line appeared with the 'blocked for more than 120 seconds' message: Aug 20 16:01:51 dh3930 kernel: nouveau :01:00.0: chromium- browse[14187]: failed to idle channel 20 [chromium-browse[14187]] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: david 2460 F pulseaudio /dev/snd/controlC0: david 2460 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Aug 20 16:07:40 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=9e4f3d6a-f1b3-40c0-8c97-97d861a7ce11 InstallationDate: Installed on 2016-10-24 (664 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-32-generic root=UUID=311cc681-166d-47bd-847d-f41c81578c1a ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-05-01 (110 days ago) dmi.bios.date: 05/06/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4701 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias:
[Kernel-packages] [Bug 1788044] Re: task kworker blocked for more than 120 seconds nouveau
Possible duplicate of #1723250 and/or #1723245 -- 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/1788044 Title: task kworker blocked for more than 120 seconds nouveau Status in linux package in Ubuntu: New Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: I was using chromium when the whole system GUI stopped responding at 15:42. This corresponds to the system journal at that point: Aug 20 15:42:56 dh3930 kernel: nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Aug 20 15:42:56 dh3930 kernel: nouveau :01:00.0: fifo: runlist 0: scheduled for recovery Aug 20 15:42:56 dh3930 kernel: nouveau :01:00.0: fifo: channel 15: killed Aug 20 15:42:56 dh3930 kernel: nouveau :01:00.0: fifo: engine 0: scheduled for recovery Aug 20 15:42:56 dh3930 kernel: nouveau :01:00.0: compiz[7682]: channel 15 killed! Aug 20 15:45:50 dh3930 kernel: INFO: task kworker/u24:4:14623 blocked for more than 120 seconds. Aug 20 15:45:50 dh3930 kernel: Not tainted 4.15.0-32-generic #35-Ubuntu Aug 20 15:45:50 dh3930 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Aug 20 15:45:50 dh3930 kernel: kworker/u24:4 D0 14623 2 0x8000 Aug 20 15:45:50 dh3930 kernel: Workqueue: events_unbound nv50_disp_atomic_commit_work [nouveau] Aug 20 15:45:50 dh3930 kernel: Call Trace: Aug 20 15:45:50 dh3930 kernel: __schedule+0x291/0x8a0 Aug 20 15:45:50 dh3930 kernel: schedule+0x2c/0x80 Aug 20 15:45:50 dh3930 kernel: schedule_timeout+0x1cf/0x350 Aug 20 15:45:50 dh3930 kernel: ? nvif_object_ioctl+0x47/0x50 [nouveau] Aug 20 15:45:50 dh3930 kernel: ? nouveau_bo_rd32+0x2a/0x30 [nouveau] Aug 20 15:45:50 dh3930 kernel: ? nv84_fence_read+0x2e/0x30 [nouveau] Aug 20 15:45:50 dh3930 kernel: ? nouveau_fence_no_signaling+0x2a/0x80 [nouveau] Aug 20 15:45:50 dh3930 kernel: dma_fence_default_wait+0x1c7/0x260 Aug 20 15:45:50 dh3930 kernel: ? dma_fence_release+0xa0/0xa0 Aug 20 15:45:50 dh3930 kernel: dma_fence_wait_timeout+0x3e/0xf0 Aug 20 15:45:50 dh3930 kernel: drm_atomic_helper_wait_for_fences+0x63/0xc0 [drm_kms_helper] Aug 20 15:45:50 dh3930 kernel: nv50_disp_atomic_commit_tail+0x55/0x3b10 [nouveau] Aug 20 15:45:50 dh3930 kernel: nv50_disp_atomic_commit_work+0x12/0x20 [nouveau] Aug 20 15:45:50 dh3930 kernel: process_one_work+0x1de/0x410 Aug 20 15:45:50 dh3930 kernel: worker_thread+0x32/0x410 Aug 20 15:45:50 dh3930 kernel: kthread+0x121/0x140 Aug 20 15:45:50 dh3930 kernel: ? process_one_work+0x410/0x410 Aug 20 15:45:50 dh3930 kernel: ? kthread_create_worker_on_cpu+0x70/0x70 Aug 20 15:45:50 dh3930 kernel: ret_from_fork+0x35/0x40 The 'blocked for more than 120 seconds' message and call trace repeated every ~121 seconds until I rebooted. At that point, the following additional line appeared with the 'blocked for more than 120 seconds' message: Aug 20 16:01:51 dh3930 kernel: nouveau :01:00.0: chromium- browse[14187]: failed to idle channel 20 [chromium-browse[14187]] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: david 2460 F pulseaudio /dev/snd/controlC0: david 2460 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Aug 20 16:07:40 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=9e4f3d6a-f1b3-40c0-8c97-97d861a7ce11 InstallationDate: Installed on 2016-10-24 (664 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-32-generic root=UUID=311cc681-166d-47bd-847d-f41c81578c1a ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-05-01 (110 days ago) dmi.bios.date: 05/06/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4701 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias:
[Kernel-packages] [Bug 1788044] [NEW] task kworker blocked for more than 120 seconds nouveau
Public bug reported: I was using chromium when the whole system GUI stopped responding at 15:42. This corresponds to the system journal at that point: Aug 20 15:42:56 dh3930 kernel: nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Aug 20 15:42:56 dh3930 kernel: nouveau :01:00.0: fifo: runlist 0: scheduled for recovery Aug 20 15:42:56 dh3930 kernel: nouveau :01:00.0: fifo: channel 15: killed Aug 20 15:42:56 dh3930 kernel: nouveau :01:00.0: fifo: engine 0: scheduled for recovery Aug 20 15:42:56 dh3930 kernel: nouveau :01:00.0: compiz[7682]: channel 15 killed! Aug 20 15:45:50 dh3930 kernel: INFO: task kworker/u24:4:14623 blocked for more than 120 seconds. Aug 20 15:45:50 dh3930 kernel: Not tainted 4.15.0-32-generic #35-Ubuntu Aug 20 15:45:50 dh3930 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Aug 20 15:45:50 dh3930 kernel: kworker/u24:4 D0 14623 2 0x8000 Aug 20 15:45:50 dh3930 kernel: Workqueue: events_unbound nv50_disp_atomic_commit_work [nouveau] Aug 20 15:45:50 dh3930 kernel: Call Trace: Aug 20 15:45:50 dh3930 kernel: __schedule+0x291/0x8a0 Aug 20 15:45:50 dh3930 kernel: schedule+0x2c/0x80 Aug 20 15:45:50 dh3930 kernel: schedule_timeout+0x1cf/0x350 Aug 20 15:45:50 dh3930 kernel: ? nvif_object_ioctl+0x47/0x50 [nouveau] Aug 20 15:45:50 dh3930 kernel: ? nouveau_bo_rd32+0x2a/0x30 [nouveau] Aug 20 15:45:50 dh3930 kernel: ? nv84_fence_read+0x2e/0x30 [nouveau] Aug 20 15:45:50 dh3930 kernel: ? nouveau_fence_no_signaling+0x2a/0x80 [nouveau] Aug 20 15:45:50 dh3930 kernel: dma_fence_default_wait+0x1c7/0x260 Aug 20 15:45:50 dh3930 kernel: ? dma_fence_release+0xa0/0xa0 Aug 20 15:45:50 dh3930 kernel: dma_fence_wait_timeout+0x3e/0xf0 Aug 20 15:45:50 dh3930 kernel: drm_atomic_helper_wait_for_fences+0x63/0xc0 [drm_kms_helper] Aug 20 15:45:50 dh3930 kernel: nv50_disp_atomic_commit_tail+0x55/0x3b10 [nouveau] Aug 20 15:45:50 dh3930 kernel: nv50_disp_atomic_commit_work+0x12/0x20 [nouveau] Aug 20 15:45:50 dh3930 kernel: process_one_work+0x1de/0x410 Aug 20 15:45:50 dh3930 kernel: worker_thread+0x32/0x410 Aug 20 15:45:50 dh3930 kernel: kthread+0x121/0x140 Aug 20 15:45:50 dh3930 kernel: ? process_one_work+0x410/0x410 Aug 20 15:45:50 dh3930 kernel: ? kthread_create_worker_on_cpu+0x70/0x70 Aug 20 15:45:50 dh3930 kernel: ret_from_fork+0x35/0x40 The 'blocked for more than 120 seconds' message and call trace repeated every ~121 seconds until I rebooted. At that point, the following additional line appeared with the 'blocked for more than 120 seconds' message: Aug 20 16:01:51 dh3930 kernel: nouveau :01:00.0: chromium- browse[14187]: failed to idle channel 20 [chromium-browse[14187]] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: david 2460 F pulseaudio /dev/snd/controlC0: david 2460 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Aug 20 16:07:40 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=9e4f3d6a-f1b3-40c0-8c97-97d861a7ce11 InstallationDate: Installed on 2016-10-24 (664 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-32-generic root=UUID=311cc681-166d-47bd-847d-f41c81578c1a ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-05-01 (110 days ago) dmi.bios.date: 05/06/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4701 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4701:bd05/06/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Also affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you
[Kernel-packages] [Bug 1787993] Re: [Bionic] Spectre v4 mitigation (Speculative Store Bypass Disable) support for arm64 using SMC firmware call to set a hardware chicken bit
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- 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/1787993 Title: [Bionic] Spectre v4 mitigation (Speculative Store Bypass Disable) support for arm64 using SMC firmware call to set a hardware chicken bit Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Track: Spectre v4 mitigation (Speculative Store Bypass Disable) support for arm64 using SMC firmware call to set a hardware chicken bit. Patch now in 4.18 to Bionic. [Test] [Fix] http://lkml.iu.edu/hypermail/linux/kernel/1805.2/05868.html -- From 4.18 -- eff0e9e1078e arm/arm64: smccc: Add SMCCC-specific return codes 8e2906245f1e arm64: Call ARCH_WORKAROUND_2 on transitions between EL0 and EL1 5cf9ce6e5ea5 arm64: Add per-cpu infrastructure to call ARCH_WORKAROUND_2 a725e3dda181 arm64: Add ARCH_WORKAROUND_2 probing a43ae4dfe56a arm64: Add 'ssbd' command-line option c32e1736ca03 arm64: ssbd: Add global mitigation state accessor 986372c4367f arm64: ssbd: Skip apply_ssbd if not using dynamic mitigation 647d0519b53f arm64: ssbd: Restore mitigation status on CPU resume 9dd9614f5476 arm64: ssbd: Introduce thread flag to control userspace mitigation 85478bab4091 arm64: KVM: Add HYP per-cpu accessors 55e3748e8902 arm64: KVM: Add ARCH_WORKAROUND_2 support for guests the first line b4f18c063a13 arm64: KVM: Handle guest's ARCH_WORKAROUND_2 requests 5d81f7dc9bca arm64: KVM: Add ARCH_WORKAROUND_2 discovery through ARCH_FEATURES_FUNC_ID [Regression Potential] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787993/+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 1788035] [NEW] nvme: avoid cqe corruption
Public bug reported: To address customer-reported NVMe issue with instance types (notably c5 and m5) that expose EBS volumes as NVMe devices, this commit from mainline v4.6 should be backported to Xenial: d783e0bd02e700e7a893ef4fa71c69438ac1c276 nvme: avoid cqe corruption when update at the same time as read dmesg sample: [Wed Aug 15 01:11:21 2018] nvme :00:1f.0: I/O 8 QID 1 timeout, aborting [Wed Aug 15 01:11:21 2018] nvme :00:1f.0: I/O 9 QID 1 timeout, aborting [Wed Aug 15 01:11:21 2018] nvme :00:1f.0: I/O 21 QID 2 timeout, aborting [Wed Aug 15 01:11:32 2018] nvme :00:1f.0: I/O 10 QID 1 timeout, aborting [Wed Aug 15 01:11:51 2018] nvme :00:1f.0: I/O 8 QID 1 timeout, reset controller [Wed Aug 15 01:11:51 2018] nvme nvme1: Abort status: 0x2 [Wed Aug 15 01:11:51 2018] nvme nvme1: Abort status: 0x2 [Wed Aug 15 01:11:51 2018] nvme nvme1: Abort status: 0x2 [Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 21 QID 2 [Wed Aug 15 01:11:51 2018] nvme :00:1f.0: completing aborted command with status: 0007 [Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector 83887751 [Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector 83887751 [Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 22 QID 2 [Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector 83887767 [Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector 83887767 [Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 23 QID 2 [Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector 83887769 [Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector 83887769 [Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 8 QID 1 [Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 9 QID 1 [Wed Aug 15 01:11:51 2018] nvme :00:1f.0: completing aborted command with status: 0007 [Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector 41943136 [Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 10 QID 1 [Wed Aug 15 01:11:51 2018] nvme :00:1f.0: completing aborted command with status: 0007 [Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector 6976 [Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 22 QID 1 [Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 23 QID 1 [Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 24 QID 1 [Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 25 QID 1 [Wed Aug 15 01:11:51 2018] nvme :00:1f.0: Cancelling I/O 2 QID 0 [Wed Aug 15 01:11:51 2018] nvme nvme1: Abort status: 0x7 [Wed Aug 15 01:11:51 2018] nvme :00:1f.0: completing aborted command with status: fffc [Wed Aug 15 01:11:51 2018] blk_update_request: I/O error, dev nvme1n1, sector 96 [Wed Aug 15 01:11:51 2018] XFS (nvme1n1): metadata I/O error: block 0x5000687 ("xlog_iodone") error 5 numblks 64 [Wed Aug 15 01:11:51 2018] XFS (nvme1n1): xfs_do_force_shutdown(0x2) called from line 1197 of file /build/linux-c2Z51P/linux-4.4.0/fs/xfs/xfs_log.c. Return address = 0xc075d428 [Wed Aug 15 01:11:51 2018] XFS (nvme1n1): xfs_log_force: error -5 returned. [Wed Aug 15 01:11:51 2018] XFS (nvme1n1): Log I/O Error Detected. Shutting down filesystem [Wed Aug 15 01:11:51 2018] XFS (nvme1n1): Please umount the filesystem and rectify the problem(s) [Wed Aug 15 01:11:51 2018] Buffer I/O error on dev nvme1n1, logical block 872, lost async page write [Wed Aug 15 01:11:51 2018] XFS (nvme1n1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. [Wed Aug 15 01:11:51 2018] XFS (nvme1n1): xfs_iunlink_remove: xfs_imap_to_bp returned error -5. [Wed Aug 15 01:11:51 2018] Buffer I/O error on dev nvme1n1, logical block 873, lost async page write [Wed Aug 15 01:11:51 2018] Buffer I/O error on dev nvme1n1, logical block 874, lost async page write [Wed Aug 15 01:11:51 2018] Buffer I/O error on dev nvme1n1, logical block 875, lost async page write [Wed Aug 15 01:11:51 2018] Buffer I/O error on dev nvme1n1, logical block 876, lost async page write [Wed Aug 15 01:11:51 2018] Buffer I/O error on dev nvme1n1, logical block 877, lost async page write [Wed Aug 15 01:11:51 2018] Buffer I/O error on dev nvme1n1, logical block 878, lost async page write [Wed Aug 15 01:11:51 2018] Buffer I/O error on dev nvme1n1, logical block 879, lost async page write [Wed Aug 15 01:11:51 2018] Buffer I/O error on dev nvme1n1, logical block 880, lost async page write [Wed Aug 15 01:11:51 2018] Buffer I/O error on dev nvme1n1, logical block 881, lost async page write [Wed Aug 15 01:11:51 2018] XFS (nvme1n1): metadata I/O error: block 0x5000697 ("xlog_iodone") error 5 numblks 64 [Wed Aug 15 01:11:51 2018] XFS (nvme1n1): xfs_log_force: error -5 returned. [Wed Aug 15 01:11:51 2018] XFS (nvme1n1): xfs_do_force_shutdown(0x2) called from line 1197 of file /build/linux-c2Z51P/linux-4.4.0/fs/xfs/xfs_log.c. Return
[Kernel-packages] [Bug 1787861] Re: Displays not detected/positioned correctly when disconnected/reconnected
Added 'xrandr' output after the AV Receiver and TV are turned off--note that VGA-0 has turned itself on, which shouldn't happen. ** Attachment added: "xrandr output after turning of HDMI accessories" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787861/+attachment/5178199/+files/xrandr.output2 -- 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/1787861 Title: Displays not detected/positioned correctly when disconnected/reconnected Status in linux package in Ubuntu: Confirmed Bug description: I just upgraded from Ubuntu 16.04 LTS to 18.04 LTS. Previously, this was all working correctly: I have 3 displays connected to an nVidia GT 730. VGA-0 (an old 21-inch CRT) is never enabled (just haven't got around to removing it). DVI-D-0 is the primary display, always connected and turned on, in 1920x1080 60hz. HDMI-0 is a secondary display (actually, linked to my AV receiver and then to my 55" HDTV), and it is turned on when I want the big screen (1920x1080 60hz, positioned to the left of the primary), turned off the rest of the time. Now, whenever I turn off my secondary HDMI display, my third (VGA) display is automatically enabled. Furthermore, when I then turn the secondary display back on, it is set to the wrong mode (interlaced at 30 Hz instead of progressive scan at 60 Hz) and in the wrong position (to the right of the main display, when I want it to the left). Running the correct 'xrandr' command to reset all three displays to the correct conditions instead results in random behavior--instead of a 3840x1080 screen, with the primary display offset to +1920x0, I usually end up with both displays set to span the entire 3840x1080 area, offset to +0x0 (so they're mirroring each other). Sometimes the VGA display remains turned on with a random (not actually displayable) resolution, sometimes it does not. Trying to force the displays into the correct mode with further 'xrandr' commands does not work; I have to reboot the machine to get the displays back to where they belong. This is the 'xrandr' command that SHOULD reset the displays to the correct modes/positions (the primary DVI display is already in the correct mode, so I don't specify that): xrandr --output VGA-0 --off --output DVI-D-0 --primary --output HDMI-0 --size 1920x1080 --rate 60 --left-of DVI-D-0 Occasionally, it does work correctly, but most of the time, it does not (see above). Under 16.04 LTS, I did have an issue for a long time where the secondary HDMI display would be set to an interlaced mode when I turned it back on (but otherwise, everything was correct--and a simple 'xrandr -output HDMI-0 --auto' fixed it); that problem was corrected with a kernel upgrade a short time ago (maybe 3 months?-- unfortunately, I never filed a bug and just lived with it, so I'm not sure exactly when the problem went away, either). Attached is the output of 'xrandr' with everything set correctly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jonathan 2183 F pulseaudio /dev/snd/controlC1: jonathan 2183 F pulseaudio /dev/snd/controlC0: jonathan 2183 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Aug 19 15:38:09 2018 HibernationDevice: RESUME=UUID=e0d7d646-78bf-474b-916a-ad6f8523c1b5 InstallationDate: Installed on 2015-08-17 (1098 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=2cd20c22-0c69-4ae2-b81c-11fd8501a2ec ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-15 (4 days ago) dmi.bios.date: 06/14/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0307 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A88T-M LE 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:
[Kernel-packages] [Bug 1787191] Re: Crash due to BUG: Bad page map in process X & BUG: Bad rss-counter state X
*** This bug is a duplicate of bug 1787127 *** https://bugs.launchpad.net/bugs/1787127 our issue with this kernel was also addressed by 3.13.0-156 -- 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/1787191 Title: Crash due to BUG: Bad page map in process X & BUG: Bad rss-counter state X Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Bug description: Multiple SuperMicro based servers running 14.04 are experiencing continual kernel errors since upgrading to 3.13.0-155 which quickly leads to the system becoming unresponsive. The errors start immediately after boot. Small excerpt from the attached kern.log: Aug 15 09:54:15 server kernel: [0.00] CPU0 microcode updated early to revision 0x713, date = 2018-01-26 ... Aug 15 09:54:17 server kernel: [ 14.381553] ipmi device interface Aug 15 09:54:17 server kernel: [ 14.610493] NFS: Registering the id_resolver key type Aug 15 09:54:17 server kernel: [ 14.610504] Key type id_resolver registered Aug 15 09:54:17 server kernel: [ 14.610505] Key type id_legacy registered Aug 15 09:54:26 server kernel: [ 23.412042] BUG: Bad page map in process plymouthd pte:800860a3d966 pmd:465c17067 Aug 15 09:54:26 server kernel: [ 23.442867] addr:7fb8cc137000 vm_flags:08100073 anon_vma:880866695ab0 mapping:88086543a870 index:7 Aug 15 09:54:26 server kernel: [ 23.472375] vma->vm_ops->fault: filemap_fault+0x0/0x400 Aug 15 09:54:26 server kernel: [ 23.484454] vma->vm_file->f_op->mmap: ext4_file_mmap+0x0/0x60 Aug 15 09:54:26 server kernel: [ 23.496669] CPU: 4 PID: 523 Comm: plymouthd Tainted: GB 3.13.0-155-generic #205-Ubuntu Aug 15 09:54:26 server kernel: [ 23.496670] Hardware name: Supermicro X9DRD-iF/LF/X9DRD-iF, BIOS 3.0b 12/05/2013 Aug 15 09:54:26 server kernel: [ 23.496671] 880465f37d00 8173983f 7fb8cc137000 Aug 15 09:54:26 server kernel: [ 23.496675] 8808652c63c0 880465f37d50 8117e374 800860a3d966 Aug 15 09:54:26 server kernel: [ 23.496678] 000465c17067 0007 880465c179b8 800860a3d966 Aug 15 09:54:26 server kernel: [ 23.496681] Call Trace: Aug 15 09:54:26 server kernel: [ 23.496684] [] dump_stack+0x64/0x80 Aug 15 09:54:26 server kernel: [ 23.496687] [] print_bad_pte+0x1a4/0x250 Aug 15 09:54:26 server kernel: [ 23.496690] [] vm_normal_page+0x6e/0x80 Aug 15 09:54:26 server kernel: [ 23.496701] [] change_protection_range+0x55f/0x720 Aug 15 09:54:26 server kernel: [ 23.496706] [] change_protection+0x65/0xb0 Aug 15 09:54:26 server kernel: [ 23.496709] [] change_prot_numa+0x1b/0x40 Aug 15 09:54:26 server kernel: [ 23.496712] [] task_numa_work+0x1d2/0x300 Aug 15 09:54:26 server kernel: [ 23.496714] [] task_work_run+0xaf/0xd0 Aug 15 09:54:26 server kernel: [ 23.496717] [] do_notify_resume+0x97/0xb0 Aug 15 09:54:26 server kernel: [ 23.496720] [] int_signal+0x12/0x17 ... Aug 15 09:54:54 server kernel: [ 50.902769] BUG: Bad rss-counter state mm:880466869880 idx:1 val:338 Aug 15 09:55:25 server kernel: [ 82.513872] BUG: Bad rss-counter state mm:880866d6b800 idx:1 val:249 ... Aug 15 09:56:30 server kernel: [ 144.954186] CPU: 18 PID: 4139 Comm: php-cgi Tainted: GB 3.13.0-155-generic #205-Ubuntu Aug 15 09:56:30 server kernel: [ 144.954189] 880467cefd00 8173983f 02d2e000 Aug 15 09:56:30 server kernel: [ 144.954193] 000468950067 2d2e 880468950970 80042a764966 Aug 15 09:56:30 server kernel: [ 144.954195] [] dump_stack+0x64/0x80 Aug 15 09:56:30 server kernel: [ 144.954199] [] vm_normal_page+0x6e/0x80 Aug 15 09:56:30 server kernel: [ 144.954203] [] change_protection+0x65/0xb0 Aug 15 09:56:30 server kernel: [ 144.954207] [] change_prot_numa+0x1b/0x40 Aug 15 09:56:30 server kernel: [ 144.954211] [] task_work_run+0xaf/0xd0 Aug 15 09:56:30 server kernel: [ 144.954214] [] retint_signal+0x48/0x86 Aug 15 09:56:30 server kernel: [ 144.954216] addr:02d2f000 vm_flags:08100073 anon_vma:880467651c18 mapping: (null) index:2d2f Aug 15 09:56:30 server kernel: [ 144.954218] CPU: 18 PID: 4139 Comm: php-cgi Tainted: GB 3.13.0-155-generic #205-Ubuntu Aug 15 09:56:30 server kernel: [ 144.954218] Hardware name: Supermicro X9DRD-iF/LF/X9DRD-iF, BIOS 3.0b 12/05/2013 Aug 15 09:56:30 server kernel: [ 144.954221] 880467cefd00 8173983f 02d2f000 Aug 15 09:56:30 server kernel: [ 144.954223] 880868111800 880467cefd50 8117e374 80042a765966 Aug 15 09:56:30 server kernel: [ 144.954225] 000468950067 2d2f 880468950978 80042a765966 Aug
[Kernel-packages] [Bug 1776155] Re: Touchpad detected as SYNA3602, does not work at all.
Does not seem to be exactly the same. But do you suggest I try the same fix anyway? -- 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/1776155 Title: Touchpad detected as SYNA3602, does not work at all. Status in linux package in Ubuntu: Confirmed Bug description: On my cheaper-end slimline laptop/netbook the touchpad is (I think wrongly) detected by Linux to be the SYNA 3602. Anyway it does not work at all, neither touchpad nor buttons. Freshly installed Ubuntu 18.04 system. External mouse works fine. It seems that there is a bug reported on a similar issue, although I can not confirm that my touchpad hardware is exactly the same: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688625 If so, there may be a whole new generation of slimline Windows 10 netbooks that have this problem. martin@alanah:~$ cat /proc/bus/input/devices I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input2 U: Uniq= H: Handlers=sysrq kbd event2 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0018 Vendor=0911 Product=5288 Version=0100 N: Name="SYNA3602:00 0911:5288 Touchpad" P: Phys=i2c-SYNA3602:00 S: Sysfs=/devices/pci:00/:00:16.1/i2c_designware.1/i2c-5/i2c-SYNA3602:00/0018:0911:5288.0001/input/input15 U: Uniq= H: Handlers=mouse0 event14 B: PROP=5 B: EV=1b B: KEY=e420 3 0 0 0 0 B: ABS=2608003 B: MSC=20 I: Bus=0003 Vendor=045e Product=00b9 Version=0111 N: Name="Microsoft Microsoft USB Wireless Mouse" P: Phys=usb-:00:15.0-1/input0 S: Sysfs=/devices/pci:00/:00:15.0/usb1/1-1/1-1:1.0/0003:045E:00B9.0002/input/input16 U: Uniq= H: Handlers=mouse1 event15 B: PROP=0 B: EV=17 B: KEY=1f 0 0 0 0 B: REL=1c3 B: MSC=10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Mon Jun 11 07:57:56 2018 InstallationDate: Installed on 2018-04-25 (46 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1536 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-25 (48 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: Multicom Multicom U230 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=c7a82fee-6e9d-491d-a38d-f5d6bdb4a930 ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: ORO10x.WP313P.NHNAUHL01 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrORO10x.WP313P.NHNAUHL01:bd09/15/2017:svnMulticom:pnMulticomU230:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: U-series dmi.product.name: Multicom U230 dmi.product.version: Default string dmi.sys.vendor: Multicom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776155/+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 1766076] Re: USB over thunderbolt turns off every once in a while
@Branan any luck? -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in linux package in Ubuntu: Expired Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd [279389.949983] usb usb3: SerialNumber: :0e:00.0 [279389.950117] hub 3-0:1.0: USB hub found
[Kernel-packages] [Bug 1787251] Re: No sound devices after booting 4.15.0-32-generic
Correct. This turned out to actually be an issue with the installed image having proposed enabled by default which allowed the machine to get into a weird state. It turned out not to be a bug in kernel, packaging, or unattended-upgrades. -- 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/1787251 Title: No sound devices after booting 4.15.0-32-generic Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: There is no sound and no sound devices appear present (either internal or USB devices) after booting 4.15.0-32-generic. If I boot back into -31, everything works normally. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair hid_plantronics i915 sdhci_pci sdhci wmi ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME Date: Wed Aug 15 12:02:10 2018 HibernationDevice: RESUME=UUID=55a42c82-50bf-4e75-a133-dbd3aa93611b InstallationDate: Installed on 2018-07-24 (22 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/16/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-406 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0: --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dean 9554 F pulseaudio /dev/snd/controlC1: dean 9554 F pulseaudio /dev/snd/controlC0: dean 9554 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=55a42c82-50bf-4e75-a133-dbd3aa93611b InstallationDate: Installed on 2018-07-24 (22 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-31-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-31.33-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-31-generic N/A linux-backports-modules-4.15.0-31-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/16/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-406 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787251/+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 1787251] Re: No sound devices after booting 4.15.0-32-generic
Dean and I decided last week that this is most likely a bug in the unattended-upgrades code. I'm marking the Bionic linux task as invalid since it doesn't look like a bug in the kernel packaging. ** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1787251 Title: No sound devices after booting 4.15.0-32-generic Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: There is no sound and no sound devices appear present (either internal or USB devices) after booting 4.15.0-32-generic. If I boot back into -31, everything works normally. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair hid_plantronics i915 sdhci_pci sdhci wmi ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME Date: Wed Aug 15 12:02:10 2018 HibernationDevice: RESUME=UUID=55a42c82-50bf-4e75-a133-dbd3aa93611b InstallationDate: Installed on 2018-07-24 (22 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/16/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-406 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0: --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dean 9554 F pulseaudio /dev/snd/controlC1: dean 9554 F pulseaudio /dev/snd/controlC0: dean 9554 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=55a42c82-50bf-4e75-a133-dbd3aa93611b InstallationDate: Installed on 2018-07-24 (22 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-31-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-31.33-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-31-generic N/A linux-backports-modules-4.15.0-31-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/16/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-406 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787251/+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 1787982] Re: linux: 3.13.0-157.207 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787982 Title: linux: 3.13.0-157.207 -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: New 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 upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid 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: bug 1787983 (linux-lts-trusty) derivatives: kernel-stable-phase:Uploaded kernel-stable-phase-changed:Monday, 20. August 2018 17:00 UTC -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787982/+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 1787983] Re: linux-lts-trusty: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1787982 + kernel-stable-phase-changed:Monday, 20. August 2018 17:30 UTC + kernel-stable-phase:Packaging ** 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: 1787982 - kernel-stable-phase-changed:Monday, 20. August 2018 17:30 UTC - kernel-stable-phase:Packaging + phase: Packaging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1787983 Title: linux-lts-trusty: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid 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: 1787982 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787983/+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 1788004] [NEW] File System inaccessible after 18.04 upgrade
Public bug reported: ZPool was functioning before upgrading to Ubuntu 18.04. Unfortunately didn't confirm pool working before upgrading the pool so can't roll back. Can't access file system anymore, though a scrub did succeed. Simple 'ls -la' segfaults, and this shows up in dmesg: [ 320.449464] detected buffer overflow in memmove [ 320.449489] [ cut here ] [ 320.449492] kernel BUG at /build/linux-wuhukg/linux-4.15.0/lib/string.c:1052! [ 320.449503] invalid opcode: [#1] SMP PTI [ 320.449506] Modules linked in: thunderbolt nls_iso8859_1 zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) snd_ hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_hda_codec_ca0132 irqbypass crct10dif_pclmu l crc32_pclmul ghash_clmulni_intel pcbc aesni_intel snd_hda_intel snd_hda_codec aes_x86_64 crypto_simd snd_hda_core glue_helper crypt d intel_cstate snd_hwdep intel_rapl_perf snd_pcm intel_wmi_thunderbolt snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_de vice snd_timer snd soundcore input_leds mac_hid mei_me mei shpchp acpi_pad intel_pch_thermal sch_fq_codel vhba(OE) parport_pc ppdev l p parport ip_tables x_tables autofs4 hid_generic usbhid hid i915 mxm_wmi e1000e i2c_algo_bit ptp drm_kms_helper pps_core syscopyarea sysfillrect [ 320.449599] sysimgblt fb_sys_fops alx drm mdio ahci libahci wmi video [ 320.449617] CPU: 3 PID: 3202 Comm: updatedb.mlocat Tainted: PW OE 4.15.0-32-generic #35-Ubuntu [ 320.449621] Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./Z170X-Gaming 7, BIOS F8 08/26/2016 [ 320.449632] RIP: 0010:fortify_panic+0x13/0x22 [ 320.449636] RSP: 0018:a85fc5d27898 EFLAGS: 00010282 [ 320.449641] RAX: 0023 RBX: a85fc5d279a8 RCX: [ 320.449645] RDX: RSI: 97dc51d96498 RDI: 97dc51d96498 [ 320.449649] RBP: a85fc5d27898 R08: R09: 058c [ 320.449652] R10: 97dc2916501c R11: b895380d R12: 0001 [ 320.449656] R13: 97dc2a717460 R14: 0070 R15: 97dc21e40300 [ 320.449661] FS: 7fb9bd9c4540() GS:97dc51d8() knlGS: [ 320.449665] CS: 0010 DS: ES: CR0: 80050033 [ 320.449669] CR2: 7fa69800e778 CR3: 000812c88005 CR4: 003606e0 [ 320.449673] DR0: DR1: DR2: [ 320.449677] DR3: DR6: fffe0ff0 DR7: 0400 [ 320.449680] Call Trace: [ 320.449779] zfs_acl_node_read.constprop.15+0x33d/0x340 [zfs] [ 320.449867] zfs_zaccess_aces_check+0x96/0x380 [zfs] [ 320.449874] ? mutex_lock+0x12/0x40 [ 320.449879] ? _cond_resched+0x19/0x40 [ 320.449929] ? arc_buf_access+0x14a/0x270 [zfs] [ 320.449977] ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs] [ 320.450056] zfs_zaccess_common+0xda/0x1f0 [zfs] [ 320.450062] ? _cond_resched+0x19/0x40 [ 320.450139] zfs_zaccess+0xd4/0x3d0 [zfs] [ 320.450235] ? rrw_enter_read_impl+0xae/0x160 [zfs] [ 320.450327] zfs_lookup+0x1c5/0x3a0 [zfs] [ 320.450415] zpl_lookup+0xc9/0x1e0 [zfs] [ 320.450424] lookup_slow+0xab/0x170 [ 320.450432] walk_component+0x1c3/0x470 [ 320.450438] ? _cond_resched+0x19/0x40 [ 320.450444] ? mutex_lock+0x12/0x40 [ 320.450451] path_lookupat+0x84/0x1f0 [ 320.450458] ? ___slab_alloc+0xf2/0x4b0 [ 320.450545] ? zfs_readdir+0x267/0x460 [zfs] [ 320.450552] ? ___slab_alloc+0xf2/0x4b0 [ 320.450560] filename_lookup+0xb6/0x190 [ 320.450569] ? __check_object_size+0xaf/0x1b0 [ 320.450578] ? strncpy_from_user+0x4d/0x170 [ 320.450586] user_path_at_empty+0x36/0x40 [ 320.450592] ? user_path_at_empty+0x36/0x40 [ 320.450600] vfs_statx+0x76/0xe0 [ 320.450606] ? _cond_resched+0x19/0x40 [ 320.450611] ? dput.part.22+0x2d/0x1e0 [ 320.450619] SYSC_newlstat+0x3d/0x70 [ 320.450628] ? SyS_poll+0x9b/0x130 [ 320.450635] ? SyS_poll+0x9b/0x130 [ 320.450643] SyS_newlstat+0xe/0x10 [ 320.450651] do_syscall_64+0x73/0x130 [ 320.450659] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 320.450664] RIP: 0033:0x7fb9bd4d2815 [ 320.450669] RSP: 002b:7ffe3d613f38 EFLAGS: 0246 ORIG_RAX: 0006 [ 320.450675] RAX: ffda RBX: 5632906b5059 RCX: 7fb9bd4d2815 [ 320.450679] RDX: 7ffe3d613fb0 RSI: 7ffe3d613fb0 RDI: 5632906b5059 [ 320.450684] RBP: 5632906ab600 R08: 0073 R09: 0073 [ 320.450688] R10: R11: 0246 R12: 7ffe3d614190 [ 320.450692] R13: R14: 7ffe3d614180 R15: [ 320.450697] Code: e0 4c 89 e2 e8 61 6a 00 00 42 c6 04 20 00 48 89 d8 5b 41 5c 5d c3 0f 0b 55 48 89 fe 48 c7 c7 f0 10 1a b8 48 89 e5 e8 7f cf 76 ff <0f> 0b 90 90 90 90 90 90 90 90 90 90 90 90 90 55 31 c9 48 89 fa [ 320.450788] RIP: fortify_panic+0x13/0x22 RSP: a85fc5d27898 [ 320.450794] ---[ end trace 8e2de80852d9eb6a ]---
[Kernel-packages] [Bug 1764645] Re: Bluetooth not working
Ooops - sorry. My 4.15.0-31 is still the proposed, working, version, so I have bluetooth again. For those who never got the proposed version 31, what do they do if, as for me, version 33 is a non-starter? -- 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/1764645 Title: Bluetooth not working Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: == SRU Justification == A regression was discovered in Bionic. The regression was introduced by mainline commit f44cb4b19ed4, which then made it's way into Bionic in 4.15.0-14 as commit c91729972ac6 via stable updates. This regression is fixed by mainline commit 803cdb8ce584. Commit 803cdb8ce584 was also cc'd to stable. However, it has not landed in upstream stable 4.15 or Bionic. == Fix == 803cdb8ce584 ("Bluetooth: btusb: Apply QCA Rome patches for some ATH3012 models") == Regression Potential == Low. This fix has also been cc'd to upstream stable, so it has had additonal upstream review. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. I've installed the Ubuntu Bionic Beta 2 and everything works fine but the bluetooth (perfectly working with Xenial). In bluetooth control panel the slider is impossible to move to "on". 1) Ubuntu Release (via 'lsb_release -rd') Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2) Version of package (apt-cache policy gnome-bluetooth) gnome-bluetooth: Installato: 3.28.0-2 Candidato: 3.28.0-2 Tabella versione: *** 3.28.0-2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen I expected to switch on the bluetooth. 4) What happened instead Bluetooth won't switch on. 5) Output of rfkill list is: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 6) Output of lspci -knn | grep Net -A3; lsusb; dmesg | grep -i blue is: 03:00.0 Network controller [0280]: Qualcomm Atheros AR9462 Wireless Network Adapter [168c:0034] (rev 01) Subsystem: Bigfoot Networks, Inc. Killer Wireless-N 1202 Half- size Mini PCIe Card [1a56:2003] Kernel driver in use: ath9k Kernel modules: ath9k 04:00.0 Ethernet controller [0200]: Qualcomm Atheros QCA8171 Gigabit Ethernet [1969:10a1] (rev 10) Bus 002 Device 002: ID 8087:8000 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8008 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 04f2:b414 Chicony Electronics Co., Ltd Bus 003 Device 003: ID 0cf3:3004 Atheros Communications, Inc. AR3012 Bluetooth 4.0 Bus 003 Device 002: ID 0b05:17c4 ASUSTek Computer, Inc. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [ 17.715399] Bluetooth: Core ver 2.22 [ 17.715414] Bluetooth: HCI device and connection manager initialized [ 17.715416] Bluetooth: HCI socket layer initialized [ 17.715418] Bluetooth: L2CAP socket layer initialized [ 17.715422] Bluetooth: SCO socket layer initialized [ 17.723207] Bluetooth: hci0: don't support firmware rome 0x1102 [ 18.600648] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 18.600649] Bluetooth: BNEP filters: protocol multicast [ 18.600651] Bluetooth: BNEP socket layer initialized ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-generic 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stormy 1484 F pulseaudio /dev/snd/controlC0: stormy 1484 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Apr 17 08:46:30 2018 HibernationDevice: RESUME=UUID=3f513ca9-6817-4099-9718-fee68d68ec11 InstallationDate: Installed on 2018-04-16 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: ASUSTeK COMPUTER INC. G750JH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions:
[Kernel-packages] [Bug 1787982] Re: linux: 3.13.0-157.207 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package 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 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: bug 1787983 (linux-lts-trusty) derivatives: + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Monday, 20. August 2018 17:00 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1787983 (linux-lts-trusty) derivatives: kernel-stable-phase:Uploaded kernel-stable-phase-changed:Monday, 20. August 2018 17:00 UTC + + -- swm properties -- + phase: Uploaded -- 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/1787982 Title: linux: 3.13.0-157.207 -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: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: In Progress 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 upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid 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: bug 1787983 (linux-lts-trusty) derivatives: kernel-stable-phase:Uploaded kernel-stable-phase-changed:Monday, 20. August 2018 17:00 UTC -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787982/+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 1787988] Re: linux: 4.17.0-9.10 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de Souza Cascardo (cascardo) -- 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/1787988 Title: linux: 4.17.0-9.10 -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 Cosmic: Confirmed Bug description: This bug is for tracking the 4.17.0-9.10 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 kernel-phase:Packaging kernel-phase-changed:Monday, 20. August 2018 16:33 UTC -- swm properties -- phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787988/+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 1787993] 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 1787993 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787993 Title: [Bionic] Spectre v4 mitigation (Speculative Store Bypass Disable) support for arm64 using SMC firmware call to set a hardware chicken bit Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Track: Spectre v4 mitigation (Speculative Store Bypass Disable) support for arm64 using SMC firmware call to set a hardware chicken bit. Patch now in 4.18 to Bionic. [Test] [Fix] http://lkml.iu.edu/hypermail/linux/kernel/1805.2/05868.html -- From 4.18 -- eff0e9e1078e arm/arm64: smccc: Add SMCCC-specific return codes 8e2906245f1e arm64: Call ARCH_WORKAROUND_2 on transitions between EL0 and EL1 5cf9ce6e5ea5 arm64: Add per-cpu infrastructure to call ARCH_WORKAROUND_2 a725e3dda181 arm64: Add ARCH_WORKAROUND_2 probing a43ae4dfe56a arm64: Add 'ssbd' command-line option c32e1736ca03 arm64: ssbd: Add global mitigation state accessor 986372c4367f arm64: ssbd: Skip apply_ssbd if not using dynamic mitigation 647d0519b53f arm64: ssbd: Restore mitigation status on CPU resume 9dd9614f5476 arm64: ssbd: Introduce thread flag to control userspace mitigation 85478bab4091 arm64: KVM: Add HYP per-cpu accessors 55e3748e8902 arm64: KVM: Add ARCH_WORKAROUND_2 support for guests the first line b4f18c063a13 arm64: KVM: Handle guest's ARCH_WORKAROUND_2 requests 5d81f7dc9bca arm64: KVM: Add ARCH_WORKAROUND_2 discovery through ARCH_FEATURES_FUNC_ID [Regression Potential] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787993/+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 1787993] [NEW] [Bionic] Spectre v4 mitigation (Speculative Store Bypass Disable) support for arm64 using SMC firmware call to set a hardware chicken bit
Public bug reported: [Impact] Track: Spectre v4 mitigation (Speculative Store Bypass Disable) support for arm64 using SMC firmware call to set a hardware chicken bit. Patch now in 4.18 to Bionic. [Test] [Fix] http://lkml.iu.edu/hypermail/linux/kernel/1805.2/05868.html -- From 4.18 -- eff0e9e1078e arm/arm64: smccc: Add SMCCC-specific return codes 8e2906245f1e arm64: Call ARCH_WORKAROUND_2 on transitions between EL0 and EL1 5cf9ce6e5ea5 arm64: Add per-cpu infrastructure to call ARCH_WORKAROUND_2 a725e3dda181 arm64: Add ARCH_WORKAROUND_2 probing a43ae4dfe56a arm64: Add 'ssbd' command-line option c32e1736ca03 arm64: ssbd: Add global mitigation state accessor 986372c4367f arm64: ssbd: Skip apply_ssbd if not using dynamic mitigation 647d0519b53f arm64: ssbd: Restore mitigation status on CPU resume 9dd9614f5476 arm64: ssbd: Introduce thread flag to control userspace mitigation 85478bab4091 arm64: KVM: Add HYP per-cpu accessors 55e3748e8902 arm64: KVM: Add ARCH_WORKAROUND_2 support for guests the first line b4f18c063a13 arm64: KVM: Handle guest's ARCH_WORKAROUND_2 requests 5d81f7dc9bca arm64: KVM: Add ARCH_WORKAROUND_2 discovery through ARCH_FEATURES_FUNC_ID [Regression Potential] ** Affects: linux (Ubuntu) Importance: High Status: Incomplete ** Tags: bionic cavium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787993 Title: [Bionic] Spectre v4 mitigation (Speculative Store Bypass Disable) support for arm64 using SMC firmware call to set a hardware chicken bit Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Track: Spectre v4 mitigation (Speculative Store Bypass Disable) support for arm64 using SMC firmware call to set a hardware chicken bit. Patch now in 4.18 to Bionic. [Test] [Fix] http://lkml.iu.edu/hypermail/linux/kernel/1805.2/05868.html -- From 4.18 -- eff0e9e1078e arm/arm64: smccc: Add SMCCC-specific return codes 8e2906245f1e arm64: Call ARCH_WORKAROUND_2 on transitions between EL0 and EL1 5cf9ce6e5ea5 arm64: Add per-cpu infrastructure to call ARCH_WORKAROUND_2 a725e3dda181 arm64: Add ARCH_WORKAROUND_2 probing a43ae4dfe56a arm64: Add 'ssbd' command-line option c32e1736ca03 arm64: ssbd: Add global mitigation state accessor 986372c4367f arm64: ssbd: Skip apply_ssbd if not using dynamic mitigation 647d0519b53f arm64: ssbd: Restore mitigation status on CPU resume 9dd9614f5476 arm64: ssbd: Introduce thread flag to control userspace mitigation 85478bab4091 arm64: KVM: Add HYP per-cpu accessors 55e3748e8902 arm64: KVM: Add ARCH_WORKAROUND_2 support for guests the first line b4f18c063a13 arm64: KVM: Handle guest's ARCH_WORKAROUND_2 requests 5d81f7dc9bca arm64: KVM: Add ARCH_WORKAROUND_2 discovery through ARCH_FEATURES_FUNC_ID [Regression Potential] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787993/+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 843431] Re: Logitech camera microphone does not work / makes "chipmunk" sound
Hi, due to a computer failure, i'm not able to test this right now... and i don't known when it could be possible. I apologize for that. -- 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/843431 Title: Logitech camera microphone does not work / makes "chipmunk" sound Status in Linux: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Oneiric: Fix Released Status in linux package in Debian: New Bug description: Did not know which application to log so feel free to let me know and I'll upload the correct log. In Natty, this mic worked great. Now, in the sound control panel, the mic does not show any input level at all and sound recorder does not record any sound. edit: I can also confirm the same behavior as Alex Popovskiy. It either works but plays too fast (high pitch) or it doesn't work at all. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.1.91-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 Uname: Linux 3.0.0-10-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Tue Sep 6 20:31:13 2011 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.22.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alex 1594 F pulseaudio /dev/snd/controlC0: alex 1594 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xf9ef4000 irq 16' Mixer name : 'VIA VT1708S' Components : 'HDA:11060397,18490397,0010' Controls : 36 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'U0x46d0x809'/'USB Device 0x46d:0x809 at usb-:00:13.2-6, high speed' Mixer name : 'USB Mixer' Components : 'USB046d:0809' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 6400 Mono: Capture 6400 [100%] [31.00dB] [on] DistroRelease: Ubuntu 11.10 HibernationDevice: RESUME=UUID=8ccfea11-7ba8-42e2-bc75-a37e20a8c83c InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-10-generic root=UUID=3c8a3aec-07c0-47ad-bab8-0365abb68a42 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 RelatedPackageVersions: linux-restricted-modules-3.0.0-10-generic N/A linux-backports-modules-3.0.0-10-generic N/A linux-firmware1.60 Tags: oneiric running-unity Uname: Linux 3.0.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 09/07/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.70 dmi.board.name: M3A770DE dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd09/07/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnM3A770DE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/843431/+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 1785675] Comment bridged from LTC Bugzilla
--- Comment From gwal...@br.ibm.com 2018-08-20 12:31 EDT--- Joseph, This a kind of test that needs some interventions in the kernels of host and guest, and maybe in the Qemu either to analysis the memory area if affected. I believe just a sanity test with page size changing between host and guest will be enough to validate it. I have re-built a kernel package with the patch from source and changing the PAGESIZE support to 4k, then the environment was running with 4k and the guest with 64k without problems. -- 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/1785675 Title: Security fix: check if IOMMU page is contained in the pinned physical page Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: == Comment: #0 - Leonardo Augusto Guimaraes Garcia - 2018-08-06 12:27:59 == Please, add the following security fix to the distro kernel: 76fa4975f3ed KVM: PPC: Check if IOMMU page is contained in the pinned physical page Also already available in the 4.14 stable tree: 58113603a4ea KVM: PPC: Check if IOMMU page is contained in the pinned physical page And in the 4.17 stable tree: 970e28cb2c7a KVM: PPC: Check if IOMMU page is contained in the pinned physical page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1785675/+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 1432869] Re: No wireless access for BCM 43162
tazesimit (simitcii), it will help immensely if you use the computer the problem is reproducible with, and provide necessary debugging logs by filing a new report with Ubuntu via a terminal: ubuntu-bug linux Please feel free to subscribe me to it. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1432869 Title: No wireless access for BCM 43162 Status in linux package in Ubuntu: Incomplete Bug description: No connectivity on 14.04.2 for Lenovo Edge E555 using a BCM43162 wireless adapter. Here is what I got with lspci -nnk | grep -iA2 net Network Controller [0280]: Broadcom Corporation Device [14e4:43ae] (rev 02) Subsystem: Lenovo Device [17aa:0622] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1432869/+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 1770166] Re: The brightness of the notebook
** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: regression-release -- 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/1770166 Title: The brightness of the notebook Status in linux package in Ubuntu: Incomplete Bug description: The brightness of the notebook does not lower or rise with the FN key. Acer Aspire 5742 i3-380m 6gb ram ssd kingston 120gb. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Core Processor Integrated Graphics Controller [1025:0487] InstallationDate: Installed on 2018-06-14 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Acer Aspire 5742 Package: xorg 1:7.7+19ubuntu7 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=921bc593-7a3c-4ced-8659-695cfe311ce9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Tags: bionic ubuntu Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.18 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire 5742 dmi.board.vendor: Acer dmi.board.version: V1.18 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.18 dmi.modalias: dmi:bvnAcer:bvrV1.18:bd03/14/2011:svnAcer:pnAspire5742:pvrV1.18:rvnAcer:rnAspire5742:rvrV1.18:cvnAcer:ct10:cvrV1.18: dmi.product.family: Intel_Mobile dmi.product.name: Aspire 5742 dmi.product.version: V1.18 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770166/+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 1787149] Re: linux: 4.15.0-33.36 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-certification-testing 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/1787149 Title: linux: 4.15.0-33.36 -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: In Progress 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 snap-certification-testing series: Confirmed Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid 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 backports: bug 1787159 (linux-azure), bug 1787161 (linux-azure-edge), bug 1787162 (linux-gcp), bug 1787163 (linux-hwe), bug 1787166 (linux-hwe-edge) derivatives: bug 1787151 (linux-raspi2), bug 1787544 (linux-oem), bug 1787154 (linux-aws), bug 1787155 (linux-azure), bug 1787156 (linux-gcp), bug 1787158 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Uploaded proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787149/+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 1787988] Re: linux: 4.17.0-9.10 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug is for tracking the 4.17.0-9.10 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 + + kernel-phase:Packaging + kernel-phase-changed:Monday, 20. August 2018 16:33 UTC ** Description changed: This bug is for tracking the 4.17.0-9.10 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 kernel-phase:Packaging kernel-phase-changed:Monday, 20. August 2018 16:33 UTC + + -- swm properties -- + phase: Packaging -- 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/1787988 Title: linux: 4.17.0-9.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: This bug is for tracking the 4.17.0-9.10 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 kernel-phase:Packaging kernel-phase-changed:Monday, 20. August 2018 16:33 UTC -- swm properties -- phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787988/+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 1787988] [NEW] linux: 4.17.0-9.10 -proposed tracker
Public bug reported: This bug is for tracking the 4.17.0-9.10 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 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux (Ubuntu Cosmic) Importance: Medium Status: Confirmed ** Tags: cosmic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2018.08.20-1 ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Tags added: cosmic ** Changed in: linux (Ubuntu Cosmic) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/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-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Tags added: kernel-sru-cycle-d2018.08.20-1 -- 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/1787988 Title: linux: 4.17.0-9.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New
[Kernel-packages] [Bug 1787982] Re: linux: 3.13.0-157.207 -proposed tracker
** Summary changed: - linux: -proposed tracker + linux: 3.13.0-157.207 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- 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/1787982 Title: linux: 3.13.0-157.207 -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: 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-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 upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid 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: bug 1787983 (linux-lts-trusty) derivatives: To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787982/+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 1787982] [NEW] linux: 3.13.0-157.207 -proposed tracker
Public bug reported: 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: bug 1787983 (linux-lts-trusty) derivatives: ** 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: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Khaled El Mously (kmously) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Khaled El Mously (kmously) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Khaled El Mously (kmously) 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/upload-to-ppa Importance: Medium Status: Invalid ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2018.07.30-3 kernel-sru-master-kernel trusty ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Tags added: trusty ** 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/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/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed
[Kernel-packages] [Bug 1787983] [NEW] linux-lts-trusty: -proposed tracker
Public bug reported: 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: 1787982 ** 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: Invalid ** 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: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** 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/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-lts-trusty (Ubuntu) Importance: Undecided Status: Invalid ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-backport-of-1787982 kernel-sru-cycle-2018.07.30-3 precise ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Tags added: precise ** 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/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/automated-testing Status: New => Invalid ** 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: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in:
Re: [Kernel-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
I am going to have a look at this soon. On Wed, 15 Aug 2018 at 23:20, Steve Langasek wrote: > Reviewing ubuntu-drivers-common in the queue, I notice: > > +if (!match) { > +free(match); > > Surely no good can come of this call to free() and it should be omitted? > > The change to start before oem-config.service seems correct but has no > associated bug linked. This looks to me like it should still go through > the SRU verification process because it's unrelated to the other > changes. (Also, it's not 100% obvious that the change is correct: for > example, why does oem-config not provide display-manager.service? Why > are there no interdependencies between oem-config's systemd units and > display-manager.service?) > > The source package as uploaded appears to have a lot of cruft in various > __pycache__ directories. This ought to be cleaned up. > > I'm going to go ahead and reject based on the missing bug reference for > the oem-config.service change. If you think this is wrong, feel free to > ping me on IRC to discuss. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1778011 > > Title: > SRU: PRIME Power Saving mode draws too much power > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=gdm3; component=main; > status=Fix Released; importance=High; assignee= > alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; > sourcepackage=nvidia-graphics-drivers-390; component=restricted; status=Fix > Released; importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; sourcepackage=nvidia-prime; > component=main; status=Fix Released; importance=High; assignee= > alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; sourcepackage=nvidia-settings; > component=main; status=Fix Released; importance=High; assignee= > alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; sourcepackage=ubuntu-drivers-common; > component=main; status=Fix Released; importance=High; assignee= > alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=gdm3; component=main; status=In Progress; importance=High; > assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=nvidia-graphics-drivers-390; component=restricted; status=In > Progress; importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=nvidia-prime; component=main; status=In Progress; > importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=nvidia-settings; component=main; status=In Progress; > importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=ubuntu-drivers-common; component=main; status=In Progress; > importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: albertomilone andrebrait cantfind ilvipero > janitor vorlon > Launchpad-Bug-Reporter: Alberto Milone (albertomilone) > Launchpad-Bug-Modifier: Steve Langasek (vorlon) > Launchpad-Message-Rationale: Subscriber > Launchpad-Message-For: albertomilone > -- Alberto Milone -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Incomplete Status in nvidia-prime source package in Bionic: In Progress Status in nvidia-settings source package in Bionic: In Progress Status in ubuntu-drivers-common source package in Bionic: In Progress Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this
Re: [Kernel-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
Software rendering is a better bet if DKMS fails, as nouveau can cause problems when dealing with (partially?) supported GPUs. I introduced that change in bionic, but then I reverted that behaviour, also because it would cause problems to hybrid graphics. I don't think users relying on something that is broken should hold us back. If anything, the fallback would cause users to file bug reports (about graphics corruption, increased power consumption, etc.) against nvidia, where these would be really nouveau's. On Thu, 16 Aug 2018 at 00:36, Steve Langasek wrote: > Bug description says: > > > [Regression Potential] > > Low, as hybrid graphics support does not work correctly, and the changes > only affect > > this use case. > > Dropping the nvidia-fallback service means that any time the nvidia > module has failed to be loaded, including if the nvidia module has > failed to build for any reason, the nouveau module will not be loaded in > its place. This is a behavior change that potentially affects users > other than those with hybrid graphics. Is that a concern? How long has > the existing behavior been there, and what are the chances that users > may be inadvertently relying on the current fallback behavior without > knowing it? > > ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic) >Status: In Progress => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1778011 > > Title: > SRU: PRIME Power Saving mode draws too much power > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=gdm3; component=main; > status=Fix Released; importance=High; assignee= > alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; > sourcepackage=nvidia-graphics-drivers-390; component=restricted; status=Fix > Released; importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; sourcepackage=nvidia-prime; > component=main; status=Fix Released; importance=High; assignee= > alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; sourcepackage=nvidia-settings; > component=main; status=Fix Released; importance=High; assignee= > alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; sourcepackage=ubuntu-drivers-common; > component=main; status=Fix Released; importance=High; assignee= > alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=gdm3; component=main; status=In Progress; importance=High; > assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=nvidia-graphics-drivers-390; component=restricted; > status=Incomplete; importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=nvidia-prime; component=main; status=In Progress; > importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=nvidia-settings; component=main; status=In Progress; > importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=ubuntu-drivers-common; component=main; status=In Progress; > importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: albertomilone andrebrait cantfind ilvipero > janitor vorlon > Launchpad-Bug-Reporter: Alberto Milone (albertomilone) > Launchpad-Bug-Modifier: Steve Langasek (vorlon) > Launchpad-Message-Rationale: Subscriber > Launchpad-Message-For: albertomilone > -- Alberto Milone -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Incomplete Status in nvidia-prime source package in Bionic: In Progress Status in nvidia-settings source package in Bionic: In Progress Status in ubuntu-drivers-common source package in Bionic: In Progress Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down
[Kernel-packages] [Bug 1787154] Re: linux-aws: 4.15.0-1020.20 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released -- 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/1787154 Title: linux-aws: 4.15.0-1020.20 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in 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: 1787149 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787154/+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 1787155] Re: linux-azure: 4.15.0-1022.23 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released -- 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/1787155 Title: linux-azure: 4.15.0-1022.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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 snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released 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: Confirmed 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 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: 1787149 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787155/+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 1787973] [NEW] Cosmic update to 4.17.17 stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.17.17 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.17.17 stable release shall be applied: fa535b8a3759 Linux 4.17.17 a4ae511d8600 x86/speculation/l1tf: Exempt zeroed PTEs from inversion ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Tags added: kernel-stable-tracking-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/1787973 Title: Cosmic update to 4.17.17 stable release Status in linux package in Ubuntu: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.17.17 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.17.17 stable release shall be applied: fa535b8a3759 Linux 4.17.17 a4ae511d8600 x86/speculation/l1tf: Exempt zeroed PTEs from inversion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787973/+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 1787972] [NEW] Cosmic update to 4.17.16 stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.17.16 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.17.16 stable release shall be applied: 085c22bb54b8 Linux 4.17.16 c812c53e814d x86/mm: Add TLB purge to free pmd/pte page interfaces a033b10861c7 ioremap: Update pgtable free interfaces with addr 0c37356f695f Bluetooth: hidp: buffer overflow in hidp_process_report 82ca3d13d852 crypto: skcipher - fix crash flushing dcache in error path f21a81f5b952 crypto: skcipher - fix aligning block size in skcipher_copy_iv() 483efa679b61 crypto: ablkcipher - fix crash flushing dcache in error path a404181a65f9 crypto: blkcipher - fix crash flushing dcache in error path 55c689bd3d1c crypto: vmac - separate tfm and request context b26243c535d3 crypto: vmac - require a block cipher with 128-bit block size 7d0da8a5 crypto: x86/sha256-mb - fix digest copy in sha256_mb_mgr_get_comp_job_avx2() 3dcf89469076 crypto: ccp - Fix command completion detection race 80a5eb6b3745 crypto: ccp - Check for NULL PSP pointer at module unload a2a9b8b34cc8 crypto: ccree - fix iv handling 4e2befa3feeb crypto: ccree - fix finup 6b773162355a kbuild: verify that $DEPMOD is installed 9c018f562dd9 x86/mm: Disable ioremap free page handling on x86-PAE dc891b7ba381 xen/pv: Call get_cpu_address_sizes to set x86_virt/phys_bits 63687997fd18 x86/mm/pti: Clear Global bit more aggressively af1cd0e89651 x86/platform/UV: Mark memblock related init code and data correctly 921eb6977ca8 x86: i8259: Add missing include file 0fee79788745 x86/l1tf: Fix build error seen if CONFIG_KVM_INTEL is disabled ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Tags added: kernel-stable-tracking-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/1787972 Title: Cosmic update to 4.17.16 stable release Status in linux package in Ubuntu: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.17.16 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.17.16 stable release shall be applied: 085c22bb54b8 Linux 4.17.16 c812c53e814d x86/mm: Add TLB purge to free pmd/pte page interfaces a033b10861c7 ioremap: Update pgtable free interfaces with addr 0c37356f695f Bluetooth: hidp: buffer overflow in hidp_process_report 82ca3d13d852 crypto: skcipher - fix crash flushing dcache in error path f21a81f5b952 crypto: skcipher - fix aligning block size in skcipher_copy_iv() 483efa679b61 crypto: ablkcipher - fix crash flushing dcache in error path a404181a65f9 crypto: blkcipher - fix crash flushing dcache in error path 55c689bd3d1c crypto: vmac - separate tfm and request context b26243c535d3 crypto: vmac - require a block cipher with 128-bit block size 7d0da8a5 crypto: x86/sha256-mb - fix digest copy in sha256_mb_mgr_get_comp_job_avx2() 3dcf89469076 crypto: ccp - Fix command completion detection race 80a5eb6b3745 crypto: ccp - Check for NULL PSP pointer at module unload a2a9b8b34cc8 crypto: ccree - fix iv handling 4e2befa3feeb crypto: ccree - fix finup 6b773162355a kbuild: verify that $DEPMOD is installed 9c018f562dd9 x86/mm: Disable ioremap free page handling on x86-PAE dc891b7ba381 xen/pv: Call get_cpu_address_sizes to set x86_virt/phys_bits 63687997fd18 x86/mm/pti: Clear Global bit more aggressively af1cd0e89651 x86/platform/UV: Mark memblock related init code and data correctly 921eb6977ca8 x86: i8259: Add missing include file 0fee79788745 x86/l1tf: Fix build error seen if CONFIG_KVM_INTEL is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787972/+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 1778011] Re: SRU: PRIME Power Saving mode draws too much power
(waiting with the other packages until Steve's concerns are addressed) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Incomplete Status in nvidia-prime source package in Bionic: In Progress Status in nvidia-settings source package in Bionic: In Progress Status in ubuntu-drivers-common source package in Bionic: In Progress Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+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 1591043] Re: xubuntu 16.04 on the haswell platform random restart
Was this issue resolved? ** Package changed: xfdesktop4 (Ubuntu) => linux (Ubuntu) ** 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/1591043 Title: xubuntu 16.04 on the haswell platform random restart Status in linux package in Ubuntu: Incomplete Bug description: Recently,I am use the xubuntu 16.04 on the haswell platform.I found my haswell's device random restart,when log in the xubuntu about 10 minutes,but it doesn't happen every time. The random reboot is similar to use the watchdog(directly power off and then automatically power on ). Now,I can't find any message about this issue. Any help will be grateful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1591043/+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 1432869] Re: No wireless access for BCM 43162
it still affects: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/1432869 Title: No wireless access for BCM 43162 Status in linux package in Ubuntu: Confirmed Bug description: No connectivity on 14.04.2 for Lenovo Edge E555 using a BCM43162 wireless adapter. Here is what I got with lspci -nnk | grep -iA2 net Network Controller [0280]: Broadcom Corporation Device [14e4:43ae] (rev 02) Subsystem: Lenovo Device [17aa:0622] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1432869/+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 1591043] [NEW] xubuntu 16.04 on the haswell platform random restart
You have been subscribed to a public bug: Recently,I am use the xubuntu 16.04 on the haswell platform.I found my haswell's device random restart,when log in the xubuntu about 10 minutes,but it doesn't happen every time. The random reboot is similar to use the watchdog(directly power off and then automatically power on ). Now,I can't find any message about this issue. Any help will be grateful. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- xubuntu 16.04 on the haswell platform random restart https://bugs.launchpad.net/bugs/1591043 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 1778011] Re: SRU: PRIME Power Saving mode draws too much power
Hello Alberto, or anyone else affected, Accepted gdm3 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gdm3/3.28.3-0ubuntu18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gdm3 (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-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/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Incomplete Status in nvidia-prime source package in Bionic: In Progress Status in nvidia-settings source package in Bionic: In Progress Status in ubuntu-drivers-common source package in Bionic: In Progress Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+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 1787180] Re: linux-aws: 4.4.0-1066.76 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released -- 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/1787180 Title: linux-aws: 4.4.0-1066.76 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1787177 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787180/+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 1787177] Re: linux: 4.4.0-134.160 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-certification-testing 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/1787177 Title: linux: 4.4.0-134.160 -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: Fix Released 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 snap-certification-testing series: Confirmed Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1787178 (linux-aws), bug 1787179 (linux-lts-xenial) derivatives: bug 1787180 (linux-aws), bug 1787181 (linux-euclid), bug 1787182 (linux-kvm), bug 1787183 (linux-raspi2), bug 1787184 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787177/+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 1787159] Re: linux-azure: 4.15.0-1022.22~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released -- 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/1787159 Title: linux-azure: 4.15.0-1022.22~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released 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: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released 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: Confirmed 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 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: 1787149 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787159/+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 1787945] Re: Tango platform uses __initcall without further checks
** 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/1787945 Title: Tango platform uses __initcall without further checks Status in linux package in Ubuntu: Confirmed Bug description: The TANGO platform is enabled by default in the multiplatform ARM kernel. However, it calls __initcall in arch/arm/mach-tango/pm.c without a check whether it actually runs on this hw. This causes an OOPS during suspend on my Tegra platform. Please disable this (multiplatform incompatible) arch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787945/+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 1764645] Re: Bluetooth not working
Sadly I don't have a kernel that works with bluetooth. The working proposed 31 was replaced with a non-working official kernel 31. I'll have to go to 4.16.something of higher. Bother. -- 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/1764645 Title: Bluetooth not working Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: == SRU Justification == A regression was discovered in Bionic. The regression was introduced by mainline commit f44cb4b19ed4, which then made it's way into Bionic in 4.15.0-14 as commit c91729972ac6 via stable updates. This regression is fixed by mainline commit 803cdb8ce584. Commit 803cdb8ce584 was also cc'd to stable. However, it has not landed in upstream stable 4.15 or Bionic. == Fix == 803cdb8ce584 ("Bluetooth: btusb: Apply QCA Rome patches for some ATH3012 models") == Regression Potential == Low. This fix has also been cc'd to upstream stable, so it has had additonal upstream review. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. I've installed the Ubuntu Bionic Beta 2 and everything works fine but the bluetooth (perfectly working with Xenial). In bluetooth control panel the slider is impossible to move to "on". 1) Ubuntu Release (via 'lsb_release -rd') Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2) Version of package (apt-cache policy gnome-bluetooth) gnome-bluetooth: Installato: 3.28.0-2 Candidato: 3.28.0-2 Tabella versione: *** 3.28.0-2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen I expected to switch on the bluetooth. 4) What happened instead Bluetooth won't switch on. 5) Output of rfkill list is: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 6) Output of lspci -knn | grep Net -A3; lsusb; dmesg | grep -i blue is: 03:00.0 Network controller [0280]: Qualcomm Atheros AR9462 Wireless Network Adapter [168c:0034] (rev 01) Subsystem: Bigfoot Networks, Inc. Killer Wireless-N 1202 Half- size Mini PCIe Card [1a56:2003] Kernel driver in use: ath9k Kernel modules: ath9k 04:00.0 Ethernet controller [0200]: Qualcomm Atheros QCA8171 Gigabit Ethernet [1969:10a1] (rev 10) Bus 002 Device 002: ID 8087:8000 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8008 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 04f2:b414 Chicony Electronics Co., Ltd Bus 003 Device 003: ID 0cf3:3004 Atheros Communications, Inc. AR3012 Bluetooth 4.0 Bus 003 Device 002: ID 0b05:17c4 ASUSTek Computer, Inc. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [ 17.715399] Bluetooth: Core ver 2.22 [ 17.715414] Bluetooth: HCI device and connection manager initialized [ 17.715416] Bluetooth: HCI socket layer initialized [ 17.715418] Bluetooth: L2CAP socket layer initialized [ 17.715422] Bluetooth: SCO socket layer initialized [ 17.723207] Bluetooth: hci0: don't support firmware rome 0x1102 [ 18.600648] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 18.600649] Bluetooth: BNEP filters: protocol multicast [ 18.600651] Bluetooth: BNEP socket layer initialized ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-generic 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stormy 1484 F pulseaudio /dev/snd/controlC0: stormy 1484 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Apr 17 08:46:30 2018 HibernationDevice: RESUME=UUID=3f513ca9-6817-4099-9718-fee68d68ec11 InstallationDate: Installed on 2018-04-16 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: ASUSTeK COMPUTER INC. G750JH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions:
[Kernel-packages] [Bug 1787162] Re: linux-gcp: 4.15.0-1018.19~16.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 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1787162 Title: linux-gcp: 4.15.0-1018.19~16.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: New 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1787149 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787162/+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 1764645] Re: Bluetooth not working
All you have to do is to boot with the last working Kernel.(you can do it at boot time trough the Grub menu) If it works then you can remove the 4.15.0-33. -- 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/1764645 Title: Bluetooth not working Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: == SRU Justification == A regression was discovered in Bionic. The regression was introduced by mainline commit f44cb4b19ed4, which then made it's way into Bionic in 4.15.0-14 as commit c91729972ac6 via stable updates. This regression is fixed by mainline commit 803cdb8ce584. Commit 803cdb8ce584 was also cc'd to stable. However, it has not landed in upstream stable 4.15 or Bionic. == Fix == 803cdb8ce584 ("Bluetooth: btusb: Apply QCA Rome patches for some ATH3012 models") == Regression Potential == Low. This fix has also been cc'd to upstream stable, so it has had additonal upstream review. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. I've installed the Ubuntu Bionic Beta 2 and everything works fine but the bluetooth (perfectly working with Xenial). In bluetooth control panel the slider is impossible to move to "on". 1) Ubuntu Release (via 'lsb_release -rd') Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2) Version of package (apt-cache policy gnome-bluetooth) gnome-bluetooth: Installato: 3.28.0-2 Candidato: 3.28.0-2 Tabella versione: *** 3.28.0-2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen I expected to switch on the bluetooth. 4) What happened instead Bluetooth won't switch on. 5) Output of rfkill list is: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 6) Output of lspci -knn | grep Net -A3; lsusb; dmesg | grep -i blue is: 03:00.0 Network controller [0280]: Qualcomm Atheros AR9462 Wireless Network Adapter [168c:0034] (rev 01) Subsystem: Bigfoot Networks, Inc. Killer Wireless-N 1202 Half- size Mini PCIe Card [1a56:2003] Kernel driver in use: ath9k Kernel modules: ath9k 04:00.0 Ethernet controller [0200]: Qualcomm Atheros QCA8171 Gigabit Ethernet [1969:10a1] (rev 10) Bus 002 Device 002: ID 8087:8000 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8008 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 04f2:b414 Chicony Electronics Co., Ltd Bus 003 Device 003: ID 0cf3:3004 Atheros Communications, Inc. AR3012 Bluetooth 4.0 Bus 003 Device 002: ID 0b05:17c4 ASUSTek Computer, Inc. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [ 17.715399] Bluetooth: Core ver 2.22 [ 17.715414] Bluetooth: HCI device and connection manager initialized [ 17.715416] Bluetooth: HCI socket layer initialized [ 17.715418] Bluetooth: L2CAP socket layer initialized [ 17.715422] Bluetooth: SCO socket layer initialized [ 17.723207] Bluetooth: hci0: don't support firmware rome 0x1102 [ 18.600648] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 18.600649] Bluetooth: BNEP filters: protocol multicast [ 18.600651] Bluetooth: BNEP socket layer initialized ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-generic 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stormy 1484 F pulseaudio /dev/snd/controlC0: stormy 1484 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Apr 17 08:46:30 2018 HibernationDevice: RESUME=UUID=3f513ca9-6817-4099-9718-fee68d68ec11 InstallationDate: Installed on 2018-04-16 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: ASUSTeK COMPUTER INC. G750JH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A
[Kernel-packages] [Bug 1721909] Re: Goodix GF3208 (fingerprint reader) not being recognised by kernel/system
Confirmed on Asus UX331UN with Ubuntu 18.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/1721909 Title: Goodix GF3208 (fingerprint reader) not being recognised by kernel/system Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: The Goodix GF3208 is not being recognised by the system (Dell Inspiron 15 7577). What's worse is that it isn't even showing the manufacturer vendor id information when doing: $ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 27c6:5301 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 005: ID 0bda:5652 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Note that the vendor id 27c6 should at least say "Shenzhen Huiding Technology Co., Ltd." as per https://github.com/torvalds/linux/blob/e19b205be43d11bff638cad4487008c48d21c103/Documentation/devicetree/bindings /vendor-prefixes.txt Will/has support been made for the Goodix GF3208 Fingerprint reader/scanner? Thanks in advance, Haz ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 7 04:03:25 2017 InstallationDate: Installed on 2017-10-01 (5 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1721909/+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 1770095] Comment bridged from LTC Bugzilla
--- Comment From kla...@br.ibm.com 2018-08-20 09:40 EDT--- (In reply to comment #22) > Confirmed that fix is in latest -proposed kernel. When is that GAed (i.e., supported officially)? Should we close? -- 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/1770095 Title: Need fix to aacraid driver to prevent panic Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: == SRU Justification == A commit introduced in mainline v4.14-rc1 to aacraid (b60710ec7d7ab1ca277b458338563ac21b393906) introduced a regression whereby a panic may happen under certain recovery situations. This regression is fixed by linux-next commit 7d3af7d96af7. == Fix == 7d3af7d96af7 ("scsi: aacraid: Correct hba_send to include iu_type") == Regression Potential == Low. This patch fixes a current regression. It was cc'd to upstream stable, so it has had additonal upstream review. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. == Comment: #0 - Douglas Miller - 2018-05-08 15:45:13 == +++ This bug was initially created as a clone of Bug #167565 +++ A recent commit to aacraid (b60710ec7d7ab1ca277b458338563ac21b393906) introduced a bug whereby a panic may happen under certain recovery situations. The following commit fixes that: https://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git/commit/?h=fixes=7d3af7d96af7b9f51e1ef67b6f4725f545737da2 We need this commit backported to Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1770095/+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 1779893] Re: my laptop freezes at the login screen
4.4.0-133 also didn't fixed the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779893 Title: my laptop freezes at the login screen Status in linux package in Ubuntu: Incomplete Bug description: I apologise in advance, this is my first report, therefore I am not sure if everything has been automatically collected, or if I need to provide further information than a short explanation of the problem. After updating the kernel at 4.4.0-128 on Ubuntu 16.04, first I had massive problems with the sound drivers. Then they disappeared (by themselves I would say, I had many tests but I don't think I screwed up anything serious) and, instead, now my sistem freezes at login screen. Sometimes it gives me the message that the wireless has been found. The mouse is available but I cannot interact with the screen, and also the clock is frozen. I have to brutally switch off the laptop for rebooting. A further kernel update to 4.4.0-130 didn't help, either. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-130-generic 4.4.0-130.156 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luigi 2426 F pulseaudio CurrentDesktop: Unity Date: Tue Jul 3 17:31:25 2018 HibernationDevice: RESUME=UUID=c24386f7-c59c-494d-b58d-abced7cc343c InstallationDate: Installed on 2017-02-28 (489 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 174f:2408 Syntek Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80TV ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic.efi.signed root=UUID=e98922f5-e948-421c-8d5f-2d7e1ad4dfe1 ro recovery nomodeset RelatedPackageVersions: linux-restricted-modules-4.4.0-130-generic N/A linux-backports-modules-4.4.0-130-generic N/A linux-firmware 1.157.19 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/10/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 3JCN23WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Torronto 5C2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-15IKB dmi.modalias: dmi:bvnLENOVO:bvr3JCN23WW:bd11/10/2016:svnLENOVO:pn80TV:pvrLenovoideapad310-15IKB:rvnLENOVO:rnTorronto5C2:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad310-15IKB: dmi.product.name: 80TV dmi.product.version: Lenovo ideapad 310-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779893/+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 1787162] Re: linux-gcp: 4.15.0-1018.19~16.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Khaled El Mously (kmously) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1787162 Title: linux-gcp: 4.15.0-1018.19~16.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: 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-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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1787149 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787162/+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 1787945] 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 1787945 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/1787945 Title: Tango platform uses __initcall without further checks Status in linux package in Ubuntu: Incomplete Bug description: The TANGO platform is enabled by default in the multiplatform ARM kernel. However, it calls __initcall in arch/arm/mach-tango/pm.c without a check whether it actually runs on this hw. This causes an OOPS during suspend on my Tegra platform. Please disable this (multiplatform incompatible) arch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787945/+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 1787162] Re: linux-gcp: 4.15.0-1018.19~16.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Kleber Sacilotto de Souza (kleber-souza) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1787162 Title: linux-gcp: 4.15.0-1018.19~16.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: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: Fix Released 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 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1787149 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787162/+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 1787618] 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 1787618 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/1787618 Title: since 3.13.0.153 doesnt wakeup from suspension Status in linux package in Ubuntu: Incomplete Bug description: hey all, since a couple of updates after kernel 3.13.0.145 the laptop doesnt wake up from suspension. i just need to hard boot by keep pressing the power button and restart. in case i boot in the older 3.13.0.145 kernel all works fine. last kernel update hasnt solved it. i suppose the updates should include this kind of services or make them better not the opposite... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787618/+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 1787162] Re: linux-gcp: 4.15.0-1018.19~16.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Khaled El Mously (kmously) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1787162 Title: linux-gcp: 4.15.0-1018.19~16.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: 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-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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1787149 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787162/+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 1787618] Re: since 3.13.0.153 doesnt wakeup from suspension
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787618 Title: since 3.13.0.153 doesnt wakeup from suspension Status in linux package in Ubuntu: Incomplete Bug description: hey all, since a couple of updates after kernel 3.13.0.145 the laptop doesnt wake up from suspension. i just need to hard boot by keep pressing the power button and restart. in case i boot in the older 3.13.0.145 kernel all works fine. last kernel update hasnt solved it. i suppose the updates should include this kind of services or make them better not the opposite... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787618/+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 1787618] [NEW] since 3.13.0.153 doesnt wakeup from suspension
You have been subscribed to a public bug: hey all, since a couple of updates after kernel 3.13.0.145 the laptop doesnt wake up from suspension. i just need to hard boot by keep pressing the power button and restart. in case i boot in the older 3.13.0.145 kernel all works fine. last kernel update hasnt solved it. i suppose the updates should include this kind of services or make them better not the opposite... ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- since 3.13.0.153 doesnt wakeup from suspension https://bugs.launchpad.net/bugs/1787618 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 1786906] 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 1786906 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/1786906 Title: "ACPI unsupported" Status in linux package in Ubuntu: Incomplete Bug description: While I'm using Ubuntu Server version on my laptop(HP omen 15, CPU:i5-8300H,GPU:GTX1050Ti), it always says "[ time.time] acpi INT3400:00: Unsupported event [0x86]", In Ubuntu Desktop version, after I turn on my computer, it'll not going on but stay at a screen and says "[ time.time] acpi INT3400:00: Unsupported event [0x86]" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786906/+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 1787188] Re: linux-lts-trusty: 3.13.0-156.206~precise1 -proposed tracker
** 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/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Invalid ** 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: 1787187 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Monday, 20. August 2018 12:33 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1787187 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Monday, 20. August 2018 12:33 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1787188 Title: linux-lts-trusty: 3.13.0-156.206~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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: 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: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: 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: 1787187 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787188/+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 1787571] Re: Bluetooth keyboard won't connect again after connection was lost
Your suggestion didn't help. Bluetooth is still crashing when the keyboard is connecting, either from the keyboard itself or through bluetoothctl. To be on the safe side, I paired the keyboard again and restarted Ubuntu, but it still won't connect again after a connection loss: $ bluetoothctl paired-devices Device 34:88:5D:42:7E:03 Keyboard K380 Device FA:6A:9E:DA:2B:30 M585/M590 $ bluetoothctl connect 34:88:5D:42:7E:03 Attempting to connect to 34:88:5D:42:7E:03 Failed to connect: org.bluez.Error.Failed It seems that my mouse is now nearly instantly connecting though, but no guarantees on that. I really can't explain why this is happening :( Repairing the keyboard after each lost connection isn't an option, especially because I always have to type the confirmation code on the keyboard, while pairing. Didn't you spot something unusual in my debug info? From my layman's view, there seem to be a lot of error messages. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1787571 Title: Bluetooth keyboard won't connect again after connection was lost Status in bluez package in Ubuntu: New Bug description: After my Bluetooth keyboard from Logitech (K380) looses its connection, either after a Ubuntu restart or by manually turning the keyboard off an on, it won't connect any more. Additionally, while the keyboard tries to reestablish the connection, my Logitech Bluetooth mouse (M590) looses its connection too! After that I can't establish any Bluetooth connection at all. Only a "sudo service bluetooth restart" helps. Then my mouse reconnects easily, if it's not disrupted by my keyboard. So I'm only possible to use my mouse and not the keyboard, because while it tries to reconnect, it kills the connection of my mouse and everything starts over again. I've also tried to reconnect the keyboard through "bluetoothctl", but without success: $ bluetoothctl paired-devices Device 34:88:5D:42:7E:03 Keyboard K380 Device FA:6A:9E:DA:2B:30 M585/M590 $ bluetoothctl connect 34:88:5D:42:7E:03 Attempting to connect to 34:88:5D:42:7E:03 Failed to connect: org.bluez.Error.Failed Both devices are "trusted": $ bluetoothctl info 34:88:5D:42:7E:03 Device 34:88:5D:42:7E:03 (public) Name: Keyboard K380 Alias: Keyboard K380 Class: 0x2540 Icon: input-keyboard Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb) UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) Modalias: usb:v046DpB342d4200 $ bluetoothctl info FA:6A:9E:DA:2B:30 Device FA:6A:9E:DA:2B:30 (random) Name: M585/M590 Alias: M585/M590 Appearance: 0x03c2 Icon: input-mouse Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Device Information(180a--1000-8000-00805f9b34fb) UUID: Battery Service (180f--1000-8000-00805f9b34fb) UUID: Human Interface Device(1812--1000-8000-00805f9b34fb) UUID: Vendor specific (0001--1000-8000-011f246d) Modalias: usb:v046DpB01Bd0007 $ bluetoothctl show Controller 2C:6F:C9:44:57:E0 (public) Name: mir Alias: mir Class: 0x000c010c Powered: yes Discoverable: yes Pairable: yes UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0532 Discovering: no The only way to use my Bluetooth keyboard is to pair it again, f.i. by doing: bluetoothctl remove XX:XX:XX:XX:XX:XX exit sudo service bluetooth restart bluetoothctl scan on trust XX:XX:XX:XX:XX:XX pair XX:XX:XX:XX:XX:XX connect XX:XX:XX:XX:XX:XX exit This keyboard works flawlessly with my Android device and also on a MacBook Pro with
[Kernel-packages] [Bug 1787945] [NEW] Tango platform uses __initcall without further checks
Public bug reported: The TANGO platform is enabled by default in the multiplatform ARM kernel. However, it calls __initcall in arch/arm/mach-tango/pm.c without a check whether it actually runs on this hw. This causes an OOPS during suspend on my Tegra platform. Please disable this (multiplatform incompatible) arch. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: 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/1787945 Title: Tango platform uses __initcall without further checks Status in linux package in Ubuntu: New Bug description: The TANGO platform is enabled by default in the multiplatform ARM kernel. However, it calls __initcall in arch/arm/mach-tango/pm.c without a check whether it actually runs on this hw. This causes an OOPS during suspend on my Tegra platform. Please disable this (multiplatform incompatible) arch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787945/+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 1787162] Re: linux-gcp: 4.15.0-1018.19~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => New ** Changed in: kernel-sru-workflow/certification-testing Status: Invalid => New ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => New ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => New ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Khaled El Mously (kmously) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Released => New ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Khaled El Mously (kmously) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Łukasz Zemczak (sil2100) => Ubuntu Stable Release Updates Team (ubuntu-sru) ** Summary changed: - linux-gcp: 4.15.0-1018.19~16.04.1 -proposed tracker + linux-gcp: 4.15.0-1018.19~16.04.2 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1787162 Title: linux-gcp: 4.15.0-1018.19~16.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: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: Fix Released 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 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1787149 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787162/+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 1787162] Re: linux-gcp: 4.15.0-1018.19~16.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Kleber Sacilotto de Souza (kleber-souza) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1787162 Title: linux-gcp: 4.15.0-1018.19~16.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: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: Fix Released 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 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1787149 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787162/+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 1725836] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1725836/+attachment/5177970/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1725836 Title: [radeon] No more than 2 displays work simultaneously Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Status in xserver-xorg-video-ati package in Ubuntu: Incomplete Bug description: I have three displays that worked fine in 17.04. Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3. All three seem to be properly specified in monitors.xml. The display setup scree detects all three. UBUNTU 17.10 AMD PitcairnLSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-02-23 (242 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: peterw 2037 F pulseaudio /dev/snd/controlC2: peterw 2037 F pulseaudio /dev/snd/controlC0: peterw 2037 F pulseaudio BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [148c:2356] HibernationDevice: RESUME=UUID=342f741e-9371-4d2a-8d0a-e6e1a5303015 InstallationDate: Installed on 2018-05-29 (82 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. G1.Sniper B5 Package: xserver-xorg-video-ati 1:18.0.1-1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: G1.Sniper B5-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd09/16/2014:svnGigabyteTechnologyCo.,Ltd.:pnG1.SniperB5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnG1.SniperB5-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: G1.Sniper B5 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev:
[Kernel-packages] [Bug 1725836] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1725836/+attachment/5177978/+files/xdpyinfo.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/1725836 Title: [radeon] No more than 2 displays work simultaneously Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Status in xserver-xorg-video-ati package in Ubuntu: Incomplete Bug description: I have three displays that worked fine in 17.04. Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3. All three seem to be properly specified in monitors.xml. The display setup scree detects all three. UBUNTU 17.10 AMD PitcairnLSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-02-23 (242 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: peterw 2037 F pulseaudio /dev/snd/controlC2: peterw 2037 F pulseaudio /dev/snd/controlC0: peterw 2037 F pulseaudio BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [148c:2356] HibernationDevice: RESUME=UUID=342f741e-9371-4d2a-8d0a-e6e1a5303015 InstallationDate: Installed on 2018-05-29 (82 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. G1.Sniper B5 Package: xserver-xorg-video-ati 1:18.0.1-1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: G1.Sniper B5-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd09/16/2014:svnGigabyteTechnologyCo.,Ltd.:pnG1.SniperB5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnG1.SniperB5-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: G1.Sniper B5 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev:
[Kernel-packages] [Bug 1725836] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1725836/+attachment/5177977/+files/Xrandr.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/1725836 Title: [radeon] No more than 2 displays work simultaneously Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Status in xserver-xorg-video-ati package in Ubuntu: Incomplete Bug description: I have three displays that worked fine in 17.04. Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3. All three seem to be properly specified in monitors.xml. The display setup scree detects all three. UBUNTU 17.10 AMD PitcairnLSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-02-23 (242 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: peterw 2037 F pulseaudio /dev/snd/controlC2: peterw 2037 F pulseaudio /dev/snd/controlC0: peterw 2037 F pulseaudio BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [148c:2356] HibernationDevice: RESUME=UUID=342f741e-9371-4d2a-8d0a-e6e1a5303015 InstallationDate: Installed on 2018-05-29 (82 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. G1.Sniper B5 Package: xserver-xorg-video-ati 1:18.0.1-1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: G1.Sniper B5-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd09/16/2014:svnGigabyteTechnologyCo.,Ltd.:pnG1.SniperB5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnG1.SniperB5-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: G1.Sniper B5 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev:
[Kernel-packages] [Bug 1725836] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1725836/+attachment/5177971/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1725836 Title: [radeon] No more than 2 displays work simultaneously Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Status in xserver-xorg-video-ati package in Ubuntu: Incomplete Bug description: I have three displays that worked fine in 17.04. Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3. All three seem to be properly specified in monitors.xml. The display setup scree detects all three. UBUNTU 17.10 AMD PitcairnLSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-02-23 (242 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: peterw 2037 F pulseaudio /dev/snd/controlC2: peterw 2037 F pulseaudio /dev/snd/controlC0: peterw 2037 F pulseaudio BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [148c:2356] HibernationDevice: RESUME=UUID=342f741e-9371-4d2a-8d0a-e6e1a5303015 InstallationDate: Installed on 2018-05-29 (82 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. G1.Sniper B5 Package: xserver-xorg-video-ati 1:18.0.1-1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: G1.Sniper B5-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd09/16/2014:svnGigabyteTechnologyCo.,Ltd.:pnG1.SniperB5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnG1.SniperB5-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: G1.Sniper B5 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev:
[Kernel-packages] [Bug 1725836] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1725836/+attachment/5177976/+files/XorgLogOld.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/1725836 Title: [radeon] No more than 2 displays work simultaneously Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Status in xserver-xorg-video-ati package in Ubuntu: Incomplete Bug description: I have three displays that worked fine in 17.04. Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3. All three seem to be properly specified in monitors.xml. The display setup scree detects all three. UBUNTU 17.10 AMD PitcairnLSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-02-23 (242 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: peterw 2037 F pulseaudio /dev/snd/controlC2: peterw 2037 F pulseaudio /dev/snd/controlC0: peterw 2037 F pulseaudio BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [148c:2356] HibernationDevice: RESUME=UUID=342f741e-9371-4d2a-8d0a-e6e1a5303015 InstallationDate: Installed on 2018-05-29 (82 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. G1.Sniper B5 Package: xserver-xorg-video-ati 1:18.0.1-1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: G1.Sniper B5-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd09/16/2014:svnGigabyteTechnologyCo.,Ltd.:pnG1.SniperB5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnG1.SniperB5-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: G1.Sniper B5 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev:
[Kernel-packages] [Bug 1725836] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1725836/+attachment/5177975/+files/XorgLog.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/1725836 Title: [radeon] No more than 2 displays work simultaneously Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Status in xserver-xorg-video-ati package in Ubuntu: Incomplete Bug description: I have three displays that worked fine in 17.04. Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3. All three seem to be properly specified in monitors.xml. The display setup scree detects all three. UBUNTU 17.10 AMD PitcairnLSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-02-23 (242 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: peterw 2037 F pulseaudio /dev/snd/controlC2: peterw 2037 F pulseaudio /dev/snd/controlC0: peterw 2037 F pulseaudio BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [148c:2356] HibernationDevice: RESUME=UUID=342f741e-9371-4d2a-8d0a-e6e1a5303015 InstallationDate: Installed on 2018-05-29 (82 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. G1.Sniper B5 Package: xserver-xorg-video-ati 1:18.0.1-1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: G1.Sniper B5-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd09/16/2014:svnGigabyteTechnologyCo.,Ltd.:pnG1.SniperB5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnG1.SniperB5-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: G1.Sniper B5 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev:
[Kernel-packages] [Bug 1725836] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1725836/+attachment/5177973/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1725836 Title: [radeon] No more than 2 displays work simultaneously Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Status in xserver-xorg-video-ati package in Ubuntu: Incomplete Bug description: I have three displays that worked fine in 17.04. Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3. All three seem to be properly specified in monitors.xml. The display setup scree detects all three. UBUNTU 17.10 AMD PitcairnLSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-02-23 (242 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: peterw 2037 F pulseaudio /dev/snd/controlC2: peterw 2037 F pulseaudio /dev/snd/controlC0: peterw 2037 F pulseaudio BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [148c:2356] HibernationDevice: RESUME=UUID=342f741e-9371-4d2a-8d0a-e6e1a5303015 InstallationDate: Installed on 2018-05-29 (82 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. G1.Sniper B5 Package: xserver-xorg-video-ati 1:18.0.1-1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: G1.Sniper B5-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd09/16/2014:svnGigabyteTechnologyCo.,Ltd.:pnG1.SniperB5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnG1.SniperB5-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: G1.Sniper B5 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev:
[Kernel-packages] [Bug 1725836] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1725836/+attachment/5177974/+files/WifiSyslog.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/1725836 Title: [radeon] No more than 2 displays work simultaneously Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Status in xserver-xorg-video-ati package in Ubuntu: Incomplete Bug description: I have three displays that worked fine in 17.04. Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3. All three seem to be properly specified in monitors.xml. The display setup scree detects all three. UBUNTU 17.10 AMD PitcairnLSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-02-23 (242 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: peterw 2037 F pulseaudio /dev/snd/controlC2: peterw 2037 F pulseaudio /dev/snd/controlC0: peterw 2037 F pulseaudio BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [148c:2356] HibernationDevice: RESUME=UUID=342f741e-9371-4d2a-8d0a-e6e1a5303015 InstallationDate: Installed on 2018-05-29 (82 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. G1.Sniper B5 Package: xserver-xorg-video-ati 1:18.0.1-1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: G1.Sniper B5-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd09/16/2014:svnGigabyteTechnologyCo.,Ltd.:pnG1.SniperB5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnG1.SniperB5-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: G1.Sniper B5 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev:
[Kernel-packages] [Bug 1725836] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1725836/+attachment/5177972/+files/PulseList.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/1725836 Title: [radeon] No more than 2 displays work simultaneously Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Status in xserver-xorg-video-ati package in Ubuntu: Incomplete Bug description: I have three displays that worked fine in 17.04. Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3. All three seem to be properly specified in monitors.xml. The display setup scree detects all three. UBUNTU 17.10 AMD PitcairnLSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-02-23 (242 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: peterw 2037 F pulseaudio /dev/snd/controlC2: peterw 2037 F pulseaudio /dev/snd/controlC0: peterw 2037 F pulseaudio BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [148c:2356] HibernationDevice: RESUME=UUID=342f741e-9371-4d2a-8d0a-e6e1a5303015 InstallationDate: Installed on 2018-05-29 (82 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. G1.Sniper B5 Package: xserver-xorg-video-ati 1:18.0.1-1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: G1.Sniper B5-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd09/16/2014:svnGigabyteTechnologyCo.,Ltd.:pnG1.SniperB5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnG1.SniperB5-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: G1.Sniper B5 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev:
[Kernel-packages] [Bug 1725836] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1725836/+attachment/5177969/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1725836 Title: [radeon] No more than 2 displays work simultaneously Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Status in xserver-xorg-video-ati package in Ubuntu: Incomplete Bug description: I have three displays that worked fine in 17.04. Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3. All three seem to be properly specified in monitors.xml. The display setup scree detects all three. UBUNTU 17.10 AMD PitcairnLSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-02-23 (242 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: peterw 2037 F pulseaudio /dev/snd/controlC2: peterw 2037 F pulseaudio /dev/snd/controlC0: peterw 2037 F pulseaudio BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [148c:2356] HibernationDevice: RESUME=UUID=342f741e-9371-4d2a-8d0a-e6e1a5303015 InstallationDate: Installed on 2018-05-29 (82 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. G1.Sniper B5 Package: xserver-xorg-video-ati 1:18.0.1-1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: G1.Sniper B5-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd09/16/2014:svnGigabyteTechnologyCo.,Ltd.:pnG1.SniperB5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnG1.SniperB5-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: G1.Sniper B5 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
[Kernel-packages] [Bug 1725836] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1725836/+attachment/5177968/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1725836 Title: [radeon] No more than 2 displays work simultaneously Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Status in xserver-xorg-video-ati package in Ubuntu: Incomplete Bug description: I have three displays that worked fine in 17.04. Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3. All three seem to be properly specified in monitors.xml. The display setup scree detects all three. UBUNTU 17.10 AMD PitcairnLSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-02-23 (242 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: peterw 2037 F pulseaudio /dev/snd/controlC2: peterw 2037 F pulseaudio /dev/snd/controlC0: peterw 2037 F pulseaudio BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [148c:2356] HibernationDevice: RESUME=UUID=342f741e-9371-4d2a-8d0a-e6e1a5303015 InstallationDate: Installed on 2018-05-29 (82 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. G1.Sniper B5 Package: xserver-xorg-video-ati 1:18.0.1-1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: G1.Sniper B5-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd09/16/2014:svnGigabyteTechnologyCo.,Ltd.:pnG1.SniperB5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnG1.SniperB5-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: G1.Sniper B5 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: