date:20210808

You have been subscribed to a public bug:

After (automated) update from 5.8.0-63 to 5.11.0.-25 the displayport over usb-c 
(Thinkpad e15gen2 i5-1135G7 / GeForce MX450/PCIe/SSE2) is not working properly.
Revert to 5.8.0-63 resolves the problem.
The problem is independent of nvdia-drivers (tried 470, 460 and intel only  
drivers). Same Monitors connected over HDMI work properly. Problem is limited 
to displayport over usb-c.

Problem symptoms: Monitor atttached over displayport allows only VGA 
resolution(1024 * 768)  and
flickers (on/off periodically). 

no special error messages found in dmesg except for abundance of
"i915 :00:02.0: [drm] *ERROR* failed to enable link training"

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.35
ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug  8 09:12:10 2021
InstallationDate: Installed on 2021-06-14 (54 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_IL:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IL
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeTermlog:

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


** Tags: amd64 apport-bug dist-upgrade focal
-- 
DisplayPort over USB-C not working after release update
https://bugs.launchpad.net/bugs/1939222
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 1939222] Re: DisplayPort over USB-C not working after release update

2021-08-08 Thread Chris Guiver

** 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/1939222

Title:
  DisplayPort over USB-C not working after release update

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After (automated) update from 5.8.0-63 to 5.11.0.-25 the displayport over 
usb-c (Thinkpad e15gen2 i5-1135G7 / GeForce MX450/PCIe/SSE2) is not working 
properly.
  Revert to 5.8.0-63 resolves the problem.
  The problem is independent of nvdia-drivers (tried 470, 460 and intel only  
drivers). Same Monitors connected over HDMI work properly. Problem is limited 
to displayport over usb-c.

  Problem symptoms: Monitor atttached over displayport allows only VGA 
resolution(1024 * 768)  and
  flickers (on/off periodically). 

  no special error messages found in dmesg except for abundance of
  "i915 :00:02.0: [drm] *ERROR* failed to enable link training"

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.35
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug  8 09:12:10 2021
  InstallationDate: Installed on 2021-06-14 (54 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IL:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IL
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939222/+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 1769236] Re: CPU frequency stuck at minimum value

2021-08-08 Thread Colin Ian King

Thermald 1.9.1-1ubuntu0.4 contains the backport of the adaptive engine,
see bug https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1913186

Thermald 1.9.1-1ubuntu.05 contains the following fixes that may also be
useful:

   - Disable legacy rapl cdev when rapl-mmio is in use
 This will prevent PL1/PL2 power limit from MSR based rapl, which
 may not be the correct one.
   - Delete all trips from zones before psvt install
 Initially zones has all the trips from sysfs, which may have wrong
 settings. Instead of deleting only for matched psvt zones, delete
 or all zones. In this way only zones which are in PSVT will be
 present.
   - Check for alternate names for B0D4 device
 B0D4 can be named as TCPU or B0D4. So search for both names
 if failed to find one.
   - Fix error for condition names
 The current code caps the max name as the last condition name,
 which is "Power_Slider". So any condition more than 56 will be
 printing error, with "Power_Slider" as condition name. For example
 for condition = 57: Unsupported condition 57 (Power_slider)
   - Set a very high RAPL MSR PL1 with --adaptive
 After upgrading Dell Latitude 5420, again noticed performance
 degradation.
 The PPCC power limit for MSR RAPL PL1 is reduced to 15W. Even though
 we disable MSR RAPL with --adaptive option, it is not getting
 disabled. So MSR RAPL limits still playing role.
 To fix that set a very high MSR RAPL PL1 limit so that it never
 causes throttling. All throttling with --adaptive option is done
 using RAPL-MMIO.
   - Special case for default PSVT
 When there are no adaptive tables and only one default PSVT table
 is present with just one entry with MAX type. Add one additional
 entry as done for non default case.
   - Increase power limit for disabled RAPL-MMIO
 Increase 100W to 200W as some desktop platform already have limit
 more than 100W.
   - Use Adaptive PPCC limits for RAPL MMIO
 Set the correct device name as RAPL-MSR so that RAPL-MMIO can
 also set the correct default power limits.

So first step is to see if thermald 1.9.1-1ubuntu0.5 helps.

** Changed in: thermald (Ubuntu)
   Importance: Undecided => High

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

Title:
  CPU frequency stuck at minimum value

Status in linux package in Ubuntu:
  Confirmed
Status in thermald package in Ubuntu:
  Incomplete

Bug description:
  I installed the Kubuntu variant of Ubuntu 18.04 on a new HP Spectre 13
  laptop.  Performance is poor.  The CPU (an i7-8550U) is running at
  400MHz, and never speeds up, even when running some of the Phoronix
  Test Suite benchmarks.

  I can use cpupower to switch to the "performance" cpufreq governor,
  but cannot change the frequency with either governor.

  Here is the output of some experiments I ran while Phoronix's c-ray test was 
running.
  __

  gjditchf@copperplate:/var/log$ cat /proc/cpuinfo | grep MHz
  cpu MHz : 400.008
  cpu MHz : 400.002
  cpu MHz : 400.002
  cpu MHz : 400.003
  cpu MHz : 400.005
  cpu MHz : 400.003
  cpu MHz : 400.001
  cpu MHz : 400.004

  gjditchf@copperplate:/var/log$ cpupower frequency-info
  analyzing CPU 0:
driver: intel_pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency:  Cannot determine or is not supported.
hardware limits: 400 MHz - 4.00 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 1.60 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 400 MHz (asserted by call to kernel)
boost state support:
  Supported: yes
  Active: yes

  gjditchf@copperplate:/var/log$ sudo cpupower frequency-set -f 1.60GHz
  Setting cpu: 0
  Error setting new values. Common errors:
  - Do you have proper administration rights? (super-user?)
  - Is the governor you requested available and modprobed?
  - Trying to set an invalid policy?
  - Trying to set a specific frequency, but userspace governor is not available,
 for example because of hardware which cannot be set to a specific frequency
 or because the userspace governor isn't loaded?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri May  4 12:57:25 2018
  InstallationDate: Installed on 2018-04-28 (6 days ago)
  InstallationMedia: Kubuntu 18.04

[Kernel-packages] [Bug 400297] Re: patch for JMicron jmc250 and jmc260 ethernet card

*** This bug is a duplicate of bug 1497005 ***
https://bugs.launchpad.net/bugs/1497005

I'm installing Linux Mint 20.2 Cinnamon on a Shuttle XS35V2.
I've got a Jmicron JMC250 network card 197b:0250 (rev 03).
It doesn't work, until I change speed from 1 Gbit/s to 100 Mbits/s :
sudo ethtool -s xx speed 100 duplex full

So, this bug seems to be still here in last version of Debian, Ubuntu
and Mint :(

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

Title:
  patch for JMicron jmc250 and jmc260 ethernet card

Status in linux package in Ubuntu:
  Expired

Bug description:
  It seems that Ubuntu 9.04 haven't has a patch for JMicron
  jmc250/jmc260 ethernet card like stated on
  http://cooldavid.org/download/jme.netdev-2.6.20080823.patch.

  I have a problem to connect to the net with my atom netbook which is
  using this ethernet chipset. The Network Manager keep on trying to
  connect to the net and switching from "conected" and "disconected"
  again and again for eth0. The same situation also hapened while using
  static IP assignment.

  Comparing with F11 that use 2.6.29 kernel version I found no problem
  with the same hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/400297/+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 1497005] Re: 197b:0250 JMicron JMC250 Gigabit ethernet doesn't work

I'm installing Linux Mint 20.2 Cinnamon on a Shuttle XS35V2.
I've got a Jmicron JMC250 network card 197b:0250 (rev 03).
It doesn't work, until I change speed from 1 Gbit/s to 100 Mbits/s :
sudo ethtool -s xx speed 100 duplex full

So, this bug seems to be still here in last version of Debian, Ubuntu
and Mint :(

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

Title:
  197b:0250 JMicron JMC250 Gigabit ethernet doesn't work

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Laptop ASUS X52JU can't connect to the router ASUS RT-AC68U via
  ethernet. NetworkManager shows that cable is unplugged. Router has
  Gigabit ethernet ports and laptop doesn't see them. I found that it's
  a bug of the JMC kernel module.

  WORKAROUND: The following allows 100 Mbps speed:
  sudo ethtool -s eth0 speed 100 duplex full

  ---
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nick   1682 F pulseaudio
   /dev/snd/controlC0:  nick   1682 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=b3669551-f67b-41f1-a310-6b79e24b871c
  InstallationDate: Installed on 2015-06-16 (93 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK Computer Inc. K52JU
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-49-generic 
root=UUID=c8aa6fb0-2c0a-430d-b6e5-7bb4ebb8346e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-49-generic N/A
   linux-backports-modules-3.16.0-49-generic  N/A
   linux-firmware 1.127.15
  Tags:  trusty
  Uname: Linux 3.16.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K52JU.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K52JU
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK52JU.206:bd01/25/2011:svnASUSTeKComputerInc.:pnK52JU:pvr1.0:rvnASUSTeKComputerInc.:rnK52JU:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: K52JU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497005/+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 926929] Re: Shuttle XS35 network interface not detected by installer

*** This bug is a duplicate of bug 1497005 ***
https://bugs.launchpad.net/bugs/1497005

** This bug is no longer a duplicate of bug 880316
   Link not detected / cable seems unplugged with jme - JMicron JMC250 Gigabit 
Ethernet Controller
** This bug has been marked a duplicate of bug 1497005
   197b:0250 JMicron JMC250 Gigabit ethernet 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/926929

Title:
  Shuttle XS35 network interface not detected by installer

Status in linux package in Ubuntu:
  Expired

Bug description:
  Tried to boot Shuttle XS35 with 11.10 32bit installer over PXE,
  however it fails to detect the network interface so the installation
  cannot continue.

  Tried to manually load kernel module for jme driver, but it was not
  found.

  Any help would be much appreciated.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/926929/+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 880316] Re: Link not detected / cable seems unplugged with jme - JMicron JMC250 Gigabit Ethernet Controller

*** This bug is a duplicate of bug 1497005 ***
https://bugs.launchpad.net/bugs/1497005

** This bug has been marked a duplicate of bug 1497005
   197b:0250 JMicron JMC250 Gigabit ethernet 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/880316

Title:
  Link not detected / cable seems unplugged with jme - JMicron JMC250
  Gigabit Ethernet Controller

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to install Ubuntu on a Shuttle XS35GTV2.

  The installer can't set up the network connection.
  I've tried Ubuntu 10.04 32 and 64 bit netinstall, minimal and server, Ubuntu 
11.10 32 bit netinstall.
  The Debian Squeeze 64 bit netinstall installer has no problem.
  (I've now installed openELEC which has no problems too)

  I was able to install Ubuntu 10.04 64 bit server but only without network 
connection. I then could load the jme module:
  # modprobe jme
  # depmod -a
  without errors.

  But I can't get eth0 running.

  The output of lspci is:
  02:00.5 Ethernet controller: JMicron Technology Corp. JMC250 PCI Express 
Gigabit Ethernet Controller (rev 03)
  03:00.0 Network controller: Realtek Semiconductor C., Ltd Device 8176 (rev 01)

  # lshw -C network
    *-network DISABLED
     description: Ethernet interface
     product: JMC250 PCI Express Gigabit Ethernet Controller
     vendor: JMicron Technology Corp.
     physical id: 0.5
     bus info: pci@:02:00.5
     logical name: eth0
     version: 03
     serial: 80:ee:73:1f:ef:df
     size: 10MB/s
     capacity: 1GB/s
     width: 32 bits
     clock: 33MHz
     capabilities: pm pciexpress msix msi bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
     configuration: autonegotiation=off broadcast=yes driver=jme 
driverversion=1.0.5 duplex=half latency=0 link=no multicast=yes port=MII 
speed=10MB/s
     resources: irq:17 memory:feaf4000-feaf7fff ioport:dc00(size=128) 
ioport:d800(size=256)
    *-network UNCLAIMED
     description: Network controller
     product: Realtek Semiconductor Co., Ltd.
     vendor: Realtek Semiconductor Co., Ltd.
     physical id: 0
     bus info: pci@:03:00.0
     version: 01
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list
     configuration: latency=0
     resources: ioport:e800(size=256) memory:febfc000-febf

  I've posted my problem at the Ubuntu users mailing list:
  
http://www.linux-archive.org/ubuntu-user/588603-jme-module-missing-netboot-installation.html

  Edit: Unfortunately I couldn't reassign it as it has nothing to do
  with gnome-nettools (see post #1).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/880316/+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 400297] Re: patch for JMicron jmc250 and jmc260 ethernet card

*** This bug is a duplicate of bug 1497005 ***
https://bugs.launchpad.net/bugs/1497005

** This bug has been marked a duplicate of bug 1497005
   197b:0250 JMicron JMC250 Gigabit ethernet 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/400297

Title:
  patch for JMicron jmc250 and jmc260 ethernet card

Status in linux package in Ubuntu:
  Expired

Bug description:
  It seems that Ubuntu 9.04 haven't has a patch for JMicron
  jmc250/jmc260 ethernet card like stated on
  http://cooldavid.org/download/jme.netdev-2.6.20080823.patch.

  I have a problem to connect to the net with my atom netbook which is
  using this ethernet chipset. The Network Manager keep on trying to
  connect to the net and switching from "conected" and "disconected"
  again and again for eth0. The same situation also hapened while using
  static IP assignment.

  Comparing with F11 that use 2.6.29 kernel version I found no problem
  with the same hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/400297/+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 1937897] Re: GPIO error logs in start and dmesg after update of kernel

2021-08-08 Thread Ole Jon Bjørkum

Well OK there is a module with that name, however I did blacklist it and
same error still occurs. It happens very early in the boot process. Now
maybe it tries to load gpio-aaeon, but still early to load modules I
would say, it's still doing say GRUB kernel parameters like fsck ones.

Now I have confirmed it does slow down boot pretty badly, however the
HWE stack just got kernel 5.11 and although it has the same error it
does seem to *almost* boot as fast as without any error.

Now I tried to actually load that module, so the reverse. It simply says
that no such device exists.

Conclusion/TLDR: So it shouldn't try to load it in the first place.

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

Title:
  GPIO error logs in start and dmesg after update of kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After update from kernel 5.11.0-22 to 5.11.0-25 i see next logs error
  to gpio:

 5.852182] gpio gpiochip2: (gpio_aaeon): tried to insert a GPIO chip with 
zero lines
  [5.852187] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to 
register, -22
  [5.852194] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22

  On pc:

  description: Desktop Computer
  product: System Product Name (SKU)
  vendor: ASUS
  version: System Version
  serial: System Serial Number
  width: 64 bits
  capabilities: smbios-3.3.0 dmi-3.3.0 smp vsyscall32
  configuration: boot=normal chassis=desktop family=To be filled by O.E.M. 
sku=SKU uuid=0ABCA172-BFA8-2AC5-FC37-3C7C3FD88FE4
*-core
 description: Motherboard
 product: TUF GAMING B550M-PLUS (WI-FI)
 vendor: ASUSTeK COMPUTER INC.
 physical id: 0
 version: Rev X.0x
 serial: 201176738701636
 slot: Default string
   *-firmware
description: BIOS
vendor: American Megatrends Inc.
physical id: 0
version: 2403
date: 06/16/2021
size: 64KiB
capacity: 16MiB
capabilities: pci apm upgrade shadowing cdboot bootselect 
socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen 
int9keyboard int14serial int17printer acpi usb biosbootspecification uefi
   *-memory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937897/+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 1929504] Re: Add support for IO functions of AAEON devices

2021-08-08 Thread Ole Jon Bjørkum

OK, but don't try to load the gpio-aaeon module on PCs that, if simply
one tries to load it manually, it simply says that no such device
exists... It shows twice in the boot log (dmesg + journalctl -b) but
even worse also on the monitors, although GRUB has "quiet" specified (no
splash).

Worst of all, on my Ryzen 3950X (16C/32T) with 5.5 GB/s PCIe4 NVMes you
get used to 1-2 second boot speed. But this actually reduces it
significantly compared to that. However it seems to be faster now that
the 5.11 kernel is the HWE one. The last 5.8 one introduced this bug for
me.

https://bugs.launchpad.net/bugs/1937897

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

Title:
  Add support for IO functions of AAEON devices

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Groovy:
  Fix Released
Status in linux source package in Hirsute:
  Fix Released
Status in linux source package in Impish:
  In Progress

Bug description:
  [Impact]
  Require drivers to enable AAEON devices.

  [Fix]
  AAEON provides a series of patches to support its GPIO/LED/Watchdog/HWMON 
devices.
  https://www.spinics.net/lists/linux-gpio/msg61301.html

  [Test]
  Verified on AAEON platform.

  [Where problems could occur]
  No, they are new drivers, should not introduce any regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929504/+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 1925126] Re: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50

2021-08-08 Thread Tomas Zemek

Reproduced today with kernel linux-image-5.11.0-25-generic
5.11.0-25.27~20.04.1:

Aug  8 22:18:11 kernel: [37254.612789] i915 :00:02.0: [drm] GPU HANG: ecode 
7:0:
Aug  8 22:18:11 kernel: [37254.612858] i915 :00:02.0: [drm] Resetting chip 
for stopped heartbeat on rcs0
Aug  8 22:18:11 kernel: [37254.714421] i915 :00:02.0: [drm] VMSVGA 
FIFO[8731] context reset due to GPU hang
Aug  8 22:18:14 kernel: [37257.670342] i915 :00:02.0: [drm] GPU HANG: ecode 
7:0:
Aug  8 22:18:14 kernel: [37257.670382] i915 :00:02.0: [drm] Resetting chip 
for stopped heartbeat on rcs0
Aug  8 22:18:14 kernel: [37257.773493] i915 :00:02.0: [drm] kwin_x11[7538] 
context reset due to GPU hang

System is Asus P8Z68V-Pro Gen3, i7-3770, iGPU:

00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller])
DeviceName: Onboard IGD
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor 
Graphics Controller
Flags: bus master, fast devsel, latency 0, IRQ 61
Memory at f740 (64-bit, non-prefetchable) [size=4M]
Memory at e000 (64-bit, prefetchable) [size=256M]
I/O ports at f000 [size=64]
Expansion ROM at 000c [virtual] [disabled] [size=128K]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915
Kernel modules: i915

On first look the symptoms are identical to the already resolved issue
https://bugs.launchpad.net/ubuntu/+source/linux-meta-
hwe-5.8/+bug/1923844 (duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux-meta-
hwe-5.8/+bug/1924624). Regression in latest 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/1925126

Title:
  Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups
  5.8.0-50

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  dmesg output with GPU HANGs, below.

  While running, it's fairly easy to cause flashing of text within a
  window, flipping between one window and another (eg. two tabs in
  gnome-terminal), or even complete freeze-ups, by moving a window or
  switching between windows, a little too quickly.

  This is a basically new install of Ubuntu 20.04 on a ThinkPad W530
  running Intel graphics and with kernel 5.8.0-50-generic.

  --

  $ dmesg -T | grep -i i915
  [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console
  [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for 
:00:02.0 on minor 0
  [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device
  [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer 
device
  [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 
(ops i915_audio_component_bind_ops [i915])
  [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 
7:0:
  [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for 
stopped heartbeat on rcs0
  [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context 
reset due to GPU hang
  [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 
7:1:ccddeeff, in gnome-shell [3417]
  [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for 
stopped heartbeat on rcs0
  [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 
7:1:ccddeeff
  [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for 
stopped heartbeat on rcs0
  [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 
7:1:003f003f, in Renderer [11805]
  [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for 
stopped heartbeat on rcs0
  [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context 
reset due to GPU hang
  [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 
7:1:40d84443, in Renderer [11805]
  [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for 
stopped heartbeat on rcs0
  [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context 
reset due to GPU han
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dev4268 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-05 (74 days ago)
  InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
  MachineType: LENOVO 2436CTO
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no

[Kernel-packages] [Bug 1924624] Re: After upgrade to kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy Bridge/Bay Trail) graphics a lot of glitches render screen unusable

2021-08-08 Thread Tomas Zemek

Today regression with kernel linux-image-5.11.0-25-generic
5.11.0-25.27~20.04.1:

Aug  8 22:18:11 kernel: [37254.612789] i915 :00:02.0: [drm] GPU HANG: ecode 
7:0:
Aug  8 22:18:11 kernel: [37254.612858] i915 :00:02.0: [drm] Resetting chip 
for stopped heartbeat on rcs0
Aug  8 22:18:11 kernel: [37254.714421] i915 :00:02.0: [drm] VMSVGA 
FIFO[8731] context reset due to GPU hang
Aug  8 22:18:14 kernel: [37257.670342] i915 :00:02.0: [drm] GPU HANG: ecode 
7:0:
Aug  8 22:18:14 kernel: [37257.670382] i915 :00:02.0: [drm] Resetting chip 
for stopped heartbeat on rcs0
Aug  8 22:18:14 kernel: [37257.773493] i915 :00:02.0: [drm] kwin_x11[7538] 
context reset due to GPU hang

System is Asus P8Z68V-Pro Gen3, i7-3770, iGPU HD4000:

00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller])
DeviceName: Onboard IGD
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor 
Graphics Controller
Flags: bus master, fast devsel, latency 0, IRQ 61
Memory at f740 (64-bit, non-prefetchable) [size=4M]
Memory at e000 (64-bit, prefetchable) [size=256M]
I/O ports at f000 [size=64]
Expansion ROM at 000c [virtual] [disabled] [size=128K]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915
Kernel modules: i915

Was the fix of this bug properly ported to 5.11?

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

Title:
  After upgrade to kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy
  Bridge/Bay Trail) graphics a lot of glitches render screen unusable

Status in linux package in Ubuntu:
  Fix Released
Status in linux-meta-hwe-5.8 package in Ubuntu:
  Fix Released

Bug description:
  After upgrading to 5.8.0-49, on a laprtop with intel graphics, graphics was 
suddenly extremely glitchy.
  Icons from the desktop flash through the browser, windows top bar gets 
distorted, all sort of glitches appear, parts of characters are missing in 
terminal, scrolling is inconsistent and the whole desktop becomes unusable.
  Under wayland the graphics are a bit more stable, but lots of glitches appear 
anyway, video reproduction in browser is stuttering and wobbly.
  Booting with previous kernel 5.8.0-48 seems to fix the issues.
  5.8.0-50 is broken as well.

  this is the result of 'sudo lshw -c video' on my hp Elitebook 8470:

  *-display 
 description: VGA compatible controller
 product: 3rd Gen Core processor Graphics Controller
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 09
 width: 64 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:33 memory:d400-d43f memory:c000-cfff 
ioport:4000(size=64) memory:c-d

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924624/+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 1939246] [NEW] With the proprietary nvidia drivers, suspend fails if I try to suspend while the connected monitors are powered off

2021-08-08 Thread Martin

Public bug reported:

As the title says, I'm unable to suspend if I have monitors connected
which don't have power. I hit the suspend button (or run `pm-suspend`),
and the computer just becomes unresponsive, stops reacting to input,
shows nothing on the screen (if I turn the monitors on again), is
unreachable through SSH, but the fans are still running, LEDs still
glowing, and it can't be waken up by any other means than a force
restart through cutting power or holding down the power button.

I followed this guide to debug this problem:
https://wiki.ubuntu.com/DebuggingKernelSuspend - the relevant part of
the dmesg output is:

[0.756829] PM:   Magic number: 0:484:522
[0.756830] PM:   hash matches drivers/base/power/main.c:1598
[0.756849] pci :07:00.0: hash matches

That :07:00.0 device is my nvidia GPU (a GTX 1080Ti).

---

1. Which part of the process does the issue occur with, the suspend to
ram, or resuming from?

The issue seems to happen during suspend. I believe this because during a normal
suspend, the GPU's RGB LEDs will turn off while the machine is suspended,
but when this issue occurs, the GPU's RGB LEDs stay on. (I knew those RGB LEDs
would come in useful some day!)

2. Please advise how you suspended specifically.

While reproducing the issue for this bug report, I've been using `pm-suspend`.
But it also happens when clicking the suspend button on my keyboard.

3. Please advise how you resumed specifically.

When this issue occurs, I can't resume. I hold the power button in until the 
system
powers off and then I boot as normal.

---

I'm unable to respond to the points which require running the latest
kernel, since the proprietary drivers don't seem to work on the latest
kernel (or maybe they're running in some form of fallback mode? I see a
640x480 output on one of my monitors).

And, as a final note, I'm sorry about this bug report. I know there's
probably nothing anybody can do about a bug in the proprietary drivers.
That sucks. I wish we didn't have to deal with bad proprietary graphics
drivers anymore. But I figured it's better to report the issue than to
not report it.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: nvidia-driver-470 470.57.02-0ubuntu0.21.04.1
ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug  8 23:03:57 2021
InstallationDate: Installed on 2021-06-10 (59 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
SourcePackage: nvidia-graphics-drivers-470
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-470 (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 nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/1939246

Title:
  With the proprietary nvidia drivers, suspend fails if I try to suspend
  while the connected monitors are powered off

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  As the title says, I'm unable to suspend if I have monitors connected
  which don't have power. I hit the suspend button (or run `pm-
  suspend`), and the computer just becomes unresponsive, stops reacting
  to input, shows nothing on the screen (if I turn the monitors on
  again), is unreachable through SSH, but the fans are still running,
  LEDs still glowing, and it can't be waken up by any other means than a
  force restart through cutting power or holding down the power button.

  I followed this guide to debug this problem:
  https://wiki.ubuntu.com/DebuggingKernelSuspend - the relevant part of
  the dmesg output is:

  [0.756829] PM:   Magic number: 0:484:522
  [0.756830] PM:   hash matches drivers/base/power/main.c:1598
  [0.756849] pci :07:00.0: hash matches

  That :07:00.0 device is my nvidia GPU (a GTX 1080Ti).

  ---

  1. Which part of the process does the issue occur with, the suspend to
  ram, or resuming from?

  The issue seems to happen during suspend. I believe this because during a 
normal
  suspend, the GPU's RGB LEDs will turn off while the machine is suspended,
  but when this issue occurs, the GPU's RGB LEDs stay on. (I knew those RGB LEDs
  would come in useful some day!)

  2. Please advise how you suspended specifically.

  While reproducing the issue for this bug report, I've been using `pm-suspend`.
  But it also happens when clicking the suspend button on my keyboard.

  3. Please advise how you resumed specifically.

  When this issue occurs, I can't resume. I hold the power button in until the 
system
  powers off and then I boot as normal.

  ---

  I'm unable to respond to the points which require running the latest

[Kernel-packages] [Bug 1939246] Re: With the proprietary nvidia drivers, suspend fails if I try to suspend while the connected monitors are powered off

2021-08-08 Thread Martin

** Attachment added: "I forgot to add the dmesg log, sorry"

https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1939246/+attachment/5516692/+files/dmesg-hash-matches-nvidia.txt

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

Title:
With the proprietary nvidia drivers, suspend fails if I try to suspend
while the connected monitors are powered off

Status in nvidia-graphics-drivers-470 package in Ubuntu:
New

Bug description:
As the title says, I'm unable to suspend if I have monitors connected
which don't have power. I hit the suspend button (or run `pm-
suspend`), and the computer just becomes unresponsive, stops reacting
to input, shows nothing on the screen (if I turn the monitors on
again), is unreachable through SSH, but the fans are still running,
LEDs still glowing, and it can't be waken up by any other means than a
force restart through cutting power or holding down the power button.

I followed this guide to debug this problem:
https://wiki.ubuntu.com/DebuggingKernelSuspend - the relevant part of
the dmesg output is:

[0.756829] PM: Magic number: 0:484:522
[0.756830] PM: hash matches drivers/base/power/main.c:1598
[0.756849] pci :07:00.0: hash matches

That :07:00.0 device is my nvidia GPU (a GTX 1080Ti).

---

1. Which part of the process does the issue occur with, the suspend to
ram, or resuming from?

The issue seems to happen during suspend. I believe this because during a
normal
suspend, the GPU's RGB LEDs will turn off while the machine is suspended,
but when this issue occurs, the GPU's RGB LEDs stay on. (I knew those RGB LEDs
would come in useful some day!)

2. Please advise how you suspended specifically.

While reproducing the issue for this bug report, I've been using `pm-suspend`.
But it also happens when clicking the suspend button on my keyboard.

3. Please advise how you resumed specifically.

When this issue occurs, I can't resume. I hold the power button in until the
system
powers off and then I boot as normal.

---

I'm unable to respond to the points which require running the latest
kernel, since the proprietary drivers don't seem to work on the latest
kernel (or maybe they're running in some form of fallback mode? I see
a 640x480 output on one of my monitors).

And, as a final note, I'm sorry about this bug report. I know there's
probably nothing anybody can do about a bug in the proprietary
drivers. That sucks. I wish we didn't have to deal with bad
proprietary graphics drivers anymore. But I figured it's better to
report the issue than to not report it.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: nvidia-driver-470 470.57.02-0ubuntu0.21.04.1
ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 8 23:03:57 2021
InstallationDate: Installed on 2021-06-10 (59 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
SourcePackage: nvidia-graphics-drivers-470
UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1939246/+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 1939251] [NEW] nvidia driver crashes after kernel upgrade

You have been subscribed to a public bug:

My two older Zotacs use the NV 340.108 driver and both are having the
same issue. After the latest dist-upgrade they boot fine but don't
display video, just a blank black screen with a randomly blinking
cursor. They're headless but I got into both with ssh in order to
uninstall the NV driver and now both boot normally but just use the
Nuveau default driver. Unfortunately I can't use either computer like
this (no NV driver). Afterward, I tried installing the NV driver with
Software-Updater but then received this warning after a few minutes:

Error while applying changes
pk-client-error-quark: Error while installing package: installed nvidia-340 
package post-installation script subprocess returned error exit status 10(313)
OK

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.35
ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug  8 18:05:04 2021
InstallationDate: Installed on 2021-02-24 (165 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.update-manager.release-upgrades: 2021-02-24T10:56:52.723450

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


** Tags: amd64 apport-bug dist-upgrade focal
-- 
nvidia driver crashes after kernel upgrade
https://bugs.launchpad.net/bugs/1939251
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 1939251] Re: nvidia driver crashes after kernel upgrade

2021-08-08 Thread Chris Guiver

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Please don't post/attach a .crash file.  The crash file should be
submitted using the `ubuntu-bug /var/crash/[filename].crash` which
gathers more details and populates fields making the .crash file much
easier to explore.

I suggest you submit that file, as this report is incomplete; you've
tagged it related to `ubuntu-release-upgrader` but you've not used that
tool (it would have upgraded your system to 20.10; ie. it's the tool
that upgrades you from one release to the next (20.04 to 20.10, or 20.04
to 22.04.1) and doesn't relate to a normal 'dist-upgrade'.

This issue likely relates to the HWE kernel, as recently the 5.8 kernel
stack (from 20.10) was moved to 5.11 (from 21.04) and thus package
likely should have been `linux-generic-hwe-20.04` (ie. switch to newer
5.11 is your issue).  (LTS releases have two kernel stack choices; GA
the more stable stays on 5.4, HWE upgrades during the first ~two years
of life).

I'll mark this 'incomplete' allowing you to submit your crash file and
create a new bug.  If you believe I've in error, or made an error,
please leave a comment saying why, and the bug report status can be
returned to "New".

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

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

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

Title:
  nvidia driver crashes after kernel upgrade

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My two older Zotacs use the NV 340.108 driver and both are having the
  same issue. After the latest dist-upgrade they boot fine but don't
  display video, just a blank black screen with a randomly blinking
  cursor. They're headless but I got into both with ssh in order to
  uninstall the NV driver and now both boot normally but just use the
  Nuveau default driver. Unfortunately I can't use either computer like
  this (no NV driver). Afterward, I tried installing the NV driver with
  Software-Updater but then received this warning after a few minutes:

  Error while applying changes
  pk-client-error-quark: Error while installing package: installed nvidia-340 
package post-installation script subprocess returned error exit status 10(313)
  OK

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.35
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug  8 18:05:04 2021
  InstallationDate: Installed on 2021-02-24 (165 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-manager.release-upgrades: 
2021-02-24T10:56:52.723450

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


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

Re: [Kernel-packages] [Bug 1939251] Re: nvidia driver crashes after kernel upgrade

2021-08-08 Thread marcw

Chris,
I followed your instructions but it didn't work complaining about a 
permission issue.  So I ran it with sudo and it seemed to work.
$ sudo ubuntu-bug /var/crash/nvidia-340.0.crash
But it still appears that the bug didn't attached the crash report.
Sorry, I tried.

On 8/8/21 6:30 PM, Chris Guiver wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better.
>
> Please don't post/attach a .crash file.  The crash file should be
> submitted using the `ubuntu-bug /var/crash/[filename].crash` which
> gathers more details and populates fields making the .crash file much
> easier to explore.
>
> I suggest you submit that file, as this report is incomplete; you've
> tagged it related to `ubuntu-release-upgrader` but you've not used that
> tool (it would have upgraded your system to 20.10; ie. it's the tool
> that upgrades you from one release to the next (20.04 to 20.10, or 20.04
> to 22.04.1) and doesn't relate to a normal 'dist-upgrade'.
>
> This issue likely relates to the HWE kernel, as recently the 5.8 kernel
> stack (from 20.10) was moved to 5.11 (from 21.04) and thus package
> likely should have been `linux-generic-hwe-20.04` (ie. switch to newer
> 5.11 is your issue).  (LTS releases have two kernel stack choices; GA
> the more stable stays on 5.4, HWE upgrades during the first ~two years
> of life).
>
> I'll mark this 'incomplete' allowing you to submit your crash file and
> create a new bug.  If you believe I've in error, or made an error,
> please leave a comment saying why, and the bug report status can be
> returned to "New".
>
> ** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>

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

Title:
  nvidia driver crashes after kernel upgrade

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My two older Zotacs use the NV 340.108 driver and both are having the
  same issue. After the latest dist-upgrade they boot fine but don't
  display video, just a blank black screen with a randomly blinking
  cursor. They're headless but I got into both with ssh in order to
  uninstall the NV driver and now both boot normally but just use the
  Nuveau default driver. Unfortunately I can't use either computer like
  this (no NV driver). Afterward, I tried installing the NV driver with
  Software-Updater but then received this warning after a few minutes:

  Error while applying changes
  pk-client-error-quark: Error while installing package: installed nvidia-340 
package post-installation script subprocess returned error exit status 10(313)
  OK

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.35
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug  8 18:05:04 2021
  InstallationDate: Installed on 2021-02-24 (165 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-manager.release-upgrades: 
2021-02-24T10:56:52.723450

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939251/+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 1924624] Re: After upgrade to kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy Bridge/Bay Trail) graphics a lot of glitches render screen unusable

There are countless different ways a GPU HANG can occur so let's assume
it's a new problem. Please open a new bug by running:

  ubuntu-bug linux-image-5.11.0-25-generic

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

Title:
  After upgrade to kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy
  Bridge/Bay Trail) graphics a lot of glitches render screen unusable

Status in linux package in Ubuntu:
  Fix Released
Status in linux-meta-hwe-5.8 package in Ubuntu:
  Fix Released

Bug description:
  After upgrading to 5.8.0-49, on a laprtop with intel graphics, graphics was 
suddenly extremely glitchy.
  Icons from the desktop flash through the browser, windows top bar gets 
distorted, all sort of glitches appear, parts of characters are missing in 
terminal, scrolling is inconsistent and the whole desktop becomes unusable.
  Under wayland the graphics are a bit more stable, but lots of glitches appear 
anyway, video reproduction in browser is stuttering and wobbly.
  Booting with previous kernel 5.8.0-48 seems to fix the issues.
  5.8.0-50 is broken as well.

  this is the result of 'sudo lshw -c video' on my hp Elitebook 8470:

  *-display 
 description: VGA compatible controller
 product: 3rd Gen Core processor Graphics Controller
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 09
 width: 64 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:33 memory:d400-d43f memory:c000-cfff 
ioport:4000(size=64) memory:c-d

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924624/+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 1937321] Re: System freeze (amdgpu kernel crash on resume from suspend)

The "invalid signature" problem I think is caused by Secure Boot. Try
disabling Secure Boot in your BIOS.

Also sorry again because it sounds like that libc6 problem is going to
keep getting in the way. But good news: Kernel 5.11 has now been
officially released to Ubuntu 20.04 updates. So you can delete the test
kernel packages with:

  sudo dpkg -P PACKAGENAME1 PACKAGENAME2 

and then do a system update to get the official update to 5.11:

  sudo apt update
  sudo apt full-upgrade

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

Title:
  System freeze (amdgpu kernel crash on resume from suspend)

Status in linux-hwe-5.8 package in Ubuntu:
  Incomplete

Bug description:
  System freezes after I close the lid on the laptop and leave it closed 
overnight. It doesn't respond to any key presses or mouse clicks including 
Ctrl-Alt+F4. my only recourse is to force the power off. Sometimes it has the 
"suspend" screen showing but mostly it's just black. The Power settings -Dim 
screen when inactive = yes
Blank screen = never
Wifi and Bluetooth can be turned off to save power = yes
Automatic suspend on battery power = yes
Power button action = Power off

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-63-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 22 17:34:17 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Renoir [103c:87cf]
  InstallationDate: Installed on 2021-06-30 (22 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: HP HP Laptop 15-ef1xxx
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic 
root=UUID=f66ca4c6-ec88-43af-81a3-7d994d7a217b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/10/2021
  dmi.bios.release: 15.34
  dmi.bios.vendor: AMI
  dmi.bios.version: F.34
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8707
  dmi.board.vendor: HP
  dmi.board.version: 37.19
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 37.19
  dmi.modalias: 
dmi:bvnAMI:bvrF.34:bd03/10/2021:br15.34:efr37.19:svnHP:pnHPLaptop15-ef1xxx:pvr:rvnHP:rn8707:rvr37.19:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-ef1xxx
  dmi.product.sku: 27A48UA#ABA
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  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+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1937321/+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 1937914] Re: [HP Probook 450 G6] Laptop Monitor Turns off During Startup, but older kernel versions work

*** This bug is a duplicate of bug 1939160 ***
https://bugs.launchpad.net/bugs/1939160

** This bug has been marked a duplicate of bug 1939160
   [HP Probook 450 G6] Laptop Monitor Turns off During Startup, but older 
kernel versions work (updated system 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/1937914

Title:
  [HP Probook 450 G6] Laptop Monitor Turns off During Startup, but older
  kernel versions work

Status in linux package in Ubuntu:
  New

Bug description:
  While starting the my laptop

  (Computer Model: HP Probook 450 G6
  ProdID 5YH15UT#ABA 
  Memory: 15.5 GB
  Processor: Intel Core i7-8565U CPU @ 1.80GHz x 8
  Graphics: NV118 / Mesa Intel UHD Graphics 620 (WHL GT2)
  Disk Capacity: 256.1 GB) 

  which runs

  (OS Name: Ubuntu 20.04.2 LTS
  OS Type: 64-bit
  GNOME Version: 3.36.8
  Windowing System: X11)

  the monitor turns off as soon as Ubuntu loads. The OS loads as normal
  and my external monitor still works, but my laptop monitor does not. I
  was able to fix the problem by pressing ESC as soon as the HP logo
  appears during start-up, then selecting "Advanced Ubuntu Options",
  then choosing an older version of Ubuntu (currently that's
  ...5.4.0-48..., while I believe the latest version is ...5.8.0-66...).

  It seems clear that this problem is caused by a bug that was
  introduced in one of the more recent updates (...5.8.0-59..., maybe?).
  I am not at all sure that the problem is in xorg; the package
  identification webpage just suggested that, if the monitor is blank
  when I would expect to see the Ubuntu logo during startup, then I
  should say that the relevant package is xorg.

  I am more than happy to run additional diagnostics that you would
  recommend if that would help you diagnose and fix the problem.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 24 14:28:51 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 620 (Whiskey Lake) 
[103c:8538]
 Subsystem: Hewlett-Packard Company GM108M [GeForce MX130] [103c:8542]
  InstallationDate: Installed on 2021-07-06 (17 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 06cb:00b7 Synaptics, Inc. 
   Bus 001 Device 002: ID 04f2:b66a Chicony Electronics Co., Ltd HP HD Camera
   Bus 001 Device 004: ID 0bda:b00b Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProBook 450 G6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=8bde40df-a693-4c3a-b5be-05611212add4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/27/2020
  dmi.bios.vendor: HP
  dmi.bios.version: R71 Ver. 01.11.01
  dmi.board.name: 8538
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 51.2A.00
  dmi.chassis.asset.tag: 5CD9308H3X
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrR71Ver.01.11.01:bd04/27/2020:svnHP:pnHPProBook450G6:pvr:rvnHP:rn8538:rvrKBCVersion51.2A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 450 G6
  dmi.product.sku: 5YH15UT#ABA
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  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+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937914/+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 1939251] Re: nvidia driver crashes after kernel upgrade

2021-08-08 Thread Chris Guiver

*** This bug is a duplicate of bug 1939254 ***
https://bugs.launchpad.net/bugs/1939254

Re-filed as https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-340/+bug/1939254

** This bug has been marked a duplicate of bug 1939254
   nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build

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

Title:
  nvidia driver crashes after kernel upgrade

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My two older Zotacs use the NV 340.108 driver and both are having the
  same issue. After the latest dist-upgrade they boot fine but don't
  display video, just a blank black screen with a randomly blinking
  cursor. They're headless but I got into both with ssh in order to
  uninstall the NV driver and now both boot normally but just use the
  Nuveau default driver. Unfortunately I can't use either computer like
  this (no NV driver). Afterward, I tried installing the NV driver with
  Software-Updater but then received this warning after a few minutes:

  Error while applying changes
  pk-client-error-quark: Error while installing package: installed nvidia-340 
package post-installation script subprocess returned error exit status 10(313)
  OK

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.35
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug  8 18:05:04 2021
  InstallationDate: Installed on 2021-02-24 (165 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-manager.release-upgrades: 
2021-02-24T10:56:52.723450

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939251/+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 1939211] [NEW] [Dell XPS 13 9380] Screen flickering after upgrading from 5.8 kernel to 5.11 kernel

You have been subscribed to a public bug:

Hello!

After the upgrade to the 5.8 series kernel to the 5.11 series kernel, I
have noticed some screen flickering. I had the same problem previously
on Fedora after upgrading to the 5.0 series kernel, but this was not
present on Ubuntu 20.04 on either the 5.4 or 5.8 series kernels. On
Fedora, it was fixed by turning off panel self-refresh on my Dell XPS 13
9380. I can try that again here if you all think it would be a useful
piece of information. In the Fedora bug, it was reported that this
problem is fixed in the 5.13 kernel. Let me know whatever else I can do.

Thanks!
Ben

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Aug  7 18:56:38 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af]
InstallationDate: Installed on 2021-06-24 (44 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: Dell Inc. XPS 13 9380
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/usr/bin/fish
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_l80o1s@/vmlinuz-5.11.0-25-generic 
root=ZFS=rpool/ROOT/ubuntu_l80o1s ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/27/2021
dmi.bios.release: 1.14
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.14.0
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.14.0:bd05/27/2021:br1.14:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9380
dmi.product.sku: 08AF
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
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+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug corruption focal ubuntu
-- 
[Dell XPS 13 9380] Screen flickering after upgrading from 5.8 kernel to 5.11 
kernel
https://bugs.launchpad.net/bugs/1939211
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-hwe-5.11 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 1939211] Re: [Dell XPS 13 9380] Screen flickering after upgrading from 5.8 kernel to 5.11 kernel

Yes please try turning off panel self refresh again by adding this
kernel parameter:

  i915.enable_psr=0

** Summary changed:

- Screen flickering after upgrading from 5.8 kernel to 5.11 kernel
+ [Dell XPS 13 9380] Screen flickering after upgrading from 5.8 kernel to 5.11 
kernel

** Package changed: xorg (Ubuntu) => linux-hwe-5.11 (Ubuntu)

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

** Tags added: regression-update

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

Title:
  [Dell XPS 13 9380] Screen flickering after upgrading from 5.8 kernel
  to 5.11 kernel

Status in linux-hwe-5.11 package in Ubuntu:
  Incomplete

Bug description:
  Hello!

  After the upgrade to the 5.8 series kernel to the 5.11 series kernel,
  I have noticed some screen flickering. I had the same problem
  previously on Fedora after upgrading to the 5.0 series kernel, but
  this was not present on Ubuntu 20.04 on either the 5.4 or 5.8 series
  kernels. On Fedora, it was fixed by turning off panel self-refresh on
  my Dell XPS 13 9380. I can try that again here if you all think it
  would be a useful piece of information. In the Fedora bug, it was
  reported that this problem is fixed in the 5.13 kernel. Let me know
  whatever else I can do.

  Thanks!
  Ben

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  7 18:56:38 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 
[VGA controller])
 Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af]
  InstallationDate: Installed on 2021-06-24 (44 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. XPS 13 9380
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/fish
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_l80o1s@/vmlinuz-5.11.0-25-generic 
root=ZFS=rpool/ROOT/ubuntu_l80o1s ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2021
  dmi.bios.release: 1.14
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  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.14.0:bd05/27/2021:br1.14:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  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+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1939211/+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 1939228] [NEW] screen tearing and redraw in ubuntu 20.04 LTS

You have been subscribed to a public bug:

I have used ubuntu 21.04 before on this device and  reported a bug and
it is solved by making psr value to 0. but in ubuntu 20.04LTS is not
working.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
.proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
.proc.driver.nvidia.gpus..30.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:30:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.91.03  Fri Jul  2 06:04:10 
UTC 2021
 GCC version:
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Sun Aug  8 13:57:13 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34]
   Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34]
InstallationDate: Installed on 2021-08-08 (0 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: LENOVO 82A1
ProcEnviron:
 LANGUAGE=en_IN:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=24316984-3147-43ba-aac0-f4497301192e ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/27/2021
dmi.bios.release: 1.32
dmi.bios.vendor: LENOVO
dmi.bios.version: DHCN32WW
dmi.board.asset.tag: ���
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0Q55722 WIN
dmi.chassis.asset.tag: ���
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Yoga Slim 7 14IIL05
dmi.ec.firmware.release: 1.29
dmi.modalias: 
dmi:bvnLENOVO:bvrDHCN32WW:bd05/27/2021:br1.32:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05:
dmi.product.family: Yoga Slim 7 14IIL05
dmi.product.name: 82A1
dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05
dmi.product.version: Yoga Slim 7 14IIL05
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
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+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug corruption focal ubuntu
-- 
screen tearing and redraw in ubuntu 20.04 LTS
https://bugs.launchpad.net/bugs/1939228
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-hwe-5.11 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 1939228] Re: screen tearing and redraw in ubuntu 20.04 LTS

*** This bug is a duplicate of bug 1937072 ***
https://bugs.launchpad.net/bugs/1937072

The kernel in Ubuntu 20.04 got upgraded recently, so now it has the same
bug as 21.04 :(

Please keep using bug 1937072

** Package changed: xorg (Ubuntu) => linux-hwe-5.11 (Ubuntu)

** This bug has been marked a duplicate of bug 1937072
   [Lenovo Yoga Slim 7 14IIL05] PSR causes incomplete screen redraws

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

Title:
  screen tearing and redraw in ubuntu 20.04 LTS

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

Bug description:
  I have used ubuntu 21.04 before on this device and  reported a bug and
  it is solved by making psr value to 0. but in ubuntu 20.04LTS is not
  working.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..30.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:30:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.91.03  Fri Jul  2 
06:04:10 UTC 2021
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Sun Aug  8 13:57:13 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34]
 Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34]
  InstallationDate: Installed on 2021-08-08 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 82A1
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=24316984-3147-43ba-aac0-f4497301192e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2021
  dmi.bios.release: 1.32
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DHCN32WW
  dmi.board.asset.tag: ���
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55722 WIN
  dmi.chassis.asset.tag: ���
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga Slim 7 14IIL05
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvrDHCN32WW:bd05/27/2021:br1.32:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05:
  dmi.product.family: Yoga Slim 7 14IIL05
  dmi.product.name: 82A1
  dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05
  dmi.product.version: Yoga Slim 7 14IIL05
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  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+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1939228/+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 1937072] Re: [Lenovo Yoga Slim 7 14IIL05] PSR causes incomplete screen redraws

** Tags added: focal

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

** Changed in: linux-hwe-5.11 (Ubuntu)
   Importance: Undecided => High

** Changed in: linux-hwe-5.11 (Ubuntu)
   Status: New => Triaged

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

Title:
  [Lenovo Yoga Slim 7 14IIL05] PSR causes incomplete screen redraws

Status in linux package in Ubuntu:
  Triaged
Status in linux-hwe-5.11 package in Ubuntu:
  Triaged

Bug description:
  In every 6/10 boot my ubuntu failed to start stuck on blank screen.
  Sometime touchpad stop working and unable to change my brightness
  after installation at first all feature are perfectly fine except
  screen glitch.Screen performance is laggy.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 21 17:13:28 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34]
 Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34]
  InstallationDate: Installed on 2021-07-21 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 82A1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/14/2021
  dmi.bios.release: 1.31
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DHCN31WW
  dmi.board.asset.tag: ���
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55722 WIN
  dmi.chassis.asset.tag: ���
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga Slim 7 14IIL05
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05:
  dmi.product.family: Yoga Slim 7 14IIL05
  dmi.product.name: 82A1
  dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05
  dmi.product.version: Yoga Slim 7 14IIL05
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937072/+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 1844384] Re: Display bug with kernel 5.2/5.3 on Dell XPS 13

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.


** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1844384

Title:
  Display bug with kernel 5.2/5.3 on Dell XPS 13

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  Hello,

  I use in multiboot Ubuntu and Archlinux, I had the opportunity to use
  many kernels and I notice a random display problem (see screenshot)
  that happens from time to time on my Dell XPS but only from kernel 5.2
  (and following).

  Under Ubuntu 19.04 with the 5.0 kernel I don't have this problem,
  under Archlinux with the old kernels (4.19LTS, 5.0, 5.1) I didn't have
  this problem either.

  But since 5.2 whether it is under Ubuntu or Archlinux, I have noticed
  this problem which is difficult to describe, it is a kind of band that
  appears at the top of the screen with a different size (sometimes very
  wide).

  The problem occurs randomly, sometimes it can go 30 minutes without
  seeing it appear and sometimes it can appear full of times for a few
  minutes.

  The problem is not specific to Ubuntu but to the kernel since 5.2 and 
following. 
  Under the 19.10 of Ubuntu in development with the 5.3 kernel, the problem is 
still present.

  Could you please forward this bug to the team that deals with the linux 
kernel.
  (the 2 screenshots were taken under Ubuntu 19.10 with the 5.3 kernel but 
under Archlinux it's the same thing.

  Configuration :
  Dell XPS 13 model 2019 (9380)
  Graphics chipset: Intel® UHD 620 (Whiskey Lake 3x8 GT2)

  Noted that this problem can occur regardless of the activity on the
  desktop (browser, video player...), sometimes the screen skips
  completely for a tenth of a second.

  Please correct the problem quickly

  
  capture1: https://nsa40.casimages.com/img/2019/09/17/190917050728230823.jpg
  capture2: https://nsa40.casimages.com/img/2019/09/17/190917050801231741.jpg
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  simon 22176 F pulseaudio
   /dev/snd/pcmC0D0p:   simon 22176 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-07-18 (60 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. XPS 13 9380
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic 
root=UUID=d10cf0fc-051d-4ccd-b2da-e944d0ddd735 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-10-generic N/A
   linux-backports-modules-5.3.0-10-generic  N/A
   linux-firmware1.182
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  eoan
  Uname: Linux 5.3.0-10-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-17 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/05/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  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.7.0:bd08/05/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.
  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-07-18T20:23:25.974818

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844384/+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 1939205] Re: sound dummy output 21.04

If you plug a headphone to the Front Headphone Jack or Lineout Jack,
could you see a output device?

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

Title:
  sound dummy output 21.04

Status in linux package in Ubuntu:
  New

Bug description:
  no more sound device /output since dist upgrade from 20.10 to 21.04

  tried both official ubuntu kernel 5.11.0.26 and newer
  5.13.8-051308-generic

  alsa log:

  http://alsa-project.org/db/?f=07dfaad1d5d30948449dc36f0caaf39c99145cce

  lsb_release -rd
  Description:  Ubuntu 21.04
  Release:  21.04

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

   ubuntu-bug linux:  package not installed

  
  cat /proc/version_signature > version.log
  cat: /proc/version_signature: No such file or directory

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

  
  be descriptive in helping as im a newbie to linux troubleshoot  :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939205/+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 1912673] Re: sounds not working on Dell XPS 17 (9700)

@Stephane,

just run $sudo apt-get update;$sudo apt install linux-
image-5.11.0-$(latest version)-generic; linux-modules-
extra-5.11.0-$(latest version)-generic;reboot

** Changed in: linux (Ubuntu)
Status: Confirmed => 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/1912673

Title:
sounds not working on Dell XPS 17 (9700)

Status in linux package in Ubuntu:
Fix Released
Status in linux package in Debian:
Fix Released

Bug description:
My investigation process:

Dell XPS 17 (9700) comes with Windows 10 preinstalled, where sounds
worked.

I installed Ubuntu 20.04 LTS fresh, sounds did not work on speakers or 3.5mm
headphones,
using linux-image-5.4.0-42-generic, I did not try blutooth.

I sudo apt upgrade, dist-upgrade to get kernels

linux-image-5.8.0-38-generic
linux-image-5.8.0-40-generic

Sounds did not work.
I download linux-image-unsigned-5.10.9-051009-generic.
Sounds did not work.

I upgrade Dell XPS 9700 firmware from 1.3 to 1.63.
Sounds did not work.

After googling I found this solution in the comments:
https://askubuntu.com/questions/1270442/no-sound-on-xps-17-9700

"""

Download and install dkms module:

https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/pc-oem-
dkms/+packages

Alternatively, you can install linux-oem-20.04, it will install
the 5.6 kernel with the above driver. Your system may be more stable
with 5.4 kernel since it is in wide use.

Manually install sof-firmware from Arch Linux:

https://archlinux.pkgs.org/rolling/archlinux-extra-x86_64/sof-
firmware-1.5.1-1-any.pkg.tar.zst.html

You will need to delete the existing "sof" and "sof-tplg" files
from the Ubuntu linux-firmware package first. Note if this package
gets updated from Canoncial and they don't update these, you will have
to delete and then reextract. Files go into the
/usr/lib/firmware/intel/sof and /usr/lib/firmware/intel/sof-tplg
folders.

Manually install the ucm2 files:

http://xps17.ddns.net/sof-soundwire.zip

These go into /usr/share/alsa/ucm2/sof-soundwire. Delete the
contents of the existing sof-soundwire folder (if you have it) and
replace them with the ones from the archive.

Reboot. You should now have all your audio devices available. If speakers
do not play, you may need to run alsamixer (non-root) from a terminal and
unmute and set the mixer levels all the way up.
"""

This solution worked for me on linux-image-5.6.0-1042-oem AFTER
manually opening alsa-mixer and changing soundcard to sof. The sound
would otherwise just show 'dummy'.

My sounds still do not work on 5.8 or 5.10, full name listed above. I
did not get to test this temporary fix with 5.4.

my full alsa-info:
http://alsa-project.org/db/?f=6a638be0cfbe8ed08a010eb26a7702e324dce5ff

based on some google research, this seems to be a common problem:

https://www.reddit.com/r/Dell/comments/hj8oxw/xps_17_9700_no_audio_on_linux_also_hardware_is/

https://www.reddit.com/r/Dell/comments/hge2yo/no_audio_on_linux_ubuntu_2004_xps_17_9700_realtek/

https://www.reddit.com/r/Dell/comments/j2kdjw/xps_17_9700_on_linux_audio_issue/
etc...

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.10
ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19
Uname: Linux 5.6.0-1042-oem x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: neoh 1786 F pulseaudio
/dev/snd/pcmC1D0p: neoh 1786 F...m pulseaudio
/dev/snd/controlC0: neoh 1786 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 21 12:08:45 2021
InstallationDate: Installed on 2021-01-20 (1 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/30/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.6.3
dmi.board.name: 0CXCCY
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0CXCCY:rvrA03:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 17 9700
dmi.product.sku: 098F
dmi.sys.vendor: Dell Inc.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Dependencies:

DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2021-01-20 (1 days ago

[Kernel-packages] [Bug 1939052] Re: No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s Gen2

@Cameron,

These patches need to be sent to upstream first.

thx.

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

Title:
  No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and
  13s Gen2

Status in linux package in Ubuntu:
  New

Bug description:
  All 3 models need the appropriate HDA verbs sent to properly
  initialize the sound hardware.

  Additionally, the Legion 15IMHG05 needs automute disabled otherwise
  speaker output will not return after removing headphones.

  The good news is that I have working patches for all 3.

  However, the 13s Gen2 reportedly has some weirdness on the volume
  control. I don't have this model of laptop so there's not a lot I can
  do. It seems tuning the volume up and down using the keys on the
  keyboard can jump the volume up and down in large increments. Volume
  adjustments via a GUI do not have this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-25-generic 5.11.0-25.27
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hiryu  7243 F pulseaudio
   /dev/snd/controlC0:  hiryu  7243 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Aug  5 10:17:57 2021
  InstallationDate: Installed on 2021-04-23 (104 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 82K6
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=825f1536-7d58-4097-9779-e5df2db0a6eb ro quiet splash 
nvidia-drm.modeset=0 resume=/dev/mapper/swap thinkpad_acpi.fan_control=1 
bluetooth.disable_ertm acpi_backlight=video vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-25-generic N/A
   linux-backports-modules-5.11.0-25-generic  N/A
   linux-firmware 1.197.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2021
  dmi.bios.release: 1.33
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H1CN33WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ITHg6
  dmi.ec.firmware.release: 1.33
  dmi.modalias: 
dmi:bvnLENOVO:bvrH1CN33WW:bd07/18/2021:br1.33:efr1.33:svnLENOVO:pn82K6:pvrLegion716ITHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ITHg6:
  dmi.product.family: Legion 7 16ITHg6
  dmi.product.name: 82K6
  dmi.product.sku: LENOVO_MT_82K6_BU_idea_FM_Legion 7 16ITHg6
  dmi.product.version: Legion 7 16ITHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939052/+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 1939052] Re: No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s Gen2

@Cameron,

How did you find those verbs? And could you please also take a look at
this bug: https://bugzilla.kernel.org/show_bug.cgi?id=203409

could you please find a workable verbs for lenovo c930 as well?


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

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

Title:
  No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and
  13s Gen2

Status in linux package in Ubuntu:
  New

Bug description:
  All 3 models need the appropriate HDA verbs sent to properly
  initialize the sound hardware.

  Additionally, the Legion 15IMHG05 needs automute disabled otherwise
  speaker output will not return after removing headphones.

  The good news is that I have working patches for all 3.

  However, the 13s Gen2 reportedly has some weirdness on the volume
  control. I don't have this model of laptop so there's not a lot I can
  do. It seems tuning the volume up and down using the keys on the
  keyboard can jump the volume up and down in large increments. Volume
  adjustments via a GUI do not have this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-25-generic 5.11.0-25.27
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hiryu  7243 F pulseaudio
   /dev/snd/controlC0:  hiryu  7243 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Aug  5 10:17:57 2021
  InstallationDate: Installed on 2021-04-23 (104 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 82K6
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=825f1536-7d58-4097-9779-e5df2db0a6eb ro quiet splash 
nvidia-drm.modeset=0 resume=/dev/mapper/swap thinkpad_acpi.fan_control=1 
bluetooth.disable_ertm acpi_backlight=video vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-25-generic N/A
   linux-backports-modules-5.11.0-25-generic  N/A
   linux-firmware 1.197.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2021
  dmi.bios.release: 1.33
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H1CN33WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ITHg6
  dmi.ec.firmware.release: 1.33
  dmi.modalias: 
dmi:bvnLENOVO:bvrH1CN33WW:bd07/18/2021:br1.33:efr1.33:svnLENOVO:pn82K6:pvrLegion716ITHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ITHg6:
  dmi.product.family: Legion 7 16ITHg6
  dmi.product.name: 82K6
  dmi.product.sku: LENOVO_MT_82K6_BU_idea_FM_Legion 7 16ITHg6
  dmi.product.version: Legion 7 16ITHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939052/+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 1938413] Re: Shutdown hangs on EHL board

2021-08-08 Thread Hsuan-Yu Lin

Hi @Doug,

I have uploaded a new test kernel on my ppa, please refer to [1] or
follow the steps below to verify:


[Installation steps]
$ sudo add-apt-repository ppa:shanelin/linux-intel
$ sudo apt-get update
$ sudo apt-get install 
linux-image-unsigned-5.11.0-1011-intel=5.11.0-1011.13+lp1938408~lp1938413~0805 
linux-modules-5.11.0-1011-intel=5.11.0-1011.13+lp1938408~lp1938413~0805 
linux-modules-extra-5.11.0-1011-intel=5.11.0-1011.13+lp1938408~lp1938413~0805


---
[1] https://launchpad.net/~shanelin/+archive/ubuntu/linux-intel
[2] Test passed (5/5) for:
CID: 202105-29064
BIOS: EHLSFWI1.R00.2091.A00.2002250754

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

Title:
  Shutdown hangs on EHL board

Status in intel:
  New
Status in linux-intel package in Ubuntu:
  In Progress

Bug description:
  [Summary]Go to Power -> Shutdown and the screen goes blank, but the
  system does not shut down.  You cannot recover and have to perform a
  hard reboot.

  [Steps to reproduce]
  1. Boot up Ubuntu
  2. Power -> Shutdown (click ok)

  [Expected result]
  System should cleanly shut down.

  [Actual result]
  Screen blanks with a blinking cursor, the system does not shut down, the fan 
is still on.  System is unresponsive, forcing you to do a hard reset.

  [Failure rate]100%

  [Additional information]
  CID: 20215-29063 
  SKU: 
  system-manufacturer: Intel Corporation
  system-product-name: Elkhart Lake Embedded Platform
  bios-version: EHLSFWI1.R00.2091.A00.2002250754
  CPU: Genuine Intel(R) CPU  @ 1.90GHz (4x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:4571]
  kernel-version: 5.11.0-1009-intel

  
  [Stage]
  Device froze, issue reported and logs collected right after a reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1938413/+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 1938408] Re: EHL board does not support soft reboot

2021-08-08 Thread Hsuan-Yu Lin

Hi @Doug,

The same test kernel has been built. Please refer to bug 1938413 comment #17.
Thanks!

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

Title:
  EHL board does not support soft reboot

Status in intel:
  New
Status in linux-intel package in Ubuntu:
  In Progress

Bug description:
  [Summary]Telling the EHL board to reboot from within Ubuntu causes it
  to hang, forcing you to do a hard reboot.

  [Steps to reproduce]
  1. Open terminal window.
  2. $ reboot

  [Expected result]
  System should gracefullyl reboot.

  [Actual result]
  Screen goes blank except for a cursor.  System does not reboot. You must hard 
reboot (pull the plug)

  [Failure rate]100%

  [Additional information]
  CID: 202105-29063 
  SKU: 
  system-manufacturer: Intel Corporation
  system-product-name: Elkhart Lake Embedded Platform
  bios-version: EHLSFWI1.R00.2091.A00.2002250754
  CPU: Genuine Intel(R) CPU  @ 1.90GHz (4x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:4571]
  kernel-version: 5.11.0-1009-intel

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1938408/+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 1939052] Re: No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s Gen2

2021-08-08 Thread Cameron Berkenpas

Some info is here:
https://github.com/thiagotei/linux-realtek-alc287

You can run a VM using someone's fork of of Qemu (which just adds a bit of 
logging) with PCIE passthrough of your sound card. Then you can narrow down 
exactly which verbs are needed. 
It seems that some of the people in your linked bug are attempting the exact 
same method already.

This is all assuming you're simply missing the verb initialization
sequence for your laptop's hardware.

For example, the 2021 Lenovo Legion's (both the AMD and Intel models)
have a separate issue where the speakers are controlled by a Cirrus
Logic (CS35L51) amplifier chip that currently has no support in Linux.

I can't do this, because I don't have this model of laptop, and I don't
really have anymore time to dedicate to this.

I've attempted to send the patches upstream. I never got a response. Not
even the slightest amount of feedback. Considering this is something
I've done on the side and that I have a lot of other responsibilities, I
think this is as likely as far as this is going to go.

Good luck on the Lenovo c930.

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

Title:
  No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and
  13s Gen2

Status in linux package in Ubuntu:
  New

Bug description:
  All 3 models need the appropriate HDA verbs sent to properly
  initialize the sound hardware.

  Additionally, the Legion 15IMHG05 needs automute disabled otherwise
  speaker output will not return after removing headphones.

  The good news is that I have working patches for all 3.

  However, the 13s Gen2 reportedly has some weirdness on the volume
  control. I don't have this model of laptop so there's not a lot I can
  do. It seems tuning the volume up and down using the keys on the
  keyboard can jump the volume up and down in large increments. Volume
  adjustments via a GUI do not have this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-25-generic 5.11.0-25.27
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hiryu  7243 F pulseaudio
   /dev/snd/controlC0:  hiryu  7243 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Aug  5 10:17:57 2021
  InstallationDate: Installed on 2021-04-23 (104 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 82K6
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=825f1536-7d58-4097-9779-e5df2db0a6eb ro quiet splash 
nvidia-drm.modeset=0 resume=/dev/mapper/swap thinkpad_acpi.fan_control=1 
bluetooth.disable_ertm acpi_backlight=video vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-25-generic N/A
   linux-backports-modules-5.11.0-25-generic  N/A
   linux-firmware 1.197.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2021
  dmi.bios.release: 1.33
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H1CN33WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ITHg6
  dmi.ec.firmware.release: 1.33
  dmi.modalias: 
dmi:bvnLENOVO:bvrH1CN33WW:bd07/18/2021:br1.33:efr1.33:svnLENOVO:pn82K6:pvrLegion716ITHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ITHg6:
  dmi.product.family: Legion 7 16ITHg6
  dmi.product.name: 82K6
  dmi.product.sku: LENOVO_MT_82K6_BU_idea_FM_Legion 7 16ITHg6
  dmi.product.version: Legion 7 16ITHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939052/+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 1926597] Re: Linux 5.10.0-1024.25 breaks HDMI with Intel i915

[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/1926597

Title:
  Linux 5.10.0-1024.25 breaks HDMI with Intel i915

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hi,

  [Thinkpad T480s, Intel iGPU 8550u, Ubuntu Focal up-to-date, GNOME
  Wayland session]

  Previous 5.10.0-1023.24 was ok. Kernel 5.8 HWE is ok. I did not test a
  X session.

  Plugging HDMI after GNOME is loaded fails to display anything on the HDMI 
display.
  Plugging HDMI at boot or at GDM screen makes the HDMI display works as usual.

  Unplugging HDMI (display only on this one) during GNOME session does
  not update displays state. Nothing happens. I have to press the
  switch-display-key on my laptop to actualize the setup and make my
  laptop's display active.

  When I unplug HDMI during GNOME session, nothing appears in logs.

  My laptop fails to enter sleep after having unplugged the HDMI.

  Related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924238

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926597/+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 1787857] Re: USB mouse cursor lags after random time of correct behaviour

[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/1787857

Title:
  USB mouse cursor lags after random time of correct behaviour

Status in linux package in Ubuntu:
  Expired
Status in rtirq package in Ubuntu:
  Invalid

Bug description:
  I installed Ubuntu Studio 18.04.1 LTS. After the first apt-get update I 
noticed the following behaviour:
  after havig logged in, my USB mouse works normally for about ten seconds, 
then the cursor starts lagging a lot which makes the mouse pretty much unusable.
  The last dmesg always contain lines these: (more in attached file)

  [<9e659b0c>] irq_default_primary_handler threaded 
[] usb_hcd_irq
  [<9e659b0c>] irq_default_primary_handler threaded 
[] _rtl_pci_interrupt [rtl_pci]
  Disabling IRQ #18

  Out of frustration & curiosity I disabled most autostart apps
  (Settings > Session ... > Autostart) and re-enabled them after
  rebooting. Since then I rarely encounter the lagging cursor. If I open
  Settings > Mouse & Touchpad and toggle any option on/off the cursor
  starts lagging.

  How can make the cursor work reliably?
  Some comment in dmesg mentions "irqpoll" boot option

  Ubuntu Studio 18.04.1
  4.15.0-20-lowlatency #21-Ubuntu SMP PREEMPT

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787857/+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 1936708] Re: Wobbly graphics on built-in display since linux-image-5.11.0-22-generic

** Description changed:

+ == SRU Justification ==
+ 
+ [Impact]
+ Wobbly graphics after a kernel update. 
+ 
+ [Fix]
+ Older panels may require more bandwidth then advertised, so we need to
+ use max params for them.
+ 
+ [Test]
+ Multiple users tested with positive result.
+ 
+ [Where problems could occur]
+ This patch reverts to the old behavior, which is to use max parameters,
+ for older panels. If there's any new panel reports with older DP
+ version, this might change the behavior on it.
+ 
+ == Original Bug Report ==
+ 
  Lenovo laptop with Intel + Nvidia graphics.
  
  Since booting from  linux-image-5.11.0-22-generic, the built-in display is 
unusable, with wobbling horizontal stripes from the disk decryption prompt 
onwards:
  https://www.youtube.com/watch?v=LyRTuPzCe2I
  HDMI output works fine.
  
  If I boot from linux-image-5.11.0-18-generic instead, all is well.
  If I use Recovery mode with linux-image-5.11.0-22-generic and continue 
bootup, it's usable but there's no HDMI output.
  
  I think others may be having this issue too:
  
https://askubuntu.com/questions/1351188/weird-graphical-glitches-appears-only-on-integrated-display-on-any-ubuntu-base#
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-22-generic 5.11.0-22.23
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alex   1598 F pulseaudio
   /dev/snd/controlC0:  alex   1598 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sat Jul 17 09:50:31 2021
  InstallationDate: Installed on 2021-01-03 (194 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 80DU
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-22-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-22-generic N/A
   linux-backports-modules-5.11.0-22-generic  N/A
   linux-firmware 1.197.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to hirsute on 2021-05-22 (55 days ago)
  dmi.bios.date: 08/18/2014
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN31WW(V1.14)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: Lenovo Y70-70 Touch
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y70-70 Touch
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN31WW(V1.14):bd08/18/2014:br1.49:efr1.49:svnLENOVO:pn80DU:pvrLenovoY70-70Touch:rvnLENOVO:rnLenovoY70-70Touch:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoY70-70Touch:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80DU
  dmi.product.sku: LENOVO_MT_80DU_BU_idea_FM_Lenovo Y70-70 Touch
  dmi.product.version: Lenovo Y70-70 Touch
  dmi.sys.vendor: LENOVO

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

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

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

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

** Changed in: linux (Ubuntu Focal)
   Status: New => Won't Fix

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

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

** Changed in: linux-oem-5.13 (Ubuntu Focal)
   Status: New => Confirmed

** Changed in: linux-oem-5.13 (Ubuntu Hirsute)
   Status: New => Invalid

** Changed in: linux-oem-5.13 (Ubuntu Impish)
   Status: New => Invalid

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

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

** Changed in: linux-oem-5.13 (Ubuntu Focal)
   Importance: Undecided => Medium

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

Title:
  Wobbly graphics on built-in display since linux-
  image-5.11.0-22-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.13 source package in Focal:
  Confirmed
Status in linux source package in Hirsute:
  Confirmed
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  Confirmed
Status in linux-oem-5.13 source package in Impish:
  Invalid

Bug description:
  == SRU Justification ==

  [Impact]
  Wobbly graphics after a kernel update. 

  [Fix]
  Older panels may require more bandwidth then advertised, so we need to
  use max params for them.

  [Te

[Kernel-packages] [Bug 1939052] Re: No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s Gen2

Well noted, thanks for sharing the info.

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

Title:
  No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and
  13s Gen2

Status in linux package in Ubuntu:
  New

Bug description:
  All 3 models need the appropriate HDA verbs sent to properly
  initialize the sound hardware.

  Additionally, the Legion 15IMHG05 needs automute disabled otherwise
  speaker output will not return after removing headphones.

  The good news is that I have working patches for all 3.

  However, the 13s Gen2 reportedly has some weirdness on the volume
  control. I don't have this model of laptop so there's not a lot I can
  do. It seems tuning the volume up and down using the keys on the
  keyboard can jump the volume up and down in large increments. Volume
  adjustments via a GUI do not have this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-25-generic 5.11.0-25.27
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hiryu  7243 F pulseaudio
   /dev/snd/controlC0:  hiryu  7243 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Aug  5 10:17:57 2021
  InstallationDate: Installed on 2021-04-23 (104 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 82K6
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=825f1536-7d58-4097-9779-e5df2db0a6eb ro quiet splash 
nvidia-drm.modeset=0 resume=/dev/mapper/swap thinkpad_acpi.fan_control=1 
bluetooth.disable_ertm acpi_backlight=video vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-25-generic N/A
   linux-backports-modules-5.11.0-25-generic  N/A
   linux-firmware 1.197.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2021
  dmi.bios.release: 1.33
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H1CN33WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ITHg6
  dmi.ec.firmware.release: 1.33
  dmi.modalias: 
dmi:bvnLENOVO:bvrH1CN33WW:bd07/18/2021:br1.33:efr1.33:svnLENOVO:pn82K6:pvrLegion716ITHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ITHg6:
  dmi.product.family: Legion 7 16ITHg6
  dmi.product.name: 82K6
  dmi.product.sku: LENOVO_MT_82K6_BU_idea_FM_Legion 7 16ITHg6
  dmi.product.version: Legion 7 16ITHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939052/+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 1938823] Re: package nvidia-dkms-470 470.57.02-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-470 package post-installation script subprocess returned error e

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

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

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

Title:
  package nvidia-dkms-470 470.57.02-0ubuntu0.20.04.1 failed to
  install/upgrade: installed nvidia-dkms-470 package post-installation
  script subprocess returned error exit status 10

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Confirmed

Bug description:
  Error when installing driver

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-dkms-470 470.57.02-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-63-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Aug  3 17:39:22 2021
  ErrorMessage: installed nvidia-dkms-470 package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2021-08-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: nvidia-graphics-drivers-470
  Title: package nvidia-dkms-470 470.57.02-0ubuntu0.20.04.1 failed to 
install/upgrade: installed nvidia-dkms-470 package post-installation script 
subprocess returned error exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1938823/+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 1919122] Re: net test from ubuntu_kernel_selftests / ubuntu_bpf failed to build on F-OEM-5.10 (Cannot find a vmlinux for VMLINUX_BTF)

2021-08-08 Thread Po-Hsu Lin

** Summary changed:

- net test from ubuntu_kernel_selftests / ubuntu_bpf failed to build on 
F-OEM-5.10
+ net test from ubuntu_kernel_selftests / ubuntu_bpf failed to build on 
F-OEM-5.10 (Cannot find a vmlinux for VMLINUX_BTF)

** Tags added: sru-20210719

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

Title:
  net test from ubuntu_kernel_selftests / ubuntu_bpf failed to build on
  F-OEM-5.10 (Cannot find a vmlinux for VMLINUX_BTF)

Status in ubuntu-kernel-tests:
  New
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Confirmed

Bug description:
  Issue found on 5.10.0-1017.18-oem

  When trying to build the prerequisite bpf test for the net test, the build 
failed with:
   *** Cannot find a vmlinux for VMLINUX_BTF at any of " ../../../../vmlinux 
/sys/kernel/btf/vmlinux /boot/vmlinux-5.10.0-1017-oem". Stop.

  This should not be considered as a regression as we didn't add
  ubuntu_kernel_selftest back to the test plan until recently, so it's
  not tested for a while.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1919122/+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 1872431] Re: ubuntu_bpf failed to build on 5.0 OEM-OSP1

2021-08-08 Thread Po-Hsu Lin

5.0 OEM EOL

** Changed in: ubuntu-kernel-tests
   Status: New => Won't Fix

** Changed in: linux-oem-osp1 (Ubuntu)
   Status: New => Won't Fix

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

Title:
  ubuntu_bpf failed to build on 5.0 OEM-OSP1

Status in ubuntu-kernel-tests:
  Won't Fix
Status in linux-oem-osp1 package in Ubuntu:
  Won't Fix

Bug description:
  Test build failed with: 
undefined reference to `RET_IF'

  make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests'
  stderr:
  /bin/sh: 1: llvm-readelf: not found
  /bin/sh: 1: llvm-readelf: not found
  Warning: Kernel ABI header at 'tools/include/uapi/linux/bpf.h' differs from 
latest version at 'include/uapi/linux/bpf.h'
  Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs 
from latest version at 'include/uapi/linux/if_link.h'
  test_select_reuseport.c: In function 'cleanup_per_test':
  test_select_reuseport.c:619:3: warning: implicit declaration of function 
'RET_IF' [-Wimplicit-function-declaration]
 RET_IF(err, "reset elem in result_map",
 ^~
  /tmp/ccvA9FfO.o: In function `main':
  test_select_reuseport.c:(.text.startup+0x8ad): undefined reference to `RET_IF'
  test_select_reuseport.c:(.text.startup+0x8ed): undefined reference to `RET_IF'
  collect2: error: ld returned 1 exit status
  make[1]: *** 
[/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/test_select_reuseport]
 Error 1
  make: *** [all] Error 2

  Possible fix:
  https://lists.ubuntu.com/archives/kernel-team/2020-April/108912.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1872431/+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 1937072] Re: [Lenovo Yoga Slim 7 14IIL05] PSR causes incomplete screen redraws

Please test latest drm-tip kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/

Headers are not needed.

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

Title:
  [Lenovo Yoga Slim 7 14IIL05] PSR causes incomplete screen redraws

Status in linux package in Ubuntu:
  Triaged
Status in linux-hwe-5.11 package in Ubuntu:
  Triaged

Bug description:
  In every 6/10 boot my ubuntu failed to start stuck on blank screen.
  Sometime touchpad stop working and unable to change my brightness
  after installation at first all feature are perfectly fine except
  screen glitch.Screen performance is laggy.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 21 17:13:28 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34]
 Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34]
  InstallationDate: Installed on 2021-07-21 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 82A1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/14/2021
  dmi.bios.release: 1.31
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DHCN31WW
  dmi.board.asset.tag: ���
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55722 WIN
  dmi.chassis.asset.tag: ���
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga Slim 7 14IIL05
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05:
  dmi.product.family: Yoga Slim 7 14IIL05
  dmi.product.name: 82A1
  dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05
  dmi.product.version: Yoga Slim 7 14IIL05
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937072/+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 1939197] Re: touchpad not working in hp firefly zbook

Kernel v5.4 is too old for this model. Please use HWE stack:
$ sudo apt install linux-generic-hwe-20.04-edge

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

Title:
  touchpad not working in hp firefly zbook

Status in linux package in Ubuntu:
  New

Bug description:
  touchpad not found in input devices

  Ubuntu 5.4.0-80.90-generic 5.4.124
  murugan@murugan:~$ sudo lspci -vnv
  00:00.0 0600: 8086:9a14 (rev 01)
Subsystem: 103c:880d
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

  00:02.0 0300: 8086:9a49 (rev 01) (prog-if 00 [VGA controller])
DeviceName: Onboard IGD
Subsystem: 103c:880d
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+ FLReset+
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, 
NROPrPrP-, LTR-
 10BitTagComp-, 10BitTagReq-, OBFF Not Supported, 
ExtFmt-, EETLPPrefix-
 EmergencyPowerReduction Not Supported, 
EmergencyPowerReductionInit-
 FRS-
 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
 AtomicOpsCtl: ReqEn-
Capabilities: [ac] MSI: Enable- Count=1/1 Maskable+ 64bit-
Address:   Data: 
Masking:   Pending: 
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] Process Address Space ID (PASID)
PASIDCap: Exec- Priv-, Max PASID Width: 14
PASIDCtl: Enable- Exec- Priv-
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] Page Request Interface (PRI)
PRICtl: Enable- Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 8000, Page Request Allocation: 

Capabilities: [320 v1] Single Root I/O Virtualization (SR-IOV)
IOVCap: Migration-, Interrupt Message Number: 000
IOVCtl: Enable- Migration- Interrupt- MSE- ARIHierarchy-
IOVSta: Migration-
Initial VFs: 7, Total VFs: 7, Number of VFs: 0, Function 
Dependency Link: 00
VF offset: 1, stride: 1, Device ID: 9a49
Supported Page Size: 0553, System Page Size: 0001
Region 0: Memory at 00401000 (64-bit, non-prefetchable)
Region 2: Memory at 00402000 (64-bit, prefetchable)
VF Migration: offset: , BIR: 0
Kernel modules: i915

  00:04.0 1180: 8086:9a03 (rev 01)
Subsystem: 103c:880d
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

  00:07.0 0604: 8086:9a23 (rev 01) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ 
TransPend-
LnkCap: Port #2, Speed 2.5GT/s, Width x4, ASPM L1, Exit Latency 
L1 <16us
ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
LnkCtl: ASPM L1 Enabled; RCB 64 bytes Dis

[Kernel-packages] [Bug 1938845] Re: Legion 7 16ITHg6 - Touchpad undetected

*** This bug is a duplicate of bug 1937056 ***
https://bugs.launchpad.net/bugs/1937056

** This bug has been marked a duplicate of bug 1937056
   Touchpad not working with ASUS TUF F15

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

Title:
  Legion 7 16ITHg6 - Touchpad undetected

Status in linux package in Ubuntu:
  New

Bug description:
  I received my Lenovo Legion 7i 16ITHg6 laptop today. The touchpad
  seems to be entirely undetected.

  I've attached the contents of /proc/bus/input/devices as devices.txt.
  No touchpad device is shown. USB mice work.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-25-generic 5.11.0-25.27
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hiryu  7344 F pulseaudio
   /dev/snd/controlC0:  hiryu  7344 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Tue Aug  3 20:05:13 2021
  InstallationDate: Installed on 2021-04-23 (103 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 82K6
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=825f1536-7d58-4097-9779-e5df2db0a6eb ro quiet splash 
nvidia-drm.modeset=1 resume=/dev/mapper/swap thinkpad_acpi.fan_control=1 
bluetooth.disable_ertm acpi_backlight=video vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-25-generic N/A
   linux-backports-modules-5.11.0-25-generic  N/A
   linux-firmware 1.197.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2021
  dmi.bios.release: 1.26
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H1CN26WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ITHg6
  dmi.ec.firmware.release: 1.26
  dmi.modalias: 
dmi:bvnLENOVO:bvrH1CN26WW:bd05/22/2021:br1.26:efr1.26:svnLENOVO:pn82K6:pvrLegion716ITHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ITHg6:
  dmi.product.family: Legion 7 16ITHg6
  dmi.product.name: 82K6
  dmi.product.sku: LENOVO_MT_82K6_BU_idea_FM_Legion 7 16ITHg6
  dmi.product.version: Legion 7 16ITHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938845/+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 1938936] Re: Broken Nvidia Prime on Lenovo Z70-80 (Nvidia 840m)

*** This bug is a duplicate of bug 1936708 ***
https://bugs.launchpad.net/bugs/1936708

** This bug has been marked a duplicate of bug 1936708
   Wobbly graphics on built-in display since linux-image-5.11.0-22-generic

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

Title:
  Broken Nvidia Prime on Lenovo Z70-80 (Nvidia 840m)

Status in linux package in Ubuntu:
  New

Bug description:
  I’m trying to revive a slightly old Lenovo Z70-80. I haven’t used it
  for a month or so. Then, I downloaded all the latest updates a couple
  of weeks ago and something broke. The screen looks as if it's tearing
  many times per second and some of the middle pixels are repeated on
  the edge of the screen. I've never seen it behave like that.

  I've had problems with Prime on this machine many times before, so I
  followed the usual steps: ensuing that nouveau is blacklisted,
  rebuilding the modules, using a custom xorg config, trying out
  multiple different driver versions, etc. Nothing helped. I even tried
  a complete re-install of Ubuntu, however, that didn’t help (everything
  was fine during the install).

  I still had an older kernel installed on my machine (5.11.0-16), I
  booted into it, built all the modules, etc (it started with Intel
  only, I believe). After a reboot back into 5.11.0-16, the Nvidia
  drivers started working perfectly. No matter which version. They're
  still broken in 5.11.0-25 and the kernel is the only difference.

  I've mentioned this on Nvidia forums already, but my post didn't get
  any attention there. It contains a few more details, like the Nvidia
  debug capture and a video of the craziness on my screen:
  https://forums.developer.nvidia.com/t/severely-distorted-image-on-a-
  laptop-with-ubuntu-21-04-nvidia-840m-470-57-02-and-older-
  drivers/185117

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-25-generic 5.11.0-25.27
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  manvydas   1414 F pulseaudio
   /dev/snd/controlC0:  manvydas   1414 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Wed Aug  4 20:11:57 2021
  InstallationDate: Installed on 2021-07-27 (7 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 80FG
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=363daad8-ef8a-44a7-a6b3-a879007f38d8 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-25-generic N/A
   linux-backports-modules-5.11.0-25-generic  N/A
   linux-firmware 1.197.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2015
  dmi.bios.release: 1.96
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ABCN96WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo Z70-80
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z70-80
  dmi.ec.firmware.release: 1.96
  dmi.modalias: 
dmi:bvnLENOVO:bvrABCN96WW:bd09/22/2015:br1.96:efr1.96:svnLENOVO:pn80FG:pvrLenovoZ70-80:rvnLENOVO:rnLenovoZ70-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoZ70-80:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80FG
  dmi.product.sku: LENOVO_MT_80FG_BU_idea_FM_Lenovo Z70-80
  dmi.product.version: Lenovo Z70-80
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938936/+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 1938464] Re: Ubuntu 20.04.2 Installation fails on ThinkPad X1 Nano

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

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

Title:
  Ubuntu 20.04.2 Installation fails on ThinkPad X1 Nano

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Issue:
  I've created Ubuntu 20.04.2 bootable USBs (tried two different sticks, and 
created on rufus/windows, etcher/macOS, and on Ubuntu 21.04, all following the 
Ubuntu bootable creation guide).
  With a new ThinkPad X1 Nano, I hit the "errno 5 input/output" error during 
installation.
  This error occurs after all options have been set, like username, password, 
partitioning options, etc., but appears to occur before the disk is actually 
written to.
  Fortunately, this means that I can boot back into my working Ubuntu 21.04 
installation, as I'll go into later.

  Hardware Information:
  - ThinkPad X1 Nano
  - Intel Core i7-1160G7 option
  - 512 GB SSD option
  - non-touch screen option
  - default options otherwise
  - came with Windows 10 Pro 20H2
  - serial number is from January 2021

  Additional Notes:
  - validated the ISO using the checksum and guide provided
  - always choosing the "Erase disk and install" option since I do not wish to 
dual boot
  - same result with secure boot enabled and disabled

  What does work:
  Ubuntu 21.04 installs perfectly fine and works perfectly fine. That's with 
secure boot enabled as well, so I doubt that this is related to secure boot. My 
hunch is that the 20.04.2 kernel is too old for my X1 Nano, and perhaps there 
was a stealth revision to its hardware/firmware since I (anecdotally) see X1 
Nano users installing 20.04.2 LTS perfectly fine. My hope is that Ubuntu 
20.04.03 LTS naturally works, but I'd prefer to install an LTS version as soon 
as possible (such as an Ubuntu 20.04.2.X, if possible).

  Kernel information:
  The installer crashes and goes into an unrecoverable state, so I could not 
gather information on the bootable itself (screen freezes a little, making it 
difficult to send a bug report). However, I can provide the Ubuntu 21.04 
information since it does work.
  - Ubuntu 5.11.0-25.27-generic 5.11.22
  - lspci-vnvn.log (attached)

  Please let me know if you require additional information, and how I
  can help. Thank you in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938464/+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 1937107] Re: Kernel Oops - unable to handle kernel paging request at

This should be fixed by Ubuntu-4.15.0-153.160.

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

Title:
  Kernel Oops - unable to handle kernel paging request at

Status in linux package in Ubuntu:
  New

Bug description:
  I had numerous kernel panics after upgrading to the latest kernel.
  Reverting to the previous Release 4.15.0-147 fixes the problem. I
  first noticed this when my desktop was "stuck". I switched to the
  console to run htop, to see if anything was blocking. And this seemed
  to consistently trigger the oops.

  Jul 21 13:22:07 nb0032 kernel: BUG: unable to handle kernel paging request at 
9df6410a7d7c
  Jul 21 13:22:07 nb0032 kernel: IP: kmem_cache_alloc+0x7a/0x1c0
  Jul 21 13:22:07 nb0032 kernel: PGD 0 P4D 0
  Jul 21 13:22:07 nb0032 kernel: Oops:  [#1] SMP PTI
  Jul 21 13:22:07 nb0032 kernel: Modules linked in: ccm rfcomm xt_nat veth 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter 
xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack 
ipt_REJECT nf_reject_ipv4 pci_stub xt_tcpudp vboxpci(OE) vboxnetadp(OE) bridge 
stp llc vboxnetflt(OE) vboxdrv(OE) ebtable_filter ebtables devlink 
ip6table_filter ip6_tables iptable_filter aufs overlay cmac bnep cdc_ether 
usbnet uvcvideo videobuf2_vmalloc videobuf2_memops btusb videobuf2_v4l2 btrtl 
btbcm videobuf2_core btintel videodev bluetooth media snd_usb_audio r8152 
snd_usbmidi_lib ecdh_generic mii binfmt_misc nls_iso8859_1 joydev hid_alps 
dell_smm_hwmon snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core
  Jul 21 13:22:07 nb0032 kernel:  dell_rbtn snd_soc_sst_dsp dell_laptop 
snd_soc_sst_ipc snd_soc_acpi intel_rapl snd_soc_core x86_pkg_temp_thermal 
intel_powerclamp arc4 snd_compress snd_hda_codec_realtek coretemp ac97_bus 
snd_hda_codec_generic kvm_intel snd_pcm_dmaengine snd_hda_intel snd_hda_codec 
kvm snd_hda_core snd_hwdep irqbypass snd_pcm intel_cstate intel_rapl_perf 
snd_seq_midi snd_seq_midi_event snd_rawmidi dell_wmi snd_seq dell_smbios dcdbas 
input_leds snd_seq_device intel_wmi_thunderbolt iwlmvm wmi_bmof snd_timer 
dell_wmi_descriptor serio_raw mac80211 snd iwlwifi soundcore rtsx_pci_ms 
cfg80211 memstick acpi_pad processor_thermal_device intel_hid int3403_thermal 
mac_hid sparse_keymap int3400_thermal int340x_thermal_zone intel_soc_dts_iosf 
acpi_thermal_rel intel_lpss_acpi intel_pch_thermal idma64 virt_dma mei_me
  Jul 21 13:22:07 nb0032 kernel:  mei intel_lpss_pci shpchp intel_lpss 
sch_fq_codel parport_pc ppdev nfsd nfs_acl lockd grace auth_rpcgss sunrpc lp 
parport ip_tables x_tables autofs4 btrfs zstd_compress algif_skcipher af_alg 
dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid 
i915 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i2c_algo_bit pcbc 
rtsx_pci_sdmmc drm_kms_helper syscopyarea e1000e sysfillrect sysimgblt 
fb_sys_fops ptp aesni_intel aes_x86_64 crypto_simd glue_helper cryptd pps_core 
drm ahci rtsx_pci libahci i2c_hid wmi hid video
  Jul 21 13:22:07 nb0032 kernel: CPU: 3 PID: 8983 Comm: htop Tainted: G 
  OE4.15.0-151-generic #157-Ubuntu
  Jul 21 13:22:07 nb0032 kernel: Hardware name: Dell Inc. Latitude 7480/00F6D3, 
BIOS 1.11.1 07/12/2018
  Jul 21 13:22:07 nb0032 kernel: RIP: 0010:kmem_cache_alloc+0x7a/0x1c0
  Jul 21 13:22:07 nb0032 kernel: RSP: 0018:aa38d1e17c50 EFLAGS: 00010282
  Jul 21 13:22:07 nb0032 kernel: RAX: 9df6410a7d7c RBX:  
RCX: 9d3b832079c0
  Jul 21 13:22:07 nb0032 kernel: RDX: 0028533c RSI: 014080c0 
RDI: 2cfbc183c370
  Jul 21 13:22:07 nb0032 kernel: RBP: aa38d1e17c80 R08: ca38bfdbc370 
R09: dfc0
  Jul 21 13:22:07 nb0032 kernel: R10: aa38d1e17eb8 R11:  
R12: 9df6410a7d7c
  Jul 21 13:22:07 nb0032 kernel: R13: 014080c0 R14: 9d3cdd125200 
R15: 9d3c9892d800
  Jul 21 13:22:07 nb0032 kernel: FS:  7fbe9e271740() 
GS:9d3cfe58() knlGS:
  Jul 21 13:22:07 nb0032 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Jul 21 13:22:07 nb0032 kernel: CR2: 9df6410a7d7c CR3: 000570a5a003 
CR4: 003626e0
  Jul 21 13:22:07 nb0032 kernel: DR0:  DR1:  
DR2: 
  Jul 21 13:22:07 nb0032 kernel: DR3:  DR6: fffe0ff0 
DR7: 0400
  Jul 21 13:22:07 nb0032 kernel: Call Trace:
  Jul 21 13:22:07 nb0032 kernel:  ? get_empty_filp+0x5c/0x1c0
  Jul 21 13:22:07 nb0032 kernel:  get_empty_filp+0x5c/0x1c0
  Jul 21 13:22:07 nb0032 kernel:  path_openat+0x40/0x18b0
  Jul 21 13:22:07 nb0032 kernel:  ? do_task_stat+0x8b0/0xbc0
  Jul 21 13:22:07 nb0032 kernel:  ? put_dec+0x18/0xa0
  Jul 21 13:22:07 nb0032 kernel:

[Kernel-packages] [Bug 1938345] Re: Touchpad not working

Please try newer images like this one:
http://cdimages.ubuntu.com/focal/daily-live/current/focal-desktop-amd64.iso

** 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/1938345

Title:
  Touchpad not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Touchpad does not work at all and doesn't show up when I run cat
  /proc/bus/input/devices

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-42-generic 5.4.0-42.46
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 5415 F pulseaudio
   /dev/snd/controlC0:  ubuntu 5415 F pulseaudio
  CasperMD5CheckMismatches: ./boot/grub/efi.img
  CasperMD5CheckResult: fail
  CasperVersion: 1.445.1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 28 21:47:10 2021
  LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Acer Nitro AN515-54
  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=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.09
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Octavia_CFS
  dmi.board.vendor: CFL
  dmi.board.version: V1.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09:bd08/02/2019:svnAcer:pnNitroAN515-54:pvrV1.09:rvnCFL:rnOctavia_CFS:rvrV1.09:cvnAcer:ct10:cvrV1.09:
  dmi.product.family: Nitro 5
  dmi.product.name: Nitro AN515-54
  dmi.product.sku: 
  dmi.product.version: V1.09
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938345/+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 1938096] Re: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend

Can you please run `watch -n0 cat /proc/interrupts` and check whether
"i2c_designware" or "SYNA8009:00" number is increasing without touching
the touchpad?

** 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/1938096

Title:
  [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after
  resume from suspend

Status in libinput package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hardware: Thinkpad X1 Carbon, 9th generation
  Touchpad: SYNA8009:00 06CB:CE57

  Right after a clean reboot, the touchpad works fine. No issues
  whatsoever. But after resuming from even its first suspend after a
  clean boot, the touchpad feels less responsive, choppy or even laggy.

  I have tried removing and re-inserting some HID kernel modules,
  "psmouse", and setting i915.psr_enabled=0 in kernelstubs. Haven't
  found anything that fixes it yet. The trackpoint works flawlessly all
  the time, so that is the current backup when I don't have an external
  mouse connected.

  My installed OS is Pop!_Os 21.04, but I have tested and confirmed this
  on a live USB with Ubuntu 21.04 as well.

  I have also tried upgrading to the latest 5.13.5 and 5.14.0rc2 kernels
  from the mainline PPA, and tried bumping the libinput10 to 1.18.0 from
  the impish repos.

  To recreate:
  1. Reboot a X1C9 machine and see that the touchpad works fine
  2. Suspend it (to RAM, need to change a BiOS setting so it doesn't do a 
software suspend)
  3. Resume from suspend and see that touchpad acts differently and less 
responsive than right after a clean boot

  What is expected:
  1. Same responsive touchpad experience after resuming from suspend as right 
after a clean boot.

  
  ---

  
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: pop:GNOME
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroRelease: Pop!_OS 21.04
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
     Subsystem: Lenovo Iris Xe Graphics [17aa:22d5]
  MachineType: LENOVO 20XW005PMX
  Package: libinput10 1.18.0-1 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: 
initrd=\EFI\Pop_OS-e5934199-eb91-4da9-9e38-0ad1de1baeb2\initrd.img 
root=UUID=e5934199-eb91-4da9-9e38-0ad1de1baeb2 ro quiet 
systemd.show_status=false loglevel=0 splash
  Tags: hirsute third-party-packages ubuntu
  Uname: Linux 5.13.5-051305-generic x86_64
  UnreportableReason: This does not seem to be an official Pop!_OS package. 
Please retry after updating the indexes of available packages, if that does not 
work then remove related third party packages and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm lpadmin plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 06/15/2021
  dmi.bios.release: 1.42
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET66W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XW005PMX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.26
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET66W(1.42):bd06/15/2021:br1.42:efr1.26:svnLENOVO:pn20XW005PMX:pvrThinkPadX1CarbonGen9:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:rvnLENOVO:rn20XW005PMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XW005PMX
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2pop0~1624392450~21.04~6fbdfd2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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

[Kernel-packages] [Bug 1938099] Re: Neither laptop kepboard nor touchpad work

Does cold boot always help?

** 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/1938099

Title:
  Neither laptop kepboard nor touchpad work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Both worked previously and at some point just stopped.

  I ran these commands in an attempt to fix but it may have worsened the issue:
apt-get update 
apt-get install xserver-xorg-input-all
apt-get install ubuntu-desktop
apt-get install ubuntu-minimal
apt-get install xorg xserver-xorg
apt-get install xserver-xorg-input-evdev
apt-get install xserver-xorg-video-vmware

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-25-generic 5.11.0-25.27
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alex   1119 F pulseaudio
   /dev/snd/pcmC1D0p:   alex   1119 F...m pulseaudio
   /dev/snd/controlC0:  alex   1119 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Mon Jul 26 19:04:27 2021
  InstallationDate: Installed on 2021-07-21 (5 days ago)
  InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: TOSHIBA Satellite C875D
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=872c0009-76c1-4ee5-a2c2-f9845844dee0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-25-generic N/A
   linux-backports-modules-5.11.0-25-generic  N/A
   linux-firmware 1.197.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2012
  dmi.bios.release: 6.30
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: PLCSC8
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.ec.firmware.release: 6.0
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr6.0:svnTOSHIBA:pnSatelliteC875D:pvrPSCBGU-001009:rvnAMD:rnPLCSC8:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: Satellite C875D
  dmi.product.sku: PSCBGU
  dmi.product.version: PSCBGU-001009
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938099/+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 1937321] Re: System freeze (amdgpu kernel crash on resume from suspend)

Please install "linux-oem-20.04c" and see if the OEM 5.13 kernel
helps...

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

Title:
  System freeze (amdgpu kernel crash on resume from suspend)

Status in linux-hwe-5.8 package in Ubuntu:
  Incomplete

Bug description:
  System freezes after I close the lid on the laptop and leave it closed 
overnight. It doesn't respond to any key presses or mouse clicks including 
Ctrl-Alt+F4. my only recourse is to force the power off. Sometimes it has the 
"suspend" screen showing but mostly it's just black. The Power settings -Dim 
screen when inactive = yes
Blank screen = never
Wifi and Bluetooth can be turned off to save power = yes
Automatic suspend on battery power = yes
Power button action = Power off

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-63-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 22 17:34:17 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Renoir [103c:87cf]
  InstallationDate: Installed on 2021-06-30 (22 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: HP HP Laptop 15-ef1xxx
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic 
root=UUID=f66ca4c6-ec88-43af-81a3-7d994d7a217b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/10/2021
  dmi.bios.release: 15.34
  dmi.bios.vendor: AMI
  dmi.bios.version: F.34
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8707
  dmi.board.vendor: HP
  dmi.board.version: 37.19
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 37.19
  dmi.modalias: 
dmi:bvnAMI:bvrF.34:bd03/10/2021:br15.34:efr37.19:svnHP:pnHPLaptop15-ef1xxx:pvr:rvnHP:rn8707:rvr37.19:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-ef1xxx
  dmi.product.sku: 27A48UA#ABA
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  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+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1937321/+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 1917674] Re: [amdgpu] kernel crash when resuming from automatic suspension to RAM (started in 5.7.0, not in 5.6.19)

Please test latest drm-tip kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/

Headers are not needed.

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

Title:
  [amdgpu] kernel crash when resuming from automatic suspension to RAM
  (started in 5.7.0, not in 5.6.19)

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.8 package in Ubuntu:
  Confirmed

Bug description:
  Automatic suspension causes the system to freeze on resume. This
  doesn't happen if I suspend it manually by opening the system menu and
  pressing the suspend button. Suspension works flawlessly when it is
  triggered manually.

  When the system resumes from automatic suspension, the lock screen is
  visible but does not respond. It's frozen. A notification says
  something like "system will suspend shortly due to inactivity". It
  never goes away.

  The keyboard responds during this (at least for a while). The CAPS
  LOCK LED turns on and off as I press it (with no delay). Sometimes I
  can even switch to another TTY and kill the X server, which is why I'm
  reporting it against gnome-shell. When switching TTY is impossible, I
  use the "REISUB" combination to shut down. Either way, I always lose
  the running session.

  This is reproducible about 60% of the time. Eventually I ended up
  disabling it and relying only on manual suspension.

  # Additional information:
  1) Ubuntu 20.04.2 LTS / Release: 20.04
  2) gnome-shell 3.36.4-1ubuntu1~20.04.2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  3 16:56:01 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-01-31 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1884 F pulseaudio
   /dev/snd/controlC1:  dsilva 1884 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-31 (49 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 004: ID 0951:16de Kingston Technology HyperX Pulsefire Core
   Bus 001 Device 003: ID 0951:16d2 Kingston Technology HyperX Alloy FPS Pro 
Mechanical Gaming Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
  Package: linux-hwe-5.8
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-45-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  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.8.0-45-generic N/A
   linux-backports-modules-5.8.0-45-generic  N/A
   linux-firmware1.187.10
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.8.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 05/27/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: B460M DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd05/27/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B460 MB
  dmi.product.name: B460MDS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Kernel-packages] [Bug 1936673] Re: BUG: kernel NULL pointer dereference, address: 0000000000000000

2021-08-08 Thread Stefan Bader

This bug should be fixed in Ubuntu-5.4.0-80.90 by:

Author: Anna Schumaker 
Date:   Wed May 19 12:54:51 2021 -0400
NFSv4: Fix a NULL pointer dereference in pnfs_mark_matching_lsegs_return()

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

** Changed in: linux (Ubuntu Focal)
   Importance: Undecided => High

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

** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1936673

Title:
  BUG: kernel NULL pointer dereference, address: 

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

Bug description:
  Hi Kernelguys,

  after updating my kernel from 5.4.0-74.83-generic to 5.4.0-77.86 I get
  a kernelpanic when putting load onto my NFSv4.1 mount.


  
  About the System:

  I run a Galera Cluster on a VMWare VM with data stored on a NetApp
  system with NFSv4.1:

  # grep nfs4 /proc/mounts
  server:/GALERANFS_MUC_2_LOG /GALERANFS_MUC_LOG nfs4 
rw,noatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=nfs-client-ip,local_lock=none,addr=nfs-server-ip
 0 0
  nfs-server-ip:/GALERANFS_MUC_2_BACKUP /GALERANFS_MUC_BACKUP nfs4 
rw,noatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=nfs-client-ip,local_lock=none,addr=nfs-server-ip
 0 0
  nfs-server-ip:/GALERANFS_MUC_2_DATA /GALERANFS_MUC_DATA nfs4 
rw,noatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=nfs-client-ip,local_lock=none,addr=nfs-server-ip
 0 0

  The panic I get when I give a little load on the NFS mount with my
  mariadb-server is:

  Jul 16 15:26:10 maria2021-muc-2 systemd[1]: Starting MariaDB 10.5.11 database 
server...
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.549355] BUG: kernel NULL 
pointer dereference, address: 
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.551391] #PF: supervisor read 
access in kernel mode
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.553377] #PF: 
error_code(0x) - not-present page
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.555350] PGD 0 P4D 0 
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.557268] Oops:  [#7] SMP PTI
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.559186] CPU: 0 PID: 44171 
Comm: mysqld Tainted: P  DO  5.4.0-77-generic #86-Ubuntu
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.560644] Hardware name: VMware, 
Inc. VMware7,1/440BX Desktop Reference Platform, BIOS 
VMW71.00V.17369862.B64.2012240522 12/24/2020
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.562497] RIP: 
0010:pnfs_mark_matching_lsegs_return+0x108/0x150 [nfsv4]
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.563447] Code: 01 f0 80 4b 40 
08 49 8b 06 4c 89 f3 4c 39 75 d0 75 9d 8b 45 bc 85 c0 75 3b 48 8b 4d c8 48 8b 
41 38 48 8d 51 38 48 39 c2 74 23 <41>
   8b 34 24 48 8b 7d c8 44 89 fa e8 88 e3 ff ff 31 c0 48 83 c4 20
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.565380] RSP: 
0018:a6e91c113d68 EFLAGS: 00010283
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.566361] RAX: 95e263669540 
RBX: 95e263669268 RCX: 95e263669240
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.567364] RDX: 95e263669278 
RSI: 95e263669540 RDI: 95e263669240
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.568358] RBP: a6e91c113db0 
R08: 0064 R09: 
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.569356] R10: 95e24b0ed480 
R11: 003d R12: 
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.570355] R13: 95e263669278 
R14: 95e263669268 R15: 
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.571353] FS:  
7f5d988cf800() GS:95e277a0() knlGS:
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.572340] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.573317] CR2:  
CR3: 0002229a2003 CR4: 001606f0
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.574289] Call Trace:
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.575260]  
_pnfs_return_layout+0x118/0x230 [nfsv4]
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.576272]  ? 
nfs_inode_detach_delegation+0x29/0x70 [nfsv4]
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.577244]  
nfs4_evict_inode+0x70/0x80 [nfsv4]
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.578205]  evict+0xd2/0x1b0
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.579174]  iput+0x148/0x210
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.580104]  
do_unlinkat+0x1c5/0x2d0
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.581014]  
__x64_sys_unlink+0x23/0x30
  Jul 16 15:26:10 maria2021-muc-2 k

[Kernel-packages] [Bug 1738534] Re: Processor turbo dsiabled/throttled after suspend

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

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

Title:
  Processor turbo dsiabled/throttled after suspend

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

Bug description:
  After suspending/resuming my laptop on battery power, I noticed choppy
  video playback.  I've narrowed it down to the CPU being locked to
  lower frequencies after suspend/resume (only on battery).  Plugging
  the laptop back in does not restore the normal performance, nor does
  suspend/resume after plugging it back in.  The performance doesn't
  drop until after the suspend/resume, I'm not sure if it is _supposed_
  to throttle when on battery, but either way the behaviour is wrong.

  Doing a full shutdown and restart restores the performance to normal.

  Prior to a suspend/resume cycle, cpupower reports:

  $ sudo cpupower frequency-info
  analyzing CPU 0:
driver: intel_pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency:  Cannot determine or is not supported.
hardware limits: 800 MHz - 3.00 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 800 MHz and 3.00 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 1.26 GHz (asserted by call to kernel)
boost state support:
  Supported: yes
  Active: yes
  2800 MHz max turbo 4 active cores
  2800 MHz max turbo 3 active cores
  2800 MHz max turbo 2 active cores
  3000 MHz max turbo 1 active cores

  Afterwards, the frequency is clamped (cpufreq-set -r --max=3.0GHz has
  no effect) and turbo is disabled:

  $ sudo cpupower frequency-info
  analyzing CPU 0:
driver: intel_pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency:  Cannot determine or is not supported.
hardware limits: 800 MHz - 3.00 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 800 MHz and 1.80 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 950 MHz (asserted by call to kernel)
boost state support:
  Supported: no
  Active: no
  2800 MHz max turbo 4 active cores
  2800 MHz max turbo 3 active cores
  2800 MHz max turbo 2 active cores
  3000 MHz max turbo 1 active cores

  Trying to re-enable turbo mode by setting the no_turbo intel_pstate
  /sys/ entry back to 0 is rejected:

  $ echo 0 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo
  0
  tee: /sys/devices/system/cpu/intel_pstate/no_turbo: Operation not permitted

  However, these two commands *do* work around the problem, forcing
  turbo mode back on and then restoring the normal frequency range:

  sudo x86_energy_perf_policy --turbo-enable 1
  sudo cpufreq-set -r --min=0.8GHz --max=3.0GHz

  I also see this error in dmesg after some resumes (but the above
  problem sometimes happens without this error message):

  Dec 16 11:36:25 shauns-laptop kernel: intel_pstate: Turbo disabled by
  BIOS or unavailable on processor

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-19-generic 4.13.0-19.22
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shaun  1194 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 16 11:18:12 2017
  InstallationDate: Installed on 2017-12-14 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 001 Device 004: ID 2232:1024 Silicon Motion 
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-19-generic 
root=UUID=7352de8c-0017-44e1-81fb-0145ad9c1185 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1

[Kernel-packages] [Bug 1939157] Re: HWE kernels: NFSv4.1 NULL pointer dereference

2021-08-08 Thread Stefan Bader

This was fixed in Ubuntu-5.4.0-80.90 by:

Author: Anna Schumaker 
Date: Wed May 19 12:54:51 2021 -0400
NFSv4: Fix a NULL pointer dereference in pnfs_mark_matching_lsegs_return()

For 5.11 this is pending release as Ubuntu-5.11.0-26.28 (currently in
-proposed).

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

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

** Changed in: linux (Ubuntu Hirsute)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Hirsute)
   Status: New => 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/1939157

Title:
  HWE kernels: NFSv4.1 NULL pointer dereference

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Hirsute:
  Fix Committed

Bug description:
  Ubuntu 20.04 systems running as NFSv4.1 clients are experiencing
  crashes (in this case with a NetApp filer mounted):

  [  266.199481] BUG: kernel NULL pointer dereference, address: 
  [  266.199495] #PF: supervisor read access in kernel mode
  [  266.199500] #PF: error_code(0x) - not-present page
  [  266.199503] PGD 0 P4D 0
  [  266.199511] Oops:  [#1] SMP PTI
  [  266.199518] CPU: 15 PID: 2244 Comm: tracker-extract Not tainted 
5.11.0-25-generic #27~20.04.1-Ubuntu
  [  266.199525] Hardware name: Intel Corporation S2600GZ/S2600GZ, BIOS 
SE5C600.86B.02.06.0006.032420170950 03/24/2017
  [  266.199529] RIP: 0010:pnfs_mark_matching_lsegs_return+0xfe/0x140 [nfsv4]
  [  266.199631] Code: f0 41 80 4d 50 08 49 8b 06 4d 89 f5 4c 39 75 d0 75 9b 8b 
45 bc 85 c0 75 3b 48 8b 45 c8 48 8b 50 38 48 83 c0 38 48 39 c2 74 23 <41> 8b 34 
24 48 8b 7d c8 44 89 fa e8 42 e0 ff ff 31 c0 48 83 c4 20
  [  266.199637] RSP: 0018:ae23a19a7c88 EFLAGS: 00010297
  [  266.199642] RAX: a048621ef238 RBX: a048621ef238 RCX: 

  [  266.199646] RDX: a04847636780 RSI: a04847636780 RDI: 
a048621ef200
  [  266.199650] RBP: ae23a19a7cd0 R08: 0001 R09: 
a086febdcc10
  [  266.199653] R10: a0677ffd6b80 R11: 0003 R12: 

  [  266.199657] R13: a048621ef228 R14: a048621ef228 R15: 

  [  266.199661] FS:  7f9de3440340() GS:a086febc() 
knlGS:
  [  266.199665] CS:  0010 DS:  ES:  CR0: 80050033
  [  266.199669] CR2:  CR3: 00012ed86006 CR4: 
001706e0
  [  266.199674] Call Trace:
  [  266.199682]  _pnfs_return_layout+0x13d/0x2c0 [nfsv4]
  [  266.199755]  ? nfs_put_delegation+0x4c/0x70 [nfsv4]
  [  266.199814]  nfs4_evict_inode+0x78/0x80 [nfsv4]
  [  266.199870]  evict+0xd2/0x180
  [  266.199879]  iput+0x18f/0x200
  [  266.199884]  nfs_dentry_iput+0x33/0x60 [nfs]
  [  266.199934]  dentry_unlink_inode+0xb8/0x110
  [  266.199946]  __dentry_kill+0xdf/0x180
  [  266.199953]  dput+0x171/0x320
  [  266.199960]  do_renameat2+0x387/0x500
  [  266.199968]  __x64_sys_rename+0x45/0x50
  [  266.199974]  do_syscall_64+0x38/0x90
  [  266.199987]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [  266.16] RIP: 0033:0x7f9de644200b
  [  266.23] Code: e8 aa ce 0a 00 85 c0 0f 95 c0 0f b6 c0 f7 d8 5d c3 66 0f 
1f 44 00 00 b8 ff ff ff ff 5d c3 90 f3 0f 1e fa b8 52 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 05 c3 0f 1f 40 00 48 8b 15 51 4e 18 00 f7 d8
  [  266.28] RSP: 002b:7ffe70e5f008 EFLAGS: 0246 ORIG_RAX: 
0052
  [  266.200014] RAX: ffda RBX: 55a5ed503070 RCX: 
7f9de644200b
  [  266.200018] RDX: 55a5ed37b940 RSI: 55a5ed1db250 RDI: 
55a5ed4aea00
  [  266.200022] RBP: 55a5ed503060 R08:  R09: 

  [  266.200025] R10: 000d R11: 0246 R12: 
0001
  [  266.200029] R13: 55a5ed503078 R14: 55a5ed503040 R15: 
55a5ed37b980
  [  266.200036] Modules linked in: nfs_layout_nfsv41_files rpcsec_gss_krb5 
auth_rpcgss nfsv4 nfs lockd grace nfs_ssc fscache intel_rapl_msr 
intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp 
crct10dif_
  pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper mgag200 
rapl joydev input_leds intel_cstate drm_kms_helper ipmi_si ipmi_devintf cec 
rc_core fb_sys_fops syscopyarea sysfillrect mei_me ipmi_msghandler s
  ysimgblt mei ioatdma mac_hid ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl 
ip6t_rt ipt_REJECT nf_reject_ipv4 xt_comment nf_log_ipv4 nf_log_common 
xt_addrtype xt_limit xt_LOG xt_recent xt_tcpudp sch_fq_codel xt_state xt_conn

  This bug occurs in all recent 20.04 HWE kernels (both 5.8 and 5.11).
  I believe it is fixed by https://patchwork.kernel.org/project/linux-
  nfs/patch/20210519165451.412566-1-anna.schuma...@netapp.com/ -- please
  consider backporting this patch.

  (The bug was briefly also present in the 5.4 kernels, but was fixed in
  5.4.0-79: see
  https://bugs.launch

[Kernel-packages] [Bug 1872311] Re: Brightness hotkeys not working on Lenovo S740

Please test latest drm-tip kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/

Headers are not needed.


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

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

Title:
  Brightness hotkeys not working on Lenovo S740

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Brightness hotkeys (Fn + F11 for decrease and Fn + F12 for increase)
  do not work on Ubuntu 20.04 and Lenovo S740 laptop. The brightness
  hotkeys did not work on 19.10 either.

  I followed the guide here:
  https://wiki.ubuntu.com/Hotkeys/Troubleshooting

  In "Step-by-step Troubleshooting", none of the steps (1-7) did produce
  any reaction to brightness change key combinations. However, I am able
  to change the laptop screen brightness through the brightness applet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  elias  1447 F pulseaudio
   /dev/snd/controlC0:  elias  1447 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 16:12:01 2020
  InstallationDate: Installed on 2019-11-19 (144 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 81RS
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=101c7da4-860d-4496-ae06-d98699795f9a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-04 (7 days ago)
  dmi.bios.date: 03/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BYCN33WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga S740-14IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrBYCN33WW:bd03/10/2020:svnLENOVO:pn81RS:pvrLenovoYogaS740-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS740-14IIL:
  dmi.product.family: Yoga S740-14IIL
  dmi.product.name: 81RS
  dmi.product.sku: LENOVO_MT_81RS_BU_idea_FM_Yoga S740-14IIL
  dmi.product.version: Lenovo Yoga S740-14IIL
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872311/+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 1912908] Re: USB keyboard not working

Would it be possible for you to do a kernel bisection?

First, find the last -rc kernel works and the first -rc kernel doesn’t
work from http://kernel.ubuntu.com/~kernel-ppa/mainline/

Then,
$ sudo apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$ git bisect start
$ git bisect good $(the working version you found)
$ git bisect bad $(the non-working version found)
$ make localmodconfig
$ make -j`nproc` deb-pkg
Install the newly built kernel, then reboot with it.
If it still have the same issue,
$ git bisect bad
Otherwise,
$ git bisect good
Repeat to "make -j`nproc` deb-pkg" until you find the offending commit.

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

Title:
  USB keyboard not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu 20.04.1 on a Intel NUC9.
  My USB keyboard is working fine with kernel 5.4.0-64 but doesn't work at all 
with the 5.8.0-40 kernel. I tested other external keyboards but none worked.
  My mouse is working fine though.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04.1 LTS (Focal Fossa)
  Affected Package:
  - linux-image-5.8.0-36-generic
  - linux-image-5.8.0-38-generic
  - linux-image-5.8.0-40-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-29 (178 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Intel(R) Client Systems NUC9VXQNX
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-40-generic 
root=UUID=22f56864-ed38-49fa-9f90-e8c2a05726aa ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-40-generic N/A
   linux-backports-modules-5.8.0-40-generic  N/A
   linux-firmware1.187.8
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.8.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: QNCFLX70.0034.2019.1125.1424
  dmi.board.name: NUC9VXQNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K47179-402
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.ec.firmware.release: 24.33
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrQNCFLX70.0034.2019.1125.1424:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9VXQNX:pvrK47173-402:rvnIntelCorporation:rnNUC9VXQNB:rvrK47179-402:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: QN
  dmi.product.name: NUC9VXQNX
  dmi.product.sku: BKNUC9VXQNX
  dmi.product.version: K47173-402
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912908/+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 1908139] Re: ThinkPad T14s external display not working on ThinkPad USB-C Dock Gen2

Please test latest drm-tip kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/

Headers are not needed.

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

Title:
  ThinkPad T14s external display not working on ThinkPad USB-C Dock Gen2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  laptop: ThinkPad T14s Gen 1 - AMD Ryzen 7 PRO 4750U
  docking station: ThinkPad USB-C Dock 2. Gen.
  external display: NE MultiSync EA275UHD
  OS: Ubuntu 20.10 - kernel 5.8.0

  Plugging the external display into one of the docking station's two
  DisplayPort connectors leads to the screen resolution changing on the
  laptop's builtin display and the external display waking up but
  showing no picture and displaying "no-signal" after a bit.

  Plugging the external display into the docking station's HDMI
  connector leads to no visible reaction on either the external nor the
  builtin display.

  Plugging the external display into the laptop's builtin HDMI connector
  works as expected. The external display is recognized and shows an
  image.

  I have recorded the output on `dmesg` during the steps mentioned above
  and inserted explanations using `echo MSG >/dev/kmsg`. The output
  follows at the end of the message. I believe `ubuntu-bug` should also
  attach the full log.

  All above modes of connection work as expected with the same laptop, dock, 
and display on Windows 10 (installed as dual boot along side Ubuntu).
  All above modes of connection also work as expected with an older laptop 
(ThinkPad T470s - Ubuntu 20.04 - kernel 5.4.0), and the same dock and display.
  This leads me to believe that this is not a hardware issue.

  The following bug seems related, but seems to have been observed on
  faulty hardware according to its author. Therefore, I decided to open
  a separate bug report.
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899336

  ```
  [  343.372511] plugging DisplayPort into dock port 1
  [  352.666113] [drm] DP Alt mode state on HPD: 1
  [  352.749192] [drm] DM_MST: starting TM on aconnector: 2105a317 [id: 
75]
  [  352.858482] [drm] amdgpu_dm_irq_schedule_work FAILED src 9
  [  352.888400] [drm] amdgpu_dm_irq_schedule_work FAILED src 9
  [  352.892555] [drm] amdgpu_dm_irq_schedule_work FAILED src 9
  [  352.896719] [drm] amdgpu_dm_irq_schedule_work FAILED src 9
  [  352.900876] [drm] amdgpu_dm_irq_schedule_work FAILED src 9
  [  352.905596] [drm] amdgpu_dm_irq_schedule_work FAILED src 9
  [  352.910323] [drm] amdgpu_dm_irq_schedule_work FAILED src 9
  [  352.914485] [drm] amdgpu_dm_irq_schedule_work FAILED src 9
  [  377.353566] plugged in - no signal
  [  396.728970] unplugging
  [  403.001418] [drm] DM_MST: stopping TM on aconnector: 2105a317 [id: 
75]
  [  415.576397] unplugged
  [  431.500729] plugging DisplayPort into dock port 2
  [  437.607724] [drm] DP Alt mode state on HPD: 1
  [  437.681116] [drm] DM_MST: starting TM on aconnector: 2105a317 [id: 
75]
  [  437.790303] [drm] amdgpu_dm_irq_schedule_work FAILED src 9
  [  437.820138] [drm] amdgpu_dm_irq_schedule_work FAILED src 9
  [  437.824305] [drm] amdgpu_dm_irq_schedule_work FAILED src 9
  [  437.828462] [drm] amdgpu_dm_irq_schedule_work FAILED src 9
  [  437.832619] [drm] amdgpu_dm_irq_schedule_work FAILED src 9
  [  437.837029] [drm] amdgpu_dm_irq_schedule_work FAILED src 9
  [  437.841984] [drm] amdgpu_dm_irq_schedule_work FAILED src 9
  [  437.846144] [drm] amdgpu_dm_irq_schedule_work FAILED src 9
  [  458.999849] plugged in - no signal
  [  465.702949] unplugging
  [  476.127418] [drm] DM_MST: stopping TM on aconnector: 2105a317 [id: 
75]
  [  476.956491] [drm] Failed to add display topology, DTM TA is not 
initialized.
  [  488.792533] unplugged
  [  529.801179] plugging HDMI into dock
  [  536.721076] [drm] DP Alt mode state on HPD: 1
  [  536.792947] [drm] DM_MST: starting TM on aconnector: 2105a317 [id: 
75]
  [  536.901958] [drm] amdgpu_dm_irq_schedule_work FAILED src 9
  [  536.906123] [drm] amdgpu_dm_irq_schedule_work FAILED src 9
  [  536.910288] [drm] amdgpu_dm_irq_schedule_work FAILED src 9
  [  536.914611] [drm] amdgpu_dm_irq_schedule_work FAILED src 9
  [  536.919568] [drm] amdgpu_dm_irq_schedule_work FAILED src 9
  [  536.923725] [drm] amdgpu_dm_irq_schedule_work FAILED src 9
  [  536.927888] [drm] amdgpu_dm_irq_schedule_work FAILED src 9
  [  536.932047] [drm] amdgpu_dm_irq_schedule_work FAILED src 9
  [  536.936451] [drm] amdgpu_dm_irq_schedule_work FAILED src 9
  [  536.941486] [drm] amdgpu_dm_irq_schedule_work FAILED src 9
  [  536.945651] [drm] amdgpu_dm_irq_schedule_work FAILED src 9
  [  536.949808] [drm] amdgpu_dm_irq_schedule_work FAILED src 9
  [  537.010093] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb 
271ba325 port 1: DPCD read on addr 0x60 for 1 bytes NAKed
  [  592.844147] plugged in - d

[Kernel-packages] [Bug 1913933] Re: System freeze while dbus-daemon execution

IIRC the CPU power saving on first gen Ryzen needs to be disabled to get
a stable system...

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

Title:
  System freeze while dbus-daemon execution

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I regularly get my system frozen while using. It does not occur on any
  user interaction I do periodically, so I checked the log files last
  time it happened:

  These are the last 3 kernel log entries before the freeze:

  Jan 30 15:34:29 ubuntu kernel: [24749.856278] audit: type=1400 
audit(1612017269.344:43): apparmor="DENIED" operation="open" 
profile="snap.standard-notes.standard-notes" 
name="/home/chshr/.dotfiles/config/.config/gtk-3.0/settings.ini" pid=21631 
comm="standard-notes" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  Jan 30 15:34:29 ubuntu kernel: [24749.903525] audit: type=1107 
audit(1612017269.392:44): pid=1236 uid=103 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" mask="send" name="org.bluez" pid=21631 
label="snap.standard-notes.standard-notes"
  Jan 30 15:34:29 ubuntu kernel: [24749.903525]  exe="/usr/bin/dbus-daemon" 
sauid=103 hostname=? addr=? terminal=?'
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

  So I think this is related to the dbus-daemon.

  If you need any more information, please let me know so I can provide
  them.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: dbus 1.12.20-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Jan 31 09:22:49 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  SourcePackage: dbus
  UpgradeStatus: Upgraded to groovy on 2021-01-24 (6 days ago)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chshr  2241 F pulseaudio
   /dev/snd/controlC0:  chshr  2241 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=UUID=a16d1655-2fcf-4952-8a1b-3a45eb9b2c52
  MachineType: Micro-Star International Co., Ltd MS-7A34
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=4542740f-595f-4809-a71b-f170ee2827e3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-41-generic N/A
   linux-backports-modules-5.8.0-41-generic  N/A
   linux-firmware1.190.3
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: yes
    Hard blocked: no
  Tags:  groovy
  Uname: Linux 5.8.0-41-generic x86_64
  Upgrad

[Kernel-packages] [Bug 1931509] Re: System hang with kernel general protection fault due to dell-wmi-sysman sysman_init failure

2021-08-08 Thread Anthony Wong

** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  System hang with kernel general protection fault due to dell-wmi-
  sysman sysman_init failure

Status in HWE Next:
  Fix Released
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Fix Released

Bug description:
  [Impact]
  Encountered below protection fault while doing reboot test since 
Ubuntu-oem-5.10-5.10.0-1028.29. Ubuntu Hirsute and Impish already have all the 
fixes.

  Jun  9 09:06:02 ubuntu kernel: [6.216367] general protection fault, 
probably for non-canonical address 0x213146a124f901ea:  [#1] SMP NOPTI
  Jun  9 09:06:02 ubuntu kernel: [6.216371] CPU: 3 PID: 447 Comm: 
systemd-udevd Not tainted 5.10.0-1030-oem #31-Ubuntu
  Jun  9 09:06:02 ubuntu kernel: [6.216372] Hardware name: Dell Inc. 
Latitude 5300/, BIOS 1.13.1 01/22/2021
  Jun  9 09:06:02 ubuntu kernel: [6.216376] RIP: 0010:kobject_put+0xd/0x60
  Jun  9 09:06:02 ubuntu kernel: [6.216378] Code: 02 0f 85 64 ff ff ff 45 
31 ff e9 6e ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 48 85 ff 74 3e 
55 48 89 e5 53 48 89 fb  47 3c 01 74 1a 48 8d 7b 38 b8 ff ff ff ff f0 0f c1 
43 38 83 f8
  Jun  9 09:06:02 ubuntu kernel: [6.216379] RSP: 0018:b233406a7c38 
EFLAGS: 00010202
  Jun  9 09:06:02 ubuntu kernel: [6.216381] RAX:  RBX: 
213146a124f901ea RCX: 
  Jun  9 09:06:02 ubuntu kernel: [6.216383] RDX: 0001 RSI: 
 RDI: 213146a124f901ea
  Jun  9 09:06:02 ubuntu kernel: [6.216384] RBP: b233406a7c40 R08: 
0001 R09: 9ac66400
  Jun  9 09:06:02 ubuntu kernel: [6.216384] R10: 9c41106d7fa0 R11: 
0001 R12: 9c4114011438
  Jun  9 09:06:02 ubuntu kernel: [6.216385] R13: 213146a124f901ea R14: 
 R15: b233406a7e70
  Jun  9 09:06:02 ubuntu kernel: [6.216387] FS:  7f9e33410880() 
GS:9c485e4c() knlGS:
  Jun  9 09:06:02 ubuntu kernel: [6.216388] CS:  0010 DS:  ES:  
CR0: 80050033
  Jun  9 09:06:02 ubuntu kernel: [6.216389] CR2: 7ffe51396080 CR3: 
00011211e003 CR4: 003706e0
  Jun  9 09:06:02 ubuntu kernel: [6.216390] Call Trace:
  Jun  9 09:06:02 ubuntu kernel: [6.216394]  kset_unregister+0x2a/0x40
  Jun  9 09:06:02 ubuntu kernel: [6.216399]  sysman_init+0x20e/0x1000 
[dell_wmi_sysman]
  Jun  9 09:06:02 ubuntu kernel: [6.216401]  ? 0xc0ce4000
  Jun  9 09:06:02 ubuntu kernel: [6.216404]  do_one_initcall+0x48/0x1d0
  Jun  9 09:06:02 ubuntu kernel: [6.216406]  ? _cond_resched+0x19/0x30
  Jun  9 09:06:02 ubuntu kernel: [6.216408]  ? 
kmem_cache_alloc_trace+0x37a/0x430
  Jun  9 09:06:02 ubuntu kernel: [6.216410]  ? do_init_module+0x28/0x250
  Jun  9 09:06:02 ubuntu kernel: [6.216412]  do_init_module+0x62/0x250
  Jun  9 09:06:02 ubuntu kernel: [6.216414]  load_module+0x11ac/0x1370
  Jun  9 09:06:02 ubuntu kernel: [6.216417]  ? 
security_kernel_post_read_file+0x5c/0x70
  Jun  9 09:06:02 ubuntu kernel: [6.216419]  ? 
security_kernel_post_read_file+0x5c/0x70
  Jun  9 09:06:02 ubuntu kernel: [6.216421]  
__do_sys_finit_module+0xc2/0x120
  Jun  9 09:06:02 ubuntu kernel: [6.216423]  ? 
__do_sys_finit_module+0xc2/0x120
  Jun  9 09:06:02 ubuntu kernel: [6.216427]  
__x64_sys_finit_module+0x1a/0x20
  Jun  9 09:06:02 ubuntu kernel: [6.216429]  do_syscall_64+0x38/0x90
  Jun  9 09:06:02 ubuntu kernel: [6.216431]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9

  [Fix]
  The first commit fixes the issue, but also cherry pick some other commits for 
some other potential regressions.

  bdda39673fde platform/x86: dell-wmi-sysman: Fix crash caused by calling 
kset_unregister twice
  eaa1dcc79694 platform/x86: dell-wmi-sysman: Cleanup sysman_init() error-exit 
handling
  f4c4e9ad1523 platform/x86: dell-wmi-sysman: Fix release_attributes_data() 
getting called twice on init_bios_attributes() failure
  ececdb898376 platform/x86: dell-wmi-sysman: Fix possible NULL pointer deref 
on exit
  9b95665a83ec platform/x86: dell-wmi-sysman: Make sysman_init() return -ENODEV 
of the interfaces are not found
  5e3f5973c8df platform/x86: dell-wmi-sysman: Make init_bios_attributes() ACPI 
object parsing more robust
  42f38dcccfb3 platform/x86: dell-wmi-sysman: Cleanup 
create_attributes_level_sysfs_files()

  [Test]
  It passed 300 and 400 times reboot tests on 2 different platforms

  [Where problems could occur]
  Those commits are pretty straightforward, and we already done some stress 
test and make sure the system continue working well.

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


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

[Kernel-packages] [Bug 1919266] Re: kubuntu hirsute daily QA-test install & no background at first login