date:20210906

We'll keep the bug open because the issue shouldn't ever happen out-of-
the-box. The next person to use the same laptop model will run into the
same problem.


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

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

** Summary changed:

- [Huawei MateBook X] Display is corrupted in kernel 5.11 but 5.8 works fine
+ [Huawei MateBook X] Display is corrupted in kernel 5.11 but 5.8 works fine 
(also fixed by i915.enable_psr=0)

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

Title:
  [Huawei MateBook X] Display is corrupted in kernel 5.11 but 5.8 works
  fine (also fixed by i915.enable_psr=0)

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

Bug description:
  display driver In  the kernel 5.8.0-generic is work fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-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: Tue Sep  7 09:18:00 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Device [1e83:3e35]
  InstallationDate: Installed on 2021-06-20 (78 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: HUAWEI MACHD-WXX9
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=37779fb3-62b0-45d9-bd7f-dc9c3ea1f0ae ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2021
  dmi.bios.release: 1.18
  dmi.bios.vendor: HUAWEI
  dmi.bios.version: 1.18
  dmi.board.asset.tag: N/A
  dmi.board.name: MACHD-WXX9-PCB
  dmi.board.vendor: HUAWEI
  dmi.board.version: M1020
  dmi.chassis.type: 10
  dmi.chassis.vendor: HUAWEI
  dmi.chassis.version: M1020
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnHUAWEI:bvr1.18:bd06/11/2021:br1.18:efr1.18:svnHUAWEI:pnMACHD-WXX9:pvrM1020:rvnHUAWEI:rnMACHD-WXX9-PCB:rvrM1020:cvnHUAWEI:ct10:cvrM1020:
  dmi.product.family: MateBook X
  dmi.product.name: MACHD-WXX9
  dmi.product.sku: C170
  dmi.product.version: M1020
  dmi.sys.vendor: HUAWEI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-1027
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.1
  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/1942828/+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 1942832] [NEW] Ubuntu MATE 21.04 installation disables Install button.

2021-09-06 Thread Robert Pearson

Public bug reported:

Downloaded Ubuntu MATE. Opened .iso with Disk Image Writer. Burned to
32GB SanDisk jump drive. Booted UEFI jump drive. Selected English(US).
Checked "install third-party..." Tried "Install alongside them".
Cancelled when installed chose the wrong drive to install to. Tried
"Something else".

When it scanned my drives it did find the brand new WD Blue 1TB SSD. But
the "install" key is disables so cannot even begin to install.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: linux-image-5.11.0-16-generic 5.11.0-16.17
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  ubuntu-mate   5494 F pulseaudio
 /dev/snd/pcmC1D1p:   ubuntu-mate   5494 F...m pulseaudio
 /dev/snd/controlC0:  ubuntu-mate   5494 F pulseaudio
CasperMD5CheckResult: pass
CasperVersion: 1.461
CurrentDesktop: MATE
Date: Tue Sep  7 04:40:02 2021
LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: System manufacturer System Product Name
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed 
maybe-ubiquity quiet splash ---
RelatedPackageVersions:
 linux-restricted-modules-5.11.0-16-generic N/A
 linux-backports-modules-5.11.0-16-generic  N/A
 linux-firmware 1.197
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1301
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: A88XM-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug hirsute

** Attachment added: "Screenshot at 2021-09-07 02-33-03.png"
   
https://bugs.launchpad.net/bugs/1942832/+attachment/5523384/+files/Screenshot%20at%202021-09-07%2002-33-03.png

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

Title:
  Ubuntu MATE 21.04 installation disables Install button.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Downloaded Ubuntu MATE. Opened .iso with Disk Image Writer. Burned to
  32GB SanDisk jump drive. Booted UEFI jump drive. Selected English(US).
  Checked "install third-party..." Tried "Install alongside them".
  Cancelled when installed chose the wrong drive to install to. Tried
  "Something else".

  When it scanned my drives it did find the brand new WD Blue 1TB SSD.
  But the "install" key is disables so cannot even begin to install.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-16-generic 5.11.0-16.17
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu-mate   5494 F pulseaudio
   /dev/snd/pcmC1D1p:   ubuntu-mate   5494 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu-mate   5494 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: MATE
  Date: Tue Sep  7 04:40:02 2021
  LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-16-generic N/A
   linux-backports-modules-5.11.0-16-generic  N/A
   linux-firmware 1.197
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present

[Kernel-packages] [Bug 1942828] Re: [Huawei MateBook X] Display is corrupted in kernel 5.11 but 5.8 works fine

2021-09-06 Thread Casper

Thanks. This solution worked for me.
The issue can be closed.

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

Title:
  [Huawei MateBook X] Display is corrupted in kernel 5.11 but 5.8 works
  fine

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

Bug description:
  display driver In  the kernel 5.8.0-generic is work fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-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: Tue Sep  7 09:18:00 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Device [1e83:3e35]
  InstallationDate: Installed on 2021-06-20 (78 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: HUAWEI MACHD-WXX9
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=37779fb3-62b0-45d9-bd7f-dc9c3ea1f0ae ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2021
  dmi.bios.release: 1.18
  dmi.bios.vendor: HUAWEI
  dmi.bios.version: 1.18
  dmi.board.asset.tag: N/A
  dmi.board.name: MACHD-WXX9-PCB
  dmi.board.vendor: HUAWEI
  dmi.board.version: M1020
  dmi.chassis.type: 10
  dmi.chassis.vendor: HUAWEI
  dmi.chassis.version: M1020
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnHUAWEI:bvr1.18:bd06/11/2021:br1.18:efr1.18:svnHUAWEI:pnMACHD-WXX9:pvrM1020:rvnHUAWEI:rnMACHD-WXX9-PCB:rvrM1020:cvnHUAWEI:ct10:cvrM1020:
  dmi.product.family: MateBook X
  dmi.product.name: MACHD-WXX9
  dmi.product.sku: C170
  dmi.product.version: M1020
  dmi.sys.vendor: HUAWEI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-1027
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.1
  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/1942828/+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 1934462] Re: Ability to hibernate lost after update of kernel version

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

Title:
  Ability to hibernate lost after update of kernel version

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hi!

  I have Ubuntu 18.04 installed (due to Petalinux requirement) where
  Hibernation so far at least worked. Recently I got an update
  notification, confirmed it and am now running on this version:

  $ uname -a
  Linux datatel-XMG-CORE-M19-GTX-1650 5.4.0-77-generic #86~18.04.1-Ubuntu SMP 
Fri Jun 18 01:23:22 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

  Before the update, using kernel 5.4.0.74 a "sudo hibernate" worked fine. Now 
it does not, instead returns a black screen for a sec and then this notice:
  hibernate:Warning: Tuxonice binary signature file not found.

  In addition the system hangs for a couple of seconds.

  Looking for help on that I saw several posts proposing to adapt
  /sys/power/state, adding "disk" and "standby" to it. I have tried that
  in any possible way I could think of, using vi directly on the file
  (as su), writing it with an "echo... > /sys/power/state" command,
  making up a file in my home and then copying to that location using
  "sudo cp ~/ /sys/power/state". Neither of this works. I always
  get a permission error. I have even tried to "chmod" all the
  directories to "777" and that was successful looking at "ls -la" but
  won't help either.

  Maybe I should mention that my Ubuntu installation resides on a USB-
  Stick.

  I posted this on Ask Ubuntu and was asked to file a bug report. So
  here you are.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.44
  ProcVersionSignature: Ubuntu 5.4.0-77.86~18.04.1-generic 5.4.119
  Uname: Linux 5.4.0-77-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.24
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul  2 09:16:59 2021
  InstallationDate: Installed on 2021-05-11 (51 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptlog:
   Log time: 2021-05-17 11:54:33.809310
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   Log time: 2021-05-17 11:55:10.776569

  --

  7th July:

  Sorry to say that I have meanwhile (after a restoration of my root partition 
to kernel version 5.4.0-74) figured out that the above error
  "hibernate:Warning: Tuxonice binary signature file not found."
  does not come from the kernel update (to -77) but seemingly from my 
repartioning.
  What I did:
  I have a 256GB SanDisk USB stick where I installed Ubuntu 18.04.04 .
  Partitioning was:
  /dev/sda1   fat32   /efi1,4G
  /dev/sda2   fat32   /mnt/UDISK  55,6G
  /dev/sda3   ext4/   140G
  /dev/sda4   swap35,9G
  I made a backup of sda3 with dd deleted sda2 und sda3 with gparted and 
increased the size of sda2 to the max then, partitioning:
  /dev/sda1   fat32   /efi1,4G
  /dev/sda2   ext4/   195,6G
  /dev/sda4   swap35,9G
  I restored (former) sda3 to now sda2 tried to reboot, got a boot problem 
because /etc/fstab still contained the old sda2 entry, removed that and the 
system booted apparently normal.
  Then I made a "sudo resize2fs /dev/sda2" to get the full size of the 
partition for the file system and it seemed to work fine.
  BUT: Now hibernation does not work any more and produces the above error - 
before the Software Updater came forward.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934462/+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 1851819] Re: bond: An illegal loopback occurred on slave

2021-09-06 Thread Mohammed Naser

FYI, I was being hit by this and the issue disappeared once I updated
the firmware on those NICs to 14.31.1014.  The problematic firmware
version I had was 14.26.1040.  Not only did I see those errors, but I
actually saw traffic being dropped.

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

Title:
  bond: An illegal loopback occurred on slave

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Mellanox ConnectX 5 adapter configured with LACP bonding; adapters in
  switchdev (offload) mode with VF's configure on both ports.

  Kernel continually reports:

  Nov  8 10:57:51 node-laveran kernel: [ 2087.912308] bond1: (slave enp3s0f0): 
An illegal loopback occurred on slave
  Nov  8 10:57:51 node-laveran kernel: [ 2087.912308] Check the configuration 
to verify that all adapters are connected to 802.3ad complian
  t switch ports
  Nov  8 10:57:51 node-laveran kernel: [ 2087.917329] bond1: (slave enp3s0f1): 
An illegal loopback occurred on slave
  Nov  8 10:57:51 node-laveran kernel: [ 2087.917329] Check the configuration 
to verify that all adapters are connected to 802.3ad complian
  t switch ports

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-generic-hwe-18.04-edge 5.3.0.19.85
  ProcVersionSignature: Ubuntu 5.3.0-19.20~18.04.2-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  Date: Fri Nov  8 10:54:32 2019
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-meta-hwe-edge
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 19 16:45 seq
   crw-rw 1 root audio 116, 33 Nov 19 16:45 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R630
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgag200drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic 
root=UUID=2ff5e234-ee62-4bce-8266-cd9aa78c532f ro intel_iommu=on iommu=pt 
probe_vf=0
  ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-23-generic N/A
   linux-backports-modules-5.3.0-23-generic  N/A
   linux-firmware1.173.12
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 5.3.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.3.4
  dmi.board.name: 02C2CP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R630
  dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R630
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851819/+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 1942830] [NEW] Fix sluggish r8169 by disaling ASPM L1.2

2021-09-06 Thread Kai-Heng Feng

Public bug reported:

[Impact]
Realtek r8169 has abysmal network speed.

[Fix]
Disable ASPM L1.2 because the device takes a long time to exit from
L1.2.

[Test]
Use `iperf` to test network speed.
When ASPM L1.2 gets disabled, TX and RX and reach ~700Mbps and ~900Mbps
respectively.

[Where problems could occur]
Disabling ASPM L1.2 can slightly increase power consumption. The CPU
package C-State seems to be unaffected so the increase is rather minor.

** Affects: hwe-next
 Importance: Undecided
 Status: New

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

** Affects: linux-oem-5.13 (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-oem-5.14 (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux (Ubuntu Focal)
 Importance: Undecided
 Status: Invalid

** Affects: linux-oem-5.13 (Ubuntu Focal)
 Importance: Medium
 Status: Confirmed

** Affects: linux-oem-5.14 (Ubuntu Focal)
 Importance: Medium
 Status: Confirmed


** Tags: oem-priority originate-from-1934257 somerville

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

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

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

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

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

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

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

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

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

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

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

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

** Tags added: oem-priority originate-from-1934257 somerville

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

Title:
  Fix sluggish r8169 by disaling ASPM L1.2

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.13 source package in Focal:
  Confirmed
Status in linux-oem-5.14 source package in Focal:
  Confirmed

Bug description:
  [Impact]
  Realtek r8169 has abysmal network speed.

  [Fix]
  Disable ASPM L1.2 because the device takes a long time to exit from
  L1.2.

  [Test]
  Use `iperf` to test network speed.
  When ASPM L1.2 gets disabled, TX and RX and reach ~700Mbps and ~900Mbps
  respectively.

  [Where problems could occur]
  Disabling ASPM L1.2 can slightly increase power consumption. The CPU
  package C-State seems to be unaffected so the increase is rather minor.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1942830/+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 1940713] Re: llvm-9, llvm-11 and llvm-12 contain a zero-byte manpage

This bug was fixed in the package llvm-toolchain-12 - 1:12.0.1-8

---
llvm-toolchain-12 (1:12.0.1-8) unstable; urgency=medium

  * Add back CMAKE_EXTRA to build LLVM gold (Closes: #993664)

  [  Gianfranco Costamagna ]
  * Refresh symbols on riscv64

 -- Sylvestre Ledru   Sat, 04 Sep 2021 16:38:24
+0200

** Changed in: llvm-toolchain-12 (Ubuntu)
   Status: New => Fix Released

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

Title:
  llvm-9, llvm-11 and llvm-12 contain a zero-byte manpage

Status in llvm-toolchain-12 package in Ubuntu:
  Fix Released

Bug description:
  The llvm-mcmarkup manpage is empty for llvm-9 (1:9.0.1-16.1ubuntu1),
  llvm-11 (1:11.0.1-2ubuntu5) and llvm-12 (1:12.0.1-1):

  llvm-9: /usr/share/man/man1/llvm-mcmarkup-9.1.gz
  llvm-11: /usr/share/man/man1/llvm-mcmarkup-11.1.gz
  llvm-12: /usr/share/man/man1/llvm-mcmarkup-12.1.gz

  These 20-byte .gz files are all compressed zero-byte manpages.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: llvm-12 1:12.0.1-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-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Fri Aug 20 21:21:54 2021
  InstallationDate: Installed on 2016-11-26 (1728 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  RebootRequiredPkgs:
   linux-image-5.13.0-14-generic
   linux-base
  SourcePackage: llvm-toolchain-12
  UpgradeStatus: Upgraded to impish on 2021-08-08 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-12/+bug/1940713/+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 1942828] Re: [Huawei MateBook X] Display driver is corrupted

Thanks for the bug report.

Please try adding kernel parameter:

  i915.enable_psr=0

to /etc/default/grub in the GRUB_CMDLINE_LINUX_DEFAULT line and then
run:

  sudo update-grub

and reboot.

Does that fix it? If not then please attach a video of the problem.

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

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

** Tags added: regression-update

** Summary changed:

- [Huawei MateBook X] Display driver is corrupted
+ [Huawei MateBook X] Display is corrupted in kernel 5.11 but 5.8 works fine

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

Title:
  [Huawei MateBook X] Display is corrupted in kernel 5.11 but 5.8 works
  fine

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

Bug description:
  display driver In  the kernel 5.8.0-generic is work fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-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: Tue Sep  7 09:18:00 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Device [1e83:3e35]
  InstallationDate: Installed on 2021-06-20 (78 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: HUAWEI MACHD-WXX9
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=37779fb3-62b0-45d9-bd7f-dc9c3ea1f0ae ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2021
  dmi.bios.release: 1.18
  dmi.bios.vendor: HUAWEI
  dmi.bios.version: 1.18
  dmi.board.asset.tag: N/A
  dmi.board.name: MACHD-WXX9-PCB
  dmi.board.vendor: HUAWEI
  dmi.board.version: M1020
  dmi.chassis.type: 10
  dmi.chassis.vendor: HUAWEI
  dmi.chassis.version: M1020
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnHUAWEI:bvr1.18:bd06/11/2021:br1.18:efr1.18:svnHUAWEI:pnMACHD-WXX9:pvrM1020:rvnHUAWEI:rnMACHD-WXX9-PCB:rvrM1020:cvnHUAWEI:ct10:cvrM1020:
  dmi.product.family: MateBook X
  dmi.product.name: MACHD-WXX9
  dmi.product.sku: C170
  dmi.product.version: M1020
  dmi.sys.vendor: HUAWEI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-1027
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.1
  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/1942828/+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 1942828] Re: [Huawei MateBook X] Display driver is corrupted

2021-09-06 Thread Chris Guiver

description implies 5.8 HWE kernel worked; thus issue likely kernel
related

** Package changed: xorg (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/1942828

Title:
  [Huawei MateBook X] Display is corrupted in kernel 5.11 but 5.8 works
  fine

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

Bug description:
  display driver In  the kernel 5.8.0-generic is work fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-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: Tue Sep  7 09:18:00 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Device [1e83:3e35]
  InstallationDate: Installed on 2021-06-20 (78 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: HUAWEI MACHD-WXX9
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=37779fb3-62b0-45d9-bd7f-dc9c3ea1f0ae ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2021
  dmi.bios.release: 1.18
  dmi.bios.vendor: HUAWEI
  dmi.bios.version: 1.18
  dmi.board.asset.tag: N/A
  dmi.board.name: MACHD-WXX9-PCB
  dmi.board.vendor: HUAWEI
  dmi.board.version: M1020
  dmi.chassis.type: 10
  dmi.chassis.vendor: HUAWEI
  dmi.chassis.version: M1020
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnHUAWEI:bvr1.18:bd06/11/2021:br1.18:efr1.18:svnHUAWEI:pnMACHD-WXX9:pvrM1020:rvnHUAWEI:rnMACHD-WXX9-PCB:rvrM1020:cvnHUAWEI:ct10:cvrM1020:
  dmi.product.family: MateBook X
  dmi.product.name: MACHD-WXX9
  dmi.product.sku: C170
  dmi.product.version: M1020
  dmi.sys.vendor: HUAWEI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-1027
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.1
  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/1942828/+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 1942828] [NEW] [Huawei MateBook X] Display driver is corrupted

You have been subscribed to a public bug:

display driver In  the kernel 5.8.0-generic is work fine.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-27-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: Tue Sep  7 09:18:00 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
   Subsystem: Device [1e83:3e35]
InstallationDate: Installed on 2021-06-20 (78 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: HUAWEI MACHD-WXX9
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=37779fb3-62b0-45d9-bd7f-dc9c3ea1f0ae ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/11/2021
dmi.bios.release: 1.18
dmi.bios.vendor: HUAWEI
dmi.bios.version: 1.18
dmi.board.asset.tag: N/A
dmi.board.name: MACHD-WXX9-PCB
dmi.board.vendor: HUAWEI
dmi.board.version: M1020
dmi.chassis.type: 10
dmi.chassis.vendor: HUAWEI
dmi.chassis.version: M1020
dmi.ec.firmware.release: 1.18
dmi.modalias: 
dmi:bvnHUAWEI:bvr1.18:bd06/11/2021:br1.18:efr1.18:svnHUAWEI:pnMACHD-WXX9:pvrM1020:rvnHUAWEI:rnMACHD-WXX9-PCB:rvrM1020:cvnHUAWEI:ct10:cvrM1020:
dmi.product.family: MateBook X
dmi.product.name: MACHD-WXX9
dmi.product.sku: C170
dmi.product.version: M1020
dmi.sys.vendor: HUAWEI
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-1027
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.1
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 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug corruption focal third-party-packages ubuntu
-- 
[Huawei MateBook X] Display driver is corrupted
https://bugs.launchpad.net/bugs/1942828
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 1892213] Re: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy/hirsute/impish

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: linux (Ubuntu Groovy)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: linux (Ubuntu Hirsute)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

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

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

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

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

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

** Changed in: linux-oem-5.14 (Ubuntu Groovy)
   Status: New => Invalid

** Changed in: linux-oem-5.14 (Ubuntu Hirsute)
   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/1892213

Title:
  psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with
  focal/groovy/hirsute/impish

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

Bug description:
  [Impact]
  The expected to fail 'raw gso min size - 1' test in psock_snd.sh is always 
failing with:

    raw gso min size - 1 (expected to fail)
    tx: 1524
    rx: 1472
    OK

  This is because after commit 7c6d2ec ("net: be more gentle about silly
  gso requests coming from user"), we relaxed the min gso_size check in 
virtio_net_hdr_to_skb().
  So when a packet which is smaller then the gso_size,
  GSO for this packet will not be set, the packet will be
  send/recv successfully.

  [Fix]
  * cfba3fb68960b4 selftests/net: remove min gso test in packet_snd

  This patch can be cherry-picked into affected kernels.

  [Test]
  Run this psock_snd.sh script, this test will no longer exist and the script 
can proceed to the next test.

  [Impact]

  [Original Bug Report]
  Testing failed on focal/linux 5.4.0-44.48:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux/20200812_171444_31971@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/l/linux/20200812_210509_145fd@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/l/linux/20200812_165855_1dabd@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200812_153600_9c7cb@/log.gz

  psock_snd.sh output:

  16:28:30 DEBUG| [stdout] # selftests: net: psock_snd.sh
  16:28:31 DEBUG| [stdout] # dgram
  16:28:31 DEBUG| [stdout] # tx: 128
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG| [stdout] # dgram bind
  16:28:31 DEBUG| [stdout] # tx: 128
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG| [stdout] # raw
  16:28:31 DEBUG| [stdout] # tx: 142
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG| [stdout] # raw bind
  16:28:31 DEBUG| [stdout] # tx: 142
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG| [stdout] # raw qdisc bypass
  16:28:31 DEBUG| [stdout] # tx: 142
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG| [stdout] # raw vlan
  16:28:31 DEBUG| [stdout] # tx: 146
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG|

[Kernel-packages] [Bug 1892213] Re: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy/hirsute/impish

** Description changed:

  [Impact]
- The expected to fail 'raw gso min size - 1' test in psock_snd.sh is always 
failing with: 
+ The expected to fail 'raw gso min size - 1' test in psock_snd.sh is always 
failing with:
  
-   raw gso min size - 1 (expected to fail)
-   tx: 1524
-   rx: 1472
-   OK
+   raw gso min size - 1 (expected to fail)
+   tx: 1524
+   rx: 1472
+   OK
  
  This is because after commit 7c6d2ec ("net: be more gentle about silly
  gso requests coming from user"), we relaxed the min gso_size check in 
virtio_net_hdr_to_skb().
  So when a packet which is smaller then the gso_size,
  GSO for this packet will not be set, the packet will be
  send/recv successfully.
  
  [Fix]
- * cfba3fb68960b4 selftests/net: remove min gso test in packet_snd 
+ * cfba3fb68960b4 selftests/net: remove min gso test in packet_snd
  
- This patch can be
+ This patch can be cherry-picked into affected kernels.
  
  [Test]
- Run this psock_snd.sh script, 
- 
+ Run this psock_snd.sh script,
  
  [Impact]
- 
  
  [Original Bug Report]
  Testing failed on focal/linux 5.4.0-44.48:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux/20200812_171444_31971@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/l/linux/20200812_210509_145fd@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/l/linux/20200812_165855_1dabd@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200812_153600_9c7cb@/log.gz
  
  psock_snd.sh output:
  
  16:28:30 DEBUG| [stdout] # selftests: net: psock_snd.sh
  16:28:31 DEBUG| [stdout] # dgram
  16:28:31 DEBUG| [stdout] # tx: 128
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG| [stdout] # dgram bind
  16:28:31 DEBUG| [stdout] # tx: 128
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG| [stdout] # raw
  16:28:31 DEBUG| [stdout] # tx: 142
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG| [stdout] # raw bind
  16:28:31 DEBUG| [stdout] # tx: 142
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG| [stdout] # raw qdisc bypass
  16:28:31 DEBUG| [stdout] # tx: 142
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG| [stdout] # raw vlan
  16:28:31 DEBUG| [stdout] # tx: 146
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG| [stdout] # raw vnet hdr
  16:28:31 DEBUG| [stdout] # tx: 152
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG| [stdout] # raw csum_off
  16:28:31 DEBUG| [stdout] # tx: 152
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG| [stdout] # raw csum_off with bad offset (fails)
  16:28:31 DEBUG| [stdout] # ./psock_snd: write: Invalid argument
  16:28:31 DEBUG| [stdout] # raw min size
  16:28:31 DEBUG| [stdout] # tx: 42
  16:28:31 DEBUG| [stdout] # rx: 0
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG| [stdout] # raw mtu size
  16:28:31 DEBUG| [stdout] # tx: 1514
  16:28:31 DEBUG| [stdout] # rx: 1472
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG| [stdout] # raw mtu size + 1 (fails)
  16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long
  16:28:31 DEBUG| [stdout] # raw vlan mtu size + 1 (fails)
  16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long
  16:28:32 DEBUG| [stdout] # dgram mtu size
  16:28:32 DEBUG| [stdout] # tx: 1500
  16:28:32 DEBUG| [stdout] # rx: 1472
  16:28:32 DEBUG| [stdout] # OK
  16:28:32 DEBUG| [stdout] #
  16:28:32 DEBUG| [stdout] # dgram mtu size + 1 (fails)
  16:28:32 DEBUG| [stdout] # ./psock_snd: write: Message too long
  16:28:32 DEBUG| [stdout] # raw truncate hlen (fails: does not arrive)
  16:28:32 DEBUG| [stdout] # tx: 14
  16:28:32 DEBUG| [stdout] # ./psock_snd: recv: Resource temporarily unavailable
  16:28:32 DEBUG| [stdout] # raw truncate hlen - 1 (fails: EINVAL)
  16:28:32 DEBUG| [stdout] # ./psock_snd: write: Invalid argument
  16:28:32 DEBUG| [stdout] # raw gso min size
  16:28:32 DEBUG| [stdout] # tx: 1525
  16:28:32 DEBUG| [stdout] # rx: 1473

[Kernel-packages] [Bug 1892213] Re: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy/hirsute/impish

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

** Description changed:

+ [Impact]
+ The expected to fail 'raw gso min size - 1' test in psock_snd.sh is always 
failing with: 
+ 
+   raw gso min size - 1 (expected to fail)
+   tx: 1524
+   rx: 1472
+   OK
+ 
+ This is because after commit 7c6d2ec ("net: be more gentle about silly
+ gso requests coming from user"), we relaxed the min gso_size check in 
virtio_net_hdr_to_skb().
+ So when a packet which is smaller then the gso_size,
+ GSO for this packet will not be set, the packet will be
+ send/recv successfully.
+ 
+ [Fix]
+ * cfba3fb68960b4 selftests/net: remove min gso test in packet_snd 
+ 
+ This patch can be
+ 
+ [Test]
+ Run this psock_snd.sh script, 
+ 
+ 
+ [Impact]
+ 
+ 
+ [Original Bug Report]
  Testing failed on focal/linux 5.4.0-44.48:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux/20200812_171444_31971@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/l/linux/20200812_210509_145fd@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/l/linux/20200812_165855_1dabd@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200812_153600_9c7cb@/log.gz
  
  psock_snd.sh output:
  
  16:28:30 DEBUG| [stdout] # selftests: net: psock_snd.sh
  16:28:31 DEBUG| [stdout] # dgram
  16:28:31 DEBUG| [stdout] # tx: 128
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
- 16:28:31 DEBUG| [stdout] # 
+ 16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG| [stdout] # dgram bind
  16:28:31 DEBUG| [stdout] # tx: 128
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
- 16:28:31 DEBUG| [stdout] # 
+ 16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG| [stdout] # raw
  16:28:31 DEBUG| [stdout] # tx: 142
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
- 16:28:31 DEBUG| [stdout] # 
+ 16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG| [stdout] # raw bind
  16:28:31 DEBUG| [stdout] # tx: 142
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
- 16:28:31 DEBUG| [stdout] # 
+ 16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG| [stdout] # raw qdisc bypass
  16:28:31 DEBUG| [stdout] # tx: 142
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
- 16:28:31 DEBUG| [stdout] # 
+ 16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG| [stdout] # raw vlan
  16:28:31 DEBUG| [stdout] # tx: 146
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
- 16:28:31 DEBUG| [stdout] # 
+ 16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG| [stdout] # raw vnet hdr
  16:28:31 DEBUG| [stdout] # tx: 152
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
- 16:28:31 DEBUG| [stdout] # 
+ 16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG| [stdout] # raw csum_off
  16:28:31 DEBUG| [stdout] # tx: 152
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
- 16:28:31 DEBUG| [stdout] # 
+ 16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG| [stdout] # raw csum_off with bad offset (fails)
  16:28:31 DEBUG| [stdout] # ./psock_snd: write: Invalid argument
  16:28:31 DEBUG| [stdout] # raw min size
  16:28:31 DEBUG| [stdout] # tx: 42
  16:28:31 DEBUG| [stdout] # rx: 0
  16:28:31 DEBUG| [stdout] # OK
- 16:28:31 DEBUG| [stdout] # 
+ 16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG| [stdout] # raw mtu size
  16:28:31 DEBUG| [stdout] # tx: 1514
  16:28:31 DEBUG| [stdout] # rx: 1472
  16:28:31 DEBUG| [stdout] # OK
- 16:28:31 DEBUG| [stdout] # 
+ 16:28:31 DEBUG| [stdout] #
  16:28:31 DEBUG| [stdout] # raw mtu size + 1 (fails)
  16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long
  16:28:31 DEBUG| [stdout] # raw vlan mtu size + 1 (fails)
  16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long
  16:28:32 DEBUG| [stdout] # dgram mtu size
  16:28:32 DEBUG| [stdout] # tx: 1500
  16:28:32 DEBUG| [stdout] # rx: 1472
  16:28:32 DEBUG| [stdout] # OK
- 16:28:32 DEBUG| [stdout] # 
+ 16:28:32 DEBUG| [stdout] #
  16:28:32 DEBUG| [stdout] # dgram mtu size + 1 (fails)
  16:28:32 DEBUG| [stdout] # ./psock_snd: write: Message too long
  16:28:32 DEBUG| [stdout] # raw truncate hlen (fails: does not arrive)
  16:28:32 DEBUG| [stdout] # tx: 14
  16:28:32 DEBUG| [stdout] # ./psock_snd: recv: Resource temporarily unavailable
  16:28:32 DEBUG| [stdout] # raw truncate hlen - 1 (fails: EINVAL)
  16:28:32 DEBUG| [stdout] # ./psock_snd: write: Invalid argument
  16:28:32 DEBUG| [stdout] #

[Kernel-packages] [Bug 1942500] Missing required logs.

2021-09-06 Thread Ubuntu Kernel Bot

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1942500

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

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

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

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

** Tags added: bionic

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

Title:
  invalid symbol # in scripts/module.lds

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04

  Kernel: 5.11.5-051105-generic

  Bug : Building External Wifi Drivers Fail , tried multiple drivers ,
  Error generated , below.

  Resolution tried : copying module.lds.S to the running kernel, does
  not work !!

  
  Error :

  ld:scripts/module.lds:6: ignoring invalid character `#' in expression
  ld:scripts/module.lds:6: syntax error
  scripts/Makefile.modfinal:58: recipe for target 
'/home/octo-ws/Documents/RTL88x2BU-Linux-Driver/88x2bu.ko' failed

  make[3]: *** [/home/octo-ws/Documents/RTL88x2BU-Linux-Driver/88x2bu.ko] Error 
1
  scripts/Makefile.modpost:117: recipe for target '__modpost' failed
  make[2]: *** [__modpost] Error 2
  Makefile:1710: recipe for target 'modules' failed
  make[1]: *** [modules] Error 2
  make[1]: Leaving directory '/usr/src/linux-headers-5.11.5-051105-generic'
  Makefile:2378: recipe for target 'modules' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942500/+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 1942500] Re: invalid symbol # in scripts/module.lds

2021-09-06 Thread ISHAN BHATNAGAR

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

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

Title:
  invalid symbol # in scripts/module.lds

Status in linux package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04

  Kernel: 5.11.5-051105-generic

  Bug : Building External Wifi Drivers Fail , tried multiple drivers ,
  Error generated , below.

  Resolution tried : copying module.lds.S to the running kernel, does
  not work !!

  
  Error :

  ld:scripts/module.lds:6: ignoring invalid character `#' in expression
  ld:scripts/module.lds:6: syntax error
  scripts/Makefile.modfinal:58: recipe for target 
'/home/octo-ws/Documents/RTL88x2BU-Linux-Driver/88x2bu.ko' failed

  make[3]: *** [/home/octo-ws/Documents/RTL88x2BU-Linux-Driver/88x2bu.ko] Error 
1
  scripts/Makefile.modpost:117: recipe for target '__modpost' failed
  make[2]: *** [__modpost] Error 2
  Makefile:1710: recipe for target 'modules' failed
  make[1]: *** [modules] Error 2
  make[1]: Leaving directory '/usr/src/linux-headers-5.11.5-051105-generic'
  Makefile:2378: recipe for target 'modules' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942500/+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 1942806] Re: Unmatched enable poweroff, LEDs, mmap PCI

** Description changed:

  [Impact]
  
   * Unable to use gpio-poweroff driver to poweroff via u-boot/opensbi/kernel
   * Unable to use LED colors
   * Unable to mmap PCI resources
  
   * Cherrypick dtb changes from meta-sifive 2021.08 release
  https://github.com/sifive/meta-sifive/tree/2021.08/recipes-
  kernel/linux/files
  
    * Fixup linux kernel to allow using gpio-poweroff driver for poweroff,
  without re-enabling back deprecated OpenSBI v0.1 extensions support
  (CONFIG_RISCV_SBI_V01) Submitted at https://lore.kernel.org/linux-
  riscv/20210907002847.111633-1-dimitri.led...@canonical.com/T/#u
  
  [Test Plan]
  
   * Boot Unmatched board, poweroff, it should poweroff.
  
   * No test case for LEDs (will try to figure it out)
  
   * No test case for mmap PCI resources (needs compatible hardware)
  
  [Where problems could occur]
  
   * DTB changes have already landed in opensbi/u-boot and thus kernel is
  being brought it line with matching support. pm_power_off reboot
  handling will have to change again in the future when support for
  OpenSBI v0.3 system reset extension is added in the kernel. When
  available, it will be used by default with regular power drivers
  probably compiled only as modules.
  
  [Other Info]
  
   * Alternative to taking these patches, poweroff support could be
  enabled by turning back on deprecated OpenSBI v0.1 extensions, which is
  a step backwards. OpenSBI v0.1 will not be available in the future.
+ 
+ https://lists.ubuntu.com/archives/kernel-team/2021-September/123845.html

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

Title:
  Unmatched enable poweroff, LEDs, mmap PCI

Status in linux-riscv package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * Unable to use gpio-poweroff driver to poweroff via u-boot/opensbi/kernel
   * Unable to use LED colors
   * Unable to mmap PCI resources

   * Cherrypick dtb changes from meta-sifive 2021.08 release
  https://github.com/sifive/meta-sifive/tree/2021.08/recipes-
  kernel/linux/files

    * Fixup linux kernel to allow using gpio-poweroff driver for
  poweroff, without re-enabling back deprecated OpenSBI v0.1 extensions
  support (CONFIG_RISCV_SBI_V01) Submitted at
  https://lore.kernel.org/linux-
  riscv/20210907002847.111633-1-dimitri.led...@canonical.com/T/#u

  [Test Plan]

   * Boot Unmatched board, poweroff, it should poweroff.

   * No test case for LEDs (will try to figure it out)

   * No test case for mmap PCI resources (needs compatible hardware)

  [Where problems could occur]

   * DTB changes have already landed in opensbi/u-boot and thus kernel
  is being brought it line with matching support. pm_power_off reboot
  handling will have to change again in the future when support for
  OpenSBI v0.3 system reset extension is added in the kernel. When
  available, it will be used by default with regular power drivers
  probably compiled only as modules.

  [Other Info]

   * Alternative to taking these patches, poweroff support could be
  enabled by turning back on deprecated OpenSBI v0.1 extensions, which
  is a step backwards. OpenSBI v0.1 will not be available in the future.

  https://lists.ubuntu.com/archives/kernel-
  team/2021-September/123845.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1942806/+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 1942500] [NEW] invalid symbol # in scripts/module.lds

You have been subscribed to a public bug:

Description:Ubuntu 18.04.5 LTS
Release:18.04

Kernel: 5.11.5-051105-generic

Bug : Building External Wifi Drivers Fail , tried multiple drivers ,
Error generated , below.

Resolution tried : copying module.lds.S to the running kernel, does not
work !!


Error :

ld:scripts/module.lds:6: ignoring invalid character `#' in expression
ld:scripts/module.lds:6: syntax error
scripts/Makefile.modfinal:58: recipe for target 
'/home/octo-ws/Documents/RTL88x2BU-Linux-Driver/88x2bu.ko' failed

make[3]: *** [/home/octo-ws/Documents/RTL88x2BU-Linux-Driver/88x2bu.ko] Error 1
scripts/Makefile.modpost:117: recipe for target '__modpost' failed
make[2]: *** [__modpost] Error 2
Makefile:1710: recipe for target 'modules' failed
make[1]: *** [modules] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-5.11.5-051105-generic'
Makefile:2378: recipe for target 'modules' failed

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


** Tags: bot-comment
-- 
invalid symbol # in scripts/module.lds
https://bugs.launchpad.net/bugs/1942500
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 1942806] Re: Unmatched enable poweroff, LEDs, mmap PCI

** Description changed:

  [Impact]
  
-  * Unable to use gpio-poweroff driver to poweroff via u-boot/opensbi/kernel
-  * Unable to use LED colors
-  * Unable to mmap PCI resources
+  * Unable to use gpio-poweroff driver to poweroff via u-boot/opensbi/kernel
+  * Unable to use LED colors
+  * Unable to mmap PCI resources
  
-  * Cherrypick dtb changes from meta-sifive 2021.08 release
+  * Cherrypick dtb changes from meta-sifive 2021.08 release
  https://github.com/sifive/meta-sifive/tree/2021.08/recipes-
  kernel/linux/files
  
-   * Fixup linux kernel to allow using gpio-poweroff driver for poweroff,
+   * Fixup linux kernel to allow using gpio-poweroff driver for poweroff,
  without re-enabling back deprecated OpenSBI v0.1 extensions support
  (CONFIG_RISCV_SBI_V01)
  
  [Test Plan]
  
-  * Boot Unmatched board, poweroff, it should poweroff.
+  * Boot Unmatched board, poweroff, it should poweroff.
  
-  * No test case for LEDs (will try to figure it out)
+  * No test case for LEDs (will try to figure it out)
  
-  * No test case for mmap PCI resources (needs compatible hardware)
+  * No test case for mmap PCI resources (needs compatible hardware)
  
  [Where problems could occur]
  
-  * DTB changes have already landed in opensbi/u-boot and thus kernel is
+  * DTB changes have already landed in opensbi/u-boot and thus kernel is
  being brought it line with matching support. pm_power_off reboot
  handling will have to change again in the future when support for
  OpenSBI v0.3 system reset extension is added in the kernel. When
  available, it will be used by default with regular power drivers
  probably compiled only as modules.
  
  [Other Info]
-  
-  * Alternative to taking this patches, poweroff support could be enabled by 
turning back on deprecated OpenSBI v0.1 extensions, which is a step backwards. 
OpenSBI v0.1 will not be available in the future.
+ 
+  * Alternative to taking these patches, poweroff support could be
+ enabled by turning back on deprecated OpenSBI v0.1 extensions, which is
+ a step backwards. OpenSBI v0.1 will not be available in the future.

** Description changed:

  [Impact]
  
   * Unable to use gpio-poweroff driver to poweroff via u-boot/opensbi/kernel
   * Unable to use LED colors
   * Unable to mmap PCI resources
  
   * Cherrypick dtb changes from meta-sifive 2021.08 release
  https://github.com/sifive/meta-sifive/tree/2021.08/recipes-
  kernel/linux/files
  
    * Fixup linux kernel to allow using gpio-poweroff driver for poweroff,
  without re-enabling back deprecated OpenSBI v0.1 extensions support
- (CONFIG_RISCV_SBI_V01)
+ (CONFIG_RISCV_SBI_V01) Submitted at https://lore.kernel.org/linux-
+ riscv/20210907002847.111633-1-dimitri.led...@canonical.com/T/#u
  
  [Test Plan]
  
   * Boot Unmatched board, poweroff, it should poweroff.
  
   * No test case for LEDs (will try to figure it out)
  
   * No test case for mmap PCI resources (needs compatible hardware)
  
  [Where problems could occur]
  
   * DTB changes have already landed in opensbi/u-boot and thus kernel is
  being brought it line with matching support. pm_power_off reboot
  handling will have to change again in the future when support for
  OpenSBI v0.3 system reset extension is added in the kernel. When
  available, it will be used by default with regular power drivers
  probably compiled only as modules.
  
  [Other Info]
  
   * Alternative to taking these patches, poweroff support could be
  enabled by turning back on deprecated OpenSBI v0.1 extensions, which is
  a step backwards. OpenSBI v0.1 will not be available in the future.

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

Title:
  Unmatched enable poweroff, LEDs, mmap PCI

Status in linux-riscv package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * Unable to use gpio-poweroff driver to poweroff via u-boot/opensbi/kernel
   * Unable to use LED colors
   * Unable to mmap PCI resources

   * Cherrypick dtb changes from meta-sifive 2021.08 release
  https://github.com/sifive/meta-sifive/tree/2021.08/recipes-
  kernel/linux/files

    * Fixup linux kernel to allow using gpio-poweroff driver for
  poweroff, without re-enabling back deprecated OpenSBI v0.1 extensions
  support (CONFIG_RISCV_SBI_V01) Submitted at
  https://lore.kernel.org/linux-
  riscv/20210907002847.111633-1-dimitri.led...@canonical.com/T/#u

  [Test Plan]

   * Boot Unmatched board, poweroff, it should poweroff.

   * No test case for LEDs (will try to figure it out)

   * No test case for mmap PCI resources (needs compatible hardware)

  [Where problems could occur]

   * DTB changes have already landed in opensbi/u-boot and thus kernel
  is being brought it line with matching support. pm_power_off reboot
  handling will have to change again in the future when support for
  OpenSBI v0.3 system reset extension is added in the kernel. When
  available,

[Kernel-packages] [Bug 1942806] [NEW] Unmatched enable poweroff, LEDs, mmap PCI

Public bug reported:

[Impact]

 * Unable to use gpio-poweroff driver to poweroff via u-boot/opensbi/kernel
 * Unable to use LED colors
 * Unable to mmap PCI resources

 * Cherrypick dtb changes from meta-sifive 2021.08 release
https://github.com/sifive/meta-sifive/tree/2021.08/recipes-
kernel/linux/files

  * Fixup linux kernel to allow using gpio-poweroff driver for poweroff,
without re-enabling back deprecated OpenSBI v0.1 extensions support
(CONFIG_RISCV_SBI_V01)

[Test Plan]

 * Boot Unmatched board, poweroff, it should poweroff.

 * No test case for LEDs (will try to figure it out)

 * No test case for mmap PCI resources (needs compatible hardware)

[Where problems could occur]

 * DTB changes have already landed in opensbi/u-boot and thus kernel is
being brought it line with matching support. pm_power_off reboot
handling will have to change again in the future when support for
OpenSBI v0.3 system reset extension is added in the kernel. When
available, it will be used by default with regular power drivers
probably compiled only as modules.

[Other Info]
 
 * Alternative to taking this patches, poweroff support could be enabled by 
turning back on deprecated OpenSBI v0.1 extensions, which is a step backwards. 
OpenSBI v0.1 will not be available in the future.

** Affects: linux-riscv (Ubuntu)
 Importance: Undecided
 Assignee: Dimitri John Ledkov (xnox)
 Status: In Progress

** Changed in: linux-riscv (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

** Summary changed:

- unmatched 2020.08 enablement
+ Unmatched enable poweroff, LEDs, mmap PCI

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

Title:
  Unmatched enable poweroff, LEDs, mmap PCI

Status in linux-riscv package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * Unable to use gpio-poweroff driver to poweroff via u-boot/opensbi/kernel
   * Unable to use LED colors
   * Unable to mmap PCI resources

   * Cherrypick dtb changes from meta-sifive 2021.08 release
  https://github.com/sifive/meta-sifive/tree/2021.08/recipes-
  kernel/linux/files

* Fixup linux kernel to allow using gpio-poweroff driver for
  poweroff, without re-enabling back deprecated OpenSBI v0.1 extensions
  support (CONFIG_RISCV_SBI_V01)

  [Test Plan]

   * Boot Unmatched board, poweroff, it should poweroff.

   * No test case for LEDs (will try to figure it out)

   * No test case for mmap PCI resources (needs compatible hardware)

  [Where problems could occur]

   * DTB changes have already landed in opensbi/u-boot and thus kernel
  is being brought it line with matching support. pm_power_off reboot
  handling will have to change again in the future when support for
  OpenSBI v0.3 system reset extension is added in the kernel. When
  available, it will be used by default with regular power drivers
  probably compiled only as modules.

  [Other Info]
   
   * Alternative to taking this patches, poweroff support could be enabled by 
turning back on deprecated OpenSBI v0.1 extensions, which is a step backwards. 
OpenSBI v0.1 will not be available in the future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1942806/+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 1930903] Re: Frequent kernel oops related to nvidia / nv_drm_master_set

2021-09-06 Thread fuomag

Mine does not reboot but I still have logs in dmesg

226290.971074] RIP: 0010:nv_drm_master_set+0x27/0x30 [nvidia_drm]
[226290.971078] Code: 30 26 de 0f 1f 44 00 00 55 48 8b 47 48 48 8b 78 20 48 8b 
05 bb 6c 00 00 48 89 e5 48 8b 40 28 e8 ef 8f 62 de 84 c0 74 02 5d c3 <0f> 0b 5d 
c3 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 41 57 41 56
[226290.971080] RSP: 0018:b2ec90bafb80 EFLAGS: 00010246
[226290.971082] RAX:  RBX: 91442f145400 RCX: 
0008
[226290.971083] RDX: c12d0ed8 RSI: 0292 RDI: 
c12d0ea0
[226290.971084] RBP: b2ec90bafb80 R08: 0008 R09: 
b2ec90bafb68
[226290.971085] R10:  R11: 91449a2e4db2 R12: 
914e42620cc0
[226290.971086] R13: 9144849a2000 R14:  R15: 
9144849a2000
[226290.971087] FS:  7f71ad066740() GS:91537ec4() 
knlGS:
[226290.971089] CS:  0010 DS:  ES:  CR0: 80050033
[226290.971090] CR2: 7f71abbed000 CR3: 00022f62a000 CR4: 
00350ee0
[226290.971091] Call Trace:
[226290.971094]  drm_new_set_master+0x7e/0x100 [drm]
[226290.971114]  drm_master_open+0x6e/0xa0 [drm]
[226290.971132]  drm_open+0xf8/0x250 [drm]
[226290.971149]  drm_stub_open+0xba/0x140 [drm]
[226290.971168]  chrdev_open+0xf7/0x220
[226290.971172]  ? cdev_device_add+0x90/0x90
[226290.971174]  do_dentry_open+0x156/0x370
[226290.971176]  vfs_open+0x2d/0x30
[226290.971178]  do_open+0x1c3/0x340
[226290.971180]  path_openat+0x10a/0x1d0
[226290.971182]  do_filp_open+0x8c/0x130
[226290.971184]  ? __check_object_size+0x1c/0x20
[226290.971187]  do_sys_openat2+0x9b/0x150
[226290.971189]  __x64_sys_openat+0x56/0x90
[226290.971191]  do_syscall_64+0x38/0x90
[226290.971193]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[226290.971196] RIP: 0033:0x7f71ad5108db
[226290.971198] Code: 25 00 00 41 00 3d 00 00 41 00 74 4b 64 8b 04 25 18 00 00 
00 85 c0 75 67 44 89 e2 48 89 ee bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 
f0 ff ff 0f 87 91 00 00 00 48 8b 4c 24 28 64 48 2b 0c 25
[226290.971199] RSP: 002b:7ffced99e140 EFLAGS: 0246 ORIG_RAX: 
0101
[226290.971201] RAX: ffda RBX: 560941202120 RCX: 
7f71ad5108db
[226290.971202] RDX: 00080002 RSI: 5609412077e0 RDI: 
ff9c
[226290.971203] RBP: 5609412077e0 R08: 7f71abbcd4f0 R09: 
560941207aa2
[226290.971204] R10:  R11: 0246 R12: 
00080002
[226290.971205] R13: 7f71abfea120 R14: 5609412063a0 R15: 
7f71abfcc7a9
[226290.971207] ---[ end trace 6e93d5846e18c259 ]---

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

Title:
  Frequent kernel oops related to nvidia / nv_drm_master_set

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

Bug description:
  After upgrading yesterday from ubuntu 20 to 21.04 my machine now
  exhibits frequent involuntary restarts, related to a kernel oops of
  the form

  Jun  3 10:48:32 zotac kernel: [   20.464926] RIP: 
0010:nv_drm_master_set+0x27/0x30 [nvidia_drm]
  [...]
  Jun  3 10:48:32 zotac kernel: [   20.464958] Call Trace:
  Jun  3 10:48:32 zotac kernel: [   20.464964]  drm_new_set_master+0x7e/0x100 
[drm]
  Jun  3 10:48:32 zotac kernel: [   20.464994]  drm_master_open+0x6e/0xa0 [drm]
  Jun  3 10:48:32 zotac kernel: [   20.465017]  drm_open+0xf8/0x250 [drm]
  Jun  3 10:48:32 zotac kernel: [   20.465044]  drm_stub_open+0xba/0x140 [drm]
  Jun  3 10:48:32 zotac kernel: [   20.465070]  chrdev_open+0xf7/0x220
  Jun  3 10:48:32 zotac kernel: [   20.465075]  ? cdev_device_add+0x90/0x90
  Jun  3 10:48:32 zotac kernel: [   20.465078]  do_dentry_open+0x156/0x370
  Jun  3 10:48:32 zotac kernel: [   20.465081]  vfs_open+0x2d/0x30
  Jun  3 10:48:32 zotac kernel: [   20.465084]  do_open+0x1c3/0x340
  Jun  3 10:48:32 zotac kernel: [   20.465087]  path_openat+0x10a/0x1d0
  Jun  3 10:48:32 zotac kernel: [   20.465090]  do_filp_open+0x8c/0x130
  Jun  3 10:48:32 zotac kernel: [   20.465093]  ? __check_object_size+0x1c/0x20
  Jun  3 10:48:32 zotac kernel: [   20.465096]  do_sys_openat2+0x9b/0x150
  Jun  3 10:48:32 zotac kernel: [   20.465099]  __x64_sys_openat+0x56/0x90
  Jun  3 10:48:32 zotac kernel: [   20.465102]  do_syscall_64+0x38/0x90
  Jun  3 10:48:32 zotac kernel: [   20.465105]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Jun  3 10:48:32 zotac kernel: [   20.465108] RIP: 0033:0x7fe6ea270954

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..0a.00.0: Error: path was not a

[Kernel-packages] [Bug 1930903] Re: Frequent kernel oops related to nvidia / nv_drm_master_set

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

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

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

Title:
  Frequent kernel oops related to nvidia / nv_drm_master_set

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

Bug description:
  After upgrading yesterday from ubuntu 20 to 21.04 my machine now
  exhibits frequent involuntary restarts, related to a kernel oops of
  the form

  Jun  3 10:48:32 zotac kernel: [   20.464926] RIP: 
0010:nv_drm_master_set+0x27/0x30 [nvidia_drm]
  [...]
  Jun  3 10:48:32 zotac kernel: [   20.464958] Call Trace:
  Jun  3 10:48:32 zotac kernel: [   20.464964]  drm_new_set_master+0x7e/0x100 
[drm]
  Jun  3 10:48:32 zotac kernel: [   20.464994]  drm_master_open+0x6e/0xa0 [drm]
  Jun  3 10:48:32 zotac kernel: [   20.465017]  drm_open+0xf8/0x250 [drm]
  Jun  3 10:48:32 zotac kernel: [   20.465044]  drm_stub_open+0xba/0x140 [drm]
  Jun  3 10:48:32 zotac kernel: [   20.465070]  chrdev_open+0xf7/0x220
  Jun  3 10:48:32 zotac kernel: [   20.465075]  ? cdev_device_add+0x90/0x90
  Jun  3 10:48:32 zotac kernel: [   20.465078]  do_dentry_open+0x156/0x370
  Jun  3 10:48:32 zotac kernel: [   20.465081]  vfs_open+0x2d/0x30
  Jun  3 10:48:32 zotac kernel: [   20.465084]  do_open+0x1c3/0x340
  Jun  3 10:48:32 zotac kernel: [   20.465087]  path_openat+0x10a/0x1d0
  Jun  3 10:48:32 zotac kernel: [   20.465090]  do_filp_open+0x8c/0x130
  Jun  3 10:48:32 zotac kernel: [   20.465093]  ? __check_object_size+0x1c/0x20
  Jun  3 10:48:32 zotac kernel: [   20.465096]  do_sys_openat2+0x9b/0x150
  Jun  3 10:48:32 zotac kernel: [   20.465099]  __x64_sys_openat+0x56/0x90
  Jun  3 10:48:32 zotac kernel: [   20.465102]  do_syscall_64+0x38/0x90
  Jun  3 10:48:32 zotac kernel: [   20.465105]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Jun  3 10:48:32 zotac kernel: [   20.465108] RIP: 0033:0x7fe6ea270954

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..0a.00.0: Error: path was not a regular file.
  .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.80  Fri May  7 06:55:54 
UTC 2021
   GCC version:  gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1)
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Fri Jun  4 17:00:45 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 460.80, 5.11.0-18-generic, x86_64: installed
   nvidia, 460.80, 5.8.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] 
[19da:2438]
  InstallationDate: Installed on 2020-05-09 (391 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: NA ZBOX-ER51070
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic 
root=UUID=4e73512b-1846-4fe4-87d1-079bbaae2a1a ro quiet splash 
crashkernel=512M-:192M vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2019
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.12
  dmi.board.asset.tag: Default string
  dmi.board.name: ZBOX-ER51070
  dmi.board.vendor: NA
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd04/25/2019:br5.12:svnNA:pnZBOX-ER51070:pvrDefaultstring:rvnNA:rnZBOX-ER51070:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: ZBOX-ER51070
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: NA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  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.11-1ubuntu1
  version.xserver-xorg-input-evdev:

[Kernel-packages] [Bug 1942377] Re: Linux 5.14/4.13.14 fails to boot

2021-09-06 Thread Gannet

Now 5.13.4 also fails to boot while 5.13.13 is OK. Obviously some fail
code has been backported from 5.14 to 5.13.14.

** Summary changed:

- Linux 5.14 fails to boot
+ Linux 5.14/4.13.14 fails to boot

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

Title:
  Linux 5.14/4.13.14 fails to boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Downloaded and installed packages of 5.14 from
  https://kernel.ubuntu.com/~kernel-ppa/mainline/ I found it is not able
  to boot. Please, look in attachment.

  Motherboard: Asus P5Q3
  CPU: Intel(R) Xeon(R) CPU X5482
  OS: Kubuntu 21.04
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2019-04-13 (872 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  Tags:  hirsute
  Uname: Linux 5.13.13-051313-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to hirsute on 2021-01-06 (238 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eugene 1270 F pulseaudio
   /dev/snd/pcmC0D0p:   eugene 1270 F...m pulseaudio
   /dev/snd/controlC2:  eugene 1270 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.04
  HibernationDevice: RESUME=UUID=7e115b53-56a4-444f-bd93-6ad4f15c4a61
  InstallationDate: Installed on 2019-04-13 (872 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.11.0-31-generic 
root=UUID=d87288b4-dbdd-4448-8088-4ebb6ed6cf33 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-31-generic N/A
   linux-backports-modules-5.11.0-31-generic  N/A
   linux-firmware 1.197.3
  RfKill:
   
  Tags:  hirsute
  Uname: Linux 5.11.0-31-generic x86_64
  UpgradeStatus: Upgraded to hirsute on 2021-01-06 (238 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/11/2010
  dmi.bios.release: 11.2
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1102:bd06/11/2010:br11.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942377/+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 1942784] Re: makedumpfile not properly working on focal with 5.11 kernel

@cascardo,

Good point, just tested it with 5.4 kernel and works fine with it too.

Thanks,
Jo

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

Title:
  makedumpfile not properly working on focal with 5.11 kernel

Status in makedumpfile package in Ubuntu:
  New
Status in makedumpfile source package in Focal:
  Confirmed

Bug description:
  [IMPACT]

  When running Focal with the hwe 5.11 kernel makedumpfile is not working as it 
should.
  Instead of compressing the dump makedumpfile falls back to cp.
  This can create problems on systems with very large RAM and result into 
exhausting all storage on the host.
  This can be resolved with upstream commit 54aec3878b3f([PATCH] make use of 
'uts_namespace.name' offset in VMCOREINFO).

  In addition the dmesg. is not created.
  This can be resolved with the following two commits  :
  - commit c617ec633392([PATCH 1/2] printk: add support for lockless ringbuffer)
  - commit 44b073b7ec46([PATCH 2/2] printk: use committed/finalized state 
values)

  [TEST CASE]

  For testing a machine running focal with the 5.11 kernel is required.
  Then trigger a crash.
  On the console we can see that makedumpfile fails and `falls back to cp`. 
  In /var/crash we can see that no dmesg file is created and instead of the 
dump file
  the uncompressed vmcoreinfo is created.

  [WHERE PROBLEMS COULD OCCUR]

  The 3 commits pulled into focal make makedumpfile compatible with the 5.11 
kernel.
  Any regression potential would involve the crash dump not being created after 
a crash in case kdump is configured.

  [OTHER]

  Only Focal with 5.11 kernel is affected.

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

2021-09-06 Thread Manvydas

Hi. Manvydas here. My bug was closed as a duplicate (#1938936). I can
confirm that Kai-Heng Feng's kernel has fixed this issue on my system as
well. Thank you very much!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 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:
  Fix Committed
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.

  [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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936708/+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 1942784] Re: makedumpfile not properly working on focal with 5.11 kernel

2021-09-06 Thread Ubuntu Foundations Team Bug Bot

The attachment "lp1942784_focal.debdiff" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

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

** Tags added: patch

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

Title:
  makedumpfile not properly working on focal with 5.11 kernel

Status in makedumpfile package in Ubuntu:
  New
Status in makedumpfile source package in Focal:
  Confirmed

Bug description:
  [IMPACT]

  When running Focal with the hwe 5.11 kernel makedumpfile is not working as it 
should.
  Instead of compressing the dump makedumpfile falls back to cp.
  This can create problems on systems with very large RAM and result into 
exhausting all storage on the host.
  This can be resolved with upstream commit 54aec3878b3f([PATCH] make use of 
'uts_namespace.name' offset in VMCOREINFO).

  In addition the dmesg. is not created.
  This can be resolved with the following two commits  :
  - commit c617ec633392([PATCH 1/2] printk: add support for lockless ringbuffer)
  - commit 44b073b7ec46([PATCH 2/2] printk: use committed/finalized state 
values)

  [TEST CASE]

  For testing a machine running focal with the 5.11 kernel is required.
  Then trigger a crash.
  On the console we can see that makedumpfile fails and `falls back to cp`. 
  In /var/crash we can see that no dmesg file is created and instead of the 
dump file
  the uncompressed vmcoreinfo is created.

  [WHERE PROBLEMS COULD OCCUR]

  The 3 commits pulled into focal make makedumpfile compatible with the 5.11 
kernel.
  Any regression potential would involve the crash dump not being created after 
a crash in case kdump is configured.

  [OTHER]

  Only Focal with 5.11 kernel is affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1942784/+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 1940113] Re: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected

2021-09-06 Thread Joseph Maillardet

Result: partial freeze of the screens. No mouse but keyboard ok. htop
running but unable to launch a new prompt or any other process.

** Attachment added: "journalctl.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+attachment/5523256/+files/journalctl.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/1940113

Title:
  Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock
  connected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  My laptop run well with last 5.4 linux kernel even if I connect my
  thunderbolt dock.

  When trying to boot with 5.11.0-25 or 5.11.0-27 (hwe) kernel with dock
  and 2 monitors connected, the kernel panic after 3 or 4 seconds.
  Without the dock, he work fine.

  After a lot of try, I was able to boot sometime on 5.11 with the dock, but 
randomly and only if I only connect 1 extra monitor (I usually use two).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jmaillar   1988 F pulseaudio
   /dev/snd/controlC1:  jmaillar   1988 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=none
  MachineType: Dell Inc. Precision 7530
  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 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=b21fab6e-02fe-4295-a308-9da15f339a36 ro
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-27-generic N/A
   linux-backports-modules-5.11.0-27-generic  N/A
   linux-firmware 1.187.15
  Tags:  focal
  Uname: Linux 5.11.0-27-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-20 (483 days ago)
  UserGroups: adm audio cdrom dip disk input kismet kvm libvirt libvirtd 
lpadmin lxd netdev plugdev sambashare sudo systemd-network users vboxusers 
video wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/25/2021
  dmi.bios.release: 1.16
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.16.1
  dmi.board.name: 0425K7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.16.1:bd05/25/2021:br1.16:svnDellInc.:pnPrecision7530:pvr:rvnDellInc.:rn0425K7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 7530
  dmi.product.sku: 0831
  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: 2015-11-27T14:42:56.796345

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+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 1942215] Re: OOPs on boot: invalid opcode: 0000 [#1] SMP NOPTI

2021-09-06 Thread Andrey Melnikov

Not sufficient. 
There is another BUG() hidden at line 398:

status = acpi_ex_resolve_operands(walk_state->opcode,
&(walk_state->operands[walk_state->num_operands - 1]), walk_state);

in `walk_state->operands[]` array referencing.

After adding same guard for walk_state->operands[]
if (walk_state->num_operands - 1 >= ARRAY_SIZE(walk_state->operands)) {
   ACPI_ERROR((AE_INFO, "Too many operands 0x%X for op_type 0x%X", 
walk_state->num_operands - 1, op_type));
   status = AE_AML_BAD_OPCODE;
   goto cleanup;
}

got in dmesg:

-- cut--

[1.121664] acpi ABCD:00: ACPI dock station (docks/bays count: 1)
[1.125182] ACPI: PM: Power Resource [PX06]
[1.125182] ACPI Error: Too many operands 0x for op_type 0x0 
(20210604/dswexec-397)
[1.125182] No Local Variables are initialized for Method [RREG]
[1.125311] Initialized Arguments for Method [RREG]:  (3 arguments defined 
for method invocation)
[1.125450]   Arg0:   2d6b3afdInteger 
FE028000
[1.125588]   Arg1:   78d25d8cInteger 
0001
[1.125591]   Arg2:   0bca9f52Integer 

[1.125591] ACPI Error: Aborting method \_SB.PCI0.GEXP.RREG due to previous 
error (AE_AML_BAD_OPCODE) (20210604/psparse-529)
[1.125591] ACPI Error: Aborting method \_SB.PCI0.GEXP.CSER due to previous 
error (AE_AML_BAD_OPCODE) (20210604/psparse-529)
[1.125591] ACPI Error: Aborting method \_SB.PCI0.GEXP.GEPS due to previous 
error (AE_AML_BAD_OPCODE) (20210604/psparse-529)
[1.125591] ACPI Error: Aborting method \_SB.PCI0.XHC.RHUB.HS06.PX06._STA 
due to previous error (AE_AML_BAD_OPCODE) (20210604/psparse-529)
[1.125591] ACPI Error: Too many operands 0x for op_type 0x0 
(20210604/dswexec-397)
[1.125591] No Local Variables are initialized for Method [RREG]
[1.125591] Initialized Arguments for Method [RREG]:  (3 arguments defined 
for method invocation)
[1.125591]   Arg0:   6c708c99Integer 
FE028000
[1.125703]   Arg1:   78d25d8cInteger 
0001
[1.125838]   Arg2:   d8c7f611Integer 

[1.126062] ACPI Error: Aborting method \_SB.PCI0.GEXP.RREG due to previous 
error (AE_AML_BAD_OPCODE) (20210604/psparse-529)
[1.126213] ACPI Error: Aborting method \_SB.PCI0.GEXP.CSER due to previous 
error (AE_AML_BAD_OPCODE) (20210604/psparse-529)
[1.126366] ACPI Error: Aborting method \_SB.PCI0.GEXP.GEPS due to previous 
error (AE_AML_BAD_OPCODE) (20210604/psparse-529)
[1.126517] ACPI Error: Aborting method \_SB.PCI0.XHC.RHUB.HS06.PX06._STA 
due to previous error (AE_AML_BAD_OPCODE) (20210604/psparse-529)

-- cut--

have classical underflow here.

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

Title:
  OOPs on boot: invalid opcode:  [#1] SMP NOPTI

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Impish:
  Incomplete

Bug description:
  Using latest Impish kernel 5.13.0-15.15 from ckt/bootstrap PPA, upon
  boot on vought we get this:

  ...
  [   11.502916] invalid opcode:  [#1] SMP NOPTI
  [   11.504249] CPU: 95 PID: 1472 Comm: systemd-udevd Not tainted 
5.13.0-15-generic #15-Ubuntu
  [   11.505734] Hardware name: Intel Corporation S2600WFD/S2600WFD, BIOS 
SE5C620.86B.0D.01.0395.022720191340 02/27/2019
  [   11.507260] RIP: 0010:acpi_ds_exec_end_op+0x187/0x774
  [   11.508771] Code: 77 28 48 8b 04 c5 00 9b ea 91 48 89 df ff d0 0f 1f 00 41 
89 c4 e9 8f 00 00 00 0f b6 43 0d 8d 50 ff 48 63 d2 48 83 fa 09 76 02 <0f> 0b 83 
c0 6c 0f b7 7b 0a 48 89 da 48 98 48 8d 34 c3 e8 c0 3c 01
  [   11.511898] RSP: 0018:aaeca1a776e0 EFLAGS: 00010286
  [   11.513428] RAX:  RBX: 8f08a7573800 RCX: 
0040
  [   11.514972] RDX:  RSI: 91ea9980 RDI: 
02cb
  [   11.516100] RBP: aaeca1a77710 R08:  R09: 
8f08a8c84af0
  [   11.517479] R10:  R11: 0003 R12: 

  [   11.518985] R13: 8f08a8c84af0 R14:  R15: 

  [   11.520425] FS:  7f7fb403ed00() GS:8f348d5c() 
knlGS:
  [   11.521931] CS:  0010 DS:  ES:  CR0: 80050033
  [   11.523424] CR2: 7f7fb38d1918 CR3: 000129b6a002 CR4: 
007706e0
  [   11.524924] DR0:  DR1:  DR2: 

  [   11.526221] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   11.527636] PKRU: 5554
  [   11.528820] Call Trace:
  [   11.529807]  acpi_ps_parse_loop+0x587/0x660
  [   11.531198]  acpi_ps_parse_aml+0x1af/0x552
  [   11.532595]  acpi_ps_execute_method+0x208/0x2ca
  [   11.533972]  acpi_ns_evaluate+0x34e/0x4f0
  [   11.535361]

[Kernel-packages] [Bug 1942784] Re: makedumpfile not properly working on focal with 5.11 kernel

2021-09-06 Thread Thadeu Lima de Souza Cascardo

Hey, @joalif.

Has this been tested with focal 5.4 kernel too?

Thanks.
Cascardo.

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

Title:
  makedumpfile not properly working on focal with 5.11 kernel

Status in makedumpfile package in Ubuntu:
  New
Status in makedumpfile source package in Focal:
  Confirmed

Bug description:
  [IMPACT]

  When running Focal with the hwe 5.11 kernel makedumpfile is not working as it 
should.
  Instead of compressing the dump makedumpfile falls back to cp.
  This can create problems on systems with very large RAM and result into 
exhausting all storage on the host.
  This can be resolved with upstream commit 54aec3878b3f([PATCH] make use of 
'uts_namespace.name' offset in VMCOREINFO).

  In addition the dmesg. is not created.
  This can be resolved with the following two commits  :
  - commit c617ec633392([PATCH 1/2] printk: add support for lockless ringbuffer)
  - commit 44b073b7ec46([PATCH 2/2] printk: use committed/finalized state 
values)

  [TEST CASE]

  For testing a machine running focal with the 5.11 kernel is required.
  Then trigger a crash.
  On the console we can see that makedumpfile fails and `falls back to cp`. 
  In /var/crash we can see that no dmesg file is created and instead of the 
dump file
  the uncompressed vmcoreinfo is created.

  [WHERE PROBLEMS COULD OCCUR]

  The 3 commits pulled into focal make makedumpfile compatible with the 5.11 
kernel.
  Any regression potential would involve the crash dump not being created after 
a crash in case kdump is configured.

  [OTHER]

  Only Focal with 5.11 kernel is affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1942784/+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 1942784] Re: makedumpfile not properly working on focal with 5.11 kernel

** Tags added: sts

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

Title:
  makedumpfile not properly working on focal with 5.11 kernel

Status in makedumpfile package in Ubuntu:
  New
Status in makedumpfile source package in Focal:
  Confirmed

Bug description:
  [IMPACT]

  When running Focal with the hwe 5.11 kernel makedumpfile is not working as it 
should.
  Instead of compressing the dump makedumpfile falls back to cp.
  This can create problems on systems with very large RAM and result into 
exhausting all storage on the host.
  This can be resolved with upstream commit 54aec3878b3f([PATCH] make use of 
'uts_namespace.name' offset in VMCOREINFO).

  In addition the dmesg. is not created.
  This can be resolved with the following two commits  :
  - commit c617ec633392([PATCH 1/2] printk: add support for lockless ringbuffer)
  - commit 44b073b7ec46([PATCH 2/2] printk: use committed/finalized state 
values)

  [TEST CASE]

  For testing a machine running focal with the 5.11 kernel is required.
  Then trigger a crash.
  On the console we can see that makedumpfile fails and `falls back to cp`. 
  In /var/crash we can see that no dmesg file is created and instead of the 
dump file
  the uncompressed vmcoreinfo is created.

  [WHERE PROBLEMS COULD OCCUR]

  The 3 commits pulled into focal make makedumpfile compatible with the 5.11 
kernel.
  Any regression potential would involve the crash dump not being created after 
a crash in case kdump is configured.

  [OTHER]

  Only Focal with 5.11 kernel is affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1942784/+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 1942784] Re: makedumpfile not properly working on focal with 5.11 kernel

Debdiff for Focal.

** Patch added: "lp1942784_focal.debdiff"

https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1942784/+attachment/5523255/+files/lp1942784_focal.debdiff

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

Title:
makedumpfile not properly working on focal with 5.11 kernel

Status in makedumpfile package in Ubuntu:
New
Status in makedumpfile source package in Focal:
Confirmed

Bug description:
[IMPACT]

When running Focal with the hwe 5.11 kernel makedumpfile is not working as it
should.
Instead of compressing the dump makedumpfile falls back to cp.
This can create problems on systems with very large RAM and result into
exhausting all storage on the host.
This can be resolved with upstream commit 54aec3878b3f([PATCH] make use of
'uts_namespace.name' offset in VMCOREINFO).

In addition the dmesg. is not created.
This can be resolved with the following two commits :
- commit c617ec633392([PATCH 1/2] printk: add support for lockless ringbuffer)
- commit 44b073b7ec46([PATCH 2/2] printk: use committed/finalized state
values)

[TEST CASE]

For testing a machine running focal with the 5.11 kernel is required.
Then trigger a crash.
On the console we can see that makedumpfile fails and `falls back to cp`.
In /var/crash we can see that no dmesg file is created and instead of the
dump file
the uncompressed vmcoreinfo is created.

[WHERE PROBLEMS COULD OCCUR]

The 3 commits pulled into focal make makedumpfile compatible with the 5.11
kernel.
Any regression potential would involve the crash dump not being created after
a crash in case kdump is configured.

[OTHER]

Only Focal with 5.11 kernel is affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1942784/+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 1942784] [NEW] makedumpfile not properly working on focal with 5.11 kernel

Public bug reported:

[IMPACT]

When running Focal with the hwe 5.11 kernel makedumpfile is not working as it 
should.
Instead of compressing the dump makedumpfile falls back to cp.
This can create problems on systems with very large RAM and result into 
exhausting all storage on the host.
This can be resolved with upstream commit 54aec3878b3f([PATCH] make use of 
'uts_namespace.name' offset in VMCOREINFO).

In addition the dmesg. is not created.
This can be resolved with the following two commits  :
- commit c617ec633392([PATCH 1/2] printk: add support for lockless ringbuffer)
- commit 44b073b7ec46([PATCH 2/2] printk: use committed/finalized state values)

[TEST CASE]

For testing a machine running focal with the 5.11 kernel is required.
Then trigger a crash.
On the console we can see that makedumpfile fails and `falls back to cp`. 
In /var/crash we can see that no dmesg file is created and instead of the dump 
file
the uncompressed vmcoreinfo is created.

[WHERE PROBLEMS COULD OCCUR]

The 3 commits pulled into focal make makedumpfile compatible with the 5.11 
kernel.
Any regression potential would involve the crash dump not being created after a 
crash in case kdump is configured.

[OTHER]

Only Focal with 5.11 kernel is affected.

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

** Affects: makedumpfile (Ubuntu Focal)
 Importance: Medium
 Assignee: Ioanna Alifieraki (joalif)
 Status: Confirmed

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

** Changed in: makedumpfile (Ubuntu Focal)
 Assignee: (unassigned) => Ioanna Alifieraki (joalif)

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

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

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

Title:
  makedumpfile not properly working on focal with 5.11 kernel

Status in makedumpfile package in Ubuntu:
  New
Status in makedumpfile source package in Focal:
  Confirmed

Bug description:
  [IMPACT]

  When running Focal with the hwe 5.11 kernel makedumpfile is not working as it 
should.
  Instead of compressing the dump makedumpfile falls back to cp.
  This can create problems on systems with very large RAM and result into 
exhausting all storage on the host.
  This can be resolved with upstream commit 54aec3878b3f([PATCH] make use of 
'uts_namespace.name' offset in VMCOREINFO).

  In addition the dmesg. is not created.
  This can be resolved with the following two commits  :
  - commit c617ec633392([PATCH 1/2] printk: add support for lockless ringbuffer)
  - commit 44b073b7ec46([PATCH 2/2] printk: use committed/finalized state 
values)

  [TEST CASE]

  For testing a machine running focal with the 5.11 kernel is required.
  Then trigger a crash.
  On the console we can see that makedumpfile fails and `falls back to cp`. 
  In /var/crash we can see that no dmesg file is created and instead of the 
dump file
  the uncompressed vmcoreinfo is created.

  [WHERE PROBLEMS COULD OCCUR]

  The 3 commits pulled into focal make makedumpfile compatible with the 5.11 
kernel.
  Any regression potential would involve the crash dump not being created after 
a crash in case kdump is configured.

  [OTHER]

  Only Focal with 5.11 kernel is affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1942784/+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 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS

2021-09-06 Thread Hash Ratez

Dear TuxInvader...

I have no idea why you do what you do but THANK YOU.  I HAVE BEEN GOING
NUTS trying to get past the kernel bug for Ubuntu upgrades.  WTF, they
call 20.04 an LTS but you cannot keep up with kernel security patches.
ARE YOU KIDDING?

YOU SAVED ME.

Hours and hours of install reboot, uninstall.  Nothing worked (please
note I am a total Linux admin hack, thus really can't bake my own
kernels).  I found this link, installed it and BAM, now running 5.10.61
etc.  Just wanted to keep the LTS 5.10 patched and you can forget Ubuntu
for not keeping up.

REF: https://launchpad.net/~tuxinvader/+archive/ubuntu/lts-mainline-
longterm

ONE COMMAND FIXES EVERTYHING (after you add TuxInvader PPA): sudo apt-
get install linux-generic-5.10

That will upgrade you to the latest 5.10.x build.  It is that easy.

THANK YOU.  Really...

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

Title:
  Recent mainline packages are built with Hirsuite 21.04, not Focal
  20.04 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi all,

  The Mainline wiki states that the mainline kernels are built with the
  previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are
  being built with Hirsuite 21.04, and before that Groovy? If this is
  intentional, then the wiki should be updated to reflect the change in
  policy.

  From https://wiki.ubuntu.com/Kernel/MainlineBuilds

Mainline kernel build toolchain
These kernels are built with the toolchain (gcc, g++, etc.) from the 
previous Ubuntu LTS release. 
(e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic 
Beaver", etc.) Therefore, 
out-of-tree kernel modules you already have built and installed for use 
with your release kernels 
are not likely to work with the mainline builds.

  The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On
  my Focal LTS system I have GCC 9.3.0.

  The Mainline kernel build toolchain
  These kernels are built with the toolchain (gcc, g++, etc.) from the previous 
Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 
18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already 
have built and installed for use with your release kernels are not likely to 
work with the mainline builds.

  The *linux-headers-generic* packages have unmet dependencies on 20.04
  LTS.

  I could install Groovy built kernels fine, but the Hirsuite ones built
  with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels
  can't be installed on Focal (libc 2.31).

  Thanks,
  Mark

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+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 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1])

This issue can be reproduced on P8 node entei with:
  * F-5.4 (5.4.0-81-generic)
  * F-5.11 (5.11.0-27-generic #29~20.04.1-Ubuntu)
  * H-5.11 (5.11.0-31-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/1927076

Title:
  IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash
  P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4
  [#1])

Status in ubuntu-kernel-tests:
  New
Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Hirsute:
  New

Bug description:
  It looks like our P8 node "entei" tend to fail with the IPv6 TCP test
  from reuseport_bpf_cpu in ubuntu_kernel_selftests/net on 5.8 kernels:

   # send cpu 119, receive socket 119
   # send cpu 121, receive socket 121
   # send cpu 123, receive socket 123
   # send cpu 125, receive socket 125
   # send cpu 127, receive socket 127
   #  IPv6 TCP 
  publish-job-status: using request.json

  It failed silently here, this can be 100% reproduced with Groovy 5.8
  and Focal 5.8.

  This will cause the ubuntu_kernel_selftests being interrupted, the
  test result for other tests cannot be processed to our result page.

  Please find attachment for the complete "net" test result on this node
  with Groovy 5.8.0-52.59

  Add the kqa-blocker tag as this might needs to be manually verified.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+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 1941955] Please test proposed package

2021-09-06 Thread Łukasz Zemczak

Hello Seth, or anyone else affected,

Accepted wireless-regdb into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/wireless-
regdb/2021.08.28-0ubuntu1~18.04.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  New upstream release 2021.08.28

Status in wireless-regdb package in Ubuntu:
  Fix Released
Status in wireless-regdb source package in Bionic:
  Fix Committed
Status in wireless-regdb source package in Focal:
  Fix Committed
Status in wireless-regdb source package in Hirsute:
  Fix Committed
Status in wireless-regdb source package in Impish:
  Fix Released

Bug description:
  [Impact]

  New upstream release. This is a database of wireless regulations, and
  should updated in all releases to ensure users have the most up-to-
  date regulatory information.

  [Test Case]

  Following reboot after installing the new database, it should be
  possible to query and change the regulatory domain using 'iw reg get'
  and 'iw reg set'.

  [Where problems could occur]

  If crda or the kernel is unable to use the new database, users may be
  stuck using the default "world" regulatory domain which is quite
  restrictive, therefore they may be unable to use wireless channels
  that they were able to use previously. Regulatory rules may have also
  changed for the user's region, which could also make some channels
  unusable, but this would not be a bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1941955/+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 1941955] Please test proposed package

2021-09-06 Thread Łukasz Zemczak

Hello Seth, or anyone else affected,

Accepted wireless-regdb into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/wireless-
regdb/2021.08.28-0ubuntu1~20.04.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: wireless-regdb (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  New upstream release 2021.08.28

Status in wireless-regdb package in Ubuntu:
  Fix Released
Status in wireless-regdb source package in Bionic:
  Fix Committed
Status in wireless-regdb source package in Focal:
  Fix Committed
Status in wireless-regdb source package in Hirsute:
  Fix Committed
Status in wireless-regdb source package in Impish:
  Fix Released

Bug description:
  [Impact]

  New upstream release. This is a database of wireless regulations, and
  should updated in all releases to ensure users have the most up-to-
  date regulatory information.

  [Test Case]

  Following reboot after installing the new database, it should be
  possible to query and change the regulatory domain using 'iw reg get'
  and 'iw reg set'.

  [Where problems could occur]

  If crda or the kernel is unable to use the new database, users may be
  stuck using the default "world" regulatory domain which is quite
  restrictive, therefore they may be unable to use wireless channels
  that they were able to use previously. Regulatory rules may have also
  changed for the user's region, which could also make some channels
  unusable, but this would not be a bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1941955/+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 1941955] Re: New upstream release 2021.08.28

2021-09-06 Thread Łukasz Zemczak

Hello Seth, or anyone else affected,

Accepted wireless-regdb into hirsute-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/wireless-
regdb/2021.08.28-0ubuntu1~21.04.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: wireless-regdb (Ubuntu Hirsute)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-hirsute

** Changed in: wireless-regdb (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-focal

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

Title:
  New upstream release 2021.08.28

Status in wireless-regdb package in Ubuntu:
  Fix Released
Status in wireless-regdb source package in Bionic:
  Fix Committed
Status in wireless-regdb source package in Focal:
  Fix Committed
Status in wireless-regdb source package in Hirsute:
  Fix Committed
Status in wireless-regdb source package in Impish:
  Fix Released

Bug description:
  [Impact]

  New upstream release. This is a database of wireless regulations, and
  should updated in all releases to ensure users have the most up-to-
  date regulatory information.

  [Test Case]

  Following reboot after installing the new database, it should be
  possible to query and change the regulatory domain using 'iw reg get'
  and 'iw reg set'.

  [Where problems could occur]

  If crda or the kernel is unable to use the new database, users may be
  stuck using the default "world" regulatory domain which is quite
  restrictive, therefore they may be unable to use wireless channels
  that they were able to use previously. Regulatory rules may have also
  changed for the user's region, which could also make some channels
  unusable, but this would not be a bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1941955/+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 1940113] Re: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected

2021-09-06 Thread Chris Chiu

Good. Please help me test the kernel in
https://people.canonical.com/~mschiu77/lp1940113/amd_3.2.140/. Thanks

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

Title:
  Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock
  connected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  My laptop run well with last 5.4 linux kernel even if I connect my
  thunderbolt dock.

  When trying to boot with 5.11.0-25 or 5.11.0-27 (hwe) kernel with dock
  and 2 monitors connected, the kernel panic after 3 or 4 seconds.
  Without the dock, he work fine.

  After a lot of try, I was able to boot sometime on 5.11 with the dock, but 
randomly and only if I only connect 1 extra monitor (I usually use two).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jmaillar   1988 F pulseaudio
   /dev/snd/controlC1:  jmaillar   1988 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=none
  MachineType: Dell Inc. Precision 7530
  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 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=b21fab6e-02fe-4295-a308-9da15f339a36 ro
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-27-generic N/A
   linux-backports-modules-5.11.0-27-generic  N/A
   linux-firmware 1.187.15
  Tags:  focal
  Uname: Linux 5.11.0-27-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-20 (483 days ago)
  UserGroups: adm audio cdrom dip disk input kismet kvm libvirt libvirtd 
lpadmin lxd netdev plugdev sambashare sudo systemd-network users vboxusers 
video wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/25/2021
  dmi.bios.release: 1.16
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.16.1
  dmi.board.name: 0425K7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.16.1:bd05/25/2021:br1.16:svnDellInc.:pnPrecision7530:pvr:rvnDellInc.:rn0425K7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 7530
  dmi.product.sku: 0831
  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: 2015-11-27T14:42:56.796345

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+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 1941773] Re: kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver

2021-09-06 Thread Chris Chiu

It should be caused by the kbuild flag `-fcf-protection=none` and this
will not be applied for the UBUNTU release image.

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

Title:
  kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I do not know how to find information to help debug.
  The laptop is lenovo E15 with latest BIOS 1.13

  kubuntu 21.04

  laptop boots correctly with 5.13.8 and trackpad works.
  with 5.13.9, 5.13.11, 5.13.13 it makes a kernel panic.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2021-08-12 (13 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Package: linux (not installed)
  Tags:  hirsute
  Uname: Linux 5.13.8-051308-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2021-08-12 (14 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Package: linux (not installed)
  Tags:  hirsute
  Uname: Linux 5.13.8-051308-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

2021-09-06 Thread Paul Szabo

Seems the issue affects devices from multiple manufacturers,
and various models. Maybe some "commonality" can be found
between them, to trigger disabling ASPM they cannot handle,
better than trying to enumerate them in kernel sources as
suggested in commit 956c6d4f20c5446727e0c912dd8f527f2dc7b779,
see e.g.
https://lore.kernel.org/lkml/20210715182639.085551...@linuxfoundation.org/

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

Title:
  rtw88_8821ce causes freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card.
  Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic 
kernel,and it works "well" for both WiFi and Bluetooth.
  However, this module (driver) causes frequent freezes, randomly but usually 
within a few minutes of running (thus very soon after boot): screen display 
remains frozen, no response to either keyboard or mouse input. All I can do is 
to hold the power button to power off, then reboot.

  After reboot, I do not see any crash reports, nor logs about the freeze.
  Please let me know if I should try to collect some info, and how.

  For now I use the DKMS module/driver from
    https://github.com/tomaspinho/rtl8821ce
  (having blacklisted rtw88_8821ce), and it seems to work perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-16-generic 5.11.0-16.17
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  psz1189 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  8 16:58:19 2021
  InstallationDate: Installed on 2021-04-23 (14 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera
   Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Protempo Ltd L116HTN6SPW
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=f3700d1b-be99-4cb7-baef-c0f157487c64 ro quiet splash pci=noaer 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-16-generic N/A
   linux-backports-modules-5.11.0-16-generic  N/A
   linux-firmware 1.197
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2020
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: YHSM-BI-11.6-X116AR300-AA55C-195-A
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrYHSM-BI-11.6-X116AR300-AA55C-195-A:bd05/26/2020:br5.12:efr1.6:svnProtempoLtd:pnL116HTN6SPW:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Notebook
  dmi.product.name: L116HTN6SPW
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Protempo Ltd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927808/+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 1942759] [NEW] No touchpad detected on 'HP ZBook Firefly G8 (1G3U1AV)' after fresh install

2021-09-06 Thread Hajo Erwich

Public bug reported:

Ubuntu 18.04.5 LTS
The touchpad is not detected with or without the Logitech M705 mouse plugged in.

cat /proc/bus/input/devices

Outputs:

I: Bus=0019 Vendor= Product=0003 Version=
N: Name="Sleep Button"
P: Phys=PNP0C0E/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0
U: Uniq=
H: Handlers=kbd event0 
B: PROP=0
B: EV=3
B: KEY=4000 0 0

I: Bus=0019 Vendor= Product=0005 Version=
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1
U: Uniq=
H: Handlers=event1 
B: PROP=0
B: EV=21
B: SW=1

I: Bus=0019 Vendor= Product=0001 Version=
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2
U: Uniq=
H: Handlers=kbd event2 
B: PROP=0
B: EV=3
B: KEY=10 0

I: Bus=0019 Vendor= Product=0001 Version=
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
U: Uniq=
H: Handlers=kbd event3 
B: PROP=0
B: EV=3
B: KEY=10 0

I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input4
U: Uniq=
H: Handlers=sysrq kbd event4 leds 
B: PROP=0
B: EV=120013
B: KEY=20 0 0 1500f0210 43803078f900d401 fedfffef fffe
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=046d Product=101b Version=0111
N: Name="Logitech M705"
P: Phys=usb-:00:14.0-4/input2:1
S: 
Sysfs=/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.2/0003:046D:C52B.0004/0003:046D:101B.0005/input/input14
U: Uniq=101b-fc-92-33-df
H: Handlers=mouse0 event5 
B: PROP=0
B: EV=17
B: KEY= 0 0 0 0
B: REL=1943
B: MSC=10

I: Bus=0019 Vendor= Product= Version=
N: Name="HP Wireless hotkeys"
P: Phys=hpq6001/input0
S: Sysfs=/devices/virtual/input/input15
U: Uniq=
H: Handlers=rfkill kbd event6 
B: PROP=0
B: EV=3
B: KEY=80 0 0 0

I: Bus=0019 Vendor= Product= Version=
N: Name="Intel HID events"
P: Phys=
S: Sysfs=/devices/platform/INT33D5:00/input/input16
U: Uniq=
H: Handlers=rfkill kbd event7 
B: PROP=0
B: EV=13
B: KEY=810003 504000 1e29400020 0
B: MSC=10

I: Bus=0019 Vendor= Product= Version=
N: Name="Intel HID 5 button array"
P: Phys=
S: Sysfs=/devices/platform/INT33D5:00/input/input17
U: Uniq=
H: Handlers=kbd event8 
B: PROP=0
B: EV=13
B: KEY=2 0 0 0 0 1 0 201c 0
B: MSC=10

I: Bus=0019 Vendor= Product= Version=
N: Name="HP WMI hotkeys"
P: Phys=wmi/input0
S: Sysfs=/devices/virtual/input/input18
U: Uniq=
H: Handlers=kbd event9 
B: PROP=0
B: EV=33
B: KEY=40 0 10007 2102400 0 0
B: MSC=10
B: SW=0

I: Bus=0003 Vendor=04f2 Product=b6bf Version=0013
N: Name="HP HD Camera: HP HD Camera"
P: Phys=usb-:00:14.0-2/button
S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-2/3-2:1.0/input/input19
U: Uniq=
H: Handlers=kbd event10 
B: PROP=0
B: EV=3
B: KEY=10 0 0 0

I: Bus=0003 Vendor=04f2 Product=b6bf Version=0013
N: Name="HP HD Camera: HP IR Camera"
P: Phys=usb-:00:14.0-2/button
S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-2/3-2:1.2/input/input20
U: Uniq=
H: Handlers=kbd event11 
B: PROP=0
B: EV=3
B: KEY=10 0 0 0

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-5.4.0-81-generic 5.4.0-81.91~18.04.1
ProcVersionSignature: Ubuntu 5.4.0-81.91~18.04.1-generic 5.4.128
Uname: Linux 5.4.0-81-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.24
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep  6 11:37:52 2021
InstallationDate: Installed on 2021-09-06 (0 days ago)
InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
SourcePackage: linux-signed-hwe-5.4
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  No touchpad detected on 'HP ZBook Firefly G8 (1G3U1AV)' after fresh
  install

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

Bug description:
  Ubuntu 18.04.5 LTS
  The touchpad is not detected with or without the Logitech M705 mouse plugged 
in.

  cat /proc/bus/input/devices

  Outputs:

  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name="Sleep Button"
  P: Phys=PNP0C0E/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0
  U: Uniq=
  H: Handlers=kbd event0 
  B: PROP=0
  B: EV=3
  B: KEY=4000 0 0

  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1
  U: Uniq=
  H: Handlers=event1 
  B: PROP=0
  B: EV=21
  B:

[Kernel-packages] [Bug 1939287] Re: dbgsym package is missing for ubuntu focal hwe kernel 5.11

The security PPA where 5.11.0-27 was built has "build dbgsyms" checked
but not "publish dbgsyms" this seems odd, cause i would think it is
useful to have access to published security ppa dbgsymbols.

Removing debug symbols is not nice. However, surely we can make disk
space savings the other way. For example, we do not need to produce
udebs for the hwe kernels anymore.

And we can experiment with using `Rules-Requires-Root: no` to allow us
building all packages in one go as non-root and without fakeroot.

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

Title:
  dbgsym package is missing for ubuntu focal hwe kernel 5.11

Status in linux-hwe-5.11 package in Ubuntu:
  Confirmed
Status in linux-hwe-5.11 source package in Focal:
  Confirmed

Bug description:
  Package "linux-image-unsigned-5.11.0-25-generic-dbgsym" is missing
  from http://ddebs.ubuntu.com/dists/focal-updates/main/binary-
  amd64/Packages

  This breaks our workflow when the system is automatically upgraded
  from 5.8.0 to 5.11.0. We have "linux-image-unsigned-5.8.0-63-generic-
  dbgsym" for focal, which is also an HWE kernel. So why not do the same
  for 5.11.0 kernels?

  Also, on focal, we have "linux-image-5.11.0-25-generic-dbgsym", which
  depends on the unsigned one, but the latter does not exist. This seems
  to indicate something is broken.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1939287/+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 1939287] Re: dbgsym package is missing for ubuntu focal hwe kernel 5.11

** Changed in: linux-hwe-5.11 (Ubuntu Focal)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: linux-hwe-5.11 (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

Title:
  dbgsym package is missing for ubuntu focal hwe kernel 5.11

Status in linux-hwe-5.11 package in Ubuntu:
  Confirmed
Status in linux-hwe-5.11 source package in Focal:
  Confirmed

Bug description:
  Package "linux-image-unsigned-5.11.0-25-generic-dbgsym" is missing
  from http://ddebs.ubuntu.com/dists/focal-updates/main/binary-
  amd64/Packages

  This breaks our workflow when the system is automatically upgraded
  from 5.8.0 to 5.11.0. We have "linux-image-unsigned-5.8.0-63-generic-
  dbgsym" for focal, which is also an HWE kernel. So why not do the same
  for 5.11.0 kernels?

  Also, on focal, we have "linux-image-5.11.0-25-generic-dbgsym", which
  depends on the unsigned one, but the latter does not exist. This seems
  to indicate something is broken.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1939287/+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 1934239] Re: mute/micmute LEDs no function on HP EliteBook 830 G8 Notebook PC

2021-09-06 Thread jeremyszu

Test 5.13.0-1011-oem from -proposed. It doesn't containing the patch.
Check the git tree as well. It doesn't exist.

** Tags removed: verification-needed-focal
** Tags added: verification-failed-fo

** Tags removed: verification-failed-fo
** Tags added: verification-failed-focal

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

Title:
  mute/micmute LEDs no function on HP EliteBook 830 G8 Notebook PC

Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux-oem-5.13 source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Invalid
Status in linux source package in Hirsute:
  Fix Released
Status in linux source package in Impish:
  Incomplete

Bug description:
  [Impact]
  The mic mute/audio mute LEDS are not work on HP EliteBook 830 G8 Notebook PC

  [Fix]
  It needs the specific quirk for the hardware layout.
  Thus, add the quirks to make it works.

  [Test]
  After applying the quirk, the audio/mic mute LEDs are working good.

  [Where problems could occur]
  If HP ships the different system boards design with the same subsystem ID of 
audio codec which is using different GPIO pins (different layout), then the 
quirk will not work (LEDs will not work when muting audio-output or microphone).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1934239/+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 1939225] Re: supervisor read write access in kernel mode

2021-09-06 Thread hereiam

** Attachment added: "error8.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1939225/+attachment/5523214/+files/error8.txt

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

Title:
  supervisor read write access in kernel mode

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

Bug description:
  There was a null pointer error.

  I attached the error log from journal control.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug  8 09:54:04 2021
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1939225/+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 1938689] Re: [SRU][H/OEM-5.10/OEM-5.13/U] Fix system hang after unplug tbt dock

2021-09-06 Thread AaronMa

** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

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

Title:
  [SRU][H/OEM-5.10/OEM-5.13/U] Fix system hang after unplug tbt dock

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

Bug description:
  SRU justification:

  [Impact]
  System hang after unplug thunderbolt dock with Intel igc lan.

  [Fix]
  igc driver continue reading and writing MMIO address after PCI device is 
unplugged.
  This cause system page fault, and system hang.
  Add safe check and prevent reading and writing the MMIO.

  The patch is in maintainer's tree, but not merged to Linus's tree.
  Due to the schedule, send SRU as SAUCE patch.

  [Test]
  Verified on hardware, after unplug the thunderbolt cable,
  system work fine.

  [Where problems could occur]
  It may break the igc driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1938689/+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 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS

2021-09-06 Thread TuxInvader

@nvrmndr - Works for me :-)
Please open a bug on my github project if you want help debugging it.

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

Title:
  Recent mainline packages are built with Hirsuite 21.04, not Focal
  20.04 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi all,

  The Mainline wiki states that the mainline kernels are built with the
  previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are
  being built with Hirsuite 21.04, and before that Groovy? If this is
  intentional, then the wiki should be updated to reflect the change in
  policy.

  From https://wiki.ubuntu.com/Kernel/MainlineBuilds

Mainline kernel build toolchain
These kernels are built with the toolchain (gcc, g++, etc.) from the 
previous Ubuntu LTS release. 
(e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic 
Beaver", etc.) Therefore, 
out-of-tree kernel modules you already have built and installed for use 
with your release kernels 
are not likely to work with the mainline builds.

  The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On
  my Focal LTS system I have GCC 9.3.0.

  The Mainline kernel build toolchain
  These kernels are built with the toolchain (gcc, g++, etc.) from the previous 
Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 
18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already 
have built and installed for use with your release kernels are not likely to 
work with the mainline builds.

  The *linux-headers-generic* packages have unmet dependencies on 20.04
  LTS.

  I could install Groovy built kernels fine, but the Hirsuite ones built
  with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels
  can't be installed on Focal (libc 2.31).

  Thanks,
  Mark

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+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 1942738] Re: XOrg / nouveau - hard lockups and does not draw to screen

2021-09-06 Thread JXT

Well I'm less concerned with getting the old GPU to work (again just a
test system trying to debug dual GPU in general) as I am getting my NEW
GPU's on my workstation working in 21.04 and future releases. Right now
Dual GPU is horribly broken and it's spans tons huge swathes of the
system. My set up has been fine for years...though updates have slowly
broken more and more. However 20.04 and newer completely break things.
I'm not really down with having to buy a new computers to run my other
GPU's or just ripping my GPU's out and tossing them and my screens aside
because something / someone decided to break everything moving forward.
I will say after some updates and tinkering I got 21.04 (XFCE) stable
but lots of things are just broken/unusable. On a normal Ubuntu install
for example launching anything on the other GPU's/Xscreens results in
ignored theming, broken input and Win95 like Window smearing just to
name a few problems.

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

Title:
  XOrg / nouveau - hard lockups and does not draw to screen

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-ati package in Ubuntu:
  New
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  Changing display settings hard locks the machine (no reisub save).
  Installing nouveau-firmware allows changes to be made without hard
  lock ups but the screen using nouveau draws the mouse cursor and will
  launch apps on it but does not draw anything on screen. Dmesg is
  flooded with nouveau and XOrg failure messages.

  Description:  Ubuntu 21.04
  Release:  21.04

  xorg:
Installed: 1:7.7+22ubuntu1
Candidate: 1:7.7+22ubuntu1
Version table:
   *** 1:7.7+22ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  nouveau-firmware:
Installed: 20091212-0ubuntu1
Candidate: 20091212-0ubuntu1
Version table:
   *** 20091212-0ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu hirsute/multiverse amd64 
Packages
  500 http://ca.archive.ubuntu.com/ubuntu hirsute/multiverse i386 
Packages
  100 /var/lib/dpkg/status

  
  xserver-xorg-video-nouveau:
Installed: 1:1.0.17-1
Candidate: 1:1.0.17-1
Version table:
   *** 1:1.0.17-1 500
  500 http://ca.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  Uname: Linux 5.11.0-31-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: XFCE
  Date: Sun Sep  5 23:52:43 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6100 nForce 405] [10de:03d1] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Elitegroup Computer Systems C61 [GeForce 6100 nForce 405] 
[1019:2601]
   Advanced Micro Devices, Inc. [AMD/ATI] Oland XT [Radeon HD 8670 / R7 
250/350] [1002:6610] (prog-if 00 [VGA controller])
 Subsystem: Diamond Multimedia Systems Oland XT [Radeon HD 8670 / R7 
250/350] [1092:0250]
  InstallationDate: Installed on 2021-04-07 (151 days ago)
  InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 04d9:a0cd Holtek Semiconductor, Inc. USB Keyboard
   Bus 002 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Acer ASE380/AST180/APM8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-31-generic 
root=UUID=cf6234fa-9047-4e3a-8931-f8f36bce86cf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/29/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: R01-B1
  dmi.board.name: EM61SM/EM61PM
  dmi.board.vendor: Acer
  dmi.chassis.asset.tag: Asset tag number: at least 22 digits
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrR01-B1:bd12/29/2006:svnAcer:pnASE380/AST180/APM8:pvrR01-B1:rvnAcer:rnEM61SM/EM61PM:rvr:cvn:ct3:cvr:
  dmi.product.name: ASE380/AST180/APM8
  dmi.product.version: R01-B1
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3
  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:

[Kernel-packages] [Bug 1938650] Re: iwd on Ubuntu 20.04 stopped working since update to kernel 5.11

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

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

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

Title:
  iwd on Ubuntu 20.04 stopped working since update to  kernel 5.11

Status in iwd package in Ubuntu:
  Confirmed
Status in linux-meta-hwe-5.11 package in Ubuntu:
  Confirmed

Bug description:
  I was using iwd on my Acer aspire v17 nitro with Ubuntu 20.04, and it was 
working great. But after the last update to kernel 5.11 it suddenly had stopped 
working. I’ve tried to reinstall it but that didn’t help. I've tried back with 
kernel 5.8 and iwd was working again. Quick google search showed that this is 
actually a wide spread problem since kernel 5.9.x, so I wish to ask is there 
going to be a solution of any kind?
  Regards!
  I.Ivanov
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-07-28 (6 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: iwd 1.5-1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Tags:  focal
  Uname: Linux 5.11.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iwd/+bug/1938650/+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 1942738] Re: XOrg / nouveau - hard lockups and does not draw to screen

I also wish older GPUs were still supported but Nvidia makes it tricky.
The open source "nouveau" driver is almost always buggy and the closed
source drivers only ever support GPUs for a limited number of years
(admittedly the Linux kernel driver model is to blame for that rather
than Nvidia but being closed source is part of it).

If there was anything we (Canonical) could do to improve the situation
then we would.

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

Title:
  XOrg / nouveau - hard lockups and does not draw to screen

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-ati package in Ubuntu:
  New
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  Changing display settings hard locks the machine (no reisub save).
  Installing nouveau-firmware allows changes to be made without hard
  lock ups but the screen using nouveau draws the mouse cursor and will
  launch apps on it but does not draw anything on screen. Dmesg is
  flooded with nouveau and XOrg failure messages.

  Description:  Ubuntu 21.04
  Release:  21.04

  xorg:
Installed: 1:7.7+22ubuntu1
Candidate: 1:7.7+22ubuntu1
Version table:
   *** 1:7.7+22ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  nouveau-firmware:
Installed: 20091212-0ubuntu1
Candidate: 20091212-0ubuntu1
Version table:
   *** 20091212-0ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu hirsute/multiverse amd64 
Packages
  500 http://ca.archive.ubuntu.com/ubuntu hirsute/multiverse i386 
Packages
  100 /var/lib/dpkg/status

  
  xserver-xorg-video-nouveau:
Installed: 1:1.0.17-1
Candidate: 1:1.0.17-1
Version table:
   *** 1:1.0.17-1 500
  500 http://ca.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  Uname: Linux 5.11.0-31-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: XFCE
  Date: Sun Sep  5 23:52:43 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6100 nForce 405] [10de:03d1] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Elitegroup Computer Systems C61 [GeForce 6100 nForce 405] 
[1019:2601]
   Advanced Micro Devices, Inc. [AMD/ATI] Oland XT [Radeon HD 8670 / R7 
250/350] [1002:6610] (prog-if 00 [VGA controller])
 Subsystem: Diamond Multimedia Systems Oland XT [Radeon HD 8670 / R7 
250/350] [1092:0250]
  InstallationDate: Installed on 2021-04-07 (151 days ago)
  InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 04d9:a0cd Holtek Semiconductor, Inc. USB Keyboard
   Bus 002 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Acer ASE380/AST180/APM8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-31-generic 
root=UUID=cf6234fa-9047-4e3a-8931-f8f36bce86cf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/29/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: R01-B1
  dmi.board.name: EM61SM/EM61PM
  dmi.board.vendor: Acer
  dmi.chassis.asset.tag: Asset tag number: at least 22 digits
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrR01-B1:bd12/29/2006:svnAcer:pnASE380/AST180/APM8:pvrR01-B1:rvnAcer:rnEM61SM/EM61PM:rvr:cvn:ct3:cvr:
  dmi.product.name: ASE380/AST180/APM8
  dmi.product.version: R01-B1
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3
  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/1942738/+subscriptions


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

[Kernel-packages] [Bug 1942738] Re: XOrg / nouveau - hard lockups and does not draw to screen

2021-09-06 Thread JXT

This machine is a frankenstien to help debug the issues with my main
workstation. I need to upgrade but dual GPU is horribly broken on across
all flavors and even non-Ubuntu/Debian distros.

I was explicitly testing how the system functions with no xorg.conf
between 2 separate GPU's. Yes the nVidia GPU is ancient and too old for
the proprietary drivers. Again just what I had on hand to simulate dual
GPU's for testing so I don't have to butcher my workstation while I
test. However despite the age of the nVidia GPU this nouveau issue
persists on newer cards as well.

Workstation has two "modern" GTX 1XXX series cards but the problems are
the same. Compositors don't draw at all or incorrectly to anything on
another XScreen or GPU which brings me to your disable the old GPU
comment. The point is to use the hardware, not lose it. I've found a ton
of problems in things moving forward and am looking for a solution
rather than "Hey just throw one GPU and all it's screens in the trash
because somethings broken in software." Ultimately this issue affects
modern dual GPU systems as well as matched brand cards. Things work in
18.04, everything breaks moving to 20.04/21.04.

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

Title:
  XOrg / nouveau - hard lockups and does not draw to screen

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-ati package in Ubuntu:
  New
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  Changing display settings hard locks the machine (no reisub save).
  Installing nouveau-firmware allows changes to be made without hard
  lock ups but the screen using nouveau draws the mouse cursor and will
  launch apps on it but does not draw anything on screen. Dmesg is
  flooded with nouveau and XOrg failure messages.

  Description:  Ubuntu 21.04
  Release:  21.04

  xorg:
Installed: 1:7.7+22ubuntu1
Candidate: 1:7.7+22ubuntu1
Version table:
   *** 1:7.7+22ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  nouveau-firmware:
Installed: 20091212-0ubuntu1
Candidate: 20091212-0ubuntu1
Version table:
   *** 20091212-0ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu hirsute/multiverse amd64 
Packages
  500 http://ca.archive.ubuntu.com/ubuntu hirsute/multiverse i386 
Packages
  100 /var/lib/dpkg/status

  
  xserver-xorg-video-nouveau:
Installed: 1:1.0.17-1
Candidate: 1:1.0.17-1
Version table:
   *** 1:1.0.17-1 500
  500 http://ca.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  Uname: Linux 5.11.0-31-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: XFCE
  Date: Sun Sep  5 23:52:43 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6100 nForce 405] [10de:03d1] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Elitegroup Computer Systems C61 [GeForce 6100 nForce 405] 
[1019:2601]
   Advanced Micro Devices, Inc. [AMD/ATI] Oland XT [Radeon HD 8670 / R7 
250/350] [1002:6610] (prog-if 00 [VGA controller])
 Subsystem: Diamond Multimedia Systems Oland XT [Radeon HD 8670 / R7 
250/350] [1092:0250]
  InstallationDate: Installed on 2021-04-07 (151 days ago)
  InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 04d9:a0cd Holtek Semiconductor, Inc. USB Keyboard
   Bus 002 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Acer ASE380/AST180/APM8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-31-generic 
root=UUID=cf6234fa-9047-4e3a-8931-f8f36bce86cf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/29/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: R01-B1
  dmi.board.name: EM61SM/EM61PM
  dmi.board.vendor: Acer
  dmi.chassis.asset.tag: Asset tag number: at least 22 digits
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrR01-B1:bd12/29/2006:svnAcer:pnASE380/AST180/APM8:pvrR01-B1:rvnAcer:rnEM61SM/EM61PM:rvr:cvn:ct3:cvr:
  dmi.product.name: ASE380/AST180/APM8
  dmi.product.version: R01-B1
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2

[Kernel-packages] [Bug 1942738] Status changed to Confirmed

2021-09-06 Thread Ubuntu Kernel Bot

This change was made by a bot.

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

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

Title:
  XOrg / nouveau - hard lockups and does not draw to screen

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-ati package in Ubuntu:
  New
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  Changing display settings hard locks the machine (no reisub save).
  Installing nouveau-firmware allows changes to be made without hard
  lock ups but the screen using nouveau draws the mouse cursor and will
  launch apps on it but does not draw anything on screen. Dmesg is
  flooded with nouveau and XOrg failure messages.

  Description:  Ubuntu 21.04
  Release:  21.04

  xorg:
Installed: 1:7.7+22ubuntu1
Candidate: 1:7.7+22ubuntu1
Version table:
   *** 1:7.7+22ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  nouveau-firmware:
Installed: 20091212-0ubuntu1
Candidate: 20091212-0ubuntu1
Version table:
   *** 20091212-0ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu hirsute/multiverse amd64 
Packages
  500 http://ca.archive.ubuntu.com/ubuntu hirsute/multiverse i386 
Packages
  100 /var/lib/dpkg/status

  
  xserver-xorg-video-nouveau:
Installed: 1:1.0.17-1
Candidate: 1:1.0.17-1
Version table:
   *** 1:1.0.17-1 500
  500 http://ca.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  Uname: Linux 5.11.0-31-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: XFCE
  Date: Sun Sep  5 23:52:43 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6100 nForce 405] [10de:03d1] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Elitegroup Computer Systems C61 [GeForce 6100 nForce 405] 
[1019:2601]
   Advanced Micro Devices, Inc. [AMD/ATI] Oland XT [Radeon HD 8670 / R7 
250/350] [1002:6610] (prog-if 00 [VGA controller])
 Subsystem: Diamond Multimedia Systems Oland XT [Radeon HD 8670 / R7 
250/350] [1092:0250]
  InstallationDate: Installed on 2021-04-07 (151 days ago)
  InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 04d9:a0cd Holtek Semiconductor, Inc. USB Keyboard
   Bus 002 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Acer ASE380/AST180/APM8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-31-generic 
root=UUID=cf6234fa-9047-4e3a-8931-f8f36bce86cf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/29/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: R01-B1
  dmi.board.name: EM61SM/EM61PM
  dmi.board.vendor: Acer
  dmi.chassis.asset.tag: Asset tag number: at least 22 digits
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrR01-B1:bd12/29/2006:svnAcer:pnASE380/AST180/APM8:pvrR01-B1:rvnAcer:rnEM61SM/EM61PM:rvr:cvn:ct3:cvr:
  dmi.product.name: ASE380/AST180/APM8
  dmi.product.version: R01-B1
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3
  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/1942738/+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 1942738] Re: XOrg / nouveau - hard lockups and does not draw to screen

Thanks for the bug report.

You seem to be using the old (not recommended) Xorg graphics drivers
called 'nouveau' and 'radeon'. They have been replaced by the newer
driver 'modesetting'. So if you are writing a Xorg config file be sure
to use the latter.

Please also note the nouveau kernel driver is often unreliable.
Unfortunately your Nvidia GPU appears to be a little too old to be
supported by the official proprietary Nvidia drivers so you don't have
much choice. If you can disable the Nvidia GPU in your BIOS and use the
Radeon instead then you might have more luck.

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

Title:
  XOrg / nouveau - hard lockups and does not draw to screen

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-ati package in Ubuntu:
  New
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  Changing display settings hard locks the machine (no reisub save).
  Installing nouveau-firmware allows changes to be made without hard
  lock ups but the screen using nouveau draws the mouse cursor and will
  launch apps on it but does not draw anything on screen. Dmesg is
  flooded with nouveau and XOrg failure messages.

  Description:  Ubuntu 21.04
  Release:  21.04

  xorg:
Installed: 1:7.7+22ubuntu1
Candidate: 1:7.7+22ubuntu1
Version table:
   *** 1:7.7+22ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  nouveau-firmware:
Installed: 20091212-0ubuntu1
Candidate: 20091212-0ubuntu1
Version table:
   *** 20091212-0ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu hirsute/multiverse amd64 
Packages
  500 http://ca.archive.ubuntu.com/ubuntu hirsute/multiverse i386 
Packages
  100 /var/lib/dpkg/status

  
  xserver-xorg-video-nouveau:
Installed: 1:1.0.17-1
Candidate: 1:1.0.17-1
Version table:
   *** 1:1.0.17-1 500
  500 http://ca.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  Uname: Linux 5.11.0-31-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: XFCE
  Date: Sun Sep  5 23:52:43 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6100 nForce 405] [10de:03d1] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Elitegroup Computer Systems C61 [GeForce 6100 nForce 405] 
[1019:2601]
   Advanced Micro Devices, Inc. [AMD/ATI] Oland XT [Radeon HD 8670 / R7 
250/350] [1002:6610] (prog-if 00 [VGA controller])
 Subsystem: Diamond Multimedia Systems Oland XT [Radeon HD 8670 / R7 
250/350] [1092:0250]
  InstallationDate: Installed on 2021-04-07 (151 days ago)
  InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 04d9:a0cd Holtek Semiconductor, Inc. USB Keyboard
   Bus 002 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Acer ASE380/AST180/APM8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-31-generic 
root=UUID=cf6234fa-9047-4e3a-8931-f8f36bce86cf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/29/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: R01-B1
  dmi.board.name: EM61SM/EM61PM
  dmi.board.vendor: Acer
  dmi.chassis.asset.tag: Asset tag number: at least 22 digits
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrR01-B1:bd12/29/2006:svnAcer:pnASE380/AST180/APM8:pvrR01-B1:rvnAcer:rnEM61SM/EM61PM:rvr:cvn:ct3:cvr:
  dmi.product.name: ASE380/AST180/APM8
  dmi.product.version: R01-B1
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3
  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:

[Kernel-packages] [Bug 1942738] Re: XOrg / nouveau - hard lockups and does not draw to screen