[Kernel-packages] [Bug 1876856] [NEW] xenial: soft lockup in check_unsafe_exec()

[Vasily Averin]

Public bug reported:

Endless cycle was detected few times during ubuntu 16.04 testing insied openvz 
VMs
dmesg output and crash dump ivestigation shows that foolowing ubuntu 
16.04.patch is guilty
commit d6572202d986a84feda4cf7e6ce0bebaa18cb8fe
Author: Colin Ian King 
Date:   Fri May 12 15:51:56 2017 +0100
UBUNTU:SAUCE: exec: ensure file system accounting in check_unsafe_exec is 
correct

BugLink: http://bugs.launchpad.net/bugs/1672819

fs/exec.c:: check_unsafe_exec()
...
recheck:
fs_recheck = false;
t = p;
n_fs = 1;
spin_lock(&p->fs->lock);
rcu_read_lock();
while_each_thread(p, t) {
if (t->fs == p->fs)
n_fs++;
if (t->flags & (PF_EXITING | PF_FORKNOEXEC))
fs_recheck  = true;
}
rcu_read_unlock();
 
if (p->fs->users > n_fs) {
if (fs_recheck) {
spin_unlock(&p->fs->lock);
goto recheck; << cycles forever
}
bprm->unsafe |= LSM_UNSAFE_SHARE;
} else
p->fs->in_exec = 1;
spin_unlock(&p->fs->lock);

dmesg example is attached,
let me know if you want to look at  crash dump image.
Bug is xenial-specific (4.4 kernel), other kernel branches seems are not 
affected.

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


** Tags: xenial

** Attachment added: "dmesg output"
   https://bugs.launchpad.net/bugs/1876856/+attachment/5366596/+files/dmesg.txt

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

Title:
  xenial: soft lockup in check_unsafe_exec()

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Endless cycle was detected few times during ubuntu 16.04 testing insied 
openvz VMs
  dmesg output and crash dump ivestigation shows that foolowing ubuntu 
16.04.patch is guilty
  commit d6572202d986a84feda4cf7e6ce0bebaa18cb8fe
  Author: Colin Ian King 
  Date:   Fri May 12 15:51:56 2017 +0100
  UBUNTU:SAUCE: exec: ensure file system accounting in check_unsafe_exec is 
correct
  
  BugLink: http://bugs.launchpad.net/bugs/1672819

  fs/exec.c:: check_unsafe_exec()
  ...
  recheck:
  fs_recheck = false;
  t = p;
  n_fs = 1;
  spin_lock(&p->fs->lock);
  rcu_read_lock();
  while_each_thread(p, t) {
  if (t->fs == p->fs)
  n_fs++;
  if (t->flags & (PF_EXITING | PF_FORKNOEXEC))
  fs_recheck  = true;
  }
  rcu_read_unlock();
   
  if (p->fs->users > n_fs) {
  if (fs_recheck) {
  spin_unlock(&p->fs->lock);
  goto recheck; << cycles forever
  }
  bprm->unsafe |= LSM_UNSAFE_SHARE;
  } else
  p->fs->in_exec = 1;
  spin_unlock(&p->fs->lock);

  dmesg example is attached,
  let me know if you want to look at  crash dump image.
  Bug is xenial-specific (4.4 kernel), other kernel branches seems are not 
affected.

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

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

** Tags added: xenial

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

Title:
  xenial: soft lockup in check_unsafe_exec()

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Endless cycle was detected few times during ubuntu 16.04 testing insied 
openvz VMs
  dmesg output and crash dump ivestigation shows that foolowing ubuntu 
16.04.patch is guilty
  commit d6572202d986a84feda4cf7e6ce0bebaa18cb8fe
  Author: Colin Ian King 
  Date:   Fri May 12 15:51:56 2017 +0100
  UBUNTU:SAUCE: exec: ensure file system accounting in check_unsafe_exec is 
correct
  
  BugLink: http://bugs.launchpad.net/bugs/1672819

  fs/exec.c:: check_unsafe_exec()
  ...
  recheck:
  fs_recheck = false;
  t = p;
  n_fs = 1;
  spin_lock(&p->fs->lock);
  rcu_read_lock();
  while_each_thread(p, t) {
  if (t->fs == p->fs)
  n_fs++;
  if (t->flags & (PF_EXITING | PF_FORKNOEXEC))
  fs_recheck  = true;
  }
  rcu_read_unlock();
   
  if (p->fs->users > n_fs) {
  if (fs_recheck) {
  spin_unlock(&p->fs->lock);
  goto recheck; << cycles forever
  }
  bprm->unsafe |= LSM_UNSAFE_SHARE;
  } else
  p->fs->in_exec = 1;
  spin_unlock(&p->fs->lock);

  dmesg example is attached,
  let me know if you want to look at  crash dump image.
  Bug is xenial-specific (4.4 kernel), other kernel branches seems are not 
affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876856/+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 1056410] Re: resizing exiting drive partitions on ARM Quantal does not work

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  resizing exiting drive partitions on ARM Quantal does not work

Status in linux package in Ubuntu:
  Expired
Status in ubiquity package in Ubuntu:
  Expired
Status in linux source package in Quantal:
  Won't Fix
Status in ubiquity source package in Quantal:
  Won't Fix

Bug description:
  I was testing this iso: 
http://cdimage.ubuntu.com/daily-live/20120925/quantal-desktop-armhf+omap4.img 
installing from a SD card to a USB key.
  In the "Installation type window" I selected "something else" and tried to 
modify the USB key partioning.
  On this USB key I had a prevoius installation of Ubuntu Beta2, I tried to 
cancel /dev/sda2 and enlarge /dev/sda1, but the installer got blocked and even 
if I waited for a long time it kept on having the cursor blinking with a circle 
and never stopped.
  I had to reboot from command line.
  I'm attaching a screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: ubiquity 2.12.3
  ProcVersionSignature: Ubuntu 3.5.0-211.18-omap4 3.5.4
  Uname: Linux 3.5.0-211-omap4 armv7l
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: armhf
  CasperVersion: 1.324
  Date: Tue Sep 25 19:18:30 2012
  InstallCmdLine: vram=40M mem=456M@0x8000 mem=512M@0xA000   fixrtc 
quiet splash -- boot=casper only-ubiquity nocompcache
  LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Beta armhf+omap4 (20120925)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1056410/+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 1056410] Re: resizing exiting drive partitions on ARM Quantal does not work

[Launchpad Bug Tracker]

[Expired for ubiquity (Ubuntu) because there has been no activity for 60
days.]

** Changed in: ubiquity (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  resizing exiting drive partitions on ARM Quantal does not work

Status in linux package in Ubuntu:
  Expired
Status in ubiquity package in Ubuntu:
  Expired
Status in linux source package in Quantal:
  Won't Fix
Status in ubiquity source package in Quantal:
  Won't Fix

Bug description:
  I was testing this iso: 
http://cdimage.ubuntu.com/daily-live/20120925/quantal-desktop-armhf+omap4.img 
installing from a SD card to a USB key.
  In the "Installation type window" I selected "something else" and tried to 
modify the USB key partioning.
  On this USB key I had a prevoius installation of Ubuntu Beta2, I tried to 
cancel /dev/sda2 and enlarge /dev/sda1, but the installer got blocked and even 
if I waited for a long time it kept on having the cursor blinking with a circle 
and never stopped.
  I had to reboot from command line.
  I'm attaching a screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: ubiquity 2.12.3
  ProcVersionSignature: Ubuntu 3.5.0-211.18-omap4 3.5.4
  Uname: Linux 3.5.0-211-omap4 armv7l
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: armhf
  CasperVersion: 1.324
  Date: Tue Sep 25 19:18:30 2012
  InstallCmdLine: vram=40M mem=456M@0x8000 mem=512M@0xA000   fixrtc 
quiet splash -- boot=casper only-ubiquity nocompcache
  LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Beta armhf+omap4 (20120925)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1056410/+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 151913] Re: Mixer channels missing Sigmatel ID 7691 - HDA Intel

[Launchpad Bug Tracker]

[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Mixer channels missing Sigmatel ID 7691 - HDA Intel

Status in alsa-driver package in Ubuntu:
  Expired
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  alsamixer only shows "Master"  "PCM" "Caller ID" and "Off-Hook"
  Sound is heard - volume can be controlled for PCM audio ONLY
  system beep sound cannot be controlled - it's Very loud
  no other mixer channels can be found or controlled with alsamixer

  Same problem exists with other kernel versions
  Have tried package version of ALSA 1.14 and development version of alsa 1.15

  Hardware: Toshiba Qosmio G30 Laptop
  Audio Hardware Intel ICH7 HDA Audio with Sigmatel 7691 CODEC 

  aplay --list-devices
   List of PLAYBACK Hardware Devices 
  card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: Intel [HDA Intel], device 6: Si3054 Modem [Si3054 Modem]
Subdevices: 1/1
Subdevice #0: subdevice #0

  
  lspci info
  00:1b.0 Audio device [0403]: Intel Corporation 82801G (ICH7 Family) High 
Definition Audio Controller [8086:27d8] (rev 02)
  Subsystem: Toshiba America Info Systems Unknown device [1179:0001]
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B-
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR-  4096
  [0.00]   Normal   4096 ->   229376
  [0.00]   HighMem229376 ->   262000
  [0.00] early_node_map[1] active PFN ranges
  [0.00] 0:0 ->   262000
  [0.00] On node 0 totalpages: 262000
  [0.00]   DMA zone: 32 pages used for memmap
  [0.00]   DMA zone: 0 pages reserved
  [0.00]   DMA zone: 4064 pages, LIFO batch:0
  [0.00]   Normal zone: 1760 pages used for memmap
  [0.00]   Normal zone: 223520 pages, LIFO batch:31
  [0.00]   HighMem zone: 254 pages used for memmap
  [0.00]   HighMem zone: 32370 pages, LIFO batch:7
  [0.00] DMI 2.4 present.
  [0.00] ACPI: RSDP signature @ 0xC00F01B0 checksum 0
  [0.00] ACPI: RSDP 000F01B0, 0014 (r0 TOSHIB)
  [0.00] ACPI: RSDT 3FF7, 0054 (r1 TOSHIB A003720060901 TASM  
401)
  [0.00] ACPI: FACP 3FF7007C, 0084 (r2 TOSHIB A003720021230 TASM  
401)
  [0.00] ACPI: DSDT 3FF70100, 5E6D (r2 TOSHIB A003720070222 MSFT  
10E)
  [0.00] ACPI: FACS 000EEE00, 0040
  [0.00] ACPI: SSDT 3FF75F6D, 0306 (r2 TOSHIB A003720060907 MSFT  
10E)
  [0.00] ACPI: DBGP 3FF76A84, 0034 (r1 TOSHIB A003720060901 TASM  
401)
  [0.00] ACPI: BOOT 3FF70054, 0028 (r1 TOSHIB A003720060901 TASM  
401)
  [0.00] ACPI: APIC 3FF769E0, 0068 (r1 TOSHIB A003720060901 TASM  
401)
  [0.00] ACPI: MCFG 3FF76A48, 003C (r1 TOSHIB A003720060901 TASM  
401)
  [0.00] ACPI: HPET 3FF76C86, 0038 (r1 TOSHIB A003720060901 TASM  
401)
  [0.00] ACPI: SLIC 3FF76CBE, 0176 (r1 TOSHIB A003720060901 TASM  
401)
  [0.00] ACPI: FROS 3FF76AB8, 006E (r1 TOSHIB A003720060901 TASM  
401)
  [0.00] ACPI: SSDT 3FF76E34, 05E1 (r2 TOSHIB A003720060908 MSFT  
10E)
  [0.00] ACPI: SSDT 3FF76BD6, 00B0 (r2 TOSHIB A003720060908 MSFT  
10E)
  [0.00] ACPI: SSDT 3FF77F58, 0076 (r2 TOSHIB A003720060928 MSFT  
10E)
  [0.00] ACPI: PM-Timer IO Port: 0xd808
  [0.00] ACPI: Local APIC address 0xfee0
  [0.00] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
  [0.00] Processor #0 6:14 APIC version 20
  [0.00] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
  [0.00] Processor #1 6:14 APIC version 20
  [0.00] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
  [0.00] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
  [0.00] ACPI: IOAPIC (id[0x01] address[0xfec0] gsi_base[0])
  [0.00] IOAPIC[0]: apic_id 1, version 32, address 0xfec0, GSI 0-23
  [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
  [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
  [0.00] ACPI: IRQ0 used by override.
  [0.00] ACPI: IRQ2 used by override.
  [0.00] ACPI: IRQ9 used by override.
  [0.00] Enabling APIC mode:  Flat.  Using 1 I/O APICs
  [0.00] ACPI: HPET id: 0x8086a201 base: 0xfed0
  [0.00] Using ACPI (MADT) for SMP configuration information
  [0.00] Allocating PCI resources starting at 5000 (gap: 
4000:bec0)
  [0.00] Built 1 zonelists. 

[Kernel-packages] [Bug 1875577] Re: Encrypted swap won't load on 20.04 with zfs root

[Ubuntu Foundations Team Bug Bot]

The attachment "2150-fix-systemd-dependency-loops.patch" seems to be a
patch.  If it isn't, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Encrypted swap won't load on 20.04 with zfs root

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  root@eu1:/var/log# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  Codename: focal

  root@eu1:/var/log# apt-cache policy cryptsetup
  cryptsetup:
Installed: (none)
Candidate: 2:2.2.2-3ubuntu2
Version table:
   2:2.2.2-3ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  OTHER BACKGROUND INFO:
  ==

  1. machine has 2 drives. each drive is partitioned into 2 partitions,
  zfs and swap

  
  2. Ubuntu 20.04 installed on ZFS root using debootstrap 
(debootstrap_1.0.118ubuntu1_all)

  
  3. The ZFS root pool is a 2 partition mirror (the first partition of each 
disk)

  
  4. /etc/crypttab is set up as follows:

  swap  
/dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802914-part2
/dev/urandom   swap,cipher=aes-xts-plain64,size=256
  swap  
/dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802933-part2
/dev/urandom   swap,cipher=aes-xts-plain64,size=256


  
  WHAT I EXPECTED
  ===

  I expected machine would reboot and have encrypted swap that used two
  devices under /dev/mapper


  WHAT HAPPENED INSTEAD
  =

  
  On reboot, swap setup fails with the following messages in /var/log/syslog:

  Apr 28 17:13:01 eu1 kernel: [5.360793] systemd[1]: cryptsetup.target: 
Found ordering cycle on systemd-cryptsetup@swap.service/start
  Apr 28 17:13:01 eu1 kernel: [5.360795] systemd[1]: cryptsetup.target: 
Found dependency on systemd-random-seed.service/start
  Apr 28 17:13:01 eu1 kernel: [5.360796] systemd[1]: cryptsetup.target: 
Found dependency on zfs-mount.service/start
  Apr 28 17:13:01 eu1 kernel: [5.360797] systemd[1]: cryptsetup.target: 
Found dependency on zfs-load-module.service/start
  Apr 28 17:13:01 eu1 kernel: [5.360798] systemd[1]: cryptsetup.target: 
Found dependency on cryptsetup.target/start
  Apr 28 17:13:01 eu1 kernel: [5.360799] systemd[1]: cryptsetup.target: Job 
systemd-cryptsetup@swap.service/start deleted to break ordering cycle starting 
with cryptsetup.target/start
  . . . . . .
  Apr 28 17:13:01 eu1 kernel: [5.361082] systemd[1]: Unnecessary job for 
/dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802914-part2 was removed

  
  Also, /dev/mapper does not contain any swap devices:

  root@eu1:/var/log# ls -l /dev/mapper
  total 0
  crw--- 1 root root 10, 236 Apr 28 17:13 control
  root@eu1:/var/log#

  
  And top shows no swap:

  MiB Swap:  0.0 total,  0.0 free,  0.0 used.  63153.6 avail
  Mem

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

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

** Tags added: focal

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

Title:
  HP-Spectre 2019 Intel wireless driver is detected incorrectly.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Output of lsb_release -rd,
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  Issue:
  I have Intel AX-201 for wireless but when i do "lspci -k", the driver is 
detected as "Intel-9462". When i did "journalctl -k | grep iwlwifi", it shows 
that the wireless driver detected is "Intel AX-201".

  Output of lspci -k,
  00:14.3 Network controller: Intel Corporation Wireless-AC 9462
   Subsystem: Intel Corporation Wireless-AC 9462
   Kernel driver in use: iwlwifi
   Kernel modules: iwlwifi

  Output of journalctl -k | grep iwlwifi,
  May 04 23:20:12 kernel: iwlwifi :00:14.3: enabling device ( -> 0002)
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-QuZ-a0-hr-b0-50.ucode failed with error -2
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-QuZ-a0-hr-b0-49.ucode failed with error -2
  May 04 23:20:12 kernel: iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ 
Version: 43.2.23.17
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug destination: 
EXTERNAL_DRAM
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug configuration: 0
  May 04 23:20:12 kernel: iwlwifi :00:14.3: loaded firmware version 
48.4fa0041f.0 op_mode iwlmvm
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6 AX201 
160MHz, REV=0x354
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Applying debug destination 
EXTERNAL_DRAM
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Allocated 0x0040 bytes for 
firmware monitor.
  May 04 23:20:12 kernel: iwlwifi :00:14.3: base HW address: 
7c:b2:7d:d0:d5:95
  May 04 23:20:12 kernel: iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0
  May 04 23:20:13 kernel: iwlwifi :00:14.3: Applying debug destination 
EXTERNAL_DRAM
  May 04 23:20:13 kernel: iwlwifi :00:14.3: FW already configured (0) - 
re-configuring

  In the additional drivers module, it shows that module Intel-9462 no
  longer works. My bluetooth is also not detected and doesn't work.

  I came across this but no else responded yet. So decided to report a bug here.
  
https://askubuntu.com/questions/1232224/intel-ax201-detected-as-ac9462-wifi-connectivity-problems

  Please let me know if any more information is required.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876847/+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 1876847] Re: HP-Spectre 2019 Intel wireless driver is detected incorrectly.

[Srikar Thottempudi]

** Attachment added: "wireless.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876847/+attachment/5366550/+files/wireless.png

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

Title:
  HP-Spectre 2019 Intel wireless driver is detected incorrectly.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Output of lsb_release -rd,
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  Issue:
  I have Intel AX-201 for wireless but when i do "lspci -k", the driver is 
detected as "Intel-9462". When i did "journalctl -k | grep iwlwifi", it shows 
that the wireless driver detected is "Intel AX-201".

  Output of lspci -k,
  00:14.3 Network controller: Intel Corporation Wireless-AC 9462
   Subsystem: Intel Corporation Wireless-AC 9462
   Kernel driver in use: iwlwifi
   Kernel modules: iwlwifi

  Output of journalctl -k | grep iwlwifi,
  May 04 23:20:12 kernel: iwlwifi :00:14.3: enabling device ( -> 0002)
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-QuZ-a0-hr-b0-50.ucode failed with error -2
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-QuZ-a0-hr-b0-49.ucode failed with error -2
  May 04 23:20:12 kernel: iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ 
Version: 43.2.23.17
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug destination: 
EXTERNAL_DRAM
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug configuration: 0
  May 04 23:20:12 kernel: iwlwifi :00:14.3: loaded firmware version 
48.4fa0041f.0 op_mode iwlmvm
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6 AX201 
160MHz, REV=0x354
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Applying debug destination 
EXTERNAL_DRAM
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Allocated 0x0040 bytes for 
firmware monitor.
  May 04 23:20:12 kernel: iwlwifi :00:14.3: base HW address: 
7c:b2:7d:d0:d5:95
  May 04 23:20:12 kernel: iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0
  May 04 23:20:13 kernel: iwlwifi :00:14.3: Applying debug destination 
EXTERNAL_DRAM
  May 04 23:20:13 kernel: iwlwifi :00:14.3: FW already configured (0) - 
re-configuring

  In the additional drivers module, it shows that module Intel-9462 no
  longer works. My bluetooth is also not detected and doesn't work.

  I came across this but no else responded yet. So decided to report a bug here.
  
https://askubuntu.com/questions/1232224/intel-ax201-detected-as-ac9462-wifi-connectivity-problems

  Please let me know if any more information is required.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876847/+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 1876847] [NEW] HP-Spectre 2019 Intel wireless driver is detected incorrectly.

[Srikar Thottempudi]

Public bug reported:

Output of lsb_release -rd,
Description:Ubuntu 20.04 LTS
Release:20.04

Issue:
I have Intel AX-201 for wireless but when i do "lspci -k", the driver is 
detected as "Intel-9462". When i did "journalctl -k | grep iwlwifi", it shows 
that the wireless driver detected is "Intel AX-201".

Output of lspci -k,
00:14.3 Network controller: Intel Corporation Wireless-AC 9462
 Subsystem: Intel Corporation Wireless-AC 9462
 Kernel driver in use: iwlwifi
 Kernel modules: iwlwifi

Output of journalctl -k | grep iwlwifi,
May 04 23:20:12 kernel: iwlwifi :00:14.3: enabling device ( -> 0002)
May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-QuZ-a0-hr-b0-50.ucode failed with error -2
May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-QuZ-a0-hr-b0-49.ucode failed with error -2
May 04 23:20:12 kernel: iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ 
Version: 43.2.23.17
May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug destination: 
EXTERNAL_DRAM
May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug configuration: 0
May 04 23:20:12 kernel: iwlwifi :00:14.3: loaded firmware version 
48.4fa0041f.0 op_mode iwlmvm
May 04 23:20:12 kernel: iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6 AX201 
160MHz, REV=0x354
May 04 23:20:12 kernel: iwlwifi :00:14.3: Applying debug destination 
EXTERNAL_DRAM
May 04 23:20:12 kernel: iwlwifi :00:14.3: Allocated 0x0040 bytes for 
firmware monitor.
May 04 23:20:12 kernel: iwlwifi :00:14.3: base HW address: 7c:b2:7d:d0:d5:95
May 04 23:20:12 kernel: iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0
May 04 23:20:13 kernel: iwlwifi :00:14.3: Applying debug destination 
EXTERNAL_DRAM
May 04 23:20:13 kernel: iwlwifi :00:14.3: FW already configured (0) - 
re-configuring

In the additional drivers module, it shows that module Intel-9462 no
longer works. My bluetooth is also not detected and doesn't work.

I came across this but no else responded yet. So decided to report a bug here.
https://askubuntu.com/questions/1232224/intel-ax201-detected-as-ac9462-wifi-connectivity-problems

Please let me know if any more information is required.

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


** Tags: focal

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/bugs/1876847/+attachment/5366548/+files/lspci-vnvn.log

** Description changed:

  Output of lsb_release -rd,
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  
  Issue:
  I have Intel AX-201 for wireless but when i do "lspci -k", the driver is 
detected as "Intel-9462". When i did "journalctl -k | grep iwlwifi", it shows 
that the wireless driver detected is "Intel AX-201".
  
  Output of lspci -k,
  00:14.3 Network controller: Intel Corporation Wireless-AC 9462
-   Subsystem: Intel Corporation Wireless-AC 9462
-   Kernel driver in use: iwlwifi
-   Kernel modules: iwlwifi
+  Subsystem: Intel Corporation Wireless-AC 9462
+  Kernel driver in use: iwlwifi
+  Kernel modules: iwlwifi
  
  Output of journalctl -k | grep iwlwifi,
  May 04 23:20:12 Thottempudi kernel: iwlwifi :00:14.3: enabling device 
( -> 0002)
  May 04 23:20:12 Thottempudi kernel: iwlwifi :00:14.3: Direct firmware 
load for iwlwifi-QuZ-a0-hr-b0-50.ucode failed with error -2
  May 04 23:20:12 Thottempudi kernel: iwlwifi :00:14.3: Direct firmware 
load for iwlwifi-QuZ-a0-hr-b0-49.ucode failed with error -2
  May 04 23:20:12 Thottempudi kernel: iwlwifi :00:14.3: 
TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug destination: 
EXTERNAL_DRAM
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug configuration: 0
  May 04 23:20:12 kernel: iwlwifi :00:14.3: loaded firmware version 
48.4fa0041f.0 op_mode iwlmvm
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6 AX201 
160MHz, REV=0x354
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Applying debug destination 
EXTERNAL_DRAM
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Allocated 0x0040 bytes for 
firmware monitor.
  May 04 23:20:12 kernel: iwlwifi :00:14.3: base HW address: 
7c:b2:7d:d0:d5:95
  May 04 23:20:12 kernel: iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0
  May 04 23:20:13 kernel: iwlwifi :00:14.3: Applying debug destination 
EXTERNAL_DRAM
  May 04 23:20:13 kernel: iwlwifi :00:14.3: FW already configured (0) - 
re-configuring
  
  In the additional drivers module, it shows that module Intel-9462 no
  longer works. My bluetooth is also not detected and doesn't work.

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

Title:
  HP-Spectre 2019 Intel wireless driver is detected incorrectly.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Output of lsb_release -rd,
  Description:  Ubunt

[Kernel-packages] [Bug 1876847] Re: Intel wireless driver is detected incorrectly.

[Srikar Thottempudi]

** Attachment added: "version.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876847/+attachment/5366549/+files/version.log

** Description changed:

  Output of lsb_release -rd,
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  
  Issue:
  I have Intel AX-201 for wireless but when i do "lspci -k", the driver is 
detected as "Intel-9462". When i did "journalctl -k | grep iwlwifi", it shows 
that the wireless driver detected is "Intel AX-201".
  
  Output of lspci -k,
  00:14.3 Network controller: Intel Corporation Wireless-AC 9462
   Subsystem: Intel Corporation Wireless-AC 9462
   Kernel driver in use: iwlwifi
   Kernel modules: iwlwifi
  
  Output of journalctl -k | grep iwlwifi,
- May 04 23:20:12 Thottempudi kernel: iwlwifi :00:14.3: enabling device 
( -> 0002)
- May 04 23:20:12 Thottempudi kernel: iwlwifi :00:14.3: Direct firmware 
load for iwlwifi-QuZ-a0-hr-b0-50.ucode failed with error -2
- May 04 23:20:12 Thottempudi kernel: iwlwifi :00:14.3: Direct firmware 
load for iwlwifi-QuZ-a0-hr-b0-49.ucode failed with error -2
- May 04 23:20:12 Thottempudi kernel: iwlwifi :00:14.3: 
TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17
+ May 04 23:20:12 kernel: iwlwifi :00:14.3: enabling device ( -> 0002)
+ May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-QuZ-a0-hr-b0-50.ucode failed with error -2
+ May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-QuZ-a0-hr-b0-49.ucode failed with error -2
+ May 04 23:20:12 kernel: iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ 
Version: 43.2.23.17
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug destination: 
EXTERNAL_DRAM
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug configuration: 0
  May 04 23:20:12 kernel: iwlwifi :00:14.3: loaded firmware version 
48.4fa0041f.0 op_mode iwlmvm
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6 AX201 
160MHz, REV=0x354
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Applying debug destination 
EXTERNAL_DRAM
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Allocated 0x0040 bytes for 
firmware monitor.
  May 04 23:20:12 kernel: iwlwifi :00:14.3: base HW address: 
7c:b2:7d:d0:d5:95
  May 04 23:20:12 kernel: iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0
  May 04 23:20:13 kernel: iwlwifi :00:14.3: Applying debug destination 
EXTERNAL_DRAM
  May 04 23:20:13 kernel: iwlwifi :00:14.3: FW already configured (0) - 
re-configuring
  
  In the additional drivers module, it shows that module Intel-9462 no
  longer works. My bluetooth is also not detected and doesn't work.

** Description changed:

  Output of lsb_release -rd,
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  
  Issue:
  I have Intel AX-201 for wireless but when i do "lspci -k", the driver is 
detected as "Intel-9462". When i did "journalctl -k | grep iwlwifi", it shows 
that the wireless driver detected is "Intel AX-201".
  
  Output of lspci -k,
  00:14.3 Network controller: Intel Corporation Wireless-AC 9462
   Subsystem: Intel Corporation Wireless-AC 9462
   Kernel driver in use: iwlwifi
   Kernel modules: iwlwifi
  
  Output of journalctl -k | grep iwlwifi,
  May 04 23:20:12 kernel: iwlwifi :00:14.3: enabling device ( -> 0002)
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-QuZ-a0-hr-b0-50.ucode failed with error -2
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-QuZ-a0-hr-b0-49.ucode failed with error -2
  May 04 23:20:12 kernel: iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ 
Version: 43.2.23.17
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug destination: 
EXTERNAL_DRAM
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug configuration: 0
  May 04 23:20:12 kernel: iwlwifi :00:14.3: loaded firmware version 
48.4fa0041f.0 op_mode iwlmvm
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6 AX201 
160MHz, REV=0x354
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Applying debug destination 
EXTERNAL_DRAM
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Allocated 0x0040 bytes for 
firmware monitor.
  May 04 23:20:12 kernel: iwlwifi :00:14.3: base HW address: 
7c:b2:7d:d0:d5:95
  May 04 23:20:12 kernel: iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0
  May 04 23:20:13 kernel: iwlwifi :00:14.3: Applying debug destination 
EXTERNAL_DRAM
  May 04 23:20:13 kernel: iwlwifi :00:14.3: FW already configured (0) - 
re-configuring
  
  In the additional drivers module, it shows that module Intel-9462 no
  longer works. My bluetooth is also not detected and doesn't work.
+ 
+ Found someone else having the same problem,
+ 
https://askubuntu.com/questions/1232224/intel-ax201-detected-as-ac9462-wifi-connectivity-problems

** Description changed:

  Output of lsb_release -rd,
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  
  Issue:
  I have Intel AX-201 for wireless but wh

[Kernel-packages] [Bug 1876022] Re: Wireless adapter not detected (WiFi) Acer One S1003

[You-Sheng Yang]

** Tags added: hwe-networking-wifi

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

Title:
  Wireless adapter not detected (WiFi)  Acer One S1003

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This tablet was running Windows when I first bought it.

  Known problem under windows : the wireless connection would fail after
  device wake up from suspend. It could still see and detect networks
  tho

  I was interested into having a Linux tablet so I installed Ubuntu
  2020.04 on it. Since my bios wouldn't accept 64 efi boot files, I had
  to use bootia32.efi. It failed many times on creating a boot partition
  until I connected it to the internet using a wired connection. Please
  note that while windows was still present on the disk, I could still
  use the WLAN under live linux. It's only when I had it completely
  erased Windows 10 that it stopped being detected by Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 30 05:27:54 2020
  InstallationDate: Installed on 2020-04-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876022/+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 1808418] Re: Thinkpad T430u won't boot without noapic workaround

[Kai-Heng Feng]

One possible choice is to use the 5.7 kernel here:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap

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

Title:
  Thinkpad T430u won't boot without noapic workaround

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

Bug description:
  I've used Ubuntu on this specific machine for years without problems,
  but starting with the 4.13 kernel that came with the 17.10 HWE and
  continuing into 18.04 kernels my computer would no longer boot,
  hanging at various screens:

  - A blank screen with a flashing cursor
  - A screen with this message:
  Loading Linux 4.13.0.36-generic ...
  Loading initial ramdisk ...
  - A screen with kernel messages, ending in:
  APCI: EC: interrupt blocked

  I've encountered the bug in a number of kernels, including:
  - 4.13.0-32
  - 4.13.0-36
  - 4.13.0-37
  - 4.15.0-24
  - 4.15.0-34
  - 4.15.0-36
  - 4.15.0-38
  - 4.15.0-42
  - 4.20.0-rc7

  I was able to work around the issue by adding noapic to
  GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"

  I'm not entirely sure of the consequences of this workaround, but one
  thing I've noticed is significantly reduced battery life.

  This bug seems very similar to what's described here for the Thinkpad
  E485/E585: https://evilazrael.de/node/401

  I'll attach screenshots of various times I've encountered this bug
  over the last year.

  $ lsb_release -rd
  Description:Ubuntu 18.04.1 LTS
  Release:18.04

  $ apt-cache policy linux-image-4.15.0-42-generic
  linux-image-4.15.0-42-generic:
    Installed: 4.15.0-42.45
    Candidate: 4.15.0-42.45
    Version table:
   *** 4.15.0-42.45 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-42-generic 4.15.0-42.45
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bryan  2349 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Dec 13 15:31:15 2018
  HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac
  InstallationDate: Installed on 2014-05-08 (1680 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 3351CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=cffbc87d-956b-4986-94df-b3b64ae5237f ro quiet splash noapic 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-07-12 (154 days ago)
  dmi.bios.date: 06/01/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H6ETA0WW (2.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3351CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH6ETA0WW(2.18):bd06/01/2018:svnLENOVO:pn3351CTO:pvrThinkPadT430u:rvnLENOVO:rn3351CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430u
  dmi.product.name: 3351CTO
  dmi.product.version: ThinkPad T430u
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808418/+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 1876844] [NEW] Speed up the process of s3 resume

[koba]

Public bug reported:

[Impact]
Process of s3 resume take 7s and it's too long which is over 5s.

[Fix]
Reference link_active_reporting field of PCI device to determine whether delay 
is taken or not.
Actual delay would be determined by taking maximum between 100ms and pci 
device's d3cold delay. 

[test]
With the patch, the total time s3 resume is 3874.298 ms which is smaller than 
5s.

[Regression Potential]
Low. This patch only changes the rules to determine whether delay is taken or 
not.
Reference the right field(link_active_reporting), but not speed of pci device.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: In Progress

** Affects: linux-oem-osp1 (Ubuntu)
 Importance: Undecided
 Assignee: koba (kobako)
 Status: In Progress

** Changed in: linux (Ubuntu)
   Status: New => In Progress

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

** Package changed: linux-oem (Ubuntu) => linux-oem-osp1 (Ubuntu)

** Changed in: linux-oem-osp1 (Ubuntu)
   Status: New => In Progress

** Changed in: linux-oem-osp1 (Ubuntu)
 Assignee: (unassigned) => koba (kobako)

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

Title:
  Speed up the process of s3 resume

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-osp1 package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Process of s3 resume take 7s and it's too long which is over 5s.

  [Fix]
  Reference link_active_reporting field of PCI device to determine whether 
delay is taken or not.
  Actual delay would be determined by taking maximum between 100ms and pci 
device's d3cold delay. 

  [test]
  With the patch, the total time s3 resume is 3874.298 ms which is smaller than 
5s.

  [Regression Potential]
  Low. This patch only changes the rules to determine whether delay is taken or 
not.
  Reference the right field(link_active_reporting), but not speed of pci device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876844/+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 1876645] Re: Unable to handle kernel pointer dereference in virtual kernel address space on Eoan

[Po-Hsu Lin]

** Tags added: regression-proposed

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

Title:
  Unable to handle kernel pointer dereference in virtual kernel address
  space on Eoan

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Issue spotted on Eoan zVM / LPAR
  It looks like this happens when running the ubunut_fan_smoke_test (jenkins 
job hang with this one)

  [ 1225.137764] docker0: port 1(veth2fda0c6) entered blocking state
  [ 1225.137767] docker0: port 1(veth2fda0c6) entered disabled state
  [ 1225.138023] device veth2fda0c6 entered promiscuous mode
  [ 1225.148523] Unable to handle kernel pointer dereference in virtual kernel 
address space
  [ 1225.148529] Failing address: 6f766c5f646f5000 TEID: 6f766c5f646f5803
  [ 1225.148531] Fault in home space mode while using kernel ASCE.
  [ 1225.148533] AS:00070d94c007 R3:0024
  [ 1225.148575] Oops: 0038 ilc:3 [#1] SMP
  [ 1225.148578] Modules linked in: veth xt_nat vxlan ip6_udp_tunnel udp_tunnel 
nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter unix_diag 
sctp cuse vhost_net tap vhost_vsock vmw_vsock_virtio_transport_common vhost 
vsock dccp_ipv4 dccp algif_rng aegis128 aegis128l aegis256 morus1280 morus640 
algif_aead anubis fcrypt khazad seed sm4_generic tea md4 michael_mic nhpoly1305 
poly1305_generic rmd128 rmd160 rmd256 rmd320 sha3_generic sm3_generic 
streebog_generic tgr192 wp512 xxhash_generic algif_hash blowfish_generic 
blowfish_common cast5_generic salsa20_generic chacha_generic camellia_generic 
cast6_generic cast_common serpent_generic twofish_generic twofish_common 
algif_skcipher af_alg xt_conntrack ipt_REJECT nf_reject_ipv4 ip6table_mangle 
ip6table_nat nf_tables nfnetlink ip6table_filter ip6_tables iptable_mangle 
xt_CHECKSUM iptable_nat xt_MASQUERADE xt_tcpudp bridge iptable_filter bpfilter 
aufs overlay 8021q garp stp mrp llc openvswitch nsh nf_conncount nf_nat 
nf_conntrack
  [ 1225.148622]  nf_defrag_ipv6 nf_defrag_ipv4 binfmt_misc zfs(PO) 
zunicode(PO) zavl(PO) icp(PO) zlua(PO) zcommon(PO) znvpair(PO) spl(O) 
genwqe_card crc_itu_t chsc_sch eadm_sch ctcm fsm vfio_ccw vfio_mdev mdev 
vfio_iommu_type1 vfio sch_fq_codel nfsd auth_rpcgss nfs_acl lockd grace sunrpc 
ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 linear dm_service_time mlx4_ib ib_uverbs mlx4_en ptp 
ib_core pps_core pkey zcrypt crc32_vx_s390 ghash_s390 prng aes_s390 des_s390 
qeth_l2 des_generic sha512_s390 sha256_s390 sha1_s390 sha_common mlx4_core zfcp 
scsi_transport_fc qeth qdio ccwgroup dasd_eckd_mod dasd_mod scsi_dh_emc 
scsi_dh_rdac scsi_dh_alua dm_multipath
  [ 1225.148711] CPU: 4 PID: 161930 Comm: dockerd Tainted: P   O  
5.3.0-52-generic #46-Ubuntu
  [ 1225.148714] Hardware name: IBM 2964 N63 400 (LPAR)
  [ 1225.148716] Krnl PSW : 0704d0018000 03ff808e972a 
(ovl_open_realfile+0x4a/0x148 [overlay])
  [ 1225.148734]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 
RI:0 EA:3
  [ 1225.148736] Krnl GPRS: 0064 6f766c5f646f5f6d 0007a14ac300 
0003a5df6600
  [ 1225.148738]8000 0001 0003 
000372e45278
  [ 1225.148740]03ff808ea508 000304048000 0005c7f32b68 
00064a2ab900
  [ 1225.148742]0003a5df6600 03ff808f31d8 03ff808e971a 
03e009c0faf8
  [ 1225.148749] Krnl Code: 03ff808e971a: a59a0404  oilh%r9,1028
    03ff808e971e: e310f0c4  lg  
%r1,192(%r15)
   #03ff808e9724: e31010680004  lg  
%r1,104(%r1)
   >03ff808e972a: e3101064  lg  
%r1,96(%r1)
    03ff808e9730: b9040082  lgr %r8,%r2
    03ff808e9734: c21c6a656a62  cgfi
%r1,1785031266
    03ff808e973a: b9140039  lgfr%r3,%r9
    03ff808e973e: e3100344  lg  %r1,832
  [ 1225.148766] Call Trace:
  [ 1225.148769] ([<>] 0x0)
  [ 1225.148774]  [<03ff808ea582>] ovl_open+0x7a/0xc0 [overlay]
  [ 1225.148780]  [<00070cbf2c04>] do_dentry_open+0x1fc/0x3b0
  [ 1225.148784]  [<00070cc0afd2>] do_last+0x1ba/0x970
  [ 1225.148786]  [<00070cc0b80e>] path_openat+0x86/0x2b8
  [ 1225.148788]  [<00070cc0cea4>] do_filp_open+0x7c/0xf8
  [ 1225.148791]  [<00070cbf4b5a>] do_sys_open+0x19a/0x2c8
  [ 1225.148798]  [<00070d1ebca8>] system_call+0xdc/0x2c8
  [ 1225.148800] Last Breaking-Event-Address:
  [ 1225.148802]  [<00070d1ed210>] __s390_indirect_jump_r14+0x0/0xc
  [ 1225.148805] ---[ end trace dc1913214325ab11 ]---

  ProblemType: Bug
  DistroReleas

[Kernel-packages] [Bug 1672819] Re: exec'ing a setuid binary from a threaded program sometimes fails to setuid

[Vasily Averin]

Guys,
your commit d6572202d986 ("UBUNTU:SAUCE: exec: ensure file system accounting in 
check_unsafe_exec is correct") looks wrong for me,
it leads to endless cycle in check_unsafe_exec().

fs/exec.c:: check_unsafe_exec()
...
recheck:
fs_recheck = false;
t = p;
n_fs = 1;
spin_lock(&p->fs->lock);
rcu_read_lock();
while_each_thread(p, t) {
if (t->fs == p->fs)
n_fs++;
if (t->flags & (PF_EXITING | PF_FORKNOEXEC))
fs_recheck  = true;
}
rcu_read_unlock();
 
if (p->fs->users > n_fs) {
if (fs_recheck) {
spin_unlock(&p->fs->lock);
goto recheck; << cycles forever
}
bprm->unsafe |= LSM_UNSAFE_SHARE;
} else
p->fs->in_exec = 1;
spin_unlock(&p->fs->lock);

We have few Soft lockups inside VMs with ubuntu 16.04, where process was 
cyceled here.
Should I submit you separate bug for this problem?

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

Title:
  exec'ing a setuid binary from a threaded program sometimes fails to
  setuid

Status in Linux:
  Unknown
Status in golang-1.6 package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in golang-1.6 source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in golang-1.6 source package in Yakkety:
  Invalid
Status in linux source package in Yakkety:
  Fix Released
Status in golang-1.6 source package in Zesty:
  Invalid
Status in linux source package in Zesty:
  Fix Released

Bug description:
  == SRU template for golang-1.6 ==

  [Impact]
  The kernel bug reported below means that occasionally (maybe 1 in 1000 times) 
the snapd -> snap-confine exec that is part of a snap execution fails to take 
the setuid bit on the snap-confine binary into account which means that the 
execution fails. This is extremely confusing for the user of the snap who just 
sees a permission denied error with no explanation.

  The kernel bug has been fixed in Xenial+ but not all users of snapd are on 
xenial+ kernels (they might be on trusty or another distribution entirely).
  Backporting this fix will mean that the snapd in the core snap will get the 
workaround next time it is built and because the snapd in trusty or the other 
distro will re-exec into the snapd in the core snap before execing 
snap-confine, users should not see the above behaviour.

  [Test case]
  This will be a bit tricky as the kernel bug has been fixed. A xenial 
container on a trusty host/VM should do the trick. The test case from 
https://gist.github.com/chipaca/806c90d96c437444f27f45a83d00a813 should be 
sufficient to demonstrate the bug and then, once golang-1.6 has been upgraded 
from proposed, the fix.

  [Regression potential]
  If there is a bug in the patch it could cause deadlocks in currently working 
programs. But the patch is pretty simple and has passed review upstream so I 
think it should be OK.

  == SRU REQUEST XENIAL, YAKKETY, ZESTY ==

  Due to two race conditions in check_unsafe_exec(),  exec'ing a setuid
  binary from a threaded program sometimes fails to setuid.

  == Fix ==

  Sauce patch for Xenial, Yakkety + Zesty:

  https://lists.ubuntu.com/archives/kernel-team/2017-May/084102.html

  This fix re-executes the unsafe check if there is a discrepancy
  between the expected fs count and the found count during the racy
  window during thread exec or exit.  This re-check occurs very
  infrequently and saves a lot of addition locking on per thread
  structures that would make performance of fork/exec/exit prohibitively
  expensive.

  == Test case ==

  See the example C code in the patch, https://lists.ubuntu.com/archives
  /kernel-team/2017-May/084102.html

  Run the test code as follows: for i in $(seq 1000); do ./a; done

  With the patch, no messages are emitted, without the patch, one sees a
  message:

  "Failed, got euid 1000 (expecting 0)"

  ..which shows the setuid program failed the check_unsafe_exec()
  because of the race.

  == Regression potential ==

  breaking existing safe exec semantics.

  

  This can be reproduced with
  https://gist.github.com/chipaca/806c90d96c437444f27f45a83d00a813

  With that, and go 1.8, if you run “make” and then

  for i in `seq 99`; do ./a_go; done

  you'll see a variable number of ”GOT 1000” (or whatever your user id
  is). If you don't, add one or two more 9s on there.

  That's a simple go reproducer. You can also use “a_p” instead of
  “a_go” to see one that only uses pthreads. “a_c” is a C version that
  does *not* reproduce the issue.

  But it's not pthreads: if in a_go.go you comment out the “import "C"”,
  you'll still see the “GOT 1000” messages, in a static bi

[Kernel-packages] [Bug 1870189] Re: initramfs does not get loaded

[Dexuan Cui]

Today I just repeated the test "Create a Gen-1 Ubuntu 19.10 VM on Azure,
and upgrade it to Ubuntu 20.04 by “do-release-upgrade –d" and I
reproduced this bug again, and the grub version is also 2.04-1ubuntu26!

So I suspect grub itself should be good, but some grub config file (i.e. 
/etc/grub.d/10_linux?) causes the bug? 
I checked my /etc/grub.d/10_linux: after I added line 263, "grub-mkconfig" can 
generate the needed initrd line correctly:

257 fi
258
259 sed "s/^/$submenu_indentation/" << EOF
260   initrd${rel_dirname}/${initrd}
261 else
262   linux ${rel_dirname}/${basename} 
root=${linux_root_device_thisversion} ro ${args} panic=-1
263   initrd${rel_dirname}/${initrd}
264 fi
265 initrdfail
266 EOF

My /etc/grub.d/10_linux is from the grub2-common package
(2.04-1ubuntu26). It looks this file in my VM that's upgraded from 19.10
to 20.04 is different from the version of the file in a VM that's
created from   https://releases.ubuntu.com/20.04/ubuntu-20.04-live-
server-amd64.iso

That's why I suspected it is specific to the cloud-image version of
Ubuntu 20.04. I don't know how exactly “do-release-upgrade -d" works and
where the upgrade procedure pulls the grub2 that lacks the initrd line
in the /etc/grub.d/10_linux.


In summary, 
1. 
https://cloud-images.ubuntu.com/focal/20200430.1/focal-server-cloudimg-amd64.img
 and 
https://cloud-images.ubuntu.com/focal/20200430.1/focal-server-cloudimg-amd64-azure.vhd.zip
 have the bug.
2.  https://releases.ubuntu.com/20.04/ubuntu-20.04-live-server-amd64.iso  does 
not have the bug.
3. A quick fix is add the needed line 263 (see above), but I think we need to 
understand how the bug is introduced.

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

Title:
  initramfs does not get loaded

Status in grub2 package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
  20.04 by “do-release-upgrade –d”.

  Then the latest Ubuntu v5.6 kernel was installed from
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
  reboot was performed, a panic with the v5.6 kernel occured because the
  rootfs can not be found.

  It turns out by default, initramfs does not get loaded:

  /boot/grub/grub.cfg:
  menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os 
$menuentry_id_option 'gnulinux-simple-3d2737e8-
  b95a-42bf-bac1-bb6fb4cda87f' {
  …
  if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic 
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro  console=tty1 
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled 
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
  else
linux /boot/vmlinuz-5.6.0-050600-generic 
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro  console=tty1 
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled 
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
  fi
  initrdfail
  }

  
  As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally, 
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit 
the “fail to mount rootfs” panic and the kernel will automatically reboot….   

  Also, the “initrdfail” here marks initrdfail=1, so when the kernel
  boots for the 2nd time, the kernel should successfully boot up.  Next,
  when the kernel boots for the 3rd time, it panics again since the
  userspace program resets initrdfail to 0, and next time when the
  kernel boots, it can boot up successfully -- this
  “panic/success/panic/success” pattern repeats forever…

  
  The linux-azure kernels are not affected since they have the vmbus driver and 
storage drivers built-in (i.e. “=y”):
  /boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
  /boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
  /boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
  /boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
  /boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
  /boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
  The v5.6 kernel uses =m rather than =y, so is affected here.

  
  It looks the setting may be intentional, but we should not assume a customer 
kernel must have the necessary vmbus/storage drivers built-in. 

  This issue only happens to the Ubuntu Marketplace image (19.10 and maybe 
19.04 as well?) on Azure. 
  We installed a Ubuntu  20.04 VM from the .iso file from 
http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub 
issue.

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

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

[Kernel-packages] [Bug 1870189] Re: initramfs does not get loaded

[Dexuan Cui]

Sorry, this statement is wrong:
==
Today I also created a VM on my host from 
https://cloud-images.ubuntu.com/focal/20200430.1/focal-server-cloudimg-amd64-azure.vhd.zip
 and can not see the bug either, and the grub version is also 2.04-1ubuntu26.
==

Actually I do see the bug as well with the vhd.zip file.

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

Title:
  initramfs does not get loaded

Status in grub2 package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
  20.04 by “do-release-upgrade –d”.

  Then the latest Ubuntu v5.6 kernel was installed from
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
  reboot was performed, a panic with the v5.6 kernel occured because the
  rootfs can not be found.

  It turns out by default, initramfs does not get loaded:

  /boot/grub/grub.cfg:
  menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os 
$menuentry_id_option 'gnulinux-simple-3d2737e8-
  b95a-42bf-bac1-bb6fb4cda87f' {
  …
  if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic 
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro  console=tty1 
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled 
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
  else
linux /boot/vmlinuz-5.6.0-050600-generic 
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro  console=tty1 
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled 
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
  fi
  initrdfail
  }

  
  As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally, 
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit 
the “fail to mount rootfs” panic and the kernel will automatically reboot….   

  Also, the “initrdfail” here marks initrdfail=1, so when the kernel
  boots for the 2nd time, the kernel should successfully boot up.  Next,
  when the kernel boots for the 3rd time, it panics again since the
  userspace program resets initrdfail to 0, and next time when the
  kernel boots, it can boot up successfully -- this
  “panic/success/panic/success” pattern repeats forever…

  
  The linux-azure kernels are not affected since they have the vmbus driver and 
storage drivers built-in (i.e. “=y”):
  /boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
  /boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
  /boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
  /boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
  /boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
  /boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
  The v5.6 kernel uses =m rather than =y, so is affected here.

  
  It looks the setting may be intentional, but we should not assume a customer 
kernel must have the necessary vmbus/storage drivers built-in. 

  This issue only happens to the Ubuntu Marketplace image (19.10 and maybe 
19.04 as well?) on Azure. 
  We installed a Ubuntu  20.04 VM from the .iso file from 
http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub 
issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+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 1875577] Re: Encrypted swap won't load on 20.04 with zfs root

[Richard Laager]

This is a tricky one because all of the dependencies make sense in
isolation. Even if we remove the dependency added by that upstream
OpenZFS commit, given that modern systems use zfs-mount-generator,
systemd-random-seed.service is going to Require= and After= var-
lib.mount because of its RequiresMountsFor=/var/lib/systemd/random-seed.
The generated var-lib.mount will be After=zfs-import.target because you
can't mount a filesystem without importing the pool. And zfs-
import.target is After= the two zfs-import-* services. Those are after
cryptsetup.target, as you might be running your pool on top of LUKS.

Mostly side note: it does seem weird and unnecessary that zfs-load-
module.service has After=cryptsetup.target. We should probably remove
that. That is coming from debian/patches/2100-zfs-load-module.patch
(which is what provides zfs-load-module.service in its entirety).

One idea here would be to eliminate the After=cryptsetup.target from
zfs-import-{cache,scan}.service and require that someone add them via a
drop-in if they are running on LUKS. However, in that case, they'll run
into the same problem anyway. So that's not really a fix.

Another option might be to remove the zfs-mount.service Before=systemd-
random-seed.service and effectively require the use of the mount
generator for Root-on-ZFS setups. That is what the Ubuntu installer does
and what the Root-on-ZFS HOWTO will use for 20.04 anyway. (I'm working
on it actively right now.) Then, modify zfs-mount-generator to NOT After
=zfs-import.target (and likewise for Wants=) if the relevant pool is
already imported (and likewise for the zfs-load-key- services). Since
the rpool will already be imported by the time zfs-mount-generator runs,
that would be omitted.

I've attached an *untested* patch to that effect. I hope to test this
yet tonight as I test more Root-on-ZFS scenarios, but no promises.

** Patch added: "2150-fix-systemd-dependency-loops.patch"
   
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1875577/+attachment/5366544/+files/2150-fix-systemd-dependency-loops.patch

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

Title:
  Encrypted swap won't load on 20.04 with zfs root

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  root@eu1:/var/log# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  Codename: focal

  root@eu1:/var/log# apt-cache policy cryptsetup
  cryptsetup:
Installed: (none)
Candidate: 2:2.2.2-3ubuntu2
Version table:
   2:2.2.2-3ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  OTHER BACKGROUND INFO:
  ==

  1. machine has 2 drives. each drive is partitioned into 2 partitions,
  zfs and swap

  
  2. Ubuntu 20.04 installed on ZFS root using debootstrap 
(debootstrap_1.0.118ubuntu1_all)

  
  3. The ZFS root pool is a 2 partition mirror (the first partition of each 
disk)

  
  4. /etc/crypttab is set up as follows:

  swap  
/dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802914-part2
/dev/urandom   swap,cipher=aes-xts-plain64,size=256
  swap  
/dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802933-part2
/dev/urandom   swap,cipher=aes-xts-plain64,size=256


  
  WHAT I EXPECTED
  ===

  I expected machine would reboot and have encrypted swap that used two
  devices under /dev/mapper


  WHAT HAPPENED INSTEAD
  =

  
  On reboot, swap setup fails with the following messages in /var/log/syslog:

  Apr 28 17:13:01 eu1 kernel: [5.360793] systemd[1]: cryptsetup.target: 
Found ordering cycle on systemd-cryptsetup@swap.service/start
  Apr 28 17:13:01 eu1 kernel: [5.360795] systemd[1]: cryptsetup.target: 
Found dependency on systemd-random-seed.service/start
  Apr 28 17:13:01 eu1 kernel: [5.360796] systemd[1]: cryptsetup.target: 
Found dependency on zfs-mount.service/start
  Apr 28 17:13:01 eu1 kernel: [5.360797] systemd[1]: cryptsetup.target: 
Found dependency on zfs-load-module.service/start
  Apr 28 17:13:01 eu1 kernel: [5.360798] systemd[1]: cryptsetup.target: 
Found dependency on cryptsetup.target/start
  Apr 28 17:13:01 eu1 kernel: [5.360799] systemd[1]: cryptsetup.target: Job 
systemd-cryptsetup@swap.service/start deleted to break ordering cycle starting 
with cryptsetup.target/start
  . . . . . .
  Apr 28 17:13:01 eu1 kernel: [5.361082] systemd[1]: Unnecessary job for 
/dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802914-part2 was removed

  
  Also, /dev/mapper does not contain any swap devices:

  root@eu1:/var/log# ls -l /dev/mapper
  total 0
  crw--- 1 root root 10, 236 Apr 28 17:13 control
  root@eu1:/var/log#

  
  And top shows no swap:

  MiB Swap:  0.0 total,  0.0 free,  0.0 used.  63153.6 avai

[Kernel-packages] [Bug 1875577] Re: Encrypted swap won't load on 20.04 with zfs root

[Richard Laager]

John Gray: Everything else aside, you should mirror your swap instead of
striping it (which I think is what you're doing). With your current
setup, if a disk dies, your system will crash.

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

Title:
  Encrypted swap won't load on 20.04 with zfs root

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  root@eu1:/var/log# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  Codename: focal

  root@eu1:/var/log# apt-cache policy cryptsetup
  cryptsetup:
Installed: (none)
Candidate: 2:2.2.2-3ubuntu2
Version table:
   2:2.2.2-3ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  OTHER BACKGROUND INFO:
  ==

  1. machine has 2 drives. each drive is partitioned into 2 partitions,
  zfs and swap

  
  2. Ubuntu 20.04 installed on ZFS root using debootstrap 
(debootstrap_1.0.118ubuntu1_all)

  
  3. The ZFS root pool is a 2 partition mirror (the first partition of each 
disk)

  
  4. /etc/crypttab is set up as follows:

  swap  
/dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802914-part2
/dev/urandom   swap,cipher=aes-xts-plain64,size=256
  swap  
/dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802933-part2
/dev/urandom   swap,cipher=aes-xts-plain64,size=256


  
  WHAT I EXPECTED
  ===

  I expected machine would reboot and have encrypted swap that used two
  devices under /dev/mapper


  WHAT HAPPENED INSTEAD
  =

  
  On reboot, swap setup fails with the following messages in /var/log/syslog:

  Apr 28 17:13:01 eu1 kernel: [5.360793] systemd[1]: cryptsetup.target: 
Found ordering cycle on systemd-cryptsetup@swap.service/start
  Apr 28 17:13:01 eu1 kernel: [5.360795] systemd[1]: cryptsetup.target: 
Found dependency on systemd-random-seed.service/start
  Apr 28 17:13:01 eu1 kernel: [5.360796] systemd[1]: cryptsetup.target: 
Found dependency on zfs-mount.service/start
  Apr 28 17:13:01 eu1 kernel: [5.360797] systemd[1]: cryptsetup.target: 
Found dependency on zfs-load-module.service/start
  Apr 28 17:13:01 eu1 kernel: [5.360798] systemd[1]: cryptsetup.target: 
Found dependency on cryptsetup.target/start
  Apr 28 17:13:01 eu1 kernel: [5.360799] systemd[1]: cryptsetup.target: Job 
systemd-cryptsetup@swap.service/start deleted to break ordering cycle starting 
with cryptsetup.target/start
  . . . . . .
  Apr 28 17:13:01 eu1 kernel: [5.361082] systemd[1]: Unnecessary job for 
/dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802914-part2 was removed

  
  Also, /dev/mapper does not contain any swap devices:

  root@eu1:/var/log# ls -l /dev/mapper
  total 0
  crw--- 1 root root 10, 236 Apr 28 17:13 control
  root@eu1:/var/log#

  
  And top shows no swap:

  MiB Swap:  0.0 total,  0.0 free,  0.0 used.  63153.6 avail
  Mem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1875577/+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 1666432] Re: Internet drops every few minutes on wired and wireless connection

[You-Sheng Yang]

** Tags added: hwe-networking-ethernet hwe-networking-wifi

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

Title:
  Internet drops every few minutes on wired and wireless connection

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Internet drops every 1-30 minutes when connected via wired or wireless
  (i.e., this is a problem on both wired and wireless) even though
  connection icon indicates the computer is still connected.

  Disconnecting and reconnecting via the connection icon resets internet
  temporarily until the next time.

  Dropped internet is discovered with "The site can't be reached"
  screens in Chromium, or error messages when downloading/updating in
  Terminal, or missing connection in Ubuntu Software app, or stalled
  syncing in Insync application (occurred even without Insync).

  Internet drops more frequently on wireless than on wired.

  It seems to disconnect more frequently with heavier internet use
  (e.g., downloading multiple files, opening several webpages in quick
  succession).

  This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron
  15 5567 (dual boot). It occurs when running Live CD as well though.

  Ethernet and wifi both work without randomly disconnecting in Windows
  10 on the same machine, and ethernet and wifi work on other machines
  running Ubuntu and Windows with the same router, so it is not a
  hardware or router issue.

  Output from sudo lshw -class network

  *-network
     description: Wireless interface
     product: Wireless 3165
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:02:00.0
     logical name: wlp2s0
     version: 79
     serial: 58:fb:84:55:21:52
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 
link=yes multicast=yes wireless=IEEE 802.11abgn
     resources: irq:283 memory:df10-df101fff
    *-network
     description: Ethernet interface
     product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
     vendor: Realtek Semiconductor Co., Ltd.
     physical id: 0
     bus info: pci@:03:00.0
     logical name: enp3s0
     version: 07
     serial: 18:db:f2:3c:d5:37
     size: 10Mbit/s
     capacity: 100Mbit/s
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 
latency=0 link=no multicast=yes port=MII speed=10Mbit/s
     resources: irq:279 ioport:d000(size=256) memory:df00-df000fff 
memory:d030-d0303fff

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb 21 16:36:55 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-02-20 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0  proto static  metric 600
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000
   192.168.1.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.1.15  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/0  
pr500k-9912ec-1  36301ded-0ac5-4a86-9621-87290ef159af  
/org/freedesktop/NetworkManager/ActiveConnection/5
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
  ----
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  -- 
  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

[Kernel-packages] [Bug 1826125] Re: Dell XPS 13 9380 flickering (Whiskey Lake)

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => New

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

Title:
  Dell XPS 13 9380 flickering  (Whiskey Lake)

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

Bug description:
  A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers
  to the point of being totally unusable.

  I have upgraded since to 18.10 and 19.04 with no changes. I have tried
  several combinations of the i915 parameters fastboot, enable_rc6 and
  enable_fbc to no avail.

  Examples of flickering are here:
  https://photos.app.goo.gl/1PkL2HrjMBP41aML9
  https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1430 F pulseaudio
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X31
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-13 (10 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 9380
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem 
root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1 
i915.enable_rc6=0 vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1035-oem N/A
   linux-backports-modules-4.15.0-1035-oem  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 4.15.0-1035-oem x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1826125/+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 1857398] Re: ubiquity should support encryption by default with zfsroot, with users able to opt in to running change-key after install

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ubiquity (Ubuntu)
   Status: New => Confirmed

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

Title:
  ubiquity should support encryption by default with zfsroot, with users
  able to opt in to running change-key after install

Status in ubiquity package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  zfs supports built-in encryption support, but the decision of whether
  a pool is encrypted or not must be made at pool creation time; it is
  possible to add encrypted datasets on top of an unencrypted pool but
  it is not possible to do an online change of a dataset (or a whole
  pool) to toggle encryption.

  We should therefore always install with encryption enabled on zfs
  systems, with a non-secret key by default, and allow the user to use
  'zfs change-key -o keylocation=prompt' after install to take ownership
  of the encryption and upgrade the security.

  This is also the simplest way to allow users to avoid having to choose
  between the security of full-disk encryption, and the advanced
  filesystem features of zfs since it requires no additional UX work in
  ubiquity.

  We should make sure that
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857040 is fixed
  first in the kernel so that enabling zfs encryption does not impose an
  unreasonable performance penalty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1857398/+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 1857398] Re: ubiquity should support encryption by default with zfsroot, with users able to opt in to running change-key after install

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: zfs-linux (Ubuntu)
   Status: New => Confirmed

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

Title:
  ubiquity should support encryption by default with zfsroot, with users
  able to opt in to running change-key after install

Status in ubiquity package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  zfs supports built-in encryption support, but the decision of whether
  a pool is encrypted or not must be made at pool creation time; it is
  possible to add encrypted datasets on top of an unencrypted pool but
  it is not possible to do an online change of a dataset (or a whole
  pool) to toggle encryption.

  We should therefore always install with encryption enabled on zfs
  systems, with a non-secret key by default, and allow the user to use
  'zfs change-key -o keylocation=prompt' after install to take ownership
  of the encryption and upgrade the security.

  This is also the simplest way to allow users to avoid having to choose
  between the security of full-disk encryption, and the advanced
  filesystem features of zfs since it requires no additional UX work in
  ubiquity.

  We should make sure that
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857040 is fixed
  first in the kernel so that enabling zfs encryption does not impose an
  unreasonable performance penalty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1857398/+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 1864392] Re: WiFi not working

[You-Sheng Yang]

** Tags added: hwe-networking-wifi

** Summary changed:

- WiFi not working
+ Intel WiFi [8086:02f0] subsystem [8086:0030] not working

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

Title:
  Intel WiFi [8086:02f0] subsystem [8086:0030] not working

Status in backport-iwlwifi-dkms package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  No WiFi APs are detected.  It's like the driver doesn't recognize the
  hardware.

  I tried reinstalling it, but it didn't work.

  Please fix this ASAP.

  Operating System: Kubuntu 19.10
  KDE Plasma Version: 5.18.1
  KDE Frameworks Version: 5.67.0
  Qt Version: 5.12.4
  Kernel Version: 5.3.0-40-generic
  OS Type: 64-bit
  Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
  Memory: 15.3 GiB of RAM

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: backport-iwlwifi-dkms 7906-0ubuntu4
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Feb 23 18:43:16 2020
  InstallationDate: Installed on 2020-01-19 (35 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: backport-iwlwifi-dkms
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-19 (37 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: linux
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Tags:  eoan
  Uname: Linux 5.3.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-19 (37 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: linux
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Tags:  eoan
  Uname: Linux 5.3.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yamiyuki   2053 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-19 (50 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IwConfig:
   enp0s31f6  no wireless extensions.
   
   lono wireless extensions.
   
   enx00249b1ec202  no wireless extensions.
  MachineType: LENOVO 20SA0002US
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=8644acd5-759a-4daa-a34c-75ad3f4c5c12 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.183.4
  Tags:  eoan
  Uname: Linux 5.3.0-40-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/15/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2QET19W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SA0002US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20SA0002US:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20SA0002US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 4th
  dmi.product.name: 20SA0002US
  dmi.product.sku: LENOVO_MT_20SA_BU_Think_FM_ThinkPad X1 Yoga 4th
  dmi.product.version: ThinkPad X1 Yoga 4th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yamiyuki   2053 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-19 (50 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IwConfig:
   enp0s31f6  no wireless extensions.
   
   lono 

[Kernel-packages] [Bug 1876429] 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 1876429

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

Title:
  Dell Latitude E6400 keyboard backlight doesn't work at Ubuntu 20.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  after a fresh installation of Ubuntu 20.04, the keyboard backlight on
  the Dell Latitude E6400 laptop does not work.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876429/+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 1876815] Re: wifi issue with 5.4.0-28 lowlatency kernel

[You-Sheng Yang]

Please remove backport-iwlwifi-dkms for this adapter. You don't need it
as in tree driver has better support.

** Tags added: hwe-networking-wifi

** Also affects: backport-iwlwifi-dkms (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: linux (Ubuntu)

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

Title:
  wifi issue with 5.4.0-28 lowlatency kernel

Status in backport-iwlwifi-dkms package in Ubuntu:
  New

Bug description:
  hello,
  after fresh ubuntustudio 20.04 install, everything worked out the box
  But after 5.4.0-28 lowlatency kernel update, wifi does not work properly
  Connection to the wifi modem is ok, but network is abnormaly slow. Come bake 
to the previous kernel 5.4.0-26 fix the issue (both kernel using same 
backport-iwlwifi-dkms driver)
  Hope this will help, and the issue will be fixed in the next released, be 
safe, bye

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-lowlatency 5.4.0.28.33
  ProcVersionSignature: Ubuntu 5.4.0-28.32-lowlatency 5.4.30
  Uname: Linux 5.4.0-28-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  transistor   2177 F pulseaudio
   /dev/snd/controlC2:  transistor   2177 F pulseaudio
   /dev/snd/controlC1:  transistor   2177 F pulseaudio
   /dev/snd/controlC0:  transistor   2177 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Mon May  4 22:59:26 2020
  InstallationDate: Installed on 2020-04-27 (7 days ago)
  InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  MachineType: Micro-Star International Co., Ltd. GL75 9SE
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-lowlatency 
root=UUID=5f15-7a39-4245-8672-0f0aec9592f7 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-28-lowlatency N/A
   linux-backports-modules-5.4.0-28-lowlatency  N/A
   linux-firmware   1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/25/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17E5IMS.103
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17E5
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17E5IMS.103:bd06/25/2019:svnMicro-StarInternationalCo.,Ltd.:pnGL759SE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17E5:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: GL
  dmi.product.name: GL75 9SE
  dmi.product.sku: 17E5.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1876815/+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 1876429] Re: Dell Latitude E6400 keyboard backlight doesn't work at Ubuntu 20.04

[Brian Murray]

** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  Dell Latitude E6400 keyboard backlight doesn't work at Ubuntu 20.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  after a fresh installation of Ubuntu 20.04, the keyboard backlight on
  the Dell Latitude E6400 laptop does not work.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876429/+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 1876429] [NEW] Dell Latitude E6400 keyboard backlight doesn't work at Ubuntu 20.04

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hello,

after a fresh installation of Ubuntu 20.04, the keyboard backlight on
the Dell Latitude E6400 laptop does not work.

Thanks

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


** Tags: bot-comment
-- 
Dell Latitude E6400 keyboard backlight doesn't work at Ubuntu 20.04
https://bugs.launchpad.net/bugs/1876429
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1875916] Re: upgrading to 4.15.0-99-generic breaks the sound and the trackpad

[Hui Wang]

Usually it takes 3 weeks for each cycle.

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

Title:
  upgrading to 4.15.0-99-generic breaks the sound and the trackpad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using kubuntu LTS 18.04.
  This morning I was promped to update the kernel to the 4.15.0-99-generic. 

  After the upgrade I did not manage to get any sound. I checked
  everything, pavucontrol, alsamix, everything was in order, the streams
  showed as if they were playing, however I couldn't get any sound from
  the speakers headphones and I could not get any sound recorded either.

  I then rebooted with the previous version of the Kernel, and have my sound 
back without doing anything at all.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4a7a721a-7a2e-4644-a881-34adcb28e1ba
  InstallationDate: Installed on 2019-01-29 (455 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig:
   lono wireless extensions.
   
   wlp108s0  no wireless extensions.
  MachineType: Dell Inc. Latitude 7390 2-in-1
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic 
root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-99-generic N/A
   linux-backports-modules-4.15.0-99-generic  N/A
   linux-firmware 1.173.17
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-99-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/27/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0YNG30
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd08/27/2018:svnDellInc.:pnLatitude73902-in-1:pvr:rvnDellInc.:rn0YNG30:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7390 2-in-1
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875916/+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 1875577] Re: Encrypted swap won't load on 20.04 with zfs root

[Dan Streetman]

This isn't a systemd bug, it's a bug in zfs's zfs-mount.service, adding in this 
upstream commit:
https://github.com/openzfs/zfs/commit/8ae8b2a1445bcccee1bb8ee7d4886f30050f6f53

That orders zfs-mount.service *before* systemd-random-seed.service, while 
systemd's generator for cryptsetup orders *after* systemd-random-seed.service:
https://github.com/systemd/systemd/blob/master/src/cryptsetup/cryptsetup-generator.c#L193

zfs-mount.service is then caught in a dependency loop:
May 04 14:37:19 lp1875577-f systemd[1]: zfs-mount.service: Found ordering cycle 
on zfs-import.target/start
May 04 14:37:19 lp1875577-f systemd[1]: zfs-mount.service: Found dependency on 
zfs-import-cache.service/start
May 04 14:37:19 lp1875577-f systemd[1]: zfs-mount.service: Found dependency on 
cryptsetup.target/start
May 04 14:37:19 lp1875577-f systemd[1]: zfs-mount.service: Found dependency on 
systemd-cryptsetup@swap.service/start
May 04 14:37:19 lp1875577-f systemd[1]: zfs-mount.service: Found dependency on 
systemd-random-seed.service/start
May 04 14:37:19 lp1875577-f systemd[1]: zfs-mount.service: Found dependency on 
zfs-mount.service/start
May 04 14:37:19 lp1875577-f systemd[1]: zfs-mount.service: Job 
zfs-import.target/start deleted to break ordering cycle starting with zfs-mount>
May 04 14:37:19 lp1875577-f systemd[1]: zfs-mount.service: Found ordering cycle 
on zfs-load-module.service/start
May 04 14:37:19 lp1875577-f systemd[1]: zfs-mount.service: Found dependency on 
cryptsetup.target/start
May 04 14:37:19 lp1875577-f systemd[1]: zfs-mount.service: Found dependency on 
systemd-cryptsetup@swap.service/start
May 04 14:37:19 lp1875577-f systemd[1]: zfs-mount.service: Found dependency on 
systemd-random-seed.service/start
May 04 14:37:19 lp1875577-f systemd[1]: zfs-mount.service: Found dependency on 
zfs-mount.service/start
May 04 14:37:19 lp1875577-f systemd[1]: zfs-mount.service: Job 
zfs-load-module.service/start deleted to break ordering cycle starting with zfs>


@didrocks, I think you added the zfs change upstream, maybe it needs to be 
adjusted to handle it some other way?  In general, services shouldn't order 
themselves before systemd-random-seed without very careful consideration.

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

Title:
  Encrypted swap won't load on 20.04 with zfs root

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  root@eu1:/var/log# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  Codename: focal

  root@eu1:/var/log# apt-cache policy cryptsetup
  cryptsetup:
Installed: (none)
Candidate: 2:2.2.2-3ubuntu2
Version table:
   2:2.2.2-3ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  OTHER BACKGROUND INFO:
  ==

  1. machine has 2 drives. each drive is partitioned into 2 partitions,
  zfs and swap

  
  2. Ubuntu 20.04 installed on ZFS root using debootstrap 
(debootstrap_1.0.118ubuntu1_all)

  
  3. The ZFS root pool is a 2 partition mirror (the first partition of each 
disk)

  
  4. /etc/crypttab is set up as follows:

  swap  
/dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802914-part2
/dev/urandom   swap,cipher=aes-xts-plain64,size=256
  swap  
/dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802933-part2
/dev/urandom   swap,cipher=aes-xts-plain64,size=256


  
  WHAT I EXPECTED
  ===

  I expected machine would reboot and have encrypted swap that used two
  devices under /dev/mapper


  WHAT HAPPENED INSTEAD
  =

  
  On reboot, swap setup fails with the following messages in /var/log/syslog:

  Apr 28 17:13:01 eu1 kernel: [5.360793] systemd[1]: cryptsetup.target: 
Found ordering cycle on systemd-cryptsetup@swap.service/start
  Apr 28 17:13:01 eu1 kernel: [5.360795] systemd[1]: cryptsetup.target: 
Found dependency on systemd-random-seed.service/start
  Apr 28 17:13:01 eu1 kernel: [5.360796] systemd[1]: cryptsetup.target: 
Found dependency on zfs-mount.service/start
  Apr 28 17:13:01 eu1 kernel: [5.360797] systemd[1]: cryptsetup.target: 
Found dependency on zfs-load-module.service/start
  Apr 28 17:13:01 eu1 kernel: [5.360798] systemd[1]: cryptsetup.target: 
Found dependency on cryptsetup.target/start
  Apr 28 17:13:01 eu1 kernel: [5.360799] systemd[1]: cryptsetup.target: Job 
systemd-cryptsetup@swap.service/start deleted to break ordering cycle starting 
with cryptsetup.target/start
  . . . . . .
  Apr 28 17:13:01 eu1 kernel: [5.361082] systemd[1]: Unnecessary job for 
/dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802914-part2 was removed

  
  Also, /dev/mapper does not contain any swap devices:

  root@eu1:/var/log# ls -l /dev/mapper
  total 0
  crw--- 1 root root 10, 236 Apr 28 17:13 c

[Kernel-packages] [Bug 1875577] Re: Encrypted swap won't load on 20.04 with zfs root

[Dan Streetman]

** Package changed: systemd (Ubuntu) => zfs-linux (Ubuntu)

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

Title:
  Encrypted swap won't load on 20.04 with zfs root

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  root@eu1:/var/log# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  Codename: focal

  root@eu1:/var/log# apt-cache policy cryptsetup
  cryptsetup:
Installed: (none)
Candidate: 2:2.2.2-3ubuntu2
Version table:
   2:2.2.2-3ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  OTHER BACKGROUND INFO:
  ==

  1. machine has 2 drives. each drive is partitioned into 2 partitions,
  zfs and swap

  
  2. Ubuntu 20.04 installed on ZFS root using debootstrap 
(debootstrap_1.0.118ubuntu1_all)

  
  3. The ZFS root pool is a 2 partition mirror (the first partition of each 
disk)

  
  4. /etc/crypttab is set up as follows:

  swap  
/dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802914-part2
/dev/urandom   swap,cipher=aes-xts-plain64,size=256
  swap  
/dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802933-part2
/dev/urandom   swap,cipher=aes-xts-plain64,size=256


  
  WHAT I EXPECTED
  ===

  I expected machine would reboot and have encrypted swap that used two
  devices under /dev/mapper


  WHAT HAPPENED INSTEAD
  =

  
  On reboot, swap setup fails with the following messages in /var/log/syslog:

  Apr 28 17:13:01 eu1 kernel: [5.360793] systemd[1]: cryptsetup.target: 
Found ordering cycle on systemd-cryptsetup@swap.service/start
  Apr 28 17:13:01 eu1 kernel: [5.360795] systemd[1]: cryptsetup.target: 
Found dependency on systemd-random-seed.service/start
  Apr 28 17:13:01 eu1 kernel: [5.360796] systemd[1]: cryptsetup.target: 
Found dependency on zfs-mount.service/start
  Apr 28 17:13:01 eu1 kernel: [5.360797] systemd[1]: cryptsetup.target: 
Found dependency on zfs-load-module.service/start
  Apr 28 17:13:01 eu1 kernel: [5.360798] systemd[1]: cryptsetup.target: 
Found dependency on cryptsetup.target/start
  Apr 28 17:13:01 eu1 kernel: [5.360799] systemd[1]: cryptsetup.target: Job 
systemd-cryptsetup@swap.service/start deleted to break ordering cycle starting 
with cryptsetup.target/start
  . . . . . .
  Apr 28 17:13:01 eu1 kernel: [5.361082] systemd[1]: Unnecessary job for 
/dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802914-part2 was removed

  
  Also, /dev/mapper does not contain any swap devices:

  root@eu1:/var/log# ls -l /dev/mapper
  total 0
  crw--- 1 root root 10, 236 Apr 28 17:13 control
  root@eu1:/var/log#

  
  And top shows no swap:

  MiB Swap:  0.0 total,  0.0 free,  0.0 used.  63153.6 avail
  Mem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1875577/+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 1870189] Re: initramfs does not get loaded

[Dexuan Cui]

Today I installed a Generation-1 Ubuntu 20.04 VM on my local Hyper-V
host from the ISO file: https://releases.ubuntu.com/20.04/ubuntu-20.04
-live-server-amd64.iso (released on 4/23/2020) and I don't see this bug
and the grub version is 2.04-1ubuntu26.

Today I also created a VM on my host from https://cloud-
images.ubuntu.com/focal/20200430.1/focal-server-cloudimg-
amd64-azure.vhd.zip and can not see the bug either, and the grub version
is also 2.04-1ubuntu26.

When the bug was originally reported on Apr 1 against my Azure VM (a
Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu 20.04 by
“do-release-upgrade –d"), the grub version was 2.04-1ubuntu22.

So it looks the issue has been fixed in the 26 version?

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

Title:
  initramfs does not get loaded

Status in grub2 package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
  20.04 by “do-release-upgrade –d”.

  Then the latest Ubuntu v5.6 kernel was installed from
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
  reboot was performed, a panic with the v5.6 kernel occured because the
  rootfs can not be found.

  It turns out by default, initramfs does not get loaded:

  /boot/grub/grub.cfg:
  menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os 
$menuentry_id_option 'gnulinux-simple-3d2737e8-
  b95a-42bf-bac1-bb6fb4cda87f' {
  …
  if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic 
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro  console=tty1 
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled 
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
  else
linux /boot/vmlinuz-5.6.0-050600-generic 
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro  console=tty1 
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled 
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
  fi
  initrdfail
  }

  
  As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally, 
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit 
the “fail to mount rootfs” panic and the kernel will automatically reboot….   

  Also, the “initrdfail” here marks initrdfail=1, so when the kernel
  boots for the 2nd time, the kernel should successfully boot up.  Next,
  when the kernel boots for the 3rd time, it panics again since the
  userspace program resets initrdfail to 0, and next time when the
  kernel boots, it can boot up successfully -- this
  “panic/success/panic/success” pattern repeats forever…

  
  The linux-azure kernels are not affected since they have the vmbus driver and 
storage drivers built-in (i.e. “=y”):
  /boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
  /boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
  /boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
  /boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
  /boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
  /boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
  The v5.6 kernel uses =m rather than =y, so is affected here.

  
  It looks the setting may be intentional, but we should not assume a customer 
kernel must have the necessary vmbus/storage drivers built-in. 

  This issue only happens to the Ubuntu Marketplace image (19.10 and maybe 
19.04 as well?) on Azure. 
  We installed a Ubuntu  20.04 VM from the .iso file from 
http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub 
issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+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 1875577] [NEW] Encrypted swap won't load on 20.04 with zfs root

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

root@eu1:/var/log# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04 LTS
Release:20.04
Codename:   focal

root@eu1:/var/log# apt-cache policy cryptsetup
cryptsetup:
  Installed: (none)
  Candidate: 2:2.2.2-3ubuntu2
  Version table:
 2:2.2.2-3ubuntu2 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

OTHER BACKGROUND INFO:
==

1. machine has 2 drives. each drive is partitioned into 2 partitions,
zfs and swap


2. Ubuntu 20.04 installed on ZFS root using debootstrap 
(debootstrap_1.0.118ubuntu1_all)


3. The ZFS root pool is a 2 partition mirror (the first partition of each disk)


4. /etc/crypttab is set up as follows:

swap  /dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802914-part2  
  /dev/urandom   swap,cipher=aes-xts-plain64,size=256
swap  /dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802933-part2  
  /dev/urandom   swap,cipher=aes-xts-plain64,size=256



WHAT I EXPECTED
===

I expected machine would reboot and have encrypted swap that used two
devices under /dev/mapper


WHAT HAPPENED INSTEAD
=


On reboot, swap setup fails with the following messages in /var/log/syslog:

Apr 28 17:13:01 eu1 kernel: [5.360793] systemd[1]: cryptsetup.target: Found 
ordering cycle on systemd-cryptsetup@swap.service/start
Apr 28 17:13:01 eu1 kernel: [5.360795] systemd[1]: cryptsetup.target: Found 
dependency on systemd-random-seed.service/start
Apr 28 17:13:01 eu1 kernel: [5.360796] systemd[1]: cryptsetup.target: Found 
dependency on zfs-mount.service/start
Apr 28 17:13:01 eu1 kernel: [5.360797] systemd[1]: cryptsetup.target: Found 
dependency on zfs-load-module.service/start
Apr 28 17:13:01 eu1 kernel: [5.360798] systemd[1]: cryptsetup.target: Found 
dependency on cryptsetup.target/start
Apr 28 17:13:01 eu1 kernel: [5.360799] systemd[1]: cryptsetup.target: Job 
systemd-cryptsetup@swap.service/start deleted to break ordering cycle starting 
with cryptsetup.target/start
. . . . . .
Apr 28 17:13:01 eu1 kernel: [5.361082] systemd[1]: Unnecessary job for 
/dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802914-part2 was removed


Also, /dev/mapper does not contain any swap devices:

root@eu1:/var/log# ls -l /dev/mapper
total 0
crw--- 1 root root 10, 236 Apr 28 17:13 control
root@eu1:/var/log#


And top shows no swap:

MiB Swap:  0.0 total,  0.0 free,  0.0 used.  63153.6 avail
Mem

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

-- 
Encrypted swap won't load on 20.04 with zfs root
https://bugs.launchpad.net/bugs/1875577
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to zfs-linux in Ubuntu.

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1868551] Re: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire

[Leonardo Müller]

On my computer I use the workaround of changing the Xorg session from
modesetting to intel. To do this, firstly checking if xserver-xorg-
video-intel is installed and then I create the file
/etc/X11/xorg.conf.d/99-intel.conf with the following content:

Section "Device"
   Identifier  "Intel Graphics"
   Driver  "intel"
   Option  "DRI""3"
EndSection

Then I restart the display manager to apply the change. Not only this
crash stops happening to me, but it also solves another bug I face with
default Xubuntu 20.04 settings:

https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1870250

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

Title:
  Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4)
  i915_active_acquire

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  uname -a
  Linux xps 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux

  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  Codename: focal

  [ 2556.956079] BUG: kernel NULL pointer dereference, address: 0040
  [ 2556.956084] #PF: supervisor read access in kernel mode
  [ 2556.956084] #PF: error_code(0x) - not-present page
  [ 2556.956085] PGD 0 P4D 0 
  [ 2556.956088] Oops:  [#1] SMP NOPTI
  [ 2556.956090] CPU: 2 PID: 1685 Comm: xfwm4 Not tainted 5.4.0-14-generic 
#17-Ubuntu
  [ 2556.956092] Hardware name: Dell Inc. XPS 13 7390/0G2D0W, BIOS 1.2.0 
10/03/2019
  [ 2556.956161] RIP: 0010:i915_active_acquire+0xe/0x80 [i915]
  [ 2556.956163] Code: 00 48 c7 c6 11 4d 6b c0 e8 af a1 d6 c7 5d c3 66 66 2e 0f 
1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 
48 89 fb 85 c0 74 17 8d 50 01 f0 0f b1 53 38 75 f2 45 31
  [ 2556.956164] RSP: 0018:ac17c13279c8 EFLAGS: 00010286
  [ 2556.956165] RAX:  RBX: 983831d3e480 RCX: 

  [ 2556.956166] RDX: 983783475200 RSI: 983831d3e480 RDI: 
0008
  [ 2556.956167] RBP: ac17c13279e0 R08:  R09: 
98382d6b6520
  [ 2556.956168] R10: 6cc0 R11: 983838b4db00 R12: 
983783475200
  [ 2556.956169] R13: 0008 R14: 983783475200 R15: 
98382d6b6400
  [ 2556.956170] FS:  7f9031c28f00() GS:98383e50() 
knlGS:
  [ 2556.956171] CS:  0010 DS:  ES:  CR0: 80050033
  [ 2556.956172] CR2: 0040 CR3: 00046eac6001 CR4: 
003606e0
  [ 2556.956173] Call Trace:
  [ 2556.956199]  i915_active_ref+0x24/0x200 [i915]
  [ 2556.956223]  i915_vma_move_to_active+0x74/0xf0 [i915]
  [ 2556.956245]  eb_submit+0xff/0x440 [i915]
  [ 2556.956267]  i915_gem_do_execbuffer+0x88e/0xc20 [i915]
  [ 2556.956271]  ? sock_def_readable+0x40/0x70
  [ 2556.956274]  ? __kmalloc_node+0x205/0x320
  [ 2556.956294]  i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915]
  [ 2556.956314]  ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915]
  [ 2556.956330]  drm_ioctl_kernel+0xae/0xf0 [drm]
  [ 2556.956338]  drm_ioctl+0x234/0x3d0 [drm]
  [ 2556.956358]  ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915]
  [ 2556.956361]  ? vfs_writev+0xc3/0xf0
  [ 2556.956363]  do_vfs_ioctl+0x407/0x670
  [ 2556.956365]  ? fput+0x13/0x15
  [ 2556.956367]  ? __sys_recvmsg+0x88/0xa0
  [ 2556.956369]  ksys_ioctl+0x67/0x90
  [ 2556.956371]  __x64_sys_ioctl+0x1a/0x20
  [ 2556.956373]  do_syscall_64+0x57/0x190
  [ 2556.956376]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 2556.956377] RIP: 0033:0x7f9032b3f68b
  [ 2556.956379] Code: 0f 1e fa 48 8b 05 05 28 0d 00 64 c7 00 26 00 00 00 48 c7 
c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d d5 27 0d 00 f7 d8 64 89 01 48
  [ 2556.956380] RSP: 002b:7ffee39a0078 EFLAGS: 0246 ORIG_RAX: 
0010
  [ 2556.956381] RAX: ffda RBX: 55a8abeb6e48 RCX: 
7f9032b3f68b
  [ 2556.956382] RDX: 7ffee39a0090 RSI: 40406469 RDI: 
000d
  [ 2556.956382] RBP: 7ffee39a0120 R08: 0001 R09: 

  [ 2556.956383] R10: 7ffee39a0140 R11: 0246 R12: 
7f9022a4f460
  [ 2556.956384] R13:  R14: 7ffee39a0090 R15: 
000d
  [ 2556.956385] Modules linked in: ccm rfcomm xt_CHECKSUM xt_MASQUERADE 
xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat 
typec_displayport iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 nf_tables cmac nfnetlink algif_hash ip6table_filter ip6_tables 
iptable_filter algif_skcipher af_alg bpfilter bridge stp llc snd_sof_pci 
snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt 
snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core 
snd_soc_acpi_intel_match 

[Kernel-packages] [Bug 1855335] Re: CONFIG_DEBUG_CREDENTIALS should be enabled

[Tyler Hicks]

This change was applied during the Focal development cycle but then
reverted pending performance testing results. That performance testing
work was never finished and I'm no longer working on this bug.

** Changed in: linux (Ubuntu)
   Status: Fix Committed => Triaged

** Changed in: linux (Ubuntu)
 Assignee: Tyler Hicks (tyhicks) => (unassigned)

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

Title:
  CONFIG_DEBUG_CREDENTIALS should be enabled

Status in linux package in Ubuntu:
  Triaged

Bug description:
  We should enable CONFIG_DEBUG_CREDENTIALS to perform sanity checks, such as 
verifying usage counts and proper magic values, when handling cred
  structs. If a cred sanity check fails a loud warning is printed to the
  logs.

  The config option raises the bar on the effort required to implement an
  exploit based on cred manipulation. CONFIG_DEBUG_CREDENTIALS will not
  prevent the attack but may aide an administrator in discovering such an
  attack on the system.

  This config option is recommended by the Kernel Self Protection
  Project[1].

  [1]
  
https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855335/+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 1855340] Re: CONFIG_HARDENED_USERCOPY_FALLBACK should be disabled

[Tyler Hicks]

** Changed in: linux (Ubuntu)
   Status: In Progress => Triaged

** Changed in: linux (Ubuntu)
 Assignee: Tyler Hicks (tyhicks) => (unassigned)

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

Title:
  CONFIG_HARDENED_USERCOPY_FALLBACK should be disabled

Status in linux package in Ubuntu:
  Triaged

Bug description:
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855340/+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 1855341] Re: CONFIG_USELIB should be disabled

[Tyler Hicks]

This change was applied during the Focal development cycle but then
reverted pending performance testing results. That performance testing
work was never finished and I'm no longer working on this bug.

** Changed in: linux (Ubuntu)
   Status: Fix Committed => Triaged

** Changed in: linux (Ubuntu)
 Assignee: Tyler Hicks (tyhicks) => (unassigned)

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

Title:
  CONFIG_USELIB should be disabled

Status in linux package in Ubuntu:
  Triaged

Bug description:
  We should disable CONFIG_USELIB to make the uselib(2) system call
  unreachable in an effort to reduce the kernel attack surface.

  The system call is only used by very old libc implementations and is
  unlikely to be used today.

  This config option is recommended by the Kernel Self Protection
  Project[1] and a 2019 study performed by Capsule 8 shows that it is
  enabled in some other major distro kernels[2].

  [1] 
https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings
  [2] 
https://capsule8.com/blog/millions-of-binaries-later-a-look-into-linux-hardening-in-the-wild/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855341/+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 1855337] Re: CONFIG_DEBUG_NOTIFIERS should be enabled

[Tyler Hicks]

This change was applied during the Focal development cycle but then
reverted pending performance testing results. That performance testing
work was never finished and I'm no longer working on this bug.

** Changed in: linux (Ubuntu)
   Status: Fix Committed => Triaged

** Changed in: linux (Ubuntu)
 Assignee: Tyler Hicks (tyhicks) => (unassigned)

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

Title:
  CONFIG_DEBUG_NOTIFIERS should be enabled

Status in linux package in Ubuntu:
  Triaged

Bug description:
  We should enable CONFIG_DEBUG_NOTIFIERS to ensure that notifier functions are 
present in the core kernel text or module text sections before calling
  those functions.

  If an invalid function pointer is detected, a warning is issued and
  the function is not called. This helps in attack prevention and
  detection.

  This config option is recommended by the Kernel Self Protection
  Project[1].

  [1]
  
https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855337/+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 1855339] Re: CONFIG_LEGACY_PTYS should be disabled

[Tyler Hicks]

This change was applied during the Focal development cycle but then
reverted pending performance testing results. That performance testing
work was never finished and I'm no longer working on this bug.

** Changed in: linux (Ubuntu)
   Status: Fix Committed => Triaged

** Changed in: linux (Ubuntu)
 Assignee: Tyler Hicks (tyhicks) => (unassigned)

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

Title:
  CONFIG_LEGACY_PTYS should be disabled

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Legacy BSD PTYs have been replaced by UNIX 98 PTYs a long time ago.
  Disable legacy BSD PTY support as it is no longer needed.

  This config option is recommended by the Kernel Self Protection
  Project[1] and a 2019 study performed by Capsule 8 shows that it is
  enabled in some other major distro kernels[2].

  [1] 
https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings
  [2] 
https://capsule8.com/blog/millions-of-binaries-later-a-look-into-linux-hardening-in-the-wild/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855339/+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 1855336] Re: CONFIG_DEBUG_SG should be enabled

[Tyler Hicks]

This change was applied during the Focal development cycle but then
reverted pending performance testing results. That performance testing
work was never finished and I'm no longer working on this bug.

** Changed in: linux (Ubuntu)
   Status: Fix Committed => Triaged

** Changed in: linux (Ubuntu)
 Assignee: Tyler Hicks (tyhicks) => (unassigned)

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

Title:
  CONFIG_DEBUG_SG should be enabled

Status in linux package in Ubuntu:
  Triaged

Bug description:
  We should enable CONFIG_DEBUG_SG to perform sanity checks when performing
  operations on scatterlists. If a sanity check fails a loud warning is
  printed to the logs.

  This change may help in detection of an attack that relies on
  scatterlist manipulation.

  This config option is recommended by the Kernel Self Protection
  Project[1].

  [1]
  
https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855336/+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 1855338] Re: CONFIG_IO_STRICT_DEVMEM should be enabled

[Tyler Hicks]

This change was applied during the Focal development cycle but then
reverted pending performance testing results. That performance testing
work was never finished and I'm no longer working on this bug.

** Changed in: linux (Ubuntu)
   Status: Fix Committed => Triaged

** Changed in: linux (Ubuntu)
 Assignee: Tyler Hicks (tyhicks) => (unassigned)

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

Title:
  CONFIG_IO_STRICT_DEVMEM should be enabled

Status in linux package in Ubuntu:
  Triaged

Bug description:
  We should enable CONFIG_IO_STRICT_DEVMEM to restrict userspace access
  of active io-memory ranges.

  This could impact kernel debugability. In that case, you may reboot with
  iomem=relaxed on the kernel commandline to override this setting.

  
  This config option is recommended by the Kernel Self Protection Project[1] 
and a 2019 study performed by Capsule 8 shows that it is enabled in many other 
major distro kernels[2].

  [1] 
https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings
  [2] 
https://capsule8.com/blog/millions-of-binaries-later-a-look-into-linux-hardening-in-the-wild/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855338/+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 1855342] Re: CONFIG_SLAB_MERGE_DEFAULT should be disabled

[Tyler Hicks]

** Changed in: linux (Ubuntu)
   Status: In Progress => Triaged

** Changed in: linux (Ubuntu)
 Assignee: Tyler Hicks (tyhicks) => (unassigned)

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

Title:
  CONFIG_SLAB_MERGE_DEFAULT should be disabled

Status in linux package in Ubuntu:
  Triaged

Bug description:
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855342/+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 1811162] Re: Turn on CONFIG_REFCOUNT_FULL for non-x86 arches

[Tyler Hicks]

** Changed in: linux (Ubuntu)
 Assignee: Tyler Hicks (tyhicks) => (unassigned)

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

Title:
  Turn on CONFIG_REFCOUNT_FULL for non-x86 arches

Status in linux package in Ubuntu:
  Triaged

Bug description:
  The upstream kernel has added refcount protection, in two ways. For
  arches that have provided a fast refcount_t implementation, they get
  it automatically (this is signaled by ARCH_HAS_REFCOUNT, which as of
  4.20 kernels, is only the x86 arch). For other arches, they can get
  refcount protection via the CONFIG_REFCOUNT_FULL configure option. The
  upstream arm64 and arm maintainers have enabled this configuration by
  default for those arches, which has been carried into the ubuntu
  kernel config. We should enable that for our other arches that do not
  provide ARCH_HAS_REFCOUNT, namely ppc64el and s390x, to gain
  protection parity with the rest of the architectures supported by
  ubuntu kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811162/+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 1855334] Re: CONFIG_DEBUG_LIST should be enabled

[Tyler Hicks]

This change was applied during the Focal development cycle but then
reverted pending performance testing results. That performance testing
work was never finished and I'm no longer working on this bug.

** Changed in: linux (Ubuntu)
   Status: Fix Committed => Triaged

** Changed in: linux (Ubuntu)
 Assignee: Tyler Hicks (tyhicks) => (unassigned)

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

Title:
  CONFIG_DEBUG_LIST should be enabled

Status in linux package in Ubuntu:
  Triaged

Bug description:
  We should turn on CONFIG_DEBUG_LIST which does some sanity checking on the
  surrounding linked list elements when adding or removing an element. If the 
sanity check fails, the list manipulation operation is not and a loud warning 
is printed to the logs in the form of a WARN().
  
  This may prevent some exploits that involve manipulating a linked list.

  This config option is recommended by the Kernel Self Protection
  Project[1] and a 2019 study performed by Capsule 8 shows that it is
  enabled in some other major distro kernels[2].

  [1] 
https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings
  [2] 
https://capsule8.com/blog/millions-of-binaries-later-a-look-into-linux-hardening-in-the-wild/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855334/+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 1848921] Re: iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem [8086:0010]

[paoletto]

In that comment the link is from -46 to the downloaded -34?

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

Title:
  iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem
  [8086:0010]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 19.10
  Kernel 5.3.0-18-generic
  Hardware: Thinkpad T460p (also tested on T480s) with Intel 9260ac wifi card.

  Expected: Wifi connects, uploads/downloads as normal

  Symptom: Wifi connects, as soon as an upload/download (any heavy
  traffic) start, the system comes to a crawl, becomes barely usable,
  and I end up opening a prompt to reboot.

  The system is unusable. This happens even with the Live USB version.

  The only solution I found was to download a different (newer) firmware.
  Latest version from: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi

  This is iwlwifi-9260-th-b0-jf-b0-34.618819.0.tgz

  I then manually copy the contained firmware to /lib/firmware, remove
  all other versions and make a link to iwlwifi-9260-th-b0-jf-46.ucode
  that the kernel expects to load.

  This completely resolves the issue.

  This is the carsh log (Thinkpad T460p, but identical to T480s, all fresh 
installs):
  
  Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: Error sending 
SCAN_CFG_CMD: time out after 2000ms.
  Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: Current CMD queue 
read_ptr 64 write_ptr 65
  Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: HW error, resetting 
before reading
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Start IWL Error Log Dump:
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Status: 0x0080, 
count: 609870115
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Loaded firmware version: 
46.6bf1df06.0
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x36BC8FCF | 
ADVANCED_SYSASSERT  
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x28A5819E | 
trm_hw_status0
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x77944CFA | 
trm_hw_status1
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x018004F5 | branchlink2
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEBCFC5F1 | 
interruptlink1
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x07206003 | 
interruptlink2
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xE956CDF4 | data1
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7D692903 | data2
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xAD22F469 | data3
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x1040C00E | beacon time
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x0FF6877F | tsf low
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x82686A2F | tsf hi
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xB715D7B2 | time gp1
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5EC31049 | time gp2
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xF7FD7FF6 | uCode 
revision type
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x31225172 | uCode 
version major
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xFD1DB8B4 | uCode 
version minor
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xC000F415 | hw version
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7F9AFDD4 | board 
version
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xD5FD2F0F | hcmd
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x8F81D049 | isr0
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEDDFDA7B | isr1
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xD9409AD7 | isr2
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5AF7DA77 | isr3
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x400240BE | isr4
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEEF6DF6B | last cmd Id
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x40528540 | wait_event
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xB9BBD6FD | l2p_control
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xC21B6142 | l2p_duration
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7BDF6F9E | l2p_mhvalid
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x190AF41B | 
l2p_addr_match
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7FF297FF | lmpm_pmg_sel
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5248C715 | timestamp
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xBBB939AF | flow_handler
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Start IWL Error Log Dump:
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Status: 0x0080, 
count: -4391457
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5350C91F | 
ADVANCED_SYSASSERT
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x1FFE5437 | umac 
branchlink1
  Oct 20 01:51:16 weyw

[Kernel-packages] [Bug 1749961] Re: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller

[Bryan Walsh]

Hi Guilherme,

First, congrats on the release of Ubuntu 20.04.  I've been following
ubuntu for over 15 years now and it is one of the most polished releases
of seen. Job well done.

...but, yes I'm still seeing the same behavior on ubuntu 20.04.

Thanks,

Bryan

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

Title:
  xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1
  Controller

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux package in Debian:
  Confirmed

Bug description:
  It was observed that while trying to use a 4K USB webcam connected to
  USB port provided by ASMedia ASM1142 USB 3.1 Controller, the webcam
  does not work and kernel log shows the following messages:

  [431.928016] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928021] xhci_hcd :12:00.0: Looking for event-dma 003f3330e020 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928024] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928026] xhci_hcd :12:00.0: Looking for event-dma 003f3330e030 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928027] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928029] xhci_hcd :12:00.0: Looking for event-dma 003f3330e050 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928386] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13

  A similar issue was already reported on Launchpad:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667750

  The fix to this issue seems to be the following patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9da5a109

  Tests in our scenario with this patch proved still broken. Our next
  approach is to modify the patch a bit and re-test.

  This LP will be used to document our progress in the investigation.

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

Title:
  wifi issue with 5.4.0-28 lowlatency kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  hello,
  after fresh ubuntustudio 20.04 install, everything worked out the box
  But after 5.4.0-28 lowlatency kernel update, wifi does not work properly
  Connection to the wifi modem is ok, but network is abnormaly slow. Come bake 
to the previous kernel 5.4.0-26 fix the issue (both kernel using same 
backport-iwlwifi-dkms driver)
  Hope this will help, and the issue will be fixed in the next released, be 
safe, bye

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-lowlatency 5.4.0.28.33
  ProcVersionSignature: Ubuntu 5.4.0-28.32-lowlatency 5.4.30
  Uname: Linux 5.4.0-28-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  transistor   2177 F pulseaudio
   /dev/snd/controlC2:  transistor   2177 F pulseaudio
   /dev/snd/controlC1:  transistor   2177 F pulseaudio
   /dev/snd/controlC0:  transistor   2177 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Mon May  4 22:59:26 2020
  InstallationDate: Installed on 2020-04-27 (7 days ago)
  InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  MachineType: Micro-Star International Co., Ltd. GL75 9SE
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-lowlatency 
root=UUID=5f15-7a39-4245-8672-0f0aec9592f7 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-28-lowlatency N/A
   linux-backports-modules-5.4.0-28-lowlatency  N/A
   linux-firmware   1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/25/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17E5IMS.103
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17E5
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17E5IMS.103:bd06/25/2019:svnMicro-StarInternationalCo.,Ltd.:pnGL759SE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17E5:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: GL
  dmi.product.name: GL75 9SE
  dmi.product.sku: 17E5.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876815/+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 1876815] [NEW] wifi issue with 5.4.0-28 lowlatency kernel

[christophe moreau]

Public bug reported:

hello,
after fresh ubuntustudio 20.04 install, everything worked out the box
But after 5.4.0-28 lowlatency kernel update, wifi does not work properly
Connection to the wifi modem is ok, but network is abnormaly slow. Come bake to 
the previous kernel 5.4.0-26 fix the issue (both kernel using same 
backport-iwlwifi-dkms driver)
Hope this will help, and the issue will be fixed in the next released, be safe, 
bye

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-lowlatency 5.4.0.28.33
ProcVersionSignature: Ubuntu 5.4.0-28.32-lowlatency 5.4.30
Uname: Linux 5.4.0-28-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC3:  transistor   2177 F pulseaudio
 /dev/snd/controlC2:  transistor   2177 F pulseaudio
 /dev/snd/controlC1:  transistor   2177 F pulseaudio
 /dev/snd/controlC0:  transistor   2177 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Mon May  4 22:59:26 2020
InstallationDate: Installed on 2020-04-27 (7 days ago)
InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
MachineType: Micro-Star International Co., Ltd. GL75 9SE
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-lowlatency 
root=UUID=5f15-7a39-4245-8672-0f0aec9592f7 ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-28-lowlatency N/A
 linux-backports-modules-5.4.0-28-lowlatency  N/A
 linux-firmware   1.187
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/25/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E17E5IMS.103
dmi.board.asset.tag: Default string
dmi.board.name: MS-17E5
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17E5IMS.103:bd06/25/2019:svnMicro-StarInternationalCo.,Ltd.:pnGL759SE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17E5:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
dmi.product.family: GL
dmi.product.name: GL75 9SE
dmi.product.sku: 17E5.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

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


** Tags: amd64 apport-bug focal

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

Title:
  wifi issue with 5.4.0-28 lowlatency kernel

Status in linux package in Ubuntu:
  New

Bug description:
  hello,
  after fresh ubuntustudio 20.04 install, everything worked out the box
  But after 5.4.0-28 lowlatency kernel update, wifi does not work properly
  Connection to the wifi modem is ok, but network is abnormaly slow. Come bake 
to the previous kernel 5.4.0-26 fix the issue (both kernel using same 
backport-iwlwifi-dkms driver)
  Hope this will help, and the issue will be fixed in the next released, be 
safe, bye

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-lowlatency 5.4.0.28.33
  ProcVersionSignature: Ubuntu 5.4.0-28.32-lowlatency 5.4.30
  Uname: Linux 5.4.0-28-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  transistor   2177 F pulseaudio
   /dev/snd/controlC2:  transistor   2177 F pulseaudio
   /dev/snd/controlC1:  transistor   2177 F pulseaudio
   /dev/snd/controlC0:  transistor   2177 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Mon May  4 22:59:26 2020
  InstallationDate: Installed on 2020-04-27 (7 days ago)
  InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  MachineType: Micro-Star International Co., Ltd. GL75 9SE
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-lowlatency 
root=UUID=5f15-7a39-4245-8672-0f0aec9592f7 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-28-lowlatency N/A
   linux-backports-modules-5.4.0-28-lowlatency  N/A
   linux-firmware   1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/25/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17E5IMS.103
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17E5
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bv

[Kernel-packages] [Bug 1876770] [NEW] speed for CX4 VF showing as unknown in ethtool output

[Joseph Salisbury]

Public bug reported:

While deploying a VM in D series (D8S_V3 and D16S_V3) and enabling
accelerated networking, MLX5 drivers are getting installed.  However,
accelerated networking is not showing as enabled in guest OS. The same
VM is showing enabled from portal.


The problem is in the Mellanox driver for the CX-4 VF.  Mellanox has already 
fixed the problem in three separate patches, which are all in mainline.

We would like to request the following three commits in all supported
releases:

2f5438ca0ee0 ("net/mlx5: Tidy up and fix reverse christmas ordring")
c268ca6087f5 ("net/mlx5: Expose port speed when possible")
dc392fc56f39 ("net/mlx5: Expose link speed directly")

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

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

Title:
  speed for CX4 VF showing as unknown in ethtool output

Status in linux-azure package in Ubuntu:
  New

Bug description:
  While deploying a VM in D series (D8S_V3 and D16S_V3) and enabling
  accelerated networking, MLX5 drivers are getting installed.  However,
  accelerated networking is not showing as enabled in guest OS. The same
  VM is showing enabled from portal.

  
  The problem is in the Mellanox driver for the CX-4 VF.  Mellanox has already 
fixed the problem in three separate patches, which are all in mainline.

  We would like to request the following three commits in all supported
  releases:

  2f5438ca0ee0 ("net/mlx5: Tidy up and fix reverse christmas ordring")
  c268ca6087f5 ("net/mlx5: Expose port speed when possible")
  dc392fc56f39 ("net/mlx5: Expose link speed directly")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1876770/+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 1666432] Re: Internet drops every few minutes on wired and wireless connection

[Sebastien Bacher]

** Package changed: network-manager (Ubuntu) => linux (Ubuntu)

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

Title:
  Internet drops every few minutes on wired and wireless connection

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Internet drops every 1-30 minutes when connected via wired or wireless
  (i.e., this is a problem on both wired and wireless) even though
  connection icon indicates the computer is still connected.

  Disconnecting and reconnecting via the connection icon resets internet
  temporarily until the next time.

  Dropped internet is discovered with "The site can't be reached"
  screens in Chromium, or error messages when downloading/updating in
  Terminal, or missing connection in Ubuntu Software app, or stalled
  syncing in Insync application (occurred even without Insync).

  Internet drops more frequently on wireless than on wired.

  It seems to disconnect more frequently with heavier internet use
  (e.g., downloading multiple files, opening several webpages in quick
  succession).

  This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron
  15 5567 (dual boot). It occurs when running Live CD as well though.

  Ethernet and wifi both work without randomly disconnecting in Windows
  10 on the same machine, and ethernet and wifi work on other machines
  running Ubuntu and Windows with the same router, so it is not a
  hardware or router issue.

  Output from sudo lshw -class network

  *-network
     description: Wireless interface
     product: Wireless 3165
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:02:00.0
     logical name: wlp2s0
     version: 79
     serial: 58:fb:84:55:21:52
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 
link=yes multicast=yes wireless=IEEE 802.11abgn
     resources: irq:283 memory:df10-df101fff
    *-network
     description: Ethernet interface
     product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
     vendor: Realtek Semiconductor Co., Ltd.
     physical id: 0
     bus info: pci@:03:00.0
     logical name: enp3s0
     version: 07
     serial: 18:db:f2:3c:d5:37
     size: 10Mbit/s
     capacity: 100Mbit/s
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 
latency=0 link=no multicast=yes port=MII speed=10Mbit/s
     resources: irq:279 ioport:d000(size=256) memory:df00-df000fff 
memory:d030-d0303fff

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb 21 16:36:55 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-02-20 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0  proto static  metric 600
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000
   192.168.1.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.1.15  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/0  
pr500k-9912ec-1  36301ded-0ac5-4a86-9621-87290ef159af  
/org/freedesktop/NetworkManager/ActiveConnection/5
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
  ----
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  -- 
  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

[Kernel-packages] [Bug 1666432] [NEW] Internet drops every few minutes on wired and wireless connection

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Internet drops every 1-30 minutes when connected via wired or wireless
(i.e., this is a problem on both wired and wireless) even though
connection icon indicates the computer is still connected.

Disconnecting and reconnecting via the connection icon resets internet
temporarily until the next time.

Dropped internet is discovered with "The site can't be reached" screens
in Chromium, or error messages when downloading/updating in Terminal, or
missing connection in Ubuntu Software app, or stalled syncing in Insync
application (occurred even without Insync).

Internet drops more frequently on wireless than on wired.

It seems to disconnect more frequently with heavier internet use (e.g.,
downloading multiple files, opening several webpages in quick
succession).

This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron
15 5567 (dual boot). It occurs when running Live CD as well though.

Ethernet and wifi both work without randomly disconnecting in Windows 10
on the same machine, and ethernet and wifi work on other machines
running Ubuntu and Windows with the same router, so it is not a hardware
or router issue.

Output from sudo lshw -class network

*-network
   description: Wireless interface
   product: Wireless 3165
   vendor: Intel Corporation
   physical id: 0
   bus info: pci@:02:00.0
   logical name: wlp2s0
   version: 79
   serial: 58:fb:84:55:21:52
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
   configuration: broadcast=yes driver=iwlwifi 
driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 
link=yes multicast=yes wireless=IEEE 802.11abgn
   resources: irq:283 memory:df10-df101fff
  *-network
   description: Ethernet interface
   product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
   vendor: Realtek Semiconductor Co., Ltd.
   physical id: 0
   bus info: pci@:03:00.0
   logical name: enp3s0
   version: 07
   serial: 18:db:f2:3c:d5:37
   size: 10Mbit/s
   capacity: 100Mbit/s
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 
latency=0 link=no multicast=yes port=MII speed=10Mbit/s
   resources: irq:279 ioport:d000(size=256) memory:df00-df000fff 
memory:d030-d0303fff

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.2-0ubuntu0.16.04.3
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Feb 21 16:36:55 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-02-20 (1 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IpRoute:
 default via 192.168.1.1 dev wlp2s0  proto static  metric 600
 169.254.0.0/16 dev wlp2s0  scope link  metric 1000
 192.168.1.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.1.15  metric 
600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
 wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/0  
pr500k-9912ec-1  36301ded-0ac5-4a86-9621-87290ef159af  
/org/freedesktop/NetworkManager/ActiveConnection/5
 enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  --   
----
 lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  --   
----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug intel realtek xenial
-- 
Internet drops every few minutes on wired and wireless connection
https://bugs.launchpad.net/bugs/1666432
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs

[jacj]

Similar issue with nvidia driver 440.82.

However, on my end, the issue appears when vlc is open and reads from an
external mounted drive : suspending the computer then waking up, the
drive is not mounted anymore this is when the /var/log/syslog is written
gigs of those same lines in just minutes.

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

Title:
  Having a video playing/paused when switched to another user generates
  gigabytes of error logs

Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed

Bug description:
  To replicate:

  1. Start a video playing, for example in vlc. 'avcodec decoder: Using
  NVIDIA VDPAU Driver Shared Library  418.56  Fri Mar 15 12:31:51 CDT
  2019 for hardware decoding'

  2. Optionally pause it.

  3. Switch to another user.

  The original user's ~/.xsession-errors will rapidly fill up with
  errors along the lines of "vdpau_chroma filter error".

  At the same time, errors are put in /var/log/syslog as well:

  [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: 
An invalid handle value was provided.
  (repeat ad nauseum)

  At least one of the two will rapidly fill up its partition and
  problems will arise.

  With AMD video hardware and driver, the video continues playing - you
  can hear the sound despite being in the other user.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1846374/+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 1876697] Re: test_regression_testsuite from ubuntu_qrt_apparmor failed on Focal zVM

[Thadeu Lima de Souza Cascardo]

My guess is that the test might be hitting the following code from
kernel/sched/core.c:

#ifdef CONFIG_RT_GROUP_SCHED
/*
 * Do not allow realtime tasks into groups that have no runtime
 * assigned.
 */
if (rt_bandwidth_enabled() && rt_policy(policy) &&
task_group(p)->rt_bandwidth.rt_runtime == 0 &&
!task_group_is_autogroup(task_group(p))) {
retval = -EPERM;
goto unlock;
}
#endif

Which is not really about the capabilities. That is just a guess.

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

Title:
  test_regression_testsuite from ubuntu_qrt_apparmor failed on Focal zVM

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Issue found on zVM "kernel04" with 5.4.0-29.33

   ==
   FAIL: test_regression_testsuite (__main__.ApparmorTestsuites)
   Run kernel regression tests 
   --
   Traceback (most recent call last):
 File "./test-apparmor.py", line 1746, in test_regression_testsuite
   self.assertEqual(expected, rc, result + report)
   AssertionError: Got exit code 2, expected 0 
   
   running aa_exec
   
   running access
   xfail: ACCESS file rx (r)
   xfail: ACCESS file rwx (r)
   xfail: ACCESS file r (wx)
   xfail: ACCESS file rx (wx)
   xfail: ACCESS file rwx (wx)
   xfail: ACCESS dir rwx (r)
   xfail: ACCESS dir r (wx)
   xfail: ACCESS dir rx (wx)
   xfail: ACCESS dir rwx (wx)
   
   running at_secure
   
   running introspect
   
   running capabilities
   (ptrace)
   (sethostname)
   (setdomainname)
   (setpriority)
   (setscheduler)
   Error: syscall_setscheduler failed. Test 'syscall_setscheduler -- 
unconfined' was expected to 'pass'. Reason for failure 'FAIL: Can't set 
SCHED_RR: Operation not permitted'
   Error: syscall_setscheduler failed. Test 'syscall_setscheduler -- all caps' 
was expected to 'pass'. Reason for failure 'FAIL: Can't set SCHED_RR: Operation 
not permitted'
 preparing apparmor_2.13.3-7ubuntu5.dsc...  done
   Error: syscall_setscheduler failed. Test 'syscall_setscheduler -- capability 
sys_nice' was expected to 'pass'. Reason for failure 'FAIL: Can't set SCHED_RR: 
Operation not permitted'
   Error: changehat_wrapper failed. Test 'syscall_setscheduler changehat -- all 
caps' was expected to 'pass'. Reason for failure 'FAIL: Can't set SCHED_RR: 
Operation not permitted'
   Error: changehat_wrapper failed. Test 'syscall_setscheduler changehat -- 
capability sys_nice' was expected to 'pass'. Reason for failure 'FAIL: Can't 
set SCHED_RR: Operation not permitted'
   (reboot)
   (chroot)
   (mlockall)
   (net_raw)

  Please find attachment for the complete test log.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1876697/+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 1875916] Re: upgrading to 4.15.0-99-generic breaks the sound and the trackpad

[Felix Barruche]

Hi, when will the next cycle be?

For sound problems : 
In /etc/modprobe.d/alsa-base.conf change "options snd-hda-intel model=auto" by 
"options snd-hda-intel model=generic" seems to reactivate the sound on the 
computer (this does not work for headphones, on Dell Inspiron 5379)
A quick fix, it allows to not revert the 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/1875916

Title:
  upgrading to 4.15.0-99-generic breaks the sound and the trackpad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using kubuntu LTS 18.04.
  This morning I was promped to update the kernel to the 4.15.0-99-generic. 

  After the upgrade I did not manage to get any sound. I checked
  everything, pavucontrol, alsamix, everything was in order, the streams
  showed as if they were playing, however I couldn't get any sound from
  the speakers headphones and I could not get any sound recorded either.

  I then rebooted with the previous version of the Kernel, and have my sound 
back without doing anything at all.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4a7a721a-7a2e-4644-a881-34adcb28e1ba
  InstallationDate: Installed on 2019-01-29 (455 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig:
   lono wireless extensions.
   
   wlp108s0  no wireless extensions.
  MachineType: Dell Inc. Latitude 7390 2-in-1
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic 
root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-99-generic N/A
   linux-backports-modules-4.15.0-99-generic  N/A
   linux-firmware 1.173.17
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-99-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/27/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0YNG30
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd08/27/2018:svnDellInc.:pnLatitude73902-in-1:pvr:rvnDellInc.:rn0YNG30:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7390 2-in-1
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875916/+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 1874058] Re: [UBUNTU 20.04] mlx5: alloc_pages_nodemask stack trace

[Frank Heimes]

The commit:

019b36123ae "net/mlx5: Fix failing fw tracer allocation on s390"

will be picked up based on the following upstream release update:

Focal update: v5.4.37 upstream stable release:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876765

Aligning this status and setting it to In Progress.

** Changed in: linux (Ubuntu Focal)
   Status: New => In Progress

** Changed in: linux (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-z-systems
   Status: Triaged => In Progress

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

** Changed in: ubuntu-z-systems
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Skipper Bug 
Screeners (skipper-screen-team)

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

Title:
  [UBUNTU 20.04] mlx5: alloc_pages_nodemask stack trace

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress

Bug description:
  Using the mlx5 device driver on Ubuntu 20.04 (beta), the
  alloc_pages_nodemask code generates a stack trace when initializing a
  device. The driver tries to allocate more contiguous memory than is
  allowed by the platform specific FORCE_MAX_ZONEORDER setting.

  FORCE_MAX_ZONEORDER on s390x: 9
  FORCE_MAX_ZONEORDER on other platforms: 11 or more

  This issue only occurs on ConnectX5 devices because the mlx5_fw_tracer
  code is only used for physical functions.

  A fix for this has recently been pulled into David Miller's net tree as part 
of a series of Mellanox fixes:
  https://lore.kernel.org/netdev/20200420213606.44292-1-sae...@mellanox.com/

  It hasn't landed in Linus' tree yet though

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874058/+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 1872726] Re: [Ubuntu 20.04] net/mlx5e: Fix endianness handling in pedit mask

[Frank Heimes]

Fix:
404402abd5f9 "net/mlx5e: Fix endianness handling in pedit mask"
upstream with v5.6

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

Title:
  [Ubuntu 20.04] net/mlx5e: Fix endianness handling in pedit mask

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  New
Status in linux source package in Focal:
  New

Bug description:
  Issue found in the Mellanox mlx5 device driver:

  The mask value is provided as 64 bit and has to be casted in
  either 32 or 16 bit. On big endian systems the wrong half was
  casted which resulted in an all zero mask.

  We need to get the upstream commit picked up for the Ubuntu 20.04
  kernel.

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=404402abd5f90aa90a134eb9604b1750c1941529

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1872726/+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 1876784] 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 1876784

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

Title:
  new bridge interface defaults to having carrier

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Creating a new bridge interface and then raising it will result in the
  bridge having carrier, even though it has no ports.  Any change to the
  bridge interface, e.g. set its mac address or priority, will cause it
  to scan all its ports for link state and then properly set its own
  link state to carrier down.  However, if it's raised without adding
  any ports or changing any of its parameters, it will have carrier
  until a port is added or any parameter is changed.

  More detail on reproduction is here:
  https://github.com/systemd/systemd/pull/15619#issuecomment-621431802

  This is causing bug 1860926.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876784/+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 1875698] Re: Touchpad doesnt responds at all

[Shreyas Songirkar]

** Description changed:

  There's no touchpad device shown on running xinput list command, I'm also 
attaching ScreenShot of the output for xinput list.
  I tried installing Synaptics touchpad drivers but it disables all 
devices,such as keyboard, external mouse,etc. only enabling touchpad working 
totally fine.
- --- 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  shreyas1883 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  shreyas1883 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-07-01 (302 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. Inspiron 5567
  Package: linux (not installed)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=d59dd119-a160-452e-9fcf-c11f06434de8 ro i18042.reset quiet splash 
vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  RelatedPackageVersions:
-  linux-restricted-modules-5.3.0-46-generic N/A
-  linux-backports-modules-5.3.0-46-generic  N/A
-  linux-firmware1.173.17
+  linux-restricted-modules-5.3.0-46-generic N/A
+  linux-backports-modules-5.3.0-46-generic  N/A
+  linux-firmware1.173.17
  Tags:  bionic
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom chrome-remote-desktop dip kvm lpadmin plugdev 
sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/22/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.8
  dmi.board.name: 05VRRG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.8:bd05/22/2019:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn05VRRG:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5567
  dmi.product.sku: 0767
  dmi.sys.vendor: Dell Inc.

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

Title:
  Touchpad doesnt responds at all

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  There's no touchpad device shown on running xinput list command, I'm also 
attaching ScreenShot of the output for xinput list.
  I tried installing Synaptics touchpad drivers but it disables all 
devices,such as keyboard, external mouse,etc. only enabling touchpad working 
totally fine.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shreyas1883 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-07-01 (302 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. Inspiron 5567
  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 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=d59dd119-a160-452e-9fcf-c11f06434de8 ro i18042.reset quiet splash 
vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-46-generic N/A
   linux-backports-modules-5.3.0-46-generic  N/A
   linux-firmware1.173.17
  Tags:  bionic
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom chrome-remote-desktop dip kvm lpadmin plugdev 
sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/22/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.8
  dmi.board.name: 05VRRG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.8:bd05/22/2019:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn05VRRG:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5567
  dmi.product.sku: 0767
  dmi.sys.vendor: Dell Inc.

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

[Kernel-packages] [Bug 1874062] Re: [UBUNTU 20.04] Performance floating interrupt

[Frank Heimes]

The commit:

s390/pci: do not set affinity for floating irqs
86dbf32da150339ca81509fa2eb84c814b55258b

will be picked up based on the following upstream release update:

Focal update: v5.4.37 upstream stable release:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876765

Aligning this status and setting it to In Progress.

** Changed in: linux (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-z-systems
   Status: Triaged => In Progress

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

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

Title:
  [UBUNTU 20.04] Performance floating interrupt

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  With the introduction of CPU directed interrupts the kernel parameter 
pci=force_floating was introduced to fall back to the previous behavior using 
floating irqs.
  Furthermore this fallback is used on machines lacking support for directed 
interrupts.

  However we were still setting the affinity in that case, both in
  __irq_alloc_descs() and via the irq_set_affinity callback in struct
  irq_chip.

  This setting of the affinity leads to a performance regression in
  streaming workloads which can be seen with e.g. by an iperf streaming
  test between two LPARs using ConnectX-5 based nics.

  In some tests the performance would drop to 20% of the performance
  with older kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874062/+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 1876784] [NEW] new bridge interface defaults to having carrier

[Dan Streetman]

Public bug reported:

Creating a new bridge interface and then raising it will result in the
bridge having carrier, even though it has no ports.  Any change to the
bridge interface, e.g. set its mac address or priority, will cause it to
scan all its ports for link state and then properly set its own link
state to carrier down.  However, if it's raised without adding any ports
or changing any of its parameters, it will have carrier until a port is
added or any parameter is changed.

More detail on reproduction is here:
https://github.com/systemd/systemd/pull/15619#issuecomment-621431802

This is causing bug 1860926.

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

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

Title:
  new bridge interface defaults to having carrier

Status in linux package in Ubuntu:
  New

Bug description:
  Creating a new bridge interface and then raising it will result in the
  bridge having carrier, even though it has no ports.  Any change to the
  bridge interface, e.g. set its mac address or priority, will cause it
  to scan all its ports for link state and then properly set its own
  link state to carrier down.  However, if it's raised without adding
  any ports or changing any of its parameters, it will have carrier
  until a port is added or any parameter is changed.

  More detail on reproduction is here:
  https://github.com/systemd/systemd/pull/15619#issuecomment-621431802

  This is causing bug 1860926.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876784/+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 1848496] Re: [zfs-root] "device-mapper: reload ioctl on osprober-linux-sdaX failed: Device or resource busy" against devices owned by ZFS

[Richard Laager]

brian-willoughby (and pranav.bhattarai):

The original report text confirms that "The exit code is 0, so update-
grub does not fail as a result." That matches my understanding (as
someone who has done a lot of ZFS installs maintaining the upstream
Root-on-ZFS HOWTO) that this is purely cosmetic.

If you're not actually running other operating systems, you can simply
remove the os-prober package to make the errors go away.

I'm not saying it shouldn't be fixed. But it's not actually breaking
your systems, right?

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

Title:
  [zfs-root] "device-mapper: reload ioctl on osprober-linux-sdaX
  failed: Device or resource busy" against devices owned by ZFS

Status in os-prober package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  On a 19.10 (pre-release, 20191016 daily) zfs installation, running
  'os-prober' (as 'update-grub' does by default) triggers the following
  error message:

  x@x:~$ sudo os-prober; echo $?
  device-mapper: reload ioctl on osprober-linux-sda5  failed: Device or 
resource busy
  Command failed.
  0
  x@x:~$

  The exit code is 0, so update-grub does not fail as a result.

  
  Partitions on the only available storage (automatically setup by installer):

  x@x:~$ sudo fdisk /dev/sda -l
  Disk /dev/sda: 10 GiB, 10737418240 bytes, 20971520 sectors
  Disk model: VBOX HARDDISK   
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: gpt
  Disk identifier: AB7BECFB-5946-48B2-9C59-D2B1261E29A5

  Device   Start  End  Sectors  Size Type
  /dev/sda1 2048  1050623  1048576  512M EFI System
  /dev/sda2  1050624  1153023   102400   50M Linux filesystem
  /dev/sda3  1153024  2070527   917504  448M Linux swap
  /dev/sda4  2070528  6264831  41943042G Solaris boot
  /dev/sda5  6264832 20971486 147066557G Solaris root
  x@x:~$ 

  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: os-prober 1.74ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 14:19:59 2019
  InstallationDate: Installed on 2019-10-17 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191016.5)
  SourcePackage: os-prober
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1848496/+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 1876022] 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 1876022

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

Title:
  Wireless adapter not detected (WiFi)  Acer One S1003

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This tablet was running Windows when I first bought it.

  Known problem under windows : the wireless connection would fail after
  device wake up from suspend. It could still see and detect networks
  tho

  I was interested into having a Linux tablet so I installed Ubuntu
  2020.04 on it. Since my bios wouldn't accept 64 efi boot files, I had
  to use bootia32.efi. It failed many times on creating a boot partition
  until I connected it to the internet using a wired connection. Please
  note that while windows was still present on the disk, I could still
  use the WLAN under live linux. It's only when I had it completely
  erased Windows 10 that it stopped being detected by Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 30 05:27:54 2020
  InstallationDate: Installed on 2020-04-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  synaptic package remians locked after it was closes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Preventing updates through terminal command

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-28-generic 5.4.0-28.32
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  admin-meir  19747 F pulseaudio
   /dev/snd/controlC0:  admin-meir  19747 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Mon May  4 10:33:49 2020
  InstallationDate: Installed on 2020-05-01 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Inspiron 3180
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=eedc8f40-27b4-4fed-8609-5e17643f30c6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-28-generic N/A
   linux-backports-modules-5.4.0-28-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0918N8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3180
  dmi.product.sku: 087E
  dmi.product.version: 1.3.0
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876776/+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 1876022] Re: Wireless adapter not detected (WiFi) Acer One S1003

[Brian Murray]

** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)

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

Title:
  Wireless adapter not detected (WiFi)  Acer One S1003

Status in linux package in Ubuntu:
  New

Bug description:
  This tablet was running Windows when I first bought it.

  Known problem under windows : the wireless connection would fail after
  device wake up from suspend. It could still see and detect networks
  tho

  I was interested into having a Linux tablet so I installed Ubuntu
  2020.04 on it. Since my bios wouldn't accept 64 efi boot files, I had
  to use bootia32.efi. It failed many times on creating a boot partition
  until I connected it to the internet using a wired connection. Please
  note that while windows was still present on the disk, I could still
  use the WLAN under live linux. It's only when I had it completely
  erased Windows 10 that it stopped being detected by Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 30 05:27:54 2020
  InstallationDate: Installed on 2020-04-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876022/+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 1876593] Re: Ethernet not working/Realtek RTL8169 fails to load

[Robert Clipsham]

Fairly sure it was just a reboot.

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

Title:
  Ethernet not working/Realtek RTL8169 fails to load

Status in linux-signed package in Ubuntu:
  New

Bug description:
  With the latest kernels on Ubuntu 20.04 LTS, my onboard Ethernet has
  stopped working.

  Last known good kernel: Ubuntu 5.4.0-21.25-generic 5.4.27
  Current (bad) kernel: Ubuntu 5.4.0-28.32-generic 5.4.30

  Ethernet controller:

  03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168]
  (rev 03)

  Select lines from dmesg with bad kernel:

  [1.479172] r8169 :03:00.0: realtek.ko not loaded, maybe it needs to 
be added to initramfs?
  [1.498143] r8169: probe of :03:00.0 failed with error -49

  With good kernel:

  [1.472510] r8169 :03:00.0 eth0: RTL8168d/8111d, 6c:f0:49:e7:de:a3, 
XID 283, IRQ 35
  [1.472511] r8169 :03:00.0 eth0: jumbo features [frames: 9200 bytes, 
tx checksumming: ko]
  [8.430734] r8169 :03:00.0 eth0: Link is Down
  [9.241421] r8169 :03:00.0 eth0: Link is Up - 100Mbps/Full - flow 
control off

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1876593/+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 1848496] Re: [zfs-root] "device-mapper: reload ioctl on osprober-linux-sdaX failed: Device or resource busy" against devices owned by ZFS

[Brian Willoughby]

Just to let you know, this error is now preventing me from updating to the 
20.04 release (forced).
I have twin 500GB drives as ZFS boot device. The upgrade/install of 20.04 shows 
this error several times and ultimately fails.
Do I have to wait for 20.04.01 in July?

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

Title:
  [zfs-root] "device-mapper: reload ioctl on osprober-linux-sdaX
  failed: Device or resource busy" against devices owned by ZFS

Status in os-prober package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  On a 19.10 (pre-release, 20191016 daily) zfs installation, running
  'os-prober' (as 'update-grub' does by default) triggers the following
  error message:

  x@x:~$ sudo os-prober; echo $?
  device-mapper: reload ioctl on osprober-linux-sda5  failed: Device or 
resource busy
  Command failed.
  0
  x@x:~$

  The exit code is 0, so update-grub does not fail as a result.

  
  Partitions on the only available storage (automatically setup by installer):

  x@x:~$ sudo fdisk /dev/sda -l
  Disk /dev/sda: 10 GiB, 10737418240 bytes, 20971520 sectors
  Disk model: VBOX HARDDISK   
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: gpt
  Disk identifier: AB7BECFB-5946-48B2-9C59-D2B1261E29A5

  Device   Start  End  Sectors  Size Type
  /dev/sda1 2048  1050623  1048576  512M EFI System
  /dev/sda2  1050624  1153023   102400   50M Linux filesystem
  /dev/sda3  1153024  2070527   917504  448M Linux swap
  /dev/sda4  2070528  6264831  41943042G Solaris boot
  /dev/sda5  6264832 20971486 147066557G Solaris root
  x@x:~$ 

  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: os-prober 1.74ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 14:19:59 2019
  InstallationDate: Installed on 2019-10-17 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191016.5)
  SourcePackage: os-prober
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1848496/+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 1876697] Re: test_regression_testsuite from ubuntu_qrt_apparmor failed on Focal zVM

[Steve Beattie]

I have seen a similar failure with that specific test when running the
tests under virtualbox on x86, though I have not tried it in several
years.

If this is the expected behavior going forward on s390s, we can address
it in qa-regression-testing.

Thanks.

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

Title:
  test_regression_testsuite from ubuntu_qrt_apparmor failed on Focal zVM

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Issue found on zVM "kernel04" with 5.4.0-29.33

   ==
   FAIL: test_regression_testsuite (__main__.ApparmorTestsuites)
   Run kernel regression tests 
   --
   Traceback (most recent call last):
 File "./test-apparmor.py", line 1746, in test_regression_testsuite
   self.assertEqual(expected, rc, result + report)
   AssertionError: Got exit code 2, expected 0 
   
   running aa_exec
   
   running access
   xfail: ACCESS file rx (r)
   xfail: ACCESS file rwx (r)
   xfail: ACCESS file r (wx)
   xfail: ACCESS file rx (wx)
   xfail: ACCESS file rwx (wx)
   xfail: ACCESS dir rwx (r)
   xfail: ACCESS dir r (wx)
   xfail: ACCESS dir rx (wx)
   xfail: ACCESS dir rwx (wx)
   
   running at_secure
   
   running introspect
   
   running capabilities
   (ptrace)
   (sethostname)
   (setdomainname)
   (setpriority)
   (setscheduler)
   Error: syscall_setscheduler failed. Test 'syscall_setscheduler -- 
unconfined' was expected to 'pass'. Reason for failure 'FAIL: Can't set 
SCHED_RR: Operation not permitted'
   Error: syscall_setscheduler failed. Test 'syscall_setscheduler -- all caps' 
was expected to 'pass'. Reason for failure 'FAIL: Can't set SCHED_RR: Operation 
not permitted'
 preparing apparmor_2.13.3-7ubuntu5.dsc...  done
   Error: syscall_setscheduler failed. Test 'syscall_setscheduler -- capability 
sys_nice' was expected to 'pass'. Reason for failure 'FAIL: Can't set SCHED_RR: 
Operation not permitted'
   Error: changehat_wrapper failed. Test 'syscall_setscheduler changehat -- all 
caps' was expected to 'pass'. Reason for failure 'FAIL: Can't set SCHED_RR: 
Operation not permitted'
   Error: changehat_wrapper failed. Test 'syscall_setscheduler changehat -- 
capability sys_nice' was expected to 'pass'. Reason for failure 'FAIL: Can't 
set SCHED_RR: Operation not permitted'
   (reboot)
   (chroot)
   (mlockall)
   (net_raw)

  Please find attachment for the complete test log.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1876697/+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 1876776] [NEW] synaptic package remians locked after it was closes

[Meir Levi]

Public bug reported:

Preventing updates through terminal command

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-28-generic 5.4.0-28.32
ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
Uname: Linux 5.4.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  admin-meir  19747 F pulseaudio
 /dev/snd/controlC0:  admin-meir  19747 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
Date: Mon May  4 10:33:49 2020
InstallationDate: Installed on 2020-05-01 (2 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Dell Inc. Inspiron 3180
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=eedc8f40-27b4-4fed-8609-5e17643f30c6 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-28-generic N/A
 linux-backports-modules-5.4.0-28-generic  N/A
 linux-firmware1.187
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/09/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.0
dmi.board.name: 0918N8
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 1.3.0
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 3180
dmi.product.sku: 087E
dmi.product.version: 1.3.0
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug focal

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

Title:
  synaptic package remians locked after it was closes

Status in linux package in Ubuntu:
  New

Bug description:
  Preventing updates through terminal command

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-28-generic 5.4.0-28.32
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  admin-meir  19747 F pulseaudio
   /dev/snd/controlC0:  admin-meir  19747 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Mon May  4 10:33:49 2020
  InstallationDate: Installed on 2020-05-01 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Inspiron 3180
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=eedc8f40-27b4-4fed-8609-5e17643f30c6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-28-generic N/A
   linux-backports-modules-5.4.0-28-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0918N8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3180
  dmi.product.sku: 087E
  dmi.product.version: 1.3.0
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876776/+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 1876022] [NEW] Wireless adapter not detected (WiFi) Acer One S1003

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

This tablet was running Windows when I first bought it.

Known problem under windows : the wireless connection would fail after
device wake up from suspend. It could still see and detect networks tho

I was interested into having a Linux tablet so I installed Ubuntu
2020.04 on it. Since my bios wouldn't accept 64 efi boot files, I had to
use bootia32.efi. It failed many times on creating a boot partition
until I connected it to the internet using a wired connection. Please
note that while windows was still present on the disk, I could still use
the WLAN under live linux. It's only when I had it completely erased
Windows 10 that it stopped being detected by Ubuntu.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.18
ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
Uname: Linux 5.4.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 30 05:27:54 2020
InstallationDate: Installed on 2020-04-29 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug dist-upgrade focal
-- 
Wireless adapter not detected (WiFi)  Acer One S1003
https://bugs.launchpad.net/bugs/1876022
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround

[bmaupin]

I tried booting another half dozen times or so with 5.7 on Ubuntu 20.04
and I didn't have any issues. So maybe it's fixed with that combination?
Unfortunately since the wifi doesn't work I can't continue to use the
5.7 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/1808418

Title:
  Thinkpad T430u won't boot without noapic workaround

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

Bug description:
  I've used Ubuntu on this specific machine for years without problems,
  but starting with the 4.13 kernel that came with the 17.10 HWE and
  continuing into 18.04 kernels my computer would no longer boot,
  hanging at various screens:

  - A blank screen with a flashing cursor
  - A screen with this message:
  Loading Linux 4.13.0.36-generic ...
  Loading initial ramdisk ...
  - A screen with kernel messages, ending in:
  APCI: EC: interrupt blocked

  I've encountered the bug in a number of kernels, including:
  - 4.13.0-32
  - 4.13.0-36
  - 4.13.0-37
  - 4.15.0-24
  - 4.15.0-34
  - 4.15.0-36
  - 4.15.0-38
  - 4.15.0-42
  - 4.20.0-rc7

  I was able to work around the issue by adding noapic to
  GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"

  I'm not entirely sure of the consequences of this workaround, but one
  thing I've noticed is significantly reduced battery life.

  This bug seems very similar to what's described here for the Thinkpad
  E485/E585: https://evilazrael.de/node/401

  I'll attach screenshots of various times I've encountered this bug
  over the last year.

  $ lsb_release -rd
  Description:Ubuntu 18.04.1 LTS
  Release:18.04

  $ apt-cache policy linux-image-4.15.0-42-generic
  linux-image-4.15.0-42-generic:
    Installed: 4.15.0-42.45
    Candidate: 4.15.0-42.45
    Version table:
   *** 4.15.0-42.45 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-42-generic 4.15.0-42.45
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bryan  2349 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Dec 13 15:31:15 2018
  HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac
  InstallationDate: Installed on 2014-05-08 (1680 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 3351CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=cffbc87d-956b-4986-94df-b3b64ae5237f ro quiet splash noapic 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-07-12 (154 days ago)
  dmi.bios.date: 06/01/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H6ETA0WW (2.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3351CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH6ETA0WW(2.18):bd06/01/2018:svnLENOVO:pn3351CTO:pvrThinkPadT430u:rvnLENOVO:rn3351CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430u
  dmi.product.name: 3351CTO
  dmi.product.version: ThinkPad T430u
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808418/+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 1876593] Re: Ethernet not working/Realtek RTL8169 fails to load

[Heiner Kallweit]

Interesting. Did you switch off the machine after flashing the updated
BIOS (and before re-testing) or did you just reboot? In the latter case
this may be an explanation. Often a BIOS initializes certain things on
cold boot only.

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

Title:
  Ethernet not working/Realtek RTL8169 fails to load

Status in linux-signed package in Ubuntu:
  New

Bug description:
  With the latest kernels on Ubuntu 20.04 LTS, my onboard Ethernet has
  stopped working.

  Last known good kernel: Ubuntu 5.4.0-21.25-generic 5.4.27
  Current (bad) kernel: Ubuntu 5.4.0-28.32-generic 5.4.30

  Ethernet controller:

  03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168]
  (rev 03)

  Select lines from dmesg with bad kernel:

  [1.479172] r8169 :03:00.0: realtek.ko not loaded, maybe it needs to 
be added to initramfs?
  [1.498143] r8169: probe of :03:00.0 failed with error -49

  With good kernel:

  [1.472510] r8169 :03:00.0 eth0: RTL8168d/8111d, 6c:f0:49:e7:de:a3, 
XID 283, IRQ 35
  [1.472511] r8169 :03:00.0 eth0: jumbo features [frames: 9200 bytes, 
tx checksumming: ko]
  [8.430734] r8169 :03:00.0 eth0: Link is Down
  [9.241421] r8169 :03:00.0 eth0: Link is Up - 100Mbps/Full - flow 
control off

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1876593/+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 1876593] Re: Ethernet not working/Realtek RTL8169 fails to load

[Robert Clipsham]

Frustratingly, this seems to have now resolved itself, so I can't test
the patch. All I did was leave the machine off for a few hours and turn
it back on - then it was working again.

I now can't reproduce the problem, with or without the Lan Boot ROM
option. The PHY ID now reports as 0x001cc912.

I'll come back to it later and see if it breaks again.

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

Title:
  Ethernet not working/Realtek RTL8169 fails to load

Status in linux-signed package in Ubuntu:
  New

Bug description:
  With the latest kernels on Ubuntu 20.04 LTS, my onboard Ethernet has
  stopped working.

  Last known good kernel: Ubuntu 5.4.0-21.25-generic 5.4.27
  Current (bad) kernel: Ubuntu 5.4.0-28.32-generic 5.4.30

  Ethernet controller:

  03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168]
  (rev 03)

  Select lines from dmesg with bad kernel:

  [1.479172] r8169 :03:00.0: realtek.ko not loaded, maybe it needs to 
be added to initramfs?
  [1.498143] r8169: probe of :03:00.0 failed with error -49

  With good kernel:

  [1.472510] r8169 :03:00.0 eth0: RTL8168d/8111d, 6c:f0:49:e7:de:a3, 
XID 283, IRQ 35
  [1.472511] r8169 :03:00.0 eth0: jumbo features [frames: 9200 bytes, 
tx checksumming: ko]
  [8.430734] r8169 :03:00.0 eth0: Link is Down
  [9.241421] r8169 :03:00.0 eth0: Link is Up - 100Mbps/Full - flow 
control off

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1876593/+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 1838133] Re: realtek r8822be kernel module fails after update to linux kernel-headers 5.0.0-21

[Pablo]

Some further info:
I rolled back to 19.10 using the 5.3.0-51-generic and rtwpci and rtw88 work 
well. But as stated before, when going to 5.4.0-28-generic (and -26) I am 
suffering from what appears to be this bug. 

My wireless adapter is an RTL8822BE which shows up in lspci and lshw -C
network, although under 5.4.0-28 lshw shows it as disabled (it appears
to work for a few seconds after startup).  dsmeg shows some issues with
changing the power mode of the device although I am too much of a noob
to understand it.

Interestingly, wireless seemed to work on the 20.04 live version (from
USB).

As I said, I rolled back from 20.04 so I no longer have access to a
20.04 machine, but can reinstall it if there is any useful debugging to
be done.

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

Title:
  realtek r8822be kernel module fails after update to linux kernel-
  headers 5.0.0-21

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Realtek Wifi stops working after the driver changed from rtlwifi to
  rtw88.

  [Fix]
  Sync rtw88 to upstream version, and use MSI on the device.

  [Test]
  User confirmed the backport fixes the issue.

  [Regression Potential]
  Low. Currently only 8822be uses rtw88.

  === Original Bug Report ===
  On July 24th I upgraded to the latest linux-headers-5.0.0-21 as part of the 
dist-upgrade for latest packages in Disco Dingo 19.04. I didn't notice that 
wifi was no longer working because at work I exclusively use a wired Ethernet 
connection.

  Today, however, when I tried to use my realtek r8822be wireless card,
  I discovered that it was totally unresponsive and did not work with
  wpa_supplicant / wpa_cli even when invoked manually from the command
  line (let alone with NetworkManager). When the problem occurred, I was
  using 19.04's latest kernel 5.0.0-21.

  I then rebooted and selected kernel 5.0.0-20 from GRUB menu. "uname
  -a" shows that I am using the previous kernel version:

  Linux pj 5.0.0-20-generic #21-Ubuntu SMP Mon Jun 24 09:32:09 UTC 2019
  x86_64 x86_64 x86_64 GNU/Linux

  With this kernel version as well as linux-headers-5.0.0.20, linux-
  headers-5.0.0-20-generic, my realtek wireless card works fine. While
  booted into 5.0.0-20 kernel, here are the realtek kernel modules that
  are loaded:

  # lsmod | grep r8
  r8822be   692224  0
  mac80211  806912  1 r8822be
  cfg80211  671744  2 mac80211,r8822be
  r8169  81920  0

  Hopefully this realtek wireless regression can get fixed in the next
  minor kernel version. Let me know if you need any more information.

  Best Regards,
  Jun

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838133/+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 1875888] Re: Add signed modules for the 435 NVIDIA driver

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.4.0-29.33

---
linux (5.4.0-29.33) focal; urgency=medium

  * focal/linux: 5.4.0-29.33 -proposed tracker (LP: #1875858)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Add signed modules for the 435 NVIDIA driver (LP: #1875888)
- [Packaging] NVIDIA -- add signed modules for the 435 NVIDIA driver

  * built-using constraints preventing uploads (LP: #1875601)
- temporarily drop Built-Using data

 -- Stefan Bader   Wed, 29 Apr 2020 15:34:16
+0200

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

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

Title:
  Add signed modules for the 435 NVIDIA driver

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Fix Released

Bug description:
  Add signed modules for the 435 NVIDIA driver in Focal, so that
  upgrades from Bionic or from Eoan to Focal continue providing signed
  modules when using the 435 driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875888/+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 1875601] Re: built-using constraints preventing uploads

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.4.0-29.33

---
linux (5.4.0-29.33) focal; urgency=medium

  * focal/linux: 5.4.0-29.33 -proposed tracker (LP: #1875858)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Add signed modules for the 435 NVIDIA driver (LP: #1875888)
- [Packaging] NVIDIA -- add signed modules for the 435 NVIDIA driver

  * built-using constraints preventing uploads (LP: #1875601)
- temporarily drop Built-Using data

 -- Stefan Bader   Wed, 29 Apr 2020 15:34:16
+0200

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

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

Title:
  built-using constraints preventing uploads

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Released

Bug description:
  We are failing binary uploads due to new built-using checks.  In the
  short term disable generation of this information.  Propose to disable
  it in the dkms-build script.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875601/+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 1876767] [NEW] Focal update: v5.4.38 upstream stable release

[Kamal Mostafa]

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v5.4.38 upstream stable release
   from git://git.kernel.org/

Note: v5.4.38 itself consisted of a single revert (never committed to
Ubuntu focal)from v5.4.37 -- so this is just a dummy tracking bug,
really.

Linux 5.4.38
UBUNTU: upstream stable to v5.4.38

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

** Affects: linux (Ubuntu Focal)
 Importance: Undecided
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

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

** Changed in: linux (Ubuntu Focal)
   Status: New => In Progress

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    v5.4.38 upstream stable release
+    from git://git.kernel.org/
  
-v5.4.38 upstream stable release
-from git://git.kernel.org/
+ Note: v5.4.38 itself consisted of a single revert (never committed to
+ Ubuntu focal)from v5.4.37 -- so this is just a dummy tracking bug,
+ really.
+ 
+ Linux 5.4.38
+ UBUNTU: upstream stable to v5.4.38

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

Title:
  Focal update: v5.4.38 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  In Progress

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     v5.4.38 upstream stable release
     from git://git.kernel.org/

  Note: v5.4.38 itself consisted of a single revert (never committed to
  Ubuntu focal)from v5.4.37 -- so this is just a dummy tracking bug,
  really.

  Linux 5.4.38
  UBUNTU: upstream stable to v5.4.38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876767/+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 1876765] Re: Focal update: v5.4.37 upstream stable release

[Kamal Mostafa]

** Changed in: linux (Ubuntu Focal)
   Status: New => In Progress

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    v5.4.37 upstream stable release
+    from git://git.kernel.org/
  
-v5.4.37 upstream stable release
-from git://git.kernel.org/
+ remoteproc: Fix wrong rvring index computation
+ ubifs: Fix ubifs_tnc_lookup() usage in do_kill_orphans()
+ printk: queue wake_up_klogd irq_work only if per-CPU areas are ready
+ ASoC: stm32: sai: fix sai probe
+ usb: dwc3: gadget: Do link recovery for SS and SSP
+ kbuild: fix DT binding schema rule again to avoid needless rebuilds
+ usb: gadget: udc: bdc: Remove unnecessary NULL checks in bdc_req_complete
+ usb: gadget: udc: atmel: Fix vbus disconnect handling
+ afs: Make record checking use TASK_UNINTERRUPTIBLE when appropriate
+ afs: Fix to actually set AFS_SERVER_FL_HAVE_EPOCH
+ iio:ad7797: Use correct attribute_group
+ propagate_one(): mnt_set_mountpoint() needs mount_lock
+ counter: 104-quad-8: Add lock guards - generic interface
+ s390/ftrace: fix potential crashes when switching tracers
+ ASoC: q6dsp6: q6afe-dai: add missing channels to MI2S DAIs
+ ASoC: tas571x: disable regulators on failed probe
+ ASoC: wm8960: Fix wrong clock after suspend & resume
+ drivers: soc: xilinx: fix firmware driver Kconfig dependency
+ nfsd: memory corruption in nfsd4_lock()
+ bpf: Forbid XADD on spilled pointers for unprivileged users
+ i2c: altera: use proper variable to hold errno
+ rxrpc: Fix DATA Tx to disable nofrag for UDP on AF_INET6 socket
+ net/cxgb4: Check the return from t4_query_params properly
+ xfs: acquire superblock freeze protection on eofblocks scans
+ svcrdma: Fix trace point use-after-free race
+ svcrdma: Fix leak of svc_rdma_recv_ctxt objects
+ net/mlx5e: Don't trigger IRQ multiple times on XSK wakeup to avoid WQ overruns
+ net/mlx5e: Get the latest values from counters in switchdev mode
+ PCI: Add ACS quirk for Zhaoxin multi-function devices
+ PCI: Make ACS quirk implementations more uniform
+ PCI: Unify ACS quirk desired vs provided checking
+ PCI: Add Zhaoxin Vendor ID
+ PCI: Add ACS quirk for Zhaoxin Root/Downstream Ports
+ PCI: Move Apex Edge TPU class quirk to fix BAR assignment
+ ARM: dts: bcm283x: Disable dsi0 node
+ cpumap: Avoid warning when CONFIG_DEBUG_PER_CPU_MAPS is enabled
+ s390/pci: do not set affinity for floating irqs
+ net/mlx5: Fix failing fw tracer allocation on s390
+ sched/core: Fix reset-on-fork from RT with uclamp
+ perf/core: fix parent pid/tid in task exit events
+ netfilter: nat: fix error handling upon registering inet hook
+ PM: sleep: core: Switch back to async_schedule_dev()
+ blk-iocost: Fix error on iocost_ioc_vrate_adj
+ um: ensure `make ARCH=um mrproper` removes arch/$(SUBARCH)/include/generated/
+ bpf, x86_32: Fix incorrect encoding in BPF_LDX zero-extension
+ bpf, x86_32: Fix clobbering of dst for BPF_JSET
+ bpf, x86_32: Fix logic error in BPF_LDX zero-extension
+ mm: shmem: disable interrupt when acquiring info->lock in userfaultfd_copy 
path
+ xfs: clear PF_MEMALLOC before exiting xfsaild thread
+ bpf, x86: Fix encoding for lower 8-bit registers in BPF_STX BPF_B
+ libbpf: Initialize *nl_pid so gcc 10 is happy
+ net: fec: set GPR bit on suspend by DT configuration.
+ x86: hyperv: report value of misc_features
+ signal: check sig before setting info in kill_pid_usb_asyncio
+ afs: Fix length of dump of bad YFSFetchStatus record
+ xfs: fix partially uninitialized structure in xfs_reflink_remap_extent
+ ALSA: hda: Release resources at error in delayed probe
+ ALSA: hda: Keep the controller initialization even if no codecs found
+ ALSA: hda: Explicitly permit using autosuspend if runtime PM is supported
+ scsi: target: fix PR IN / READ FULL STATUS for FC
+ scsi: target: tcmu: reset_ring should reset TCMU_DEV_BIT_BROKEN
+ objtool: Fix CONFIG_UBSAN_TRAP unreachable warnings
+ objtool: Support Clang non-section symbols in ORC dump
+ xen/xenbus: ensure xenbus_map_ring_valloc() returns proper grant status
+ A

[Kernel-packages] [Bug 1876765] [NEW] Focal update: v5.4.37 upstream stable release

[Kamal Mostafa]

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v5.4.37 upstream stable release
   from git://git.kernel.org/

remoteproc: Fix wrong rvring index computation
ubifs: Fix ubifs_tnc_lookup() usage in do_kill_orphans()
printk: queue wake_up_klogd irq_work only if per-CPU areas are ready
ASoC: stm32: sai: fix sai probe
usb: dwc3: gadget: Do link recovery for SS and SSP
kbuild: fix DT binding schema rule again to avoid needless rebuilds
usb: gadget: udc: bdc: Remove unnecessary NULL checks in bdc_req_complete
usb: gadget: udc: atmel: Fix vbus disconnect handling
afs: Make record checking use TASK_UNINTERRUPTIBLE when appropriate
afs: Fix to actually set AFS_SERVER_FL_HAVE_EPOCH
iio:ad7797: Use correct attribute_group
propagate_one(): mnt_set_mountpoint() needs mount_lock
counter: 104-quad-8: Add lock guards - generic interface
s390/ftrace: fix potential crashes when switching tracers
ASoC: q6dsp6: q6afe-dai: add missing channels to MI2S DAIs
ASoC: tas571x: disable regulators on failed probe
ASoC: wm8960: Fix wrong clock after suspend & resume
drivers: soc: xilinx: fix firmware driver Kconfig dependency
nfsd: memory corruption in nfsd4_lock()
bpf: Forbid XADD on spilled pointers for unprivileged users
i2c: altera: use proper variable to hold errno
rxrpc: Fix DATA Tx to disable nofrag for UDP on AF_INET6 socket
net/cxgb4: Check the return from t4_query_params properly
xfs: acquire superblock freeze protection on eofblocks scans
svcrdma: Fix trace point use-after-free race
svcrdma: Fix leak of svc_rdma_recv_ctxt objects
net/mlx5e: Don't trigger IRQ multiple times on XSK wakeup to avoid WQ overruns
net/mlx5e: Get the latest values from counters in switchdev mode
PCI: Add ACS quirk for Zhaoxin multi-function devices
PCI: Make ACS quirk implementations more uniform
PCI: Unify ACS quirk desired vs provided checking
PCI: Add Zhaoxin Vendor ID
PCI: Add ACS quirk for Zhaoxin Root/Downstream Ports
PCI: Move Apex Edge TPU class quirk to fix BAR assignment
ARM: dts: bcm283x: Disable dsi0 node
cpumap: Avoid warning when CONFIG_DEBUG_PER_CPU_MAPS is enabled
s390/pci: do not set affinity for floating irqs
net/mlx5: Fix failing fw tracer allocation on s390
sched/core: Fix reset-on-fork from RT with uclamp
perf/core: fix parent pid/tid in task exit events
netfilter: nat: fix error handling upon registering inet hook
PM: sleep: core: Switch back to async_schedule_dev()
blk-iocost: Fix error on iocost_ioc_vrate_adj
um: ensure `make ARCH=um mrproper` removes arch/$(SUBARCH)/include/generated/
bpf, x86_32: Fix incorrect encoding in BPF_LDX zero-extension
bpf, x86_32: Fix clobbering of dst for BPF_JSET
bpf, x86_32: Fix logic error in BPF_LDX zero-extension
mm: shmem: disable interrupt when acquiring info->lock in userfaultfd_copy path
xfs: clear PF_MEMALLOC before exiting xfsaild thread
bpf, x86: Fix encoding for lower 8-bit registers in BPF_STX BPF_B
libbpf: Initialize *nl_pid so gcc 10 is happy
net: fec: set GPR bit on suspend by DT configuration.
x86: hyperv: report value of misc_features
signal: check sig before setting info in kill_pid_usb_asyncio
afs: Fix length of dump of bad YFSFetchStatus record
xfs: fix partially uninitialized structure in xfs_reflink_remap_extent
ALSA: hda: Release resources at error in delayed probe
ALSA: hda: Keep the controller initialization even if no codecs found
ALSA: hda: Explicitly permit using autosuspend if runtime PM is supported
scsi: target: fix PR IN / READ FULL STATUS for FC
scsi: target: tcmu: reset_ring should reset TCMU_DEV_BIT_BROKEN
objtool: Fix CONFIG_UBSAN_TRAP unreachable warnings
objtool: Support Clang non-section symbols in ORC dump
xen/xenbus: ensure xenbus_map_ring_valloc() returns proper grant status
ALSA: hda: call runtime_allow() for all hda controllers
net: stmmac: socfpga: Allow all RGMII modes
mac80211: fix channel switch trigger from unknown mesh peer
arm64: Delete the space separator in __emit_inst
ext4: use matching invalidatepage in ext4_writepage
ext4: increase wait time needed before reuse of deleted inode numbers
ext4: convert BUG_ON's to WARN_ON's in mballoc.c
blk-mq: Put driver tag in blk_mq_dispatch_rq_list() when no budget
hwmon: (jc42) Fix name to have no illegal characters
taprio: do not use BIT() in TCA_TAPRIO_ATTR_FLAG_* definitions
qed: Fix race condition between scheduling and destroying the slowpath workqueue
Crypto: chelsio - Fixes a hang issue during driver registration
net: use indirect call wrappers for skb_copy_datagram_iter()
qed: Fix use after free in qed_chain_free
ext4: check for non-zero journal inum in ext4_calculate_over

[Kernel-packages] [Bug 1872758] Re: System doesn't wake up after suspend on HP Pavillon 15-CS1022NL

[Frantz Honegger]

Hi,
I believe I have same bug on my DELL Latitude 5490.
It is impossible to wake up from lock (it works only if I wake up the computer 
in the first 5 seconds), suspend and hibernation.
The screen remains black, the fan is working, but the computer does not respond 
and has to be shut down by pressing the power button for a few seconds.
Everything works fine in Ubuntu 18.04.3, but the bug exists in Ubuntu 18.04.4 
and 20.04.
For the moment I am back to 18.04.3.
Thank you very much for your help.

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

Title:
  System doesn't wake up after suspend on HP Pavillon 15-CS1022NL

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1)
  lsb_release -rd
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  2)
  I think the bug is in the Kernel 5.3.0-46:

  apt-cache policy linux-headers-5.3.0-46-generic
  linux-headers-5.3.0-46-generic:
    Installato: 5.3.0-46.38~18.04.1
    Candidato:  5.3.0-46.38~18.04.1
    Tabella versione:
    *** 5.3.0-46.38~18.04.1 500
  500 http://it.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) When I wake up the laptop from suspension the laptop wakes up
  correctly.

  4) When I wake up the laptop from suspension the laptop doesn't wake
  up: I can hear the fans and I can see the keyboard backlight (and
  Power light) on but the screen is black.

  Furthermore I tried different Kernels and almost each version has the
  same problem. The first one which doesn't have this bug is the
  4.18.20-041820-generic version.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.3.0-46-generic 5.3.0-46.38~18.04.1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Tue Apr 14 17:30:12 2020
  InstallationDate: Installed on 2020-02-24 (49 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  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/+bug/1872758/+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 1876753] 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/1876753

Title:
  Thinkpad T430 Power Cycles instead of rebooting

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After installing Xubuntu 20.04, Thinkpad T430 does not reboot properly
  any more.

  Expected behavior: Power LED and HDD stay on, System reboots.

  Actual behavior: System switches off (including power LED and HDD
  which leads to emergency head parking and loud click noise) and
  switches back on after 5 seconds.

  Problem occurs with Xubuntu 20.04 and Ubuntu 20.04 even when booted
  from live USB medium. It also occurs with Mainline Kernel 5.6.7 which
  I installed for testing.

  It does not occur with several live media used for testing (Xubuntu
  18.04, Windows 10, Manjaro 20, MX 19) or when rebooted from within
  GRUB2 on my Xubuntu installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-28-generic 5.4.0-28.32
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  1954 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Mon May  4 17:58:49 2020
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2020-05-01 (3 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 2351BH6
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-28-generic N/A
   linux-backports-modules-5.4.0-28-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETC2WW (2.82 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2351BH6
  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: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:svnLENOVO:pn2351BH6:pvrThinkPadT430:rvnLENOVO:rn2351BH6:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2351BH6
  dmi.product.sku: LENOVO_MT_2351
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876753/+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 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0

[Uwe Terborg]

Hi,

i had the problems with 5.3.0-28, 5.3.0-45, 5.3.0-46 and 5.3.0-51  but
not with 4.18.0-25!

BR
Uwe

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

Title:
  5.3.0-46-generic - i915 - frequent GPU hangs  / resets rcs0

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

Bug description:
  Hi,

  Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent
  (every couple of minutes) GPU hangs and reset manifesting as 2-3
  seconds freezes of the GUI (other than the mouse pointer).

  No particular triggers identified although have Chrome / Chromium
  running with Hardware Acceleration enabled does appear to increase the
  frequency.

  I have seen incidences of these hangs in jounralctl output using
  previous kernels in the 5.3.0-xx series but they were very infrequent
  (one or twice in a week of daily usage)

  System Info
  steve@steve-Inspiron-5580:~$ inxi -SCGxxxz
  System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 
compiler: gcc v: 7.5.0
     Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 
Distro: Linux Mint 19.3 Tricia
     base: Ubuntu 18.04 bionic
  CPU:   Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT 
MCP arch: Kaby Lake rev: B
     L2 cache: 6144 KiB
     flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 28800
     Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 
800 3: 800 4: 800 5: 800 6: 800 7: 800
     8: 800
  Graphics:  Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 
00:02.0 chip ID: 8086:3ea0
     Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: 
fbdev,vesa resolution: 1920x1080~60Hz
     OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 
GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0
     direct render: Yes

  steve@steve-Inspiron-5580:~$ journalctl -b | grep i915
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: 
deactivate vga console
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: 
changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC 
firmware i915/kbl_dmc_ver1_04.bin (v1.4)
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 
20190619 for :00:02.0 on minor 0
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary 
device
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb 
frame buffer device
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound 
:00:02.0 (ops i915_audio_component_bind_ops [i915])
  Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: 
ecode 9:0:0x, hang on rcs0
  Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 
for hang on rcs0
  Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 
for hang on rcs0
  Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 
for hang on rcs0
  Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 
for hang on rcs0

  I note another user has reported similar issues on the same kernel at 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steve  3920 F pulseaudio
   /dev/snd/pcmC0D0p:   steve  3920 F...m pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.3
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2019-12-27 (104 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  MachineType: Dell Inc. Inspiron 5580
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: 
quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-46-generic N/A
   linux-backports-modules-5.3.0-46-generic  N/A
   linux-firmware1.173.17
  Tags:  tricia
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 07/02/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0K0DFT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellIn

[Kernel-packages] [Bug 1876753] [NEW] Thinkpad T430 Power Cycles instead of rebooting

[jdr]

Public bug reported:

After installing Xubuntu 20.04, Thinkpad T430 does not reboot properly
any more.

Expected behavior: Power LED and HDD stay on, System reboots.

Actual behavior: System switches off (including power LED and HDD which
leads to emergency head parking and loud click noise) and switches back
on after 5 seconds.

Problem occurs with Xubuntu 20.04 and Ubuntu 20.04 even when booted from
live USB medium. It also occurs with Mainline Kernel 5.6.7 which I
installed for testing.

It does not occur with several live media used for testing (Xubuntu
18.04, Windows 10, Manjaro 20, MX 19) or when rebooted from within GRUB2
on my Xubuntu installation.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-28-generic 5.4.0-28.32
ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
Uname: Linux 5.4.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  david  1954 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Mon May  4 17:58:49 2020
HibernationDevice: RESUME=none
InstallationDate: Installed on 2020-05-01 (3 days ago)
InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 2351BH6
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-28-generic N/A
 linux-backports-modules-5.4.0-28-generic  N/A
 linux-firmware1.187
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/07/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: G1ETC2WW (2.82 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2351BH6
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: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:svnLENOVO:pn2351BH6:pvrThinkPadT430:rvnLENOVO:rn2351BH6:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T430
dmi.product.name: 2351BH6
dmi.product.sku: LENOVO_MT_2351
dmi.product.version: ThinkPad T430
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal

** Attachment added: "Video of behavior"
   
https://bugs.launchpad.net/bugs/1876753/+attachment/5366285/+files/9154556-Video

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

Title:
  Thinkpad T430 Power Cycles instead of rebooting

Status in linux package in Ubuntu:
  New

Bug description:
  After installing Xubuntu 20.04, Thinkpad T430 does not reboot properly
  any more.

  Expected behavior: Power LED and HDD stay on, System reboots.

  Actual behavior: System switches off (including power LED and HDD
  which leads to emergency head parking and loud click noise) and
  switches back on after 5 seconds.

  Problem occurs with Xubuntu 20.04 and Ubuntu 20.04 even when booted
  from live USB medium. It also occurs with Mainline Kernel 5.6.7 which
  I installed for testing.

  It does not occur with several live media used for testing (Xubuntu
  18.04, Windows 10, Manjaro 20, MX 19) or when rebooted from within
  GRUB2 on my Xubuntu installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-28-generic 5.4.0-28.32
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  1954 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Mon May  4 17:58:49 2020
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2020-05-01 (3 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 2351BH6
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-28-generic N/A
   linux-backports-modules-5.4.0-28-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETC2WW (2.82 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2351BH6
  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: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:svnLENOVO:pn2351BH6:pvrThinkP

[Kernel-packages] [Bug 1876548] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

** Tags added: disco

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

Title:
  Could not install linux-image-unsigned-5.0.0-36-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Updated from Ubuntu 18.04 to Ubuntu 20.04. Can now only do partial
  upgrades with error message: installed linux-image-
  unsigned-5.0.0-36-generic package post-removal script subprocess
  returned error exit status 1. I have tried removing this package
  through various terminal commands and synaptic package manager. Always
  returns this message.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.8
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 15:17:57 2020
  InstallationDate: Installed on 2011-08-27 (3171 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptHistorylog:
   Start-Date: 2020-05-03  15:16:10
   Requested-By: eingley (1000)
   Remove: linux-image-unsigned-5.0.0-36-generic:amd64 (5.0.0-36.39~18.04.1)
   Error: Sub-process /usr/bin/dpkg returned an error code (1)
   End-Date: 2020-05-03  15:16:37
  VarLogDistupgradeAptlog:
   Log time: 2020-05-03 15:15:46.834531
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
 MarkDelete linux-image-unsigned-5.0.0-36-generic:amd64 < 
5.0.0-36.39~18.04.1 @rH mK Nb Ib > FU=0
  VarLogDistupgradeTermlog:
   
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2019-04-27T17:49:35.111043

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876548/+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 1876593] Re: Ethernet not working/Realtek RTL8169 fails to load

[Heiner Kallweit]

Typically it helps to do a rmmod r8169 + modprobe r8169 to work around the BIOS 
bug.
Maybe also a PHY soft reset helps to make the PHY behave sanely again.
Can you test whether the following fixes the issue for you?

diff --git a/drivers/net/ethernet/realtek/r8169_main.c 
b/drivers/net/ethernet/realtek/r8169_main.c
index 8b665f2ec..9b1ad5d45 100644
--- a/drivers/net/ethernet/realtek/r8169_main.c
+++ b/drivers/net/ethernet/realtek/r8169_main.c
@@ -5104,6 +5104,17 @@ static int r8169_mdio_write_reg(struct mii_bus *mii_bus, 
int phyaddr,
return 0;
 }
 
+static void rtl_phy_soft_reset(struct rtl8169_private *tp)
+{
+   int i = 30;
+
+   rtl_writephy(tp, MII_BMCR, BMCR_ANENABLE | BMCR_RESET);
+
+   do {
+   msleep(20);
+   } while (rtl_readphy(tp, MII_BMCR) & BMCR_RESET && --i);
+}
+
 static int r8169_mdio_register(struct rtl8169_private *tp)
 {
struct pci_dev *pdev = tp->pci_dev;
@@ -5123,6 +5134,11 @@ static int r8169_mdio_register(struct rtl8169_private 
*tp)
new_bus->read = r8169_mdio_read_reg;
new_bus->write = r8169_mdio_write_reg;
 
+   /* A BIOS bug causes few boards to report an invalid PHY ID otherwise */
+   if (tp->mac_version == RTL_GIGA_MAC_VER_25 ||
+   tp->mac_version == RTL_GIGA_MAC_VER_26)
+   rtl_phy_soft_reset(tp);
+
ret = devm_mdiobus_register(new_bus);
if (ret)
return ret;
-- 
2.26.2

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

Title:
  Ethernet not working/Realtek RTL8169 fails to load

Status in linux-signed package in Ubuntu:
  New

Bug description:
  With the latest kernels on Ubuntu 20.04 LTS, my onboard Ethernet has
  stopped working.

  Last known good kernel: Ubuntu 5.4.0-21.25-generic 5.4.27
  Current (bad) kernel: Ubuntu 5.4.0-28.32-generic 5.4.30

  Ethernet controller:

  03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168]
  (rev 03)

  Select lines from dmesg with bad kernel:

  [1.479172] r8169 :03:00.0: realtek.ko not loaded, maybe it needs to 
be added to initramfs?
  [1.498143] r8169: probe of :03:00.0 failed with error -49

  With good kernel:

  [1.472510] r8169 :03:00.0 eth0: RTL8168d/8111d, 6c:f0:49:e7:de:a3, 
XID 283, IRQ 35
  [1.472511] r8169 :03:00.0 eth0: jumbo features [frames: 9200 bytes, 
tx checksumming: ko]
  [8.430734] r8169 :03:00.0 eth0: Link is Down
  [9.241421] r8169 :03:00.0 eth0: Link is Up - 100Mbps/Full - flow 
control off

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1876593/+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 1868551] Re: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire

[Guy Baconniere]

I tested the test kernel 5.4 for about a day without issue
but all my computers using Intel GPU are using by default
kernel 5.5. I don't want to change that.

If you want to follow other users having the same kind of
issues with different i915 bugs on different Linux distro
follow comments on
https://linuxreviews.org/Linux_Kernel_5.5_Will_Not_Fix_The_Frequent_Intel_GPU_Hangs_In_Recent_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/1868551

Title:
  Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4)
  i915_active_acquire

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  uname -a
  Linux xps 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux

  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  Codename: focal

  [ 2556.956079] BUG: kernel NULL pointer dereference, address: 0040
  [ 2556.956084] #PF: supervisor read access in kernel mode
  [ 2556.956084] #PF: error_code(0x) - not-present page
  [ 2556.956085] PGD 0 P4D 0 
  [ 2556.956088] Oops:  [#1] SMP NOPTI
  [ 2556.956090] CPU: 2 PID: 1685 Comm: xfwm4 Not tainted 5.4.0-14-generic 
#17-Ubuntu
  [ 2556.956092] Hardware name: Dell Inc. XPS 13 7390/0G2D0W, BIOS 1.2.0 
10/03/2019
  [ 2556.956161] RIP: 0010:i915_active_acquire+0xe/0x80 [i915]
  [ 2556.956163] Code: 00 48 c7 c6 11 4d 6b c0 e8 af a1 d6 c7 5d c3 66 66 2e 0f 
1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 
48 89 fb 85 c0 74 17 8d 50 01 f0 0f b1 53 38 75 f2 45 31
  [ 2556.956164] RSP: 0018:ac17c13279c8 EFLAGS: 00010286
  [ 2556.956165] RAX:  RBX: 983831d3e480 RCX: 

  [ 2556.956166] RDX: 983783475200 RSI: 983831d3e480 RDI: 
0008
  [ 2556.956167] RBP: ac17c13279e0 R08:  R09: 
98382d6b6520
  [ 2556.956168] R10: 6cc0 R11: 983838b4db00 R12: 
983783475200
  [ 2556.956169] R13: 0008 R14: 983783475200 R15: 
98382d6b6400
  [ 2556.956170] FS:  7f9031c28f00() GS:98383e50() 
knlGS:
  [ 2556.956171] CS:  0010 DS:  ES:  CR0: 80050033
  [ 2556.956172] CR2: 0040 CR3: 00046eac6001 CR4: 
003606e0
  [ 2556.956173] Call Trace:
  [ 2556.956199]  i915_active_ref+0x24/0x200 [i915]
  [ 2556.956223]  i915_vma_move_to_active+0x74/0xf0 [i915]
  [ 2556.956245]  eb_submit+0xff/0x440 [i915]
  [ 2556.956267]  i915_gem_do_execbuffer+0x88e/0xc20 [i915]
  [ 2556.956271]  ? sock_def_readable+0x40/0x70
  [ 2556.956274]  ? __kmalloc_node+0x205/0x320
  [ 2556.956294]  i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915]
  [ 2556.956314]  ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915]
  [ 2556.956330]  drm_ioctl_kernel+0xae/0xf0 [drm]
  [ 2556.956338]  drm_ioctl+0x234/0x3d0 [drm]
  [ 2556.956358]  ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915]
  [ 2556.956361]  ? vfs_writev+0xc3/0xf0
  [ 2556.956363]  do_vfs_ioctl+0x407/0x670
  [ 2556.956365]  ? fput+0x13/0x15
  [ 2556.956367]  ? __sys_recvmsg+0x88/0xa0
  [ 2556.956369]  ksys_ioctl+0x67/0x90
  [ 2556.956371]  __x64_sys_ioctl+0x1a/0x20
  [ 2556.956373]  do_syscall_64+0x57/0x190
  [ 2556.956376]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 2556.956377] RIP: 0033:0x7f9032b3f68b
  [ 2556.956379] Code: 0f 1e fa 48 8b 05 05 28 0d 00 64 c7 00 26 00 00 00 48 c7 
c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d d5 27 0d 00 f7 d8 64 89 01 48
  [ 2556.956380] RSP: 002b:7ffee39a0078 EFLAGS: 0246 ORIG_RAX: 
0010
  [ 2556.956381] RAX: ffda RBX: 55a8abeb6e48 RCX: 
7f9032b3f68b
  [ 2556.956382] RDX: 7ffee39a0090 RSI: 40406469 RDI: 
000d
  [ 2556.956382] RBP: 7ffee39a0120 R08: 0001 R09: 

  [ 2556.956383] R10: 7ffee39a0140 R11: 0246 R12: 
7f9022a4f460
  [ 2556.956384] R13:  R14: 7ffee39a0090 R15: 
000d
  [ 2556.956385] Modules linked in: ccm rfcomm xt_CHECKSUM xt_MASQUERADE 
xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat 
typec_displayport iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 nf_tables cmac nfnetlink algif_hash ip6table_filter ip6_tables 
iptable_filter algif_skcipher af_alg bpfilter bridge stp llc snd_sof_pci 
snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt 
snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi snd_hda_codec_hdmi snd_soc_core 
snd_compress ac97_bus snd_pcm_dmaengine bnep snd_hda_codec_realtek 
snd_hda_codec_generic snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core 
snd_hwdep snd_pcm n

[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0

[Guillaume FRANCOIS]

Hello,

I installed today "5.3.0-52-generic #46-Ubuntu SMP" following comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/comments/101
(and fixing the typo for /etc/sourceS.list)

It removed all visible hang issued I have before especially with
IntelliJ and the whole desktop.

Since I boot at 15h36 I got only 3 lines in journalctl, which is way
less then before.

mai 04 15:44:08 francogu-linux-7540 kernel: [drm:intel_pipe_update_end [i915]] 
*ERROR* Atomic update failure on pipe C (start=62403 end=62404) time 145 us, 
min 1073, max 1079, scanline start 1070, end 1079
mai 04 15:57:58 francogu-linux-7540 kernel: [drm:intel_pipe_update_end [i915]] 
*ERROR* Atomic update failure on pipe C (start=112170 end=112171) time 162 us, 
min 1073, max 1079, scanline start 1069, end 1079
mai 04 17:18:25 francogu-linux-7540 kernel: [drm:intel_pipe_update_end [i915]] 
*ERROR* Atomic update failure on pipe B (start=401843 end=401844) time 210 us, 
min 1073, max 1079, scanline start 1072, end 1086

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

Title:
  5.3.0-46-generic - i915 - frequent GPU hangs  / resets rcs0

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

Bug description:
  Hi,

  Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent
  (every couple of minutes) GPU hangs and reset manifesting as 2-3
  seconds freezes of the GUI (other than the mouse pointer).

  No particular triggers identified although have Chrome / Chromium
  running with Hardware Acceleration enabled does appear to increase the
  frequency.

  I have seen incidences of these hangs in jounralctl output using
  previous kernels in the 5.3.0-xx series but they were very infrequent
  (one or twice in a week of daily usage)

  System Info
  steve@steve-Inspiron-5580:~$ inxi -SCGxxxz
  System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 
compiler: gcc v: 7.5.0
     Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 
Distro: Linux Mint 19.3 Tricia
     base: Ubuntu 18.04 bionic
  CPU:   Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT 
MCP arch: Kaby Lake rev: B
     L2 cache: 6144 KiB
     flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 28800
     Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 
800 3: 800 4: 800 5: 800 6: 800 7: 800
     8: 800
  Graphics:  Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 
00:02.0 chip ID: 8086:3ea0
     Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: 
fbdev,vesa resolution: 1920x1080~60Hz
     OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 
GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0
     direct render: Yes

  steve@steve-Inspiron-5580:~$ journalctl -b | grep i915
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: 
deactivate vga console
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: 
changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC 
firmware i915/kbl_dmc_ver1_04.bin (v1.4)
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 
20190619 for :00:02.0 on minor 0
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary 
device
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb 
frame buffer device
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound 
:00:02.0 (ops i915_audio_component_bind_ops [i915])
  Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: 
ecode 9:0:0x, hang on rcs0
  Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 
for hang on rcs0
  Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 
for hang on rcs0
  Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 
for hang on rcs0
  Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 
for hang on rcs0

  I note another user has reported similar issues on the same kernel at 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steve  3920 F pulseaudio
   /dev/snd/pcmC0D0p:   steve  3920 F...m pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.3
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2019-12-27 (104 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  MachineType: Dell Inc. Inspiron 5580
  Package: linux (not installe

[Kernel-packages] [Bug 1876548] Re: Could not install linux-image-unsigned-5.0.0-36-generic

[Brian Murray]

** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)

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

Title:
  Could not install linux-image-unsigned-5.0.0-36-generic

Status in linux package in Ubuntu:
  New

Bug description:
  Updated from Ubuntu 18.04 to Ubuntu 20.04. Can now only do partial
  upgrades with error message: installed linux-image-
  unsigned-5.0.0-36-generic package post-removal script subprocess
  returned error exit status 1. I have tried removing this package
  through various terminal commands and synaptic package manager. Always
  returns this message.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.8
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 15:17:57 2020
  InstallationDate: Installed on 2011-08-27 (3171 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptHistorylog:
   Start-Date: 2020-05-03  15:16:10
   Requested-By: eingley (1000)
   Remove: linux-image-unsigned-5.0.0-36-generic:amd64 (5.0.0-36.39~18.04.1)
   Error: Sub-process /usr/bin/dpkg returned an error code (1)
   End-Date: 2020-05-03  15:16:37
  VarLogDistupgradeAptlog:
   Log time: 2020-05-03 15:15:46.834531
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
 MarkDelete linux-image-unsigned-5.0.0-36-generic:amd64 < 
5.0.0-36.39~18.04.1 @rH mK Nb Ib > FU=0
  VarLogDistupgradeTermlog:
   
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2019-04-27T17:49:35.111043

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876548/+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 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0

[Rob Cork]

I haven't had a hang since installing 5.3.0-52-generic on April 30th.

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

Title:
  5.3.0-46-generic - i915 - frequent GPU hangs  / resets rcs0

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

Bug description:
  Hi,

  Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent
  (every couple of minutes) GPU hangs and reset manifesting as 2-3
  seconds freezes of the GUI (other than the mouse pointer).

  No particular triggers identified although have Chrome / Chromium
  running with Hardware Acceleration enabled does appear to increase the
  frequency.

  I have seen incidences of these hangs in jounralctl output using
  previous kernels in the 5.3.0-xx series but they were very infrequent
  (one or twice in a week of daily usage)

  System Info
  steve@steve-Inspiron-5580:~$ inxi -SCGxxxz
  System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 
compiler: gcc v: 7.5.0
     Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 
Distro: Linux Mint 19.3 Tricia
     base: Ubuntu 18.04 bionic
  CPU:   Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT 
MCP arch: Kaby Lake rev: B
     L2 cache: 6144 KiB
     flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 28800
     Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 
800 3: 800 4: 800 5: 800 6: 800 7: 800
     8: 800
  Graphics:  Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 
00:02.0 chip ID: 8086:3ea0
     Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: 
fbdev,vesa resolution: 1920x1080~60Hz
     OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 
GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0
     direct render: Yes

  steve@steve-Inspiron-5580:~$ journalctl -b | grep i915
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: 
deactivate vga console
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: 
changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC 
firmware i915/kbl_dmc_ver1_04.bin (v1.4)
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 
20190619 for :00:02.0 on minor 0
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary 
device
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb 
frame buffer device
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound 
:00:02.0 (ops i915_audio_component_bind_ops [i915])
  Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: 
ecode 9:0:0x, hang on rcs0
  Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 
for hang on rcs0
  Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 
for hang on rcs0
  Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 
for hang on rcs0
  Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 
for hang on rcs0

  I note another user has reported similar issues on the same kernel at 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steve  3920 F pulseaudio
   /dev/snd/pcmC0D0p:   steve  3920 F...m pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.3
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2019-12-27 (104 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  MachineType: Dell Inc. Inspiron 5580
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: 
quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-46-generic N/A
   linux-backports-modules-5.3.0-46-generic  N/A
   linux-firmware1.173.17
  Tags:  tricia
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 07/02/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0K0DFT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd07/02/2019:svnDellIn

[Kernel-packages] [Bug 1876548] [NEW] Could not install linux-image-unsigned-5.0.0-36-generic

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Updated from Ubuntu 18.04 to Ubuntu 20.04. Can now only do partial
upgrades with error message: installed linux-image-
unsigned-5.0.0-36-generic package post-removal script subprocess
returned error exit status 1. I have tried removing this package through
various terminal commands and synaptic package manager. Always returns
this message.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.8
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
Uname: Linux 5.4.0-9-generic x86_64
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Sun May  3 15:17:57 2020
InstallationDate: Installed on 2011-08-27 (3171 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeAptHistorylog:
 Start-Date: 2020-05-03  15:16:10
 Requested-By: eingley (1000)
 Remove: linux-image-unsigned-5.0.0-36-generic:amd64 (5.0.0-36.39~18.04.1)
 Error: Sub-process /usr/bin/dpkg returned an error code (1)
 End-Date: 2020-05-03  15:16:37
VarLogDistupgradeAptlog:
 Log time: 2020-05-03 15:15:46.834531
 Starting pkgProblemResolver with broken count: 0
 Starting 2 pkgProblemResolver with broken count: 0
 Done
   MarkDelete linux-image-unsigned-5.0.0-36-generic:amd64 < 5.0.0-36.39~18.04.1 
@rH mK Nb Ib > FU=0
VarLogDistupgradeTermlog:
 
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2019-04-27T17:49:35.111043

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


** Tags: amd64 apport-bug dist-upgrade focal
-- 
Could not install linux-image-unsigned-5.0.0-36-generic 
https://bugs.launchpad.net/bugs/1876548
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1876741] 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/1876741

Title:
  Lenovo X1 boot crash with HDMI cable attached and laptop lid closed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hey everyone,
  just upgraded to 20.04 in my Lenovo X1 Carbon laptop and found myself in 
really big troubles.

  I always started my laptop pressing the power button and then closing
  the laptop lid, because I'm using an external HDMI display. This
  worked always well with Ubuntu 19.10. With 20.04 the system crash.

  These are the actions that reproduce the problem:

  1 - Boot the system, pressing the power button and closing the laptop lid 
with an external HDMI display attached to the laptop;
  2 - See on the external HDMI display the boot progress: BIOS loading and then 
grub not appearing;
  3 - Listen to the fans that are about to make the laptop lift;
  4 - Press the power button to force off the laptop;

  At this point the only way to have everything back is:

  1 - Detach any external device;
  2 - Detach the power cable;
  3 - Wait 3 seconds or more;
  4 - Open the laptop lid;
  5 - Attach the power cable;
  6 - Press the power button;

  Without doing exactly as I written the laptop will not boot up, even
  if I force power off, after starting it again, after the BIOS display,
  the screen goes blank and the fans lift.

  NOTE 1: I already disabled secure boot in the BIOS, and also selected
  discrete graphics for the display (otherwise I'm not able to even
  start X);

  NOTE 2: the scenario is exactly the same with nvidia-driver-435 and
  nvidia-driver-440;

  NOTE 3: if I leave the laptop lid open, everything is just fine;

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-28-generic 5.4.0-28.32
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  rasca  2750 F pulseaudio
   /dev/snd/controlC1:  rasca  2750 F pulseaudio
   /dev/snd/controlC0:  rasca  2750 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  4 16:24:47 2020
  InstallationDate: Installed on 2019-12-10 (146 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QVCTO1WW
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=c61df9cc-bd36-4ed2-8f52-de114bbf3fc3 ro rd.driver.blacklist=nouveau
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-28-generic N/A
   linux-backports-modules-5.4.0-28-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-28 (6 days ago)
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET43W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T08861 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET43W(1.30):bd03/24/2020:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QVCTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme 2nd
  dmi.product.name: 20QVCTO1WW
  dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd
  dmi.product.version: ThinkPad X1 Extreme 2nd
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876741/+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 1749961] Re: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller

[Guilherme G. Piccoli]

Hi John and all, thanks for updating logs and enhancing the report! Due
to a lot of other work, and the nature of this problem (being a FW issue
that we'd try to alleviate using a hack in linux), I wasn't able to work
the tentative hack approach yet.

The issue was "resolved" through a FW update by ASMedia, but this was
only worked with a specific motherboard vendor, not as a general
release. This is the problem with FW fixes...they are quite scattered
and vendor-depending. So, can you John or any of the reporters try to
reproduce the problem with:

(a) Ubuntu 20.04, just released?
(b) Ubuntu 18.04 running the current HWE kernel (5.3)?

That'd be good data points. Also, if you could try Ubuntu 20.04 with latest 
mainline kernel (from [0]), that would be a gigantic help!
Thanks in advance,


Guilherme


[0] https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

** No longer affects: linux (Ubuntu Artful)

** Changed in: linux (Ubuntu Trusty)
   Status: In Progress => Won't Fix

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

Title:
  xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1
  Controller

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux package in Debian:
  Confirmed

Bug description:
  It was observed that while trying to use a 4K USB webcam connected to
  USB port provided by ASMedia ASM1142 USB 3.1 Controller, the webcam
  does not work and kernel log shows the following messages:

  [431.928016] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928021] xhci_hcd :12:00.0: Looking for event-dma 003f3330e020 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928024] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928026] xhci_hcd :12:00.0: Looking for event-dma 003f3330e030 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928027] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928029] xhci_hcd :12:00.0: Looking for event-dma 003f3330e050 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928386] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13

  A similar issue was already reported on Launchpad:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667750

  The fix to this issue seems to be the following patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9da5a109

  Tests in our scenario with this patch proved still broken. Our next
  approach is to modify the patch a bit and re-test.

  This LP will be used to document our progress in the investigation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749961/+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 1876741] [NEW] Lenovo X1 boot crash with HDMI cable attached and laptop lid closed

[Raoul Scarazzini]

Public bug reported:

Hey everyone,
just upgraded to 20.04 in my Lenovo X1 Carbon laptop and found myself in really 
big troubles.

I always started my laptop pressing the power button and then closing
the laptop lid, because I'm using an external HDMI display. This worked
always well with Ubuntu 19.10. With 20.04 the system crash.

These are the actions that reproduce the problem:

1 - Boot the system, pressing the power button and closing the laptop lid with 
an external HDMI display attached to the laptop;
2 - See on the external HDMI display the boot progress: BIOS loading and then 
grub not appearing;
3 - Listen to the fans that are about to make the laptop lift;
4 - Press the power button to force off the laptop;

At this point the only way to have everything back is:

1 - Detach any external device;
2 - Detach the power cable;
3 - Wait 3 seconds or more;
4 - Open the laptop lid;
5 - Attach the power cable;
6 - Press the power button;

Without doing exactly as I written the laptop will not boot up, even if
I force power off, after starting it again, after the BIOS display, the
screen goes blank and the fans lift.

NOTE 1: I already disabled secure boot in the BIOS, and also selected
discrete graphics for the display (otherwise I'm not able to even start
X);

NOTE 2: the scenario is exactly the same with nvidia-driver-435 and
nvidia-driver-440;

NOTE 3: if I leave the laptop lid open, everything is just fine;

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-28-generic 5.4.0-28.32
ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
Uname: Linux 5.4.0-28-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  rasca  2750 F pulseaudio
 /dev/snd/controlC1:  rasca  2750 F pulseaudio
 /dev/snd/controlC0:  rasca  2750 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon May  4 16:24:47 2020
InstallationDate: Installed on 2019-12-10 (146 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: LENOVO 20QVCTO1WW
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=c61df9cc-bd36-4ed2-8f52-de114bbf3fc3 ro rd.driver.blacklist=nouveau
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-28-generic N/A
 linux-backports-modules-5.4.0-28-generic  N/A
 linux-firmware1.187
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-04-28 (6 days ago)
dmi.bios.date: 03/24/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: N2OET43W (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QVCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T08861 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET43W(1.30):bd03/24/2020:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QVCTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Extreme 2nd
dmi.product.name: 20QVCTO1WW
dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd
dmi.product.version: ThinkPad X1 Extreme 2nd
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal hdmi nvidia

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

Title:
  Lenovo X1 boot crash with HDMI cable attached and laptop lid closed

Status in linux package in Ubuntu:
  New

Bug description:
  Hey everyone,
  just upgraded to 20.04 in my Lenovo X1 Carbon laptop and found myself in 
really big troubles.

  I always started my laptop pressing the power button and then closing
  the laptop lid, because I'm using an external HDMI display. This
  worked always well with Ubuntu 19.10. With 20.04 the system crash.

  These are the actions that reproduce the problem:

  1 - Boot the system, pressing the power button and closing the laptop lid 
with an external HDMI display attached to the laptop;
  2 - See on the external HDMI display the boot progress: BIOS loading and then 
grub not appearing;
  3 - Listen to the fans that are about to make the laptop lift;
  4 - Press the power button to force off the laptop;

  At this point the only way to have everything back is:

  1 - Detach any external device;
  2 - Detach the power cable;
  3 - Wait 3 seconds or more;
  4 - Open the laptop lid;
  5 - Attach the power cable;
  6 - Press the power button;

  Without doing exactly as I written the laptop will not boot up, even
  if I force power off, after starting it again, after the BIOS display,
  the screen goes blank and the fans lift.

  NOTE 1: I already disabled secure boot in the BIOS, and also selected
  discrete graphics for the display (otherwise I

[Kernel-packages] [Bug 1872908] Re: bcmwl kernel module does not build with 5.6.0 kernel

[Launchpad Bug Tracker]

This bug was fixed in the package bcmwl - 6.30.223.271+bdcom-0ubuntu6

---
bcmwl (6.30.223.271+bdcom-0ubuntu6) groovy; urgency=medium

  * debian/dkms.conf.in,
debian/patches/0028-add-support-for-linux-5.6.patch (LP: #1872908):
- Add support for Linux 5.6.

 -- Alberto Milone   Mon, 04 May 2020
13:23:19 +0200

** Changed in: bcmwl (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  bcmwl kernel module does not build with 5.6.0 kernel

Status in bcmwl package in Ubuntu:
  Fix Released
Status in bcmwl source package in Focal:
  Triaged

Bug description:
  After kernel update to 5.6.0-1007-oem wifi stopped working.
  Turned out dkms is unable to build the bcmwl module.

  The make log shows:

  ubuntu@ubuntu-inspiron-5482:~$ cat 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log
  DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.6.0-1007-oem (x86_64)
  ons 15 apr 2020 09:19:05 CEST
  make: Entering directory '/usr/src/linux-headers-5.6.0-1007-oem'
  CFG80211 API is prefered for this kernel version
  Using CFG80211 API
AR  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a
CC [M]  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
CC [M]  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
CC [M]  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o
CC [M]  
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In 
function ‘osl_reg_map’:
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: 
error: implicit declaration of function ‘ioremap_nocache’; did you mean 
‘ioremap_cache’? [-Werror=implicit-function-declaration]
949 |  return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
|  ^~~
|  ioremap_cache
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: 
warning: returning ‘int’ from a function with return type ‘void *’ makes 
pointer from integer without a cast [-Wint-conversion]
949 |  return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ~^~~~
  In file included from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40:
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c: 
In function ‘wl_set_auth_type’:
  
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5:
 warning: this statement may fall through [-Wimplicit-fallthrough=]
 52 |  if (wl_dbg_level & WL_DBG_DBG) {   \
| ^
  
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:816:3:
 note: in expansion of macro ‘WL_DBG’
816 |   WL_DBG(("network eap\n"));
|   ^~
  
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:817:2:
 note: here
817 |  default:
|  ^~~
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In 
function ‘wl_attach’:
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:20: 
error: implicit declaration of function ‘ioremap_nocache’; did you mean 
‘ioremap_cache’? [-Werror=implicit-function-declaration]
593 |  if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ)) 
== NULL) {
|^~~
|ioremap_cache
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:18: 
warning: assignment to ‘void *’ from ‘int’ makes pointer from integer without a 
cast [-Wint-conversion]
593 |  if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ)) 
== NULL) {
|  ^
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In 
function ‘wl_pci_probe’:
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:780:2: 
warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
780 |  if ((val & 0xff00) != 0)
|  ^~
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:782:3: 
note: ...this statement, but the latter is misleadingly indented as if it were 
guarded by the ‘if’
782 |   bar1_size = pci_resource_len(pdev, 2);
|   ^
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:783:15: 
warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
783 |   bar1_addr = (uchar *)ioremap_nocache(pci_resource_start(pdev, 2),
|   ^
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In 
function ‘wl_reg_proc_entry’:
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:3376:58: 
error: passing ar

[Kernel-packages] [Bug 1873506] Re: ubuntu/focal64 fails to mount Vagrant shared folders

[Jake Cobb]

Not sure how to test this as requested by the bot.  I don't think just
enabling proposed on an existing published image is sufficient.  Are
there proposed cloud image builds posted 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/1873506

Title:
  ubuntu/focal64 fails to mount Vagrant shared folders

Status in cloud-images:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed

Bug description:
  SRU Justification

  Impact: When our kernel packaging was updated to build the virtualbox
  guest packages by downloading the dkms package, the modules were
  accidentally moved to linux-modules-extra instead of linux-modules.
  This has caused the modules to go missing in our Vagrant images.

  Fix: Move the modules back to linux-modules.

  Test Case: Build the kernel packages and confirm that the vboxguest
  and vboxsf drivers are now in linux-modules rather than linux-modules-
  extra.

  Regression Potential: Since linux-modules is required, anyone who is
  using the vbox drivers will continue to have them after this change.
  Therefore the risk of regression is extremely low.

  
  ---

  
  Attempting to `vagrant up` using the `ubuntu/focal64` box fails to mount the 
`/vagrant` shared folder. `ubuntu/bionic64` works as expected. Here is the 
Vagrant error message:

  Vagrant was unable to mount VirtualBox shared folders. This is usually
  because the filesystem "vboxsf" is not available. This filesystem is
  made available via the VirtualBox Guest Additions and kernel module.
  Please verify that these guest additions are properly installed in the
  guest. This is not a bug in Vagrant and is usually caused by a faulty
  Vagrant box. For context, the command attempted was:

  mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant

  The error output from the command was:

  : No such device

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1873506/+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 1826125] Re: Dell XPS 13 9380 flickering (Whiskey Lake)

[Timo Aaltonen]

** Changed in: linux
   Importance: Critical => Unknown

** Changed in: linux
 Remote watch: freedesktop.org Bugzilla #110511 => 
gitlab.freedesktop.org/drm/intel/issues #272

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

Title:
  Dell XPS 13 9380 flickering  (Whiskey Lake)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers
  to the point of being totally unusable.

  I have upgraded since to 18.10 and 19.04 with no changes. I have tried
  several combinations of the i915 parameters fastboot, enable_rc6 and
  enable_fbc to no avail.

  Examples of flickering are here:
  https://photos.app.goo.gl/1PkL2HrjMBP41aML9
  https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1430 F pulseaudio
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X31
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-13 (10 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 9380
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem 
root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1 
i915.enable_rc6=0 vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1035-oem N/A
   linux-backports-modules-4.15.0-1035-oem  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 4.15.0-1035-oem x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1826125/+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 1874057] s390/pci: Fix zpci_alloc_domain() over allocation (for focal 2)

[bugproxy]

--- Comment on attachment From niklas.schne...@ibm.com 2020-05-04 09:52 
EDT---


Oh thank you for your patience, I totally screwed up the backport patch
as I accidentally included some code from the next commit

7a11c67a1ff9b0231e6a28294776d55b569a ("s390/pci: Improve handling of
unset UID")

Actually that now applies cleanly on top and I think we might
want to include that as well, escpecially since it will also simplify
the backporting of the multi-function patch series.

** Attachment added: "s390/pci: Fix zpci_alloc_domain() over allocation (for 
focal 2)"
   
https://bugs.launchpad.net/bugs/1874057/+attachment/5366222/+files/0001-s390-pci-Fix-zpci_alloc_domain-over-allocation.patch

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

Title:
  [UBUNTU 20.04] s390x/pci: do not allow to create more pci functions
  than configured via CONFIG_PCI_NR_FUNCTIONS

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  SRU Justification:
  ==

  [Impact]

  * PCI Functions with UIDs >128 are currently not accounted correctly
  in the s390x/pci (zPCI) code.

  * Furthermore, the code allows that more than CONFIG_PCI_NR_FUNCTIONS
  are created.

  * This can lead to issues with data structures which were only
  allocated for CONFIG_PCI_NR_FUNCTIONS.

  [Fix]

  *
  
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874057/+attachment/5357850/+files/0001-s390
  -pci-Fix-zpci_alloc_domain-over-allocation-for-focal.patch

  [Test Case]

  * Set the kernel parameter CONFIG_PCI_NR_FUNCTIONS to a specific
  (reasonablly low) number.

  * And check if more PCI functions can be created than specified by
  CONFIG_PCI_NR_FUNCTIONS (e.g. using a RoCE adapter) and watch for
  kernel message 'Adding PCI function ... failed'

  
  [Regression Potential] 

  * There is regression potential can be considered as low, since:

  * the zPCI cards are less wide spread than for example ccw adapters on
  s390x

  * the fix got already upstream accepted in 5.7, hence upstream
  reviewed, too

  * the modifications span just two files and both are s390x arch
  specific

  [Other Info]

  * the above patch-file is based on commit
  969ae01bab2fe938b4c8324836038b5ac1c78fac ("s390/pci: Fix
  zpci_alloc_domain() over allocation"), but this backport was needed
  for getting this applied to focal master-next

  * and this patch got upstream accepted with kernel v5.7-rc1, hence on
  the long term it should be in 'gorilla'

  __

  PCI Functions with UIDs >128 are currently not accounted correctly in
  the s390x/pci code. Furthermore, the code allows that more than
  CONFIG_PCI_NR_FUNCTIONS are created. This can lead to issues with data
  structures which were only allocated for CONFIG_PCI_NR_FUNCTIONS.

  This has been fixed in the following upstream commit:

  969ae01bab2fe938b4c8324836038b5ac1c78fac
  ("s390/pci: Fix zpci_alloc_domain() over allocation")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874057/+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 1870189] Re: initramfs does not get loaded

[David Baird]

I'm actually not sure the best place to file a ticket for the cloudimg
distribution. Any recommendation appreciated.

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

Title:
  initramfs does not get loaded

Status in grub2 package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
  20.04 by “do-release-upgrade –d”.

  Then the latest Ubuntu v5.6 kernel was installed from
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
  reboot was performed, a panic with the v5.6 kernel occured because the
  rootfs can not be found.

  It turns out by default, initramfs does not get loaded:

  /boot/grub/grub.cfg:
  menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os 
$menuentry_id_option 'gnulinux-simple-3d2737e8-
  b95a-42bf-bac1-bb6fb4cda87f' {
  …
  if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic 
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro  console=tty1 
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled 
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
  else
linux /boot/vmlinuz-5.6.0-050600-generic 
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro  console=tty1 
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled 
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
  fi
  initrdfail
  }

  
  As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally, 
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit 
the “fail to mount rootfs” panic and the kernel will automatically reboot….   

  Also, the “initrdfail” here marks initrdfail=1, so when the kernel
  boots for the 2nd time, the kernel should successfully boot up.  Next,
  when the kernel boots for the 3rd time, it panics again since the
  userspace program resets initrdfail to 0, and next time when the
  kernel boots, it can boot up successfully -- this
  “panic/success/panic/success” pattern repeats forever…

  
  The linux-azure kernels are not affected since they have the vmbus driver and 
storage drivers built-in (i.e. “=y”):
  /boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
  /boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
  /boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
  /boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
  /boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
  /boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
  The v5.6 kernel uses =m rather than =y, so is affected here.

  
  It looks the setting may be intentional, but we should not assume a customer 
kernel must have the necessary vmbus/storage drivers built-in. 

  This issue only happens to the Ubuntu Marketplace image (19.10 and maybe 
19.04 as well?) on Azure. 
  We installed a Ubuntu  20.04 VM from the .iso file from 
http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub 
issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+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 1876196] Re: apt info does not show the Supported: information for 20.04 LTS kernels

[Andy Whitcroft]

This was an intentional change.  As the release pocket in immutable we
end up with inaccurate information in the pocket if the support time
changes for a package, such as happens when we enter ESM.  There is/will
be tooling to find the support lifetime.  Part of this is the ubuntu-
security-status command.

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

Title:
  apt info does not show the Supported: information for 20.04 LTS
  kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  One of our cert tests has been failing on Focal kernels.  Lookning at
  the -29 kernel today, we noticed that the Supported: item is missing
  when looking at Apt info.

  Focal:
  ubuntu@hogplum:~$ apt-cache show linux-image-`uname -r`
  Package: linux-image-5.4.0-29-generic
  Architecture: amd64
  Version: 5.4.0-29.33
  Built-Using: linux (= 5.4.0-29.33)
  Priority: optional
  Section: kernel
  Source: linux-signed
  Origin: Ubuntu
  Maintainer: Canonical Kernel Team 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 11415
  Provides: aufs-dkms, fuse-module, ivtv-modules, kvm-api-4, linux-image, 
redhat-cluster-modules, spl-dkms, spl-modules, virtualbox-guest-dkms, 
virtualbox-guest-modules, zfs-dkms, zfs-modules
  Depends: kmod, linux-base (>= 4.5ubuntu1~16.04.1), 
linux-modules-5.4.0-29-generic
  Recommends: grub-pc | grub-efi-amd64 | grub-efi-ia32 | grub | lilo, 
initramfs-tools | linux-initramfs-tool
  Suggests: fdutils, linux-doc | linux-source-5.4.0, linux-tools, 
linux-headers-5.4.0-29-generic
  Conflicts: linux-image-unsigned-5.4.0-29-generic
  Filename: 
pool/main/l/linux-signed/linux-image-5.4.0-29-generic_5.4.0-29.33_amd64.deb
  Size: 8870728
  MD5sum: 5af753b944eb16b8f248e236edb6ce54
  SHA1: 389bd3f05310f2adc7c1110890afc1ef4a2acc19
  SHA256: eb420ae6d31dd3cbf341de32035976271e568b868416e8bd00b644dcb39cde1a
  Description-en: Signed kernel image generic
   A kernel image for generic.  This version of it is signed with
   Canonical's UEFI/Opal signing key.
  Description-md5: 54a18b1adebc179da3c9e59a5db5fe77

  For comparison, this is 5.3 from Bionic HWE:
  Package: linux-image-5.3.0-46-generic
  Architecture: amd64
  Version: 5.3.0-46.38~18.04.1
  Built-Using: linux-hwe (= 5.3.0-46.38~18.04.1)
  Priority: optional
  Section: kernel
  Source: linux-signed-hwe
  Origin: Ubuntu
  Maintainer: Canonical Kernel Team 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 8955
  Provides: aufs-dkms, fuse-module, ivtv-modules, kvm-api-4, linux-image, 
redhat-cluster-modules, spl-dkms, spl-modules, virtualbox-guest-dkms, 
virtualbox-guest-modules, zfs-dkms, zfs-modules
  Depends: kmod, linux-base (>= 4.5ubuntu1~16.04.1), 
linux-modules-5.3.0-46-generic
  Recommends: grub-pc | grub-efi-amd64 | grub-efi-ia32 | grub | lilo, 
initramfs-tools | linux-initramfs-tool
  Suggests: fdutils, linux-hwe-doc-5.3.0 | linux-hwe-source-5.3.0, 
linux-hwe-tools, linux-headers-5.3.0-46-generic
  Conflicts: linux-image-unsigned-5.3.0-46-generic
  Filename: 
pool/main/l/linux-signed-hwe/linux-image-5.3.0-46-generic_5.3.0-46.38~18.04.1_amd64.deb
  Size: 8729628
  MD5sum: 6d575e91196fe11ac1437d5e12377d92
  SHA1: 88795748a4a757719fa62c950910e510bf6a964a
  SHA256: 1534e292a6e85d42fc0e34e368fde2a42c044cc239b15f18e5ff8ac467bca2af
  Description-en: Signed kernel image generic
   A kernel image for generic.  This version of it is signed with
   Canonical's UEFI/Opal signing key.
  Description-md5: 54a18b1adebc179da3c9e59a5db5fe77
  Supported: 5y

  And from the last 4.15 I had installed before moving to the HWE stack:
  Package: linux-image-4.15.0-99-generic
  Architecture: amd64
  Version: 4.15.0-99.100
  Built-Using: linux (= 4.15.0-99.100)
  Priority: optional
  Section: kernel
  Source: linux-signed
  Origin: Ubuntu
  Maintainer: Canonical Kernel Team 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 8213
  Provides: aufs-dkms, fuse-module, ivtv-modules, kvm-api-4, linux-image, 
redhat-cluster-modules, spl-dkms, spl-modules, virtualbox-guest-modules, 
zfs-dkms, zfs-modules
  Depends: kmod, linux-base (>= 4.5ubuntu1~16.04.1), 
linux-modules-4.15.0-99-generic
  Recommends: grub-pc | grub-efi-amd64 | grub-efi-ia32 | grub | lilo, 
initramfs-tools | linux-initramfs-tool
  Suggests: fdutils, linux-doc-4.15.0 | linux-source-4.15.0, linux-tools, 
linux-headers-4.15.0-99-generic
  Conflicts: linux-image-unsigned-4.15.0-99-generic
  Filename: 
pool/main/l/linux-signed/linux-image-4.15.0-99-generic_4.15.0-99.100_amd64.deb
  Size: 8003012
  MD5sum: 251da0e19f02f3af93bc3de89bf738c1
  SHA1: ad385f85faaad98e80f1886fcb29d16d9626bfa3
  SHA256: e17bb925a2266e2b709835e08fcc73aab57a1d29261a3dd0156ed7ced6fc9ccc
  Description-en: Signed kernel image generic
   A kernel image for generic.  This version of it is signed with
   Canonical's UEFI/Opal signing key.
  Description-md5: 54a18b1ad

[Kernel-packages] [Bug 1870189] Re: initramfs does not get loaded

[David Baird]

Hmmm, I am not using the ISO, but rather the pre-installed cloudimg, and
I am not so sure it is actually fixed. I just tried out the latest one,
and can confirm the issue still persists with it:

https://cloud-images.ubuntu.com/focal/20200430.1/focal-server-cloudimg-
amd64.img

Here is the output from booting:

[0.00] Linux version 5.4.0-28-generic (buildd@lgw01-amd64-036) (gcc 
version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #32-Ubuntu SMP Wed Apr 22 17:40:10 UTC 
2020 (Ubuntu 5.4.0-28.32-generic 5.4.30)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=PARTUUID=be1f3b17-864d-49f8-8249-5fb0edc7e606 ro console=tty1 
console=ttyS0 panic=-1
...
[0.999771] VFS: Cannot open root device 
"PARTUUID=be1f3b17-864d-49f8-8249-5fb0edc7e606" or unknown-block(0,0): error -6
[1.001738] Please append a correct "root=" boot option; here are the 
available partitions:
[1.003295] 0b00 1048575 sr0
[1.003295]  driver: sr
[1.004578] Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)
[1.006119] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.4.0-28-generic 
#32-Ubuntu
[1.007522] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
[1.009254] Call Trace:
[1.009790]  dump_stack+0x6d/0x9a
[1.010488]  panic+0x101/0x2e3
[1.011137]  mount_block_root+0x23f/0x2e8
[1.011931]  mount_root+0x38/0x3a
[1.012624]  prepare_namespace+0x13f/0x194
[1.013443]  kernel_init_freeable+0x231/0x255
[1.014319]  ? rest_init+0xb0/0xb0
[1.015018]  kernel_init+0xe/0x100
[1.015721]  ret_from_fork+0x35/0x40
[1.016842] Kernel Offset: 0x1ac0 from 0x8100 (relocation 
range: 0x8000-0xbfff)


Upon reboot, initrdfail will now be set, and therefore it will actually load 
the initrd on the second reboot. But, because I am trying to configure the 
machine on the first boot using cloud-init NoCloud, it needs to actually work 
on the first boot. (Anyways, I think it's a moot point that first time booting 
should work.)

In the above, the "panic=-1" followed by "Cannot open root device"
indicates that there is still something amiss, at least with the
cloudimg distribution. I can file a different ticket for cloudimg, if it
would be more appropriate. Please advise. Thanks!

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

Title:
  initramfs does not get loaded

Status in grub2 package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
  20.04 by “do-release-upgrade –d”.

  Then the latest Ubuntu v5.6 kernel was installed from
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
  reboot was performed, a panic with the v5.6 kernel occured because the
  rootfs can not be found.

  It turns out by default, initramfs does not get loaded:

  /boot/grub/grub.cfg:
  menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os 
$menuentry_id_option 'gnulinux-simple-3d2737e8-
  b95a-42bf-bac1-bb6fb4cda87f' {
  …
  if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic 
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro  console=tty1 
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled 
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
  else
linux /boot/vmlinuz-5.6.0-050600-generic 
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro  console=tty1 
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled 
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
  fi
  initrdfail
  }

  
  As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally, 
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit 
the “fail to mount rootfs” panic and the kernel will automatically reboot….   

  Also, the “initrdfail” here marks initrdfail=1, so when the kernel
  boots for the 2nd time, the kernel should successfully boot up.  Next,
  when the kernel boots for the 3rd time, it panics again since the
  userspace program resets initrdfail to 0, and next time when the
  kernel boots, it can boot up successfully -- this
  “panic/success/panic/success” pattern repeats forever…

  
  The linux-azure kernels are not affected since they have the vmbus driver and 
storage drivers built-in (i.e. “=y”):
  /boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
  /boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
  /boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
  /boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
  /boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
  /boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
  The v5.6 kernel u

[Kernel-packages] [Bug 1826125] Re: Dell XPS 13 9380 flickering (Whiskey Lake)

[Paulo Matos]

As mentioned in freedesktop's gitlab, this issue re-occurred after the
upgrade to 20.04

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

Title:
  Dell XPS 13 9380 flickering  (Whiskey Lake)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers
  to the point of being totally unusable.

  I have upgraded since to 18.10 and 19.04 with no changes. I have tried
  several combinations of the i915 parameters fastboot, enable_rc6 and
  enable_fbc to no avail.

  Examples of flickering are here:
  https://photos.app.goo.gl/1PkL2HrjMBP41aML9
  https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1430 F pulseaudio
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X31
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-13 (10 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 9380
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem 
root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1 
i915.enable_rc6=0 vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1035-oem N/A
   linux-backports-modules-4.15.0-1035-oem  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 4.15.0-1035-oem x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1826125/+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