[Kernel-packages] [Bug 1869235] Re: Ryzen 3rd gen (3900X) ECC support missing from kernel

[Alex Hung]

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

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

Title:
  Ryzen 3rd gen (3900X) ECC support missing from kernel

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  Ubuntu server:
  Description:Ubuntu 19.10
  Release:19.10
  Installed kernel:
  linux-generic:
Installed: 5.3.0.42.36
  (I could not figure out what package to select in the 'in what package did 
you find this bug' chooser)

  Expected behavior: ECC RAM is detected and utilized
  Result instead:
  Error in dmesg at boot:
  EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?) (more in the 
attached KernelErrors.log)

  Kernel 5.3 is missing ECC support for some families of AMD Ryzen 3rd
  gen CPUs.

  Support is added via these two commits in the mainline tree:
  
https://github.com/torvalds/linux/commit/e53a3b267fb0a79db9ca1f1e08b97889b22013e6
  
https://github.com/torvalds/linux/commit/3e443eb353eda6f4b4796e07f2599683fa752f1d

  The second commit actually adds the missing support, but it relies on
  the first commit: a partial refactor of the AMD ECC code.

  I tested myself, followed the instructions at 
https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel to build my own kernel, 
cherry-picked the two above commits, and have working ECC support on my 
self-built kernel:
  Linux smaug 5.3.0-43-generic #36 SMP Sat Mar 21 02:33:30 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux:

  EDAC MC: Ver: 3.0.0
  EDAC amd64: Node 0: DRAM ECC enabled.
  EDAC amd64: F17h_M70h detected (node 0).
  EDAC MC: UMC0 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC MC: UMC1 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC amd64: using x16 syndromes.
  EDAC amd64: MCT channel count: 2
  EDAC MC0: Giving out device to module amd64_edac controller F17h_M70h: DEV 
:00:18.3 (INTERRUPT)
  EDAC PCI0: Giving out device to module amd64_edac controller EDAC PCI 
controller: DEV :00:18.0 (POLLED)
  AMD64 EDAC driver v3.5.0

  
  If this could be included in a future hardware support kernel release, that 
would be very helpful.  I am unsure what the policy is for including this kind 
of backport in non-LTS kernels, though I know the LTS releases have hardware 
support updates that include this type of fix.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-03-20 (6 days ago)
  InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=89cfcc61-dbca-43d3-9a2e-5961df9ae5b4 ro
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  RfKill:
   
  Tags:  eoan uec-images
  Uname: Linux 5.3.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lxd plugdev sudo
  _MarkForUpload: False
  dmi.bios.date: 10/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.30
  dmi.board.name: X470D4U2-2T
  dmi.board.vendor: ASRockRack
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd10/03/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRockRack:rnX470D4U2-2T:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1871248] Re: amdgpu kernel errors in Linux 5.4

[Alex Hung]

The errors (or warnings) are generated by ASSERT like the following
statement.

if (!i2c_success)
   /* Write failure */
   ASSERT(i2c_success);

Details @
https://elixir.bootlin.com/linux/v5.4.31/source/drivers/gpu/drm/amd/display/dc/core/dc_link.c#L1737

I am not an amdgpu expert but I don't think they are harmful but are
indication that one feature in amdgpu does not work.

If this really bugs you, I can backport a fix that silences the ASSERTs
but outputs "simple log message" in uptream kernel. See following for
details.

commit a0e40018dcc3f59a10ca21d58f8ea8ceb1b035ac
Author: Rodrigo Siqueira 
Date:   Mon Feb 24 10:13:37 2020 -0500

drm/amd/display: Stop if retimer is not available

Raven provides retimer feature support that requires i2c interaction in
order to make it work well, all settings required for this configuration
are loaded from the Atom bios which include the i2c address. If the
retimer feature is not available, we should abort the attempt to set
this feature, otherwise, it makes the following line return
I2C_CHANNEL_OPERATION_NO_RESPONSE:

... // skipped

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

Title:
  amdgpu kernel errors in Linux 5.4

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux atlas 5.4.0-21-generic #25-Ubuntu SMP Sat Mar 28 13:10:28 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux
  Ubuntu 20.04 beta fresh installation. Upgrades applied.
  AMD Ryzen 3 3200G with Radeon Vega Graphics
  Motherboard: Gigabyte B450 I AORUS PRO WIFI/B450 I AORUS PRO WIFI-CF, BIOS 
F50 11/27/2019

  These errors keep appearing in the kernel messages. 
  [3.258890] [ cut here ]
  [3.258944] WARNING: CPU: 1 PID: 621 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link.c:1737 
write_i2c_retimer_setting+0xc8/0x3e0 [amdgpu]
  [3.258945] Modules linked in: amd64_edac_mod(-) cmac algif_hash 
algif_skcipher af_alg bnep edac_mce_amd ccp kvm snd_hda_codec_realtek 
snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel 
snd_intel_nhlt snd_hda_codec snd_hda_core snd_hwdep snd_pcm crct10dif_pclmul 
ghash_clmulni_intel snd_seq_midi nls_iso8859_1 snd_seq_midi_event snd_rawmidi 
snd_seq aesni_intel iwlmvm crypto_simd mac80211 amdgpu cryptd libarc4 
glue_helper snd_seq_device amd_iommu_v2 btusb iwlwifi gpu_sched btrtl wmi_bmof 
ttm btbcm k10temp snd_timer btintel input_leds drm_kms_helper bluetooth snd 
fb_sys_fops syscopyarea cfg80211 sysfillrect soundcore sysimgblt ecdh_generic 
ecc mac_hid sch_fq_codel parport_pc ppdev lp drm parport ip_tables x_tables 
autofs4 hid_generic usbhid hid nvme crc32_pclmul i2c_piix4 ahci igb nvme_core 
i2c_algo_bit dca libahci wmi video gpio_amdpt gpio_generic
  [3.258966] CPU: 1 PID: 621 Comm: gpu-manager Not tainted 5.4.0-21-generic 
#25-Ubuntu
  [3.258967] Hardware name: Gigabyte Technology Co., Ltd. B450 I AORUS PRO 
WIFI/B450 I AORUS PRO WIFI-CF, BIOS F50 11/27/2019
  [3.259012] RIP: 0010:write_i2c_retimer_setting+0xc8/0x3e0 [amdgpu]

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kirt   1293 F pulseaudio
   /dev/snd/controlC0:  kirt   1293 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  6 15:52:30 2020
  InstallationDate: Installed on 2020-04-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Gigabyte Technology Co., Ltd. B450 I AORUS PRO WIFI
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=9940ba5b-7683-413e-92a2-854b3816799b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 I AORUS PRO WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450IAORUSPROWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450IAORUSPROWIFI-CF:rvrx.x:cvnDefaultstring:ct3:

[Kernel-packages] [Bug 1871248] Re: amdgpu kernel errors in Linux 5.4

[Alex Hung]

A kernel, based on Ubuntu-5.4.0-21.25 + a0e40018dcc3f, is available for
testing @ https://people.canonical.com/~alexhung/LP1871248/

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

Title:
  amdgpu kernel errors in Linux 5.4

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux atlas 5.4.0-21-generic #25-Ubuntu SMP Sat Mar 28 13:10:28 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux
  Ubuntu 20.04 beta fresh installation. Upgrades applied.
  AMD Ryzen 3 3200G with Radeon Vega Graphics
  Motherboard: Gigabyte B450 I AORUS PRO WIFI/B450 I AORUS PRO WIFI-CF, BIOS 
F50 11/27/2019

  These errors keep appearing in the kernel messages. 
  [3.258890] [ cut here ]
  [3.258944] WARNING: CPU: 1 PID: 621 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link.c:1737 
write_i2c_retimer_setting+0xc8/0x3e0 [amdgpu]
  [3.258945] Modules linked in: amd64_edac_mod(-) cmac algif_hash 
algif_skcipher af_alg bnep edac_mce_amd ccp kvm snd_hda_codec_realtek 
snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel 
snd_intel_nhlt snd_hda_codec snd_hda_core snd_hwdep snd_pcm crct10dif_pclmul 
ghash_clmulni_intel snd_seq_midi nls_iso8859_1 snd_seq_midi_event snd_rawmidi 
snd_seq aesni_intel iwlmvm crypto_simd mac80211 amdgpu cryptd libarc4 
glue_helper snd_seq_device amd_iommu_v2 btusb iwlwifi gpu_sched btrtl wmi_bmof 
ttm btbcm k10temp snd_timer btintel input_leds drm_kms_helper bluetooth snd 
fb_sys_fops syscopyarea cfg80211 sysfillrect soundcore sysimgblt ecdh_generic 
ecc mac_hid sch_fq_codel parport_pc ppdev lp drm parport ip_tables x_tables 
autofs4 hid_generic usbhid hid nvme crc32_pclmul i2c_piix4 ahci igb nvme_core 
i2c_algo_bit dca libahci wmi video gpio_amdpt gpio_generic
  [3.258966] CPU: 1 PID: 621 Comm: gpu-manager Not tainted 5.4.0-21-generic 
#25-Ubuntu
  [3.258967] Hardware name: Gigabyte Technology Co., Ltd. B450 I AORUS PRO 
WIFI/B450 I AORUS PRO WIFI-CF, BIOS F50 11/27/2019
  [3.259012] RIP: 0010:write_i2c_retimer_setting+0xc8/0x3e0 [amdgpu]

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kirt   1293 F pulseaudio
   /dev/snd/controlC0:  kirt   1293 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  6 15:52:30 2020
  InstallationDate: Installed on 2020-04-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Gigabyte Technology Co., Ltd. B450 I AORUS PRO WIFI
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=9940ba5b-7683-413e-92a2-854b3816799b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 I AORUS PRO WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450IAORUSPROWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450IAORUSPROWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450 I AORUS PRO WIFI
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1861925] Re: BrightnessOutofRange: Actual brightness for amdgpu_bl0 not in range 0..255

[Alex Hung]

Kernel 5.7rc1 is released, and it can be downloaded @
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc1/

There are some changes related to amd backlight from 5.6 to 5.7rc1 such
as the following (list may be not completed), and it surely worthwhile
to give 5.7rc1 a try.

accde06fcb7fd82abdfa77ecf4dc63d724a6d9bf
945628101be55833a63355510d4b6c934183deab
8a683eb6311a03b655ab8ff368cd7b203074275c
cb8348fec250e517b5facb4cab3125ddc597f9aa

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

Title:
  BrightnessOutofRange: Actual brightness for amdgpu_bl0 not in range
  0..255

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I have a acer aspire a315-41 laptop, it has BIOS 1.15, Ubuntu 19.10,
  Kernel stock 5.3, and 5.5.0. I have a problem with the Backlight. I
  can not control.

  According to: https://wiki.ubuntu.com/Kernel/Debugging/Backlight

  It is : Backlight control does not work, but there are entries in
  /sys/class/backlight.

  The problem is as far I could find:

  sanya@Aspire-A315-41:/sys/class/backlight/amdgpu_bl0$ cat brightness
  135
  sanya@Aspire-A315-41:/sys/class/backlight/amdgpu_bl0$ cat actual_brightness
  43500
  sanya@Aspire-A315-41:/sys/class/backlight/amdgpu_bl0$ cat max_brightness
  255

  The brightness read from the HW is not in the range, and when I change
  the brightness by the keys the value in the brightness file changes
  too, but the actual_brightness is stuck at the value 43500...

  I have tried all the steps mentioned in
  https://wiki.ubuntu.com/Kernel/Debugging/Backlight

  Actually I have tried all these kernel startup parameter variants
  without luck:

  GRUB_CMDLINE_LINUX_DEFAULT=""
  #GRUB_CMDLINE_LINUX_DEFAULT="video.use_native_backlight=1"
  #GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi="
  #GRUB_CMDLINE_LINUX_DEFAULT="video.use_bios_initial_backlight=0"
  #GRUB_CMDLINE_LINUX_DEFAULT="amdgpu.dcfeaturemask=0x4 amdgpu.abmlevel=2"
  #GRUB_CMDLINE_LINUX_DEFAULT="acpi_backlight=video amdgpu.abmlevel=1"
  #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=Linux acpi_backlight=vendor"
  #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=! acpi_osi=\"Windows 2009\" 
acpi_backlight=vendor"
  #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=! acpi_osi=\"Windows 2009\" 
acpi_backlight=video"
  #GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=! acpi_osi=\"Windows 2009\" 
acpi_backlight=vendor"
  #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=! acpi_osi=\"Windows 2009\" 
acpi_backlight=vendor"
  #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=! acpi_osi=\"Windows 2009\" 
acpi_backlight=vendor"

  I guess the fwts has found also this as an error:

  autobrightness: Automated LCD brightness test.
  

  Test 1 of 2: Test for maximum and actual brightness.
  PASSED: Test 1, Maximum brightness for amdgpu_bl0 is 255 which is sane.
  FAILED [HIGH] BrightnessOutofRange: Test 1, Actual brightness for amdgpu_bl0 
not
  in range 0..255.

  Test 2 of 2: Change actual brightness.
  FAILED [MEDIUM] BrightnessMismatch: Test 2, 256 brightness levels did not 
match
  the brightnesss level just set for backlight amdgpu_bl0.
  The failed brightness levels were: 0-255.

  It would be great if someone could help set the HW brightness back to
  the normal range.

  If you need any more debug files please let me know!

  Thanks,
  Regards,
  Sandor

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

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

[Kernel-packages] [Bug 1871248] Re: amdgpu kernel errors in Linux 5.4

[Alex Hung]

A SRU was sent for reviewing. Your help will be needed to test proposed
kernel before next kernel updates later.

This patch is contained in kernel 5.7 rc1 and it is likely to be
included in next Ubuntu release without backporting.

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

Title:
  amdgpu kernel errors in Linux 5.4

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux atlas 5.4.0-21-generic #25-Ubuntu SMP Sat Mar 28 13:10:28 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux
  Ubuntu 20.04 beta fresh installation. Upgrades applied.
  AMD Ryzen 3 3200G with Radeon Vega Graphics
  Motherboard: Gigabyte B450 I AORUS PRO WIFI/B450 I AORUS PRO WIFI-CF, BIOS 
F50 11/27/2019

  These errors keep appearing in the kernel messages. 
  [3.258890] [ cut here ]
  [3.258944] WARNING: CPU: 1 PID: 621 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link.c:1737 
write_i2c_retimer_setting+0xc8/0x3e0 [amdgpu]
  [3.258945] Modules linked in: amd64_edac_mod(-) cmac algif_hash 
algif_skcipher af_alg bnep edac_mce_amd ccp kvm snd_hda_codec_realtek 
snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel 
snd_intel_nhlt snd_hda_codec snd_hda_core snd_hwdep snd_pcm crct10dif_pclmul 
ghash_clmulni_intel snd_seq_midi nls_iso8859_1 snd_seq_midi_event snd_rawmidi 
snd_seq aesni_intel iwlmvm crypto_simd mac80211 amdgpu cryptd libarc4 
glue_helper snd_seq_device amd_iommu_v2 btusb iwlwifi gpu_sched btrtl wmi_bmof 
ttm btbcm k10temp snd_timer btintel input_leds drm_kms_helper bluetooth snd 
fb_sys_fops syscopyarea cfg80211 sysfillrect soundcore sysimgblt ecdh_generic 
ecc mac_hid sch_fq_codel parport_pc ppdev lp drm parport ip_tables x_tables 
autofs4 hid_generic usbhid hid nvme crc32_pclmul i2c_piix4 ahci igb nvme_core 
i2c_algo_bit dca libahci wmi video gpio_amdpt gpio_generic
  [3.258966] CPU: 1 PID: 621 Comm: gpu-manager Not tainted 5.4.0-21-generic 
#25-Ubuntu
  [3.258967] Hardware name: Gigabyte Technology Co., Ltd. B450 I AORUS PRO 
WIFI/B450 I AORUS PRO WIFI-CF, BIOS F50 11/27/2019
  [3.259012] RIP: 0010:write_i2c_retimer_setting+0xc8/0x3e0 [amdgpu]

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kirt   1293 F pulseaudio
   /dev/snd/controlC0:  kirt   1293 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  6 15:52:30 2020
  InstallationDate: Installed on 2020-04-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Gigabyte Technology Co., Ltd. B450 I AORUS PRO WIFI
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=9940ba5b-7683-413e-92a2-854b3816799b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 I AORUS PRO WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450IAORUSPROWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450IAORUSPROWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450 I AORUS PRO WIFI
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1872462] Re: rtl8723de wifi and bluetooth not working simultaneously

[Alex Hung]

If you still have older kernels, it would be helpful to identify which
previous kernel does not have this problem. See
https://askubuntu.com/questions/82140/how-can-i-boot-with-an-older-
kernel-version/584738#584738

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

Title:
  rtl8723de wifi and bluetooth not working simultaneously

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  RTL8723DE wifi+bluetooth adapter works only with one of the two
  components enabled. This is a common bug encountered in all distros
  after installing dkms module from lwfinger/rtlwifi_new repo. Ubuntu
  20.04 fixed this in previous kernel releases (only distribution to do
  so) and gave support for rtl8723de out of the box. Unfortunately, Bug
  shows up again after doing sudo apt dist-upgrade. I presume this is a
  kernel issue, as a new version was released recently. Since then,
  bluetooth is able to scan for devices but cannot connect if wifi is
  enabled first and vice versa.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seba   1449 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Mon Apr 13 09:31:54 2020
  InstallationDate: Installed on 2020-04-07 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN 
Adapter
   Bus 001 Device 002: ID 04f2:b5d5 Chicony Electronics Co., Ltd HP TrueVision 
HD Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Laptop 14-bs0xx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=10f9e70b-7750-4172-9b6f-9c1647d6e763 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.32
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 831C
  dmi.board.vendor: HP
  dmi.board.version: 17.42
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.32:bd02/26/2018:svnHP:pnHPLaptop14-bs0xx:pvrType1ProductConfigId:rvnHP:rn831C:rvr17.42:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 14-bs0xx
  dmi.product.sku: 2RH45LA#AKH
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1872408] Re: Network lost after long sleep

[Alex Hung]

@moreje,

Did you try re-initialize the NIC driver with following commands?

sudo modprobe -r e1000e && sudo modprobe e1000e

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

Title:
  Network lost after long sleep

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  After a long time in sleep mode, my Desktop running Ubuntu 20.04 loses its 
network ethernet link.
  the demsg shows the following lines after sleep exit:

  [10402.613687] PM: suspend exit
  [10403.035311] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
  [10403.121362] ata1.00: configured for UDMA/133
  [10403.363882] e1000e: enp0s25 NIC Link is Down
  [10406.484276] e1000e: enp0s25 NIC Link is Up 10 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [10406.484281] e1000e :00:19.0 enp0s25: 10/100 speed: disabling TSO
  [10406.484322] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s25: link becomes ready

  the ethernet is up but at 10 M / full duplex
  DHCP of my router does not give any address.

  the only way to retrieve a Full 1000 M functionnal link is to reboot
  the machine.

  Can't determine how much time of sleep it needs to reproduce, since an
  immediate sleep/wake-up does not produce network loss.

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

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

[Kernel-packages] [Bug 1872351] Re: Disabling wifi causes kernel error

[Alex Hung]

This is a warning message generated by sta_info.c (See details @
https://elixir.bootlin.com/linux/v5.4.32/source/net/mac80211/sta_info.c#L1059)

Does your wifi return to normal after disabling and enabling?

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

Title:
  Disabling wifi causes kernel error

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have multiple issues with wifi on my Dell XPS 9380.
  This error was triggered when I tried to disable my wifi.

  [ 3634.322471] [ cut here ]
  [ 3634.322524] WARNING: CPU: 3 PID: 1188 at net/mac80211/sta_info.c:1057 
__sta_info_destroy_part2+0x14e/0x160 [mac80211]
  [ 3634.322525] Modules linked in: rfcomm vboxnetadp(OE) vboxnetflt(OE) 
vboxdrv(OE) ccm typec_displayport cmac algif_hash algif_skcipher af_alg bnep 
binfmt_misc nls_iso8859_1 mei_hdcp intel_rapl_msr snd_hda_codec_hdmi 
dell_laptop snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio 
snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core snd_usb_audio 
ath10k_pci x86_pkg_temp_thermal snd_usbmidi_lib snd_seq_midi snd_hwdep 
snd_seq_midi_event ath10k_core intel_powerclamp coretemp cdc_ether snd_rawmidi 
usbnet btusb kvm_intel r8152 ath btrtl mii btbcm kvm snd_seq uvcvideo 
videobuf2_vmalloc btintel videobuf2_memops intel_cstate videobuf2_v4l2 joydev 
snd_seq_device snd_pcm dell_wmi intel_rapl_perf videobuf2_common bluetooth 
mac80211 dell_smbios videodev snd_timer dcdbas mc input_leds ecdh_generic ecc 
wmi_bmof snd dell_wmi_descriptor serio_raw intel_wmi_thunderbolt cfg80211 
soundcore rtsx_pci_ms libarc4 memstick hid_multitouch processor_thermal_device 
ucsi_acpi typec_ucsi mei_me intel_rapl_common
  [ 3634.322564]  intel_xhci_usb_role_switch mei typec intel_soc_dts_iosf 
intel_pch_thermal roles int3403_thermal int340x_thermal_zone int3400_thermal 
mac_hid acpi_pad intel_hid acpi_thermal_rel sparse_keymap sch_fq_codel 
parport_pc ppdev lp parport ip_tables x_tables autofs4 mmc_block dm_crypt 
usbhid hid_generic crct10dif_pclmul crc32_pclmul rtsx_pci_sdmmc i915 
ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_algo_bit glue_helper 
drm_kms_helper psmouse syscopyarea sysfillrect nvme sysimgblt i2c_i801 
fb_sys_fops nvme_core drm intel_lpss_pci rtsx_pci intel_lpss idma64 i2c_hid 
virt_dma wmi hid pinctrl_sunrisepoint video pinctrl_intel
  [ 3634.322599] CPU: 3 PID: 1188 Comm: NetworkManager Tainted: G   OE  
   5.4.0-21-generic #25-Ubuntu
  [ 3634.322600] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.12.1 
12/11/2019
  [ 3634.322633] RIP: 0010:__sta_info_destroy_part2+0x14e/0x160 [mac80211]
  [ 3634.322635] Code: 24 0c 01 00 00 00 0f 84 52 ff ff ff 45 31 c0 b9 01 00 00 
00 4c 89 e2 48 89 de 4c 89 ef e8 0a a6 ff ff 85 c0 0f 84 34 ff ff ff <0f> 0b e9 
2d ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00
  [ 3634.322636] RSP: 0018:a70c009c3918 EFLAGS: 00010282
  [ 3634.322638] RAX: ff94 RBX: 9006104cc8c0 RCX: 

  [ 3634.322640] RDX: 90061ba3c740 RSI:  RDI: 
900613a62f48
  [ 3634.322641] RBP: a70c009c3938 R08: 90061e4d78c8 R09: 
0004
  [ 3634.322642] R10:  R11:  R12: 
900613f28000
  [ 3634.322643] R13: 900613a607a0 R14: 9006104cc8c0 R15: 
900613a60d68
  [ 3634.322644] FS:  7f596b396240() GS:90061e4c() 
knlGS:
  [ 3634.322645] CS:  0010 DS:  ES:  CR0: 80050033
  [ 3634.322646] CR2: 0db00945f000 CR3: 000494824005 CR4: 
003606e0
  [ 3634.322647] Call Trace:
  [ 3634.322670]  __sta_info_flush+0x128/0x180 [mac80211]
  [ 3634.322696]  ieee80211_set_disassoc+0xc0/0x5f0 [mac80211]
  [ 3634.322719]  ieee80211_mgd_deauth+0x104/0x490 [mac80211]
  [ 3634.322743]  ieee80211_deauth+0x18/0x20 [mac80211]
  [ 3634.322782]  cfg80211_mlme_deauth+0xb6/0x1e0 [cfg80211]
  [ 3634.322804]  cfg80211_mlme_down+0x66/0x80 [cfg80211]
  [ 3634.322823]  cfg80211_disconnect+0x127/0x1e0 [cfg80211]
  [ 3634.322827]  ? _raw_spin_unlock_bh+0x1e/0x20
  [ 3634.322845]  __cfg80211_leave+0x133/0x1b0 [cfg80211]
  [ 3634.322862]  cfg80211_leave+0x2c/0x40 [cfg80211]
  [ 3634.322879]  cfg80211_netdev_notifier_call+0x1b2/0x590 [cfg80211]
  [ 3634.322902]  ? ath10k_warn.cold+0x1a/0x1f [ath10k_core]
  [ 3634.322911]  ? ath10k_config_ps+0x52/0x70 [ath10k_core]
  [ 3634.322913]  ? rtnl_is_locked+0x15/0x20
  [ 3634.322917]  ? inetdev_event+0x47/0x560
  [ 3634.322919]  ? skb_dequeue+0x5a/0x70
  [ 3634.322923]  notifier_call_chain+0x55/0x80
  [ 3634.322925]  raw_notifier_call_chain+0x16/0x20
  [ 3634.322927]  call_netdevice_notifiers_info+0x2e/0x60
  [ 3634.322929]  __dev_close_many+0x63/0x120
  [ 3634.322931]  dev_close_many+0x91/0x150
  [ 3634.322933]  dev_close.part.0+0x4a/0x70
  [ 3634.322936]  dev_close+0x18/0x20
  [ 3634.322955]  cfg80211_shutdown_all_interfaces+0x77/0xd0

[Kernel-packages] [Bug 1872351] Re: Qualcomm Atheros QCA6174 Killer 1435 Wireless-AC: Disabling wifi causes kernel warning in __sta_info_destroy_part2

[Alex Hung]

try "rfkill list" to list all radio devices, such as

$ rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

run "rfkill block 2" to disable it, and "run kill unblock 2" to enable
it, assuming your wifi is also (2).

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

Title:
  Qualcomm Atheros QCA6174 Killer 1435 Wireless-AC: Disabling wifi
  causes kernel warning in __sta_info_destroy_part2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have multiple issues with wifi on my Dell XPS 9380.
  This error was triggered when I tried to disable my wifi.

  [ 3634.322471] [ cut here ]
  [ 3634.322524] WARNING: CPU: 3 PID: 1188 at net/mac80211/sta_info.c:1057 
__sta_info_destroy_part2+0x14e/0x160 [mac80211]
  [ 3634.322525] Modules linked in: rfcomm vboxnetadp(OE) vboxnetflt(OE) 
vboxdrv(OE) ccm typec_displayport cmac algif_hash algif_skcipher af_alg bnep 
binfmt_misc nls_iso8859_1 mei_hdcp intel_rapl_msr snd_hda_codec_hdmi 
dell_laptop snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio 
snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core snd_usb_audio 
ath10k_pci x86_pkg_temp_thermal snd_usbmidi_lib snd_seq_midi snd_hwdep 
snd_seq_midi_event ath10k_core intel_powerclamp coretemp cdc_ether snd_rawmidi 
usbnet btusb kvm_intel r8152 ath btrtl mii btbcm kvm snd_seq uvcvideo 
videobuf2_vmalloc btintel videobuf2_memops intel_cstate videobuf2_v4l2 joydev 
snd_seq_device snd_pcm dell_wmi intel_rapl_perf videobuf2_common bluetooth 
mac80211 dell_smbios videodev snd_timer dcdbas mc input_leds ecdh_generic ecc 
wmi_bmof snd dell_wmi_descriptor serio_raw intel_wmi_thunderbolt cfg80211 
soundcore rtsx_pci_ms libarc4 memstick hid_multitouch processor_thermal_device 
ucsi_acpi typec_ucsi mei_me intel_rapl_common
  [ 3634.322564]  intel_xhci_usb_role_switch mei typec intel_soc_dts_iosf 
intel_pch_thermal roles int3403_thermal int340x_thermal_zone int3400_thermal 
mac_hid acpi_pad intel_hid acpi_thermal_rel sparse_keymap sch_fq_codel 
parport_pc ppdev lp parport ip_tables x_tables autofs4 mmc_block dm_crypt 
usbhid hid_generic crct10dif_pclmul crc32_pclmul rtsx_pci_sdmmc i915 
ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_algo_bit glue_helper 
drm_kms_helper psmouse syscopyarea sysfillrect nvme sysimgblt i2c_i801 
fb_sys_fops nvme_core drm intel_lpss_pci rtsx_pci intel_lpss idma64 i2c_hid 
virt_dma wmi hid pinctrl_sunrisepoint video pinctrl_intel
  [ 3634.322599] CPU: 3 PID: 1188 Comm: NetworkManager Tainted: G   OE  
   5.4.0-21-generic #25-Ubuntu
  [ 3634.322600] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.12.1 
12/11/2019
  [ 3634.322633] RIP: 0010:__sta_info_destroy_part2+0x14e/0x160 [mac80211]
  [ 3634.322635] Code: 24 0c 01 00 00 00 0f 84 52 ff ff ff 45 31 c0 b9 01 00 00 
00 4c 89 e2 48 89 de 4c 89 ef e8 0a a6 ff ff 85 c0 0f 84 34 ff ff ff <0f> 0b e9 
2d ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00
  [ 3634.322636] RSP: 0018:a70c009c3918 EFLAGS: 00010282
  [ 3634.322638] RAX: ff94 RBX: 9006104cc8c0 RCX: 

  [ 3634.322640] RDX: 90061ba3c740 RSI:  RDI: 
900613a62f48
  [ 3634.322641] RBP: a70c009c3938 R08: 90061e4d78c8 R09: 
0004
  [ 3634.322642] R10:  R11:  R12: 
900613f28000
  [ 3634.322643] R13: 900613a607a0 R14: 9006104cc8c0 R15: 
900613a60d68
  [ 3634.322644] FS:  7f596b396240() GS:90061e4c() 
knlGS:
  [ 3634.322645] CS:  0010 DS:  ES:  CR0: 80050033
  [ 3634.322646] CR2: 0db00945f000 CR3: 000494824005 CR4: 
003606e0
  [ 3634.322647] Call Trace:
  [ 3634.322670]  __sta_info_flush+0x128/0x180 [mac80211]
  [ 3634.322696]  ieee80211_set_disassoc+0xc0/0x5f0 [mac80211]
  [ 3634.322719]  ieee80211_mgd_deauth+0x104/0x490 [mac80211]
  [ 3634.322743]  ieee80211_deauth+0x18/0x20 [mac80211]
  [ 3634.322782]  cfg80211_mlme_deauth+0xb6/0x1e0 [cfg80211]
  [ 3634.322804]  cfg80211_mlme_down+0x66/0x80 [cfg80211]
  [ 3634.322823]  cfg80211_disconnect+0x127/0x1e0 [cfg80211]
  [ 3634.322827]  ? _raw_spin_unlock_bh+0x1e/0x20
  [ 3634.322845]  __cfg80211_leave+0x133/0x1b0 [cfg80211]
  [ 3634.322862]  cfg80211_leave+0x2c/0x40 [cfg80211]
  [ 3634.322879]  cfg80211_netdev_notifier_call+0x1b2/0x590 [cfg80211]
  [ 3634.322902]  ? ath10k_warn.cold+0x1a/0x1f [ath10k_core]
  [ 3634.322911]  ? ath10k_config_ps+0x52/0x70 [ath10k_core]
  [ 3634.322913]  ? rtnl_is_locked+0x15/0x20
  [ 3634.322917]  ? inetdev_event+0x47/0x560
  [ 3634.322919]  ? skb_dequeue+0x5a/0x70
  [ 3634.322923]  notifier_call_chain+0x55/0x80
  [ 3634.322925]  raw_notifier_call_chain+0x16/0x20
  [ 3634.322927]  call_netdevice_notifiers_info+0x2e/0x60
  [ 3634.322929]  __dev_close_many+0x63/0

[Kernel-packages] [Bug 1864895] Re: dmseg report multiple "ACPI Error" and "ACPI BIOS Error"

[Alex Hung]

** Changed in: linux (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  dmseg report multiple "ACPI Error" and "ACPI BIOS Error"

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  'lsb_release -rd':
  Description:  Ubuntu 19.10
  Release:  19.10

  'cat /proc/version_signature > version.log':
  Ubuntu 5.3.0-40.32-generic 5.3.18

  'sudo lspci -vnvn > lspci-vnvn.log' as attachments.

  'dmesg | grep "Error"':
  [0.214136] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.TPLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.214145] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.214196] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.214200] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.214203] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.214205] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.216645] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.216648] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.216652] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.216654] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.219087] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.219091] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.219094] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.219097] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.221521] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS04._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.221524] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.221527] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS04._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.221529] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.223957] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS05._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.223961] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.226392] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS06._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.226396] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.226399] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS06._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.226401] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.228826] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS07._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.228829] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.231260] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS08._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.231263] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.233688] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS09._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.233691] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.233694] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS09._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.233696] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.236125] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS10._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.236128] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.238559] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS11._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.238562] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobje

[Kernel-packages] [Bug 1872351] Re: Qualcomm Atheros QCA6174 Killer 1435 Wireless-AC: Disabling wifi causes kernel warning in __sta_info_destroy_part2

[Alex Hung]

The same wifi used on one of the system I have, and I was able to
reproduce the same error once a while. When this warning message
occurred, the system wouldn't connect to my router, either.

I was able to workaround this by "sudo modprobe -r ath10k_pci ; sudo
modprobe ath10k_pci"

I compared kernel 5.4 (used in Ubuntu 20.04) and 5.7-rc1, and there
aren't fixes for this problem. The only patch that touches
"__sta_info_destroy_part2" is commit b16798f5b907733 (see
https://lore.kernel.org/linux-
wireless/20200326155133.ccb4fb0bb356.If48f0f0504efdcf16b8921f48c6d3bb2cb763c99@changeid/)

This patch has cc'ed stable, and it will eventually be included in 5.4.
A test kernel (Ubuntu-5.4.0-21.25 + b16798f5b907733) was built and is
available @ https://people.canonical.com/~alexhung/LP1872351/

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

Title:
  Qualcomm Atheros QCA6174 Killer 1435 Wireless-AC: Disabling wifi
  causes kernel warning in __sta_info_destroy_part2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have multiple issues with wifi on my Dell XPS 9380.
  This error was triggered when I tried to disable my wifi.

  [ 3634.322471] [ cut here ]
  [ 3634.322524] WARNING: CPU: 3 PID: 1188 at net/mac80211/sta_info.c:1057 
__sta_info_destroy_part2+0x14e/0x160 [mac80211]
  [ 3634.322525] Modules linked in: rfcomm vboxnetadp(OE) vboxnetflt(OE) 
vboxdrv(OE) ccm typec_displayport cmac algif_hash algif_skcipher af_alg bnep 
binfmt_misc nls_iso8859_1 mei_hdcp intel_rapl_msr snd_hda_codec_hdmi 
dell_laptop snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio 
snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core snd_usb_audio 
ath10k_pci x86_pkg_temp_thermal snd_usbmidi_lib snd_seq_midi snd_hwdep 
snd_seq_midi_event ath10k_core intel_powerclamp coretemp cdc_ether snd_rawmidi 
usbnet btusb kvm_intel r8152 ath btrtl mii btbcm kvm snd_seq uvcvideo 
videobuf2_vmalloc btintel videobuf2_memops intel_cstate videobuf2_v4l2 joydev 
snd_seq_device snd_pcm dell_wmi intel_rapl_perf videobuf2_common bluetooth 
mac80211 dell_smbios videodev snd_timer dcdbas mc input_leds ecdh_generic ecc 
wmi_bmof snd dell_wmi_descriptor serio_raw intel_wmi_thunderbolt cfg80211 
soundcore rtsx_pci_ms libarc4 memstick hid_multitouch processor_thermal_device 
ucsi_acpi typec_ucsi mei_me intel_rapl_common
  [ 3634.322564]  intel_xhci_usb_role_switch mei typec intel_soc_dts_iosf 
intel_pch_thermal roles int3403_thermal int340x_thermal_zone int3400_thermal 
mac_hid acpi_pad intel_hid acpi_thermal_rel sparse_keymap sch_fq_codel 
parport_pc ppdev lp parport ip_tables x_tables autofs4 mmc_block dm_crypt 
usbhid hid_generic crct10dif_pclmul crc32_pclmul rtsx_pci_sdmmc i915 
ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_algo_bit glue_helper 
drm_kms_helper psmouse syscopyarea sysfillrect nvme sysimgblt i2c_i801 
fb_sys_fops nvme_core drm intel_lpss_pci rtsx_pci intel_lpss idma64 i2c_hid 
virt_dma wmi hid pinctrl_sunrisepoint video pinctrl_intel
  [ 3634.322599] CPU: 3 PID: 1188 Comm: NetworkManager Tainted: G   OE  
   5.4.0-21-generic #25-Ubuntu
  [ 3634.322600] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.12.1 
12/11/2019
  [ 3634.322633] RIP: 0010:__sta_info_destroy_part2+0x14e/0x160 [mac80211]
  [ 3634.322635] Code: 24 0c 01 00 00 00 0f 84 52 ff ff ff 45 31 c0 b9 01 00 00 
00 4c 89 e2 48 89 de 4c 89 ef e8 0a a6 ff ff 85 c0 0f 84 34 ff ff ff <0f> 0b e9 
2d ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00
  [ 3634.322636] RSP: 0018:a70c009c3918 EFLAGS: 00010282
  [ 3634.322638] RAX: ff94 RBX: 9006104cc8c0 RCX: 

  [ 3634.322640] RDX: 90061ba3c740 RSI:  RDI: 
900613a62f48
  [ 3634.322641] RBP: a70c009c3938 R08: 90061e4d78c8 R09: 
0004
  [ 3634.322642] R10:  R11:  R12: 
900613f28000
  [ 3634.322643] R13: 900613a607a0 R14: 9006104cc8c0 R15: 
900613a60d68
  [ 3634.322644] FS:  7f596b396240() GS:90061e4c() 
knlGS:
  [ 3634.322645] CS:  0010 DS:  ES:  CR0: 80050033
  [ 3634.322646] CR2: 0db00945f000 CR3: 000494824005 CR4: 
003606e0
  [ 3634.322647] Call Trace:
  [ 3634.322670]  __sta_info_flush+0x128/0x180 [mac80211]
  [ 3634.322696]  ieee80211_set_disassoc+0xc0/0x5f0 [mac80211]
  [ 3634.322719]  ieee80211_mgd_deauth+0x104/0x490 [mac80211]
  [ 3634.322743]  ieee80211_deauth+0x18/0x20 [mac80211]
  [ 3634.322782]  cfg80211_mlme_deauth+0xb6/0x1e0 [cfg80211]
  [ 3634.322804]  cfg80211_mlme_down+0x66/0x80 [cfg80211]
  [ 3634.322823]  cfg80211_disconnect+0x127/0x1e0 [cfg80211]
  [ 3634.322827]  ? _raw_spin_unlock_bh+0x1e/0x20
  [ 3634.322845]  __cfg80211_leave+0x133/0x1b0 [cfg80211]
  [ 3634.322862]  cfg80211_leave+0x2c/0x40 [cfg80211]
  [ 3634.322879]  cfg80211_netdev_notifier_call

[Kernel-packages] [Bug 1872311] Re: Brightness hotkeys not working on Lenovo S740

[Alex Hung]

The brightness interface (/sys/class/backlight/intel_backlight) is
working, so it must be the missing events that cause your problem.

Ubuntu needs keycodes (KEY_BRIGHTNESSDOWN 224 & KEY_BRIGHTNESSUP 225),
and this can be from either scancode or ACPI events. Laptops usually use
ACPI for brightness, and this can be confirmed by pressing hotkeys while
running

   $ watch -n1 cat /proc/interrupts

Note: ACPI usually is on IRQ 9. Check whether interrupts increase with
brightness up/down presses.

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

Title:
  Brightness hotkeys not working on Lenovo S740

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Brightness hotkeys (Fn + F11 for decrease and Fn + F12 for increase)
  do not work on Ubuntu 20.04 and Lenovo S740 laptop. The brightness
  hotkeys did not work on 19.10 either.

  I followed the guide here:
  https://wiki.ubuntu.com/Hotkeys/Troubleshooting

  In "Step-by-step Troubleshooting", none of the steps (1-7) did produce
  any reaction to brightness change key combinations. However, I am able
  to change the laptop screen brightness through the brightness applet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  elias  1447 F pulseaudio
   /dev/snd/controlC0:  elias  1447 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 16:12:01 2020
  InstallationDate: Installed on 2019-11-19 (144 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 81RS
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=101c7da4-860d-4496-ae06-d98699795f9a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-04 (7 days ago)
  dmi.bios.date: 03/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BYCN33WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga S740-14IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrBYCN33WW:bd03/10/2020:svnLENOVO:pn81RS:pvrLenovoYogaS740-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS740-14IIL:
  dmi.product.family: Yoga S740-14IIL
  dmi.product.name: 81RS
  dmi.product.sku: LENOVO_MT_81RS_BU_idea_FM_Yoga S740-14IIL
  dmi.product.version: Lenovo Yoga S740-14IIL
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1872311] Re: Brightness hotkeys not working on Lenovo S740

[Alex Hung]

If ACPI approach is used, there are also two different approaches used -
ACPI standard or OEM-specific .

ACPI defines events from brightness up and down, and it is
video/brightnessdown BRTDN 0087 & video/brightnessup BRTUP 0086.
The can be checked by running "acpi_listen" and pressing brightness
hotkeys.

If OEM-specific events are used, it should be handled by platform driver
like "ideapad_laptop".

Would you mind sharing acpidump log (sudo acpidump > acpi.log) so more
analysis can be performed?

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

Title:
  Brightness hotkeys not working on Lenovo S740

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Brightness hotkeys (Fn + F11 for decrease and Fn + F12 for increase)
  do not work on Ubuntu 20.04 and Lenovo S740 laptop. The brightness
  hotkeys did not work on 19.10 either.

  I followed the guide here:
  https://wiki.ubuntu.com/Hotkeys/Troubleshooting

  In "Step-by-step Troubleshooting", none of the steps (1-7) did produce
  any reaction to brightness change key combinations. However, I am able
  to change the laptop screen brightness through the brightness applet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  elias  1447 F pulseaudio
   /dev/snd/controlC0:  elias  1447 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 16:12:01 2020
  InstallationDate: Installed on 2019-11-19 (144 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 81RS
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=101c7da4-860d-4496-ae06-d98699795f9a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-04 (7 days ago)
  dmi.bios.date: 03/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BYCN33WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga S740-14IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrBYCN33WW:bd03/10/2020:svnLENOVO:pn81RS:pvrLenovoYogaS740-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS740-14IIL:
  dmi.product.family: Yoga S740-14IIL
  dmi.product.name: 81RS
  dmi.product.sku: LENOVO_MT_81RS_BU_idea_FM_Yoga S740-14IIL
  dmi.product.version: Lenovo Yoga S740-14IIL
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1873179] Re: i915 bug: ZOOM messenger is very slow w/ kernel 5.3.0-46

[Alex Hung]

There are four patches added to i915 from Ubuntu-5.3.0-45.37 to
Ubuntu-5.3.0-46.38, like in
https://people.canonical.com/~alexhung/LP1873179/patches/

I built four kernels, each with one patch removed:
https://people.canonical.com/~alexhung/LP1873179/

For example,

p-1 = Ubuntu-5.3.0-46.38 with Revert "drm/i915: Schedue request retirement in 
execlists_user_end()"
p-2 = p-1 with Revert "drm/i915/userptr: fix size calculation"
p-3 = p-2 ...
p-all = p3 ...

Let us know which one caused your problem and we can discuss further.

If a patch is identified, I am also interested in knowing whether focal
kernel (based on 5.4) is able to solve your problem. If so, we can
investigate where we can backport anything from 5.4 to 5.3.

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

Title:
  i915 bug: ZOOM messenger is very slow w/ kernel 5.3.0-46

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi.

  I'm running Xubuntu 5.3.0-45.37-generic 5.3.18 on ThinkPad P1 Gen2 (ThinkPad 
Carbon X1 without Nvidia graphics).
  This bug happens on Eoan kernel 5.3.0-46 only. 
  Kernels -45 and earlier don't have it, so I had to revert to 5.3.0-45. 

  Steps to reproduce:
  1. Install ZOOM .deb from https://zoom.us/download?os=linux
  2. Start it.
  3. Try to start ZOOM meeting.
  4. GUI becomes very-very slow, but not completely frozen. No crashes.
  5. As soon as ZOOM meeting window is closed, lines "Resetting rcs0 for hang 
on rcs0" stop coming and GUI is OK.

  In syslog I see following lines:
  ---
  [  111.956936] i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0
  [  111.957947] i915 :00:02.0: Resetting rcs0 for hang on rcs0
  [  119.951013] i915 :00:02.0: Resetting rcs0 for hang on rcs0
  [  127.949941] i915 :00:02.0: Resetting rcs0 for hang on rcs0
  [  135.950174] i915 :00:02.0: Resetting rcs0 for hang on rcs0
  [  143.950558] i915 :00:02.0: Resetting rcs0 for hang on rcs0
  [  151.950819] i915 :00:02.0: Resetting rcs0 for hang on rcs0
  ---
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vburdo 1450 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-03-15 (31 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QUS11E00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic 
root=UUID=6059e627-eadb-4530-bba0-ac77ea95ba2d ro quiet splash 
resume=UUID=2ba66786-beee-495b-bcff-db0f19c70ccb vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-45-generic N/A
   linux-backports-modules-5.3.0-45-generic  N/A
   linux-firmware1.183.5
  Tags:  eoan
  Uname: Linux 5.3.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lp lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET42W (1.29 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QUS11E00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QUS11E00:pvrThinkPadP1Gen2:rvnLENOVO:rn20QUS11E00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P1 Gen 2
  dmi.product.name: 20QUS11E00
  dmi.product.sku: LENOVO_MT_20QU_BU_Think_FM_ThinkPad P1 Gen 2
  dmi.product.version: ThinkPad P1 Gen 2
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-03-16T16:40:07.038972
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vburdo 1450 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-03-15 (31 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QUS11E00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic 
root=UUID=6059e627-eadb-4530-bba0-ac77ea95ba2d ro quiet splash 
resume=UUID=2ba66786-beee-495b-bcff-db0f19c70ccb vt.handoff=7
  ProcVersionSignature: 

[Kernel-packages] [Bug 1873083] Re: Lenovo Yoga C940 frequently does thermal shutdown

[Alex Hung]

"sudo echo "disabled" > /sys/class/thermal/thermal_zone0/mode" is not
correct.

Try
   echo "disabled" | sudo tee /sys/class/thermal/thermal_zone0/mode

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

Title:
  Lenovo Yoga C940 frequently does thermal shutdown

Status in linux package in Ubuntu:
  Incomplete
Status in thermald package in Ubuntu:
  New

Bug description:
  On a bit higher load and especially if Laptop is charging, very often
  Kernel does an emergency thermal shutdown.

  thermal thermal_zone3: critical temperature reached (80 C), shutting
  down

  It says 80 C, but sensors command shows that temperatures hovering
  close to 100C before the shutdown happens.

  dmesg is often also full of these (for each core):
  mce: CPU2: Core temperature above threshold, cpu clock throttled (total 
events = 246766)

  When I boot to Windows, it seems that CPU is throttled more
  aggressively on load and thermal shutdown doesn't happen with a
  similar load, but CPU frequencies drop to 1600 range, while in Ubuntu
  they are 2800 range.

  I would rather have more throttling that computer shutting down
  randomly without the ability to save work.

  Is there a workaround?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anton  1874 F pulseaudio
   /dev/snd/pcmC0D0p:   anton  1874 F...m pulseaudio
   /dev/snd/pcmC0D6c:   anton  1874 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 23:54:21 2020
  InstallationDate: Installed on 2019-11-29 (137 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 81Q9
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=24af2874-e109-44f9-a5b9-8a9ce34b3f0f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-04 (11 days ago)
  dmi.bios.date: 01/09/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AUCN54WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga C940-14IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrAUCN54WW:bd01/09/2020:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL:
  dmi.product.family: Yoga C940-14IIL
  dmi.product.name: 81Q9
  dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL
  dmi.product.version: Lenovo Yoga C940-14IIL
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1873179] Re: i915 bug: ZOOM messenger is very slow w/ kernel 5.3.0-46

[Alex Hung]

If they all work fine, that probably means it is the first patch that
cause zoom problem, i.e.

>From 411b24761d2833e8ccd0ccf0a5599edede059183 Mon Sep 17 00:00:00 2001
From: Chris Wilson 
Date: Mon, 24 Feb 2020 15:06:53 -0600
Subject: [PATCH 4/4] drm/i915: Schedue request retirement in
 execlists_user_end()

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

Link: https://gitlab.freedesktop.org/drm/intel/issues/614
Signed-off-by: Seth Forshee 
Acked-by: Alex Hung 
Acked-by: Colin Ian King 
Signed-off-by: Khalid Elmously 
---


** Bug watch added: gitlab.freedesktop.org/drm/intel/issues #614
   https://gitlab.freedesktop.org/drm/intel/issues/614

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

Title:
  i915 bug: ZOOM messenger is very slow w/ kernel 5.3.0-46

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi.

  I'm running Xubuntu 5.3.0-45.37-generic 5.3.18 on ThinkPad P1 Gen2 (ThinkPad 
Carbon X1 without Nvidia graphics).
  This bug happens on Eoan kernel 5.3.0-46 only. 
  Kernels -45 and earlier don't have it, so I had to revert to 5.3.0-45. 

  Steps to reproduce:
  1. Install ZOOM .deb from https://zoom.us/download?os=linux
  2. Start it.
  3. Try to start ZOOM meeting.
  4. GUI becomes very-very slow, but not completely frozen. No crashes.
  5. As soon as ZOOM meeting window is closed, lines "Resetting rcs0 for hang 
on rcs0" stop coming and GUI is OK.

  In syslog I see following lines:
  ---
  [  111.956936] i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0
  [  111.957947] i915 :00:02.0: Resetting rcs0 for hang on rcs0
  [  119.951013] i915 :00:02.0: Resetting rcs0 for hang on rcs0
  [  127.949941] i915 :00:02.0: Resetting rcs0 for hang on rcs0
  [  135.950174] i915 :00:02.0: Resetting rcs0 for hang on rcs0
  [  143.950558] i915 :00:02.0: Resetting rcs0 for hang on rcs0
  [  151.950819] i915 :00:02.0: Resetting rcs0 for hang on rcs0
  ---
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vburdo 1450 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-03-15 (31 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QUS11E00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic 
root=UUID=6059e627-eadb-4530-bba0-ac77ea95ba2d ro quiet splash 
resume=UUID=2ba66786-beee-495b-bcff-db0f19c70ccb vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-45-generic N/A
   linux-backports-modules-5.3.0-45-generic  N/A
   linux-firmware1.183.5
  Tags:  eoan
  Uname: Linux 5.3.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lp lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET42W (1.29 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QUS11E00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QUS11E00:pvrThinkPadP1Gen2:rvnLENOVO:rn20QUS11E00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P1 Gen 2
  dmi.product.name: 20QUS11E00
  dmi.product.sku: LENOVO_MT_20QU_BU_Think_FM_ThinkPad P1 Gen 2
  dmi.product.version: ThinkPad P1 Gen 2
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-03-16T16:40:07.038972
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vburdo 1450 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-03-15 (31 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QUS11E00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic 
root=UUID=6059e627-eadb-4530-bba0-ac77ea95ba2d ro quiet splash 
resume=UUID=2ba66786-beee-495b-bcff-db0f19c70ccb vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-45.37-generi

[Kernel-packages] [Bug 1843511] Re: i915 enable_rc6=0 not respected

[Alex Hung]

i915.enable_rc6 has been removed since kernel 4.16

See https://patchwork.freedesktop.org/patch/191386/ or commit
fb6db0f5bf1d4d3a4a for more details

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

Title:
  i915 enable_rc6=0 not respected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
   i915 enable_rc6=0 is not respected.  I want to disable rc6 power savings 
because it is a tower
  machine with a kilowatt supply and lots of fan so I don't give a rip about 
power consumption, I do not
  want my display interrupted while I'm watching a movie or video and when 
monitoring things I want to
  be able to walk by the monitor and see what is going on without having to go 
up and wiggle the mouse
  and wait for it to wake up and my monitor to sync.

   I have an i7-9700k on an Asus Z390A Prime motherboard.  I have
  enable RC6 disabled in the BIOS so BIOS isn't enabling it, in
  /etc/modprobe.d/i915.conf I have:

   options i915 enable_guc=3 enable_dc=0 enable_rc6=0

   In /etc/default/grub I have:

   GRUB_CMDLINE_LINUX_DEFAULT="quiet splash xdg.force_integrated=1
  modprobe.blacklist=nouveau i915.i915_enable_rc6=0"

   I have done update-grub2 and update-initramfs -u -k all and
  rebooted, but still:

  cat /sys/class/drm/card0/power/rc6_enable
  1

   The kernel totally ignores my instructions and enables the damned
  thing anyway.  ARRGGH!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-lowlatency 5.0.0.28.29
  ProcVersionSignature: Ubuntu 5.0.0-28.30-lowlatency 5.0.21
  Uname: Linux 5.0.0-28-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nanook 4342 F pulseaudio
  CurrentDesktop: MATE
  Date: Tue Sep 10 16:14:06 2019
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-28-lowlatency 
root=UUID=718970be-1c9c-4b4e-8940-1e26324e158b ro console=tty1 console=ttyS0 
panic=-1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-28-lowlatency N/A
   linux-backports-modules-5.0.0-28-lowlatency  N/A
   linux-firmware   1.178.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1105
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z390-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1105:bd06/06/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: ASUS_MB_CNL
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1873179] Re: i915 bug: ZOOM messenger is very slow w/ kernel 5.3.0-46

[Alex Hung]

The patch was intended to fix Intel RC6 power saving that failed after a
security fix. That implies that zoom may have issues with Intel RC6.

I manually built Ubuntu-5.4.0-21.25
(https://people.canonical.com/~alexhung/LP1873179/focal/) for testing.
The i915 RC6 fix are different. Let's see if zoom behaves differently

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

Title:
  i915 bug: ZOOM messenger is very slow w/ kernel 5.3.0-46

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi.

  I'm running Xubuntu 5.3.0-45.37-generic 5.3.18 on ThinkPad P1 Gen2 (ThinkPad 
Carbon X1 without Nvidia graphics).
  This bug happens on Eoan kernel 5.3.0-46 only. 
  Kernels -45 and earlier don't have it, so I had to revert to 5.3.0-45. 

  Steps to reproduce:
  1. Install ZOOM .deb from https://zoom.us/download?os=linux
  2. Start it.
  3. Try to start ZOOM meeting.
  4. GUI becomes very-very slow, but not completely frozen. No crashes.
  5. As soon as ZOOM meeting window is closed, lines "Resetting rcs0 for hang 
on rcs0" stop coming and GUI is OK.

  In syslog I see following lines:
  ---
  [  111.956936] i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0
  [  111.957947] i915 :00:02.0: Resetting rcs0 for hang on rcs0
  [  119.951013] i915 :00:02.0: Resetting rcs0 for hang on rcs0
  [  127.949941] i915 :00:02.0: Resetting rcs0 for hang on rcs0
  [  135.950174] i915 :00:02.0: Resetting rcs0 for hang on rcs0
  [  143.950558] i915 :00:02.0: Resetting rcs0 for hang on rcs0
  [  151.950819] i915 :00:02.0: Resetting rcs0 for hang on rcs0
  ---
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vburdo 1450 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-03-15 (31 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QUS11E00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic 
root=UUID=6059e627-eadb-4530-bba0-ac77ea95ba2d ro quiet splash 
resume=UUID=2ba66786-beee-495b-bcff-db0f19c70ccb vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-45-generic N/A
   linux-backports-modules-5.3.0-45-generic  N/A
   linux-firmware1.183.5
  Tags:  eoan
  Uname: Linux 5.3.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lp lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET42W (1.29 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QUS11E00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QUS11E00:pvrThinkPadP1Gen2:rvnLENOVO:rn20QUS11E00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P1 Gen 2
  dmi.product.name: 20QUS11E00
  dmi.product.sku: LENOVO_MT_20QU_BU_Think_FM_ThinkPad P1 Gen 2
  dmi.product.version: ThinkPad P1 Gen 2
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-03-16T16:40:07.038972
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vburdo 1450 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-03-15 (31 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QUS11E00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic 
root=UUID=6059e627-eadb-4530-bba0-ac77ea95ba2d ro quiet splash 
resume=UUID=2ba66786-beee-495b-bcff-db0f19c70ccb vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-45-generic N/A
   linux-backports-modules-5.3.0-45-generic  N/A
   linux-firmware1.183.5
  Tags:  eoan
  Uname: Linux 5.3.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lp lpadmin lxd plugdev sambashare sudo
  _MarkF

[Kernel-packages] [Bug 1861925] Re: BrightnessOutofRange: Actual brightness for amdgpu_bl0 not in range 0..255

[Alex Hung]

@esanya,

Thanks for updating the results. Hopefully the HW failure is the root
cause of the brightness problem that acer can fix.

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

Title:
  BrightnessOutofRange: Actual brightness for amdgpu_bl0 not in range
  0..255

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I have a acer aspire a315-41 laptop, it has BIOS 1.15, Ubuntu 19.10,
  Kernel stock 5.3, and 5.5.0. I have a problem with the Backlight. I
  can not control.

  According to: https://wiki.ubuntu.com/Kernel/Debugging/Backlight

  It is : Backlight control does not work, but there are entries in
  /sys/class/backlight.

  The problem is as far I could find:

  sanya@Aspire-A315-41:/sys/class/backlight/amdgpu_bl0$ cat brightness
  135
  sanya@Aspire-A315-41:/sys/class/backlight/amdgpu_bl0$ cat actual_brightness
  43500
  sanya@Aspire-A315-41:/sys/class/backlight/amdgpu_bl0$ cat max_brightness
  255

  The brightness read from the HW is not in the range, and when I change
  the brightness by the keys the value in the brightness file changes
  too, but the actual_brightness is stuck at the value 43500...

  I have tried all the steps mentioned in
  https://wiki.ubuntu.com/Kernel/Debugging/Backlight

  Actually I have tried all these kernel startup parameter variants
  without luck:

  GRUB_CMDLINE_LINUX_DEFAULT=""
  #GRUB_CMDLINE_LINUX_DEFAULT="video.use_native_backlight=1"
  #GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi="
  #GRUB_CMDLINE_LINUX_DEFAULT="video.use_bios_initial_backlight=0"
  #GRUB_CMDLINE_LINUX_DEFAULT="amdgpu.dcfeaturemask=0x4 amdgpu.abmlevel=2"
  #GRUB_CMDLINE_LINUX_DEFAULT="acpi_backlight=video amdgpu.abmlevel=1"
  #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=Linux acpi_backlight=vendor"
  #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=! acpi_osi=\"Windows 2009\" 
acpi_backlight=vendor"
  #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=! acpi_osi=\"Windows 2009\" 
acpi_backlight=video"
  #GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=! acpi_osi=\"Windows 2009\" 
acpi_backlight=vendor"
  #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=! acpi_osi=\"Windows 2009\" 
acpi_backlight=vendor"
  #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=! acpi_osi=\"Windows 2009\" 
acpi_backlight=vendor"

  I guess the fwts has found also this as an error:

  autobrightness: Automated LCD brightness test.
  

  Test 1 of 2: Test for maximum and actual brightness.
  PASSED: Test 1, Maximum brightness for amdgpu_bl0 is 255 which is sane.
  FAILED [HIGH] BrightnessOutofRange: Test 1, Actual brightness for amdgpu_bl0 
not
  in range 0..255.

  Test 2 of 2: Change actual brightness.
  FAILED [MEDIUM] BrightnessMismatch: Test 2, 256 brightness levels did not 
match
  the brightnesss level just set for backlight amdgpu_bl0.
  The failed brightness levels were: 0-255.

  It would be great if someone could help set the HW brightness back to
  the normal range.

  If you need any more debug files please let me know!

  Thanks,
  Regards,
  Sandor

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

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

[Kernel-packages] [Bug 1877870] Re: ACPI errors

[Alex Hung]

This is usually the result of duplicated name declaration in ACPI BIOS,
and there are usually no harms.

An ACPI dump (sudo acpidump > acpi.log) will be helpful for further
analysis.

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

Title:
  ACPI errors

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  i have a bunch of acpi errors showing up on the log. this one repeats
  a lot:

  ACPI BIOS Error (bug): Failure creating named object
  [\_SB.PCI0.XHC.RHUB.SS09._UPC], AE_ALREADY_EXISTS
  (20190816/dswload2-323)

  my bios is updated (from windows, on april 3, 2020)

  currently running ubuntu 20.04 with kernel 5.4.0-29-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pkillpeers   1879 F pulseaudio
   /dev/snd/controlC0:  pkillpeers   1879 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 10 16:24:50 2020
  InstallationDate: Installed on 2020-05-07 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0408:5300 Quanta Computer, Inc. HP Wide Vision HD 
Camera
   Bus 001 Device 002: ID 046d:c07e Logitech, Inc. G402 Gaming Mouse
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP OMEN by HP Laptop 15-dc0xxx
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=c93b8267-6fe4-492f-ad94-1252537b50fb ro
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2020
  dmi.bios.vendor: AMI
  dmi.bios.version: F.12
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 84DB
  dmi.board.vendor: HP
  dmi.board.version: 93.24
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.12:bd03/23/2020:svnHP:pnOMENbyHPLaptop15-dc0xxx:pvr:rvnHP:rn84DB:rvr93.24:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 15-dc0xxx
  dmi.product.sku: 4ML16EA#AB9
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1877488] Re: External mouse movement wakes computer from hibernate

[Alex Hung]

You can disable wakeup by modifying "/proc/acpi/wakeup" in Linux

1. get all wakeup sources - "cat /proc/acpi/wakeup"

The results are something like

Device  S-state   Status   Sysfs node
PEG0  S4*enabled   pci::00:01.0
PEGP  S4*disabled  pci::01:00.0
PEG1  S4*disabled
PEGP  S4*disabled
...
XHC   S3*enabled   pci::00:14.0
...

2. find out which USB maps to your logitech mouse. You probably need
trial and error couple times. The above example is XHC which is USB3
controller which is capable of waking up from S3, S2 and S1. Your will
differ.

3. disable it by "echo XHC | sudo tee /proc/acpi/wakeup" (assuming XHC
is the one).

finally, you can disable it automatically by rc.local (like
https://vpsfix.com/community/server-administration/no-etc-rc-local-file-
on-ubuntu-18-04-heres-what-to-do/)

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

Title:
  External mouse movement wakes computer from hibernate

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When the computer is suspended, moving the mouse (External logitech)
  causes the computer to come out of hibernation.  I can tell because
  the Legion logo lights up.  After a little while (minute?)  it
  evidently suspends again because the logo turns off again.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.19
  ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34
  Uname: Linux 5.4.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  7 19:07:34 2020
  InstallationDate: Installed on 2020-03-12 (56 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lisa   1854 F pulseaudio
   /dev/snd/controlC0:  lisa   1854 F pulseaudio
   /dev/snd/pcmC0D0p:   lisa   1854 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-12 (57 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306)
  MachineType: LENOVO 81T2
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-30-generic 
root=UUID=51068ea2-6b38-4cfc-a75f-4f404cd04685 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-30-generic N/A
   linux-backports-modules-5.4.0-30-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 11/23/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN35WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN35WW:bd11/23/2019:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1877870] Re: ACPI errors

[Alex Hung]

ACPI consists of many tables. Two types of them are DSDT and SSDT.

DSDT is mandatory, and SSDTs are addon to DSDT and are optional. SSDT is
/ can be loaded according to hardware config during boot time. In the
case of this system, the ACPI objects that are erroneous are both
declared in DSDT and a SSDT (i.e. SSDT6 if you extract from acpi.log).
It seems to be that contents of SSDT6 are almost copied to DSDT and it
should not be loaded at all.

Fortunately, most of the duplicated objects (methods) are very similar,
if not identical, to their clones in DSDT. When kernel parses SSDT6, it
found these objects already exist and stopped loading them. This does
not cause functional loss so there is nothing to worry about.

A fix must be done in BIOS, but a workaround is to modify SSDT6 and
override it with ACPI override by Linux kernel; however, the later would
"taint" the kernel and it would also be a overkill when nothing is
broken.

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

Title:
  ACPI errors

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  i have a bunch of acpi errors showing up on the log. this one repeats
  a lot:

  ACPI BIOS Error (bug): Failure creating named object
  [\_SB.PCI0.XHC.RHUB.SS09._UPC], AE_ALREADY_EXISTS
  (20190816/dswload2-323)

  my bios is updated (from windows, on april 3, 2020)

  currently running ubuntu 20.04 with kernel 5.4.0-29-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pkillpeers   1879 F pulseaudio
   /dev/snd/controlC0:  pkillpeers   1879 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 10 16:24:50 2020
  InstallationDate: Installed on 2020-05-07 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0408:5300 Quanta Computer, Inc. HP Wide Vision HD 
Camera
   Bus 001 Device 002: ID 046d:c07e Logitech, Inc. G402 Gaming Mouse
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP OMEN by HP Laptop 15-dc0xxx
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=c93b8267-6fe4-492f-ad94-1252537b50fb ro
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2020
  dmi.bios.vendor: AMI
  dmi.bios.version: F.12
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 84DB
  dmi.board.vendor: HP
  dmi.board.version: 93.24
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.12:bd03/23/2020:svnHP:pnOMENbyHPLaptop15-dc0xxx:pvr:rvnHP:rn84DB:rvr93.24:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 15-dc0xxx
  dmi.product.sku: 4ML16EA#AB9
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1882823] Re: int3403 thermal INT3403:00

[Alex Hung]

This is not related to audio driver but is related to thermal driver
"int3403_thermal.c". It supports upto event 0x90 (See line 21 & line 64
@
https://elixir.bootlin.com/linux/v5.7.1/source/drivers/thermal/intel/int340x_thermal/int3403_thermal.c).
Intel may have added a new event that is yet supported in kernel.

It is a good idea to send an email to mailing list "linux-
p...@vger.kernel.org (open list:THERMAL)" so the driver can be updated
accordingly.

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

Title:
  int3403 thermal INT3403:00

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [8.112761] int3403 thermal INT3403:00: Unsupported event [0x91]
  [   10.121722] int3403 thermal INT3403:00: Unsupported event [0x91]
  [   12.165233] int3403 thermal INT3403:00: Unsupported event [0x91]

  Is constantly flooding my dmesg. I believe this is also due to missing
  audio drivers as well. Which is another issue that I am facing.

  Realtek ALC1220

  Ubuntu 20.04

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

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

[Kernel-packages] [Bug 1882823] Re: int3403 thermal INT3403:00

[Alex Hung]

@junocomp,

These mailing lists don't like HTML-formated emails. You need to send
emails in text, and this depends on the email client program you are
using.

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

Title:
  int3403 thermal INT3403:00

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [8.112761] int3403 thermal INT3403:00: Unsupported event [0x91]
  [   10.121722] int3403 thermal INT3403:00: Unsupported event [0x91]
  [   12.165233] int3403 thermal INT3403:00: Unsupported event [0x91]

  Is constantly flooding my dmesg. I believe this is also due to missing
  audio drivers as well. Which is another issue that I am facing.

  Realtek ALC1220

  Ubuntu 20.04

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

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

[Kernel-packages] [Bug 1882823] Re: int3403 thermal INT3403:00

[Alex Hung]

I sent an email asking about 0x91 to mailing list. I will update here
when information is available.

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

Title:
  int3403 thermal INT3403:00

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [8.112761] int3403 thermal INT3403:00: Unsupported event [0x91]
  [   10.121722] int3403 thermal INT3403:00: Unsupported event [0x91]
  [   12.165233] int3403 thermal INT3403:00: Unsupported event [0x91]

  Is constantly flooding my dmesg. I believe this is also due to missing
  audio drivers as well. Which is another issue that I am facing.

  Realtek ALC1220

  Ubuntu 20.04

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

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

[Kernel-packages] [Bug 1882823] Re: int3403 thermal INT3403:00

[Alex Hung]

https://marc.info/?l=linux-pm&m=159199577712570&w=2

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

Title:
  int3403 thermal INT3403:00

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [8.112761] int3403 thermal INT3403:00: Unsupported event [0x91]
  [   10.121722] int3403 thermal INT3403:00: Unsupported event [0x91]
  [   12.165233] int3403 thermal INT3403:00: Unsupported event [0x91]

  Is constantly flooding my dmesg. I believe this is also due to missing
  audio drivers as well. Which is another issue that I am facing.

  Realtek ALC1220

  Ubuntu 20.04

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

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

[Kernel-packages] [Bug 1882823] Re: int3403 thermal INT3403:00

[Alex Hung]

A patch was sent for reviews: https://marc.info/?l=linux-
pm&m=159226080621530&w=2

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

Title:
  int3403 thermal INT3403:00

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [8.112761] int3403 thermal INT3403:00: Unsupported event [0x91]
  [   10.121722] int3403 thermal INT3403:00: Unsupported event [0x91]
  [   12.165233] int3403 thermal INT3403:00: Unsupported event [0x91]

  Is constantly flooding my dmesg. I believe this is also due to missing
  audio drivers as well. Which is another issue that I am facing.

  Realtek ALC1220

  Ubuntu 20.04

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

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

[Kernel-packages] [Bug 1879082] Re: Kernel reporting 100% battery, always

[Alex Hung]

#17 looks like correct behavours. I also noticed #13 said battery was
acting without problems anymore. Is it still the case or did you have
problems when running #17?

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

Title:
  Kernel reporting 100% battery, always

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Running Kubuntu 20.04:  Regardless of whether the laptop is plugged-
  in, or the battery state (Even just before dying) the reported
  percentage is incorrect and the system believes it is plugged in at
  all times (see upower -d below, it is always the same).

  $ cat /proc/version_signature
  Ubuntu 5.4.0-29.33-generic 5.4.30

  $ lsb_release -a
  LSB Version:
core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04 LTS
  Release:20.04
  Codename:   focal

  $ uname -a
  Linux Vergil 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

  $ upower -d
  Device: /org/freedesktop/UPower/devices/line_power_ACAD
native-path:  ACAD
power supply: yes
updated:  Sat 16 May 2020 12:35:46 PM CDT (909 seconds ago)
has history:  no
has statistics:   no
line-power
  warning-level:   none
  online:  yes
  icon-name:  'ac-adapter-symbolic'

  Device: /org/freedesktop/UPower/devices/battery_BAT1
native-path:  BAT1
vendor:   TOSHIBA
model:PABAS0241231
serial:   
power supply: yes
updated:  Sat 16 May 2020 12:49:47 PM CDT (68 seconds ago)
has history:  yes
has statistics:   yes
battery
  present: yes
  rechargeable:yes
  state:   fully-charged
  warning-level:   none
  energy:  4294.84 Wh
  energy-empty:0 Wh
  energy-full: 4294.84 Wh
  energy-full-design:  4294.84 Wh
  energy-rate: 0 W
  voltage: 65.535 V
  percentage:  100%
  capacity:100%
  technology:  lithium-ion
  icon-name:  'battery-full-charged-symbolic'

  Device: /org/freedesktop/UPower/devices/DisplayDevice
power supply: yes
updated:  Sat 16 May 2020 12:32:09 PM CDT (1126 seconds ago)
has history:  no
has statistics:   no
battery
  present: yes
  state:   fully-charged
  warning-level:   none
  energy:  4294.84 Wh
  energy-full: 4294.84 Wh
  energy-rate: 0 W
  percentage:  100%
  icon-name:  'battery-full-charged-symbolic'

  Daemon:
daemon-version:  0.99.11
on-battery:  no
lid-is-closed:   no
lid-is-present:  yes
critical-action: HybridSleep

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sperger1191 F pulseaudio
   /dev/snd/controlC0:  sperger1191 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sat May 16 12:41:59 2020
  InstallationDate: Installed on 2020-03-11 (65 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: TOSHIBA Satellite C55-B
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=fd25621b-6551-420a-a1c5-13a0746ae679 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-10 (5 days ago)
  dmi.bios.date: 07/19/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.30
  dmi.board.asset.tag: *
  dmi.board.name: ZSWAA
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: *
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.30:bd07/19/2014:svnTOSHIBA:pnSatelliteC55-B:pvrPSCLUU-05M07V:rvnTOSHIBA:rnZSWAA:rvr1.00:cvnTOSHIBA:ct10:cvr*:
  dmi.product.family: *
  dmi.product.name: Satellite C55-B
  dmi.product.sku: PSCLUU
  dmi.product.version: PSCLUU-05M07V
  dmi.sys.vendor: TOSHIBA

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

--

[Kernel-packages] [Bug 1882823] Re: int3403 thermal INT3403:00

[Alex Hung]

I also cc'ed stable which includes kernel 5.4. It should be available in
kernel 5.4 automatically when (and if) it lands into mainline kernel.

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

Title:
  int3403 thermal INT3403:00

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [8.112761] int3403 thermal INT3403:00: Unsupported event [0x91]
  [   10.121722] int3403 thermal INT3403:00: Unsupported event [0x91]
  [   12.165233] int3403 thermal INT3403:00: Unsupported event [0x91]

  Is constantly flooding my dmesg. I believe this is also due to missing
  audio drivers as well. Which is another issue that I am facing.

  Realtek ALC1220

  Ubuntu 20.04

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

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

[Kernel-packages] [Bug 1865170] Re: lid close simply turns off laptop screen

[Alex Hung]

It looks like BIOS issue. An acpidump log will help (sudo acpidump >
acpi.log)

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

Title:
  lid close simply turns off laptop screen

Status in gnome-session package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1)
  ubuntu-session version: 3.28.1-0ubuntu3
  Expected behavior: On laptop screen close, system should suspend
  Actual behavior: On laptop screen close, laptop screen disabled

  Previously, I triggered 'suspend when laptop lid is closed' in gnome-
  tweaks. This worked fine until about 2-3 days ago, when I came back to
  work with a dead laptop (I don't charge overnight, usually, but I do
  use a dock at work). Now, whenever I close my laptop screen, it
  doesn't trigger sleep - instead, it simply disables the laptop screen,
  resulting in my external monitor being used as the only output screen.
  Once I re-open my laptop, the laptop screen is re-enabled as the
  primary monitor.

  This happens regardless of connection to my dock. I tested this by
  unplugging my laptop, closing it, letting it sit for 3 minutes, then
  re-opening it. While the laptop was closed, fans still ran. When I re-
  opened my laptop, the lock screen didn't appear.

  Links to attempted fixes that didn't work:

  - 
https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate
  - 
https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close
  - 
https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369
  - 
https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid

  Results of attempted fixes:
  - mem_sleep: no behavior change (files correctly modified)
  - pm-hibernate: first run, hangs until I kill the process. future runs result 
in exit code 1.
  - update bios: already on latest bios
  - logind.conf: no behavior change
  - gnome tweaks: no behavior change

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-session 3.28.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18
  Uname: Linux 4.15.0-1073-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 28 10:23:52 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1
  InstallationDate: Installed on 2020-01-08 (51 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  colton 4205 F pulseaudio
   /dev/snd/controlC0:  colton 4205 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-08 (53 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 7390
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem 
root=UUID=ef2a7f80-1cfd-48d6-a2be-0875e4832f2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1073-oem N/A
   linux-backports-modules-4.15.0-1073-oem  N/A
   linux-firmware   1.173.15
  Tags:  bionic
  Uname: Linux 4.15.0-1073-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0377MH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 

[Kernel-packages] [Bug 1868733] Re: Battery charge state frozen/incorrect

[Alex Hung]

Please try latest mainline kernel (https://kernel.ubuntu.com/~kernel-
ppa/mainline/v5.6-rc7/)

If this still fails, please upload log file from acpidump (sudo acpidump
> acpi.log). Usually ACPI battery are named BAT"0" (just a convention).
Let's check whether BIOS has more than one batteries in ACPI AML code.

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

Title:
  Battery charge state frozen/incorrect

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This may be a copy of: 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824886
  However with the bug's age I did not want to take a chance and reported 
separately and commented/subscribed there as well.

  Running Kubuntu 19.10.
  After running 45 minutes, unplugged, on old computer, with brightness 100% 
and streaming video:

  $ upower -d 
  Device: /org/freedesktop/UPower/devices/line_power_ACAD
native-path:  ACAD
power supply: yes
updated:  Tue 24 Mar 2020 08:48:42 AM CDT (2763 seconds ago)
has history:  no
has statistics:   no
line-power
  warning-level:   none
  online:  yes
  icon-name:  'ac-adapter-symbolic'

  Device: /org/freedesktop/UPower/devices/battery_BAT1
native-path:  BAT1
vendor:   TOSHIBA
model:PABAS0241231
serial:   
power supply: yes
updated:  Tue 24 Mar 2020 09:34:43 AM CDT (2 seconds ago)
has history:  yes
has statistics:   yes
battery
  present: yes
  rechargeable:yes
  state:   fully-charged
  warning-level:   none
  energy:  4294.84 Wh
  energy-empty:0 Wh
  energy-full: 4294.84 Wh
  energy-full-design:  4294.84 Wh
  energy-rate: 0 W
  voltage: 65.535 V
  percentage:  100%
  capacity:100%
  technology:  lithium-ion
  icon-name:  'battery-full-charged-symbolic'

  Device: /org/freedesktop/UPower/devices/DisplayDevice
power supply: yes
updated:  Tue 24 Mar 2020 08:26:14 AM CDT (4111 seconds ago)
has history:  no
has statistics:   no
battery
  present: yes
  state:   fully-charged
  warning-level:   none
  energy:  4294.84 Wh
  energy-full: 4294.84 Wh
  energy-rate: 0 W
  percentage:  100%
  icon-name:  'battery-full-charged-symbolic'

  Daemon:
daemon-version:  0.99.11
on-battery:  no
lid-is-closed:   no
lid-is-present:  yes
critical-action: HybridSleep
  
_
  $ acpi
  Battery 0: Not charging, 100%
  
_
  $ cat /sys/class/power_supply/BAT1/charge*
  65535000
  65535000
  65535000
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sperger1086 F pulseaudio
   /dev/snd/controlC0:  sperger1086 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-03-11 (12 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 001 Device 003: ID 04f2:b446 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:8000 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 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TOSHIBA Satellite C55-B
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=fd25621b-6551-420a-a1c5-13a0746ae679 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  eoan
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/19/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.30
  dmi.board.asset.tag: *
  dmi.board.name: ZSWAA
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor

[Kernel-packages] [Bug 1865170] Re: lid close simply turns off laptop screen

[Alex Hung]

Thanks for opening a bug and testing. Let's mark it fix released. Please
re-open if you have found it fails again.

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

** Changed in: gnome-session (Ubuntu)
   Status: New => 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/1865170

Title:
  lid close simply turns off laptop screen

Status in gnome-session package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1)
  ubuntu-session version: 3.28.1-0ubuntu3
  Expected behavior: On laptop screen close, system should suspend
  Actual behavior: On laptop screen close, laptop screen disabled

  Previously, I triggered 'suspend when laptop lid is closed' in gnome-
  tweaks. This worked fine until about 2-3 days ago, when I came back to
  work with a dead laptop (I don't charge overnight, usually, but I do
  use a dock at work). Now, whenever I close my laptop screen, it
  doesn't trigger sleep - instead, it simply disables the laptop screen,
  resulting in my external monitor being used as the only output screen.
  Once I re-open my laptop, the laptop screen is re-enabled as the
  primary monitor.

  This happens regardless of connection to my dock. I tested this by
  unplugging my laptop, closing it, letting it sit for 3 minutes, then
  re-opening it. While the laptop was closed, fans still ran. When I re-
  opened my laptop, the lock screen didn't appear.

  Links to attempted fixes that didn't work:

  - 
https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate
  - 
https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close
  - 
https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369
  - 
https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid

  Results of attempted fixes:
  - mem_sleep: no behavior change (files correctly modified)
  - pm-hibernate: first run, hangs until I kill the process. future runs result 
in exit code 1.
  - update bios: already on latest bios
  - logind.conf: no behavior change
  - gnome tweaks: no behavior change

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-session 3.28.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18
  Uname: Linux 4.15.0-1073-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 28 10:23:52 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1
  InstallationDate: Installed on 2020-01-08 (51 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  colton 4205 F pulseaudio
   /dev/snd/controlC0:  colton 4205 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-08 (53 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 7390
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem 
root=UUID=ef2a7f80-1cfd-48d6-a2be-0875e4832f2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1073-oem N/A
   linux-backports-modules-4.15.0-1073-oem  N/A
   linux-firmware   1.173.15
  Tags:  bionic
  Uname: Linux 4.15.0-1073-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0377MH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor:

[Kernel-packages] [Bug 1869235] Re: Ryzen 3rd gen (3900X) ECC support missing from kernel

[Alex Hung]

@araemo,

Thanks for reporting.

I will prepare a SRU for eoan kernel (5.3). Can you try the below kernel
(Ubuntu-5.3.0-42.34 + cherry-picked e53a3b267fb0 & 3e443eb353ed). If
your problem goes away I will send the patches for SRU reviews.

https://people.canonical.com/~alexhung/LP1869235/

We may need your help test proposed kernel before next kernel updates
later as I do not have the hardware to verify 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/1869235

Title:
  Ryzen 3rd gen (3900X) ECC support missing from kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu server:
  Description:Ubuntu 19.10
  Release:19.10
  Installed kernel:
  linux-generic:
Installed: 5.3.0.42.36
  (I could not figure out what package to select in the 'in what package did 
you find this bug' chooser)

  Expected behavior: ECC RAM is detected and utilized
  Result instead:
  Error in dmesg at boot:
  EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?) (more in the 
attached KernelErrors.log)

  Kernel 5.3 is missing ECC support for some families of AMD Ryzen 3rd
  gen CPUs.

  Support is added via these two commits in the mainline tree:
  
https://github.com/torvalds/linux/commit/e53a3b267fb0a79db9ca1f1e08b97889b22013e6
  
https://github.com/torvalds/linux/commit/3e443eb353eda6f4b4796e07f2599683fa752f1d

  The second commit actually adds the missing support, but it relies on
  the first commit: a partial refactor of the AMD ECC code.

  I tested myself, followed the instructions at 
https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel to build my own kernel, 
cherry-picked the two above commits, and have working ECC support on my 
self-built kernel:
  Linux smaug 5.3.0-43-generic #36 SMP Sat Mar 21 02:33:30 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux:

  EDAC MC: Ver: 3.0.0
  EDAC amd64: Node 0: DRAM ECC enabled.
  EDAC amd64: F17h_M70h detected (node 0).
  EDAC MC: UMC0 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC MC: UMC1 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC amd64: using x16 syndromes.
  EDAC amd64: MCT channel count: 2
  EDAC MC0: Giving out device to module amd64_edac controller F17h_M70h: DEV 
:00:18.3 (INTERRUPT)
  EDAC PCI0: Giving out device to module amd64_edac controller EDAC PCI 
controller: DEV :00:18.0 (POLLED)
  AMD64 EDAC driver v3.5.0

  
  If this could be included in a future hardware support kernel release, that 
would be very helpful.  I am unsure what the policy is for including this kind 
of backport in non-LTS kernels, though I know the LTS releases have hardware 
support updates that include this type of fix.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-03-20 (6 days ago)
  InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=89cfcc61-dbca-43d3-9a2e-5961df9ae5b4 ro
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  RfKill:
   
  Tags:  eoan uec-images
  Uname: Linux 5.3.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lxd plugdev sudo
  _MarkForUpload: False
  dmi.bios.date: 10/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.30
  dmi.board.name: X470D4U2-2T
  dmi.board.vendor: ASRockRack
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd10/03/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRockRack:rnX470D4U2-2T:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.n

[Kernel-packages] [Bug 1872311] Re: Brightness hotkeys not working on Lenovo S740

[Alex Hung]

No ACPI interrupts means either BIOS is broken or system is using other
mechanism like scancode from KBC/EC.

Checking scancode is easy: sudo showkey -s
Also checking interrupts: watch -n1 cat /proc/interrupts <-- usually IRQ 1

If there aren't events from KBC/EC, this is a BIOS or a KBC/EC 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/1872311

Title:
  Brightness hotkeys not working on Lenovo S740

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Brightness hotkeys (Fn + F11 for decrease and Fn + F12 for increase)
  do not work on Ubuntu 20.04 and Lenovo S740 laptop. The brightness
  hotkeys did not work on 19.10 either.

  I followed the guide here:
  https://wiki.ubuntu.com/Hotkeys/Troubleshooting

  In "Step-by-step Troubleshooting", none of the steps (1-7) did produce
  any reaction to brightness change key combinations. However, I am able
  to change the laptop screen brightness through the brightness applet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  elias  1447 F pulseaudio
   /dev/snd/controlC0:  elias  1447 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 16:12:01 2020
  InstallationDate: Installed on 2019-11-19 (144 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 81RS
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=101c7da4-860d-4496-ae06-d98699795f9a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-04 (7 days ago)
  dmi.bios.date: 03/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BYCN33WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga S740-14IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrBYCN33WW:bd03/10/2020:svnLENOVO:pn81RS:pvrLenovoYogaS740-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS740-14IIL:
  dmi.product.family: Yoga S740-14IIL
  dmi.product.name: 81RS
  dmi.product.sku: LENOVO_MT_81RS_BU_idea_FM_Yoga S740-14IIL
  dmi.product.version: Lenovo Yoga S740-14IIL
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1872311] Re: Brightness hotkeys not working on Lenovo S740

[Alex Hung]

It may worth a shot to ask on Lenovo's forum
(https://forums.lenovo.com/t5/English-Community/ct-p/Community-EN).
Perhaps they will forward this to developers who can take a look and
release a fix for everybody.

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

Title:
  Brightness hotkeys not working on Lenovo S740

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Brightness hotkeys (Fn + F11 for decrease and Fn + F12 for increase)
  do not work on Ubuntu 20.04 and Lenovo S740 laptop. The brightness
  hotkeys did not work on 19.10 either.

  I followed the guide here:
  https://wiki.ubuntu.com/Hotkeys/Troubleshooting

  In "Step-by-step Troubleshooting", none of the steps (1-7) did produce
  any reaction to brightness change key combinations. However, I am able
  to change the laptop screen brightness through the brightness applet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  elias  1447 F pulseaudio
   /dev/snd/controlC0:  elias  1447 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 16:12:01 2020
  InstallationDate: Installed on 2019-11-19 (144 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 81RS
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=101c7da4-860d-4496-ae06-d98699795f9a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-04 (7 days ago)
  dmi.bios.date: 03/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BYCN33WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga S740-14IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrBYCN33WW:bd03/10/2020:svnLENOVO:pn81RS:pvrLenovoYogaS740-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS740-14IIL:
  dmi.product.family: Yoga S740-14IIL
  dmi.product.name: 81RS
  dmi.product.sku: LENOVO_MT_81RS_BU_idea_FM_Yoga S740-14IIL
  dmi.product.version: Lenovo Yoga S740-14IIL
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1871248] Re: amdgpu kernel errors in Linux 5.4

[Alex Hung]

** Description changed:

+ [Impact]
+ 
+ amdgpu generates assert warning messages when retimer is not supported.
+ This behaviour can cause confusions to users.
+ 
+ [Fix]
+ 
+ This is fixed by commit a0e40018dcc3f59a. It silences ASSERTs by
+ outputing a debug message and exiting when retimer is not supported by
+ hardware.
+ 
+ [Test]
+ 
+ Verified on B450 I AORUS PRO WIFI with AMD Ryzen 3 3200G as discussed
+ on LP:1871248.
+ 
+ [Regression Potential]
+ 
+ Low. It is for unsupported hardware features, and the patch was cherry-picked
+ from upstream kernel 5.7 rc1.
+ 
+ ==
+ 
  Linux atlas 5.4.0-21-generic #25-Ubuntu SMP Sat Mar 28 13:10:28 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux
  Ubuntu 20.04 beta fresh installation. Upgrades applied.
  AMD Ryzen 3 3200G with Radeon Vega Graphics
  Motherboard: Gigabyte B450 I AORUS PRO WIFI/B450 I AORUS PRO WIFI-CF, BIOS 
F50 11/27/2019
  
- These errors keep appearing in the kernel messages. 
+ These errors keep appearing in the kernel messages.
  [3.258890] [ cut here ]
  [3.258944] WARNING: CPU: 1 PID: 621 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link.c:1737 
write_i2c_retimer_setting+0xc8/0x3e0 [amdgpu]
  [3.258945] Modules linked in: amd64_edac_mod(-) cmac algif_hash 
algif_skcipher af_alg bnep edac_mce_amd ccp kvm snd_hda_codec_realtek 
snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel 
snd_intel_nhlt snd_hda_codec snd_hda_core snd_hwdep snd_pcm crct10dif_pclmul 
ghash_clmulni_intel snd_seq_midi nls_iso8859_1 snd_seq_midi_event snd_rawmidi 
snd_seq aesni_intel iwlmvm crypto_simd mac80211 amdgpu cryptd libarc4 
glue_helper snd_seq_device amd_iommu_v2 btusb iwlwifi gpu_sched btrtl wmi_bmof 
ttm btbcm k10temp snd_timer btintel input_leds drm_kms_helper bluetooth snd 
fb_sys_fops syscopyarea cfg80211 sysfillrect soundcore sysimgblt ecdh_generic 
ecc mac_hid sch_fq_codel parport_pc ppdev lp drm parport ip_tables x_tables 
autofs4 hid_generic usbhid hid nvme crc32_pclmul i2c_piix4 ahci igb nvme_core 
i2c_algo_bit dca libahci wmi video gpio_amdpt gpio_generic
  [3.258966] CPU: 1 PID: 621 Comm: gpu-manager Not tainted 5.4.0-21-generic 
#25-Ubuntu
  [3.258967] Hardware name: Gigabyte Technology Co., Ltd. B450 I AORUS PRO 
WIFI/B450 I AORUS PRO WIFI-CF, BIOS F50 11/27/2019
  [3.259012] RIP: 0010:write_i2c_retimer_setting+0xc8/0x3e0 [amdgpu]
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  kirt   1293 F pulseaudio
-  /dev/snd/controlC0:  kirt   1293 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  kirt   1293 F pulseaudio
+  /dev/snd/controlC0:  kirt   1293 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  6 15:52:30 2020
  InstallationDate: Installed on 2020-04-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Gigabyte Technology Co., Ltd. B450 I AORUS PRO WIFI
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=9940ba5b-7683-413e-92a2-854b3816799b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-5.4.0-21-generic N/A
-  linux-backports-modules-5.4.0-21-generic  N/A
-  linux-firmware1.187
+  linux-restricted-modules-5.4.0-21-generic N/A
+  linux-backports-modules-5.4.0-21-generic  N/A
+  linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 I AORUS PRO WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450IAORUSPROWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450IAORUSPROWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450 I AORUS PRO WIFI
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

-- 
You received this bug notification because you are a member of Kernel
Packages,

[Kernel-packages] [Bug 1875921] Re: Wifi doesnt connect when I come back from sleep mode

[Alex Hung]

Try to reinitialize wifi driver: "sudo modprobe -r iwlwifi ; sudo
modprobe iwlwifi" after sleep and resume.

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

Title:
  Wifi doesnt connect when I come back from sleep mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It tries to connect when I come back from sleep mode but isn't able to
  connect. I always need to restart laptop to start using it again.

  Also while using google chrome on pressing chrome button the alignment
  of screens in mini view is towards left and has too much extra space
  on write and it doesn't gets resize according to the view of the
  screen instead gets stretched making it unable to identify.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-26-generic 5.4.0-26.30
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vinayak1953 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 29 20:48:10 2020
  InstallationDate: Installed on 2018-12-15 (501 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP EliteBook Folio 9470m
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=23b1456b-56d2-43ad-8ddb-4743100e6d3b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-26 (3 days ago)
  dmi.bios.date: 07/27/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IBD Ver. F.72
  dmi.board.name: 18DF
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 62.19
  dmi.chassis.asset.tag: CNU408BGZM
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IBDVer.F.72:bd07/27/2018:svnHewlett-Packard:pnHPEliteBookFolio9470m:pvrA1029D1102:rvnHewlett-Packard:rn18DF:rvrKBCVersion62.19:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook Folio 9470m
  dmi.product.sku: D5Y13UP#ABA
  dmi.product.version: A1029D1102
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1875672] Re: lubuntu 20.04 lts can't find touchpad

[Alex Hung]

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

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

Title:
  lubuntu 20.04 lts can't find touchpad

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Description:Ubuntu 20.04 LTS
  Release:20.04

  $ cat /proc/bus/input/devices
  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input0
  U: Uniq=
  H: Handlers=sysrq kbd event0 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0003 Vendor=046d Product=c247 Version=0110
  N: Name="Logitech G100s Optical Gaming Mouse"
  P: Phys=usb-:00:04.0-2/input0
  S: 
Sysfs=/devices/pci:00/:00:04.0/usb2/2-2/2-2:1.0/0003:046D:C247.0001/input/input1
  U: Uniq=
  H: Handlers=mouse0 event1 
  B: PROP=0
  B: EV=17
  B: KEY=ff 0 0 0 0
  B: REL=903
  B: MSC=10

  I: Bus=0003 Vendor=04f2 Product=b012 Version=0346
  N: Name="USB2.0 1.3M UVC WebCam : USB2.0"
  P: Phys=usb-:00:04.1-7/button
  S: Sysfs=/devices/pci:00/:00:04.1/usb1/1-7/1-7:1.0/input/input2
  U: Uniq=
  H: Handlers=kbd event2 
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0

  I: Bus= Vendor= Product= Version=
  N: Name="HDA NVidia Mic"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:08.0/sound/card0/input3
  U: Uniq=
  H: Handlers=event3 
  B: PROP=0
  B: EV=21
  B: SW=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA NVidia Headphone"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:08.0/sound/card0/input4
  U: Uniq=
  H: Handlers=event4 
  B: PROP=0
  B: EV=21
  B: SW=4

  
  cat /proc/version_signature 
  Ubuntu 5.4.0-26.30-generic 5.4.30

  
  lspci -vnvn
  00:00.0 Host bridge [0600]: NVIDIA Corporation MCP79 Host Bridge [10de:0a83] 
(rev b1)
  Subsystem: NVIDIA Corporation MCP79 Host Bridge [10de:cb79]
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
  Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- 
  Kernel driver in use: nForce2_smbus
  Kernel modules: i2c_nforce2, nv_tco

  00:03.3 RAM memory [0500]: NVIDIA Corporation MCP79 Memory Controller 
[10de:0a89] (rev b1)
  Subsystem: NVIDIA Corporation MCP79 Memory Controller [10de:cb79]
  Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
  Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- 
  Kernel driver in use: ohci-pci

  00:04.1 USB controller [0c03]: NVIDIA Corporation MCP79 EHCI USB 2.0 
Controller [10de:0aa6] (rev b1) (prog-if 20 [EHCI])
  Subsystem: ASUSTeK Computer Inc. MCP79 EHCI USB 2.0 Controller 
[1043:1a87]
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
  Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: ehci-pci

  00:08.0 Audio device [0403]: NVIDIA Corporation MCP79 High Definition Audio 
[10de:0ac0] (rev b1)
  Subsystem: ASUSTeK Computer Inc. MCP79 High Definition Audio 
[1043:1903]
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
  Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: snd_hda_intel
  Kernel modules: snd_hda_intel

  00:09.0 PCI bridge [0604]: NVIDIA Corporation MCP79 PCI Bridge [10de:0aab] 
(rev b1) (prog-if 01 [Subtractive decode])
  Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
  Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- 
SERR- TAbort- 
Reset- FastB2B-
  PriDiscTmr- SecDiscTmr+ DiscTmrStat- DiscTmrSERREn-
  Capabilities: 

  00:0a.0 Ethernet controller [0200]: NVIDIA Corporation MCP79 Ethernet 
[10de:0ab0] (rev b1)
  Subsystem: ASUSTeK Computer Inc. MCP79 Ethernet [1043:1215]
  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: forcedeth
  Kernel modules: forcedeth

  00:0b.0 IDE interface [0101]: NVIDIA Corporation MCP79 SATA Controller 
[10de:0ab4] (rev b1) (prog-if 85 [PCI native mode-only controller, supports bus 
mastering])
  Subsystem: ASUSTeK Computer Inc. MCP79 SATA Controller [1043:1a87]
  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWI

[Kernel-packages] [Bug 1875437] Re: Qualcomm Atheros QCA6174 [168c:003e] subsystem [1a56:1535] WIFI stops working and system breaks

[Alex Hung]

This can be similar to LP:1872351

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

Title:
  Qualcomm Atheros QCA6174 [168c:003e] subsystem [1a56:1535] WIFI stops
  working and system breaks

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a dell XPS 15 9570 laptop. I have been using Ubuntu (18, 19 and
  20) for the last two years. Everything work fine except for the wifi,
  which randomly stops working. Sometimes I can just turn off and on the
  wifi and it comes to work until next random crash. However, other
  times, when it happens, I cannot turn off wifi, it seems like the
  system breaks, I have to hard shutdown the laptop and after boot it
  works again.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-26-generic 5.4.0-26.30
  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/controlC0:  pedrolarben   1800 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 27 18:19:56 2020
  InstallationDate: Installed on 2020-04-25 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-26-generic 
root=UUID=1a07689c-3362-41b2-b2e1-ae28e49f5384 ro quiet splash 
acpi_rev_override=1 acpi_osi=Linux nouveau.modeset=0 pcie_aspm=force 
drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 
mem_sleep_default=deep mitigations=off vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1879082] Re: Kernel reporting 100% battery, always

[Alex Hung]

It looks like OS is picking up the virtual (i.e. dummy) battery from
BIOS. Do you also observe this bug when booting with Ubuntu live on a
USB drive?

Can you run "ls /sys/class/power_supply/" to check whether there are
other batteries found by kernel? Usually BIOS likes starting names from
BAT0.

Attaching acpidump file (sudo acpidump > acpi.log) will be helpful to
see what BIOS offers to kernel.

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

Title:
  Kernel reporting 100% battery, always

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running Kubuntu 20.04:  Regardless of whether the laptop is plugged-
  in, or the battery state (Even just before dying) the reported
  percentage is incorrect and the system believes it is plugged in at
  all times (see upower -d below, it is always the same).

  $ cat /proc/version_signature
  Ubuntu 5.4.0-29.33-generic 5.4.30

  $ lsb_release -a
  LSB Version:
core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04 LTS
  Release:20.04
  Codename:   focal

  $ uname -a
  Linux Vergil 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

  $ upower -d
  Device: /org/freedesktop/UPower/devices/line_power_ACAD
native-path:  ACAD
power supply: yes
updated:  Sat 16 May 2020 12:35:46 PM CDT (909 seconds ago)
has history:  no
has statistics:   no
line-power
  warning-level:   none
  online:  yes
  icon-name:  'ac-adapter-symbolic'

  Device: /org/freedesktop/UPower/devices/battery_BAT1
native-path:  BAT1
vendor:   TOSHIBA
model:PABAS0241231
serial:   
power supply: yes
updated:  Sat 16 May 2020 12:49:47 PM CDT (68 seconds ago)
has history:  yes
has statistics:   yes
battery
  present: yes
  rechargeable:yes
  state:   fully-charged
  warning-level:   none
  energy:  4294.84 Wh
  energy-empty:0 Wh
  energy-full: 4294.84 Wh
  energy-full-design:  4294.84 Wh
  energy-rate: 0 W
  voltage: 65.535 V
  percentage:  100%
  capacity:100%
  technology:  lithium-ion
  icon-name:  'battery-full-charged-symbolic'

  Device: /org/freedesktop/UPower/devices/DisplayDevice
power supply: yes
updated:  Sat 16 May 2020 12:32:09 PM CDT (1126 seconds ago)
has history:  no
has statistics:   no
battery
  present: yes
  state:   fully-charged
  warning-level:   none
  energy:  4294.84 Wh
  energy-full: 4294.84 Wh
  energy-rate: 0 W
  percentage:  100%
  icon-name:  'battery-full-charged-symbolic'

  Daemon:
daemon-version:  0.99.11
on-battery:  no
lid-is-closed:   no
lid-is-present:  yes
critical-action: HybridSleep

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sperger1191 F pulseaudio
   /dev/snd/controlC0:  sperger1191 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sat May 16 12:41:59 2020
  InstallationDate: Installed on 2020-03-11 (65 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: TOSHIBA Satellite C55-B
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=fd25621b-6551-420a-a1c5-13a0746ae679 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-10 (5 days ago)
  dmi.bios.date: 07/19/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.30
  dmi.board.asset.tag: *
  dmi.board.name: ZSWAA
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: *
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.30:bd07/19/2014:svnTOSHIBA:pnSatelliteC55-B:pvrPSCLUU-05M07V:rvnTOSHIBA:rnZSWAA:rvr1.00:cvnTOSHIBA:ct10:cvr*:
  dmi.product.family: *
  dmi.product.name:

[Kernel-packages] [Bug 1881675] Re: Intel Wireless 8260 [8086:24f3] Subsystem [8086:0010] iwlwifi Microcode SW Error ubuntu 20.04

[Alex Hung]

When my wifi card has issues after long usage, I re-init wifi driver
like "modprobe -r iwlwifi ; modprobe iwlwifi", and it may save some
troubles rebooting.

I don't have Intel wifi but this works on my Qualcomm Atheros QCA6174
(which uses ath10k_pci).

You may also clear the logs in /var/log/ directory. There are also
discussion about limiting log size (i.e.
https://serverfault.com/questions/546072/how-to-avoid-log-files-growing-
too-big)

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

Title:
  Intel Wireless 8260 [8086:24f3] Subsystem [8086:0010] iwlwifi
  Microcode SW Error ubuntu 20.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes, this bug happens and keep logging as long as I do not not
  shut down the computer. Internet becomes irresponsive, and the whole
  computer is slowed. It will keep logging until saturating the hard
  drive. I had to format the hard drive and reinstall to be able to use
  the computer again once.

  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846676] iwlwifi :02:00.0: 
Microcode SW error detected.  Restarting 0x200.
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846823] iwlwifi :02:00.0: 
Start IWL Error Log Dump:
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846829] iwlwifi :02:00.0: 
Status: 0x0040, count: 6
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846833] iwlwifi :02:00.0: 
Loaded firmware version: 36.77d01142.0
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846838] iwlwifi :02:00.0: 
0x0039 | BAD_COMMAND 
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846842] iwlwifi :02:00.0: 
0x0230 | trm_hw_status0
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846845] iwlwifi :02:00.0: 
0x | trm_hw_status1
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846849] iwlwifi :02:00.0: 
0x00024200 | branchlink2
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846853] iwlwifi :02:00.0: 
0x00039872 | interruptlink1
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846856] iwlwifi :02:00.0: 
0x | interruptlink2
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846860] iwlwifi :02:00.0: 
0x0002 | data1
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846863] iwlwifi :02:00.0: 
0xDEADBEEF | data2
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846867] iwlwifi :02:00.0: 
0xDEADBEEF | data3
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846870] iwlwifi :02:00.0: 
0x2D004C01 | beacon time
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846874] iwlwifi :02:00.0: 
0x39E4BA08 | tsf low
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846877] iwlwifi :02:00.0: 
0x0046 | tsf hi
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846880] iwlwifi :02:00.0: 
0x | time gp1
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846884] iwlwifi :02:00.0: 
0xE24C9E94 | time gp2
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846887] iwlwifi :02:00.0: 
0x0001 | uCode revision type
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846891] iwlwifi :02:00.0: 
0x0024 | uCode version major
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846894] iwlwifi :02:00.0: 
0x77D01142 | uCode version minor
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846898] iwlwifi :02:00.0: 
0x0201 | hw version
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846901] iwlwifi :02:00.0: 
0x00489008 | board version
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846905] iwlwifi :02:00.0: 
0x000D0304 | hcmd
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846908] iwlwifi :02:00.0: 
0x24022080 | isr0
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846912] iwlwifi :02:00.0: 
0x | isr1
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846915] iwlwifi :02:00.0: 
0x0820180A | isr2
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846919] iwlwifi :02:00.0: 
0x004154C0 | isr3
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846922] iwlwifi :02:00.0: 
0x | isr4
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846926] iwlwifi :02:00.0: 
0x9B5E009D | last cmd Id
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846929] iwlwifi :02:00.0: 
0x | wait_event
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846933] iwlwifi :02:00.0: 
0x0080 | l2p_control
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846936] iwlwifi :02:00.0: 
0x00010030 | l2p_duration
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846940] iwlwifi :02:00.0: 
0x003F | l2p_mhvalid
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846943] iwlwifi :02:00.0: 
0x0080 | l2p_addr_match
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846946] iwlwifi :02:00.0: 
0x000D | lmpm_pmg_sel
  Jun  1 16:58:36 maxime-lx-home kernel: [ 3799.846950] iwlwifi :02:00.0: 
0x08081421 | timestamp
  Jun  1 16:58:36 maxime-lx-home

[Kernel-packages] [Bug 1879082] Re: Kernel reporting 100% battery, always

[Alex Hung]

BAT1 is the correct one according to acpi.log in #12.

There are no obvious code error in BIOS, but let's try to see whether
kernel correct reports what BIOS reports.

When AC is connected:
  kernel's battery status: $ cat /sys/class/power_supply/BAT0/status
  BIOS battery status: sudo acpidbg -b "e _SB.PCI0.LPCB.BAT1._BST"

First number is battery state
  • Bit [0] – 1 indicates the battery is discharging.
  • Bit [1] – 1 indicates the battery is charging.

Do the same When AC is disconnected as well.

There are also other information that may be helpful:

  Battery information
sudo acpidbg -b "e _SB.PCI0.LPCB.BAT1._BIF"
sudo acpidbg -b "e _SB.PCI0.LPCB.BAT1._BIX"

  EC ready (battery gets information from EC)
sudo acpidbg -b "e _SB.PCI0.LPCB.ECOK"

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

Title:
  Kernel reporting 100% battery, always

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Running Kubuntu 20.04:  Regardless of whether the laptop is plugged-
  in, or the battery state (Even just before dying) the reported
  percentage is incorrect and the system believes it is plugged in at
  all times (see upower -d below, it is always the same).

  $ cat /proc/version_signature
  Ubuntu 5.4.0-29.33-generic 5.4.30

  $ lsb_release -a
  LSB Version:
core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04 LTS
  Release:20.04
  Codename:   focal

  $ uname -a
  Linux Vergil 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

  $ upower -d
  Device: /org/freedesktop/UPower/devices/line_power_ACAD
native-path:  ACAD
power supply: yes
updated:  Sat 16 May 2020 12:35:46 PM CDT (909 seconds ago)
has history:  no
has statistics:   no
line-power
  warning-level:   none
  online:  yes
  icon-name:  'ac-adapter-symbolic'

  Device: /org/freedesktop/UPower/devices/battery_BAT1
native-path:  BAT1
vendor:   TOSHIBA
model:PABAS0241231
serial:   
power supply: yes
updated:  Sat 16 May 2020 12:49:47 PM CDT (68 seconds ago)
has history:  yes
has statistics:   yes
battery
  present: yes
  rechargeable:yes
  state:   fully-charged
  warning-level:   none
  energy:  4294.84 Wh
  energy-empty:0 Wh
  energy-full: 4294.84 Wh
  energy-full-design:  4294.84 Wh
  energy-rate: 0 W
  voltage: 65.535 V
  percentage:  100%
  capacity:100%
  technology:  lithium-ion
  icon-name:  'battery-full-charged-symbolic'

  Device: /org/freedesktop/UPower/devices/DisplayDevice
power supply: yes
updated:  Sat 16 May 2020 12:32:09 PM CDT (1126 seconds ago)
has history:  no
has statistics:   no
battery
  present: yes
  state:   fully-charged
  warning-level:   none
  energy:  4294.84 Wh
  energy-full: 4294.84 Wh
  energy-rate: 0 W
  percentage:  100%
  icon-name:  'battery-full-charged-symbolic'

  Daemon:
daemon-version:  0.99.11
on-battery:  no
lid-is-closed:   no
lid-is-present:  yes
critical-action: HybridSleep

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sperger1191 F pulseaudio
   /dev/snd/controlC0:  sperger1191 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sat May 16 12:41:59 2020
  InstallationDate: Installed on 2020-03-11 (65 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: TOSHIBA Satellite C55-B
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=fd25621b-6551-420a-a1c5-13a0746ae679 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-10 (5 days ago)
  dmi.bios.date: 07/19/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.30
  dmi.board.

[Kernel-packages] [Bug 1879082] Re: Kernel reporting 100% battery, always

[Alex Hung]

In fact I suspect EC firmware may be mis-behaving. You can try to remove
all power sources (AC & battery) for a min to reset EC.

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

Title:
  Kernel reporting 100% battery, always

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Running Kubuntu 20.04:  Regardless of whether the laptop is plugged-
  in, or the battery state (Even just before dying) the reported
  percentage is incorrect and the system believes it is plugged in at
  all times (see upower -d below, it is always the same).

  $ cat /proc/version_signature
  Ubuntu 5.4.0-29.33-generic 5.4.30

  $ lsb_release -a
  LSB Version:
core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04 LTS
  Release:20.04
  Codename:   focal

  $ uname -a
  Linux Vergil 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

  $ upower -d
  Device: /org/freedesktop/UPower/devices/line_power_ACAD
native-path:  ACAD
power supply: yes
updated:  Sat 16 May 2020 12:35:46 PM CDT (909 seconds ago)
has history:  no
has statistics:   no
line-power
  warning-level:   none
  online:  yes
  icon-name:  'ac-adapter-symbolic'

  Device: /org/freedesktop/UPower/devices/battery_BAT1
native-path:  BAT1
vendor:   TOSHIBA
model:PABAS0241231
serial:   
power supply: yes
updated:  Sat 16 May 2020 12:49:47 PM CDT (68 seconds ago)
has history:  yes
has statistics:   yes
battery
  present: yes
  rechargeable:yes
  state:   fully-charged
  warning-level:   none
  energy:  4294.84 Wh
  energy-empty:0 Wh
  energy-full: 4294.84 Wh
  energy-full-design:  4294.84 Wh
  energy-rate: 0 W
  voltage: 65.535 V
  percentage:  100%
  capacity:100%
  technology:  lithium-ion
  icon-name:  'battery-full-charged-symbolic'

  Device: /org/freedesktop/UPower/devices/DisplayDevice
power supply: yes
updated:  Sat 16 May 2020 12:32:09 PM CDT (1126 seconds ago)
has history:  no
has statistics:   no
battery
  present: yes
  state:   fully-charged
  warning-level:   none
  energy:  4294.84 Wh
  energy-full: 4294.84 Wh
  energy-rate: 0 W
  percentage:  100%
  icon-name:  'battery-full-charged-symbolic'

  Daemon:
daemon-version:  0.99.11
on-battery:  no
lid-is-closed:   no
lid-is-present:  yes
critical-action: HybridSleep

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sperger1191 F pulseaudio
   /dev/snd/controlC0:  sperger1191 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sat May 16 12:41:59 2020
  InstallationDate: Installed on 2020-03-11 (65 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: TOSHIBA Satellite C55-B
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=fd25621b-6551-420a-a1c5-13a0746ae679 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-10 (5 days ago)
  dmi.bios.date: 07/19/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.30
  dmi.board.asset.tag: *
  dmi.board.name: ZSWAA
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: *
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.30:bd07/19/2014:svnTOSHIBA:pnSatelliteC55-B:pvrPSCLUU-05M07V:rvnTOSHIBA:rnZSWAA:rvr1.00:cvnTOSHIBA:ct10:cvr*:
  dmi.product.family: *
  dmi.product.name: Satellite C55-B
  dmi.product.sku: PSCLUU
  dmi.product.version: PSCLUU-05M07V
  dmi.sys.vendor: TOSHIBA

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

-- 
Mailing list: https://launchpad.net

[Kernel-packages] [Bug 1864527] [NEW] CPU0 is busy after S3 in Dell Precision 3530

[Alex Hung]

Public bug reported:

CPU0 (and sometimes other cores too) is not entering C10 half of the
time when system is idle. "top" shows a touchpad driver takes 5%~6% of
CPU usage, and "/proc/interrupts" reveals considerable interrupts from
the touchpad device. This results in additional 4~5 watt power
consumption.

This anomaly can be workarounded by simply touching the touchpad - in
other words, it is more visible when using a USB mouse.

This can be fixed by a kernel 5.5 commit 52cf93e63ee6 which is included
in bionic (4.15) and focal kernel (5.4) but not in eoan (5.3).

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

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

Title:
  CPU0 is busy after S3 in Dell Precision 3530

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  CPU0 (and sometimes other cores too) is not entering C10 half of the
  time when system is idle. "top" shows a touchpad driver takes 5%~6% of
  CPU usage, and "/proc/interrupts" reveals considerable interrupts from
  the touchpad device. This results in additional 4~5 watt power
  consumption.

  This anomaly can be workarounded by simply touching the touchpad - in
  other words, it is more visible when using a USB mouse.

  This can be fixed by a kernel 5.5 commit 52cf93e63ee6 which is
  included in bionic (4.15) and focal kernel (5.4) but not in eoan
  (5.3).

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

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

[Kernel-packages] [Bug 1864527] Re: CPU0 is busy after S3 in Dell Precision 3530

[Alex Hung]

apport information

** Tags added: apport-collected bionic

** Description changed:

  CPU0 (and sometimes other cores too) is not entering C10 half of the
  time when system is idle. "top" shows a touchpad driver takes 5%~6% of
  CPU usage, and "/proc/interrupts" reveals considerable interrupts from
  the touchpad device. This results in additional 4~5 watt power
  consumption.
  
  This anomaly can be workarounded by simply touching the touchpad - in
  other words, it is more visible when using a USB mouse.
  
- This can be fixed by a kernel 5.5 commit 52cf93e63ee6 which is included
- in bionic (4.15) and focal kernel (5.4) but not in eoan (5.3).
+ This can be fixed by a kernel 5.5 commit 52cf93e63ee6 which is included in 
bionic (4.15) and focal kernel (5.4) but not in eoan (5.3).
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.11
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  alexhung   3397 F pulseaudio
+  /dev/snd/pcmC0D0p:   alexhung   3397 F...m pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2019-10-29 (118 days ago)
+ InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
+ MachineType: Dell Inc. Precision 3530
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=b0c947ea-9aa0-4ca2-a634-7b925900c129 ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
+ RelatedPackageVersions:
+  linux-restricted-modules-5.3.0-40-generic N/A
+  linux-backports-modules-5.3.0-40-generic  N/A
+  linux-firmware1.173.14
+ Tags:  bionic
+ Uname: Linux 5.3.0-40-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 01/30/2018
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 99.6.4
+ dmi.board.vendor: Dell Inc.
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr99.6.4:bd01/30/2018:svnDellInc.:pnPrecision3530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
+ dmi.product.family: Precision
+ dmi.product.name: Precision 3530
+ dmi.product.sku: 0820
+ dmi.sys.vendor: Dell Inc.

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

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

Title:
  CPU0 is busy after S3 in Dell Precision 3530

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  CPU0 (and sometimes other cores too) is not entering C10 half of the
  time when system is idle. "top" shows a touchpad driver takes 5%~6% of
  CPU usage, and "/proc/interrupts" reveals considerable interrupts from
  the touchpad device. This results in additional 4~5 watt power
  consumption.

  This anomaly can be workarounded by simply touching the touchpad - in
  other words, it is more visible when using a USB mouse.

  This can be fixed by a kernel 5.5 commit 52cf93e63ee6 which is included in 
bionic (4.15) and focal kernel (5.4) but not in eoan (5.3).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alexhung   3397 F pulseaudio
   /dev/snd/pcmC0D0p:   alexhung   3397 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-10-29 (118 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Dell Inc. Precision 3530
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=b0c947ea-9aa0-4ca2-a634-7b925900c129 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 99.6.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr99.6.4:bd01/30/2018:svnDellInc.:pnPrecision3530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 3530
  dmi.product.sku: 0820
  dmi.sys.vendor: Dell Inc.

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

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

[Alex Hung]

apport information

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

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

Title:
  CPU0 is busy after S3 in Dell Precision 3530

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  CPU0 (and sometimes other cores too) is not entering C10 half of the
  time when system is idle. "top" shows a touchpad driver takes 5%~6% of
  CPU usage, and "/proc/interrupts" reveals considerable interrupts from
  the touchpad device. This results in additional 4~5 watt power
  consumption.

  This anomaly can be workarounded by simply touching the touchpad - in
  other words, it is more visible when using a USB mouse.

  This can be fixed by a kernel 5.5 commit 52cf93e63ee6 which is included in 
bionic (4.15) and focal kernel (5.4) but not in eoan (5.3).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alexhung   3397 F pulseaudio
   /dev/snd/pcmC0D0p:   alexhung   3397 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-10-29 (118 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Dell Inc. Precision 3530
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=b0c947ea-9aa0-4ca2-a634-7b925900c129 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 99.6.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr99.6.4:bd01/30/2018:svnDellInc.:pnPrecision3530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 3530
  dmi.product.sku: 0820
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1864527] RfKill.txt

[Alex Hung]

apport information

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

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

Title:
  CPU0 is busy after S3 in Dell Precision 3530

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  CPU0 (and sometimes other cores too) is not entering C10 half of the
  time when system is idle. "top" shows a touchpad driver takes 5%~6% of
  CPU usage, and "/proc/interrupts" reveals considerable interrupts from
  the touchpad device. This results in additional 4~5 watt power
  consumption.

  This anomaly can be workarounded by simply touching the touchpad - in
  other words, it is more visible when using a USB mouse.

  This can be fixed by a kernel 5.5 commit 52cf93e63ee6 which is included in 
bionic (4.15) and focal kernel (5.4) but not in eoan (5.3).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alexhung   3397 F pulseaudio
   /dev/snd/pcmC0D0p:   alexhung   3397 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-10-29 (118 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Dell Inc. Precision 3530
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=b0c947ea-9aa0-4ca2-a634-7b925900c129 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 99.6.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr99.6.4:bd01/30/2018:svnDellInc.:pnPrecision3530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 3530
  dmi.product.sku: 0820
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1864527] PulseList.txt

[Alex Hung]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1864527/+attachment/5330679/+files/PulseList.txt

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

Title:
  CPU0 is busy after S3 in Dell Precision 3530

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  CPU0 (and sometimes other cores too) is not entering C10 half of the
  time when system is idle. "top" shows a touchpad driver takes 5%~6% of
  CPU usage, and "/proc/interrupts" reveals considerable interrupts from
  the touchpad device. This results in additional 4~5 watt power
  consumption.

  This anomaly can be workarounded by simply touching the touchpad - in
  other words, it is more visible when using a USB mouse.

  This can be fixed by a kernel 5.5 commit 52cf93e63ee6 which is included in 
bionic (4.15) and focal kernel (5.4) but not in eoan (5.3).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alexhung   3397 F pulseaudio
   /dev/snd/pcmC0D0p:   alexhung   3397 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-10-29 (118 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Dell Inc. Precision 3530
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=b0c947ea-9aa0-4ca2-a634-7b925900c129 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 99.6.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr99.6.4:bd01/30/2018:svnDellInc.:pnPrecision3530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 3530
  dmi.product.sku: 0820
  dmi.sys.vendor: Dell Inc.

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

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

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

[Alex Hung]

apport information

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

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

Title:
  CPU0 is busy after S3 in Dell Precision 3530

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  CPU0 (and sometimes other cores too) is not entering C10 half of the
  time when system is idle. "top" shows a touchpad driver takes 5%~6% of
  CPU usage, and "/proc/interrupts" reveals considerable interrupts from
  the touchpad device. This results in additional 4~5 watt power
  consumption.

  This anomaly can be workarounded by simply touching the touchpad - in
  other words, it is more visible when using a USB mouse.

  This can be fixed by a kernel 5.5 commit 52cf93e63ee6 which is included in 
bionic (4.15) and focal kernel (5.4) but not in eoan (5.3).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alexhung   3397 F pulseaudio
   /dev/snd/pcmC0D0p:   alexhung   3397 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-10-29 (118 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Dell Inc. Precision 3530
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=b0c947ea-9aa0-4ca2-a634-7b925900c129 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 99.6.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr99.6.4:bd01/30/2018:svnDellInc.:pnPrecision3530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 3530
  dmi.product.sku: 0820
  dmi.sys.vendor: Dell Inc.

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

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

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

[Alex Hung]

apport information

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

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

Title:
  CPU0 is busy after S3 in Dell Precision 3530

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  CPU0 (and sometimes other cores too) is not entering C10 half of the
  time when system is idle. "top" shows a touchpad driver takes 5%~6% of
  CPU usage, and "/proc/interrupts" reveals considerable interrupts from
  the touchpad device. This results in additional 4~5 watt power
  consumption.

  This anomaly can be workarounded by simply touching the touchpad - in
  other words, it is more visible when using a USB mouse.

  This can be fixed by a kernel 5.5 commit 52cf93e63ee6 which is included in 
bionic (4.15) and focal kernel (5.4) but not in eoan (5.3).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alexhung   3397 F pulseaudio
   /dev/snd/pcmC0D0p:   alexhung   3397 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-10-29 (118 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Dell Inc. Precision 3530
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=b0c947ea-9aa0-4ca2-a634-7b925900c129 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 99.6.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr99.6.4:bd01/30/2018:svnDellInc.:pnPrecision3530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 3530
  dmi.product.sku: 0820
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1864527] CRDA.txt

[Alex Hung]

apport information

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

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

Title:
  CPU0 is busy after S3 in Dell Precision 3530

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  CPU0 (and sometimes other cores too) is not entering C10 half of the
  time when system is idle. "top" shows a touchpad driver takes 5%~6% of
  CPU usage, and "/proc/interrupts" reveals considerable interrupts from
  the touchpad device. This results in additional 4~5 watt power
  consumption.

  This anomaly can be workarounded by simply touching the touchpad - in
  other words, it is more visible when using a USB mouse.

  This can be fixed by a kernel 5.5 commit 52cf93e63ee6 which is included in 
bionic (4.15) and focal kernel (5.4) but not in eoan (5.3).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alexhung   3397 F pulseaudio
   /dev/snd/pcmC0D0p:   alexhung   3397 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-10-29 (118 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Dell Inc. Precision 3530
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=b0c947ea-9aa0-4ca2-a634-7b925900c129 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 99.6.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr99.6.4:bd01/30/2018:svnDellInc.:pnPrecision3530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 3530
  dmi.product.sku: 0820
  dmi.sys.vendor: Dell Inc.

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

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

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

[Alex Hung]

apport information

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

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

Title:
  CPU0 is busy after S3 in Dell Precision 3530

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  CPU0 (and sometimes other cores too) is not entering C10 half of the
  time when system is idle. "top" shows a touchpad driver takes 5%~6% of
  CPU usage, and "/proc/interrupts" reveals considerable interrupts from
  the touchpad device. This results in additional 4~5 watt power
  consumption.

  This anomaly can be workarounded by simply touching the touchpad - in
  other words, it is more visible when using a USB mouse.

  This can be fixed by a kernel 5.5 commit 52cf93e63ee6 which is included in 
bionic (4.15) and focal kernel (5.4) but not in eoan (5.3).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alexhung   3397 F pulseaudio
   /dev/snd/pcmC0D0p:   alexhung   3397 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-10-29 (118 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Dell Inc. Precision 3530
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=b0c947ea-9aa0-4ca2-a634-7b925900c129 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 99.6.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr99.6.4:bd01/30/2018:svnDellInc.:pnPrecision3530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 3530
  dmi.product.sku: 0820
  dmi.sys.vendor: Dell Inc.

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

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

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

[Alex Hung]

apport information

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

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

Title:
  CPU0 is busy after S3 in Dell Precision 3530

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  CPU0 (and sometimes other cores too) is not entering C10 half of the
  time when system is idle. "top" shows a touchpad driver takes 5%~6% of
  CPU usage, and "/proc/interrupts" reveals considerable interrupts from
  the touchpad device. This results in additional 4~5 watt power
  consumption.

  This anomaly can be workarounded by simply touching the touchpad - in
  other words, it is more visible when using a USB mouse.

  This can be fixed by a kernel 5.5 commit 52cf93e63ee6 which is included in 
bionic (4.15) and focal kernel (5.4) but not in eoan (5.3).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alexhung   3397 F pulseaudio
   /dev/snd/pcmC0D0p:   alexhung   3397 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-10-29 (118 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Dell Inc. Precision 3530
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=b0c947ea-9aa0-4ca2-a634-7b925900c129 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 99.6.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr99.6.4:bd01/30/2018:svnDellInc.:pnPrecision3530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 3530
  dmi.product.sku: 0820
  dmi.sys.vendor: Dell Inc.

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

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

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

[Alex Hung]

apport information

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

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

Title:
  CPU0 is busy after S3 in Dell Precision 3530

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  CPU0 (and sometimes other cores too) is not entering C10 half of the
  time when system is idle. "top" shows a touchpad driver takes 5%~6% of
  CPU usage, and "/proc/interrupts" reveals considerable interrupts from
  the touchpad device. This results in additional 4~5 watt power
  consumption.

  This anomaly can be workarounded by simply touching the touchpad - in
  other words, it is more visible when using a USB mouse.

  This can be fixed by a kernel 5.5 commit 52cf93e63ee6 which is included in 
bionic (4.15) and focal kernel (5.4) but not in eoan (5.3).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alexhung   3397 F pulseaudio
   /dev/snd/pcmC0D0p:   alexhung   3397 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-10-29 (118 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Dell Inc. Precision 3530
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=b0c947ea-9aa0-4ca2-a634-7b925900c129 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 99.6.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr99.6.4:bd01/30/2018:svnDellInc.:pnPrecision3530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 3530
  dmi.product.sku: 0820
  dmi.sys.vendor: Dell Inc.

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

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

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

[Alex Hung]

apport information

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

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

Title:
  CPU0 is busy after S3 in Dell Precision 3530

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  CPU0 (and sometimes other cores too) is not entering C10 half of the
  time when system is idle. "top" shows a touchpad driver takes 5%~6% of
  CPU usage, and "/proc/interrupts" reveals considerable interrupts from
  the touchpad device. This results in additional 4~5 watt power
  consumption.

  This anomaly can be workarounded by simply touching the touchpad - in
  other words, it is more visible when using a USB mouse.

  This can be fixed by a kernel 5.5 commit 52cf93e63ee6 which is included in 
bionic (4.15) and focal kernel (5.4) but not in eoan (5.3).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alexhung   3397 F pulseaudio
   /dev/snd/pcmC0D0p:   alexhung   3397 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-10-29 (118 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Dell Inc. Precision 3530
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=b0c947ea-9aa0-4ca2-a634-7b925900c129 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 99.6.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr99.6.4:bd01/30/2018:svnDellInc.:pnPrecision3530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 3530
  dmi.product.sku: 0820
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1864527] IwConfig.txt

[Alex Hung]

apport information

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

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

Title:
  CPU0 is busy after S3 in Dell Precision 3530

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  CPU0 (and sometimes other cores too) is not entering C10 half of the
  time when system is idle. "top" shows a touchpad driver takes 5%~6% of
  CPU usage, and "/proc/interrupts" reveals considerable interrupts from
  the touchpad device. This results in additional 4~5 watt power
  consumption.

  This anomaly can be workarounded by simply touching the touchpad - in
  other words, it is more visible when using a USB mouse.

  This can be fixed by a kernel 5.5 commit 52cf93e63ee6 which is included in 
bionic (4.15) and focal kernel (5.4) but not in eoan (5.3).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alexhung   3397 F pulseaudio
   /dev/snd/pcmC0D0p:   alexhung   3397 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-10-29 (118 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Dell Inc. Precision 3530
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=b0c947ea-9aa0-4ca2-a634-7b925900c129 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 99.6.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr99.6.4:bd01/30/2018:svnDellInc.:pnPrecision3530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 3530
  dmi.product.sku: 0820
  dmi.sys.vendor: Dell Inc.

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

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

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

[Alex Hung]

apport information

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

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

Title:
  CPU0 is busy after S3 in Dell Precision 3530

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  CPU0 (and sometimes other cores too) is not entering C10 half of the
  time when system is idle. "top" shows a touchpad driver takes 5%~6% of
  CPU usage, and "/proc/interrupts" reveals considerable interrupts from
  the touchpad device. This results in additional 4~5 watt power
  consumption.

  This anomaly can be workarounded by simply touching the touchpad - in
  other words, it is more visible when using a USB mouse.

  This can be fixed by a kernel 5.5 commit 52cf93e63ee6 which is included in 
bionic (4.15) and focal kernel (5.4) but not in eoan (5.3).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alexhung   3397 F pulseaudio
   /dev/snd/pcmC0D0p:   alexhung   3397 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-10-29 (118 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Dell Inc. Precision 3530
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=b0c947ea-9aa0-4ca2-a634-7b925900c129 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 99.6.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr99.6.4:bd01/30/2018:svnDellInc.:pnPrecision3530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 3530
  dmi.product.sku: 0820
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1864527] ProcEnviron.txt

[Alex Hung]

apport information

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

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

Title:
  CPU0 is busy after S3 in Dell Precision 3530

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  CPU0 (and sometimes other cores too) is not entering C10 half of the
  time when system is idle. "top" shows a touchpad driver takes 5%~6% of
  CPU usage, and "/proc/interrupts" reveals considerable interrupts from
  the touchpad device. This results in additional 4~5 watt power
  consumption.

  This anomaly can be workarounded by simply touching the touchpad - in
  other words, it is more visible when using a USB mouse.

  This can be fixed by a kernel 5.5 commit 52cf93e63ee6 which is included in 
bionic (4.15) and focal kernel (5.4) but not in eoan (5.3).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alexhung   3397 F pulseaudio
   /dev/snd/pcmC0D0p:   alexhung   3397 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-10-29 (118 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Dell Inc. Precision 3530
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=b0c947ea-9aa0-4ca2-a634-7b925900c129 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 99.6.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr99.6.4:bd01/30/2018:svnDellInc.:pnPrecision3530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 3530
  dmi.product.sku: 0820
  dmi.sys.vendor: Dell Inc.

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

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

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

[Alex Hung]

apport information

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

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

Title:
  CPU0 is busy after S3 in Dell Precision 3530

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  CPU0 (and sometimes other cores too) is not entering C10 half of the
  time when system is idle. "top" shows a touchpad driver takes 5%~6% of
  CPU usage, and "/proc/interrupts" reveals considerable interrupts from
  the touchpad device. This results in additional 4~5 watt power
  consumption.

  This anomaly can be workarounded by simply touching the touchpad - in
  other words, it is more visible when using a USB mouse.

  This can be fixed by a kernel 5.5 commit 52cf93e63ee6 which is included in 
bionic (4.15) and focal kernel (5.4) but not in eoan (5.3).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alexhung   3397 F pulseaudio
   /dev/snd/pcmC0D0p:   alexhung   3397 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-10-29 (118 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Dell Inc. Precision 3530
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=b0c947ea-9aa0-4ca2-a634-7b925900c129 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 99.6.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr99.6.4:bd01/30/2018:svnDellInc.:pnPrecision3530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 3530
  dmi.product.sku: 0820
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1864527] Re: CPU0 is busy after S3 in Dell Precision 3530

[Alex Hung]

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

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

Title:
  CPU0 is busy after S3 in Dell Precision 3530

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Eoan:
  New

Bug description:
  CPU0 (and sometimes other cores too) is not entering C10 half of the
  time when system is idle. "top" shows a touchpad driver takes 5%~6% of
  CPU usage, and "/proc/interrupts" reveals considerable interrupts from
  the touchpad device. This results in additional 4~5 watt power
  consumption.

  This anomaly can be workarounded by simply touching the touchpad - in
  other words, it is more visible when using a USB mouse.

  This can be fixed by a kernel 5.5 commit 52cf93e63ee6 which is included in 
bionic (4.15) and focal kernel (5.4) but not in eoan (5.3).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alexhung   3397 F pulseaudio
   /dev/snd/pcmC0D0p:   alexhung   3397 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-10-29 (118 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Dell Inc. Precision 3530
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=b0c947ea-9aa0-4ca2-a634-7b925900c129 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 99.6.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr99.6.4:bd01/30/2018:svnDellInc.:pnPrecision3530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 3530
  dmi.product.sku: 0820
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1864527] Re: CPU0 is busy after S3 in Dell Precision 3530

[Alex Hung]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Alex Hung (alexhung)

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

Title:
  CPU0 is busy after S3 in Dell Precision 3530

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in linux source package in Focal:
  Fix Released

Bug description:
  CPU0 (and sometimes other cores too) is not entering C10 half of the
  time when system is idle. "top" shows a touchpad driver takes 5%~6% of
  CPU usage, and "/proc/interrupts" reveals considerable interrupts from
  the touchpad device. This results in additional 4~5 watt power
  consumption.

  This anomaly can be workarounded by simply touching the touchpad - in
  other words, it is more visible when using a USB mouse.

  This can be fixed by a kernel 5.5 commit 52cf93e63ee6 which is included in 
bionic (4.15) and focal kernel (5.4) but not in eoan (5.3).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alexhung   3397 F pulseaudio
   /dev/snd/pcmC0D0p:   alexhung   3397 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-10-29 (118 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Dell Inc. Precision 3530
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=b0c947ea-9aa0-4ca2-a634-7b925900c129 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 99.6.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr99.6.4:bd01/30/2018:svnDellInc.:pnPrecision3530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 3530
  dmi.product.sku: 0820
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1864895] Re: dmseg report multiple "ACPI Error" and "ACPI BIOS Error"

[Alex Hung]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Alex Hung (alexhung)

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

Title:
  dmseg report multiple "ACPI Error" and "ACPI BIOS Error"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  'lsb_release -rd':
  Description:  Ubuntu 19.10
  Release:  19.10

  'cat /proc/version_signature > version.log':
  Ubuntu 5.3.0-40.32-generic 5.3.18

  'sudo lspci -vnvn > lspci-vnvn.log' as attachments.

  'dmesg | grep "Error"':
  [0.214136] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.TPLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.214145] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.214196] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.214200] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.214203] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.214205] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.216645] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.216648] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.216652] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.216654] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.219087] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.219091] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.219094] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.219097] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.221521] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS04._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.221524] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.221527] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS04._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.221529] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.223957] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS05._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.223961] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.226392] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS06._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.226396] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.226399] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS06._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.226401] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.228826] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS07._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.228829] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.231260] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS08._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.231263] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.233688] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS09._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.233691] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.233694] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS09._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.233696] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.236125] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS10._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.236128] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.238559] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS11._UPC], AE_ALREADY_EXISTS (20190703/dswload2-

[Kernel-packages] [Bug 1864895] Re: dmseg report multiple "ACPI Error" and "ACPI BIOS Error"

[Alex Hung]

There are two types of ACPI errors observed: AE_ALREADY_EXISTS and
AE_NOT_FOUND

The former, AE_ALREADY_EXISTS, usually happens

1) when BIOS loads multiple SSDTs (in /sys/firmware/acpi/tables) that
contains the objects with the same names (and usually the same functions
too). Naming conflicts prevent kernel to load all of them correctly.

2) BIOS's ACPI methods are not serialized and multiple calls the same
methods occur.

I would guess we are seeing scenario 1 here. They are usually harmless
because a copy of working SSDT is loaded while duplicated ones are
discarded.

The later, AE_NOT_FOUND, is the opposite. This occurs when BIOS does NOT
load SSDTs and therefore kernel is not able to get information and
perform accordingly.

Neither types of error messages can be fixed without BIOS fixes.

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

Title:
  dmseg report multiple "ACPI Error" and "ACPI BIOS Error"

Status in linux package in Ubuntu:
  Triaged

Bug description:
  'lsb_release -rd':
  Description:  Ubuntu 19.10
  Release:  19.10

  'cat /proc/version_signature > version.log':
  Ubuntu 5.3.0-40.32-generic 5.3.18

  'sudo lspci -vnvn > lspci-vnvn.log' as attachments.

  'dmesg | grep "Error"':
  [0.214136] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.TPLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.214145] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.214196] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.214200] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.214203] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.214205] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.216645] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.216648] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.216652] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.216654] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.219087] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.219091] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.219094] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.219097] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.221521] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS04._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.221524] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.221527] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS04._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.221529] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.223957] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS05._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.223961] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.226392] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS06._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.226396] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.226399] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS06._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.226401] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.228826] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS07._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.228829] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.231260] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS08._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.231263] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.233688] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS09._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.233691] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psob

[Kernel-packages] [Bug 1864895] Re: dmseg report multiple "ACPI Error" and "ACPI BIOS Error"

[Alex Hung]

Fortunately, all of the failing ACPI methods are optional, and there are
good chances that Linux / Ubuntu will work without them. There are three
types of devices *might* be affected according to the error messages:

1. USB (\_SB.PCI0.XHC.RHUB...)- but USB ports and devices should just-
work without BIOS code, which are usually for OEM customization.

2. Touchpad (\_SB.PCI0.I2Cx...) - error messages are reported for i2c-2
and i2c-3, but it is likely the touchpad is connected to i2c-1. Please
check whether you are experience problems with your touchpad.

3. Switchable graphics (\_SB.PCI0.PEG0...)- but error messages are
"AE_ALREADY_EXISTS". lspci also shows no discrete VGA present on this
system, and nothing to worry about.


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

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

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

Title:
  dmseg report multiple "ACPI Error" and "ACPI BIOS Error"

Status in linux package in Ubuntu:
  Triaged

Bug description:
  'lsb_release -rd':
  Description:  Ubuntu 19.10
  Release:  19.10

  'cat /proc/version_signature > version.log':
  Ubuntu 5.3.0-40.32-generic 5.3.18

  'sudo lspci -vnvn > lspci-vnvn.log' as attachments.

  'dmesg | grep "Error"':
  [0.214136] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.TPLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.214145] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.214196] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.214200] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.214203] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.214205] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.216645] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.216648] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.216652] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.216654] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.219087] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.219091] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.219094] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.219097] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.221521] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS04._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.221524] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.221527] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS04._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.221529] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.223957] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS05._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.223961] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.226392] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS06._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.226396] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.226399] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS06._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.226401] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.228826] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS07._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.228829] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.231260] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS08._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.231263] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.233688] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS09._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.233691] ACPI Error:

[Kernel-packages] [Bug 1865170] Re: lid close simply turns off laptop screen

[Alex Hung]

There are a few s2idle fixes and workaround in mainline kernel, and it
may worth a try. If it can fix your problem, fixes can be backported to
bionic

latest mainline kernel: https://kernel.ubuntu.com/~kernel-
ppa/mainline/v5.6-rc4/

instructions: https://askubuntu.com/questions/879888/how-do-i-update-
kernel-to-the-latest-mainline-version

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

Title:
  lid close simply turns off laptop screen

Status in gnome-session package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1)
  ubuntu-session version: 3.28.1-0ubuntu3
  Expected behavior: On laptop screen close, system should suspend
  Actual behavior: On laptop screen close, laptop screen disabled

  Previously, I triggered 'suspend when laptop lid is closed' in gnome-
  tweaks. This worked fine until about 2-3 days ago, when I came back to
  work with a dead laptop (I don't charge overnight, usually, but I do
  use a dock at work). Now, whenever I close my laptop screen, it
  doesn't trigger sleep - instead, it simply disables the laptop screen,
  resulting in my external monitor being used as the only output screen.
  Once I re-open my laptop, the laptop screen is re-enabled as the
  primary monitor.

  This happens regardless of connection to my dock. I tested this by
  unplugging my laptop, closing it, letting it sit for 3 minutes, then
  re-opening it. While the laptop was closed, fans still ran. When I re-
  opened my laptop, the lock screen didn't appear.

  Links to attempted fixes that didn't work:

  - 
https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate
  - 
https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close
  - 
https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369
  - 
https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid

  Results of attempted fixes:
  - mem_sleep: no behavior change (files correctly modified)
  - pm-hibernate: first run, hangs until I kill the process. future runs result 
in exit code 1.
  - update bios: already on latest bios
  - logind.conf: no behavior change
  - gnome tweaks: no behavior change

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-session 3.28.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18
  Uname: Linux 4.15.0-1073-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 28 10:23:52 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1
  InstallationDate: Installed on 2020-01-08 (51 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  colton 4205 F pulseaudio
   /dev/snd/controlC0:  colton 4205 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-08 (53 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 7390
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem 
root=UUID=ef2a7f80-1cfd-48d6-a2be-0875e4832f2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1073-oem N/A
   linux-backports-modules-4.15.0-1073-oem  N/A
   linux-firmware   1.173.15
  Tags:  bionic
  Uname: Linux 4.15.0-1073-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0377MH
  dmi.board.vendor: Dell Inc.

[Kernel-packages] [Bug 1865570] Re: suspend only works once on ThinkPad X1 Carbon gen 7

[Alex Hung]

Some system does not work well with s2idle, but they might work with
regular suspend (s3).

Please try "echo deep | sudo tee /sys/power/mem_sleep" to switch to s3,
and verify whether this is s2idle related or a power management issue
with e1000e driver.

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

Title:
  suspend only works once on ThinkPad X1 Carbon gen 7

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  5.4.0-16 and 5.4.0-17 go to suspend when the lid is closed, but *only
  once* after boot. On subsequent attempts, when the lid it closed,
  backlight and wifi are turned off, but system does not suspend.

  First successful suspend:
  [ 147.413295] PM: suspend entry (s2idle)
  [ 147.416601] Filesystems sync: 0.003 seconds
  [ 147.419371] Freezing user space processes ... (elapsed 0.001 seconds) done.
  [ 147.421210] OOM killer disabled.
  [ 147.421210] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [ 147.422375] printk: Suspending console(s) (use no_console_suspend to debug)
  [ 147.422630] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local 
choice (Reason: 3=DEAUTH_LEAVING)
  [ 147.527810] e1000e: EEE TX LPI TIMER: 0011
  [ 150.246317] ACPI: EC: interrupt blocked
  [ 881.134544] ACPI: EC: interrupt unblocked
  [ 883.933255] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
  [ 884.047802] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
  [ 884.112730] iwlwifi :00:14.3: FW already configured (0) - re-configuring
  [ 886.815475] e1000e :00:1f.6 enp0s31f6: PHY Wakeup cause - Unicast Packet
  [ 887.485832] e1000e :00:1f.6 enp0s31f6: Hardware Error
  [ 888.016931] OOM killer enabled.
  [ 888.016932] Restarting tasks ... done.
  [ 888.060613] PM: suspend exit

  Second unsuccessful suspend:
  [ 907.584802] PM: suspend entry (s2idle)
  [ 907.589779] Filesystems sync: 0.004 seconds
  [ 907.591416] Freezing user space processes ... (elapsed 0.002 seconds) done.
  [ 907.593518] OOM killer disabled.
  [ 907.593518] Freezing remaining freezable tasks ... (elapsed 0.328 seconds) 
done.
  [ 907.921560] printk: Suspending console(s) (use no_console_suspend to debug)
  [ 907.922127] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local 
choice (Reason: 3=DEAUTH_LEAVING)
  [ 908.024438] e1000e: EEE TX LPI TIMER: 0011
  [ 909.916364] PM: pci_pm_suspend(): e1000e_pm_suspend+0x0/0x80 [e1000e] 
returns -2
  [ 909.916367] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -2
  [ 909.916369] PM: Device :00:1f.6 failed to suspend async: error -2
  [ 911.183052] PM: Some devices failed to suspend, or early wake event detected
  [ 911.197091] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
  [ 911.314903] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
  [ 911.382438] iwlwifi :00:14.3: FW already configured (0) - re-configuring
  [ 911.413624] OOM killer enabled.
  [ 911.413625] Restarting tasks ... done.
  [ 911.462021] PM: suspend exit

  It looks like Ethernet driver prevents suspend. Ethernet is not
  connected (I do not have the adaptor).

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

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

[Kernel-packages] [Bug 1775153] Re: fanotify09 test case 0 in LTP syscall test failed with T kernel

[Alex Hung]

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

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

Title:
  fanotify09 test case 0 in LTP syscall test failed with T kernel

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  Invalid

Bug description:
  The "fanotify09" from the LTP syscall tests has failed on a testing
  node with A/T kernel installed.

  Steps (with root):
    1. sudo apt-get install git xfsprogs -y
    2. git clone --depth=1 https://github.com/linux-test-project/ltp.git
    3. cd ltp
    4. make autotools
    5. ./configure
    6. make; make install
    7. cd /opt/ltp
    8. echo "fanotify09" > /tmp/jobs
    9. ./runltp -f /tmp/jobs

  <<>>
  tag=fanotify09 stime=1528192114
  cmdline="fanotify09"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
  fanotify09.c:134: PASS: group 0 get event: mask 2 pid=43803 fd=9
  fanotify09.c:182: FAIL: group 1 got event
  fanotify09.c:182: FAIL: group 2 got event

  Summary:
  passed   1
  failed   2
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=0
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-43-generic 4.13.0-43.48
  ProcVersionSignature: User Name 4.13.0-43.48-generic 4.13.16
  Uname: Linux 4.13.0-43-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun  5 08:30 seq
   crw-rw 1 root audio 116, 33 Jun  5 08:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.9
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Jun  5 09:14:07 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Cavium ThunderX CRB
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 EFI VGA
   1 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic 
root=UUID=ddcb8b36-6267-4392-a1f9-74d9203b742e ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-43-generic N/A
   linux-backports-modules-4.13.0-43-generic  N/A
   linux-firmware 1.169.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 0
  dmi.chassis.vendor: Cavium
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.:
  dmi.product.family: Default string
  dmi.product.name: ThunderX CRB
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cavium

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1775153/+subscriptions

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

[Kernel-packages] [Bug 1782758] Re: getrandom02 / inotify09 in ubuntu_ltp_syscalls timed out with B-GCP

[Alex Hung]

The problem has been fixed by commit (upstream): d90a10e2444b "fsnotify:
Fix fsnotify_mark_connector race"

This is also included in bionic kernel
(b75e7fe93538ef420bb1e5f68b8c3b3525a33e73) since Ubuntu-4.15.0-24.26. It
is cannot be reproduced anymore, either.

Note: getrandom02 is fixed in LP:1831229

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

Title:
  getrandom02 / inotify09 in ubuntu_ltp_syscalls timed out with B-GCP

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Fix Released

Bug description:
  Node: n1-highcpu-4

  tag=inotify09 stime=1532045405
  cmdline="inotify09"
  contacts=""
  analysis=exit
  <<>>
  tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
  Test timeouted, sending SIGKILL!
  tst_test.c:1055: INFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
  tst_test.c:1056: BROK: Test killed! (timeout?)

  tag=getrandom02 stime=1532045091
  cmdline="getrandom02"
  contacts=""
  analysis=exit
  <<>>
  tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
  getrandom02.c:72: PASS: getrandom returned 256
  getrandom02.c:72: PASS: getrandom returned 6
  getrandom02.c:72: PASS: getrandom returned 256
  Test timeouted, sending SIGKILL!
  tst_test.c:1055: INFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
  tst_test.c:1056: BROK: Test killed! (timeout?)

  Need some more investigation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1782758/+subscriptions

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

[Kernel-packages] [Bug 1775153] Re: fanotify09 test case 0 in LTP syscall test failed with T kernel

[Alex Hung]

The attached is a backported patch for fanotify09 for trusty kernel. The
test result was improved (as below) but it doesn't eliminate all
failures.

$ sudo ./fanotify09 
tst_test.c:1118: INFO: Timeout per run is 0h 05m 00s
fanotify09.c:161: INFO: Test #0: Events on children with both inode and mount 
marks
fanotify09.c:150: PASS: group 0 got event: mask 2 pid=7950 fd=6 
path=/tmp/4gc48T/mntpoint/tfile_7950
fanotify09.c:202: FAIL: first group got more than 1 events (48 > 24)
fanotify09.c:218: FAIL: group 1 got event
fanotify09.c:150: PASS: group 1 got event: mask 10 pid=7950 fd=6 
path=/tmp/4gc48T/mntpoint/testdir
fanotify09.c:218: FAIL: group 2 got event
fanotify09.c:150: PASS: group 2 got event: mask 10 pid=7950 fd=6 
path=/tmp/4gc48T/mntpoint/testdir
fanotify09.c:161: INFO: Test #1: Events on children and subdirs with both inode 
and mount marks
fanotify09.c:150: PASS: group 0 got event: mask 2 pid=7950 fd=6 
path=/tmp/4gc48T/mntpoint/tfile_7950
fanotify09.c:150: PASS: group 0 got event: mask 10 pid=7950 fd=7 
path=/tmp/4gc48T/mntpoint/testdir
fanotify09.c:218: FAIL: group 1 got event
fanotify09.c:150: PASS: group 1 got event: mask 10 pid=7950 fd=6 
path=/tmp/4gc48T/mntpoint/testdir
fanotify09.c:218: FAIL: group 2 got event
fanotify09.c:150: PASS: group 2 got event: mask 10 pid=7950 fd=6 
path=/tmp/4gc48T/mntpoint/testdir


** Patch added: "0001-fanotify-fix-logic-of-events-on-child.patch"
   
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1775153/+attachment/5289748/+files/0001-fanotify-fix-logic-of-events-on-child.patch

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

Title:
  fanotify09 test case 0 in LTP syscall test failed with T kernel

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  Invalid

Bug description:
  The "fanotify09" from the LTP syscall tests has failed on a testing
  node with A/T kernel installed.

  Steps (with root):
    1. sudo apt-get install git xfsprogs -y
    2. git clone --depth=1 https://github.com/linux-test-project/ltp.git
    3. cd ltp
    4. make autotools
    5. ./configure
    6. make; make install
    7. cd /opt/ltp
    8. echo "fanotify09" > /tmp/jobs
    9. ./runltp -f /tmp/jobs

  <<>>
  tag=fanotify09 stime=1528192114
  cmdline="fanotify09"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
  fanotify09.c:134: PASS: group 0 get event: mask 2 pid=43803 fd=9
  fanotify09.c:182: FAIL: group 1 got event
  fanotify09.c:182: FAIL: group 2 got event

  Summary:
  passed   1
  failed   2
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=0
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-43-generic 4.13.0-43.48
  ProcVersionSignature: User Name 4.13.0-43.48-generic 4.13.16
  Uname: Linux 4.13.0-43-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun  5 08:30 seq
   crw-rw 1 root audio 116, 33 Jun  5 08:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.9
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Jun  5 09:14:07 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Cavium ThunderX CRB
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 EFI VGA
   1 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic 
root=UUID=ddcb8b36-6267-4392-a1f9-74d9203b742e ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-43-generic N/A
   linux-backports-modules-4.13.0-43-generic  N/A
   linux-firmware 1.169.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 0
  dmi.chassis.vendor: Cavium
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E

[Kernel-packages] [Bug 1775378] Re: fanotify06 in LTP syscall test failed with T kernel

[Alex Hung]

This is fixed by a backported patch of 8edc6e1688f. Kernel and patch
file is available @ https://people.canonical.com/~alexhung/LP1775378/

The result is as below:

$ sudo ./fanotify06 
tst_device.c:87: INFO: Found free device 0 '/dev/loop0'
tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext2 opts='' extra opts=''
mke2fs 1.42.9 (4-Feb-2014)
tst_test.c:1118: INFO: Timeout per run is 0h 05m 00s
tst_fs_setup.c:43: INFO: fanotify06.c:239: overlayfs is not configured in this 
kernel
fanotify06.c:169: INFO: Test #0: Fanotify merge mount mark
fanotify06.c:147: PASS: group 0 got event: mask 2 pid=1626 fd=12
fanotify06.c:147: PASS: group 1 got event: mask 2 pid=1626 fd=12
fanotify06.c:147: PASS: group 2 got event: mask 2 pid=1626 fd=12
fanotify06.c:230: PASS: group 3 got no event
fanotify06.c:230: PASS: group 4 got no event
fanotify06.c:230: PASS: group 5 got no event
fanotify06.c:230: PASS: group 6 got no event
fanotify06.c:230: PASS: group 7 got no event
fanotify06.c:230: PASS: group 8 got no event
fanotify06.c:169: INFO: Test #1: Fanotify merge overlayfs mount mark
fanotify06.c:173: CONF: overlayfs is not configured in this kernel.

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

Title:
  fanotify06 in LTP syscall test failed with T kernel

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged

Bug description:
  The "fanotify06" from the LTP syscall tests has failed on a testing
  node with T kernel installed.

  Steps (with root):
1. sudo apt-get install git xfsprogs -y
2. git clone --depth=1 https://github.com/linux-test-project/ltp.git
3. cd ltp
4. make autotools
5. ./configure
6. make; make install
7. /opt/ltp/testcases/bin/fanotify06

  <<>>
  tag=fanotify06 stime=1528269991
  cmdline="fanotify06"
  contacts=""
  analysis=exit
  <<>>
  tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
  fanotify06.c:147: PASS: group 0 get event: mask 2 pid=22619 fd=29
  fanotify06.c:147: PASS: group 1 get event: mask 2 pid=22619 fd=29
  fanotify06.c:147: PASS: group 2 get event: mask 2 pid=22619 fd=29
  fanotify06.c:197: FAIL: group 3 got event
  fanotify06.c:197: FAIL: group 4 got event
  fanotify06.c:197: FAIL: group 5 got event
  fanotify06.c:208: PASS: group 6 got no event
  fanotify06.c:208: PASS: group 7 got no event
  fanotify06.c:197: FAIL: group 8 got event

  Summary:
  passed   5
  failed   4
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=0
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-149-generic 3.13.0-149.199
  ProcVersionSignature: User Name 3.13.0-149.199-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-149-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun  6 10:09 seq
   crw-rw 1 root audio 116, 33 Jun  6 10:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg: [3.472391] init: plymouth-upstart-bridge main process 
ended, respawning
  Date: Wed Jun  6 10:12:15 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Intel Corporation S1200RP
  PciMultimedia:
   
  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=/boot/vmlinuz-3.13.0-149-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-149-generic N/A
   linux-backports-modules-3.13.0-149-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
  dmi.board.asset.tag: 
  dmi.board.name: S1200RP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G62254-407
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17
  dmi.chassis.vendor: ..
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..:
  dmi.product.name: S1200RP
  dmi.product.version: 
  dmi.sys.vendor: Intel Corporation

To 

[Kernel-packages] [Bug 1775378] Re: fanotify06 in LTP syscall test failed with T kernel

[Alex Hung]

** Changed in: linux (Ubuntu Trusty)
   Status: Triaged => In Progress

** Changed in: linux (Ubuntu Trusty)
 Assignee: (unassigned) => Alex Hung (alexhung)

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Alex Hung (alexhung)

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

Title:
  fanotify06 in LTP syscall test failed with T kernel

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  In Progress

Bug description:
  The "fanotify06" from the LTP syscall tests has failed on a testing
  node with T kernel installed.

  Steps (with root):
1. sudo apt-get install git xfsprogs -y
2. git clone --depth=1 https://github.com/linux-test-project/ltp.git
3. cd ltp
4. make autotools
5. ./configure
6. make; make install
7. /opt/ltp/testcases/bin/fanotify06

  <<>>
  tag=fanotify06 stime=1528269991
  cmdline="fanotify06"
  contacts=""
  analysis=exit
  <<>>
  tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
  fanotify06.c:147: PASS: group 0 get event: mask 2 pid=22619 fd=29
  fanotify06.c:147: PASS: group 1 get event: mask 2 pid=22619 fd=29
  fanotify06.c:147: PASS: group 2 get event: mask 2 pid=22619 fd=29
  fanotify06.c:197: FAIL: group 3 got event
  fanotify06.c:197: FAIL: group 4 got event
  fanotify06.c:197: FAIL: group 5 got event
  fanotify06.c:208: PASS: group 6 got no event
  fanotify06.c:208: PASS: group 7 got no event
  fanotify06.c:197: FAIL: group 8 got event

  Summary:
  passed   5
  failed   4
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=0
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-149-generic 3.13.0-149.199
  ProcVersionSignature: User Name 3.13.0-149.199-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-149-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun  6 10:09 seq
   crw-rw 1 root audio 116, 33 Jun  6 10:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg: [3.472391] init: plymouth-upstart-bridge main process 
ended, respawning
  Date: Wed Jun  6 10:12:15 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Intel Corporation S1200RP
  PciMultimedia:
   
  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=/boot/vmlinuz-3.13.0-149-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-149-generic N/A
   linux-backports-modules-3.13.0-149-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
  dmi.board.asset.tag: 
  dmi.board.name: S1200RP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G62254-407
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17
  dmi.chassis.vendor: ..
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..:
  dmi.product.name: S1200RP
  dmi.product.version: 
  dmi.sys.vendor: Intel Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1775378/+subscriptions

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

[Kernel-packages] [Bug 1773299] Re: Dell systems crash when disabling Nvidia dGPU

[Alex Hung]

** Tags removed: verification-needed-bionic
** Tags added: verification-done-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/1773299

Title:
  Dell systems crash when disabling Nvidia dGPU

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Some Dell systems crash when disabling Nvidia dGPU with I+N
  configurations

  As NV Linux driver doesn't now support RTD3, BIOS removed the code to
  prevent system crashes as a short-term solution This is for Linux as
  Nvidia's Windows driver supports RTD3.

  In this workaround an _OSI string, Linux-Dell-Video, was used in BIOS
  as a workaround in Linux.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1773299/+subscriptions

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

[Kernel-packages] [Bug 1773295] Re: False positive ACPI _PRS error messages

[Alex Hung]

** Tags removed: verification-needed-bionic
** Tags added: verification-done-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/1773295

Title:
  False positive ACPI _PRS error messages

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  New platforms have hardware registers for routing table implemented as
  "write once". Once set by UEFI firmware during POST, OS will not be
  able to modify the routing table, and ACPI _PRS method are removed
  according to ACPI spec.

  As a result, generating the error messages "ACPI Exception:
  AE_NOT_FOUND, Evaluating _PRS" in kernel by default does not make
  sense, and they should be muted by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1773295/+subscriptions

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

[Kernel-packages] [Bug 1773295] Re: False positive ACPI _PRS error messages

[Alex Hung]

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

Title:
  False positive ACPI _PRS error messages

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

Bug description:
  New platforms have hardware registers for routing table implemented as
  "write once". Once set by UEFI firmware during POST, OS will not be
  able to modify the routing table, and ACPI _PRS method are removed
  according to ACPI spec.

  As a result, generating the error messages "ACPI Exception:
  AE_NOT_FOUND, Evaluating _PRS" in kernel by default does not make
  sense, and they should be muted by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1773295/+subscriptions

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

[Kernel-packages] [Bug 1787058] Re: ThinkPad systems have no HDMI sound when using the nvidia GPU

[Alex Hung]

** Tags removed: verification-needed-bionic
** Tags added: verification-done-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/1787058

Title:
  ThinkPad systems have no HDMI sound when using the nvidia GPU

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Some ThinkPad systems have a power-saving feature that turns off
  Nvidia HDMI audio device in Windows, but NVidia Linux driver does not
  support this feature. As a result, HDMI audio will not work on Linux.

  A BIOS workaround is added with an OEM_OSI string "Linux-Lenovo-NV-
  HDMI-Audio" which needs enabling in Linux kernel too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1787058/+subscriptions

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

[Kernel-packages] [Bug 1773295] [NEW] False positive ACPI _PRS error messages

[Alex Hung]

Public bug reported:

New platforms have hardware registers for routing table implemented as
"write once". Once set by UEFI firmware during POST, OS will not be able
to modify the routing table, and ACPI _PRS method are removed according
to ACPI spec.

As a result, generating the error messages "ACPI Exception:
AE_NOT_FOUND, Evaluating _PRS" in kernel by default does not make sense,
and they should be muted by default.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Alex Hung (alexhung)
 Status: New

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Alex Hung (alexhung)

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

Title:
  False positive ACPI _PRS error messages

Status in linux package in Ubuntu:
  New

Bug description:
  New platforms have hardware registers for routing table implemented as
  "write once". Once set by UEFI firmware during POST, OS will not be
  able to modify the routing table, and ACPI _PRS method are removed
  according to ACPI spec.

  As a result, generating the error messages "ACPI Exception:
  AE_NOT_FOUND, Evaluating _PRS" in kernel by default does not make
  sense, and they should be muted by default.

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

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

[Kernel-packages] [Bug 1773299] [NEW] Dell systems crash when disabling Nvidia dGPU

[Alex Hung]

Public bug reported:

Some Dell systems crash when disabling Nvidia dGPU with I+N
configurations

As NV Linux driver doesn't now support RTD3, BIOS removed the code to
prevent system crashes as a short-term solution This is for Linux as
Nvidia's Windows driver supports RTD3.

In this workaround an _OSI string, Linux-Dell-Video, was used in BIOS as
a workaround in Linux.

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

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Alex Hung (alexhung)
 Status: New


** Tags: originate-from-1741414 somerville

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Alex Hung (alexhung)

** Tags added: originate-from-1741414 somerville

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

Title:
  Dell systems crash when disabling Nvidia dGPU

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Some Dell systems crash when disabling Nvidia dGPU with I+N
  configurations

  As NV Linux driver doesn't now support RTD3, BIOS removed the code to
  prevent system crashes as a short-term solution This is for Linux as
  Nvidia's Windows driver supports RTD3.

  In this workaround an _OSI string, Linux-Dell-Video, was used in BIOS
  as a workaround in Linux.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1773299/+subscriptions

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

[Kernel-packages] [Bug 1773295] Re: False positive ACPI _PRS error messages

[Alex Hung]

** Tags added: originate-from-1741178 somerville

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

Title:
  False positive ACPI _PRS error messages

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  New platforms have hardware registers for routing table implemented as
  "write once". Once set by UEFI firmware during POST, OS will not be
  able to modify the routing table, and ACPI _PRS method are removed
  according to ACPI spec.

  As a result, generating the error messages "ACPI Exception:
  AE_NOT_FOUND, Evaluating _PRS" in kernel by default does not make
  sense, and they should be muted by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1773295/+subscriptions

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

[Kernel-packages] [Bug 1787058] [NEW] ThinkPad systems have no HDMI sound when using the nvidia GPU

[Alex Hung]

Public bug reported:

Some ThinkPad systems have a power-saving feature that turns off HDMI audio 
device in Windows, but NVidia Linux driver does not support this feature. As a 
result, HDMI audio will not work on Linux.

A BIOS workaround is added with an OEM_OSI string "Linux-Lenovo-NV-HDMI-Audio" 
which needs enabling in Linux kernel too.

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

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Alex Hung (alexhung)
 Status: In Progress


** Tags: originate-from-1756020 sutton

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Alex Hung (alexhung)

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

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

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

Title:
  ThinkPad systems have no HDMI sound when using the nvidia GPU

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Some ThinkPad systems have a power-saving feature that turns off HDMI audio 
device in Windows, but NVidia Linux driver does not support this feature. As a 
result, HDMI audio will not work on Linux.
  
  A BIOS workaround is added with an OEM_OSI string 
"Linux-Lenovo-NV-HDMI-Audio" which needs enabling in Linux kernel too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1787058/+subscriptions

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

[Kernel-packages] [Bug 1773299] Re: Dell systems crash when disabling Nvidia dGPU

[Alex Hung]

** Changed in: hwe-next
   Status: New => 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/1773299

Title:
  Dell systems crash when disabling Nvidia dGPU

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  Some Dell systems crash when disabling Nvidia dGPU with I+N
  configurations

  As NV Linux driver doesn't now support RTD3, BIOS removed the code to
  prevent system crashes as a short-term solution This is for Linux as
  Nvidia's Windows driver supports RTD3.

  In this workaround an _OSI string, Linux-Dell-Video, was used in BIOS
  as a workaround in Linux.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1773299/+subscriptions

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

[Kernel-packages] [Bug 1787058] Re: ThinkPad systems have no HDMI sound when using the nvidia GPU

[Alex Hung]

** Summary changed:

- Some ThinkPad systems no HDMI sound when using the nvidia GPU
+ ThinkPad systems have no HDMI sound when using the nvidia GPU

** Tags added: originate-from-1756020 sutton

** Description changed:

- Some ThinkPad systems have a power-saving feature that turns off HDMI audio 
device in Windows, but NVidia Linux driver does not support this feature. As a 
result, HDMI audio will not work on Linux.
- 
- A BIOS workaround is added with an OEM_OSI string 
"Linux-Lenovo-NV-HDMI-Audio" which needs enabling in Linux kernel too.
+ Some ThinkPad systems have a power-saving feature that turns off Nvidia
+ HDMI audio device in Windows, but NVidia Linux driver does not support
+ this feature. As a result, HDMI audio will not work on Linux.
+ 
+ A BIOS workaround is added with an OEM_OSI string "Linux-Lenovo-NV-HDMI-
+ Audio" which needs enabling in Linux kernel too.

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

Title:
  ThinkPad systems have no HDMI sound when using the nvidia GPU

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Some ThinkPad systems have a power-saving feature that turns off
  Nvidia HDMI audio device in Windows, but NVidia Linux driver does not
  support this feature. As a result, HDMI audio will not work on Linux.

  A BIOS workaround is added with an OEM_OSI string "Linux-Lenovo-NV-
  HDMI-Audio" which needs enabling in Linux kernel too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1787058/+subscriptions

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

[Kernel-packages] [Bug 1810702] Re: HP mobile workstations with hybrid graphics support, can not directly output to external monitors by dGPU

[Alex Hung]

** Changed in: linux (Ubuntu)
   Status: Fix Committed => 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/1810702

Title:
  HP mobile workstations with hybrid graphics support, can not directly
  output to external monitors by dGPU

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  For HP Inc. mobile workstation with hybrid graphics support, dGPU can 
directly output to external monitors; however, Nvidia and AMD's Linux drivers 
aren't able to support this feature.
  
  The OEM _OSI string "Linux-HPI-Hybrid-Graphics" is used by BIOS to implement 
dGPU direct output to external monitors.

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

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

[Kernel-packages] [Bug 1772624] Re: Broadcom BCM4356 wifi chipset firmware is not working

[Alex Hung]

I recalled trying the firmware in 16.04 (.5?) and it worked. You can
boot from USB and copy brcmfmac4356-pcie.bin.

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

Title:
  Broadcom BCM4356 wifi chipset firmware is not working

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  After upgrading to Ubuntu 18.04 I got an issue with the wifi chipset
  (Broadcom BCM4356) not initializing properly.

  Here is the error I got when loading the driver brcmfmac:

  ```
  [ 8189.092819] brcmfmac: brcmf_fw_map_chip_to_name: using 
brcm/brcmfmac4356-pcie.bin for chip 0x004356(17238) rev 0x02
  [ 8189.093100] brcmfmac :04:00.0: Direct firmware load for 
brcm/brcmfmac4356-pcie.txt failed with error -2
  [ 8191.568544] brcmfmac: brcmf_msgbuf_query_dcmd: Timeout on response for 
query command
  [ 8191.568562] brcmfmac: brcmf_c_preinit_dcmds: Retreiving cur_etheraddr 
failed, -5
  [ 8191.568570] brcmfmac: brcmf_bus_started: failed: -5
  [ 8191.568588] brcmfmac: brcmf_pcie_attach_bus: dongle is not responding
  ```

  As seen here https://answers.launchpad.net/ubuntu/+question/668329, I
  reverted to the previous linux-firmware version and then the wifi
  chipset is working:

  Previous firmware package: https://packages.ubuntu.com/artful-updates
  /linux-firmware

  ```
  [10087.698214] brcmfmac: brcmf_fw_map_chip_to_name: using 
brcm/brcmfmac4356-pcie.bin for chip 0x004356(17238) rev 0x02
  [10087.698634] brcmfmac :04:00.0: Direct firmware load for 
brcm/brcmfmac4356-pcie.txt failed with error -2
  [10088.104176] brcmfmac :04:00.0: Direct firmware load for 
brcm/brcmfmac4356-pcie.clm_blob failed with error -2
  [10088.104186] brcmfmac: brcmf_c_process_clm_blob: no clm_blob 
available(err=-2), device may have limited channels available
  [10088.105170] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Oct 
22 2015 06:16:41 version 7.35.180.119 (r594535) FWID 01-1a5c4016
  [10088.179872] brcmfmac :04:00.0 wlp4s0: renamed from wlan0
  ```

  The problem seems to have been reported to the linux-wireless mailing
  list but no fix has been committed apparently :
  https://www.spinics.net/lists/linux-wireless/msg168687.html

  System information:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  linux-image-4.15.0-20-generic:
Installé : 4.15.0-20.21
Candidat : 4.15.0-20.21
   Table de version :
   *** 4.15.0-20.21 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  linux-firmware:
Installé : 1.173
Candidat : 1.173
   Table de version :
   *** 1.173 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://fr.archive.ubuntu.com/ubuntu bionic/main i386 Packages
  100 /var/lib/dpkg/status

  
  Regards,
  Jean Pierre.

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

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

[Kernel-packages] [Bug 1810702] [NEW] 4HP mobile workstations, with hybrid graphics support, dGPU can not directly output to external monitors

[Alex Hung]

Public bug reported:

For HP Inc. mobile workstation with hybrid graphics support, dGPU can directly 
output to external monitors; however, Nvidia and AMD's Linux drivers aren't 
able to support this feature.

The OEM _OSI string "Linux-HPI-Hybrid-Graphics" is used by BIOS to implement 
dGPU direct output to external monitors.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Alex Hung (alexhung)
 Status: Incomplete

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Alex Hung (alexhung)

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

Title:
  4HP mobile workstations, with hybrid graphics support, dGPU can not
  directly output to external monitors

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  For HP Inc. mobile workstation with hybrid graphics support, dGPU can 
directly output to external monitors; however, Nvidia and AMD's Linux drivers 
aren't able to support this feature.
  
  The OEM _OSI string "Linux-HPI-Hybrid-Graphics" is used by BIOS to implement 
dGPU direct output to external monitors.

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

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

[Kernel-packages] [Bug 1810702] Re: HP mobile workstations, with hybrid graphics support, dGPU can not directly output to external monitors

[Alex Hung]

** Summary changed:

- 4HP mobile workstations, with hybrid graphics support, dGPU can not directly 
output to external monitors
+ HP mobile workstations, with hybrid graphics support, dGPU can not directly 
output to external monitors

** Summary changed:

- HP mobile workstations, with hybrid graphics support, dGPU can not directly 
output to external monitors
+ For HP mobile workstations with hybrid graphics support, dGPU can not 
directly output to external monitors

** Summary changed:

- For HP mobile workstations with hybrid graphics support, dGPU can not 
directly output to external monitors
+ HP mobile workstations with hybrid graphics support, can not directly output 
to external monitors by dGPU

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

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

Title:
  HP mobile workstations with hybrid graphics support, can not directly
  output to external monitors by dGPU

Status in linux package in Ubuntu:
  In Progress

Bug description:
  For HP Inc. mobile workstation with hybrid graphics support, dGPU can 
directly output to external monitors; however, Nvidia and AMD's Linux drivers 
aren't able to support this feature.
  
  The OEM _OSI string "Linux-HPI-Hybrid-Graphics" is used by BIOS to implement 
dGPU direct output to external monitors.

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

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

Re: [Kernel-packages] [Bug 1810702] Re: HP mobile workstations with hybrid graphics support, can not directly output to external monitors by dGPU

[Alex Hung]

On Tue, Jan 8, 2019 at 4:20 AM Stefan Bader  wrote:
>
> And what about cosmic, too.

Thanks for the reminder. This should also apply to cosmic too.

>
> ** Also affects: linux (Ubuntu Bionic)
>Importance: Undecided
>Status: New
>
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
>Status: Fix Committed => New
>
> ** Changed in: linux (Ubuntu Bionic)
>Status: New => Fix Committed
>
> ** Changed in: linux (Ubuntu Bionic)
>Importance: Undecided => Medium
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1810702
>
> Title:
>   HP mobile workstations with hybrid graphics support, can not directly
>   output to external monitors by dGPU
>
> Status in linux package in Ubuntu:
>   New
> Status in linux source package in Bionic:
>   Fix Committed
>
> Bug description:
>   For HP Inc. mobile workstation with hybrid graphics support, dGPU can 
> directly output to external monitors; however, Nvidia and AMD's Linux drivers 
> aren't able to support this feature.
>
>   The OEM _OSI string "Linux-HPI-Hybrid-Graphics" is used by BIOS to 
> implement dGPU direct output to external monitors.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810702/+subscriptions


-- 
Cheers,
Alex Hung

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

Title:
  HP mobile workstations with hybrid graphics support, can not directly
  output to external monitors by dGPU

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  For HP Inc. mobile workstation with hybrid graphics support, dGPU can 
directly output to external monitors; however, Nvidia and AMD's Linux drivers 
aren't able to support this feature.
  
  The OEM _OSI string "Linux-HPI-Hybrid-Graphics" is used by BIOS to implement 
dGPU direct output to external monitors.

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

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

[Kernel-packages] [Bug 1810702] Re: HP mobile workstations with hybrid graphics support, can not directly output to external monitors by dGPU

[Alex Hung]

** Tags removed: verification-needed-bionic
** Tags added: verification-done-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/1810702

Title:
  HP mobile workstations with hybrid graphics support, can not directly
  output to external monitors by dGPU

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  For HP Inc. mobile workstation with hybrid graphics support, dGPU can 
directly output to external monitors; however, Nvidia and AMD's Linux drivers 
aren't able to support this feature.
  
  The OEM _OSI string "Linux-HPI-Hybrid-Graphics" is used by BIOS to implement 
dGPU direct output to external monitors.

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

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

[Kernel-packages] [Bug 1907160] [NEW] intel-hid is not loaded on new Intel platform

[Alex Hung]

Public bug reported:

[Impact]

 intel-hid, used to handle BIOS events, is not loaded on new intel
rocket lake platforms because the existing hardware ids "INT33D5" and
"INTC1051" aren't used in BIOS.

[Fix]

 A new id "INTC1054" is added to intel-hid kernel driver.

[Test Case]

 This was tested on a rocket lake platform and intel-hid was loaded
correctly as kernel log below:

 [ 2.938964] input: Intel HID 5 button array as
/devices/platform/INT1054:00/input/input11

[Where problems could occur]

 None.

 An new ID was added for new platforms. Previous platforms will not be
affected.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Alex Hung (alexhung)
 Status: New

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Alex Hung (alexhung)

** Description changed:

  [Impact]
  
-  intel-hid is not loaded on new intel rocket lake platforms because the 
existing
-  hardware ids "INT33D5" and "INTC1051" aren't used in BIOS.
+  intel-hid is not loaded on new intel rocket lake platforms because the
+ existing hardware ids "INT33D5" and "INTC1051" aren't used in BIOS.
  
  [Fix]
  
-  A new id "INTC1054" is added to intel-hid kernel driver.
+  A new id "INTC1054" is added to intel-hid kernel driver.
  
  [Test Case]
  
-  This was tested on a rocket lake platform and intel-hid was loaded correctly 
as kernel log below:
-  
-  [ 2.938964] input: Intel HID 5 button array as 
/devices/platform/INT1054:00/input/input11
+  This was tested on a rocket lake platform and intel-hid was loaded
+ correctly as kernel log below:
+ 
+  [ 2.938964] input: Intel HID 5 button array as
+ /devices/platform/INT1054:00/input/input11
  
  [Where problems could occur]
  
-  None.
+  None.
  
-  An new ID was added for new platforms. Previous platforms will not be
+  An new ID was added for new platforms. Previous platforms will not be
  affected.

** Description changed:

  [Impact]
  
-  intel-hid is not loaded on new intel rocket lake platforms because the
- existing hardware ids "INT33D5" and "INTC1051" aren't used in BIOS.
+  intel-hid, used to handle BIOS events, is not loaded on new intel
+ rocket lake platforms because the existing hardware ids "INT33D5" and
+ "INTC1051" aren't used in BIOS.
  
  [Fix]
  
   A new id "INTC1054" is added to intel-hid kernel driver.
  
  [Test Case]
  
   This was tested on a rocket lake platform and intel-hid was loaded
  correctly as kernel log below:
  
   [ 2.938964] input: Intel HID 5 button array as
  /devices/platform/INT1054:00/input/input11
  
  [Where problems could occur]
  
   None.
  
   An new ID was added for new platforms. Previous platforms will not be
  affected.

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

Title:
  intel-hid is not loaded on new Intel platform

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]

   intel-hid, used to handle BIOS events, is not loaded on new intel
  rocket lake platforms because the existing hardware ids "INT33D5" and
  "INTC1051" aren't used in BIOS.

  [Fix]

   A new id "INTC1054" is added to intel-hid kernel driver.

  [Test Case]

   This was tested on a rocket lake platform and intel-hid was loaded
  correctly as kernel log below:

   [ 2.938964] input: Intel HID 5 button array as
  /devices/platform/INT1054:00/input/input11

  [Where problems could occur]

   None.

   An new ID was added for new platforms. Previous platforms will not be
  affected.

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

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

[Kernel-packages] [Bug 1907160] Re: intel-hid is not loaded on new Intel platform

[Alex Hung]

Yes this is also sent to upstream for review and hopefully it will be in
5.11

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

Title:
  intel-hid is not loaded on new Intel platform

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.10 package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Fix Committed

Bug description:
  [Impact]

   intel-hid, used to handle BIOS events, is not loaded on new intel
  rocket lake platforms because the existing hardware ids "INT33D5" and
  "INTC1051" aren't used in BIOS.

  [Fix]

   A new id "INTC1054" is added to intel-hid kernel driver.

  [Test Case]

   This was tested on a rocket lake platform and intel-hid was loaded
  correctly as kernel log below:

   [ 2.938964] input: Intel HID 5 button array as
  /devices/platform/INT1054:00/input/input11

  [Where problems could occur]

   None.

   An new ID was added for new platforms. Previous platforms will not be
  affected.

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

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

[Kernel-packages] [Bug 1892547] Re: [ 0.172384] ACPI Exception: Could not find/resolve named package element: OC06 (20170831/dspkginit-381) [ 0.172444] ACPI Exception: Could not find/resolve named pac

[Alex Hung]

This should be an ACPI BIOS bug, and there is not much to be done in
Linux.

An acpidump log (sudo acpidump > acpi.log) is required for more analysis
of what functions are impacted.

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

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

Title:
  [0.172384] ACPI Exception: Could not find/resolve named package
  element: OC06 (20170831/dspkginit-381) [0.172444] ACPI Exception:
  Could not find/resolve named package element: OC07
  (20170831/dspkginit-381)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [0.172384] ACPI Exception: Could not find/resolve named package
  element: OC06 (20170831/dspkginit-381)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-112-generic 4.15.0-112.113
  ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xilion 1667 F pulseaudio
  CurrentDesktop: LXDE
  Date: Fri Aug 21 22:15:54 2020
  HibernationDevice: RESUME=UUID=3a74be02-d33e-4932-8d91-4d1fa8672def
  InstallationDate: Installed on 2018-06-18 (795 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  IwConfig:
   lono wireless extensions.
   
   enp0s29f7u2  no wireless extensions.
   
   enp1s3no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic 
root=UUID=4ed73824-614c-4c5a-a4ca-782b0ed7ace2 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-112-generic N/A
   linux-backports-modules-4.15.0-112-generic  N/A
   linux-firmware  1.173.19
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/09/2006
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0301
  dmi.board.name: P5GPL-X SE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0301:bd06/09/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5GPL-XSE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1892012] Re: Bluetooth doesn't turn on

[Alex Hung]

This sounds like Bluetooth hardware malfunctions until a full reset (or
completely powered off).

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

Title:
  Bluetooth doesn't turn on

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  UPDATE
  ==

  I tried another kernel (`5.4.0-40-generic` and it didn't worked.
  Trying to reboot (and get back to the latest kernel) it didn't shutdown, so I 
hard shutdown it, and restart with the `5.4.0-42-generic`.

  And now, it works.
  I hope the logs below may help you to find out what happened, and help others 
to fix their issue if it's similar to this one.

  ---

  
  Hello,

  For now, everything worked fine, until this morning when Bluetooth
  stop working.

  Ubuntu 20.04

  **What expected to happen :** Bluetooth turn on on start, and if it's
  off it turns on when I turn it on.

  **What happens :** it doesn't turn on.

  ```
   $ dmesg | grep -i blue
  [2.433133] Bluetooth: Core ver 2.22
  [2.433147] Bluetooth: HCI device and connection manager initialized
  [2.433149] Bluetooth: HCI socket layer initialized
  [2.433151] Bluetooth: L2CAP socket layer initialized
  [2.433153] Bluetooth: SCO socket layer initialized
  [3.559082] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [3.559083] Bluetooth: BNEP filters: protocol multicast
  [3.559088] Bluetooth: BNEP socket layer initialized
  [4.456149] Bluetooth: hci0: command 0xfc05 tx timeout
  [4.456167] Bluetooth: hci0: Reading Intel version information failed 
(-110)
  ```

  Last `/var/log/dpkg.log` logs (previous were from 3 days ago)
  ```
  2020-08-18 01:06:02 startup archives unpack
  2020-08-18 01:06:03 install python3-blessings:all  1.6-3
  2020-08-18 01:06:03 status half-installed python3-blessings:all 1.6-3
  2020-08-18 01:06:03 status unpacked python3-blessings:all 1.6-3
  2020-08-18 01:06:03 install python3-pynvml:amd64  7.352.0-3
  2020-08-18 01:06:03 status half-installed python3-pynvml:amd64 7.352.0-3
  2020-08-18 01:06:03 status unpacked python3-pynvml:amd64 7.352.0-3
  2020-08-18 01:06:03 install gpustat:all  0.6.0-1
  2020-08-18 01:06:03 status half-installed gpustat:all 0.6.0-1
  2020-08-18 01:06:03 status unpacked gpustat:all 0.6.0-1
  2020-08-18 01:06:03 startup packages configure
  2020-08-18 01:06:03 configure python3-blessings:all 1.6-3 
  2020-08-18 01:06:03 status unpacked python3-blessings:all 1.6-3
  2020-08-18 01:06:03 status half-configured python3-blessings:all 1.6-3
  2020-08-18 01:06:03 status installed python3-blessings:all 1.6-3
  2020-08-18 01:06:03 configure python3-pynvml:amd64 7.352.0-3 
  2020-08-18 01:06:03 status unpacked python3-pynvml:amd64 7.352.0-3
  2020-08-18 01:06:03 status half-configured python3-pynvml:amd64 7.352.0-3
  2020-08-18 01:06:04 status installed python3-pynvml:amd64 7.352.0-3
  2020-08-18 01:06:04 configure gpustat:all 0.6.0-1 
  2020-08-18 01:06:04 status unpacked gpustat:all 0.6.0-1
  2020-08-18 01:06:04 status half-configured gpustat:all 0.6.0-1
  2020-08-18 01:06:04 status installed gpustat:all 0.6.0-1

  ```

  ```
   $ dpkg -l | grep -i blue
  ii  bluez 5.53-0ubuntu3   
  amd64Bluetooth tools and daemons
  ii  bluez-cups5.53-0ubuntu3   
  amd64Bluetooth printer driver for CUPS
  ii  bluez-obexd   5.53-0ubuntu3   
  amd64bluez obex daemon
  ii  gir1.2-gnomebluetooth-1.0:amd64   3.34.1-1
  amd64Introspection data for GnomeBluetooth
  ii  gnome-bluetooth   3.34.1-1
  amd64GNOME Bluetooth tools
  ii  libbluetooth3:amd64   5.53-0ubuntu3   
  amd64Library to use the BlueZ Linux Bluetooth stack
  ii  libgnome-bluetooth13:amd643.34.1-1
  amd64GNOME Bluetooth tools - support library
  ii  libkf5bluezqt-data5.68.0-0ubuntu1 
  all  data files for bluez-qt
  ii  libkf5bluezqt6:amd64  5.68.0-0ubuntu1 
  amd64Qt wrapper for bluez
  ii  node-bluebird 3.5.1+dfsg2-2build1 
  all  Fully featured Promises/A+ implementation for Node.js
  ii  pulseaudio-module-bluetooth   1:13.99.1-1ubuntu3.5
  amd64Bluetooth module for PulseAudio sound server
  ii  qml-module-org-kde-bluezqt:amd64  5.68.0-0ubuntu1 
  amd64QML wrapper for bluez
  ```

  ```
   $ sudo service bluetooth status
  [sudo] password for brieucdug:
  ● bluetooth.service - Bluetooth service
   

[Kernel-packages] [Bug 1886588] Re: ath10k_pci often crashes in focal

[Alex Hung]

vicamo posted a probable solution @
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891405. See #19
for more details

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

Title:
  ath10k_pci often crashes in focal

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  WIreless connectivity has been very flaky in focal ever since release.
  Thought I'd start investigating a bit. This is all I found, but it
  clearly signisfies an error. Please let med know, if I can provide
  more information.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: firmware crashed! (guid 
ba24fee9-d0cb-42e2-9aef-06f0d07a053e)
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: qca6174 hw3.2 target 
0x0503 chip_id 0x00340aff sub 1a56:1535
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: kconfig debug 0 debugfs 
1 tracing 1 dfs 0 testmode 0
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: firmware ver 
WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 
29eb8ca1
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: board_file api 2 bmi_id 
N/A crc32 4ac0889b
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: htt-ver 3.60 wmi-op 4 
htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: failed to get memcpy hi 
address for firmware address 4: -16
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: failed to read firmware 
dump area: -16
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: Copy Engine register 
dump:
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: [00]: 0x00034400  11  11 
  3   3
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: [01]: 0x00034800   3   2 
175 176
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: [02]: 0x00034c00  12  11 
 10  11
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: [03]: 0x00035000  12  12 
 14  12
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: [04]: 0x00035400 6557 
6549  11 203
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: [05]: 0x00035800   0   0 
 64   0
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: [06]: 0x00035c00   3   1 
 10   8
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: [07]: 0x00036000   1   0 
  1   0
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: failed to read 
hi_board_data address: -28
  [ma. juli  6 23:16:51 2020] ieee80211 phy0: Hardware restart was requested
  [ma. juli  6 23:16:51 2020] ath10k_pci :3b:00.0: unsupported HTC service 
id: 1536
  [ma. juli  6 23:16:51 2020] ath10k_pci :3b:00.0: device successfully 
recovered
  [ma. juli  6 23:19:57 2020] mce: CPU2: Core temperature above threshold, cpu 
clock throttled (total events = 6714)
  [ma. juli  6 23:19:57 2020] mce: CPU1: Package temperature above threshold, 
cpu clock throttled (total events = 20892)
  [ma. juli  6 23:19:57 2020] mce: CPU5: Package temperature above threshold, 
cpu clock throttled (total events = 20892)
  [ma. juli  6 23:19:57 2020] mce: CPU4: Package temperature above threshold, 
cpu clock throttled (total events = 20892)
  [ma. juli  6 23:19:57 2020] mce: CPU2: Package temperature above threshold, 
cpu clock throttled (total events = 20893)
  [ma. juli  6 23:19:57 2020] mce: CPU0: Package temperature above threshold, 
cpu clock throttled (total events = 20893)
  [ma. juli  6 23:19:57 2020] mce: CPU3: Package temperature above threshold, 
cpu clock throttled (total events = 20893)
  [ma. juli  6 23:19:57 2020] mce: CPU2: Core temperature/speed normal
  [ma. juli  6 23:19:57 2020] mce: CPU1: Package temperature/speed normal
  [ma. juli  6 23:19:57 2020] mce: CPU5: Package temperature/speed normal
  [ma. juli  6 23:19:57 2020] mce: CPU4: Package temperature/speed normal
  [ma. juli  6 23:19:57 2020] mce: CPU2: Package temperature/speed normal
  [ma. juli  6 23:19:57 2020] mce: CPU0: Package temperature/speed normal
  [ma. juli  6 23:19:57 2020] mce: CPU3: Package temperature/speed normal
  [ma. juli  6 23:20:08 2020] docker0: port 1(veth76af7ee) entered disabled 
state
  [ma. juli  6 23:20:08 2020] veth76e34af: renamed from eth0
  [ma. juli  6 23:20:08 2020] docker0: port 1(veth76af7ee) entered disabled 
state
  [ma. juli  6 23:20:08 2020] device veth76af7ee left promiscuous mode
  [ma. juli  6 23:20:08 2020] docker0: port 1(veth76af7ee) entered disabled 
state
  [ma. juli  6 23:20:18 2020] wlp59s0: deauthenticating from 00:22:07:80:6c:2e 
by local choice (Reason: 3=DEAUTH_LEAVING)
  [ma. juli  6 23:21:46 2020] ath10k_pci :3b:00.0: pci irq msi 
oper_irq_mode 2 irq_mode 0 reset_mode 0
  [ma. juli  6 23:21:46 2020] ath10k_pci :3b:00.0: qca6174 hw3.2 target 
0x0503 chip_id 0x00340aff sub 1a56:1535
  [ma. juli  6 23:21:46 2020] ath10k_pci :3b:00.0: kconfig debug 0 debugfs 
1 tracing 1 dfs 0 testmode 0
  [ma. juli  6 23:21:

[Kernel-packages] [Bug 1872351] Re: Qualcomm Atheros QCA6174 [168c:003e] Subsystem: Killer 1435 Wireless-AC [1a56:143a]: Disabling wifi causes kernel warning in __sta_info_destroy_part2

[Alex Hung]

Perhaps vicamo's comments #19 on LP:1891405 will help

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

Title:
  Qualcomm Atheros QCA6174 [168c:003e] Subsystem: Killer 1435 Wireless-
  AC [1a56:143a]: Disabling wifi causes kernel warning in
  __sta_info_destroy_part2

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have multiple issues with wifi on my Dell XPS 9380.
  This error was triggered when I tried to disable my wifi.

  [ 3634.322471] [ cut here ]
  [ 3634.322524] WARNING: CPU: 3 PID: 1188 at net/mac80211/sta_info.c:1057 
__sta_info_destroy_part2+0x14e/0x160 [mac80211]
  [ 3634.322525] Modules linked in: rfcomm vboxnetadp(OE) vboxnetflt(OE) 
vboxdrv(OE) ccm typec_displayport cmac algif_hash algif_skcipher af_alg bnep 
binfmt_misc nls_iso8859_1 mei_hdcp intel_rapl_msr snd_hda_codec_hdmi 
dell_laptop snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio 
snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core snd_usb_audio 
ath10k_pci x86_pkg_temp_thermal snd_usbmidi_lib snd_seq_midi snd_hwdep 
snd_seq_midi_event ath10k_core intel_powerclamp coretemp cdc_ether snd_rawmidi 
usbnet btusb kvm_intel r8152 ath btrtl mii btbcm kvm snd_seq uvcvideo 
videobuf2_vmalloc btintel videobuf2_memops intel_cstate videobuf2_v4l2 joydev 
snd_seq_device snd_pcm dell_wmi intel_rapl_perf videobuf2_common bluetooth 
mac80211 dell_smbios videodev snd_timer dcdbas mc input_leds ecdh_generic ecc 
wmi_bmof snd dell_wmi_descriptor serio_raw intel_wmi_thunderbolt cfg80211 
soundcore rtsx_pci_ms libarc4 memstick hid_multitouch processor_thermal_device 
ucsi_acpi typec_ucsi mei_me intel_rapl_common
  [ 3634.322564]  intel_xhci_usb_role_switch mei typec intel_soc_dts_iosf 
intel_pch_thermal roles int3403_thermal int340x_thermal_zone int3400_thermal 
mac_hid acpi_pad intel_hid acpi_thermal_rel sparse_keymap sch_fq_codel 
parport_pc ppdev lp parport ip_tables x_tables autofs4 mmc_block dm_crypt 
usbhid hid_generic crct10dif_pclmul crc32_pclmul rtsx_pci_sdmmc i915 
ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_algo_bit glue_helper 
drm_kms_helper psmouse syscopyarea sysfillrect nvme sysimgblt i2c_i801 
fb_sys_fops nvme_core drm intel_lpss_pci rtsx_pci intel_lpss idma64 i2c_hid 
virt_dma wmi hid pinctrl_sunrisepoint video pinctrl_intel
  [ 3634.322599] CPU: 3 PID: 1188 Comm: NetworkManager Tainted: G   OE  
   5.4.0-21-generic #25-Ubuntu
  [ 3634.322600] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.12.1 
12/11/2019
  [ 3634.322633] RIP: 0010:__sta_info_destroy_part2+0x14e/0x160 [mac80211]
  [ 3634.322635] Code: 24 0c 01 00 00 00 0f 84 52 ff ff ff 45 31 c0 b9 01 00 00 
00 4c 89 e2 48 89 de 4c 89 ef e8 0a a6 ff ff 85 c0 0f 84 34 ff ff ff <0f> 0b e9 
2d ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00
  [ 3634.322636] RSP: 0018:a70c009c3918 EFLAGS: 00010282
  [ 3634.322638] RAX: ff94 RBX: 9006104cc8c0 RCX: 

  [ 3634.322640] RDX: 90061ba3c740 RSI:  RDI: 
900613a62f48
  [ 3634.322641] RBP: a70c009c3938 R08: 90061e4d78c8 R09: 
0004
  [ 3634.322642] R10:  R11:  R12: 
900613f28000
  [ 3634.322643] R13: 900613a607a0 R14: 9006104cc8c0 R15: 
900613a60d68
  [ 3634.322644] FS:  7f596b396240() GS:90061e4c() 
knlGS:
  [ 3634.322645] CS:  0010 DS:  ES:  CR0: 80050033
  [ 3634.322646] CR2: 0db00945f000 CR3: 000494824005 CR4: 
003606e0
  [ 3634.322647] Call Trace:
  [ 3634.322670]  __sta_info_flush+0x128/0x180 [mac80211]
  [ 3634.322696]  ieee80211_set_disassoc+0xc0/0x5f0 [mac80211]
  [ 3634.322719]  ieee80211_mgd_deauth+0x104/0x490 [mac80211]
  [ 3634.322743]  ieee80211_deauth+0x18/0x20 [mac80211]
  [ 3634.322782]  cfg80211_mlme_deauth+0xb6/0x1e0 [cfg80211]
  [ 3634.322804]  cfg80211_mlme_down+0x66/0x80 [cfg80211]
  [ 3634.322823]  cfg80211_disconnect+0x127/0x1e0 [cfg80211]
  [ 3634.322827]  ? _raw_spin_unlock_bh+0x1e/0x20
  [ 3634.322845]  __cfg80211_leave+0x133/0x1b0 [cfg80211]
  [ 3634.322862]  cfg80211_leave+0x2c/0x40 [cfg80211]
  [ 3634.322879]  cfg80211_netdev_notifier_call+0x1b2/0x590 [cfg80211]
  [ 3634.322902]  ? ath10k_warn.cold+0x1a/0x1f [ath10k_core]
  [ 3634.322911]  ? ath10k_config_ps+0x52/0x70 [ath10k_core]
  [ 3634.322913]  ? rtnl_is_locked+0x15/0x20
  [ 3634.322917]  ? inetdev_event+0x47/0x560
  [ 3634.322919]  ? skb_dequeue+0x5a/0x70
  [ 3634.322923]  notifier_call_chain+0x55/0x80
  [ 3634.322925]  raw_notifier_call_chain+0x16/0x20
  [ 3634.322927]  call_netdevice_notifiers_info+0x2e/0x60
  [ 3634.322929]  __dev_close_many+0x63/0x120
  [ 3634.322931]  dev_close_many+0x91/0x150
  [ 3634.322933]  dev_close.part.0+0x4a/0x70
  [ 3634.322936]  dev_close+0x18/0x20
  [ 3634.322955]  cfg80211_shutdown_all_interfaces+0x77

[Kernel-packages] [Bug 1892012] Re: Bluetooth doesn't turn on

[Alex Hung]

You can also try the unload & reload Bluetooth driver by "sudo modprobe
-r btusb ; sudo modprobe btusb". It may save you some time.

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

Title:
  Bluetooth doesn't turn on

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  UPDATE
  ==

  I tried another kernel (`5.4.0-40-generic` and it didn't worked.
  Trying to reboot (and get back to the latest kernel) it didn't shutdown, so I 
hard shutdown it, and restart with the `5.4.0-42-generic`.

  And now, it works.
  I hope the logs below may help you to find out what happened, and help others 
to fix their issue if it's similar to this one.

  ---

  
  Hello,

  For now, everything worked fine, until this morning when Bluetooth
  stop working.

  Ubuntu 20.04

  **What expected to happen :** Bluetooth turn on on start, and if it's
  off it turns on when I turn it on.

  **What happens :** it doesn't turn on.

  ```
   $ dmesg | grep -i blue
  [2.433133] Bluetooth: Core ver 2.22
  [2.433147] Bluetooth: HCI device and connection manager initialized
  [2.433149] Bluetooth: HCI socket layer initialized
  [2.433151] Bluetooth: L2CAP socket layer initialized
  [2.433153] Bluetooth: SCO socket layer initialized
  [3.559082] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [3.559083] Bluetooth: BNEP filters: protocol multicast
  [3.559088] Bluetooth: BNEP socket layer initialized
  [4.456149] Bluetooth: hci0: command 0xfc05 tx timeout
  [4.456167] Bluetooth: hci0: Reading Intel version information failed 
(-110)
  ```

  Last `/var/log/dpkg.log` logs (previous were from 3 days ago)
  ```
  2020-08-18 01:06:02 startup archives unpack
  2020-08-18 01:06:03 install python3-blessings:all  1.6-3
  2020-08-18 01:06:03 status half-installed python3-blessings:all 1.6-3
  2020-08-18 01:06:03 status unpacked python3-blessings:all 1.6-3
  2020-08-18 01:06:03 install python3-pynvml:amd64  7.352.0-3
  2020-08-18 01:06:03 status half-installed python3-pynvml:amd64 7.352.0-3
  2020-08-18 01:06:03 status unpacked python3-pynvml:amd64 7.352.0-3
  2020-08-18 01:06:03 install gpustat:all  0.6.0-1
  2020-08-18 01:06:03 status half-installed gpustat:all 0.6.0-1
  2020-08-18 01:06:03 status unpacked gpustat:all 0.6.0-1
  2020-08-18 01:06:03 startup packages configure
  2020-08-18 01:06:03 configure python3-blessings:all 1.6-3 
  2020-08-18 01:06:03 status unpacked python3-blessings:all 1.6-3
  2020-08-18 01:06:03 status half-configured python3-blessings:all 1.6-3
  2020-08-18 01:06:03 status installed python3-blessings:all 1.6-3
  2020-08-18 01:06:03 configure python3-pynvml:amd64 7.352.0-3 
  2020-08-18 01:06:03 status unpacked python3-pynvml:amd64 7.352.0-3
  2020-08-18 01:06:03 status half-configured python3-pynvml:amd64 7.352.0-3
  2020-08-18 01:06:04 status installed python3-pynvml:amd64 7.352.0-3
  2020-08-18 01:06:04 configure gpustat:all 0.6.0-1 
  2020-08-18 01:06:04 status unpacked gpustat:all 0.6.0-1
  2020-08-18 01:06:04 status half-configured gpustat:all 0.6.0-1
  2020-08-18 01:06:04 status installed gpustat:all 0.6.0-1

  ```

  ```
   $ dpkg -l | grep -i blue
  ii  bluez 5.53-0ubuntu3   
  amd64Bluetooth tools and daemons
  ii  bluez-cups5.53-0ubuntu3   
  amd64Bluetooth printer driver for CUPS
  ii  bluez-obexd   5.53-0ubuntu3   
  amd64bluez obex daemon
  ii  gir1.2-gnomebluetooth-1.0:amd64   3.34.1-1
  amd64Introspection data for GnomeBluetooth
  ii  gnome-bluetooth   3.34.1-1
  amd64GNOME Bluetooth tools
  ii  libbluetooth3:amd64   5.53-0ubuntu3   
  amd64Library to use the BlueZ Linux Bluetooth stack
  ii  libgnome-bluetooth13:amd643.34.1-1
  amd64GNOME Bluetooth tools - support library
  ii  libkf5bluezqt-data5.68.0-0ubuntu1 
  all  data files for bluez-qt
  ii  libkf5bluezqt6:amd64  5.68.0-0ubuntu1 
  amd64Qt wrapper for bluez
  ii  node-bluebird 3.5.1+dfsg2-2build1 
  all  Fully featured Promises/A+ implementation for Node.js
  ii  pulseaudio-module-bluetooth   1:13.99.1-1ubuntu3.5
  amd64Bluetooth module for PulseAudio sound server
  ii  qml-module-org-kde-bluezqt:amd64  5.68.0-0ubuntu1 
  amd64QML wrapper for bluez
  ```

  ```
   $ sudo service bluetooth status
  [sudo] password for brieucdug:
  ● blueto

[Kernel-packages] [Bug 1891032] Re: Brightness key freeze screen

[Alex Hung]

You can use the GUI app "keyboard shortcuts" to setup custom keys, or
you can manually modify hwdb files (ex.
/lib/udev/hwdb.d/60-keyboard.hwdb).

The following tutorials may provide some help.

== Modify keymap ==
 * cd /lib/udev/hwdb.d/
 * edit keymap file (60-keyboard.hwdb)
 * add a change, ex KEYBOARD_KEY_81=f20 # mic mute
 * run "sudo udevadm hwdb --update"
 * load changes "sudo udevadm trigger" (not tested) or reboot
 * not reboot required:
  * udevadm hwdb -u
  * udevadm control --reload
  * udevadm trigger --action=add --subsystem-match=input
 * check updated keymap
  * udevadm info /dev/input/event

more information
 * http://askubuntu.com/questions/499252/my-custom-udev-hwdb-rule-doesnt-work
 * http://thinkpad-scripts.readthedocs.org/en/latest/guides/additional-keys.html

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

Title:
  Brightness key freeze screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When I press the KEY_BRIGHTNESSDOWN or KEY_BRIGHTNESSUP the screen
  freeze for a few seconds.

  Sometimes it up/down brightness to max/min with just one press and the
  overlay get stuck in the screen.

  Maybe useful information:
  # evtest
  Event: time 1597066500.752632, -- SYN_REPORT 
  Event: time 1597066502.755372, type 4 (EV_MSC), code 4 (MSC_SCAN), value 86
  Event: time 1597066502.755372, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 1
  Event: time 1597066502.755372, -- SYN_REPORT 
  Event: time 1597066502.761653, type 4 (EV_MSC), code 4 (MSC_SCAN), value 86
  Event: time 1597066502.761653, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 0
  Event: time 1597066502.761653, -- SYN_REPORT 
  Event: time 1597066521.533682, type 4 (EV_MSC), code 4 (MSC_SCAN), value 85
  Event: time 1597066521.533682, type 1 (EV_KEY), code 224 
(KEY_BRIGHTNESSDOWN), value 1
  Event: time 1597066521.533682, -- SYN_REPORT 
  Event: time 1597066521.542973, type 4 (EV_MSC), code 4 (MSC_SCAN), value 85
  Event: time 1597066521.542973, type 1 (EV_KEY), code 224 
(KEY_BRIGHTNESSDOWN), value 0

  $ lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.core.rules
  Date: Mon Aug 10 10:44:20 2020
  InstallationDate: Installed on 2018-07-23 (749 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 5558
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=c78b51e8-c664-4dd2-8020-7bc5da6f2bc0 ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2020-07-11 (29 days ago)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0R392V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5558:pvr01:rvnDellInc.:rn0R392V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5558
  dmi.product.sku: Inspiron 5558
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1892909] Re: ACPI Error

[Alex Hung]

These object names look like "PCI Interrupt Link Device" but they are
not declared (further analysis requires acpidump log - sudo acpidump >
acpi.log). This is a BIOS bug which kernel can do little to help.

Fortunately, if you don't observe any obvious failures, these errors can
be ignored

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

Title:
  ACPI Error

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 
x86_64 GNU/Linux
  -


  
  [0.297458] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKC (20190816/dspkginit-438)
  [0.297464] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKD (20190816/dspkginit-438)
  [0.297468] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKA (20190816/dspkginit-438)
  [0.297472] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKB (20190816/dspkginit-438)
  [0.297482] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKD (20190816/dspkginit-438)
  [0.297485] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKA (20190816/dspkginit-438)
  [0.297489] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKB (20190816/dspkginit-438)
  [0.297492] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKC (20190816/dspkginit-438)
  [0.297502] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKA (20190816/dspkginit-438)
  [0.297506] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKB (20190816/dspkginit-438)
  [0.297509] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKC (20190816/dspkginit-438)
  [0.297512] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKD (20190816/dspkginit-438)
  [0.297523] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKB (20190816/dspkginit-438)
  [0.297526] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKC (20190816/dspkginit-438)
  [0.297529] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKD (20190816/dspkginit-438)
  [0.297533] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKA (20190816/dspkginit-438)
  [0.297543] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKC (20190816/dspkginit-438)
  [0.297546] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKD (20190816/dspkginit-438)
  [0.297550] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKA (20190816/dspkginit-438)
  [0.297553] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKB (20190816/dspkginit-438)
  [0.297563] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKD (20190816/dspkginit-438)
  [0.297566] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKA (20190816/dspkginit-438)
  [0.297570] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKB (20190816/dspkginit-438)
  [0.297573] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKC (20190816/dspkginit-438)
  [0.297583] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKB (20190816/dspkginit-438)
  [0.297586] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKC (20190816/dspkginit-438)
  [0.297590] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKD (20190816/dspkginit-438)
  [0.297593] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKA (20190816/dspkginit-438)
  [0.297603] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKC (20190816/dspkginit-438)
  [0.297607] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKD (20190816/dspkginit-438)
  [0.297610] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKA (20190816/dspkginit-438)
  [0.297614] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKB (20190816/dspkginit-438)
  [0.297623] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKD (20190816/dspkginit-438)
  [0.297627] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKA (20190816/dspkginit-438)
  [0.297630] ACPI Error: AE_NOT_FOUND, While resolving a na

[Kernel-packages] [Bug 1893624] Re: Ryzen 4800u, kernel 5.8.5 boot errors (AMD-Vi, ACPI, HDCP, Bluetooth)

[Alex Hung]

Linux 5.8.5-050805, or any kernels on https://kernel.ubuntu.com/~kernel-
ppa/mainline/, is not a supported kernel version.

Kernel 5.8 is also used on groovy. Please download and install deb @
https://people.canonical.com/~alexhung/LP1893624/

Once installed, please verify errors and update bug descriptions if
errors are still present.

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

Title:
  Ryzen 4800u, kernel 5.8.5 boot errors (AMD-Vi, ACPI, HDCP, Bluetooth)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Lenovo Ideapad S540 13ARE (AMD Ryzen 4800U).
  Ubuntu Budgie 20.04.1 LTS, updated kernel to 5.8.5. Secure Boot disabled. 
Clean install with entire disk (Windows came preinstalled) wiped out.

  Most things work just fine. If not for the errors shown during boot, I
  would not have noticed the issues.Video (native resolutions works),
  audio, wifi, suspend, the quick buttons (brightness, volume etc) all
  work fine. However during boot, errors are shortly shown:

  asterix@Idefix:~$ sudo dmesg -l err
  [3.204455] pci :00:00.2: AMD-Vi: Unable to read/write to IOMMU perf 
counter.
  [4.901524] I2C multi instantiate pseudo device driver INT3515:00: IRQ 
index 1 not found
  [4.919327] snd_pci_acp3x :03:00.5: Invalid ACP audio mode : 0
  [4.939476] ACPI Error: No handler for Region [ECSI] (bf2d92b9) 
[EmbeddedControl] (20200528/evregion-127)
  [4.939724] ACPI Error: Region EmbeddedControl (ID=3) has no handler 
(20200528/exfldio-261)
  [4.939929] ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous 
error (AE_NOT_EXIST) (20200528/psparse-529)
  [4.940212] ACPI Error: Aborting method \_SB.UBTC._DSM due to previous 
error (AE_NOT_EXIST) (20200528/psparse-529)
  [4.940517] ucsi_acpi USBC000:00: ucsi_acpi_dsm: failed to evaluate _DSM 2
  [5.235689] acp_pdm_mach acp_pdm_mach.0: snd_soc_register_card(acp) 
failed: -517
  [6.273068] [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find 
connector for link!
  [6.273591] [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find 
connector for link!
  [6.273748] [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find 
connector for link!
  [7.036019] [drm:mod_hdcp_add_display_to_topology [amdgpu]] *ERROR* Failed 
to add display topology, DTM TA is not initialized.
  [7.891436] Bluetooth: hci0: Failed to send Intel_Write_DDC (-22)```

  lspci-vnvn.log: https://pastebin.com/Kygie8nu

  What can I do to help solve this? Note I am not a developer and a Linux 
novice.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-30 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Package: linux (not installed)
  Tags:  focal
  Uname: Linux 5.8.5-050805-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1893624] Re: Ryzen 4800u, kernel 5.8.5 boot errors (AMD-Vi, ACPI, HDCP, Bluetooth)

[Alex Hung]

You can use apt purge to remove installed kernel: sudo apt purge linux-
image-... linux-header-..., where ... is the version you want to remove.

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

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

Title:
  Ryzen 4800u, kernel 5.8.5 boot errors (AMD-Vi, ACPI, HDCP, Bluetooth)

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Lenovo Ideapad S540 13ARE (AMD Ryzen 4800U).
  Ubuntu Budgie 20.04.1 LTS, updated kernel to 5.8.5. Secure Boot disabled. 
Clean install with entire disk (Windows came preinstalled) wiped out.

  Most things work just fine. If not for the errors shown during boot, I
  would not have noticed the issues.Video (native resolutions works),
  audio, wifi, suspend, the quick buttons (brightness, volume etc) all
  work fine. However during boot, errors are shortly shown:

  asterix@Idefix:~$ sudo dmesg -l err
  [3.204455] pci :00:00.2: AMD-Vi: Unable to read/write to IOMMU perf 
counter.
  [4.901524] I2C multi instantiate pseudo device driver INT3515:00: IRQ 
index 1 not found
  [4.919327] snd_pci_acp3x :03:00.5: Invalid ACP audio mode : 0
  [4.939476] ACPI Error: No handler for Region [ECSI] (bf2d92b9) 
[EmbeddedControl] (20200528/evregion-127)
  [4.939724] ACPI Error: Region EmbeddedControl (ID=3) has no handler 
(20200528/exfldio-261)
  [4.939929] ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous 
error (AE_NOT_EXIST) (20200528/psparse-529)
  [4.940212] ACPI Error: Aborting method \_SB.UBTC._DSM due to previous 
error (AE_NOT_EXIST) (20200528/psparse-529)
  [4.940517] ucsi_acpi USBC000:00: ucsi_acpi_dsm: failed to evaluate _DSM 2
  [5.235689] acp_pdm_mach acp_pdm_mach.0: snd_soc_register_card(acp) 
failed: -517
  [6.273068] [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find 
connector for link!
  [6.273591] [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find 
connector for link!
  [6.273748] [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find 
connector for link!
  [7.036019] [drm:mod_hdcp_add_display_to_topology [amdgpu]] *ERROR* Failed 
to add display topology, DTM TA is not initialized.
  [7.891436] Bluetooth: hci0: Failed to send Intel_Write_DDC (-22)```

  lspci-vnvn.log: https://pastebin.com/Kygie8nu

  What can I do to help solve this? Note I am not a developer and a Linux 
novice.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-30 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Package: linux (not installed)
  Tags:  focal
  Uname: Linux 5.8.5-050805-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1882823] Re: int3403 thermal INT3403:00

[Alex Hung]

The fix is included in Ubuntu-5.4.0-43.47 and later

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

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

Title:
  int3403 thermal INT3403:00

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  [8.112761] int3403 thermal INT3403:00: Unsupported event [0x91]
  [   10.121722] int3403 thermal INT3403:00: Unsupported event [0x91]
  [   12.165233] int3403 thermal INT3403:00: Unsupported event [0x91]

  Is constantly flooding my dmesg. I believe this is also due to missing
  audio drivers as well. Which is another issue that I am facing.

  Realtek ALC1220

  Ubuntu 20.04

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

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

[Kernel-packages] [Bug 1894392] Re: brightness slider working but not the brightness in ubuntu 20.04

[Alex Hung]

Did you try to remove the kernel parameter "acpi_osi=linux"?

Please run "ls /sys/class/backlight/" to see what backlight interfaces
are available.

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

Title:
  brightness slider working but not the brightness in ubuntu 20.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  brightness control not working

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-46-generic 5.4.0-46.50
  ProcVersionSignature: Ubuntu 5.4.0-46.50-generic 5.4.60
  Uname: Linux 5.4.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sakthee4780 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  6 01:01:49 2020
  HibernationDevice: RESUME=UUID=5441a3ef-63d8-4455-b227-f27cec9e699f
  InstallationDate: Installed on 2020-06-12 (85 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP 241 G1
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-46-generic root=/dev/sda2 
ro quiet nomodeset acpi_osi=linux
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-46-generic N/A
   linux-backports-modules-5.4.0-46-generic  N/A
   linux-firmware1.187.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/27/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.31
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8072
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 70.07
  dmi.chassis.asset.tag: 5CG5380YZX
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.31:bd04/27/2015:svnHewlett-Packard:pnHP241G1:pvr098810400010060370081:rvnHewlett-Packard:rn8072:rvrKBCVersion70.07:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PRE X=MIN
  dmi.product.name: HP 241 G1
  dmi.product.sku: P4C96PC#ACJ
  dmi.product.version: 098810400010060370081
  dmi.sys.vendor: Hewlett-Packard

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

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