date:20210527

[Kernel-packages] [Bug 1929920] [NEW] 'sudo' commands fail with "already defined" errors on oracle images

2021-05-27 Thread Khaled El Mously

Public bug reported:

The problem was first noticed when it caused these errors:

http://10.246.72.9/5.11.0-1007.7-oracle/hirsute-linux-oracle-oracle-
amd64-5.11.0-VM.Standard2.1-ubuntu_qrt_kernel_security/ubuntu_qrt_kernel_security/results/ubuntu_qrt_kernel_security
.test-kernel-security.py/debug/ubuntu_qrt_kernel_security.test-kernel-
security.py.DEBUG.html


and Sam has narrowed it down to a problem running sudo commands, which
all fail with the error:

Alias "x" already defined


This affects the 2021-05-10 SRU cycle. More info on this Trello card:

https://trello.com/c/dZXTo7L3/1257-alias-x-already-defined-error-
triggered-by-sudo-in-oracle-hirsute

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


** Tags: sru-20210510

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

** No longer affects: kernel-sru-workflow

** Tags added: sru-20210510

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

Title:
  'sudo' commands fail with "already defined" errors on oracle images

Status in linux package in Ubuntu:
  New

Bug description:
  The problem was first noticed when it caused these errors:

  http://10.246.72.9/5.11.0-1007.7-oracle/hirsute-linux-oracle-oracle-
  
amd64-5.11.0-VM.Standard2.1-ubuntu_qrt_kernel_security/ubuntu_qrt_kernel_security/results/ubuntu_qrt_kernel_security
  .test-kernel-security.py/debug/ubuntu_qrt_kernel_security.test-kernel-
  security.py.DEBUG.html


  and Sam has narrowed it down to a problem running sudo commands, which
  all fail with the error:

  Alias "x" already defined

  
  This affects the 2021-05-10 SRU cycle. More info on this Trello card:

  https://trello.com/c/dZXTo7L3/1257-alias-x-already-defined-error-
  triggered-by-sudo-in-oracle-hirsute

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

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

[Kernel-packages] [Bug 1929899] [NEW] libbpf.so.0 missing version information

2021-05-27 Thread Matthew Berryman

Public bug reported:

➜ ip address
ip: /lib/x86_64-linux-gnu/libbpf.so.0: no version information available 
(required by ip)
ip: /lib/x86_64-linux-gnu/libbpf.so.0: no version information available 
(required by ip)
ip: /lib/x86_64-linux-gnu/libbpf.so.0: no version information available 
(required by ip)
ip: /lib/x86_64-linux-gnu/libbpf.so.0: no version information available 
(required by ip)
ip: symbol lookup error: ip: undefined symbol: bpf_object__open_file, version 
LIBBPF_0.0.6

➜ lsb_release -rd
Description:Ubuntu 21.04
Release:21.04

➜ sudo apt-cache policy libbpf0:amd64
libbpf0:
  Installed: 1:0.3-2ubuntu1
  Candidate: 1:0.3-2ubuntu1
  Version table:
 *** 1:0.3-2ubuntu1 500
500 http://au.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status

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

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

Title:
  libbpf.so.0 missing version information

Status in libbpf package in Ubuntu:
  New

Bug description:
  ➜ ip address
  ip: /lib/x86_64-linux-gnu/libbpf.so.0: no version information available 
(required by ip)
  ip: /lib/x86_64-linux-gnu/libbpf.so.0: no version information available 
(required by ip)
  ip: /lib/x86_64-linux-gnu/libbpf.so.0: no version information available 
(required by ip)
  ip: /lib/x86_64-linux-gnu/libbpf.so.0: no version information available 
(required by ip)
  ip: symbol lookup error: ip: undefined symbol: bpf_object__open_file, version 
LIBBPF_0.0.6

  ➜ lsb_release -rd
  Description:  Ubuntu 21.04
  Release:  21.04

  ➜ sudo apt-cache policy libbpf0:amd64
  libbpf0:
Installed: 1:0.3-2ubuntu1
Candidate: 1:0.3-2ubuntu1
Version table:
   *** 1:0.3-2ubuntu1 500
  500 http://au.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Kernel-packages] [Bug 1929833] Re: bluez: meshctl missing

2021-05-27 Thread Daniel van Vugt

** Tags added: impish

** Changed in: bluez (Ubuntu)
   Importance: Undecided => Medium

** Changed in: bluez (Ubuntu)
   Status: New => Triaged

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

Title:
  bluez: meshctl missing

Status in bluez package in Ubuntu:
  Triaged

Bug description:
  bluez has added a new tool for BT mesh handling.

  Debian has a new binary package: https://packages.debian.org/bullseye
  /bluez-meshd

  Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973579

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

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

[Kernel-packages] [Bug 1928047] Re: AX201 BT will cause system could not enter S0i3

2021-05-27 Thread AceLan Kao

** Tags removed: verification-needed-focal
** Tags added: verification-done-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/1928047

Title:
  AX201 BT will cause system could not enter S0i3

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]
  Platforms with AX201 BT fail to pass the power consumption tests

  [Fix]
  Intel provides us the patch to fix it.
  
https://patchwork.kernel.org/project/intel-gfx/patch/20210325120947.11950-1-anshuman.gu...@intel.com/

  [Test]
  Verified on the Dell machines with AX201 BT on them.

  [Where problems may occur]
  This patch extend the s0ix fix for gen8 and gen11 to all PCHs. Not sure if it 
will lead to regressions on different PCH.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1928047/+subscriptions

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

[Kernel-packages] [Bug 1896578] Re: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations

2021-05-27 Thread Matthew Ruffell

Hi Evan,

As I mentioned in my previous message, I submitted the patches to the
Ubuntu kernel mailing list for SRU.

These patches have now gotten 2 acks [1][2] from senior kernel team
members, and the patches have now been applied [3] to the 4.15, 5.4, 5.8
and 5.11 kernels.

[1] https://lists.ubuntu.com/archives/kernel-team/2021-May/120475.html
[2] https://lists.ubuntu.com/archives/kernel-team/2021-May/120799.html
[3] https://lists.ubuntu.com/archives/kernel-team/2021-May/120800.html

This is what is going to happen next. Next week, between the 31st of May
and 4th of June, the kernel team will build the next kernel update, and
place it in -proposed for testing.

As soon as these kernels enter -proposed, we need to install and test
Raid10 in these new kernels as much as possible. The testing and
verification window is between the 7th and 18th of June.

If all goes well, we can mark the launchpad bug as verified, and we will
see a release to -updates around the 21st of June, give or take a few
days if any CVEs turn up.

The schedule is on https://kernel.ubuntu.com/ if anything were to
change.

I will write back once the next kernel update is in -proposed, likely
early to mid next week. I would really, really appreciate it if you
could help test the kernels when they arrive in -proposed, as I really
don't want to introduce any more regressions.

Thanks,
Matthew

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

Title:
  raid10: Block discard is very slow, causing severe delays for mkfs and
  fstrim operations

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1896578

  [Impact]

  Block discard is very slow on Raid10, which causes common use cases
  which invoke block discard, such as mkfs and fstrim operations, to
  take a very long time.

  For example, on a i3.8xlarge instance on AWS, which has 4x 1.9TB NVMe
  devices which support block discard, a mkfs.xfs operation on Raid 10
  takes between 8 to 11 minutes, where the same mkfs.xfs operation on
  Raid 0, takes 4 seconds.

  The bigger the devices, the longer it takes.

  The cause is that Raid10 currently uses a 512k chunk size, and uses
  this for the discard_max_bytes value. If we need to discard 1.9TB, the
  kernel splits the request into millions of 512k bio requests, even if
  the underlying device supports larger requests.

  For example, the NVMe devices on i3.8xlarge support 2.2TB of discard
  at once:

  $ cat /sys/block/nvme0n1/queue/discard_max_bytes
  2199023255040
  $ cat /sys/block/nvme0n1/queue/discard_max_hw_bytes
  2199023255040

  Where the Raid10 md device only supports 512k:

  $ cat /sys/block/md0/queue/discard_max_bytes
  524288
  $ cat /sys/block/md0/queue/discard_max_hw_bytes
  524288

  If we perform a mkfs.xfs operation on the /dev/md array, it takes over
  11 minutes and if we examine the stack, it is stuck in
  blkdev_issue_discard()

  $ sudo cat /proc/1626/stack
  [<0>] wait_barrier+0x14c/0x230 [raid10]
  [<0>] regular_request_wait+0x39/0x150 [raid10]
  [<0>] raid10_write_request+0x11e/0x850 [raid10]
  [<0>] raid10_make_request+0xd7/0x150 [raid10]
  [<0>] md_handle_request+0x123/0x1a0
  [<0>] md_submit_bio+0xda/0x120
  [<0>] __submit_bio_noacct+0xde/0x320
  [<0>] submit_bio_noacct+0x4d/0x90
  [<0>] submit_bio+0x4f/0x1b0
  [<0>] __blkdev_issue_discard+0x154/0x290
  [<0>] blkdev_issue_discard+0x5d/0xc0
  [<0>] blk_ioctl_discard+0xc4/0x110
  [<0>] blkdev_common_ioctl+0x56c/0x840
  [<0>] blkdev_ioctl+0xeb/0x270
  [<0>] block_ioctl+0x3d/0x50
  [<0>] __x64_sys_ioctl+0x91/0xc0
  [<0>] do_syscall_64+0x38/0x90
  [<0>] entry_SYSCALL_64_after_hwframe+0x44/0xa9

  [Fix]

  Xiao Ni has developed a patchset which resolves the block discard
  performance problems. These commits have now landed in 5.13-rc1.

  commit cf78408f937a67f59f5e90ee8e6cadeed7c128a8
  Author: Xiao Ni 
  Date:   Thu Feb 4 15:50:43 2021 +0800
  Subject: md: add md_submit_discard_bio() for submitting discard bio
  Link: 
https://github.com/torvalds/linux/commit/cf78408f937a67f59f5e90ee8e6cadeed7c128a8

  commit c2968285925adb97b9aa4ede94c1f1ab61ce0925
  Author: Xiao Ni 
  Date:   Thu Feb 4 15:50:44 2021 +0800
  Subject: md/raid10: extend r10bio devs to raid disks
  Link: 
https://github.com/torvalds/linux/commit/c2968285925adb97b9aa4ede94c1f1ab61ce0925

  commit f2e7e269a7525317752d472bb48a549780e87d22
  Author: Xiao Ni 
  Date:   Thu Feb 4 15:50:45 2021 +0800
  Subject: md/raid10: pull the code that wait for blocked dev into one function
  Link: 
https://github.com/torvalds/linux/commit/f2e7e269a7525317752d472bb48a549780e87d22

  commit d30588b2731fb01e1616cf16c3fe79

[Kernel-packages] [Bug 1907262] Re: raid10: discard leads to corrupted file system

2021-05-27 Thread Matthew Ruffell

Hi Thimo,

As I mentioned in my previous message, I submitted the patches to the
Ubuntu kernel mailing list for SRU.

These patches have now gotten 2 acks [1][2] from senior kernel team
members, and the patches have now been applied [3] to the 4.15, 5.4, 5.8
and 5.11 kernels.

[1] https://lists.ubuntu.com/archives/kernel-team/2021-May/120475.html
[2] https://lists.ubuntu.com/archives/kernel-team/2021-May/120799.html
[3] https://lists.ubuntu.com/archives/kernel-team/2021-May/120800.html

This is what is going to happen next. Next week, between the 31st of May
and 4th of June, the kernel team will build the next kernel update, and
place it in -proposed for testing.

As soon as these kernels enter -proposed, we need to install and test
Raid10 in these new kernels as much as possible. The testing and
verification window is between the 7th and 18th of June.

If all goes well, we can mark the launchpad bug as verified, and we will
see a release to -updates around the 21st of June, give or take a few
days if any CVEs turn up.

The schedule is on https://kernel.ubuntu.com/ if anything were to
change.

I will write back once the next kernel update is in -proposed, likely
early to mid next week. I would really, really appreciate it if you
could help test the kernels when they arrive in -proposed, as I really
don't want to introduce any more regressions.

Thanks,
Matthew

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

Title:
  raid10: discard leads to corrupted file system

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Released

Bug description:
  Seems to be closely related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578

  After updating the Ubuntu 18.04 kernel from 4.15.0-124 to 4.15.0-126
  the fstrim command triggered by fstrim.timer causes a severe number of
  mismatches between two RAID10 component devices.

  This bug affects several machines in our company with different HW
  configurations (All using ECC RAM). Both, NVMe and SATA SSDs are
  affected.

  How to reproduce:
   - Create a RAID10 LVM and filesystem on two SSDs
  mdadm -C -v -l10 -n2 -N "lv-raid" -R /dev/md0 /dev/nvme0n1p2 
/dev/nvme1n1p2
  pvcreate -ff -y /dev/md0
  vgcreate -f -y VolGroup /dev/md0
  lvcreate -n root-L 100G -ay -y VolGroup
  mkfs.ext4 /dev/VolGroup/root
  mount /dev/VolGroup/root /mnt
   - Write some data, sync and delete it
  dd if=/dev/zero of=/mnt/data.raw bs=4K count=1M
  sync
  rm /mnt/data.raw
   - Check the RAID device
  echo check >/sys/block/md0/md/sync_action
   - After finishing (see /proc/mdstat), check the mismatch_cnt (should be 0):
  cat /sys/block/md0/md/mismatch_cnt
   - Trigger the bug
  fstrim /mnt
   - Re-Check the RAID device
  echo check >/sys/block/md0/md/sync_action
   - After finishing (see /proc/mdstat), check the mismatch_cnt (probably in 
the range of N*1):
  cat /sys/block/md0/md/mismatch_cnt

  After investigating this issue on several machines it *seems* that the
  first drive does the trim correctly while the second one goes wild. At
  least the number and severity of errors found by a  USB stick live
  session fsck.ext4 suggests this.

  To perform the single drive evaluation the RAID10 was started using a single 
drive at once:
mdadm --assemble /dev/md127 /dev/nvme0n1p2
mdadm --run /dev/md127
fsck.ext4 -n -f /dev/VolGroup/root

vgchange -a n /dev/VolGroup
mdadm --stop /dev/md127

mdadm --assemble /dev/md127 /dev/nvme1n1p2
mdadm --run /dev/md127
fsck.ext4 -n -f /dev/VolGroup/root

  When starting these fscks without -n, on the first device it seems the
  directory structure is OK while on the second device there is only the
  lost+found folder left.

  Side-note: Another machine using HWE kernel 5.4.0-56 (after using -53
  before) seems to have a quite similar issue.

  Unfortunately the risk/regression assessment in the aforementioned bug
  is not complete: the workaround only mitigates the issues during FS
  creation. This bug on the other hand is triggered by a weekly service
  (fstrim) causing severe file system corruption.

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

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

[Kernel-packages] [Bug 1921632] Re: build module CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m for 5.11, 5.13-rc2 and later

2021-05-27 Thread Hui Wang

@mesouug,

OK, got it.

@gadydm,

Yes, it does.

thx.


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

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

Title:
  build module CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m for 5.11,
  5.13-rc2 and later

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Hirsute:
  Fix Committed
Status in linux source package in Impish:
  Confirmed

Bug description:
  [Impact]
  Ubuntu users ran the kernel on the Dell soundwire audio machines,
  the dmesg shows the audio mchine driver is not found, then the
  audio fails to initialize

  [Fix]
  Enable the intel soundwire audio machine driver and some related
  codec driver.

  [Test]
  run fakeroot debian/rules clean updateconfigs, and check the
  config.common.ubuntu, the content is not changed.
  Build the kernel with this patch applied, the soundwire audio
  machine driver is built.

  
  [Where problems could occur]
  This could possibly introduce the building failure, I tested it,
  so far no failure.

  
  See also
  https://bugzilla.kernel.org/show_bug.cgi?id=212465

  Default kernel from
  https://cdimage.ubuntu.com/kubuntu/daily-live/20210327/
  and also upstream kernel
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.12-rc4/

  tested and both do not work.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D7c', 
'/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2021-03-28 (0 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210326)
  MachineType: HP HP Spectre x360 Convertible 13-aw2xxx
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-11-generic 
root=/dev/mapper/sys-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-11-generic N/A
   linux-backports-modules-5.11.0-11-generic  N/A
   linux-firmware 1.195
  Tags:  hirsute
  Uname: Linux 5.11.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/08/2020
  dmi.bios.release: 15.10
  dmi.bios.vendor: AMI
  dmi.bios.version: F.10
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8709
  dmi.board.vendor: HP
  dmi.board.version: 31.30
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 31.30
  dmi.modalias: 
dmi:bvnAMI:bvrF.10:bd12/08/2020:br15.10:efr31.30:svnHP:pnHPSpectrex360Convertible13-aw2xxx:pvr:rvnHP:rn8709:rvr31.30:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-aw2xxx
  dmi.product.sku: 2G2D8EA#ABU
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1851749] Re: Frequently getting thermal warnings and cpu throttling messages in syslog

2021-05-27 Thread Luigi Calligaris

I am affected as well on a Dell P74G Inspiron 7460 with an i7-7500U CPU
@ 2.70GHz and an integrated GPU + an Nvidia GPU using the NVidia
drivers.


According from information I found here

https://icecat.biz/p/dell/w56752561pth-gld/inspiron-
notebooks-7460-33552288.html

the TDPs of my CPU are:

Thermal Design Power (TDP) 15 W
Configurable TDP-up frequency 2.9 GHz
Configurable TDP-up25 W
Configurable TDP-down 7.5 W


CPU version as read from /proc/cpuinfo:

vendor_id   : GenuineIntel
cpu family  : 6
model   : 142
model name  : Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz
stepping: 9
microcode   : 0xde


>From lspci, detail of the GPUs:

00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
01:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 940MX] (rev a2)


My Kernel:

uname -a
Linux [redacted] 5.4.0-66-generic #74-Ubuntu SMP Wed Jan 27 22:54:38 UTC 2021 
x86_64 x86_64 x86_64 GNU/Linux


Output of the commands recommended above:

dmidecode looks odd returning info about WiFi:

sudo dmidecode -H 11
# dmidecode 3.2
Getting SMBIOS data from sysfs.
SMBIOS 2.8 present.
85 structures occupying 5497 bytes.
Table at 0x000E9CA0.

Handle 0x000B, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: JNGFF1 - WLAN/BT/Wigig CONN
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other


sudo modprobe msr
sudo rdmsr -f 29:24 -d 0x1a2
2


Reproducing the issue:

stress -c 8
stress: info: [48012] dispatching hogs: 8 cpu, 0 io, 0 vm, 0 hdd

Dmesg output:

[17674.962910] mce: CPU3: Core temperature above threshold, cpu clock throttled 
(total events = 3987)
[17674.962910] mce: CPU1: Core temperature above threshold, cpu clock throttled 
(total events = 3986)
[17674.962912] mce: CPU0: Package temperature above threshold, cpu clock 
throttled (total events = 7491)
[17674.962913] mce: CPU2: Package temperature above threshold, cpu clock 
throttled (total events = 7491)
[17674.962914] mce: CPU1: Package temperature above threshold, cpu clock 
throttled (total events = 7487)
[17674.962915] mce: CPU3: Package temperature above threshold, cpu clock 
throttled (total events = 7491)
[17674.966955] mce: CPU1: Core temperature/speed normal
[17674.966956] mce: CPU3: Core temperature/speed normal
[17674.966957] mce: CPU2: Package temperature/speed normal
[17674.966958] mce: CPU0: Package temperature/speed normal
[17674.966958] mce: CPU3: Package temperature/speed normal
[17674.966960] mce: CPU1: Package temperature/speed normal

Turbostat line being used (NOTE: 100 milliseconds interval):
turbostat --quiet --Summary --show 
Busy%,Bzy_MHz,PkgTmp,PkgWatt,CorWatt,GFXWatt,Time_Of_Day_Seconds --interval 0.1


Output of turbostat across the beginning of stress:

Time_Of_Day_Seconds Busy%   Bzy_MHz PkgTmp  PkgWatt CorWatt GFXWatt
1622157712.441769   9.23795 51  1.750.200.11
1622157712.542624   10.77   711 52  1.840.210.12
1622157712.643427   8.98708 51  1.800.170.07
1622157712.744178   12.97   746 51  1.900.240.13
1622157712.850717   13.32   712 51  1.680.200.11 <--- START 
STRESS
1622157712.951114   95.99   258775  12.69   10.76   0.17
1622157713.051319   99.59   350082  19.36   17.56   0.14
1622157713.151571   99.65   350085  19.54   17.66   0.18
1622157713.252241   99.65   350088  19.76   17.82   0.14
1622157713.352490   99.59   350090  19.66   17.76   0.17
1622157713.452694   99.65   350090  19.22   17.54   0.08
1622157713.552947   99.59   350091  20.09   18.09   0.14


Output of turbostat across the throttle trigger event:
Time_Of_Day_Seconds Busy%   Bzy_MHz PkgTmp  PkgWatt CorWatt GFXWatt
1622157718.567121   99.65   350095  19.97   17.94   0.16
1622157718.667327   99.68   350095  19.79   18.05   0.13
1622157718.767572   99.62   350095  19.76   17.94   0.13
1622157718.867776   99.65   350096  19.81   18.00   0.16
1622157718.968029   99.65   350095  20.01   17.98   0.17
1622157719.068238   99.65   350096  20.13   18.29   0.17
1622157719.169153   99.65   350097  20.35   18.44   0.21
1622157719.269796   99.65   350097  20.12   18.24   0.20 <--- 
THRESHOLD TRIGGERED
1622157719.370056   99.59   335590  18.04   15.99   0.18
1622157719.470352   99.53   311786  14.53   12.69   0.17
1622157719.572124   99.61   311786  14.33   12.56   0.09
1622157719.672498   99.61   310385  14.67   12.78   0.16
1622157719.772984   99.63   311885  14.46   12.71   0.13
1622157719.873219   99.62   311384  14.63   12.71   0.14
1622157719.973515   99.60   312585  14.54   12.74   0.13

--

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-raspi2/4.15.0.1086.83)

2021-05-27 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-meta-raspi2 (4.15.0.1086.83) for 
bionic have finished running.
The following regressions have been reported in tests triggered by the package:

bbswitch/unknown (arm64)
langford/0.0.20130228-5ubuntu1 (armhf)
lttng-modules/unknown (arm64)
ddcci-driver-linux/unknown (arm64)
rtl8821ce/5.5.2.1-0ubuntu3~18.04.1 (armhf)
lime-forensics/unknown (arm64)
asic0x/unknown (arm64)
langford/unknown (arm64)
nat-rtsp/unknown (arm64)
r8168/8.045.08-2ubuntu1 (armhf)
r8168/unknown (arm64)
dm-writeboost/unknown (arm64)
ktap/unknown (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-meta-raspi2

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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

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

[Kernel-packages] [Bug 1867465] Re: Installer disconnects wifi (after choosing download while installing, 3rd party)

2021-05-27 Thread MarkF

@Piotr, I've given up on this. I was less concerned about security than
I was about the user experience. If the installer knows it's going to
drop the connection, why not inform the user of this? It's really
unnerving to have your connection drop, and think there's some kind of
bug going on. It's little satisfaction to learn later it's not a bug.

I don't know what it is with *buntu, but I've given up. They don't care
about attracting more people. It's a circle-the-wagons approach. I say
it to anyone who will listen: Re-open Bug#1. *buntu has lost its way.
Shuttleworth should look at his contemporaries (who've moved on to
launching cars into space, and being the richest men in the world). He
should ask why he got left behind. Windows 10 was a windfall to the
Linux Desktop, and we're still missing the point.

I've moved on to a non-buntu based distro. Peace be upon all.

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

Title:
  Installer disconnects wifi (after choosing download while installing,
  3rd party)

Status in systemd:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Won't Fix

Bug description:
  ISO testing 20.04 daily 20200314. On the Live desktop I connect to
  wifi. When I click the install icon, and choose to install 3rd party
  (leaving download while installing checked), the wifi disconnects.

  I rebooted and tried again to make sure it wasn't something random.
  (It happened exactly the same.).

  This is an older Dell E5420 laptop with Broadcom BCM4313 wireless
  card. (Today's Lubuntu had a wifi-related problem too. I couldn't
  connect to wifi upon reboot after install. I had to reboot a 2nd time
  for it to work. I reported that to their Discourse forum, not reported
  as a bug yet.).

  I apologize that I don't know the package or pid to report this for.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-14.17-lowlatency 5.4.18
  Uname: Linux 5.4.0-14-lowlatency x86_64
  NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.441
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat Mar 14 20:29:15 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:049b]
  LiveMediaBuild: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314)
  MachineType: Dell Inc. Latitude E5420
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/ubuntustudio.seed 
initrd=/casper/initrd quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/26/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0H5TG2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/26/2013:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1867465/+subscriptions

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

[Kernel-packages] [Bug 1867465] Re: Installer disconnects wifi (after choosing download while installing, 3rd party)

2021-05-27 Thread Piotr

@Dimitri John Ledkov I had also this issue. I know now that this will be
not fixed. This problem is not affect my security? I am safe? This
worried me because Network Manager save wi-fi password. Can you answer?

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

Title:
  Installer disconnects wifi (after choosing download while installing,
  3rd party)

Status in systemd:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Won't Fix

Bug description:
  ISO testing 20.04 daily 20200314. On the Live desktop I connect to
  wifi. When I click the install icon, and choose to install 3rd party
  (leaving download while installing checked), the wifi disconnects.

  I rebooted and tried again to make sure it wasn't something random.
  (It happened exactly the same.).

  This is an older Dell E5420 laptop with Broadcom BCM4313 wireless
  card. (Today's Lubuntu had a wifi-related problem too. I couldn't
  connect to wifi upon reboot after install. I had to reboot a 2nd time
  for it to work. I reported that to their Discourse forum, not reported
  as a bug yet.).

  I apologize that I don't know the package or pid to report this for.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-14.17-lowlatency 5.4.18
  Uname: Linux 5.4.0-14-lowlatency x86_64
  NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.441
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat Mar 14 20:29:15 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:049b]
  LiveMediaBuild: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314)
  MachineType: Dell Inc. Latitude E5420
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/ubuntustudio.seed 
initrd=/casper/initrd quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/26/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0H5TG2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/26/2013:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1867465/+subscriptions

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

[Kernel-packages] [Bug 1928600] Re: [amdgpu] Gnome locks up with artifacts on screen and [drm:amdgpu_dm_commit_planes [amdgpu]] ERROR Waiting for fences timed out!

2021-05-27 Thread Paul Tansom

Thought I'd better give an update on progress from my end. The above
task is proving more of a challenge than hoped (not helped by time out
on customer sites using different hardware).

The stock 5.8 series kernel (linux-image-5.8.0-53-generic) is
reasonably, but not completely, stable. I can generally manage a few
days without a lock up and that is pretty much always on a resume or
suspend. The issue gets progressively worse as the kernel version
increases so I decided to start with the 5.11 series. The first
available to download was RC2, and that ran fine for most of a day, but
then locked up on a resume and several reboots failed to get to the
desktop, so instead of moving on to RC3 as I was expecting I'm backing
off to the 5.8 series RC2 to start from there and work my way up. Given
how long it can be between lock ups even on the current version this may
be a slightly long winded process - hence adding some notes now.

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

Title:
  [amdgpu] Gnome locks up with artifacts on screen and
  [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences
  timed out!

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With this hardware configuration this issue has been a problem only
  when suspending or resuming from suspend under 20.04. Having decided
  to upgrade through 20.10 to 21.04 to see if things improve enough to
  help me identify which package to report a bug against things have
  become significantly worse.

  With 20.04 it was an occasional occurrence found when returning to the
  computer. Either it was stuck in the suspend process with a blank
  screen or one with artefacts on, or it would start the resume and then
  lock.

  On the upgrade to 21.04 (I didn't stop on 20.10 for more than enough
  time to tidy up and upgrade again), the system seemed improved
  initially - including notably improved boot times (no idea if that is
  related). After a bit of checking things out I went to enable the PPAs
  that had been disabled (Teamviewer, Nextcloud, Anydesk and Chrome -
  all of which have been installed after the problems were initially
  noted). When the window to authenticate popped up the screen filled
  with artefacts and I had to reset. After several attempts to reboot
  into a working desktop variously booting to artefacts, or getting
  artefacts immediately after logging in (usually when opening and
  maximising a terminal to capture the logs for later) I managed to
  change from Wayland to X.Org and logged in successfully with no
  problems for the rest of the day (including a Jitsi meeting lasting
  about 4 hours or more). The next day (today) suspend and resume is
  causing problems as before, boot has slowed down again (again, no idea
  if this is related).

  Compared to 20.04 there are more frequent locks (it had reached one
  every other day, but now it is more frequent - 4 today so far).

  Key things I have noted:

  - it is significantly worse under Wayland (to the point of being unusable)
  - it usually happens during the suspend / resume, but not always
  - when using the desktop it will always related to moving or resizing a window
  - leaving the PC powered off for a few minutes helps to get a reliable reboot 
(as in, if you reboot too quickly you get artefacts immediately after logging 
in)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 16 19:23:00 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-16 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (1 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2020-10-16 (214 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   lono wireless extensions.
   
   enp34s0   no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7B79
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=2fd8e91e-4658-4060-bc40-5db44750fc91 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware

[Kernel-packages] [Bug 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged

2021-05-27 Thread Launchpad Bug Tracker

This bug was fixed in the package pulseaudio - 1:14.2-2ubuntu2

---
pulseaudio (1:14.2-2ubuntu2) impish; urgency=medium

  * d/p/0016-check_off_profile_when_switching_profile.patch
  * d/p/0017-add_dynamic_priority_bonus_base_for_alsa_profiles.patch
Fix a "Rear Mic" always showing on input list when using dual codec.
(LP: #1929371)

 -- Jeremy Szu   Tue, 25 May 2021 12:41:39
+

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

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

Title:
  [SRU] there is always a "Rear Microphone - Built-in Audio" option on
  the input device list even if the microphone is unplugged

Status in OEM Priority Project:
  Triaged
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Hirsute:
  Fix Released
Status in pulseaudio source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]
  In Lenovo P520, which using a codec for front panel, the other codec for rear 
panel and both are on a same card.

  In this case, the rear Mic will present on input devices of "Sound
  Settings" even if attaching nothing to rear mic jack.

  [Fix]
  For alsa-ucm-conf part, the Mic 2 should use "Rear Mic Jack" as JackControl 
because of
  ```
control.18 {
iface CARD
name 'Rear Mic Jack'
value true
comment {
access read
type BOOLEAN
count 1
}
}
  ```
  After applying "Rear Mic Jack", the rear Mic will not always there anymore 
but it's not there as well if hot-plugging audio device on rear mic. Thus, it 
needs to change pulseaudio to handle if all devices are off cases.

  For pulseaudio, if there is no any audio devices attached, then
  attaching an input device on rear mic jack. The port will not be
  selected automatically because the profiles is off. It needs patch
  pulseaudio to check off profiles (for dual codec case).

  [Test]
  After applying these patches, the rear mic jack works good in all cases (boot 
without mic and then attach mic, boot with mic and then hotplug it) and other 
functions (line-in / line-out) work pretty well.

  [Where problems could occur]
  This change only apply the bonus on below cases:
  ```
  if ((has_input_port && found_available_input_port && !has_output_port) ||
  (has_output_port && found_available_output_port && !has_input_port) ||
  (has_input_port && found_available_input_port && has_output_port && 
found_available_output_port)) 
  ```
  and these cases have been tested.
  If there are some complex codec design then it might cause problem but so far 
we didn't see that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1929371/+subscriptions

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

[Kernel-packages] [Bug 1929870] Re: AMD desktop often fails to resume from deep suspend

2021-05-27 Thread Jacob Abrams

** Attachment added: "kernel log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929870/+attachment/5500782/+files/kern.log

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

Title:
  AMD desktop often fails to resume from deep suspend

Status in linux package in Ubuntu:
  New

Bug description:
  Machine setup:

  Desktop PC
  Ubuntu 21.04
  Linux version 5.11.0-17-generic
  AMD Ryzen 3900X
  Asus X590 PRIME PRO motherboard
  NVIDIA P400 GPU

  Approximately one in every 4 attempts to resume from a deep suspend
  fails. When the issue occurs the fans spin up but the monitor displays
  no output and input devices do not function, the system appears frozen
  and must be restarted using power or reset buttons.

  I have tried using different dNVIDIA isplay drivers (proprietary as
  well as open source) as well as trying an AMD Radeon HD 6450 GPU
  instead of the NVIDIA GPU.

  I have tried the following kernel parameters: processor.max_cstate=1
  rcu_nocbs=0-23

  I have updated the BIOS several times.

  I had similar problems with Ubuntu 20.10.

  I have enabled some additional kernel logging with initcall_debug.

  Fairly consistently the last message printed in the kernel log is from
  the ethernet driver:

  May 27 09:19:43 jacob-tm kernel: [  230.878348] OOM killer enabled.
  May 27 09:19:43 jacob-tm kernel: [  230.878349] Restarting tasks ... 
  May 27 09:19:43 jacob-tm kernel: [  230.879023] usb 5-2.3: USB disconnect, 
device number 4
  May 27 09:19:43 jacob-tm kernel: [  230.879026] usb 5-2.3.1: USB disconnect, 
device number 5
  May 27 09:19:43 jacob-tm kernel: [  230.879285] done.
  May 27 09:19:43 jacob-tm kernel: [  230.879318] PM: suspend exit
  May 27 09:19:43 jacob-tm kernel: [  230.880916] rfkill: input handler enabled
  May 27 09:19:43 jacob-tm kernel: [  230.955727] kauditd_printk_skb: 1 
callbacks suppressed
  May 27 09:19:43 jacob-tm kernel: [  230.955731] audit: type=1400 
audit(1622132383.424:64): apparmor="DENIED" operation="capab
  le" profile="/usr/sbin/cupsd" pid=4418 comm="cupsd" capability=12  
capname="net_admin"
  May 27 09:19:43 jacob-tm kernel: [  230.966192] audit: type=1400 
audit(1622132383.432:65): apparmor="DENIED" operation="capab
  le" profile="/usr/sbin/cups-browsed" pid=4429 comm="cups-browsed" 
capability=23  capname="sys_nice"
  May 27 09:19:43 jacob-tm kernel: [  231.120385] rfkill: input handler disabled
  May 27 09:19:43 jacob-tm kernel: [  231.225924] usb 5-2.3.2: USB disconnect, 
device number 6
  May 27 09:19:43 jacob-tm kernel: [  231.481893] usb 5-2.3.5: USB disconnect, 
device number 7
  May 27 09:19:47 jacob-tm kernel: [  235.009576] igb :05:00.0 enp5s0: igb: 
enp5s0 NIC Link is Up 1000 Mbps Full Duplex, Fl
  ow Control: RX/TX
  May 27 09:19:47 jacob-tm kernel: [  235.009913] IPv6: 
ADDRCONF(NETDEV_CHANGE): enp5s0: link becomes ready

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-17-generic 5.11.0-17.18
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jacob  2024 F pulseaudio
   /dev/snd/controlC0:  jacob  2024 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 27 14:12:33 2021
  InstallationDate: Installed on 2020-10-28 (211 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=f721d5df-ceec-434a-919a-0680ee380996 ro quiet splash initcall_debug 
processor.max_cstate=1 rcu_nocbs=0-23 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware 1.197
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to hirsute on 2021-05-14 (13 days ago)
  dmi.bios.date: 05/08/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3604
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X570-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3604:bd05/08/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:

[Kernel-packages] [Bug 1929870] [NEW] AMD desktop often fails to resume from deep suspend

2021-05-27 Thread Jacob Abrams

Public bug reported:

Machine setup:

Desktop PC
Ubuntu 21.04
Linux version 5.11.0-17-generic
AMD Ryzen 3900X
Asus X590 PRIME PRO motherboard
NVIDIA P400 GPU

Approximately one in every 4 attempts to resume from a deep suspend
fails. When the issue occurs the fans spin up but the monitor displays
no output and input devices do not function, the system appears frozen
and must be restarted using power or reset buttons.

I have tried using different dNVIDIA isplay drivers (proprietary as well
as open source) as well as trying an AMD Radeon HD 6450 GPU instead of
the NVIDIA GPU.

I have tried the following kernel parameters: processor.max_cstate=1
rcu_nocbs=0-23

I have updated the BIOS several times.

I had similar problems with Ubuntu 20.10.

I have enabled some additional kernel logging with initcall_debug.

Fairly consistently the last message printed in the kernel log is from
the ethernet driver:

May 27 09:19:43 jacob-tm kernel: [  230.878348] OOM killer enabled.
May 27 09:19:43 jacob-tm kernel: [  230.878349] Restarting tasks ... 
May 27 09:19:43 jacob-tm kernel: [  230.879023] usb 5-2.3: USB disconnect, 
device number 4
May 27 09:19:43 jacob-tm kernel: [  230.879026] usb 5-2.3.1: USB disconnect, 
device number 5
May 27 09:19:43 jacob-tm kernel: [  230.879285] done.
May 27 09:19:43 jacob-tm kernel: [  230.879318] PM: suspend exit
May 27 09:19:43 jacob-tm kernel: [  230.880916] rfkill: input handler enabled
May 27 09:19:43 jacob-tm kernel: [  230.955727] kauditd_printk_skb: 1 callbacks 
suppressed
May 27 09:19:43 jacob-tm kernel: [  230.955731] audit: type=1400 
audit(1622132383.424:64): apparmor="DENIED" operation="capab
le" profile="/usr/sbin/cupsd" pid=4418 comm="cupsd" capability=12  
capname="net_admin"
May 27 09:19:43 jacob-tm kernel: [  230.966192] audit: type=1400 
audit(1622132383.432:65): apparmor="DENIED" operation="capab
le" profile="/usr/sbin/cups-browsed" pid=4429 comm="cups-browsed" capability=23 
 capname="sys_nice"
May 27 09:19:43 jacob-tm kernel: [  231.120385] rfkill: input handler disabled
May 27 09:19:43 jacob-tm kernel: [  231.225924] usb 5-2.3.2: USB disconnect, 
device number 6
May 27 09:19:43 jacob-tm kernel: [  231.481893] usb 5-2.3.5: USB disconnect, 
device number 7
May 27 09:19:47 jacob-tm kernel: [  235.009576] igb :05:00.0 enp5s0: igb: 
enp5s0 NIC Link is Up 1000 Mbps Full Duplex, Fl
ow Control: RX/TX
May 27 09:19:47 jacob-tm kernel: [  235.009913] IPv6: ADDRCONF(NETDEV_CHANGE): 
enp5s0: link becomes ready

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: linux-image-5.11.0-17-generic 5.11.0-17.18
ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
Uname: Linux 5.11.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  jacob  2024 F pulseaudio
 /dev/snd/controlC0:  jacob  2024 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu May 27 14:12:33 2021
InstallationDate: Installed on 2020-10-28 (211 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
IwConfig:
 lono wireless extensions.
 
 enp5s0no wireless extensions.
 
 docker0   no wireless extensions.
MachineType: System manufacturer System Product Name
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=f721d5df-ceec-434a-919a-0680ee380996 ro quiet splash initcall_debug 
processor.max_cstate=1 rcu_nocbs=0-23 vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.11.0-17-generic N/A
 linux-backports-modules-5.11.0-17-generic  N/A
 linux-firmware 1.197
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to hirsute on 2021-05-14 (13 days ago)
dmi.bios.date: 05/08/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3604
dmi.board.asset.tag: Default string
dmi.board.name: PRIME X570-PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3604:bd05/08/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug hirsute

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

Title:
  AMD desktop often

[Kernel-packages] [Bug 1929868] Re: Should nvidia-driver-XXX-server stop recommending nvidia-settings?

2021-05-27 Thread Camille Rodriguez

That situation occurs as well when installing nvidia-utils-* (in my case
nvidia-utils-450-server), which installs nvidia-settings. See
https://archlinux.org/packages/extra/x86_64/nvidia-settings/. This
requirement is optional and should be omitted on servers, as the same
issue will occur (hibernation, unreachable node, very difficult to
recover)

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

Title:
  Should nvidia-driver-XXX-server stop recommending nvidia-settings?

Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Confirmed

Bug description:
  The nvidia-driver-* packages have a Recommends on nvidia-settings.
  Installing them w/ recommends enabled therefore ends up bringing in
  the whole X stack, including gdm3. gdm3 will do things like suspend
  systems if the login screen is idle - not behavior server users would
  expect. The description for nvidia-settings suggests it is only
  applicable for graphics configuration. Therefore, would it make sense
  to remove the nvidia-settings recommendation from the nvidia-
  driver-*-server packages, which are more oriented for server class
  hardware?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460-server/+bug/1929868/+subscriptions

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

[Kernel-packages] [Bug 1929868] Re: Should nvidia-driver-XXX-server stop recommending nvidia-settings?

2021-05-27 Thread Launchpad Bug Tracker

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

** Changed in: nvidia-graphics-drivers-460-server (Ubuntu)
   Status: New => Confirmed

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

Title:
  Should nvidia-driver-XXX-server stop recommending nvidia-settings?

Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Confirmed

Bug description:
  The nvidia-driver-* packages have a Recommends on nvidia-settings.
  Installing them w/ recommends enabled therefore ends up bringing in
  the whole X stack, including gdm3. gdm3 will do things like suspend
  systems if the login screen is idle - not behavior server users would
  expect. The description for nvidia-settings suggests it is only
  applicable for graphics configuration. Therefore, would it make sense
  to remove the nvidia-settings recommendation from the nvidia-
  driver-*-server packages, which are more oriented for server class
  hardware?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460-server/+bug/1929868/+subscriptions

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

[Kernel-packages] [Bug 1929868] Re: Should nvidia-driver-XXX-server stop recommending nvidia-settings?

2021-05-27 Thread dann frazier

** Description changed:

The nvidia-driver-* packages have a Recommends on nvidia-settings.
- Installing them w/ recommends enabled ends up bringing in the whole X
- stack, including gdm3. gdm3 will do things like suspend systems if the
- login screen is idle - not behavior server users would expect. The
- description for nvidia-settings suggests it is only applicable for
+ Installing them w/ recommends enabled therefore ends up bringing in the
+ whole X stack, including gdm3. gdm3 will do things like suspend systems
+ if the login screen is idle - not behavior server users would expect.
+ The description for nvidia-settings suggests it is only applicable for
graphics configuration. Therefore, would it make sense to remove the
nvidia-settings recommendation from the nvidia-driver-*-server packages,
which are more oriented for server class hardware?

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

Title:
Should nvidia-driver-XXX-server stop recommending nvidia-settings?

Status in nvidia-graphics-drivers-460-server package in Ubuntu:
Confirmed

Bug description:
The nvidia-driver-* packages have a Recommends on nvidia-settings.
Installing them w/ recommends enabled therefore ends up bringing in
the whole X stack, including gdm3. gdm3 will do things like suspend
systems if the login screen is idle - not behavior server users would
expect. The description for nvidia-settings suggests it is only
applicable for graphics configuration. Therefore, would it make sense
to remove the nvidia-settings recommendation from the nvidia-
driver-*-server packages, which are more oriented for server class
hardware?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460-server/+bug/1929868/+subscriptions

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

[Kernel-packages] [Bug 1929868] [NEW] Should nvidia-driver-XXX-server stop recommending nvidia-settings?

2021-05-27 Thread dann frazier

Public bug reported:

The nvidia-driver-* packages have a Recommends on nvidia-settings.
Installing them w/ recommends enabled therefore ends up bringing in the
whole X stack, including gdm3. gdm3 will do things like suspend systems
if the login screen is idle - not behavior server users would expect.
The description for nvidia-settings suggests it is only applicable for
graphics configuration. Therefore, would it make sense to remove the
nvidia-settings recommendation from the nvidia-driver-*-server packages,
which are more oriented for server class hardware?

** Affects: nvidia-graphics-drivers-460-server (Ubuntu)
 Importance: Undecided
 Status: Confirmed

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

Title:
  Should nvidia-driver-XXX-server stop recommending nvidia-settings?

Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Confirmed

Bug description:
  The nvidia-driver-* packages have a Recommends on nvidia-settings.
  Installing them w/ recommends enabled therefore ends up bringing in
  the whole X stack, including gdm3. gdm3 will do things like suspend
  systems if the login screen is idle - not behavior server users would
  expect. The description for nvidia-settings suggests it is only
  applicable for graphics configuration. Therefore, would it make sense
  to remove the nvidia-settings recommendation from the nvidia-
  driver-*-server packages, which are more oriented for server class
  hardware?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460-server/+bug/1929868/+subscriptions

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

71 matches

Mail list logo