[Kernel-packages] [Bug 1724863] Update Released

2017-11-14 Thread Chris Halse Rogers
The verification of the Stable Release Update for bcmwl has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  bcmwl 6.30.223.271+bdcom-0ubuntu1~1.1 ADT test failure with linux-hwe-
  edge 4.13.0-16.19~16.04.3

Status in bcmwl package in Ubuntu:
  In Progress
Status in bcmwl source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Currently the DKMS package bcmwl-kernel-source fails to install in
  supported custom kernels that are based on 4.11 or 4.13. That includes
  the current 4.11 hwe-edge and the upcoming 4.13 hwe-edge kernels and
  some of the custom and cloud kernels as well.

  [Test Case]

  Install the bcmwl-kernel-source package with the 4.13 hwe-edge kernel
  from -proposed. The package installation should proceed without any
  errors.

  [Regression Potential]

  Although new patches were added, the regression risk is very low since
  the new changes are conditionally compiled based on the kernel version.

  Besides that the new package was tested with the following kernels in an
  amd64 environment:

  - linux-generic 4.4
  - linux-hwe 4.10
  - linux-hwe-edge 4.11
  - linux-hwe-edge 4.13 (from xenial-proposed)
  - linux-azure 4.11
  - linux-azure-edge 4.13 (which is in process of getting promoted to
xenial-proposed)

  [Original Description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/b/bcmwl/20171018_120646_2caa6@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/b/bcmwl/20171018_120820_2caa6@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1724863/+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 1773637] Update Released

2019-01-15 Thread Chris Halse Rogers
The verification of the Stable Release Update for ubuntu-release-
upgrader has completed successfully and the package has now been
released to -updates.  Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report.  In the event that you encounter a regression using the package
from -updates please report a new bug using ubuntu-bug and tag the bug
report regression-update so we can easily find any regressions.

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

Title:
  Distribution upgrade to 18.04: used nvidia display driver is commented
  out

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Won't Fix
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Cosmic:
  Won't Fix
Status in ubuntu-release-upgrader source package in Cosmic:
  Fix Released

Bug description:
  Impact
  --
  Users who have manually configured an xorg.conf file with nvidia enabled as a 
driver will be surprised to have disabled on upgrade to a new release of Ubuntu 
and won't have a graphical display.

  Test Case
  -
  If you don't have a system with nvidia hardware to upgrade this is a bit 
convoluted but still works.

  1) Run do-release-upgrade (use -d if upgrading to disco)
  2) Cancel the upgrade
  3) Create an /etc/X11/xorg.conf file with a Device section listed in the 
original description using the nvidia driver.
  4) cd to /tmp/ubuntu-release-upgrader-$TEMPNAME
  5) run ./$target-release-name --frontend DistUpgradeViewText
  6) Observe the Driver line is commented out of xorg.conf

  When testing the release-upgrader from -proposed you'll need to use
  the -p switch to get the right tarball. Additionally, you'll want to
  add a step 4.5 where you modify xorg_fix_proprietary.py so nvidia
  defaults to True instead of False (line 106) this'll simulate the
  nvidia driver being loaded.

  Regression Potential
  
  This just changes how xorg_fix_proprietary check for nvidia being in use and 
it only affects people who have an /etc/X11/xorg.conf so the impact of a 
regression is rather small. Additionally, the logic used to determine if nvidia 
in use is the same logic used in the apport package hook for all xorg packages 
so is well tested.

  Original Description
  
  I upgraded my system from 17.10 to 18.04 Bionic Beaver via do-release-upgrade.
  After the installation had finished, Xorg wouldn't start. I later found out 
that this was because the installation routine had commented out the nvidia 
display driver I used in the xorg.conf:

  Section "Device"
  Identifier "nvidia"
  #Driver "nvidia"
  BusID "PCI:10@0:0:0"
  Option "ConstrainCursor" "off"
  EndSection

  As the installtion routine backuped my xorg.conf I could verify that
  the line hadn't been commented out before upgrading. Removing the "#"
  solved the problem.

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..0a.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:0a:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 27 11:43:16 2018
  DistUpgraded: 2018-05-21 10:52:35,978 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-22-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:229d]
     Subsystem: Hewlett-Packard Company GM108M [GeForce 840M] [103c:229d]
  InstallationDate: Installed on 2017-11-02 (205 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c76a9d7-c435-4600-abc9-2ecd10fc3001 ro 

[Kernel-packages] [Bug 1754584] Update Released

2018-04-17 Thread Chris Halse Rogers
The verification of the Stable Release Update for zfs-linux has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  zfs system process hung on container stop/delete

Status in Native ZFS for Linux:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in zfs-linux source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Committed
Status in zfs-linux source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in zfs-linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Request [Xenial][Artful] ==

  == Justification ==

  It is possible to hang zfs asynchronous reads if a read to a page that
  is mmap'd onto the the file being read is the same offset in the
  mapping as in the file. This is caused by two lock operations on the
  page.

  == Fix ==

  Upstream ZFS fix to ensure the page is not double-locked during async
  I/O of one or more pages.

  == Testing ==

  Create a zfs pool + zfs file system, run the reproducer program in
  comment #28 on the zfs filesystem.  Without the fix this can lock up,
  with the fix this runs to completion.

  == Regression Potential ==

  Minimal, the locking fix addresses a fundamental bug in the locking
  and this should not affect ZFS read/write I/O with this fix.

  --

  Summary:
  On a Bionic system running 4.15.0-10-generic, after attempting to build 
libaio in a Bionic daily container I cannot stop or delete the container. dmesg 
shows a variety of hung tasks

  Steps to Reproduce:
  Use the following script and watch for the the hang. At that point attempt to 
stop or delete the container: http://paste.ubuntu.com/p/SxfgbxM8v7/

  Originally filed against LXD: https://github.com/lxc/lxd/issues/4314

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  powersj2414 F pulseaudio
   /dev/snd/controlC0:  powersj2414 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  9 09:19:11 2018
  HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb
  InstallationDate: Installed on 2018-02-19 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  Lsusb:
   Bus 001 Device 002: ID 8087:8001 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20BSCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=/dev/mapper/ubuntu--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET42W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET42W(1.20):bd09/13/2017:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 3rd
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO
  ---
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  powersj1878 F pulseaudio
   /dev/snd/controlC0:  p

[Kernel-packages] [Bug 1728115] Re: crashkernel offset prevents kernel boot

2018-03-20 Thread Chris Halse Rogers
This package has been waiting for testing in Artful for 90 days and is
blocking the release of other makedumpfile fixes for Xenial and Artful.
Please test this SRU!

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

Title:
  crashkernel offset prevents kernel boot

Status in linux package in Ubuntu:
  Incomplete
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  New
Status in makedumpfile source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Incomplete
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  On Power Systems, the kernel won't boot when given a crashkernel parameter 
with an offset/start address of 32M. No output will be shown, giving no clue to 
the user why the system has not booted, or what the problem is.

  [Test Case]
  Installing kdump-tools on artful, then booting the system. It won't boot. 
With the fix, it boots and the crash kernel is reserved.

  [Regression Potential]
  Some Power Systems might have problems loading the kernel at this address. 
LP#1567539 is not really clear if PowerNV systems won't kdump when using an 
address different from 32M. However, it has been requested from an IBM person 
to test it with 128M instead, and no particular problem was shown. It's 
possible that there was no reason at first to use 32M, and no problems will be 
found on either PowerNV or other systems on the field. On the other hand, it's 
possible they might break kdump. But, right now, those systems won't even boot 
the first kernel without this change.

  

  The linux kernel won't boot when crashkernel parameter tells it to
  load a crash kernel at 32Mi on ppc64el on artful.

  This happens because the artful kernel is too big. In fact, multiple
  requirements on the architecture lead to that:

  Kernel memory at address 0 is reserved.
  crashkernel must be at first RMO, so architecture puts it at 128Mi. However, 
kdump-tools currently puts it at @32Mi because of bug 
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1567539.
  PACA and LPPACA need to be at the first RMO as well, and with 2048 CPUs, they 
take more than 5MB and 2MiB, respectively.

  With the kernel now taking around 25MB from stext to _end, the kernel
  can't reserve enough memory for PACA or LPPACA right after boot, and
  it panics.

  So, right after installing kdump-tools on artful, and rebooting, the
  kernel won't boot, with no sign of life as we haven't even started any
  console. Investigation for this issue took an entire day.

  The fix would be setting the loading address to 128MiB, and start
  reducing size of PACA and maybe remove some of the requirements for
  the location of PACA and crash kernel.

  I would not even set the loading address of the crash kernel in the
  parameter itself, and leave it to the kernel to decide it, which it
  already does and already would put it at 128Mi.

  Cascardo.

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

2018-03-20 Thread Chris Halse Rogers
The verification of the Stable Release Update for zfs-linux has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  zfs-import-cache.service fails on startup

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Artful:
  Fix Released
Status in zfs-linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Request, Artful ==

  Enable ZFS module to be loaded without the broken ubuntu-load-zfs-
  unconditionally.patch.

  == Fix ==

  Add a new zfs-load-module.service script that modprobes the ZFS module
  and remove any hard coded module loading from zfs-import-cache.service
  & zfs-import-scan.service and make these latter scripts require the
  new zfs-load-module.service script.  Also remove the now defunct
  ubuntu-load-zfs-unconditionally.patch as this will no longer be
  required.

  == Testcase ==

  On a clean VM, install with the fixed package, zfs should load
  automatically.

  == Regression potential ==

  ZFS module may not load if the changes are broken. However, testing
  proves this not to be the case.

  

  I just noticed on my test VM of artful that zfs-import-cache.service
  does not have a ConditionPathExists=/etc/zfs/zpool.cache. Because of
  that, it fails on startup, since the cache file does not exist.

  This line is being deleted by 
debian/patches/ubuntu-load-zfs-unconditionally.patch. This patch seems to exist 
per:
  https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1672749

  This patch still exists in bionic, so I assume it will be similarly
  broken.

  If the goal of the patch is to load the module (and only that), I
  think it should create a third unit instead:

  zfs-load-module.service
   ^^ runs modprobe zfs

  zfs-import-cache.service & zfs-import-scan.service
    ^^ per upstream minus modprobe plus Requires=zfs-load-module.service

  I have tested this manually and it works. I can submit a package patch
  if this is the desired solution.

  Interestingly, before this change, zfs-import-scan.service wasn't
  starting. If started manually, it worked. I had to give it a
  `systemctl enable zfs-import-scan.service` to create the Wants
  symlinks. Looking at the zfsutils-linux.postinst, I see the correct
  boilerplate from dh_systemd, so I'm not sure why this wasn't already
  done. Can anyone confirm or deny whether zfs-import-scan.service is
  enabled out-of-the-box on their system?

  Is the zfs-import-scan.service not starting actually the cause of the
  original bug? The design is that *either* zfs-import-cache.service or
  zfs-import-scan.service starts. They both call modprobe zfs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1741081/+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 1788314] Re: Conflict between zfs-linux and s390-tools

2018-10-02 Thread Chris Halse Rogers
Hello Stéphane, or anyone else affected,

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

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

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

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

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

** Tags added: verification-needed verification-needed-bionic

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

Title:
  Conflict between zfs-linux and s390-tools

Status in s390-tools package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Invalid

Bug description:
  Not sure which of the two needs fixing, but there's a path conflict
  between zfs-linux and s390-tools which effectively prevents installing
  ZFS on s390x in cosmic.

  (Reading database ... 83042 files and directories currently installed.)
  Preparing to unpack .../zfsutils-linux_0.7.9-3ubuntu5_s390x.deb ...
  Unpacking zfsutils-linux (0.7.9-3ubuntu5) ...
  dpkg: error processing archive 
/var/cache/apt/archives/zfsutils-linux_0.7.9-3ubuntu5_s390x.deb (--unpack):
   trying to overwrite '/usr/share/initramfs-tools/hooks/zdev', which is also 
in package s390-tools 2.6.0-0ubuntu2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/zfsutils-linux_0.7.9-3ubuntu5_s390x.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  Exit request sent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1788314/+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 1720197] Re: Every second(?) boot fails to display anything [MSHYBRID mode]

2018-10-02 Thread Chris Halse Rogers
I have made some changes to my configuration, so it's not an entirely
clean test, but I *did* notice that I no longer needed to mess with
gfxpayload. I guess that it's fixed?

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

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

Title:
  Every second(?) boot fails to display anything [MSHYBRID mode]

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

Bug description:
  When this laptop's firmware is set to MSHYBRID mode (intel/nvidia
  switchable graphics) it seems that every second boot it fails to
  display anything.

  This appears to be regardless of whether or not I enter the grub menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  3020 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Sep 28 13:41:53 2017
  InstallationDate: Installed on 2017-09-20 (8 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170919)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76 Oryx Pro
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic.efi.signed 
root=ZFS=rpool/system ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.02dRSA1 02/20/2017
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76
  dmi.board.version: oryp3-ess
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.version: oryp3-ess
  dmi.sys.vendor: System76

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1720197/+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 1825940] Update Released

2019-08-13 Thread Chris Halse Rogers
The verification of the Stable Release Update for mesa has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [graphics] Enable ICL

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Ice Lake (ICL) graphics needs to be enabled for OEM OSP1 image which is based 
on 18.04.3 graphics stack with linux-oem-osp1 kernel.

  
  [Test case]
  The usual desktop usage, graphics tests etc.

  
  [Regression potential]
  Linux-oem-osp1 kernel is a new kernel used only on new OEM enablements, and 
it can't regress any currently running system.

  Mesa backports are limited to ICL, so they shouldn't regress earlier
  generations either.

  --

  Original description:

  ICL graphics is not enabled in 19.04.
  if you want to use 19.04 on ICL platform, you need do like this

  Add kernel option
  i915.alpha_support=1

  Target Release:19.10
  Target Kernel: 5.2
  Target Mesa: 19.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1825940/+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 1815172] Re: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa

2019-08-29 Thread Chris Halse Rogers
Hello Alkis, or anyone else affected,

Accepted mesa into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/19.0.8-0ubuntu0~18.04.2 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 and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

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

** Changed in: mesa (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

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

Title:
  [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Won't Fix
Status in mesa source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Several schools reported black screens after normally updating their Ubuntu 
boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

  This is caused by mesa assuming that soft-pinning on GEN8+ is working
  since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So
  a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT
  sizes/pin flags, but that's left for future.

  [Test case]
  install fixed mesa or kernel, check that the regression is fixed

  [Regression potential]
  mesa: shouldn't be any, it just reverts the change to always soft-pin
  (TODO kernel: adds commits from upstream stable, which have been well tested 
upstream by now)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1815172/+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 1845317] Re: Add new pci-id's for CML-S, ICL

2019-10-02 Thread Chris Halse Rogers
Hello Timo, or anyone else affected,

Accepted mesa into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/19.0.8-0ubuntu0~18.04.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 and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

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

** Changed in: mesa (Ubuntu Bionic)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  Add new pci-id's for CML-S, ICL

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in libdrm source package in Bionic:
  New
Status in linux source package in Bionic:
  Won't Fix
Status in linux-oem-osp1 source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Comet Lake (CML) is basically same gen9 GPU as Sky Lake (SKL) (as is KBL, 
CFL, WHL). There are new CML-S desktop cpu's on the way, and they add three new 
pci-id's that need to be added across the stack in order to use the GPU 
properly.

  There's also one ICL pci-id which was added recently (not in 5.3).

  [Test case]
  The proper way to test is to have an actual machine and boot it up with the 
updated stack, but since these are just pci-id's with no regression potential 
on older hw, it should be fine to just accept them.

  [Regression potential]
  None, just adds new pci-id's to allow the new GPUs to load the proper drivers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1845317/+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 1956855] Update Released

2022-03-01 Thread Chris Halse Rogers
The verification of the Stable Release Update for alsa-ucm-conf has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [SRU] alsa-ucm-conf: Add Realtek 4050 USB Codec profile for a Dell
  machine

Status in HWE Next:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Impish:
  Fix Released
Status in alsa-ucm-conf source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  This Dell machine has dual Realtek 4050 USB Codecs as front and rear codec, 
the front codec has speaker and headset, the rear codec has line-out audio 
jack. Without UCM, the pulseaudio can't detect this two usb audio codec and the 
audio can't work at all.

  [Fix]
  Backport a upstream patch, the patch adds the front and rear profiles in the 
ucm, then pulseaudio will enable all audio devices in this machine.

  [Test]
  booting with patched ucm, open the gnome-sound-setting, we could see usb 
speaker, usb headset and usb lineout, play sound to speaker, headset and 
lineout, all worked well, record sound via headset, it could record the sound 
correctly.

  [Where problems could occur]
  This SRU adds the new ucm files to a folder, in theory it will not introduce 
regressions, but It adds a file USB-Audio.conf, it could make other ucm conf 
files in the USB-Audio folder fail to parse, and make the P620 and WD15/19's 
audio fail to work, but this possibility is very low, we already tested it and 
no regression found so far.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1956855/+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 1940485] Re: thermald often limits CPU frequency while on AC

2022-03-07 Thread Chris Halse Rogers
Sorry about the late reply. I do not exactly know how to reproduce this
behaviour, so I've been consistently running upstream thermald and
collecting the logs while using the laptop normally.

Unfortunately, I have not observed this behaviour with the upstream
thermald, so I can't get the requested logs. It's possible that the
upstream code contains a fix for whatever my problem is?

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

Title:
  thermald often limits CPU frequency while on AC

Status in thermald package in Ubuntu:
  In Progress

Bug description:
  I'm not entirely sure if this is a thermald issue, but on my laptop
  (Dell XPS 15" 2-in-1) I find that the CPU frequency, under load on AC,
  is often throttled to 2.5GHz rather than the base 3.1GHz or 3.8GHz
  turbo frequency.

  Restarting thermald (with `systemctl restart thermald`) will let the
  system scale up to the expected ~3.8GHz boost frequency.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: thermald 2.4.6-1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 19 09:24:56 2021
  InstallationDate: Installed on 2021-06-26 (53 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
  SourcePackage: thermald
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1940485/+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 1940485] Re: thermald often limits CPU frequency while on AC

2022-03-07 Thread Chris Halse Rogers
I've been most recently running on git commit
2fc02bbf3a654c4e56fae51518f9983733ccd776, which would be slightly after
2.4.8.

I see that we've got a new thermald version (2.4.7) in the archive. I
shall re-enable the system thermald and see if I can still reproduce.

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

Title:
  thermald often limits CPU frequency while on AC

Status in thermald package in Ubuntu:
  In Progress

Bug description:
  I'm not entirely sure if this is a thermald issue, but on my laptop
  (Dell XPS 15" 2-in-1) I find that the CPU frequency, under load on AC,
  is often throttled to 2.5GHz rather than the base 3.1GHz or 3.8GHz
  turbo frequency.

  Restarting thermald (with `systemctl restart thermald`) will let the
  system scale up to the expected ~3.8GHz boost frequency.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: thermald 2.4.6-1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 19 09:24:56 2021
  InstallationDate: Installed on 2021-06-26 (53 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
  SourcePackage: thermald
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1940485/+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 1960933] Update Released

2022-03-08 Thread Chris Halse Rogers
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  rtw89_pci constantly drops connection with old firmware

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Impish:
  Fix Released

Bug description:
  [Impact]

  This was on a new Lenovo P14s Gen2 AMD. I'm using Ubuntu 21.10
  (impish)

  The current linux-firmware package (1.201.4+1.201.3) ships with
  realtek rtw89_pci firmware (/lib/firmware/rtw89/rtw8852a_fw.bin)
  version v0.13.8.0.

  My wifi chip wasn't able to keep a connection for more than a minute when 
connected to a Rodgers "Advanced Wi-Fi Modem". I searched around tried 
disabling the power_save and stuff. But that had little to no effect. I was 
about to open an issue on the upstream project and did a last ditch attempt to 
see if there were any firmware updates... I found linux-firmware.git and it had
  two newer versions!

   - v0.13.30.0 (was submitted in May 2021, but it took until october 2021 to 
show up)
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/rtw89/rtw8852a_fw.bin?id=ec17b637b7ab928ca7ebc0389e0e3921f1cc7d17

   - v0.13.33.0 (was submitted in November 2021 and got merged in December 
2021):
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/rtw89/rtw8852a_fw.bin?id=4a7e1f5cabaebe5c044b94b91149f35471d1e983

  I've downloaded and installed the latest "v0.13.33.0" on a whim and
  rebooted. And what a pleasant surprise: Instantly, my wifi connection
  lasted until the rest of the day.

  Could you please consider updating this realtek firmware in the next
  release? Thanks!

  [Test Case]

  See above.

  [Fix]

  Cherry pick two commit to match current Jammy:
  4a7e1f5cabae ("rtw89: 8852a: update fw to v0.13.33.0")
  ec17b637b7ab ("rtw89: 8852a: update fw to v0.13.30.0")

  [Where Problems Could Occur]

  Limited to wifi using RTL8852A HW.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1960933/+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 1958620] Re: Flickering white/black screen once KMS comes up

2022-03-25 Thread Chris Halse Rogers
Further investigation:
Affects:
1) 5.13.19 does not suffer from this bug
2) The Ubuntu 5.15 kernels, and mainline 5.16 and 5.17 kernels *do* suffer from 
this bug.

Also of note: this only occurs the *first* time KMS tries to come up on
the panel, and *only* if there is not a second monitor plugged in.
Having a second monitor plugged in at boot results in a successful boot,
*plugging in* a second monitor after triggering this bug results in
*both* displays  working fine, and *removing* a second monitor leaves
the laptop panel working.

It looks like maybe a bug has been introduced in framebuffer allocation?

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

Title:
  Flickering white/black screen once KMS comes up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This looks like a regression from the 5.13.0-20-generic kernel to the
  5.15.0-17-generic kernel. The display works fine under efifb, but as
  soon as the DRM drivers are loaded and KMS kicks in the display is
  replaced by black with flickering white (apparently when what would be
  on the output changes).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-17-generic 5.15.0-17.17
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  7134 F pipewire-media-
   /dev/snd/seq:chris  7133 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 21 17:07:08 2022
  InstallationDate: Installed on 2021-06-26 (208 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
  MachineType: Dell Inc. XPS 15 9575
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.204
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago)
  dmi.bios.date: 07/07/2019
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958620/+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 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up

2022-03-28 Thread Chris Halse Rogers
Confirmed, 6d7a793aabf31d7ba2b16fc13a94cc is bad, it's predecessor is
good.

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

Title:
  [Dell XPS 15 9575] Flickering white/black screen once KMS comes up

Status in linux package in Ubuntu:
  Triaged

Bug description:
  This looks like a regression from the 5.13.0-20-generic kernel to the
  5.15.0-17-generic kernel. The display works fine under efifb, but as
  soon as the DRM drivers are loaded and KMS kicks in the display is
  replaced by black with flickering white (apparently when what would be
  on the output changes).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-17-generic 5.15.0-17.17
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  7134 F pipewire-media-
   /dev/snd/seq:chris  7133 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 21 17:07:08 2022
  InstallationDate: Installed on 2021-06-26 (208 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
  MachineType: Dell Inc. XPS 15 9575
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.204
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago)
  dmi.bios.date: 07/07/2019
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958620/+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 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up

2022-03-29 Thread Chris Halse Rogers
I suspect this may have been fixed by
9ce5884e5139037445d0efcf37aeba21008011ad; I'm building an Ubuntu kernel
with that cherry-picked to test.

Hm. Although that seems to have been included in 5.16, and I *thought*
I'd verified that 5.16 exhibited the bug?

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

Title:
  [Dell XPS 15 9575] Flickering white/black screen once KMS comes up

Status in linux package in Ubuntu:
  Triaged

Bug description:
  This looks like a regression from the 5.13.0-20-generic kernel to the
  5.15.0-17-generic kernel. The display works fine under efifb, but as
  soon as the DRM drivers are loaded and KMS kicks in the display is
  replaced by black with flickering white (apparently when what would be
  on the output changes).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-17-generic 5.15.0-17.17
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  7134 F pipewire-media-
   /dev/snd/seq:chris  7133 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 21 17:07:08 2022
  InstallationDate: Installed on 2021-06-26 (208 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
  MachineType: Dell Inc. XPS 15 9575
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.204
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago)
  dmi.bios.date: 07/07/2019
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958620/+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 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up

2022-03-30 Thread Chris Halse Rogers
Nope. It looked like a good candidate, but isn't the fix.

5.17.1 fails, drm-tip succeeds, so the fix is somewhere between v5.17
and drm-tip. I'm (slowly) bisecting to find the commit that fixes it.

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

Title:
  [Dell XPS 15 9575] Flickering white/black screen once KMS comes up

Status in linux package in Ubuntu:
  Triaged

Bug description:
  This looks like a regression from the 5.13.0-20-generic kernel to the
  5.15.0-17-generic kernel. The display works fine under efifb, but as
  soon as the DRM drivers are loaded and KMS kicks in the display is
  replaced by black with flickering white (apparently when what would be
  on the output changes).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-17-generic 5.15.0-17.17
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  7134 F pipewire-media-
   /dev/snd/seq:chris  7133 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 21 17:07:08 2022
  InstallationDate: Installed on 2021-06-26 (208 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
  MachineType: Dell Inc. XPS 15 9575
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.204
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago)
  dmi.bios.date: 07/07/2019
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958620/+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 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up

2022-03-30 Thread Chris Halse Rogers
Thanks for that bisect.

Annoyingly, that commit doesn't cherry-pick cleanly onto 5.15, but I'll
see if I can munge it up to test.

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

Title:
  [Dell XPS 15 9575] Flickering white/black screen once KMS comes up

Status in linux package in Ubuntu:
  Triaged

Bug description:
  This looks like a regression from the 5.13.0-20-generic kernel to the
  5.15.0-17-generic kernel. The display works fine under efifb, but as
  soon as the DRM drivers are loaded and KMS kicks in the display is
  replaced by black with flickering white (apparently when what would be
  on the output changes).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-17-generic 5.15.0-17.17
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  7134 F pipewire-media-
   /dev/snd/seq:chris  7133 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 21 17:07:08 2022
  InstallationDate: Installed on 2021-06-26 (208 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
  MachineType: Dell Inc. XPS 15 9575
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.204
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago)
  dmi.bios.date: 07/07/2019
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958620/+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 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up

2022-03-31 Thread Chris Halse Rogers
Hm. That commit has too many dependencies to cherry-pick (or even
cherry-pick a small series) without significant conflicts. It might be
still possible to *understand* the patch and write an equivalent for
5.15.

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

Title:
  [Dell XPS 15 9575] Flickering white/black screen once KMS comes up

Status in linux package in Ubuntu:
  Triaged

Bug description:
  This looks like a regression from the 5.13.0-20-generic kernel to the
  5.15.0-17-generic kernel. The display works fine under efifb, but as
  soon as the DRM drivers are loaded and KMS kicks in the display is
  replaced by black with flickering white (apparently when what would be
  on the output changes).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-17-generic 5.15.0-17.17
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  7134 F pipewire-media-
   /dev/snd/seq:chris  7133 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 21 17:07:08 2022
  InstallationDate: Installed on 2021-06-26 (208 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
  MachineType: Dell Inc. XPS 15 9575
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.204
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago)
  dmi.bios.date: 07/07/2019
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958620/+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 1986852] Re: Support SMBIOS 3.4 and 3.5 in Jammy for Hardware Enablement

2022-08-30 Thread Chris Halse Rogers
Hello Mauricio, or anyone else affected,

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

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
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: dmidecode (Ubuntu Jammy)
   Status: Invalid => 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 dmidecode in Ubuntu.
https://bugs.launchpad.net/bugs/1986852

Title:
  Support SMBIOS 3.4 and 3.5 in Jammy for Hardware Enablement

Status in dmidecode package in Ubuntu:
  In Progress
Status in dmidecode source package in Jammy:
  Fix Committed
Status in dmidecode source package in Kinetic:
  In Progress

Bug description:
  [Impact]

   * Support the SMBIOS 3.4 and 3.5 specifications in Jammy
 to enable new hardware in LTS release per SRU policy [1].

   * Backport of 15 relatively simple patches from dmidecode 3.4
 in Kinetic to dmidecode 3.3 in Jammy (vs. 49 for full version).
   
   * Patches are detailed below.

  [Test Plan]

   * Check no regressions on current systems with SMBIOS < 3.4,
 i.e., no output changes in text and binary form.

  $ sudo dmidecode > old.txt 2>&1
  $ sudo dmidecode --dump-bin old.bin

  $ apt install dmidecode # modified package
 
  $ sudo dmidecode > new.txt 2>&1
  $ sudo dmidecode --dump-bin new.bin

  $ cmp old.txt new.txt; echo $?
  0

  $ cmp old.bin new.bin; echo $?
  0

   * Check for expected output on new systems with SMBIOS >= 3.4.
   
 $ diff old.txt new.txt
 ...
 < # SMBIOS implementations newer than version 3.3.0 are not
 < # fully supported by this version of dmidecode.
 ...
 < Unknown Type
 <   Header and Data:
 ...
 > Firmware Inventory Information
 >   Firmware Component Name: BMC Firmware
 ...
 <   Type: 
 ---
 >   Type: DDR5
 ...
 <   Upgrade: 
 ---
 >   Upgrade: Socket LGA4677
 ...
 < Unknown Type
 <   Header and Data:
 ...
 > Firmware Inventory Information
 >   Firmware Component Name: BIOS Firmware
   
   * Possibly perform synthetic testing with crafted C structures.
   
  [Where problems could occur]

   * Mostly the patches add support for new bits/codes/strings,
 so there's no changes expected for the old spec support,
 but some patches lightly change things a little bit (but
 only one should change a string, as far as I could tell).

   * So, theoretically, parsers that expect a very precise
 and constant format/string might have issues *in case*
 the changes introduced any. (But such tools maybe are
 already using the binary form anyway, for more detail.)

  [Other info]

* No additional fixes upstream to the included patches.
  (The git repo's commits have the 'Fixes:' tag usage.)
  There's only 2 more commits after dmidecode-3-4 now.
  
  [Original Description]

  Backport the support for SMBIOS 3.4 and 3.5 specifications
  in Ubuntu Kinetic (dmidecode 3.4) to Jammy (dmidecode 3.3)
  to enable new hardware in the LTS release per SRU policy [1].

  [1] https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases

  [Patchset Details]

  Patches 1-8,10-11 are for SMBIOS 3.4;
  Patches 9,12-14 are for SMBIOS 3.5;
  Patch 15 updates supported version.

  01: SMBIOS 3.4: add new codes/strings for memory device type
  02: SMBIOS 3.4: add new codes/strings for processor socket
  03: SMBIOS 3.4: add new codes/strings for slot characteristics
  04: SMBIOS 3.4: add new codes/strings for memory device speed [string 
backward-compatible changes]
  05: SMBIOS 3.4: add new codes/strings for slot types [changes append '(U.2)' 
to 'PCI Express {2,3} SFF-8639' per spec]
  06: SMBIOS 3.4: add new codes/strings for processor characteristics
  07: SMBIOS 3

[Kernel-packages] [Bug 1936009] Update Released

2021-08-11 Thread Chris Halse Rogers
The verification of the Stable Release Update for alsa-ucm-conf has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [SRU] The internal mic of Dell Precision 5750 can't record sound

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Hirsute:
  Fix Committed
Status in alsa-ucm-conf source package in Impish:
  Fix Released

Bug description:
  [Impact]
  After upgrade the linux kernel, the mixer names of rt715 is changed, the 
current alsa-ucm-conf will fail to initialize that codec, then users can't 
record sound from internal mic since the internal mic is routed to the codec 
rt715.

  [Fix]
  Backport 3 upstream commits, after applying these 3 commits, the ucm conf 
file dosn't initialize the codec with hardcoded mixer names anymore, it will 
check the existence of the mixer name first, then conditionally initialize the 
codec.

  [Test]
  run 'alsactl init 1' on the precision 5750 with old and new kernel, there is 
no error logs, use the internal mic to record sound, it could record 
successfully.

  [Where problems will occur]
  The change only affects the rt715 codec, so far, that codec only connects to 
the internal mic on Dell soundwire audio machines, so it could introduce 
regression on the internal mic like users can't record sound via internal mic 
anymore on the Dell soundwire audio machines. But this possibility is very low 
since we already tested these 3 commits on different Dell soundwire audio 
machines (latitude and precision). We tested it with old kernel and new kernel, 
all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1936009/+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 1940485] [NEW] thermald often limits CPU frequency while on AC

2021-08-18 Thread Chris Halse Rogers
Public bug reported:

I'm not entirely sure if this is a thermald issue, but on my laptop
(Dell XPS 15" 2-in-1) I find that the CPU frequency, under load on AC,
is often throttled to 2.5GHz rather than the base 3.1GHz or 3.8GHz turbo
frequency.

Restarting thermald (with `systemctl restart thermald`) will let the
system scale up to the expected ~3.8GHz boost frequency.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: thermald 2.4.6-1
ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
Uname: Linux 5.11.0-20-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu67
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 19 09:24:56 2021
InstallationDate: Installed on 2021-06-26 (53 days ago)
InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
SourcePackage: thermald
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  thermald often limits CPU frequency while on AC

Status in thermald package in Ubuntu:
  New

Bug description:
  I'm not entirely sure if this is a thermald issue, but on my laptop
  (Dell XPS 15" 2-in-1) I find that the CPU frequency, under load on AC,
  is often throttled to 2.5GHz rather than the base 3.1GHz or 3.8GHz
  turbo frequency.

  Restarting thermald (with `systemctl restart thermald`) will let the
  system scale up to the expected ~3.8GHz boost frequency.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: thermald 2.4.6-1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 19 09:24:56 2021
  InstallationDate: Installed on 2021-06-26 (53 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
  SourcePackage: thermald
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1940485/+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 1940485] Re: thermald often limits CPU frequency while on AC

2021-08-29 Thread Chris Halse Rogers
Still occurs on current impish:

mir on  explicit-platform-interfaces [$!?] 
at 13:09:42 ❯ thermald --version
2.4.6

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

Title:
  thermald often limits CPU frequency while on AC

Status in thermald package in Ubuntu:
  Incomplete

Bug description:
  I'm not entirely sure if this is a thermald issue, but on my laptop
  (Dell XPS 15" 2-in-1) I find that the CPU frequency, under load on AC,
  is often throttled to 2.5GHz rather than the base 3.1GHz or 3.8GHz
  turbo frequency.

  Restarting thermald (with `systemctl restart thermald`) will let the
  system scale up to the expected ~3.8GHz boost frequency.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: thermald 2.4.6-1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 19 09:24:56 2021
  InstallationDate: Installed on 2021-06-26 (53 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
  SourcePackage: thermald
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1940485/+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 1988836] Re: Enable the open NVIDIA kernel modules

2022-09-27 Thread Chris Halse Rogers
Hello Alberto, or anyone else affected,

Accepted nvidia-graphics-drivers-515 into focal-proposed. The package
will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-515/515.65.01-0ubuntu0.20.04.2 in a few hours, and then in the
-proposed repository.

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

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

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

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

** Changed in: nvidia-graphics-drivers-515 (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

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

Title:
  Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Committed
Status in ubuntu-drivers-common source package in Focal:
  In Progress
Status in linux-restricted-modules source package in Jammy:
  In Progress
Status in nvidia-graphics-drivers-515 source package in Jammy:
  In Progress
Status in ubuntu-drivers-common source package in Jammy:
  In Progress

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

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

2022-10-18 Thread Chris Halse Rogers
Ok.

Sorry for the delay in getting to this.

There's a lot of code churn between 2.4.9 in Jammy and the 2.5 release,
a bunch of which appears to be refactoring rather than straight bugfixes
or new hardware support. It also appears to drop support for setting
something(?) via a msr and will instead complain about needing a newer
kernel - is the Jammy kernel new enough to avoid that codepath?

What effort has been made to cherry-pick the necessary fixes for these
bugs?

This is not a "no", but since there's a fair amount of code churn here I
think we need a more holistic test plan - how can we ensure that these
changes don't break existing systems? Would it be less work overall to
cherry-pick only the necessary fixes and need less thorough testing?

-- 
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:
  In Progress

Bug description:
  [Impact]
   * thermald prematurely throttling GPU

  [Test Plan]
   * Run game on the target machine.
   * the FPS must not be throttled below 20FPS.

  [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

2022-10-18 Thread Chris Halse Rogers
I'm just surprised that "make passive policy 1 default" isn't a cleanly
cherry-pickable thing. That *sounds* like it should be one line of code
:)

Unless it first needs to implement support for "passive policy 1", which
it may well need to! But I don't know that unless someone tells me :)

Since the churn *is* necessary, then we should organise testing on a
wide variety of laptops - both ones which are expected to have bugs
fixed by this upload, and ones which aren't expected to be affected by
this upload. The CI lab should have a reasonable selection; what sort of
automated testing can be done for this?

-- 
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:
  In Progress

Bug description:
  [Impact]
   * thermald prematurely throttling GPU

  [Test Plan]
   * Run game on the target machine.
   * the FPS must not be throttled below 20FPS.

  [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

2022-10-23 Thread Chris Halse Rogers
When upstream mixes bugfixes and refactorings, SRUs are a balance between:
*) The exact upstream code has *probably* been tested more, so is probably safer
*) The minimal fix changes behaviour less, so is probably safer

Since *both* options are "probably safer", it mostly depends on what
"the minimal fix" looks like. If the minimal fix looks sensible, we'll
generally prefer it even if it's not a direct cherry-pick from upstream.

Here it looks like maybe the minimal fix *is* sensible? Could you
confidently generate a package that fixes these bugs but doesn't include
all the refactorings?

-- 
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:
  In Progress

Bug description:
  [Impact]
   * thermald prematurely throttling GPU

  [Test Plan]
   * Run game on the target machine.
   * the FPS must not be throttled below 20FPS.

  [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

2022-10-24 Thread Chris Halse Rogers
Ok, so we're back to:

Since the churn *is* necessary, then we should organise testing on a
wide variety of systems - both ones which are expected to have bugs
fixed by this upload, and ones which aren't expected to be affected by
this upload. The CI lab should have a reasonable selection; what sort of
automated testing can be done for this?

-- 
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:
  In Progress

Bug description:
  [Impact]
   * thermald prematurely throttling GPU

  [Test Plan]
   * Run game on the target machine.
   * the FPS must not be throttled below 20FPS.

  [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 1992435] Update Released

2022-10-24 Thread Chris Halse Rogers
The verification of the Stable Release Update for alsa-ucm-conf has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  sof-hda-dsp Dmic0 not initial correctly

Status in OEM Priority Project:
  Confirmed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  Device use sof-hda-dsp driver will not able to initial the Dmic0 status 
correctly

  [Test Plan]
  1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service"
  2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state"
  3. reboot system
  4. Dmic should be on and volume set to 70%

  [Where problems could occur]
  Only fix for Dmic0 control and upstream already merged the code. The risk 
will be low

  [Other Info]
  Pull Request in upstream 
https://github.com/alsa-project/alsa-ucm-conf/pull/132

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1992435/+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 1958620] [NEW] Flickering white/black screen once KMS comes up

2022-01-20 Thread Chris Halse Rogers
Public bug reported:

This looks like a regression from the 5.13.0-20-generic kernel to the
5.15.0-17-generic kernel. The display works fine under efifb, but as
soon as the DRM drivers are loaded and KMS kicks in the display is
replaced by black with flickering white (apparently when what would be
on the output changes).

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-17-generic 5.15.0-17.17
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu75
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  chris  7134 F pipewire-media-
 /dev/snd/seq:chris  7133 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 21 17:07:08 2022
InstallationDate: Installed on 2021-06-26 (208 days ago)
InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
MachineType: Dell Inc. XPS 15 9575
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.13.0-20-generic N/A
 linux-backports-modules-5.13.0-20-generic  N/A
 linux-firmware 1.204
SourcePackage: linux
UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago)
dmi.bios.date: 07/07/2019
dmi.bios.release: 1.7
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.7.1
dmi.board.name: 0C32VW
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9575
dmi.product.sku: 080D
dmi.sys.vendor: Dell Inc.

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


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

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

Title:
  Flickering white/black screen once KMS comes up

Status in linux package in Ubuntu:
  New

Bug description:
  This looks like a regression from the 5.13.0-20-generic kernel to the
  5.15.0-17-generic kernel. The display works fine under efifb, but as
  soon as the DRM drivers are loaded and KMS kicks in the display is
  replaced by black with flickering white (apparently when what would be
  on the output changes).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-17-generic 5.15.0-17.17
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  7134 F pipewire-media-
   /dev/snd/seq:chris  7133 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 21 17:07:08 2022
  InstallationDate: Installed on 2021-06-26 (208 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
  MachineType: Dell Inc. XPS 15 9575
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.204
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago)
  dmi.bios.date: 07/07/2019
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958620/+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 1942181] Re: Add support for AlderLake CPUs

2021-09-28 Thread Chris Halse Rogers
Hello Colin, or anyone else affected,

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

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

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

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

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

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

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

Title:
  Add support for AlderLake CPUs

Status in OEM Priority Project:
  Fix Released
Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Focal:
  Fix Released
Status in thermald source package in Hirsute:
  Fix Committed
Status in thermald source package in Impish:
  Fix Released

Bug description:
  [Impact]

   * Support thermald on AlderLake CPUs.

  [Test Plan]

   * Use a machine with a AlderLake CPUs
   * systemctl status thermald
   * Status of thermald should be `running`

  [Where problems could occur]

   * This change is to support Jasper Lake in thermald, which won't
  impact other hardware because the changes match on the CPU model ID.

  [Other Info]

  Supported added with:
   * 
https://github.com/intel/thermal_daemon/commit/ffb226c62d3bc052f47970be9802254e48799bf4
   * 
https://github.com/intel/thermal_daemon/commit/d0c9e7fb5aea85b84841eba927feb8767765fda2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1942181/+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 1945227] Re: drm/amdgpu: Add support for Yellow Carp

2021-09-28 Thread Chris Halse Rogers
Hello Timo, or anyone else affected,

Accepted mesa into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/21.0.3-0ubuntu0.3~20.04.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-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

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

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

** Changed in: mesa (Ubuntu Focal)
   Status: New => Fix Committed

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

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

Title:
  drm/amdgpu: Add support for Yellow Carp

Status in linux-firmware package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  New
Status in mesa source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  New hardware support for AMD's Yellow Carp need five commits
  backported to mesa and new firmware. This is only needed on focal,
  skipping hirsute/impish (no kernel support there).

  [Test plan]

  Install updates, boot a YC machine and check that the desktop has full
  hardware acceleration.

  [Where problems could occur]

  The firmware is new, so it will simply add new files to l-f without
  any impact on others.

  Mesa adds five commits in total, and while some affect other chips,
  they mostly fix hw bugs or add a helper and such, hard to see what
  could go wrong.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945227/+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 1945565] Update Released

2021-10-12 Thread Chris Halse Rogers
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [SRU] Revert amdgpu/renoir firmware

Status in OEM Priority Project:
  New
Status in linux-firmware package in Ubuntu:
  Won't Fix
Status in linux-firmware source package in Focal:
  Fix Released

Bug description:
  [Impact]
  The USB-type-C port is useless when uplug the USB-type-C <-> DP/HDMI/VGA 
Dongle after the system resumed from S3.

  [Fix]
  Revert below change, this issue is gone.

  commit a543b9c1bfd12e60d962acd48108234481a8581f
  Author: Alex Deucher 
  Date:   Thu Jul 1 12:23:11 2021 +0800

  amdgpu: update renoir firmware from 21.20

  BugLink: https://bugs.launchpad.net/bugs/1934014

  From internal git commit:
  8b05e03570818d047d7ea0a7388c89c4192fd20b

  Signed-off-by: Alex Deucher 
  Signed-off-by: Josh Boyer 
  (backported from commit 56ef642160203f8be7e1334feca4a76852c74bc0)
  [khfeng: Squashed multiple updates into one commit]
  Signed-off-by: Kai-Heng Feng 
  Signed-off-by: Timo Aaltonen 

  [Test]
  Verify S3 on renoir's platforms.

  [Where problems could occur]
  Renoir based systems can't resume from s2idle.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1945565/+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 1945227] Update Released

2021-10-12 Thread Chris Halse Rogers
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  drm/amdgpu: Add support for Yellow Carp

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  Fix Released
Status in mesa source package in Focal:
  Fix Released

Bug description:
  [Impact]

  New hardware support for AMD's Yellow Carp need five commits
  backported to mesa and new firmware. This is only needed on focal,
  skipping hirsute (no kernel support there).

  [Test plan]

  Install updates, boot a YC machine and check that the desktop has full
  hardware acceleration.

  [Where problems could occur]

  The firmware is new, so it will simply add new files to l-f without
  any impact on others.

  Mesa adds five commits in total, and while some affect other chips,
  they mostly fix hw bugs or add a helper and such, hard to see what
  could go wrong.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945227/+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 1945438] Update Released

2021-10-12 Thread Chris Halse Rogers
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Update ADL-P dmc firmware

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  It's reported that 2.12 fixes some issues with DC6 power saving state
  on ADL-P

  [Test case]

  With a suitable kernel (oem-5.14 which knows about this fw version)
  test that DC6 power state works without issues.

  [Where things could go wrong]

  Using this version needs kernel support, so it does not affect other
  systems than Alder Lake P.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945438/+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 1933938] Update Released

2021-10-12 Thread Chris Halse Rogers
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Missing CNVi firmware for Intel AX211/AX201/9560/9462 on ADL-S/ADL-P

Status in HWE Next:
  New
Status in intel:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-oem-5.13 source package in Focal:
  In Progress
Status in linux-oem-5.14 source package in Focal:
  In Progress
Status in linux source package in Impish:
  In Progress
Status in linux-firmware source package in Impish:
  Fix Released
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid

Bug description:
  [SRU Justfication]

  [Impact]

  Intel CNVi moves key elements of Wi-Fi and Bluetooth Technology into
  Intel processors. As a result, their driver may have to be revised
  across processor generations.

  [Fix]

  This depends on a few changes set to address all issues on supporting:
  * PCI [8086:7af0] Subsystem [8086:4090] (AX211)
    * WiFi: iwlwifi-so-a0-gf-a0-*
    * BT: intel/ibt-1040-0041.* (ADL-S)
    * BT: intel/ibt-0040-0041.* (ADL-P)
  * PCI [8086:7af0] Subsystem [8086:4070] (AX201)
    * WiFi: iwlwifi-so-a0-hr-b0-*
    * BT: intel/ibt-1040-4150.*
    * BT: intel/ibt-0040-4150.*
  * PCI [8086:7af0] Subsystem [8086:0aaa] (9462)
    * WiFi: iwlwifi-so-a0-jf-b0-*
    * BT: intel/ibt-1040-1020.*

  AX201 wifi firmware for ADL platforms will be available with FW
  API >= 64, so a patchset "iwlwifi: bump FW API to 64 for AX devices"
  will be required. Depending fixes are pulled as well.

  For reset of them, 3 additional commits for iwlwifi, also in mainline
  now, are required.

  The last patch for 9462 Bluetooth is still under review at the time of
  writing. This is the only patch that is not yet in unstable.

  [Test Case]

  Install these CRF on ADL-S/ADL-P platforms and check if WiFi/Bluetooth
  is working.

  [Where problems could occur]

  While this is a new generation, we may have common issues like power
  consumption, network throughput, suspend/resume issues.

  [Other Info]

  Intel is to release the corresponding firmware blobs next week. These
  are verified with pre-released firmware.

  == original bug report ==

  * PCI [8086:7af0] Subsystem [8086:4090] (AX211)
    * WiFi: iwlwifi-so-a0-gf-a0-*
    * BT: intel/ibt-1040-0041.sfi
  * PCI [8086:7af0] Subsystem [8086:4070] (AX201)
    * WiFi: iwlwifi-so-a0-hr-b0-*
    * BT: ibt-1040-4150.sfi
  * PCI [8086:7af0] Subsystem [8086:0264] (9462)
    * WiFi: iwlwifi-so-a0-jf-b0-*
    * BT: intel/ibt-1040-1020.*
* BT: intel/ibt-0040-1020.*

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1933938/+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 1944417] Update Released

2021-10-12 Thread Chris Halse Rogers
The verification of the Stable Release Update for zfs-linux has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Add support for 5.14

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Focal:
  Invalid
Status in zfs-linux source package in Hirsute:
  Fix Released

Bug description:
  == SRU Hirsute ==

  [Impact]

  Add support for 5.14 kernels in Hirsute for zfs-linux dkms module.
  zfs-linux needs  compat changes in order to build against 5.14 kernel
  like oem-5.14 in focal:

  - Linux-5.12-compat-bio-bi_disk-member-moved.patch
  - Linux-5.12-compat-replace-bio_-_io_acct-with-disk_-_.patch
  - Linux-5.12-compat-idmapped-mounts.patch
  - Linux-5.12-update-bio_max_segs-replaces-BIO_MAX_PAGE.patch
  - Remove-iov_iter_advance-for-iter_write.patch
  - linux-5.13-compat-bdevops-revalidate_disk-removed.patch
  - Linux-5.14-compat-blk_alloc_disk.patch
  - Linux-5.14-compat-explicity-assign-set_page_dirty.patch
  - Linux-5.14-compat-META.patch

  [Test Plan]

  Run the ubuntu ZFS regressions tests, these cover smoke testing core
  functionality, POSIX fs semantics, subset of xfs tests and all mount
  options with file system stress-ng stress tests.

  see git://kernel.ubuntu.com/ubuntu/autotest-client/tests/ubuntu_zfs*
  tests

  [Where problems could occur]

  in BIO and block allocation layers in ZFS. These are exercised
  extensively by the ZFS regression tests.

  The 5.12..5.14 compat options are dkms build time config checks, so
  build testing the zfs-dkms package with 5.11 and 5.14 kernels will
  ensure these dkms build-time options are exercised.

  [Other Info]

  These Linux 5.12..5.14 compat patches are in Ubuntu impish and have
  had some testing already, so the regression potential is low as these
  code paths have already had some exposure to real work loads.

  Tested on x86-64 with 5.11 and 5.14 kernels to exercise the build-time
  dkms config kernel detection paths. Exercised with the ubuntu zfs
  regression tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1944417/+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 1981922] Update Released

2022-08-02 Thread Chris Halse Rogers
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Upgrade yellow carp DMCUB firmware to fix suspend failure

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  Fix Committed
Status in linux-firmware source package in Impish:
  Won't Fix
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  Certain Rembrandt designs use LPDDR memory and current firmware in 
linux-firmware package in Focal and Jammy has a failure resuming from s0i3 on 
DC power with it.

  Some sample designs affected by the failure are Thinkpad X13, Z13,
  Z16.

  This failure doesn't affect resume with AC power or designs without
  LPDDR memory.

  [Fix]
  Upgrade yellow carp DMCUB firmware binary.

  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git/commit/?id=4458bb4185b6d6e1f5c586fcf4b8cf6f5d3c8e24

  [Test]
  Verify suspend/resume works.
  Verify that externally plugged displays haven't regressed.

  [Where problems could occur]
  Firmware is only loaded to Rembrandt designs.  Regressions would be tied to 
those platforms.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1981922/+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 1763823] Update Released

2018-05-15 Thread Chris Halse Rogers
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Update firmware for 18.04 hwe kernel

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Xenial:
  Fix Released

Bug description:
  SRU Justification

  Impact: A 4.15-based hwe-edge kernel has been introduced into xenial.
  However some of the firmware files it requires are missing from
  xenial's linux-firmware, rendering the relevant hardware inoperable.

  Fix: Add the missing firmware files.

  Regression Potential: Most of these files will not be used by the
  existing kernels in xenial. A few may be, and while regressions are
  not expected it's possible that new firmware versions might introduce
  regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1763823/+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 1753439] Update Released

2018-05-15 Thread Chris Halse Rogers
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Redpine: BLE scanning for nearby beacons per second is too low and
  result high loss rate.

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Confirmed
Status in linux-firmware source package in Bionic:
  Invalid

Bug description:
  SRU Justification

  Impact: BLE scanning for nearby beacons per second is too low and
  result high loss rate.

  Fix: Updated firmware.

  Test Case: Test on affected hardware using instructions below.

  Regression Potential: Limited to specific hardware.

  ---

  Steps to replicate the issue:

  1. Power on the BT device, then change the terminal by "Ctil+F1" or open 
another putty to ssh SUT.
  2.Use command below to discover BLE device.
  $ sudo stdbuf -i0-o0 -e0 /snap/bluez/current/usr/bin/hcitool lescan 
--duplicates --passive | perl -nle 'print scalar(localtime), " ",$_'
  3. log as attachment.

  This bug is for tracking purposes only, do not triage.

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

2018-05-15 Thread Chris Halse Rogers
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Update Qualcomm QCA6174-HMC (DW1820) to comply with CE-RED (Radio
  Emissions Directive)

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Released

Bug description:
  SRU Justification

  Impact: New ath10k firmware is needed for compliance with CE-RED.

  Fix: Updated firmware files.

  Regression Potential: This update has been in upstream linux-firmware
  for a while now. While regressions are possible, the firmware should
  have seen a lot of use by now.

  ---

  To comply with CE-RED (Radio Emissions Directive),
  ath10k/QCA6174/hw3.0/board-2.bin and
  ath10k/QCA6174/hw3.0/firmware-6.bin have to be updated.

  The commits are:

  commit 1d1dd4be21cde408b0fb12774d477293bc8d4cc2
  Author: Kalle Valo 
  AuthorDate: Thu Feb 15 15:10:51 2018 +0200
  Commit: Kalle Valo 
  CommitDate: Thu Feb 15 15:10:51 2018 +0200

  ath10k: QCA6174 hw3.0: update board-2.bin

  Signed-off-by: Kalle Valo 

  commit 6f1d3b7cfeef426f3c3d79bf916e3bef8f82a3dc
  Author: Kalle Valo 
  AuthorDate: Thu Feb 15 15:10:51 2018 +0200
  Commit: Kalle Valo 
  CommitDate: Thu Feb 15 15:10:51 2018 +0200

  ath10k: QCA6174 hw3.0: update firmware-6.bin to
  WLAN.RM.4.4.1-00079-QCARMSWPZ-1

  Signed-off-by: Kalle Valo 

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1752044/+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 1757443] Update Released

2018-05-15 Thread Chris Halse Rogers
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Redpine: BLE radio lost issue

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Triaged
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Incomplete
Status in linux-firmware source package in Bionic:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Radio stops capturing advertisements after several hours.

  Fix: Updated firmware.

  Test Case: See below.

  Regression Potential: Limited to specific hardware.

  ---

  Below are the steps to replicate the issue

  We are doing continuous BLE scanning and monitoring the advertisements
  from reference device. After long periods of capture (several hours),
  the radio stops capturing advertisements and won't start again until
  we power cycle the box or manually unload/load the module via modprobe

  This bug is for tracking purposes only, please don't triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757443/+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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2020-09-08 Thread Chris Halse Rogers
Hello Martin, or anyone else affected,

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

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

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

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

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

** Changed in: gdm3 (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

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

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in OEM Priority Project:
  In Progress
Status in gdm3 package in Ubuntu:
  Fix Released
Status in gnome-session package in Ubuntu:
  Invalid
Status in grub2 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Invalid
Status in gdm3 source package in Focal:
  Fix Committed
Status in gnome-session source package in Focal:
  Invalid
Status in grub2 source package in Focal:
  Invalid
Status in nvidia-graphics-drivers-390 source package in Focal:
  Invalid
Status in nvidia-graphics-drivers-430 source package in Focal:
  Invalid
Status in nvidia-graphics-drivers-435 source package in Focal:
  Invalid
Status in nvidia-graphics-drivers-440 source package in Focal:
  Invalid

Bug description:
  [ Impact ]
  In some platforms with specific Nvidia cards (with nvidia-driver-440), enable 
auto-login (either during installation or after installation) will fail (either 
stuck in gdm login screen and not able to login even typing correct password).

  [ Test Case ]
  Here are two scenario of auto login with groovy (20.10) daily build[1]:

  1) Checked "Install third-party software" (e.g. nvidia-driver) with
  enabling "Login automatically" during installation.

  2) Install groovy daily build with default options, after installation 
completed:
  2.1) Install nvidia-driver-440 (450.66-0ubuntu1) from ubuntu-archive.
  2.2) Enable "Login automatically" from system settings.

  Then reboot.

  [Expected result]
  System will boot into desktop environment without the login page.

  [Actual result]
  System boots to login page, and can't login to desktop environment with the 
correct password.

  [ Regression potential ]
  Medium, the patch comes from upstream[2] to use /dev/tty1 (instead of tty0) 
to prevent the auto-login user gets tty1. I did verified gdm3 from my PPA[3] 
and it works good. It passed the 30 times reboot stress test by using 
stress/reboot_30 from checkbox.

  [1] sha256sum: 
bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822
  [2] https://gitlab.gnome.org/GNOME/gdm/-/commit/f843233ad4 
https://gitlab.gnome.org/GNOME/gdm/-/commit/690b3c01
  [3] https://launchpad.net/~os369510/+archive/ubuntu/gdm3-1845801

  ---

  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic

[Kernel-packages] [Bug 1893004] Re: [SRU]alsa-ucm-conf: the volume can't be adjusted on the usb audio of the Dell WD15/WD19 dock

2020-09-14 Thread Chris Halse Rogers
Hello Hui, or anyone else affected,

Accepted alsa-ucm-conf into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.2-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-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

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

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

** Changed in: alsa-ucm-conf (Ubuntu Focal)
   Status: Confirmed => Fix Committed

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

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

Title:
  [SRU]alsa-ucm-conf: the volume can't be adjusted on the usb audio of
  the Dell WD15/WD19 dock

Status in HWE Next:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  On the Dell WD15/19 Dock station, there is a USB audio card, and
  a headset audio jack routes to this audio card. We found if we plug
  some specific headset (non-iphone type headset), we could not record
  any sound from headset-mic even we set the input volume to max.

  [Fix]
  Improve the ucm for the audio card in this Dock, let the driver mixer
  value be adjustable, then we could adjust the input volume from driver
  side. 

  [Test Case]
  plug various types of headset to the WD19 and WD15 dock stations, and
  adjust the input volume from gnome, check the input volume in the driver
  by running amixer, found the input volume is changed in the driver;
  record the sound from headset-mic, it could record the sound from all
  headsets we tested.

  [Regression Risk]
  It could make the PA fail to load the ucm on the machines with Dell
  WD15/WD19 dock station, then users only see analogue output/input from
  gnome-control-center instead of usb-speaks usb-lineout and usb-mic.
  But this possibility is very low since we have tested the patch on WD15
  and WD19 dock, all worked very well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1893004/+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 1881107] Re: zfs: backport AES-GCM performance accelleration

2020-06-02 Thread Chris Halse Rogers
Do we have the tests run on hardware that does not support the relevant
instructions, in addition to running them on CPUs with the AES
instructions?

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

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

Title:
  zfs: backport AES-GCM performance accelleration

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Focal:
  Fix Committed
Status in zfs-linux source package in Groovy:
  Fix Released

Bug description:
  == SRU Justification ==

  Upstream commit 31b160f0a6c673c8f926233af2ed6d5354808393 contains AES-
  GCM acceleration changes that significantly improve encrypted
  performance.

  Tests on a memory backed pool show performance improvements of ~15-22%
  for AES-CCM writes, ~17-20% AES-CCM reads, 34-36% AES-GCM writes and
  ~79-80% AES-GCM reads on a Sandybridge x86-64 CPU, so this looks like
  a promising optimization that will benefit a lot of users.

  == The fix ==

  Backport of upstream 31b160f0a6c673c8f926233af2ed6d5354808393 - this
  is already backported in Groovy ZFS 0.8.3-1ubuntu13

  == Test case ==

  Run ZFS performance tests from ubuntu_performance_zfs_encryption
  ubuntu kernel team autotests. With the fix the encryption runs
  significantly faster, as noted earlier in the SRU justification.

  Also test with the 4 types of ZFS ubuntu autotests, should not fail
  any of these.

  == Regression Potential ==

  This fix alters the crypto engine and adds in new optimizations for
  CPUs that have capable instruction sets.  There is a risk that this
  new crypto code is erroneous.

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

2020-06-02 Thread Chris Halse Rogers
Hello Colin, or anyone else affected,

Accepted zfs-linux into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/zfs-
linux/0.8.3-1ubuntu12.1 in a few hours, and then in the -proposed
repository.

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

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

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

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

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

Title:
  zfs: backport AES-GCM performance accelleration

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Focal:
  Fix Committed
Status in zfs-linux source package in Groovy:
  Fix Released

Bug description:
  == SRU Justification ==

  Upstream commit 31b160f0a6c673c8f926233af2ed6d5354808393 contains AES-
  GCM acceleration changes that significantly improve encrypted
  performance.

  Tests on a memory backed pool show performance improvements of ~15-22%
  for AES-CCM writes, ~17-20% AES-CCM reads, 34-36% AES-GCM writes and
  ~79-80% AES-GCM reads on a Sandybridge x86-64 CPU, so this looks like
  a promising optimization that will benefit a lot of users.

  == The fix ==

  Backport of upstream 31b160f0a6c673c8f926233af2ed6d5354808393 - this
  is already backported in Groovy ZFS 0.8.3-1ubuntu13

  == Test case ==

  Run ZFS performance tests from ubuntu_performance_zfs_encryption
  ubuntu kernel team autotests. With the fix the encryption runs
  significantly faster, as noted earlier in the SRU justification.

  Also test with the 4 types of ZFS ubuntu autotests, should not fail
  any of these.

  == Regression Potential ==

  This fix alters the crypto engine and adds in new optimizations for
  CPUs that have capable instruction sets.  There is a risk that this
  new crypto code is erroneous.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1881107/+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 1874698] Update Released

2020-06-16 Thread Chris Halse Rogers
The verification of the Stable Release Update for alsa-ucm-conf has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left]
  Recording problem

Status in HWE Next:
  New
Status in OEM Priority Project:
  Fix Committed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in alsa-ucm-conf source package in Focal:
  Fix Released
Status in linux source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Groovy:
  Fix Released

Bug description:
  This is for alsa-ucm-conf:

  The patches are already in the mainline alsa-ucm-conf, so only
  sent the SRU for focal

  [Impact]
  On the machines without Intel HDMI, the sof driver will fail to initialize.

  [Fix]
  After fixing the kernel, we also need to change the ucm2 to make it
  support the machine without Intel hdmi audio.

  [Test Case]
  Boot the kernel on the machines without Intel HDMI audio, everything
  works well including the audio.

  [Regression Risk]
  Low, these 2 patches are already in the mainline alsa-ucm-conf. And we
  already tested them on 4 HP machines.

  
  This is for linux kernel:

  The patch is already in the oem-5.6 kernel and unstable kernel, so only
  sent the SRU for focal

  [Impact]
  On the machines without Intel HDMI, the sof driver will fail to initialize.

  [Fix]
  Intel upstream 2 patches in the kernel to fix it.

  [Test Case]
  Boot the kernel on the machines without Intel HDMI audio, everything
  works well including the audio.

  [Regression Risk]
  Low, these 2 patches are already in the mainline kernel.

  On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy
  output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa-
  base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that
  now "snd-hda-intel" is loaded instead of sof-audio-pci. While the
  speakers are working fine, I do not have the internal microphone
  working (suspect a digital array).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wittawat   2063 F pulseaudio
   /dev/snd/controlC0:  wittawat   2063 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 12:42:32 2020
  InstallationDate: Installed on 2020-04-23 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Mic, Left
  Symptom_Type: None of the above
  Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] 
Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8600
  dmi.board.vendor: HP
  dmi.board.version: 44.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 15-dh0xxx
  dmi.product.sku: 7JX54EA#ABD
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1874698/+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 1874933] Re: Performance workaround for Dell 7390 2-in-1 Ice Lake

2020-06-23 Thread Chris Halse Rogers
I've added the testcase to the bug description. That seems like a
sensible enough reproducer.

** Description changed:

  == SRU justification focal ==
  
  As reported here:
  
https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/intel-linux/1174225-dell-xps-7390-intel-ice-lake-performance-hit-hard-by-a-linux-kernel-regression?view=stream
  
  This primarily impacts "Ubuntu 20.04 LTS (Focal Fossa)." as it switched to 
5.4 kernel.
  The 5.4 kernel added support for "Processor thermal device", for Ice Lake, 
which will expose the power tables (via PPCC).
  
  This system default "max RAPL long term power limit" is 15W. But this
  power table is specifying as 9W. So thermald will limit power to 9W.
  
  If dptfxtract is executed, then power limit will be higher than power up
  value, but most of the users will use out of the box setup. So this need
  a workaround.
  
  This workaround will ignore any power limit less than the power up power
  limit.
  
  This is addressed in thermald 2.1 with two commits:
  
https://github.com/intel/thermal_daemon/commit/f7db434293387c965e8d9141608f855893740e3a
  
https://github.com/intel/thermal_daemon/commit/c3461690eafb7304bf59a39fb02955a5154b3861
  
  I know 20.04 LTS uses 1.9.1. I can assist in backport if required.
  
  == Fix ==
  
  Two upstream commits to ease backporting:
     - eeadf7d2efe Restore to min state on deactivation without
   depending on hardware state
     - 9a6dc27879a Clean up the code and documentation
  
  Two upstream commits for the fix:
     - f7db4342933 Avoid polling power in non PPCC case
     - c3461690eaf Ignore invalid PPCC max power limit
  
  == Test case ==
  
- As reported here: https://www.phoronix.com/forums/forum/linux-graphics-x
- -org-drivers/intel-linux/1174225-dell-xps-7390-intel-ice-lake-
- performance-hit-hard-by-a-linux-kernel-regression?view=stream
+ Open two terminals:
+ -In the first terminal run the following command:
+"sudo turbostat --show PkgWatt"
+ -In the second terminal run some all CPU busy workload, like stress-ng or 
mprime
+ 
+ After few seconds turbostat will show that power is capped around 9W.
+ 
+ Install the updated thermald, and repeat.
+ 
+ Now with this fix the power should be capped around 15W.
  
  == Regression Potential ==
  
  This fix involves changing the power limits logic so there is a potential 
that this may affect change the throttling behaviour of other systems with
  poorly defined PPCC power tables because it now ignores the power limits
  less than the power up limits. Users will see their machines run faster
  and hence active cooling may crank up (e.g. fans) but I think the speed
  improvement outweighs the noise factor.
  
  Note that these changes are already in thermald 2.1 that is now in
  Ubuntu  Groovy 20.10.
  
  ---

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

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

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

Title:
  Performance workaround for Dell 7390 2-in-1 Ice Lake

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

Bug description:
  == SRU justification focal ==

  As reported here:
  
https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/intel-linux/1174225-dell-xps-7390-intel-ice-lake-performance-hit-hard-by-a-linux-kernel-regression?view=stream

  This primarily impacts "Ubuntu 20.04 LTS (Focal Fossa)." as it switched to 
5.4 kernel.
  The 5.4 kernel added support for "Processor thermal device", for Ice Lake, 
which will expose the power tables (via PPCC).

  This system default "max RAPL long term power limit" is 15W. But this
  power table is specifying as 9W. So thermald will limit power to 9W.

  If dptfxtract is executed, then power limit will be higher than power
  up value, but most of the users will use out of the box setup. So this
  need a workaround.

  This workaround will ignore any power limit less than the power up
  power limit.

  This is addressed in thermald 2.1 with two commits:
  
https://github.com/intel/thermal_daemon/commit/f7db434293387c965e8d9141608f855893740e3a
  
https://github.com/intel/thermal_daemon/commit/c3461690eafb7304bf59a39fb02955a5154b3861

  I know 20.04 LTS uses 1.9.1. I can assist in backport if required.

  == Fix ==

  Two upstream commits to ease backporting:
     - eeadf7d2efe Restore to min state on deactivation without
   depending on hardware state
     - 9a6dc27879a Clean up the code and documentation

  Two upstream commits for the fix:
     - f7db4342933 Avoid polling power in non PPCC case
     - c3461690eaf Ignore invalid PPCC max power limit

  == Test case ==

  Open two terminals:
  -In the first terminal run the following command:
 "sudo turbostat --show PkgWatt"
  -In 

[Kernel-packages] [Bug 1874933] Please test proposed package

2020-06-23 Thread Chris Halse Rogers
Hello Srinivas, or anyone else affected,

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

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

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

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

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

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

Title:
  Performance workaround for Dell 7390 2-in-1 Ice Lake

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

Bug description:
  == SRU justification focal ==

  As reported here:
  
https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/intel-linux/1174225-dell-xps-7390-intel-ice-lake-performance-hit-hard-by-a-linux-kernel-regression?view=stream

  This primarily impacts "Ubuntu 20.04 LTS (Focal Fossa)." as it switched to 
5.4 kernel.
  The 5.4 kernel added support for "Processor thermal device", for Ice Lake, 
which will expose the power tables (via PPCC).

  This system default "max RAPL long term power limit" is 15W. But this
  power table is specifying as 9W. So thermald will limit power to 9W.

  If dptfxtract is executed, then power limit will be higher than power
  up value, but most of the users will use out of the box setup. So this
  need a workaround.

  This workaround will ignore any power limit less than the power up
  power limit.

  This is addressed in thermald 2.1 with two commits:
  
https://github.com/intel/thermal_daemon/commit/f7db434293387c965e8d9141608f855893740e3a
  
https://github.com/intel/thermal_daemon/commit/c3461690eafb7304bf59a39fb02955a5154b3861

  I know 20.04 LTS uses 1.9.1. I can assist in backport if required.

  == Fix ==

  Two upstream commits to ease backporting:
     - eeadf7d2efe Restore to min state on deactivation without
   depending on hardware state
     - 9a6dc27879a Clean up the code and documentation

  Two upstream commits for the fix:
     - f7db4342933 Avoid polling power in non PPCC case
     - c3461690eaf Ignore invalid PPCC max power limit

  == Test case ==

  Open two terminals:
  -In the first terminal run the following command:
 "sudo turbostat --show PkgWatt"
  -In the second terminal run some all CPU busy workload, like stress-ng or 
mprime

  After few seconds turbostat will show that power is capped around 9W.

  Install the updated thermald, and repeat.

  Now with this fix the power should be capped around 15W.

  == Regression Potential ==

  This fix involves changing the power limits logic so there is a potential 
that this may affect change the throttling behaviour of other systems with
  poorly defined PPCC power tables because it now ignores the power limits
  less than the power up limits. Users will see their machines run faster
  and hence active cooling may crank up (e.g. fans) but I think the speed
  improvement outweighs the noise factor.

  Note that these changes are already in thermald 2.1 that is now in
  Ubuntu  Groovy 20.10.

  ---

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1874933/+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 1872059] Proposed package upload rejected

2020-04-28 Thread Chris Halse Rogers
An upload of apport to focal-proposed has been rejected from the upload
queue for the following reason: "Groovy already has an apport verson
2.20.11-0ubuntu28 uploaded, withThis will need a new upload with a new
version.".

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

Title:
  missing hardware/runtime info when reporing linux-firmware bugs via
  apport

Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  In Progress
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Bionic:
  Invalid
Status in linux-firmware source package in Eoan:
  Invalid
Status in apport source package in Focal:
  In Progress
Status in linux-firmware source package in Focal:
  Invalid

Bug description:
  linux-firmware doesn't install any package hooks for apport, so it
  will only carry some default items leaving hardware list, kernel
  messages unattached. Suggest symlink /usr/share/apport/package-hooks
  /source_linux-firmware.py to source_linux.py as other linux image debs
  do in bug 1847967.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 10 19:15:15 2020
  Dependencies:
   
  InstallationDate: Installed on 2019-09-28 (194 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Dependencies:
   
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-09-28 (194 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923)
  MachineType: Apple Inc. MacBookPro11,1
  NonfreeKernelModules: wl
  Package: linux-firmware
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic 
root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet 
splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev 
sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 06/13/2019
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 156.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.family: Mac
  dmi.product.name: MacBookPro11,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1872059/+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 1876862] [NEW] Missing v3d driver disables 3D support on RPi4

2020-05-05 Thread Chris Halse Rogers
Public bug reported:

Our raspberry pi kernel builds don't include the v3d drm driver
(The relevant diff between the raspbian kernel config and ours)
-CONFIG_DRM_V3D=m
+# CONFIG_DRM_V3D is not set

This means 3D acceleration is unavailable on our Pi 4 images.

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

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

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

Title:
  Missing v3d driver disables 3D support on RPi4

Status in linux-raspi package in Ubuntu:
  New
Status in linux-raspi source package in Focal:
  New

Bug description:
  Our raspberry pi kernel builds don't include the v3d drm driver
  (The relevant diff between the raspbian kernel config and ours)
  -CONFIG_DRM_V3D=m
  +# CONFIG_DRM_V3D is not set

  This means 3D acceleration is unavailable on our Pi 4 images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1876862/+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 1876066] Re: Support Intel TGL CPU on Focal

2020-05-05 Thread Chris Halse Rogers
Hello Alex, or anyone else affected,

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

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

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

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

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

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

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

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

Title:
  Support Intel TGL CPU on Focal

Status in OEM Priority Project:
  Confirmed
Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Focal:
  Fix Committed
Status in thermald source package in Groovy:
  Fix Released

Bug description:
  [impact]

  thermald doesn't support Tiger Lake cpus

  [test case]

  run thermald on Tiger Lake cpu

  It can be checked by following command, and the patch works if it return 
"passed".
  $ systemctl is-active --quiet thermald && echo passed

  [regression potential]

  because TGL is not supported by current thermald, so thermald always inactive 
on TGL platform. This patch is to activate it.
  So, there's not potential regression.

  [scope]

  needed for F/G

  [original description]

  need the patch to support Intel TGL CPU on Focal

  https://github.com/intel/thermal_daemon/blob/master/src/thd_engine.cpp#L666

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1876066/+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 1856084] Update Released

2020-01-07 Thread Chris Halse Rogers
The verification of the Stable Release Update for zfs-linux has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Livelock between ZFS evict and writeback threads

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Bionic:
  Fix Released
Status in zfs-linux source package in Disco:
  Fix Released
Status in zfs-linux source package in Eoan:
  Fix Released
Status in zfs-linux source package in Focal:
  Fix Released
Status in zfs-linux package in Debian:
  Fix Released

Bug description:
  Livelock between ZFS evict and writeback threads

  [Impact]
  ZIO pipeline stalls, causing ZFS workloads to hang indefinitely

  [Description]
  For certain ZFS workloads, we start seeing hung task timeouts in the kernel 
logs due to zil_commit() stalling. This is due to zfs_zget() not detecting 
whether a znode has been marked for deletion before attempting to access it, 
causing a constant "retry loop" in zfs_get_data() if that znode has been 
unlinked already. An example of the stack traces follows:

  [72742.051703] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [72742.070429] mysqld  D0  5713   2881 0x0320
  [72742.073220] Call Trace:
  [72742.075305]  __schedule+0x24e/0x880
  [72742.090436]  schedule+0x2c/0x80
  [72742.090438]  schedule_preempt_disabled+0xe/0x10
  [72742.090441]  __mutex_lock.isra.5+0x276/0x4e0
  [72742.090547]  ? dmu_tx_destroy+0x105/0x130 [zfs]
  [72742.090555]  __mutex_lock_slowpath+0x13/0x20
  [72742.115374]  ? __mutex_lock_slowpath+0x13/0x20
  [72742.132266]  mutex_lock+0x2f/0x40
  [72742.134207]  zil_commit_impl+0x1b0/0x1b30 [zfs]
  [72742.150428]  ? spl_kmem_alloc+0x115/0x180 [spl]
  [72742.152622]  ? mutex_lock+0x12/0x40
  [72742.154819]  ? zfs_refcount_add_many+0x9a/0x100 [zfs]
  [72742.171450]  zil_commit+0xde/0x150 [zfs]
  [72742.173687]  zfs_fsync+0x77/0xe0 [zfs]
  [72742.175044]  zpl_fsync+0x80/0x110 [zfs]
  [72742.191690]  vfs_fsync_range+0x51/0xb0
  [72742.193876]  do_fsync+0x3d/0x70
  [72742.195126]  SyS_fsync+0x10/0x20
  [72742.211059]  do_syscall_64+0x73/0x130
  [72742.214078]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2

  It's possible to hit this issue due to a race between the ZFS evict
  and writeback threads. If the z_iput task is trying to evict a znode
  that's currently sitting in the writeback thread, both will "livelock"
  each other and stall the ZIO pipeline, causing other ZFS operations
  (such as zil_commit) to hang indefinitely.

  This has been documented and fixed upstream in PR#9583 [0]. We need to
  pull two fixes from upstream: the first one fixes the zfs_zget() issue
  in the writeback thread, while the second fixes a regression on
  O_TMPFILE descriptors caused by the first one.

  Upstream patches:
   - Break out of zfs_zget early if unlinked znode (41e1aa2a06f8)
   - Check for unlinked znodes after igrab() (0c46813805f4)

  [Test Case]
  Being a race condition, this issue has been hard to reproduce consistently. 
The racing window between evict() and the ZFS writeback thread is quite strict, 
but users have reported this to show up after some hours of running 
LXD-containerized mySQL workloads.

  [Regression Potential]
  These patches have been tested both in the ZFS test suite and in production 
environments, so the potential for further regressions should be low.
  Additional regressions would likely cause issues with the ZFS 
writeback/commit and IO pipeline, so they should be spotted fairly quickly.

  [0] https://github.com/zfsonlinux/zfs/pull/9583
  [1] https://github.com/zfsonlinux/zfs/commit/41e1aa2a06f8
  [2] https://github.com/zfsonlinux/zfs/commit/0c46813805f4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1856084/+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 1958620] Re: Flickering white/black screen once KMS comes up

2022-01-24 Thread Chris Halse Rogers
There is no scanout hardware connected to the AMD GPU, so if there is
any involvement by amdgpu it is purely by making i915 misbehave.

This is also not a GNOME bug - the display corrupts as soon as the KMS
driver is loaded, which, since I've got an encrypted rootfs, is early in
the initramfs. The same behaviour is observed regardless of the kernel
commandline options, too, so it's not plymouth doing something weird, or
vthandoff. It also happens with break=mount.

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

Title:
  Flickering white/black screen once KMS comes up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This looks like a regression from the 5.13.0-20-generic kernel to the
  5.15.0-17-generic kernel. The display works fine under efifb, but as
  soon as the DRM drivers are loaded and KMS kicks in the display is
  replaced by black with flickering white (apparently when what would be
  on the output changes).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-17-generic 5.15.0-17.17
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  7134 F pipewire-media-
   /dev/snd/seq:chris  7133 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 21 17:07:08 2022
  InstallationDate: Installed on 2021-06-26 (208 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
  MachineType: Dell Inc. XPS 15 9575
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.204
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago)
  dmi.bios.date: 07/07/2019
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958620/+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 1957094] Re: on-demand mode doesn't work with nvidia-390

2022-02-01 Thread Chris Halse Rogers
Hello jeremyszu, or anyone else affected,

Accepted ubuntu-drivers-common into impish-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-drivers-common/1:0.9.2.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-
impish to verification-done-impish. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-impish. 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: ubuntu-drivers-common (Ubuntu Impish)
   Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-impish

** Description changed:

  [Impact]
  
   * In any Ubuntu series, if user using a old GPU (which supported by
  nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB
  GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver
  correctly.
  
  [Test Plan]
  
   * install nvidia-390 on nvidia-390 supported system.
   * prime-select on-demand
   * reboot
   * glxinfo
   * after applying this patch, it will fall back to "ON" mode after reboot.
  
+  * install nvidia-450 on nvidia-450 supported system.
+  * prime-select on-demand
+  * 
+ 
  [Where problems could occur]
   * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user 
stays in on-demand mode with 390 without problem, the after upgrading u-d-c and 
reboot. The mode will fall back to "ON" mode.
   * From my point of view, it's fine because nvidia-390 doesn't support RTD3. 
Thus, the nvidia will always stay in "Active" stage no matter which mode it is.
  * While there is no way to inform the user about this change, changing to the 
only supported default will avoid breaking GLX.
- 
  
  ---
  
  The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu-
  drivers-common/+bug/1942789.
  
  It impacts Jammy and Impish so far.
  
  [Steps to reproduce]
  1. Find a GPU supports nvidia-390
  2. ubuntu-drivers install nvidia:390
  3. prime-select on-demand
  4. glxinfo
  
  [Expected result]
  Shows intel or nvidia drives monitor
  
  [Actual result]
  Error: couldn't find RGB GLX visual or fbconfig
  
  Since we are all agree "on-demand" mode as default mode.
  Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter 
RTD3).
  We could consider to make it as performance mode and leave a note on 
nvidia-settings.
  I'll prepare some test packages.

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

Title:
  on-demand mode doesn't work with nvidia-390

Status in OEM Priority Project:
  New
Status in nvidia-settings package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Committed
Status in nvidia-settings source package in Impish:
  New
Status in ubuntu-drivers-common source package in Impish:
  Fix Committed
Status in nvidia-settings source package in Jammy:
  New
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

   * In any Ubuntu series, if user using a old GPU (which supported by
  nvidia-390 only) then issuing glxinfo will get "Error: couldn't find
  RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri
  driver correctly.

  [Test Plan]

   * install nvidia-390 on nvidia-390 supported system.
   * prime-select on-demand
   * reboot
   * glxinfo
   * after applying this patch, it will fall back to "ON" mode after reboot.

   * install nvidia-450 on nvidia-450 supported system.
   * prime-select on-demand
   * 

  [Where problems could occur]
   * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user 
stays in on-demand mode with 390 without problem, the after upgrading u-d-c and 
reboot. The mode will fall back to "ON" mode.
   * From my point of view, it's fine because nvidia-390 doesn't support RTD3. 
Thus, the nvidia will always stay in "Active" stage no matter which mode it is.
  * While there is no way to inform the user about this change, changing to the 
only supported default will avoid breaking GLX.

  ---

  The regressio

[Kernel-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390

2022-02-01 Thread Chris Halse Rogers
I've accepted this, but have amended the test plan to try and ensure
this doesn't change the behaviour on the -450 series drivers.

I'm not entirely sure what the "" check
should be. @Alberto, @Jeremy: Could you please replace that part of the
test-plan with the steps required to check that on-demand still works
for -450?

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

Title:
  on-demand mode doesn't work with nvidia-390

Status in OEM Priority Project:
  New
Status in nvidia-settings package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Committed
Status in nvidia-settings source package in Impish:
  New
Status in ubuntu-drivers-common source package in Impish:
  Fix Committed
Status in nvidia-settings source package in Jammy:
  New
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

   * In any Ubuntu series, if user using a old GPU (which supported by
  nvidia-390 only) then issuing glxinfo will get "Error: couldn't find
  RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri
  driver correctly.

  [Test Plan]

   * install nvidia-390 on nvidia-390 supported system.
   * prime-select on-demand
   * reboot
   * glxinfo
   * after applying this patch, it will fall back to "ON" mode after reboot.

   * install nvidia-450 on nvidia-450 supported system.
   * prime-select on-demand
   * 

  [Where problems could occur]
   * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user 
stays in on-demand mode with 390 without problem, the after upgrading u-d-c and 
reboot. The mode will fall back to "ON" mode.
   * From my point of view, it's fine because nvidia-390 doesn't support RTD3. 
Thus, the nvidia will always stay in "Active" stage no matter which mode it is.
  * While there is no way to inform the user about this change, changing to the 
only supported default will avoid breaking GLX.

  ---

  The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu-
  drivers-common/+bug/1942789.

  It impacts Jammy and Impish so far.

  [Steps to reproduce]
  1. Find a GPU supports nvidia-390
  2. ubuntu-drivers install nvidia:390
  3. prime-select on-demand
  4. glxinfo

  [Expected result]
  Shows intel or nvidia drives monitor

  [Actual result]
  Error: couldn't find RGB GLX visual or fbconfig

  Since we are all agree "on-demand" mode as default mode.
  Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter 
RTD3).
  We could consider to make it as performance mode and leave a note on 
nvidia-settings.
  I'll prepare some test packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1957094/+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 1957094] Re: on-demand mode doesn't work with nvidia-390

2022-02-01 Thread Chris Halse Rogers
Hello jeremyszu, or anyone else affected,

Accepted ubuntu-drivers-common into focal-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-drivers-
common/1:0.9.0~0.20.04.5 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: ubuntu-drivers-common (Ubuntu Focal)
   Status: New => Fix Committed

** Tags added: verification-needed-focal

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

Title:
  on-demand mode doesn't work with nvidia-390

Status in OEM Priority Project:
  New
Status in nvidia-settings package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Committed
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in nvidia-settings source package in Impish:
  New
Status in ubuntu-drivers-common source package in Impish:
  Fix Committed
Status in nvidia-settings source package in Jammy:
  New
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

   * In any Ubuntu series, if user using a old GPU (which supported by
  nvidia-390 only) then issuing glxinfo will get "Error: couldn't find
  RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri
  driver correctly.

  [Test Plan]

   * install nvidia-390 on nvidia-390 supported system.
   * prime-select on-demand
   * reboot
   * glxinfo
   * after applying this patch, it will fall back to "ON" mode after reboot.

   * install nvidia-450 on nvidia-450 supported system.
   * prime-select on-demand
   * 

  [Where problems could occur]
   * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user 
stays in on-demand mode with 390 without problem, the after upgrading u-d-c and 
reboot. The mode will fall back to "ON" mode.
   * From my point of view, it's fine because nvidia-390 doesn't support RTD3. 
Thus, the nvidia will always stay in "Active" stage no matter which mode it is.
  * While there is no way to inform the user about this change, changing to the 
only supported default will avoid breaking GLX.

  ---

  The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu-
  drivers-common/+bug/1942789.

  It impacts Jammy and Impish so far.

  [Steps to reproduce]
  1. Find a GPU supports nvidia-390
  2. ubuntu-drivers install nvidia:390
  3. prime-select on-demand
  4. glxinfo

  [Expected result]
  Shows intel or nvidia drives monitor

  [Actual result]
  Error: couldn't find RGB GLX visual or fbconfig

  Since we are all agree "on-demand" mode as default mode.
  Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter 
RTD3).
  We could consider to make it as performance mode and leave a note on 
nvidia-settings.
  I'll prepare some test packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1957094/+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 1957094] Re: on-demand mode doesn't work with nvidia-390

2022-02-01 Thread Chris Halse Rogers
For the nvidia-settings upload, the new wording looks somewhat strange:

++   " in on-demand mode (only if nvidia version >= 
450; "
++   "otherwise, the behavior will approach to "
++   "performance mode). This option is applied 
after "
++   "a system restart.");

Perhaps better wording would be something along the lines of “(only
using nvidia driver versions >= 450. On earlier drivers this behaves the
same as performance mode)”?

Also: is this a translatable string?

Alternatively: how hard would it be to *detect* the driver version, as
ubuntu-drivers-common does, and grey out the option?

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

Title:
  on-demand mode doesn't work with nvidia-390

Status in OEM Priority Project:
  New
Status in nvidia-settings package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Committed
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in nvidia-settings source package in Impish:
  New
Status in ubuntu-drivers-common source package in Impish:
  Fix Committed
Status in nvidia-settings source package in Jammy:
  New
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

   * In any Ubuntu series, if user using a old GPU (which supported by
  nvidia-390 only) then issuing glxinfo will get "Error: couldn't find
  RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri
  driver correctly.

  [Test Plan]

   * install nvidia-390 on nvidia-390 supported system.
   * prime-select on-demand
   * reboot
   * glxinfo
   * after applying this patch, it will fall back to "ON" mode after reboot.

   * install nvidia-450 on nvidia-450 supported system.
   * prime-select on-demand
   * 

  [Where problems could occur]
   * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user 
stays in on-demand mode with 390 without problem, the after upgrading u-d-c and 
reboot. The mode will fall back to "ON" mode.
   * From my point of view, it's fine because nvidia-390 doesn't support RTD3. 
Thus, the nvidia will always stay in "Active" stage no matter which mode it is.
  * While there is no way to inform the user about this change, changing to the 
only supported default will avoid breaking GLX.

  ---

  The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu-
  drivers-common/+bug/1942789.

  It impacts Jammy and Impish so far.

  [Steps to reproduce]
  1. Find a GPU supports nvidia-390
  2. ubuntu-drivers install nvidia:390
  3. prime-select on-demand
  4. glxinfo

  [Expected result]
  Shows intel or nvidia drives monitor

  [Actual result]
  Error: couldn't find RGB GLX visual or fbconfig

  Since we are all agree "on-demand" mode as default mode.
  Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter 
RTD3).
  We could consider to make it as performance mode and leave a note on 
nvidia-settings.
  I'll prepare some test packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1957094/+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 1964992] Update Released

2023-04-18 Thread Chris Halse Rogers
The verification of the Stable Release Update for zfs-linux has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  ZFS ignores ARC sizes below allmem/32

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Bionic:
  Fix Released
Status in zfs-linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  ZFS ignores tunable "zfs_arc_max" due to it being below allmem/32 threshold. 
This prevents users from properly restraining ARC sizes, and can cause 
increased memory contention in some systems.

  [Test Plan]
  1. Deploy test system with ZFS storage and 32GB RAM
  2. Add ARC tunables to /etc/modprobe.d/99-zfs-arc.conf
     # cat /etc/modprobe.d/99-zfs-arc.conf
     options zfs zfs_arc_min=536870912
     options zfs zfs_arc_max=966367641
  3. Reboot system
  4. Verify ARC sizes through "arc_summary"
     # arc_summary | grep -A3 "ARC size"
     ARC size (current):   < 0.1 %1.3 MiB
     Target size (adaptive):   100.0 %   15.7 GiB
     Min size (hard limit):  3.2 %  512.0 MiB
     Max size (high water):   31:1   15.7 GiB

  For a 32GB test system, we should be able to set max ARC sizes below
  1GB.

  [Fix]
  This has been fixed by upstream commit:
   - 36a6e2335c45 "Don't ignore zfs_arc_max below allmem/32"
   - e945e8d7f4fc "Restore FreeBSD sysctl processing for arc.min and arc.max"

  The commit has been introduced in upstream zfs-2.0.0, so it's needed
  for Bionic and Focal. Releases starting with Impish already have this
  commit by default:

  $ git describe --contains 36a6e2335c45
  zfs-2.0.0-rc1~332
  $ rmadison zfs-linux
   zfs-linux | 0.7.5-1ubuntu15| bionic  | source
   zfs-linux | 0.7.5-1ubuntu16.12 | bionic-updates  | source
   zfs-linux | 0.8.3-1ubuntu12| focal   | source
   zfs-linux | 0.8.3-1ubuntu12.9  | focal-security  | source
   zfs-linux | 0.8.3-1ubuntu12.13 | focal-updates   | source
   zfs-linux | 0.8.3-1ubuntu12.14 | focal-proposed  | source
   zfs-linux | 2.0.6-1ubuntu2 | impish  | source
   zfs-linux | 2.0.6-1ubuntu2.1   | impish-updates  | source
   zfs-linux | 2.1.2-1ubuntu3 | jammy   | source

  [Regression Potential]
  The introduced commit essentially removes the limitation of setting ARC 
tunables below allmem/32, and re-arranges the order of how some of the tunables 
are parsed. Regressions would possibly show up as other tunables being ignored 
or not being set correctly due to parsing errors. We should validate whether 
other ARC related tunables are still being set correctly, and whether ZFS is 
using the set values for the ARC memory thresholds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1964992/+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-04-27 Thread Chris Halse Rogers
Hi there! Sorry for the delay in getting to this. Some review:
*) It'd be easier to review if debian/changelog mentioned each of the patches 
and what they do. For example, rather than having the changelog entry:
  * Support ITMTv2 for Raptor Lake (LP: #2007579)
you could have the changelog entries:
  * debian/patches/0003-Parse-ITMT-Table.patch: 
  * debian/patches/0006-Install-ITMT-target.patch:
  * debian/patches/0018-Process-ITMT-v2.patch:
- Support ITMTv2 for Raptor Lake (LP: #2007579)

Since you know why you selected the patches you've added, this means I
don't need to try and reverse-engineer what bug each of the patches is
trying to address.

*) 0015-Ensure-there-is-one-trips-element-per-zone.patch: Why is this
patch here? It looks to me like it's patching code that we don't build?

Overall this looks like it's mostly there; it's not entirely clear to me
what *all* the patches are for, but it looks like they're (mostly)
sensible patches.

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

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 2004644] Re: Incompatible jbd2 format between kernel and lttng-modules

2023-02-28 Thread Chris Halse Rogers
Has lttng-smoke-test been run against the packages from -proposed? It's
not *entirely* clear to me, but that looked to be a part of the test-
case, and the autopkgtests don't (appear?) to run the smoke test?

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

Title:
  Incompatible jbd2 format between kernel and lttng-modules

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in lttng-modules package in Ubuntu:
  Fix Committed
Status in lttng-modules source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Incomplete
Status in lttng-modules source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Incomplete
Status in lttng-modules source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Incomplete
Status in lttng-modules source package in Kinetic:
  Fix Committed
Status in linux source package in Lunar:
  Incomplete
Status in lttng-modules source package in Lunar:
  Fix Committed

Bug description:
  [SRU Justification]

  Impact:
  Upstream stable added a change in the format of jbd2 in 5.4.229, 5.15.87, 
6.1.3.
  This is incompatible with the current changes in the lttng-module for 
bionic-5.4 backports, focal, jammy, and kinetic.

  Focal and bionic updates are needed for the current sru kernel release 
(2023.01.30). Both adt and rt fail during compilation of the module.
  Jammy and kinetic updates are not needed for this cycle because patches from 
upstream stable are not applied yet but it will be needed for the next 
release(s).

  Correct changes are already in lttng-modules:master and in 2.13.8-1
  version.

  Fix(es):
  1. focal and bionic: Picking 4 patches from upstream lttng-modules which 
handle the changed interface as well as add the required code to enable that 
change for other versions as well:
  LTTNG_KERNEL_RANGE(5,4,229, 5,5,0)
  LTTNG_KERNEL_RANGE(5,10,163, 5,11,0)
  LTTNG_KERNEL_RANGE(5,15,87, 5,16,0)
  LTTNG_KERNEL_RANGE(6,0,18, 6,1,0)
  LTTNG_KERNEL_RANGE(6,1,4, 6,2,0)

  2. Jammy and kinetic: backport 2.13.8-1

  Tescase(s) for focal:
  1. lttng-smoke-test fail to compile with the error from below.
  2. adt lttng-module fail to compile with same error

  Regression potential:
  We may notice new failures in ubuntu_lttng_smoke_test once this will compile 
and run. But it was tested locally and results were good, so probablity is very 
very low.

  760 21:14:39 DEBUG| [stdout] In file included from 
/var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/define_trace.h:87,
761 21:14:39 DEBUG| [stdout] from 
/var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:177,
762 21:14:39 DEBUG| [stdout] from 
/var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:29:
763 21:14:39 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:131:6:
 error: conflicting types for ‘trace_jbd2_run_stats’
764 21:14:39 DEBUG| [stdout] 131 | void trace_##_name(_proto);
765 21:14:39 DEBUG| [stdout] | ^~
766 21:14:39 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:43:2:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
767 21:14:39 DEBUG| [stdout] 43 | 
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
768 21:14:39 DEBUG| [stdout] | ^~~
769 21:14:39 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:85:2:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
770 21:14:39 DEBUG| [stdout] 85 | LTTNG_TRACEPOINT_EVENT_MAP(name, 
name, \
771 21:14:39 DEBUG| [stdout] | ^~
772 21:14:39 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:104:1:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
773 21:14:39 DEBUG| [stdout] 104 | 
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
774 21:14:39 DEBUG| [stdout] | ^~
775 21:14:39 DEBUG| [stdout] In file included from 
./include/trace/events/jbd2.h:9,
776 21:14:39 DEBUG| [stdout] from 
/var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:18:
777 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:243:21: note: 
previous definition of ‘trace_jbd2_run_stats’ was here
778 21:14:39 DEBUG| [stdout] 243 | static inline void 
trace_##name(proto) \
779 21:14:39 DEBUG| [stdout] | ^~
780 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:406:2: note: 
in expansion of macro ‘__DECLARE_TRACE’
781 21:14:39 DEBUG| [stdout] 406 | __DECLARE_TRACE(name, PARAMS(proto), 
P

[Kernel-packages] [Bug 1950282] Update Released

2023-02-28 Thread Chris Halse Rogers
The verification of the Stable Release Update for libmbim has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Jammy:
  Fix Committed
Status in libqmi source package in Jammy:
  Fix Committed
Status in linux source package in Jammy:
  New
Status in modemmanager source package in Jammy:
  Fix Committed

Bug description:
  * Impact

  Fibocom FM350 modems aren't working with the current version of
  modemmanager in 22.04.

  * Test case

  - install modemmanager, libmbim, and libqmi from -proposed
  - reboot and try WWAN function to see if any regression there.
  - perform dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  The verification should be done on FM350 to ensure it's correctly
  handled but also on other hardware to verify that there are no
  regressions

  * Regression potential

  The SRU does an update to new modemmanager serie so we should do a
  complete round of testing on different hardware and confirm there are
  no regression.

  ---

  :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] 
(rev 01)
  Subsystem: Hewlett-Packard Company Device [103c:8914]

  https://lore.kernel.org/linux-
  wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/

  Modemmanager requires >= 1.19.1, the detail info is in
  lp:1962525

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-07-13 (119 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Intel Corporation Alder Lake Client Platform
  Package: linux-firmware 1.187.20+staging.31
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem 
root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 
automatic-oem-config quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-9007-oem N/A
   linux-backports-modules-5.14.0-9007-oem  N/A
   linux-firmware   1.187.20+staging.31
  Tags:  focal
  Uname: Linux 5.14.0-9007-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/23/2021
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: AlderLake-M LP5 RVP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 0.1
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002:
  dmi.product.family: Alder Lake Client System
  dmi.product.name: Alder Lake Client Platform
  dmi.product.sku: 01010002
  dmi.product.version: 0.1
  dmi.sys.vendor: Intel Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1950282/+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 1989556] Proposed package upload rejected

2022-11-03 Thread Chris Halse Rogers
An upload of thermald to jammy-proposed has been rejected from the
upload queue for the following reason: "Please re-upload with an overall
"upgrade to 2.5.1" process bug, detailing the testing to be done to
detect regressions across hardware"".

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

Title:
  Add support for Raptor Lake S CPUs

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

Bug description:
  [Impact]

   * Support thermald on Raptor Lake S CPU.

  [Test Plan]

   * Use a machine with a Raptor Lake S cpu.

   * systemctl status thermald

   * Status of thermald should be `running`

  [Where problems could occur]

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1989556/+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 1989047] Proposed package upload rejected

2022-11-03 Thread Chris Halse Rogers
An upload of thermald to jammy-proposed has been rejected from the
upload queue for the following reason: "Please re-upload with an overall
"upgrade to 2.5.1" process bug, detailing the testing to be done to
detect regressions across hardware"".

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

Title:
  ADL: Fix System hang up when run Prime95 with i9-12900K CPU

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

Bug description:
  [Impact]
   * System hang up when run Prime95 10~15 minutes
  [Test Plan]
  1. Find a unit with i9-12900k CPU and liquid cooling
  2. Connect to Internet and install below tools
  >sudo apt update
  >sudo apt install stress-ng
  >sudo apt install 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 #decompressed from p95*.tar.gz
  >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]
   * it install Passive Policy as default and use PL1 max/min from PPCC, there 
may be some edge cases that don't handle well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1989047/+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] Proposed package upload rejected

2022-11-03 Thread Chris Halse Rogers
An upload of thermald to jammy-proposed has been rejected from the
upload queue for the following reason: "Please re-upload with an overall
"upgrade to 2.5.1" process bug, detailing the testing to be done to
detect regressions across hardware"".

-- 
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:
  Fix Released
Status in thermald source package in Jammy:
  New

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 1981087] Proposed package upload rejected

2022-11-03 Thread Chris Halse Rogers
An upload of thermald to jammy-proposed has been rejected from the
upload queue for the following reason: "Please re-upload with an overall
"upgrade to 2.5.1" process bug, detailing the testing to be done to
detect regressions across hardware"".

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

Bug description:
  [Impact]
   * thermald prematurely throttling GPU

  [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 1995606] Re: Upgrade thermald to 2.5.1

2022-11-04 Thread Chris Halse Rogers
** Description changed:

  [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.
  
- Currently, just use stress-ng and observe the temperature/frequency/power  
manually(e.g. s-tui).
- The whole test cases are the followings and run on the platforms, 
RPL/ADL/TGL/CML/CFL/KBL.
- 1. check if thermald could read rules from /dev/acpi_thermal_rel and generate 
the xml file on /etc/thermald/ correctly.
- 2. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded 
correctly.
- 3. 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.
- a. rapl.sh
- b. intel_pstate.sh
- c. powerclamp.sh
- d. processor.sh
+ [Test case]
+ For each supported CPU series (RPL/ADL/TGL/CML/CFL/KBL) the following tests 
will be run on machines in the CI lab:
  
- 4. check if the power/frequency would be throttled once the temperature reach 
the trip-points of thermal zone.
- 5. check if system would be throttled even the temperature is under the 
thrip-poits.
+ * 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)
+ * check if thermald could read rules from /dev/acpi_thermal_rel and generate 
the xml file on /etc/thermald/ correctly.
+   - (TODO: What are the concrete steps to check this?)
+ * check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded 
correctly.
+   - (TODO: How do we check this)
+ * 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
+ * check if the power/frequency would be throttled once the temperature reach 
the trip-points of thermal zone.
+ * check if system would be throttled even the temperature is under the 
thrip-poits.

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

Status in thermald package in Ubuntu:
  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 each supported CPU series (RPL/ADL/TGL/CML/CFL/KBL) the following tests 
will be run on machines in the CI lab:

  * 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)
  * check if thermald could read rules from /dev/acpi_thermal_rel and generate 
the xml file on /etc/thermald/ correctly.
- (TODO: What are the concrete steps to check this?)
  * check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded 
correctly.
- (TODO: How do we check this)
  * 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
  * check if the power/frequency would be throttled once the temperature reach 
the trip-points of thermal zone.
  * check if system would be throttled even the temperature is under the 
thrip-poits.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+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 1992714] Re: [SRU] SoF for RPL platform support

2022-11-08 Thread Chris Halse Rogers
Hello AceLan, or anyone else affected,

Accepted firmware-sof into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/firmware-
sof/2.0-1ubuntu4 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: firmware-sof (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

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

Title:
  [SRU] SoF for RPL platform support

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in firmware-sof source package in Kinetic:
  In Progress
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  RPL platforms require new sof struct and firmware to enable its audio

  [Fix]
  Below 2 commits are from v6.1-rc1
  63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions
  5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake

  Firmware are from here
  https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2

  [Test]
  Verified Dell machine which comes with rpl sdw audio.

  [Where problems could occur]
  Adding new struct, new ID, and new firmware, it won't affect old systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1992714/+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 1992714] Re: [SRU] SoF for RPL platform support

2022-11-08 Thread Chris Halse Rogers
Hello AceLan, or anyone else affected,

Accepted firmware-sof into kinetic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/firmware-
sof/2.1.1-1ubuntu1.1 in a few hours, and then in the -proposed
repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
kinetic to verification-done-kinetic. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-kinetic. 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: firmware-sof (Ubuntu Kinetic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-kinetic

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

Title:
  [SRU] SoF for RPL platform support

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in firmware-sof source package in Kinetic:
  Fix Committed
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  RPL platforms require new sof struct and firmware to enable its audio

  [Fix]
  Below 2 commits are from v6.1-rc1
  63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions
  5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake

  Firmware are from here
  https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2

  [Test]
  Verified Dell machine which comes with rpl sdw audio.

  [Where problems could occur]
  Adding new struct, new ID, and new firmware, it won't affect old systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1992714/+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

2022-11-08 Thread Chris Halse Rogers
Ok. So, sorry about all the back and forth. Partially this is because
I'm more familiar with thermald than others on the SRU team, and so
don't necessarily make things explicit that should be.

At a high level, what the SRU team (in general, so that *I* don't have
to be the single point of failure) is looking for is:

*) What is the scope of potential regressions - what hardware *could* this 
effect, what possible effects could it have
  - The answer to “what hardware” is: the list of CPUIDs in 
tdh_engine.cpp:id_table. This is SandyBridge onwards
  - The answer to “what effects” is: temperature throttling problems - either 
reduced performance of CPU (and GPU?) due to unnecessary throttling, or 
instability due to not controlling temperatures 

*) What is the scope of *upstream* support - what systems do *they* test on, 
and expect to continue to work.
  - Relatedly: what testing does upstream do
  - What do we do if upstream doesn't test on hardware that we support (ie: 
*we* care about all the hardware)

*) What is the process we are going to use to verify that upstream doesn't drop 
support for systems?
  - Upstream doesn't seem to make it very easy to identify this
  - eg: the current SRU includes dropping the MSR poking support. What process 
do we/will we have to catch such cases?

*) What is the process for testing that an upload does not regress
  - The [Test Case] above is good for systems with KBL or newer processors
  - thermald also supports systems from SandyBridge onwards - how are we 
testing these? These are still supported by Ubuntu; we need a testing system 
more than “maybe users will report regressions”, particularly since it's not 
necessarily going to be clear to users that “my system got slower” is related 
to the thermald update.

Most of those questions are covered above, I think, but some could do
with your input.

Particularly the SandyBridge+ question is an important one to answer.

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

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

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 each supported 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, we may face the edge case in the future.

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

2023-06-23 Thread Chris Halse Rogers
What *is* the in-motion condition? How would someone trigger it, and
what would be the consequences of it not triggering, or triggering at an
inappropriate time?

-- 
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:
  New
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]
  low

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 1995606] Re: Upgrade thermald to 2.5.1 for Jammy (22.04)

2023-06-23 Thread Chris Halse Rogers
In addition to the things identified above:

* I've added a question on
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2018275 about
what that's actually fixing.

* debian/patches/0004-Fixed-enumeration-of-cpu-thermal-sensors.patch:
this looks reasonable, but I'd like to make sure that were testing on at
least one system that should hit this fix (if I understand it correctly,
it should apply to anything having > 4 cores, which should be easy to
arrange)

Otherwise this looks reasonable, thanks!

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

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 2018275] Re: Fix the in-motion function does not work

2023-06-30 Thread Chris Halse Rogers
Ok, "here's a patch from an unmerged branch abandoned a year ago" isn't
particularly reassuring. However, investigation reveals that an
equivalent commit was merged to trunk and exists in 2.5.1:
https://github.com/intel/thermal_daemon/commit/4339234275b87b3973487cade283addd14fc9818

So, reverse-engineering the problem this is fixing:
* there exists a laptop with a firmware thermal table that contains a "motion" 
condition in each of its entries
* To determine the policy to apply thermald checks against each condition in 
each of the table entries. If it encounters a condition it does not understand, 
the check returns THD_ERROR (and presumably the check fails?)
* Since each entry of the firmware table on this laptop contains a "motion" 
condition, they are all rejected, and thermald instead applies the default "max 
power" policy.
* The patch implements a stub motion condition check - if the table specifies 
"motion = 0" then the condition is satisfied.

Am I correct in that understanding?

So the risk of regression here is mostly that thermald will *start
working* on such laptops. Or, alternatively, if there is a laptop where
*some, but not all* table entries contain a "motion" condition then this
will be enabling extra policy options, which might be inappropriate?

-- 
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:
  New
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.

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 1995606] Re: Upgrade thermald to 2.5.1 for Jammy (22.04)

2023-07-05 Thread Chris Halse Rogers
Relaying communication from off-Launchpad: Since we have no way to test
it, 0004-Fixed-enumeration-of-cpu-thermal-sensors.patch should be
dropped, and apart from that this is now acceptable.

-- 
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 2018275] Re: Fix the in-motion function does not work

2023-07-05 Thread Chris Halse Rogers
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 2018236] Re: Fix ADL: System shutdwon automically when run Prime95&stress-ng with i9-12900K

2023-07-05 Thread Chris Halse Rogers
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&stress-ng 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 2012260] Re: Add support for Alder Lake N

2023-07-05 Thread Chris Halse Rogers
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 2007579] Re: Raptor Lake Thermald ITMT version 2 support

2023-07-05 Thread Chris Halse Rogers
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 1995606] Re: Upgrade thermald to 2.5.1 for Jammy (22.04)

2023-07-05 Thread Chris Halse Rogers
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 1989044] Re: RPL: Add INT3400 base path

2023-07-05 Thread Chris Halse Rogers
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 1981087] Re: thermald prematurely throttling GPU

2023-07-05 Thread Chris Halse Rogers
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 1981087] Please test proposed package

2023-07-05 Thread Chris Halse Rogers
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 2018275] Re: Fix the in-motion function does not work

2023-07-05 Thread Chris Halse Rogers
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 2018236] Re: Fix ADL: System shutdwon automically when run Prime95&stress-ng with i9-12900K

2023-07-05 Thread Chris Halse Rogers
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&stress-ng 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 2012260] Re: Add support for Alder Lake N

2023-07-05 Thread Chris Halse Rogers
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 1995606] Re: Upgrade thermald to 2.5.1 for Jammy (22.04)

2023-07-25 Thread Chris Halse Rogers
I see that all the individual bugs have been verified, but has the test
plan documented on *this* bug been carried out? That is:

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

-- 
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 1892358] Update Released

2020-11-03 Thread Chris Halse Rogers
The verification of the Stable Release Update for systemd has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  autopkgtest success rate dropped inhibiting proposed migration

Status in build-essential package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Invalid
Status in iputils package in Ubuntu:
  Invalid
Status in kbd package in Ubuntu:
  Invalid
Status in linux-meta package in Ubuntu:
  Invalid
Status in ntpsec package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Invalid
Status in linux-meta source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Released
Status in build-essential source package in Focal:
  Confirmed
Status in linux-meta source package in Focal:
  New
Status in qemu source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Fix Released
Status in util-linux source package in Focal:
  Confirmed

Bug description:
  [impact]

  autopkgtests are failing/flaky and prevent other packages from
  migrating to -updates

  [test case]

  check autopkgtest history

  [regression potential]

  in regard to the changed test cases, any regression would likely
  result in either an incorrectly passed test, or an incorrectly failed
  test.

  [scope]

  for systemd, this is needed for x, b, and f.

  tests in g appear to be mostly stable, but I've opened MR (linked from
  this bug) to update the tests there as well.

  i don't plan to update x, as it's reaching ESM in ~6 months, and
  backporting the test fixes is more work than just a simple code copy,
  since there are additional differences/changes needed in the older
  version of systemd (and python3). the failing/flaky tests in x have
  been like that forever, and people have just retried them; we can keep
  retrying them until x moves into ESM next year.

  [original description]

  Hi,
  we had such cases in the past like bug 1817721 for bionic and maybe bug 
1892130 is about the same as well. There were more but I didn't want to search 
for all of them - what I checked is that there are no open ones clearly 
pointing out the recent further drop in already flaky subtests.

  In particular the tests "tests-in-lxd" and "systemd-fsckd" were known
  to be flaky before, but got even worse.

  Here stats of the last 40 runs, it might be a coincidences that this
  is after 246-2ubuntu1 landed. Could as well be any other change

  groovy
    amd64
  tests-in-lxd   (F 42% S  0% B 10% => P 45%/) 
BFFFBFF.B.F.F...FBF
  build-login(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  unit-config(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  networkd-testpy(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-and-services  (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-smoke (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  logind (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  storage(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  upstream   (F 35% S  0% B 10% => P 52%/) 
..FFB.FFF.FFBFF.B.F.F..FFBF
  udev   (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  systemd-fsckd  (F 37% S  0% B 10% => P 50%/) 
BFFFB.FF...FB.F..B.
  root-unittests (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
    ppc64el
  tests-in-lxd   (F 25% S  0% B  0% => P 75%/) 
FFFFF.F.
  systemd-fsckd  (F 35% S  0% B  0% => P 65%/) 
FFF...FFFFF.F..F
  root-unittests (F  2% S  0% B  0% => P 97%/) 
..F.
    s390x
  tests-in-lxd   (F 52% S  0% B  0% => P 47%/) 
FFF.FFF.FF....F.
  timedated  (F  2% S  0% B  0% => P 97%/) 
...F
  upstream   (F 17% S  0% B  0% => P 82%/) 
.F..F.F.FFF...F.
  systemd-fsckd  (F 32% S  0% 

[Kernel-packages] [Bug 1897934] Update Released

2020-11-03 Thread Chris Halse Rogers
The verification of the Stable Release Update for alsa-lib has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [SRU][Intel HDA] The initial sound level is set to zero (muted)

Status in Release Notes for Ubuntu:
  Invalid
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Released
Status in alsa-lib source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  Fail to run '/usr/sbin/alsactl restore' on the HDA-Intel machines, this
  results in the failure on setting the init mixer values for HDA sound
  card, and users experience the mute of audio after installing the 20.10.  

  [Fix]
  Backport a patch from the latest alsa-lib (v1.2.3+)

  [Test]
  Without the patched alsa-lib, rm ~/.config/pulse/*;sudo rm /var/lib/alsa/*;
  sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is
  muted.

  Install the patched alsa-lib, rm ~/.config/pulse/*;sudo rm /var/lib/alsa/*;
  sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is
  not muted.

  [Regression Potential]
  This could make the ucm audio fail to initialize, but this possibility is
  very low, since this patch is from upstream, and I tested on a ucm based
  machine, the audio is good.

  
  On boot into the live session - or on first install the sound level is muted.

  I have to use GNOME Control Center - Sounds to change to an
  appropriate level.  Once changed the level chosen is correctly
  retained between reboots.

  This appears to be a regression from 20.04 where the sound level was
  set to - I guess - 80% on the live-session/first install

  ProblemType: BugDistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.1-1ubuntu11
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu-budgie   5041 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.452
  CurrentDesktop: Budgie:GNOME
  Date: Wed Sep 30 16:03:08 2020
  LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2016
  dmi.bios.release: 15.31
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 95.22
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897934/+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 1413440] Re: USB stops working after a while (xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command)

2015-10-08 Thread Chris Halse Rogers
FWIW I can't recall getting this error on the 4.2 kernels  currently in
Wily. This might be fixed in 15.10.

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

Title:
  USB stops working after a while (xhci_hcd :00:14.0: Timeout while
  waiting for setup device command)

Status in System76:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  On my laptop the kernel will sometimes drop the USB hub. After this,
  the laptop doesn't recognise any device plugged in to the USB ports -
  plugging and unplugging any device I've tried into any of the USB
  ports produces no response, not even dmesg entries.

  Strangely this also applies to bluetooth - it no longer works once USB
  has dropped (possibly the module is hung of the bus internally).

  Once this has happened only a reboot fixes it; I've not managed to
  find any combination of module unload/reload or suspend cycles to
  reinitialise things correctly.

  Relevant snippet of dmesg:
  [48830.625057] xhci_hcd :00:14.0: Timeout while waiting for setup device 
command
  [48838.079718] xhci_hcd :00:14.0: Stopped the command ring failed, maybe 
the host is dead
  [48838.079742] xhci_hcd :00:14.0: Abort command ring failed
  [48838.079746] xhci_hcd :00:14.0: HC died; cleaning up
  [48838.079770] xhci_hcd :00:14.0: Timeout while waiting for setup device 
command
  [48838.079806] sched: RT throttling activated
  [48838.079981] usb 1-1: USB disconnect, device number 16
  [48838.079985] usb 1-1.2: USB disconnect, device number 18
  [48838.079987] usb 1-1.2.3: USB disconnect, device number 19
  [48838.080285] usb 1-1.2.4: USB disconnect, device number 20
  [48838.111892] usb 1-1.4: USB disconnect, device number 17
  [48838.191292] usb 1-4: USB disconnect, device number 6
  [48838.267550] usb 1-10: USB disconnect, device number 8
  [48838.282968] usb 2-1: device not accepting address 8, error -62
  [48838.282983] usb 2-1: USB disconnect, device number 8
  [48838.282986] usb 2-1.2: USB disconnect, device number 9

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-9-generic 3.18.0-9.10
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  4255 F pulseaudio
   /dev/snd/controlC0:  chris  4255 F pulseaudio
  CRDA:
   country AU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5170 - 5250 @ 40), (3, 23), (N/A)
(5250 - 5330 @ 40), (3, 23), (0 ms), DFS
(5735 - 5835 @ 40), (3, 30), (N/A)
  CurrentDesktop: Unity
  Date: Thu Jan 22 12:59:27 2015
  InstallationDate: Installed on 2013-08-06 (533 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System76, Inc. Galago UltraPro
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic.efi.signed 
root=UUID=92c2fa03-f29c-4bcc-87ab-f0fe28c134f2 ro quiet splash vt.handoff=7 
init=/lib/systemd/systemd break=mount
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-9-generic N/A
   linux-backports-modules-3.18.0-9-generic  N/A
   linux-firmware1.141
  RfKill:
   1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2013-08-06 (533 days ago)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Galago UltraPro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: galu1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, Inc,
  dmi.chassis.version: galu1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1:
  dmi.product.name: Galago UltraPro
  dmi.product.version: galu1
  dmi.sys.vendor: System76, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/system76/+bug/1413440/+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 1489045] Update Released

2015-09-08 Thread Chris Halse Rogers
The verification of the Stable Release Update for dkms has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Backport autopkgtest script to precise/trusty

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Precise:
  Fix Released
Status in dkms source package in Trusty:
  Fix Committed

Bug description:
  The kernel team has requested that we run DKMS tests via autopkgtests
  for precise and trusty the same way that we now do for vivid and
  upwards. For this we need to backport debian/scripts/dkms-autopkgtest
  from https://launchpad.net/ubuntu/+source/dkms/2.2.0.3-2ubuntu1.

  TEST CASE:
   Run autopkgtest for a DKMS package:

     adt-run bcmwl --- qemu adt-trusty-amd64-cloud.img   # or use a
  precise image, or "--- lxc "

  This currently fails with

     adt-run [15:18:24]: test command1: /usr/lib/dkms/dkms-autopkgtest
     adt-run [15:18:24]: test command1: [---
     bash: /usr/lib/dkms/dkms-autopkgtest: No such file or directory

  With the proposed packages this should work and look more like

  Setting up bcmwl-kernel-source (6.30.223.248+bdcom-0ubuntu4) ...
  Loading new bcmwl-6.30.223.248+bdcom DKMS files...
  First Installation: checking all kernels...
  Building only for 4.1.0-3-generic
  Building for architecture x86_64
  Building initial module for 4.1.0-3-generic
  Done.

  wl:
  Running module version sanity check.
   - Original module
     - No original module exists within this kernel
   - Installation
     - Installing to /lib/modules/4.1.0-3-generic/updates/dkms/

  depmod

  DKMS: install completed.
  update-initramfs: deferring update (trigger activated)
  Setting up libfakeroot:amd64 (1.20.2-1ubuntu1) ...
  Setting up fakeroot (1.20.2-1ubuntu1) ...
  update-alternatives: using /usr/bin/fakeroot-sysv to provide 
/usr/bin/fakeroot (fakeroot) in auto mode
  Setting up manpages-dev (3.74-1ubuntu1) ...
  Processing triggers for initramfs-tools (0.120ubuntu3) ...
  update-initramfs: Generating /boot/initrd.img-4.1.0-3-generic
  I: Testing binary package bcmwl-kernel-source
  I: Testing if bcmwl modules are correctly installed
  bcmwl, 6.30.223.248+bdcom, 4.1.0-3-generic, x86_64: installed
  adt-run [17:23:43]: test command1: ---]

  REGRESSION POTENTIAL: Almost zero. dkms is an arch: all package, thus
  no miscompilation possible. The new script is not being used in dkms'
  actual operation, only when being invoked through autopkgtest. As
  every DKMS package test fails right now, there is no test regression
  possible either.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1489045/+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 1324790] [NEW] Bluetooth problem with Parrot Zik headphones

2014-05-30 Thread Chris Halse Rogers
Public bug reported:

HSP profile fails to work on my bluetooth headset (a Parrot Zik); a2dp
works fine. HSP profile doesn't get sound or have the mic working.

This seems at least in part to be a kernel issue; the relevant bit of syslog is:
...
May 30 08:34:43 RedTail bluetoothd[4864]: 
/org/bluez/4864/hci0/dev_90_03_B7_5F_6F_DF/fd10: fd(25) ready
May 30 08:34:44 RedTail kernel: [63184.627985] input: 90:03:B7:5F:6F:DF as 
/devices/virtual/input/input121
May 30 08:34:45 RedTail bluetoothd[4864]: Badly formated or unrecognized 
command: AT+CSCS=?
May 30 08:34:45 RedTail bluetoothd[4864]: Badly formated or unrecognized 
command: AT+CPBS=?
May 30 08:34:45 RedTail bluetoothd[4864]: Badly formated or unrecognized 
command: AT+CIMI
May 30 08:35:12 RedTail bluetoothd[4864]: 
/org/bluez/4864/hci0/dev_90_03_B7_5F_6F_DF/fd11: fd(23) ready
May 30 08:37:26 RedTail bluetoothd[4864]: Audio connection got disconnected
May 30 08:37:55 RedTail kernel: [63376.126544] Bluetooth: hci0 SCO packet for 
unknown connection handle 0
May 30 08:37:55 RedTail kernel: [63376.126559] Bluetooth: hci0 SCO packet for 
unknown connection handle 0
May 30 08:37:55 RedTail kernel: [63376.126566] Bluetooth: hci0 SCO packet for 
unknown connection handle 0
May 30 08:37:55 RedTail kernel: [63376.126572] Bluetooth: hci0 SCO packet for 
unknown connection handle 0
May 30 08:37:55 RedTail kernel: [63376.126578] Bluetooth: hci0 SCO packet for 
unknown connection handle 0
May 30 08:37:55 RedTail kernel: [63376.126584] Bluetooth: hci0 SCO packet for 
unknown connection handle 0
May 30 08:37:55 RedTail kernel: [63376.126590] Bluetooth: hci0 SCO packet for 
unknown connection handle 0
May 30 08:37:55 RedTail kernel: [63376.126595] Bluetooth: hci0 SCO packet for 
unknown connection handle 0
May 30 08:37:55 RedTail kernel: [63376.126601] Bluetooth: hci0 SCO packet for 
unknown connection handle 0
May 30 08:37:55 RedTail kernel: [63376.126606] Bluetooth: hci0 SCO packet for 
unknown connection handle 0
May 30 08:37:55 RedTail kernel: [63376.126612] Bluetooth: hci0 SCO packet for 
unknown connection handle 0
May 30 08:37:55 RedTail kernel: [63376.126617] Bluetooth: hci0 SCO packet for 
unknown connection handle 0
May 30 08:37:55 RedTail kernel: [63376.126623] Bluetooth: hci0 SCO packet for 
unknown connection handle 7936
May 30 08:37:55 RedTail kernel: [63376.126629] Bluetooth: hci0 SCO packet for 
unknown connection handle 48
May 30 08:37:55 RedTail kernel: [63376.126635] Bluetooth: hci0 SCO packet for 
unknown connection handle 0
May 30 08:37:55 RedTail kernel: [63376.126641] Bluetooth: hci0 SCO packet for 
unknown connection handle 0
May 30 08:37:55 RedTail kernel: [63376.126647] Bluetooth: hci0 SCO packet for 
unknown connection handle 0
...

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.15.0-2-generic (not installed)
ProcVersionSignature: Ubuntu 3.15.0-2.6-generic 3.15.0-rc6
Uname: Linux 3.15.0-2-generic x86_64
ApportVersion: 2.14.2-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC1D0c:   chris  3967 F...m pulseaudio
 /dev/snd/pcmC1D0p:   chris  3967 F...m pulseaudio
 /dev/snd/controlC1:  chris  3967 F pulseaudio
 /dev/snd/controlC0:  chris  3967 F pulseaudio
CurrentDesktop: Unity
Date: Fri May 30 08:56:58 2014
InstallationDate: Installed on 2013-08-06 (296 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: System76, Inc. Galago UltraPro
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.15.0-2-generic.efi.signed 
root=UUID=92c2fa03-f29c-4bcc-87ab-f0fe28c134f2 ro quiet splash 
i915.i915_enable_rc6=7 vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.15.0-2-generic N/A
 linux-backports-modules-3.15.0-2-generic  N/A
 linux-firmware1.130
SourcePackage: linux
UpgradeStatus: Upgraded to utopic on 2013-08-06 (296 days ago)
dmi.bios.date: 07/09/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: Galago UltraPro
dmi.board.vendor: System76, Inc.
dmi.board.version: galu1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: System76, Inc,
dmi.chassis.version: galu1
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1:
dmi.product.name: Galago UltraPro
dmi.product.version: galu1
dmi.sys.vendor: System76, Inc.

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


** Tags: amd64 apport-bug utopic

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

Title:
  Bluetooth problem with Parrot Zik headphones

Status in “linux” package in Ubuntu:
  New

Bug description:
  HSP profile fails to work on my bluetooth headset (a Parrot Zik)

[Kernel-packages] [Bug 1295483] [NEW] [i915] kernel BUG at /build/buildd/linux-3.13.0/lib/swiotlb.c:456!

2014-03-20 Thread Chris Halse Rogers
Public bug reported:

It looks like Chrome's GPU acceleration is very infrequently capable of
taking down the kernel; I've been running it for a number of weeks and
only just hit this BUG:

Mar 21 14:17:49 RedTail kernel: [58101.987805] [ cut here 
]
Mar 21 14:17:49 RedTail kernel: [58101.987823] kernel BUG at 
/build/buildd/linux-3.13.0/lib/swiotlb.c:456!
Mar 21 14:17:49 RedTail kernel: [58101.987840] invalid opcode:  [#1] SMP 
Mar 21 14:17:49 RedTail kernel: [58101.987852] Modules linked in: 
hid_magicmouse hidp hid ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs ctr ccm 
xt_conntrack ipt_REJECT overlayfs ip6table_filter ip6_tables ebtable_
nat ebtables xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp 
bridge stp llc iptable_filter ip_tables x_tables lttng_probe_writeback 
lttng_probe_workqueue rfcomm bnep lttng_probe_vmscan lttng_probe_udp 
lttng_probe_timer lttng_probe_sunrpc lttng_probe_statedump lttng_probe_sock 
lttng_probe_skb lttng_probe_signal lttng_probe_scsi lttng_probe_sche
d lttng_probe_rpm lttng_probe_regulator lttng_probe_regmap lttng_probe_rcu 
lttng_probe_random lttng_probe_printk lttng_probe_power lttng_probe_net 
lttng_probe_napi lttng_probe_module lttng_probe_kvm_x86_mmu lttng_
probe_kvm_x86 lttng_probe_kvm lttng_probe_kmem lttng_probe_jbd2 lttng_probe_irq 
lttng_probe_gpio lttng_probe_ext4 lttng_probe_compaction lttng_probe_btrfs 
lttng_probe_block lttng_probe_asoc lttng_types lttng_ring_
buffer_metadata_mmap_client lttng_ring_buffer_client_mmap_overwrite 
lttng_ring_buffer_client_mmap_discard lttng_ring_buffer_metadata_client 
lttng_ring_buffer_client_overwrite binfmt_misc lttng_ring_buffer_client_d
iscard lttng_tracer lttng_statedump lttng_ftrace lttng_kprobes 
lttng_lib_ring_buffer lttng_kretprobes joydev nls_iso8859_1 
x86_pkg_temp_thermal intel_powerclamp coretemp arc4 kvm_intel kvm ath9k 
ath9k_common psmou
se ath9k_hw serio_raw snd_hda_codec_via ath snd_hda_codec_hdmi snd_hda_intel 
mac80211 uvcvideo videobuf2_vmalloc snd_hda_codec videobuf2_memops 
videobuf2_core lpc_ich snd_hwdep snd_pcm videodev cfg80211 rtsx_pci_m
s memstick dm_multipath scsi_dh ath3k btusb snd_page_alloc bluetooth mei_me 
snd_seq_midi snd_seq_midi_event mei snd_rawmidi snd_seq snd_seq_device 
snd_timer snd mac_hid soundcore lp parport btrfs xor raid6_pq libc
rc32c dm_crypt rtsx_pci_sdmmc i915 crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd i2c_algo_bit drm_kms_helper ahci e1000e libahci drm rtsx_pci 
ptp pps_core wmi video
Mar 21 14:17:49 RedTail kernel: [58101.988405] CPU: 7 PID: 19627 Comm: chrome 
Not tainted 3.13.0-18-generic #38-Ubuntu
Mar 21 14:17:49 RedTail kernel: [58101.988424] Hardware name: System76, Inc. 
Galago UltraPro/Galago UltraPro, BIOS 4.6.5 07/09/2013
Mar 21 14:17:49 RedTail kernel: [58101.988456] task: 88003e62c7d0 ti: 
8802d47c6000 task.ti: 8802d47c6000
Mar 21 14:17:49 RedTail kernel: [58101.988476] RIP: 0010:[]  
[] swiotlb_tbl_map_single+0x28d/0x2a0
Mar 21 14:17:49 RedTail kernel: [58101.988503] RSP: 0018:8802d47c7a70  
EFLAGS: 00010246
Mar 21 14:17:49 RedTail kernel: [58101.988517] RAX:  RBX: 
 RCX: 
Mar 21 14:17:49 RedTail kernel: [58101.988535] RDX: 00058000 RSI: 
d4abd000 RDI: 
Mar 21 14:17:49 RedTail kernel: [58101.988553] RBP: 8802d47c7ad0 R08: 
 R09: 880402f726d0
Mar 21 14:17:49 RedTail kernel: [58101.988571] R10: 1ea06000 R11: 
0062 R12: 880409239098
Mar 21 14:17:49 RedTail kernel: [58101.988589] R13: 0001 R14: 
1600 R15: 0020
Mar 21 14:17:49 RedTail kernel: [58101.988607] FS:  7fa8d07d5a00() 
GS:88041fbc() knlGS:
Mar 21 14:17:49 RedTail kernel: [58101.988627] CS:  0010 DS:  ES:  CR0: 
80050033
Mar 21 14:17:49 RedTail kernel: [58101.988642] CR2: 2f6213eea004 CR3: 
000362cb9000 CR4: 001407e0
Mar 21 14:17:49 RedTail kernel: [58101.988660] Stack:
Mar 21 14:17:49 RedTail kernel: [58101.988667]  1fa944c0 
00058000 88039dff9e40 
Mar 21 14:17:49 RedTail kernel: [58101.988691]  880409239098 
 001a957a 
Mar 21 14:17:49 RedTail kernel: [58101.988723]  880409239098 
0040 1600 88021bf3f800
Mar 21 14:17:49 RedTail kernel: [58101.988759] Call Trace:
Mar 21 14:17:49 RedTail kernel: [58101.988777]  [] 
swiotlb_map_sg_attrs+0xba/0x150
Mar 21 14:17:49 RedTail kernel: [58101.988820]  [] 
i915_gem_gtt_prepare_object+0x82/0xb0 [i915]
Mar 21 14:17:49 RedTail kernel: [58101.988854]  [] 
i915_gem_object_pin+0x47a/0x720 [i915]
Mar 21 14:17:49 RedTail kernel: [58101.90]  [] 
i915_gem_execbuffer_reserve_vma.isra.12+0x6c/0x1e0 [i915]
Mar 21 14:17:49 RedTail kernel: [5810

[Kernel-packages] [Bug 1295483] Re: [i915] kernel BUG at /build/buildd/linux-3.13.0/lib/swiotlb.c:456!

2014-03-20 Thread Chris Halse Rogers
apport information

** Tags added: apport-collected

** Description changed:

  It looks like Chrome's GPU acceleration is very infrequently capable of
  taking down the kernel; I've been running it for a number of weeks and
  only just hit this BUG:
  
  Mar 21 14:17:49 RedTail kernel: [58101.987805] [ cut here 
]
  Mar 21 14:17:49 RedTail kernel: [58101.987823] kernel BUG at 
/build/buildd/linux-3.13.0/lib/swiotlb.c:456!
  Mar 21 14:17:49 RedTail kernel: [58101.987840] invalid opcode:  [#1] SMP 
  Mar 21 14:17:49 RedTail kernel: [58101.987852] Modules linked in: 
hid_magicmouse hidp hid ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs ctr ccm 
xt_conntrack ipt_REJECT overlayfs ip6table_filter ip6_tables ebtable_
  nat ebtables xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp 
bridge stp llc iptable_filter ip_tables x_tables lttng_probe_writeback 
  lttng_probe_workqueue rfcomm bnep lttng_probe_vmscan lttng_probe_udp 
lttng_probe_timer lttng_probe_sunrpc lttng_probe_statedump lttng_probe_sock 
lttng_probe_skb lttng_probe_signal lttng_probe_scsi lttng_probe_sche
  d lttng_probe_rpm lttng_probe_regulator lttng_probe_regmap lttng_probe_rcu 
lttng_probe_random lttng_probe_printk lttng_probe_power lttng_probe_net 
lttng_probe_napi lttng_probe_module lttng_probe_kvm_x86_mmu lttng_
  probe_kvm_x86 lttng_probe_kvm lttng_probe_kmem lttng_probe_jbd2 
lttng_probe_irq lttng_probe_gpio lttng_probe_ext4 lttng_probe_compaction 
lttng_probe_btrfs lttng_probe_block lttng_probe_asoc lttng_types lttng_ring_
  buffer_metadata_mmap_client lttng_ring_buffer_client_mmap_overwrite 
lttng_ring_buffer_client_mmap_discard lttng_ring_buffer_metadata_client 
lttng_ring_buffer_client_overwrite binfmt_misc lttng_ring_buffer_client_d
  iscard lttng_tracer lttng_statedump lttng_ftrace lttng_kprobes 
lttng_lib_ring_buffer lttng_kretprobes joydev nls_iso8859_1 
x86_pkg_temp_thermal intel_powerclamp coretemp arc4 kvm_intel kvm ath9k 
ath9k_common psmou
  se ath9k_hw serio_raw snd_hda_codec_via ath snd_hda_codec_hdmi snd_hda_intel 
mac80211 uvcvideo videobuf2_vmalloc snd_hda_codec videobuf2_memops 
videobuf2_core lpc_ich snd_hwdep snd_pcm videodev cfg80211 rtsx_pci_m
  s memstick dm_multipath scsi_dh ath3k btusb snd_page_alloc bluetooth mei_me 
snd_seq_midi snd_seq_midi_event mei snd_rawmidi snd_seq snd_seq_device 
snd_timer snd mac_hid soundcore lp parport btrfs xor raid6_pq libc
  rc32c dm_crypt rtsx_pci_sdmmc i915 crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd i2c_algo_bit drm_kms_helper ahci e1000e libahci drm rtsx_pci 
  ptp pps_core wmi video
  Mar 21 14:17:49 RedTail kernel: [58101.988405] CPU: 7 PID: 19627 Comm: chrome 
Not tainted 3.13.0-18-generic #38-Ubuntu
  Mar 21 14:17:49 RedTail kernel: [58101.988424] Hardware name: System76, Inc. 
Galago UltraPro/Galago UltraPro, BIOS 4.6.5 07/09/2013
  Mar 21 14:17:49 RedTail kernel: [58101.988456] task: 88003e62c7d0 ti: 
8802d47c6000 task.ti: 8802d47c6000
  Mar 21 14:17:49 RedTail kernel: [58101.988476] RIP: 0010:[] 
 [] swiotlb_tbl_map_single+0x28d/0x2a0
  Mar 21 14:17:49 RedTail kernel: [58101.988503] RSP: 0018:8802d47c7a70  
EFLAGS: 00010246
  Mar 21 14:17:49 RedTail kernel: [58101.988517] RAX:  RBX: 
 RCX: 
  Mar 21 14:17:49 RedTail kernel: [58101.988535] RDX: 00058000 RSI: 
d4abd000 RDI: 
  Mar 21 14:17:49 RedTail kernel: [58101.988553] RBP: 8802d47c7ad0 R08: 
 R09: 880402f726d0
  Mar 21 14:17:49 RedTail kernel: [58101.988571] R10: 1ea06000 R11: 
0062 R12: 880409239098
  Mar 21 14:17:49 RedTail kernel: [58101.988589] R13: 0001 R14: 
1600 R15: 0020
  Mar 21 14:17:49 RedTail kernel: [58101.988607] FS:  7fa8d07d5a00() 
GS:88041fbc() knlGS:
  Mar 21 14:17:49 RedTail kernel: [58101.988627] CS:  0010 DS:  ES:  
CR0: 80050033
  Mar 21 14:17:49 RedTail kernel: [58101.988642] CR2: 2f6213eea004 CR3: 
000362cb9000 CR4: 001407e0
  Mar 21 14:17:49 RedTail kernel: [58101.988660] Stack:
  Mar 21 14:17:49 RedTail kernel: [58101.988667]  1fa944c0 
00058000 88039dff9e40 
  Mar 21 14:17:49 RedTail kernel: [58101.988691]  880409239098 
 001a957a 
  Mar 21 14:17:49 RedTail kernel: [58101.988723]  880409239098 
0040 1600 88021bf3f800
  Mar 21 14:17:49 RedTail kernel: [58101.988759] Call Trace:
  Mar 21 14:17:49 RedTail kernel: [58101.988777]  [] 
swiotlb_map_sg_attrs+0xba/0x150
  Mar 21 14:17:49 RedTail kernel: [58101.988820]  [] 
i915_gem_gtt_prepare_object+0x82/0xb0 [i915]
  Mar 21 14:17:49 RedTail kernel: [58101.988854]  [] 
i915_gem_object_pin+0x47a/0x720 [i915]
  Mar 21 14:1

Re: [Kernel-packages] [Bug 1295483] Re: [i915] kernel BUG at/build/buildd/linux-3.13.0/lib/swiotlb.c:456!

2014-03-21 Thread Chris Halse Rogers
I'm now running the 3.14 rc7 build from there.

However, it'll be difficult to tell if this is fixed or not; I've only 
encountered it once in a couple of weeks' solid use of Chrome.

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

Title:
  [i915] kernel BUG at /build/buildd/linux-3.13.0/lib/swiotlb.c:456!

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  It looks like Chrome's GPU acceleration is very infrequently capable
  of taking down the kernel; I've been running it for a number of weeks
  and only just hit this BUG:

  Mar 21 14:17:49 RedTail kernel: [58101.987805] [ cut here 
]
  Mar 21 14:17:49 RedTail kernel: [58101.987823] kernel BUG at 
/build/buildd/linux-3.13.0/lib/swiotlb.c:456!
  Mar 21 14:17:49 RedTail kernel: [58101.987840] invalid opcode:  [#1] SMP 
  Mar 21 14:17:49 RedTail kernel: [58101.987852] Modules linked in: 
hid_magicmouse hidp hid ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs ctr ccm 
xt_conntrack ipt_REJECT overlayfs ip6table_filter ip6_tables ebtable_
  nat ebtables xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp 
bridge stp llc iptable_filter ip_tables x_tables lttng_probe_writeback 
  lttng_probe_workqueue rfcomm bnep lttng_probe_vmscan lttng_probe_udp 
lttng_probe_timer lttng_probe_sunrpc lttng_probe_statedump lttng_probe_sock 
lttng_probe_skb lttng_probe_signal lttng_probe_scsi lttng_probe_sche
  d lttng_probe_rpm lttng_probe_regulator lttng_probe_regmap lttng_probe_rcu 
lttng_probe_random lttng_probe_printk lttng_probe_power lttng_probe_net 
lttng_probe_napi lttng_probe_module lttng_probe_kvm_x86_mmu lttng_
  probe_kvm_x86 lttng_probe_kvm lttng_probe_kmem lttng_probe_jbd2 
lttng_probe_irq lttng_probe_gpio lttng_probe_ext4 lttng_probe_compaction 
lttng_probe_btrfs lttng_probe_block lttng_probe_asoc lttng_types lttng_ring_
  buffer_metadata_mmap_client lttng_ring_buffer_client_mmap_overwrite 
lttng_ring_buffer_client_mmap_discard lttng_ring_buffer_metadata_client 
lttng_ring_buffer_client_overwrite binfmt_misc lttng_ring_buffer_client_d
  iscard lttng_tracer lttng_statedump lttng_ftrace lttng_kprobes 
lttng_lib_ring_buffer lttng_kretprobes joydev nls_iso8859_1 
x86_pkg_temp_thermal intel_powerclamp coretemp arc4 kvm_intel kvm ath9k 
ath9k_common psmou
  se ath9k_hw serio_raw snd_hda_codec_via ath snd_hda_codec_hdmi snd_hda_intel 
mac80211 uvcvideo videobuf2_vmalloc snd_hda_codec videobuf2_memops 
videobuf2_core lpc_ich snd_hwdep snd_pcm videodev cfg80211 rtsx_pci_m
  s memstick dm_multipath scsi_dh ath3k btusb snd_page_alloc bluetooth mei_me 
snd_seq_midi snd_seq_midi_event mei snd_rawmidi snd_seq snd_seq_device 
snd_timer snd mac_hid soundcore lp parport btrfs xor raid6_pq libc
  rc32c dm_crypt rtsx_pci_sdmmc i915 crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd i2c_algo_bit drm_kms_helper ahci e1000e libahci drm rtsx_pci 
  ptp pps_core wmi video
  Mar 21 14:17:49 RedTail kernel: [58101.988405] CPU: 7 PID: 19627 Comm: chrome 
Not tainted 3.13.0-18-generic #38-Ubuntu
  Mar 21 14:17:49 RedTail kernel: [58101.988424] Hardware name: System76, Inc. 
Galago UltraPro/Galago UltraPro, BIOS 4.6.5 07/09/2013
  Mar 21 14:17:49 RedTail kernel: [58101.988456] task: 88003e62c7d0 ti: 
8802d47c6000 task.ti: 8802d47c6000
  Mar 21 14:17:49 RedTail kernel: [58101.988476] RIP: 0010:[] 
 [] swiotlb_tbl_map_single+0x28d/0x2a0
  Mar 21 14:17:49 RedTail kernel: [58101.988503] RSP: 0018:8802d47c7a70  
EFLAGS: 00010246
  Mar 21 14:17:49 RedTail kernel: [58101.988517] RAX:  RBX: 
 RCX: 
  Mar 21 14:17:49 RedTail kernel: [58101.988535] RDX: 00058000 RSI: 
d4abd000 RDI: 
  Mar 21 14:17:49 RedTail kernel: [58101.988553] RBP: 8802d47c7ad0 R08: 
 R09: 880402f726d0
  Mar 21 14:17:49 RedTail kernel: [58101.988571] R10: 1ea06000 R11: 
0062 R12: 880409239098
  Mar 21 14:17:49 RedTail kernel: [58101.988589] R13: 0001 R14: 
1600 R15: 0020
  Mar 21 14:17:49 RedTail kernel: [58101.988607] FS:  7fa8d07d5a00() 
GS:88041fbc() knlGS:
  Mar 21 14:17:49 RedTail kernel: [58101.988627] CS:  0010 DS:  ES:  
CR0: 80050033
  Mar 21 14:17:49 RedTail kernel: [58101.988642] CR2: 2f6213eea004 CR3: 
000362cb9000 CR4: 001407e0
  Mar 21 14:17:49 RedTail kernel: [58101.988660] Stack:
  Mar 21 14:17:49 RedTail kernel: [58101.988667]  1fa944c0 
00058000 88039dff9e40 
  Mar 21 14:17:49 RedTail kernel: [58101.988691]  880409239098 
 001a957a 
  Mar 21 14:17:49 RedTail kernel: [58101.988723]  880

[Kernel-packages] [Bug 1259237] Re: Hybrid graphics enablement in 12.04.4

2013-12-18 Thread Chris Halse Rogers
Hello Alberto, or anyone else affected,

Accepted nvidia-settings into precise-proposed. The package will build
now and be available at http://launchpad.net/ubuntu/+source/nvidia-
settings/331.20-0ubuntu0.0.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation 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, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

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

** Tags added: verification-needed

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

Title:
  Hybrid graphics enablement in 12.04.4

Status in “bbswitch” package in Ubuntu:
  Invalid
Status in “nvidia-graphics-drivers-173” package in Ubuntu:
  In Progress
Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  In Progress
Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  In Progress
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  In Progress
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  In Progress
Status in “nvidia-prime” package in Ubuntu:
  Invalid
Status in “nvidia-settings” package in Ubuntu:
  In Progress
Status in “screen-resolution-extra” package in Ubuntu:
  Invalid
Status in “bbswitch” source package in Precise:
  In Progress
Status in “nvidia-prime” source package in Precise:
  In Progress
Status in “screen-resolution-extra” source package in Precise:
  In Progress

Bug description:
  SRU request:

  Please accept the following packages in precise-proposed.

  lightdm
  nvidia-prime
  nvidia-graphics-drivers-331
  nvidia-graphics-drivers-331-updates
  nvidia-graphics-drivers-304
  nvidia-graphics-drivers-304-updates
  nvidia-graphics-drivers-173
  nvidia-settings
  screen-resolution-extra
  bbswitch

  
  [Rationale]
  This is the result of the HWE effort to bring power management to systems 
with NVIDIA Optimus.

  [Impact]
  Without this work, we keep both GPUs on all the time, thus heavily impacting 
on battery life. Thanks to this work, it is now possible to easily disable the 
discrete card when raw power is not needed.

  Furthermore nvidia-prime has better hardware detection now, and won't
  try to enable hybrid graphics on desktop systems any more.

  As for the technical details:
  * bbswitch is a backport of the package that now lives in main in 14.04.
  * The actual work happened in lightdm, nvidia-331, nvidia-331-updates, 
nvidia-prime, screen-resolution-extra, and nvidia-settings.
  * nvidia-settings now replaces all the different nvidia-settings flavours, so 
as to reduce the maintainance effort. I patched the app so that it checks the 
driver version (at runtime) and doesn't expose features that older driver 
releases do not support.
  * nvidia-331 and nvidia-331-updates replace 319 and 319-updates. These are 
the new LTS releases by NVIDIA.
  * nvidia-304 and nvidia-304-updates recommend the new nvidia-settings, 
include a security update, and build against the upcoming Linux 3.11 
(lts-saucy).
  * nvidia-173, in addition to being compatible with Linux 3.11 (lts-saucy), 
also introduces transitional packages for 173-updates, as it doesn't make sense 
to maintain a separate -updates flavour any more. 

  
  [Test Case]
  After installing the update, users should be able to boot the system as 
usual, with no regressions of any kind.

  * Systems with a single NVIDIA card: nvidia-prime will detect the
  hardware and do nothing at all on unsupported systems (such as the one
  card use case, or the desktop use case)

  * Systems with NVIDIA Optimus: nvidia-prime will preserve its previous
  behaviour by leaving both GPUs on. Users can launch nvidia-settings
  and switch to the power profile that they need.

  [Regression Potential]
  Low. The new features are enabled only if the user manually selects them.

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

2013-12-18 Thread Chris Halse Rogers
Hello Alberto, or anyone else affected,

Accepted nvidia-graphics-drivers-304-updates into precise-proposed. The
package will build now and be available at
http://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-304-updates/304.116-0ubuntu0.0.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation 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, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

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

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

Title:
  Hybrid graphics enablement in 12.04.4

Status in “bbswitch” package in Ubuntu:
  Invalid
Status in “nvidia-graphics-drivers-173” package in Ubuntu:
  In Progress
Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  In Progress
Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  In Progress
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  In Progress
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  In Progress
Status in “nvidia-prime” package in Ubuntu:
  Invalid
Status in “nvidia-settings” package in Ubuntu:
  In Progress
Status in “screen-resolution-extra” package in Ubuntu:
  Invalid
Status in “bbswitch” source package in Precise:
  In Progress
Status in “nvidia-prime” source package in Precise:
  In Progress
Status in “screen-resolution-extra” source package in Precise:
  In Progress

Bug description:
  SRU request:

  Please accept the following packages in precise-proposed.

  lightdm
  nvidia-prime
  nvidia-graphics-drivers-331
  nvidia-graphics-drivers-331-updates
  nvidia-graphics-drivers-304
  nvidia-graphics-drivers-304-updates
  nvidia-graphics-drivers-173
  nvidia-settings
  screen-resolution-extra
  bbswitch

  
  [Rationale]
  This is the result of the HWE effort to bring power management to systems 
with NVIDIA Optimus.

  [Impact]
  Without this work, we keep both GPUs on all the time, thus heavily impacting 
on battery life. Thanks to this work, it is now possible to easily disable the 
discrete card when raw power is not needed.

  Furthermore nvidia-prime has better hardware detection now, and won't
  try to enable hybrid graphics on desktop systems any more.

  As for the technical details:
  * bbswitch is a backport of the package that now lives in main in 14.04.
  * The actual work happened in lightdm, nvidia-331, nvidia-331-updates, 
nvidia-prime, screen-resolution-extra, and nvidia-settings.
  * nvidia-settings now replaces all the different nvidia-settings flavours, so 
as to reduce the maintainance effort. I patched the app so that it checks the 
driver version (at runtime) and doesn't expose features that older driver 
releases do not support.
  * nvidia-331 and nvidia-331-updates replace 319 and 319-updates. These are 
the new LTS releases by NVIDIA.
  * nvidia-304 and nvidia-304-updates recommend the new nvidia-settings, 
include a security update, and build against the upcoming Linux 3.11 
(lts-saucy).
  * nvidia-173, in addition to being compatible with Linux 3.11 (lts-saucy), 
also introduces transitional packages for 173-updates, as it doesn't make sense 
to maintain a separate -updates flavour any more. 

  
  [Test Case]
  After installing the update, users should be able to boot the system as 
usual, with no regressions of any kind.

  * Systems with a single NVIDIA card: nvidia-prime will detect the
  hardware and do nothing at all on unsupported systems (such as the one
  card use case, or the desktop use case)

  * Systems with NVIDIA Optimus: nvidia-prime will preserve its previous
  behaviour by leaving both GPUs on. Users can launch nvidia-settings
  and switch to the power profile that they need.

  [Regression Potential]
  Low. The new features are enabled only if the user manually selects them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1259237/+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 1259237] Re: Hybrid graphics enablement in 12.04.4

2013-12-18 Thread Chris Halse Rogers
Hello Alberto, or anyone else affected,

Accepted screen-resolution-extra into precise-proposed. The package will
build now and be available at http://launchpad.net/ubuntu/+source
/screen-resolution-extra/0.14ubuntu2.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation 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, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

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

** Changed in: screen-resolution-extra (Ubuntu Precise)
   Status: In Progress => Fix Committed

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

Title:
  Hybrid graphics enablement in 12.04.4

Status in “bbswitch” package in Ubuntu:
  Invalid
Status in “lightdm” package in Ubuntu:
  In Progress
Status in “nvidia-graphics-drivers-173” package in Ubuntu:
  In Progress
Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  In Progress
Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  In Progress
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  In Progress
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  In Progress
Status in “nvidia-prime” package in Ubuntu:
  Invalid
Status in “nvidia-settings” package in Ubuntu:
  In Progress
Status in “screen-resolution-extra” package in Ubuntu:
  Invalid
Status in “bbswitch” source package in Precise:
  In Progress
Status in “nvidia-prime” source package in Precise:
  In Progress
Status in “screen-resolution-extra” source package in Precise:
  Fix Committed

Bug description:
  SRU request:

  Please accept the following packages in precise-proposed.

  lightdm
  nvidia-prime
  nvidia-graphics-drivers-331
  nvidia-graphics-drivers-331-updates
  nvidia-graphics-drivers-304
  nvidia-graphics-drivers-304-updates
  nvidia-graphics-drivers-173
  nvidia-settings
  screen-resolution-extra
  bbswitch

  
  [Rationale]
  This is the result of the HWE effort to bring power management to systems 
with NVIDIA Optimus.

  [Impact]
  Without this work, we keep both GPUs on all the time, thus heavily impacting 
on battery life. Thanks to this work, it is now possible to easily disable the 
discrete card when raw power is not needed.

  Furthermore nvidia-prime has better hardware detection now, and won't
  try to enable hybrid graphics on desktop systems any more.

  As for the technical details:
  * bbswitch is a backport of the package that now lives in main in 14.04.
  * The actual work happened in lightdm, nvidia-331, nvidia-331-updates, 
nvidia-prime, screen-resolution-extra, and nvidia-settings.
  * nvidia-settings now replaces all the different nvidia-settings flavours, so 
as to reduce the maintainance effort. I patched the app so that it checks the 
driver version (at runtime) and doesn't expose features that older driver 
releases do not support.
  * nvidia-331 and nvidia-331-updates replace 319 and 319-updates. These are 
the new LTS releases by NVIDIA.
  * nvidia-304 and nvidia-304-updates recommend the new nvidia-settings, 
include a security update, and build against the upcoming Linux 3.11 
(lts-saucy).
  * nvidia-173, in addition to being compatible with Linux 3.11 (lts-saucy), 
also introduces transitional packages for 173-updates, as it doesn't make sense 
to maintain a separate -updates flavour any more. 

  
  [Test Case]
  After installing the update, users should be able to boot the system as 
usual, with no regressions of any kind.

  * Systems with a single NVIDIA card: nvidia-prime will detect the
  hardware and do nothing at all on unsupported systems (such as the one
  card use case, or the desktop use case)

  * Systems with NVIDIA Optimus: nvidia-prime will preserve its previous
  behaviour by leaving both GPUs on. Users can launch nvidia-settings
  and switch to the power profile that they need.

  [Regression Potential]
  Low. The new features are enabled only if the user manually selects them.

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

2013-12-18 Thread Chris Halse Rogers
Hello Alberto, or anyone else affected,

Accepted lightdm into precise-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/lightdm/1.2.3-0ubuntu2.4 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 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, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

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

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

Title:
  Hybrid graphics enablement in 12.04.4

Status in “bbswitch” package in Ubuntu:
  Invalid
Status in “lightdm” package in Ubuntu:
  In Progress
Status in “nvidia-graphics-drivers-173” package in Ubuntu:
  In Progress
Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  In Progress
Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  In Progress
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  In Progress
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  In Progress
Status in “nvidia-prime” package in Ubuntu:
  Invalid
Status in “nvidia-settings” package in Ubuntu:
  In Progress
Status in “screen-resolution-extra” package in Ubuntu:
  Invalid
Status in “bbswitch” source package in Precise:
  In Progress
Status in “nvidia-prime” source package in Precise:
  In Progress
Status in “screen-resolution-extra” source package in Precise:
  Fix Committed

Bug description:
  SRU request:

  Please accept the following packages in precise-proposed.

  lightdm
  nvidia-prime
  nvidia-graphics-drivers-331
  nvidia-graphics-drivers-331-updates
  nvidia-graphics-drivers-304
  nvidia-graphics-drivers-304-updates
  nvidia-graphics-drivers-173
  nvidia-settings
  screen-resolution-extra
  bbswitch

  
  [Rationale]
  This is the result of the HWE effort to bring power management to systems 
with NVIDIA Optimus.

  [Impact]
  Without this work, we keep both GPUs on all the time, thus heavily impacting 
on battery life. Thanks to this work, it is now possible to easily disable the 
discrete card when raw power is not needed.

  Furthermore nvidia-prime has better hardware detection now, and won't
  try to enable hybrid graphics on desktop systems any more.

  As for the technical details:
  * bbswitch is a backport of the package that now lives in main in 14.04.
  * The actual work happened in lightdm, nvidia-331, nvidia-331-updates, 
nvidia-prime, screen-resolution-extra, and nvidia-settings.
  * nvidia-settings now replaces all the different nvidia-settings flavours, so 
as to reduce the maintainance effort. I patched the app so that it checks the 
driver version (at runtime) and doesn't expose features that older driver 
releases do not support.
  * nvidia-331 and nvidia-331-updates replace 319 and 319-updates. These are 
the new LTS releases by NVIDIA.
  * nvidia-304 and nvidia-304-updates recommend the new nvidia-settings, 
include a security update, and build against the upcoming Linux 3.11 
(lts-saucy).
  * nvidia-173, in addition to being compatible with Linux 3.11 (lts-saucy), 
also introduces transitional packages for 173-updates, as it doesn't make sense 
to maintain a separate -updates flavour any more. 

  
  [Test Case]
  After installing the update, users should be able to boot the system as 
usual, with no regressions of any kind.

  * Systems with a single NVIDIA card: nvidia-prime will detect the
  hardware and do nothing at all on unsupported systems (such as the one
  card use case, or the desktop use case)

  * Systems with NVIDIA Optimus: nvidia-prime will preserve its previous
  behaviour by leaving both GPUs on. Users can launch nvidia-settings
  and switch to the power profile that they need.

  [Regression Potential]
  Low. The new features are enabled only if the user manually selects them.

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

2014-02-04 Thread Chris Halse Rogers
Hello michaelcole, or anyone else affected,

Accepted linux-firmware into saucy-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/linux-
firmware/1.116.2 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 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, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

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

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

Title:
  /lib/firmware/iwlwifi-7260-7.ucode is the wrong version

Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux” source package in Saucy:
  Fix Committed

Bug description:
  Hi, I ran into a bug that made wifi unstable on my Lenovo Ideapad
  Y710.  I needed to disable/reenable networking about every 5 minutes.
  I was able to get some connectivity, but obviously, this is a pain in
  the ass.

  After working with the awesome support folks at Intel, I think we
  isolated the problem and solution.

  The problem likely affects all laptops with the Intel(R) Wireless 7260
  chipset.

  The solution is to use updated firmware from here:
  http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-
  
firmware.git/plain/iwlwifi-7260-7.ucode?id=824994715e0276e64cdbf2badbe02921a78fb287

  Just replace the /lib/firmware/iwlwifi-7260-7.ucode binary with the new
  one.

  Below is the last email I got from Luca at ilw at linux.intel.com - if
  you have questions, they know the technical details to the solution.
  Thanks again!

  Mike

  --

  Hi Mike,

  My colleague noticed that you are using an older version of the firmware
  which contains a bug that may be the cause of the problem you're seeing.

  We have pushed a new firmware (with a fix for this) to the
  linux-firmware.git repository.  You can get it here:

  http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-
  
firmware.git/plain/iwlwifi-7260-7.ucode?id=824994715e0276e64cdbf2badbe02921a78fb287

  Just replace the /lib/firmware/iwlwifi-7260-7.ucode binary with the new
  one.

  I checked Ubuntu's packages and it seems that they only updated to the
  new one in the linux-firmware 1.122 package (for trusty).  Ubuntu Saucy
  (13.10) still has the old version in the linux-firmware 1.116 package.
  It would be nice if someone would poke Ubuntu to add 1.122 to the
  saucy-updates or something.  I believe Linux Mint is following Ubuntu in
  this case.

  I hope this helps!

  (And thanks to Emmanuel for the help ;)

  --
  Cheers,
  Luca.
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  michael2173 F pulseaudio
   /dev/snd/controlC0:  michael2173 F pulseaudio
  DistroRelease: Ubuntu 13.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=6ca2b9e3-fdd0-434e-b92a-06c69c90ca9b
  InstallationDate: Installed on 2013-12-25 (36 days ago)
  InstallationMedia: Linux Mint 16 "petra" - Release amd64 20131126
  MachineType: LENOVO 20250
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=dccd14b6-5933-476f-b0f0-3175e5cd454a ro quiet splash
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-12-generic N/A
   linux-backports-modules-3.11.0-12-generic  N/A
   linux-firmware 1.116
  Tags:  petra
  Uname: Linux 3.11.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 09/02/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7FCN35WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Durian 7A1
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193Std
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z710
  dmi.modalias: 
dmi:bvnLENOVO:bvr7FCN35WW:bd09/02/2013:svnLENOVO:pn20250:pvrLenovoZ710:rvnLENOVO:rnDurian7A1:rvr3193Std:cvnLENOVO:ct10:cvrLenovoIdeaPadZ710:
  dmi.product.name: 20250

  1   2   >