[Kernel-packages] [Bug 2015467] [NEW] [Dell Storage Ubuntu22.04 BUG] Segfault in libnvme during garbage collection

[Sheik Ajith Ali Mohammed Farook]

Private bug reported:


Facing segmentation fault with libnvme  if objects don’t get deleted in the 
right order.  

Repro steps:
Execute the attached script file.

Following fix is required to address issue:
https://github.com/linux-nvme/libnvme/pull/583

Would like to know the upstream release with this fix.

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

** Attachment added: "Script to reproduce the issue"
   
https://bugs.launchpad.net/bugs/2015467/+attachment/5661574/+files/nvme_conn.py

** Information type changed from Public to Private

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

Title:
  [Dell Storage Ubuntu22.04 BUG] Segfault in libnvme during garbage
  collection

Status in linux package in Ubuntu:
  New

Bug description:
  
  Facing segmentation fault with libnvme  if objects don’t get deleted in the 
right order.  

  Repro steps:
  Execute the attached script file.

  Following fix is required to address issue:
  https://github.com/linux-nvme/libnvme/pull/583

  Would like to know the upstream release with this fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015467/+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 1208993] Re: Ubuntu slows down and hangs while copying file from/to USB

[Ali-Hashemi]

ubuntu 22.04 and 1TB hdd with a considerably fine hardware status.
problem still remains, matter of fact i just lost a whole bunch of data because 
after screen froze i just unplugged the usb and then i had to re-create the 
ntfs volume from scratch (gparted) to be able to mount it again.

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

Title:
  Ubuntu slows down and hangs while copying file from/to USB

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi

  While copying many and large files to and from a USB drive, the system
  becomes incredibly slow and sometimes hangs. I watched the system
  monitor while it was running slowly but cpu was not above 50% at any
  time, the same for memory.

  I'm using the "WD my passport" HD with a USB3 port of my "ASUS K55VD"
  laptop.

  Description:  Ubuntu 13.04
  Release:  13.04

  nautilus:
Installed: 1:3.6.3-0ubuntu16
Candidate: 1:3.6.3-0ubuntu16
Version table:
   *** 1:3.6.3-0ubuntu16 0
  500 http://ubuntu-archive.mirror.nucleus.be/ raring/main amd64 
Packages
  100 /var/lib/dpkg/status

  
  Steps to reproduce:
  1) Aquire many large files (like your totally legit moviecollection)
  2) Copy files to external HD
  3) Open your browser and be sad when your system becomes incredibly slow 
after a few minutes


  This is my first bugreport so if I'm missing something, please tell
  me.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  Date: Tue Aug  6 22:56:34 2013
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'656x715+154+151'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2013-05-31 (67 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208993/+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 2003718] [NEW] [Ubuntu 22.04] Duplicate link for NVMe device by-id

[Sheik Ajith Ali Mohammed Farook]

Private bug reported:

[Impact]

Users may choose wrong link and would not be able to work with it.

[Test Plan]

Connect to NVMe/TCP subsystem using nvme connect-all. This was tested
against Dell PowerStore, PowerFlex and PowerMax

Steps to Reproduce:
1. Use nvme connect-all to connect to an NVMe/TCP subsystems
2. Check /dev/disc/by-id

[Original report]

Description:
When working with NVMe/TCP host functionality, connecting to NVMe subsystem 
through multiple controllers can lead to an invalid device link created in 
/dev/disc/by-id/ being created.

Steps to reproduce:
Step 1: Install Ubuntu 22.04 LTS (ubuntu-22.04.1-live-server-amd64) on system.
Step 2: Install nvme-cli package, currently installed version is nvme version 
1.16
Step 3: In the os terminal, type any nvme connect-all to connect to NVMe 
subsystems and check the duplicate entries in /dev/disk/by-id/.

Expected Behavior:
No duplicate entries of NVMe subsystems should exist.

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

** Information type changed from Public to Private

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

Title:
  [Ubuntu 22.04] Duplicate link for NVMe device by-id

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]

  Users may choose wrong link and would not be able to work with it.

  [Test Plan]

  Connect to NVMe/TCP subsystem using nvme connect-all. This was tested
  against Dell PowerStore, PowerFlex and PowerMax

  Steps to Reproduce:
  1. Use nvme connect-all to connect to an NVMe/TCP subsystems
  2. Check /dev/disc/by-id

  [Original report]

  Description:
  When working with NVMe/TCP host functionality, connecting to NVMe subsystem 
through multiple controllers can lead to an invalid device link created in 
/dev/disc/by-id/ being created.

  Steps to reproduce:
  Step 1: Install Ubuntu 22.04 LTS (ubuntu-22.04.1-live-server-amd64) on system.
  Step 2: Install nvme-cli package, currently installed version is nvme version 
1.16
  Step 3: In the os terminal, type any nvme connect-all to connect to NVMe 
subsystems and check the duplicate entries in /dev/disk/by-id/.

  Expected Behavior:
  No duplicate entries of NVMe subsystems should exist.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003718/+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 2001721] Re: [amdgpu] Ubuntu screen green flickering

[ali]

i did removed the HDMI and the Hard-Drive, "no boot drive" also same
problem.

** Attachment added: "20230107_210923.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2001721/+attachment/5639925/+files/20230107_210923.jpg

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

Title:
  [amdgpu] Ubuntu screen green flickering

Status in linux package in Ubuntu:
  New

Bug description:
  Hi

  i did use ubuntu for more than a year on this laptop 
  last a few days i used HDMI cable, today for a few hours i did use a new 
cable "longer one"
  now suddenly my laptop display went green as you can see in the attachment   

  i did some search but can't find solution.

  
  
https://askubuntu.com/questions/1231441/ubuntu-screen-flickering/1250859#1250859
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1883534

  Ali

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  4 22:41:41 2023
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev e2) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Stoney [Radeon R2/R3/R4/R5 Graphics] [17aa:3f1a]
  InstallationDate: Installed on 2021-12-20 (380 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: LENOVO 81N3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=52450c12-da25-47db-984c-a2036e93aff5 ro reboot=pci quiet splash 
acpi=force vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2019
  dmi.bios.release: 1.20
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AYCN20WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S145-15AST
  dmi.ec.firmware.release: 1.20
  dmi.modalias: 
dmi:bvnLENOVO:bvrAYCN20WW:bd11/27/2019:br1.20:efr1.20:svnLENOVO:pn81N3:pvrLenovoIdeaPadS145-15AST:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15AST:skuLENOVO_MT_81N3_BU_idea_FM_IdeaPadS145-15AST:
  dmi.product.family: IdeaPad S145-15AST
  dmi.product.name: 81N3
  dmi.product.sku: LENOVO_MT_81N3_BU_idea_FM_IdeaPad S145-15AST
  dmi.product.version: Lenovo IdeaPad S145-15AST
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2001721/+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 2001721] Re: [amdgpu] Ubuntu screen green flickering

[ali]

i did try run Ubuntu 22.04 from USB, same problem

** Attachment added: "20230107_193248.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2001721/+attachment/5639924/+files/20230107_193248.jpg

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

Title:
  [amdgpu] Ubuntu screen green flickering

Status in linux package in Ubuntu:
  New

Bug description:
  Hi

  i did use ubuntu for more than a year on this laptop 
  last a few days i used HDMI cable, today for a few hours i did use a new 
cable "longer one"
  now suddenly my laptop display went green as you can see in the attachment   

  i did some search but can't find solution.

  
  
https://askubuntu.com/questions/1231441/ubuntu-screen-flickering/1250859#1250859
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1883534

  Ali

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  4 22:41:41 2023
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev e2) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Stoney [Radeon R2/R3/R4/R5 Graphics] [17aa:3f1a]
  InstallationDate: Installed on 2021-12-20 (380 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: LENOVO 81N3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=52450c12-da25-47db-984c-a2036e93aff5 ro reboot=pci quiet splash 
acpi=force vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2019
  dmi.bios.release: 1.20
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AYCN20WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S145-15AST
  dmi.ec.firmware.release: 1.20
  dmi.modalias: 
dmi:bvnLENOVO:bvrAYCN20WW:bd11/27/2019:br1.20:efr1.20:svnLENOVO:pn81N3:pvrLenovoIdeaPadS145-15AST:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15AST:skuLENOVO_MT_81N3_BU_idea_FM_IdeaPadS145-15AST:
  dmi.product.family: IdeaPad S145-15AST
  dmi.product.name: 81N3
  dmi.product.sku: LENOVO_MT_81N3_BU_idea_FM_IdeaPad S145-15AST
  dmi.product.version: Lenovo IdeaPad S145-15AST
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2001721/+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 2001721] Re: [amdgpu] Ubuntu screen green flickering

[ali]

Thanks for helping me out.

it's the same issue.

The HDMI is out of the problem.

now i am working on https://ubuntu.com/tutorials/install-ubuntu-
desktop#3-create-a-bootable-usb-stick

see the attachment the problem is in the boot screen too.

** Attachment added: "20230107_160252.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2001721/+attachment/5639897/+files/20230107_160252.jpg

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

Title:
  [amdgpu] Ubuntu screen green flickering

Status in linux package in Ubuntu:
  New

Bug description:
  Hi

  i did use ubuntu for more than a year on this laptop 
  last a few days i used HDMI cable, today for a few hours i did use a new 
cable "longer one"
  now suddenly my laptop display went green as you can see in the attachment   

  i did some search but can't find solution.

  
  
https://askubuntu.com/questions/1231441/ubuntu-screen-flickering/1250859#1250859
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1883534

  Ali

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  4 22:41:41 2023
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev e2) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Stoney [Radeon R2/R3/R4/R5 Graphics] [17aa:3f1a]
  InstallationDate: Installed on 2021-12-20 (380 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: LENOVO 81N3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=52450c12-da25-47db-984c-a2036e93aff5 ro reboot=pci quiet splash 
acpi=force vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2019
  dmi.bios.release: 1.20
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AYCN20WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S145-15AST
  dmi.ec.firmware.release: 1.20
  dmi.modalias: 
dmi:bvnLENOVO:bvrAYCN20WW:bd11/27/2019:br1.20:efr1.20:svnLENOVO:pn81N3:pvrLenovoIdeaPadS145-15AST:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15AST:skuLENOVO_MT_81N3_BU_idea_FM_IdeaPadS145-15AST:
  dmi.product.family: IdeaPad S145-15AST
  dmi.product.name: 81N3
  dmi.product.sku: LENOVO_MT_81N3_BU_idea_FM_IdeaPad S145-15AST
  dmi.product.version: Lenovo IdeaPad S145-15AST
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2001721/+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 1999629] Re: xorg-core package does not provide xorg-video-abi under kinetic(22.10), which breaks Nvidia CUDA for graphics cards with graphics drivers version 510 and below

[ali pourjamal]

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Confirmed

** Summary changed:

- xorg-core package does not provide xorg-video-abi under kinetic(22.10), which 
breaks Nvidia CUDA for graphics cards with graphics drivers version 510 and 
below
+ xorg-core package does not provide xorg-video-abi version 24 ( it is version 
25) under kinetic(22.10), which breaks Nvidia CUDA for graphics cards with 
graphics drivers version 510 and below

** Summary changed:

- xorg-core package does not provide xorg-video-abi version 24 ( it is version 
25) under kinetic(22.10), which breaks Nvidia CUDA for graphics cards with 
graphics drivers version 510 and below
+ xorg-core package does not provide xorg-video-abi version 24 ( it is version 
25) under ubuntu 22 and later, makes it impossible to install cuda 10.2 or older

** Description changed:

  Description:  Ubuntu 22.10
  Release:  22.10
  
  xserver-xorg-core:
-   Installed: 2:21.1.4-2ubuntu1
-   Candidate: 2:21.1.4-2ubuntu1
-   Version table:
-  *** 2:21.1.4-2ubuntu1 500
- 500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 2:21.1.4-2ubuntu1
+   Candidate: 2:21.1.4-2ubuntu1
+   Version table:
+  *** 2:21.1.4-2ubuntu1 500
+ 500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
+ 100 /var/lib/dpkg/status
+ 
+ Under Ubuntu 22, I was trying to make NVIDIA CUDA work, but I can't
+ because the only compatible mix of CUDA and drivers results in a virtual
+ dependency problem.
+ 
+ apparently the problem is the lack the xorg-video-abi-24 in the xserver-
+ xorg-core package
+ 
+ as the grep command shows, only the video-abi-25 is provided in ubuntu
+ 22 , but in order to install cuda 10.2 (or older), the version 24 is
+ needed.
+ 
+ $ apt-cache show xserver-xorg-core | grep -E '(Package|Version|Provides)'
+ Package: xserver-xorg-core
+ Version: 2:21.1.3-2ubuntu2.5
+ Provides: xorg-input-abi-24, xorg-video-abi-25, xserver-xorg-video-modesetting
+ Package: xserver-xorg-core
+ Version: 2:21.1.3-2ubuntu2
+ Provides: xorg-input-abi-24, xorg-video-abi-25, xserver-xorg-video-modesetting
  
  
- Under Ubuntu 22, I was trying to make NVIDIA CUDA work, but I can't because 
the only compatible mix of CUDA and drivers results in a virtual dependency 
problem.
+ installing cuda 10.2 or older will give you this error:
  
- The latest version of the nividia-drivers on my system is 510,for all
- packages newer than this the persistence daemon fails.  No problem I
- suppose, I'll just install 510 and cuda-drivers-510.
+  xserver-xorg-video-nvidia-510 : Depends: xorg-video-abi-24 but it is not 
installable or
+   xorg-video-abi-23 but it is not 
installable or
+   xorg-video-abi-20 but it is not 
installable or
+   xorg-video-abi-19 but it is not 
installable or
+   xorg-video-abi-18 but it is not 
installable or
+   xorg-video-abi-15 but it is not 
installable or
+   xorg-video-abi-14 but it is not 
installable or
+   xorg-video-abi-13 but it is not 
installable or
+   xorg-video-abi-12 but it is not 
installable or
+   xorg-video-abi-11 but it is not 
installable or
+   xorg-video-abi-10 but it is not 
installable or
+   xorg-video-abi-8 but it is not 
installable or
+   xorg-video-abi-6.0 but it is not 
installable
  
- Only that doesn't work, because apparently though this package is
- installed it doesn't rprovide any of the xorg-video-abi virtual packages
- like it did in prior versions.
- 
- sudo apt-get install cuda-drivers-510 
- Reading package lists... Done
- Building dependency tree... Done
- Reading state information... Done
- Some packages could not be installed. This may mean that you have
- requested an impossible situation or if you are using the unstable
- distribution that some required packages have not yet been created
- or been moved out of Incoming.
- The following information may help resolve the situation:
- 
- The following packages have unmet dependencies:
-  xserver-xorg-video-nvidia-510 : Depends: xorg-video-abi-24 but it is not 
installable or
-   xorg-video-abi-23 but it is not 
installable or
-   xorg-video-abi-20 but it is not 
installable or
-   xorg-video-abi-19 but it is not 
installable or
-   xorg-video-abi-18 but it is not 
installable or
-   xorg-video-abi-15 but it 

[Kernel-packages] [Bug 1999629] Re: xorg-core package does not provide xorg-video-abi under kinetic(22.10), which breaks Nvidia CUDA for graphics cards with graphics drivers version 510 and below

[ali pourjamal]

apparently the problem is the lack the xorg-video-abi-24 in the 
xserver-xorg-core package as it was pointed out
as the grep command shows, only the video-abi-25 is provided in ubuntu 22 , but 
in order to install cuda 10.2 (or older), the version 24 is needed. 

$ apt-cache show xserver-xorg-core | grep -E '(Package|Version|Provides)'
Package: xserver-xorg-core
Version: 2:21.1.3-2ubuntu2.5
Provides: xorg-input-abi-24, xorg-video-abi-25, xserver-xorg-video-modesetting
Package: xserver-xorg-core
Version: 2:21.1.3-2ubuntu2
Provides: xorg-input-abi-24, xorg-video-abi-25, xserver-xorg-video-modesetting

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

Title:
  xorg-core package does not provide xorg-video-abi under
  kinetic(22.10), which breaks Nvidia CUDA for graphics cards with
  graphics drivers version 510 and below

Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510-server package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 22.10
  Release:  22.10

  xserver-xorg-core:
Installed: 2:21.1.4-2ubuntu1
Candidate: 2:21.1.4-2ubuntu1
Version table:
   *** 2:21.1.4-2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Under Ubuntu 22, I was trying to make NVIDIA CUDA work, but I can't because 
the only compatible mix of CUDA and drivers results in a virtual dependency 
problem.

  The latest version of the nividia-drivers on my system is 510,for all
  packages newer than this the persistence daemon fails.  No problem I
  suppose, I'll just install 510 and cuda-drivers-510.

  Only that doesn't work, because apparently though this package is
  installed it doesn't rprovide any of the xorg-video-abi virtual
  packages like it did in prior versions.

  sudo apt-get install cuda-drivers-510 
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help resolve the situation:

  The following packages have unmet dependencies:
   xserver-xorg-video-nvidia-510 : Depends: xorg-video-abi-24 but it is not 
installable or
xorg-video-abi-23 but it is not 
installable or
xorg-video-abi-20 but it is not 
installable or
xorg-video-abi-19 but it is not 
installable or
xorg-video-abi-18 but it is not 
installable or
xorg-video-abi-15 but it is not 
installable or
xorg-video-abi-14 but it is not 
installable or
xorg-video-abi-13 but it is not 
installable or
xorg-video-abi-12 but it is not 
installable or
xorg-video-abi-11 but it is not 
installable or
xorg-video-abi-10 but it is not 
installable or
xorg-video-abi-8 but it is not 
installable or
xorg-video-abi-6.0 but it is not 
installable
  E: Unable to correct problems, you have held broken packages.

  
  According to my research this package is the provider in focal 
  https://packages.ubuntu.com/focal/xorg-video-abi-24

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1999629/+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 1999629] Re: xorg-core package does not provide xorg-video-abi under kinetic(22.10), which breaks Nvidia CUDA for graphics cards with graphics drivers version 510 and below

[ali pourjamal]

i can confirm this bug exists on 22.04.1 too,

$ apt-cache show xserver-xorg-core | grep -E '(Package|Version|Provides)'
Package: xserver-xorg-core
Version: 2:21.1.3-2ubuntu2.5
Provides: xorg-input-abi-24, xorg-video-abi-25, xserver-xorg-video-modesetting
Package: xserver-xorg-core
Version: 2:21.1.3-2ubuntu2
Provides: xorg-input-abi-24, xorg-video-abi-25, xserver-xorg-video-modesetting

this shows that the abi-24 provider exists, but upon installing cuda
10.2 (the latest version which supports my gpu) the error below comes
up.

The following packages have unmet dependencies:
 xserver-xorg-video-nvidia-440 : Depends: xorg-video-abi-24 but it is not 
installable or
  xorg-video-abi-23 but it is not 
installable or
  xorg-video-abi-20 but it is not 
installable or
  xorg-video-abi-19 but it is not 
installable or
  xorg-video-abi-18 but it is not 
installable or
  xorg-video-abi-15 but it is not 
installable or
  xorg-video-abi-14 but it is not 
installable or
  xorg-video-abi-13 but it is not 
installable or
  xorg-video-abi-12 but it is not 
installable or
  xorg-video-abi-11 but it is not 
installable or
  xorg-video-abi-10 but it is not 
installable or
  xorg-video-abi-8 but it is not 
installable or
  xorg-video-abi-6.0 but it is not 
installable
i'm downgrading to 20.04 for now.

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

Title:
  xorg-core package does not provide xorg-video-abi under
  kinetic(22.10), which breaks Nvidia CUDA for graphics cards with
  graphics drivers version 510 and below

Status in nvidia-graphics-drivers-510 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-510-server package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 22.10
  Release:  22.10

  xserver-xorg-core:
Installed: 2:21.1.4-2ubuntu1
Candidate: 2:21.1.4-2ubuntu1
Version table:
   *** 2:21.1.4-2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Under Ubuntu 22, I was trying to make NVIDIA CUDA work, but I can't because 
the only compatible mix of CUDA and drivers results in a virtual dependency 
problem.

  The latest version of the nividia-drivers on my system is 510,for all
  packages newer than this the persistence daemon fails.  No problem I
  suppose, I'll just install 510 and cuda-drivers-510.

  Only that doesn't work, because apparently though this package is
  installed it doesn't rprovide any of the xorg-video-abi virtual
  packages like it did in prior versions.

  sudo apt-get install cuda-drivers-510 
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help resolve the situation:

  The following packages have unmet dependencies:
   xserver-xorg-video-nvidia-510 : Depends: xorg-video-abi-24 but it is not 
installable or
xorg-video-abi-23 but it is not 
installable or
xorg-video-abi-20 but it is not 
installable or
xorg-video-abi-19 but it is not 
installable or
xorg-video-abi-18 but it is not 
installable or
xorg-video-abi-15 but it is not 
installable or
xorg-video-abi-14 but it is not 
installable or
xorg-video-abi-13 but it is not 
installable or
xorg-video-abi-12 but it is not 
installable or
xorg-video-abi-11 but it is not 
installable or
xorg-video-abi-10 but it is not 
installable or
xorg-video-abi-8 but it is not 
installable or
xorg-video-abi-6.0 but it is not 
installable
  E: Unable to correct problems, you have held broken packages.

  
  According to my research this package is 

[Kernel-packages] [Bug 1999629] Re: xorg-core package does not provide xorg-video-abi under kinetic(22.10), which breaks Nvidia CUDA for graphics cards with graphics drivers version 510 and below

[ali pourjamal]

i can confirm this bug exists on 22.04.1 too,

$ apt-cache show xserver-xorg-core | grep -E '(Package|Version|Provides)'
Package: xserver-xorg-core
Version: 2:21.1.3-2ubuntu2.5
Provides: xorg-input-abi-24, xorg-video-abi-25, xserver-xorg-video-modesetting
Package: xserver-xorg-core
Version: 2:21.1.3-2ubuntu2
Provides: xorg-input-abi-24, xorg-video-abi-25, xserver-xorg-video-modesetting

this shows that the abi-24 provider exists, but upon installing cuda
10.2 (the latest version which supports my gpu) the error below comes
up.

The following packages have unmet dependencies:
 xserver-xorg-video-nvidia-440 : Depends: xorg-video-abi-24 but it is not 
installable or
  xorg-video-abi-23 but it is not 
installable or
  xorg-video-abi-20 but it is not 
installable or
  xorg-video-abi-19 but it is not 
installable or
  xorg-video-abi-18 but it is not 
installable or
  xorg-video-abi-15 but it is not 
installable or
  xorg-video-abi-14 but it is not 
installable or
  xorg-video-abi-13 but it is not 
installable or
  xorg-video-abi-12 but it is not 
installable or
  xorg-video-abi-11 but it is not 
installable or
  xorg-video-abi-10 but it is not 
installable or
  xorg-video-abi-8 but it is not 
installable or
  xorg-video-abi-6.0 but it is not 
installable
i'm downgrading to 20.04 for now.

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

Title:
  xorg-core package does not provide xorg-video-abi under
  kinetic(22.10), which breaks Nvidia CUDA for graphics cards with
  graphics drivers version 510 and below

Status in nvidia-graphics-drivers-510 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-510-server package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 22.10
  Release:  22.10

  xserver-xorg-core:
Installed: 2:21.1.4-2ubuntu1
Candidate: 2:21.1.4-2ubuntu1
Version table:
   *** 2:21.1.4-2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Under Ubuntu 22, I was trying to make NVIDIA CUDA work, but I can't because 
the only compatible mix of CUDA and drivers results in a virtual dependency 
problem.

  The latest version of the nividia-drivers on my system is 510,for all
  packages newer than this the persistence daemon fails.  No problem I
  suppose, I'll just install 510 and cuda-drivers-510.

  Only that doesn't work, because apparently though this package is
  installed it doesn't rprovide any of the xorg-video-abi virtual
  packages like it did in prior versions.

  sudo apt-get install cuda-drivers-510 
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help resolve the situation:

  The following packages have unmet dependencies:
   xserver-xorg-video-nvidia-510 : Depends: xorg-video-abi-24 but it is not 
installable or
xorg-video-abi-23 but it is not 
installable or
xorg-video-abi-20 but it is not 
installable or
xorg-video-abi-19 but it is not 
installable or
xorg-video-abi-18 but it is not 
installable or
xorg-video-abi-15 but it is not 
installable or
xorg-video-abi-14 but it is not 
installable or
xorg-video-abi-13 but it is not 
installable or
xorg-video-abi-12 but it is not 
installable or
xorg-video-abi-11 but it is not 
installable or
xorg-video-abi-10 but it is not 
installable or
xorg-video-abi-8 but it is not 
installable or
xorg-video-abi-6.0 but it is not 
installable
  E: Unable to correct problems, you have held broken packages.

  
  According to my research this package is 

[Kernel-packages] [Bug 1948626] Re: [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010

[Sheik Ajith Ali Mohammed Farook]

Hi Michael,

Could you please provide the latest nvme-stas 2.0 deb package to test
NVMe-oF-TCP CDC Client support with Ubuntu 22.04 Jammy?

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

Title:
  [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC
  Client  - TP 8010

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  NVMe-oF suffers from a well-known discovery problem that fundamentally limits 
the size of realistic deployments. To address this discovery problem, the FMDS 
working group (within nvme.org) is working on two proposals that will allow 
NVMe-oF to be managed via a “network centric” provisioning process instead of 
an “end-node centric” one.
  TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will 
enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP 
Network and will prevent an end-user from needing to manually configure the IP 
Address of Discovery Controllers.
  TP-8010 (this launchpad): will define the concept of a Centralized Discovery 
Controller (CDC) and will allow end-users to manage connectivity from a single 
point of management on an IP Fabric by IP Fabric basis.

  Here is code that implements TP8009 and TP8010:
  https://github.com/martin-belanger/nvme-stas/ which now got pulled into 
upstream - https://github.com/linux-nvme/nvme-stas

  [Fix]
  1. Update kernel with TP8010 kernel patches:

  a.
  
https://git.infradead.org/git/nvme.git/commit/647b2e01fb2d3394090ed11d1b5238157c52f907

  b.
  
https://git.infradead.org/git/nvme.git/commit/de87c02ea9b4d93d1114b912b621ead81f6738e0

  c.
   nvme: add CNTRLTYPE definitions for 'identify controller
  https://lore.kernel.org/all/66fc4f03-ed5c-4727-ba94-c23daf7d6...@oracle.com/

  [Test Case]
   1.  Compile libnvme and nvme-stas packages from github using the kernel 
   with these patches.  

   2.  Test libnvme and nvme-stas packages

  [Where problems could occur]
  Regression risk for these patches are low

  [Other Info]
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/nvme_tcp_patches_2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948626/+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 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

[ali nourzad]

can this be a solution ?
https://stackoverflow.com/questions/2895816/how-do-i-strip-local-
symbols-from-linux-kernel-module-without-breaking-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/1842320

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Triaged
Status in grub2-unsigned package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
   #endif
  ```

  If everything works as expected, then i386 should working good.

  If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
  4GB memory region and never be able to access.

  [Other Info]

   * Upstream grub2 bug #61058
  https://savannah.gnu.org/bugs/index.php?61058

   * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320

   * Test grubx64.efi:
  https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320

   * Test source code: https://github.com/os369510/grub2/tree/lp1842320

   * If you built the package, then test grubx64.efi is under
  

[Kernel-packages] [Bug 1991725] Re: fails to sign kernel modules

[Hesham Mohamed Khalil Youssif Ali]

I've done similar steps to install nvidia drivers on ubuntu 22.10 with
secure boot enabled but i didn't face mokutil

steps to reproduce

1-during installation i didn't install third party drivers

2-i updated the system then restart

3-i enabled the proposed repo and installed the updated "dkms" package
(sudo apt install dkms)

4- disabled proposed repo and reboot

5-I installed the nvidia driver with gui (proprietary ,tested) and
rebooted the system successfully and ubuntu. the nvidia driver is
working

the problem is i didn't encounter mokutil during and after the
installation of nvidia driver . (like creating password then after the
reboot i enroll mok)

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

Title:
  fails to sign kernel modules

Status in Release Notes for Ubuntu:
  Fix Released
Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  With the current state of the DKMS package, if a user attempts to
  install any package that includes a third-party driver (Broadcom WiFi,
  VirtualBox, v4l2loobpack, etc.), the process of signing the newly
  built driver with a MOK key will fail silently. This means that any
  packages and hardware that require third-party drivers are currently
  unusable on a system with Secure Boot. This bug has been tested and
  verified to occur with the bcmwl-kernel-source package, but also is
  very likely to affect any other packages that use DKMS modules.

  This fix for this is in the -proposed pocket at the moment, and has
  been tested to work.

  [Test plan]

  1: Obtain a system with UEFI, Secure Boot, and Broadcom WiFi. (If Broadcom 
WiFi is not an option, install VirtualBox in Step 9 rather than 
bcmwl-kernel-source.)
  2. Install Ubuntu on the system, but do not enable the installation of 
third-party drivers.
  3. When installation finishes, reboot.
  4. When the system boots into the Ubuntu desktop, connect to the Internet 
without WiFi, and update all packages on the system.
  5. Enable -proposed.
  6. Update *just* the DKMS package with "sudo apt install dkms".
  7. Disable -proposed.
  8. Run "sudo apt install bcmwl-kernel-source".
  9. Reboot and enroll the MOK, then reboot again. The WiFi adapter should 
begin working once Ubuntu boots.

  [Where problems could occur]

  Theoretically, a bug in the code could result in DKMS drivers still
  not being signed in some instances (though there are no known
  instances where this happens). But as Secure Boot + DKMS is already
  entirely broken, even this kind of breakage would be an improvement
  beyond what we already have. Given the rather obvious nature of such
  breakage, thorough testing should be able to detect it with ease.

  ---

  Original bug reports:

  Expected on kinetic:  dkms will sign built modules with MOK key if
  requested.

  What happens:
  dkms outputs "Binary kmod-sign not found, modules won't be signed"

  Fix:
  update dkms to 3.0.7:  https://github.com/dell/dkms/pull/242

  ---

  dkms 3.0.6-2ubuntu2 is being tested in kinetic-proposed to resolve
  this issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1991725/+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 1983656] Re: iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500

[Arif Ali]

tested kernel linux/5.15.0-53.59 on both jammy and focal

* Create 2 jammy instances
* Add SRIOV interface with vlan tag
* Configure interface with mtu 9000, and errors in dmesg
* Enabled proposed and installing the linux-image-generic package
* reboot both instances
* network with MTU up via netplan
* We can ping between instances

Followed the same steps for linux-image-generic-hwe-20.04 for the 2
focal nodes in comment #16, and have verified that this works as
expected

** Tags added: verification-done-jammy

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

Title:
  iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed

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

  [Impact]

  Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b]
  get no traffic flow and produce error messages in both the host and
  guest during network configuration.

  Environment: Ubuntu OpenStack Focal-Ussuri with OVN
  Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE
  Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy

  Host Error Messages:
  ice :98:00.1: VF 7 failed opcode 6, retval: -5

  Guest Error Messages:
  iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6

  In the context of these errors "6" refers to the value of
  VIRTCHNL_OP_CONFIG_VSI_QUEUES

  It was found in these cases that the VM is able to successfully
  transmit packets but never receives any and the RX packet drop
  counters for the VF in "ip link" on the host increase equal to the RX
  packet count.

  There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d
  claiming to resolve this error in some cases. It is already included
  in 5.15.0-41-generic and did not resolve the issue.

  The following conditions are required to trigger the bug:
  - A port VLAN must be assigned by the host
  - The MTU must be set >1500 by the guest

  There is no workaround, Intel E810 SR-IOV VFs with MTU >1500 cannot be
  used without these patches.

  [Fix]

  iavf currently sets the maximum packet size to IAVF_MAX_RXBUFFER, but
  on the previous ice driver, it was decremented by VLAN_HLEN to make
  some space to fit the VLAN header. This doesn't happen on iavf, and we
  end up trying to use a packet size larger than IAVF_MAX_RXBUFFER,
  causing the IAVF_ERR_PARAM error.

  The fix is to change the maximum packet size from IAVF_MAX_RXBUFFER to
  max_mtu received from the PF via GET_VF_RESOURCES msg.

  Also pick up a necessary commit for i40e to announce the correct
  maximum packet size by GET_VF_RESOURCES msg.

  This has been fixed by the following commits:

  commit 399c98c4dc50b7eb7e9f24da7ffdda6f025676ef
  Author: Michal Jaron 
  Date:   Tue Sep 13 15:38:35 2022 +0200
  Subject: iavf: Fix set max MTU size with port VLAN and jumbo frames
  Link: 
https://github.com/torvalds/linux/commit/399c98c4dc50b7eb7e9f24da7ffdda6f025676ef

  commit 372539def2824c43b6afe2403045b140f65c5acc
  Author: Michal Jaron 
  Date:   Tue Sep 13 15:38:36 2022 +0200
  Subject: i40e: Fix VF set max MTU size
  Link: 
https://github.com/torvalds/linux/commit/372539def2824c43b6afe2403045b140f65c5acc

  A test kernel is available in the following ppa:

  https://launchpad.net/~arif-ali/+archive/ubuntu/sf00343742

  If you install the test kernel to a compute host and VM, when you
  attach a VF and set the MTU to 9000, it succeeds, and traffic can
  flow.

  [Test Plan]

  Create a Focal VM and assign an Intel E810 (ice) SR-IOV VF with a port
  vlan:

  Openstack works, as does creating a VM directly with uvtool/libvirt.

  $ uvt-kvm create focal-test release=focal

  Using the document to understand SRIOV basics in the link below

  
https://www.intel.com/content/www/us/en/developer/articles/technical/configure-
  sr-iov-network-virtual-functions-in-linux-kvm.html

  The following command show all the bus info for all the network
  devices

  $ lshw -c network -businfo

  Choose one, as shown below

  pci@:17:01.4  ens2f0v4 networkEthernet Adaptive
  Virtual Function

  We can then add the following into the XML definition via “virsh edit
  focal-test”

  
    
  
    
   
  
    
  

  Then we stop and start the VM via "virsh shutdown focal-test" and then
  "virsh start focal-test". We can then login to the VM using the
  command below

  $ uvt-kvm ssh focal-test

  Once you have logged in, run the following ip parameters

  $ sudo ip a a 192.168.1.7/24 dev enp7s0
  $ sudo ip link set up dev enp7s0
  $ sudo ip link set mtu 9000 dev enp7s0

  Now check dmesg, and we will find the

[Kernel-packages] [Bug 1983656] Re: iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500

[Arif Ali]

The kernel was tested on 2 instances below is my testing transcript

1. Enable proposed on one of the VMs
2. Install linux-image-generic, which installed kernel 5.4.0-132.148 
3. Rebooted the node, and was able to set the IP, and ping another VM
4. Set the MTU to 9000, and was still able to ping the other VM
5. On the second VM, changed the MTU 9000 (this still had old kernel), and the 
ping stopped. The error in  dmesg was there as per the first comment
5. Upgraded the kernel on the second VM from proposed, and rebooted the VM
6. Ping started, when the second VM came up
7. Set the MTU to 9000, and the ping still continued

The same steps were repeated with setting the MTU in netplan, and we didn't 
have any issues
We also tested an MTU of 1550, to go outside of the standard 1500 and 9000, and 
we didn't see any issues either


** Tags added: verification-done-focal

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

Title:
  iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed

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

  [Impact]

  Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b]
  get no traffic flow and produce error messages in both the host and
  guest during network configuration.

  Environment: Ubuntu OpenStack Focal-Ussuri with OVN
  Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE
  Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy

  Host Error Messages:
  ice :98:00.1: VF 7 failed opcode 6, retval: -5

  Guest Error Messages:
  iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6

  In the context of these errors "6" refers to the value of
  VIRTCHNL_OP_CONFIG_VSI_QUEUES

  It was found in these cases that the VM is able to successfully
  transmit packets but never receives any and the RX packet drop
  counters for the VF in "ip link" on the host increase equal to the RX
  packet count.

  There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d
  claiming to resolve this error in some cases. It is already included
  in 5.15.0-41-generic and did not resolve the issue.

  The following conditions are required to trigger the bug:
  - A port VLAN must be assigned by the host
  - The MTU must be set >1500 by the guest

  There is no workaround, Intel E810 SR-IOV VFs with MTU >1500 cannot be
  used without these patches.

  [Fix]

  iavf currently sets the maximum packet size to IAVF_MAX_RXBUFFER, but
  on the previous ice driver, it was decremented by VLAN_HLEN to make
  some space to fit the VLAN header. This doesn't happen on iavf, and we
  end up trying to use a packet size larger than IAVF_MAX_RXBUFFER,
  causing the IAVF_ERR_PARAM error.

  The fix is to change the maximum packet size from IAVF_MAX_RXBUFFER to
  max_mtu received from the PF via GET_VF_RESOURCES msg.

  Also pick up a necessary commit for i40e to announce the correct
  maximum packet size by GET_VF_RESOURCES msg.

  This has been fixed by the following commits:

  commit 399c98c4dc50b7eb7e9f24da7ffdda6f025676ef
  Author: Michal Jaron 
  Date:   Tue Sep 13 15:38:35 2022 +0200
  Subject: iavf: Fix set max MTU size with port VLAN and jumbo frames
  Link: 
https://github.com/torvalds/linux/commit/399c98c4dc50b7eb7e9f24da7ffdda6f025676ef

  commit 372539def2824c43b6afe2403045b140f65c5acc
  Author: Michal Jaron 
  Date:   Tue Sep 13 15:38:36 2022 +0200
  Subject: i40e: Fix VF set max MTU size
  Link: 
https://github.com/torvalds/linux/commit/372539def2824c43b6afe2403045b140f65c5acc

  A test kernel is available in the following ppa:

  https://launchpad.net/~arif-ali/+archive/ubuntu/sf00343742

  If you install the test kernel to a compute host and VM, when you
  attach a VF and set the MTU to 9000, it succeeds, and traffic can
  flow.

  [Test Plan]

  Create a Focal VM and assign an Intel E810 (ice) SR-IOV VF with a port
  vlan:

  Openstack works, as does creating a VM directly with uvtool/libvirt.

  $ uvt-kvm create focal-test release=focal

  Using the document to understand SRIOV basics in the link below

  
https://www.intel.com/content/www/us/en/developer/articles/technical/configure-
  sr-iov-network-virtual-functions-in-linux-kvm.html

  The following command show all the bus info for all the network
  devices

  $ lshw -c network -businfo

  Choose one, as shown below

  pci@:17:01.4  ens2f0v4 networkEthernet Adaptive
  Virtual Function

  We can then add the following into the XML definition via “virsh edit
  focal-test”

  
    
  
    
   
  
    
  

  Then we stop and start the VM via "virsh shutdown foca

[Kernel-packages] [Bug 1993567] [NEW] devices buf

[Ahmad Ali]

Public bug reported:

touch mouse donesnt work and the heat of video card unavailable on
sensor extenstion

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-50-generic 5.15.0-50.56
ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
Uname: Linux 5.15.0-50-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ahmad  1899 F pulseaudio
 /dev/snd/pcmC0D0p:   ahmad  1899 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 19 20:08:00 2022
InstallationDate: Installed on 2022-10-11 (8 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 005: ID 13d3:3490 IMC Networks 
 Bus 001 Device 003: ID 13d3:5a11 IMC Networks USB2.0 VGA UVC WebCam
 Bus 001 Device 002: ID 18f8:1486 [Maxxter] X5s ZEUS Macro Pro Gaming Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. VivoBook 15_ASUS Laptop X540UBR
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=UUID=67ffb376-9c2a-4fc6-a9d2-aa844b3f17da ro quiet splash acpi=off 
vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-50-generic N/A
 linux-backports-modules-5.15.0-50-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.5
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
 
dmi.bios.date: 08/13/2018
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X540UBR.301
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X540UBR
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540UBR.301:bd08/13/2018:br5.12:svnASUSTeKCOMPUTERINC.:pnVivoBook15_ASUSLaptopX540UBR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540UBR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: VivoBook
dmi.product.name: VivoBook 15_ASUS Laptop X540UBR
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug jammy

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

Title:
  devices buf

Status in linux package in Ubuntu:
  New

Bug description:
  touch mouse donesnt work and the heat of video card unavailable on
  sensor extenstion

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-50-generic 5.15.0-50.56
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  Uname: Linux 5.15.0-50-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ahmad  1899 F pulseaudio
   /dev/snd/pcmC0D0p:   ahmad  1899 F...m pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 19 20:08:00 2022
  InstallationDate: Installed on 2022-10-11 (8 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 13d3:3490 IMC Networks 
   Bus 001 Device 003: ID 13d3:5a11 IMC Networks USB2.0 VGA UVC WebCam
   Bus 001 Device 002: ID 18f8:1486 [Maxxter] X5s ZEUS Macro Pro Gaming Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. VivoBook 15_ASUS Laptop X540UBR
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=UUID=67ffb376-9c2a-4fc6-a9d2-aa844b3f17da ro quiet splash acpi=off 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:
   
  dmi.bios.date: 08/13/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X540UBR.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X540UBR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 

[Kernel-packages] [Bug 1992593] ProcInterrupts.txt

[ali]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1992593/+attachment/5623883/+files/ProcInterrupts.txt

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

Title:
  HDMI port not working after upgrade to 5.15.0-50-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Yesterday i upgraded the linux kernel from 5.15.0-46-generic to
  5.15.0-50. After rebooting the second monitor was not getting detected
  (connected via HDMI cable). When i booted back from 5.15.0-46, the
  monitor worked again.

  I am running Ubuntu 20.04.5 LTS

    *-display
     description: VGA compatible controller
     product: Renoir
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:04:00.0
     version: c6
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
     configuration: driver=amdgpu latency=0
     resources: irq:45 memory:d000-dfff memory:e000-e01f 
ioport:e000(size=256) memory:fe60-fe67
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ali2669 F pipewire-media-
   /dev/snd/controlC0:  ali2669 F pipewire-media-
   /dev/snd/seq:    ali2668 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-01-25 (260 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 1.187.33
  Tags:  focal
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2021
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N.1.07.A03
  dmi.board.asset.tag: Standard
  dmi.board.name: PF5NU1G
  dmi.board.vendor: NB02
  dmi.board.version: Standard
  dmi.chassis.asset.tag: Standard
  dmi.chassis.type: 10
  dmi.chassis.vendor: SchenkerTechnologiesGmbH
  dmi.chassis.version: Standard
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20:
  dmi.product.name: SCHENKER VIA 15 Pro
  dmi.product.sku: SVI15PM20
  dmi.product.version: Standard
  dmi.sys.vendor: SchenkerTechnologiesGmbH

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

[ali]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1992593/+attachment/5623882/+files/ProcEnviron.txt

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

Title:
  HDMI port not working after upgrade to 5.15.0-50-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Yesterday i upgraded the linux kernel from 5.15.0-46-generic to
  5.15.0-50. After rebooting the second monitor was not getting detected
  (connected via HDMI cable). When i booted back from 5.15.0-46, the
  monitor worked again.

  I am running Ubuntu 20.04.5 LTS

    *-display
     description: VGA compatible controller
     product: Renoir
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:04:00.0
     version: c6
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
     configuration: driver=amdgpu latency=0
     resources: irq:45 memory:d000-dfff memory:e000-e01f 
ioport:e000(size=256) memory:fe60-fe67
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ali2669 F pipewire-media-
   /dev/snd/controlC0:  ali2669 F pipewire-media-
   /dev/snd/seq:    ali2668 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-01-25 (260 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 1.187.33
  Tags:  focal
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2021
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N.1.07.A03
  dmi.board.asset.tag: Standard
  dmi.board.name: PF5NU1G
  dmi.board.vendor: NB02
  dmi.board.version: Standard
  dmi.chassis.asset.tag: Standard
  dmi.chassis.type: 10
  dmi.chassis.vendor: SchenkerTechnologiesGmbH
  dmi.chassis.version: Standard
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20:
  dmi.product.name: SCHENKER VIA 15 Pro
  dmi.product.sku: SVI15PM20
  dmi.product.version: Standard
  dmi.sys.vendor: SchenkerTechnologiesGmbH

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

[ali]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1992593/+attachment/5623881/+files/ProcCpuinfoMinimal.txt

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

Title:
  HDMI port not working after upgrade to 5.15.0-50-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Yesterday i upgraded the linux kernel from 5.15.0-46-generic to
  5.15.0-50. After rebooting the second monitor was not getting detected
  (connected via HDMI cable). When i booted back from 5.15.0-46, the
  monitor worked again.

  I am running Ubuntu 20.04.5 LTS

    *-display
     description: VGA compatible controller
     product: Renoir
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:04:00.0
     version: c6
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
     configuration: driver=amdgpu latency=0
     resources: irq:45 memory:d000-dfff memory:e000-e01f 
ioport:e000(size=256) memory:fe60-fe67
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ali2669 F pipewire-media-
   /dev/snd/controlC0:  ali2669 F pipewire-media-
   /dev/snd/seq:    ali2668 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-01-25 (260 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 1.187.33
  Tags:  focal
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2021
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N.1.07.A03
  dmi.board.asset.tag: Standard
  dmi.board.name: PF5NU1G
  dmi.board.vendor: NB02
  dmi.board.version: Standard
  dmi.chassis.asset.tag: Standard
  dmi.chassis.type: 10
  dmi.chassis.vendor: SchenkerTechnologiesGmbH
  dmi.chassis.version: Standard
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20:
  dmi.product.name: SCHENKER VIA 15 Pro
  dmi.product.sku: SVI15PM20
  dmi.product.version: Standard
  dmi.sys.vendor: SchenkerTechnologiesGmbH

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

[ali]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1992593/+attachment/5623888/+files/acpidump.txt

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

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

Title:
  HDMI port not working after upgrade to 5.15.0-50-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Yesterday i upgraded the linux kernel from 5.15.0-46-generic to
  5.15.0-50. After rebooting the second monitor was not getting detected
  (connected via HDMI cable). When i booted back from 5.15.0-46, the
  monitor worked again.

  I am running Ubuntu 20.04.5 LTS

    *-display
     description: VGA compatible controller
     product: Renoir
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:04:00.0
     version: c6
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
     configuration: driver=amdgpu latency=0
     resources: irq:45 memory:d000-dfff memory:e000-e01f 
ioport:e000(size=256) memory:fe60-fe67
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ali2669 F pipewire-media-
   /dev/snd/controlC0:  ali2669 F pipewire-media-
   /dev/snd/seq:ali2668 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-01-25 (260 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 1.187.33
  Tags:  focal
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2021
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N.1.07.A03
  dmi.board.asset.tag: Standard
  dmi.board.name: PF5NU1G
  dmi.board.vendor: NB02
  dmi.board.version: Standard
  dmi.chassis.asset.tag: Standard
  dmi.chassis.type: 10
  dmi.chassis.vendor: SchenkerTechnologiesGmbH
  dmi.chassis.version: Standard
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20:
  dmi.product.name: SCHENKER VIA 15 Pro
  dmi.product.sku: SVI15PM20
  dmi.product.version: Standard
  dmi.sys.vendor: SchenkerTechnologiesGmbH

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

[ali]

apport information

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

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

Title:
  HDMI port not working after upgrade to 5.15.0-50-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Yesterday i upgraded the linux kernel from 5.15.0-46-generic to
  5.15.0-50. After rebooting the second monitor was not getting detected
  (connected via HDMI cable). When i booted back from 5.15.0-46, the
  monitor worked again.

  I am running Ubuntu 20.04.5 LTS

    *-display
     description: VGA compatible controller
     product: Renoir
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:04:00.0
     version: c6
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
     configuration: driver=amdgpu latency=0
     resources: irq:45 memory:d000-dfff memory:e000-e01f 
ioport:e000(size=256) memory:fe60-fe67
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ali2669 F pipewire-media-
   /dev/snd/controlC0:  ali2669 F pipewire-media-
   /dev/snd/seq:    ali2668 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-01-25 (260 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 1.187.33
  Tags:  focal
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2021
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N.1.07.A03
  dmi.board.asset.tag: Standard
  dmi.board.name: PF5NU1G
  dmi.board.vendor: NB02
  dmi.board.version: Standard
  dmi.chassis.asset.tag: Standard
  dmi.chassis.type: 10
  dmi.chassis.vendor: SchenkerTechnologiesGmbH
  dmi.chassis.version: Standard
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20:
  dmi.product.name: SCHENKER VIA 15 Pro
  dmi.product.sku: SVI15PM20
  dmi.product.version: Standard
  dmi.sys.vendor: SchenkerTechnologiesGmbH

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

[ali]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1992593/+attachment/5623885/+files/RfKill.txt

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

Title:
  HDMI port not working after upgrade to 5.15.0-50-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Yesterday i upgraded the linux kernel from 5.15.0-46-generic to
  5.15.0-50. After rebooting the second monitor was not getting detected
  (connected via HDMI cable). When i booted back from 5.15.0-46, the
  monitor worked again.

  I am running Ubuntu 20.04.5 LTS

    *-display
     description: VGA compatible controller
     product: Renoir
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:04:00.0
     version: c6
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
     configuration: driver=amdgpu latency=0
     resources: irq:45 memory:d000-dfff memory:e000-e01f 
ioport:e000(size=256) memory:fe60-fe67
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ali2669 F pipewire-media-
   /dev/snd/controlC0:  ali2669 F pipewire-media-
   /dev/snd/seq:    ali2668 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-01-25 (260 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 1.187.33
  Tags:  focal
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2021
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N.1.07.A03
  dmi.board.asset.tag: Standard
  dmi.board.name: PF5NU1G
  dmi.board.vendor: NB02
  dmi.board.version: Standard
  dmi.chassis.asset.tag: Standard
  dmi.chassis.type: 10
  dmi.chassis.vendor: SchenkerTechnologiesGmbH
  dmi.chassis.version: Standard
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20:
  dmi.product.name: SCHENKER VIA 15 Pro
  dmi.product.sku: SVI15PM20
  dmi.product.version: Standard
  dmi.sys.vendor: SchenkerTechnologiesGmbH

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

[ali]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1992593/+attachment/5623886/+files/UdevDb.txt

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

Title:
  HDMI port not working after upgrade to 5.15.0-50-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Yesterday i upgraded the linux kernel from 5.15.0-46-generic to
  5.15.0-50. After rebooting the second monitor was not getting detected
  (connected via HDMI cable). When i booted back from 5.15.0-46, the
  monitor worked again.

  I am running Ubuntu 20.04.5 LTS

    *-display
     description: VGA compatible controller
     product: Renoir
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:04:00.0
     version: c6
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
     configuration: driver=amdgpu latency=0
     resources: irq:45 memory:d000-dfff memory:e000-e01f 
ioport:e000(size=256) memory:fe60-fe67
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ali2669 F pipewire-media-
   /dev/snd/controlC0:  ali2669 F pipewire-media-
   /dev/snd/seq:    ali2668 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-01-25 (260 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 1.187.33
  Tags:  focal
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2021
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N.1.07.A03
  dmi.board.asset.tag: Standard
  dmi.board.name: PF5NU1G
  dmi.board.vendor: NB02
  dmi.board.version: Standard
  dmi.chassis.asset.tag: Standard
  dmi.chassis.type: 10
  dmi.chassis.vendor: SchenkerTechnologiesGmbH
  dmi.chassis.version: Standard
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20:
  dmi.product.name: SCHENKER VIA 15 Pro
  dmi.product.sku: SVI15PM20
  dmi.product.version: Standard
  dmi.sys.vendor: SchenkerTechnologiesGmbH

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

[ali]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1992593/+attachment/5623884/+files/ProcModules.txt

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

Title:
  HDMI port not working after upgrade to 5.15.0-50-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Yesterday i upgraded the linux kernel from 5.15.0-46-generic to
  5.15.0-50. After rebooting the second monitor was not getting detected
  (connected via HDMI cable). When i booted back from 5.15.0-46, the
  monitor worked again.

  I am running Ubuntu 20.04.5 LTS

    *-display
     description: VGA compatible controller
     product: Renoir
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:04:00.0
     version: c6
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
     configuration: driver=amdgpu latency=0
     resources: irq:45 memory:d000-dfff memory:e000-e01f 
ioport:e000(size=256) memory:fe60-fe67
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ali2669 F pipewire-media-
   /dev/snd/controlC0:  ali2669 F pipewire-media-
   /dev/snd/seq:    ali2668 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-01-25 (260 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 1.187.33
  Tags:  focal
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2021
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N.1.07.A03
  dmi.board.asset.tag: Standard
  dmi.board.name: PF5NU1G
  dmi.board.vendor: NB02
  dmi.board.version: Standard
  dmi.chassis.asset.tag: Standard
  dmi.chassis.type: 10
  dmi.chassis.vendor: SchenkerTechnologiesGmbH
  dmi.chassis.version: Standard
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20:
  dmi.product.name: SCHENKER VIA 15 Pro
  dmi.product.sku: SVI15PM20
  dmi.product.version: Standard
  dmi.sys.vendor: SchenkerTechnologiesGmbH

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

[ali]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1992593/+attachment/5623880/+files/ProcCpuinfo.txt

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

Title:
  HDMI port not working after upgrade to 5.15.0-50-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Yesterday i upgraded the linux kernel from 5.15.0-46-generic to
  5.15.0-50. After rebooting the second monitor was not getting detected
  (connected via HDMI cable). When i booted back from 5.15.0-46, the
  monitor worked again.

  I am running Ubuntu 20.04.5 LTS

    *-display
     description: VGA compatible controller
     product: Renoir
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:04:00.0
     version: c6
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
     configuration: driver=amdgpu latency=0
     resources: irq:45 memory:d000-dfff memory:e000-e01f 
ioport:e000(size=256) memory:fe60-fe67
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ali2669 F pipewire-media-
   /dev/snd/controlC0:  ali2669 F pipewire-media-
   /dev/snd/seq:    ali2668 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-01-25 (260 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 1.187.33
  Tags:  focal
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2021
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N.1.07.A03
  dmi.board.asset.tag: Standard
  dmi.board.name: PF5NU1G
  dmi.board.vendor: NB02
  dmi.board.version: Standard
  dmi.chassis.asset.tag: Standard
  dmi.chassis.type: 10
  dmi.chassis.vendor: SchenkerTechnologiesGmbH
  dmi.chassis.version: Standard
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20:
  dmi.product.name: SCHENKER VIA 15 Pro
  dmi.product.sku: SVI15PM20
  dmi.product.version: Standard
  dmi.sys.vendor: SchenkerTechnologiesGmbH

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

[ali]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1992593/+attachment/5623876/+files/Lspci-vt.txt

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

Title:
  HDMI port not working after upgrade to 5.15.0-50-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Yesterday i upgraded the linux kernel from 5.15.0-46-generic to
  5.15.0-50. After rebooting the second monitor was not getting detected
  (connected via HDMI cable). When i booted back from 5.15.0-46, the
  monitor worked again.

  I am running Ubuntu 20.04.5 LTS

    *-display
     description: VGA compatible controller
     product: Renoir
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:04:00.0
     version: c6
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
     configuration: driver=amdgpu latency=0
     resources: irq:45 memory:d000-dfff memory:e000-e01f 
ioport:e000(size=256) memory:fe60-fe67
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ali2669 F pipewire-media-
   /dev/snd/controlC0:  ali2669 F pipewire-media-
   /dev/snd/seq:    ali2668 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-01-25 (260 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 1.187.33
  Tags:  focal
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2021
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N.1.07.A03
  dmi.board.asset.tag: Standard
  dmi.board.name: PF5NU1G
  dmi.board.vendor: NB02
  dmi.board.version: Standard
  dmi.chassis.asset.tag: Standard
  dmi.chassis.type: 10
  dmi.chassis.vendor: SchenkerTechnologiesGmbH
  dmi.chassis.version: Standard
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20:
  dmi.product.name: SCHENKER VIA 15 Pro
  dmi.product.sku: SVI15PM20
  dmi.product.version: Standard
  dmi.sys.vendor: SchenkerTechnologiesGmbH

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

[ali]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1992593/+attachment/5623879/+files/Lsusb-v.txt

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

Title:
  HDMI port not working after upgrade to 5.15.0-50-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Yesterday i upgraded the linux kernel from 5.15.0-46-generic to
  5.15.0-50. After rebooting the second monitor was not getting detected
  (connected via HDMI cable). When i booted back from 5.15.0-46, the
  monitor worked again.

  I am running Ubuntu 20.04.5 LTS

    *-display
     description: VGA compatible controller
     product: Renoir
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:04:00.0
     version: c6
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
     configuration: driver=amdgpu latency=0
     resources: irq:45 memory:d000-dfff memory:e000-e01f 
ioport:e000(size=256) memory:fe60-fe67
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ali2669 F pipewire-media-
   /dev/snd/controlC0:  ali2669 F pipewire-media-
   /dev/snd/seq:    ali2668 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-01-25 (260 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 1.187.33
  Tags:  focal
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2021
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N.1.07.A03
  dmi.board.asset.tag: Standard
  dmi.board.name: PF5NU1G
  dmi.board.vendor: NB02
  dmi.board.version: Standard
  dmi.chassis.asset.tag: Standard
  dmi.chassis.type: 10
  dmi.chassis.vendor: SchenkerTechnologiesGmbH
  dmi.chassis.version: Standard
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20:
  dmi.product.name: SCHENKER VIA 15 Pro
  dmi.product.sku: SVI15PM20
  dmi.product.version: Standard
  dmi.sys.vendor: SchenkerTechnologiesGmbH

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

[ali]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1992593/+attachment/5623877/+files/Lsusb.txt

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

Title:
  HDMI port not working after upgrade to 5.15.0-50-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Yesterday i upgraded the linux kernel from 5.15.0-46-generic to
  5.15.0-50. After rebooting the second monitor was not getting detected
  (connected via HDMI cable). When i booted back from 5.15.0-46, the
  monitor worked again.

  I am running Ubuntu 20.04.5 LTS

    *-display
     description: VGA compatible controller
     product: Renoir
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:04:00.0
     version: c6
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
     configuration: driver=amdgpu latency=0
     resources: irq:45 memory:d000-dfff memory:e000-e01f 
ioport:e000(size=256) memory:fe60-fe67
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ali2669 F pipewire-media-
   /dev/snd/controlC0:  ali2669 F pipewire-media-
   /dev/snd/seq:    ali2668 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-01-25 (260 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 1.187.33
  Tags:  focal
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2021
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N.1.07.A03
  dmi.board.asset.tag: Standard
  dmi.board.name: PF5NU1G
  dmi.board.vendor: NB02
  dmi.board.version: Standard
  dmi.chassis.asset.tag: Standard
  dmi.chassis.type: 10
  dmi.chassis.vendor: SchenkerTechnologiesGmbH
  dmi.chassis.version: Standard
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20:
  dmi.product.name: SCHENKER VIA 15 Pro
  dmi.product.sku: SVI15PM20
  dmi.product.version: Standard
  dmi.sys.vendor: SchenkerTechnologiesGmbH

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

[ali]

apport information

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

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

Title:
  HDMI port not working after upgrade to 5.15.0-50-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Yesterday i upgraded the linux kernel from 5.15.0-46-generic to
  5.15.0-50. After rebooting the second monitor was not getting detected
  (connected via HDMI cable). When i booted back from 5.15.0-46, the
  monitor worked again.

  I am running Ubuntu 20.04.5 LTS

    *-display
     description: VGA compatible controller
     product: Renoir
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:04:00.0
     version: c6
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
     configuration: driver=amdgpu latency=0
     resources: irq:45 memory:d000-dfff memory:e000-e01f 
ioport:e000(size=256) memory:fe60-fe67
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ali2669 F pipewire-media-
   /dev/snd/controlC0:  ali2669 F pipewire-media-
   /dev/snd/seq:    ali2668 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-01-25 (260 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 1.187.33
  Tags:  focal
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2021
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N.1.07.A03
  dmi.board.asset.tag: Standard
  dmi.board.name: PF5NU1G
  dmi.board.vendor: NB02
  dmi.board.version: Standard
  dmi.chassis.asset.tag: Standard
  dmi.chassis.type: 10
  dmi.chassis.vendor: SchenkerTechnologiesGmbH
  dmi.chassis.version: Standard
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20:
  dmi.product.name: SCHENKER VIA 15 Pro
  dmi.product.sku: SVI15PM20
  dmi.product.version: Standard
  dmi.sys.vendor: SchenkerTechnologiesGmbH

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

[ali]

apport information

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

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

Title:
  HDMI port not working after upgrade to 5.15.0-50-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Yesterday i upgraded the linux kernel from 5.15.0-46-generic to
  5.15.0-50. After rebooting the second monitor was not getting detected
  (connected via HDMI cable). When i booted back from 5.15.0-46, the
  monitor worked again.

  I am running Ubuntu 20.04.5 LTS

    *-display
     description: VGA compatible controller
     product: Renoir
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:04:00.0
     version: c6
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
     configuration: driver=amdgpu latency=0
     resources: irq:45 memory:d000-dfff memory:e000-e01f 
ioport:e000(size=256) memory:fe60-fe67
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ali2669 F pipewire-media-
   /dev/snd/controlC0:  ali2669 F pipewire-media-
   /dev/snd/seq:    ali2668 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-01-25 (260 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 1.187.33
  Tags:  focal
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2021
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N.1.07.A03
  dmi.board.asset.tag: Standard
  dmi.board.name: PF5NU1G
  dmi.board.vendor: NB02
  dmi.board.version: Standard
  dmi.chassis.asset.tag: Standard
  dmi.chassis.type: 10
  dmi.chassis.vendor: SchenkerTechnologiesGmbH
  dmi.chassis.version: Standard
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20:
  dmi.product.name: SCHENKER VIA 15 Pro
  dmi.product.sku: SVI15PM20
  dmi.product.version: Standard
  dmi.sys.vendor: SchenkerTechnologiesGmbH

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

[ali]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1992593/+attachment/5623878/+files/Lsusb-t.txt

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

Title:
  HDMI port not working after upgrade to 5.15.0-50-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Yesterday i upgraded the linux kernel from 5.15.0-46-generic to
  5.15.0-50. After rebooting the second monitor was not getting detected
  (connected via HDMI cable). When i booted back from 5.15.0-46, the
  monitor worked again.

  I am running Ubuntu 20.04.5 LTS

    *-display
     description: VGA compatible controller
     product: Renoir
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:04:00.0
     version: c6
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
     configuration: driver=amdgpu latency=0
     resources: irq:45 memory:d000-dfff memory:e000-e01f 
ioport:e000(size=256) memory:fe60-fe67
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ali2669 F pipewire-media-
   /dev/snd/controlC0:  ali2669 F pipewire-media-
   /dev/snd/seq:    ali2668 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-01-25 (260 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 1.187.33
  Tags:  focal
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2021
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N.1.07.A03
  dmi.board.asset.tag: Standard
  dmi.board.name: PF5NU1G
  dmi.board.vendor: NB02
  dmi.board.version: Standard
  dmi.chassis.asset.tag: Standard
  dmi.chassis.type: 10
  dmi.chassis.vendor: SchenkerTechnologiesGmbH
  dmi.chassis.version: Standard
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20:
  dmi.product.name: SCHENKER VIA 15 Pro
  dmi.product.sku: SVI15PM20
  dmi.product.version: Standard
  dmi.sys.vendor: SchenkerTechnologiesGmbH

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

[ali]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1992593/+attachment/5623874/+files/IwConfig.txt

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

Title:
  HDMI port not working after upgrade to 5.15.0-50-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Yesterday i upgraded the linux kernel from 5.15.0-46-generic to
  5.15.0-50. After rebooting the second monitor was not getting detected
  (connected via HDMI cable). When i booted back from 5.15.0-46, the
  monitor worked again.

  I am running Ubuntu 20.04.5 LTS

    *-display
     description: VGA compatible controller
     product: Renoir
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:04:00.0
     version: c6
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
     configuration: driver=amdgpu latency=0
     resources: irq:45 memory:d000-dfff memory:e000-e01f 
ioport:e000(size=256) memory:fe60-fe67
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ali2669 F pipewire-media-
   /dev/snd/controlC0:  ali2669 F pipewire-media-
   /dev/snd/seq:    ali2668 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-01-25 (260 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 1.187.33
  Tags:  focal
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2021
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N.1.07.A03
  dmi.board.asset.tag: Standard
  dmi.board.name: PF5NU1G
  dmi.board.vendor: NB02
  dmi.board.version: Standard
  dmi.chassis.asset.tag: Standard
  dmi.chassis.type: 10
  dmi.chassis.vendor: SchenkerTechnologiesGmbH
  dmi.chassis.version: Standard
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20:
  dmi.product.name: SCHENKER VIA 15 Pro
  dmi.product.sku: SVI15PM20
  dmi.product.version: Standard
  dmi.sys.vendor: SchenkerTechnologiesGmbH

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

[ali]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1992593/+attachment/5623872/+files/CRDA.txt

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

Title:
  HDMI port not working after upgrade to 5.15.0-50-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Yesterday i upgraded the linux kernel from 5.15.0-46-generic to
  5.15.0-50. After rebooting the second monitor was not getting detected
  (connected via HDMI cable). When i booted back from 5.15.0-46, the
  monitor worked again.

  I am running Ubuntu 20.04.5 LTS

    *-display
     description: VGA compatible controller
     product: Renoir
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:04:00.0
     version: c6
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
     configuration: driver=amdgpu latency=0
     resources: irq:45 memory:d000-dfff memory:e000-e01f 
ioport:e000(size=256) memory:fe60-fe67
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ali2669 F pipewire-media-
   /dev/snd/controlC0:  ali2669 F pipewire-media-
   /dev/snd/seq:    ali2668 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-01-25 (260 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 1.187.33
  Tags:  focal
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2021
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N.1.07.A03
  dmi.board.asset.tag: Standard
  dmi.board.name: PF5NU1G
  dmi.board.vendor: NB02
  dmi.board.version: Standard
  dmi.chassis.asset.tag: Standard
  dmi.chassis.type: 10
  dmi.chassis.vendor: SchenkerTechnologiesGmbH
  dmi.chassis.version: Standard
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20:
  dmi.product.name: SCHENKER VIA 15 Pro
  dmi.product.sku: SVI15PM20
  dmi.product.version: Standard
  dmi.sys.vendor: SchenkerTechnologiesGmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992593/+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 1992593] Re: HDMI port not working after upgrade to 5.15.0-50-generic

[ali]

apport information

** Tags added: apport-collected focal

** Description changed:

  Yesterday i upgraded the linux kernel from 5.15.0-46-generic to
  5.15.0-50. After rebooting the second monitor was not getting detected
  (connected via HDMI cable). When i booted back from 5.15.0-46, the
  monitor worked again.
  
  I am running Ubuntu 20.04.5 LTS
  
    *-display
     description: VGA compatible controller
     product: Renoir
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:04:00.0
     version: c6
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
     configuration: driver=amdgpu latency=0
     resources: irq:45 memory:d000-dfff memory:e000-e01f 
ioport:e000(size=256) memory:fe60-fe67
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.24
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  ali2669 F pipewire-media-
+  /dev/snd/controlC0:  ali2669 F pipewire-media-
+  /dev/snd/seq:ali2668 F pipewire
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2022-01-25 (260 days ago)
+ InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
+ MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro
+ NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
+ Package: linux (not installed)
+ ProcFB: 0 amdgpudrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  linux-restricted-modules-5.15.0-46-generic N/A
+  linux-backports-modules-5.15.0-46-generic  N/A
+  linux-firmware 1.187.33
+ Tags:  focal
+ Uname: Linux 5.15.0-46-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare 
sudo
+ _MarkForUpload: True
+ dmi.bios.date: 05/11/2021
+ dmi.bios.release: 5.16
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: N.1.07.A03
+ dmi.board.asset.tag: Standard
+ dmi.board.name: PF5NU1G
+ dmi.board.vendor: NB02
+ dmi.board.version: Standard
+ dmi.chassis.asset.tag: Standard
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: SchenkerTechnologiesGmbH
+ dmi.chassis.version: Standard
+ dmi.ec.firmware.release: 1.7
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20:
+ dmi.product.name: SCHENKER VIA 15 Pro
+ dmi.product.sku: SVI15PM20
+ dmi.product.version: Standard
+ dmi.sys.vendor: SchenkerTechnologiesGmbH

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1992593/+attachment/5623871/+files/AlsaInfo.txt

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

Title:
  HDMI port not working after upgrade to 5.15.0-50-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Yesterday i upgraded the linux kernel from 5.15.0-46-generic to
  5.15.0-50. After rebooting the second monitor was not getting detected
  (connected via HDMI cable). When i booted back from 5.15.0-46, the
  monitor worked again.

  I am running Ubuntu 20.04.5 LTS

    *-display
     description: VGA compatible controller
     product: Renoir
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:04:00.0
     version: c6
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
     configuration: driver=amdgpu latency=0
     resources: irq:45 memory:d000-dfff memory:e000-e01f 
ioport:e000(size=256) memory:fe60-fe67
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ali2669 F pipewire-media-
   /dev/snd/controlC0:  ali2669 F pipewire-media-
   /dev/snd/seq:ali2668 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-01-25 (260 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro
  Nonf

[Kernel-packages] [Bug 1992593] [NEW] HDMI port not working after upgrade to 5.15.0-50-generic

[ali]

Public bug reported:

Yesterday i upgraded the linux kernel from 5.15.0-46-generic to
5.15.0-50. After rebooting the second monitor was not getting detected
(connected via HDMI cable). When i booted back from 5.15.0-46, the
monitor worked again.

I am running Ubuntu 20.04.5 LTS

  *-display
   description: VGA compatible controller
   product: Renoir
   vendor: Advanced Micro Devices, Inc. [AMD/ATI]
   physical id: 0
   bus info: pci@:04:00.0
   version: c6
   width: 64 bits
   clock: 33MHz
   capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
   configuration: driver=amdgpu latency=0
   resources: irq:45 memory:d000-dfff memory:e000-e01f 
ioport:e000(size=256) memory:fe60-fe67

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

** Description changed:

  Yesterday i upgraded the linux kernel from 5.15.0-46-generic to
  5.15.0-50. After rebooting the second monitor was not getting detected
- (connected va HDMI cable). When i booted back from 5.15.0-46, i monitor
- worked again.
+ (connected via HDMI cable). When i booted back from 5.15.0-46, the
+ monitor worked again.
  
  I am running Ubuntu 20.04.5 LTS
  
- 
-   *-display 
-description: VGA compatible controller
-product: Renoir
-vendor: Advanced Micro Devices, Inc. [AMD/ATI]
-physical id: 0
-bus info: pci@:04:00.0
-version: c6
-width: 64 bits
-clock: 33MHz
-capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
-configuration: driver=amdgpu latency=0
-resources: irq:45 memory:d000-dfff memory:e000-e01f 
ioport:e000(size=256) memory:fe60-fe67
+   *-display
+    description: VGA compatible controller
+    product: Renoir
+    vendor: Advanced Micro Devices, Inc. [AMD/ATI]
+    physical id: 0
+    bus info: pci@:04:00.0
+    version: c6
+    width: 64 bits
+    clock: 33MHz
+    capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
+    configuration: driver=amdgpu latency=0
+    resources: irq:45 memory:d000-dfff memory:e000-e01f 
ioport:e000(size=256) memory:fe60-fe67

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

Title:
  HDMI port not working after upgrade to 5.15.0-50-generic

Status in linux package in Ubuntu:
  New

Bug description:
  Yesterday i upgraded the linux kernel from 5.15.0-46-generic to
  5.15.0-50. After rebooting the second monitor was not getting detected
  (connected via HDMI cable). When i booted back from 5.15.0-46, the
  monitor worked again.

  I am running Ubuntu 20.04.5 LTS

    *-display
     description: VGA compatible controller
     product: Renoir
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:04:00.0
     version: c6
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
     configuration: driver=amdgpu latency=0
     resources: irq:45 memory:d000-dfff memory:e000-e01f 
ioport:e000(size=256) memory:fe60-fe67

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992593/+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 1983656] Re: SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf)

[Arif Ali]

Been working with Trent and Intel, and below [1] is the patch for the
MTU fix

My test kernels are available in PPA [2] for both 5.4 and 5.15

[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue.git/commit/drivers/net/ethernet/intel/iavf?h=dev-queue=399c98c4dc50b7eb7e9f24da7ffdda6f025676ef
[2] https://launchpad.net/~arif-ali/+archive/ubuntu/sf00343742

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

Title:
  SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b]
  get no traffic flow and produce error messages in both the host and
  guest during network configuration.

  Environment: Ubuntu OpenStack Focal-Ussuri with OVN
  Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE
  Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy

  Host Error Messages:
  ice :98:00.1: VF 7 failed opcode 6, retval: -5

  Guest Error Messages:
  iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6

  In the context of these errors "6" refers to the value of
  VIRTCHNL_OP_CONFIG_VSI_QUEUES

  It was found in these cases that the VM is able to successfully
  transmit packets but never receives any and the RX packet drop
  counters for the VF in "ip link" on the host increase equal to the RX
  packet count.

  
  There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d claiming to 
resolve this error in some cases. It is already included in the test kernel 
v5.15.0-41 and did not resolve the issue. 

  These Virtual Machines do work with the Mainline v5.19 build on the
  host and it includes the following two VIRTCHNL_OP_CONFIG_VSI_QUEUES
  related commits that are not currently backported to v5.15 or any
  upstream stable kernel:

  6096dae926a22e2892ef9169f582589c16d39639 ice: clear stale Tx queue settings 
before configuring [v5.18]
  be2af71496a54a7195ac62caba6fab49cfe5006c ice: Fix queue config fail handling 
[v5.19]

  Additionally during testing if we link down an interface and/or try to use 
netplan apply to start DHCP instead of manual configuration we triggered the 
following memory corruption bug:
  efe41860008e57fb6b69855b4b93fdf34bc42798 ice: Fix memory corruption in VF 
driver [v5.19]

  
  It appears that this ice/iavf driver is quite immature as many significant 
SR-IOV related fixes have landed in each of the recent kernel releases and we 
may need to consider pro-actively backporting more fixes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983656/+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 1948626] Re: [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010

[Sheik Ajith Ali Mohammed Farook]

Hi Michael,

I have done the basic sanity test by following the below test cases with
linux/5.15.0-43.46 kernel.

 1. Test NVMe/TCP initiator support with the kernel
 2. Create nvme
 3. Connect and mount the luns
 4. Complile and test libnvme and nvme-stas packages from github

Have not faced any issue with the NVMe/TCP connection and with the
latest nvme packages except socket connection error: -111 and -110 at
some point. I have attached the sos report for reference.

** Attachment added: "sosreport-linux-2022-07-19-5.15.0-43.46.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948626/+attachment/5604036/+files/sosreport-linux-2022-07-19-5.15.0-43.46.tar.xz

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

Title:
  [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC
  Client  - TP 8010

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  NVMe-oF suffers from a well-known discovery problem that fundamentally limits 
the size of realistic deployments. To address this discovery problem, the FMDS 
working group (within nvme.org) is working on two proposals that will allow 
NVMe-oF to be managed via a “network centric” provisioning process instead of 
an “end-node centric” one.
  TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will 
enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP 
Network and will prevent an end-user from needing to manually configure the IP 
Address of Discovery Controllers.
  TP-8010 (this launchpad): will define the concept of a Centralized Discovery 
Controller (CDC) and will allow end-users to manage connectivity from a single 
point of management on an IP Fabric by IP Fabric basis.

  Here is code that implements TP8009 and TP8010:
  https://github.com/martin-belanger/nvme-stas/ which now got pulled into 
upstream - https://github.com/linux-nvme/nvme-stas

  [Fix]
  1. Update kernel with TP8010 kernel patches:

  a.
  
https://git.infradead.org/git/nvme.git/commit/647b2e01fb2d3394090ed11d1b5238157c52f907

  b.
  
https://git.infradead.org/git/nvme.git/commit/de87c02ea9b4d93d1114b912b621ead81f6738e0

  c.
   nvme: add CNTRLTYPE definitions for 'identify controller
  https://lore.kernel.org/all/66fc4f03-ed5c-4727-ba94-c23daf7d6...@oracle.com/

  [Test Case]
   1.  Compile libnvme and nvme-stas packages from github using the kernel 
   with these patches.  

   2.  Test libnvme and nvme-stas packages

  [Where problems could occur]
  Regression risk for these patches are low

  [Other Info]
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/nvme_tcp_patches_2

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

[Ammad Ali]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1962485/+attachment/5564287/+files/acpidump.txt

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

Title:
  Kernel Crash [general protection fault:  [#1] SMP NOPTI]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I am running openstack xena release on ubuntu focal. Today my compute
  node running ubuntu focal crashed with due to kernel and dump has been
  generated in /var/crash/. Below is the kernel trace in crash dump.

  [455151.890114] general protection fault:  [#1] SMP NOPTI
  [455151.890285] CPU: 43 PID: 83232 Comm: qemu-system-x86 Kdump: loaded 
Tainted: G   OE 5.4.0-88-generic #99-Ubuntu
  [455151.890612] Hardware name: Dell Inc. PowerEdge R6525/X, BIOS 2.5.6 
10/06/2021
  [455151.890842] RIP: 0010:count_subheaders.part.0+0x26/0x60
  [455151.890998] Code: 00 00 00 90 0f 1f 44 00 00 48 83 3f 00 74 4d 55 48 89 
e5 41 55 45 31 ed 41 54 45 31 e4 53 48 89 fb 48 8b 7b 18 48 85 ff 74 23 <48> 83 
3f 00 74 25 e8 cf ff ff ff 41 
  01 c5 48 83 c3 40 48 83 3b 00
  [455151.891552] RSP: 0018:a6b477487b88 EFLAGS: 00010202
  [455151.891707] RAX:  RBX: 9387c594f280 RCX: 

  [455151.891918] RDX: 0060 RSI: 9390702a72c0 RDI: 
0314a8c0f1b16f3e
  [455151.892130] RBP: a6b477487ba0 R08:  R09: 
bc6ed7f0
  [455151.892341] R10: a6b477487cd0 R11: 0001 R12: 

  [455151.892552] R13:  R14: 9391e5684000 R15: 
bd5f9880
  [455151.892767] FS:  7f69950c75c0() GS:9391feac() 
knlGS:
  [455151.893016] CS:  0010 DS:  ES:  CR0: 80050033
  [455151.893207] CR2: 7f61e9e45000 CR3: 017c54afa000 CR4: 
00340ee0
  [455151.893434] Call Trace:
  [455151.893514]  count_subheaders.part.0+0x31/0x60
  [455151.893646]  unregister_sysctl_table+0x30/0x90
  [455151.893781]  unregister_net_sysctl_table+0xe/0x10
  [455151.893922]  __devinet_sysctl_unregister.isra.0+0x2c/0x60
  [455151.894082]  devinet_sysctl_unregister+0x29/0x40
  [455151.894220]  inetdev_event+0x1e8/0x560
  [455151.894334]  ? skb_dequeue+0x5f/0x70
  [455151.89]  notifier_call_chain+0x55/0x80
  [455151.894565]  ? notifier_call_chain+0x55/0x80
  [455151.894693]  raw_notifier_call_chain+0x16/0x20
  [455151.894829]  call_netdevice_notifiers_info+0x2e/0x60
  [455151.894983]  ? tun_show_owner+0x60/0x60
  [455151.895098]  rollback_registered_many+0x36e/0x520
  [455151.895239]  unregister_netdevice_queue+0x94/0x120
  [455151.895383]  __tun_detach+0x421/0x430
  [455151.895495]  tun_chr_close+0x3a/0x70
  [455151.895605]  __fput+0xcc/0x260
  [455151.895698]  fput+0xe/0x10
  [455151.895792]  task_work_run+0x8f/0xb0
  [455151.895903]  exit_to_usermode_loop+0x131/0x160
  [455151.896036]  do_syscall_64+0x163/0x190
  [455151.896150]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [455151.896302] RIP: 0033:0x7f69965ba3fb
  [455151.896410] Code: 03 00 00 00 0f 05 48 3d 00 f0 ff ff 77 41 c3 48 83 ec 
18 89 7c 24 0c e8 f3 fb ff ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 
00 f0 ff ff 77 2f 44 89 c7 89 44 24 0c e8 31 fc ff ff 8b 44
  [455151.896975] RSP: 002b:7ffdff14b350 EFLAGS: 0293 ORIG_RAX: 
0003
  [455151.897201] RAX:  RBX: 557fe0875e50 RCX: 
7f69965ba3fb
  [455151.897412] RDX: 557fe0748f40 RSI: 0001 RDI: 
002b
  [455151.897637] RBP: 557fe0887460 R08:  R09: 

  [455151.904390] R10: 0032 R11: 0293 R12: 
557fe0875e50
  [455151.911165] R13: 0001 R14: 557fe09efc10 R15: 
557fe0747900

  I didn't find any documented details on kernel 5.4 for this bug. I
  have uploaded the logs via ubuntu-bug linux command.

  # uname -a
  Linux kvm03-a1-r01-khi04.rapid.pk 5.4.0-88-generic #99-Ubuntu SMP Thu Sep 23 
17:29:00 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

  # cat /proc/version_signature
  Ubuntu 5.4.0-88.99-generic 5.4.140

  I am using Dell R6525 with EPYC 7532 CPUs.

  Let me know if there is there are more information needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-88-generic 5.4.0-88.99
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Uname: Linux 5.4.0-88-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 28 17:38 seq
   crw-rw 1 root audio 116, 33 Feb 28 17:38 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: pass
  

[Kernel-packages] [Bug 1962485] ProcCpuinfoMinimal.txt

[Ammad Ali]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1962485/+attachment/5564282/+files/ProcCpuinfoMinimal.txt

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

Title:
  Kernel Crash [general protection fault:  [#1] SMP NOPTI]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I am running openstack xena release on ubuntu focal. Today my compute
  node running ubuntu focal crashed with due to kernel and dump has been
  generated in /var/crash/. Below is the kernel trace in crash dump.

  [455151.890114] general protection fault:  [#1] SMP NOPTI
  [455151.890285] CPU: 43 PID: 83232 Comm: qemu-system-x86 Kdump: loaded 
Tainted: G   OE 5.4.0-88-generic #99-Ubuntu
  [455151.890612] Hardware name: Dell Inc. PowerEdge R6525/X, BIOS 2.5.6 
10/06/2021
  [455151.890842] RIP: 0010:count_subheaders.part.0+0x26/0x60
  [455151.890998] Code: 00 00 00 90 0f 1f 44 00 00 48 83 3f 00 74 4d 55 48 89 
e5 41 55 45 31 ed 41 54 45 31 e4 53 48 89 fb 48 8b 7b 18 48 85 ff 74 23 <48> 83 
3f 00 74 25 e8 cf ff ff ff 41 
  01 c5 48 83 c3 40 48 83 3b 00
  [455151.891552] RSP: 0018:a6b477487b88 EFLAGS: 00010202
  [455151.891707] RAX:  RBX: 9387c594f280 RCX: 

  [455151.891918] RDX: 0060 RSI: 9390702a72c0 RDI: 
0314a8c0f1b16f3e
  [455151.892130] RBP: a6b477487ba0 R08:  R09: 
bc6ed7f0
  [455151.892341] R10: a6b477487cd0 R11: 0001 R12: 

  [455151.892552] R13:  R14: 9391e5684000 R15: 
bd5f9880
  [455151.892767] FS:  7f69950c75c0() GS:9391feac() 
knlGS:
  [455151.893016] CS:  0010 DS:  ES:  CR0: 80050033
  [455151.893207] CR2: 7f61e9e45000 CR3: 017c54afa000 CR4: 
00340ee0
  [455151.893434] Call Trace:
  [455151.893514]  count_subheaders.part.0+0x31/0x60
  [455151.893646]  unregister_sysctl_table+0x30/0x90
  [455151.893781]  unregister_net_sysctl_table+0xe/0x10
  [455151.893922]  __devinet_sysctl_unregister.isra.0+0x2c/0x60
  [455151.894082]  devinet_sysctl_unregister+0x29/0x40
  [455151.894220]  inetdev_event+0x1e8/0x560
  [455151.894334]  ? skb_dequeue+0x5f/0x70
  [455151.89]  notifier_call_chain+0x55/0x80
  [455151.894565]  ? notifier_call_chain+0x55/0x80
  [455151.894693]  raw_notifier_call_chain+0x16/0x20
  [455151.894829]  call_netdevice_notifiers_info+0x2e/0x60
  [455151.894983]  ? tun_show_owner+0x60/0x60
  [455151.895098]  rollback_registered_many+0x36e/0x520
  [455151.895239]  unregister_netdevice_queue+0x94/0x120
  [455151.895383]  __tun_detach+0x421/0x430
  [455151.895495]  tun_chr_close+0x3a/0x70
  [455151.895605]  __fput+0xcc/0x260
  [455151.895698]  fput+0xe/0x10
  [455151.895792]  task_work_run+0x8f/0xb0
  [455151.895903]  exit_to_usermode_loop+0x131/0x160
  [455151.896036]  do_syscall_64+0x163/0x190
  [455151.896150]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [455151.896302] RIP: 0033:0x7f69965ba3fb
  [455151.896410] Code: 03 00 00 00 0f 05 48 3d 00 f0 ff ff 77 41 c3 48 83 ec 
18 89 7c 24 0c e8 f3 fb ff ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 
00 f0 ff ff 77 2f 44 89 c7 89 44 24 0c e8 31 fc ff ff 8b 44
  [455151.896975] RSP: 002b:7ffdff14b350 EFLAGS: 0293 ORIG_RAX: 
0003
  [455151.897201] RAX:  RBX: 557fe0875e50 RCX: 
7f69965ba3fb
  [455151.897412] RDX: 557fe0748f40 RSI: 0001 RDI: 
002b
  [455151.897637] RBP: 557fe0887460 R08:  R09: 

  [455151.904390] R10: 0032 R11: 0293 R12: 
557fe0875e50
  [455151.911165] R13: 0001 R14: 557fe09efc10 R15: 
557fe0747900

  I didn't find any documented details on kernel 5.4 for this bug. I
  have uploaded the logs via ubuntu-bug linux command.

  # uname -a
  Linux kvm03-a1-r01-khi04.rapid.pk 5.4.0-88-generic #99-Ubuntu SMP Thu Sep 23 
17:29:00 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

  # cat /proc/version_signature
  Ubuntu 5.4.0-88.99-generic 5.4.140

  I am using Dell R6525 with EPYC 7532 CPUs.

  Let me know if there is there are more information needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-88-generic 5.4.0-88.99
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Uname: Linux 5.4.0-88-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 28 17:38 seq
   crw-rw 1 root audio 116, 33 Feb 28 17:38 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  

[Kernel-packages] [Bug 1962485] Lsusb-v.txt

[Ammad Ali]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1962485/+attachment/5564280/+files/Lsusb-v.txt

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

Title:
  Kernel Crash [general protection fault:  [#1] SMP NOPTI]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I am running openstack xena release on ubuntu focal. Today my compute
  node running ubuntu focal crashed with due to kernel and dump has been
  generated in /var/crash/. Below is the kernel trace in crash dump.

  [455151.890114] general protection fault:  [#1] SMP NOPTI
  [455151.890285] CPU: 43 PID: 83232 Comm: qemu-system-x86 Kdump: loaded 
Tainted: G   OE 5.4.0-88-generic #99-Ubuntu
  [455151.890612] Hardware name: Dell Inc. PowerEdge R6525/X, BIOS 2.5.6 
10/06/2021
  [455151.890842] RIP: 0010:count_subheaders.part.0+0x26/0x60
  [455151.890998] Code: 00 00 00 90 0f 1f 44 00 00 48 83 3f 00 74 4d 55 48 89 
e5 41 55 45 31 ed 41 54 45 31 e4 53 48 89 fb 48 8b 7b 18 48 85 ff 74 23 <48> 83 
3f 00 74 25 e8 cf ff ff ff 41 
  01 c5 48 83 c3 40 48 83 3b 00
  [455151.891552] RSP: 0018:a6b477487b88 EFLAGS: 00010202
  [455151.891707] RAX:  RBX: 9387c594f280 RCX: 

  [455151.891918] RDX: 0060 RSI: 9390702a72c0 RDI: 
0314a8c0f1b16f3e
  [455151.892130] RBP: a6b477487ba0 R08:  R09: 
bc6ed7f0
  [455151.892341] R10: a6b477487cd0 R11: 0001 R12: 

  [455151.892552] R13:  R14: 9391e5684000 R15: 
bd5f9880
  [455151.892767] FS:  7f69950c75c0() GS:9391feac() 
knlGS:
  [455151.893016] CS:  0010 DS:  ES:  CR0: 80050033
  [455151.893207] CR2: 7f61e9e45000 CR3: 017c54afa000 CR4: 
00340ee0
  [455151.893434] Call Trace:
  [455151.893514]  count_subheaders.part.0+0x31/0x60
  [455151.893646]  unregister_sysctl_table+0x30/0x90
  [455151.893781]  unregister_net_sysctl_table+0xe/0x10
  [455151.893922]  __devinet_sysctl_unregister.isra.0+0x2c/0x60
  [455151.894082]  devinet_sysctl_unregister+0x29/0x40
  [455151.894220]  inetdev_event+0x1e8/0x560
  [455151.894334]  ? skb_dequeue+0x5f/0x70
  [455151.89]  notifier_call_chain+0x55/0x80
  [455151.894565]  ? notifier_call_chain+0x55/0x80
  [455151.894693]  raw_notifier_call_chain+0x16/0x20
  [455151.894829]  call_netdevice_notifiers_info+0x2e/0x60
  [455151.894983]  ? tun_show_owner+0x60/0x60
  [455151.895098]  rollback_registered_many+0x36e/0x520
  [455151.895239]  unregister_netdevice_queue+0x94/0x120
  [455151.895383]  __tun_detach+0x421/0x430
  [455151.895495]  tun_chr_close+0x3a/0x70
  [455151.895605]  __fput+0xcc/0x260
  [455151.895698]  fput+0xe/0x10
  [455151.895792]  task_work_run+0x8f/0xb0
  [455151.895903]  exit_to_usermode_loop+0x131/0x160
  [455151.896036]  do_syscall_64+0x163/0x190
  [455151.896150]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [455151.896302] RIP: 0033:0x7f69965ba3fb
  [455151.896410] Code: 03 00 00 00 0f 05 48 3d 00 f0 ff ff 77 41 c3 48 83 ec 
18 89 7c 24 0c e8 f3 fb ff ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 
00 f0 ff ff 77 2f 44 89 c7 89 44 24 0c e8 31 fc ff ff 8b 44
  [455151.896975] RSP: 002b:7ffdff14b350 EFLAGS: 0293 ORIG_RAX: 
0003
  [455151.897201] RAX:  RBX: 557fe0875e50 RCX: 
7f69965ba3fb
  [455151.897412] RDX: 557fe0748f40 RSI: 0001 RDI: 
002b
  [455151.897637] RBP: 557fe0887460 R08:  R09: 

  [455151.904390] R10: 0032 R11: 0293 R12: 
557fe0875e50
  [455151.911165] R13: 0001 R14: 557fe09efc10 R15: 
557fe0747900

  I didn't find any documented details on kernel 5.4 for this bug. I
  have uploaded the logs via ubuntu-bug linux command.

  # uname -a
  Linux kvm03-a1-r01-khi04.rapid.pk 5.4.0-88-generic #99-Ubuntu SMP Thu Sep 23 
17:29:00 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

  # cat /proc/version_signature
  Ubuntu 5.4.0-88.99-generic 5.4.140

  I am using Dell R6525 with EPYC 7532 CPUs.

  Let me know if there is there are more information needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-88-generic 5.4.0-88.99
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Uname: Linux 5.4.0-88-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 28 17:38 seq
   crw-rw 1 root audio 116, 33 Feb 28 17:38 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: pass
  

[Kernel-packages] [Bug 1962485] ProcModules.txt

[Ammad Ali]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1962485/+attachment/5564284/+files/ProcModules.txt

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

Title:
  Kernel Crash [general protection fault:  [#1] SMP NOPTI]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I am running openstack xena release on ubuntu focal. Today my compute
  node running ubuntu focal crashed with due to kernel and dump has been
  generated in /var/crash/. Below is the kernel trace in crash dump.

  [455151.890114] general protection fault:  [#1] SMP NOPTI
  [455151.890285] CPU: 43 PID: 83232 Comm: qemu-system-x86 Kdump: loaded 
Tainted: G   OE 5.4.0-88-generic #99-Ubuntu
  [455151.890612] Hardware name: Dell Inc. PowerEdge R6525/X, BIOS 2.5.6 
10/06/2021
  [455151.890842] RIP: 0010:count_subheaders.part.0+0x26/0x60
  [455151.890998] Code: 00 00 00 90 0f 1f 44 00 00 48 83 3f 00 74 4d 55 48 89 
e5 41 55 45 31 ed 41 54 45 31 e4 53 48 89 fb 48 8b 7b 18 48 85 ff 74 23 <48> 83 
3f 00 74 25 e8 cf ff ff ff 41 
  01 c5 48 83 c3 40 48 83 3b 00
  [455151.891552] RSP: 0018:a6b477487b88 EFLAGS: 00010202
  [455151.891707] RAX:  RBX: 9387c594f280 RCX: 

  [455151.891918] RDX: 0060 RSI: 9390702a72c0 RDI: 
0314a8c0f1b16f3e
  [455151.892130] RBP: a6b477487ba0 R08:  R09: 
bc6ed7f0
  [455151.892341] R10: a6b477487cd0 R11: 0001 R12: 

  [455151.892552] R13:  R14: 9391e5684000 R15: 
bd5f9880
  [455151.892767] FS:  7f69950c75c0() GS:9391feac() 
knlGS:
  [455151.893016] CS:  0010 DS:  ES:  CR0: 80050033
  [455151.893207] CR2: 7f61e9e45000 CR3: 017c54afa000 CR4: 
00340ee0
  [455151.893434] Call Trace:
  [455151.893514]  count_subheaders.part.0+0x31/0x60
  [455151.893646]  unregister_sysctl_table+0x30/0x90
  [455151.893781]  unregister_net_sysctl_table+0xe/0x10
  [455151.893922]  __devinet_sysctl_unregister.isra.0+0x2c/0x60
  [455151.894082]  devinet_sysctl_unregister+0x29/0x40
  [455151.894220]  inetdev_event+0x1e8/0x560
  [455151.894334]  ? skb_dequeue+0x5f/0x70
  [455151.89]  notifier_call_chain+0x55/0x80
  [455151.894565]  ? notifier_call_chain+0x55/0x80
  [455151.894693]  raw_notifier_call_chain+0x16/0x20
  [455151.894829]  call_netdevice_notifiers_info+0x2e/0x60
  [455151.894983]  ? tun_show_owner+0x60/0x60
  [455151.895098]  rollback_registered_many+0x36e/0x520
  [455151.895239]  unregister_netdevice_queue+0x94/0x120
  [455151.895383]  __tun_detach+0x421/0x430
  [455151.895495]  tun_chr_close+0x3a/0x70
  [455151.895605]  __fput+0xcc/0x260
  [455151.895698]  fput+0xe/0x10
  [455151.895792]  task_work_run+0x8f/0xb0
  [455151.895903]  exit_to_usermode_loop+0x131/0x160
  [455151.896036]  do_syscall_64+0x163/0x190
  [455151.896150]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [455151.896302] RIP: 0033:0x7f69965ba3fb
  [455151.896410] Code: 03 00 00 00 0f 05 48 3d 00 f0 ff ff 77 41 c3 48 83 ec 
18 89 7c 24 0c e8 f3 fb ff ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 
00 f0 ff ff 77 2f 44 89 c7 89 44 24 0c e8 31 fc ff ff 8b 44
  [455151.896975] RSP: 002b:7ffdff14b350 EFLAGS: 0293 ORIG_RAX: 
0003
  [455151.897201] RAX:  RBX: 557fe0875e50 RCX: 
7f69965ba3fb
  [455151.897412] RDX: 557fe0748f40 RSI: 0001 RDI: 
002b
  [455151.897637] RBP: 557fe0887460 R08:  R09: 

  [455151.904390] R10: 0032 R11: 0293 R12: 
557fe0875e50
  [455151.911165] R13: 0001 R14: 557fe09efc10 R15: 
557fe0747900

  I didn't find any documented details on kernel 5.4 for this bug. I
  have uploaded the logs via ubuntu-bug linux command.

  # uname -a
  Linux kvm03-a1-r01-khi04.rapid.pk 5.4.0-88-generic #99-Ubuntu SMP Thu Sep 23 
17:29:00 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

  # cat /proc/version_signature
  Ubuntu 5.4.0-88.99-generic 5.4.140

  I am using Dell R6525 with EPYC 7532 CPUs.

  Let me know if there is there are more information needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-88-generic 5.4.0-88.99
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Uname: Linux 5.4.0-88-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 28 17:38 seq
   crw-rw 1 root audio 116, 33 Feb 28 17:38 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: 

[Kernel-packages] [Bug 1962485] Lsusb-t.txt

[Ammad Ali]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1962485/+attachment/5564279/+files/Lsusb-t.txt

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

Title:
  Kernel Crash [general protection fault:  [#1] SMP NOPTI]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I am running openstack xena release on ubuntu focal. Today my compute
  node running ubuntu focal crashed with due to kernel and dump has been
  generated in /var/crash/. Below is the kernel trace in crash dump.

  [455151.890114] general protection fault:  [#1] SMP NOPTI
  [455151.890285] CPU: 43 PID: 83232 Comm: qemu-system-x86 Kdump: loaded 
Tainted: G   OE 5.4.0-88-generic #99-Ubuntu
  [455151.890612] Hardware name: Dell Inc. PowerEdge R6525/X, BIOS 2.5.6 
10/06/2021
  [455151.890842] RIP: 0010:count_subheaders.part.0+0x26/0x60
  [455151.890998] Code: 00 00 00 90 0f 1f 44 00 00 48 83 3f 00 74 4d 55 48 89 
e5 41 55 45 31 ed 41 54 45 31 e4 53 48 89 fb 48 8b 7b 18 48 85 ff 74 23 <48> 83 
3f 00 74 25 e8 cf ff ff ff 41 
  01 c5 48 83 c3 40 48 83 3b 00
  [455151.891552] RSP: 0018:a6b477487b88 EFLAGS: 00010202
  [455151.891707] RAX:  RBX: 9387c594f280 RCX: 

  [455151.891918] RDX: 0060 RSI: 9390702a72c0 RDI: 
0314a8c0f1b16f3e
  [455151.892130] RBP: a6b477487ba0 R08:  R09: 
bc6ed7f0
  [455151.892341] R10: a6b477487cd0 R11: 0001 R12: 

  [455151.892552] R13:  R14: 9391e5684000 R15: 
bd5f9880
  [455151.892767] FS:  7f69950c75c0() GS:9391feac() 
knlGS:
  [455151.893016] CS:  0010 DS:  ES:  CR0: 80050033
  [455151.893207] CR2: 7f61e9e45000 CR3: 017c54afa000 CR4: 
00340ee0
  [455151.893434] Call Trace:
  [455151.893514]  count_subheaders.part.0+0x31/0x60
  [455151.893646]  unregister_sysctl_table+0x30/0x90
  [455151.893781]  unregister_net_sysctl_table+0xe/0x10
  [455151.893922]  __devinet_sysctl_unregister.isra.0+0x2c/0x60
  [455151.894082]  devinet_sysctl_unregister+0x29/0x40
  [455151.894220]  inetdev_event+0x1e8/0x560
  [455151.894334]  ? skb_dequeue+0x5f/0x70
  [455151.89]  notifier_call_chain+0x55/0x80
  [455151.894565]  ? notifier_call_chain+0x55/0x80
  [455151.894693]  raw_notifier_call_chain+0x16/0x20
  [455151.894829]  call_netdevice_notifiers_info+0x2e/0x60
  [455151.894983]  ? tun_show_owner+0x60/0x60
  [455151.895098]  rollback_registered_many+0x36e/0x520
  [455151.895239]  unregister_netdevice_queue+0x94/0x120
  [455151.895383]  __tun_detach+0x421/0x430
  [455151.895495]  tun_chr_close+0x3a/0x70
  [455151.895605]  __fput+0xcc/0x260
  [455151.895698]  fput+0xe/0x10
  [455151.895792]  task_work_run+0x8f/0xb0
  [455151.895903]  exit_to_usermode_loop+0x131/0x160
  [455151.896036]  do_syscall_64+0x163/0x190
  [455151.896150]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [455151.896302] RIP: 0033:0x7f69965ba3fb
  [455151.896410] Code: 03 00 00 00 0f 05 48 3d 00 f0 ff ff 77 41 c3 48 83 ec 
18 89 7c 24 0c e8 f3 fb ff ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 
00 f0 ff ff 77 2f 44 89 c7 89 44 24 0c e8 31 fc ff ff 8b 44
  [455151.896975] RSP: 002b:7ffdff14b350 EFLAGS: 0293 ORIG_RAX: 
0003
  [455151.897201] RAX:  RBX: 557fe0875e50 RCX: 
7f69965ba3fb
  [455151.897412] RDX: 557fe0748f40 RSI: 0001 RDI: 
002b
  [455151.897637] RBP: 557fe0887460 R08:  R09: 

  [455151.904390] R10: 0032 R11: 0293 R12: 
557fe0875e50
  [455151.911165] R13: 0001 R14: 557fe09efc10 R15: 
557fe0747900

  I didn't find any documented details on kernel 5.4 for this bug. I
  have uploaded the logs via ubuntu-bug linux command.

  # uname -a
  Linux kvm03-a1-r01-khi04.rapid.pk 5.4.0-88-generic #99-Ubuntu SMP Thu Sep 23 
17:29:00 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

  # cat /proc/version_signature
  Ubuntu 5.4.0-88.99-generic 5.4.140

  I am using Dell R6525 with EPYC 7532 CPUs.

  Let me know if there is there are more information needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-88-generic 5.4.0-88.99
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Uname: Linux 5.4.0-88-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 28 17:38 seq
   crw-rw 1 root audio 116, 33 Feb 28 17:38 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: pass
  

[Kernel-packages] [Bug 1962485] ProcCpuinfo.txt

[Ammad Ali]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1962485/+attachment/5564281/+files/ProcCpuinfo.txt

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

Title:
  Kernel Crash [general protection fault:  [#1] SMP NOPTI]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I am running openstack xena release on ubuntu focal. Today my compute
  node running ubuntu focal crashed with due to kernel and dump has been
  generated in /var/crash/. Below is the kernel trace in crash dump.

  [455151.890114] general protection fault:  [#1] SMP NOPTI
  [455151.890285] CPU: 43 PID: 83232 Comm: qemu-system-x86 Kdump: loaded 
Tainted: G   OE 5.4.0-88-generic #99-Ubuntu
  [455151.890612] Hardware name: Dell Inc. PowerEdge R6525/X, BIOS 2.5.6 
10/06/2021
  [455151.890842] RIP: 0010:count_subheaders.part.0+0x26/0x60
  [455151.890998] Code: 00 00 00 90 0f 1f 44 00 00 48 83 3f 00 74 4d 55 48 89 
e5 41 55 45 31 ed 41 54 45 31 e4 53 48 89 fb 48 8b 7b 18 48 85 ff 74 23 <48> 83 
3f 00 74 25 e8 cf ff ff ff 41 
  01 c5 48 83 c3 40 48 83 3b 00
  [455151.891552] RSP: 0018:a6b477487b88 EFLAGS: 00010202
  [455151.891707] RAX:  RBX: 9387c594f280 RCX: 

  [455151.891918] RDX: 0060 RSI: 9390702a72c0 RDI: 
0314a8c0f1b16f3e
  [455151.892130] RBP: a6b477487ba0 R08:  R09: 
bc6ed7f0
  [455151.892341] R10: a6b477487cd0 R11: 0001 R12: 

  [455151.892552] R13:  R14: 9391e5684000 R15: 
bd5f9880
  [455151.892767] FS:  7f69950c75c0() GS:9391feac() 
knlGS:
  [455151.893016] CS:  0010 DS:  ES:  CR0: 80050033
  [455151.893207] CR2: 7f61e9e45000 CR3: 017c54afa000 CR4: 
00340ee0
  [455151.893434] Call Trace:
  [455151.893514]  count_subheaders.part.0+0x31/0x60
  [455151.893646]  unregister_sysctl_table+0x30/0x90
  [455151.893781]  unregister_net_sysctl_table+0xe/0x10
  [455151.893922]  __devinet_sysctl_unregister.isra.0+0x2c/0x60
  [455151.894082]  devinet_sysctl_unregister+0x29/0x40
  [455151.894220]  inetdev_event+0x1e8/0x560
  [455151.894334]  ? skb_dequeue+0x5f/0x70
  [455151.89]  notifier_call_chain+0x55/0x80
  [455151.894565]  ? notifier_call_chain+0x55/0x80
  [455151.894693]  raw_notifier_call_chain+0x16/0x20
  [455151.894829]  call_netdevice_notifiers_info+0x2e/0x60
  [455151.894983]  ? tun_show_owner+0x60/0x60
  [455151.895098]  rollback_registered_many+0x36e/0x520
  [455151.895239]  unregister_netdevice_queue+0x94/0x120
  [455151.895383]  __tun_detach+0x421/0x430
  [455151.895495]  tun_chr_close+0x3a/0x70
  [455151.895605]  __fput+0xcc/0x260
  [455151.895698]  fput+0xe/0x10
  [455151.895792]  task_work_run+0x8f/0xb0
  [455151.895903]  exit_to_usermode_loop+0x131/0x160
  [455151.896036]  do_syscall_64+0x163/0x190
  [455151.896150]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [455151.896302] RIP: 0033:0x7f69965ba3fb
  [455151.896410] Code: 03 00 00 00 0f 05 48 3d 00 f0 ff ff 77 41 c3 48 83 ec 
18 89 7c 24 0c e8 f3 fb ff ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 
00 f0 ff ff 77 2f 44 89 c7 89 44 24 0c e8 31 fc ff ff 8b 44
  [455151.896975] RSP: 002b:7ffdff14b350 EFLAGS: 0293 ORIG_RAX: 
0003
  [455151.897201] RAX:  RBX: 557fe0875e50 RCX: 
7f69965ba3fb
  [455151.897412] RDX: 557fe0748f40 RSI: 0001 RDI: 
002b
  [455151.897637] RBP: 557fe0887460 R08:  R09: 

  [455151.904390] R10: 0032 R11: 0293 R12: 
557fe0875e50
  [455151.911165] R13: 0001 R14: 557fe09efc10 R15: 
557fe0747900

  I didn't find any documented details on kernel 5.4 for this bug. I
  have uploaded the logs via ubuntu-bug linux command.

  # uname -a
  Linux kvm03-a1-r01-khi04.rapid.pk 5.4.0-88-generic #99-Ubuntu SMP Thu Sep 23 
17:29:00 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

  # cat /proc/version_signature
  Ubuntu 5.4.0-88.99-generic 5.4.140

  I am using Dell R6525 with EPYC 7532 CPUs.

  Let me know if there is there are more information needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-88-generic 5.4.0-88.99
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Uname: Linux 5.4.0-88-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 28 17:38 seq
   crw-rw 1 root audio 116, 33 Feb 28 17:38 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: 

[Kernel-packages] [Bug 1962485] UdevDb.txt

[Ammad Ali]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1962485/+attachment/5564285/+files/UdevDb.txt

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

Title:
  Kernel Crash [general protection fault:  [#1] SMP NOPTI]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I am running openstack xena release on ubuntu focal. Today my compute
  node running ubuntu focal crashed with due to kernel and dump has been
  generated in /var/crash/. Below is the kernel trace in crash dump.

  [455151.890114] general protection fault:  [#1] SMP NOPTI
  [455151.890285] CPU: 43 PID: 83232 Comm: qemu-system-x86 Kdump: loaded 
Tainted: G   OE 5.4.0-88-generic #99-Ubuntu
  [455151.890612] Hardware name: Dell Inc. PowerEdge R6525/X, BIOS 2.5.6 
10/06/2021
  [455151.890842] RIP: 0010:count_subheaders.part.0+0x26/0x60
  [455151.890998] Code: 00 00 00 90 0f 1f 44 00 00 48 83 3f 00 74 4d 55 48 89 
e5 41 55 45 31 ed 41 54 45 31 e4 53 48 89 fb 48 8b 7b 18 48 85 ff 74 23 <48> 83 
3f 00 74 25 e8 cf ff ff ff 41 
  01 c5 48 83 c3 40 48 83 3b 00
  [455151.891552] RSP: 0018:a6b477487b88 EFLAGS: 00010202
  [455151.891707] RAX:  RBX: 9387c594f280 RCX: 

  [455151.891918] RDX: 0060 RSI: 9390702a72c0 RDI: 
0314a8c0f1b16f3e
  [455151.892130] RBP: a6b477487ba0 R08:  R09: 
bc6ed7f0
  [455151.892341] R10: a6b477487cd0 R11: 0001 R12: 

  [455151.892552] R13:  R14: 9391e5684000 R15: 
bd5f9880
  [455151.892767] FS:  7f69950c75c0() GS:9391feac() 
knlGS:
  [455151.893016] CS:  0010 DS:  ES:  CR0: 80050033
  [455151.893207] CR2: 7f61e9e45000 CR3: 017c54afa000 CR4: 
00340ee0
  [455151.893434] Call Trace:
  [455151.893514]  count_subheaders.part.0+0x31/0x60
  [455151.893646]  unregister_sysctl_table+0x30/0x90
  [455151.893781]  unregister_net_sysctl_table+0xe/0x10
  [455151.893922]  __devinet_sysctl_unregister.isra.0+0x2c/0x60
  [455151.894082]  devinet_sysctl_unregister+0x29/0x40
  [455151.894220]  inetdev_event+0x1e8/0x560
  [455151.894334]  ? skb_dequeue+0x5f/0x70
  [455151.89]  notifier_call_chain+0x55/0x80
  [455151.894565]  ? notifier_call_chain+0x55/0x80
  [455151.894693]  raw_notifier_call_chain+0x16/0x20
  [455151.894829]  call_netdevice_notifiers_info+0x2e/0x60
  [455151.894983]  ? tun_show_owner+0x60/0x60
  [455151.895098]  rollback_registered_many+0x36e/0x520
  [455151.895239]  unregister_netdevice_queue+0x94/0x120
  [455151.895383]  __tun_detach+0x421/0x430
  [455151.895495]  tun_chr_close+0x3a/0x70
  [455151.895605]  __fput+0xcc/0x260
  [455151.895698]  fput+0xe/0x10
  [455151.895792]  task_work_run+0x8f/0xb0
  [455151.895903]  exit_to_usermode_loop+0x131/0x160
  [455151.896036]  do_syscall_64+0x163/0x190
  [455151.896150]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [455151.896302] RIP: 0033:0x7f69965ba3fb
  [455151.896410] Code: 03 00 00 00 0f 05 48 3d 00 f0 ff ff 77 41 c3 48 83 ec 
18 89 7c 24 0c e8 f3 fb ff ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 
00 f0 ff ff 77 2f 44 89 c7 89 44 24 0c e8 31 fc ff ff 8b 44
  [455151.896975] RSP: 002b:7ffdff14b350 EFLAGS: 0293 ORIG_RAX: 
0003
  [455151.897201] RAX:  RBX: 557fe0875e50 RCX: 
7f69965ba3fb
  [455151.897412] RDX: 557fe0748f40 RSI: 0001 RDI: 
002b
  [455151.897637] RBP: 557fe0887460 R08:  R09: 

  [455151.904390] R10: 0032 R11: 0293 R12: 
557fe0875e50
  [455151.911165] R13: 0001 R14: 557fe09efc10 R15: 
557fe0747900

  I didn't find any documented details on kernel 5.4 for this bug. I
  have uploaded the logs via ubuntu-bug linux command.

  # uname -a
  Linux kvm03-a1-r01-khi04.rapid.pk 5.4.0-88-generic #99-Ubuntu SMP Thu Sep 23 
17:29:00 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

  # cat /proc/version_signature
  Ubuntu 5.4.0-88.99-generic 5.4.140

  I am using Dell R6525 with EPYC 7532 CPUs.

  Let me know if there is there are more information needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-88-generic 5.4.0-88.99
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Uname: Linux 5.4.0-88-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 28 17:38 seq
   crw-rw 1 root audio 116, 33 Feb 28 17:38 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: pass
  

[Kernel-packages] [Bug 1962485] ProcInterrupts.txt

[Ammad Ali]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1962485/+attachment/5564283/+files/ProcInterrupts.txt

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

Title:
  Kernel Crash [general protection fault:  [#1] SMP NOPTI]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I am running openstack xena release on ubuntu focal. Today my compute
  node running ubuntu focal crashed with due to kernel and dump has been
  generated in /var/crash/. Below is the kernel trace in crash dump.

  [455151.890114] general protection fault:  [#1] SMP NOPTI
  [455151.890285] CPU: 43 PID: 83232 Comm: qemu-system-x86 Kdump: loaded 
Tainted: G   OE 5.4.0-88-generic #99-Ubuntu
  [455151.890612] Hardware name: Dell Inc. PowerEdge R6525/X, BIOS 2.5.6 
10/06/2021
  [455151.890842] RIP: 0010:count_subheaders.part.0+0x26/0x60
  [455151.890998] Code: 00 00 00 90 0f 1f 44 00 00 48 83 3f 00 74 4d 55 48 89 
e5 41 55 45 31 ed 41 54 45 31 e4 53 48 89 fb 48 8b 7b 18 48 85 ff 74 23 <48> 83 
3f 00 74 25 e8 cf ff ff ff 41 
  01 c5 48 83 c3 40 48 83 3b 00
  [455151.891552] RSP: 0018:a6b477487b88 EFLAGS: 00010202
  [455151.891707] RAX:  RBX: 9387c594f280 RCX: 

  [455151.891918] RDX: 0060 RSI: 9390702a72c0 RDI: 
0314a8c0f1b16f3e
  [455151.892130] RBP: a6b477487ba0 R08:  R09: 
bc6ed7f0
  [455151.892341] R10: a6b477487cd0 R11: 0001 R12: 

  [455151.892552] R13:  R14: 9391e5684000 R15: 
bd5f9880
  [455151.892767] FS:  7f69950c75c0() GS:9391feac() 
knlGS:
  [455151.893016] CS:  0010 DS:  ES:  CR0: 80050033
  [455151.893207] CR2: 7f61e9e45000 CR3: 017c54afa000 CR4: 
00340ee0
  [455151.893434] Call Trace:
  [455151.893514]  count_subheaders.part.0+0x31/0x60
  [455151.893646]  unregister_sysctl_table+0x30/0x90
  [455151.893781]  unregister_net_sysctl_table+0xe/0x10
  [455151.893922]  __devinet_sysctl_unregister.isra.0+0x2c/0x60
  [455151.894082]  devinet_sysctl_unregister+0x29/0x40
  [455151.894220]  inetdev_event+0x1e8/0x560
  [455151.894334]  ? skb_dequeue+0x5f/0x70
  [455151.89]  notifier_call_chain+0x55/0x80
  [455151.894565]  ? notifier_call_chain+0x55/0x80
  [455151.894693]  raw_notifier_call_chain+0x16/0x20
  [455151.894829]  call_netdevice_notifiers_info+0x2e/0x60
  [455151.894983]  ? tun_show_owner+0x60/0x60
  [455151.895098]  rollback_registered_many+0x36e/0x520
  [455151.895239]  unregister_netdevice_queue+0x94/0x120
  [455151.895383]  __tun_detach+0x421/0x430
  [455151.895495]  tun_chr_close+0x3a/0x70
  [455151.895605]  __fput+0xcc/0x260
  [455151.895698]  fput+0xe/0x10
  [455151.895792]  task_work_run+0x8f/0xb0
  [455151.895903]  exit_to_usermode_loop+0x131/0x160
  [455151.896036]  do_syscall_64+0x163/0x190
  [455151.896150]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [455151.896302] RIP: 0033:0x7f69965ba3fb
  [455151.896410] Code: 03 00 00 00 0f 05 48 3d 00 f0 ff ff 77 41 c3 48 83 ec 
18 89 7c 24 0c e8 f3 fb ff ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 
00 f0 ff ff 77 2f 44 89 c7 89 44 24 0c e8 31 fc ff ff 8b 44
  [455151.896975] RSP: 002b:7ffdff14b350 EFLAGS: 0293 ORIG_RAX: 
0003
  [455151.897201] RAX:  RBX: 557fe0875e50 RCX: 
7f69965ba3fb
  [455151.897412] RDX: 557fe0748f40 RSI: 0001 RDI: 
002b
  [455151.897637] RBP: 557fe0887460 R08:  R09: 

  [455151.904390] R10: 0032 R11: 0293 R12: 
557fe0875e50
  [455151.911165] R13: 0001 R14: 557fe09efc10 R15: 
557fe0747900

  I didn't find any documented details on kernel 5.4 for this bug. I
  have uploaded the logs via ubuntu-bug linux command.

  # uname -a
  Linux kvm03-a1-r01-khi04.rapid.pk 5.4.0-88-generic #99-Ubuntu SMP Thu Sep 23 
17:29:00 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

  # cat /proc/version_signature
  Ubuntu 5.4.0-88.99-generic 5.4.140

  I am using Dell R6525 with EPYC 7532 CPUs.

  Let me know if there is there are more information needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-88-generic 5.4.0-88.99
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Uname: Linux 5.4.0-88-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 28 17:38 seq
   crw-rw 1 root audio 116, 33 Feb 28 17:38 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  

[Kernel-packages] [Bug 1962485] Lspci-vt.txt

[Ammad Ali]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1962485/+attachment/5564277/+files/Lspci-vt.txt

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

Title:
  Kernel Crash [general protection fault:  [#1] SMP NOPTI]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I am running openstack xena release on ubuntu focal. Today my compute
  node running ubuntu focal crashed with due to kernel and dump has been
  generated in /var/crash/. Below is the kernel trace in crash dump.

  [455151.890114] general protection fault:  [#1] SMP NOPTI
  [455151.890285] CPU: 43 PID: 83232 Comm: qemu-system-x86 Kdump: loaded 
Tainted: G   OE 5.4.0-88-generic #99-Ubuntu
  [455151.890612] Hardware name: Dell Inc. PowerEdge R6525/X, BIOS 2.5.6 
10/06/2021
  [455151.890842] RIP: 0010:count_subheaders.part.0+0x26/0x60
  [455151.890998] Code: 00 00 00 90 0f 1f 44 00 00 48 83 3f 00 74 4d 55 48 89 
e5 41 55 45 31 ed 41 54 45 31 e4 53 48 89 fb 48 8b 7b 18 48 85 ff 74 23 <48> 83 
3f 00 74 25 e8 cf ff ff ff 41 
  01 c5 48 83 c3 40 48 83 3b 00
  [455151.891552] RSP: 0018:a6b477487b88 EFLAGS: 00010202
  [455151.891707] RAX:  RBX: 9387c594f280 RCX: 

  [455151.891918] RDX: 0060 RSI: 9390702a72c0 RDI: 
0314a8c0f1b16f3e
  [455151.892130] RBP: a6b477487ba0 R08:  R09: 
bc6ed7f0
  [455151.892341] R10: a6b477487cd0 R11: 0001 R12: 

  [455151.892552] R13:  R14: 9391e5684000 R15: 
bd5f9880
  [455151.892767] FS:  7f69950c75c0() GS:9391feac() 
knlGS:
  [455151.893016] CS:  0010 DS:  ES:  CR0: 80050033
  [455151.893207] CR2: 7f61e9e45000 CR3: 017c54afa000 CR4: 
00340ee0
  [455151.893434] Call Trace:
  [455151.893514]  count_subheaders.part.0+0x31/0x60
  [455151.893646]  unregister_sysctl_table+0x30/0x90
  [455151.893781]  unregister_net_sysctl_table+0xe/0x10
  [455151.893922]  __devinet_sysctl_unregister.isra.0+0x2c/0x60
  [455151.894082]  devinet_sysctl_unregister+0x29/0x40
  [455151.894220]  inetdev_event+0x1e8/0x560
  [455151.894334]  ? skb_dequeue+0x5f/0x70
  [455151.89]  notifier_call_chain+0x55/0x80
  [455151.894565]  ? notifier_call_chain+0x55/0x80
  [455151.894693]  raw_notifier_call_chain+0x16/0x20
  [455151.894829]  call_netdevice_notifiers_info+0x2e/0x60
  [455151.894983]  ? tun_show_owner+0x60/0x60
  [455151.895098]  rollback_registered_many+0x36e/0x520
  [455151.895239]  unregister_netdevice_queue+0x94/0x120
  [455151.895383]  __tun_detach+0x421/0x430
  [455151.895495]  tun_chr_close+0x3a/0x70
  [455151.895605]  __fput+0xcc/0x260
  [455151.895698]  fput+0xe/0x10
  [455151.895792]  task_work_run+0x8f/0xb0
  [455151.895903]  exit_to_usermode_loop+0x131/0x160
  [455151.896036]  do_syscall_64+0x163/0x190
  [455151.896150]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [455151.896302] RIP: 0033:0x7f69965ba3fb
  [455151.896410] Code: 03 00 00 00 0f 05 48 3d 00 f0 ff ff 77 41 c3 48 83 ec 
18 89 7c 24 0c e8 f3 fb ff ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 
00 f0 ff ff 77 2f 44 89 c7 89 44 24 0c e8 31 fc ff ff 8b 44
  [455151.896975] RSP: 002b:7ffdff14b350 EFLAGS: 0293 ORIG_RAX: 
0003
  [455151.897201] RAX:  RBX: 557fe0875e50 RCX: 
7f69965ba3fb
  [455151.897412] RDX: 557fe0748f40 RSI: 0001 RDI: 
002b
  [455151.897637] RBP: 557fe0887460 R08:  R09: 

  [455151.904390] R10: 0032 R11: 0293 R12: 
557fe0875e50
  [455151.911165] R13: 0001 R14: 557fe09efc10 R15: 
557fe0747900

  I didn't find any documented details on kernel 5.4 for this bug. I
  have uploaded the logs via ubuntu-bug linux command.

  # uname -a
  Linux kvm03-a1-r01-khi04.rapid.pk 5.4.0-88-generic #99-Ubuntu SMP Thu Sep 23 
17:29:00 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

  # cat /proc/version_signature
  Ubuntu 5.4.0-88.99-generic 5.4.140

  I am using Dell R6525 with EPYC 7532 CPUs.

  Let me know if there is there are more information needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-88-generic 5.4.0-88.99
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Uname: Linux 5.4.0-88-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 28 17:38 seq
   crw-rw 1 root audio 116, 33 Feb 28 17:38 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: pass
  

[Kernel-packages] [Bug 1962485] WifiSyslog.txt

[Ammad Ali]

apport information

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

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

Title:
  Kernel Crash [general protection fault:  [#1] SMP NOPTI]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I am running openstack xena release on ubuntu focal. Today my compute
  node running ubuntu focal crashed with due to kernel and dump has been
  generated in /var/crash/. Below is the kernel trace in crash dump.

  [455151.890114] general protection fault:  [#1] SMP NOPTI
  [455151.890285] CPU: 43 PID: 83232 Comm: qemu-system-x86 Kdump: loaded 
Tainted: G   OE 5.4.0-88-generic #99-Ubuntu
  [455151.890612] Hardware name: Dell Inc. PowerEdge R6525/X, BIOS 2.5.6 
10/06/2021
  [455151.890842] RIP: 0010:count_subheaders.part.0+0x26/0x60
  [455151.890998] Code: 00 00 00 90 0f 1f 44 00 00 48 83 3f 00 74 4d 55 48 89 
e5 41 55 45 31 ed 41 54 45 31 e4 53 48 89 fb 48 8b 7b 18 48 85 ff 74 23 <48> 83 
3f 00 74 25 e8 cf ff ff ff 41 
  01 c5 48 83 c3 40 48 83 3b 00
  [455151.891552] RSP: 0018:a6b477487b88 EFLAGS: 00010202
  [455151.891707] RAX:  RBX: 9387c594f280 RCX: 

  [455151.891918] RDX: 0060 RSI: 9390702a72c0 RDI: 
0314a8c0f1b16f3e
  [455151.892130] RBP: a6b477487ba0 R08:  R09: 
bc6ed7f0
  [455151.892341] R10: a6b477487cd0 R11: 0001 R12: 

  [455151.892552] R13:  R14: 9391e5684000 R15: 
bd5f9880
  [455151.892767] FS:  7f69950c75c0() GS:9391feac() 
knlGS:
  [455151.893016] CS:  0010 DS:  ES:  CR0: 80050033
  [455151.893207] CR2: 7f61e9e45000 CR3: 017c54afa000 CR4: 
00340ee0
  [455151.893434] Call Trace:
  [455151.893514]  count_subheaders.part.0+0x31/0x60
  [455151.893646]  unregister_sysctl_table+0x30/0x90
  [455151.893781]  unregister_net_sysctl_table+0xe/0x10
  [455151.893922]  __devinet_sysctl_unregister.isra.0+0x2c/0x60
  [455151.894082]  devinet_sysctl_unregister+0x29/0x40
  [455151.894220]  inetdev_event+0x1e8/0x560
  [455151.894334]  ? skb_dequeue+0x5f/0x70
  [455151.89]  notifier_call_chain+0x55/0x80
  [455151.894565]  ? notifier_call_chain+0x55/0x80
  [455151.894693]  raw_notifier_call_chain+0x16/0x20
  [455151.894829]  call_netdevice_notifiers_info+0x2e/0x60
  [455151.894983]  ? tun_show_owner+0x60/0x60
  [455151.895098]  rollback_registered_many+0x36e/0x520
  [455151.895239]  unregister_netdevice_queue+0x94/0x120
  [455151.895383]  __tun_detach+0x421/0x430
  [455151.895495]  tun_chr_close+0x3a/0x70
  [455151.895605]  __fput+0xcc/0x260
  [455151.895698]  fput+0xe/0x10
  [455151.895792]  task_work_run+0x8f/0xb0
  [455151.895903]  exit_to_usermode_loop+0x131/0x160
  [455151.896036]  do_syscall_64+0x163/0x190
  [455151.896150]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [455151.896302] RIP: 0033:0x7f69965ba3fb
  [455151.896410] Code: 03 00 00 00 0f 05 48 3d 00 f0 ff ff 77 41 c3 48 83 ec 
18 89 7c 24 0c e8 f3 fb ff ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 
00 f0 ff ff 77 2f 44 89 c7 89 44 24 0c e8 31 fc ff ff 8b 44
  [455151.896975] RSP: 002b:7ffdff14b350 EFLAGS: 0293 ORIG_RAX: 
0003
  [455151.897201] RAX:  RBX: 557fe0875e50 RCX: 
7f69965ba3fb
  [455151.897412] RDX: 557fe0748f40 RSI: 0001 RDI: 
002b
  [455151.897637] RBP: 557fe0887460 R08:  R09: 

  [455151.904390] R10: 0032 R11: 0293 R12: 
557fe0875e50
  [455151.911165] R13: 0001 R14: 557fe09efc10 R15: 
557fe0747900

  I didn't find any documented details on kernel 5.4 for this bug. I
  have uploaded the logs via ubuntu-bug linux command.

  # uname -a
  Linux kvm03-a1-r01-khi04.rapid.pk 5.4.0-88-generic #99-Ubuntu SMP Thu Sep 23 
17:29:00 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

  # cat /proc/version_signature
  Ubuntu 5.4.0-88.99-generic 5.4.140

  I am using Dell R6525 with EPYC 7532 CPUs.

  Let me know if there is there are more information needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-88-generic 5.4.0-88.99
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Uname: Linux 5.4.0-88-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 28 17:38 seq
   crw-rw 1 root audio 116, 33 Feb 28 17:38 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: 

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

[Ammad Ali]

apport information

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

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

Title:
  Kernel Crash [general protection fault:  [#1] SMP NOPTI]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I am running openstack xena release on ubuntu focal. Today my compute
  node running ubuntu focal crashed with due to kernel and dump has been
  generated in /var/crash/. Below is the kernel trace in crash dump.

  [455151.890114] general protection fault:  [#1] SMP NOPTI
  [455151.890285] CPU: 43 PID: 83232 Comm: qemu-system-x86 Kdump: loaded 
Tainted: G   OE 5.4.0-88-generic #99-Ubuntu
  [455151.890612] Hardware name: Dell Inc. PowerEdge R6525/X, BIOS 2.5.6 
10/06/2021
  [455151.890842] RIP: 0010:count_subheaders.part.0+0x26/0x60
  [455151.890998] Code: 00 00 00 90 0f 1f 44 00 00 48 83 3f 00 74 4d 55 48 89 
e5 41 55 45 31 ed 41 54 45 31 e4 53 48 89 fb 48 8b 7b 18 48 85 ff 74 23 <48> 83 
3f 00 74 25 e8 cf ff ff ff 41 
  01 c5 48 83 c3 40 48 83 3b 00
  [455151.891552] RSP: 0018:a6b477487b88 EFLAGS: 00010202
  [455151.891707] RAX:  RBX: 9387c594f280 RCX: 

  [455151.891918] RDX: 0060 RSI: 9390702a72c0 RDI: 
0314a8c0f1b16f3e
  [455151.892130] RBP: a6b477487ba0 R08:  R09: 
bc6ed7f0
  [455151.892341] R10: a6b477487cd0 R11: 0001 R12: 

  [455151.892552] R13:  R14: 9391e5684000 R15: 
bd5f9880
  [455151.892767] FS:  7f69950c75c0() GS:9391feac() 
knlGS:
  [455151.893016] CS:  0010 DS:  ES:  CR0: 80050033
  [455151.893207] CR2: 7f61e9e45000 CR3: 017c54afa000 CR4: 
00340ee0
  [455151.893434] Call Trace:
  [455151.893514]  count_subheaders.part.0+0x31/0x60
  [455151.893646]  unregister_sysctl_table+0x30/0x90
  [455151.893781]  unregister_net_sysctl_table+0xe/0x10
  [455151.893922]  __devinet_sysctl_unregister.isra.0+0x2c/0x60
  [455151.894082]  devinet_sysctl_unregister+0x29/0x40
  [455151.894220]  inetdev_event+0x1e8/0x560
  [455151.894334]  ? skb_dequeue+0x5f/0x70
  [455151.89]  notifier_call_chain+0x55/0x80
  [455151.894565]  ? notifier_call_chain+0x55/0x80
  [455151.894693]  raw_notifier_call_chain+0x16/0x20
  [455151.894829]  call_netdevice_notifiers_info+0x2e/0x60
  [455151.894983]  ? tun_show_owner+0x60/0x60
  [455151.895098]  rollback_registered_many+0x36e/0x520
  [455151.895239]  unregister_netdevice_queue+0x94/0x120
  [455151.895383]  __tun_detach+0x421/0x430
  [455151.895495]  tun_chr_close+0x3a/0x70
  [455151.895605]  __fput+0xcc/0x260
  [455151.895698]  fput+0xe/0x10
  [455151.895792]  task_work_run+0x8f/0xb0
  [455151.895903]  exit_to_usermode_loop+0x131/0x160
  [455151.896036]  do_syscall_64+0x163/0x190
  [455151.896150]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [455151.896302] RIP: 0033:0x7f69965ba3fb
  [455151.896410] Code: 03 00 00 00 0f 05 48 3d 00 f0 ff ff 77 41 c3 48 83 ec 
18 89 7c 24 0c e8 f3 fb ff ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 
00 f0 ff ff 77 2f 44 89 c7 89 44 24 0c e8 31 fc ff ff 8b 44
  [455151.896975] RSP: 002b:7ffdff14b350 EFLAGS: 0293 ORIG_RAX: 
0003
  [455151.897201] RAX:  RBX: 557fe0875e50 RCX: 
7f69965ba3fb
  [455151.897412] RDX: 557fe0748f40 RSI: 0001 RDI: 
002b
  [455151.897637] RBP: 557fe0887460 R08:  R09: 

  [455151.904390] R10: 0032 R11: 0293 R12: 
557fe0875e50
  [455151.911165] R13: 0001 R14: 557fe09efc10 R15: 
557fe0747900

  I didn't find any documented details on kernel 5.4 for this bug. I
  have uploaded the logs via ubuntu-bug linux command.

  # uname -a
  Linux kvm03-a1-r01-khi04.rapid.pk 5.4.0-88-generic #99-Ubuntu SMP Thu Sep 23 
17:29:00 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

  # cat /proc/version_signature
  Ubuntu 5.4.0-88.99-generic 5.4.140

  I am using Dell R6525 with EPYC 7532 CPUs.

  Let me know if there is there are more information needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-88-generic 5.4.0-88.99
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Uname: Linux 5.4.0-88-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 28 17:38 seq
   crw-rw 1 root audio 116, 33 Feb 28 17:38 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: pass
  Date: 

[Kernel-packages] [Bug 1962485] CurrentDmesg.txt

[Ammad Ali]

apport information

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

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

Title:
  Kernel Crash [general protection fault:  [#1] SMP NOPTI]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I am running openstack xena release on ubuntu focal. Today my compute
  node running ubuntu focal crashed with due to kernel and dump has been
  generated in /var/crash/. Below is the kernel trace in crash dump.

  [455151.890114] general protection fault:  [#1] SMP NOPTI
  [455151.890285] CPU: 43 PID: 83232 Comm: qemu-system-x86 Kdump: loaded 
Tainted: G   OE 5.4.0-88-generic #99-Ubuntu
  [455151.890612] Hardware name: Dell Inc. PowerEdge R6525/X, BIOS 2.5.6 
10/06/2021
  [455151.890842] RIP: 0010:count_subheaders.part.0+0x26/0x60
  [455151.890998] Code: 00 00 00 90 0f 1f 44 00 00 48 83 3f 00 74 4d 55 48 89 
e5 41 55 45 31 ed 41 54 45 31 e4 53 48 89 fb 48 8b 7b 18 48 85 ff 74 23 <48> 83 
3f 00 74 25 e8 cf ff ff ff 41 
  01 c5 48 83 c3 40 48 83 3b 00
  [455151.891552] RSP: 0018:a6b477487b88 EFLAGS: 00010202
  [455151.891707] RAX:  RBX: 9387c594f280 RCX: 

  [455151.891918] RDX: 0060 RSI: 9390702a72c0 RDI: 
0314a8c0f1b16f3e
  [455151.892130] RBP: a6b477487ba0 R08:  R09: 
bc6ed7f0
  [455151.892341] R10: a6b477487cd0 R11: 0001 R12: 

  [455151.892552] R13:  R14: 9391e5684000 R15: 
bd5f9880
  [455151.892767] FS:  7f69950c75c0() GS:9391feac() 
knlGS:
  [455151.893016] CS:  0010 DS:  ES:  CR0: 80050033
  [455151.893207] CR2: 7f61e9e45000 CR3: 017c54afa000 CR4: 
00340ee0
  [455151.893434] Call Trace:
  [455151.893514]  count_subheaders.part.0+0x31/0x60
  [455151.893646]  unregister_sysctl_table+0x30/0x90
  [455151.893781]  unregister_net_sysctl_table+0xe/0x10
  [455151.893922]  __devinet_sysctl_unregister.isra.0+0x2c/0x60
  [455151.894082]  devinet_sysctl_unregister+0x29/0x40
  [455151.894220]  inetdev_event+0x1e8/0x560
  [455151.894334]  ? skb_dequeue+0x5f/0x70
  [455151.89]  notifier_call_chain+0x55/0x80
  [455151.894565]  ? notifier_call_chain+0x55/0x80
  [455151.894693]  raw_notifier_call_chain+0x16/0x20
  [455151.894829]  call_netdevice_notifiers_info+0x2e/0x60
  [455151.894983]  ? tun_show_owner+0x60/0x60
  [455151.895098]  rollback_registered_many+0x36e/0x520
  [455151.895239]  unregister_netdevice_queue+0x94/0x120
  [455151.895383]  __tun_detach+0x421/0x430
  [455151.895495]  tun_chr_close+0x3a/0x70
  [455151.895605]  __fput+0xcc/0x260
  [455151.895698]  fput+0xe/0x10
  [455151.895792]  task_work_run+0x8f/0xb0
  [455151.895903]  exit_to_usermode_loop+0x131/0x160
  [455151.896036]  do_syscall_64+0x163/0x190
  [455151.896150]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [455151.896302] RIP: 0033:0x7f69965ba3fb
  [455151.896410] Code: 03 00 00 00 0f 05 48 3d 00 f0 ff ff 77 41 c3 48 83 ec 
18 89 7c 24 0c e8 f3 fb ff ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 
00 f0 ff ff 77 2f 44 89 c7 89 44 24 0c e8 31 fc ff ff 8b 44
  [455151.896975] RSP: 002b:7ffdff14b350 EFLAGS: 0293 ORIG_RAX: 
0003
  [455151.897201] RAX:  RBX: 557fe0875e50 RCX: 
7f69965ba3fb
  [455151.897412] RDX: 557fe0748f40 RSI: 0001 RDI: 
002b
  [455151.897637] RBP: 557fe0887460 R08:  R09: 

  [455151.904390] R10: 0032 R11: 0293 R12: 
557fe0875e50
  [455151.911165] R13: 0001 R14: 557fe09efc10 R15: 
557fe0747900

  I didn't find any documented details on kernel 5.4 for this bug. I
  have uploaded the logs via ubuntu-bug linux command.

  # uname -a
  Linux kvm03-a1-r01-khi04.rapid.pk 5.4.0-88-generic #99-Ubuntu SMP Thu Sep 23 
17:29:00 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

  # cat /proc/version_signature
  Ubuntu 5.4.0-88.99-generic 5.4.140

  I am using Dell R6525 with EPYC 7532 CPUs.

  Let me know if there is there are more information needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-88-generic 5.4.0-88.99
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Uname: Linux 5.4.0-88-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 28 17:38 seq
   crw-rw 1 root audio 116, 33 Feb 28 17:38 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  

[Kernel-packages] [Bug 1962485] Lsusb.txt

[Ammad Ali]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1962485/+attachment/5564278/+files/Lsusb.txt

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

Title:
  Kernel Crash [general protection fault:  [#1] SMP NOPTI]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I am running openstack xena release on ubuntu focal. Today my compute
  node running ubuntu focal crashed with due to kernel and dump has been
  generated in /var/crash/. Below is the kernel trace in crash dump.

  [455151.890114] general protection fault:  [#1] SMP NOPTI
  [455151.890285] CPU: 43 PID: 83232 Comm: qemu-system-x86 Kdump: loaded 
Tainted: G   OE 5.4.0-88-generic #99-Ubuntu
  [455151.890612] Hardware name: Dell Inc. PowerEdge R6525/X, BIOS 2.5.6 
10/06/2021
  [455151.890842] RIP: 0010:count_subheaders.part.0+0x26/0x60
  [455151.890998] Code: 00 00 00 90 0f 1f 44 00 00 48 83 3f 00 74 4d 55 48 89 
e5 41 55 45 31 ed 41 54 45 31 e4 53 48 89 fb 48 8b 7b 18 48 85 ff 74 23 <48> 83 
3f 00 74 25 e8 cf ff ff ff 41 
  01 c5 48 83 c3 40 48 83 3b 00
  [455151.891552] RSP: 0018:a6b477487b88 EFLAGS: 00010202
  [455151.891707] RAX:  RBX: 9387c594f280 RCX: 

  [455151.891918] RDX: 0060 RSI: 9390702a72c0 RDI: 
0314a8c0f1b16f3e
  [455151.892130] RBP: a6b477487ba0 R08:  R09: 
bc6ed7f0
  [455151.892341] R10: a6b477487cd0 R11: 0001 R12: 

  [455151.892552] R13:  R14: 9391e5684000 R15: 
bd5f9880
  [455151.892767] FS:  7f69950c75c0() GS:9391feac() 
knlGS:
  [455151.893016] CS:  0010 DS:  ES:  CR0: 80050033
  [455151.893207] CR2: 7f61e9e45000 CR3: 017c54afa000 CR4: 
00340ee0
  [455151.893434] Call Trace:
  [455151.893514]  count_subheaders.part.0+0x31/0x60
  [455151.893646]  unregister_sysctl_table+0x30/0x90
  [455151.893781]  unregister_net_sysctl_table+0xe/0x10
  [455151.893922]  __devinet_sysctl_unregister.isra.0+0x2c/0x60
  [455151.894082]  devinet_sysctl_unregister+0x29/0x40
  [455151.894220]  inetdev_event+0x1e8/0x560
  [455151.894334]  ? skb_dequeue+0x5f/0x70
  [455151.89]  notifier_call_chain+0x55/0x80
  [455151.894565]  ? notifier_call_chain+0x55/0x80
  [455151.894693]  raw_notifier_call_chain+0x16/0x20
  [455151.894829]  call_netdevice_notifiers_info+0x2e/0x60
  [455151.894983]  ? tun_show_owner+0x60/0x60
  [455151.895098]  rollback_registered_many+0x36e/0x520
  [455151.895239]  unregister_netdevice_queue+0x94/0x120
  [455151.895383]  __tun_detach+0x421/0x430
  [455151.895495]  tun_chr_close+0x3a/0x70
  [455151.895605]  __fput+0xcc/0x260
  [455151.895698]  fput+0xe/0x10
  [455151.895792]  task_work_run+0x8f/0xb0
  [455151.895903]  exit_to_usermode_loop+0x131/0x160
  [455151.896036]  do_syscall_64+0x163/0x190
  [455151.896150]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [455151.896302] RIP: 0033:0x7f69965ba3fb
  [455151.896410] Code: 03 00 00 00 0f 05 48 3d 00 f0 ff ff 77 41 c3 48 83 ec 
18 89 7c 24 0c e8 f3 fb ff ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 
00 f0 ff ff 77 2f 44 89 c7 89 44 24 0c e8 31 fc ff ff 8b 44
  [455151.896975] RSP: 002b:7ffdff14b350 EFLAGS: 0293 ORIG_RAX: 
0003
  [455151.897201] RAX:  RBX: 557fe0875e50 RCX: 
7f69965ba3fb
  [455151.897412] RDX: 557fe0748f40 RSI: 0001 RDI: 
002b
  [455151.897637] RBP: 557fe0887460 R08:  R09: 

  [455151.904390] R10: 0032 R11: 0293 R12: 
557fe0875e50
  [455151.911165] R13: 0001 R14: 557fe09efc10 R15: 
557fe0747900

  I didn't find any documented details on kernel 5.4 for this bug. I
  have uploaded the logs via ubuntu-bug linux command.

  # uname -a
  Linux kvm03-a1-r01-khi04.rapid.pk 5.4.0-88-generic #99-Ubuntu SMP Thu Sep 23 
17:29:00 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

  # cat /proc/version_signature
  Ubuntu 5.4.0-88.99-generic 5.4.140

  I am using Dell R6525 with EPYC 7532 CPUs.

  Let me know if there is there are more information needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-88-generic 5.4.0-88.99
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Uname: Linux 5.4.0-88-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 28 17:38 seq
   crw-rw 1 root audio 116, 33 Feb 28 17:38 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: pass
  Date: 

[Kernel-packages] [Bug 1962485] Re: Kernel Crash [general protection fault: 0000 [#1] SMP NOPTI]

[Ammad Ali]

apport information

** Tags added: apport-collected

** Description changed:

  Hi,
  
  I am running openstack xena release on ubuntu focal. Today my compute
  node running ubuntu focal crashed with due to kernel and dump has been
  generated in /var/crash/. Below is the kernel trace in crash dump.
  
  [455151.890114] general protection fault:  [#1] SMP NOPTI
  [455151.890285] CPU: 43 PID: 83232 Comm: qemu-system-x86 Kdump: loaded 
Tainted: G   OE 5.4.0-88-generic #99-Ubuntu
  [455151.890612] Hardware name: Dell Inc. PowerEdge R6525/X, BIOS 2.5.6 
10/06/2021
  [455151.890842] RIP: 0010:count_subheaders.part.0+0x26/0x60
  [455151.890998] Code: 00 00 00 90 0f 1f 44 00 00 48 83 3f 00 74 4d 55 48 89 
e5 41 55 45 31 ed 41 54 45 31 e4 53 48 89 fb 48 8b 7b 18 48 85 ff 74 23 <48> 83 
3f 00 74 25 e8 cf ff ff ff 41 
  01 c5 48 83 c3 40 48 83 3b 00
  [455151.891552] RSP: 0018:a6b477487b88 EFLAGS: 00010202
  [455151.891707] RAX:  RBX: 9387c594f280 RCX: 

  [455151.891918] RDX: 0060 RSI: 9390702a72c0 RDI: 
0314a8c0f1b16f3e
  [455151.892130] RBP: a6b477487ba0 R08:  R09: 
bc6ed7f0
  [455151.892341] R10: a6b477487cd0 R11: 0001 R12: 

  [455151.892552] R13:  R14: 9391e5684000 R15: 
bd5f9880
  [455151.892767] FS:  7f69950c75c0() GS:9391feac() 
knlGS:
  [455151.893016] CS:  0010 DS:  ES:  CR0: 80050033
  [455151.893207] CR2: 7f61e9e45000 CR3: 017c54afa000 CR4: 
00340ee0
  [455151.893434] Call Trace:
  [455151.893514]  count_subheaders.part.0+0x31/0x60
  [455151.893646]  unregister_sysctl_table+0x30/0x90
  [455151.893781]  unregister_net_sysctl_table+0xe/0x10
  [455151.893922]  __devinet_sysctl_unregister.isra.0+0x2c/0x60
  [455151.894082]  devinet_sysctl_unregister+0x29/0x40
  [455151.894220]  inetdev_event+0x1e8/0x560
  [455151.894334]  ? skb_dequeue+0x5f/0x70
  [455151.89]  notifier_call_chain+0x55/0x80
  [455151.894565]  ? notifier_call_chain+0x55/0x80
  [455151.894693]  raw_notifier_call_chain+0x16/0x20
  [455151.894829]  call_netdevice_notifiers_info+0x2e/0x60
  [455151.894983]  ? tun_show_owner+0x60/0x60
  [455151.895098]  rollback_registered_many+0x36e/0x520
  [455151.895239]  unregister_netdevice_queue+0x94/0x120
  [455151.895383]  __tun_detach+0x421/0x430
  [455151.895495]  tun_chr_close+0x3a/0x70
  [455151.895605]  __fput+0xcc/0x260
  [455151.895698]  fput+0xe/0x10
  [455151.895792]  task_work_run+0x8f/0xb0
  [455151.895903]  exit_to_usermode_loop+0x131/0x160
  [455151.896036]  do_syscall_64+0x163/0x190
  [455151.896150]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [455151.896302] RIP: 0033:0x7f69965ba3fb
  [455151.896410] Code: 03 00 00 00 0f 05 48 3d 00 f0 ff ff 77 41 c3 48 83 ec 
18 89 7c 24 0c e8 f3 fb ff ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 
00 f0 ff ff 77 2f 44 89 c7 89 44 24 0c e8 31 fc ff ff 8b 44
  [455151.896975] RSP: 002b:7ffdff14b350 EFLAGS: 0293 ORIG_RAX: 
0003
  [455151.897201] RAX:  RBX: 557fe0875e50 RCX: 
7f69965ba3fb
  [455151.897412] RDX: 557fe0748f40 RSI: 0001 RDI: 
002b
  [455151.897637] RBP: 557fe0887460 R08:  R09: 

  [455151.904390] R10: 0032 R11: 0293 R12: 
557fe0875e50
  [455151.911165] R13: 0001 R14: 557fe09efc10 R15: 
557fe0747900
  
  I didn't find any documented details on kernel 5.4 for this bug. I have
  uploaded the logs via ubuntu-bug linux command.
  
  # uname -a
  Linux kvm03-a1-r01-khi04.rapid.pk 5.4.0-88-generic #99-Ubuntu SMP Thu Sep 23 
17:29:00 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  
  # cat /proc/version_signature
  Ubuntu 5.4.0-88.99-generic 5.4.140
  
  I am using Dell R6525 with EPYC 7532 CPUs.
  
  Let me know if there is there are more information needed.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-88-generic 5.4.0-88.99
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Uname: Linux 5.4.0-88-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 28 17:38 seq
   crw-rw 1 root audio 116, 33 Feb 28 17:38 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: pass
  Date: Mon Feb 28 21:20:20 2022
  InstallationDate: Installed on 2021-07-29 (214 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Dell Inc. PowerEdge R6525
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color

[Kernel-packages] [Bug 1962485] [NEW] Kernel Crash [general protection fault: 0000 [#1] SMP NOPTI]

[Ammad Ali]

Public bug reported:

Hi,

I am running openstack xena release on ubuntu focal. Today my compute
node running ubuntu focal crashed with due to kernel and dump has been
generated in /var/crash/. Below is the kernel trace in crash dump.

[455151.890114] general protection fault:  [#1] SMP NOPTI
[455151.890285] CPU: 43 PID: 83232 Comm: qemu-system-x86 Kdump: loaded Tainted: 
G   OE 5.4.0-88-generic #99-Ubuntu
[455151.890612] Hardware name: Dell Inc. PowerEdge R6525/X, BIOS 2.5.6 
10/06/2021
[455151.890842] RIP: 0010:count_subheaders.part.0+0x26/0x60
[455151.890998] Code: 00 00 00 90 0f 1f 44 00 00 48 83 3f 00 74 4d 55 48 89 e5 
41 55 45 31 ed 41 54 45 31 e4 53 48 89 fb 48 8b 7b 18 48 85 ff 74 23 <48> 83 3f 
00 74 25 e8 cf ff ff ff 41 
01 c5 48 83 c3 40 48 83 3b 00
[455151.891552] RSP: 0018:a6b477487b88 EFLAGS: 00010202
[455151.891707] RAX:  RBX: 9387c594f280 RCX: 

[455151.891918] RDX: 0060 RSI: 9390702a72c0 RDI: 
0314a8c0f1b16f3e
[455151.892130] RBP: a6b477487ba0 R08:  R09: 
bc6ed7f0
[455151.892341] R10: a6b477487cd0 R11: 0001 R12: 

[455151.892552] R13:  R14: 9391e5684000 R15: 
bd5f9880
[455151.892767] FS:  7f69950c75c0() GS:9391feac() 
knlGS:
[455151.893016] CS:  0010 DS:  ES:  CR0: 80050033
[455151.893207] CR2: 7f61e9e45000 CR3: 017c54afa000 CR4: 
00340ee0
[455151.893434] Call Trace:
[455151.893514]  count_subheaders.part.0+0x31/0x60
[455151.893646]  unregister_sysctl_table+0x30/0x90
[455151.893781]  unregister_net_sysctl_table+0xe/0x10
[455151.893922]  __devinet_sysctl_unregister.isra.0+0x2c/0x60
[455151.894082]  devinet_sysctl_unregister+0x29/0x40
[455151.894220]  inetdev_event+0x1e8/0x560
[455151.894334]  ? skb_dequeue+0x5f/0x70
[455151.89]  notifier_call_chain+0x55/0x80
[455151.894565]  ? notifier_call_chain+0x55/0x80
[455151.894693]  raw_notifier_call_chain+0x16/0x20
[455151.894829]  call_netdevice_notifiers_info+0x2e/0x60
[455151.894983]  ? tun_show_owner+0x60/0x60
[455151.895098]  rollback_registered_many+0x36e/0x520
[455151.895239]  unregister_netdevice_queue+0x94/0x120
[455151.895383]  __tun_detach+0x421/0x430
[455151.895495]  tun_chr_close+0x3a/0x70
[455151.895605]  __fput+0xcc/0x260
[455151.895698]  fput+0xe/0x10
[455151.895792]  task_work_run+0x8f/0xb0
[455151.895903]  exit_to_usermode_loop+0x131/0x160
[455151.896036]  do_syscall_64+0x163/0x190
[455151.896150]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[455151.896302] RIP: 0033:0x7f69965ba3fb
[455151.896410] Code: 03 00 00 00 0f 05 48 3d 00 f0 ff ff 77 41 c3 48 83 ec 18 
89 7c 24 0c e8 f3 fb ff ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 2f 44 89 c7 89 44 24 0c e8 31 fc ff ff 8b 44
[455151.896975] RSP: 002b:7ffdff14b350 EFLAGS: 0293 ORIG_RAX: 
0003
[455151.897201] RAX:  RBX: 557fe0875e50 RCX: 
7f69965ba3fb
[455151.897412] RDX: 557fe0748f40 RSI: 0001 RDI: 
002b
[455151.897637] RBP: 557fe0887460 R08:  R09: 

[455151.904390] R10: 0032 R11: 0293 R12: 
557fe0875e50
[455151.911165] R13: 0001 R14: 557fe09efc10 R15: 
557fe0747900

I didn't find any documented details on kernel 5.4 for this bug. I have
uploaded the logs via ubuntu-bug linux command.

# uname -a
Linux kvm03-a1-r01-khi04.rapid.pk 5.4.0-88-generic #99-Ubuntu SMP Thu Sep 23 
17:29:00 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

# cat /proc/version_signature
Ubuntu 5.4.0-88.99-generic 5.4.140

I am using Dell R6525 with EPYC 7532 CPUs.

Let me know if there is there are more information needed.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-88-generic 5.4.0-88.99
ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
Uname: Linux 5.4.0-88-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Feb 28 17:38 seq
 crw-rw 1 root audio 116, 33 Feb 28 17:38 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: pass
Date: Mon Feb 28 21:20:20 2022
InstallationDate: Installed on 2021-07-29 (214 days ago)
InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Dell Inc. PowerEdge R6525
PciMultimedia:
 
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-88-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro iommu=pt intel_iommu=on swapaccount=1 

[Kernel-packages] [Bug 1939347] Re: Ubuntu 20.04 freeze since kernel 5.11

[Inayat Ali]

#55 kapper1224 fixed it for me.
Didn't create or modify any .conf file(think thats for arch only)
Just added the kernel mod param: GRUB_CMDLINE_LINUX="i915.enable_guc=2"
then sudo update-grub and reboot

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

Title:
  Ubuntu 20.04 freeze since kernel 5.11

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since the last kernel update 5.11.0-25-generic, the system freezes in a few 
seconds or minutes, sometimes even on the login screen. 
  The machine is a recent dell latitude 7490. The graphics card is Intel 
Corporation UHD Graphics 620 (rev 07). No multiboot. No problem with the 
previous kernel 5.8.0-63.
  I had the same problem with fedora a few months ago, which forced me to 
switch to ubuntu without any problems so far.  
  Thanks for your help.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  plawrence   1996 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-21 (414 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 1bcf:2b96 Sunplus Innovation Technology Inc. 
Integrated_Webcam_HD
   Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 5880
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7490
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=01fd281b-07d7-45f2-846b-d5b79ed5d431 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-25-generic N/A
   linux-backports-modules-5.11.0-25-generic  N/A
   linux-firmware 1.187.15
  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
  dmi.bios.date: 02/23/2021
  dmi.bios.release: 1.19
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.19.0
  dmi.board.name: 0KP0FT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.0:bd02/23/2021:br1.19:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.product.sku: 081C
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939347/+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 1881319] Re: [Lenovo IdeaPad 5 15ARE05] Touchpad not recognized

[Dolan H. Ali]

Lenovo IdeaPad 5 15ARE05
- Processor: AMD® Ryzen 7 4700u with radeon graphics × 8 
- OS: Ubuntu 21.04
- GNOME: 3.38.5
- Kernel: 5.11.0-22-generic

Main issues:

* Touchpad is not working.

* Finger-print is not working.

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

Title:
  [Lenovo IdeaPad 5 15ARE05] Touchpad not recognized

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad isn't reacting at all

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-33-generic 5.4.0-33.37
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  andreas1223 F pulseaudio
   /dev/snd/controlC0:  andreas1223 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Fri May 29 18:05:01 2020
  InstallationDate: Installed on 2020-05-29 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  MachineType: LENOVO 81YQ
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=4197e5c6-f903-46c3-bc16-3013c5650810 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-33-generic N/A
   linux-backports-modules-5.4.0-33-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E7CN24WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 5 15ARE05
  dmi.modalias: 
dmi:bvnLENOVO:bvrE7CN24WW:bd03/25/2020:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05:
  dmi.product.family: IdeaPad 5 15ARE05
  dmi.product.name: 81YQ
  dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05
  dmi.product.version: IdeaPad 5 15ARE05
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881319/+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 1933259] [NEW] Bluetooth not working/can't turn it on

[Ali Reza hayati]

Public bug reported:

Can't turn on the bluetooth on 21.04. Using bluetoothctl these are the
returns:

```
bluetoothctl
Agent registered
[CHG] Controller 60:14:B3:AC:14:C8 Pairable: yes
[bluetooth]# connect 60:14:B3:AC:14:C8
Device 60:14:B3:AC:14:C8 not available
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.NotReady
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.NotReady
[bluetooth]# 
```

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


** Tags: bluetooth bluetoothctl

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

Title:
  Bluetooth not working/can't turn it on

Status in bluez package in Ubuntu:
  New

Bug description:
  Can't turn on the bluetooth on 21.04. Using bluetoothctl these are the
  returns:

  ```
  bluetoothctl
  Agent registered
  [CHG] Controller 60:14:B3:AC:14:C8 Pairable: yes
  [bluetooth]# connect 60:14:B3:AC:14:C8
  Device 60:14:B3:AC:14:C8 not available
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.NotReady
  [bluetooth]# power on
  Changing power on succeeded
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.NotReady
  [bluetooth]# 
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933259/+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 1933259] Re: Bluetooth not working/can't turn it on

[Ali Reza hayati]

I should mention that bluetooth was working on 20.04 and 20.10 but after
upgrade to 21.04 it doesn't work anymore.

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

Title:
  Bluetooth not working/can't turn it on

Status in bluez package in Ubuntu:
  New

Bug description:
  Can't turn on the bluetooth on 21.04. Using bluetoothctl these are the
  returns:

  ```
  bluetoothctl
  Agent registered
  [CHG] Controller 60:14:B3:AC:14:C8 Pairable: yes
  [bluetooth]# connect 60:14:B3:AC:14:C8
  Device 60:14:B3:AC:14:C8 not available
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.NotReady
  [bluetooth]# power on
  Changing power on succeeded
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.NotReady
  [bluetooth]# 
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933259/+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 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL

[Ali Saidi]

Brian, 7.2.8-1ubuntu1.20.10.2 fix addresses the issue. Thanks!

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

Title:
  crash utility fails on arm64 with  cannot determine VA_BITS_ACTUAL

Status in crash package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in crash source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Invalid
Status in crash source package in Focal:
  Fix Committed
Status in linux source package in Focal:
  Fix Released
Status in crash source package in Groovy:
  Fix Committed
Status in linux source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility
  7.2.8-1ubuntu0.18.04 fails with:

  crash: cannot determine VA_BITS_ACTUAL

  This bug has been addressed upstream and needed patches both in crash
  and kernel.

  Kernel patch :

  commit bbdbc11804ff0b4130e7550113b452e96a74d16e
  Author: Bhupesh Sharma 
  Date:   Thu May 14 00:22:37 2020 +0530
  arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo

  Crash patch :

  commit 1c45cea02df7f947b4296c1dcaefa1024235ef10
  Author: Bhupesh Sharma 
  Date:   Tue Jul 14 01:14:49 2020 +0530

  arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ

  
  Series affected :

  Kenrel : 
  This affects Focal (5.4 kernel)  and Groovy (5.8 kernel).
  Hirsute already contains the commit and kernels prior to 5.3 are not affected.

  Crash :
  The commit is already in Hirsute.
  Groovy, Focal and Bionic are affected.
  In case of Bionic the bug appears only if 5.4 hwe kernel is used.

  [Test Case]

  On an arm64 host which runs the affected releases and kernels after creating 
a crashdump try to open it with crash.
  It will fail with :
  crash: cannot determine VA_BITS_ACTUAL

  [Where problems could occur]

  Kernel patch :

  The kernel patch reads the appropriate cpu register and exports TCR_EL1.T1SZ 
variable in vmcoreinfo. Given that this is a simple operation
  and that this patch landed upstream in 5.9 and no regressions have been 
reported, it is safe to assume that the regression potential is minimal.
  Any potential problem would occur in vmcoreinfo since this is where 
TCR_EL1.T1SZ variable is exported.

  Crash patch :

  This patch renames tcr_el1_t1sz variable to TCR_EL1_T1SZ to be compatible 
with the kernel change above for crash to be able to read it.
  The regression potential is small and any problem would regard reading this 
variable.

  [Other]

  Workaround :
  This bug/change in crash provides a workaround for 5.4+ 
https://github.com/crash-utility/crash/issues/52 kernels.

  While it appears as though it this was fixed it
  https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still
  doesn't seem to work with a 5.4 kernel including. I also tested
  
https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb
  and it exhibits the same problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+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 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL

[Ali Saidi]

Apologies for not getting back to this earlier, it looks like the
verification was already done.

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

Title:
  crash utility fails on arm64 with  cannot determine VA_BITS_ACTUAL

Status in crash package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in crash source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Invalid
Status in crash source package in Focal:
  Fix Committed
Status in linux source package in Focal:
  Fix Released
Status in crash source package in Groovy:
  Fix Committed
Status in linux source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility
  7.2.8-1ubuntu0.18.04 fails with:

  crash: cannot determine VA_BITS_ACTUAL

  This bug has been addressed upstream and needed patches both in crash
  and kernel.

  Kernel patch :

  commit bbdbc11804ff0b4130e7550113b452e96a74d16e
  Author: Bhupesh Sharma 
  Date:   Thu May 14 00:22:37 2020 +0530
  arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo

  Crash patch :

  commit 1c45cea02df7f947b4296c1dcaefa1024235ef10
  Author: Bhupesh Sharma 
  Date:   Tue Jul 14 01:14:49 2020 +0530

  arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ

  
  Series affected :

  Kenrel : 
  This affects Focal (5.4 kernel)  and Groovy (5.8 kernel).
  Hirsute already contains the commit and kernels prior to 5.3 are not affected.

  Crash :
  The commit is already in Hirsute.
  Groovy, Focal and Bionic are affected.
  In case of Bionic the bug appears only if 5.4 hwe kernel is used.

  [Test Case]

  On an arm64 host which runs the affected releases and kernels after creating 
a crashdump try to open it with crash.
  It will fail with :
  crash: cannot determine VA_BITS_ACTUAL

  [Where problems could occur]

  Kernel patch :

  The kernel patch reads the appropriate cpu register and exports TCR_EL1.T1SZ 
variable in vmcoreinfo. Given that this is a simple operation
  and that this patch landed upstream in 5.9 and no regressions have been 
reported, it is safe to assume that the regression potential is minimal.
  Any potential problem would occur in vmcoreinfo since this is where 
TCR_EL1.T1SZ variable is exported.

  Crash patch :

  This patch renames tcr_el1_t1sz variable to TCR_EL1_T1SZ to be compatible 
with the kernel change above for crash to be able to read it.
  The regression potential is small and any problem would regard reading this 
variable.

  [Other]

  Workaround :
  This bug/change in crash provides a workaround for 5.4+ 
https://github.com/crash-utility/crash/issues/52 kernels.

  While it appears as though it this was fixed it
  https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still
  doesn't seem to work with a 5.4 kernel including. I also tested
  
https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb
  and it exhibits the same problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+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 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL

[Ali Saidi]

Apologies for not getting back to this earlier, it looks like the
verification was already done.

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

Title:
  crash utility fails on arm64 with  cannot determine VA_BITS_ACTUAL

Status in crash package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in crash source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Invalid
Status in crash source package in Focal:
  Fix Committed
Status in linux source package in Focal:
  Fix Released
Status in crash source package in Groovy:
  Fix Committed
Status in linux source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility
  7.2.8-1ubuntu0.18.04 fails with:

  crash: cannot determine VA_BITS_ACTUAL

  This bug has been addressed upstream and needed patches both in crash
  and kernel.

  Kernel patch :

  commit bbdbc11804ff0b4130e7550113b452e96a74d16e
  Author: Bhupesh Sharma 
  Date:   Thu May 14 00:22:37 2020 +0530
  arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo

  Crash patch :

  commit 1c45cea02df7f947b4296c1dcaefa1024235ef10
  Author: Bhupesh Sharma 
  Date:   Tue Jul 14 01:14:49 2020 +0530

  arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ

  
  Series affected :

  Kenrel : 
  This affects Focal (5.4 kernel)  and Groovy (5.8 kernel).
  Hirsute already contains the commit and kernels prior to 5.3 are not affected.

  Crash :
  The commit is already in Hirsute.
  Groovy, Focal and Bionic are affected.
  In case of Bionic the bug appears only if 5.4 hwe kernel is used.

  [Test Case]

  On an arm64 host which runs the affected releases and kernels after creating 
a crashdump try to open it with crash.
  It will fail with :
  crash: cannot determine VA_BITS_ACTUAL

  [Where problems could occur]

  Kernel patch :

  The kernel patch reads the appropriate cpu register and exports TCR_EL1.T1SZ 
variable in vmcoreinfo. Given that this is a simple operation
  and that this patch landed upstream in 5.9 and no regressions have been 
reported, it is safe to assume that the regression potential is minimal.
  Any potential problem would occur in vmcoreinfo since this is where 
TCR_EL1.T1SZ variable is exported.

  Crash patch :

  This patch renames tcr_el1_t1sz variable to TCR_EL1_T1SZ to be compatible 
with the kernel change above for crash to be able to read it.
  The regression potential is small and any problem would regard reading this 
variable.

  [Other]

  Workaround :
  This bug/change in crash provides a workaround for 5.4+ 
https://github.com/crash-utility/crash/issues/52 kernels.

  While it appears as though it this was fixed it
  https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still
  doesn't seem to work with a 5.4 kernel including. I also tested
  
https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb
  and it exhibits the same problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+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 1926184] Re: locking/qrwlock: Fix ordering in queued_write_lock_slowpath()

[Ali Saidi]

I've been unable to reproduce the issue with the fixed kernel.

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

Title:
  locking/qrwlock: Fix ordering in queued_write_lock_slowpath()

Status in linux package in Ubuntu:
  In Progress
Status in linux-aws package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux-aws source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Committed
Status in linux-aws source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Committed
Status in linux-aws source package in Groovy:
  Confirmed
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-aws source package in Hirsute:
  Confirmed

Bug description:
  [Impact]
  * Out of order reads can fetch a NULL pointer causing a kernel crash. Affects 
kernels from v4.15 to v5.11.

  [Fix]
  * commit 84a24bf8c52e ("locking/qrwlock: Fix ordering in 
queued_write_lock_slowpath()")

  * For Bionic, we also require an additional patch: commit fcfdfe30e324
  ("locking/barriers: Introduce smp_cond_load_relaxed() and
  atomic_cond_read_relaxed()")

  [Where problems could occur]

  * This is quite a subtle bug. It is more prevalent on arm64. Regression
  possibility seems quite low. The worst impact could be a minor performance 
degradation.

  * Kernels 4.15 / 5.4 / 5.8 / 5.11 were successfully built and booted
  with this patch. Also, by using ftrace we could see that the changed
  function was executed with success multiple times.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926184/+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 1919275] [NEW] crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL

[Ali Saidi]

Public bug reported:

On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility
7.2.8-1ubuntu0.18.04 fails with:

crash: cannot determine VA_BITS_ACTUAL

This bug/change in crash provides a workaround for 5.4+
https://github.com/crash-utility/crash/issues/52 kernels.

While it appears as though it this was fixed it
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still
doesn't seem to work with a 5.4 kernel including. I also tested
https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb
and it exhibits the same problem.

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

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

Title:
  crash utility fails on arm64 with  cannot determine VA_BITS_ACTUAL

Status in crash package in Ubuntu:
  New

Bug description:
  On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility
  7.2.8-1ubuntu0.18.04 fails with:

  crash: cannot determine VA_BITS_ACTUAL

  This bug/change in crash provides a workaround for 5.4+
  https://github.com/crash-utility/crash/issues/52 kernels.

  While it appears as though it this was fixed it
  https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still
  doesn't seem to work with a 5.4 kernel including. I also tested
  
https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb
  and it exhibits the same problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+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 1879214] Re: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported

[Ali Saidi]

Also impacts the bionic 18.04-aws kernel

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

Title:
  Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to
  makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47
  not supported

Status in makedumpfile package in Ubuntu:
  Confirmed
Status in makedumpfile source package in Focal:
  Confirmed
Status in makedumpfile source package in Groovy:
  Confirmed
Status in makedumpfile source package in Hirsute:
  Confirmed

Bug description:
  [Impact]

  On arm64 and kernels 5.4+ makedumpfile fails.

  Upstream patches solve this bug :

  [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage option
  
https://github.com/makedumpfile/makedumpfile/commit/d8b701796f0491f2ac4b06c7a5b795c29399efab

  [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo
  
https://github.com/makedumpfile/makedumpfile/commit/67d0e1d68f28c567a704fd6b9b8fd696ad3df183

  [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA
  
https://github.com/makedumpfile/makedumpfile/commit/a0216b678a95f099a16172cc4a67ad5aa6a89583

  [Test Case]

  OS: Ubuntu 20.04 LTS
  kernel: 5.4.0-21-generic
  arch:arm64
  Description:
  When testing kdump on Ubuntu 20.04 LTS (arm64), makedumpfile fails. The test 
steps are as follows:
  # echo 1> / proc / sys / kernel / sysrq
  # echo c> / proc / sysrq-trigger
  The error logs are as follows:
  [   26.599161] kdump-tools[653]: Starting kdump-tools:
  [   26.612761] kdump-tools[659]: Starting kdump-tools:
  [   26.628565] kdump-tools[659]: * running makedumpfile -c -d 31 /proc/vmcore 
/var/crash/2020050
  [   26.648621] kdump-tools[676]: * running makedumpfile -c -d 31 /proc/vmcore 
/var/crash/2020050
  [   26.668445] kdump-tools[676]: calculate_plat_config: PAGE SIZE 0x1000 and 
VA Bits 47 not supported
  [   26.678199] kdump-tools[676]: get_machdep_info_arm64
  [   26.692518] kdump-tools[659]: get_machdep_info_arm64
  [   26.852221] hns3 :7d:00.0: get link status cmd failed -16

  [   94.351303] kdump-tools[659]: * kdump-tools: makedumpfile failed, * 
kdump-tools: saved vmcore in /var/crash/202005061048
  [   94.435510] kdump-tools[659]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/202005061048/dmesg.202005061048
  [   94.457103] kdump-tools[688]: calculate_plat_config: PAGE SIZE 0x1000 and 
VA Bits 47 not supported
  [   94.476228] kdump-tools[688]: get_machdep_info_arm64: Can't determine 
platform config values
  [   94.485912] kdump-tools[688]: makedumpfile Failed.
  [   94.500760] kdump-tools[659]:  * kdump-tools: makedumpfile --dump-dmesg 
failed. dmesg content will be unavailable
  [   94.520225] kdump-tools[659]:  * kdump-tools: failed to save dmesg content 
in /var/crash/202005061048
  [   94.544205] kdump-tools[691]: Wed, 06 May 2020 10:49:42 -0400
  [   94.564597] kdump-tools[692]: Rebooting.
  [   94.678709] reboot: Restarting systemlpc uart init Done

  [Regression Potential]

  Patch 1 : [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage 
option
  removes get_elf_loads function this function was only used with --mem-usage 
option
  , since kernel commit kernel commit 23c85094fe18 (kernel versions >4.19)
  the information needed is in vmcoreinfo
  Any regression potential would affect the --mem-usage only

  Patch 2 : [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo
  arm64 only
  make use of NUMBER(VA_BITS) in vmcoreinfo as the current way of guessing 
VA_BITS
  does not work on Linux 5.4 and later.
  Before this commit VA_BITS would be calculated in get_versiondep_info_arm64, 
however
  this way of calculation breaks after 5.4. This commit gets the VA_BITS from 
vmcoreinfo
  and as a safeguard it uses the old way of deriving VA_BITS only if reading 
from vmcoreinfo doesn't work.

  From the kernel side VA_BITS is in vmcoreinfo since kernel 4.12, F and later 
use later kernel so not
  great regression potentional and if any it would only affect arm64.

  Patch 3 : [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA
  arm64 only
  Linux 5.4 and later kernels for arm64 changed the kernel VA space
  arrangement and introduced 52-bit kernel VAs by merging branch
  commit b333b0ba2346.  Support 5.9+ kernels with vmcoreinfo entries
  and 5.4+ kernels with best guessing.

  This patch makes adjustemnt to properly calculate vabits_actual, 
max_physmem_bits, page_offset
  Any regression potential would affect only arm64 and the calculation of the 
above variables.

  [Other]

  For H only the 3 commits are needed and they cherry-pick.

  For G and F the 3rd commit does not apply and an extra commit is
  needed :

  commit da0d25ffa585c9a1adb94562c815daa393b1ee5e
  [PATCH] arm64: Add support for ARMv8.2-LPA (52-bit PA support)

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

-- 

[Kernel-packages] [Bug 1915380] [NEW] I cannot access wifi : package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed to install/upgrade: installed bcmwl-kernel-source package post-installation

[Ali Analooee]

Public bug reported:

I cannot turn wifi on.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Feb 11 11:50:50 2021
ErrorMessage: installed bcmwl-kernel-source package post-installation script 
subprocess returned error exit status 10
InstallationDate: Installed on 2020-09-01 (162 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.4
SourcePackage: bcmwl
Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed to 
install/upgrade: installed bcmwl-kernel-source package post-installation script 
subprocess returned error exit status 10
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

Title:
  I cannot access wifi : package bcmwl-kernel-source 6.30.223.271+bdcom-
  0ubuntu5 failed to install/upgrade: installed bcmwl-kernel-source
  package post-installation script subprocess returned error exit status
  10

Status in bcmwl package in Ubuntu:
  New

Bug description:
  I cannot turn wifi on.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Feb 11 11:50:50 2021
  ErrorMessage: installed bcmwl-kernel-source package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2020-09-01 (162 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SourcePackage: bcmwl
  Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed to 
install/upgrade: installed bcmwl-kernel-source package post-installation script 
subprocess returned error exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1915380/+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 1912829] [NEW] nvidia-kernel-source-435 435.21-0ubuntu7: nvidia kernel module failed to build

[Ali]

Public bug reported:

i install google chrome and after install i have this error message and
my wi-fi icon disappear too.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-kernel-source-435 455.45.01-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-38-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
DKMSKernelVersion: 5.8.0-38-generic
Date: Fri Jan 22 10:08:06 2021
Dependencies:
 nvidia-kernel-source-455 460.32.03-0ubuntu0.20.04.1
 nvidia-kernel-source-460 460.32.03-0ubuntu0.20.04.1
DuplicateSignature: 
dkms:nvidia-kernel-source-435:435.21-0ubuntu7:/var/lib/dkms/nvidia/435.21/build/common/inc/nv-linux.h:503:17:
 error: too many arguments to function ‘__vmalloc’
InstallationDate: Installed on 2020-10-12 (102 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageVersion: 435.21-0ubuntu7
Python3Details: /usr/local/bin/python3.6, Python 3.6.3, unpackaged
PythonDetails: /usr/bin/python3.8, Python 3.8.5, unpackaged
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.4
SourcePackage: nvidia-graphics-drivers-455
Title: nvidia-kernel-source-435 435.21-0ubuntu7: nvidia kernel module failed to 
build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-455 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  nvidia-kernel-source-435 435.21-0ubuntu7: nvidia kernel module failed
  to build

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

Bug description:
  i install google chrome and after install i have this error message
  and my wi-fi icon disappear too.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-kernel-source-435 455.45.01-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.8.0-38-generic
  Date: Fri Jan 22 10:08:06 2021
  Dependencies:
   nvidia-kernel-source-455 460.32.03-0ubuntu0.20.04.1
   nvidia-kernel-source-460 460.32.03-0ubuntu0.20.04.1
  DuplicateSignature: 
dkms:nvidia-kernel-source-435:435.21-0ubuntu7:/var/lib/dkms/nvidia/435.21/build/common/inc/nv-linux.h:503:17:
 error: too many arguments to function ‘__vmalloc’
  InstallationDate: Installed on 2020-10-12 (102 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageVersion: 435.21-0ubuntu7
  Python3Details: /usr/local/bin/python3.6, Python 3.6.3, unpackaged
  PythonDetails: /usr/bin/python3.8, Python 3.8.5, unpackaged
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SourcePackage: nvidia-graphics-drivers-455
  Title: nvidia-kernel-source-435 435.21-0ubuntu7: nvidia kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-455/+bug/1912829/+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 1861294] Re: Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060 intel gpu

[Mohammad Ali Toufighi]

Same issue with 5.4.0-58-generic kernel on Ubuntu 20.04 and Intel UHD
graphics.

This can be seen in the logs:
kernel: [58329.813068] GpuWatchdog[9872]: segfault at 0 ip 5623a08ff439 sp 
7f46ae892680 error 6 in code[56239d2cf000+57ee000]
kernel: [58329.813084] Code: 00 79 09 48 8b 7d c0 e8 45 3d c0 fe c7 45 c0 aa aa 
aa aa 0f ae f0 41 8b 84 24 e0 00 00 00 89 45 c0 48 8d 7d c0 e8 97 50 9d fc  
04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 5d 41 5e

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

Title:
  Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060
  intel gpu

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running up-to-date Ubuntu-18.04.3 with kernel 5.3.0-26 on a Dell
  Optiplex 7060 with an i7-8700 CPU and Intel UHD Graphics 630
  (Coffeelake 3x8 GT2).

  I had chrome, slack and vmware-player running in Gnome. While doing
  some git clone, screen+mouse+keyboard froze for 2 minutes after which
  xorg and everything else recovered. I saw this in dmesg:

  kernel: show_signal_msg: 2 callbacks suppressed
  kernel: GpuWatchdog[20399]: segfault at 0 ip 556fd1665ded sp 
7efbf17e46c0 error 6 in chrome[556fcd72a000+7171000]
  kernel: Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 a9 
5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30  04 25 00 00 
00 00 37 13 00 00 c6 05 c1 6d 
  kernel: nvme nvme0: I/O 202 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 203 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 204 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 205 QID 6 timeout, aborting
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: I/O 202 QID 6 timeout, reset controller
  kernel: nvme nvme0: 12/0/0 default/read/poll queues

  While writing this bug report, the system froze again, and this time
  it didn't recover. After a cold reset I didn't see any other
  GpuWatchdog messages in journalctl.

  Ubuntu applied a BIOS firmware update before the first freeze, so my
  BIOS was updated as part of the cold reset I did. Not sure if this is
  relevant to reproducing the freeze.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294/+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 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs

[Ali Akbar]

The same thing happens with nvidia-driver-410.104 while using VLC

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

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

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

Bug description:
  To replicate:

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

  2. Optionally pause it.

  3. Switch to another user.

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

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

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

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

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

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

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

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

[Ali Akbar]

The same thing happens with nvidia-driver-410 while using VLC

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

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

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

Bug description:
  To replicate:

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

  2. Optionally pause it.

  3. Switch to another user.

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1581088] Re: Middle mouse (wheel-click) button stopped working after upgrade to 16.04

[Ali Raeini]

My M185 didn't register middle-click (bottom 2) neither, after trick
#91, sometimes middle-click registered as bottom 4, mostly 2, and
sometimes nothing, with a similar experience to #99. So I repeated #91
and ran `xinput set-button-map 4 1 2 3 2 2` and for now everything is
working and solid.

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

Title:
  Middle mouse (wheel-click) button stopped working after upgrade to
  16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to 16.04 clicking the middle mouse button (scroll
  wheel) on my Logitech M185 stopped working.

  xev does not even show the event for clicking the wheel, while it
  shows other button clicks and scroll wheel up/down events.

  xinput list shows the USB receiver 2 times:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB Receiver   id=9[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB Receiver   id=10   [slave  pointer 
 (2)]
  ⎜   ↳ HID 046a:0023   id=13   [slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=16   [slave  pointer 
 (2)]
  ⎜   ↳ TPPS/2 IBM TrackPoint   id=17   [slave  pointer 
 (2)]

  Listing the capabilities looks like this:

  $ xinput list 9
  Logitech USB Receiver id=9[slave  pointer  (2)]
   Reporting 7 classes:
    Class originated from: 9. Type: XIButtonClass
    Buttons supported: 24
    Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel 
Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" 
"Button Side" "Button Extra" "Button Forward" "Button Back" "Button Task" 
"Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button 
Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" 
"Button Unknown" "Button Unknown" "Button Unknown"
    Button state:
    Class originated from: 9. Type: XIValuatorClass
    Detail for Valuator 0:
  Label: Rel X
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 9. Type: XIValuatorClass
    Detail for Valuator 1:
  Label: Rel Y
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 9. Type: XIValuatorClass
    Detail for Valuator 2:
  Label: Rel Horiz Wheel
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 9. Type: XIValuatorClass
    Detail for Valuator 3:
  Label: Rel Vert Wheel
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 9. Type: XIScrollClass
    Scroll info for Valuator 2
  type: 2 (horizontal)
  increment: 1.00
  flags: 0x0
    Class originated from: 9. Type: XIScrollClass
    Scroll info for Valuator 3
  type: 1 (vertical)
  increment: -1.00
  flags: 0x2 ( preferred )

  $ xinput list 10
  Logitech USB Receiver id=10   [slave  pointer  (2)]
   Reporting 6 classes:
    Class originated from: 10. Type: XIButtonClass
    Buttons supported: 7
    Button labels: "Button 0" "Button Unknown" "Button Unknown" "Button Wheel 
Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right"
    Button state:
    Class originated from: 10. Type: XIKeyClass
    Keycodes supported: 248
    Class originated from: 10. Type: XIValuatorClass
    Detail for Valuator 0:
  Label: Rel X
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 10. Type: XIValuatorClass
    Detail for Valuator 1:
  Label: Rel Y
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 10. Type: XIValuatorClass
    Detail for Valuator 2:
  Label: Rel Horiz Wheel
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 10. Type: XIScrollClass
    Scroll info for Valuator 2
  type: 2 (horizontal)
  increment: 1.00
  flags: 0x0

  Does anyone have an idea how I can attempt to further debug that issue? Or 
maybe even a solution? Should I consider this issue a bug? Can I provide more 
info?
  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  toby  11625 F pulseaudio
   /dev/snd/controlC0:  toby  11625 F pulseaudio
   /dev/snd/pcmC1D0p:   toby  11625 F...m pulseaudio
   /dev/snd/controlC1:  toby  11625 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  

[Kernel-packages] [Bug 1819881] Re: [CONFIG] please enable highdpi font FONT_TER16x32

[Ali Fakhamati]

I test it on Ubuntu 19.04, in booting font is OK, but tty still very
small

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

Title:
  [CONFIG] please enable highdpi font FONT_TER16x32

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  == Justification ==
  The console font size on a high resolution screen is only suitable for
  eagles, although we can choose a bigger font by running:
sudo dpkg-reconfigure console-setup

  But that is not enough, the font size before video driver kicks in is
  still small. If we need to debug some early stage issues that will be a
  problem.

  
  == Fix ==
  ac8b6f14 (Fonts: New Terminus large console font)
  Config for this TER16x32 and the compiled-in fonts support needs to be
  enabled to keep engineers away from ophthalmologists.

  * Disco
It's already there. Just need to enable the configs.
  * Cosmic / Bionic
Patch can be cherry-picked.
  * Xenial
It needs an extra patch to make it a clean cherry-pick:
* 7bcae826 (lib/fonts/Kconfig: keep non-Sparc fonts listed together
  * Trusty
It needs two extra patches to make it a clean cherry-pick:
* fonts: Add 6x10 font (33ac9dba)
* lib/fonts/Kconfig: keep non-Sparc fonts listed together (7bcae826).
And a config entry for the 6x10 font.

  Commit "fonts: Add 6x10 font" is just adding a new font.
  Commit "lib/fonts/Kconfig: keep non-Sparc fonts listed together" is
  just a patch for context rearrangement.

  I think these two are safe to be pulled-in.

  
  == Test ==
  Test kernels: http://people.canonical.com/~phlin/kernel/lp-1819881-font/

  Add "fbcon=font:TER16x32" to the GRUB_CMDLINE_LINUX in
  /etc/default/grub, and follow these steps.

  * Disco
sudo update-grub; sudo reboot
  * Cosmic / Bionic
Add "GRUB_GFXPAYLOAD_LINUX=3840x2160" to /etc/default/grub
sudo update-grub; sudo reboot
  * Xenial
sudo update-grub; sudo reboot
  * Trusty
sudo update-grub; sudo reboot (I need the proprietary nvidia driver
to boot for my SUT - Dell Precision M3800)

  The font before the video driver kicks in will get bigger.

  == Regression potential ==
  Minimal, changes are limited to adding console fonts, turn on fonts
  related kernel configs.


  
  [CONFIG] please enable highdpi font FONT_TER16x32

  This is now available in v5.0

  config/config.common.ubuntu:# CONFIG_FONT_TER16x32 is not set

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/lib/fonts/Kconfig?id=ac8b6f148fc97e9e10b48bd337ef571b1d1136aa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819881/+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 1825626] Re: nvLock: client timed out, taking the lock

[Ali Fakhamati]

i have same problem
ubuntu 19.04

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

Title:
  nvLock: client timed out, taking the lock

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

Bug description:
  While launching an app or performing an operation, the screen has a
  certain chance to freeze for a few seconds and then recover.

  [ System Info ]
  Version : Ubuntu 19.04
  Kernel : x86_64 Linux 5.0.0-13-generic
  GPU : NVIDIA GeForce GTX 1050
  Xorg version : 1:7.7+19ubuntu12
  Product Name : Aspire VX5-591G (Acer)

  [ Log File ]
  Uploaded as an attachment

  *Sorry for my not-good English.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 20 17:19:29 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
   virtualbox, 6.0.6, 4.18.0-17-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 630 [1025:1127]
 Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] 
[1025:1128]
  MachineType: Acer Aspire VX5-591G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=a0525f6e-8c28-4e08-9c6e-9745ee51c18a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Wish_KLS
  dmi.board.vendor: KBL
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.06
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06:
  dmi.product.family: Aspire VX 15
  dmi.product.name: Aspire VX5-591G
  dmi.product.sku: 
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1825626/+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 1820832] Re: [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz

[Muhammed Ali Geldi]

I can also confirm that this bug is still present. I'm on Ubuntu 19.04
with the latest drivers & updates installed.

Also, I want to add something here: It's not that it specifically
limits the framerate to 60 Hz. Rather, it limits it to the monitor with
the lowest refresh rate. Try setting one monitor's refresh rate to 30
Hz, and you should instantly notice how laggy the whole desktop
environment becomes.

I understand that this issue might be looked at as "not that important",
but I believe a lot of people that would love to switch from Windows to
something like Ubuntu really wouldn't appreciate the fact that their 144
Hz monitor doesn't work as intended. If you own one yourself, you
probably would never want to set it to 60 Hz out of free will.

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

Title:
  [xorg] multiple monitors: limits the framerate of faster 120/144hz
  monitors to 60hz

Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  multiple monitors on xorg
  =

  Was recently discussed over on
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892

  Another user + myself have the following issue:

  The slowest connected display limits the FPS. The test case we used is
  over at the top of the other bug report ^^

  This we found today happens with either amd vega graphics, or nvidia
  pascal graphics, the vendor doesn't seem to matter. We have both seen
  the same issue (xorg).

  This is on 18.10, and booting into the 'Gnome (xorg)' login option.
  With the FPS being logged by journalctl -f. With only single monitor
  attached. Then it initially goes as high as the primary monitor can
  show. (And glmark2 running in background, to maintain a continued
  load). Which is 120fps for my case. Then as soon as secondary monitor
  is plugged in, which is a 60hz TV. This is being plugged into the HDMI
  port of the same graphics card in real time. Then the FPS logged by
  'journalctl -f' drops, and becomes capped to 60hz, in the output being
  printed by journalctl -f.

  My setup:
  kernel 5.0.0-05-lowlatency #201903032031
  NVIDIA Driver for UNIX platforms 415.27 (the closed source one)
  ubuntu 18.10

  mutter version:

  mutter/cosmic-updates,now 3.30.2-1~ubuntu18.10.4 amd64 [installed]
  mutter-common/cosmic-updates,cosmic-updates,now 3.30.2-1~ubuntu18.10.4 all 
[installed]

  To confirm where the '.4' at the very end of the ~ubuntu18.10.4
  version number, it seems to be that we have updated now on our client
  machines the be most recent bugfix updates, kindly provided by Daniel.
  Which closed the other bug
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 being
  referred to, as being solved for people's single monitor scenarios.

  Thanks again for the other recent bug fixes in this area, it is a nice
  progress. Very helpful! We hope you can also look into this latest
  problem / issue for the multiple monitor scenario.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1820832/+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 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[Amad Ali]

linux-generic-hwe-16.04-edge from xenial-proposed repo fixes the
problem.

$ sudo cat /etc/apt/sources.list | grep proposed
deb http://archive.ubuntu.com/ubuntu xenial-proposed main

$ sudo apt-cache policy linux-generic-hwe-16.04-edge
linux-generic-hwe-16.04-edge:
  Installed: 4.10.0.23.16
  Candidate: 4.10.0.23.16
  Version table:
 *** 4.10.0.23.16 500
500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 4.10.0.22.15 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages

$  uname -a
Linux  4.10.0-23-generic #25~16.04.1-Ubuntu SMP Fri Jun 9 
10:45:17 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

$ ip link show | grep bond0
bond0:  mtu 9000 qdisc noqueue master 
br-bond0 state UP mode DEFAULT group default qlen 1000   

$ sudo ovs-vsctl list-br | grep br-int
br-int

$ ip link show | grep br-int
32: br-int:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000

$ sudo ip link set br-int mtu 9000
$ ip link show | grep br-int
32: br-int:  mtu 9000 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000

also solves BUG mentioned in LP#1685742

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

Title:
  bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10
  in XENIAL LTS

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux-hwe package in Ubuntu:
  Fix Released
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in linux-hwe source package in Xenial:
  Fix Released
Status in linux-hwe-edge source package in Xenial:
  Confirmed
Status in linux source package in Yakkety:
  Fix Released
Status in linux-hwe source package in Yakkety:
  Fix Committed
Status in linux-hwe-edge source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  In Progress
Status in linux-hwe source package in Zesty:
  Confirmed
Status in linux-hwe-edge source package in Zesty:
  Confirmed

Bug description:
  Since I upgraded the kernel from linux-image-4.8.0-46-generic to
  linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to
  change the MTU.

  It seems to be known bug already fixed:
  https://bugzilla.kernel.org/show_bug.cgi?id=194763

  # ip l sh eno49
  2: eno49:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh eno50
  3: eno50:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh bond0
  6: bond0:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l set mtu 9000 bond0
  RTNETLINK answers: Invalid argument

  root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog
  Apr  4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 
requested, hw max 1500

  # modinfo ixgbe
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko
  version:4.4.0-k
  license:GPL
  description:Intel(R) 10 Gigabit PCI Express Network Driver

  # modinfo bonding
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko
  author: Thomas Davis, tada...@lbl.gov and many others
  description:Ethernet Channel Bonding Driver, v3.7.1
  version:3.7.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+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 1597961] Re: [Acer Aspire E5-573] Qualcomm Atheros Bluetooth 4.0 not working on [Ubuntu 16.04

[Amjad Ali]

Is there any update on this bug? I still can't use Bluetooth on my
laptop.

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

Title:
  [Acer Aspire E5-573] Qualcomm Atheros Bluetooth 4.0 not working on
  [Ubuntu 16.04

Status in linux package in Ubuntu:
  Expired

Bug description:
  While using Windows with my Acer Aspire E5-573, I'm able to use the Bluetooth:
  03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless 
Network Adapter [168c:0036] (rev 01)
Subsystem: Lite-On Communications Inc QCA9565 / AR9565 Wireless Network 
Adapter [11ad:0803]

  I've installed Ubuntu 16.04 in dual boot. While using Ubuntu, the
  Bluetooth adapter is the only piece of hardware that does not work.

  $ dmesg | grep -i bluetooth
  [   20.905534] Bluetooth: Core ver 2.21
  [   20.905548] Bluetooth: HCI device and connection manager initialized
  [   20.905551] Bluetooth: HCI socket layer initialized
  [   20.905553] Bluetooth: L2CAP socket layer initialized
  [   20.905557] Bluetooth: SCO socket layer initialized
  [   21.477624] Bluetooth: Can't change to loading configuration err
  [   21.477654] Bluetooth: Loading patch file failed
  [  124.347977] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [  124.347980] Bluetooth: BNEP filters: protocol multicast
  [  124.347985] Bluetooth: BNEP socket layer initialized

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vinicius   1913 F pulseaudio
   /dev/snd/controlC1:  vinicius   1913 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jun 30 22:27:24 2016
  HibernationDevice: RESUME=UUID=8ab51bc9-dd7d-4e30-9c74-696b6bb851ef
  InstallationDate: Installed on 2016-06-23 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Acer Aspire E5-573
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed 
root=UUID=216c2bbc-7194-46dc-929e-2a02be497343 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/16/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.37
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZORO_BH
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.37:bd02/16/2016:svnAcer:pnAspireE5-573:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-573
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597961/+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 1675949] Re: perf report can't annotate kernel and dbgsym package has wrong addresses

[Ali]

root@host1:~/fio# uname -a
Linux host1 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:20:17 UTC 2017 
aarch64 aarch64 aarch64 GNU/Linux

root@host1:~/fio# dpkg -S $(which perf)
linux-tools-common: /usr/bin/perf

root@host1:~/fio# dpkg --get-selections | grep linux-tools
linux-tools-4.10.0-11   install
linux-tools-4.10.0-13   install
linux-tools-4.10.0-13-generic   install
linux-tools-4.10.0-14   install
linux-tools-4.10.0-14-generic   install
linux-tools-4.10.0-9install
linux-tools-4.10.0-9-genericinstall
linux-tools-common  install
linux-tools-generic install

Running perf like: perf record -F 99 -g -- sleep 10 also has the same
issue

I've been running: perf record -a -- sleep 10

Annotation works on kernel modules and user code, but non-module kernel
code has the issue where annotation doesn't work on it.

After running record, run perf report, select one of the kernel symbols,
hit enter, select Annotate  and hit enter again.

Thanks,
Ali

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

Title:
  perf report can't annotate kernel and dbgsym package has wrong
  addresses

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running zesty 4.10.0-13-generic kernel and running:
  $ perf record 

  followed by

  $ perf report

  results in output that can't be annotated (even when run as root). The 
following message appears:
  Couldn't annotate do_io_submit:
  No vmlinux file with build id 81ba79d482fa9e3ea58486de8f119b27fe6db55e
  was found in the path.

  Note that annotation using /proc/kcore requires CAP_SYS_RAWIO
  capability.

  Please use:

  perf buildid-cache -vu vmlinux

  Note this is being run as root and /proc/kcore is accessible with dd from the 
same shell:
  $ dd if=/proc/kcore bs=8 count=16 | hexdump
  000 457f 464c 0102 0001    
  010 0004 00b7 0001     
  020 0040       
  030   0040 0038 0003   
  040 0004    00e8   

  Additionally, installing the linux-image-4.10.0-13-generic-dbgsym
  actually hurts the situation because the symbol addresses in the
  dbgsym don't match the kernel addresses.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675949/+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 1675949] Re: perf report can't annotate kernel and dbgsym package has wrong addresses

[Ali]

Hi Seth,

Thanks for taking a look. After upgrading to 4.10.0-14-generic I'm still
seeing the same issue. The build-id has changed, but the symptoms are
the same:

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

Title:
  perf report can't annotate kernel and dbgsym package has wrong
  addresses

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running zesty 4.10.0-13-generic kernel and running:
  $ perf record 

  followed by

  $ perf report

  results in output that can't be annotated (even when run as root). The 
following message appears:
  Couldn't annotate do_io_submit:
  No vmlinux file with build id 81ba79d482fa9e3ea58486de8f119b27fe6db55e
  was found in the path.

  Note that annotation using /proc/kcore requires CAP_SYS_RAWIO
  capability.

  Please use:

  perf buildid-cache -vu vmlinux

  Note this is being run as root and /proc/kcore is accessible with dd from the 
same shell:
  $ dd if=/proc/kcore bs=8 count=16 | hexdump
  000 457f 464c 0102 0001    
  010 0004 00b7 0001     
  020 0040       
  030   0040 0038 0003   
  040 0004    00e8   

  Additionally, installing the linux-image-4.10.0-13-generic-dbgsym
  actually hurts the situation because the symbol addresses in the
  dbgsym don't match the kernel addresses.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675949/+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 1675949] [NEW] perf report can't annotate kernel and dbgsym package has wrong addresses

[Ali]

Public bug reported:

Running zesty 4.10.0-13-generic kernel and running:
$ perf record 

followed by

$ perf report

results in output that can't be annotated (even when run as root). The 
following message appears:
Couldn't annotate do_io_submit:
No vmlinux file with build id 81ba79d482fa9e3ea58486de8f119b27fe6db55e
was found in the path.

Note that annotation using /proc/kcore requires CAP_SYS_RAWIO
capability.

Please use:

perf buildid-cache -vu vmlinux

Note this is being run as root and /proc/kcore is accessible with dd from the 
same shell:
$ dd if=/proc/kcore bs=8 count=16 | hexdump
000 457f 464c 0102 0001    
010 0004 00b7 0001     
020 0040       
030   0040 0038 0003   
040 0004    00e8   

Additionally, installing the linux-image-4.10.0-13-generic-dbgsym
actually hurts the situation because the symbol addresses in the dbgsym
don't match the kernel addresses.

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

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

Title:
  perf report can't annotate kernel and dbgsym package has wrong
  addresses

Status in linux package in Ubuntu:
  New

Bug description:
  Running zesty 4.10.0-13-generic kernel and running:
  $ perf record 

  followed by

  $ perf report

  results in output that can't be annotated (even when run as root). The 
following message appears:
  Couldn't annotate do_io_submit:
  No vmlinux file with build id 81ba79d482fa9e3ea58486de8f119b27fe6db55e
  was found in the path.

  Note that annotation using /proc/kcore requires CAP_SYS_RAWIO
  capability.

  Please use:

  perf buildid-cache -vu vmlinux

  Note this is being run as root and /proc/kcore is accessible with dd from the 
same shell:
  $ dd if=/proc/kcore bs=8 count=16 | hexdump
  000 457f 464c 0102 0001    
  010 0004 00b7 0001     
  020 0040       
  030   0040 0038 0003   
  040 0004    00e8   

  Additionally, installing the linux-image-4.10.0-13-generic-dbgsym
  actually hurts the situation because the symbol addresses in the
  dbgsym don't match the kernel addresses.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675949/+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 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

[Ali]

I fixed this problem with this link:
https://github.com/pvaret/rtl8192cu-fixes

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

Title:
  kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  booting PC with USB WLAN stick RTL8192CU attached on kernel 4.4.0-63-generic:
  Grub works, entering full disk encryption passphrase works, but when the 
desktop comes up mouse and keyboard (via USB) are dead and the desktop also.

  booting the PC without the stick attached works fine, but as soon as
  it is attached (see syslog) mouse, keyboard and the desktop itself are
  dead (checked by opening terminal and "watch date" - freezes, with
  desktop still visible).

  problem is resolved by booting former kernel 4.4.0-59-generic.

  syslog upon attaching stick 
---
  Feb 21 07:17:02 orin kernel: [  188.998338] usb 8-2: new high-speed USB 
device number 2 using xhci_hcd
  Feb 21 07:17:02 orin kernel: [  189.129674] usb 8-2: New USB device found, 
idVendor=0bda, idProduct=8178
  Feb 21 07:17:02 orin kernel: [  189.129682] usb 8-2: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
  Feb 21 07:17:02 orin kernel: [  189.129687] usb 8-2: Product: USB WLAN
  Feb 21 07:17:02 orin kernel: [  189.129691] usb 8-2: Manufacturer: Realtek
  Feb 21 07:17:02 orin kernel: [  189.129694] usb 8-2: SerialNumber: 
00e04c01
  Feb 21 07:17:02 orin mtp-probe: checking bus 8, device 2: 
"/sys/devices/pci:00/:00:10.1/usb8/8-2"
  Feb 21 07:17:02 orin mtp-probe: bus: 8, device: 2 was not an MTP device
  Feb 21 07:17:02 orin dbus[1112]: [system] Activating via systemd: service 
name='org.freedesktop.UDisks2' unit='udisks2.service'
  Feb 21 07:17:02 orin systemd[1]: Starting Disk Manager...
  Feb 21 07:17:02 orin udisksd[2447]: udisks daemon version 2.1.7 starting
  Feb 21 07:17:02 orin dbus[1112]: [system] Successfully activated service 
'org.freedesktop.UDisks2'
  Feb 21 07:17:02 orin systemd[1]: Started Disk Manager.
  Feb 21 07:17:02 orin udisksd[2447]: Acquired the name org.freedesktop.UDisks2 
on the system message bus
  Feb 21 07:17:02 orin org.gtk.vfs.AfcVolumeMonitor[1918]: Volume monitor alive
  Feb 21 07:17:03 orin kernel: [  190.200286] cfg80211: World regulatory domain 
updated:
  Feb 21 07:17:03 orin kernel: [  190.200294] cfg80211:  DFS Master region: 
unset
  Feb 21 07:17:03 orin kernel: [  190.200297] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
  Feb 21 07:17:03 orin kernel: [  190.200303] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200308] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200312] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200317] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200321] cfg80211:   (525 KHz - 
533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200325] cfg80211:   (549 KHz - 
573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200329] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200333] cfg80211:   (5724 KHz - 
6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.223081] rtl8192cu: Chip version 0x11
  Feb 21 07:17:03 orin kernel: [  190.625235] rtl8192cu: MAC address: 
14:cc:20:10:43:98
  Feb 21 07:17:03 orin kernel: [  190.625241] rtl8192cu: Board Type 0
  Feb 21 07:17:03 orin kernel: [  190.626355] rtl_usb: rx_max_size 15360, 
rx_urb_num 8, in_ep 1
  Feb 21 07:17:03 orin kernel: [  190.626408] rtl8192cu: Loading firmware 
rtlwifi/rtl8192cufw_TMSC.bin
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7698] (wlan0): 
using nl80211 for WiFi device control
  Feb 21 07:17:03 orin kernel: [  190.636625] ieee80211 phy0: Selected rate 
control algorithm 'rtl_rc'
  Feb 21 07:17:03 orin kernel: [  190.637211] usbcore: registered new interface 
driver rtl8192cu
  Feb 21 07:17:03 orin systemd[1]: Starting Load/Save RF Kill Switch Status...
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7780] device 
(wlan0): driver supports Access Point (AP) mode
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7798] manager: 
(wlan0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/4)
  Feb 21 07:17:03 orin kernel: [  190.648972] usbcore: registered new interface 
driver 

[Kernel-packages] [Bug 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

[Ali]

this problem still remain in 4.4.0-66.
I have this problem .when I connect to Internet ubuntu is friezed.

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

Title:
  kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  booting PC with USB WLAN stick RTL8192CU attached on kernel 4.4.0-63-generic:
  Grub works, entering full disk encryption passphrase works, but when the 
desktop comes up mouse and keyboard (via USB) are dead and the desktop also.

  booting the PC without the stick attached works fine, but as soon as
  it is attached (see syslog) mouse, keyboard and the desktop itself are
  dead (checked by opening terminal and "watch date" - freezes, with
  desktop still visible).

  problem is resolved by booting former kernel 4.4.0-59-generic.

  syslog upon attaching stick 
---
  Feb 21 07:17:02 orin kernel: [  188.998338] usb 8-2: new high-speed USB 
device number 2 using xhci_hcd
  Feb 21 07:17:02 orin kernel: [  189.129674] usb 8-2: New USB device found, 
idVendor=0bda, idProduct=8178
  Feb 21 07:17:02 orin kernel: [  189.129682] usb 8-2: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
  Feb 21 07:17:02 orin kernel: [  189.129687] usb 8-2: Product: USB WLAN
  Feb 21 07:17:02 orin kernel: [  189.129691] usb 8-2: Manufacturer: Realtek
  Feb 21 07:17:02 orin kernel: [  189.129694] usb 8-2: SerialNumber: 
00e04c01
  Feb 21 07:17:02 orin mtp-probe: checking bus 8, device 2: 
"/sys/devices/pci:00/:00:10.1/usb8/8-2"
  Feb 21 07:17:02 orin mtp-probe: bus: 8, device: 2 was not an MTP device
  Feb 21 07:17:02 orin dbus[1112]: [system] Activating via systemd: service 
name='org.freedesktop.UDisks2' unit='udisks2.service'
  Feb 21 07:17:02 orin systemd[1]: Starting Disk Manager...
  Feb 21 07:17:02 orin udisksd[2447]: udisks daemon version 2.1.7 starting
  Feb 21 07:17:02 orin dbus[1112]: [system] Successfully activated service 
'org.freedesktop.UDisks2'
  Feb 21 07:17:02 orin systemd[1]: Started Disk Manager.
  Feb 21 07:17:02 orin udisksd[2447]: Acquired the name org.freedesktop.UDisks2 
on the system message bus
  Feb 21 07:17:02 orin org.gtk.vfs.AfcVolumeMonitor[1918]: Volume monitor alive
  Feb 21 07:17:03 orin kernel: [  190.200286] cfg80211: World regulatory domain 
updated:
  Feb 21 07:17:03 orin kernel: [  190.200294] cfg80211:  DFS Master region: 
unset
  Feb 21 07:17:03 orin kernel: [  190.200297] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
  Feb 21 07:17:03 orin kernel: [  190.200303] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200308] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200312] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200317] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200321] cfg80211:   (525 KHz - 
533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200325] cfg80211:   (549 KHz - 
573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200329] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200333] cfg80211:   (5724 KHz - 
6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.223081] rtl8192cu: Chip version 0x11
  Feb 21 07:17:03 orin kernel: [  190.625235] rtl8192cu: MAC address: 
14:cc:20:10:43:98
  Feb 21 07:17:03 orin kernel: [  190.625241] rtl8192cu: Board Type 0
  Feb 21 07:17:03 orin kernel: [  190.626355] rtl_usb: rx_max_size 15360, 
rx_urb_num 8, in_ep 1
  Feb 21 07:17:03 orin kernel: [  190.626408] rtl8192cu: Loading firmware 
rtlwifi/rtl8192cufw_TMSC.bin
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7698] (wlan0): 
using nl80211 for WiFi device control
  Feb 21 07:17:03 orin kernel: [  190.636625] ieee80211 phy0: Selected rate 
control algorithm 'rtl_rc'
  Feb 21 07:17:03 orin kernel: [  190.637211] usbcore: registered new interface 
driver rtl8192cu
  Feb 21 07:17:03 orin systemd[1]: Starting Load/Save RF Kill Switch Status...
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7780] device 
(wlan0): driver supports Access Point (AP) mode
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7798] manager: 
(wlan0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/4)
  Feb 21 07:17:03 orin kernel: [  190.648972] usbcore: 

[Kernel-packages] [Bug 1671917] Re: perf probes on arm64 don't work with 4.10 kernel b/c of register name issue

[Ali]

It looks like the amd64 version of the deb is there, but not the arm64
version.

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

Title:
  perf probes on arm64 don't work with 4.10 kernel b/c of register name
  issue

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  perf probe doesn't work because the register names in the perf tool
  are incorrect. This was fixed upstream by
  https://patchwork.kernel.org/patch/9534823/.

  perf probe -x /lib/aarch64-linux-gnu/libc.so.6 -a 'malloc bytes'
  Failed to write event: Invalid argument
Error: Failed to add events.

  Rebuilding perf with the above mentioned change results in:
  ubuntu:/usr/src/linux-source-4.10.0/tools/perf# ./perf probe -x 
/lib/aarch64-linux-gnu/libc.so.6 -a 'malloc bytes'
  Added new event:
probe_libc:malloc(on malloc in /lib/aarch64-linux-gnu/libc-2.24.so with 
bytes)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671917/+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 1671917] Re: perf probes on arm64 don't work with 4.10 kernel b/c of register name issue

[Ali]

I don't see the linux-tools-4.10-11-13~lp1671917 in that directory.

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

Title:
  perf probes on arm64 don't work with 4.10 kernel b/c of register name
  issue

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  perf probe doesn't work because the register names in the perf tool
  are incorrect. This was fixed upstream by
  https://patchwork.kernel.org/patch/9534823/.

  perf probe -x /lib/aarch64-linux-gnu/libc.so.6 -a 'malloc bytes'
  Failed to write event: Invalid argument
Error: Failed to add events.

  Rebuilding perf with the above mentioned change results in:
  ubuntu:/usr/src/linux-source-4.10.0/tools/perf# ./perf probe -x 
/lib/aarch64-linux-gnu/libc.so.6 -a 'malloc bytes'
  Added new event:
probe_libc:malloc(on malloc in /lib/aarch64-linux-gnu/libc-2.24.so with 
bytes)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671917/+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 1671917] [NEW] perf probes on arm64 don't work with 4.10 kernel b/c of register name issue

[Ali]

Public bug reported:

perf probe doesn't work because the register names in the perf tool are
incorrect. This was fixed upstream by
https://patchwork.kernel.org/patch/9534823/.

perf probe -x /lib/aarch64-linux-gnu/libc.so.6 -a 'malloc bytes'
Failed to write event: Invalid argument
  Error: Failed to add events.

Rebuilding perf with the above mentioned change results in:
ubuntu:/usr/src/linux-source-4.10.0/tools/perf# ./perf probe -x 
/lib/aarch64-linux-gnu/libc.so.6 -a 'malloc bytes'
Added new event:
  probe_libc:malloc(on malloc in /lib/aarch64-linux-gnu/libc-2.24.so with 
bytes)

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

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

Title:
  perf probes on arm64 don't work with 4.10 kernel b/c of register name
  issue

Status in linux package in Ubuntu:
  New

Bug description:
  perf probe doesn't work because the register names in the perf tool
  are incorrect. This was fixed upstream by
  https://patchwork.kernel.org/patch/9534823/.

  perf probe -x /lib/aarch64-linux-gnu/libc.so.6 -a 'malloc bytes'
  Failed to write event: Invalid argument
Error: Failed to add events.

  Rebuilding perf with the above mentioned change results in:
  ubuntu:/usr/src/linux-source-4.10.0/tools/perf# ./perf probe -x 
/lib/aarch64-linux-gnu/libc.so.6 -a 'malloc bytes'
  Added new event:
probe_libc:malloc(on malloc in /lib/aarch64-linux-gnu/libc-2.24.so with 
bytes)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671917/+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 1597961] Re: Qualcomm Atheros Bluetooth 4.0 not working on Ubuntu 16.04

[Amjad Ali]

I am experiencing this issue as well, on Acer TravelMate P246-M. And
like Antonio, the hardware wireless switch (Fn + F3) doesn't work for me
either. I am using elementary OS 0.4 Loki, based on Ubuntu 16.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/1597961

Title:
  Qualcomm Atheros Bluetooth 4.0 not working on Ubuntu 16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  While using Windows with my Acer Aspire E5-573, I'm able to use the Bluetooth:
  03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless 
Network Adapter [168c:0036] (rev 01)
Subsystem: Lite-On Communications Inc QCA9565 / AR9565 Wireless Network 
Adapter [11ad:0803]

  I've installed Ubuntu 16.04 in dual boot. While using Ubuntu, the
  Bluetooth adapter is the only piece of hardware that does not work.

  $ dmesg | grep -i bluetooth
  [   20.905534] Bluetooth: Core ver 2.21
  [   20.905548] Bluetooth: HCI device and connection manager initialized
  [   20.905551] Bluetooth: HCI socket layer initialized
  [   20.905553] Bluetooth: L2CAP socket layer initialized
  [   20.905557] Bluetooth: SCO socket layer initialized
  [   21.477624] Bluetooth: Can't change to loading configuration err
  [   21.477654] Bluetooth: Loading patch file failed
  [  124.347977] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [  124.347980] Bluetooth: BNEP filters: protocol multicast
  [  124.347985] Bluetooth: BNEP socket layer initialized

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vinicius   1913 F pulseaudio
   /dev/snd/controlC1:  vinicius   1913 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jun 30 22:27:24 2016
  HibernationDevice: RESUME=UUID=8ab51bc9-dd7d-4e30-9c74-696b6bb851ef
  InstallationDate: Installed on 2016-06-23 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Acer Aspire E5-573
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed 
root=UUID=216c2bbc-7194-46dc-929e-2a02be497343 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/16/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.37
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZORO_BH
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.37:bd02/16/2016:svnAcer:pnAspireE5-573:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-573
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597961/+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 1594569] [NEW] package linux-headers-3.13.0-32 3.13.0-32.57~precise1 failed to install/upgrade: cannot copy extracted data for './usr/src/linux-headers-3.13.0-32/arch/powerpc/bo

[Muhammad Ali Siddiqui]

Public bug reported:

linux-headers-3.13.0-32 3.13.57~precise not installed

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-headers-3.13.0-32 3.13.0-32.57~precise1
ProcVersionSignature: Ubuntu 3.13.0-88.135-generic 3.13.11-ckt39
Uname: Linux 3.13.0-88-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
Date: Mon Jun 20 13:11:53 2016
DuplicateSignature: 
package:linux-headers-3.13.0-32:3.13.0-32.57~precise1:cannot copy extracted 
data for './usr/src/linux-headers-3.13.0-32/arch/powerpc/boot/Makefile' to 
'/usr/src/linux-headers-3.13.0-32/arch/powerpc/boot/Makefile.dpkg-new': 
unexpected end of file or stream
ErrorMessage: cannot copy extracted data for 
'./usr/src/linux-headers-3.13.0-32/arch/powerpc/boot/Makefile' to 
'/usr/src/linux-headers-3.13.0-32/arch/powerpc/boot/Makefile.dpkg-new': 
unexpected end of file or stream
InstallationDate: Installed on 2016-06-20 (0 days ago)
InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.6
 apt  1.0.1ubuntu2.14
SourcePackage: linux-lts-trusty
Title: package linux-headers-3.13.0-32 3.13.0-32.57~precise1 failed to 
install/upgrade: cannot copy extracted data for 
'./usr/src/linux-headers-3.13.0-32/arch/powerpc/boot/Makefile' to 
'/usr/src/linux-headers-3.13.0-32/arch/powerpc/boot/Makefile.dpkg-new': 
unexpected end of file or stream
UpgradeStatus: Upgraded to trusty on 2016-06-20 (0 days ago)

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


** Tags: amd64 apport-package dist-upgrade need-duplicate-check

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

Title:
  package linux-headers-3.13.0-32 3.13.0-32.57~precise1 failed to
  install/upgrade: cannot copy extracted data for './usr/src/linux-
  headers-3.13.0-32/arch/powerpc/boot/Makefile' to '/usr/src/linux-
  headers-3.13.0-32/arch/powerpc/boot/Makefile.dpkg-new': unexpected end
  of file or stream

Status in linux-lts-trusty package in Ubuntu:
  New

Bug description:
  linux-headers-3.13.0-32 3.13.57~precise not installed

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-headers-3.13.0-32 3.13.0-32.57~precise1
  ProcVersionSignature: Ubuntu 3.13.0-88.135-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-88-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Mon Jun 20 13:11:53 2016
  DuplicateSignature: 
package:linux-headers-3.13.0-32:3.13.0-32.57~precise1:cannot copy extracted 
data for './usr/src/linux-headers-3.13.0-32/arch/powerpc/boot/Makefile' to 
'/usr/src/linux-headers-3.13.0-32/arch/powerpc/boot/Makefile.dpkg-new': 
unexpected end of file or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/src/linux-headers-3.13.0-32/arch/powerpc/boot/Makefile' to 
'/usr/src/linux-headers-3.13.0-32/arch/powerpc/boot/Makefile.dpkg-new': 
unexpected end of file or stream
  InstallationDate: Installed on 2016-06-20 (0 days ago)
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.6
   apt  1.0.1ubuntu2.14
  SourcePackage: linux-lts-trusty
  Title: package linux-headers-3.13.0-32 3.13.0-32.57~precise1 failed to 
install/upgrade: cannot copy extracted data for 
'./usr/src/linux-headers-3.13.0-32/arch/powerpc/boot/Makefile' to 
'/usr/src/linux-headers-3.13.0-32/arch/powerpc/boot/Makefile.dpkg-new': 
unexpected end of file or stream
  UpgradeStatus: Upgraded to trusty on 2016-06-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1594569/+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 1584997] [NEW] package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 30

[Ali Noaman Ibrahim]

Public bug reported:

No wifi connection with new installed ubuntu 16.04

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
AptOrdering:
 bcmwl-kernel-source: Install
 bcmwl-kernel-source: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Mon May 23 19:49:43 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 30
InstallationDate: Installed on 2016-05-22 (1 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.10ubuntu1
SourcePackage: bcmwl
Title: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 30
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 30

Status in bcmwl package in Ubuntu:
  New

Bug description:
  No wifi connection with new installed ubuntu 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  AptOrdering:
   bcmwl-kernel-source: Install
   bcmwl-kernel-source: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon May 23 19:49:43 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 30
  InstallationDate: Installed on 2016-05-22 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.10ubuntu1
  SourcePackage: bcmwl
  Title: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 30
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1584997/+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 1572711] [NEW] package linux-image-4.4.0-21-generic 4.4.0-21.37 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[ali]

Public bug reported:

linux-image

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-21-generic 4.4.0-21.37
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic i686
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ali1922 F pulseaudio
Date: Tue Apr 19 22:13:53 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 2
HibernationDevice: RESUME=UUID=c70841a7-2455-4752-8661-2baad803bab2
InstallationDate: Installed on 2015-04-08 (378 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta i386 (20150326)
MachineType: Packard Bell EasyNote TJ65
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=dc4823c9-daae-46a3-a740-abdf0084a807 ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3
SourcePackage: linux
Title: package linux-image-4.4.0-21-generic 4.4.0-21.37 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/26/2009
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.06
dmi.board.name: SJV50MV
dmi.board.vendor: Packard Bell
dmi.board.version: Rev
dmi.chassis.type: 10
dmi.chassis.vendor: Packard Bell
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.06:bd03/26/2009:svnPackardBell:pnEasyNoteTJ65:pvr0100:rvnPackardBell:rnSJV50MV:rvrRev:cvnPackardBell:ct10:cvrN/A:
dmi.product.name: EasyNote TJ65
dmi.product.version: 0100
dmi.sys.vendor: Packard Bell

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


** Tags: apport-package i386 xenial

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

Title:
  package linux-image-4.4.0-21-generic 4.4.0-21.37 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  linux-image

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ali1922 F pulseaudio
  Date: Tue Apr 19 22:13:53 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  HibernationDevice: RESUME=UUID=c70841a7-2455-4752-8661-2baad803bab2
  InstallationDate: Installed on 2015-04-08 (378 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta i386 (20150326)
  MachineType: Packard Bell EasyNote TJ65
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=dc4823c9-daae-46a3-a740-abdf0084a807 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3
  SourcePackage: linux
  Title: package linux-image-4.4.0-21-generic 4.4.0-21.37 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/26/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.06
  dmi.board.name: SJV50MV
  dmi.board.vendor: Packard Bell
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Packard Bell
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.06:bd03/26/2009:svnPackardBell:pnEasyNoteTJ65:pvr0100:rvnPackardBell:rnSJV50MV:rvrRev:cvnPackardBell:ct10:cvrN/A:
  dmi.product.name: EasyNote TJ65
  dmi.product.version: 0100
  dmi.sys.vendor: Packard Bell

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572711/+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 1572710] [NEW] package linux-image-4.4.0-21-generic 4.4.0-21.37 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[ali]

Public bug reported:

kernel

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-21-generic 4.4.0-21.37
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic i686
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ali1922 F pulseaudio
CurrentDesktop: Unity
Date: Wed Apr 20 21:47:07 2016
HibernationDevice: RESUME=UUID=c70841a7-2455-4752-8661-2baad803bab2
InstallationDate: Installed on 2015-04-08 (378 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta i386 (20150326)
MachineType: Packard Bell EasyNote TJ65
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=dc4823c9-daae-46a3-a740-abdf0084a807 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-21-generic N/A
 linux-backports-modules-4.4.0-21-generic  N/A
 linux-firmware1.157
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/26/2009
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.06
dmi.board.name: SJV50MV
dmi.board.vendor: Packard Bell
dmi.board.version: Rev
dmi.chassis.type: 10
dmi.chassis.vendor: Packard Bell
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.06:bd03/26/2009:svnPackardBell:pnEasyNoteTJ65:pvr0100:rvnPackardBell:rnSJV50MV:rvrRev:cvnPackardBell:ct10:cvrN/A:
dmi.product.name: EasyNote TJ65
dmi.product.version: 0100
dmi.sys.vendor: Packard Bell

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


** Tags: apport-bug i386 xenial

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

Title:
  package linux-image-4.4.0-21-generic 4.4.0-21.37 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  kernel

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ali1922 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Apr 20 21:47:07 2016
  HibernationDevice: RESUME=UUID=c70841a7-2455-4752-8661-2baad803bab2
  InstallationDate: Installed on 2015-04-08 (378 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta i386 (20150326)
  MachineType: Packard Bell EasyNote TJ65
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=dc4823c9-daae-46a3-a740-abdf0084a807 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/26/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.06
  dmi.board.name: SJV50MV
  dmi.board.vendor: Packard Bell
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Packard Bell
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.06:bd03/26/2009:svnPackardBell:pnEasyNoteTJ65:pvr0100:rvnPackardBell:rnSJV50MV:rvrRev:cvnPackardBell:ct10:cvrN/A:
  dmi.product.name: EasyNote TJ65
  dmi.product.version: 0100
  dmi.sys.vendor: Packard Bell

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572710/+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 1392176] Re: mounts cgroups unconditionally which causes undesired effects with cpu hotplug

[Ali]

Serge,

Does the issue being moot apply to wiley or 16.04?

Thanks,
Ali

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

Title:
  mounts cgroups unconditionally which causes undesired effects with cpu
  hotplug

Status in cgmanager package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #0 - Preeti U. Murthy <preeti.mur...@in.ibm.com> - 2014-10-20 
04:40:12 ==
  ---Problem Description---
  Systemd mounts cgroups explicitly every boot. Since the user had no say in 
it, undesired consequences are observed in reaction to cpu hotplug operations.  
Here is how.

  Systemd moves the tasks to the cgroup mounted by it. This cgroup 
automatically becomes the child of the root cgroup which is present by default. 
The children cgroups are not expected to remember their configured cpusets 
after hotplug operations in the kernel. Hence when cpus are taken offline and 
brought back online they are no longer used for load balancing of tasks and 
hence remain unused. 
 This is an undesired consequence because the user had not even asked for 
cgroups to be mounted, yet is not able to use the full capacity of the system.

  Only when the user himself creates cgroup hierarchies, should he be
  exposed to the side effects of cpu hotplug on cpusets. Else all online
  cpus must be made available to him which is not happening since
  systemd mounts cgroups on every boot.

  Hence please revert this feature or provide an explaination as to why this is 
being done.
   
  ---uname output---
  Linux tul181p1 3.16.0-18-generic #25-Ubuntu SMP Fri Sep 26 02:39:53 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Tuleta 8286-42A 
   ---Debugger---
  A debugger was configured, however the system did not enter into the debugger
   
  ---Steps to Reproduce---
   $ taskset -p $$
  $ 0-127
  $ echo 0 > /sys/devices/system/cpu/cpu7/online
  $ taskset -p $$
  $ 0-6,8-127
  $ echo 1 > /sys/devices/system/cpu/cpu7/online
  $ taskset -p $$
  $ 0-6,8-127
   
   
  Userspace tool common name: systemd 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: systemd_208-8ubuntu8_ppc64el.deb

  Userspace tool obtained from project website:   208-8ubuntu8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1392176/+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 1313279] Re: xHCI host not responding to stop endpoint command

[Naser Ali]

I have  an Intel NUC D54250WYK running BIOS V32, Ubuntu 14.04 and Unity
with a very similar issue. If I boot with the 290e tuner attached and
then turn on an external DAC, the Cambridge Audio DacMagic 100, all the
USB ports fail. Logs show the same xHCI host crash.

I found two ways to deal with the problem.

1. Uninstall the MythTV backend - undesirable
2. Remove the 290e usb tuner during booting. Putting it in after a minute after 
booting means both DAC and 290e coexist, but they used to without this 
complication at the beginning of the year using, still on the same NUC on 
Trusty.

Still looks like a kernel bug.

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

Title:
  xHCI host not responding to stop endpoint command

Status in The Linux Kernel:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 14.04 LTS
  Release:  14.04
  Hardware: Intel NUC D34010WYK (Core i3 4010U)
  Memory: 4 gigabytes
  USD device: PCTV 292e DVB-T tuner

  I have 2 PCTV 292e DVB-T tuners connected to the system. When I start
  to use either of the tuner, the xHCI host crashes. Since I'm booting
  from an USB disk. If I only connect 1 of the tuners, the system works
  ok. It does not matter which one of the tuners I connect.

  [   68.990396] xhci_hcd :00:14.0: xHCI host not responding to stop 
endpoint command.
  [   68.990402] xhci_hcd :00:14.0: Assuming host is dying, halting host.

  Sometimes this also leads to this:

  [  638.183002] IP: [815325dd] usb_enable_link_state+0x2d/0x2f0
  [  638.183057] PGD 0 
  [  638.183077] Oops:  [#1] SMP 

  I can also observe the same fault with OpenELEC Linux distribution
  that runs kernel 3.14 when I run the system from an internal SATA SSD
  drive (not from an external USB disk).

  lsusb -v: http://paste.ubuntu.com/7343384/
  dmesg: http://sprunge.us/HMXH
  dmesg (crash type 2): http://sprunge.us/PSiX

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lubuntu-desktop 0.55
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Sun Apr 27 11:12:22 2014
  InstallationDate: Installed on 2014-04-07 (19 days ago)
  InstallationMedia: Lubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  SourcePackage: lubuntu-meta
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1313279/+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 1166442] Re: Elantech clickpad/touchpad lacks multitouch features.

[Ali Najafi]

#137 and #167 helped me on Lenovo G5070 to have multitouch working (edge
scrolling, two-finger scrolling, two-finger right-click, right and
middle clicks on corners). However it broke the physical right click.

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

Title:
  Elantech clickpad/touchpad lacks multitouch features.

Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux” source package in Precise:
  Fix Released
Status in “linux” source package in Quantal:
  Fix Released
Status in “linux” source package in Raring:
  Fix Released
Status in “linux” source package in Saucy:
  Fix Released
Status in “linux” package in Arch Linux:
  New

Bug description:
  Newer versions of the Elantech multitouch trackpad are not fully
  supported in Linux.  These appear in many of the newer Samsung
  laptops, for example.  elantech.c in the kernel needs to be updated to
  support these models (up to v7 perhaps?)

  This bug is confirmed to affect a range of samsung laptops running
  Ubuntu 12.04 and newer, ArchLinux, Fedora and also affects the current
  (3.9) upstream kernel.

  A dkms package was produced in 2011 (see
  https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
  intel/+bug/681904/comments/64) which may fix certain older laptops
  affected by this issue, but doesn't fix newer models.

  == Original Report ==

  Hello,

  So far I've been having a problem with my Elantech multitouch trackpad in 
Linux. Basically all i get is right click, left click, and tap to click, along 
with basic  movement. The problem seems to be rooted in improper detection of 
the trackpad, likely b/c its a new revision or whatnot. Of note is that working 
elantech trackpads of the past in forums i scouted through show up as ETPS/2 
Elantech Touchpad. Mine just shows up in xinput as PS/2 Elantech Touchpad. I 
think this might be a simple fix in the end, just improper detection, I hope. 
For reference, I've tried kernel 3.5 on Ubuntu 12.10 and kernel 3.8.0-17 on 
Ubuntu 13.04 thus far, with all combinations of psmouse.
  
--
  What's expected: touchpad multitouch support
  What happened: basic touchpad support
  Laptop mode: Samsung Series 7 NP780 series
  Ubuntu distro(s) tested: Ubuntu 12.10, Ubuntu 13.04
  Kernels used: 3.5 signed (Ubuntu 12.10 default), 3.8.0-16, 3.8.0-17 signed
  Other tests: Attempted using psmouse-elantech-v6, psmouse-alps, and 
psmouse-alps-dst. No improvements so removed.

  synclient -l reports Couldn't find synaptics properties. No synaptics driver 
loaded?
  
--
  See attached for more info. Ask anything you need!
  ---
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gscoppino   2272 F pulseaudio
  DistroRelease: Ubuntu 13.04
  HibernationDevice: RESUME=UUID=f683852c-7aa0-4f32-8b86-56f0a018989d
  InstallationDate: Installed on 2013-04-06 (3 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 770Z5E/780Z5E/870Z5E/880Z5E
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-17-generic.efi.signed 
root=UUID=cf39fbe5-c8ff-4d16-b11e-a41a4f3ae955 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-17-generic N/A
   linux-backports-modules-3.8.0-17-generic  N/A
   linux-firmware1.104
  StagingDrivers: rts5139
  Tags:  raring staging
  Uname: Linux 3.8.0-17-generic x86_64
  UpgradeStatus: Upgraded to raring on 2013-04-06 (3 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 02/26/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P03ABU.139.130226.SK
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP780Z5E-S01UB
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP03ABU.139.130226.SK:bd02/26/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn770Z5E/780Z5E/870Z5E/880Z5E:pvrP03ABU:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP780Z5E-S01UB:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 770Z5E/780Z5E/870Z5E/880Z5E
  dmi.product.version: P03ABU
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  ---
  ApportVersion: 

Re: [Kernel-packages] [Bug 1331654] Re: [Dell Inspiron 1525] Cannot resume from suspend

[Ashraf Ali]

I have installed the kernel 3.13.11-03131105-generic and the issue is
solved .


On Wed, Sep 3, 2014 at 5:13 PM, Richard Mortimer 1331...@bugs.launchpad.net
 wrote:

 It looks like linux-image-3.13.0-35-generic (3.13.0-35.62) contains the
 fixes for this bug.

 I've done some initial testing and it seems to work for me after a few
 suspend/resume cycles.

 The changelog says that it includes LP: #1347088 (Linux 3.13.11.5). The
 launchpad #1347088 comments state that

 drm/i915: Avoid div-by-zero when pixel_multiplier is zero

 is included as part of the 3.13.11.5 patch.

 --
 You received this bug notification because you are subscribed to a
 duplicate bug report (1305371).
 https://bugs.launchpad.net/bugs/1331654

 Title:
   [Dell Inspiron 1525] Cannot resume from suspend

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



-- 
ashrafalipk

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

Title:
  [Dell Inspiron 1525] Cannot resume from suspend

Status in The Linux Kernel:
  Unknown
Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  Hello folks,

  After upgrading to Ubuntu Trusty (14.04), I cannot more resume from a
  previous suspend. All things were all right on 13.10.

  If I boot previous kernel 3.11.0-23, everything works well.

  Also I've tried these kernels:

  vanilla 3.13.0-rc1 (Bugged)
  vanilla 3.12.22 (Working)

  I also noted if I suspend from lightdm menu (on 3.13.0-rc1), I can
  resume after, but If I do this after logged with my user (not root), I
  am unable to resume from suspend.

  I cannot perform Sysrq magic keys, I can only press the power button.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-29-generic 3.13.0-29.53
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  iuri   2137 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jun 18 15:22:53 2014
  HibernationDevice: RESUME=UUID=5dd061d0-fd44-4034-9107-63948dcd2c16
  InstallationDate: Installed on 2014-05-01 (48 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 1525
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-29-generic 
root=UUID=a198f31e-440b-4f9b-87bb-d5e956fbe42f ro rootflags=subvol=@ 
locale=pt_BR quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-29-generic N/A
   linux-backports-modules-3.13.0-29-generic  N/A
   linux-firmware 1.127.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0D109D
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd10/16/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0D109D:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1525
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1331654/+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 1357763] Re: Touchpad won't work on Toshiba Satellite S55

[Ali Rajabi]

I cannot boot the upstream kernel, it freezes on Loading initial
ramdisk 

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

Title:
  Touchpad won't work on Toshiba Satellite S55

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I just installed ubuntu 14.04.01 and touchpad doesn't work at all.
  Here's what I get from : 
  cat /proc/bus/input/devices

  I: Bus=0011 Vendor=0002 Product=000e Version=
  N: Name=ETPS/2 Elantech Touchpad
  P: Phys=isa0060/serio2/input0
  S: Sysfs=/devices/platform/i8042/serio2/input/input9
  U: Uniq=
  H: Handlers=mouse1 event5 
  B: PROP=5
  B: EV=b
  B: KEY=e420 1 0 0 0 0
  B: ABS=66180001103

  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  al 1722 F pulseaudio
   /dev/snd/controlC1:  al 1722 F pulseaudio
   /dev/snd/pcmC1D0p:   al 1722 F...m pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=2fc684f2-13d5-44f8-bf9f-6ce3dfd43541
  InstallationDate: Installed on 2014-08-16 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: TOSHIBA Satellite S55-B
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic.efi.signed 
root=UUID=466b0ec4-c2f9-464a-b8cd-23882554fc79 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-34-generic N/A
   linux-backports-modules-3.13.0-34-generic  N/A
   linux-firmware 1.127.5
  Tags:  trusty
  Uname: Linux 3.13.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/07/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.50
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.50:bd07/07/2014:svnTOSHIBA:pnSatelliteS55-B:pvrPSPRBU-004001:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite S55-B
  dmi.product.version: PSPRBU-004001
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1357763/+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 1357763] Re: Touchpad won't work on Toshiba Satellite S55

[Ali Rajabi]

kernel-unable-to-test-upstream

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

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

Title:
  Touchpad won't work on Toshiba Satellite S55

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I just installed ubuntu 14.04.01 and touchpad doesn't work at all.
  Here's what I get from : 
  cat /proc/bus/input/devices

  I: Bus=0011 Vendor=0002 Product=000e Version=
  N: Name=ETPS/2 Elantech Touchpad
  P: Phys=isa0060/serio2/input0
  S: Sysfs=/devices/platform/i8042/serio2/input/input9
  U: Uniq=
  H: Handlers=mouse1 event5 
  B: PROP=5
  B: EV=b
  B: KEY=e420 1 0 0 0 0
  B: ABS=66180001103

  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  al 1722 F pulseaudio
   /dev/snd/controlC1:  al 1722 F pulseaudio
   /dev/snd/pcmC1D0p:   al 1722 F...m pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=2fc684f2-13d5-44f8-bf9f-6ce3dfd43541
  InstallationDate: Installed on 2014-08-16 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: TOSHIBA Satellite S55-B
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic.efi.signed 
root=UUID=466b0ec4-c2f9-464a-b8cd-23882554fc79 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-34-generic N/A
   linux-backports-modules-3.13.0-34-generic  N/A
   linux-firmware 1.127.5
  Tags:  trusty
  Uname: Linux 3.13.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/07/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.50
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.50:bd07/07/2014:svnTOSHIBA:pnSatelliteS55-B:pvrPSPRBU-004001:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite S55-B
  dmi.product.version: PSPRBU-004001
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1357763/+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 1357763] [NEW] Touchpad won't work on Toshiba Satellite S55

[Ali Rajabi]

Public bug reported:

I just installed ubuntu 14.04.01 and touchpad doesn't work at all.
Here's what I get from : 
cat /proc/bus/input/devices

I: Bus=0011 Vendor=0002 Product=000e Version=
N: Name=ETPS/2 Elantech Touchpad
P: Phys=isa0060/serio2/input0
S: Sysfs=/devices/platform/i8042/serio2/input/input9
U: Uniq=
H: Handlers=mouse1 event5 
B: PROP=5
B: EV=b
B: KEY=e420 1 0 0 0 0
B: ABS=66180001103

Description:Ubuntu 14.04.1 LTS
Release:14.04

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


** Tags: trusty

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

Title:
  Touchpad won't work on Toshiba Satellite S55

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I just installed ubuntu 14.04.01 and touchpad doesn't work at all.
  Here's what I get from : 
  cat /proc/bus/input/devices

  I: Bus=0011 Vendor=0002 Product=000e Version=
  N: Name=ETPS/2 Elantech Touchpad
  P: Phys=isa0060/serio2/input0
  S: Sysfs=/devices/platform/i8042/serio2/input/input9
  U: Uniq=
  H: Handlers=mouse1 event5 
  B: PROP=5
  B: EV=b
  B: KEY=e420 1 0 0 0 0
  B: ABS=66180001103

  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1357763/+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 1357763] Re: Touchpad won't work on Toshiba Satellite S55

[Ali Rajabi]

apport information

** Tags added: apport-collected

** Description changed:

  I just installed ubuntu 14.04.01 and touchpad doesn't work at all.
  Here's what I get from : 
  cat /proc/bus/input/devices
  
  I: Bus=0011 Vendor=0002 Product=000e Version=
  N: Name=ETPS/2 Elantech Touchpad
  P: Phys=isa0060/serio2/input0
  S: Sysfs=/devices/platform/i8042/serio2/input/input9
  U: Uniq=
  H: Handlers=mouse1 event5 
  B: PROP=5
  B: EV=b
  B: KEY=e420 1 0 0 0 0
  B: ABS=66180001103
  
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
+ --- 
+ ApportVersion: 2.14.1-0ubuntu3.2
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  al 1722 F pulseaudio
+  /dev/snd/controlC1:  al 1722 F pulseaudio
+  /dev/snd/pcmC1D0p:   al 1722 F...m pulseaudio
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 14.04
+ HibernationDevice: RESUME=UUID=2fc684f2-13d5-44f8-bf9f-6ce3dfd43541
+ InstallationDate: Installed on 2014-08-16 (0 days ago)
+ InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
+ MachineType: TOSHIBA Satellite S55-B
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic.efi.signed 
root=UUID=466b0ec4-c2f9-464a-b8cd-23882554fc79 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
+ RelatedPackageVersions:
+  linux-restricted-modules-3.13.0-34-generic N/A
+  linux-backports-modules-3.13.0-34-generic  N/A
+  linux-firmware 1.127.5
+ Tags:  trusty
+ Uname: Linux 3.13.0-34-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 07/07/2014
+ dmi.bios.vendor: INSYDE Corp.
+ dmi.bios.version: 1.50
+ dmi.board.asset.tag: Type2 - Board Asset Tag
+ dmi.board.name: Type2 - Board Product Name1
+ dmi.board.vendor: Type2 - Board Vendor Name1
+ dmi.board.version: Type2 - Board Version
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: OEM Chassis ManuFacturer
+ dmi.chassis.version: OEM Chassis Version
+ dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.50:bd07/07/2014:svnTOSHIBA:pnSatelliteS55-B:pvrPSPRBU-004001:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
+ dmi.product.name: Satellite S55-B
+ dmi.product.version: PSPRBU-004001
+ dmi.sys.vendor: TOSHIBA

** Attachment added: AlsaInfo.txt
   
https://bugs.launchpad.net/bugs/1357763/+attachment/4179520/+files/AlsaInfo.txt

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

Title:
  Touchpad won't work on Toshiba Satellite S55

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I just installed ubuntu 14.04.01 and touchpad doesn't work at all.
  Here's what I get from : 
  cat /proc/bus/input/devices

  I: Bus=0011 Vendor=0002 Product=000e Version=
  N: Name=ETPS/2 Elantech Touchpad
  P: Phys=isa0060/serio2/input0
  S: Sysfs=/devices/platform/i8042/serio2/input/input9
  U: Uniq=
  H: Handlers=mouse1 event5 
  B: PROP=5
  B: EV=b
  B: KEY=e420 1 0 0 0 0
  B: ABS=66180001103

  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  al 1722 F pulseaudio
   /dev/snd/controlC1:  al 1722 F pulseaudio
   /dev/snd/pcmC1D0p:   al 1722 F...m pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=2fc684f2-13d5-44f8-bf9f-6ce3dfd43541
  InstallationDate: Installed on 2014-08-16 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: TOSHIBA Satellite S55-B
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic.efi.signed 
root=UUID=466b0ec4-c2f9-464a-b8cd-23882554fc79 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-34-generic N/A
   linux-backports-modules-3.13.0-34-generic  N/A
   linux-firmware 1.127.5
  Tags:  trusty
  Uname: Linux 3.13.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/07/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.50
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  

[Kernel-packages] [Bug 1357763] CRDA.txt

[Ali Rajabi]

apport information

** Attachment added: CRDA.txt
   https://bugs.launchpad.net/bugs/1357763/+attachment/4179522/+files/CRDA.txt

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

Title:
  Touchpad won't work on Toshiba Satellite S55

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I just installed ubuntu 14.04.01 and touchpad doesn't work at all.
  Here's what I get from : 
  cat /proc/bus/input/devices

  I: Bus=0011 Vendor=0002 Product=000e Version=
  N: Name=ETPS/2 Elantech Touchpad
  P: Phys=isa0060/serio2/input0
  S: Sysfs=/devices/platform/i8042/serio2/input/input9
  U: Uniq=
  H: Handlers=mouse1 event5 
  B: PROP=5
  B: EV=b
  B: KEY=e420 1 0 0 0 0
  B: ABS=66180001103

  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  al 1722 F pulseaudio
   /dev/snd/controlC1:  al 1722 F pulseaudio
   /dev/snd/pcmC1D0p:   al 1722 F...m pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=2fc684f2-13d5-44f8-bf9f-6ce3dfd43541
  InstallationDate: Installed on 2014-08-16 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: TOSHIBA Satellite S55-B
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic.efi.signed 
root=UUID=466b0ec4-c2f9-464a-b8cd-23882554fc79 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-34-generic N/A
   linux-backports-modules-3.13.0-34-generic  N/A
   linux-firmware 1.127.5
  Tags:  trusty
  Uname: Linux 3.13.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/07/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.50
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.50:bd07/07/2014:svnTOSHIBA:pnSatelliteS55-B:pvrPSPRBU-004001:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite S55-B
  dmi.product.version: PSPRBU-004001
  dmi.sys.vendor: TOSHIBA

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

[Ali Rajabi]

apport information

** Attachment added: ProcModules.txt
   
https://bugs.launchpad.net/bugs/1357763/+attachment/4179530/+files/ProcModules.txt

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

Title:
  Touchpad won't work on Toshiba Satellite S55

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I just installed ubuntu 14.04.01 and touchpad doesn't work at all.
  Here's what I get from : 
  cat /proc/bus/input/devices

  I: Bus=0011 Vendor=0002 Product=000e Version=
  N: Name=ETPS/2 Elantech Touchpad
  P: Phys=isa0060/serio2/input0
  S: Sysfs=/devices/platform/i8042/serio2/input/input9
  U: Uniq=
  H: Handlers=mouse1 event5 
  B: PROP=5
  B: EV=b
  B: KEY=e420 1 0 0 0 0
  B: ABS=66180001103

  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  al 1722 F pulseaudio
   /dev/snd/controlC1:  al 1722 F pulseaudio
   /dev/snd/pcmC1D0p:   al 1722 F...m pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=2fc684f2-13d5-44f8-bf9f-6ce3dfd43541
  InstallationDate: Installed on 2014-08-16 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: TOSHIBA Satellite S55-B
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic.efi.signed 
root=UUID=466b0ec4-c2f9-464a-b8cd-23882554fc79 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-34-generic N/A
   linux-backports-modules-3.13.0-34-generic  N/A
   linux-firmware 1.127.5
  Tags:  trusty
  Uname: Linux 3.13.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/07/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.50
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.50:bd07/07/2014:svnTOSHIBA:pnSatelliteS55-B:pvrPSPRBU-004001:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite S55-B
  dmi.product.version: PSPRBU-004001
  dmi.sys.vendor: TOSHIBA

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

[Ali Rajabi]

apport information

** Attachment added: ProcInterrupts.txt
   
https://bugs.launchpad.net/bugs/1357763/+attachment/4179529/+files/ProcInterrupts.txt

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

Title:
  Touchpad won't work on Toshiba Satellite S55

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I just installed ubuntu 14.04.01 and touchpad doesn't work at all.
  Here's what I get from : 
  cat /proc/bus/input/devices

  I: Bus=0011 Vendor=0002 Product=000e Version=
  N: Name=ETPS/2 Elantech Touchpad
  P: Phys=isa0060/serio2/input0
  S: Sysfs=/devices/platform/i8042/serio2/input/input9
  U: Uniq=
  H: Handlers=mouse1 event5 
  B: PROP=5
  B: EV=b
  B: KEY=e420 1 0 0 0 0
  B: ABS=66180001103

  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  al 1722 F pulseaudio
   /dev/snd/controlC1:  al 1722 F pulseaudio
   /dev/snd/pcmC1D0p:   al 1722 F...m pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=2fc684f2-13d5-44f8-bf9f-6ce3dfd43541
  InstallationDate: Installed on 2014-08-16 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: TOSHIBA Satellite S55-B
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic.efi.signed 
root=UUID=466b0ec4-c2f9-464a-b8cd-23882554fc79 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-34-generic N/A
   linux-backports-modules-3.13.0-34-generic  N/A
   linux-firmware 1.127.5
  Tags:  trusty
  Uname: Linux 3.13.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/07/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.50
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.50:bd07/07/2014:svnTOSHIBA:pnSatelliteS55-B:pvrPSPRBU-004001:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite S55-B
  dmi.product.version: PSPRBU-004001
  dmi.sys.vendor: TOSHIBA

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

[Ali Rajabi]

apport information

** Attachment added: WifiSyslog.txt
   
https://bugs.launchpad.net/bugs/1357763/+attachment/4179535/+files/WifiSyslog.txt

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

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

Title:
  Touchpad won't work on Toshiba Satellite S55

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I just installed ubuntu 14.04.01 and touchpad doesn't work at all.
  Here's what I get from : 
  cat /proc/bus/input/devices

  I: Bus=0011 Vendor=0002 Product=000e Version=
  N: Name=ETPS/2 Elantech Touchpad
  P: Phys=isa0060/serio2/input0
  S: Sysfs=/devices/platform/i8042/serio2/input/input9
  U: Uniq=
  H: Handlers=mouse1 event5 
  B: PROP=5
  B: EV=b
  B: KEY=e420 1 0 0 0 0
  B: ABS=66180001103

  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  al 1722 F pulseaudio
   /dev/snd/controlC1:  al 1722 F pulseaudio
   /dev/snd/pcmC1D0p:   al 1722 F...m pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=2fc684f2-13d5-44f8-bf9f-6ce3dfd43541
  InstallationDate: Installed on 2014-08-16 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: TOSHIBA Satellite S55-B
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic.efi.signed 
root=UUID=466b0ec4-c2f9-464a-b8cd-23882554fc79 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-34-generic N/A
   linux-backports-modules-3.13.0-34-generic  N/A
   linux-firmware 1.127.5
  Tags:  trusty
  Uname: Linux 3.13.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/07/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.50
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.50:bd07/07/2014:svnTOSHIBA:pnSatelliteS55-B:pvrPSPRBU-004001:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite S55-B
  dmi.product.version: PSPRBU-004001
  dmi.sys.vendor: TOSHIBA

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

[Ali Rajabi]

apport information

** Attachment added: RfKill.txt
   https://bugs.launchpad.net/bugs/1357763/+attachment/4179532/+files/RfKill.txt

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

Title:
  Touchpad won't work on Toshiba Satellite S55

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I just installed ubuntu 14.04.01 and touchpad doesn't work at all.
  Here's what I get from : 
  cat /proc/bus/input/devices

  I: Bus=0011 Vendor=0002 Product=000e Version=
  N: Name=ETPS/2 Elantech Touchpad
  P: Phys=isa0060/serio2/input0
  S: Sysfs=/devices/platform/i8042/serio2/input/input9
  U: Uniq=
  H: Handlers=mouse1 event5 
  B: PROP=5
  B: EV=b
  B: KEY=e420 1 0 0 0 0
  B: ABS=66180001103

  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  al 1722 F pulseaudio
   /dev/snd/controlC1:  al 1722 F pulseaudio
   /dev/snd/pcmC1D0p:   al 1722 F...m pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=2fc684f2-13d5-44f8-bf9f-6ce3dfd43541
  InstallationDate: Installed on 2014-08-16 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: TOSHIBA Satellite S55-B
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic.efi.signed 
root=UUID=466b0ec4-c2f9-464a-b8cd-23882554fc79 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-34-generic N/A
   linux-backports-modules-3.13.0-34-generic  N/A
   linux-firmware 1.127.5
  Tags:  trusty
  Uname: Linux 3.13.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/07/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.50
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.50:bd07/07/2014:svnTOSHIBA:pnSatelliteS55-B:pvrPSPRBU-004001:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite S55-B
  dmi.product.version: PSPRBU-004001
  dmi.sys.vendor: TOSHIBA

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

[Ali Rajabi]

apport information

** Attachment added: IwConfig.txt
   
https://bugs.launchpad.net/bugs/1357763/+attachment/4179524/+files/IwConfig.txt

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

Title:
  Touchpad won't work on Toshiba Satellite S55

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I just installed ubuntu 14.04.01 and touchpad doesn't work at all.
  Here's what I get from : 
  cat /proc/bus/input/devices

  I: Bus=0011 Vendor=0002 Product=000e Version=
  N: Name=ETPS/2 Elantech Touchpad
  P: Phys=isa0060/serio2/input0
  S: Sysfs=/devices/platform/i8042/serio2/input/input9
  U: Uniq=
  H: Handlers=mouse1 event5 
  B: PROP=5
  B: EV=b
  B: KEY=e420 1 0 0 0 0
  B: ABS=66180001103

  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  al 1722 F pulseaudio
   /dev/snd/controlC1:  al 1722 F pulseaudio
   /dev/snd/pcmC1D0p:   al 1722 F...m pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=2fc684f2-13d5-44f8-bf9f-6ce3dfd43541
  InstallationDate: Installed on 2014-08-16 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: TOSHIBA Satellite S55-B
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic.efi.signed 
root=UUID=466b0ec4-c2f9-464a-b8cd-23882554fc79 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-34-generic N/A
   linux-backports-modules-3.13.0-34-generic  N/A
   linux-firmware 1.127.5
  Tags:  trusty
  Uname: Linux 3.13.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/07/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.50
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.50:bd07/07/2014:svnTOSHIBA:pnSatelliteS55-B:pvrPSPRBU-004001:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite S55-B
  dmi.product.version: PSPRBU-004001
  dmi.sys.vendor: TOSHIBA

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