date:20230705

Hello koba, or anyone else affected,

Accepted thermald into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/thermald/2.4.9-1ubuntu0.3 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Changed in: thermald (Ubuntu Jammy)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-jammy

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

Title:
  Add support for Alder Lake N

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Jammy:
  Fix Committed
Status in thermald source package in Kinetic:
  New

Bug description:
  [Impact]

   * Support thermald on Alder Lake N CPU.

  [Test Plan]

   * Use a machine with a Alder Lake N cpu.

   * systemctl status thermald

   * Status of thermald should be `running`

  [Where problems could occur]

   * This change is to add support for Alder Lake N in thermald, which
  won't impact other hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2012260/+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 2018236] Re: Fix ADL: System shutdwon automically when run Prime95 with i9-12900K

Hello koba, or anyone else affected,

Accepted thermald into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/thermald/2.4.9-1ubuntu0.3 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Changed in: thermald (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-jammy

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

Title:
  Fix ADL: System shutdwon automically when run Prime95 with
  i9-12900K

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Jammy:
  Fix Committed

Bug description:
  [Description]
  System shutdown automatically when stressing the machine.

  [Fix]
  Need these two to fix the issue.

  cbdd92b) Parse idsp and trips
  d385f20) Use PL1 max/min from PPCC when policies match
  
https://github.com/intel/thermal_daemon/commit/d385f20764e1e5477450405be71ec719adc973be

  [Test Case]
  1. Find a unit with i9-12900k CPU and air cooling
  2. Install tools
  #sudo apt install stress-ng s-tui
  #sudo systemctl stop thermald
  #sudo thermald --no-daemon --loglevel=debug --adaptive --ignore-cpuid-check > 
thermald_log.txt &
  #download prime95 linux version: p95v308b15.linux64.tar.gz and decompress
  4. Stress test: (you may need to open multiple terminals for the test)
  #./mprime
  #sudo stress-ng -a 0 --class cpu,cpu-cache --ignite-cpu -v
  5. monitor cpu temperature for 6 hours if you didn’t hit overheat and 
shutdown issue.
  #sudo s-tui -c

  [Where problems could occur]
  low

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2018236/+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 2018275] Re: Fix the in-motion function does not work

Hello koba, or anyone else affected,

Accepted thermald into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/thermald/2.4.9-1ubuntu0.3 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Changed in: thermald (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-jammy

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

Title:
  Fix the in-motion function does not work

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Jammy:
  Fix Committed

Bug description:
  [Summary]
  in-Motion condition doesn't work with adaptive performance policy

  [Fix]
  This patch fix the issue,
  cc0890a59725) Always match motion = 0

  [Test cases]
  1. Install the Ubuntu 22.04-oem image on BMM4-DVT2-C2X
  2. run the thermald applied the fix.
  #thermald --no-daemon --loglevel=debug --adaptive --ignore-cpuid-check > 
thermald_log.log" and check the log
  3. in-motion condition works

  [Where problems could occur]
  because motion is always 0, the rules with motion=1 wouldn't be hit.
  but motion=1 isn't supported.

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

Hello Colette, or anyone else affected,

Accepted thermald into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/thermald/2.4.9-1ubuntu0.3 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

Title:
  thermald prematurely throttling GPU

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
   * thermald prematurely throttling GPU

  [Fix]
  This fix is removed the code refactoring part and keep the necessary.

  (patch: 0009-Install-passive-default.patch)
  82609c7) Separate Adaptive engine and GDDV

  [Test Plan]
  Test1,
   * Run game on the target machine.
   * the FPS must not be significantly reduced.
  Test2,
   * Run on others platform, ADL/TGL/CML/CFL/KBL.
   * Use monitoring tool(e.g. s-tui) and stress-ng to verify if the machine 
runs normally.

  [Where problems could occur]
   * better support for Passive Policy. currently passive policy 1 is supported 
and it should have a bug if the machine only enable pssive policy 2.

  ~~~
  I got a new game and started playing it
  It would run at over 100 FPS solidly some of the time and then cyclically dip 
down to below 20 FPS for a few minutes

  I determined that it was thermald trying to keep my GPU below 70°C
  to determine this I sudo systemctl stop thermald
  The game ran solidly and consistently with the GPU at 75°C

  This is well below the specs set by the manufacturer and perhaps
  unreasonably low for a laptop

  But more importantly I was given no indication this was happening. I
  had to sleuth it out myself.

  Perhaps it is impossible to determine good defaults for all hardware,
  I don't know. However without an indication that this is happening
  there will be a lot of people with a mysteriously broken experience.
  This was extremely difficult for me to find and I had several friend
  who are experts on linux gaming and video drivers trying to track this
  down. I discovered it by luck and perseverance.

  This absolutely needs some sort of indication and hopefully a way to
  remedy it from the GUI. ideally it would set thermal limits that are
  more in line with what the device is designed for and not a
  conservative default if at all possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: thermald 2.4.9-1
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Fri Jul  8 16:08:55 2022
  InstallationDate: Installed on 2020-10-19 (626 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: thermald
  UpgradeStatus: Upgraded to jammy on 2022-06-17 (20 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1981087/+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 1981087] Re: thermald prematurely throttling GPU

This is fixed in v2.5, so Kinetic and above.

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

** Changed in: thermald (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-jammy

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

Title:
  thermald prematurely throttling GPU

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
   * thermald prematurely throttling GPU

  [Fix]
  This fix is removed the code refactoring part and keep the necessary.

  (patch: 0009-Install-passive-default.patch)
  82609c7) Separate Adaptive engine and GDDV

  [Test Plan]
  Test1,
   * Run game on the target machine.
   * the FPS must not be significantly reduced.
  Test2,
   * Run on others platform, ADL/TGL/CML/CFL/KBL.
   * Use monitoring tool(e.g. s-tui) and stress-ng to verify if the machine 
runs normally.

  [Where problems could occur]
   * better support for Passive Policy. currently passive policy 1 is supported 
and it should have a bug if the machine only enable pssive policy 2.

  ~~~
  I got a new game and started playing it
  It would run at over 100 FPS solidly some of the time and then cyclically dip 
down to below 20 FPS for a few minutes

  I determined that it was thermald trying to keep my GPU below 70°C
  to determine this I sudo systemctl stop thermald
  The game ran solidly and consistently with the GPU at 75°C

  This is well below the specs set by the manufacturer and perhaps
  unreasonably low for a laptop

  But more importantly I was given no indication this was happening. I
  had to sleuth it out myself.

  Perhaps it is impossible to determine good defaults for all hardware,
  I don't know. However without an indication that this is happening
  there will be a lot of people with a mysteriously broken experience.
  This was extremely difficult for me to find and I had several friend
  who are experts on linux gaming and video drivers trying to track this
  down. I discovered it by luck and perseverance.

  This absolutely needs some sort of indication and hopefully a way to
  remedy it from the GUI. ideally it would set thermal limits that are
  more in line with what the device is designed for and not a
  conservative default if at all possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: thermald 2.4.9-1
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Fri Jul  8 16:08:55 2022
  InstallationDate: Installed on 2020-10-19 (626 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: thermald
  UpgradeStatus: Upgraded to jammy on 2022-06-17 (20 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1981087/+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 1989044] Re: RPL: Add INT3400 base path

Hello koba, or anyone else affected,

Accepted thermald into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/thermald/2.4.9-1ubuntu0.3 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Changed in: thermald (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-jammy

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

Title:
  RPL: Add INT3400 base path

Status in thermald package in Ubuntu:
  New
Status in thermald source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
   * Add INT3400 base path for Raptor Lake CPU.

  [Test Plan]
   * Use a machine with a Raptor Lake cpu.
   * check the thermald log.
   * Get the base path of INT3400.

  [Where problems could occur]
   * This change is to add path in INT3400 for Raptor Lake, which won't impact 
other hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1989044/+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 1995606] Re: Upgrade thermald to 2.5.1 for Jammy (22.04)

Hello koba, or anyone else affected,

Accepted thermald into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/thermald/2.4.9-1ubuntu0.3 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Changed in: thermald (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-jammy

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

Title:
  Upgrade thermald to 2.5.1 for Jammy (22.04)

Status in OEM Priority Project:
  New
Status in thermald package in Ubuntu:
  New
Status in thermald source package in Jammy:
  Fix Committed

Bug description:
  [Justification]
  The purpose of this bug is that prevent the regression in the future.
  The automatic test scripts are better for the future SRU and is still on the 
planning.

  [Test case]
  For these CPU series, RPL/ADL/TGL/CML/CFL/KBL, the following tests will be 
run on machines in the CI lab:

  1. Run stress-ng, and observe the temperature/frequency/power with s-tui
    - Temperatures should stay just below trip values
    - Power/performance profiles should stay roughly the same between old 
thermald and new thermald (unless specifically expected eg: to fix 
premature/insufficient throttling)
  2. check if thermald could read rules from /dev/acpi_thermal_rel and generate 
the xml file on /etc/thermald/ correctly.
    - this depends on if acpi_thermal_rel exist.
    - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto"
   could be landed in etc/thermald/.
    - if not, the user-defined xml could be created, then jump to (3).
    - run thermald with --loglevel=debug, and compare the log with xml.auto 
file. check if the configuration could be parsed correctly.
  3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded 
correctly.
    - run thermald with --loglevel=debug, and compare the log with xml files.
    - if parsed correctly, the configurations from XML files would appear in 
the log.

  4. Run unit tests, the scripts are under test folder, using emul_temp to 
simulate the High temperatue and check thermald would throttle CPU through the 
related cooling device.
    - rapl.sh
    - intel_pstate.sh
    - powerclamp.sh
    - processor.sh
  5. check if the power/frequency would be throttled once the temperature reach 
the trip-points of thermal zone.
  6. check if system would be throttled even the temperature is under the 
trip-points.

  [ Where problems could occur ]
  since the PL1 min/max is introduced, there may have some cases that don't 
check the minimum of PL1 then make PL1 to smaller and smaller and throttle the 
CPU. 
  this may cause machines run like the old behavior that doesn't have PL1 
min/max.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1995606/+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 2007579] Re: Raptor Lake Thermald ITMT version 2 support

Hello Srinivas, or anyone else affected,

Accepted thermald into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/thermald/2.4.9-1ubuntu0.3 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Changed in: thermald (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

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

Title:
  Raptor Lake Thermald ITMT version 2 support

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Bionic:
  Won't Fix
Status in thermald source package in Focal:
  Won't Fix
Status in thermald source package in Jammy:
  Fix Committed
Status in thermald source package in Kinetic:
  Fix Released
Status in thermald source package in Lunar:
  Fix Released

Bug description:
  == SRU Justification Kinetic ==

  Raptor Lake system uses ITMT v2 instead of V1 for thermal
  configuration via GDDV.

  This was observed on Dell XPS 9320 system.
  Because thermald can't parse V2 table, it is not getting correct thermal 
threshold temperature and power limits.

  == The Fix ==

  This is fixed in upstream thermald by the patch:
  
https://github.com/intel/thermal_daemon/commit/90d56bc06cdcf78e7398ea7da389401516591774
  This fix is part of Thermald 2.5.2 release.

  The fix applies cleanly and this is already in Ubuntu Lunar in
  thermald 2.5.2.  The fix checks for illegal ITMT version and handles
  version 2 as a specific exceptional case.

  == Regression Risks ==

  For systems that do not used ITMT, no change in behaviour will occur.
  Systems with versions > 2 (currently not valid) will not have ITMT
  parsed anymore; this will avoid misinterpreting unsupported ITMT data.
  Finally, version 2 of ITMT will be now parsed differently and
  additional fields will be parsed and these will be ignored as
  intended.

  == Test Plan ==

  Test against a Dell XPS 9320 system. See if it handles the ITMT correctly. 
The thermald log should indicate version 2 is being used with the message: 
  "ignore dummy_str: ds d1 d2 d3 " where ds = a string, d1 .. d3 are uint64 
values that are parsed and ignored.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2007579/+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 2012260] Re: Add support for Alder Lake N

This is fixed in 2.5.2, so lunar and later. Do you intend to fix this
for Kinetic, as well?

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

Title:
  Add support for Alder Lake N

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Jammy:
  Fix Committed
Status in thermald source package in Kinetic:
  New

Bug description:
  [Impact]

   * Support thermald on Alder Lake N CPU.

  [Test Plan]

   * Use a machine with a Alder Lake N cpu.

   * systemctl status thermald

   * Status of thermald should be `running`

  [Where problems could occur]

   * This change is to add support for Alder Lake N in thermald, which
  won't impact other hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2012260/+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 2018236] Re: Fix ADL: System shutdwon automically when run Prime95 with i9-12900K

These patches are in 2.5, so fixed in Kinetic and above.

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

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

Title:
  Fix ADL: System shutdwon automically when run Prime95 with
  i9-12900K

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Jammy:
  In Progress

Bug description:
  [Description]
  System shutdown automatically when stressing the machine.

  [Fix]
  Need these two to fix the issue.

  cbdd92b) Parse idsp and trips
  d385f20) Use PL1 max/min from PPCC when policies match
  
https://github.com/intel/thermal_daemon/commit/d385f20764e1e5477450405be71ec719adc973be

  [Test Case]
  1. Find a unit with i9-12900k CPU and air cooling
  2. Install tools
  #sudo apt install stress-ng s-tui
  #sudo systemctl stop thermald
  #sudo thermald --no-daemon --loglevel=debug --adaptive --ignore-cpuid-check > 
thermald_log.txt &
  #download prime95 linux version: p95v308b15.linux64.tar.gz and decompress
  4. Stress test: (you may need to open multiple terminals for the test)
  #./mprime
  #sudo stress-ng -a 0 --class cpu,cpu-cache --ignite-cpu -v
  5. monitor cpu temperature for 6 hours if you didn’t hit overheat and 
shutdown issue.
  #sudo s-tui -c

  [Where problems could occur]
  low

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2018236/+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 2018275] Re: Fix the in-motion function does not work

This patch is in 2.5.1, and so is fixed in Kinetic and newer.

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

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

Title:
  Fix the in-motion function does not work

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Jammy:
  In Progress

Bug description:
  [Summary]
  in-Motion condition doesn't work with adaptive performance policy

  [Fix]
  This patch fix the issue,
  cc0890a59725) Always match motion = 0

  [Test cases]
  1. Install the Ubuntu 22.04-oem image on BMM4-DVT2-C2X
  2. run the thermald applied the fix.
  #thermald --no-daemon --loglevel=debug --adaptive --ignore-cpuid-check > 
thermald_log.log" and check the log
  3. in-motion condition works

  [Where problems could occur]
  because motion is always 0, the rules with motion=1 wouldn't be hit.
  but motion=1 isn't supported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2018275/+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 2026216] Re: ethernet not found after kernel update to linux-image-5.19.0-46-generic

2023-07-05 Thread Ubuntu Foundations Team Bug Bot

** Package changed: ubuntu => linux-signed-hwe-5.19 (Ubuntu)

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

Title:
  ethernet not found after kernel update to linux-
  image-5.19.0-46-generic

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

Bug description:
  After updating kernel to linux-image-5.19.0-46-generic (by apt upgrade), 
ubuntu doesn't discover ethernet.
  Things work as expected after choosing older kernel at grub.
  
  After (kernel) update ubuntu stopped at terminal (did not show gdm screen). 
After logging in to terminal, ifconfig didn't show ethernet (did show lo and 
docker).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-45-generic 5.19.0-45.46~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Wed Jul  5 17:47:51 2023
  InstallationDate: Installed on 2023-02-03 (152 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   TERM=alacritty
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: linux-signed-hwe-5.19
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2026216/+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 2024427] Re: potential S3 issue for amdgpu Navi 31/Navi33

2023-07-05 Thread Mario Limonciello

Under stress testing it was reported that the system will sometimes fail
to wake from S3.

This firmware version has been run heavily under Q/A on various 6.1.y
kernel and those issues don't occur after taking this runtime firmware
update.

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

Title:
  potential S3 issue for amdgpu Navi 31/Navi33

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-firmware source package in Jammy:
  New
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Triaged
Status in linux-firmware source package in Lunar:
  New
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Triaged
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  amdgppu update is needed to fix some potential Navi31/Navi33 S3 issue.

  amdgpu:
  ac2f5739fdca drm/amdgpu/mes11: enable reg active poll
  a2fe4534bb38 drm/amd/amdgpu: update mes11 api def
  da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin
  616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2
  09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4

  Navi31:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=ffe1a41e2ddbc39109b12d95dcac282d90eba8fc
  Navi33:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=a5d7b4df1a76f82e2ecb725cc1b56ce111830bac

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2024427/+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 1988023] Re: Could not switch uppercase/lowercase by using keyboard of laptop

2023-07-05 Thread Nick Rosbrook

Re-assigning since it sounds like this is not a systemd issue.

** Package changed: systemd (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/1988023

Title:
  Could not switch uppercase/lowercase by using keyboard of laptop

Status in linux package in Ubuntu:
  New

Bug description:
  1. Fresh install ubuntu server 22.04.1 on Lenovo server.
  2. Install console-data package 
  3. Get locale status: 
  # localectl status
 System Locale: LANG=en_US.UTF-8
 VC Keymap: n/a
X11 Layout: us
 X11 Model: pc105
  4. Fail to ist and set keymap with command "localectl", but the kmap file can 
be found in the /usr/share./keymaps/
  #localectl list-keymaps 
  Failed to read list of keymaps: No such file or directory 
  # localectl set-keymap us
  Failed to set keymap: Keymap us is not installed.
  # find /usr/ -name us.kmap.gz
  /usr/share/keymaps/i386/qwerty/us.kmap.gz 
  5. It need type "CapsLock" twice when want to switch uppercase/lowercase by 
using keyboard of laptop, not once, the other keyboard has no issue about it.
  # dumpkeys | grep -E "keymaps|58"
  keymaps 0-127
  keycode  58 = CtrlL_Lock 
  6. It can switch uppercase/lowercase normally after run command "loadkeys us".

  Please help check why need type twice "CapsLock" for switching 
uppercase/lowercase and how to fix it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-29 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220809)
  MachineType: Lenovo ThinkSystem SR630 V2
  Package: systemd 249.11-0ubuntu3.4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/21/2022
  dmi.bios.release: 1.30
  dmi.bios.vendor: Lenovo
  dmi.bios.version: AFE118I-1.30
  dmi.board.asset.tag: none
  dmi.board.name: 7Z70CTO1WW
  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.80
  dmi.modalias: 
dmi:bvnLenovo:bvrAFE118I-1.30:bd04/21/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR630V2:pvr05:rvnLenovo:rn7Z70CTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7Z70CTO1WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkSystem SR630 V2
  dmi.product.sku: 7Z70CTO1WW
  dmi.product.version: 05
  dmi.sys.vendor: Lenovo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988023/+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 2024774] Re: AMD Rembrandt / Phoenix PSR-SU related freezes

2023-07-05 Thread Mario Limonciello

> Not entirely sure if this is the exact logging you are looking for,
but this is the result from my testing.

Thanks for having a try.

> ➜ ~ sudo python Downloads/psr.py
> DRI device 0 DMCUB F/W version: 0x043c
> ○ PSR 2 with Y coordinates (eDP 1.4a) [3]
> ○ Sink OUI: Parade
> ○ resv_40f: 01
> ○ ID String: 08-03
> ○ PSR Status: 00-00-02

You do have an affected panel, and if the system isn't freezing this
shows that the updated firmware worked.  The version you tested (
0x043c )  is a little newer than I suggested ( 0x43a ) but
that's fine.  The fix carries forward.

> BOOT_IMAGE=/boot/vmlinuz-6.4.0-060400-generic
root=UUID=41d8f993-282a-48a5-b355-6f537a3a17ab ro quiet splash
amdgpu.dcdebugmask=0x0 vt.handoff=7

Good; you don't have PSR manually disabled.

> Jul 3 19:45:50 rct14s kernel: [ 1001.214638] WARNING: CPU: 3 PID: 237
at drivers/gpu/drm/amd/amdgpu/../display/dc/dce/dmub_psr.c:126
dmub_psr_get_state+0xcc/0xe0 [amdgpu]

This warning we're tracking at
https://gitlab.freedesktop.org/drm/amd/-/issues/2645


** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2645
   https://gitlab.freedesktop.org/drm/amd/-/issues/2645

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

Title:
  AMD Rembrandt / Phoenix PSR-SU related freezes

Status in Linux Firmware:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Confirmed
Status in linux-firmware source package in Lunar:
  Confirmed
Status in linux-firmware source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

   When using kernel 6.2 or later AMD has enabled PSR selective update (PSR-SU).
   After a non-deterministic amount of time the system may hang with a message 
like this in the logs:
   "[amdgpu :67:00.0: [drm] *ERROR* [CONNECTOR:78:eDP-1] commit wait timed 
out]"

   Affects users of laptops that contain:
   * AMD Rembrandt (Yellow Carp) or AMD Phoenix (Pink Sardine) chips
   * eDP panels with Parade TCONs (8-03 and 8-01 both reported to fail)

  [ Test Plan ]

   * Test an affected laptop with the newer firmware and ensure that PSR-SU 
function can be enabled and system is stable.
   * Ensure other functions such as hotplugging monitors and suspending 
continue to work.

  [ Where problems could occur ]

   * Affected firmware only is loaded on Rembrandt and Phoenix laptops.
  Problems would be localized to these machines.

  [ Other Info ]
  The minimum firmware needed to help these hangs:
  * Rembrandt: 0x43a or later
  * Phoenix: 0x8001000 or later

  The following commit upgrades the firmware for Rembrandt 
(amdgpu/yellow_carp_dmcub.bin) to 0x43c:
  9dbd8ec2 ("amdgpu: DMCUB updates for various AMDGPU asics")

  The following commit upgrades the firmware for Phoenix 
(amdgpu/dcn_3_1_4_dmcub.bin) to 0x8001a00:
  045b2136 ("amdgpu: update DMCUB to v0.0.172.0 for various AMDGPU ASICs")

  The TCON in a given laptop can be identified from the DPCD with this script:
  https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/psr.py

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux-firmware/+bug/2024774/+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 2023594] Re: Case [Azure] Fix VM crash/hang issues due to fast VF add/remove events

2023-07-05 Thread Tim Gardner

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

** Changed in: linux-azure (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Changed in: linux-azure (Ubuntu Lunar)
   Status: In Progress => Fix Committed

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

Title:
   Case [Azure] Fix VM crash/hang issues due to fast VF add/remove
  events

Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Focal:
  Fix Committed
Status in linux-azure source package in Jammy:
  Fix Committed
Status in linux-azure source package in Lunar:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  A Linux guest on Hyper-V/Azure can occasionally crash during early Linux 
kernel boot due to a strange host behavior:
  1. The host assigns a VF to the guest;
  2. The host immediately unassigns the VF from the guest; //Dexuan: due to 
some race conditions bug in Linux vPCI driver, Linux can crash.
  3. The host assigns the VF to the guest again.

  Starting late 2022 (around Nov 2022), Linux guests on Azure started to
  crash more frequently due to a host side update at that time: a new
  host/hypervisor feature of handling "correctable memory errors" can
  cause a lot of successive VF remove/add events, so the race conditions
  bug in Linux vPCI driver can surface much more easily. The Hyper-V
  team is implementing a batching mechanism so that the guest will get
  much less VF remove/add events (ETA: June 2023), but meanwhile we
  should also get the Linux race condition bugs fixed so that Linux
  guests won't crash even if it receives the successive VF remove/add
  events.

  [Test Plan]

  Microsoft tested

  [Regression potential]

  PCI devices may not get registered, or VMs may crash.

  [Other Info]

  SF: #00349076

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2023594/+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 2022370] Re: mlxbf-gige: Fix kernel panic at shutdown

2023-07-05 Thread Feysel Mohammed

Using 5.15.0-1019-bluefield, After performing 1000 reboots kernel panic
not observed.


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

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

Title:
  mlxbf-gige: Fix kernel panic at shutdown

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Focal:
  Fix Committed
Status in linux-bluefield source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

  We occasionally see a race condition (once every 350 reboots) where napi is 
still
  running (mlxbf_gige_poll) while a shutdown has been initiated through 
"reboot".
  Since mlxbf_gige_poll is still running, it tries to access a NULL pointer and 
as
  a result causes a kernel panic.

  [Fix]

  The fix is to explicitly disable napi and dequeue it during shutdown.
  mlxbf_gige_remove already calls:
  unregister_netdev->unregister_netdevice->unregister_netdev_queue->
  rollback_registered->rollback_registered_many->dev_close_many->
  __dev_close_many->ndo_stop->mlxbf_gige_stop which stops napi
  
  So use mlxbf_gige_remove in place of the existing shutdown logic.

  [Test Case]

  * Issue at least 1000 reboots from linux and make sure there is no
  panic caused by the mlxbf-gige driver.

  [Regression Potential]

  * since this issue is hard to reproduce, it hasn't been tested
  thoroughly yet. so it needs several reboot loops to validate it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2022370/+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 2025266] Re: nvidia-dkms-* FTBS with linux 6.4

This bug was fixed in the package nvidia-graphics-drivers-390 -
390.157-0ubuntu7

---
nvidia-graphics-drivers-390 (390.157-0ubuntu7) mantic; urgency=medium

  * debian/dkms_nvidia.conf,
debian/templates/dkms_nvidia.conf.in,
debian/dkms_nvidia/patches/buildfix_kernel_6.4.patch:
- Support linux 6.4 ABI (LP: #2025266).

 -- Paolo Pisati   Wed, 28 Jun 2023 14:29:47
+

** Changed in: nvidia-graphics-drivers-390 (Ubuntu Mantic)
   Status: New => Fix Released

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

Title:
  nvidia-dkms-* FTBS with linux 6.4

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Mantic:
  New
Status in nvidia-graphics-drivers-510 source package in Mantic:
  Won't Fix
Status in nvidia-graphics-drivers-515 source package in Mantic:
  Won't Fix

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c: In function 
‘nv_drm_update_drm_driver_features’:
  /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c:769:18: error: 
‘struct drm_driver’ has no member named ‘dumb_destroy’
769 | nv_drm_driver.dumb_destroy = nv_drm_dumb_destroy;
|  ^
  make[2]: *** [scripts/Makefile.build:260: 
/var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.o] Error 1

  [Fix]

  Apply the attached patch.

  [How to test]

  Build the dkms package and install it.

  [Regression potential]

  This patch doesn't come from NVIDIA itself, so there's a regression
  potential, though i can't state how severe that could be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2025266/+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 2026196] Re: package linux-headers-6.2.0-23-generic 6.2.0-23.23 failed to install/upgrade: installed linux-headers-6.2.0-23-generic package post-installation script subprocess r

2023-07-05 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package linux-headers-6.2.0-23-generic 6.2.0-23.23 failed to
  install/upgrade: installed linux-headers-6.2.0-23-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  Has a restart error after update

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-23-generic 6.2.0-23.23
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rama   1510 F wireplumber
   /dev/snd/controlC2:  rama   1510 F wireplumber
   /dev/snd/controlC0:  rama   1510 F wireplumber
   /dev/snd/seq:rama   1507 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Thu Jun 22 21:40:11 2023
  ErrorMessage: installed linux-headers-6.2.0-23-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2023-05-07 (58 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H WIFI
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=644d521c-89d4-4057-ac87-ecbdd199ff7e ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-headers-6.2.0-23-generic 6.2.0-23.23 failed to 
install/upgrade: installed linux-headers-6.2.0-23-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F60e
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF60e:bd12/09/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3HWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3HWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H WIFI
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026196/+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 2026196] [NEW] package linux-headers-6.2.0-23-generic 6.2.0-23.23 failed to install/upgrade: installed linux-headers-6.2.0-23-generic package post-installation script subprocess

2023-07-05 Thread Ramakrishnan

Public bug reported:

Has a restart error after update

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-headers-6.2.0-23-generic 6.2.0-23.23
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  rama   1510 F wireplumber
 /dev/snd/controlC2:  rama   1510 F wireplumber
 /dev/snd/controlC0:  rama   1510 F wireplumber
 /dev/snd/seq:rama   1507 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Thu Jun 22 21:40:11 2023
ErrorMessage: installed linux-headers-6.2.0-23-generic package 
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2023-05-07 (58 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: Gigabyte Technology Co., Ltd. B450M DS3H WIFI
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=644d521c-89d4-4057-ac87-ecbdd199ff7e ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: N/A
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-headers-6.2.0-23-generic 6.2.0-23.23 failed to 
install/upgrade: installed linux-headers-6.2.0-23-generic package 
post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/09/2020
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F60e
dmi.board.asset.tag: Default string
dmi.board.name: B450M DS3H WIFI-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF60e:bd12/09/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3HWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3HWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: B450M DS3H WIFI
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-package 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/2026196

Title:
  package linux-headers-6.2.0-23-generic 6.2.0-23.23 failed to
  install/upgrade: installed linux-headers-6.2.0-23-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  Has a restart error after update

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-23-generic 6.2.0-23.23
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rama   1510 F wireplumber
   /dev/snd/controlC2:  rama   1510 F wireplumber
   /dev/snd/controlC0:  rama   1510 F wireplumber
   /dev/snd/seq:rama   1507 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Thu Jun 22 21:40:11 2023
  ErrorMessage: installed linux-headers-6.2.0-23-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2023-05-07 (58 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H WIFI
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=644d521c-89d4-4057-ac87-ecbdd199ff7e ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-headers-6.2.0-23-generic 6.2.0-23.23 failed to 
install/upgrade: installed linux-headers-6.2.0-23-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F60e
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias:

[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM

2023-07-05 Thread Samer Attrah

@David @Giuliano

Hello,

Thank you so much, I just stopped the secure boot and run Giuliano's
script and it worked perfectly.

thanks, David
thanks, Giuliano

Kind regards
Samer Attrah

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

Title:
  UVC  Quanta 0408:4035  camera PROBLEM

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing',
  USB 0408:4035.

  The camera is reported to have problems by many users:  
  https://linux-hardware.org/?id=usb:0408-4035
  The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera 
is “recongized” but fails installation.

  My console commands report similar info to other users: 
  
https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58

  
  PROPOSED SOLUTION 
  I got in contact with laurent.pinch...@ideasonboard.com   and with 
riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And  
me...@vger.kernel.org mailinglist.

  Laurent proposed me a fix and I modified the 5,15 uvc_driver.c
  version, and loaded it on github

  https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User-
  Facing-0x0408-0x4035-/blob/main/uvc_driver.c

  I offered to test the fix, so I tried to compile the module with the
  new source.

  COMPILING PROBLEMS
  I’m running **Ubuntu 22.04.1 LTS, with kernel 
  giuliano@Astra2A:/usr/src$ cat /proc/version_signature
  Ubuntu 5.15.0-56.62-generic 5.15.64

  BUT  the linux-source that I found installed seems to be different
  tgiuliano@Astra2A:/usr/src$ ls -al linux-so*
  lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> 
linux-source-5.15.0/linux-source-5.15.0.tar.bz2

  I expanded  the tar file, configured the IDE and compiled without error  any 
errors… 
  I manually copied the uvcvideo.ko in 
  /lib/modules/5.15.0-56-
  sudo cp…...

  then tryed to intall the new uvcvideo.ko module
  sudo rmmod uvcvideo && sudo modprobe uvcvideo

  BUT… IT FAILS
  giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo
  modprobe: ERROR: could not insert 'uvcvideo': Exec format error

  and dmesg shows
  [25961.151982] usbcore: registered new interface driver uvcvideo
  [26323.125534] usbcore: deregistering interface driver uvcvideo
  [26323.189294] uvcvideo: disagrees about version of symbol module_layout


  These are the TWO modinfo from the old and new uvcvideo modules
  https://pastebin.com/tSj8Exm6
  Basically
  OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions 
  NEW module: vermagic: 5.15.64 SMP mod_unload modversions


  -kindly ASK

  HOW can FORCE the uvcdriver.c to match mi kernel version ?
  Have I got OTHER ways to make the kernel module I’m compiling, match my 
running system ?

  I would like to test the module so to confirm the patch and let it
  enter the kernel main stream...

  
  BR
  Giuliano

  PS
  btw…. to allow Eclipse to compile the kernel, I had to pass this commands
  scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_TRUSTED_KEYS

  hope that this does not affect the module layout & checking
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  giuliano   2142 F pulseaudio
   /dev/snd/pcmC1D0p:   giuliano   2142 F...m pulseaudio
   /dev/snd/controlC0:  giuliano   2142 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-03 (66 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Acer Nitro AN517-55
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic 
root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-57-generic N/A
   linux-backports-modules-5.15.0-57-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  Tags:  jammy
  Uname: Linux 5.15.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/20/2022
  dmi.bios.release: 1.6
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Ignis_ADH

[Kernel-packages] [Bug 2022940] Re: Azure: Fix perf regression: remove rx_cqes, tx_cqes counters for MANA

2023-07-05 Thread Tim Gardner

** Changed in: linux-azure (Ubuntu Lunar)
Status: In Progress => Fix Committed

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

Title:
Azure: Fix perf regression: remove rx_cqes, tx_cqes counters for MANA

Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Lunar:
Fix Committed

Bug description:
SRU Justification

[Impact]

net: mana: Fix perf regression: remove rx_cqes, tx_cqes counters

https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=1919b39fc6eabb9a6f9a51706ff6d03865f5df29

It resolves a big perf regression.

More details:
The apc->eth_stats.rx_cqes is one per NIC (vport), and it's on the
frequent and parallel code path of all queues. So, r/w into this
single shared variable by many threads on different CPUs creates a
lot caching and memory overhead, hence perf regression. And, it's
not accurate due to the high volume concurrent r/w.

For example, a workload is iperf with 128 threads, and with RPS
enabled. We saw perf regression of 25% with the previous patch
adding the counters. And this patch eliminates the regression.

Since the error path of mana_poll_rx_cq() already has warnings, so
keeping the counter and convert it to a per-queue variable is not
necessary. So, just remove this counter from this high frequency
code path.

Also, remove the tx_cqes counter for the same reason. We have
warnings & other counters for errors on that path, and don't need
to count every normal cqe processing.

[Test Plan]

MSFT tested

[Regression potential]

Counters are disappearing that may be in use by user space programs.

[Other Info]

SF: #00361807

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2022940/+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 2019481] Re: System boots to a black screen when nvidia-390 is installed

23.04 had some recent updates with kernel and nvidia driver/libraries,
which fixed the nvidia 390 issue for me.

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

Title:
  System boots to a black screen when nvidia-390 is installed

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

Bug description:
  Upon installing the 3rd party nVidia version 390 drivers for the Dell
  E6520 laptop, after reboot hangs with a black screen and a blinking
  cursor in the upper left hand corner.  Booting to a terminal prompt
  and using "sudo apt remove *nvidia*" and rebooting solves the issue.
  This did NOT happen in 22.04 LTS on this laptop with no other hardware
  or BIOS changes.  This install of 23.04 was a clean install, the 22.04
  install was wiped.

  vendor   : NVIDIA Corporation
  model: GF119M [NVS 4200M]
  driver   : nvidia-driver-390 - distro non-free recommended
  driver   : xserver-xorg-video-nouveau - distro free builtin

  If I install that driver the system will not boot, removing it solves
  the issue.  I've wiped and reinstalled 23.04 4x, both with full
  options and minimal, the problem always returns.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 13 10:46:41 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0494]
   NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA 
controller])
 Subsystem: Dell GF119M [NVS 4200M] [1028:1494]
  InstallationDate: Installed on 2023-05-13 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: Dell Inc. Latitude E6520
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=f7260292-99f4-4e45-a79a-97643cc0cb92 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2018
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A21
  dmi.board.name: 0692FT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA21:bd03/06/2018:br4.6:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0692FT:rvrA00:cvnDellInc.:ct9:cvr:sku:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019481/+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 2017212] Re: ASUS N56VM fails to load GUI fresh install of Ubuntu 23.04

checkout my update on:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2016459?comments=all

all seems fixed with latest ubuntu kernel/nvidia 390 updates.

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

Title:
  ASUS N56VM fails to load GUI fresh install of Ubuntu 23.04

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

Bug description:
  NVRM: failed to copy vbios to system memory.
  NVRM: RmInitAdapter failed!

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.157  Wed Oct 12 09:19:07 
UTC 2022
   GCC version:
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Fri Apr 21 07:45:45 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:1477]
   NVIDIA Corporation GF108M [GeForce GT 620M/630M/635M/640M LE] [10de:0de9] 
(rev a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108M [GeForce GT 620M/630M/635M/640M 
LE] [1043:1477]
  InstallationDate: Installed on 2023-04-20 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: ASUSTeK COMPUTER INC. N56VM
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=linux
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=0d37dcc1-3316-40c4-b4d9-7c5f62470833 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N56VM.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N56VM
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN56VM.214:bd08/28/2012:br4.6:svnASUSTeKCOMPUTERINC.:pnN56VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
  dmi.product.family: N
  dmi.product.name: N56VM
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2017212/+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 2017687] Re: GTX 675MX fails with blank screen

Looks like it is fixed after latest kernel/nvidia/library updates.
you might want to check it out.

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

Title:
  GTX 675MX fails with blank screen

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

Bug description:
  Installing with additional drivers or adding nvidia-driver-390 renders
  the system unusable.

  On restart there are few lines of the usual kernal information then a
  brief orange flash follwed by black.  System is unusable.

  Is the GTX 675MX supported by this driver?  If not, the option to use
  this driver should be removed.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: nvidia-driver-390 (not installed)
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 25 17:51:25 2023
  InstallationDate: Installed on 2023-04-23 (2 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2017687/+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 2016459] Re: NVRM: RmInitAdapter failed! , failed to copy vbios to system memory

Hi, 
Last 23.04 updates seems to fix it!

(initially i meant 23.04 of course instead 23.10.)

Just want to let you know, as i noticed new nvidia 390 package updates
(from ubuntu), i'd gave it a try.

Updated all packages, deactivated the mainline-kernel installed manual
running: 6.2.0-24-generic, 390.157-0ubuntu5.23.04.1 nvidia 
and disabled the manual applied library order hack in 
/etc/ld.so.conf.d/nvidia.conf

nvidia loads, 2 external 4K screens works as before. all seems solved
with the most recent update (kernel/nvidia and more stuff)

maybe another want so check/confirm, but i think this ticket can be
closed

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

Title:
  NVRM: RmInitAdapter failed! , failed to copy vbios to system memory

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

Bug description:
  Hi, just performed a do-release_upgrade -d to try 23.10 on my lenovo T430 
laptop with Nvidia chipset (NVIDIA NVS 5200M).
  Upgrade went smooth, but noticed my external displays where not seen. a 
checkup shows nvidia-settings doesn't show full as usual, and noticed messages 
in recarding NVRM which i had never before.

  ```
  [35057.710742] NVRM: RmInitAdapter failed! (0x30:0x:663)
  [35057.710792] NVRM: rm_init_adapter failed for device bearing minor number 0
  [35060.706390] NVRM: failed to copy vbios to system memory.
  [35060.706501] NVRM: RmInitAdapter failed! (0x30:0x:663)
  [35060.706562] NVRM: rm_init_adapter failed for device bearing minor number 0
  [35063.708929] NVRM: failed to copy vbios to system memory.
  [35063.709041] NVRM: RmInitAdapter failed! (0x30:0x:663)
  [35063.709087] NVRM: rm_init_adapter failed for device bearing minor number 0

  ```

  searching for nvidia
  ```
  2023-04-16T22:15:49.402742+02:00 T430-i7 kernel: [   14.428429] nvidia: 
loading out-of-tree module taints kernel.
  2023-04-16T22:15:49.402743+02:00 T430-i7 kernel: [   14.428443] nvidia: 
module license 'NVIDIA' taints kernel.
  2023-04-16T22:15:49.402757+02:00 T430-i7 kernel: [   14.528477] 
nvidia-nvlink: Nvlink Core is being initialized, major device number 234
  2023-04-16T22:15:49.402845+02:00 T430-i7 kernel: [   14.529212] nvidia 
:01:00.0: enabling device ( -> 0003)
  2023-04-16T22:15:49.402847+02:00 T430-i7 kernel: [   14.529674] nvidia 
:01:00.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=none:owns=none
  2023-04-16T22:15:49.402857+02:00 T430-i7 kernel: [   14.589081] 
nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  
390.157  Wed Oct 12 09:15:25 UTC 2022
  2023-04-16T22:15:49.402870+02:00 T430-i7 kernel: [   14.619491] [drm] 
[nvidia-drm] [GPU ID 0x0100] Loading driver
  2023-04-16T22:15:49.402901+02:00 T430-i7 kernel: [   14.657436] 
[drm:nv_drm_load [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed 
to allocate NvKmsKapiDevice
  2023-04-16T22:15:49.402903+02:00 T430-i7 kernel: [   14.659661] 
[drm:nv_drm_probe_devices [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 
0x0100] Failed to register device
  2023-04-16T22:15:49.402988+02:00 T430-i7 kernel: [   15.433547] nvidia-uvm: 
Loaded the UVM driver in 8 mode, major device number 511
  2023-04-16T22:15:49.402993+02:00 T430-i7 kernel: [   15.536785] audit: 
type=1400 audit(1681676145.574:3): apparmor="STATUS" operation="profile_load" 
profile="unconfined" name="nvidia_modprobe" pid=2406 comm="apparmor_parser"
  2023-04-16T22:15:49.403000+02:00 T430-i7 kernel: [   15.536790] audit: 
type=1400 audit(1681676145.574:4): apparmor="STATUS" operation="profile_load" 
profile="unconfined" name="nvidia_modprobe//kmod" pid=2406 
comm="apparmor_parser"
  2023-04-16T22:15:49.403188+02:00 T430-i7 kernel: [   18.933794] nvidia-uvm: 
Unloaded the UVM driver in 8 mode
  2023-04-16T22:15:49.403194+02:00 T430-i7 kernel: [   18.987254] 
nvidia-modeset: Unloading
  2023-04-16T22:15:49.403195+02:00 T430-i7 kernel: [   19.023265] 
nvidia-nvlink: Unregistered the Nvlink Core, major device number 234
  2023-04-16T22:15:49.403218+02:00 T430-i7 kernel: [   19.328850] 
nvidia-nvlink: Nvlink Core is being initialized, major device number 234
  2023-04-16T22:15:49.654976+02:00 T430-i7 kernel: [   19.608711] nvidia 
:01:00.0: enabling device ( -> 0003)
  2023-04-16T22:15:49.654996+02:00 T430-i7 kernel: [   19.608847] nvidia 
:01:00.0: vgaarb: changed VGA decodes: 
olddecodes=none,decodes=none:owns=none
  2023-04-16T22:15:49.720716+02:00 T430-i7 systemd[1]: Starting 
nvidia-persistenced.service - NVIDIA Persistence Daemon...
  2023-04-16T22:15:49.723994+02:00 T430-i7 nvidia-persistenced: Verbose syslog 
connection opened
  2023-04-16T22:15:49.724337+02:00 T430-i7 nvidia-persistenced: Now running 
with user ID 139 and group ID 155
  2023-04-16T22:15:49.724508+02:00 T430-i7 systemd[1]: Started 
nvidia-persistenced.service - NVIDIA

[Kernel-packages] [Bug 2024675] Re: NVIDIA CVE-2023-25515, CVE-2023-25516

This bug was fixed in the package libnvidia-nscq-450 -
450.248.02-0ubuntu0.20.04.1

---
libnvidia-nscq-450 (450.248.02-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream release (LP: #2024675).

 -- Alberto Milone   Fri, 30 Jun 2023
10:08:50 +

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

Title:
  NVIDIA CVE-2023-25515, CVE-2023-25516

Status in fabric-manager-450 package in Ubuntu:
  Fix Released
Status in fabric-manager-470 package in Ubuntu:
  Fix Released
Status in fabric-manager-525 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-450 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-470 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-530 package in Ubuntu:
  Triaged
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-530 source package in Focal:
  New
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-530 source package in Jammy:
  New
Status in fabric-manager-450 source package in Kinetic:
  Fix Released
Status in fabric-manager-470 source package in Kinetic:
  Fix Released
Status in fabric-manager-525 source package in Kinetic:
  Fix Released
Status in libnvidia-nscq-450 source package in Kinetic:
  Fix Released
Status in libnvidia-nscq-470 source package in Kinetic:
  Fix Released
Status in libnvidia-nscq-525 source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-530 source package in Kinetic:
  New
Status in fabric-manager-450 source package in Lunar:
  Fix Released
Status in fabric-manager-470 source package in Lunar:
  Fix Released
Status in fabric-manager-525 source package in Lunar:
  Fix Released
Status in libnvidia-nscq-450 source package in Lunar:
  Fix Released
Status in libnvidia-nscq-470 source package in Lunar:
  Fix Released
Status in libnvidia-nscq-525 source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-530 source package in Lunar:
  New

Bug description:
  CVE-2023-25516, CVE-2023-25516

[Kernel-packages] [Bug 2024675] Re: NVIDIA CVE-2023-25515, CVE-2023-25516

This bug was fixed in the package libnvidia-nscq-450 -
450.248.02-0ubuntu0.22.04.1

---
libnvidia-nscq-450 (450.248.02-0ubuntu0.22.04.1) jammy; urgency=medium

  * New upstream release (LP: #2024675).

 -- Alberto Milone   Fri, 30 Jun 2023
10:07:49 +

** Changed in: libnvidia-nscq-450 (Ubuntu Focal)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-25515, CVE-2023-25516

Status in fabric-manager-450 package in Ubuntu:
  Fix Released
Status in fabric-manager-470 package in Ubuntu:
  Fix Released
Status in fabric-manager-525 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-450 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-470 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-530 package in Ubuntu:
  Triaged
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-530 source package in Focal:
  New
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-530 source package in Jammy:
  New
Status in fabric-manager-450 source package in Kinetic:
  Fix Released
Status in fabric-manager-470 source package in Kinetic:
  Fix Released
Status in fabric-manager-525 source package in Kinetic:
  Fix Released
Status in libnvidia-nscq-450 source package in Kinetic:
  Fix Released
Status in libnvidia-nscq-470 source package in Kinetic:
  Fix Released
Status in libnvidia-nscq-525 source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-530 source package in Kinetic:
  New
Status in fabric-manager-450 source package in Lunar:
  Fix Released
Status in fabric-manager-470 source package in Lunar:
  Fix Released
Status in fabric-manager-525 source package in Lunar:
  Fix Released
Status in libnvidia-nscq-450 source package in Lunar:
  Fix Released
Status in libnvidia-nscq-470 source package in Lunar:
  Fix Released
Status in libnvidia-nscq-525 source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-530 source package in

[Kernel-packages] [Bug 2024675] Re: NVIDIA CVE-2023-25515, CVE-2023-25516

This bug was fixed in the package libnvidia-nscq-450 -
450.248.02-0ubuntu0.22.10.1

---
libnvidia-nscq-450 (450.248.02-0ubuntu0.22.10.1) kinetic; urgency=medium

  * New upstream release (LP: #2024675).

 -- Alberto Milone   Fri, 30 Jun 2023
10:06:39 +

** Changed in: libnvidia-nscq-450 (Ubuntu Jammy)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-25515, CVE-2023-25516

Status in fabric-manager-450 package in Ubuntu:
  Fix Released
Status in fabric-manager-470 package in Ubuntu:
  Fix Released
Status in fabric-manager-525 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-450 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-470 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-530 package in Ubuntu:
  Triaged
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-530 source package in Focal:
  New
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-530 source package in Jammy:
  New
Status in fabric-manager-450 source package in Kinetic:
  Fix Released
Status in fabric-manager-470 source package in Kinetic:
  Fix Released
Status in fabric-manager-525 source package in Kinetic:
  Fix Released
Status in libnvidia-nscq-450 source package in Kinetic:
  Fix Released
Status in libnvidia-nscq-470 source package in Kinetic:
  Fix Released
Status in libnvidia-nscq-525 source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-530 source package in Kinetic:
  New
Status in fabric-manager-450 source package in Lunar:
  Fix Released
Status in fabric-manager-470 source package in Lunar:
  Fix Released
Status in fabric-manager-525 source package in Lunar:
  Fix Released
Status in libnvidia-nscq-450 source package in Lunar:
  Fix Released
Status in libnvidia-nscq-470 source package in Lunar:
  Fix Released
Status in libnvidia-nscq-525 source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-530 source package in

[Kernel-packages] [Bug 2025243] Re: Introduce the NVIDIA 535-server ERD driver series, and enable arm64 for 535, 525, 525-server in Focal

This bug was fixed in the package nvidia-graphics-drivers-525-server -
525.125.06-0ubuntu0.20.04.2

---
nvidia-graphics-drivers-525-server (525.125.06-0ubuntu0.20.04.2) focal; 
urgency=medium

  [ Alberto Milone ]
  * debian/rules:
- Drop the unused generate-nvidia-icd-json target;

  [ Dimitri John Ledkov ]
  * debian:
- Enable arm64 builds (LP: #2025243).
  * debian/templates:
- Encode amd64-only libraries and binaries.

 -- Alberto Milone   Fri, 30 Jun 2023
16:11:31 +

** Changed in: nvidia-graphics-drivers-525 (Ubuntu Focal)
   Status: New => Fix Released

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

Title:
  Introduce the NVIDIA 535-server ERD driver series, and enable arm64
  for 535, 525, 525-server in Focal

Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  New
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Jammy:
  New
Status in nvidia-graphics-drivers-525-server source package in Jammy:
  In Progress
Status in nvidia-graphics-drivers-525 source package in Kinetic:
  New
Status in nvidia-graphics-drivers-525-server source package in Kinetic:
  In Progress
Status in nvidia-graphics-drivers-525 source package in Lunar:
  New
Status in nvidia-graphics-drivers-525-server source package in Lunar:
  In Progress

Bug description:
  Introduce the NVIDIA 535-server ERD driver series, enabling the -open
  kernel module.

  Release notes:
  
https://docs.nvidia.com/datacenter/tesla/tesla-release-notes-535-54-03/index.html

  
  Changelogs for the drivers in focal:

  
  nvidia-graphics-drivers-525 (525.125.06-0ubuntu0.20.04.3) focal; 
urgency=medium

[ Dimitri John Ledkov ]
* debian:
  - Enable arm64 builds (LP: #2025243).
* debian/templates:
  - Encode amd64-only libraries and binaries.

  
  nvidia-graphics-drivers-535 (535.54.03-0ubuntu0.20.04.4) focal; urgency=medium

[ Dimitri John Ledkov ]
* templates: encode amd64-only libraries and binaries
* debian: Enable arm64 builds (LP: #2025243).

   -- Alberto Milone   Mon, 03 Jul 2023
  13:34:05 +

  
  nvidia-graphics-drivers-525-server (525.125.06-0ubuntu0.20.04.2) focal; 
urgency=medium

[ Alberto Milone ]
* debian/rules:
  - Drop the unused generate-nvidia-icd-json target;

[ Dimitri John Ledkov ]
* debian:
  - Enable arm64 builds (LP: #2025243).
* debian/templates:
  - Encode amd64-only libraries and binaries.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-525/+bug/2025243/+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 2024675] Re: NVIDIA CVE-2023-25515, CVE-2023-25516

This bug was fixed in the package libnvidia-nscq-450 -
450.248.02-0ubuntu0.23.04.1

---
libnvidia-nscq-450 (450.248.02-0ubuntu0.23.04.1) lunar; urgency=medium

  * New upstream release (LP: #2024675).

 -- Alberto Milone   Fri, 30 Jun 2023
10:05:24 +

** Changed in: libnvidia-nscq-450 (Ubuntu Lunar)
   Status: New => Fix Released

** Changed in: libnvidia-nscq-450 (Ubuntu Kinetic)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-25515, CVE-2023-25516

Status in fabric-manager-450 package in Ubuntu:
  Fix Released
Status in fabric-manager-470 package in Ubuntu:
  Fix Released
Status in fabric-manager-525 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-450 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-470 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-530 package in Ubuntu:
  Triaged
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-530 source package in Focal:
  New
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-530 source package in Jammy:
  New
Status in fabric-manager-450 source package in Kinetic:
  Fix Released
Status in fabric-manager-470 source package in Kinetic:
  Fix Released
Status in fabric-manager-525 source package in Kinetic:
  Fix Released
Status in libnvidia-nscq-450 source package in Kinetic:
  Fix Released
Status in libnvidia-nscq-470 source package in Kinetic:
  Fix Released
Status in libnvidia-nscq-525 source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-530 source package in Kinetic:
  New
Status in fabric-manager-450 source package in Lunar:
  Fix Released
Status in fabric-manager-470 source package in Lunar:
  Fix Released
Status in fabric-manager-525 source package in Lunar:
  Fix Released
Status in libnvidia-nscq-450 source package in Lunar:
  Fix Released
Status in libnvidia-nscq-470 source package in Lunar:
  Fix Released
Status in libnvidia-nscq-525 source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-525-server source

[Kernel-packages] [Bug 2025243] Re: Introduce the NVIDIA 535-server ERD driver series, and enable arm64 for 535, 525, 525-server in Focal

This bug was fixed in the package nvidia-graphics-drivers-535 -
535.54.03-0ubuntu0.20.04.4

---
nvidia-graphics-drivers-535 (535.54.03-0ubuntu0.20.04.4) focal; urgency=medium

  [ Dimitri John Ledkov ]
  * templates: encode amd64-only libraries and binaries
  * debian: Enable arm64 builds (LP: #2025243).

 -- Alberto Milone   Mon, 03 Jul 2023
13:34:05 +

** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
   Status: New => Fix Released

** Changed in: nvidia-graphics-drivers-525-server (Ubuntu Focal)
   Status: In Progress => Fix Released

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

Title:
  Introduce the NVIDIA 535-server ERD driver series, and enable arm64
  for 535, 525, 525-server in Focal

Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  New
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Jammy:
  New
Status in nvidia-graphics-drivers-525-server source package in Jammy:
  In Progress
Status in nvidia-graphics-drivers-525 source package in Kinetic:
  New
Status in nvidia-graphics-drivers-525-server source package in Kinetic:
  In Progress
Status in nvidia-graphics-drivers-525 source package in Lunar:
  New
Status in nvidia-graphics-drivers-525-server source package in Lunar:
  In Progress

Bug description:
  Introduce the NVIDIA 535-server ERD driver series, enabling the -open
  kernel module.

  Release notes:
  
https://docs.nvidia.com/datacenter/tesla/tesla-release-notes-535-54-03/index.html

  
  Changelogs for the drivers in focal:

  
  nvidia-graphics-drivers-525 (525.125.06-0ubuntu0.20.04.3) focal; 
urgency=medium

[ Dimitri John Ledkov ]
* debian:
  - Enable arm64 builds (LP: #2025243).
* debian/templates:
  - Encode amd64-only libraries and binaries.

  
  nvidia-graphics-drivers-535 (535.54.03-0ubuntu0.20.04.4) focal; urgency=medium

[ Dimitri John Ledkov ]
* templates: encode amd64-only libraries and binaries
* debian: Enable arm64 builds (LP: #2025243).

   -- Alberto Milone   Mon, 03 Jul 2023
  13:34:05 +

  
  nvidia-graphics-drivers-525-server (525.125.06-0ubuntu0.20.04.2) focal; 
urgency=medium

[ Alberto Milone ]
* debian/rules:
  - Drop the unused generate-nvidia-icd-json target;

[ Dimitri John Ledkov ]
* debian:
  - Enable arm64 builds (LP: #2025243).
* debian/templates:
  - Encode amd64-only libraries and binaries.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-525/+bug/2025243/+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 2019212] Re: Backport packages for 22.04.3 HWE stack

2023-07-05 Thread Timo Aaltonen

** Description changed:

  [Impact]
  The graphics HWE stack from lunar needs to be backported to jammy for 22.04.3
  
  mesa
  - new major release (23.0.4)
  
+ mesa-amber
+ - a minor update from upstream mesa (21.3.7 -> 21.3.9), though there were no 
+   changes to the classic dri drivers
+ - drops old i915 driver, while mesa provides the more modern i915_dri.so 
called 
+   i915g
+ - fixes installation (LP: #2006744) and image build
+ 
  [Test case]
+ mesa:
  Install the new mesa on various hw configs, check that everything still works 
like before or better.
+ 
+ mesa-amber:
+ no need to test anything besides checking that the packages can be installed 
next to mesa and image build is fixed
  
  [Where things could go wrong]
  This is a major update of Mesa, there could be regressions but we'll backport 
the final stable release of 23.0.x in order to minimize the chance for those.

** Changed in: mesa-amber (Ubuntu)
   Status: New => Invalid

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

Title:
  Backport packages for 22.04.3 HWE stack

Status in mesa package in Ubuntu:
  Invalid
Status in mesa-amber package in Ubuntu:
  Invalid
Status in mesa source package in Jammy:
  Fix Committed
Status in mesa-amber source package in Jammy:
  New

Bug description:
  [Impact]
  The graphics HWE stack from lunar needs to be backported to jammy for 22.04.3

  mesa
  - new major release (23.0.4)

  mesa-amber
  - a minor update from upstream mesa (21.3.7 -> 21.3.9), though there were no 
changes to the classic dri drivers
  - drops old i915 driver, while mesa provides the more modern i915_dri.so 
called 
i915g
  - fixes installation (LP: #2006744) and image build

  [Test case]
  mesa:
  Install the new mesa on various hw configs, check that everything still works 
like before or better.

  mesa-amber:
  no need to test anything besides checking that the packages can be installed 
next to mesa and image build is fixed

  [Where things could go wrong]
  This is a major update of Mesa, there could be regressions but we'll backport 
the final stable release of 23.0.x in order to minimize the chance for those.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2019212/+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 2019212] Re: Backport packages for 22.04.3 HWE stack

2023-07-05 Thread Timo Aaltonen

** Also affects: mesa-amber (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Backport packages for 22.04.3 HWE stack

Status in mesa package in Ubuntu:
  Invalid
Status in mesa-amber package in Ubuntu:
  New
Status in mesa source package in Jammy:
  Fix Committed
Status in mesa-amber source package in Jammy:
  New

Bug description:
  [Impact]
  The graphics HWE stack from lunar needs to be backported to jammy for 22.04.3

  mesa
  - new major release (23.0.4)

  [Test case]
  Install the new mesa on various hw configs, check that everything still works 
like before or better.

  [Where things could go wrong]
  This is a major update of Mesa, there could be regressions but we'll backport 
the final stable release of 23.0.x in order to minimize the chance for those.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2019212/+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 2023401] Re: [Dell XPS 17 9700] Upon shutdown, shutdown process doesn't complete and the computer stays on

2023-07-05 Thread Nick Rosbrook

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

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

Title:
  [Dell XPS 17 9700] Upon shutdown, shutdown process doesn't complete
  and the computer stays on

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  When I want to shutdown my computer, very often since last Ubuntu
  version, the process seems not to go to the end, and the computer
  never shuts down. I used not to notice it, physically close my laptop
  and put it back in my bag, then hours later find it very hot and with
  fans going at full speed.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  9 16:35:50 2023
  DistUpgraded: 2023-04-21 10:53:49,032 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) 
(prog-if 00 [VGA controller])
 Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:098f]
 Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:098f]
  InstallationDate: Installed on 2021-04-12 (787 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. XPS 17 9700
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (49 days ago)
  dmi.bios.date: 03/14/2023
  dmi.bios.release: 1.24
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.24.0
  dmi.board.name: 0PV91W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.24.0:bd03/14/2023:br1.24:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0PV91W:rvrA00:cvnDellInc.:ct10:cvr:sku098F:
  dmi.product.family: XPS
  dmi.product.name: XPS 17 9700
  dmi.product.sku: 098F
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023401/+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 2025549] Re: package nvidia-firmware-535-535.54.03 (not installed) failed to install/upgrade: tentative de remplacement de « /lib/firmware/nvidia/535.54.03/gsp_ga10x.bin », qui

2023-07-05 Thread Beau Bouchard

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

** This bug is no longer a duplicate of bug 2025514
   package nvidia-firmware-535-535.54.03 (not installed) failed to 
install/upgrade: trying to overwrite 
'/lib/firmware/nvidia/535.54.03/gsp_ga10x.bin', which is also in package 
nvidia-kernel-common-535 535.54.03-0ubuntu0~gpu23.04.1
** This bug has been marked a duplicate of bug 2025565
   Package fails to update libnvidia-gl-535 / 
libnvidia-gl-535_535.54.03-0ubuntu0.22.04.1_amd64.deb

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

Title:
  package nvidia-firmware-535-535.54.03 (not installed) failed to
  install/upgrade: tentative de remplacement de «
  /lib/firmware/nvidia/535.54.03/gsp_ga10x.bin », qui appartient aussi
  au paquet nvidia-kernel-common-535 535.54.03-0ubuntu0~gpu23.04.1

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

Bug description:
  tentative de remplacement de « /lib/firmware/nvidia/535.54.03/gsp_ga10x.bin 
», qui appartient aussi
   au paquet nvidia-kernel-common-535 535.54.03-0ubuntu0~gpu23.04.1

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: nvidia-firmware-535-535.54.03 (not installed)
  Uname: Linux 6.4.1-x1g2 x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sun Jul  2 08:26:57 2023
  ErrorMessage: tentative de remplacement de « 
/lib/firmware/nvidia/535.54.03/gsp_ga10x.bin », qui appartient aussi au paquet 
nvidia-kernel-common-535 535.54.03-0ubuntu0~gpu23.04.1
  InstallationDate: Installed on 2022-10-21 (253 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: /usr/bin/python3.11, Python 3.11.2, python-is-python3, 3.11.1-3
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0
  SourcePackage: nvidia-graphics-drivers-535
  Title: package nvidia-firmware-535-535.54.03 (not installed) failed to 
install/upgrade: tentative de remplacement de « 
/lib/firmware/nvidia/535.54.03/gsp_ga10x.bin », qui appartient aussi au paquet 
nvidia-kernel-common-535 535.54.03-0ubuntu0~gpu23.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2025549/+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 2023695] Re: [Azure][MANA][VLANTagging] Support for VLAN Tagging for MANA

2023-07-05 Thread Tim Gardner

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

** Changed in: linux (Ubuntu Focal)
   Status: Incomplete => Fix Committed

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

** Changed in: linux (Ubuntu Jammy)
   Status: Incomplete => Fix Committed

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

** Changed in: linux (Ubuntu Lunar)
   Status: Incomplete => Fix Committed

** Changed in: linux (Ubuntu Lunar)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  [Azure][MANA][VLANTagging] Support for VLAN Tagging for MANA

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  This request is from MSFT LSG team to backport the MANA VLAN Tagging
  Support, the patch have been accepted upstream in and in the Linux
  next tree.

  
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=b803d1fded40

  [Test Plan]

  MSFT tested

  [Regression potential]

  Non-VLAN packets could be misclassified.

  [Other Info]

  SF: #00362474

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023695/+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 1995606] Re: Upgrade thermald to 2.5.1 for Jammy (22.04)

2023-07-05 Thread Benjamin Drung

Thanks. I have uploaded thermald 2.4.9-1ubuntu0.3 jammy with a small
change and unsubscribed ~ubuntu-sponsors. I added "Cherry-pick following
fixes from thermald 2.5.1 and 2.5.2 (LP: #1995606)" to d/changelog since
this bug was not referenced.

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

Title:
  Upgrade thermald to 2.5.1 for Jammy (22.04)

Status in OEM Priority Project:
  New
Status in thermald package in Ubuntu:
  New
Status in thermald source package in Jammy:
  In Progress

Bug description:
  [Justification]
  The purpose of this bug is that prevent the regression in the future.
  The automatic test scripts are better for the future SRU and is still on the 
planning.

  [Test case]
  For these CPU series, RPL/ADL/TGL/CML/CFL/KBL, the following tests will be 
run on machines in the CI lab:

  1. Run stress-ng, and observe the temperature/frequency/power with s-tui
    - Temperatures should stay just below trip values
    - Power/performance profiles should stay roughly the same between old 
thermald and new thermald (unless specifically expected eg: to fix 
premature/insufficient throttling)
  2. check if thermald could read rules from /dev/acpi_thermal_rel and generate 
the xml file on /etc/thermald/ correctly.
    - this depends on if acpi_thermal_rel exist.
    - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto"
   could be landed in etc/thermald/.
    - if not, the user-defined xml could be created, then jump to (3).
    - run thermald with --loglevel=debug, and compare the log with xml.auto 
file. check if the configuration could be parsed correctly.
  3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded 
correctly.
    - run thermald with --loglevel=debug, and compare the log with xml files.
    - if parsed correctly, the configurations from XML files would appear in 
the log.

  4. Run unit tests, the scripts are under test folder, using emul_temp to 
simulate the High temperatue and check thermald would throttle CPU through the 
related cooling device.
    - rapl.sh
    - intel_pstate.sh
    - powerclamp.sh
    - processor.sh
  5. check if the power/frequency would be throttled once the temperature reach 
the trip-points of thermal zone.
  6. check if system would be throttled even the temperature is under the 
trip-points.

  [ Where problems could occur ]
  since the PL1 min/max is introduced, there may have some cases that don't 
check the minimum of PL1 then make PL1 to smaller and smaller and throttle the 
CPU. 
  this may cause machines run like the old behavior that doesn't have PL1 
min/max.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1995606/+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 2026028] Re: usbrtl sometimes doesn't reload firmware

** Description changed:

  [Impact]
  
  The btrtl driver in the 5.15 jammy kernel sometimes doesn't (re-) load
  firmware which results in the BT adapter running potentially old
  firmware rather than the current version from /lib/firmware provided by
  the linux-firmware package.
  
  This will show in logs like so:
  Jul 04 14:57:23 vivo kernel: Bluetooth: hci0: RTL: examining hci_ver=0a 
hci_rev=dfc6 lmp_ver=0a lmp_subver=d922
  Jul 04 14:57:23 vivo kernel: Bluetooth: hci0: RTL: unknown IC info, lmp 
subver d922, hci rev dfc6, hci ver 000a
  Jul 04 14:57:23 vivo kernel: Bluetooth: hci0: RTL: assuming no firmware 
upload needed
  
  The driver reads subver from the adapter to determine chip type. But
  that value is overwritten by a firmware load. In the above case, a
  firmware was already loaded which returns subver d922 which the driver
  does not recognize and it therefore won't load new firmware.
  
  [Test Case]
  
- TBD. Not sure yet how to reliably reproduce this problem.
+ 1) Boot machine with USB adapter plugged in.
+ 2) Verify firmware is loaded.
+ 3) Reboot a couple of times and verify that firmware is reloaded every time.
  
  [Where Problems Could Occur]
  
  Limited to Realtek USB bluetooth adapters that use the btrtl driver.
  Issues could show up as Bluetooth connection/initialization problems.

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

Title:
  usbrtl sometimes doesn't reload firmware

Status in linux package in Ubuntu:
  New
Status in linux source package in Jammy:
  Confirmed

Bug description:
  [Impact]

  The btrtl driver in the 5.15 jammy kernel sometimes doesn't (re-) load
  firmware which results in the BT adapter running potentially old
  firmware rather than the current version from /lib/firmware provided
  by the linux-firmware package.

  This will show in logs like so:
  Jul 04 14:57:23 vivo kernel: Bluetooth: hci0: RTL: examining hci_ver=0a 
hci_rev=dfc6 lmp_ver=0a lmp_subver=d922
  Jul 04 14:57:23 vivo kernel: Bluetooth: hci0: RTL: unknown IC info, lmp 
subver d922, hci rev dfc6, hci ver 000a
  Jul 04 14:57:23 vivo kernel: Bluetooth: hci0: RTL: assuming no firmware 
upload needed

  The driver reads subver from the adapter to determine chip type. But
  that value is overwritten by a firmware load. In the above case, a
  firmware was already loaded which returns subver d922 which the driver
  does not recognize and it therefore won't load new firmware.

  [Test Case]

  1) Boot machine with USB adapter plugged in.
  2) Verify firmware is loaded.
  3) Reboot a couple of times and verify that firmware is reloaded every time.

  [Where Problems Could Occur]

  Limited to Realtek USB bluetooth adapters that use the btrtl driver.
  Issues could show up as Bluetooth connection/initialization problems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026028/+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 2026028] Re: usbrtl sometimes doesn't reload firmware

** Description changed:

  [Impact]
  
  The btrtl driver in the 5.15 jammy kernel sometimes doesn't (re-) load
  firmware which results in the BT adapter running potentially old
  firmware rather than the current version from /lib/firmware provided by
  the linux-firmware package.
  
+ This will show in logs like so:
+ Jul 04 14:57:23 vivo kernel: Bluetooth: hci0: RTL: examining hci_ver=0a 
hci_rev=dfc6 lmp_ver=0a lmp_subver=d922
+ Jul 04 14:57:23 vivo kernel: Bluetooth: hci0: RTL: unknown IC info, lmp 
subver d922, hci rev dfc6, hci ver 000a
+ Jul 04 14:57:23 vivo kernel: Bluetooth: hci0: RTL: assuming no firmware 
upload needed
+ 
+ The driver reads subver from the adapter to determine chip type. But
+ that value is overwritten by a firmware load. In the above case, a
+ firmware was already loaded which returns subver d922 which the driver
+ does not recognize and it therefore won't load new firmware.
+ 
  [Test Case]
  
- TBD.
+ TBD. Not sure yet how to reliably reproduce this problem.
  
  [Where Problems Could Occur]
  
  Limited to Realtek USB bluetooth adapters that use the btrtl driver.
  Issues could show up as Bluetooth connection/initialization problems.

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

Title:
  usbrtl sometimes doesn't reload firmware

Status in linux package in Ubuntu:
  New
Status in linux source package in Jammy:
  Confirmed

Bug description:
  [Impact]

  The btrtl driver in the 5.15 jammy kernel sometimes doesn't (re-) load
  firmware which results in the BT adapter running potentially old
  firmware rather than the current version from /lib/firmware provided
  by the linux-firmware package.

  This will show in logs like so:
  Jul 04 14:57:23 vivo kernel: Bluetooth: hci0: RTL: examining hci_ver=0a 
hci_rev=dfc6 lmp_ver=0a lmp_subver=d922
  Jul 04 14:57:23 vivo kernel: Bluetooth: hci0: RTL: unknown IC info, lmp 
subver d922, hci rev dfc6, hci ver 000a
  Jul 04 14:57:23 vivo kernel: Bluetooth: hci0: RTL: assuming no firmware 
upload needed

  The driver reads subver from the adapter to determine chip type. But
  that value is overwritten by a firmware load. In the above case, a
  firmware was already loaded which returns subver d922 which the driver
  does not recognize and it therefore won't load new firmware.

  [Test Case]

  TBD. Not sure yet how to reliably reproduce this problem.

  [Where Problems Could Occur]

  Limited to Realtek USB bluetooth adapters that use the btrtl driver.
  Issues could show up as Bluetooth connection/initialization problems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026028/+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 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM

2023-07-05 Thread David

@Samer Attrah (samerattrah)

I had exactly the same problem that you have, I solved it by disabling secure 
boot from bios.
(to have permission to disable secure boot I also had to set a supervisory 
password from bios as well).

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

Title:
  UVC  Quanta 0408:4035  camera PROBLEM

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing',
  USB 0408:4035.

  The camera is reported to have problems by many users:  
  https://linux-hardware.org/?id=usb:0408-4035
  The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera 
is “recongized” but fails installation.

  My console commands report similar info to other users: 
  
https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58

  
  PROPOSED SOLUTION 
  I got in contact with laurent.pinch...@ideasonboard.com   and with 
riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And  
me...@vger.kernel.org mailinglist.

  Laurent proposed me a fix and I modified the 5,15 uvc_driver.c
  version, and loaded it on github

  https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User-
  Facing-0x0408-0x4035-/blob/main/uvc_driver.c

  I offered to test the fix, so I tried to compile the module with the
  new source.

  COMPILING PROBLEMS
  I’m running **Ubuntu 22.04.1 LTS, with kernel 
  giuliano@Astra2A:/usr/src$ cat /proc/version_signature
  Ubuntu 5.15.0-56.62-generic 5.15.64

  BUT  the linux-source that I found installed seems to be different
  tgiuliano@Astra2A:/usr/src$ ls -al linux-so*
  lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> 
linux-source-5.15.0/linux-source-5.15.0.tar.bz2

  I expanded  the tar file, configured the IDE and compiled without error  any 
errors… 
  I manually copied the uvcvideo.ko in 
  /lib/modules/5.15.0-56-
  sudo cp…...

  then tryed to intall the new uvcvideo.ko module
  sudo rmmod uvcvideo && sudo modprobe uvcvideo

  BUT… IT FAILS
  giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo
  modprobe: ERROR: could not insert 'uvcvideo': Exec format error

  and dmesg shows
  [25961.151982] usbcore: registered new interface driver uvcvideo
  [26323.125534] usbcore: deregistering interface driver uvcvideo
  [26323.189294] uvcvideo: disagrees about version of symbol module_layout


  These are the TWO modinfo from the old and new uvcvideo modules
  https://pastebin.com/tSj8Exm6
  Basically
  OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions 
  NEW module: vermagic: 5.15.64 SMP mod_unload modversions


  -kindly ASK

  HOW can FORCE the uvcdriver.c to match mi kernel version ?
  Have I got OTHER ways to make the kernel module I’m compiling, match my 
running system ?

  I would like to test the module so to confirm the patch and let it
  enter the kernel main stream...

  
  BR
  Giuliano

  PS
  btw…. to allow Eclipse to compile the kernel, I had to pass this commands
  scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_TRUSTED_KEYS

  hope that this does not affect the module layout & checking
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  giuliano   2142 F pulseaudio
   /dev/snd/pcmC1D0p:   giuliano   2142 F...m pulseaudio
   /dev/snd/controlC0:  giuliano   2142 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-03 (66 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Acer Nitro AN517-55
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic 
root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-57-generic N/A
   linux-backports-modules-5.15.0-57-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  Tags:  jammy
  Uname: Linux 5.15.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/20/2022
  dmi.bios.release: 1.6
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Asset Tag

[Kernel-packages] [Bug 2026028] [NEW] usbrtl sometimes doesn't reload firmware

Public bug reported:

[Impact]

The btrtl driver in the 5.15 jammy kernel sometimes doesn't (re-) load
firmware which results in the BT adapter running potentially old
firmware rather than the current version from /lib/firmware provided by
the linux-firmware package.

[Test Case]

TBD.

[Where Problems Could Occur]

Limited to Realtek USB bluetooth adapters that use the btrtl driver.
Issues could show up as Bluetooth connection/initialization problems.

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

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

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

** Description changed:

  [Impact]
  
  The btrtl driver in the 5.15 jammy kernel sometimes doesn't (re-) load
  firmware which results in the BT adapter running potentially old
  firmware rather than the current version from /lib/firmware provided by
  the linux-firmware package.
  
  [Test Case]
  
  TBD.
  
  [Where Problems Could Occur]
  
- Limited to Realtek USB bluetooth adapters that use the btrl driver.
+ Limited to Realtek USB bluetooth adapters that use the btrtl driver.
  Issues could show up as Bluetooth connection/initialization problems.

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

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

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

** No longer affects: linux-hwe-5.15 (Ubuntu)

** No longer affects: linux (Ubuntu Focal)

** No longer affects: linux-hwe-5.15 (Ubuntu Focal)

** No longer affects: linux-hwe-5.15 (Ubuntu Jammy)

** Changed in: linux (Ubuntu Jammy)
   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/2026028

Title:
  usbrtl sometimes doesn't reload firmware

Status in linux package in Ubuntu:
  New
Status in linux source package in Jammy:
  Confirmed

Bug description:
  [Impact]

  The btrtl driver in the 5.15 jammy kernel sometimes doesn't (re-) load
  firmware which results in the BT adapter running potentially old
  firmware rather than the current version from /lib/firmware provided
  by the linux-firmware package.

  [Test Case]

  TBD.

  [Where Problems Could Occur]

  Limited to Realtek USB bluetooth adapters that use the btrtl driver.
  Issues could show up as Bluetooth connection/initialization problems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026028/+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 2025675] Re: Realtek Bluetooth Radio ID 6655:8771 cannot connect after update

Your BT dongle has issues and can't be enumerated:
[68416.105078] usb 1-14: Device not responding to setup address.

Can you downgrade linux-firmware to 3.13 and unplug and reinsert the
dongle and capture the output of dmesg and check if it's working or not?

Then upgrade linux-firmware to 3.14 and do the same?

I just learned that there is an issue with the btrtl driver in 5.15 that
(sometimes) prevents a firmware reload which could be a problem here.

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

Title:
  Realtek Bluetooth Radio ID 6655:8771 cannot connect after update

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  After updating my system this morning, about six hours ago, my
  Bluetooth radio (Model number: Insignia ns-pa3bt5a2b22) (Bus 001
  Device 002: ID 6655:8771 Realtek Bluetooth Radio) stopped working
  entirely.

  ubuntu-version:
Ubuntu 22.04.2 LTS
  linux-firmware:
Installed: 20220329.git681281e4-0ubuntu3.14

  Expected behavior:

  Bluetooth should connect, scanning for new devices should complete and
  list all discoverable devices.

  Actual behavior:

  Bluetooth shows up in the settings interface as expected, but does not
  connect to or show any previously connected devices (Logitech MX
  Master 3s, k850, Bose QC35), and scans for new devices forever.

  
  Additional information:

  In initial debugging stages,

  sudo dmesg | grep -i 'blue'

  Gave:
  ...
  [   85.034768] Bluetooth: hci0: Ignoring error of Inquiry Cancel command

  Following the steps given here before I found this bug:
  https://askubuntu.com/questions/1398873/bluetooth-5-0-adapter-help
  did not resolve the problem, but did cause the dmesg to go away, such that I 
now just get:
  [ 1827.904469] usb 1-1: Product: Bluetooth Radio
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peter 116412 F pulseaudio
   /dev/snd/controlC1:  peter 116412 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Dependencies: firmware-sof-signed 2.0-1ubuntu4.1
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2020-02-17 (1233 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. G3 3590
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-firmware 20220329.git681281e4-0ubuntu3.14 [modified: 
lib/firmware/rtl_bt/rtl8761b_config.bin lib/firmware/rtl_bt/rtl8761b_fw.bin]
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-76-generic 
root=UUID=27481db2-b6db-4a13-86dc-a742ee212a30 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-76-generic N/A
   linux-backports-modules-5.15.0-76-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.14
  Tags:  jammy
  Uname: Linux 5.15.0-76-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-07-03 (0 days ago)
  UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/19/2020
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.name: 0CVWRM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd08/19/2020:br1.11:svnDellInc.:pnG33590:pvr:rvnDellInc.:rn0CVWRM:rvrA00:cvnDellInc.:ct10:cvr:sku0949:
  dmi.product.family: GSeries
  dmi.product.name: G3 3590
  dmi.product.sku: 0949
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2025675/+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 2025987] Re: 5.15.0-76: Qemu live migration causes VMs to crash but works with HWE kernel

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

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

Title:
  5.15.0-76: Qemu live migration causes VMs to crash but works with HWE
  kernel

Status in linux package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  New

Bug description:
  I am trying to live migrate Qemu VMs between Amd Zen3 to Zen2 servers.

  What we expect:
  VMs continue to run after live-migrate

  What happened:
  VMs instantly get stuck after migration with 100% CPU usage.

  All Nodes are running Ubuntu 22.04.
  We have tested Kernel releases back to 5.15.0-70.

  Nodes running Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 :
  Zen2 -> Zen3 migration: OK
  Zen3 -> Zen2 migration: OK

  Nodes running Ubuntu 5.15.0-76.83-generic 5.15.99 :
  Zen2 -> Zen3 migration: OK
  Zen3 -> Zen2 migration: NOT OK

  We've tested it with fresh started and with live-migrated VMs, getting
  same results.

  Its probably related to
  KVM: SVM: fix tsc scaling cache logic
  
https://linux.googlesource.com/linux/kernel/git/torvalds/linux/+/11d39e8cc43e1c6737af19ca9372e590061b5ad2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025987/+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 2025987] Re: 5.15.0-76: Qemu live migration causes VMs to crash but works with HWE kernel

** Description changed:

  I am trying to live migrate Qemu VMs between Amd Zen3 to Zen2 servers.
  
  What we expect:
  VMs continue to run after live-migrate
  
  What happened:
  VMs instantly get stuck after migration with 100% CPU usage.
  
  All Nodes are running Ubuntu 22.04.
+ We have tested Kernel releases back to 5.15.0-70.
  
  Nodes running Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 :
  Zen2 -> Zen3 migration: OK
  Zen3 -> Zen2 migration: OK
  
  Nodes running Ubuntu 5.15.0-76.83-generic 5.15.99 :
  Zen2 -> Zen3 migration: OK
  Zen3 -> Zen2 migration: NOT OK
  
  We've tested it with fresh started and with live-migrated VMs, getting
  same results.
  
- Its probably related to 
+ Its probably related to
  KVM: SVM: fix tsc scaling cache logic
  
https://linux.googlesource.com/linux/kernel/git/torvalds/linux/+/11d39e8cc43e1c6737af19ca9372e590061b5ad2

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

Title:
  5.15.0-76: Qemu live migration causes VMs to crash but works with HWE
  kernel

Status in linux package in Ubuntu:
  New

Bug description:
  I am trying to live migrate Qemu VMs between Amd Zen3 to Zen2 servers.

  What we expect:
  VMs continue to run after live-migrate

  What happened:
  VMs instantly get stuck after migration with 100% CPU usage.

  All Nodes are running Ubuntu 22.04.
  We have tested Kernel releases back to 5.15.0-70.

  Nodes running Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 :
  Zen2 -> Zen3 migration: OK
  Zen3 -> Zen2 migration: OK

  Nodes running Ubuntu 5.15.0-76.83-generic 5.15.99 :
  Zen2 -> Zen3 migration: OK
  Zen3 -> Zen2 migration: NOT OK

  We've tested it with fresh started and with live-migrated VMs, getting
  same results.

  Its probably related to
  KVM: SVM: fix tsc scaling cache logic
  
https://linux.googlesource.com/linux/kernel/git/torvalds/linux/+/11d39e8cc43e1c6737af19ca9372e590061b5ad2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025987/+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 2025988] [NEW] Backport dwarves 1.25

2023-07-05 Thread Dimitri John Ledkov

Public bug reported:

[Impact]

To continue having BTF enabled in Linux HWE kernels and update to
dwarves is required.

v6.3+ kernels require dwarves v1.25 or better.

This bug report is similar to a previous such backport
https://bugs.launchpad.net/ubuntu/+source/dwarves-dfsg/+bug/1912811

Similar to before, to minimise changes, dwarves will be built with
vendored and statically linked libbpf on releases that have older libbpf
(jammy & kinetic). Lunar & Mantic use shared linked libbpf as the one in
the archive is the same version as vendored one.

[Test Case]

* Rebuild given series GA kernel
* On Jammy, rebuild GA, HWE, and Mantic kernels

[Where problems could occur]

Currently in jammy-lunar we ship cherry-pick from development pre-
release 1.25 to address new BTF types. The upstream approach since this
cherry-pick has changed to a more conservative one. This backport will
align Ubuntu BTF with now released versions of BTF.

Currently in jammy-lunar we have a BTF bug which leads to generating
duplicate BTF information. This backport will address it. See
https://bugs.launchpad.net/ubuntu/lunar/+source/dwarves/+bug/2025370

** Affects: libbpf (Ubuntu)
 Importance: Undecided
 Status: Fix Released

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

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

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

** Affects: libbpf (Ubuntu Mantic)
 Importance: Undecided
 Status: Fix Released

** Also affects: libbpf (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

** Also affects: libbpf (Ubuntu Mantic)
   Importance: Undecided
   Status: New

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

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

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

Title:
  Backport dwarves 1.25

Status in libbpf package in Ubuntu:
  Fix Released
Status in libbpf source package in Jammy:
  New
Status in libbpf source package in Kinetic:
  New
Status in libbpf source package in Lunar:
  New
Status in libbpf source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  To continue having BTF enabled in Linux HWE kernels and update to
  dwarves is required.

  v6.3+ kernels require dwarves v1.25 or better.

  This bug report is similar to a previous such backport
  https://bugs.launchpad.net/ubuntu/+source/dwarves-dfsg/+bug/1912811

  Similar to before, to minimise changes, dwarves will be built with
  vendored and statically linked libbpf on releases that have older
  libbpf (jammy & kinetic). Lunar & Mantic use shared linked libbpf as
  the one in the archive is the same version as vendored one.

  [Test Case]

  * Rebuild given series GA kernel
  * On Jammy, rebuild GA, HWE, and Mantic kernels

  [Where problems could occur]

  Currently in jammy-lunar we ship cherry-pick from development pre-
  release 1.25 to address new BTF types. The upstream approach since
  this cherry-pick has changed to a more conservative one. This backport
  will align Ubuntu BTF with now released versions of BTF.

  Currently in jammy-lunar we have a BTF bug which leads to generating
  duplicate BTF information. This backport will address it. See
  https://bugs.launchpad.net/ubuntu/lunar/+source/dwarves/+bug/2025370

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libbpf/+bug/2025988/+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 2025987] Re: 5.15.0-76: Qemu live migration causes VMs to crash but works with HWE kernel

** Description changed:

- I am trying to live migrate VMs between Amd Zen3 to Zen2 servers.
+ I am trying to live migrate Qemu VMs between Amd Zen3 to Zen2 servers.
  
  What we expect:
- VMs continue to run after live-migrate 
+ VMs continue to run after live-migrate
  
  What happened:
  VMs instantly get stuck after migration with 100% CPU usage.
- 
  
  All Nodes are running Ubuntu 22.04.
  
  Nodes running Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 :
  Zen2 -> Zen3 migration: OK
  Zen3 -> Zen2 migration: OK
  
- 
  Nodes running Ubuntu 5.15.0-76.83-generic 5.15.99 :
  Zen2 -> Zen3 migration: OK
  Zen3 -> Zen2 migration: NOT OK
  
  We've tested it with fresh started and with live-migrated VMs, getting
  same results.
+ 
+ Its probably related to 
+ KVM: SVM: fix tsc scaling cache logic
+ 
https://linux.googlesource.com/linux/kernel/git/torvalds/linux/+/11d39e8cc43e1c6737af19ca9372e590061b5ad2

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

Title:
  5.15.0-76: Qemu live migration causes VMs to crash but works with HWE
  kernel

Status in linux package in Ubuntu:
  New

Bug description:
  I am trying to live migrate Qemu VMs between Amd Zen3 to Zen2 servers.

  What we expect:
  VMs continue to run after live-migrate

  What happened:
  VMs instantly get stuck after migration with 100% CPU usage.

  All Nodes are running Ubuntu 22.04.

  Nodes running Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 :
  Zen2 -> Zen3 migration: OK
  Zen3 -> Zen2 migration: OK

  Nodes running Ubuntu 5.15.0-76.83-generic 5.15.99 :
  Zen2 -> Zen3 migration: OK
  Zen3 -> Zen2 migration: NOT OK

  We've tested it with fresh started and with live-migrated VMs, getting
  same results.

  Its probably related to 
  KVM: SVM: fix tsc scaling cache logic
  
https://linux.googlesource.com/linux/kernel/git/torvalds/linux/+/11d39e8cc43e1c6737af19ca9372e590061b5ad2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025987/+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 2025987] Re: 5.15.0-76: Qemu live migration causes VMs to crash but works with HWE kernel

** Attachment added: "lspci-vnvn-zen3.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025987/+attachment/5684002/+files/lspci-vnvn-zen3.log

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

Title:
  5.15.0-76: Qemu live migration causes VMs to crash but works with HWE
  kernel

Status in linux package in Ubuntu:
  New

Bug description:
  I am trying to live migrate Qemu VMs between Amd Zen3 to Zen2 servers.

  What we expect:
  VMs continue to run after live-migrate

  What happened:
  VMs instantly get stuck after migration with 100% CPU usage.

  All Nodes are running Ubuntu 22.04.

  Nodes running Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 :
  Zen2 -> Zen3 migration: OK
  Zen3 -> Zen2 migration: OK

  Nodes running Ubuntu 5.15.0-76.83-generic 5.15.99 :
  Zen2 -> Zen3 migration: OK
  Zen3 -> Zen2 migration: NOT OK

  We've tested it with fresh started and with live-migrated VMs, getting
  same results.

  Its probably related to 
  KVM: SVM: fix tsc scaling cache logic
  
https://linux.googlesource.com/linux/kernel/git/torvalds/linux/+/11d39e8cc43e1c6737af19ca9372e590061b5ad2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025987/+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 2025987] [NEW] 5.15.0-76: Qemu live migration causes VMs to crash but works with HWE kernel

Public bug reported:

I am trying to live migrate Qemu VMs between Amd Zen3 to Zen2 servers.

What we expect:
VMs continue to run after live-migrate

What happened:
VMs instantly get stuck after migration with 100% CPU usage.

All Nodes are running Ubuntu 22.04.

Nodes running Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 :
Zen2 -> Zen3 migration: OK
Zen3 -> Zen2 migration: OK

Nodes running Ubuntu 5.15.0-76.83-generic 5.15.99 :
Zen2 -> Zen3 migration: OK
Zen3 -> Zen2 migration: NOT OK

We've tested it with fresh started and with live-migrated VMs, getting
same results.

Its probably related to 
KVM: SVM: fix tsc scaling cache logic
https://linux.googlesource.com/linux/kernel/git/torvalds/linux/+/11d39e8cc43e1c6737af19ca9372e590061b5ad2

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


** Tags: kernel-bug

** Attachment added: "lspci-vnvn-zen2.log"
   
https://bugs.launchpad.net/bugs/2025987/+attachment/5684001/+files/lspci-vnvn-zen2.log

** Summary changed:

- 5.15.0-76: Qemu live migration only works with hwe kernel
+ 5.15.0-76: Qemu live migration causes VMs to crash but works with HWE kernel

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

Title:
  5.15.0-76: Qemu live migration causes VMs to crash but works with HWE
  kernel

Status in linux package in Ubuntu:
  New

Bug description:
  I am trying to live migrate Qemu VMs between Amd Zen3 to Zen2 servers.

  What we expect:
  VMs continue to run after live-migrate

  What happened:
  VMs instantly get stuck after migration with 100% CPU usage.

  All Nodes are running Ubuntu 22.04.

  Nodes running Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 :
  Zen2 -> Zen3 migration: OK
  Zen3 -> Zen2 migration: OK

  Nodes running Ubuntu 5.15.0-76.83-generic 5.15.99 :
  Zen2 -> Zen3 migration: OK
  Zen3 -> Zen2 migration: NOT OK

  We've tested it with fresh started and with live-migrated VMs, getting
  same results.

  Its probably related to 
  KVM: SVM: fix tsc scaling cache logic
  
https://linux.googlesource.com/linux/kernel/git/torvalds/linux/+/11d39e8cc43e1c6737af19ca9372e590061b5ad2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025987/+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 2025640] Re: Ubuntu 22.04 in the middle of updating drivers from 530.41.03 to 535.54.03 video input cuts out

2023-07-05 Thread Rovano

** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
   Status: Invalid => New

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

Title:
  Ubuntu 22.04 in the middle of updating drivers from 530.41.03 to
  535.54.03 video input cuts out

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

Bug description:
  https://forums.developer.nvidia.com/t/ubuntu-22-04-in-the-middle-of-
  updating-drivers-from-530-41-03-to-535-54-03-video-input-cuts-
  out/258588

  https://forums.linuxmint.com/viewtopic.php?p=2344294

  timeline 10:36 - 10:39
  switch to TTY not helped, SSH not tested
  I don't have a keyboard shortcut to restart X.

  After emergency sync, reboot (sysrq) is all fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2025640/+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 2025984] UdevDb.txt

apport information

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

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

Title:
  Size in crease in modules in 6.2.0-1007

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,
  we haven't even been able to strip off all the weight we gained with bug 
2015867 and now I've found another change eating another ~13mb.

  This time it might again be all intentional, and maybe even unchangeable.
  But I'd like to file it so that you can consciously think about it and we can 
be sure :-)

  Comparing 6.2.0-1006-kvm to 6.2.0-1007-kvm which is a Lunar SRU AFAICS.
  I see
  root@l-old:~# ll /usr/lib/modules/6.2.0-1006-kvm/kernel/net/ipv6
  total 368
  drwxr-xr-x  3 root root   4096 Jun 21 20:18 ./
  drwxr-xr-x 21 root root   4096 Jun 21 20:18 ../
  -rw-r--r--  1 root root  26305 May 31 09:04 ah6.ko
  -rw-r--r--  1 root root 119073 May 31 09:04 esp6.ko
  -rw-r--r--  1 root root  16889 May 31 09:04 esp6_offload.ko
  -rw-r--r--  1 root root  74929 May 31 09:04 ip6_udp_tunnel.ko
  -rw-r--r--  1 root root  13409 May 31 09:04 ipcomp6.ko
  drwxr-xr-x  2 root root   4096 Jun 21 20:18 netfilter/
  -rw-r--r--  1 root root  54617 May 31 09:04 sit.ko
  -rw-r--r--  1 root root  16961 May 31 09:04 tunnel6.ko
  -rw-r--r--  1 root root  19449 May 31 09:04 xfrm6_tunnel.ko

  root@l-new:~# ll /usr/lib/modules/6.2.0-1007-kvm/kernel/net/ipv6
  total 752
  drwxr-xr-x  3 root root   4096 Jun 28 20:17 ./
  drwxr-xr-x 21 root root   4096 Jun 28 20:17 ../
  -rw-r--r--  1 root root  92705 Jun 21 12:50 ah6.ko
  -rw-r--r--  1 root root 118881 Jun 21 12:50 esp6.ko
  -rw-r--r--  1 root root  83465 Jun 21 12:50 esp6_offload.ko
  -rw-r--r--  1 root root  74481 Jun 21 12:50 ip6_udp_tunnel.ko
  -rw-r--r--  1 root root  79129 Jun 21 12:50 ipcomp6.ko
  drwxr-xr-x  2 root root   4096 Jun 28 20:17 netfilter/
  -rw-r--r--  1 root root 123361 Jun 21 12:50 sit.ko
  -rw-r--r--  1 root root  81905 Jun 21 12:50 tunnel6.ko
  -rw-r--r--  1 root root  84137 Jun 21 12:50 xfrm6_tunnel.ko

  That is just an example, modules have been growing all over the place.
  In sum the mentioned ~13mb.
  But neither did all modules change, nor was it by an equal amount.
  Here for example sit.ko more than doubled.

  https://launchpad.net/ubuntu/+source/linux-kvm/6.2.0-1007.7 isn't too obvious 
either, so I'd appreciate you having a look.
  --- 
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudBuildName: minimal
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSerial: 20230628
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 23.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   TERM=xterm-256color
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1007-kvm 
root=PARTUUID=c4efe7a6-19b9-4886-a813-48bddc64bc45 ro console=tty1 
console=ttyS0 panic=-1
  ProcVersionSignature: Ubuntu 6.2.0-1007.7-kvm 6.2.12
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-1007-kvm N/A
   linux-backports-modules-6.2.0-1007-kvm  N/A
   linux-firmware  N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: cloud-image lunar
  Uname: Linux 6.2.0-1007-kvm x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

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

apport information

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

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

Title:
  Size in crease in modules in 6.2.0-1007

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,
  we haven't even been able to strip off all the weight we gained with bug 
2015867 and now I've found another change eating another ~13mb.

  This time it might again be all intentional, and maybe even unchangeable.
  But I'd like to file it so that you can consciously think about it and we can 
be sure :-)

  Comparing 6.2.0-1006-kvm to 6.2.0-1007-kvm which is a Lunar SRU AFAICS.
  I see
  root@l-old:~# ll /usr/lib/modules/6.2.0-1006-kvm/kernel/net/ipv6
  total 368
  drwxr-xr-x  3 root root   4096 Jun 21 20:18 ./
  drwxr-xr-x 21 root root   4096 Jun 21 20:18 ../
  -rw-r--r--  1 root root  26305 May 31 09:04 ah6.ko
  -rw-r--r--  1 root root 119073 May 31 09:04 esp6.ko
  -rw-r--r--  1 root root  16889 May 31 09:04 esp6_offload.ko
  -rw-r--r--  1 root root  74929 May 31 09:04 ip6_udp_tunnel.ko
  -rw-r--r--  1 root root  13409 May 31 09:04 ipcomp6.ko
  drwxr-xr-x  2 root root   4096 Jun 21 20:18 netfilter/
  -rw-r--r--  1 root root  54617 May 31 09:04 sit.ko
  -rw-r--r--  1 root root  16961 May 31 09:04 tunnel6.ko
  -rw-r--r--  1 root root  19449 May 31 09:04 xfrm6_tunnel.ko

  root@l-new:~# ll /usr/lib/modules/6.2.0-1007-kvm/kernel/net/ipv6
  total 752
  drwxr-xr-x  3 root root   4096 Jun 28 20:17 ./
  drwxr-xr-x 21 root root   4096 Jun 28 20:17 ../
  -rw-r--r--  1 root root  92705 Jun 21 12:50 ah6.ko
  -rw-r--r--  1 root root 118881 Jun 21 12:50 esp6.ko
  -rw-r--r--  1 root root  83465 Jun 21 12:50 esp6_offload.ko
  -rw-r--r--  1 root root  74481 Jun 21 12:50 ip6_udp_tunnel.ko
  -rw-r--r--  1 root root  79129 Jun 21 12:50 ipcomp6.ko
  drwxr-xr-x  2 root root   4096 Jun 28 20:17 netfilter/
  -rw-r--r--  1 root root 123361 Jun 21 12:50 sit.ko
  -rw-r--r--  1 root root  81905 Jun 21 12:50 tunnel6.ko
  -rw-r--r--  1 root root  84137 Jun 21 12:50 xfrm6_tunnel.ko

  That is just an example, modules have been growing all over the place.
  In sum the mentioned ~13mb.
  But neither did all modules change, nor was it by an equal amount.
  Here for example sit.ko more than doubled.

  https://launchpad.net/ubuntu/+source/linux-kvm/6.2.0-1007.7 isn't too obvious 
either, so I'd appreciate you having a look.
  --- 
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudBuildName: minimal
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSerial: 20230628
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 23.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   TERM=xterm-256color
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1007-kvm 
root=PARTUUID=c4efe7a6-19b9-4886-a813-48bddc64bc45 ro console=tty1 
console=ttyS0 panic=-1
  ProcVersionSignature: Ubuntu 6.2.0-1007.7-kvm 6.2.12
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-1007-kvm N/A
   linux-backports-modules-6.2.0-1007-kvm  N/A
   linux-firmware  N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: cloud-image lunar
  Uname: Linux 6.2.0-1007-kvm x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0

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

apport information

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

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

Title:
  Size in crease in modules in 6.2.0-1007

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,
  we haven't even been able to strip off all the weight we gained with bug 
2015867 and now I've found another change eating another ~13mb.

  This time it might again be all intentional, and maybe even unchangeable.
  But I'd like to file it so that you can consciously think about it and we can 
be sure :-)

  Comparing 6.2.0-1006-kvm to 6.2.0-1007-kvm which is a Lunar SRU AFAICS.
  I see
  root@l-old:~# ll /usr/lib/modules/6.2.0-1006-kvm/kernel/net/ipv6
  total 368
  drwxr-xr-x  3 root root   4096 Jun 21 20:18 ./
  drwxr-xr-x 21 root root   4096 Jun 21 20:18 ../
  -rw-r--r--  1 root root  26305 May 31 09:04 ah6.ko
  -rw-r--r--  1 root root 119073 May 31 09:04 esp6.ko
  -rw-r--r--  1 root root  16889 May 31 09:04 esp6_offload.ko
  -rw-r--r--  1 root root  74929 May 31 09:04 ip6_udp_tunnel.ko
  -rw-r--r--  1 root root  13409 May 31 09:04 ipcomp6.ko
  drwxr-xr-x  2 root root   4096 Jun 21 20:18 netfilter/
  -rw-r--r--  1 root root  54617 May 31 09:04 sit.ko
  -rw-r--r--  1 root root  16961 May 31 09:04 tunnel6.ko
  -rw-r--r--  1 root root  19449 May 31 09:04 xfrm6_tunnel.ko

  root@l-new:~# ll /usr/lib/modules/6.2.0-1007-kvm/kernel/net/ipv6
  total 752
  drwxr-xr-x  3 root root   4096 Jun 28 20:17 ./
  drwxr-xr-x 21 root root   4096 Jun 28 20:17 ../
  -rw-r--r--  1 root root  92705 Jun 21 12:50 ah6.ko
  -rw-r--r--  1 root root 118881 Jun 21 12:50 esp6.ko
  -rw-r--r--  1 root root  83465 Jun 21 12:50 esp6_offload.ko
  -rw-r--r--  1 root root  74481 Jun 21 12:50 ip6_udp_tunnel.ko
  -rw-r--r--  1 root root  79129 Jun 21 12:50 ipcomp6.ko
  drwxr-xr-x  2 root root   4096 Jun 28 20:17 netfilter/
  -rw-r--r--  1 root root 123361 Jun 21 12:50 sit.ko
  -rw-r--r--  1 root root  81905 Jun 21 12:50 tunnel6.ko
  -rw-r--r--  1 root root  84137 Jun 21 12:50 xfrm6_tunnel.ko

  That is just an example, modules have been growing all over the place.
  In sum the mentioned ~13mb.
  But neither did all modules change, nor was it by an equal amount.
  Here for example sit.ko more than doubled.

  https://launchpad.net/ubuntu/+source/linux-kvm/6.2.0-1007.7 isn't too obvious 
either, so I'd appreciate you having a look.
  --- 
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudBuildName: minimal
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSerial: 20230628
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 23.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   TERM=xterm-256color
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1007-kvm 
root=PARTUUID=c4efe7a6-19b9-4886-a813-48bddc64bc45 ro console=tty1 
console=ttyS0 panic=-1
  ProcVersionSignature: Ubuntu 6.2.0-1007.7-kvm 6.2.12
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-1007-kvm N/A
   linux-backports-modules-6.2.0-1007-kvm  N/A
   linux-firmware  N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: cloud-image lunar
  Uname: Linux 6.2.0-1007-kvm x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0

[Kernel-packages] [Bug 2025984] acpidump.txt

apport information

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

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

Title:
  Size in crease in modules in 6.2.0-1007

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,
  we haven't even been able to strip off all the weight we gained with bug 
2015867 and now I've found another change eating another ~13mb.

  This time it might again be all intentional, and maybe even unchangeable.
  But I'd like to file it so that you can consciously think about it and we can 
be sure :-)

  Comparing 6.2.0-1006-kvm to 6.2.0-1007-kvm which is a Lunar SRU AFAICS.
  I see
  root@l-old:~# ll /usr/lib/modules/6.2.0-1006-kvm/kernel/net/ipv6
  total 368
  drwxr-xr-x  3 root root   4096 Jun 21 20:18 ./
  drwxr-xr-x 21 root root   4096 Jun 21 20:18 ../
  -rw-r--r--  1 root root  26305 May 31 09:04 ah6.ko
  -rw-r--r--  1 root root 119073 May 31 09:04 esp6.ko
  -rw-r--r--  1 root root  16889 May 31 09:04 esp6_offload.ko
  -rw-r--r--  1 root root  74929 May 31 09:04 ip6_udp_tunnel.ko
  -rw-r--r--  1 root root  13409 May 31 09:04 ipcomp6.ko
  drwxr-xr-x  2 root root   4096 Jun 21 20:18 netfilter/
  -rw-r--r--  1 root root  54617 May 31 09:04 sit.ko
  -rw-r--r--  1 root root  16961 May 31 09:04 tunnel6.ko
  -rw-r--r--  1 root root  19449 May 31 09:04 xfrm6_tunnel.ko

  root@l-new:~# ll /usr/lib/modules/6.2.0-1007-kvm/kernel/net/ipv6
  total 752
  drwxr-xr-x  3 root root   4096 Jun 28 20:17 ./
  drwxr-xr-x 21 root root   4096 Jun 28 20:17 ../
  -rw-r--r--  1 root root  92705 Jun 21 12:50 ah6.ko
  -rw-r--r--  1 root root 118881 Jun 21 12:50 esp6.ko
  -rw-r--r--  1 root root  83465 Jun 21 12:50 esp6_offload.ko
  -rw-r--r--  1 root root  74481 Jun 21 12:50 ip6_udp_tunnel.ko
  -rw-r--r--  1 root root  79129 Jun 21 12:50 ipcomp6.ko
  drwxr-xr-x  2 root root   4096 Jun 28 20:17 netfilter/
  -rw-r--r--  1 root root 123361 Jun 21 12:50 sit.ko
  -rw-r--r--  1 root root  81905 Jun 21 12:50 tunnel6.ko
  -rw-r--r--  1 root root  84137 Jun 21 12:50 xfrm6_tunnel.ko

  That is just an example, modules have been growing all over the place.
  In sum the mentioned ~13mb.
  But neither did all modules change, nor was it by an equal amount.
  Here for example sit.ko more than doubled.

  https://launchpad.net/ubuntu/+source/linux-kvm/6.2.0-1007.7 isn't too obvious 
either, so I'd appreciate you having a look.
  --- 
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudBuildName: minimal
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSerial: 20230628
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 23.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   TERM=xterm-256color
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1007-kvm 
root=PARTUUID=c4efe7a6-19b9-4886-a813-48bddc64bc45 ro console=tty1 
console=ttyS0 panic=-1
  ProcVersionSignature: Ubuntu 6.2.0-1007.7-kvm 6.2.12
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-1007-kvm N/A
   linux-backports-modules-6.2.0-1007-kvm  N/A
   linux-firmware  N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: cloud-image lunar
  Uname: Linux 6.2.0-1007-kvm x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor:

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

apport information

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

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

Title:
  Size in crease in modules in 6.2.0-1007

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,
  we haven't even been able to strip off all the weight we gained with bug 
2015867 and now I've found another change eating another ~13mb.

  This time it might again be all intentional, and maybe even unchangeable.
  But I'd like to file it so that you can consciously think about it and we can 
be sure :-)

  Comparing 6.2.0-1006-kvm to 6.2.0-1007-kvm which is a Lunar SRU AFAICS.
  I see
  root@l-old:~# ll /usr/lib/modules/6.2.0-1006-kvm/kernel/net/ipv6
  total 368
  drwxr-xr-x  3 root root   4096 Jun 21 20:18 ./
  drwxr-xr-x 21 root root   4096 Jun 21 20:18 ../
  -rw-r--r--  1 root root  26305 May 31 09:04 ah6.ko
  -rw-r--r--  1 root root 119073 May 31 09:04 esp6.ko
  -rw-r--r--  1 root root  16889 May 31 09:04 esp6_offload.ko
  -rw-r--r--  1 root root  74929 May 31 09:04 ip6_udp_tunnel.ko
  -rw-r--r--  1 root root  13409 May 31 09:04 ipcomp6.ko
  drwxr-xr-x  2 root root   4096 Jun 21 20:18 netfilter/
  -rw-r--r--  1 root root  54617 May 31 09:04 sit.ko
  -rw-r--r--  1 root root  16961 May 31 09:04 tunnel6.ko
  -rw-r--r--  1 root root  19449 May 31 09:04 xfrm6_tunnel.ko

  root@l-new:~# ll /usr/lib/modules/6.2.0-1007-kvm/kernel/net/ipv6
  total 752
  drwxr-xr-x  3 root root   4096 Jun 28 20:17 ./
  drwxr-xr-x 21 root root   4096 Jun 28 20:17 ../
  -rw-r--r--  1 root root  92705 Jun 21 12:50 ah6.ko
  -rw-r--r--  1 root root 118881 Jun 21 12:50 esp6.ko
  -rw-r--r--  1 root root  83465 Jun 21 12:50 esp6_offload.ko
  -rw-r--r--  1 root root  74481 Jun 21 12:50 ip6_udp_tunnel.ko
  -rw-r--r--  1 root root  79129 Jun 21 12:50 ipcomp6.ko
  drwxr-xr-x  2 root root   4096 Jun 28 20:17 netfilter/
  -rw-r--r--  1 root root 123361 Jun 21 12:50 sit.ko
  -rw-r--r--  1 root root  81905 Jun 21 12:50 tunnel6.ko
  -rw-r--r--  1 root root  84137 Jun 21 12:50 xfrm6_tunnel.ko

  That is just an example, modules have been growing all over the place.
  In sum the mentioned ~13mb.
  But neither did all modules change, nor was it by an equal amount.
  Here for example sit.ko more than doubled.

  https://launchpad.net/ubuntu/+source/linux-kvm/6.2.0-1007.7 isn't too obvious 
either, so I'd appreciate you having a look.
  --- 
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudBuildName: minimal
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSerial: 20230628
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 23.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   TERM=xterm-256color
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1007-kvm 
root=PARTUUID=c4efe7a6-19b9-4886-a813-48bddc64bc45 ro console=tty1 
console=ttyS0 panic=-1
  ProcVersionSignature: Ubuntu 6.2.0-1007.7-kvm 6.2.12
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-1007-kvm N/A
   linux-backports-modules-6.2.0-1007-kvm  N/A
   linux-firmware  N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: cloud-image lunar
  Uname: Linux 6.2.0-1007-kvm x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0

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

apport information

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

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

Title:
  Size in crease in modules in 6.2.0-1007

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,
  we haven't even been able to strip off all the weight we gained with bug 
2015867 and now I've found another change eating another ~13mb.

  This time it might again be all intentional, and maybe even unchangeable.
  But I'd like to file it so that you can consciously think about it and we can 
be sure :-)

  Comparing 6.2.0-1006-kvm to 6.2.0-1007-kvm which is a Lunar SRU AFAICS.
  I see
  root@l-old:~# ll /usr/lib/modules/6.2.0-1006-kvm/kernel/net/ipv6
  total 368
  drwxr-xr-x  3 root root   4096 Jun 21 20:18 ./
  drwxr-xr-x 21 root root   4096 Jun 21 20:18 ../
  -rw-r--r--  1 root root  26305 May 31 09:04 ah6.ko
  -rw-r--r--  1 root root 119073 May 31 09:04 esp6.ko
  -rw-r--r--  1 root root  16889 May 31 09:04 esp6_offload.ko
  -rw-r--r--  1 root root  74929 May 31 09:04 ip6_udp_tunnel.ko
  -rw-r--r--  1 root root  13409 May 31 09:04 ipcomp6.ko
  drwxr-xr-x  2 root root   4096 Jun 21 20:18 netfilter/
  -rw-r--r--  1 root root  54617 May 31 09:04 sit.ko
  -rw-r--r--  1 root root  16961 May 31 09:04 tunnel6.ko
  -rw-r--r--  1 root root  19449 May 31 09:04 xfrm6_tunnel.ko

  root@l-new:~# ll /usr/lib/modules/6.2.0-1007-kvm/kernel/net/ipv6
  total 752
  drwxr-xr-x  3 root root   4096 Jun 28 20:17 ./
  drwxr-xr-x 21 root root   4096 Jun 28 20:17 ../
  -rw-r--r--  1 root root  92705 Jun 21 12:50 ah6.ko
  -rw-r--r--  1 root root 118881 Jun 21 12:50 esp6.ko
  -rw-r--r--  1 root root  83465 Jun 21 12:50 esp6_offload.ko
  -rw-r--r--  1 root root  74481 Jun 21 12:50 ip6_udp_tunnel.ko
  -rw-r--r--  1 root root  79129 Jun 21 12:50 ipcomp6.ko
  drwxr-xr-x  2 root root   4096 Jun 28 20:17 netfilter/
  -rw-r--r--  1 root root 123361 Jun 21 12:50 sit.ko
  -rw-r--r--  1 root root  81905 Jun 21 12:50 tunnel6.ko
  -rw-r--r--  1 root root  84137 Jun 21 12:50 xfrm6_tunnel.ko

  That is just an example, modules have been growing all over the place.
  In sum the mentioned ~13mb.
  But neither did all modules change, nor was it by an equal amount.
  Here for example sit.ko more than doubled.

  https://launchpad.net/ubuntu/+source/linux-kvm/6.2.0-1007.7 isn't too obvious 
either, so I'd appreciate you having a look.
  --- 
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudBuildName: minimal
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSerial: 20230628
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 23.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   TERM=xterm-256color
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1007-kvm 
root=PARTUUID=c4efe7a6-19b9-4886-a813-48bddc64bc45 ro console=tty1 
console=ttyS0 panic=-1
  ProcVersionSignature: Ubuntu 6.2.0-1007.7-kvm 6.2.12
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-1007-kvm N/A
   linux-backports-modules-6.2.0-1007-kvm  N/A
   linux-firmware  N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: cloud-image lunar
  Uname: Linux 6.2.0-1007-kvm x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0

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

apport information

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

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

Title:
  Size in crease in modules in 6.2.0-1007

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,
  we haven't even been able to strip off all the weight we gained with bug 
2015867 and now I've found another change eating another ~13mb.

  This time it might again be all intentional, and maybe even unchangeable.
  But I'd like to file it so that you can consciously think about it and we can 
be sure :-)

  Comparing 6.2.0-1006-kvm to 6.2.0-1007-kvm which is a Lunar SRU AFAICS.
  I see
  root@l-old:~# ll /usr/lib/modules/6.2.0-1006-kvm/kernel/net/ipv6
  total 368
  drwxr-xr-x  3 root root   4096 Jun 21 20:18 ./
  drwxr-xr-x 21 root root   4096 Jun 21 20:18 ../
  -rw-r--r--  1 root root  26305 May 31 09:04 ah6.ko
  -rw-r--r--  1 root root 119073 May 31 09:04 esp6.ko
  -rw-r--r--  1 root root  16889 May 31 09:04 esp6_offload.ko
  -rw-r--r--  1 root root  74929 May 31 09:04 ip6_udp_tunnel.ko
  -rw-r--r--  1 root root  13409 May 31 09:04 ipcomp6.ko
  drwxr-xr-x  2 root root   4096 Jun 21 20:18 netfilter/
  -rw-r--r--  1 root root  54617 May 31 09:04 sit.ko
  -rw-r--r--  1 root root  16961 May 31 09:04 tunnel6.ko
  -rw-r--r--  1 root root  19449 May 31 09:04 xfrm6_tunnel.ko

  root@l-new:~# ll /usr/lib/modules/6.2.0-1007-kvm/kernel/net/ipv6
  total 752
  drwxr-xr-x  3 root root   4096 Jun 28 20:17 ./
  drwxr-xr-x 21 root root   4096 Jun 28 20:17 ../
  -rw-r--r--  1 root root  92705 Jun 21 12:50 ah6.ko
  -rw-r--r--  1 root root 118881 Jun 21 12:50 esp6.ko
  -rw-r--r--  1 root root  83465 Jun 21 12:50 esp6_offload.ko
  -rw-r--r--  1 root root  74481 Jun 21 12:50 ip6_udp_tunnel.ko
  -rw-r--r--  1 root root  79129 Jun 21 12:50 ipcomp6.ko
  drwxr-xr-x  2 root root   4096 Jun 28 20:17 netfilter/
  -rw-r--r--  1 root root 123361 Jun 21 12:50 sit.ko
  -rw-r--r--  1 root root  81905 Jun 21 12:50 tunnel6.ko
  -rw-r--r--  1 root root  84137 Jun 21 12:50 xfrm6_tunnel.ko

  That is just an example, modules have been growing all over the place.
  In sum the mentioned ~13mb.
  But neither did all modules change, nor was it by an equal amount.
  Here for example sit.ko more than doubled.

  https://launchpad.net/ubuntu/+source/linux-kvm/6.2.0-1007.7 isn't too obvious 
either, so I'd appreciate you having a look.
  --- 
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudBuildName: minimal
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSerial: 20230628
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 23.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   TERM=xterm-256color
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1007-kvm 
root=PARTUUID=c4efe7a6-19b9-4886-a813-48bddc64bc45 ro console=tty1 
console=ttyS0 panic=-1
  ProcVersionSignature: Ubuntu 6.2.0-1007.7-kvm 6.2.12
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-1007-kvm N/A
   linux-backports-modules-6.2.0-1007-kvm  N/A
   linux-firmware  N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: cloud-image lunar
  Uname: Linux 6.2.0-1007-kvm x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0

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

apport information

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

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

Title:
  Size in crease in modules in 6.2.0-1007

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,
  we haven't even been able to strip off all the weight we gained with bug 
2015867 and now I've found another change eating another ~13mb.

  This time it might again be all intentional, and maybe even unchangeable.
  But I'd like to file it so that you can consciously think about it and we can 
be sure :-)

  Comparing 6.2.0-1006-kvm to 6.2.0-1007-kvm which is a Lunar SRU AFAICS.
  I see
  root@l-old:~# ll /usr/lib/modules/6.2.0-1006-kvm/kernel/net/ipv6
  total 368
  drwxr-xr-x  3 root root   4096 Jun 21 20:18 ./
  drwxr-xr-x 21 root root   4096 Jun 21 20:18 ../
  -rw-r--r--  1 root root  26305 May 31 09:04 ah6.ko
  -rw-r--r--  1 root root 119073 May 31 09:04 esp6.ko
  -rw-r--r--  1 root root  16889 May 31 09:04 esp6_offload.ko
  -rw-r--r--  1 root root  74929 May 31 09:04 ip6_udp_tunnel.ko
  -rw-r--r--  1 root root  13409 May 31 09:04 ipcomp6.ko
  drwxr-xr-x  2 root root   4096 Jun 21 20:18 netfilter/
  -rw-r--r--  1 root root  54617 May 31 09:04 sit.ko
  -rw-r--r--  1 root root  16961 May 31 09:04 tunnel6.ko
  -rw-r--r--  1 root root  19449 May 31 09:04 xfrm6_tunnel.ko

  root@l-new:~# ll /usr/lib/modules/6.2.0-1007-kvm/kernel/net/ipv6
  total 752
  drwxr-xr-x  3 root root   4096 Jun 28 20:17 ./
  drwxr-xr-x 21 root root   4096 Jun 28 20:17 ../
  -rw-r--r--  1 root root  92705 Jun 21 12:50 ah6.ko
  -rw-r--r--  1 root root 118881 Jun 21 12:50 esp6.ko
  -rw-r--r--  1 root root  83465 Jun 21 12:50 esp6_offload.ko
  -rw-r--r--  1 root root  74481 Jun 21 12:50 ip6_udp_tunnel.ko
  -rw-r--r--  1 root root  79129 Jun 21 12:50 ipcomp6.ko
  drwxr-xr-x  2 root root   4096 Jun 28 20:17 netfilter/
  -rw-r--r--  1 root root 123361 Jun 21 12:50 sit.ko
  -rw-r--r--  1 root root  81905 Jun 21 12:50 tunnel6.ko
  -rw-r--r--  1 root root  84137 Jun 21 12:50 xfrm6_tunnel.ko

  That is just an example, modules have been growing all over the place.
  In sum the mentioned ~13mb.
  But neither did all modules change, nor was it by an equal amount.
  Here for example sit.ko more than doubled.

  https://launchpad.net/ubuntu/+source/linux-kvm/6.2.0-1007.7 isn't too obvious 
either, so I'd appreciate you having a look.
  --- 
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudBuildName: minimal
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSerial: 20230628
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 23.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   TERM=xterm-256color
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1007-kvm 
root=PARTUUID=c4efe7a6-19b9-4886-a813-48bddc64bc45 ro console=tty1 
console=ttyS0 panic=-1
  ProcVersionSignature: Ubuntu 6.2.0-1007.7-kvm 6.2.12
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-1007-kvm N/A
   linux-backports-modules-6.2.0-1007-kvm  N/A
   linux-firmware  N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: cloud-image lunar
  Uname: Linux 6.2.0-1007-kvm x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0

[Kernel-packages] [Bug 2025984] [NEW] Size in crease in modules in 6.2.0-1007

Public bug reported:

Hi,
we haven't even been able to strip off all the weight we gained with bug 
2015867 and now I've found another change eating another ~13mb.

This time it might again be all intentional, and maybe even unchangeable.
But I'd like to file it so that you can consciously think about it and we can 
be sure :-)

Comparing 6.2.0-1006-kvm to 6.2.0-1007-kvm which is a Lunar SRU AFAICS.
I see
root@l-old:~# ll /usr/lib/modules/6.2.0-1006-kvm/kernel/net/ipv6
total 368
drwxr-xr-x  3 root root   4096 Jun 21 20:18 ./
drwxr-xr-x 21 root root   4096 Jun 21 20:18 ../
-rw-r--r--  1 root root  26305 May 31 09:04 ah6.ko
-rw-r--r--  1 root root 119073 May 31 09:04 esp6.ko
-rw-r--r--  1 root root  16889 May 31 09:04 esp6_offload.ko
-rw-r--r--  1 root root  74929 May 31 09:04 ip6_udp_tunnel.ko
-rw-r--r--  1 root root  13409 May 31 09:04 ipcomp6.ko
drwxr-xr-x  2 root root   4096 Jun 21 20:18 netfilter/
-rw-r--r--  1 root root  54617 May 31 09:04 sit.ko
-rw-r--r--  1 root root  16961 May 31 09:04 tunnel6.ko
-rw-r--r--  1 root root  19449 May 31 09:04 xfrm6_tunnel.ko

root@l-new:~# ll /usr/lib/modules/6.2.0-1007-kvm/kernel/net/ipv6
total 752
drwxr-xr-x  3 root root   4096 Jun 28 20:17 ./
drwxr-xr-x 21 root root   4096 Jun 28 20:17 ../
-rw-r--r--  1 root root  92705 Jun 21 12:50 ah6.ko
-rw-r--r--  1 root root 118881 Jun 21 12:50 esp6.ko
-rw-r--r--  1 root root  83465 Jun 21 12:50 esp6_offload.ko
-rw-r--r--  1 root root  74481 Jun 21 12:50 ip6_udp_tunnel.ko
-rw-r--r--  1 root root  79129 Jun 21 12:50 ipcomp6.ko
drwxr-xr-x  2 root root   4096 Jun 28 20:17 netfilter/
-rw-r--r--  1 root root 123361 Jun 21 12:50 sit.ko
-rw-r--r--  1 root root  81905 Jun 21 12:50 tunnel6.ko
-rw-r--r--  1 root root  84137 Jun 21 12:50 xfrm6_tunnel.ko

That is just an example, modules have been growing all over the place.
In sum the mentioned ~13mb.
But neither did all modules change, nor was it by an equal amount.
Here for example sit.ko more than doubled.

https://launchpad.net/ubuntu/+source/linux-kvm/6.2.0-1007.7 isn't too obvious 
either, so I'd appreciate you having a look.
--- 
ProblemType: Bug
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: 
ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
CRDA: N/A
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudBuildName: minimal
CloudID: lxd
CloudName: lxd
CloudPlatform: lxd
CloudSerial: 20230628
CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
DistroRelease: Ubuntu 23.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci: Error: [Errno 2] No such file or directory: 'lspci'
Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
Package: linux (not installed)
PciMultimedia:
 
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
 TERM=xterm-256color
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1007-kvm 
root=PARTUUID=c4efe7a6-19b9-4886-a813-48bddc64bc45 ro console=tty1 
console=ttyS0 panic=-1
ProcVersionSignature: Ubuntu 6.2.0-1007.7-kvm 6.2.12
RelatedPackageVersions:
 linux-restricted-modules-6.2.0-1007-kvm N/A
 linux-backports-modules-6.2.0-1007-kvm  N/A
 linux-firmware  N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
Tags: cloud-image lunar
Uname: Linux 6.2.0-1007-kvm x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 2/2/2022
dmi.bios.release: 0.0
dmi.bios.vendor: EDK II
dmi.bios.version: unknown
dmi.board.name: LXD
dmi.board.vendor: Canonical Ltd.
dmi.board.version: pc-q35-8.0
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-8.0
dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-8.0
dmi.sys.vendor: QEMU

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


** Tags: apport-collected bot-stop-nagging cloud-image lunar

** Tags added: bot-stop-nagging

** Tags added: apport-collected cloud-image lunar

** Description changed:

  Hi,
  we haven't even been able to strip off all the weight we gained with bug 
2015867 and now I've found another change eating another ~13mb.
  
  This time it might again be all intentional, and maybe even unchangeable.
  But I'd like to file it so that you can consciously think about it and we can 
be sure :-)
  
  Comparing

[Kernel-packages] [Bug 2025915] Re: package linux-headers-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: installed linux-headers-6.2.0-24-generic package post-installation script subprocess r

You have unsupported DKMS modules installed that prevent the kernel
upgrade. Remove them and retry the upgrade:

$ dkms remove anbox-ashmem/1 --all
$ dkms remove anbox-binder/1 --all

Or you disable dkms autoinstall:

$ touch /etc/dkms/no-autoinstall


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

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

Title:
  package linux-headers-6.2.0-24-generic 6.2.0-24.24 failed to
  install/upgrade: installed linux-headers-6.2.0-24-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Upgrading to Ubuntu 23.04 I got
  The upgrade will continue but the 'linux-image-6.2.0-24-generic' package may 
not be in a working state. Please consider submitting a bug report about it.

  installed linux-image-6.2.0-24-generic package post-installation
  script subprocess returned error exit status 1

  Could not install the upgrades

  The upgrade has aborted. Your system could be in an unusable state. A
  recovery will run now (dpkg --configure -a).

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-24-generic 6.2.0-24.24
  ProcVersionSignature: Ubuntu 5.19.0-46.47-generic 5.19.17
  Uname: Linux 5.19.0-46-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brad   1995 F wireplumber
   /dev/snd/seq:brad   1992 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  Date: Tue Jul  4 14:21:28 2023
  ErrorMessage: installed linux-headers-6.2.0-24-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2020-07-28 (1071 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20JTS1GT1E
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic 
root=UUID=102d7791-8e92-444e-b259-b45288c3edab ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  SourcePackage: linux
  Title: package linux-headers-6.2.0-24-generic 6.2.0-24.24 failed to 
install/upgrade: installed linux-headers-6.2.0-24-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to lunar on 2023-07-04 (0 days ago)
  dmi.bios.date: 02/26/2018
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET45W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20JTS1GT1E
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: J70046952
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.19
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET45W(1.24):bd02/26/2018:br1.24:efr1.19:svnLENOVO:pn20JTS1GT1E:pvrThinkPadT470sW10DG:rvnLENOVO:rn20JTS1GT1E:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20JT_BU_Think_FM_ThinkPadT470sW10DG:
  dmi.product.family: ThinkPad T470s W10DG
  dmi.product.name: 20JTS1GT1E
  dmi.product.sku: LENOVO_MT_20JT_BU_Think_FM_ThinkPad T470s W10DG
  dmi.product.version: ThinkPad T470s W10DG
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025915/+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 2025971] [NEW] package libnvidia-compute-450-server (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in

2023-07-05 Thread redhwan nasser

Public bug reported:

I try to use nvidia-graphics-drivers-450-server with RTX 4090.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libnvidia-compute-450-server (not installed)
ProcVersionSignature: Ubuntu 5.15.0-76.83~20.04.1-generic 5.15.99
Uname: Linux 5.15.0-76-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.27
AptOrdering:
 libcuda1-340:amd64: Remove
 nvidia-opencl-icd-340:amd64: Remove
 libnvidia-compute-450-server:amd64: Install
 nvidia-utils-450-server:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Jul  5 16:03:14 2023
DpkgTerminalLog:
 Preparing to unpack 
.../libnvidia-compute-450-server_450.248.02-0ubuntu0.20.04.1_amd64.deb ...
 Unpacking libnvidia-compute-450-server:amd64 (450.248.02-0ubuntu0.20.04.1) ...
 [1mdpkg:[0m error processing archive 
/var/cache/apt/archives/libnvidia-compute-450-server_450.248.02-0ubuntu0.20.04.1_amd64.deb
 (--unpack):
  trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is 
also in package nvidia-340 340.108-0ubuntu5.20.04.2
ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', 
which is also in package nvidia-340 340.108-0ubuntu5.20.04.2
InstallationDate: Installed on 2023-06-26 (9 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.9
SourcePackage: nvidia-graphics-drivers-450-server
Title: package libnvidia-compute-450-server (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package 
nvidia-340 340.108-0ubuntu5.20.04.2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

Title:
  package libnvidia-compute-450-server (not installed) failed to
  install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-
  gnu/libnvidia-ml.so', which is also in package nvidia-340
  340.108-0ubuntu5.20.04.2

Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  New

Bug description:
  I try to use nvidia-graphics-drivers-450-server with RTX 4090.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libnvidia-compute-450-server (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-76.83~20.04.1-generic 5.15.99
  Uname: Linux 5.15.0-76-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.27
  AptOrdering:
   libcuda1-340:amd64: Remove
   nvidia-opencl-icd-340:amd64: Remove
   libnvidia-compute-450-server:amd64: Install
   nvidia-utils-450-server:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Jul  5 16:03:14 2023
  DpkgTerminalLog:
   Preparing to unpack 
.../libnvidia-compute-450-server_450.248.02-0ubuntu0.20.04.1_amd64.deb ...
   Unpacking libnvidia-compute-450-server:amd64 (450.248.02-0ubuntu0.20.04.1) 
...
   [1mdpkg:[0m error processing archive 
/var/cache/apt/archives/libnvidia-compute-450-server_450.248.02-0ubuntu0.20.04.1_amd64.deb
 (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is 
also in package nvidia-340 340.108-0ubuntu5.20.04.2
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package 
nvidia-340 340.108-0ubuntu5.20.04.2
  InstallationDate: Installed on 2023-06-26 (9 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: nvidia-graphics-drivers-450-server
  Title: package libnvidia-compute-450-server (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package 
nvidia-340 340.108-0ubuntu5.20.04.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450-server/+bug/2025971/+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 1995606] Re: Upgrade thermald to 2.5.1 for Jammy (22.04)

2023-07-05 Thread koba

+202307051456,
@Raof, @Lucas
v3: because the patch, 0004-Fixed-enumeration-of-cpu-thermal-sensors.patch,
can't verify on the proper machine, pull it out from patches.

** Patch added: "thermald_jammy_2.4.9-1ubuntu0.3.v3.debdiff"

https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1995606/+attachment/5683967/+files/thermald_jammy_2.4.9-1ubuntu0.3.v3.debdiff

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

Title:
Upgrade thermald to 2.5.1 for Jammy (22.04)

Status in OEM Priority Project:
New
Status in thermald package in Ubuntu:
New
Status in thermald source package in Jammy:
In Progress

Bug description:
[Justification]
The purpose of this bug is that prevent the regression in the future.
The automatic test scripts are better for the future SRU and is still on the
planning.

[Test case]
For these CPU series, RPL/ADL/TGL/CML/CFL/KBL, the following tests will be
run on machines in the CI lab:

1. Run stress-ng, and observe the temperature/frequency/power with s-tui
- Temperatures should stay just below trip values
- Power/performance profiles should stay roughly the same between old
thermald and new thermald (unless specifically expected eg: to fix
premature/insufficient throttling)
2. check if thermald could read rules from /dev/acpi_thermal_rel and generate
the xml file on /etc/thermald/ correctly.
- this depends on if acpi_thermal_rel exist.
- if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto"
could be landed in etc/thermald/.
- if not, the user-defined xml could be created, then jump to (3).
- run thermald with --loglevel=debug, and compare the log with xml.auto
file. check if the configuration could be parsed correctly.
3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded
correctly.
- run thermald with --loglevel=debug, and compare the log with xml files.
- if parsed correctly, the configurations from XML files would appear in
the log.

4. Run unit tests, the scripts are under test folder, using emul_temp to
simulate the High temperatue and check thermald would throttle CPU through the
related cooling device.
- rapl.sh
- intel_pstate.sh
- powerclamp.sh
- processor.sh
5. check if the power/frequency would be throttled once the temperature reach
the trip-points of thermal zone.
6. check if system would be throttled even the temperature is under the
trip-points.

[ Where problems could occur ]
since the PL1 min/max is introduced, there may have some cases that don't
check the minimum of PL1 then make PL1 to smaller and smaller and throttle the
CPU.
this may cause machines run like the old behavior that doesn't have PL1
min/max.

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

[Kernel-packages] [Bug 1995606] Re: Upgrade thermald to 2.5.1 for Jammy (22.04)