2019-11-13 19:00:50 |
Juan Carlos Carvajal Bermúdez |
bug |
|
|
added bug |
2019-11-13 19:00:50 |
Juan Carlos Carvajal Bermúdez |
attachment added |
|
sudo lspci -vnvn > lspci-vnvn.log https://bugs.launchpad.net/bugs/1852479/+attachment/5305209/+files/lspci-vnvn.log |
|
2019-11-13 19:30:10 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
2019-11-13 19:53:25 |
Juan Carlos Carvajal Bermúdez |
tags |
|
apport-collected eoan |
|
2019-11-13 19:53:26 |
Juan Carlos Carvajal Bermúdez |
description |
My laptop just crashed spectacularly two times. I was using chrome both times but I am not sure if that is related. There was no possibility of rescuing the system whatsoever. I just dug into the logs.
probably related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173
kernel log:
rfkill: input handler disabled
pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
pcieport 0000:00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
pcieport 0000:00:1d.0: AER: device [8086:a330] error status/mask=00000001/00002000
pcieport 0000:00:1d.0: AER: [ 0] RxErr
pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
pcieport 0000:00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
pcieport 0000:00:1d.0: AER: device [8086:a330] error status/mask=00000001/00002000
pcieport 0000:00:1d.0: AER: [ 0] RxErr
pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
pcieport 0000:00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
pcieport 0000:00:1d.0: AER: device [8086:a330] error status/mask=00000001/00002000
pcieport 0000:00:1d.0: AER: [ 0] RxErr
pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
pcieport 0000:00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
pcieport 0000:00:1d.0: AER: device [8086:a330] error status/mask=00000001/00002000
pcieport 0000:00:1d.0: AER: [ 0] RxErr
pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
pcieport 0000:00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
pcieport 0000:00:1d.0: AER: device [8086:a330] error status/mask=00000001/00002000
pcieport 0000:00:1d.0: AER: [ 0] RxErr
pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
pcieport 0000:00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
pcieport 0000:00:1d.0: AER: device [8086:a330] error status/mask=00000001/00002000
pcieport 0000:00:1d.0: AER: [ 0] RxErr
pcieport 0000:00:1d.0: AER: Multiple Corrected error received: 0000:00:1d.0
pcieport 0000:00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
pcieport 0000:00:1d.0: AER: device [8086:a330] error status/mask=00000001/00002000
pcieport 0000:00:1d.0: AER: [ 0] RxErr
pcieport 0000:00:1d.0: AER: Multiple Corrected error received: 0000:00:1d.0
pcieport 0000:00:1d.0: AER: can't find device of ID00e8
pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
pcieport 0000:00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
pcieport 0000:00:1d.0: AER: device [8086:a330] error status/mask=00000001/00002000
pcieport 0000:00:1d.0: AER: [ 0] RxErr
pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
pcieport 0000:00:1d.0: AER: can't find device of ID00e8
pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
pcieport 0000:00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
pcieport 0000:00:1d.0: AER: device [8086:a330] error status/mask=00000001/00002000
pcieport 0000:00:1d.0: AER: [ 0] RxErr
pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
pcieport 0000:00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
pcieport 0000:00:1d.0: AER: device [8086:a330] error status/mask=00000001/00002000
pcieport 0000:00:1d.0: AER: [ 0] RxErr
pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
pcieport 0000:00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
pcieport 0000:00:1d.0: AER: device [8086:a330] error status/mask=00000001/00002000
pcieport 0000:00:1d.0: AER: [ 0] RxErr
pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
pcieport 0000:00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
pcieport 0000:00:1d.0: AER: device [8086:a330] error status/mask=00000001/00002000
pcieport 0000:00:1d.0: AER: [ 0] RxErr
pcieport 0000:00:1d.0: AER: Multiple Corrected error received: 0000:00:1d.0
pcieport 0000:00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
pcieport 0000:00:1d.0: AER: device [8086:a330] error status/mask=00000001/00002000
pcieport 0000:00:1d.0: AER: [ 0] RxErr
pcieport 0000:00:1d.0: AER: Error of this Agent is reported first
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER: device [144d:a808] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER: [ 0] RxErr
pcieport 0000:00:1d.0: AER: Corrected error received: 0000:03:00.0
pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
pcieport 0000:00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
pcieport 0000:00:1d.0: AER: device [8086:a330] error status/mask=00000001/00002000
pcieport 0000:00:1d.0: AER: [ 0] RxErr
pcieport 0000:00:1d.0: AER: Multiple Corrected error received: 0000:03:00.0
pcieport 0000:00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
pcieport 0000:00:1d.0: AER: device [8086:a330] error status/mask=00000001/00002000
pcieport 0000:00:1d.0: AER: [ 0] RxErr
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER: device [144d:a808] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER: [ 0] RxErr
nvme 0000:03:00.0: AER: Error of this Agent is reported first
lspci -tv
-[0000:00]-+-00.0 Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers
+-01.0-[01]--+-00.0 NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile]
| \-00.1 NVIDIA Corporation GP106 High Definition Audio Controller
+-02.0 Intel Corporation UHD Graphics 630 (Mobile)
+-12.0 Intel Corporation Cannon Lake PCH Thermal Controller
+-14.0 Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller
+-14.2 Intel Corporation Cannon Lake PCH Shared SRAM
+-15.0 Intel Corporation Cannon Lake PCH Serial IO I2C Controller #0
+-16.0 Intel Corporation Cannon Lake PCH HECI Controller
+-17.0 Intel Corporation Cannon Lake Mobile PCH SATA AHCI Controller
+-1b.0-[02]--
+-1d.0-[03]----00.0 Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
+-1d.5-[04]----00.0 Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
+-1d.6-[05]----00.0 Intel Corporation Wireless-AC 9260
+-1e.0 Intel Corporation Device a328
+-1e.3 Intel Corporation Device a32b
+-1f.0 Intel Corporation Device a30d
+-1f.3 Intel Corporation Cannon Lake PCH cAVS
+-1f.4 Intel Corporation Cannon Lake PCH SMBus Controller
\-1f.5 Intel Corporation Cannon Lake PCH SPI Controller
Ubuntu 5.3.0-20.21+system76~1572304854~19.10~8caa3e6-generic 5.3.7 |
My laptop just crashed spectacularly two times. I was using chrome both times but I am not sure if that is related. There was no possibility of rescuing the system whatsoever. I just dug into the logs.
probably related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173
kernel log:
rfkill: input handler disabled
pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
pcieport 0000:00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
pcieport 0000:00:1d.0: AER: device [8086:a330] error status/mask=00000001/00002000
pcieport 0000:00:1d.0: AER: [ 0] RxErr
pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
pcieport 0000:00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
pcieport 0000:00:1d.0: AER: device [8086:a330] error status/mask=00000001/00002000
pcieport 0000:00:1d.0: AER: [ 0] RxErr
pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
pcieport 0000:00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
pcieport 0000:00:1d.0: AER: device [8086:a330] error status/mask=00000001/00002000
pcieport 0000:00:1d.0: AER: [ 0] RxErr
pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
pcieport 0000:00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
pcieport 0000:00:1d.0: AER: device [8086:a330] error status/mask=00000001/00002000
pcieport 0000:00:1d.0: AER: [ 0] RxErr
pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
pcieport 0000:00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
pcieport 0000:00:1d.0: AER: device [8086:a330] error status/mask=00000001/00002000
pcieport 0000:00:1d.0: AER: [ 0] RxErr
pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
pcieport 0000:00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
pcieport 0000:00:1d.0: AER: device [8086:a330] error status/mask=00000001/00002000
pcieport 0000:00:1d.0: AER: [ 0] RxErr
pcieport 0000:00:1d.0: AER: Multiple Corrected error received: 0000:00:1d.0
pcieport 0000:00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
pcieport 0000:00:1d.0: AER: device [8086:a330] error status/mask=00000001/00002000
pcieport 0000:00:1d.0: AER: [ 0] RxErr
pcieport 0000:00:1d.0: AER: Multiple Corrected error received: 0000:00:1d.0
pcieport 0000:00:1d.0: AER: can't find device of ID00e8
pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
pcieport 0000:00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
pcieport 0000:00:1d.0: AER: device [8086:a330] error status/mask=00000001/00002000
pcieport 0000:00:1d.0: AER: [ 0] RxErr
pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
pcieport 0000:00:1d.0: AER: can't find device of ID00e8
pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
pcieport 0000:00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
pcieport 0000:00:1d.0: AER: device [8086:a330] error status/mask=00000001/00002000
pcieport 0000:00:1d.0: AER: [ 0] RxErr
pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
pcieport 0000:00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
pcieport 0000:00:1d.0: AER: device [8086:a330] error status/mask=00000001/00002000
pcieport 0000:00:1d.0: AER: [ 0] RxErr
pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
pcieport 0000:00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
pcieport 0000:00:1d.0: AER: device [8086:a330] error status/mask=00000001/00002000
pcieport 0000:00:1d.0: AER: [ 0] RxErr
pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
pcieport 0000:00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
pcieport 0000:00:1d.0: AER: device [8086:a330] error status/mask=00000001/00002000
pcieport 0000:00:1d.0: AER: [ 0] RxErr
pcieport 0000:00:1d.0: AER: Multiple Corrected error received: 0000:00:1d.0
pcieport 0000:00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
pcieport 0000:00:1d.0: AER: device [8086:a330] error status/mask=00000001/00002000
pcieport 0000:00:1d.0: AER: [ 0] RxErr
pcieport 0000:00:1d.0: AER: Error of this Agent is reported first
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER: device [144d:a808] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER: [ 0] RxErr
pcieport 0000:00:1d.0: AER: Corrected error received: 0000:03:00.0
pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
pcieport 0000:00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
pcieport 0000:00:1d.0: AER: device [8086:a330] error status/mask=00000001/00002000
pcieport 0000:00:1d.0: AER: [ 0] RxErr
pcieport 0000:00:1d.0: AER: Multiple Corrected error received: 0000:03:00.0
pcieport 0000:00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
pcieport 0000:00:1d.0: AER: device [8086:a330] error status/mask=00000001/00002000
pcieport 0000:00:1d.0: AER: [ 0] RxErr
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER: device [144d:a808] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER: [ 0] RxErr
nvme 0000:03:00.0: AER: Error of this Agent is reported first
lspci -tv
-[0000:00]-+-00.0 Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers
+-01.0-[01]--+-00.0 NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile]
| \-00.1 NVIDIA Corporation GP106 High Definition Audio Controller
+-02.0 Intel Corporation UHD Graphics 630 (Mobile)
+-12.0 Intel Corporation Cannon Lake PCH Thermal Controller
+-14.0 Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller
+-14.2 Intel Corporation Cannon Lake PCH Shared SRAM
+-15.0 Intel Corporation Cannon Lake PCH Serial IO I2C Controller #0
+-16.0 Intel Corporation Cannon Lake PCH HECI Controller
+-17.0 Intel Corporation Cannon Lake Mobile PCH SATA AHCI Controller
+-1b.0-[02]--
+-1d.0-[03]----00.0 Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
+-1d.5-[04]----00.0 Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
+-1d.6-[05]----00.0 Intel Corporation Wireless-AC 9260
+-1e.0 Intel Corporation Device a328
+-1e.3 Intel Corporation Device a32b
+-1f.0 Intel Corporation Device a30d
+-1f.3 Intel Corporation Cannon Lake PCH cAVS
+-1f.4 Intel Corporation Cannon Lake PCH SMBus Controller
\-1f.5 Intel Corporation Cannon Lake PCH SPI Controller
Ubuntu 5.3.0-20.21+system76~1572304854~19.10~8caa3e6-generic 5.3.7
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: pop:GNOME
DistroRelease: Pop!_OS 19.10
MachineType: SchenkerTechnologiesGmbH XMG NEO 15 - XNE15M18
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-20-generic root=UUID=ce33b159-ce12-4227-92f3-3ea93527e6d4 ro quiet splash pci=noaer vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-20.21+system76~1572304854~19.10~8caa3e6-generic 5.3.7
RelatedPackageVersions:
linux-restricted-modules-5.3.0-20-generic N/A
linux-backports-modules-5.3.0-20-generic N/A
linux-firmware 1.183.1+system76~1571781891~19.10~fb0e8b8
Tags: eoan
Uname: Linux 5.3.0-20-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-08-19 (86 days ago)
UserGroups: adm dialout sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/29/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N.1.09
dmi.board.asset.tag: Standard
dmi.board.name: GK5CN6Z
dmi.board.vendor: SchenkerTechnologiesGmbH
dmi.board.version: Standard
dmi.chassis.asset.tag: Standard
dmi.chassis.type: 10
dmi.chassis.vendor: SchenkerTechnologiesGmbH
dmi.chassis.version: Standard
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.09:bd11/29/2018:svnSchenkerTechnologiesGmbH:pnXMGNEO15-XNE15M18:pvrStandard:rvnSchenkerTechnologiesGmbH:rnGK5CN6Z:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:
dmi.product.family: CFL
dmi.product.name: XMG NEO 15 - XNE15M18
dmi.product.sku: XNE15M18
dmi.product.version: Standard
dmi.sys.vendor: SchenkerTechnologiesGmbH |
|
2019-11-13 19:53:27 |
Juan Carlos Carvajal Bermúdez |
attachment added |
|
AlsaInfo.txt https://bugs.launchpad.net/bugs/1852479/+attachment/5305212/+files/AlsaInfo.txt |
|
2019-11-13 19:53:28 |
Juan Carlos Carvajal Bermúdez |
attachment added |
|
AudioDevicesInUse.txt https://bugs.launchpad.net/bugs/1852479/+attachment/5305213/+files/AudioDevicesInUse.txt |
|
2019-11-13 19:53:30 |
Juan Carlos Carvajal Bermúdez |
attachment added |
|
CRDA.txt https://bugs.launchpad.net/bugs/1852479/+attachment/5305214/+files/CRDA.txt |
|
2019-11-13 19:53:32 |
Juan Carlos Carvajal Bermúdez |
attachment added |
|
CurrentDmesg.txt https://bugs.launchpad.net/bugs/1852479/+attachment/5305215/+files/CurrentDmesg.txt |
|
2019-11-13 19:53:33 |
Juan Carlos Carvajal Bermúdez |
attachment added |
|
IwConfig.txt https://bugs.launchpad.net/bugs/1852479/+attachment/5305216/+files/IwConfig.txt |
|
2019-11-13 19:53:34 |
Juan Carlos Carvajal Bermúdez |
attachment added |
|
Lspci.txt https://bugs.launchpad.net/bugs/1852479/+attachment/5305217/+files/Lspci.txt |
|
2019-11-13 19:53:36 |
Juan Carlos Carvajal Bermúdez |
attachment added |
|
Lsusb.txt https://bugs.launchpad.net/bugs/1852479/+attachment/5305218/+files/Lsusb.txt |
|
2019-11-13 19:53:37 |
Juan Carlos Carvajal Bermúdez |
attachment added |
|
ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1852479/+attachment/5305219/+files/ProcCpuinfo.txt |
|
2019-11-13 19:53:39 |
Juan Carlos Carvajal Bermúdez |
attachment added |
|
ProcCpuinfoMinimal.txt https://bugs.launchpad.net/bugs/1852479/+attachment/5305220/+files/ProcCpuinfoMinimal.txt |
|
2019-11-13 19:53:40 |
Juan Carlos Carvajal Bermúdez |
attachment added |
|
ProcEnviron.txt https://bugs.launchpad.net/bugs/1852479/+attachment/5305221/+files/ProcEnviron.txt |
|
2019-11-13 19:53:42 |
Juan Carlos Carvajal Bermúdez |
attachment added |
|
ProcInterrupts.txt https://bugs.launchpad.net/bugs/1852479/+attachment/5305222/+files/ProcInterrupts.txt |
|
2019-11-13 19:53:45 |
Juan Carlos Carvajal Bermúdez |
attachment added |
|
ProcModules.txt https://bugs.launchpad.net/bugs/1852479/+attachment/5305223/+files/ProcModules.txt |
|
2019-11-13 19:53:47 |
Juan Carlos Carvajal Bermúdez |
attachment added |
|
PulseList.txt https://bugs.launchpad.net/bugs/1852479/+attachment/5305224/+files/PulseList.txt |
|
2019-11-13 19:53:49 |
Juan Carlos Carvajal Bermúdez |
attachment added |
|
RfKill.txt https://bugs.launchpad.net/bugs/1852479/+attachment/5305225/+files/RfKill.txt |
|
2019-11-13 19:53:51 |
Juan Carlos Carvajal Bermúdez |
attachment added |
|
UdevDb.txt https://bugs.launchpad.net/bugs/1852479/+attachment/5305226/+files/UdevDb.txt |
|
2019-11-13 19:53:53 |
Juan Carlos Carvajal Bermúdez |
attachment added |
|
WifiSyslog.txt https://bugs.launchpad.net/bugs/1852479/+attachment/5305227/+files/WifiSyslog.txt |
|
2019-11-13 19:54:28 |
Juan Carlos Carvajal Bermúdez |
linux (Ubuntu): status |
Incomplete |
Confirmed |
|
2019-11-17 16:10:15 |
Juan Carlos Carvajal Bermúdez |
marked as duplicate |
|
1746340 |
|
2019-12-05 12:12:02 |
Juan Carlos Carvajal Bermúdez |
bug watch added |
|
https://bugzilla.kernel.org/show_bug.cgi?id=195039 |
|