[Kernel-packages] [Bug 1995573] Re: Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536]

2022-11-07 Thread AceLan Kao
** Description changed:

  [Impact]
  Screen cannot turn on after screen is off
  
  [Fix]
  Below commit from v6.0-rc1 fixes the issue
  c577b2f43e80 drm/mgag200: Enable atomic gamma lut update
  
+ And applied some other commits to fix the conflicts
+ c48a36301634 drm/mgag200: Optimize damage clips
+ 3064debaf55e drm/mgag200: Add FB_DAMAGE_CLIPS support
+ 5913ab941d6e drm/mgag200: Acquire I/O lock while reading EDID
+ 931e3f3a0e99 drm/mgag200: Protect concurrent access to I/O registers with lock
+ e13f13e039dc drm: Add DRM-managed mutex_init()
+ 
  [Tests]
  Verified on the machine with Matrox G200eW3 [102b:0536] graphics card.
  
  [Where problems could occur]
+ The commits to solve the conflicts are trivial, and not likely to introduce 
regressions. The fix patch change a lot of code and hard to evaluate the risk, 
but check the latest linus/master tree and linux-next/master tree, there is no 
fixed commit for all these cherry-picked commits, so should be safe to include 
them.

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

Title:
  Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-5.17 source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  In Progress
Status in linux-oem-5.17 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  Screen cannot turn on after screen is off

  [Fix]
  Below commit from v6.0-rc1 fixes the issue
  c577b2f43e80 drm/mgag200: Enable atomic gamma lut update

  And applied some other commits to fix the conflicts
  c48a36301634 drm/mgag200: Optimize damage clips
  3064debaf55e drm/mgag200: Add FB_DAMAGE_CLIPS support
  5913ab941d6e drm/mgag200: Acquire I/O lock while reading EDID
  931e3f3a0e99 drm/mgag200: Protect concurrent access to I/O registers with lock
  e13f13e039dc drm: Add DRM-managed mutex_init()

  [Tests]
  Verified on the machine with Matrox G200eW3 [102b:0536] graphics card.

  [Where problems could occur]
  The commits to solve the conflicts are trivial, and not likely to introduce 
regressions. The fix patch change a lot of code and hard to evaluate the risk, 
but check the latest linus/master tree and linux-next/master tree, there is no 
fixed commit for all these cherry-picked commits, so should be safe to include 
them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1995573/+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 1980602] Re: grub failures 22.10

2022-11-07 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  grub failures  22.10

Status in linux package in Ubuntu:
  Expired

Bug description:
  On initial power -up , each morning , grub fails to complete. 
  It reports problems with accessing / processing /dev/sde13  when the actual 
OS  being used , according to grub . is  /dev/sde14 .

  It will load / process when second attempt is made on same /dev/sde14
  .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980602/+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 1986520] Re: There are libvirtd errors in /var/log/syslog when powering on or off virtual machine in Ubuntu 22.04 LTS

2022-11-07 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  There are libvirtd errors in /var/log/syslog when powering on or off
  virtual machine in Ubuntu 22.04 LTS

Status in libvirt package in Ubuntu:
  Expired
Status in linux package in Ubuntu:
  Expired

Bug description:
  Hardware Configuration:
  Server MTM: Bona POR SE450
  OS installed: Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso)
  BMC Version: 1.40 (Build ID: USX311E)
  UEFI Version: 1.03 (Build ID: CME105C)
  LXPM Version: 3.19 (Build ID: CML103A)
  CPU: Xeon Silver 4314 16C 135W 2.4GHz
  DIMM2,4,7,9: Hynix 32GB 2Rx4 3200 MHz RDIMM HMA84GR7CJR4N-XNTG; 
HMA84GR7CJR4N-XNT4
  DIMM1,3,8,10: Intel Optane DCPMM_128GB QVR2
  IO Config:
  RAID: Intel VROC (VMD NVMe RAID) Premium
  SLOT5: NIC: ThinkSystem Mellanox ConnectX-6 Dx 100GbE QSFP56 2-port PCIe 4 
Ethernet Adapter
  SLOT7: NIC: Intel I350 1GbE RJ45 4-port Internal Lock OCP Ethernet Adapter
  Storage:
  DISK1: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  DISK2: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  PSU1: CFFv4 AC 1100W (Delta) 110V
  PSU2: CFFv4 AC 1100W (Delta) 110V
  M/B build version: PASS5 MB

  Steps:
  1. Power on SUT and install Ubuntu 22.04 LTS on VROC NVMe RAID 0 disk.
  2. Install KVM features and desktop GUI.
  3. Run "apt upgrade" to update packages.
  4. Create a namespace on BPS DIMM App Direct Not Interleaved mode.
  5. Run "virt-manager" then install Windows Server 2022 on the namespace.
  6. Reboot Guest OS and Host OS to check if there is any unexpected error in 
system logs. (=> failed, there are libvirtd errors in /var/log/syslog when 
booting into OS or powering on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.] )

  Expected behaviors:
  There are no any unexpected errors in system logs.

  Current behaviors:
  There are libvirtd errors in /var/log/syslog when booting into OS or powering 
on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.]
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-18 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
   Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
   Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Lenovo ThinkEdge SE450
  Package: linux (not installed)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-46.49-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 20220329.git681281e4-0ubuntu3.4
  RfKill:
   
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: Lenovo
  dmi.bios.version: CME105F-1.23
  dmi.board.asset.tag: none
  dmi.board.name: 7D8TCTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLenovo:bvrCME105F-1.23:bd08/08/2022:br1.23:efr1.40:svnLenovo:pnThinkEdgeSE450:pvr05:rvnLenovo:rn7D8TCTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7D8TCTO1WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkEdge SE450
  

[Kernel-packages] [Bug 1986520] Re: There are libvirtd errors in /var/log/syslog when powering on or off virtual machine in Ubuntu 22.04 LTS

2022-11-07 Thread Launchpad Bug Tracker
[Expired for libvirt (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  There are libvirtd errors in /var/log/syslog when powering on or off
  virtual machine in Ubuntu 22.04 LTS

Status in libvirt package in Ubuntu:
  Expired
Status in linux package in Ubuntu:
  Expired

Bug description:
  Hardware Configuration:
  Server MTM: Bona POR SE450
  OS installed: Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso)
  BMC Version: 1.40 (Build ID: USX311E)
  UEFI Version: 1.03 (Build ID: CME105C)
  LXPM Version: 3.19 (Build ID: CML103A)
  CPU: Xeon Silver 4314 16C 135W 2.4GHz
  DIMM2,4,7,9: Hynix 32GB 2Rx4 3200 MHz RDIMM HMA84GR7CJR4N-XNTG; 
HMA84GR7CJR4N-XNT4
  DIMM1,3,8,10: Intel Optane DCPMM_128GB QVR2
  IO Config:
  RAID: Intel VROC (VMD NVMe RAID) Premium
  SLOT5: NIC: ThinkSystem Mellanox ConnectX-6 Dx 100GbE QSFP56 2-port PCIe 4 
Ethernet Adapter
  SLOT7: NIC: Intel I350 1GbE RJ45 4-port Internal Lock OCP Ethernet Adapter
  Storage:
  DISK1: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  DISK2: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  PSU1: CFFv4 AC 1100W (Delta) 110V
  PSU2: CFFv4 AC 1100W (Delta) 110V
  M/B build version: PASS5 MB

  Steps:
  1. Power on SUT and install Ubuntu 22.04 LTS on VROC NVMe RAID 0 disk.
  2. Install KVM features and desktop GUI.
  3. Run "apt upgrade" to update packages.
  4. Create a namespace on BPS DIMM App Direct Not Interleaved mode.
  5. Run "virt-manager" then install Windows Server 2022 on the namespace.
  6. Reboot Guest OS and Host OS to check if there is any unexpected error in 
system logs. (=> failed, there are libvirtd errors in /var/log/syslog when 
booting into OS or powering on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.] )

  Expected behaviors:
  There are no any unexpected errors in system logs.

  Current behaviors:
  There are libvirtd errors in /var/log/syslog when booting into OS or powering 
on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.]
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-18 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
   Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
   Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Lenovo ThinkEdge SE450
  Package: linux (not installed)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-46.49-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 20220329.git681281e4-0ubuntu3.4
  RfKill:
   
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: Lenovo
  dmi.bios.version: CME105F-1.23
  dmi.board.asset.tag: none
  dmi.board.name: 7D8TCTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLenovo:bvrCME105F-1.23:bd08/08/2022:br1.23:efr1.40:svnLenovo:pnThinkEdgeSE450:pvr05:rvnLenovo:rn7D8TCTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7D8TCTO1WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkEdge SE450
  

[Kernel-packages] [Bug 1995911] [NEW] package libnvidia-gl-390 (not installed) failed to install/upgrade: new libnvidia-gl-390:amd64 package pre-installation script subprocess returned error exit stat

2022-11-07 Thread Javier Calderon
Public bug reported:

upgrade from 18.04 to 22.04 I have a black screen with flashing cursor,
after uninstall and reinstall nvidia driver

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: libnvidia-gl-390 (not installed)
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
Uname: Linux 5.15.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Mon Nov  7 17:10:19 2022
ErrorMessage: new libnvidia-gl-390:amd64 package pre-installation script 
subprocess returned error exit status 2
InstallationDate: Installed on 2020-06-19 (871 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.8
SourcePackage: nvidia-graphics-drivers-390
Title: package libnvidia-gl-390 (not installed) failed to install/upgrade: new 
libnvidia-gl-390:amd64 package pre-installation script subprocess returned 
error exit status 2
UpgradeStatus: Upgraded to jammy on 2022-11-04 (4 days ago)

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


** Tags: amd64 apport-package jammy need-duplicate-check

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

Title:
  package libnvidia-gl-390 (not installed) failed to install/upgrade:
  new libnvidia-gl-390:amd64 package pre-installation script subprocess
  returned error exit status 2

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

Bug description:
  upgrade from 18.04 to 22.04 I have a black screen with flashing
  cursor, after uninstall and reinstall nvidia driver

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libnvidia-gl-390 (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Nov  7 17:10:19 2022
  ErrorMessage: new libnvidia-gl-390:amd64 package pre-installation script 
subprocess returned error exit status 2
  InstallationDate: Installed on 2020-06-19 (871 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: nvidia-graphics-drivers-390
  Title: package libnvidia-gl-390 (not installed) failed to install/upgrade: 
new libnvidia-gl-390:amd64 package pre-installation script subprocess returned 
error exit status 2
  UpgradeStatus: Upgraded to jammy on 2022-11-04 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1995911/+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 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones

2022-11-07 Thread Drew R.
FYI - I have the NP950XEE (GalaxyBook2 Pro w/ Intel ARC graphics), have
been struggling with the same problem and trying to fix for days now.  I
have perfect sound in headphones, no sound on speakers.  I've
implemented every fix discussed here, and haven't seen one single
effect.  I'm running 22.04.  I tried upgrading kernels to 5.17 and 6.0
also, no effect.  No matter what I try, headphones work, speakers not
(and no metallic sound on headphones).  Can anyone give any
help/guidance, I'm stuck.

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

Title:
  [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on
  internal speakers, very very quiet on headphones

Status in Linux:
  New
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I've been googling this issue for 10's of hours and tried many things.

  Relase of Ubuntu: 19.10

  Expected outcome: Music plays on the internal speakers and headphones.

  Actual outcome: I can barely hear audio using headphones with volume
  turned up to 150%.  Absolutely nothing comes out of the speakers. (The
  speakers sound great under Windows 10.)

  Complete alsa-info output is attached, but here are some snippets:

  !!DMI Information
  !!---

  Manufacturer:  SAMSUNG ELECTRONICS CO., LTD.
  Product Name:  950SBE/951SBE
  Product Version:   P06RES
  Firmware Version:  P06RES.075.190529.SP
  Board Vendor:  SAMSUNG ELECTRONICS CO., LTD.
  Board Name:NP950SBE-K01US

  
  !!Kernel Information
  !!--

  Kernel release:5.3.0-19-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes


  !!ALSA Version
  !!

  Driver version: k5.3.0-19-generic
  Library version:1.1.9
  Utilities version:  1.1.9

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

  Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes

  
  !!Soundcards recognised by ALSA
  !!-

   0 [PCH]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0x604b118000 irq 177

  
  !!PCI Soundcards installed in the system
  !!--

  00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP
  High Definition Audio Controller (rev 11)

  
  !!Advanced information - PCI Vendor/Device/Subsystem ID's
  !!---

  00:1f.3 0401: 8086:9dc8 (rev 11)
  DeviceName: Onboard - Sound

  
  !!HDA-Intel Codec information
  !!---
  --startcollapse--

  Codec: Realtek ALC298
  Address: 0
  AFG Function Id: 0x1 (unsol 1)
  Vendor Id: 0x10ec0298
  Subsystem Id: 0x144dc812
  Revision Id: 0x100103
  No Modem Function Group found
  Default PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
  Default Amp-In caps: N/A
  Default Amp-Out caps: N/A
  State of AFG node 0x01:
Power states:  D0 D1 D2 D3 D3cold CLKSTOP EPSS
Power: setting=D0, actual=D0
  GPIO: io=8, o=0, i=0, unsolicited=1, wake=0
IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Headphone Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Device: name="ALC298 Analog", type="Audio", device=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x00 0x00]
Converter: stream=1, channel=0
PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
Power states:  D0 D1 D2 D3 EPSS
Power: setting=D0, actual=D0
  Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Speaker Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x7f 0x7f]
Converter: stream=1, channel=0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin 1383 F pulseaudio
  

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

2022-11-07 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  Can't boot with kernel 5.15.0-52

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  These packages are installed:

  linux-image-5.15.0-50-generic/jammy-updates,jammy-security,now 5.15.0-50.56 
amd64 [installed,automatic]
  linux-image-5.15.0-52-generic/jammy-updates,jammy-security,now 5.15.0-52.58 
amd64 [installed,automatic]

  After grub and booting, there's some text appears, and then the screen
  goes blank. After forcing the computer to turn off, I boot again but
  using 5.15.0-50, it can boot like usual.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-52-generic 5.15.0-52.58
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  Uname: Linux 5.15.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fikr4n 2015 F pulseaudio
   /dev/snd/controlC0:  fikr4n 2015 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  8 08:57:48 2022
  InstallationDate: Installed on 2021-06-05 (520 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: HP HP ENVY Laptop 15-ep0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=UUID=34001051-5122-4187-b21f-2032a99219e8 ro quiet splash 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.6
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-08-28 (71 days ago)
  dmi.bios.date: 07/30/2021
  dmi.bios.release: 15.7
  dmi.bios.vendor: AMI
  dmi.bios.version: F.07
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 878E
  dmi.board.vendor: HP
  dmi.board.version: 18.33
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 18.33
  dmi.modalias: 
dmi:bvnAMI:bvrF.07:bd07/30/2021:br15.7:efr18.33:svnHP:pnHPENVYLaptop15-ep0xxx:pvr:rvnHP:rn878E:rvr18.33:cvnHP:ct10:cvrChassisVersion:sku16P91PA#AR6:
  dmi.product.family: 103C_5335KV HP ENVY
  dmi.product.name: HP ENVY Laptop 15-ep0xxx
  dmi.product.sku: 16P91PA#AR6
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995903/+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 1995903] [NEW] Can't boot with kernel 5.15.0-52

2022-11-07 Thread Fikrul Arif
Public bug reported:

These packages are installed:

linux-image-5.15.0-50-generic/jammy-updates,jammy-security,now 5.15.0-50.56 
amd64 [installed,automatic]
linux-image-5.15.0-52-generic/jammy-updates,jammy-security,now 5.15.0-52.58 
amd64 [installed,automatic]

After grub and booting, there's some text appears, and then the screen
goes blank. After forcing the computer to turn off, I boot again but
using 5.15.0-50, it can boot like usual.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-52-generic 5.15.0-52.58
ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
Uname: Linux 5.15.0-50-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  fikr4n 2015 F pulseaudio
 /dev/snd/controlC0:  fikr4n 2015 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov  8 08:57:48 2022
InstallationDate: Installed on 2021-06-05 (520 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: HP HP ENVY Laptop 15-ep0xxx
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=UUID=34001051-5122-4187-b21f-2032a99219e8 ro quiet splash 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.6
SourcePackage: linux
UpgradeStatus: Upgraded to jammy on 2022-08-28 (71 days ago)
dmi.bios.date: 07/30/2021
dmi.bios.release: 15.7
dmi.bios.vendor: AMI
dmi.bios.version: F.07
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 878E
dmi.board.vendor: HP
dmi.board.version: 18.33
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 18.33
dmi.modalias: 
dmi:bvnAMI:bvrF.07:bd07/30/2021:br15.7:efr18.33:svnHP:pnHPENVYLaptop15-ep0xxx:pvr:rvnHP:rn878E:rvr18.33:cvnHP:ct10:cvrChassisVersion:sku16P91PA#AR6:
dmi.product.family: 103C_5335KV HP ENVY
dmi.product.name: HP ENVY Laptop 15-ep0xxx
dmi.product.sku: 16P91PA#AR6
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug jammy wayland-session

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

Title:
  Can't boot with kernel 5.15.0-52

Status in linux package in Ubuntu:
  New

Bug description:
  These packages are installed:

  linux-image-5.15.0-50-generic/jammy-updates,jammy-security,now 5.15.0-50.56 
amd64 [installed,automatic]
  linux-image-5.15.0-52-generic/jammy-updates,jammy-security,now 5.15.0-52.58 
amd64 [installed,automatic]

  After grub and booting, there's some text appears, and then the screen
  goes blank. After forcing the computer to turn off, I boot again but
  using 5.15.0-50, it can boot like usual.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-52-generic 5.15.0-52.58
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  Uname: Linux 5.15.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fikr4n 2015 F pulseaudio
   /dev/snd/controlC0:  fikr4n 2015 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  8 08:57:48 2022
  InstallationDate: Installed on 2021-06-05 (520 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: HP HP ENVY Laptop 15-ep0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=UUID=34001051-5122-4187-b21f-2032a99219e8 ro quiet splash 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.6
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-08-28 (71 days ago)
  dmi.bios.date: 07/30/2021
  dmi.bios.release: 15.7
  dmi.bios.vendor: AMI
  dmi.bios.version: F.07
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 878E
  dmi.board.vendor: HP
  dmi.board.version: 18.33
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 18.33
  dmi.modalias: 
dmi:bvnAMI:bvrF.07:bd07/30/2021:br15.7:efr18.33:svnHP:pnHPENVYLaptop15-ep0xxx:pvr:rvnHP:rn878E:rvr18.33:cvnHP:ct10:cvrChassisVersion:sku16P91PA#AR6:
  dmi.product.family: 103C_5335KV HP ENVY
  dmi.product.name: HP ENVY Laptop 15-ep0xxx
  dmi.product.sku: 16P91PA#AR6
  dmi.sys.vendor: HP

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


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

[Kernel-packages] [Bug 1995886] Re: vmxnet3: update to latest ToT

2022-11-07 Thread Ronak Doshi
Hi Tim,

Can you confirm that these kernels already have patches mentioned in
update 5?

Thanks,
Ronak

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

Title:
  vmxnet3: update to latest ToT

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  New
Status in linux source package in Kinetic:
  New

Bug description:
  This request is to port vmxnet3 patches to Ubuntu kernel. Below are
  the commits in order:

  vmxnet3: prepare for version 7 changes
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=55f0395fcace9e675af2cbb96015ce1ae8856806

  vmxnet3: add support for capability registers
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=6f91f4ba046e5de6a6e579620b32b8ecf56873f7

  vmxnet3: add support for large passthrough BAR register
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=543fb67405410cc548a72d7a9a4087688d2f56ac

  vmxnet3: add support for out of order rx completion
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=2c5a5748105a6bb901579d365c6f93e79f282b69

  vmxnet3: add command to set ring buffer sizes
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=c7112ebd27ea0dbe4eecd5c96cad93757e34e73d

  vmxnet3: limit number of TXDs used for TSO packet
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=d2857b99a74b082368ee80f359372faa1d051043

  vmxnet3: use ext1 field to indicate encapsulated packet
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=60cafa0395c2bed44d13277ed328317ed16a58c0

  vmxnet3: update to version 7
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=acc38e041bd304621d4f59cea4849747d13bba9c

  vmxnet3: disable overlay offloads if UPT device does not support
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=a56b158a5078b8120d3d72fc9fd44efed5123b12

  vmxnet3: do not reschedule napi for rx processing
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/vmxnet3?id=5b91884bf50b21d34bd3daa5c8f8b7e92e0a2c46

  This is a request to bring latest Ubuntu LTS releases' vmxnet3 driver
  up to date with ToT Linux kernel.

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

2022-11-07 Thread Tim Gardner
Git repositories at:

git://git.launchpad.net/~timg-tpi/ubuntu/+source/linux/+git/jammy 
jammy-vmxnet3-update-to-6.0-lp1995886
git://git.launchpad.net/~timg-tpi/ubuntu/+source/linux/+git/kinetic 
kinetic-vmxnet3-update-to-6.0-lp1995886

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

Title:
  vmxnet3: update to latest ToT

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  New
Status in linux source package in Kinetic:
  New

Bug description:
  This request is to port vmxnet3 patches to Ubuntu kernel. Below are
  the commits in order:

  vmxnet3: prepare for version 7 changes
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=55f0395fcace9e675af2cbb96015ce1ae8856806

  vmxnet3: add support for capability registers
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=6f91f4ba046e5de6a6e579620b32b8ecf56873f7

  vmxnet3: add support for large passthrough BAR register
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=543fb67405410cc548a72d7a9a4087688d2f56ac

  vmxnet3: add support for out of order rx completion
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=2c5a5748105a6bb901579d365c6f93e79f282b69

  vmxnet3: add command to set ring buffer sizes
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=c7112ebd27ea0dbe4eecd5c96cad93757e34e73d

  vmxnet3: limit number of TXDs used for TSO packet
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=d2857b99a74b082368ee80f359372faa1d051043

  vmxnet3: use ext1 field to indicate encapsulated packet
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=60cafa0395c2bed44d13277ed328317ed16a58c0

  vmxnet3: update to version 7
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=acc38e041bd304621d4f59cea4849747d13bba9c

  vmxnet3: disable overlay offloads if UPT device does not support
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=a56b158a5078b8120d3d72fc9fd44efed5123b12

  vmxnet3: do not reschedule napi for rx processing
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/vmxnet3?id=5b91884bf50b21d34bd3daa5c8f8b7e92e0a2c46

  This is a request to bring latest Ubuntu LTS releases' vmxnet3 driver
  up to date with ToT Linux kernel.

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

2022-11-07 Thread Tim Gardner
Test kernels at (1). Please provide test results.

1 - https://kernel.ubuntu.com/~rtg/vmxnet3-update-to-6.0-lp1995886/

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

Title:
  vmxnet3: update to latest ToT

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  New
Status in linux source package in Kinetic:
  New

Bug description:
  This request is to port vmxnet3 patches to Ubuntu kernel. Below are
  the commits in order:

  vmxnet3: prepare for version 7 changes
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=55f0395fcace9e675af2cbb96015ce1ae8856806

  vmxnet3: add support for capability registers
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=6f91f4ba046e5de6a6e579620b32b8ecf56873f7

  vmxnet3: add support for large passthrough BAR register
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=543fb67405410cc548a72d7a9a4087688d2f56ac

  vmxnet3: add support for out of order rx completion
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=2c5a5748105a6bb901579d365c6f93e79f282b69

  vmxnet3: add command to set ring buffer sizes
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=c7112ebd27ea0dbe4eecd5c96cad93757e34e73d

  vmxnet3: limit number of TXDs used for TSO packet
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=d2857b99a74b082368ee80f359372faa1d051043

  vmxnet3: use ext1 field to indicate encapsulated packet
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=60cafa0395c2bed44d13277ed328317ed16a58c0

  vmxnet3: update to version 7
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=acc38e041bd304621d4f59cea4849747d13bba9c

  vmxnet3: disable overlay offloads if UPT device does not support
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=a56b158a5078b8120d3d72fc9fd44efed5123b12

  vmxnet3: do not reschedule napi for rx processing
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/vmxnet3?id=5b91884bf50b21d34bd3daa5c8f8b7e92e0a2c46

  This is a request to bring latest Ubuntu LTS releases' vmxnet3 driver
  up to date with ToT Linux kernel.

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

2022-11-07 Thread Tim Gardner
** Also affects: linux (Ubuntu Jammy)
   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/1995886

Title:
  vmxnet3: update to latest ToT

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  New
Status in linux source package in Kinetic:
  New

Bug description:
  This request is to port vmxnet3 patches to Ubuntu kernel. Below are
  the commits in order:

  vmxnet3: prepare for version 7 changes
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=55f0395fcace9e675af2cbb96015ce1ae8856806

  vmxnet3: add support for capability registers
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=6f91f4ba046e5de6a6e579620b32b8ecf56873f7

  vmxnet3: add support for large passthrough BAR register
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=543fb67405410cc548a72d7a9a4087688d2f56ac

  vmxnet3: add support for out of order rx completion
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=2c5a5748105a6bb901579d365c6f93e79f282b69

  vmxnet3: add command to set ring buffer sizes
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=c7112ebd27ea0dbe4eecd5c96cad93757e34e73d

  vmxnet3: limit number of TXDs used for TSO packet
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=d2857b99a74b082368ee80f359372faa1d051043

  vmxnet3: use ext1 field to indicate encapsulated packet
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=60cafa0395c2bed44d13277ed328317ed16a58c0

  vmxnet3: update to version 7
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=acc38e041bd304621d4f59cea4849747d13bba9c

  vmxnet3: disable overlay offloads if UPT device does not support
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=a56b158a5078b8120d3d72fc9fd44efed5123b12

  vmxnet3: do not reschedule napi for rx processing
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/vmxnet3?id=5b91884bf50b21d34bd3daa5c8f8b7e92e0a2c46

  This is a request to bring latest Ubuntu LTS releases' vmxnet3 driver
  up to date with ToT Linux kernel.

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

2022-11-07 Thread Ronak Doshi
Also, ensure below commits are present in the kernel. I am not sure if
these are present in Ubuntu latest LTS releases. So, please double check
and apply the above ones (in description) on the ones mentioned below.

vmxnet3: prepare for version 6 changes
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
next.git/commit/drivers/net/vmxnet3?id=69dbef0d1c22476c422ee255e99d0e112ddd829d

vmxnet3: add support for 32 Tx/Rx queues
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
next.git/commit/drivers/net/vmxnet3?id=39f9895a00f4c5f50e4e0a94f710c6a87afb1920

vmxnet3: add support for ESP IPv6 RSS
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
next.git/commit/drivers/net/vmxnet3?id=79d124bb36c0662e16e1ae01e7ff68ab80eb67a8

vmxnet3: set correct hash type based on rss information
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
next.git/commit/drivers/net/vmxnet3?id=b3973bb40041eb336188d16fcc249000ea3c4bf4

vmxnet3: increase maximum configurable mtu to 9190
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
next.git/commit/drivers/net/vmxnet3?id=8c5663e461e6914304bbbf2c1cf67e5dce18740f

vmxnet3: update to version 6
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
next.git/commit/drivers/net/vmxnet3?id=ce2639ad6921fbaf8a854b5d1b1033adee685e6e

vmxnet3: fix minimum vectors alloc issue
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
next.git/commit/drivers/net/vmxnet3?id=f71ef02f1a4a3c49962fa341ad8de19071f0f9bf

vmxnet3: remove power of 2 limitation on the queues
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
next.git/commit/drivers/net/vmxnet3?id=15ccf2f4b09c4443435e815b8086bc161da27e24

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

Title:
  vmxnet3: update to latest ToT

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  New
Status in linux source package in Kinetic:
  New

Bug description:
  This request is to port vmxnet3 patches to Ubuntu kernel. Below are
  the commits in order:

  vmxnet3: prepare for version 7 changes
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=55f0395fcace9e675af2cbb96015ce1ae8856806

  vmxnet3: add support for capability registers
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=6f91f4ba046e5de6a6e579620b32b8ecf56873f7

  vmxnet3: add support for large passthrough BAR register
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=543fb67405410cc548a72d7a9a4087688d2f56ac

  vmxnet3: add support for out of order rx completion
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=2c5a5748105a6bb901579d365c6f93e79f282b69

  vmxnet3: add command to set ring buffer sizes
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=c7112ebd27ea0dbe4eecd5c96cad93757e34e73d

  vmxnet3: limit number of TXDs used for TSO packet
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=d2857b99a74b082368ee80f359372faa1d051043

  vmxnet3: use ext1 field to indicate encapsulated packet
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=60cafa0395c2bed44d13277ed328317ed16a58c0

  vmxnet3: update to version 7
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=acc38e041bd304621d4f59cea4849747d13bba9c

  vmxnet3: disable overlay offloads if UPT device does not support
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=a56b158a5078b8120d3d72fc9fd44efed5123b12

  vmxnet3: do not reschedule napi for rx processing
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/vmxnet3?id=5b91884bf50b21d34bd3daa5c8f8b7e92e0a2c46

  This is a request to bring latest Ubuntu LTS releases' vmxnet3 driver
  up to date with ToT Linux kernel.

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

2022-11-07 Thread Tim Gardner
** Also affects: linux (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

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

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

Title:
  vmxnet3: update to latest ToT

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Kinetic:
  New

Bug description:
  This request is to port vmxnet3 patches to Ubuntu kernel. Below are
  the commits in order:

  vmxnet3: prepare for version 7 changes
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=55f0395fcace9e675af2cbb96015ce1ae8856806

  vmxnet3: add support for capability registers
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=6f91f4ba046e5de6a6e579620b32b8ecf56873f7

  vmxnet3: add support for large passthrough BAR register
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=543fb67405410cc548a72d7a9a4087688d2f56ac

  vmxnet3: add support for out of order rx completion
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=2c5a5748105a6bb901579d365c6f93e79f282b69

  vmxnet3: add command to set ring buffer sizes
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=c7112ebd27ea0dbe4eecd5c96cad93757e34e73d

  vmxnet3: limit number of TXDs used for TSO packet
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=d2857b99a74b082368ee80f359372faa1d051043

  vmxnet3: use ext1 field to indicate encapsulated packet
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=60cafa0395c2bed44d13277ed328317ed16a58c0

  vmxnet3: update to version 7
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=acc38e041bd304621d4f59cea4849747d13bba9c

  vmxnet3: disable overlay offloads if UPT device does not support
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=a56b158a5078b8120d3d72fc9fd44efed5123b12

  vmxnet3: do not reschedule napi for rx processing
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/vmxnet3?id=5b91884bf50b21d34bd3daa5c8f8b7e92e0a2c46

  This is a request to bring latest Ubuntu LTS releases' vmxnet3 driver
  up to date with ToT Linux kernel.

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

2022-11-07 Thread Ronak Doshi
This is not a bug, but a task to port the upstream patches to ongoing
ubuntu releases.

Thanks,
Ronak

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

Title:
  vmxnet3: update to latest ToT

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This request is to port vmxnet3 patches to Ubuntu kernel. Below are
  the commits in order:

  vmxnet3: prepare for version 7 changes
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=55f0395fcace9e675af2cbb96015ce1ae8856806

  vmxnet3: add support for capability registers
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=6f91f4ba046e5de6a6e579620b32b8ecf56873f7

  vmxnet3: add support for large passthrough BAR register
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=543fb67405410cc548a72d7a9a4087688d2f56ac

  vmxnet3: add support for out of order rx completion
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=2c5a5748105a6bb901579d365c6f93e79f282b69

  vmxnet3: add command to set ring buffer sizes
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=c7112ebd27ea0dbe4eecd5c96cad93757e34e73d

  vmxnet3: limit number of TXDs used for TSO packet
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=d2857b99a74b082368ee80f359372faa1d051043

  vmxnet3: use ext1 field to indicate encapsulated packet
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=60cafa0395c2bed44d13277ed328317ed16a58c0

  vmxnet3: update to version 7
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=acc38e041bd304621d4f59cea4849747d13bba9c

  vmxnet3: disable overlay offloads if UPT device does not support
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=a56b158a5078b8120d3d72fc9fd44efed5123b12

  vmxnet3: do not reschedule napi for rx processing
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/vmxnet3?id=5b91884bf50b21d34bd3daa5c8f8b7e92e0a2c46

  This is a request to bring latest Ubuntu LTS releases' vmxnet3 driver
  up to date with ToT Linux kernel.

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

2022-11-07 Thread Ronak Doshi
In general the request to bring the vmxnet3 driver in next upcoming
Ubuntu LTS release up-to-date with upstream repo.

Let me know if you need any clarifications.

Thanks,
Ronak

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

Title:
  vmxnet3: update to latest ToT

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This request is to port vmxnet3 patches to Ubuntu kernel. Below are
  the commits in order:

  vmxnet3: prepare for version 7 changes
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=55f0395fcace9e675af2cbb96015ce1ae8856806

  vmxnet3: add support for capability registers
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=6f91f4ba046e5de6a6e579620b32b8ecf56873f7

  vmxnet3: add support for large passthrough BAR register
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=543fb67405410cc548a72d7a9a4087688d2f56ac

  vmxnet3: add support for out of order rx completion
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=2c5a5748105a6bb901579d365c6f93e79f282b69

  vmxnet3: add command to set ring buffer sizes
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=c7112ebd27ea0dbe4eecd5c96cad93757e34e73d

  vmxnet3: limit number of TXDs used for TSO packet
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=d2857b99a74b082368ee80f359372faa1d051043

  vmxnet3: use ext1 field to indicate encapsulated packet
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=60cafa0395c2bed44d13277ed328317ed16a58c0

  vmxnet3: update to version 7
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=acc38e041bd304621d4f59cea4849747d13bba9c

  vmxnet3: disable overlay offloads if UPT device does not support
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=a56b158a5078b8120d3d72fc9fd44efed5123b12

  vmxnet3: do not reschedule napi for rx processing
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/vmxnet3?id=5b91884bf50b21d34bd3daa5c8f8b7e92e0a2c46

  This is a request to bring latest Ubuntu LTS releases' vmxnet3 driver
  up to date with ToT Linux kernel.

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

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

apport-collect 1995886

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

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

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

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

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

Title:
  vmxnet3: update to latest ToT

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This request is to port vmxnet3 patches to Ubuntu kernel. Below are
  the commits in order:

  vmxnet3: prepare for version 7 changes
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=55f0395fcace9e675af2cbb96015ce1ae8856806

  vmxnet3: add support for capability registers
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=6f91f4ba046e5de6a6e579620b32b8ecf56873f7

  vmxnet3: add support for large passthrough BAR register
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=543fb67405410cc548a72d7a9a4087688d2f56ac

  vmxnet3: add support for out of order rx completion
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=2c5a5748105a6bb901579d365c6f93e79f282b69

  vmxnet3: add command to set ring buffer sizes
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=c7112ebd27ea0dbe4eecd5c96cad93757e34e73d

  vmxnet3: limit number of TXDs used for TSO packet
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=d2857b99a74b082368ee80f359372faa1d051043

  vmxnet3: use ext1 field to indicate encapsulated packet
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=60cafa0395c2bed44d13277ed328317ed16a58c0

  vmxnet3: update to version 7
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=acc38e041bd304621d4f59cea4849747d13bba9c

  vmxnet3: disable overlay offloads if UPT device does not support
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=a56b158a5078b8120d3d72fc9fd44efed5123b12

  vmxnet3: do not reschedule napi for rx processing
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/vmxnet3?id=5b91884bf50b21d34bd3daa5c8f8b7e92e0a2c46

  This is a request to bring latest Ubuntu LTS releases' vmxnet3 driver
  up to date with ToT Linux kernel.

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

2022-11-07 Thread Ronak Doshi
== SRU Justification ==
Recently, a couple of features went in vmxnet3 driver. VMWare is requesting 
these patches in
Bionic and Xenial or upcoming all LTS releases.

== Fixes ==
Mentioned in the description

== Regression Potential ==
Low. Limited to vmxnet3 driver.

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

Title:
  vmxnet3: update to latest ToT

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This request is to port vmxnet3 patches to Ubuntu kernel. Below are
  the commits in order:

  vmxnet3: prepare for version 7 changes
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=55f0395fcace9e675af2cbb96015ce1ae8856806

  vmxnet3: add support for capability registers
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=6f91f4ba046e5de6a6e579620b32b8ecf56873f7

  vmxnet3: add support for large passthrough BAR register
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=543fb67405410cc548a72d7a9a4087688d2f56ac

  vmxnet3: add support for out of order rx completion
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=2c5a5748105a6bb901579d365c6f93e79f282b69

  vmxnet3: add command to set ring buffer sizes
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=c7112ebd27ea0dbe4eecd5c96cad93757e34e73d

  vmxnet3: limit number of TXDs used for TSO packet
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=d2857b99a74b082368ee80f359372faa1d051043

  vmxnet3: use ext1 field to indicate encapsulated packet
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=60cafa0395c2bed44d13277ed328317ed16a58c0

  vmxnet3: update to version 7
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=acc38e041bd304621d4f59cea4849747d13bba9c

  vmxnet3: disable overlay offloads if UPT device does not support
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=a56b158a5078b8120d3d72fc9fd44efed5123b12

  vmxnet3: do not reschedule napi for rx processing
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/vmxnet3?id=5b91884bf50b21d34bd3daa5c8f8b7e92e0a2c46

  This is a request to bring latest Ubuntu LTS releases' vmxnet3 driver
  up to date with ToT Linux kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995886/+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 1995886] [NEW] vmxnet3: update to latest ToT

2022-11-07 Thread Ronak Doshi
Public bug reported:

This request is to port vmxnet3 patches to Ubuntu kernel. Below are the
commits in order:

vmxnet3: prepare for version 7 changes
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
next.git/commit/drivers/net/vmxnet3?id=55f0395fcace9e675af2cbb96015ce1ae8856806

vmxnet3: add support for capability registers
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
next.git/commit/drivers/net/vmxnet3?id=6f91f4ba046e5de6a6e579620b32b8ecf56873f7

vmxnet3: add support for large passthrough BAR register
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
next.git/commit/drivers/net/vmxnet3?id=543fb67405410cc548a72d7a9a4087688d2f56ac

vmxnet3: add support for out of order rx completion
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
next.git/commit/drivers/net/vmxnet3?id=2c5a5748105a6bb901579d365c6f93e79f282b69

vmxnet3: add command to set ring buffer sizes
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
next.git/commit/drivers/net/vmxnet3?id=c7112ebd27ea0dbe4eecd5c96cad93757e34e73d

vmxnet3: limit number of TXDs used for TSO packet
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
next.git/commit/drivers/net/vmxnet3?id=d2857b99a74b082368ee80f359372faa1d051043

vmxnet3: use ext1 field to indicate encapsulated packet
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
next.git/commit/drivers/net/vmxnet3?id=60cafa0395c2bed44d13277ed328317ed16a58c0

vmxnet3: update to version 7
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
next.git/commit/drivers/net/vmxnet3?id=acc38e041bd304621d4f59cea4849747d13bba9c

vmxnet3: disable overlay offloads if UPT device does not support
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
next.git/commit/drivers/net/vmxnet3?id=a56b158a5078b8120d3d72fc9fd44efed5123b12

vmxnet3: do not reschedule napi for rx processing
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/vmxnet3?id=5b91884bf50b21d34bd3daa5c8f8b7e92e0a2c46

This is a request to bring latest Ubuntu LTS releases' vmxnet3 driver up
to date with ToT Linux kernel.

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

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

Title:
  vmxnet3: update to latest ToT

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This request is to port vmxnet3 patches to Ubuntu kernel. Below are
  the commits in order:

  vmxnet3: prepare for version 7 changes
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=55f0395fcace9e675af2cbb96015ce1ae8856806

  vmxnet3: add support for capability registers
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=6f91f4ba046e5de6a6e579620b32b8ecf56873f7

  vmxnet3: add support for large passthrough BAR register
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=543fb67405410cc548a72d7a9a4087688d2f56ac

  vmxnet3: add support for out of order rx completion
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=2c5a5748105a6bb901579d365c6f93e79f282b69

  vmxnet3: add command to set ring buffer sizes
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=c7112ebd27ea0dbe4eecd5c96cad93757e34e73d

  vmxnet3: limit number of TXDs used for TSO packet
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=d2857b99a74b082368ee80f359372faa1d051043

  vmxnet3: use ext1 field to indicate encapsulated packet
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=60cafa0395c2bed44d13277ed328317ed16a58c0

  vmxnet3: update to version 7
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=acc38e041bd304621d4f59cea4849747d13bba9c

  vmxnet3: disable overlay offloads if UPT device does not support
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=a56b158a5078b8120d3d72fc9fd44efed5123b12

  vmxnet3: do not reschedule napi for rx processing
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/vmxnet3?id=5b91884bf50b21d34bd3daa5c8f8b7e92e0a2c46

  This is a request to bring latest Ubuntu LTS releases' vmxnet3 driver
  up to date with ToT Linux kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995886/+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 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)

2022-11-07 Thread Ferran Delgado
I've updated to the latest ubuntu 22.10 with kernel 5.19.0-23-generic and the 
issue isn't fixed. 
I've tried to disable psr by adding i915.enable_psr=0 and still flickering. The 
only thing that solved the issue was adding nomodeset to the 
GRUB_CMDLINE_LINUX_DEFAULT but now I cannot connect an external monitor.

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

Title:
  [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0
  intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @
  18/1/2022

  Booting into desktop gets heavy screen flickering and disforming (unusable)
  both booting on xorg and wayland

  on kernel 5.13 it did not occur so heavy (only little glitches once in
  a while see bug 1948778)

  adding the kernel paramater intel_idle.max_cstate=4 fixed this

  i had these same bugs on this machine before:

  https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644

  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-17-generic 5.15.0-17.17
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lotuspsychje   1201 F pipewire-media-
lotuspsychje   1207 F pulseaudio
   /dev/snd/seq:lotuspsychje   1193 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 04:22:00 2022
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth 
Adapter
   Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 
Camera
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook N7x0WU
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic 
root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash 
intel_idle.max_cstate=4 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-17-generic N/A
   linux-backports-modules-5.15.0-17-generic  N/A
   linux-firmware 1.204
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2019
  dmi.bios.release: 7.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 7.13
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N7x0WU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.14
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: N7x0WU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

apport-collect 1995787

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

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

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

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

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

Title:
  After upgrading my system suddenly my PC got freeze and start showing
  EXT4-fs error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading my system suddenly my PC got freeze and start showing
  black screen and EXT4-fs error these are some last updated packages
  below and I user sudo apt upgrade cmd.

  
  2022-11-04 09:15:24 upgrade code-insiders:amd64 1.74.0-1667455053 
1.74.0-1667502703
  2022-11-04 09:15:38 upgrade mutter-common:all 42.2-0ubuntu1 42.5-0ubuntu1
  2022-11-04 09:15:38 upgrade gir1.2-mutter-10:amd64 42.2-0ubuntu1 42.5-0ubuntu1
  2022-11-04 09:15:38 upgrade libmutter-10-0:amd64 42.2-0ubuntu1 42.5-0ubuntu1
  2022-11-05 08:33:17 upgrade tzdata:all 2022e-0ubuntu0.22.04.0 
2022f-0ubuntu0.22.04.0
  2022-11-05 11:37:45 upgrade code-insiders:amd64 1.74.0-1667502703 
1.74.0-1667540431
  2022-11-05 11:37:58 upgrade nodejs:amd64 16.18.0-deb-1nodesource1 
16.18.1-deb-1nodesource1
  2022-11-06 12:12:28 upgrade distro-info-data:all 0.52ubuntu0.1 0.52ubuntu0.2

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.14
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  6 12:55:01 2022
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

2022-11-07 Thread Julian Andres Klode
Actions: cherry-pick two patches for kinetic and upload new upstream
release to lunar.

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

Title:
  FTBFS on kinetic

Status in linux package in Ubuntu:
  Fix Released
Status in strace package in Ubuntu:
  Triaged

Bug description:
  As can be seen in [1], strace FTBFS in kinetic: this is caused by the
  kernel headers (linux-libc-dev) which do not define F_GETLK64 and
  other on 64b builds because the kernel contains a bogus commit
  (306f7cc1e906 "uapi: always define F_GETLK64/F_SETLK64/F_SETLKW64 in
  fcntl.h"). This commit actually did the opposite of what it was
  supposed to do, namely defining those macros even on 64b builds. There
  is an attempt here to fix this which was not merged yet:
  
https://lore.kernel.org/lkml/cajf2gtqtnmoeb62-63ou8y4dbrdym7iztdtfluxx9u0ltwu...@mail.gmail.com/T/

  [1]: https://launchpadlibrarian.net/625441996/buildlog_ubuntu-kinetic-
  amd64.strace_5.16-0ubuntu4_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990964/+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 1991676] Re: Package grub-efi-arm64-signed 1.173.2~18.04.1+2.04-1ubuntu47.4 from bionic-proposed fails to install/upgrade (grub-install: error: efibootmgr: not found.)

2022-11-07 Thread Julian Andres Klode
** Changed in: grub2-signed (Ubuntu Bionic)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

** Changed in: grub2-signed (Ubuntu)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

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

Title:
  Package grub-efi-arm64-signed 1.173.2~18.04.1+2.04-1ubuntu47.4 from
  bionic-proposed fails to install/upgrade (grub-install: error:
  efibootmgr: not found.)

Status in ubuntu-kernel-tests:
  New
Status in grub2-signed package in Ubuntu:
  Invalid
Status in linux-hwe-5.4 package in Ubuntu:
  Confirmed
Status in grub2-signed source package in Bionic:
  Triaged
Status in linux-hwe-5.4 source package in Bionic:
  Confirmed

Bug description:
  The ADT tests for arm64 kernels in Bionic are failing during the setup
  phase with the following errors:

  Setting up grub-efi-arm64-signed (1.173.2~18.04.1+2.04-1ubuntu47.4) ...
  Installing for arm64-efi platform.
  grub-install: error: efibootmgr: not found.
  dpkg: error processing package grub-efi-arm64-signed (--configure):
   installed grub-efi-arm64-signed package post-installation script subprocess 
returned error exit status 1
  Setting up libx11-6:arm64 (2:1.6.4-3ubuntu0.5) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  Processing triggers for libc-bin (2.27-3ubuntu1.6) ...
  Errors were encountered while processing:
   grub-efi-arm64-signed
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  blame: 
  badpkg: testbed setup commands failed with status 100
  autopkgtest [15:12:03]: ERROR: erroneous package: testbed setup commands 
failed with status 100

  ADT test log:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/l/linux-hwe-5.4/20220930_151219_13ac3@/log.gz

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

2022-11-07 Thread Julian Andres Klode
** Changed in: grub2-unsigned (Ubuntu)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

** Changed in: grub2-signed (Ubuntu)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

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

[Kernel-packages] [Bug 1995787] Re: After upgrading my system suddenly my PC got freeze and start showing EXT4-fs error

2022-11-07 Thread Nick Rosbrook
** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)

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

Title:
  After upgrading my system suddenly my PC got freeze and start showing
  EXT4-fs error

Status in linux package in Ubuntu:
  New

Bug description:
  After upgrading my system suddenly my PC got freeze and start showing
  black screen and EXT4-fs error these are some last updated packages
  below and I user sudo apt upgrade cmd.

  
  2022-11-04 09:15:24 upgrade code-insiders:amd64 1.74.0-1667455053 
1.74.0-1667502703
  2022-11-04 09:15:38 upgrade mutter-common:all 42.2-0ubuntu1 42.5-0ubuntu1
  2022-11-04 09:15:38 upgrade gir1.2-mutter-10:amd64 42.2-0ubuntu1 42.5-0ubuntu1
  2022-11-04 09:15:38 upgrade libmutter-10-0:amd64 42.2-0ubuntu1 42.5-0ubuntu1
  2022-11-05 08:33:17 upgrade tzdata:all 2022e-0ubuntu0.22.04.0 
2022f-0ubuntu0.22.04.0
  2022-11-05 11:37:45 upgrade code-insiders:amd64 1.74.0-1667502703 
1.74.0-1667540431
  2022-11-05 11:37:58 upgrade nodejs:amd64 16.18.0-deb-1nodesource1 
16.18.1-deb-1nodesource1
  2022-11-06 12:12:28 upgrade distro-info-data:all 0.52ubuntu0.1 0.52ubuntu0.2

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.14
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  6 12:55:01 2022
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995787/+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 1995787] [NEW] After upgrading my system suddenly my PC got freeze and start showing EXT4-fs error

2022-11-07 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

After upgrading my system suddenly my PC got freeze and start showing
black screen and EXT4-fs error these are some last updated packages
below and I user sudo apt upgrade cmd.


2022-11-04 09:15:24 upgrade code-insiders:amd64 1.74.0-1667455053 
1.74.0-1667502703
2022-11-04 09:15:38 upgrade mutter-common:all 42.2-0ubuntu1 42.5-0ubuntu1
2022-11-04 09:15:38 upgrade gir1.2-mutter-10:amd64 42.2-0ubuntu1 42.5-0ubuntu1
2022-11-04 09:15:38 upgrade libmutter-10-0:amd64 42.2-0ubuntu1 42.5-0ubuntu1
2022-11-05 08:33:17 upgrade tzdata:all 2022e-0ubuntu0.22.04.0 
2022f-0ubuntu0.22.04.0
2022-11-05 11:37:45 upgrade code-insiders:amd64 1.74.0-1667502703 
1.74.0-1667540431
2022-11-05 11:37:58 upgrade nodejs:amd64 16.18.0-deb-1nodesource1 
16.18.1-deb-1nodesource1
2022-11-06 12:12:28 upgrade distro-info-data:all 0.52ubuntu0.1 0.52ubuntu0.2

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-release-upgrader-core 1:22.04.14
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
Uname: Linux 5.15.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov  6 12:55:01 2022
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug dist-upgrade jammy wayland-session
-- 
After upgrading my system suddenly my PC got freeze and start showing EXT4-fs 
error
https://bugs.launchpad.net/bugs/1995787
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1983143] Re: AMD Rembrandt: DP tunneling fails with Thunderbolt monitors

2022-11-07 Thread Timo Aaltonen
so we don't have that in kinetic and up

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

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

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

Title:
  AMD Rembrandt: DP tunneling fails with Thunderbolt monitors

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux-oem-6.0 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Triaged
Status in linux-oem-5.14 source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Summary]
  No video output on Thunderbolt monitor.
  1. Connect monitor to DUT directly
  2. Connect monitor to DUT via Docking

  System can detect the monitor and able to change display mode but no
  output on the monitor

  [Steps to reproduce]
  1. Boot to OS
  2. Plug an external monitor via thunderbolt port

  [Expected result]
  Display on external monitor normally

  [Actual result]
  No vidoe ouput on external monitor

  [Failure rate]
  3/3

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1983143/+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 1995870] Missing required logs.

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

apport-collect 1995870

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

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

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

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

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

Title:
  BUG: scheduling while atomic: ip/1210/0x0200 on xenial/hwe rumford

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  There is a bug being triggered on a udelay within the tg3 driver with
  xenial/linux-hwe 4.15.0-197.208~16.04.1 on rumford.

  This has been observed in multiple cycles during boot-testing.

  [   27.437584] BUG: scheduling while atomic: ip/1210/0x0200
  [   27.468440] Modules linked in: nls_iso8859_1 intel_rapl sb_edac 
x86_pkg_temp_thermal intel_powerclamp coretemp ipmi_ssif kvm_intel hpilo kvm 
irqbypass intel_cstate shpchp ioatdma dca intel_rapl_perf ipmi_si ipmi_devintf 
lpc_ich ipmi_msghandler acpi_power_meter mac_hid ib_iser rdma_cm iw_cm ib_cm 
ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mgag200 
i2c_algo_bit ses crct10dif_pclmul enclosure crc32_pclmul ttm 
ghash_clmulni_intel drm_kms_helper mlx5_core pcbc syscopyarea aesni_intel mlxfw 
sysfillrect sysimgblt aes_x86_64 fb_sys_fops tg3 devlink crypto_simd hpsa nvme 
glue_helper ptp drm cryptd pps_core nvme_core scsi_transport_sas wmi
  [   27.468491] CPU: 1 PID: 1210 Comm: ip Not tainted 4.15.0-197-generic 
#208~16.04.1-Ubuntu
  [   27.468493] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, 
BIOS P89 05/21/2018
  [   27.468494] Call Trace:
  [   27.468508]  dump_stack+0x6d/0x8b
  [   27.468515]  __schedule_bug+0x54/0x70
  [   27.468519]  __schedule+0x635/0x8b0
  [   27.468522]  schedule+0x36/0x80
  [   27.468527]  schedule_hrtimeout_range_clock+0xbc/0x1b0
  [   27.468532]  ? __hrtimer_init+0x90/0x90
  [   27.468536]  schedule_hrtimeout_range+0x13/0x20
  [   27.468539]  usleep_range+0x62/0x90
  [   27.468547]  tg3_ape_event_lock+0x36/0xa0 [tg3]
  [   27.468552]  tg3_ape_driver_state_change.part.69+0xc6/0x160 [tg3]
  [   27.468557]  tg3_start+0xebc/0x10b0 [tg3]
  [   27.468563]  tg3_open+0x130/0x280 [tg3]
  [   27.468568]  __dev_open+0xd7/0x150
  [   27.468572]  __dev_change_flags+0x186/0x1c0
  [   27.468575]  dev_change_flags+0x29/0x70
  [   27.468580]  do_setlink+0x355/0xd90
  [   27.468589]  ? nla_parse+0xa7/0x120
  [   27.468592]  rtnl_newlink+0x773/0x8f0
  [   27.468597]  ? do_anonymous_page+0x24b/0x430
  [   27.468605]  ? ns_capable_common+0x2b/0x50
  [   27.468608]  ? ns_capable+0x10/0x20
  [   27.468612]  rtnetlink_rcv_msg+0x205/0x290
  [   27.468615]  ? _cond_resched+0x1a/0x50
  [   27.468620]  ? __kmalloc_node_track_caller+0x201/0x2c0
  [   27.468623]  ? rtnl_calcit.isra.25+0x100/0x100
  [   27.468627]  netlink_rcv_skb+0xd9/0x110
  [   27.468630]  rtnetlink_rcv+0x15/0x20
  [   27.468633]  netlink_unicast+0x198/0x260
  [   27.468637]  netlink_sendmsg+0x2ea/0x410
  [   27.468640]  sock_sendmsg+0x3e/0x50
  [   27.468642]  ___sys_sendmsg+0x2e9/0x300
  [   27.468646]  ? lru_cache_add_active_or_unevictable+0x36/0xb0
  [   27.468649]  ? do_anonymous_page+0x24b/0x430
  [   27.468653]  ? __handle_mm_fault+0xae7/0xc80
  [   27.468657]  __sys_sendmsg+0x54/0x90
  [   27.468659]  ? __sys_sendmsg+0x54/0x90
  [   27.468662]  SyS_sendmsg+0x12/0x20
  [   27.468667]  do_syscall_64+0x73/0x130
  [   27.468670]  entry_SYSCALL_64_after_hwframe+0x41/0xa6
  [   27.468673] RIP: 0033:0x7f285dd57590
  [   27.468675] RSP: 002b:7ffd4370bf38 EFLAGS: 0246 ORIG_RAX: 
002e
  [   27.468678] RAX: ffda RBX: 7ffd43714040 RCX: 
7f285dd57590
  [   27.468679] RDX:  RSI: 7ffd4370bf80 RDI: 
0003
  [   27.468681] RBP: 6364ddd8 R08: 0040 R09: 
0008
  [   27.468682] R10: 05e7 R11: 0246 R12: 
7ffd4370bf80
  [   27.468683] R13:  R14: 006573a0 R15: 
7ffd43714018
  [   27.468703] NOHZ: local_softirq_pending 282

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995870/+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 1995870] [NEW] BUG: scheduling while atomic: ip/1210/0x00000200 on xenial/hwe rumford

2022-11-07 Thread Luke Nowakowski-Krijger
Public bug reported:

There is a bug being triggered on a udelay within the tg3 driver with
xenial/linux-hwe 4.15.0-197.208~16.04.1 on rumford.

This has been observed in multiple cycles during boot-testing.

[   27.437584] BUG: scheduling while atomic: ip/1210/0x0200
[   27.468440] Modules linked in: nls_iso8859_1 intel_rapl sb_edac 
x86_pkg_temp_thermal intel_powerclamp coretemp ipmi_ssif kvm_intel hpilo kvm 
irqbypass intel_cstate shpchp ioatdma dca intel_rapl_perf ipmi_si ipmi_devintf 
lpc_ich ipmi_msghandler acpi_power_meter mac_hid ib_iser rdma_cm iw_cm ib_cm 
ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mgag200 
i2c_algo_bit ses crct10dif_pclmul enclosure crc32_pclmul ttm 
ghash_clmulni_intel drm_kms_helper mlx5_core pcbc syscopyarea aesni_intel mlxfw 
sysfillrect sysimgblt aes_x86_64 fb_sys_fops tg3 devlink crypto_simd hpsa nvme 
glue_helper ptp drm cryptd pps_core nvme_core scsi_transport_sas wmi
[   27.468491] CPU: 1 PID: 1210 Comm: ip Not tainted 4.15.0-197-generic 
#208~16.04.1-Ubuntu
[   27.468493] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS 
P89 05/21/2018
[   27.468494] Call Trace:
[   27.468508]  dump_stack+0x6d/0x8b
[   27.468515]  __schedule_bug+0x54/0x70
[   27.468519]  __schedule+0x635/0x8b0
[   27.468522]  schedule+0x36/0x80
[   27.468527]  schedule_hrtimeout_range_clock+0xbc/0x1b0
[   27.468532]  ? __hrtimer_init+0x90/0x90
[   27.468536]  schedule_hrtimeout_range+0x13/0x20
[   27.468539]  usleep_range+0x62/0x90
[   27.468547]  tg3_ape_event_lock+0x36/0xa0 [tg3]
[   27.468552]  tg3_ape_driver_state_change.part.69+0xc6/0x160 [tg3]
[   27.468557]  tg3_start+0xebc/0x10b0 [tg3]
[   27.468563]  tg3_open+0x130/0x280 [tg3]
[   27.468568]  __dev_open+0xd7/0x150
[   27.468572]  __dev_change_flags+0x186/0x1c0
[   27.468575]  dev_change_flags+0x29/0x70
[   27.468580]  do_setlink+0x355/0xd90
[   27.468589]  ? nla_parse+0xa7/0x120
[   27.468592]  rtnl_newlink+0x773/0x8f0
[   27.468597]  ? do_anonymous_page+0x24b/0x430
[   27.468605]  ? ns_capable_common+0x2b/0x50
[   27.468608]  ? ns_capable+0x10/0x20
[   27.468612]  rtnetlink_rcv_msg+0x205/0x290
[   27.468615]  ? _cond_resched+0x1a/0x50
[   27.468620]  ? __kmalloc_node_track_caller+0x201/0x2c0
[   27.468623]  ? rtnl_calcit.isra.25+0x100/0x100
[   27.468627]  netlink_rcv_skb+0xd9/0x110
[   27.468630]  rtnetlink_rcv+0x15/0x20
[   27.468633]  netlink_unicast+0x198/0x260
[   27.468637]  netlink_sendmsg+0x2ea/0x410
[   27.468640]  sock_sendmsg+0x3e/0x50
[   27.468642]  ___sys_sendmsg+0x2e9/0x300
[   27.468646]  ? lru_cache_add_active_or_unevictable+0x36/0xb0
[   27.468649]  ? do_anonymous_page+0x24b/0x430
[   27.468653]  ? __handle_mm_fault+0xae7/0xc80
[   27.468657]  __sys_sendmsg+0x54/0x90
[   27.468659]  ? __sys_sendmsg+0x54/0x90
[   27.468662]  SyS_sendmsg+0x12/0x20
[   27.468667]  do_syscall_64+0x73/0x130
[   27.468670]  entry_SYSCALL_64_after_hwframe+0x41/0xa6
[   27.468673] RIP: 0033:0x7f285dd57590
[   27.468675] RSP: 002b:7ffd4370bf38 EFLAGS: 0246 ORIG_RAX: 
002e
[   27.468678] RAX: ffda RBX: 7ffd43714040 RCX: 7f285dd57590
[   27.468679] RDX:  RSI: 7ffd4370bf80 RDI: 0003
[   27.468681] RBP: 6364ddd8 R08: 0040 R09: 0008
[   27.468682] R10: 05e7 R11: 0246 R12: 7ffd4370bf80
[   27.468683] R13:  R14: 006573a0 R15: 7ffd43714018
[   27.468703] NOHZ: local_softirq_pending 282

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

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

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

Title:
  BUG: scheduling while atomic: ip/1210/0x0200 on xenial/hwe rumford

Status in linux package in Ubuntu:
  New

Bug description:
  There is a bug being triggered on a udelay within the tg3 driver with
  xenial/linux-hwe 4.15.0-197.208~16.04.1 on rumford.

  This has been observed in multiple cycles during boot-testing.

  [   27.437584] BUG: scheduling while atomic: ip/1210/0x0200
  [   27.468440] Modules linked in: nls_iso8859_1 intel_rapl sb_edac 
x86_pkg_temp_thermal intel_powerclamp coretemp ipmi_ssif kvm_intel hpilo kvm 
irqbypass intel_cstate shpchp ioatdma dca intel_rapl_perf ipmi_si ipmi_devintf 
lpc_ich ipmi_msghandler acpi_power_meter mac_hid ib_iser rdma_cm iw_cm ib_cm 
ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mgag200 
i2c_algo_bit ses crct10dif_pclmul enclosure crc32_pclmul ttm 
ghash_clmulni_intel drm_kms_helper mlx5_core pcbc syscopyarea 

[Kernel-packages] [Bug 1995870] [NEW] BUG: scheduling while atomic: ip/1210/0x00000200 on xenial/hwe rumford

2022-11-07 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

There is a bug being triggered on a udelay within the tg3 driver with
xenial/linux-hwe 4.15.0-197.208~16.04.1 on rumford.

This has been observed in multiple cycles during boot-testing.

[   27.437584] BUG: scheduling while atomic: ip/1210/0x0200
[   27.468440] Modules linked in: nls_iso8859_1 intel_rapl sb_edac 
x86_pkg_temp_thermal intel_powerclamp coretemp ipmi_ssif kvm_intel hpilo kvm 
irqbypass intel_cstate shpchp ioatdma dca intel_rapl_perf ipmi_si ipmi_devintf 
lpc_ich ipmi_msghandler acpi_power_meter mac_hid ib_iser rdma_cm iw_cm ib_cm 
ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mgag200 
i2c_algo_bit ses crct10dif_pclmul enclosure crc32_pclmul ttm 
ghash_clmulni_intel drm_kms_helper mlx5_core pcbc syscopyarea aesni_intel mlxfw 
sysfillrect sysimgblt aes_x86_64 fb_sys_fops tg3 devlink crypto_simd hpsa nvme 
glue_helper ptp drm cryptd pps_core nvme_core scsi_transport_sas wmi
[   27.468491] CPU: 1 PID: 1210 Comm: ip Not tainted 4.15.0-197-generic 
#208~16.04.1-Ubuntu
[   27.468493] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS 
P89 05/21/2018
[   27.468494] Call Trace:
[   27.468508]  dump_stack+0x6d/0x8b
[   27.468515]  __schedule_bug+0x54/0x70
[   27.468519]  __schedule+0x635/0x8b0
[   27.468522]  schedule+0x36/0x80
[   27.468527]  schedule_hrtimeout_range_clock+0xbc/0x1b0
[   27.468532]  ? __hrtimer_init+0x90/0x90
[   27.468536]  schedule_hrtimeout_range+0x13/0x20
[   27.468539]  usleep_range+0x62/0x90
[   27.468547]  tg3_ape_event_lock+0x36/0xa0 [tg3]
[   27.468552]  tg3_ape_driver_state_change.part.69+0xc6/0x160 [tg3]
[   27.468557]  tg3_start+0xebc/0x10b0 [tg3]
[   27.468563]  tg3_open+0x130/0x280 [tg3]
[   27.468568]  __dev_open+0xd7/0x150
[   27.468572]  __dev_change_flags+0x186/0x1c0
[   27.468575]  dev_change_flags+0x29/0x70
[   27.468580]  do_setlink+0x355/0xd90
[   27.468589]  ? nla_parse+0xa7/0x120
[   27.468592]  rtnl_newlink+0x773/0x8f0
[   27.468597]  ? do_anonymous_page+0x24b/0x430
[   27.468605]  ? ns_capable_common+0x2b/0x50
[   27.468608]  ? ns_capable+0x10/0x20
[   27.468612]  rtnetlink_rcv_msg+0x205/0x290
[   27.468615]  ? _cond_resched+0x1a/0x50
[   27.468620]  ? __kmalloc_node_track_caller+0x201/0x2c0
[   27.468623]  ? rtnl_calcit.isra.25+0x100/0x100
[   27.468627]  netlink_rcv_skb+0xd9/0x110
[   27.468630]  rtnetlink_rcv+0x15/0x20
[   27.468633]  netlink_unicast+0x198/0x260
[   27.468637]  netlink_sendmsg+0x2ea/0x410
[   27.468640]  sock_sendmsg+0x3e/0x50
[   27.468642]  ___sys_sendmsg+0x2e9/0x300
[   27.468646]  ? lru_cache_add_active_or_unevictable+0x36/0xb0
[   27.468649]  ? do_anonymous_page+0x24b/0x430
[   27.468653]  ? __handle_mm_fault+0xae7/0xc80
[   27.468657]  __sys_sendmsg+0x54/0x90
[   27.468659]  ? __sys_sendmsg+0x54/0x90
[   27.468662]  SyS_sendmsg+0x12/0x20
[   27.468667]  do_syscall_64+0x73/0x130
[   27.468670]  entry_SYSCALL_64_after_hwframe+0x41/0xa6
[   27.468673] RIP: 0033:0x7f285dd57590
[   27.468675] RSP: 002b:7ffd4370bf38 EFLAGS: 0246 ORIG_RAX: 
002e
[   27.468678] RAX: ffda RBX: 7ffd43714040 RCX: 7f285dd57590
[   27.468679] RDX:  RSI: 7ffd4370bf80 RDI: 0003
[   27.468681] RBP: 6364ddd8 R08: 0040 R09: 0008
[   27.468682] R10: 05e7 R11: 0246 R12: 7ffd4370bf80
[   27.468683] R13:  R14: 006573a0 R15: 7ffd43714018
[   27.468703] NOHZ: local_softirq_pending 282

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

-- 
BUG: scheduling while atomic: ip/1210/0x0200 on xenial/hwe rumford
https://bugs.launchpad.net/bugs/1995870
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1983143] Re: AMD Rembrandt: DP tunneling fails with Thunderbolt monitors

2022-11-07 Thread Timo Aaltonen
** Also affects: linux (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

Title:
  AMD Rembrandt: DP tunneling fails with Thunderbolt monitors

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux-oem-6.0 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  New
Status in linux-oem-5.14 source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Summary]
  No video output on Thunderbolt monitor.
  1. Connect monitor to DUT directly
  2. Connect monitor to DUT via Docking

  System can detect the monitor and able to change display mode but no
  output on the monitor

  [Steps to reproduce]
  1. Boot to OS
  2. Plug an external monitor via thunderbolt port

  [Expected result]
  Display on external monitor normally

  [Actual result]
  No vidoe ouput on external monitor

  [Failure rate]
  3/3

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1983143/+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 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)

2022-11-07 Thread Ferran Delgado
I'm having the same flickering issue with Ubuntu 18.04 image from the
dell recovery image. And I also tried Ubuntu 22.04

It worked fine before and the flickering started when I changed the motherboard.
I've tried most of the flags on the grub config but the only one that worked 
was `nomodeset` but then I cannot use any external monitor. 

For what I'm reading around there's no final solution right?

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

Title:
  [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0
  intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @
  18/1/2022

  Booting into desktop gets heavy screen flickering and disforming (unusable)
  both booting on xorg and wayland

  on kernel 5.13 it did not occur so heavy (only little glitches once in
  a while see bug 1948778)

  adding the kernel paramater intel_idle.max_cstate=4 fixed this

  i had these same bugs on this machine before:

  https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644

  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-17-generic 5.15.0-17.17
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lotuspsychje   1201 F pipewire-media-
lotuspsychje   1207 F pulseaudio
   /dev/snd/seq:lotuspsychje   1193 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 04:22:00 2022
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth 
Adapter
   Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 
Camera
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook N7x0WU
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic 
root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash 
intel_idle.max_cstate=4 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-17-generic N/A
   linux-backports-modules-5.15.0-17-generic  N/A
   linux-firmware 1.204
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2019
  dmi.bios.release: 7.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 7.13
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N7x0WU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.14
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: N7x0WU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

2022-11-07 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  ACPI BIOS Error

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  version.log
  Ubuntu 5.15.0-52.58-generic 5.15.60

  
  lspci-vnvn.log
  00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 30h-3fh) Processor Root Complex [1022:1422]
Subsystem: ASUSTeK Computer Inc. Family 15h (Models 30h-3fh) Processor 
Root Complex [1043:85cb]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag+ RBE+ FLReset-
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 256 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis- 
NROPrPrP- LTR-
 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt+ 
EETLPPrefix+, MaxEETLPPrefixes 1
 EmergencyPowerReduction Not Supported, 
EmergencyPowerReductionInit-
 FRS-
 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- 
OBFF Disabled,
 AtomicOpsCtl: ReqEn-
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: fee02004  Data: 0026
Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 
Len=010 
Capabilities: [270 v1] Secondary PCI Express
LnkCtl3: LnkEquIntrruptEn- PerformEqu-
LaneErrStat: 0
Capabilities: [2b0 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [2c0 v1] Page Request Interface (PRI)
PRICtl: Enable- Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 0020, Page Request Allocation: 

Capabilities: [2d0 v1] Process Address Space ID (PASID)
PASIDCap: Exec- Priv-, Max PASID Width: 10
PASIDCtl: Enable- Exec- Priv-
Kernel driver in use: radeon
Kernel modules: radeon, amdgpu

  00:01.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri 
HDMI/DP Audio Controller [1002:1308]
Subsystem: ASUSTeK Computer Inc. Kaveri HDMI/DP Audio Controller 
[1043:85cb]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag+ RBE+ FLReset-
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 256 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis- 
NROPrPrP- LTR-
 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt+ 
EETLPPrefix+, MaxEETLPPrefixes 1
 EmergencyPowerReduction Not Supported, 
EmergencyPowerReductionInit-
 FRS-
 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- 
OBFF Disabled,
 AtomicOpsCtl: ReqEn-
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: fee08004  Data: 0025
Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 
Len=010 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

  00:02.0 Host bridge 

[Kernel-packages] [Bug 1995859] [NEW] ACPI BIOS Error

2022-11-07 Thread bygot
Public bug reported:

version.log
Ubuntu 5.15.0-52.58-generic 5.15.60


lspci-vnvn.log
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 30h-3fh) Processor Root Complex [1022:1422]
Subsystem: ASUSTeK Computer Inc. Family 15h (Models 30h-3fh) Processor 
Root Complex [1043:85cb]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag+ RBE+ FLReset-
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 256 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis- 
NROPrPrP- LTR-
 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt+ 
EETLPPrefix+, MaxEETLPPrefixes 1
 EmergencyPowerReduction Not Supported, 
EmergencyPowerReductionInit-
 FRS-
 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- 
OBFF Disabled,
 AtomicOpsCtl: ReqEn-
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: fee02004  Data: 0026
Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 
Len=010 
Capabilities: [270 v1] Secondary PCI Express
LnkCtl3: LnkEquIntrruptEn- PerformEqu-
LaneErrStat: 0
Capabilities: [2b0 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [2c0 v1] Page Request Interface (PRI)
PRICtl: Enable- Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 0020, Page Request Allocation: 

Capabilities: [2d0 v1] Process Address Space ID (PASID)
PASIDCap: Exec- Priv-, Max PASID Width: 10
PASIDCtl: Enable- Exec- Priv-
Kernel driver in use: radeon
Kernel modules: radeon, amdgpu

00:01.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri 
HDMI/DP Audio Controller [1002:1308]
Subsystem: ASUSTeK Computer Inc. Kaveri HDMI/DP Audio Controller 
[1043:85cb]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag+ RBE+ FLReset-
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 256 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis- 
NROPrPrP- LTR-
 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt+ 
EETLPPrefix+, MaxEETLPPrefixes 1
 EmergencyPowerReduction Not Supported, 
EmergencyPowerReductionInit-
 FRS-
 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- 
OBFF Disabled,
 AtomicOpsCtl: ReqEn-
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: fee08004  Data: 0025
Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 
Len=010 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 30h-3fh) Processor Root Port [1022:1424]
DeviceName:  Onboard IGD
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- 

[Kernel-packages] [Bug 1995853] [NEW] armhf kernels are compiled with gcc-11

2022-11-07 Thread Juerg Haefliger
Public bug reported:

[Impact]

We currently compile the Kinetic raspi armhf kernels with gcc-11 because
a gcc-12-compiled armhf raspi kernel won't boot or hang. We need to
figure out what's going on and fix it to be able to go back to the
default compiler.

[Test Case]

Boot armhf kernel and exercise the system. It either won't come up at
all or hang/freeze later on.

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

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

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

** No longer affects: gcc-12 (Ubuntu)

** Summary changed:

- The armhf kernel is compiled with gcc-11
+ armhf kernels are compiled with gcc-11

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

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

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

** Description changed:

- We currently compile the raspi armhf kernels with gcc-11 because a
- gcc-12 compiled armhf raspi kernel won't boot or hang. We need to figure
- out what's going on and fix it to be able to go back to the default
- compiler.
+ We currently compile the Kinetic raspi armhf kernels with gcc-11 because
+ a gcc-12-compiled armhf raspi kernel won't boot or hang. We need to
+ figure out what's going on and fix it to be able to go back to the
+ default compiler.

** Description changed:

+ [Impact]
+ 
  We currently compile the Kinetic raspi armhf kernels with gcc-11 because
  a gcc-12-compiled armhf raspi kernel won't boot or hang. We need to
  figure out what's going on and fix it to be able to go back to the
  default compiler.
+ 
+ [Test Case]
+ 
+ Boot armhf kernel and exercise the system. It either won't come up at
+ all or hang/freeze later on.

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

Title:
  armhf kernels are compiled with gcc-11

Status in linux-raspi package in Ubuntu:
  Invalid
Status in linux-raspi source package in Kinetic:
  Confirmed

Bug description:
  [Impact]

  We currently compile the Kinetic raspi armhf kernels with gcc-11
  because a gcc-12-compiled armhf raspi kernel won't boot or hang. We
  need to figure out what's going on and fix it to be able to go back to
  the default compiler.

  [Test Case]

  Boot armhf kernel and exercise the system. It either won't come up at
  all or hang/freeze later on.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1995853/+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 1981089] Re: Please have linux-tools-common Provide: bpftool

2022-11-07 Thread Andrea Righi
** Also affects: linux (Ubuntu Lunar)
   Importance: Medium
   Status: Triaged

** Also affects: lava (Ubuntu Lunar)
   Importance: Undecided
   Status: Triaged

** Also affects: bpfcc (Ubuntu Lunar)
   Importance: Undecided
   Status: Triaged

** Also affects: bpftrace (Ubuntu Lunar)
   Importance: Undecided
   Status: New

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

** Also affects: lava (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: bpfcc (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: bpftrace (Ubuntu Kinetic)
   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/1981089

Title:
  Please have linux-tools-common Provide: bpftool

Status in bpfcc package in Ubuntu:
  Triaged
Status in bpftrace package in Ubuntu:
  New
Status in lava package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in bpfcc source package in Kinetic:
  New
Status in bpftrace source package in Kinetic:
  New
Status in lava source package in Kinetic:
  New
Status in linux source package in Kinetic:
  New
Status in bpfcc source package in Lunar:
  Triaged
Status in bpftrace source package in Lunar:
  New
Status in lava source package in Lunar:
  Triaged
Status in linux source package in Lunar:
  Triaged

Bug description:
  In Debian, 'bpftool' is provided as a separate binary package.  There
  are other packages in the archive (bpfcc, lava-dispatcher-host) which
  reference this package.  Rather than patching each package in Ubuntu
  to know the different Ubuntu name for the package (linux-tools-
  common), we should make linux-tools-common Provides: bpftool.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bpfcc/+bug/1981089/+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 1988470] Re: System runs into emergency mode if SSD is missing

2022-11-07 Thread Juerg Haefliger
Systemd is waiting for the (unattached) drive to come online and
eventually times out. That's not a kernel problem. Is this Ubuntu server
(classic) or core?

** Changed in: linux-raspi (Ubuntu)
   Status: Expired => New

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

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

Title:
  System runs into emergency mode if SSD is missing

Status in linux-raspi package in Ubuntu:
  Incomplete

Bug description:
  I have M.2 SSD, attached to USB3 port. Everything worked fine in 20.04LTS. I 
could detach the drive, then boot the system, and it ran correctly in UI mode 
with desktop, etc.
  I have another behavior after upgrade to 22.04LTS with 5.15.0.1013 core. Now 
the system boots into emergency mode with command prompt, if SSD is detached. 
SSD linking is defined in the /etc/fstab.
  System works fine if SSD is attached to USB3 port before power is on. Also I 
can attach SDD when the system is in the command prompt mode (see above) then 
reboot from the command line, then system will boot the GUI.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1988470/+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 1945749] Re: [nvidia] System freeze using nvidia-470 but nvidia-460 is fine

2022-11-07 Thread Vincenzo Simeone
Is this issue still present?
Did you resolve it anyhow?

The same symptoms: random freezes, sometimes I can only move the mouse and 
nothing else, and other times everything freezes.
In either case, nothing responds, neither the ssh nor CTRL+ALT+F2, I've to hard 
reset with the power button.

My current specs: (I initially had the bug with Ubuntu 21.04, then tried
Arch Linux (with LTS kernel/driver and non), now I'm with Debian but
didn't solve)

OS: Debian GNU/Linux 11 (bullseye) x86_64
Host: MS-7C02 1.0
Kernel: 5.10.0-18-amd64
CPU: AMD Ryzen 5 3600 (12) @ 3.600GHz
GPU: NVIDIA GeForce GTX 1660 SUPER with driver ver. 470.141.03
Memory: 15991MiB - CMK16GX4M2B3200C16

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

Title:
  [nvidia] System freeze using nvidia-470 but nvidia-460 is fine

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

Bug description:
  System randomly freezes, no clue how to reproduce it. Multiple people
  have the same issue. Dell Precision 5550 running Ubuntu 20.04.3 LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.63.01  Tue Aug  3 
20:44:16 UTC 2021
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  1 10:41:30 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 470.63.01, 5.11.0-36-generic, x86_64: installed
   nvidia, 470.63.01, 5.11.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA 
controller])
     Subsystem: Dell Device [1028:097e]
     Subsystem: Dell TU117GLM [Quadro T1000 Mobile] [1028:097e]
  InstallationDate: Installed on 2021-08-27 (34 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Precision 5550
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=42e96b11-9efb-45e0-ace2-85fe35b2047b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2021
  dmi.bios.release: 1.9
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.1
  dmi.board.name: 0V6K79
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnPrecision5550:pvr:sku097E:rvnDellInc.:rn0V6K79:rvrA03:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5550
  dmi.product.sku: 097E
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1945749/+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 1976147] Re: [Kernel 5.15] System messages (kernel and systemd) are not shown during boot until it reach a late stage

2022-11-07 Thread Juerg Haefliger
We seem to have lost the relevant config changes in Kinetic. Sigh.


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

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

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

Title:
  [Kernel 5.15] System messages (kernel and systemd) are not shown
  during boot until it reach a late stage

Status in linux-raspi package in Ubuntu:
  Triaged
Status in linux-raspi source package in Jammy:
  Fix Released
Status in linux-raspi source package in Kinetic:
  Confirmed

Bug description:
  # lsb_release -rd
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  # uname -a
  Linux fpgrpi 5.15.0-1008-raspi #8-Ubuntu SMP PREEMPT Thu May 19 11:58:51 UTC 
2022 aarch64 aarch64 aarch64 GNU/Linux

  Problem summary:
  
  System is a Raspberry Pi 4 Model B Rev 1.4.

  When you remove the 'quiet' and 'splash' options in file
  /boot/firmware/cmdline.txt in order to see "live" the kernel and
  systemd messages generated during boot these messages are not shown
  from the start of the boot process. It remains a blank screen until
  boot process reached a late stage (maybe the gpu driver init but I'm
  not sure).

  It works with previous kernels 5.13 from Impish (it show all messages
  from the boot start) but is broken in kernels 5.15 from jammy.

  What was expected:
  --
  As in kernel 5.13 the boot will show 4 raspberries in the top of the screen 
and the kernel and systemd messages generated will be shown from the start of 
the boot process.

  How to reproduce:
  -
  Remove the 'quiet' and 'splash' options in file /boot/firmware/cmdline.txt in 
order to see "live" the kernel and systemd messages generated during boot. With 
kernel 5.13 these messages are shown from the boot process start but with 
kernel 5.15 the screen remains blank until a late boot stage.

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