[Kernel-packages] [Bug 1857152] Re: NVMe drive not properly detected (using 5.4.0-9-generic)

[Kai-Heng Feng]

Should be fixed by this commit:
commit 22802bf742c25b1e2473c70b3b99da98af65ef4d
Author: Keith Busch 
Date:   Tue Dec 3 00:44:59 2019 +0900

nvme: Namepace identification descriptor list is optional

Despite NVM Express specification 1.3 requires a controller claiming to
be 1.3 or higher implement Identify CNS 03h (Namespace Identification
Descriptor list), the driver doesn't really need this identification in
order to use a namespace. The code had already documented in comments
that we're not to consider an error to this command.

Return success if the controller provided any response to an
namespace identification descriptors command.

Fixes: 538af88ea7d9de24 ("nvme: make nvme_report_ns_ids propagate error 
back")
Link: https://bugzilla.kernel.org/show_bug.cgi?id=205679
Reported-by: Ingo Brunberg 
Cc: Sagi Grimberg 
Cc: sta...@vger.kernel.org # 5.4+
Reviewed-by: Christoph Hellwig 
Signed-off-by: Keith Busch 

It's in upstream stable kernel so we'll get this update soon.

** Bug watch added: Linux Kernel Bug Tracker #205679
   https://bugzilla.kernel.org/show_bug.cgi?id=205679

-- 
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/1857152

Title:
  NVMe drive not properly detected (using 5.4.0-9-generic)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Windows partition on an NVMe drive in my machine.  I have
  confirmed that the drive is still functional by using it as the boot
  device from the BIOS menu.  When I boot into Ubuntu, the drive is
  somewhat acknowledged, in that /dev/nvme0 exists, but the partitions
  are not discovered.

  Examining the journal, I see the following emitted from the kernel:

  $ journalctl | grep nvme
  Dec 20 11:30:04 surprise kernel: nvme nvme0: pci function :01:00.0
  Dec 20 11:30:04 surprise kernel: nvme nvme0: missing or invalid SUBNQN field.
  Dec 20 11:30:04 surprise kernel: nvme nvme0: allocated 64 MiB host memory 
buffer.
  Dec 20 11:30:04 surprise kernel: nvme nvme0: 15/0/0 default/read/poll queues
  Dec 20 11:30:04 surprise kernel: nvme nvme0: Identify Descriptors failed (2)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu14
  Architecture: amd64
  CurrentDesktop: i3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-05-07 (226 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=UUID=73909634-a75d-42c9-8f66-a69138690756 
nvme_core.default_ps_max_latency_us=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-9-generic N/A
   linux-backports-modules-5.4.0-9-generic  N/A
   linux-firmware   1.184
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-9-generic x86_64
  UpgradeStatus: Upgraded to focal on 2019-11-15 (34 days ago)
  UserGroups: adm boinc cdrom dip docker libvirt lpadmin lxd plugdev sambashare 
sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 01/25/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-25T16:40:26.261317

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857152/+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 1849830] Re: usb_set_interface failed (-110) when connecting a videoconference peripheral

[Kai-Heng Feng]

Can you please boot with kernel parameter "log_buf_len=32M dyndbg='file
drivers/usb/* +p'" and attach dmesg?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849830

Title:
  usb_set_interface failed (-110) when connecting a videoconference
  peripheral

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The VideConference peripheral is a LogiGroup with camera, micro and
  audio. Camera works fine, but micro and audio fails. The LogiGroup
  system is connected using a single USB port. In other Linux laptop, it
  works fine

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-19-generic 5.3.0-19.20
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   carlos 1859 F...m pulseaudio
   /dev/snd/controlC0:  carlos 1859 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Oct 25 15:01:12 2019
  InstallationDate: Installed on 2019-10-24 (0 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. XPS 13 7390
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 0G2D0W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd08/23/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849830/+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 1856387] Re: Freezing on boot since kernel 4.15.0-72-generic release

[Anthony Buckley]

Hello,
I have completed the bisect as requested and identified the problem commit. The 
bisect message is as follows:-

git bisect good
f723dd269d0740e09af47bb5590ffc4f61766153 is the first bad commit
commit f723dd269d0740e09af47bb5590ffc4f61766153
Author: Thomas Gleixner 
Date:   Thu Nov 7 09:05:00 2019 +0100

x86/timer: Skip PIT initialization on modern chipsets

BugLink: https://bugs.launchpad.net/bugs/1851216

Recent Intel chipsets including Skylake and ApolloLake have a special
ITSSPRC register which allows the 8254 PIT to be gated.  When gated, the
8254 registers can still be programmed as normal, but there are no IRQ0
timer interrupts.

Some products such as the Connex L1430 and exone go Rugged E11 use this
register to ship with the PIT gated by default. This causes Linux to fail
to boot:

  Kernel panic - not syncing: IO-APIC + timer doesn't work! Boot with
  apic=debug and send a report.

The panic happens before the framebuffer is initialized, so to the user, it
appears as an early boot hang on a black screen.

Affected products typically have a BIOS option that can be used to enable
the 8254 and make Linux work (Chipset -> South Cluster Configuration ->
Miscellaneous Configuration -> 8254 Clock Gating), however it would be best
to make Linux support the no-8254 case.

Modern sytems allow to discover the TSC and local APIC timer frequencies,
so the calibration against the PIT is not required. These systems have
always running timers and the local APIC timer works also in deep power
states.

So the setup of the PIT including the IO-APIC timer interrupt delivery
checks are a pointless exercise.

Skip the PIT setup and the IO-APIC timer interrupt checks on these systems,
which avoids the panic caused by non ticking PITs and also speeds up the
boot process.

Thanks to Daniel for providing the changelog, initial analysis of the
problem and testing against a variety of machines.

Reported-by: Daniel Drake 
Signed-off-by: Thomas Gleixner 
Tested-by: Daniel Drake 
Cc: b...@alien8.de
Cc: h...@zytor.com
Cc: li...@endlessm.com
Cc: rafael.j.wyso...@intel.com
Cc: hdego...@redhat.com
Link: https://lkml.kernel.org/r/20190628072307.24678-1-dr...@endlessm.com

(backported from commit c8c4076723daca08bf35ccd68f22ea1c6219e207)
Signed-off-by: You-Sheng Yang 
Acked-by: Stefan Bader 
Acked-by: Connor Kuehl 
Signed-off-by: Stefan Bader 

:04 04 9c51f067713006f928684555c3254e89bdc10361
ad4d7a34eed39a733c78e630f4d9125f67e001bb M  arch


Regards

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1856387

Title:
  Freezing on boot since kernel 4.15.0-72-generic release

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After the update to install kernel 4.15.0-72-generic (a bit over a week ago) 
my computer will not boot. On boot, all I see is the purple screen with:
  Loading Linux 4.15.0-72-generic ...
  Loading initial ramdisk ...
  and nothing happens. Just sits there. I've waited about 5-10 minutes on 
occasion but to no avail.
  I've checked a number of logs in /var/log but not found anything.

  If I go into the advanced options and select kernel
  4.15.0-70-generic, the computer boots normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-72-generic 4.15.0-72.81
  ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
  Uname: Linux 4.15.0-70-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tony   1977 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 14 21:53:14 2019
  HibernationDevice: RESUME=UUID=5475ce25-e091-45e2-9811-9b5cddc08dd1
  InstallationDate: Installed on 2018-09-16 (454 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 046d:c063 Logitech, Inc. DELL Laser Mouse
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GIGABYTE Sabre 17WV8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic 
root=UUID=9455257c-d3b7-4d61-853d-ab0b0ee40013 ro acpi=off
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-70-generic N/A
   linux-backports-modules-4.15.0-70-generic  N/A
   linux-firmware 1.173.13
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F05
  dmi.board.asset.tag: Tag 1234

[Kernel-packages] [Bug 1856308] Re: [Realtek Audio Codec ALC294] [ASUS R542UF] Since Linux 4.20 and newer no sound at all

[fademind]

Disabling SND_HDA_INTEL_DETECT_DMIC does job and sounds back in.

snd_hda_intel.dmic_detect=0

https://cateee.net/lkddb/web-lkddb/SND_HDA_INTEL_DETECT_DMIC.html

-- 
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/1856308

Title:
  [Realtek Audio Codec ALC294] [ASUS R542UF] Since Linux 4.20 and newer
  no sound at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Similar issue https://bugs.launchpad.net/ubuntu/+source/alsa-
  driver/+bug/1784485

  tl;dr

  I have sound only under 4.19.x series. 
  I have NOT sound at all under newer kernel series. 

  HW Details:
  ```
  kubuntu@kubuntu:~$ sudo hwinfo --sound
  20: PCI 1f.3: 0403 Audio device 
[Created at pci.386]
Unique ID: nS1_.b28td23g3aB
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Sunrise Point-LP HD Audio"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x9d71 "Sunrise Point-LP HD Audio"
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x1a00 
Revision: 0x21
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xef528000-0xef52bfff (rw,non-prefetchable)
Memory Range: 0xef50-0xef50 (rw,non-prefetchable)
IRQ: 132 (1577 events)
Module Alias: "pci:v8086d9D71sv1043sd1A00bc04sc03i00"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Driver Info #1:
  Driver Status: snd_soc_skl is active
  Driver Activation Cmd: "modprobe snd_soc_skl"
Config Status: cfg=new, avail=yes, need=no, active=unknown
  ```
  ```
   Linux version 5.3.0-24-generic (buildd@lgw01-amd64-035) (gcc version 9.2.1 
20191008 (Ubuntu 9.2.1-9ubuntu2)) #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 
(Ubuntu 5.3.0-24.26-generic 5.3.10)
  ```
  ```
  [0.00] efi: EFI v2.60 by American Megatrends
  [0.00] efi:  TPMFinalLog=0x8adf  ACPI 2.0=0x8a98d000  
ACPI=0x8a98d000  SMBIOS=0x8b214000  SMBIOS 3.0=0x8b213000  ESRT=0x884d4e98  
MEMATTR=0x8739a018 
  [0.00] secureboot: Secure boot could not be determined (mode 0)
  [0.00] SMBIOS 3.0.0 present.
  [0.00] DMI: ASUSTeK COMPUTER INC. VivoBook 15_ASUS Laptop 
X542UF/X542UF, BIOS X542UF.307 06/13/2019
  [0.00] tsc: Detected 1800.000 MHz processor
  [0.00] [Firmware Bug]: TSC ADJUST: CPU0: -214721515 force to 0
  ```
  ```
  kubuntu@kubuntu:~$ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 08)
  00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07)
  00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 08)
  00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #0 (rev 21)
  00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #1 (rev 21)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME 
HECI #1 (rev 21)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller 
[AHCI mode] (rev 21)
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#1 (rev f1)
  00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#5 (rev f1)
  00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#6 (rev f1)
  00:1e.0 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO UART Controller #0 (rev 21)
  00:1e.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO SPI Controller #0 (rev 21)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point LPC Controller/eSPI 
Controller (rev 21)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
  01:00.0 3D controller: NVIDIA Corporation GM108M [GeForce MX130] (rev a2)
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
  03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter (rev 31)
  ```
  ```
  kubuntu@kubuntu:~$ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC294 Analog [ALC294 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice 

[Kernel-packages] [Bug 1836176] Re: Touchscreen stops working after S3 suspend on Lenovo X1 Yoga 3th

[Kai-Heng Feng]

Can you please test kernel parameter "usbcore.quirks=056a:5146:m"?

-- 
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/1836176

Title:
  Touchscreen stops working after S3 suspend on Lenovo X1 Yoga 3th

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Fedora:
  Confirmed

Bug description:
  As described above. With the last BIOS-updates Lenovo enabled proper
  S3 deep sleep mode for Linux. Sadly the touchscreen doesn't work after
  resuming. There are a lot of others facing the same problem:

  https://forums.lenovo.com/t5/Other-Linux-Discussions/X1Y3-Touchscreen-
  not-working-after-resume-on-Linux/td-p/4021200/highlight/false

  A workaround described in the Arch-wiki doesn't seem to work on
  Ubuntu:
  
https://wiki.archlinux.org/index.php/Lenovo_ThinkPad_X1_Yoga_(Gen_3)#Fix_touchscreen_after_resume

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-20-generic 5.0.0-20.21
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   4186 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 11 11:19:05 2019
  HibernationDevice: RESUME=UUID=1c3b8070-c343-4dbf-8fe2-4112233d7954
  InstallationDate: Installed on 2018-11-30 (222 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20LES01W00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic 
root=UUID=d887a86a-3729-4962-9692-d9db9d49ed4c ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-20-generic N/A
   linux-backports-modules-5.0.0-20-generic  N/A
   linux-firmware1.178.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-04-14 (87 days ago)
  dmi.bios.date: 06/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N25ET49W (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LES01W00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN25ET49W(1.35):bd06/12/2019:svnLENOVO:pn20LES01W00:pvrThinkPadX1Yoga3rd:rvnLENOVO:rn20LES01W00:rvrNotDefined:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 3rd
  dmi.product.name: 20LES01W00
  dmi.product.sku: LENOVO_MT_20LE_BU_Think_FM_ThinkPad X1 Yoga 3rd
  dmi.product.version: ThinkPad X1 Yoga 3rd
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836176/+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 1850130] Re: zpools fail to import after reboot on fresh install of eoan

[Richard Laager]

Try adding "After=multipathd.service" to zfs-import-cache.service and
zfs-import-pool.service. If that fixes it, then we should probably add
that upstream.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1850130

Title:
  zpools fail to import after reboot on fresh install of eoan

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  Fresh installation of stock Ubuntu 19.10 Eoan with experimental root on ZFS.
  System has existing zpools with data.

  Installation is uneventful. First boot with no problems. Updates
  applied. No other changes from fresh installation. Reboot.

  External pool 'tank' imports with no errors. Reboot.

  External pool has failed to import on boot. In contrast bpool and
  rpool are ok. Manually re-import 'tank' with no issues. I can see both
  'tank' and its path in /dev/disk/by-id/ in /etc/zfs/zpool.cache.
  Reboot.

  'tank' has failed to import on boot. It is also missing from
  /etc/zfs/zpool.cache. Is it possible that the cache is being re-
  generated on reboot, and the newly imported pools are getting erased
  from it? I can re-import the pools again manually with no issues, but
  they don't persist between re-boots.

  Installing normally on ext4 this is not an issue and data pools import
  automatically on boot with no further effort.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1850130/+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 1858254] Re: thermald: [ERR]THD engine start failed

[Clinton H]

** Description changed:

  1) Ubuntu 19.10
  2) 1.9
  3) No error in log app.
  4) See error below.
  
+ Dec 29 2019  9:28:18 PM systemd: Starting GRUB failed boot detection...
+ Dec 29 2019  9:28:21 PM kernel: vboxdrv: module verification failed: 
signature and/or required key missing - tainting kernel
  Dec 29 2019  9:28:26 PM thermald: [ERR]THD engine start failed
  Dec 29 2019  9:28:26 PM systemd: Started GRUB failed boot detection.
- Dec 29 2019  9:28:21 PM kernel: vboxdrv: module verification failed: 
signature and/or required key missing - tainting kernel
- Dec 29 2019  9:28:18 PM systemd: Starting GRUB failed boot detection...
- 
  Dec 29 2019  9:28:26 PM thermald: [ERR]THD engine start failed
  Dec 29 2019  9:28:26 PM thermald: [ERR]THD engine start failed
  Dec 29 2019  9:28:26 PM thermald: I/O warning : failed to load external 
entity "/etc/thermald/thermal-conf.xml"

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1858254

Title:
  thermald: [ERR]THD engine start failed

Status in thermald package in Ubuntu:
  New

Bug description:
  1) Ubuntu 19.10
  2) 1.9
  3) No error in log app.
  4) See error below.

  Dec 29 2019  9:28:18 PM systemd: Starting GRUB failed boot detection...
  Dec 29 2019  9:28:21 PM kernel: vboxdrv: module verification failed: 
signature and/or required key missing - tainting kernel
  Dec 29 2019  9:28:26 PM thermald: [ERR]THD engine start failed
  Dec 29 2019  9:28:26 PM systemd: Started GRUB failed boot detection.
  Dec 29 2019  9:28:26 PM thermald: [ERR]THD engine start failed
  Dec 29 2019  9:28:26 PM thermald: [ERR]THD engine start failed
  Dec 29 2019  9:28:26 PM thermald: I/O warning : failed to load external 
entity "/etc/thermald/thermal-conf.xml"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1858254/+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 1858254] [NEW] thermald: [ERR]THD engine start failed

[Clinton H]

Public bug reported:

1) Ubuntu 19.10
2) 1.9
3) No error in log app.
4) See error below.

Dec 29 2019  9:28:26 PM thermald: [ERR]THD engine start failed
Dec 29 2019  9:28:26 PM systemd: Started GRUB failed boot detection.
Dec 29 2019  9:28:21 PM kernel: vboxdrv: module verification failed: signature 
and/or required key missing - tainting kernel
Dec 29 2019  9:28:18 PM systemd: Starting GRUB failed boot detection...

Dec 29 2019  9:28:26 PM thermald: [ERR]THD engine start failed
Dec 29 2019  9:28:26 PM thermald: [ERR]THD engine start failed
Dec 29 2019  9:28:26 PM thermald: I/O warning : failed to load external entity 
"/etc/thermald/thermal-conf.xml"

** Affects: thermald (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1858254

Title:
  thermald: [ERR]THD engine start failed

Status in thermald package in Ubuntu:
  New

Bug description:
  1) Ubuntu 19.10
  2) 1.9
  3) No error in log app.
  4) See error below.

  Dec 29 2019  9:28:26 PM thermald: [ERR]THD engine start failed
  Dec 29 2019  9:28:26 PM systemd: Started GRUB failed boot detection.
  Dec 29 2019  9:28:21 PM kernel: vboxdrv: module verification failed: 
signature and/or required key missing - tainting kernel
  Dec 29 2019  9:28:18 PM systemd: Starting GRUB failed boot detection...

  Dec 29 2019  9:28:26 PM thermald: [ERR]THD engine start failed
  Dec 29 2019  9:28:26 PM thermald: [ERR]THD engine start failed
  Dec 29 2019  9:28:26 PM thermald: I/O warning : failed to load external 
entity "/etc/thermald/thermal-conf.xml"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1858254/+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 1838796] Re: TPM event log does not contain events measured after ExitBootServices

[VINAY RAJESH]

Hi Chris,

Can you please point me to the parser tool that you used to parse the
binary_bios_measurements? We can try that tool at our end to see if the
our tool has a bug.

-- 
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/1838796

Title:
  TPM event log does not contain events measured after ExitBootServices

Status in linux package in Ubuntu:
  Won't Fix
Status in linux-azure package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Won't Fix
Status in linux-azure source package in Xenial:
  In Progress
Status in linux source package in Disco:
  Won't Fix
Status in linux-azure source package in Disco:
  In Progress

Bug description:
  The TPM event log (/sys/kernel/security/tpm0/binary_bios_measurements)
  does not contain any events that are measured by UEFI after the
  kernel's EFI Boot stub calls ExitBootServices().

  This means that PCR values calculated from the event log will not
  match the actual PCR values on the machine for PCR indices into which
  these events are measured.

  There are upstream patches to fix this in the mainline kernel tree: 
https://lore.kernel.org/lkml/20190520205501.177637-1-matthewgarr...@google.com/
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  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
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-06-20 (43 days ago)
  InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  Lspci:

  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic 
root=UUID=fcb8dc9d-4dd3-490f-9f1c-fa6364770bb0 ro
  ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-22-generic N/A
   linux-backports-modules-4.18.0-22-generic  N/A
   linux-firmware 1.173.3
  RfKill:

  Tags:  bionic
  Uname: Linux 4.18.0-22-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: 01/30/2019
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.0
  dmi.chassis.asset.tag: 8486-4870-7514-9524-5524-7794-69
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v4.0
  dmi.sys.vendor: Microsoft Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838796/+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 1858182] WifiSyslog.txt

[Ryan Bach]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1858182/+attachment/5317506/+files/WifiSyslog.txt

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1858182

Title:
  Add support for Rizon 3900 Series Processors by updating to a newer
  kernel version

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  According to:
  https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.4.7
  -Stable-Released

  "Greg Kroah-Hartman took time out of his New Year's Eve festivities to
  release Linux 5.4.7, 4.19.92, and 4.14.161 as the newest supported
  stable releases of the Linux kernel.

  Making these kernels noteworthy is that they contain the necessary MCE
  fix for booting the new AMD Ryzen Threadripper 3900 series processors.
  With Linux 5.5 mainline or these back-ported kernels, Linux should be
  booting now without issue.

  These stable kernel updates also add Intel Comet Lake PCH-V and Elkhart Lake 
SoC support to the intel_th driver. But the rest of the changes are an 
assortment of mostly mundane fixes, unless you happened to be affected by one 
of the particular bugs addressed."
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  ryan   2274 F pulseaudio
   /dev/snd/controlC0:  ryan   2274 F pulseaudio
   /dev/snd/controlC1:  ryan   2274 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-02 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200101)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rsu7l4@/vmlinuz-5.4.0-9-generic 
root=ZFS=rpool/ROOT/ubuntu_rsu7l4 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-9-generic N/A
   linux-backports-modules-5.4.0-9-generic  N/A
   linux-firmware   1.184
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-9-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: 04/03/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99X EVO R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr2501:bd04/03/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: SKU
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858182/+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 1858182] UdevDb.txt

[Ryan Bach]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1858182/+attachment/5317505/+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/1858182

Title:
  Add support for Rizon 3900 Series Processors by updating to a newer
  kernel version

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  According to:
  https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.4.7
  -Stable-Released

  "Greg Kroah-Hartman took time out of his New Year's Eve festivities to
  release Linux 5.4.7, 4.19.92, and 4.14.161 as the newest supported
  stable releases of the Linux kernel.

  Making these kernels noteworthy is that they contain the necessary MCE
  fix for booting the new AMD Ryzen Threadripper 3900 series processors.
  With Linux 5.5 mainline or these back-ported kernels, Linux should be
  booting now without issue.

  These stable kernel updates also add Intel Comet Lake PCH-V and Elkhart Lake 
SoC support to the intel_th driver. But the rest of the changes are an 
assortment of mostly mundane fixes, unless you happened to be affected by one 
of the particular bugs addressed."
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  ryan   2274 F pulseaudio
   /dev/snd/controlC0:  ryan   2274 F pulseaudio
   /dev/snd/controlC1:  ryan   2274 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-02 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200101)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rsu7l4@/vmlinuz-5.4.0-9-generic 
root=ZFS=rpool/ROOT/ubuntu_rsu7l4 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-9-generic N/A
   linux-backports-modules-5.4.0-9-generic  N/A
   linux-firmware   1.184
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-9-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: 04/03/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99X EVO R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr2501:bd04/03/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: SKU
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858182/+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 1858182] CRDA.txt

[Ryan Bach]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1858182/+attachment/5317494/+files/CRDA.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/1858182

Title:
  Add support for Rizon 3900 Series Processors by updating to a newer
  kernel version

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  According to:
  https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.4.7
  -Stable-Released

  "Greg Kroah-Hartman took time out of his New Year's Eve festivities to
  release Linux 5.4.7, 4.19.92, and 4.14.161 as the newest supported
  stable releases of the Linux kernel.

  Making these kernels noteworthy is that they contain the necessary MCE
  fix for booting the new AMD Ryzen Threadripper 3900 series processors.
  With Linux 5.5 mainline or these back-ported kernels, Linux should be
  booting now without issue.

  These stable kernel updates also add Intel Comet Lake PCH-V and Elkhart Lake 
SoC support to the intel_th driver. But the rest of the changes are an 
assortment of mostly mundane fixes, unless you happened to be affected by one 
of the particular bugs addressed."
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  ryan   2274 F pulseaudio
   /dev/snd/controlC0:  ryan   2274 F pulseaudio
   /dev/snd/controlC1:  ryan   2274 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-02 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200101)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rsu7l4@/vmlinuz-5.4.0-9-generic 
root=ZFS=rpool/ROOT/ubuntu_rsu7l4 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-9-generic N/A
   linux-backports-modules-5.4.0-9-generic  N/A
   linux-firmware   1.184
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-9-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: 04/03/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99X EVO R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr2501:bd04/03/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: SKU
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858182/+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 1858182] PulseList.txt

[Ryan Bach]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1858182/+attachment/5317504/+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/1858182

Title:
  Add support for Rizon 3900 Series Processors by updating to a newer
  kernel version

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  According to:
  https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.4.7
  -Stable-Released

  "Greg Kroah-Hartman took time out of his New Year's Eve festivities to
  release Linux 5.4.7, 4.19.92, and 4.14.161 as the newest supported
  stable releases of the Linux kernel.

  Making these kernels noteworthy is that they contain the necessary MCE
  fix for booting the new AMD Ryzen Threadripper 3900 series processors.
  With Linux 5.5 mainline or these back-ported kernels, Linux should be
  booting now without issue.

  These stable kernel updates also add Intel Comet Lake PCH-V and Elkhart Lake 
SoC support to the intel_th driver. But the rest of the changes are an 
assortment of mostly mundane fixes, unless you happened to be affected by one 
of the particular bugs addressed."
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  ryan   2274 F pulseaudio
   /dev/snd/controlC0:  ryan   2274 F pulseaudio
   /dev/snd/controlC1:  ryan   2274 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-02 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200101)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rsu7l4@/vmlinuz-5.4.0-9-generic 
root=ZFS=rpool/ROOT/ubuntu_rsu7l4 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-9-generic N/A
   linux-backports-modules-5.4.0-9-generic  N/A
   linux-firmware   1.184
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-9-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: 04/03/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99X EVO R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr2501:bd04/03/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: SKU
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858182/+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 1858182] Re: Add support for Rizon 3900 Series Processors by updating to a newer kernel version

[Ryan Bach]

apport information

** Tags added: apport-collected focal

** Description changed:

  According to:
  https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.4.7-Stable-
  Released
  
  "Greg Kroah-Hartman took time out of his New Year's Eve festivities to
  release Linux 5.4.7, 4.19.92, and 4.14.161 as the newest supported
  stable releases of the Linux kernel.
  
  Making these kernels noteworthy is that they contain the necessary MCE
  fix for booting the new AMD Ryzen Threadripper 3900 series processors.
  With Linux 5.5 mainline or these back-ported kernels, Linux should be
  booting now without issue.
  
- These stable kernel updates also add Intel Comet Lake PCH-V and Elkhart
- Lake SoC support to the intel_th driver. But the rest of the changes are
- an assortment of mostly mundane fixes, unless you happened to be
- affected by one of the particular bugs addressed."
+ These stable kernel updates also add Intel Comet Lake PCH-V and Elkhart Lake 
SoC support to the intel_th driver. But the rest of the changes are an 
assortment of mostly mundane fixes, unless you happened to be affected by one 
of the particular bugs addressed."
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu15
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC2:  ryan   2274 F pulseaudio
+  /dev/snd/controlC0:  ryan   2274 F pulseaudio
+  /dev/snd/controlC1:  ryan   2274 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-01-02 (1 days ago)
+ InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200101)
+ IwConfig:
+  enp2s0no wireless extensions.
+  
+  lono wireless extensions.
+ MachineType: To be filled by O.E.M. To be filled by O.E.M.
+ NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 amdgpudrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rsu7l4@/vmlinuz-5.4.0-9-generic 
root=ZFS=rpool/ROOT/ubuntu_rsu7l4 ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
+ RelatedPackageVersions:
+  linux-restricted-modules-5.4.0-9-generic N/A
+  linux-backports-modules-5.4.0-9-generic  N/A
+  linux-firmware   1.184
+ RfKill:
+  0: hci0: Bluetooth
+   Soft blocked: no
+   Hard blocked: no
+ Tags:  focal
+ Uname: Linux 5.4.0-9-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: 04/03/2014
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 2501
+ dmi.board.asset.tag: To be filled by O.E.M.
+ dmi.board.name: M5A99X EVO R2.0
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: Rev 1.xx
+ 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.:bvr2501:bd04/03/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
+ dmi.product.family: To be filled by O.E.M.
+ dmi.product.name: To be filled by O.E.M.
+ dmi.product.sku: SKU
+ dmi.product.version: To be filled by O.E.M.
+ dmi.sys.vendor: To be filled by O.E.M.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1858182/+attachment/5317493/+files/AlsaInfo.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/1858182

Title:
  Add support for Rizon 3900 Series Processors by updating to a newer
  kernel version

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  According to:
  https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.4.7
  -Stable-Released

  "Greg Kroah-Hartman took time out of his New Year's Eve festivities to
  release Linux 5.4.7, 4.19.92, and 4.14.161 as the newest supported
  stable releases of the Linux kernel.

  Making these kernels noteworthy is that they contain the necessary MCE
  fix for booting the new AMD Ryzen Threadripper 3900 series processors.
  With Linux 5.5 mainline or these back-ported kernels, Linux should be
  booting now without issue.

  These stable kernel updates also add Intel Comet Lake PCH-V and Elkhart Lake 
SoC support to the intel_th driver. But the rest of the changes are an 
assortment of mostly mundane fixes, unless you happened to be affected by one 
of the particular bugs addressed."
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  ryan   2274 F pulseaudio
   /dev/s

[Kernel-packages] [Bug 1858182] Lspci.txt

[Ryan Bach]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1858182/+attachment/5317496/+files/Lspci.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1858182

Title:
  Add support for Rizon 3900 Series Processors by updating to a newer
  kernel version

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  According to:
  https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.4.7
  -Stable-Released

  "Greg Kroah-Hartman took time out of his New Year's Eve festivities to
  release Linux 5.4.7, 4.19.92, and 4.14.161 as the newest supported
  stable releases of the Linux kernel.

  Making these kernels noteworthy is that they contain the necessary MCE
  fix for booting the new AMD Ryzen Threadripper 3900 series processors.
  With Linux 5.5 mainline or these back-ported kernels, Linux should be
  booting now without issue.

  These stable kernel updates also add Intel Comet Lake PCH-V and Elkhart Lake 
SoC support to the intel_th driver. But the rest of the changes are an 
assortment of mostly mundane fixes, unless you happened to be affected by one 
of the particular bugs addressed."
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  ryan   2274 F pulseaudio
   /dev/snd/controlC0:  ryan   2274 F pulseaudio
   /dev/snd/controlC1:  ryan   2274 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-02 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200101)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rsu7l4@/vmlinuz-5.4.0-9-generic 
root=ZFS=rpool/ROOT/ubuntu_rsu7l4 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-9-generic N/A
   linux-backports-modules-5.4.0-9-generic  N/A
   linux-firmware   1.184
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-9-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: 04/03/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99X EVO R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr2501:bd04/03/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: SKU
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858182/+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 1858182] ProcCpuinfoMinimal.txt

[Ryan Bach]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1858182/+attachment/5317501/+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/1858182

Title:
  Add support for Rizon 3900 Series Processors by updating to a newer
  kernel version

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  According to:
  https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.4.7
  -Stable-Released

  "Greg Kroah-Hartman took time out of his New Year's Eve festivities to
  release Linux 5.4.7, 4.19.92, and 4.14.161 as the newest supported
  stable releases of the Linux kernel.

  Making these kernels noteworthy is that they contain the necessary MCE
  fix for booting the new AMD Ryzen Threadripper 3900 series processors.
  With Linux 5.5 mainline or these back-ported kernels, Linux should be
  booting now without issue.

  These stable kernel updates also add Intel Comet Lake PCH-V and Elkhart Lake 
SoC support to the intel_th driver. But the rest of the changes are an 
assortment of mostly mundane fixes, unless you happened to be affected by one 
of the particular bugs addressed."
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  ryan   2274 F pulseaudio
   /dev/snd/controlC0:  ryan   2274 F pulseaudio
   /dev/snd/controlC1:  ryan   2274 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-02 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200101)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rsu7l4@/vmlinuz-5.4.0-9-generic 
root=ZFS=rpool/ROOT/ubuntu_rsu7l4 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-9-generic N/A
   linux-backports-modules-5.4.0-9-generic  N/A
   linux-firmware   1.184
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-9-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: 04/03/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99X EVO R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr2501:bd04/03/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: SKU
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858182/+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 1858182] ProcModules.txt

[Ryan Bach]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1858182/+attachment/5317503/+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/1858182

Title:
  Add support for Rizon 3900 Series Processors by updating to a newer
  kernel version

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  According to:
  https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.4.7
  -Stable-Released

  "Greg Kroah-Hartman took time out of his New Year's Eve festivities to
  release Linux 5.4.7, 4.19.92, and 4.14.161 as the newest supported
  stable releases of the Linux kernel.

  Making these kernels noteworthy is that they contain the necessary MCE
  fix for booting the new AMD Ryzen Threadripper 3900 series processors.
  With Linux 5.5 mainline or these back-ported kernels, Linux should be
  booting now without issue.

  These stable kernel updates also add Intel Comet Lake PCH-V and Elkhart Lake 
SoC support to the intel_th driver. But the rest of the changes are an 
assortment of mostly mundane fixes, unless you happened to be affected by one 
of the particular bugs addressed."
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  ryan   2274 F pulseaudio
   /dev/snd/controlC0:  ryan   2274 F pulseaudio
   /dev/snd/controlC1:  ryan   2274 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-02 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200101)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rsu7l4@/vmlinuz-5.4.0-9-generic 
root=ZFS=rpool/ROOT/ubuntu_rsu7l4 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-9-generic N/A
   linux-backports-modules-5.4.0-9-generic  N/A
   linux-firmware   1.184
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-9-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: 04/03/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99X EVO R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr2501:bd04/03/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: SKU
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858182/+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 1858182] ProcCpuinfo.txt

[Ryan Bach]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1858182/+attachment/5317500/+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/1858182

Title:
  Add support for Rizon 3900 Series Processors by updating to a newer
  kernel version

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  According to:
  https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.4.7
  -Stable-Released

  "Greg Kroah-Hartman took time out of his New Year's Eve festivities to
  release Linux 5.4.7, 4.19.92, and 4.14.161 as the newest supported
  stable releases of the Linux kernel.

  Making these kernels noteworthy is that they contain the necessary MCE
  fix for booting the new AMD Ryzen Threadripper 3900 series processors.
  With Linux 5.5 mainline or these back-ported kernels, Linux should be
  booting now without issue.

  These stable kernel updates also add Intel Comet Lake PCH-V and Elkhart Lake 
SoC support to the intel_th driver. But the rest of the changes are an 
assortment of mostly mundane fixes, unless you happened to be affected by one 
of the particular bugs addressed."
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  ryan   2274 F pulseaudio
   /dev/snd/controlC0:  ryan   2274 F pulseaudio
   /dev/snd/controlC1:  ryan   2274 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-02 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200101)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rsu7l4@/vmlinuz-5.4.0-9-generic 
root=ZFS=rpool/ROOT/ubuntu_rsu7l4 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-9-generic N/A
   linux-backports-modules-5.4.0-9-generic  N/A
   linux-firmware   1.184
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-9-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: 04/03/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99X EVO R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr2501:bd04/03/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: SKU
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858182/+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 1858182] CurrentDmesg.txt

[Ryan Bach]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1858182/+attachment/5317495/+files/CurrentDmesg.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1858182

Title:
  Add support for Rizon 3900 Series Processors by updating to a newer
  kernel version

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  According to:
  https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.4.7
  -Stable-Released

  "Greg Kroah-Hartman took time out of his New Year's Eve festivities to
  release Linux 5.4.7, 4.19.92, and 4.14.161 as the newest supported
  stable releases of the Linux kernel.

  Making these kernels noteworthy is that they contain the necessary MCE
  fix for booting the new AMD Ryzen Threadripper 3900 series processors.
  With Linux 5.5 mainline or these back-ported kernels, Linux should be
  booting now without issue.

  These stable kernel updates also add Intel Comet Lake PCH-V and Elkhart Lake 
SoC support to the intel_th driver. But the rest of the changes are an 
assortment of mostly mundane fixes, unless you happened to be affected by one 
of the particular bugs addressed."
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  ryan   2274 F pulseaudio
   /dev/snd/controlC0:  ryan   2274 F pulseaudio
   /dev/snd/controlC1:  ryan   2274 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-02 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200101)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rsu7l4@/vmlinuz-5.4.0-9-generic 
root=ZFS=rpool/ROOT/ubuntu_rsu7l4 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-9-generic N/A
   linux-backports-modules-5.4.0-9-generic  N/A
   linux-firmware   1.184
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-9-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: 04/03/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99X EVO R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr2501:bd04/03/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: SKU
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858182/+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 1858182] Lsusb-t.txt

[Ryan Bach]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1858182/+attachment/5317498/+files/Lsusb-t.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/1858182

Title:
  Add support for Rizon 3900 Series Processors by updating to a newer
  kernel version

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  According to:
  https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.4.7
  -Stable-Released

  "Greg Kroah-Hartman took time out of his New Year's Eve festivities to
  release Linux 5.4.7, 4.19.92, and 4.14.161 as the newest supported
  stable releases of the Linux kernel.

  Making these kernels noteworthy is that they contain the necessary MCE
  fix for booting the new AMD Ryzen Threadripper 3900 series processors.
  With Linux 5.5 mainline or these back-ported kernels, Linux should be
  booting now without issue.

  These stable kernel updates also add Intel Comet Lake PCH-V and Elkhart Lake 
SoC support to the intel_th driver. But the rest of the changes are an 
assortment of mostly mundane fixes, unless you happened to be affected by one 
of the particular bugs addressed."
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  ryan   2274 F pulseaudio
   /dev/snd/controlC0:  ryan   2274 F pulseaudio
   /dev/snd/controlC1:  ryan   2274 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-02 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200101)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rsu7l4@/vmlinuz-5.4.0-9-generic 
root=ZFS=rpool/ROOT/ubuntu_rsu7l4 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-9-generic N/A
   linux-backports-modules-5.4.0-9-generic  N/A
   linux-firmware   1.184
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-9-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: 04/03/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99X EVO R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr2501:bd04/03/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: SKU
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858182/+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 1858182] Lsusb.txt

[Ryan Bach]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1858182/+attachment/5317497/+files/Lsusb.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/1858182

Title:
  Add support for Rizon 3900 Series Processors by updating to a newer
  kernel version

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  According to:
  https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.4.7
  -Stable-Released

  "Greg Kroah-Hartman took time out of his New Year's Eve festivities to
  release Linux 5.4.7, 4.19.92, and 4.14.161 as the newest supported
  stable releases of the Linux kernel.

  Making these kernels noteworthy is that they contain the necessary MCE
  fix for booting the new AMD Ryzen Threadripper 3900 series processors.
  With Linux 5.5 mainline or these back-ported kernels, Linux should be
  booting now without issue.

  These stable kernel updates also add Intel Comet Lake PCH-V and Elkhart Lake 
SoC support to the intel_th driver. But the rest of the changes are an 
assortment of mostly mundane fixes, unless you happened to be affected by one 
of the particular bugs addressed."
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  ryan   2274 F pulseaudio
   /dev/snd/controlC0:  ryan   2274 F pulseaudio
   /dev/snd/controlC1:  ryan   2274 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-02 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200101)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rsu7l4@/vmlinuz-5.4.0-9-generic 
root=ZFS=rpool/ROOT/ubuntu_rsu7l4 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-9-generic N/A
   linux-backports-modules-5.4.0-9-generic  N/A
   linux-firmware   1.184
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-9-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: 04/03/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99X EVO R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr2501:bd04/03/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: SKU
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858182/+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 1858182] Lsusb-v.txt

[Ryan Bach]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1858182/+attachment/5317499/+files/Lsusb-v.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/1858182

Title:
  Add support for Rizon 3900 Series Processors by updating to a newer
  kernel version

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  According to:
  https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.4.7
  -Stable-Released

  "Greg Kroah-Hartman took time out of his New Year's Eve festivities to
  release Linux 5.4.7, 4.19.92, and 4.14.161 as the newest supported
  stable releases of the Linux kernel.

  Making these kernels noteworthy is that they contain the necessary MCE
  fix for booting the new AMD Ryzen Threadripper 3900 series processors.
  With Linux 5.5 mainline or these back-ported kernels, Linux should be
  booting now without issue.

  These stable kernel updates also add Intel Comet Lake PCH-V and Elkhart Lake 
SoC support to the intel_th driver. But the rest of the changes are an 
assortment of mostly mundane fixes, unless you happened to be affected by one 
of the particular bugs addressed."
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  ryan   2274 F pulseaudio
   /dev/snd/controlC0:  ryan   2274 F pulseaudio
   /dev/snd/controlC1:  ryan   2274 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-02 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200101)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rsu7l4@/vmlinuz-5.4.0-9-generic 
root=ZFS=rpool/ROOT/ubuntu_rsu7l4 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-9-generic N/A
   linux-backports-modules-5.4.0-9-generic  N/A
   linux-firmware   1.184
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-9-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: 04/03/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99X EVO R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr2501:bd04/03/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: SKU
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858182/+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 1858182] ProcInterrupts.txt

[Ryan Bach]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1858182/+attachment/5317502/+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/1858182

Title:
  Add support for Rizon 3900 Series Processors by updating to a newer
  kernel version

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  According to:
  https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.4.7
  -Stable-Released

  "Greg Kroah-Hartman took time out of his New Year's Eve festivities to
  release Linux 5.4.7, 4.19.92, and 4.14.161 as the newest supported
  stable releases of the Linux kernel.

  Making these kernels noteworthy is that they contain the necessary MCE
  fix for booting the new AMD Ryzen Threadripper 3900 series processors.
  With Linux 5.5 mainline or these back-ported kernels, Linux should be
  booting now without issue.

  These stable kernel updates also add Intel Comet Lake PCH-V and Elkhart Lake 
SoC support to the intel_th driver. But the rest of the changes are an 
assortment of mostly mundane fixes, unless you happened to be affected by one 
of the particular bugs addressed."
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  ryan   2274 F pulseaudio
   /dev/snd/controlC0:  ryan   2274 F pulseaudio
   /dev/snd/controlC1:  ryan   2274 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-02 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200101)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rsu7l4@/vmlinuz-5.4.0-9-generic 
root=ZFS=rpool/ROOT/ubuntu_rsu7l4 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-9-generic N/A
   linux-backports-modules-5.4.0-9-generic  N/A
   linux-firmware   1.184
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-9-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: 04/03/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99X EVO R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr2501:bd04/03/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: SKU
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858182/+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 1828596] Re: kdump fails when crash is triggered after DLPAR cpu add operation

[Guilherme G. Piccoli]

** Patch added: "eoan_V3.debdiff"
   
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828596/+attachment/5317481/+files/eoan_V3.debdiff

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1828596

Title:
  kdump fails when crash is triggered after DLPAR cpu add operation

Status in The Ubuntu-power-systems project:
  In Progress
Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Xenial:
  In Progress
Status in makedumpfile source package in Bionic:
  In Progress
Status in makedumpfile source package in Cosmic:
  Won't Fix
Status in makedumpfile source package in Disco:
  In Progress
Status in makedumpfile source package in Eoan:
  In Progress
Status in makedumpfile source package in Focal:
  In Progress

Bug description:
  [Impact]
  After a CPU add/hotplug operation on Power systems, kdump will fail after a 
crash. The kdump kernel needs to be reloaded after a CPU add/hotplug.

  [Test case]
  Do CPU add/hotplug, trigger a crash, and check for a successful kdump.

  [Regression potential]
  Multiple reloads caused by multiple sequential CPU adds may cause spurious 
log results, and systemd may fail to properly reload the kdump kernel. This has 
been handled by resetting the failure counter when doing such reloads.

  == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 ==
  ---Problem Description---
  kdump fails when crash is triggered after CPU add operation.

  Machine Type = na

  ---System Hang---
   Crashed in early boot process of kdump kernel after crash

  Had to issue system reset from HMC to reclaim

  ---Steps to Reproduce---
   1. Configure kdump.
  2. Add cpu from HMC.
  3. Trigger crash.
  4. Machine hangs after crash as below:

  ---
  [169250.213166] IPI complete
  [169250.234331] kexec: Starting switchover sequence.
  I'm in purgatory
   --- STRUCK HERE ---

  ---uname output---
  na

  ---Debugger---
  A debugger is not configured

  == Comment: #1 - Hari Krishna Bathini  - 2019-05-10 05:56:46 ==
  The problem is, kexec udev rule to restart kdump-tools service - when a core 
is added,
  is not being triggered. The old DT created by kexec (before the core is added)
  is being used by KDump Kernel. So, when system crashes on a thread from
  the added core(s), KDump kernel is failing to get the 'boot_cpuid' and
  eventually failing to boot..

  == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 ==
  The udev rule when CPU is added is not triggered because ppc64 does not
  eject add/remove event when a CPU is hot added/removed. It only ejects
  online/offline event to user space when CPU is hot added/removed.

  So, the below udev rules are never triggered when needed:

  SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"
  SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"

  Also, with how CPU hot add & remove are handled in ppc64, a udev trigger
  to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU
  hot add case by updating the udev rule and drop the udev rule meant for CPU
  hot remove in the kdump udev rules file:

  SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try-
  restart kdump-tools.service"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828596/+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 1828596] Re: kdump fails when crash is triggered after DLPAR cpu add operation

[Guilherme G. Piccoli]

** Patch added: "focal_new.debdiff"
   
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828596/+attachment/5317480/+files/focal_new.debdiff

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1828596

Title:
  kdump fails when crash is triggered after DLPAR cpu add operation

Status in The Ubuntu-power-systems project:
  In Progress
Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Xenial:
  In Progress
Status in makedumpfile source package in Bionic:
  In Progress
Status in makedumpfile source package in Cosmic:
  Won't Fix
Status in makedumpfile source package in Disco:
  In Progress
Status in makedumpfile source package in Eoan:
  In Progress
Status in makedumpfile source package in Focal:
  In Progress

Bug description:
  [Impact]
  After a CPU add/hotplug operation on Power systems, kdump will fail after a 
crash. The kdump kernel needs to be reloaded after a CPU add/hotplug.

  [Test case]
  Do CPU add/hotplug, trigger a crash, and check for a successful kdump.

  [Regression potential]
  Multiple reloads caused by multiple sequential CPU adds may cause spurious 
log results, and systemd may fail to properly reload the kdump kernel. This has 
been handled by resetting the failure counter when doing such reloads.

  == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 ==
  ---Problem Description---
  kdump fails when crash is triggered after CPU add operation.

  Machine Type = na

  ---System Hang---
   Crashed in early boot process of kdump kernel after crash

  Had to issue system reset from HMC to reclaim

  ---Steps to Reproduce---
   1. Configure kdump.
  2. Add cpu from HMC.
  3. Trigger crash.
  4. Machine hangs after crash as below:

  ---
  [169250.213166] IPI complete
  [169250.234331] kexec: Starting switchover sequence.
  I'm in purgatory
   --- STRUCK HERE ---

  ---uname output---
  na

  ---Debugger---
  A debugger is not configured

  == Comment: #1 - Hari Krishna Bathini  - 2019-05-10 05:56:46 ==
  The problem is, kexec udev rule to restart kdump-tools service - when a core 
is added,
  is not being triggered. The old DT created by kexec (before the core is added)
  is being used by KDump Kernel. So, when system crashes on a thread from
  the added core(s), KDump kernel is failing to get the 'boot_cpuid' and
  eventually failing to boot..

  == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 ==
  The udev rule when CPU is added is not triggered because ppc64 does not
  eject add/remove event when a CPU is hot added/removed. It only ejects
  online/offline event to user space when CPU is hot added/removed.

  So, the below udev rules are never triggered when needed:

  SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"
  SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"

  Also, with how CPU hot add & remove are handled in ppc64, a udev trigger
  to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU
  hot add case by updating the udev rule and drop the udev rule meant for CPU
  hot remove in the kdump udev rules file:

  SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try-
  restart kdump-tools.service"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828596/+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 1828596] Re: kdump fails when crash is triggered after DLPAR cpu add operation

[Guilherme G. Piccoli]

A recent issue on makedumpfile was reported and investigated on LP#1857616. Due 
to the relevance of that, it makes sense to respin the debdiffs. So, I've 
reworked debdiffs for Bionic and Eoan, that should replace the ones above. 
Disco is not affected.
Since those packages are not in -proposed, the respin is on top of the same 
version, to replace the old upload.

Now, Focal is present in -proposed for some time, so the respin is on top of 
-proposed version (which I expect to be released to -updates soon), with 
version increment.
Thanks,


Guilherme

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1828596

Title:
  kdump fails when crash is triggered after DLPAR cpu add operation

Status in The Ubuntu-power-systems project:
  In Progress
Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Xenial:
  In Progress
Status in makedumpfile source package in Bionic:
  In Progress
Status in makedumpfile source package in Cosmic:
  Won't Fix
Status in makedumpfile source package in Disco:
  In Progress
Status in makedumpfile source package in Eoan:
  In Progress
Status in makedumpfile source package in Focal:
  In Progress

Bug description:
  [Impact]
  After a CPU add/hotplug operation on Power systems, kdump will fail after a 
crash. The kdump kernel needs to be reloaded after a CPU add/hotplug.

  [Test case]
  Do CPU add/hotplug, trigger a crash, and check for a successful kdump.

  [Regression potential]
  Multiple reloads caused by multiple sequential CPU adds may cause spurious 
log results, and systemd may fail to properly reload the kdump kernel. This has 
been handled by resetting the failure counter when doing such reloads.

  == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 ==
  ---Problem Description---
  kdump fails when crash is triggered after CPU add operation.

  Machine Type = na

  ---System Hang---
   Crashed in early boot process of kdump kernel after crash

  Had to issue system reset from HMC to reclaim

  ---Steps to Reproduce---
   1. Configure kdump.
  2. Add cpu from HMC.
  3. Trigger crash.
  4. Machine hangs after crash as below:

  ---
  [169250.213166] IPI complete
  [169250.234331] kexec: Starting switchover sequence.
  I'm in purgatory
   --- STRUCK HERE ---

  ---uname output---
  na

  ---Debugger---
  A debugger is not configured

  == Comment: #1 - Hari Krishna Bathini  - 2019-05-10 05:56:46 ==
  The problem is, kexec udev rule to restart kdump-tools service - when a core 
is added,
  is not being triggered. The old DT created by kexec (before the core is added)
  is being used by KDump Kernel. So, when system crashes on a thread from
  the added core(s), KDump kernel is failing to get the 'boot_cpuid' and
  eventually failing to boot..

  == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 ==
  The udev rule when CPU is added is not triggered because ppc64 does not
  eject add/remove event when a CPU is hot added/removed. It only ejects
  online/offline event to user space when CPU is hot added/removed.

  So, the below udev rules are never triggered when needed:

  SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"
  SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"

  Also, with how CPU hot add & remove are handled in ppc64, a udev trigger
  to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU
  hot add case by updating the udev rule and drop the udev rule meant for CPU
  hot remove in the kdump udev rules file:

  SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try-
  restart kdump-tools.service"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828596/+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 1828596] Re: kdump fails when crash is triggered after DLPAR cpu add operation

[Guilherme G. Piccoli]

I'm re-attaching the untouched disco debdiff, just for
organization/completeness.

** Patch added: "disco_reattachment.debdiff"
   
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828596/+attachment/5317482/+files/disco_reattachment.debdiff

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1828596

Title:
  kdump fails when crash is triggered after DLPAR cpu add operation

Status in The Ubuntu-power-systems project:
  In Progress
Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Xenial:
  In Progress
Status in makedumpfile source package in Bionic:
  In Progress
Status in makedumpfile source package in Cosmic:
  Won't Fix
Status in makedumpfile source package in Disco:
  In Progress
Status in makedumpfile source package in Eoan:
  In Progress
Status in makedumpfile source package in Focal:
  In Progress

Bug description:
  [Impact]
  After a CPU add/hotplug operation on Power systems, kdump will fail after a 
crash. The kdump kernel needs to be reloaded after a CPU add/hotplug.

  [Test case]
  Do CPU add/hotplug, trigger a crash, and check for a successful kdump.

  [Regression potential]
  Multiple reloads caused by multiple sequential CPU adds may cause spurious 
log results, and systemd may fail to properly reload the kdump kernel. This has 
been handled by resetting the failure counter when doing such reloads.

  == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 ==
  ---Problem Description---
  kdump fails when crash is triggered after CPU add operation.

  Machine Type = na

  ---System Hang---
   Crashed in early boot process of kdump kernel after crash

  Had to issue system reset from HMC to reclaim

  ---Steps to Reproduce---
   1. Configure kdump.
  2. Add cpu from HMC.
  3. Trigger crash.
  4. Machine hangs after crash as below:

  ---
  [169250.213166] IPI complete
  [169250.234331] kexec: Starting switchover sequence.
  I'm in purgatory
   --- STRUCK HERE ---

  ---uname output---
  na

  ---Debugger---
  A debugger is not configured

  == Comment: #1 - Hari Krishna Bathini  - 2019-05-10 05:56:46 ==
  The problem is, kexec udev rule to restart kdump-tools service - when a core 
is added,
  is not being triggered. The old DT created by kexec (before the core is added)
  is being used by KDump Kernel. So, when system crashes on a thread from
  the added core(s), KDump kernel is failing to get the 'boot_cpuid' and
  eventually failing to boot..

  == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 ==
  The udev rule when CPU is added is not triggered because ppc64 does not
  eject add/remove event when a CPU is hot added/removed. It only ejects
  online/offline event to user space when CPU is hot added/removed.

  So, the below udev rules are never triggered when needed:

  SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"
  SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"

  Also, with how CPU hot add & remove are handled in ppc64, a udev trigger
  to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU
  hot add case by updating the udev rule and drop the udev rule meant for CPU
  hot remove in the kdump udev rules file:

  SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try-
  restart kdump-tools.service"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828596/+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 1828596] Re: kdump fails when crash is triggered after DLPAR cpu add operation

[Guilherme G. Piccoli]

I'm re-attaching the untouched Xenial debdiff, just for
organization/completeness.

** Patch added: "xenial_reattachment.debdiff"
   
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828596/+attachment/5317484/+files/xenial_reattachment.debdiff

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1828596

Title:
  kdump fails when crash is triggered after DLPAR cpu add operation

Status in The Ubuntu-power-systems project:
  In Progress
Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Xenial:
  In Progress
Status in makedumpfile source package in Bionic:
  In Progress
Status in makedumpfile source package in Cosmic:
  Won't Fix
Status in makedumpfile source package in Disco:
  In Progress
Status in makedumpfile source package in Eoan:
  In Progress
Status in makedumpfile source package in Focal:
  In Progress

Bug description:
  [Impact]
  After a CPU add/hotplug operation on Power systems, kdump will fail after a 
crash. The kdump kernel needs to be reloaded after a CPU add/hotplug.

  [Test case]
  Do CPU add/hotplug, trigger a crash, and check for a successful kdump.

  [Regression potential]
  Multiple reloads caused by multiple sequential CPU adds may cause spurious 
log results, and systemd may fail to properly reload the kdump kernel. This has 
been handled by resetting the failure counter when doing such reloads.

  == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 ==
  ---Problem Description---
  kdump fails when crash is triggered after CPU add operation.

  Machine Type = na

  ---System Hang---
   Crashed in early boot process of kdump kernel after crash

  Had to issue system reset from HMC to reclaim

  ---Steps to Reproduce---
   1. Configure kdump.
  2. Add cpu from HMC.
  3. Trigger crash.
  4. Machine hangs after crash as below:

  ---
  [169250.213166] IPI complete
  [169250.234331] kexec: Starting switchover sequence.
  I'm in purgatory
   --- STRUCK HERE ---

  ---uname output---
  na

  ---Debugger---
  A debugger is not configured

  == Comment: #1 - Hari Krishna Bathini  - 2019-05-10 05:56:46 ==
  The problem is, kexec udev rule to restart kdump-tools service - when a core 
is added,
  is not being triggered. The old DT created by kexec (before the core is added)
  is being used by KDump Kernel. So, when system crashes on a thread from
  the added core(s), KDump kernel is failing to get the 'boot_cpuid' and
  eventually failing to boot..

  == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 ==
  The udev rule when CPU is added is not triggered because ppc64 does not
  eject add/remove event when a CPU is hot added/removed. It only ejects
  online/offline event to user space when CPU is hot added/removed.

  So, the below udev rules are never triggered when needed:

  SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"
  SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"

  Also, with how CPU hot add & remove are handled in ppc64, a udev trigger
  to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU
  hot add case by updating the udev rule and drop the udev rule meant for CPU
  hot remove in the kdump udev rules file:

  SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try-
  restart kdump-tools.service"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828596/+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 1828596] Re: kdump fails when crash is triggered after DLPAR cpu add operation

[Guilherme G. Piccoli]

** Patch added: "bionic_V3.debdiff"
   
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828596/+attachment/5317483/+files/bionic_V3.debdiff

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1828596

Title:
  kdump fails when crash is triggered after DLPAR cpu add operation

Status in The Ubuntu-power-systems project:
  In Progress
Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Xenial:
  In Progress
Status in makedumpfile source package in Bionic:
  In Progress
Status in makedumpfile source package in Cosmic:
  Won't Fix
Status in makedumpfile source package in Disco:
  In Progress
Status in makedumpfile source package in Eoan:
  In Progress
Status in makedumpfile source package in Focal:
  In Progress

Bug description:
  [Impact]
  After a CPU add/hotplug operation on Power systems, kdump will fail after a 
crash. The kdump kernel needs to be reloaded after a CPU add/hotplug.

  [Test case]
  Do CPU add/hotplug, trigger a crash, and check for a successful kdump.

  [Regression potential]
  Multiple reloads caused by multiple sequential CPU adds may cause spurious 
log results, and systemd may fail to properly reload the kdump kernel. This has 
been handled by resetting the failure counter when doing such reloads.

  == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 ==
  ---Problem Description---
  kdump fails when crash is triggered after CPU add operation.

  Machine Type = na

  ---System Hang---
   Crashed in early boot process of kdump kernel after crash

  Had to issue system reset from HMC to reclaim

  ---Steps to Reproduce---
   1. Configure kdump.
  2. Add cpu from HMC.
  3. Trigger crash.
  4. Machine hangs after crash as below:

  ---
  [169250.213166] IPI complete
  [169250.234331] kexec: Starting switchover sequence.
  I'm in purgatory
   --- STRUCK HERE ---

  ---uname output---
  na

  ---Debugger---
  A debugger is not configured

  == Comment: #1 - Hari Krishna Bathini  - 2019-05-10 05:56:46 ==
  The problem is, kexec udev rule to restart kdump-tools service - when a core 
is added,
  is not being triggered. The old DT created by kexec (before the core is added)
  is being used by KDump Kernel. So, when system crashes on a thread from
  the added core(s), KDump kernel is failing to get the 'boot_cpuid' and
  eventually failing to boot..

  == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 ==
  The udev rule when CPU is added is not triggered because ppc64 does not
  eject add/remove event when a CPU is hot added/removed. It only ejects
  online/offline event to user space when CPU is hot added/removed.

  So, the below udev rules are never triggered when needed:

  SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"
  SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"

  Also, with how CPU hot add & remove are handled in ppc64, a udev trigger
  to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU
  hot add case by updating the udev rule and drop the udev rule meant for CPU
  hot remove in the kdump udev rules file:

  SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try-
  restart kdump-tools.service"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828596/+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 1858182] Re: Add support for Rizon 3900 Series Processors by updating to a newer kernel version

[Ryan Bach]

apport-collect 1858182 doesn't finish it stops at finding linux for some
reason.

-- 
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/1858182

Title:
  Add support for Rizon 3900 Series Processors by updating to a newer
  kernel version

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  According to:
  https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.4.7
  -Stable-Released

  "Greg Kroah-Hartman took time out of his New Year's Eve festivities to
  release Linux 5.4.7, 4.19.92, and 4.14.161 as the newest supported
  stable releases of the Linux kernel.

  Making these kernels noteworthy is that they contain the necessary MCE
  fix for booting the new AMD Ryzen Threadripper 3900 series processors.
  With Linux 5.5 mainline or these back-ported kernels, Linux should be
  booting now without issue.

  These stable kernel updates also add Intel Comet Lake PCH-V and
  Elkhart Lake SoC support to the intel_th driver. But the rest of the
  changes are an assortment of mostly mundane fixes, unless you happened
  to be affected by one of the particular bugs addressed."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858182/+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 1857616] Re: Cannot collect dump due to "Can't get a valid pmd_pte" error

[Guilherme G. Piccoli]

We still need to discuss the feasibility/need of inclusion of each fix
in Xenial.

** Description changed:

- Due to an issue in the kaslr address resolution in makedumpfile, we may
- get the following error when collecting a dump:
+ [Impact]
+ 
+ * Currently makedumpfile has 2 flaws due to: (a) out of synchronization
+ with kernel code and, (b) kaslr handling. The first is related to a
+ definition of a memory flag bit, whereas the second is about kaslr
+ offset calculation - both cause similar failures when collecting the
+ vmcore in kdump environment:
  
  Excluding unnecessary pages : [ 46.3 %] / __vtop4_x86_64[ 39.341233]: Can't 
get a valid pmd_pte.
  readmem: Can't convert a virtual address(e05cb400) to physical 
address.
  readmem: type_addr: 0, addr:e05cb400, size:32768
  __exclude_unnecessary_pages: Can't read the buffer of struct page.
  create_2nd_bitmap: Can't exclude unnecessary pages.
  
- This is believed to be fixed by commit: 3222d4ad04c6 ("x86_64: fix
- get_kaslr_offset_x86_64() to return kaslr_offset correctly"). This LP
- keeps track of Test/SRU for this commit.
+ * The report is mainly related to the first issue, which started to
+ happen after the merge of kernel commit 326e1b8f83a4 ("mm/sparsemem:
+ introduce a SECTION_IS_EARLY flag"), introduced in kernel 5.3. After
+ this commit, a memory flag was changed and induced the error in dump
+ collection. The fix is available in makedumpfile, as commit 7bdb468c2c
+ ("Increase SECTION_MAP_LAST_BIT to 4"). This is hereby SRUed to Bionic
+ (due to HWE kernel 5.3), Eoan and Focal.
+ 
+ * The other issue is fixed in both Eoan and Focal, on makedumpfile
+ 1.6.6-based version. It is related with the kaslr offset: if the offset
+ is small enough, we may return 0 wrongly in get_kaslr_offset_x86_64(),
+ causing the vmcore collection to fail or even worse, to erase unintended
+ data from the memory dump. This is fixed by makedumpfile commit
+ 3222d4ad04 ("x86_64: fix get_kaslr_offset_x86_64() to return
+ kaslr_offset correctly"), which isn't present in versions before 1.6.6.
+ We hereby SRU this fix for Bionic.
+ 
+ * Notice this modification is being worked concurrently with other
+ kdump-tools' changes in LP #1828596.
+ 
+ [Test Case]
+ 
+ 1) Deploy an Eoan VM e.g. with uvt-kvm;
+ 2) Set-up console output in the guest;
+ 3) Install the kdump-tools package;
+ 4) Configure and collect a dump (with sysrq to panic the system) - the error 
aforementioned is observed given Eoan kernel is 5.3-based.
+ 
+ [Regression Potential]
+ 
+ * The modifications hereby proposed are minimal and scope-constrained to
+ makedumpfile in x86_64; both are merged in makedumpfile upstream, one of
+ them being already released in E/F. An unlikely  regression would
+ potentially fails vmcore collection in kdump environment.

** Changed in: makedumpfile (Ubuntu Xenial)
   Status: Invalid => Opinion

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1857616

Title:
  Cannot collect dump due to "Can't get a valid pmd_pte" error

Status in makedumpfile package in Ubuntu:
  Confirmed
Status in makedumpfile source package in Xenial:
  Opinion
Status in makedumpfile source package in Bionic:
  Confirmed
Status in makedumpfile source package in Disco:
  Invalid
Status in makedumpfile source package in Eoan:
  Confirmed
Status in makedumpfile source package in Focal:
  Confirmed

Bug description:
  [Impact]

  * Currently makedumpfile has 2 flaws due to: (a) out of
  synchronization with kernel code and, (b) kaslr handling. The first is
  related to a definition of a memory flag bit, whereas the second is
  about kaslr offset calculation - both cause similar failures when
  collecting the vmcore in kdump environment:

  Excluding unnecessary pages : [ 46.3 %] / __vtop4_x86_64[ 39.341233]: Can't 
get a valid pmd_pte.
  readmem: Can't convert a virtual address(e05cb400) to physical 
address.
  readmem: type_addr: 0, addr:e05cb400, size:32768
  __exclude_unnecessary_pages: Can't read the buffer of struct page.
  create_2nd_bitmap: Can't exclude unnecessary pages.

  * The report is mainly related to the first issue, which started to
  happen after the merge of kernel commit 326e1b8f83a4 ("mm/sparsemem:
  introduce a SECTION_IS_EARLY flag"), introduced in kernel 5.3. After
  this commit, a memory flag was changed and induced the error in dump
  collection. The fix is available in makedumpfile, as commit 7bdb468c2c
  ("Increase SECTION_MAP_LAST_BIT to 4"). This is hereby SRUed to Bionic
  (due to HWE kernel 5.3), Eoan and Focal.

  * The other issue is fixed in both Eoan and Focal, on makedumpfile
  1.6.6-based version. It is related with the kaslr offset: if the
  offset is small enough, we may return 0 wrongly in
  get_kaslr_offset_x86_64(), causing the vmcore collection to fail or
  even worse, to erase unintended data from the memory dump

[Kernel-packages] [Bug 1826549] Re: Mouse wheel scroll does not work after upgrade to Ubuntu 19.04 with Linux kernel 5.0 (but kernel 4.18 works)

[Vladimir Kondratyev]

The problem still existed in December 2019 (Ubuntu 19.04). But I can
confirm that Ubuntu 19.10 fixes this issue. Most probably fix will never
be ported to Ubuntu 19.04 kernel.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1826549

Title:
  Mouse wheel scroll does not work after upgrade to Ubuntu 19.04 with
  Linux kernel 5.0 (but kernel 4.18 works)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've just upgraded to Ubuntu 19.04 and found that scrolling with mouse
  wheel does not work any more. My mouse is Microsoft Wireless Optical
  Mouse 2000. The mouse is connected to USB port via wireless receiver
  (Microsoft Wireless Mouse Receiver v1.0).

  
  I've found that problem is related to new Linux kernel 5.0. When I boot with 
previous kernel 4.18 all works good.

  The problem is reproducible with xorg and with wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 15:23:34 2019
  DistUpgraded: 2019-04-26 14:07:47,232 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2017-09-12 (591 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 003: ID 05e3:0745 Genesys Logic, Inc. Logilink CR0012
   Bus 001 Device 002: ID 045e:00e1 Microsoft Corp. Wireless Laser Mouse 6000 
Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic 
root=UUID=249a1929-c0a6-4e3c-98dd-3a16b38e6c07 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-04-26 (0 days ago)
  dmi.bios.date: 07/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.20
  dmi.board.name: Z270 Pro4
  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.:bvrP2.20:bd07/20/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ270Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826549/+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 1856983] Re: bionic/linux-gcp: 5.0.0-1028.29~18.04.1 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   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/1856983

Title:
  bionic/linux-gcp: 5.0.0-1028.29~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm 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:
  Confirmed
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:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1856985
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Ready for Promote to Proposed
  phase-changed: Thursday, 19. December 2019 23:51 UTC
  reason:
promote-to-proposed: Stalled -- ready for review
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1856982
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856983/+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 1856370] Re: [nvidia] Black screen with message "GPU has fallen off the bus" after resuming from suspend

[Stuardo -StR- Rodríguez]

I can no longer replicate the issue.

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856370/+attachment/5317469/+files/dmesg.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu.
https://bugs.launchpad.net/bugs/1856370

Title:
  [nvidia] Black screen with message "GPU has fallen off the bus" after
  resuming from suspend

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  New

Bug description:
  Every time I suspend my laptop, after I resume it, a black screen
  shows with the error message

  - GPU has fallen off the bus

  It's a plain vanilla Ubunbtu 19.10 installation on an Dell XPS 15 7590
  with NVIDIA(R) GeForce(R) GTX 1650 4GB GDDR5

  Description:  Ubuntu 19.10
  Release:  19.10
  nvidia driver 435

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 13 16:31:58 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 5.3.0-18-generic, x86_64: installed
   nvidia, 435.21, 5.3.0-24-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0905]
 Subsystem: Dell Device [1028:0905]
  InstallationDate: Installed on 2019-12-13 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. XPS 15 7590
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=0b1a4be3-b095-45fc-ae1b-4b6fb7845eb2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.name: 0VYV0G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd09/25/2019:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 7590
  dmi.product.sku: 0905
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856370/+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 1845046] Re: Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low quality headset mode and fails to switch to A2DP when selected

[Magne H]

The following did the job for me. Remember to change the headset to AD2P
under SOUNDS in Ubuntu on your headset.

---

Ref. from source:

https://askubuntu.com/questions/1139404/sony-noise-cancelling-
headphones-wh-1000xm2-3-and-bluetooth-initial-autoconnec

---

The "ambient noise" you're hearing is a loopback from your computer's
mic coming out through your headphones.

This is apparently due to a bug with A2DP's implementation.

I fixed this in Ubuntu 19.04 by installing Blueman and pairing my
headphones as an Audio Sink rather than a headset:

Unpair your headphones, if they're currently paired.
sudo apt install blueman
Open Blueman, click on "search".
Select your headphones, right click, select "Setup"
Make sure they're paired as an Audio Sink rather than a Headset
Select your headphones as an audio output in your sound settings

If you have Spotify open throughout the process you have to restart it.

-- 
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/1845046

Title:
  Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low
  quality headset mode and fails to switch to A2DP when selected

Status in PulseAudio:
  Unknown
Status in bluez package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Whenever I turn on my headphones theyll connect to my computer but im
  able to hear the input audio from my microphone and low quality output
  audio. I have to disconnect the headphones in the bluetooth devices
  and reconnect for it to fix the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  litleck1398 F pulseaudio
   /dev/snd/controlC0:  litleck1398 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 23 17:07:59 2019
  InstallationDate: Installed on 2019-09-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: WH-1000XM3
  Symptom_Type: High background noise, or volume is too low
  Title: [WH-1000XM3, playback] Background noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2019
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.0.19
  dmi.board.name: 01NYPT
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified:
  dmi.product.family: Alienware
  dmi.product.name: Alienware Aurora R5
  dmi.product.sku: 0729
  dmi.product.version: 1.0.19
  dmi.sys.vendor: Alienware

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1845046/+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 1858231] Status changed to Confirmed

[Ubuntu Kernel Bot]

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/1858231

Title:
  QCA6174 Wifi adapter not functional

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The QCA6174 Wifi adapter is not functional in Ubuntu 19.10, both from
  the live cd and an install.  It is functional in a 18.04 install.

  At boot, the kernel log contains the following messages in 19.10:

  [   15.665517] ath10k_pci :6f:00.0: DMAR: 32bit DMA uses non-identity 
mapping
  [   15.665524] ath10k_pci :6f:00.0: failed to alloc CE src ring 0: -12
  [   15.665527] ath10k_pci :6f:00.0: failed to allocate copy engine pipe 
0: -12
  [   15.665528] ath10k_pci :6f:00.0: failed to allocate copy engine pipes: 
-12
  [   15.665530] ath10k_pci :6f:00.0: failed to setup resource: -12
  [   15.667627] ath10k_pci: probe of :6f:00.0 failed with error -12

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-24-generic 5.3.0-24.26
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ed 1932 F pulseaudio
   /dev/snd/controlC0:  ed 1932 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan  3 14:31:15 2020
  InstallationDate: Installed on 2020-01-03 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: Dell Inc. Precision 7540
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-24-generic 
root=UUID=f393b98c-0896-48e8-a242-e6d8d5b262bf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 0499T7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd07/24/2019:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0499T7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 7540
  dmi.product.sku: 0926
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858231/+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 1858231] Re: QCA6174 Wifi adapter not functional

[Edward Schwartz]

** Attachment added: "lspci"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858231/+attachment/5317468/+files/lspci-vnvn.log

-- 
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/1858231

Title:
  QCA6174 Wifi adapter not functional

Status in linux package in Ubuntu:
  New

Bug description:
  The QCA6174 Wifi adapter is not functional in Ubuntu 19.10, both from
  the live cd and an install.  It is functional in a 18.04 install.

  At boot, the kernel log contains the following messages in 19.10:

  [   15.665517] ath10k_pci :6f:00.0: DMAR: 32bit DMA uses non-identity 
mapping
  [   15.665524] ath10k_pci :6f:00.0: failed to alloc CE src ring 0: -12
  [   15.665527] ath10k_pci :6f:00.0: failed to allocate copy engine pipe 
0: -12
  [   15.665528] ath10k_pci :6f:00.0: failed to allocate copy engine pipes: 
-12
  [   15.665530] ath10k_pci :6f:00.0: failed to setup resource: -12
  [   15.667627] ath10k_pci: probe of :6f:00.0 failed with error -12

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-24-generic 5.3.0-24.26
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ed 1932 F pulseaudio
   /dev/snd/controlC0:  ed 1932 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan  3 14:31:15 2020
  InstallationDate: Installed on 2020-01-03 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: Dell Inc. Precision 7540
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-24-generic 
root=UUID=f393b98c-0896-48e8-a242-e6d8d5b262bf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 0499T7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd07/24/2019:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0499T7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 7540
  dmi.product.sku: 0926
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858231/+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 1858231] [NEW] QCA6174 Wifi adapter not functional

[Edward Schwartz]

Public bug reported:

The QCA6174 Wifi adapter is not functional in Ubuntu 19.10, both from
the live cd and an install.  It is functional in a 18.04 install.

At boot, the kernel log contains the following messages in 19.10:

[   15.665517] ath10k_pci :6f:00.0: DMAR: 32bit DMA uses non-identity 
mapping
[   15.665524] ath10k_pci :6f:00.0: failed to alloc CE src ring 0: -12
[   15.665527] ath10k_pci :6f:00.0: failed to allocate copy engine pipe 0: 
-12
[   15.665528] ath10k_pci :6f:00.0: failed to allocate copy engine pipes: 
-12
[   15.665530] ath10k_pci :6f:00.0: failed to setup resource: -12
[   15.667627] ath10k_pci: probe of :6f:00.0 failed with error -12

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-24-generic 5.3.0-24.26
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  ed 1932 F pulseaudio
 /dev/snd/controlC0:  ed 1932 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan  3 14:31:15 2020
InstallationDate: Installed on 2020-01-03 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
IwConfig:
 lono wireless extensions.
 
 eno1  no wireless extensions.
MachineType: Dell Inc. Precision 7540
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-24-generic 
root=UUID=f393b98c-0896-48e8-a242-e6d8d5b262bf ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-24-generic N/A
 linux-backports-modules-5.3.0-24-generic  N/A
 linux-firmware1.183.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/24/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.3
dmi.board.name: 0499T7
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd07/24/2019:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0499T7:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 7540
dmi.product.sku: 0926
dmi.sys.vendor: Dell Inc.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan

** Attachment added: "kernel version"
   
https://bugs.launchpad.net/bugs/1858231/+attachment/5317453/+files/version.log

-- 
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/1858231

Title:
  QCA6174 Wifi adapter not functional

Status in linux package in Ubuntu:
  New

Bug description:
  The QCA6174 Wifi adapter is not functional in Ubuntu 19.10, both from
  the live cd and an install.  It is functional in a 18.04 install.

  At boot, the kernel log contains the following messages in 19.10:

  [   15.665517] ath10k_pci :6f:00.0: DMAR: 32bit DMA uses non-identity 
mapping
  [   15.665524] ath10k_pci :6f:00.0: failed to alloc CE src ring 0: -12
  [   15.665527] ath10k_pci :6f:00.0: failed to allocate copy engine pipe 
0: -12
  [   15.665528] ath10k_pci :6f:00.0: failed to allocate copy engine pipes: 
-12
  [   15.665530] ath10k_pci :6f:00.0: failed to setup resource: -12
  [   15.667627] ath10k_pci: probe of :6f:00.0 failed with error -12

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-24-generic 5.3.0-24.26
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ed 1932 F pulseaudio
   /dev/snd/controlC0:  ed 1932 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan  3 14:31:15 2020
  InstallationDate: Installed on 2020-01-03 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: Dell Inc. Precision 7540
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-24-generic 
root=UUID=f393b98c-0896-48e8-a242-e6d8d5b262bf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2019
  dmi.bios.vendor: Dell I

[Kernel-packages] [Bug 1856983] Re: bionic/linux-gcp: 5.0.0-1028.29~18.04.1 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

-- 
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/1856983

Title:
  bionic/linux-gcp: 5.0.0-1028.29~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm 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:
  Confirmed
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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1856985
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Ready for Promote to Proposed
  phase-changed: Thursday, 19. December 2019 23:51 UTC
  reason:
promote-to-proposed: Stalled -- ready for review
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1856982
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856983/+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 1686189] Re: External monitor connecting problem on Intel graphics card

[TF]

Same fault by using VGA instead of DP.

-- 
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/1686189

Title:
  External monitor connecting problem on Intel graphics card

Status in linux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am facing a problem with Intel Graphics driver. I have external
  monitor and in display settings the second monitor is detecting but
  it's not working, so could you email me a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.4.25-040425-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 25 21:45:16 2017
  DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
  InstallationDate: Installed on 2017-04-25 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 3537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic 
root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 03JPPR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 3537
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 25 21:37:24 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686189/+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 1858182] Missing required logs.

[Ubuntu Kernel Bot]

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 1858182

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/1858182

Title:
  Add support for Rizon 3900 Series Processors by updating to a newer
  kernel version

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  According to:
  https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.4.7
  -Stable-Released

  "Greg Kroah-Hartman took time out of his New Year's Eve festivities to
  release Linux 5.4.7, 4.19.92, and 4.14.161 as the newest supported
  stable releases of the Linux kernel.

  Making these kernels noteworthy is that they contain the necessary MCE
  fix for booting the new AMD Ryzen Threadripper 3900 series processors.
  With Linux 5.5 mainline or these back-ported kernels, Linux should be
  booting now without issue.

  These stable kernel updates also add Intel Comet Lake PCH-V and
  Elkhart Lake SoC support to the intel_th driver. But the rest of the
  changes are an assortment of mostly mundane fixes, unless you happened
  to be affected by one of the particular bugs addressed."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858182/+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 1856983] Re: bionic/linux-gcp: 5.0.0-1028.29~18.04.1 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Invalid

** Changed in: kernel-sru-workflow/security-signoff
   Status: Invalid => Confirmed

-- 
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/1856983

Title:
  bionic/linux-gcp: 5.0.0-1028.29~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm 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:
  Confirmed
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:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1856985
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Ready for Promote to Proposed
  phase-changed: Thursday, 19. December 2019 23:51 UTC
  reason:
promote-to-proposed: Stalled -- ready for review
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1856982
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856983/+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 1686189] Re: External monitor connecting problem on Intel graphics card

[TF]

I'm using a HP Pro X2 612 G1. It has VGA compatible controller: Intel
Corporation Device 0a1e (rev 0b) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Device 221b. The external Monitor
(connected to DisplayPort) is recognized, but it the grafics is
distorted and flickering. There is no hardware issue, because the same
configuration is working with windows 10.

Booting Linux version 5.3.0-26-generic (buildd@lgw01-amd64-039) (gcc
version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #28~18.04.1-Ubuntu SMP
Wed Dec 18 , Command line: BOOT_IMAGE=/vmlinuz-5.3.0-26-generic
root=UUID=480802c1-9e34-498b-bce0-044986a92dfc ro quiet splash
i915.edp_vswing=1 vt.handoff=1.

I tried booting without any i915 parameters, but it doesn't change the
behavior.

Any ideas what's going wrong ?

-- 
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/1686189

Title:
  External monitor connecting problem on Intel graphics card

Status in linux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am facing a problem with Intel Graphics driver. I have external
  monitor and in display settings the second monitor is detecting but
  it's not working, so could you email me a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.4.25-040425-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 25 21:45:16 2017
  DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
  InstallationDate: Installed on 2017-04-25 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 3537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic 
root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 03JPPR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 3537
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 25 21:37:24 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686189/+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 1858182] Re: Add support for Rizon 3900 Series Processors by updating to a newer kernel version

[Brad Figg]

@ryan

The kernel SRU workflow project is a special project that is only used
for internal processes. Your bug should have been filed against the
ubuntu/linux project which I have now fixed. Also note that we closely
follow upstream stable releases and automatically pick them up.

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: kernel-sru-workflow

-- 
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/1858182

Title:
  Add support for Rizon 3900 Series Processors by updating to a newer
  kernel version

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  According to:
  https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.4.7
  -Stable-Released

  "Greg Kroah-Hartman took time out of his New Year's Eve festivities to
  release Linux 5.4.7, 4.19.92, and 4.14.161 as the newest supported
  stable releases of the Linux kernel.

  Making these kernels noteworthy is that they contain the necessary MCE
  fix for booting the new AMD Ryzen Threadripper 3900 series processors.
  With Linux 5.5 mainline or these back-ported kernels, Linux should be
  booting now without issue.

  These stable kernel updates also add Intel Comet Lake PCH-V and
  Elkhart Lake SoC support to the intel_th driver. But the rest of the
  changes are an assortment of mostly mundane fixes, unless you happened
  to be affected by one of the particular bugs addressed."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858182/+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 1855071] Re: precise/linux-lts-trusty: -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Invalid

-- 
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/1855071

Title:
  precise/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:
  New
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-signing-to-proposed 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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1855073
  packages:
main: linux-lts-trusty
meta: linux-meta-lts-trusty
signed: linux-signed-lts-trusty
  phase: Holding before Packaging
  phase-changed: Wednesday, 04. December 2019 09:36 UTC
  reason:
prepare-package: Holding -- waiting for master bug
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1855071/+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 1850472] Re: linux-kvm: -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1850472

Title:
  linux-kvm:  -proposed tracker

Status in Kernel SRU Workflow:
  New
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Eoan:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850472/+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 1855073] Re: trusty/linux: -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   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/1855073

Title:
  trusty/linux:  -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-signing-to-proposed 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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Ready for Packaging
  phase-changed: Wednesday, 04. December 2019 09:36 UTC
  reason:
prepare-package: Pending -- version not specified
  trackers:
precise/linux-lts-trusty: bug 1855071
unknown/unknown: bug 1855071
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1855073/+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 1825429] Re: linux: -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   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/1825429

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
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:
  New
Status in Kernel SRU Workflow prepare-package-lrm series:
  New
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Disco:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1825430 (bionic/linux-hwe-edge)

  -- swm properties --

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1825429/+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 1699051] Re: linux: -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   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/1699051

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
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:
  Confirmed
Status in Kernel SRU Workflow prepare-package-lbm series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  Confirmed
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:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 
  derivatives: 1699052,1699053

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1699051/+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 1691152] Re: linux-azure: -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Invalid

-- 
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/1691152

Title:
  linux-azure:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
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:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-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:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  New

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: 1691146

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1691152/+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 1856235] Re: bionic/linux-raspi2-5.3: 5.3.0-1015.17~18.04.2 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   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/1856235

Title:
  bionic/linux-raspi2-5.3: 5.3.0-1015.17~18.04.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1854744
  packages:
main: linux-raspi2-5.3
meta: linux-meta-raspi2-5.3
  phase: Testing
  phase-changed: Wednesday, 18. December 2019 23:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Stalled -- waiting for signoff
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856235/+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 1828596] Re: kdump fails when crash is triggered after DLPAR cpu add operation

[Guilherme G. Piccoli]

Focal was uploaded but it's failing in ppc64el again (see LP #1851663).
I've submitted a merge request[0] in Britney to skip this test once more.

Cheers,


Guilherme

[0] https://code.launchpad.net/~gpiccoli/britney/hints-
ubuntu/+merge/377160

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1828596

Title:
  kdump fails when crash is triggered after DLPAR cpu add operation

Status in The Ubuntu-power-systems project:
  In Progress
Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Xenial:
  In Progress
Status in makedumpfile source package in Bionic:
  In Progress
Status in makedumpfile source package in Cosmic:
  Won't Fix
Status in makedumpfile source package in Disco:
  In Progress
Status in makedumpfile source package in Eoan:
  In Progress
Status in makedumpfile source package in Focal:
  In Progress

Bug description:
  [Impact]
  After a CPU add/hotplug operation on Power systems, kdump will fail after a 
crash. The kdump kernel needs to be reloaded after a CPU add/hotplug.

  [Test case]
  Do CPU add/hotplug, trigger a crash, and check for a successful kdump.

  [Regression potential]
  Multiple reloads caused by multiple sequential CPU adds may cause spurious 
log results, and systemd may fail to properly reload the kdump kernel. This has 
been handled by resetting the failure counter when doing such reloads.

  == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 ==
  ---Problem Description---
  kdump fails when crash is triggered after CPU add operation.

  Machine Type = na

  ---System Hang---
   Crashed in early boot process of kdump kernel after crash

  Had to issue system reset from HMC to reclaim

  ---Steps to Reproduce---
   1. Configure kdump.
  2. Add cpu from HMC.
  3. Trigger crash.
  4. Machine hangs after crash as below:

  ---
  [169250.213166] IPI complete
  [169250.234331] kexec: Starting switchover sequence.
  I'm in purgatory
   --- STRUCK HERE ---

  ---uname output---
  na

  ---Debugger---
  A debugger is not configured

  == Comment: #1 - Hari Krishna Bathini  - 2019-05-10 05:56:46 ==
  The problem is, kexec udev rule to restart kdump-tools service - when a core 
is added,
  is not being triggered. The old DT created by kexec (before the core is added)
  is being used by KDump Kernel. So, when system crashes on a thread from
  the added core(s), KDump kernel is failing to get the 'boot_cpuid' and
  eventually failing to boot..

  == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 ==
  The udev rule when CPU is added is not triggered because ppc64 does not
  eject add/remove event when a CPU is hot added/removed. It only ejects
  online/offline event to user space when CPU is hot added/removed.

  So, the below udev rules are never triggered when needed:

  SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"
  SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"

  Also, with how CPU hot add & remove are handled in ppc64, a udev trigger
  to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU
  hot add case by updating the udev rule and drop the udev rule meant for CPU
  hot remove in the kdump udev rules file:

  SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try-
  restart kdump-tools.service"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828596/+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 1858206] Re: WiFi adapter does not work: Linksys WUSB6400M

[El jinete sin cabeza]

With https://askubuntu.com/a/1179178 + Kernel 5.4.7 Work for my.

** Description changed:

  WiFi adapter does not work: Linksys WUSB6400M.
  
  Attach image.
  
  ---
  
  Others:
- * https://github.com/AnandSingh/rtl8822bu
- * 
https://askubuntu.com/questions/1178802/proper-way-of-installing-wifi-drivers-rtl8822bu
+ With 
https://askubuntu.com/questions/1178802/proper-way-of-installing-wifi-drivers-rtl8822bu
 and kernel 5.4.7 work fine!
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.3.0-24-generic 5.3.0-24.26
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1903 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan  3 10:46:26 2020
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (396 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-24-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.184
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2018-12-02 (396 days ago)
  dmi.bios.date: 04/29/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.34
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

** Attachment added: "dmesg_5.4.7-050407-generic.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858206/+attachment/5317434/+files/dmesg_5.4.7-050407-generic.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/1858206

Title:
  WiFi adapter does not work: Linksys WUSB6400M

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  WiFi adapter does not work: Linksys WUSB6400M.

  Attach image.

  ---

  Others:
  With 
https://askubuntu.com/questions/1178802/proper-way-of-installing-wifi-drivers-rtl8822bu
 and kernel 5.4.7 work fine!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.3.0-24-generic 5.3.0-24.26
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1903 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan  3 10:46:26 2020
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (396 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-24-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.184
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2018-12-02 (396 days ago)
  dmi.bios.date: 04/29/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.34
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858206/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
P

[Kernel-packages] [Bug 1857385] Re: xHCI host controller not responding, assume dead via USB-C docking station

[Kai-Heng Feng]

Can you please test this kernel:
https://people.canonical.com/~khfeng/lp1857385/

-- 
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/1857385

Title:
  xHCI host controller not responding, assume dead via USB-C docking
  station

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  I'm using a Lenovo T495s with the Lenovo AJ40 - Ultra Docking Station USB-C 
(https://support.lenovo.com/us/en/solutions/pd500173O) and, when I undock the 
laptop from the docking station, the USB Hub disconnects all the local laptop 
USB ports and they are unusable.
  If I try to re-attach the laptop to the docking station nothing change, the 
ports (docking and laptop) are still disconnected, the hdmi/lan/power is 
working good. Sometimes it happens also when the laptop is docked and I'm 
working.

  The issue seems similar of the bug 1766076:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076

  but here no thunderbolt, it's a ryzen cpu.
  As written in the bug 1766076, the only way to have the USB in working 
condition is unbinding/binding the xhci or using the unit/systemd workaround 
described on post 83 
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076/comments/83) with 
some modification, sometimes is still not working at all.

  The issue is present on Ubuntu 19.10 (see below the logs), on Ubuntu
  18.04 (with kernel 4.x or 5.0 mainline by ubuntu, 5.2 and 5.4 debs
  installed from kernel.org) and on Fedora 31 too. In Windows everything
  is working fine.

  The bios and firmware of the docking station are updated to the last
  one (1 month ago).

  The dmesg when I undock the laptop:

  [  305.299725] usb 2-1: USB disconnect, device number 2
  [  305.310888] [drm] DM_MST: stopping TM on aconnector: 8e933bad [id: 
77]
  [  305.311186] [drm] DM_MST: Disabling connector: 0c5e8d66 [id: 81] 
[master: 8e933bad]
  [  305.311957] [drm] DM_MST: Disabling connector: b7fb3125 [id: 86] 
[master: 8e933bad]
  [  305.312136] [drm] DM_MST: Disabling connector: e642e447 [id: 91] 
[master: 8e933bad]
  [  305.362012] r8169 :03:00.0 enp3s0f0: Link is Down
  [  305.464627] usb 3-4: USB disconnect, device number 2
  [  305.464642] usb 3-4.2: USB disconnect, device number 3
  [  305.472691] usb 2-4: USB disconnect, device number 4
  [  305.472704] usb 2-4.2: USB disconnect, device number 5
  [  305.472712] usb 2-4.2.4: USB disconnect, device number 7
  [  306.725746] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  306.725892] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  ...hundreds of line - the same
  [  310.520323] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  310.520504] xhci_hcd :05:00.3: xHCI host not responding to stop 
endpoint command.
  [  310.520622] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  hundreds of line - the same
  [  310.529388] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  310.529626] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  310.530634] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  310.530740] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  310.530843] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  310.531095] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  310.531324] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  310.532315] xhci_hcd :05:00.3: xHCI host controller not responding, 
assume dead
  [  310.532379] xhci_hcd :05:00.3: HC died; cleaning up
  [  310.532440] xhci_hcd :05:00.3: Timeout while waiting for configure 
endpoint command
  [  310.670248] usb 2-4.3: USB disconnect, device number 6
  [  310.834039] usb 2-4.5: USB disconnect, device number 8
  [  310.835017] usb 2-2: USB disconnect, device number 10

  When I re-attach the latop to the docking:

  [  343.111212] r8169 :03:00.0 enp3s0f0: Link is Up - 100Mbps/Full - flow 
control rx/tx
  [  344.272052] [drm] DM_MST: starting TM on aconnector: 8e933bad [id: 
77]
  [  344.365795] [drm] DM_MST: added connector: e2f1a7b4 [id: 100] 
[master: 8e933bad]
  [  344.365857] [drm] DM_MST: added connector: c263592d [id: 105] 
[master: 8e933bad]
  [  344.365899] [drm] DM_MST: added connector: 44df80f6 [id: 116] 
[master: 8e933bad]

  Software:
  Ubuntu 19.10 - Ubuntu 5.3.0-24.26-generic 5.3.10
  Linux  5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  lspci: (laptop + docking)
  00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root 
Complex
  00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU
  00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 
00h-1fh) PCIe Dummy Host Bridge
  00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP 
Bridge [6:0]
  00:01.3 PCI bridge: Advance

[Kernel-packages] [Bug 1858206] Re: WiFi adapter does not work: Linksys WUSB6400M

[El jinete sin cabeza]

** Description changed:

  WiFi adapter does not work: Linksys WUSB6400M.
  
  Attach image.
  
  ---
  
  Others:
- https://github.com/AnandSingh/rtl8822bu
+ * https://github.com/AnandSingh/rtl8822bu
+ * 
https://askubuntu.com/questions/1178802/proper-way-of-installing-wifi-drivers-rtl8822bu
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.3.0-24-generic 5.3.0-24.26
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1903 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan  3 10:46:26 2020
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (396 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-24-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.184
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2018-12-02 (396 days ago)
  dmi.bios.date: 04/29/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.34
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

-- 
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/1858206

Title:
  WiFi adapter does not work: Linksys WUSB6400M

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  WiFi adapter does not work: Linksys WUSB6400M.

  Attach image.

  ---

  Others:
  * https://github.com/AnandSingh/rtl8822bu
  * 
https://askubuntu.com/questions/1178802/proper-way-of-installing-wifi-drivers-rtl8822bu

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.3.0-24-generic 5.3.0-24.26
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1903 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan  3 10:46:26 2020
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (396 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-24-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.184
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2018-12-02 (396 days ago)
  dmi.bios.date: 04/29/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.34
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858206/+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 1858206] Re: WiFi adapter does not work: Linksys WUSB6400M

[El jinete sin cabeza]

** Description changed:

  WiFi adapter does not work: Linksys WUSB6400M.
  
  Attach image.
+ 
+ ---
+ 
+ Others:
+ https://github.com/AnandSingh/rtl8822bu
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.3.0-24-generic 5.3.0-24.26
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  caravena   1903 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  caravena   1903 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan  3 10:46:26 2020
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (396 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-24-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-5.3.0-24-generic N/A
-  linux-backports-modules-5.3.0-24-generic  N/A
-  linux-firmware1.184
+  linux-restricted-modules-5.3.0-24-generic N/A
+  linux-backports-modules-5.3.0-24-generic  N/A
+  linux-firmware1.184
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2018-12-02 (396 days ago)
  dmi.bios.date: 04/29/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.34
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

-- 
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/1858206

Title:
  WiFi adapter does not work: Linksys WUSB6400M

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  WiFi adapter does not work: Linksys WUSB6400M.

  Attach image.

  ---

  Others:
  * https://github.com/AnandSingh/rtl8822bu
  * 
https://askubuntu.com/questions/1178802/proper-way-of-installing-wifi-drivers-rtl8822bu

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.3.0-24-generic 5.3.0-24.26
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1903 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan  3 10:46:26 2020
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (396 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-24-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.184
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2018-12-02 (396 days ago)
  dmi.bios.date: 04/29/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.34
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858206/+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 1858206] Re: WiFi adapter does not work: Linksys WUSB6400M

[El jinete sin cabeza]

It also does not work with the 5.5-rc4 version of linux.

** Attachment added: "dmesg_5.5.0-050500rc4-generic.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858206/+attachment/5317423/+files/dmesg_5.5.0-050500rc4-generic.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/1858206

Title:
  WiFi adapter does not work: Linksys WUSB6400M

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  WiFi adapter does not work: Linksys WUSB6400M.

  Attach image.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.3.0-24-generic 5.3.0-24.26
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1903 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan  3 10:46:26 2020
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (396 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-24-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.184
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2018-12-02 (396 days ago)
  dmi.bios.date: 04/29/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.34
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858206/+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 1858206] Status changed to Confirmed

[Ubuntu Kernel Bot]

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/1858206

Title:
  WiFi adapter does not work: Linksys WUSB6400M

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  WiFi adapter does not work: Linksys WUSB6400M.

  Attach image.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.3.0-24-generic 5.3.0-24.26
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1903 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan  3 10:46:26 2020
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (396 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-24-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.184
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2018-12-02 (396 days ago)
  dmi.bios.date: 04/29/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.34
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858206/+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 1858206] [NEW] WiFi adapter does not work: Linksys WUSB6400M

[El jinete sin cabeza]

Public bug reported:

WiFi adapter does not work: Linksys WUSB6400M.

Attach image.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.3.0-24-generic 5.3.0-24.26
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  caravena   1903 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan  3 10:46:26 2020
HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
InstallationDate: Installed on 2018-12-02 (396 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-24-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-24-generic N/A
 linux-backports-modules-5.3.0-24-generic  N/A
 linux-firmware1.184
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2018-12-02 (396 days ago)
dmi.bios.date: 04/29/2019
dmi.bios.vendor: Insyde
dmi.bios.version: F.34
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8486
dmi.board.vendor: HP
dmi.board.version: 72.23
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
dmi.product.sku: 3PX63LA#ABM
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug focal wayland-session

** Attachment added: "Linksys.jpg"
   
https://bugs.launchpad.net/bugs/1858206/+attachment/5317404/+files/Linksys.jpg

-- 
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/1858206

Title:
  WiFi adapter does not work: Linksys WUSB6400M

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  WiFi adapter does not work: Linksys WUSB6400M.

  Attach image.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.3.0-24-generic 5.3.0-24.26
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1903 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan  3 10:46:26 2020
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (396 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-24-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.184
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2018-12-02 (396 days ago)
  dmi.bios.date: 04/29/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.34
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858206/+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 1854213] Fwd: [Bug 1831710] Re: Touchpad not working (Lenevo Ideapad 330 series)

[Sumneet Kaur Bamrah]

Hi Kai,

Sharing/Forwarding a previous mail in response to - "Do you mean the DKMS
works on previous kernels?"

Apologise, since I am unsure. Hope this helps!

Sumneet


-- Forwarded message -
From: Jeremy <1831...@bugs.launchpad.net>
Date: Wed, Jun 5, 2019 at 3:30 PM
Subject: [Bug 1831710] Re: Touchpad not working (Lenevo Ideapad 330 series)
To: 


Any results from terminal for
dmesg | grep -i elan

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1831710

Title:
  Touchpad not working (Lenevo Ideapad 330 series)

Status in linux-signed-hwe package in Ubuntu:
  New

Bug description:
  The touch pad has not been used since the purchase of the product.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-21-generic 4.18.0-21.22~18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun  5 13:41:22 2019
  InstallationDate: Installed on 2019-06-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1831710/+subscriptions


-- 
Thanks and Regards,
Sumneet Kaur Bamrah

-- 
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/1854213

Title:
  No Wifi Adapter found - Lenevo Ideapad 330 series

Status in linux package in Ubuntu:
  Confirmed
Status in rtl8821ce package in Ubuntu:
  New

Bug description:
  Commands executed

  1.  ubuntu-bug linux

  2. cat /proc/version_signature
  Ubuntu 5.3.0-23.25~18.04.2-generic 5.3.7

  3. sudo lspci -vnvn > lspci-vnvn.log
  pcilib: sysfs_read_vpd: read failed: Input/output error

  4. lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  5. apt-cache policy pkgname
  N: Unable to locate package pkgname

  What you expected to happen? 
  Connect to the Internet after installing the update

  What happened instead?
  No Wifi Adapter found message displayed instead

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.3.0-23-generic 5.3.0-23.25~18.04.2
  ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.2-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 28 00:44:57 2019
  InstallationDate: Installed on 2019-06-05 (175 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: linux-signed-hwe-edge
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  athena 1573 F pulseaudio
   /dev/snd/controlC0:  athena 1573 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-06-05 (212 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IwConfig:
   enp3s0f3u3  no wireless extensions.
   
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: LENOVO 81D2
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=29a08da7-0f52-4ee8-8424-f2b37885999f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.173.13
  Tags:  bionic
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/10/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7VCN46WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330-15ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr7VCN46WW:bd12/10/2018:svnLENOVO:pn81D2:pvrLenovoideapad330-15ARR:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15ARR:
  dmi.product.family: ideapad 330-15ARR
  dmi.product.name: 81D2
  dmi.product.sku: LENOVO_MT_81D2_BU_idea_FM_ideapad 330-15ARR
  dmi.product.version: Lenovo ideapad 330-15ARR
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.

[Kernel-packages] [Bug 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic

[Rodop]

The same problem on Lenovo Ideapad320 with kernel 4.15.0-72-generic
#81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64
GNU/Linux.

The problem didn't exist in previous kernel version.

-- 
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/1854798

Title:
  Synaptics s3203 touchpad not working after update to kernel
  4.15.0-72-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  SRU justification
  =
  [Impact]
  Synaptics s3203 touchpad not working after update to kernel
  4.15.0-72-generic

  [Fix]
  After applied commit "Input: synaptics-rmi4 - avoid processing unknown
  IRQs",
  no irq response from touchpad.
  This commit is depended on commit:
  "Input: synaptics-rmi4 - convert irq distribution to irq_domain"

  [Test]
  Verified on hardware, tests results are good.

  [Regression Potential]
  Low.
  Fix bug that introduced by stable release update.

  2nd and 3rd patches are fixes for the 1st patch.
  These commits are already included by eoan kernel, so bionic 4.15 only.

  Original reports
  ===

  environment:
  Dell Laptop XPS-9333
  Device:
  # xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SYNAPTICS Synaptics Large Touch Screen  id=9[slave  pointer 
 (2)]
  ⎜   ↳ Synaptics s3203 id=12   [slave  pointer 
 (2)]
  ⎜   ↳ Ultrathin Touch Mouse   id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=13   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=14   [slave  
keyboard (3)]
  ↳ Integrated_Webcam_HD: Integrate id=10   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]

  # xinput --list-props 12
  Device 'Synaptics s3203':
   Device Enabled (142):1
   Coordinate Transformation Matrix (144):  1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
   Device Accel Profile (270):  1
   Device Accel Constant Deceleration (271):2.50
   Device Accel Adaptive Deceleration (272):1.00
   Device Accel Velocity Scaling (273): 9.712231
   Synaptics Edges (304):   162, 3908, 133, 2339
   Synaptics Finger (305):  25, 30, 0
   Synaptics Tap Time (306):180
   Synaptics Tap Move (307):209
   Synaptics Tap Durations (308):   180, 180, 100
   Synaptics ClickPad (309):1
   Synaptics Middle Button Timeout (310):   0
   Synaptics Two-Finger Pressure (311): 282
   Synaptics Two-Finger Width (312):7
   Synaptics Scrolling Distance (313):  -95, 95
   Synaptics Edge Scrolling (314):  0, 0, 0
   Synaptics Two-Finger Scrolling (315):1, 1
   Synaptics Move Speed (316):  1.00, 1.75, 0.042008, 0.00
   Synaptics Off (317): 0
   Synaptics Locked Drags (318):0
   Synaptics Locked Drags Timeout (319):5000
   Synaptics Tap Action (320):  0, 0, 0, 0, 1, 3, 2
   Synaptics Click Action (321):1, 3, 2
   Synaptics Circular Scrolling (322):  0
   Synaptics Circular Scrolling Distance (323): 0.10
   Synaptics Circular Scrolling Trigger (324):  0
   Synaptics Circular Pad (325):0
   Synaptics Palm Detection (326):  1
   Synaptics Palm Dimensions (327): 10, 200
   Synaptics Coasting Speed (328):  20.00, 50.00
   Synaptics Pressure Motion (329): 30, 160
   Synaptics Pressure Motion Factor (330):  1.00, 1.00
   Synaptics Resolution Detect (331):   1
   Synaptics Grab Event Device (332):   0
   Synaptics Gestures (333):1
   Synaptics Capabilities (334):1, 0, 0, 1, 1, 1, 0
   Synaptics Pad Resolution (335):  42, 42
   Synaptics Area (336):0, 0, 0, 0
   Synaptics Soft Button Areas (337):   0, 0, 0, 0, 0, 0, 0, 0
   Synaptics Noise Cancellation (338):  23, 23
   Device Product ID (262): 1739, 10036
   Device Node (263):   "/dev/input/event5"

  # lspci
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 09)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller 

[Kernel-packages] [Bug 1809704] Re: efivarfs test in ubuntu_kernel_selftest failed on the second run

[Po-Hsu Lin]

https://lists.ubuntu.com/archives/kernel-team/2020-January/106590.html

** Description changed:

- This seems to be an issue to the test case, if you run the test suite
- twice, it will fail on the second run.
+ == SRU Justification ==
+ If you run the test selftest/efivarfs test suite twice, it will fail on
+ the second run.
+ 
+ This is because the test file created in the first run will obtain the
+ immutable property, and it will make the second attempt failed with
+ premission denied error.
+ 
+ == Fix ==
+ * 1f0ea958 (selftests: efivarfs: return Kselftest Skip code for skipped tests)
+ * dff6d2ae (selftests/efivarfs: clean up test files from test_create*())
+ 
+ This issue exists in X/B/D, fixed in newer releases.
+ 
+ For Xenial it lacks the crucial commit which allows the selftest
+ framework to handle KSFT_SKIP return code (3f4435b5), so the first
+ commit has to be backported to keep using 0 as its return value. The
+ second commit is a backport with fuzzy adjustments.
+ 
+ For Bionic, the first commit is a clean cherry-pick, the second is a
+ backport with fuzzy adjustments.
+ 
+ For Disco, it just needs the second commit, which is also a backport
+ with fuzzy adjustments as well.
+ 
+ == Test ==
+ Patch tested against the affected kernels, and it works as expected.
+ 
+ == Regression Potential ==
+ Low, changes limited to testing tools.
+ 
+ 
+ == Original Bug Report ==
+ This seems to be an issue to the test case, if you run the test suite twice, 
it will fail on the second run.
  
  The first run will create the test file:
  $ ll 
/sys/firmware/efi/efivars/test_create_read-210be57c-9849-4fc7-a635-e6382d1aec27
  -rw--- 1 root root 0 Dec 24 07:16 
/sys/firmware/efi/efivars/test_create_read-210be57c-9849-4fc7-a635-e6382d1aec27
  
  This is cause the open(O_WRONLY) test in test_create_read failed with 
premission denied on the second run.
  This issue can be reproduced with upstream kernel tree on Xenial as well.
  
  $ sudo make -C linux/tools/testing/selftests TARGETS=efivarfs run_tests
  make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
  for TARGET in efivarfs; do \
   make -C $TARGET; \
  done;
  make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs'
  make[1]: Nothing to be done for 'all'.
  make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs'
  for TARGET in efivarfs; do \
   make -C $TARGET run_tests; \
  done;
  make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs'
  
  running test_create
  
  ./efivarfs.sh: line 48: 
/sys/firmware/efi/efivars/test_create-210be57c-9849-4fc7-a635-e6382d1aec27: 
Permission denied
    [PASS]
  
  running test_create_empty
  
  ./efivarfs.sh: line 65: 
/sys/firmware/efi/efivars/test_create_empty-210be57c-9849-4fc7-a635-e6382d1aec27:
 Permission denied
    [PASS]
  
  running test_create_read
  
  open(O_WRONLY): Permission denied
    [FAIL]
  
  running test_delete
  
    [PASS]
  
  running test_zero_size_delete
  
    [PASS]
  
  running test_open_unlink
  
    [PASS]
  
  running test_valid_filenames
  
    [PASS]
  
  running test_invalid_filenames
  
    [PASS]
  selftests: efivarfs.sh [FAIL]
  make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs'
  make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-141-generic 4.4.0-141.167
  ProcVersionSignature: User Name 4.4.0-141.167-generic 4.4.162
  Uname: Linux 4.4.0-141-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 24 05:10 seq
   crw-rw 1 root audio 116, 33 Dec 24 05:10 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   [92859.670497] smpboot: CPU 111 is now offline
   [92859.723040] kvm: disabled by bios
   [92859.750562] smpboot: Booting Node 1 Processor 111 APIC 0x7d
   [92859.821706] kvm: disabled by bios
  Date: Tue Dec 25 06:30:01 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Found

[Kernel-packages] [Bug 1830678] Re: netns_sysfs from containers test suite in LTP failed with KVM kernel

[Po-Hsu Lin]

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: ubuntu-kernel-tests
   Status: Confirmed => In Progress

-- 
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/1830678

Title:
  netns_sysfs from containers test suite in LTP failed with KVM kernel

Status in ubuntu-kernel-tests:
  In Progress
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux-kvm source package in Disco:
  New

Bug description:
  <<>>
  tag=netns_sysfs stime=1559024934
  cmdline="netns_sysfs.sh"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  RTNETLINK answers: Operation not supported
  netns_sysfs 1 TBROK: failed to add a new (host) dummy device
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=2 corefile=no
  cutime=1 cstime=0
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1035-kvm 4.15.0-1035.35
  ProcVersionSignature: User Name 4.15.0-1035.35-kvm 4.15.18
  Uname: Linux 4.15.0-1035-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Tue May 28 06:22:51 2019
  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/1830678/+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 1851486] Re: Handle the skip return code in kernel_selftests on Xenial

[Po-Hsu Lin]

** Changed in: linux (Ubuntu)
   Status: Incomplete => Fix Released

** Changed in: linux (Ubuntu Xenial)
   Status: Incomplete => Confirmed

** Changed in: ubuntu-kernel-tests
   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/1851486

Title:
  Handle the skip return code in kernel_selftests on Xenial

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed

Bug description:
  Like bug 1812352

  In the ubuntu_kernel_selftests, the skipped test will uses return code
  4 (KSFT_SKIP).

  However the code to handle this non-zero return code was not
  implemented in the kselftest framework. And this will generate some
  false-positives results as those skipped tests were treated as a
  failure.

  In X-KVM kernel, test_user_copy.sh test in user will fail because of this:
  user: module test_user_copy is not found [SKIP]
  not ok 1..1 selftests: test_user_copy.sh [FAIL]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1851486/+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 1854744] Re: eoan/linux-raspi2: 5.3.0-1015.17 -proposed tracker

[Gavin Lin]

Hardware Certification have completed testing this -proposed kernel. No 
regressions were observed, results are available here:
Rpi2b-armhf: 
https://certification.canonical.com/hardware/201906-27188/submission/156954/
Rpi3b-arm64: 
https://certification.canonical.com/hardware/201811-26649/submission/157048/
Rpi3b-armhf: 
https://certification.canonical.com/hardware/201811-26649/submission/157046/
Rpi3a+-arm64: 
https://certification.canonical.com/hardware/201901-26785/submission/157006/
Rpi3a+-armhf: 
https://certification.canonical.com/hardware/201901-26785/submission/157284/
Rpi3b+-arm64: 
https://certification.canonical.com/hardware/201810-26542/submission/156955/
Rpi3b+-armhf: 
https://certification.canonical.com/hardware/201810-26542/submission/157103/
Rpi4b-1g-arm64: 
https://certification.canonical.com/hardware/201911-27471/submission/157608/
Rpi4b-1g-armhf: 
https://certification.canonical.com/hardware/201910-27407/submission/157607/
Rpi4b-2g-arm64: 
https://certification.canonical.com/hardware/201911-27507/submission/157604/
Rpi4b-2g-armhf: 
https://certification.canonical.com/hardware/201911-27506/submission/157605/
Rpi4b-4g-arm64: 
https://certification.canonical.com/hardware/201911-27456/submission/157603/
Rpi4b-4g-armhf: 
https://certification.canonical.com/hardware/201911-27455/submission/157606/
CM3-arm64: 
https://certification.canonical.com/hardware/201711-25992/submission/157627/
CM3-armhf: 
https://certification.canonical.com/hardware/201711-25992/submission/157612/
CM3+-arm64: 
https://certification.canonical.com/hardware/201908-27277/submission/157609/
CM3+-armhf: 
https://certification.canonical.com/hardware/201908-27277/submission/157611/

** Changed in: kernel-sru-workflow/certification-testing
   Status: Invalid => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1854744

Title:
  eoan/linux-raspi2: 5.3.0-1015.17 -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:
  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 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Eoan:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: '1856807'
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Signoff
  phase-changed: Friday, 20. December 2019 17:48 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- security signoff not verified
security-signoff: Stalled -- waiting for signoff
  trackers:
bionic/linux-raspi2-5.3: bug 1856235
eoan/linux-raspi2/pi-kernel: bug 1854743
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854744/+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 1857348] Re: amdgpu crashes badly

[piontec]

I checked there, but there's no 'picasso_ta.bin' file there:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/tree/amdgpu

-- 
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/1857348

Title:
  amdgpu crashes badly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm running current ubuntu 19.10 with kernel "Ubuntu
  5.3.0-24.26-generic 5.3.10" on a ThinkPad T495 laptop, which is
  confirmed to be certified here:
  https://certification.ubuntu.com/hardware/201905-27049

  Unfortunately, the experience is really bad: `amdgpu` driver in the
  kernel crashes sometimes. I managed to get the `dmesg` output, please
  see atachemnt. This is confirmed at least on linux-image-5.3.0-18 and
  linux-image-5.3.0-24 "linux-image-X-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-generic 5.3.0.24.28
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Mon Dec 23 14:50:14 2019
  InstallationDate: Installed on 2019-12-07 (16 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20NJ0010PB
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-24-generic 
root=/dev/mapper/ubuntu--vg-rootfs ro rootflags=subvol=@ quiet splash 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/28/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R12ET46W(1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NJ0010PB
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR12ET46W(1.16):bd10/28/2019:svnLENOVO:pn20NJ0010PB:pvrThinkPadT495:rvnLENOVO:rn20NJ0010PB:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T495
  dmi.product.name: 20NJ0010PB
  dmi.product.sku: LENOVO_MT_20NJ_BU_Think_FM_ThinkPad T495
  dmi.product.version: ThinkPad T495
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857348/+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 1855378] Re: PC shutdown when power connected in suspend

[Kai-Heng Feng]

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc4

-- 
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/1855378

Title:
  PC shutdown when power connected in suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  If PC on (not in suspend), plugging in the power does not fail.

  If PC in suspend, plugging in the power causes PC to shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evince 3.28.4-0ubuntu1.2
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec  5 21:34:13 2019
  InstallationDate: Installed on 2019-06-21 (168 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arturo 2308 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-06-21 (194 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 05c8:03ab Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion x360 Convertible 15-br0xx
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic 
root=UUID=f8e5cecc-719e-4e69-afd5-b82a7690e747 ro quiet splash pci=noaer 
vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-37-generic N/A
   linux-backports-modules-5.0.0-37-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.0.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 07/26/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8315
  dmi.board.vendor: HP
  dmi.board.version: 33.20
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd07/26/2017:svnHP:pnHPPavilionx360Convertible15-br0xx:pvrType1ProductConfigId:rvnHP:rn8315:rvr33.20:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 15-br0xx
  dmi.product.sku: 1KT67UA#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855378/+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 1857348] Re: amdgpu crashes badly

[Kai-Heng Feng]

Firmware can be found here:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/

Once the firmwares are copied to /lib/firmwares, initramfs also requires an 
update:
$ sudo update-initramfs -u -k all

-- 
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/1857348

Title:
  amdgpu crashes badly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm running current ubuntu 19.10 with kernel "Ubuntu
  5.3.0-24.26-generic 5.3.10" on a ThinkPad T495 laptop, which is
  confirmed to be certified here:
  https://certification.ubuntu.com/hardware/201905-27049

  Unfortunately, the experience is really bad: `amdgpu` driver in the
  kernel crashes sometimes. I managed to get the `dmesg` output, please
  see atachemnt. This is confirmed at least on linux-image-5.3.0-18 and
  linux-image-5.3.0-24 "linux-image-X-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-generic 5.3.0.24.28
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Mon Dec 23 14:50:14 2019
  InstallationDate: Installed on 2019-12-07 (16 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20NJ0010PB
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-24-generic 
root=/dev/mapper/ubuntu--vg-rootfs ro rootflags=subvol=@ quiet splash 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/28/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R12ET46W(1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NJ0010PB
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR12ET46W(1.16):bd10/28/2019:svnLENOVO:pn20NJ0010PB:pvrThinkPadT495:rvnLENOVO:rn20NJ0010PB:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T495
  dmi.product.name: 20NJ0010PB
  dmi.product.sku: LENOVO_MT_20NJ_BU_Think_FM_ThinkPad T495
  dmi.product.version: ThinkPad T495
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857348/+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 1858077] Re: iwlwifi crash, lock and restart

[Kai-Heng Feng]

Unfortunately all of them are unsigned.

-- 
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/1858077

Title:
  iwlwifi crash, lock and restart

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My whole system was frozen for a few seconds, then it got back to
  normal. In dmesg I found iwlwifi module crash, please see the attached
  log.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-generic 5.3.0.24.28
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  piontec2965 F pulseaudio
   /dev/snd/controlC1:  piontec2965 F pulseaudio
   /dev/snd/controlC0:  piontec2965 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan  2 09:55:20 2020
  InstallationDate: Installed on 2019-12-07 (25 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20NJ0010PB
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-24-generic 
root=/dev/mapper/ubuntu--vg-rootfs ro rootflags=subvol=@ quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/28/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R12ET46W(1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NJ0010PB
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR12ET46W(1.16):bd10/28/2019:svnLENOVO:pn20NJ0010PB:pvrThinkPadT495:rvnLENOVO:rn20NJ0010PB:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T495
  dmi.product.name: 20NJ0010PB
  dmi.product.sku: LENOVO_MT_20NJ_BU_Think_FM_ThinkPad T495
  dmi.product.version: ThinkPad T495
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858077/+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 1854213] Re: No Wifi Adapter found - Lenevo Ideapad 330 series

[Kai-Heng Feng]

Do you mean the DKMS works on previous kernels?

-- 
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/1854213

Title:
  No Wifi Adapter found - Lenevo Ideapad 330 series

Status in linux package in Ubuntu:
  Confirmed
Status in rtl8821ce package in Ubuntu:
  New

Bug description:
  Commands executed

  1.  ubuntu-bug linux

  2. cat /proc/version_signature
  Ubuntu 5.3.0-23.25~18.04.2-generic 5.3.7

  3. sudo lspci -vnvn > lspci-vnvn.log
  pcilib: sysfs_read_vpd: read failed: Input/output error

  4. lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  5. apt-cache policy pkgname
  N: Unable to locate package pkgname

  What you expected to happen? 
  Connect to the Internet after installing the update

  What happened instead?
  No Wifi Adapter found message displayed instead

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.3.0-23-generic 5.3.0-23.25~18.04.2
  ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.2-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 28 00:44:57 2019
  InstallationDate: Installed on 2019-06-05 (175 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: linux-signed-hwe-edge
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  athena 1573 F pulseaudio
   /dev/snd/controlC0:  athena 1573 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-06-05 (212 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IwConfig:
   enp3s0f3u3  no wireless extensions.
   
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: LENOVO 81D2
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=29a08da7-0f52-4ee8-8424-f2b37885999f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.173.13
  Tags:  bionic
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/10/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7VCN46WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330-15ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr7VCN46WW:bd12/10/2018:svnLENOVO:pn81D2:pvrLenovoideapad330-15ARR:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15ARR:
  dmi.product.family: ideapad 330-15ARR
  dmi.product.name: 81D2
  dmi.product.sku: LENOVO_MT_81D2_BU_idea_FM_ideapad 330-15ARR
  dmi.product.version: Lenovo ideapad 330-15ARR
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854213/+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 1857348] Re: amdgpu crashes badly

[Lukasz Piatkowski]

I updated the kernel to mainline 5.5.0-050500rc4-generic #201912291930
,but now I get this in dmesg:

[1.198203] amdgpu :06:00.0: Direct firmware load for 
amdgpu/picasso_ta.bin failed with error -2
[1.198207] amdgpu :06:00.0: psp v10.0: Failed to load firmware 
"amdgpu/picasso_ta.bin"

-- 
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/1857348

Title:
  amdgpu crashes badly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm running current ubuntu 19.10 with kernel "Ubuntu
  5.3.0-24.26-generic 5.3.10" on a ThinkPad T495 laptop, which is
  confirmed to be certified here:
  https://certification.ubuntu.com/hardware/201905-27049

  Unfortunately, the experience is really bad: `amdgpu` driver in the
  kernel crashes sometimes. I managed to get the `dmesg` output, please
  see atachemnt. This is confirmed at least on linux-image-5.3.0-18 and
  linux-image-5.3.0-24 "linux-image-X-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-generic 5.3.0.24.28
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Mon Dec 23 14:50:14 2019
  InstallationDate: Installed on 2019-12-07 (16 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20NJ0010PB
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-24-generic 
root=/dev/mapper/ubuntu--vg-rootfs ro rootflags=subvol=@ quiet splash 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/28/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R12ET46W(1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NJ0010PB
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR12ET46W(1.16):bd10/28/2019:svnLENOVO:pn20NJ0010PB:pvrThinkPadT495:rvnLENOVO:rn20NJ0010PB:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T495
  dmi.product.name: 20NJ0010PB
  dmi.product.sku: LENOVO_MT_20NJ_BU_Think_FM_ThinkPad T495
  dmi.product.version: ThinkPad T495
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857348/+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 1858077] Re: iwlwifi crash, lock and restart

[Lukasz Piatkowski]

I can test it for some time, but I had to disable secure boot to run it.
Are there mainline signed kerneles available somewhere?

-- 
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/1858077

Title:
  iwlwifi crash, lock and restart

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My whole system was frozen for a few seconds, then it got back to
  normal. In dmesg I found iwlwifi module crash, please see the attached
  log.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-generic 5.3.0.24.28
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  piontec2965 F pulseaudio
   /dev/snd/controlC1:  piontec2965 F pulseaudio
   /dev/snd/controlC0:  piontec2965 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan  2 09:55:20 2020
  InstallationDate: Installed on 2019-12-07 (25 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20NJ0010PB
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-24-generic 
root=/dev/mapper/ubuntu--vg-rootfs ro rootflags=subvol=@ quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/28/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R12ET46W(1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NJ0010PB
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR12ET46W(1.16):bd10/28/2019:svnLENOVO:pn20NJ0010PB:pvrThinkPadT495:rvnLENOVO:rn20NJ0010PB:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T495
  dmi.product.name: 20NJ0010PB
  dmi.product.sku: LENOVO_MT_20NJ_BU_Think_FM_ThinkPad T495
  dmi.product.version: ThinkPad T495
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858077/+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 1854213] Re: No Wifi Adapter found - Lenevo Ideapad 330 series

[Sumneet Kaur Bamrah]

Okay, thanks for sharing an update. Hopefully, things will improve by then.
I managed to work with the previous installation (update) temporarily. Any
alternative until then, Kai?

On Fri, Jan 3, 2020 at 11:10 AM Kai-Heng Feng 
wrote:

> The 8821ce DKMS is pretty bad.
> We need to wait for a few months until Realtek finished 8821ce support in
> rtw88.
>
> ** Also affects: rtl8821ce (Ubuntu)
>Importance: Undecided
>Status: New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1854213
>
> Title:
>   No Wifi Adapter found - Lenevo Ideapad 330 series
>
> Status in linux package in Ubuntu:
>   Confirmed
> Status in rtl8821ce package in Ubuntu:
>   New
>
> Bug description:
>   Commands executed
>
>   1.  ubuntu-bug linux
>
>   2. cat /proc/version_signature
>   Ubuntu 5.3.0-23.25~18.04.2-generic 5.3.7
>
>   3. sudo lspci -vnvn > lspci-vnvn.log
>   pcilib: sysfs_read_vpd: read failed: Input/output error
>
>   4. lsb_release -rd
>   Description:  Ubuntu 18.04.3 LTS
>   Release:  18.04
>
>   5. apt-cache policy pkgname
>   N: Unable to locate package pkgname
>
>   What you expected to happen?
>   Connect to the Internet after installing the update
>
>   What happened instead?
>   No Wifi Adapter found message displayed instead
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: linux-image-5.3.0-23-generic 5.3.0-23.25~18.04.2
>   ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.2-generic 5.3.7
>   Uname: Linux 5.3.0-23-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.9
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Thu Nov 28 00:44:57 2019
>   InstallationDate: Installed on 2019-06-05 (175 days ago)
>   InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
> (20190210)
>   SourcePackage: linux-signed-hwe-edge
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   ---
>   ProblemType: Bug
>   ApportVersion: 2.20.9-0ubuntu7.9
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC1:  athena 1573 F pulseaudio
>/dev/snd/controlC0:  athena 1573 F pulseaudio
>   CurrentDesktop: ubuntu:GNOME
>   DistroRelease: Ubuntu 18.04
>   InstallationDate: Installed on 2019-06-05 (212 days ago)
>   InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
> (20190210)
>   IwConfig:
>enp3s0f3u3  no wireless extensions.
>
>enp2s0no wireless extensions.
>
>lono wireless extensions.
>   MachineType: LENOVO 81D2
>   Package: linux (not installed)
>   ProcFB: 0 amdgpudrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
> root=UUID=29a08da7-0f52-4ee8-8424-f2b37885999f ro quiet splash vt.handoff=1
>   ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10
>   RelatedPackageVersions:
>linux-restricted-modules-5.3.0-24-generic N/A
>linux-backports-modules-5.3.0-24-generic  N/A
>linux-firmware1.173.13
>   Tags:  bionic
>   Uname: Linux 5.3.0-24-generic x86_64
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>   dmi.bios.date: 12/10/2018
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: 7VCN46WW
>   dmi.board.asset.tag: NO Asset Tag
>   dmi.board.name: LNVNB161216
>   dmi.board.vendor: LENOVO
>   dmi.board.version: NO DPK
>   dmi.chassis.asset.tag: NO Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: Lenovo ideapad 330-15ARR
>   dmi.modalias:
> dmi:bvnLENOVO:bvr7VCN46WW:bd12/10/2018:svnLENOVO:pn81D2:pvrLenovoideapad330-15ARR:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15ARR:
>   dmi.product.family: ideapad 330-15ARR
>   dmi.product.name: 81D2
>   dmi.product.sku: LENOVO_MT_81D2_BU_idea_FM_ideapad 330-15ARR
>   dmi.product.version: Lenovo ideapad 330-15ARR
>   dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854213/+subscriptions
>


-- 
Thanks and Regards,
Sumneet Kaur Bamrah

-- 
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/1854213

Title:
  No Wifi Adapter found - Lenevo Ideapad 330 series

Status in linux package in Ubuntu:
  Confirmed
Status in rtl8821ce package in Ubuntu:
  New

Bug description:
  Commands executed

  1.  ubuntu-bug linux

  2. cat /proc/version_signature
  Ubuntu 5.3.0-23.25~18.04.2-generic 5.3.7

  3. sudo lspci -vnvn > lspci-vnvn.log
  pcilib: sysfs_read_vpd: read failed: Input/output error

  4. lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  5. apt-cache policy pkgname
  N: Unable to locate package pkgname

  What you expected to happen? 
  Connect to the Internet after installing the update

  What happened instead