[Kernel-packages] [Bug 1901922] Autopkgtest regression report (alsa-lib/1.2.3.2-1ubuntu3.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted alsa-lib (1.2.3.2-1ubuntu3.1) for 
groovy have finished running.
The following regressions have been reported in tests triggered by the package:

openjdk-8/8u275-b01-0ubuntu1~20.10 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/groovy/update_excuses.html#alsa-lib

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

Thank you!

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

Title:
  [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup

Status in PulseAudio:
  Unknown
Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in alsa-lib source package in Groovy:
  Fix Committed
Status in alsa-ucm-conf source package in Groovy:
  Fix Committed
Status in alsa-lib source package in Hirsute:
  Fix Committed
Status in alsa-ucm-conf source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  On the machines with AMD Ryzen acp audio design, the audio can't work
  anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1(
  focal), this is a regression on libasound2 for those machines. the AMD
  Ryzen acp audio card needs to load ucm to work with pulseaudio, but
  this audio card doesn't have an independant ucm for it, it needs to
  link to an existing HDA-Intel ucm, the check_empty_configuration() needs
  to cover the situation that Linked is true, otherwise it will fail
  to load the ucm for the audio card. Even the audio card could load the
  ucm, the output is muted and the init output volume is too low if
  freshly install the OS on these machines.

  [Fix]
  Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD
  Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix
  init mute and init output volume problem.

  [Test Case]
  Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf
  /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd
  list-cards, we could see the pulseaudio load the ucm successfully and we 
could see
  the sound card is generated and all output and input devices are listed
  under sound card, but the init output is muted and the volume is very low
  if we manually unumte it. Now install the updated alsa-ucm-conf, rm 
~/.config/pulse/*; sudo rm -rf
  /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is
  not muted anymore and the output volume is OK to most users.

  [Regression Risk]
  This could make the machines with sof audio driver fail to load ucm
  , then all audio function can't work as before, like the speaker can't
  output sound or the internal mic can't be found or can't record sound.
  But this possibility is very low, I tested this SRU on some machines with or
  without sof audio driver, all worked as well as before.

  
  After logging in, only a dummy device is available for audio playback 
(resulting in no audible playback). When running "pactl load-module 
module-detect" the sound card shows up, and playback works as expected.

  If pulseaudio is restarted with "pulseaudio -k" the playback device
  disappears again. Running the above command get things working again.

  If I change the following section in /etc/pulse/default.pa from:

  ### Automatically load driver modules depending on the hardware available
  .ifexists module-udev-detect.so
  load-module module-udev-detect
  .else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  .endif

  To:

  ### Automatically load driver modules depending on the hardware available
  #.ifexists module-udev-detect.so
  #load-module module-udev-detect
  #.else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  #.endif

  Things start working as they should after running "pulseaudio -k".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Oct 28 17:21:02 2020
  InstallationDate: Installed on 2020-10-23 (4 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2020
  dmi.bios.release: 1.9
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET40W

[Kernel-packages] [Bug 1901922] Autopkgtest regression report (alsa-lib/1.2.2-2.1ubuntu2.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted alsa-lib (1.2.2-2.1ubuntu2.2) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

openjdk-8/8u275-b01-0ubuntu1~20.04 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#alsa-lib

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

Thank you!

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

Title:
  [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup

Status in PulseAudio:
  Unknown
Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in alsa-lib source package in Groovy:
  Fix Committed
Status in alsa-ucm-conf source package in Groovy:
  Fix Committed
Status in alsa-lib source package in Hirsute:
  Fix Committed
Status in alsa-ucm-conf source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  On the machines with AMD Ryzen acp audio design, the audio can't work
  anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1(
  focal), this is a regression on libasound2 for those machines. the AMD
  Ryzen acp audio card needs to load ucm to work with pulseaudio, but
  this audio card doesn't have an independant ucm for it, it needs to
  link to an existing HDA-Intel ucm, the check_empty_configuration() needs
  to cover the situation that Linked is true, otherwise it will fail
  to load the ucm for the audio card. Even the audio card could load the
  ucm, the output is muted and the init output volume is too low if
  freshly install the OS on these machines.

  [Fix]
  Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD
  Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix
  init mute and init output volume problem.

  [Test Case]
  Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf
  /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd
  list-cards, we could see the pulseaudio load the ucm successfully and we 
could see
  the sound card is generated and all output and input devices are listed
  under sound card, but the init output is muted and the volume is very low
  if we manually unumte it. Now install the updated alsa-ucm-conf, rm 
~/.config/pulse/*; sudo rm -rf
  /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is
  not muted anymore and the output volume is OK to most users.

  [Regression Risk]
  This could make the machines with sof audio driver fail to load ucm
  , then all audio function can't work as before, like the speaker can't
  output sound or the internal mic can't be found or can't record sound.
  But this possibility is very low, I tested this SRU on some machines with or
  without sof audio driver, all worked as well as before.

  
  After logging in, only a dummy device is available for audio playback 
(resulting in no audible playback). When running "pactl load-module 
module-detect" the sound card shows up, and playback works as expected.

  If pulseaudio is restarted with "pulseaudio -k" the playback device
  disappears again. Running the above command get things working again.

  If I change the following section in /etc/pulse/default.pa from:

  ### Automatically load driver modules depending on the hardware available
  .ifexists module-udev-detect.so
  load-module module-udev-detect
  .else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  .endif

  To:

  ### Automatically load driver modules depending on the hardware available
  #.ifexists module-udev-detect.so
  #load-module module-udev-detect
  #.else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  #.endif

  Things start working as they should after running "pulseaudio -k".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Oct 28 17:21:02 2020
  InstallationDate: Installed on 2020-10-23 (4 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2020
  dmi.bios.release: 1.9
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET40W(1

[Kernel-packages] [Bug 1901922] Re: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup

[Nick Price]

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

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

Title:
  [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup

Status in PulseAudio:
  Unknown
Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in alsa-lib source package in Groovy:
  Fix Committed
Status in alsa-ucm-conf source package in Groovy:
  Fix Committed
Status in alsa-lib source package in Hirsute:
  Fix Committed
Status in alsa-ucm-conf source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  On the machines with AMD Ryzen acp audio design, the audio can't work
  anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1(
  focal), this is a regression on libasound2 for those machines. the AMD
  Ryzen acp audio card needs to load ucm to work with pulseaudio, but
  this audio card doesn't have an independant ucm for it, it needs to
  link to an existing HDA-Intel ucm, the check_empty_configuration() needs
  to cover the situation that Linked is true, otherwise it will fail
  to load the ucm for the audio card. Even the audio card could load the
  ucm, the output is muted and the init output volume is too low if
  freshly install the OS on these machines.

  [Fix]
  Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD
  Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix
  init mute and init output volume problem.

  [Test Case]
  Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf
  /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd
  list-cards, we could see the pulseaudio load the ucm successfully and we 
could see
  the sound card is generated and all output and input devices are listed
  under sound card, but the init output is muted and the volume is very low
  if we manually unumte it. Now install the updated alsa-ucm-conf, rm 
~/.config/pulse/*; sudo rm -rf
  /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is
  not muted anymore and the output volume is OK to most users.

  [Regression Risk]
  This could make the machines with sof audio driver fail to load ucm
  , then all audio function can't work as before, like the speaker can't
  output sound or the internal mic can't be found or can't record sound.
  But this possibility is very low, I tested this SRU on some machines with or
  without sof audio driver, all worked as well as before.

  
  After logging in, only a dummy device is available for audio playback 
(resulting in no audible playback). When running "pactl load-module 
module-detect" the sound card shows up, and playback works as expected.

  If pulseaudio is restarted with "pulseaudio -k" the playback device
  disappears again. Running the above command get things working again.

  If I change the following section in /etc/pulse/default.pa from:

  ### Automatically load driver modules depending on the hardware available
  .ifexists module-udev-detect.so
  load-module module-udev-detect
  .else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  .endif

  To:

  ### Automatically load driver modules depending on the hardware available
  #.ifexists module-udev-detect.so
  #load-module module-udev-detect
  #.else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  #.endif

  Things start working as they should after running "pulseaudio -k".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Oct 28 17:21:02 2020
  InstallationDate: Installed on 2020-10-23 (4 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2020
  dmi.bios.release: 1.9
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET40W(1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UDCTO1WW
  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.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UDCTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20UDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14 Gen 1

[Kernel-packages] [Bug 1901922] Re: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup

[Nick Price]

Oh, as mentioned elsewhere, the microphone light on the keyboard doesn't
seem to turn off/on as expected, but this may be an issue elsewhere
(FWIW it works as expected under a current Fedora install on this
system)

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

Title:
  [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup

Status in PulseAudio:
  Unknown
Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in alsa-lib source package in Groovy:
  Fix Committed
Status in alsa-ucm-conf source package in Groovy:
  Fix Committed
Status in alsa-lib source package in Hirsute:
  Fix Committed
Status in alsa-ucm-conf source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  On the machines with AMD Ryzen acp audio design, the audio can't work
  anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1(
  focal), this is a regression on libasound2 for those machines. the AMD
  Ryzen acp audio card needs to load ucm to work with pulseaudio, but
  this audio card doesn't have an independant ucm for it, it needs to
  link to an existing HDA-Intel ucm, the check_empty_configuration() needs
  to cover the situation that Linked is true, otherwise it will fail
  to load the ucm for the audio card. Even the audio card could load the
  ucm, the output is muted and the init output volume is too low if
  freshly install the OS on these machines.

  [Fix]
  Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD
  Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix
  init mute and init output volume problem.

  [Test Case]
  Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf
  /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd
  list-cards, we could see the pulseaudio load the ucm successfully and we 
could see
  the sound card is generated and all output and input devices are listed
  under sound card, but the init output is muted and the volume is very low
  if we manually unumte it. Now install the updated alsa-ucm-conf, rm 
~/.config/pulse/*; sudo rm -rf
  /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is
  not muted anymore and the output volume is OK to most users.

  [Regression Risk]
  This could make the machines with sof audio driver fail to load ucm
  , then all audio function can't work as before, like the speaker can't
  output sound or the internal mic can't be found or can't record sound.
  But this possibility is very low, I tested this SRU on some machines with or
  without sof audio driver, all worked as well as before.

  
  After logging in, only a dummy device is available for audio playback 
(resulting in no audible playback). When running "pactl load-module 
module-detect" the sound card shows up, and playback works as expected.

  If pulseaudio is restarted with "pulseaudio -k" the playback device
  disappears again. Running the above command get things working again.

  If I change the following section in /etc/pulse/default.pa from:

  ### Automatically load driver modules depending on the hardware available
  .ifexists module-udev-detect.so
  load-module module-udev-detect
  .else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  .endif

  To:

  ### Automatically load driver modules depending on the hardware available
  #.ifexists module-udev-detect.so
  #load-module module-udev-detect
  #.else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  #.endif

  Things start working as they should after running "pulseaudio -k".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Oct 28 17:21:02 2020
  InstallationDate: Installed on 2020-10-23 (4 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2020
  dmi.bios.release: 1.9
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET40W(1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UDCTO1WW
  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.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn2

[Kernel-packages] [Bug 1901922] Re: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup

[Nick Price]

Did a fresh install of Groovy on an affected machine and updated it to
the latest release packages first, and confirmed the audio issue still
existed.

I then installed the packages above and rebooted, and audio seems to be
working as expected on that system now.

I think that did the trick!

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

Title:
  [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup

Status in PulseAudio:
  Unknown
Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in alsa-lib source package in Groovy:
  Fix Committed
Status in alsa-ucm-conf source package in Groovy:
  Fix Committed
Status in alsa-lib source package in Hirsute:
  Fix Committed
Status in alsa-ucm-conf source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  On the machines with AMD Ryzen acp audio design, the audio can't work
  anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1(
  focal), this is a regression on libasound2 for those machines. the AMD
  Ryzen acp audio card needs to load ucm to work with pulseaudio, but
  this audio card doesn't have an independant ucm for it, it needs to
  link to an existing HDA-Intel ucm, the check_empty_configuration() needs
  to cover the situation that Linked is true, otherwise it will fail
  to load the ucm for the audio card. Even the audio card could load the
  ucm, the output is muted and the init output volume is too low if
  freshly install the OS on these machines.

  [Fix]
  Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD
  Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix
  init mute and init output volume problem.

  [Test Case]
  Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf
  /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd
  list-cards, we could see the pulseaudio load the ucm successfully and we 
could see
  the sound card is generated and all output and input devices are listed
  under sound card, but the init output is muted and the volume is very low
  if we manually unumte it. Now install the updated alsa-ucm-conf, rm 
~/.config/pulse/*; sudo rm -rf
  /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is
  not muted anymore and the output volume is OK to most users.

  [Regression Risk]
  This could make the machines with sof audio driver fail to load ucm
  , then all audio function can't work as before, like the speaker can't
  output sound or the internal mic can't be found or can't record sound.
  But this possibility is very low, I tested this SRU on some machines with or
  without sof audio driver, all worked as well as before.

  
  After logging in, only a dummy device is available for audio playback 
(resulting in no audible playback). When running "pactl load-module 
module-detect" the sound card shows up, and playback works as expected.

  If pulseaudio is restarted with "pulseaudio -k" the playback device
  disappears again. Running the above command get things working again.

  If I change the following section in /etc/pulse/default.pa from:

  ### Automatically load driver modules depending on the hardware available
  .ifexists module-udev-detect.so
  load-module module-udev-detect
  .else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  .endif

  To:

  ### Automatically load driver modules depending on the hardware available
  #.ifexists module-udev-detect.so
  #load-module module-udev-detect
  #.else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  #.endif

  Things start working as they should after running "pulseaudio -k".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Oct 28 17:21:02 2020
  InstallationDate: Installed on 2020-10-23 (4 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2020
  dmi.bios.release: 1.9
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET40W(1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UDCTO1WW
  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.ec.firmware.release: 1.9
  dmi.moda

[Kernel-packages] [Bug 1904054] Re: kernel 5.8 general protection fault at boot

[Colin Ian King]

It maybe worth checking with one or more of the mainline kernels to see
if these behave differently from the Ubuntu kernel just to see if they
boot fine or if they suffer from the same issue.

The mainline kernels can be found in https://kernel.ubuntu.com/~kernel-
ppa/mainline

For example, it may be worth installing the initial 5.8 kernel release
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8/ - use the
following:

https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8/amd64/linux-headers-5.8.0-050800-generic_5.8.0-050800.202008022230_amd64.deb
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8/amd64/linux-headers-5.8.0-050800_5.8.0-050800.202008022230_all.deb
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8/amd64/linux-image-unsigned-5.8.0-050800-generic_5.8.0-050800.202008022230_amd64.deb
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8/amd64/linux-modules-5.8.0-050800-generic_5.8.0-050800.202008022230_amd64.deb

If this boots OK, then maybe then try the latest mainline 5.8 kernel in
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.18/

Failing that, it may be worth trying the mainline kernels from 5.5..to
5.7 too to see when the issue starts to occur.

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

Title:
  kernel 5.8 general protection fault at boot

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu kernel version 5.8.0-28 (as well as the previous 5.8.0-26)
  crashes at boot with many general protection faults, on my Intel NUC
  10. Ubuntu kernel version 5.4.0-52 did not exhibit this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-28-generic 5.8.0-28.30
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  benp   2912 F pulseaudio
   /dev/snd/controlC1:  benp   2912 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 12 11:51:07 2020
  InstallationDate: Installed on 2020-10-08 (35 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Intel(R) Client Systems NUC10i7FNH
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash crashkernel=512M-:192M
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.190.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2020-10-28 (15 days ago)
  dmi.bios.date: 08/17/2020
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: FNCML357.0045.2020.0817.1709
  dmi.board.asset.tag: Default string
  dmi.board.name: NUC10i7FNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K61360-302
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrFNCML357.0045.2020.0817.1709:bd08/17/2020:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: FN
  dmi.product.name: NUC10i7FNH
  dmi.product.sku: BXNUC10i7FNH
  dmi.product.version: K61081-302
  dmi.sys.vendor: Intel(R) Client Systems

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

-- 
Mailing list: https://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 1903048] Re: [SRU] Bluetooth won't activate on the pi 400

[Dave Jones]

On Fri, Nov 13, 2020 at 09:37:34AM -, Sebastien Bacher wrote:
>@Matthieu, @Dave, thanks for the comments and details.
>
>I'm not blocking work to land, the 20.10 SRU could be accepted now and I 
>didn't revert in that serie.
>The SRU team tries to ensure the fix is in the new serie so it doesn't get 
>forgotten/regress when next version is out but I think it's pretty clear we 
>are going to sort out the review details, that's not a blocker and SRU team 
>has been happy in the past to let things in with the understand than $newserie 
>is being sorted out

Ah, my apologies - I had mis-interpreted the reversion as applying to 
the SRU. I've no issue with a reversion in hirsute, provided it doesn't 
delay existing users from using their Bluetooth hardware.

>> If upstream say "yes" to the patches, without further discussion: that's
>> great, but there'd presumably still be some delay before another version
>> makes its way down to us, so we'd be applying *some* patch to make it work 
>> in the interim.
>
>Again I'm not asking for the patches to be reviewed or accepted upstream
>before they are uploaded to Ubuntu, I'm just asking for them to be sent
>upstream and the reference to the email/report/merge request to be added
>to the patches. It would probably have been less work to just do it
>rather than type a long explanation here on why we need to distro patch
>in any case (which I never  disagreed with)

I estimate, as I think several others do judging by various comments, 
that the patches in their current state don't stand much chance of 
passing muster upstream, and I have no desire to waste their time with a 
premature submission. At the very least, some justification needs adding 
to the 1 second sleep: either a datasheet reference, which I've so far 
failed to find, or some empirical measurements that it's actually 
required (which I'm in the process of gathering; I've verified *a* delay 
is required but not the minimum, or whether it can be combined with the 
post-load nanosleep), along with evidence it doesn't break any existing 
platforms (I've found a datasheet reference to back that bit up, but 
tests are good too).

Anyway, sorry I mis-interpreted the release your action applied to; I 
look forward to seeing the SRU land.

In the meantime, rest assured a submission will be made upstream as soon 
as I think I've got a faint hope of it passing!

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

Title:
  [SRU] Bluetooth won't activate on the pi 400

Status in bluez package in Ubuntu:
  Triaged
Status in bluez source package in Hirsute:
  Triaged

Bug description:
  [Impact]

  Without these patches, Bluetooth is inoperable on the recently
  released Raspberry Pi 400.

  [Test Case]

  * Boot the Ubuntu Desktop for Pi image on a Pi 400.
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is not enabled and attempting to activate it fails
  * sudo add-apt-repository ppa:waveform/pi-bluetooth
  * sudo apt update
  * sudo apt install bluez
  * sudo reboot
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, 
mobile phones, headphones, etc.) can connect and operate correctly 

  [Regression Potential]

  Extremely low (on groovy in particular, this has the same version of
  bluez as hirsute). The only significant risk is to non-Pi platforms or
  dongles which also use the Broadcom 43xx (or Cypress 305) chips for
  Bluetooth which might be inadvertently affected by these patches.

  [Original Description]

  The new Pi 400 has a slightly different Wifi/BT chip to the Pi4.
  Whilst wifi works happily, Bluetooth fails to operate. This doesn't
  appear to be an issue with either the firmware (the latest versions
  from upstream Raspbian have been tried), or the kernel (a known-good
  raspi kernel has been tested under Ubuntu), but with Bluez itself.
  Specifically, tracing the initialization with btmon on Raspbian and
  Ubuntu, the stack consistently fails when attempting to "Set Default
  PHY" on the latter. Curiously, under Ubuntu the adapter also appears
  to lack a MAC address.

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

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

[Kernel-packages] [Bug 1904249] Missing required logs.

[Ubuntu Kernel Bot]

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

apport-collect 1904249

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

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

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

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

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

Title:
  nvidia: module license 'NVIDIA' taints kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The nvidia module is not loaded properly on kernel 5.8 which is
  causing the fan/thermals to go crazy. This only happens when running
  on Nvidia and Ondemand. No issues on Intel graphics.

  The error goes away on kernel 5.4

  Ubuntu 20.04
  Nvidia 450.80.02
  5.8.0-28-generic

  $ dmesg | grep nvidia
  [1.159145] nvidia-gpu :01:00.3: enabling device ( -> 0002)
  [3.446992] nvidia: loading out-of-tree module taints kernel.
  [3.447002] nvidia: module license 'NVIDIA' taints kernel.
  [3.482650] nvidia-nvlink: Nvlink Core is being initialized, major device 
number 511
  [3.483217] nvidia :01:00.0: enabling device (0006 -> 0007)
  [3.483347] nvidia :01:00.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=none:owns=none
  [3.618157] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for 
UNIX platforms  450.80.02  Wed Sep 23 00:48:09 UTC 2020
  [3.630548] [drm] [nvidia-drm] [GPU ID 0x0100] Loading driver
  [3.630551] [drm] Initialized nvidia-drm 0.0.0 20160202 for :01:00.0 
on minor 1
  [3.662490] audit: type=1400 audit(1605307253.247:6): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=690 
comm="apparmor_parser"
  [3.664545] audit: type=1400 audit(1605307253.247:7): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" 
pid=690 comm="apparmor_parser"
  [3.701059] nvidia_uvm: module verification failed: signature and/or 
required key missing - tainting kernel
  [3.706629] nvidia-uvm: Loaded the UVM driver, major device number 509.
  [4.225159] nvidia-gpu :01:00.3: i2c timeout error e000

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

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

[Kernel-packages] [Bug 1904249] [NEW] nvidia: module license 'NVIDIA' taints kernel

[Juno Computers]

Public bug reported:

The nvidia module is not loaded properly on kernel 5.8 which is causing
the fan/thermals to go crazy. This only happens when running on Nvidia
and Ondemand. No issues on Intel graphics.

The error goes away on kernel 5.4

Ubuntu 20.04
Nvidia 450.80.02
5.8.0-28-generic

$ dmesg | grep nvidia
[1.159145] nvidia-gpu :01:00.3: enabling device ( -> 0002)
[3.446992] nvidia: loading out-of-tree module taints kernel.
[3.447002] nvidia: module license 'NVIDIA' taints kernel.
[3.482650] nvidia-nvlink: Nvlink Core is being initialized, major device 
number 511
[3.483217] nvidia :01:00.0: enabling device (0006 -> 0007)
[3.483347] nvidia :01:00.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=none:owns=none
[3.618157] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for 
UNIX platforms  450.80.02  Wed Sep 23 00:48:09 UTC 2020
[3.630548] [drm] [nvidia-drm] [GPU ID 0x0100] Loading driver
[3.630551] [drm] Initialized nvidia-drm 0.0.0 20160202 for :01:00.0 on 
minor 1
[3.662490] audit: type=1400 audit(1605307253.247:6): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=690 
comm="apparmor_parser"
[3.664545] audit: type=1400 audit(1605307253.247:7): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" 
pid=690 comm="apparmor_parser"
[3.701059] nvidia_uvm: module verification failed: signature and/or 
required key missing - tainting kernel
[3.706629] nvidia-uvm: Loaded the UVM driver, major device number 509.
[4.225159] nvidia-gpu :01:00.3: i2c timeout error e000

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

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

Title:
  nvidia: module license 'NVIDIA' taints kernel

Status in linux package in Ubuntu:
  New

Bug description:
  The nvidia module is not loaded properly on kernel 5.8 which is
  causing the fan/thermals to go crazy. This only happens when running
  on Nvidia and Ondemand. No issues on Intel graphics.

  The error goes away on kernel 5.4

  Ubuntu 20.04
  Nvidia 450.80.02
  5.8.0-28-generic

  $ dmesg | grep nvidia
  [1.159145] nvidia-gpu :01:00.3: enabling device ( -> 0002)
  [3.446992] nvidia: loading out-of-tree module taints kernel.
  [3.447002] nvidia: module license 'NVIDIA' taints kernel.
  [3.482650] nvidia-nvlink: Nvlink Core is being initialized, major device 
number 511
  [3.483217] nvidia :01:00.0: enabling device (0006 -> 0007)
  [3.483347] nvidia :01:00.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=none:owns=none
  [3.618157] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for 
UNIX platforms  450.80.02  Wed Sep 23 00:48:09 UTC 2020
  [3.630548] [drm] [nvidia-drm] [GPU ID 0x0100] Loading driver
  [3.630551] [drm] Initialized nvidia-drm 0.0.0 20160202 for :01:00.0 
on minor 1
  [3.662490] audit: type=1400 audit(1605307253.247:6): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=690 
comm="apparmor_parser"
  [3.664545] audit: type=1400 audit(1605307253.247:7): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" 
pid=690 comm="apparmor_parser"
  [3.701059] nvidia_uvm: module verification failed: signature and/or 
required key missing - tainting kernel
  [3.706629] nvidia-uvm: Loaded the UVM driver, major device number 509.
  [4.225159] nvidia-gpu :01:00.3: i2c timeout error e000

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

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

[Kernel-packages] [Bug 1904054] Re: kernel 5.8 general protection fault at boot

[Ben Poliakoff]

I updated GRUB_CMDLINE_LINUX_DEFAULT. I was able to boot to multiuser
mode once (kernel boot log for that is attached, titled "kern.log.debug-
successful").  The system locked up shortly after I stashed a copy of
that log.

** Attachment added: "Successful boot of 5.8.0-28-generic (which subsequently 
locked up)"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904054/+attachment/5434231/+files/kern.log.debug-successful

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

Title:
  kernel 5.8 general protection fault at boot

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu kernel version 5.8.0-28 (as well as the previous 5.8.0-26)
  crashes at boot with many general protection faults, on my Intel NUC
  10. Ubuntu kernel version 5.4.0-52 did not exhibit this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-28-generic 5.8.0-28.30
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  benp   2912 F pulseaudio
   /dev/snd/controlC1:  benp   2912 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 12 11:51:07 2020
  InstallationDate: Installed on 2020-10-08 (35 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Intel(R) Client Systems NUC10i7FNH
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash crashkernel=512M-:192M
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.190.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2020-10-28 (15 days ago)
  dmi.bios.date: 08/17/2020
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: FNCML357.0045.2020.0817.1709
  dmi.board.asset.tag: Default string
  dmi.board.name: NUC10i7FNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K61360-302
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrFNCML357.0045.2020.0817.1709:bd08/17/2020:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: FN
  dmi.product.name: NUC10i7FNH
  dmi.product.sku: BXNUC10i7FNH
  dmi.product.version: K61081-302
  dmi.sys.vendor: Intel(R) Client Systems

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

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

[Kernel-packages] [Bug 1904054] Re: kernel 5.8 general protection fault at boot

[Ben Poliakoff]

Subsequent attempts to boot the 5.8.0-28-generic kernel exhibited GPFs
and at least one full kernel panic, screenshot of that is attached.
Ubuntu kernel version 5.4.0-52-generic remains the only stable option at
the moment.

** Attachment added: "kernel panic with 5.8.0-28-generic"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904054/+attachment/5434232/+files/PXL_20201113_223208755.jpg

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

Title:
  kernel 5.8 general protection fault at boot

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu kernel version 5.8.0-28 (as well as the previous 5.8.0-26)
  crashes at boot with many general protection faults, on my Intel NUC
  10. Ubuntu kernel version 5.4.0-52 did not exhibit this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-28-generic 5.8.0-28.30
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  benp   2912 F pulseaudio
   /dev/snd/controlC1:  benp   2912 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 12 11:51:07 2020
  InstallationDate: Installed on 2020-10-08 (35 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Intel(R) Client Systems NUC10i7FNH
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash crashkernel=512M-:192M
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.190.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2020-10-28 (15 days ago)
  dmi.bios.date: 08/17/2020
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: FNCML357.0045.2020.0817.1709
  dmi.board.asset.tag: Default string
  dmi.board.name: NUC10i7FNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K61360-302
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrFNCML357.0045.2020.0817.1709:bd08/17/2020:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: FN
  dmi.product.name: NUC10i7FNH
  dmi.product.sku: BXNUC10i7FNH
  dmi.product.version: K61081-302
  dmi.sys.vendor: Intel(R) Client Systems

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

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

[Kernel-packages] [Bug 1882388] Re: Touchpad recognised as generic mouse

[Fernando]

Hi,

```uname -r```
5.4.0-53-generic

Issue still ongoing

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

Title:
  Touchpad recognised as generic mouse

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've just re-installed 20.04 (dual boot/windows 10) on my Lenovo
  ideapadY700. My laptop recognises touchpad as mouse. I have no other
  mouse plugged.

  Touchpad firmware: 2ul001af
  Lenovo ideapad700-15ISK BIOS version: CDCN54WW

  I'm new in Ubuntu and I don't know much...

  ```$ uname -a```

  ```Linux nando-Lenovo 5.4.0-33-generic #37-Ubuntu SMP Thu May 21
  12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux```

  ```$ dmesg | grep psmouse```

  ```[   30.218871] psmouse serio1: elantech: synaptics_send_cmd query 0x01 
failed.
  [   30.218879] psmouse serio1: elantech: failed to query firmware version.
  [  165.209816] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost 
synchronization, throwing 2 bytes away.
  [  216.923481] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost 
synchronization, throwing 2 bytes away.
  [  468.662298] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost 
synchronization, throwing 2 bytes away.
  [  553.556484] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost 
synchronization, throwing 2 bytes away.
  ```

  ```$ xinput```

  ```⎡ Virtual core pointer id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ PS/2 Logitech Wheel Mouse   id=14   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ Sleep Buttonid=10   [slave  
keyboard (3)]
  ↳ Lenovo EasyCamera: Lenovo EasyC id=11   [slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  ```

  ```$ cat /proc/bus/input/devices```

  ```I: Bus=0011 Vendor=0002 Product=0001 Version=0063
  N: Name="PS/2 Logitech Wheel Mouse"
  P: Phys=isa0060/serio1/input0
  S: Sysfs=/devices/platform/i8042/serio1/input/input19
  U: Uniq=
  H: Handlers=mouse0 event16
  B: PROP=1
  B: EV=7
  B: KEY=7 0 0 0 0
  B: REL=3
  ```
  I have read a lot of solutions; I tried to use xorg, but it didn't work.
  When I removed it, it worked for a day (only) and I decided erase and 
re-install Ubuntu.

  Please help!
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-33-generic 5.4.0-33.37
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nando  1137 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  6 20:24:24 2020
  InstallationDate: Installed on 2020-06-06 (0 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 002: ID 5986:0672 Acer, Inc Lenovo EasyCamera
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80NV
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=eccd5181-f592-4fbf-a03f-3efbc86e693b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-33-generic N/A
   linux-backports-modules-5.4.0-33-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN54WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 5A
  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 ideapad Y700-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN54WW:bd06/13/2017:svnLENOVO:pn80NV:pvrLenovoideapadY700-15ISK:rvnLENOVO:rnAllsparks5A:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapadY700-15ISK:
  dmi.product.family: IDEAPAD
  dmi.

[Kernel-packages] [Bug 1901272] Re: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4

[Arpad Jordan]

I face a similar issue that I posted on ubuntu forum:

https://ubuntuforums.org/showthread.php?t=2452881

PPA solves my issue and interestingly changes the Bluetooth controller
address

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

Title:
  Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on
  Raspberry Pi 4

Status in bluez package in Ubuntu:
  Incomplete
Status in linux-raspi package in Ubuntu:
  Incomplete
Status in pi-bluetooth package in Ubuntu:
  Confirmed
Status in bluez source package in Groovy:
  Incomplete
Status in linux-raspi source package in Groovy:
  Incomplete
Status in pi-bluetooth source package in Groovy:
  New

Bug description:
  Raspberry pi 4 4Gb ram
  Ubuntu desktop 20.10 64 bit
  After reboot no Bluetooth devices connect, scanning Bluetooth devices works, 
results with same device name (duplicated and with not set up status).
  Sometimes after several reboots it works.
  If I use power off and cycle power then it works fine each time.

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

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

[Kernel-packages] [Bug 1904243] Re: 21.04 Panics attempting to boot 5.10.0-3.4 in gcp EFI disk

[Sean Feole]

** Description changed:

- This was caught while testing a few runs in the google cloud. 
+ This was caught while testing a few runs in the google cloud.
  Steps to reproduce:
- 1.) deploy 21.04 in the cloud (any instance type)
+ 1.) deploy 21.04 in the cloud (n1-standard-1 instance type)
  2.) install 5.10.0-3.4 from the canonical-kernel-team bootstrap ppa
  2a.) sudo add-apt-repository ppa:canonical-kernel-team/bootstrap
  3.) sudo apt install linux-generic-wip
  
  Full startup logs attached:
  
  looks to be grub related, I have not looked into this any further.
  
-1.410153] VFS: Cannot open root device 
"PARTUUID=02631d3d-a298-4349-b157-aa86d82843b5" or unknown-block(0,0): error -6
+    1.410153] VFS: Cannot open root device 
"PARTUUID=02631d3d-a298-4349-b157-aa86d82843b5" or unknown-block(0,0): error -6
  [1.411882] Please append a correct "root=" boot option; here are the 
available partitions:
  [1.413203] Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)
  [1.414356] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.10.0-3-generic 
#4-Ubuntu
  [1.415702] Hardware name: Google Google Compute Engine/Google Compute 
Engine, BIOS Google 01/01/2011
  [1.417180] Call Trace:
  [1.417710]  show_stack+0x52/0x58
  [1.418263]  dump_stack+0x70/0x8b
  [1.418738]  panic+0x101/0x2e3
  [1.419209]  mount_block_root+0x21e/0x298
  [1.419778]  mount_root+0x38/0x3a
  [1.420243]  prepare_namespace+0x13f/0x18d
  [1.420840]  kernel_init_freeable+0x156/0x17d
  [1.421574]  ? rest_init+0xba/0xba
  [1.422135]  kernel_init+0xe/0x116
  [1.422708]  ret_from_fork+0x22/0x30
  [1.423858] Kernel Offset: 0x10c0 from 0x8100 (relocation 
range: 0x8000-0xbfff)
  [1.425374] ACPI MEMORY or I/O RESET_REG.

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

Title:
  21.04 Panics attempting to boot 5.10.0-3.4 in gcp EFI disk

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Hirsute:
  Incomplete

Bug description:
  This was caught while testing a few runs in the google cloud.
  Steps to reproduce:
  1.) deploy 21.04 in the cloud (n1-standard-1 instance type)
  2.) install 5.10.0-3.4 from the canonical-kernel-team bootstrap ppa
  2a.) sudo add-apt-repository ppa:canonical-kernel-team/bootstrap
  3.) sudo apt install linux-generic-wip

  Full startup logs attached:

  looks to be grub related, I have not looked into this any further.

     1.410153] VFS: Cannot open root device 
"PARTUUID=02631d3d-a298-4349-b157-aa86d82843b5" or unknown-block(0,0): error -6
  [1.411882] Please append a correct "root=" boot option; here are the 
available partitions:
  [1.413203] Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)
  [1.414356] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.10.0-3-generic 
#4-Ubuntu
  [1.415702] Hardware name: Google Google Compute Engine/Google Compute 
Engine, BIOS Google 01/01/2011
  [1.417180] Call Trace:
  [1.417710]  show_stack+0x52/0x58
  [1.418263]  dump_stack+0x70/0x8b
  [1.418738]  panic+0x101/0x2e3
  [1.419209]  mount_block_root+0x21e/0x298
  [1.419778]  mount_root+0x38/0x3a
  [1.420243]  prepare_namespace+0x13f/0x18d
  [1.420840]  kernel_init_freeable+0x156/0x17d
  [1.421574]  ? rest_init+0xba/0xba
  [1.422135]  kernel_init+0xe/0x116
  [1.422708]  ret_from_fork+0x22/0x30
  [1.423858] Kernel Offset: 0x10c0 from 0x8100 (relocation 
range: 0x8000-0xbfff)
  [1.425374] ACPI MEMORY or I/O RESET_REG.

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

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

[Kernel-packages] [Bug 1904033] Re: 5.10-rc1+ sdhci crash due to commit e0d072782c734d27f5af062c62266f2598f68542on Synquacer ARM64 dev box

[Colin Ian King]

** Summary changed:

- 5.10-rc1+ sdhci crash due to commit e0d072782c734d27f5af062c62266f2598f68542
+ 5.10-rc1+ sdhci crash due to commit 
e0d072782c734d27f5af062c62266f2598f68542on Synquacer ARM64 dev box

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

Title:
  5.10-rc1+ sdhci crash due to commit
  e0d072782c734d27f5af062c62266f2598f68542on Synquacer ARM64 dev box

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

Bug description:
  Booting 5.10-rc1+ on a Synquacer ARM64 development box crashes.
  Bisected this down to:

  commit e0d072782c734d27f5af062c62266f2598f68542 (HEAD, refs/bisect/bad)
  Author: Jim Quinlan 
  Date:   Thu Sep 17 18:43:40 2020 +0200

  dma-mapping: introduce DMA range map, supplanting dma_pfn_offset

  
  Disabling the sdchi driver and/or removing this commit allows the kernel to 
boot without the crash.

  Attached is a photo of the crash.

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

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

[Kernel-packages] [Bug 1904243] Missing required logs.

[Ubuntu Kernel Bot]

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

apport-collect 1904243

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

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

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

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

** Tags added: breezy

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

Title:
  21.04 Panics attempting to boot 5.10.0-3.4 in gcp EFI disk

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Hirsute:
  Incomplete

Bug description:
  This was caught while testing a few runs in the google cloud. 
  Steps to reproduce:
  1.) deploy 21.04 in the cloud (any instance type)
  2.) install 5.10.0-3.4 from the canonical-kernel-team bootstrap ppa
  2a.) sudo add-apt-repository ppa:canonical-kernel-team/bootstrap
  3.) sudo apt install linux-generic-wip

  Full startup logs attached:

  looks to be grub related, I have not looked into this any further.

 1.410153] VFS: Cannot open root device 
"PARTUUID=02631d3d-a298-4349-b157-aa86d82843b5" or unknown-block(0,0): error -6
  [1.411882] Please append a correct "root=" boot option; here are the 
available partitions:
  [1.413203] Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)
  [1.414356] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.10.0-3-generic 
#4-Ubuntu
  [1.415702] Hardware name: Google Google Compute Engine/Google Compute 
Engine, BIOS Google 01/01/2011
  [1.417180] Call Trace:
  [1.417710]  show_stack+0x52/0x58
  [1.418263]  dump_stack+0x70/0x8b
  [1.418738]  panic+0x101/0x2e3
  [1.419209]  mount_block_root+0x21e/0x298
  [1.419778]  mount_root+0x38/0x3a
  [1.420243]  prepare_namespace+0x13f/0x18d
  [1.420840]  kernel_init_freeable+0x156/0x17d
  [1.421574]  ? rest_init+0xba/0xba
  [1.422135]  kernel_init+0xe/0x116
  [1.422708]  ret_from_fork+0x22/0x30
  [1.423858] Kernel Offset: 0x10c0 from 0x8100 (relocation 
range: 0x8000-0xbfff)
  [1.425374] ACPI MEMORY or I/O RESET_REG.

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

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

[Kernel-packages] [Bug 1904243] [NEW] 21.04 Panics attempting to boot 5.10.0-3.4 in gcp EFI disk

[Sean Feole]

Public bug reported:

This was caught while testing a few runs in the google cloud. 
Steps to reproduce:
1.) deploy 21.04 in the cloud (any instance type)
2.) install 5.10.0-3.4 from the canonical-kernel-team bootstrap ppa
2a.) sudo add-apt-repository ppa:canonical-kernel-team/bootstrap
3.) sudo apt install linux-generic-wip

Full startup logs attached:

looks to be grub related, I have not looked into this any further.

   1.410153] VFS: Cannot open root device 
"PARTUUID=02631d3d-a298-4349-b157-aa86d82843b5" or unknown-block(0,0): error -6
[1.411882] Please append a correct "root=" boot option; here are the 
available partitions:
[1.413203] Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)
[1.414356] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.10.0-3-generic 
#4-Ubuntu
[1.415702] Hardware name: Google Google Compute Engine/Google Compute 
Engine, BIOS Google 01/01/2011
[1.417180] Call Trace:
[1.417710]  show_stack+0x52/0x58
[1.418263]  dump_stack+0x70/0x8b
[1.418738]  panic+0x101/0x2e3
[1.419209]  mount_block_root+0x21e/0x298
[1.419778]  mount_root+0x38/0x3a
[1.420243]  prepare_namespace+0x13f/0x18d
[1.420840]  kernel_init_freeable+0x156/0x17d
[1.421574]  ? rest_init+0xba/0xba
[1.422135]  kernel_init+0xe/0x116
[1.422708]  ret_from_fork+0x22/0x30
[1.423858] Kernel Offset: 0x10c0 from 0x8100 (relocation 
range: 0x8000-0xbfff)
[1.425374] ACPI MEMORY or I/O RESET_REG.

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

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


** Tags: breezy

** Attachment added: "diske.txt"
   https://bugs.launchpad.net/bugs/1904243/+attachment/5434230/+files/diske.txt

** Also affects: linux (Ubuntu Hirsute)
   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/1904243

Title:
  21.04 Panics attempting to boot 5.10.0-3.4 in gcp EFI disk

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Hirsute:
  Incomplete

Bug description:
  This was caught while testing a few runs in the google cloud. 
  Steps to reproduce:
  1.) deploy 21.04 in the cloud (any instance type)
  2.) install 5.10.0-3.4 from the canonical-kernel-team bootstrap ppa
  2a.) sudo add-apt-repository ppa:canonical-kernel-team/bootstrap
  3.) sudo apt install linux-generic-wip

  Full startup logs attached:

  looks to be grub related, I have not looked into this any further.

 1.410153] VFS: Cannot open root device 
"PARTUUID=02631d3d-a298-4349-b157-aa86d82843b5" or unknown-block(0,0): error -6
  [1.411882] Please append a correct "root=" boot option; here are the 
available partitions:
  [1.413203] Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)
  [1.414356] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.10.0-3-generic 
#4-Ubuntu
  [1.415702] Hardware name: Google Google Compute Engine/Google Compute 
Engine, BIOS Google 01/01/2011
  [1.417180] Call Trace:
  [1.417710]  show_stack+0x52/0x58
  [1.418263]  dump_stack+0x70/0x8b
  [1.418738]  panic+0x101/0x2e3
  [1.419209]  mount_block_root+0x21e/0x298
  [1.419778]  mount_root+0x38/0x3a
  [1.420243]  prepare_namespace+0x13f/0x18d
  [1.420840]  kernel_init_freeable+0x156/0x17d
  [1.421574]  ? rest_init+0xba/0xba
  [1.422135]  kernel_init+0xe/0x116
  [1.422708]  ret_from_fork+0x22/0x30
  [1.423858] Kernel Offset: 0x10c0 from 0x8100 (relocation 
range: 0x8000-0xbfff)
  [1.425374] ACPI MEMORY or I/O RESET_REG.

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

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

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

[Timo Aaltonen]

Hello Johan, or anyone else affected,

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

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

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

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

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

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

Title:
  [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup

Status in PulseAudio:
  Unknown
Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in alsa-lib source package in Groovy:
  Fix Committed
Status in alsa-ucm-conf source package in Groovy:
  Fix Committed
Status in alsa-lib source package in Hirsute:
  Fix Committed
Status in alsa-ucm-conf source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  On the machines with AMD Ryzen acp audio design, the audio can't work
  anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1(
  focal), this is a regression on libasound2 for those machines. the AMD
  Ryzen acp audio card needs to load ucm to work with pulseaudio, but
  this audio card doesn't have an independant ucm for it, it needs to
  link to an existing HDA-Intel ucm, the check_empty_configuration() needs
  to cover the situation that Linked is true, otherwise it will fail
  to load the ucm for the audio card. Even the audio card could load the
  ucm, the output is muted and the init output volume is too low if
  freshly install the OS on these machines.

  [Fix]
  Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD
  Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix
  init mute and init output volume problem.

  [Test Case]
  Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf
  /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd
  list-cards, we could see the pulseaudio load the ucm successfully and we 
could see
  the sound card is generated and all output and input devices are listed
  under sound card, but the init output is muted and the volume is very low
  if we manually unumte it. Now install the updated alsa-ucm-conf, rm 
~/.config/pulse/*; sudo rm -rf
  /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is
  not muted anymore and the output volume is OK to most users.

  [Regression Risk]
  This could make the machines with sof audio driver fail to load ucm
  , then all audio function can't work as before, like the speaker can't
  output sound or the internal mic can't be found or can't record sound.
  But this possibility is very low, I tested this SRU on some machines with or
  without sof audio driver, all worked as well as before.

  
  After logging in, only a dummy device is available for audio playback 
(resulting in no audible playback). When running "pactl load-module 
module-detect" the sound card shows up, and playback works as expected.

  If pulseaudio is restarted with "pulseaudio -k" the playback device
  disappears again. Running the above command get things working again.

  If I change the following section in /etc/pulse/default.pa from:

  ### Automatically load driver modules depending on the hardware available
  .ifexists module-udev-detect.so
  load-module module-udev-detect
  .else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  .endif

  To:

  ### Automatically load driver modules depending on the hardware available
  #.ifexists module-udev-detect.so
  #load-module module-udev-detect
  #.else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  #.endif

  Things start working as they should after running "pul

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

[Timo Aaltonen]

Hello Johan, or anyone else affected,

Accepted alsa-ucm-conf into groovy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.2-1ubuntu5.1 in a few hours, and then in the -proposed
repository.

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

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

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

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

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

Title:
  [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup

Status in PulseAudio:
  Unknown
Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in alsa-lib source package in Groovy:
  Fix Committed
Status in alsa-ucm-conf source package in Groovy:
  Fix Committed
Status in alsa-lib source package in Hirsute:
  Fix Committed
Status in alsa-ucm-conf source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  On the machines with AMD Ryzen acp audio design, the audio can't work
  anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1(
  focal), this is a regression on libasound2 for those machines. the AMD
  Ryzen acp audio card needs to load ucm to work with pulseaudio, but
  this audio card doesn't have an independant ucm for it, it needs to
  link to an existing HDA-Intel ucm, the check_empty_configuration() needs
  to cover the situation that Linked is true, otherwise it will fail
  to load the ucm for the audio card. Even the audio card could load the
  ucm, the output is muted and the init output volume is too low if
  freshly install the OS on these machines.

  [Fix]
  Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD
  Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix
  init mute and init output volume problem.

  [Test Case]
  Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf
  /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd
  list-cards, we could see the pulseaudio load the ucm successfully and we 
could see
  the sound card is generated and all output and input devices are listed
  under sound card, but the init output is muted and the volume is very low
  if we manually unumte it. Now install the updated alsa-ucm-conf, rm 
~/.config/pulse/*; sudo rm -rf
  /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is
  not muted anymore and the output volume is OK to most users.

  [Regression Risk]
  This could make the machines with sof audio driver fail to load ucm
  , then all audio function can't work as before, like the speaker can't
  output sound or the internal mic can't be found or can't record sound.
  But this possibility is very low, I tested this SRU on some machines with or
  without sof audio driver, all worked as well as before.

  
  After logging in, only a dummy device is available for audio playback 
(resulting in no audible playback). When running "pactl load-module 
module-detect" the sound card shows up, and playback works as expected.

  If pulseaudio is restarted with "pulseaudio -k" the playback device
  disappears again. Running the above command get things working again.

  If I change the following section in /etc/pulse/default.pa from:

  ### Automatically load driver modules depending on the hardware available
  .ifexists module-udev-detect.so
  load-module module-udev-detect
  .else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  .endif

  To:

  ### Automatically load driver modules depending on the hardware available
  #.ifexists module-udev-detect.so
  #load-module module-udev-detect
  #.else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  #.endif

  Things start working as they should after running 

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

[Timo Aaltonen]

Hello Johan, or anyone else affected,

Accepted alsa-lib into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/alsa-
lib/1.2.2-2.1ubuntu2.2 in a few hours, and then in the -proposed
repository.

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

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

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

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

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

Title:
  [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup

Status in PulseAudio:
  Unknown
Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in alsa-lib source package in Groovy:
  Fix Committed
Status in alsa-ucm-conf source package in Groovy:
  Fix Committed
Status in alsa-lib source package in Hirsute:
  Fix Committed
Status in alsa-ucm-conf source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  On the machines with AMD Ryzen acp audio design, the audio can't work
  anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1(
  focal), this is a regression on libasound2 for those machines. the AMD
  Ryzen acp audio card needs to load ucm to work with pulseaudio, but
  this audio card doesn't have an independant ucm for it, it needs to
  link to an existing HDA-Intel ucm, the check_empty_configuration() needs
  to cover the situation that Linked is true, otherwise it will fail
  to load the ucm for the audio card. Even the audio card could load the
  ucm, the output is muted and the init output volume is too low if
  freshly install the OS on these machines.

  [Fix]
  Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD
  Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix
  init mute and init output volume problem.

  [Test Case]
  Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf
  /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd
  list-cards, we could see the pulseaudio load the ucm successfully and we 
could see
  the sound card is generated and all output and input devices are listed
  under sound card, but the init output is muted and the volume is very low
  if we manually unumte it. Now install the updated alsa-ucm-conf, rm 
~/.config/pulse/*; sudo rm -rf
  /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is
  not muted anymore and the output volume is OK to most users.

  [Regression Risk]
  This could make the machines with sof audio driver fail to load ucm
  , then all audio function can't work as before, like the speaker can't
  output sound or the internal mic can't be found or can't record sound.
  But this possibility is very low, I tested this SRU on some machines with or
  without sof audio driver, all worked as well as before.

  
  After logging in, only a dummy device is available for audio playback 
(resulting in no audible playback). When running "pactl load-module 
module-detect" the sound card shows up, and playback works as expected.

  If pulseaudio is restarted with "pulseaudio -k" the playback device
  disappears again. Running the above command get things working again.

  If I change the following section in /etc/pulse/default.pa from:

  ### Automatically load driver modules depending on the hardware available
  .ifexists module-udev-detect.so
  load-module module-udev-detect
  .else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  .endif

  To:

  ### Automatically load driver modules depending on the hardware available
  #.ifexists module-udev-detect.so
  #load-module module-udev-detect
  #.else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  #.endif

  Things start working as they should after running "pulseaudio 

[Kernel-packages] [Bug 1901922] Re: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup

[Timo Aaltonen]

Hello Johan, or anyone else affected,

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

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

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

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

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

** Tags added: verification-needed verification-needed-groovy

** Tags added: verification-needed-focal

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

Title:
  [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup

Status in PulseAudio:
  Unknown
Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in alsa-lib source package in Groovy:
  Fix Committed
Status in alsa-ucm-conf source package in Groovy:
  Fix Committed
Status in alsa-lib source package in Hirsute:
  Fix Committed
Status in alsa-ucm-conf source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  On the machines with AMD Ryzen acp audio design, the audio can't work
  anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1(
  focal), this is a regression on libasound2 for those machines. the AMD
  Ryzen acp audio card needs to load ucm to work with pulseaudio, but
  this audio card doesn't have an independant ucm for it, it needs to
  link to an existing HDA-Intel ucm, the check_empty_configuration() needs
  to cover the situation that Linked is true, otherwise it will fail
  to load the ucm for the audio card. Even the audio card could load the
  ucm, the output is muted and the init output volume is too low if
  freshly install the OS on these machines.

  [Fix]
  Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD
  Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix
  init mute and init output volume problem.

  [Test Case]
  Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf
  /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd
  list-cards, we could see the pulseaudio load the ucm successfully and we 
could see
  the sound card is generated and all output and input devices are listed
  under sound card, but the init output is muted and the volume is very low
  if we manually unumte it. Now install the updated alsa-ucm-conf, rm 
~/.config/pulse/*; sudo rm -rf
  /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is
  not muted anymore and the output volume is OK to most users.

  [Regression Risk]
  This could make the machines with sof audio driver fail to load ucm
  , then all audio function can't work as before, like the speaker can't
  output sound or the internal mic can't be found or can't record sound.
  But this possibility is very low, I tested this SRU on some machines with or
  without sof audio driver, all worked as well as before.

  
  After logging in, only a dummy device is available for audio playback 
(resulting in no audible playback). When running "pactl load-module 
module-detect" the sound card shows up, and playback works as expected.

  If pulseaudio is restarted with "pulseaudio -k" the playback device
  disappears again. Running the above command get things working again.

  If I change the following section in /etc/pulse/default.pa from:

  ### Automatically load driver modules depending on the hardware available
  .ifexists module-udev-detect.so
  load-module module-udev-detect
  .else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  .endif

  To:

  ### Automatically load driver modules depending on the hardware available
  #.ifexists module-udev-detect.so
  #load-module module-udev-detect
  #.else
  ### Use the static hardware detection module (for systems that lack udev 
sup

[Kernel-packages] [Bug 1899993] Re: EFI: Fails when BootCurrent entry does not exist

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  EFI: Fails when BootCurrent entry does not exist

Status in curtin package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  In Progress
Status in curtin source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in curtin source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in curtin source package in Focal:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in curtin source package in Groovy:
  Invalid
Status in linux source package in Groovy:
  Fix Committed
Status in curtin source package in Hirsute:
  Invalid
Status in linux source package in Hirsute:
  In Progress

Bug description:
  [Impact]
  MAAS installs fail on systems that have EFI Variables that include a "/" in 
the name.

  Split out of bug 1894217.

  [Test Case]
  $ ls /sys/firmware/efi/efivars | grep ^Boot
  ls: reading directory '/sys/firmware/efi/efivars': Input/output error
  Boot mode select-7683c190-9523-4402-81ff-a11e93dc389c
  Boot-8be4df61-93ca-11d2-aa0d-00e098032b8c
  BootCurrent-8be4df61-93ca-11d2-aa0d-00e098032b8c
  BootOptionSupport-8be4df61-93ca-11d2-aa0d-00e098032b8c
  BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c

  The Input/output error is the key symptom. See below to see how that
  percolates up to MAAS install failures.

  [Regression Risk]
  There's a very tiny chance that someone has written code that depends on an 
the -EIO error for some reason. It's hard to guess why such a script would do 
that.

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

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

[Kernel-packages] [Bug 1898903] Re: *-tools-common packages descriptions have typo "PGKVER"

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  *-tools-common packages descriptions have typo "PGKVER"

Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.4 package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in linux-hwe-5.4 source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-hwe-5.4 source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux-hwe-5.4 source package in Focal:
  Invalid
Status in linux source package in Groovy:
  Fix Released
Status in linux-hwe-5.4 source package in Groovy:
  Invalid

Bug description:
  $ apt show linux-tools-common
  Description: Linux kernel version specific tools for version 4.15.0
   This package provides the architecture independent parts for kernel
   version locked tools (such as perf and x86_energy_perf_policy) for
   version PGKVER.
   ^^

  Seems to be true for all versions/flavors.

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

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

[Kernel-packages] [Bug 1903293] Re: Avoid double newline when running insertchanges

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  Avoid double newline when running insertchanges

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  In Progress

Bug description:
  [Impact]
  When preparing derivative kernels and inserting master kernel changes, if the 
derivative has not changes on its own, we end up with two empty lines, which is 
caught up by verify-release-ready.

  [Test case]
  Run cranky-close with derivative changes and no derivative changes.

  [Regression Potential]
  We could break changelogs, or the kernel preparation altogether.

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

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

[Kernel-packages] [Bug 1902957] Re: Update kernel packaging to support forward porting kernels

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  Update kernel packaging to support forward porting kernels

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  In Progress

Bug description:
  SRU Justification

  Impact: Our kernel packaging currently has support for backporting
  kernels to older releases. This includes appending ~BACKPORT_SUFFIX to
  the version string for the backport kernel, where BACKPORT_SUFFIX is
  defined in update.conf. We need to start doing similar forward ported
  kernels, but BACKPORT_SUFFIX should be appended using a + rather than
  a ~. Our kernel packaging cannot easily determine whether a + or a ~
  is appropriate.

  Fix: Move the leading character into BACKPORT_SUFFIX, and do not
  insert any leading characters from the kernel packaging scripts. Since
  the script which generates update.conf has access to information from
  kernel-series, it can more easily determine whether + or ~ is the
  appropriate leader.

  Test Case: Run through the normal steps for updating a backport
  kernel. The version string generated should have ~SERIES for a
  backport to an older series, and +SERIES for a backport to a newer
  series.

  Regression Potential: Backport kernels could end up with an incorrect
  version strings. Since all kernel uploads undergo review, any such
  errors should be caught before uploading.

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

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

[Kernel-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400

[Iain Lane]

The point for me is that we should be trying to avoid taking on
indefinite technical debt (patches that have to be rebased forever).
It's "fine" to include them ahead of any upstream schedule if we need to
for hardware enablement, but we do need to have plans to make this be a
non permanent situation. That's what Seb is asking for, and I'm totally
on board with that.

btw, I don't think it's fair to characterise code review as pedantry

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

Title:
  [SRU] Bluetooth won't activate on the pi 400

Status in bluez package in Ubuntu:
  Triaged
Status in bluez source package in Hirsute:
  Triaged

Bug description:
  [Impact]

  Without these patches, Bluetooth is inoperable on the recently
  released Raspberry Pi 400.

  [Test Case]

  * Boot the Ubuntu Desktop for Pi image on a Pi 400.
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is not enabled and attempting to activate it fails
  * sudo add-apt-repository ppa:waveform/pi-bluetooth
  * sudo apt update
  * sudo apt install bluez
  * sudo reboot
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, 
mobile phones, headphones, etc.) can connect and operate correctly 

  [Regression Potential]

  Extremely low (on groovy in particular, this has the same version of
  bluez as hirsute). The only significant risk is to non-Pi platforms or
  dongles which also use the Broadcom 43xx (or Cypress 305) chips for
  Bluetooth which might be inadvertently affected by these patches.

  [Original Description]

  The new Pi 400 has a slightly different Wifi/BT chip to the Pi4.
  Whilst wifi works happily, Bluetooth fails to operate. This doesn't
  appear to be an issue with either the firmware (the latest versions
  from upstream Raspbian have been tried), or the kernel (a known-good
  raspi kernel has been tested under Ubuntu), but with Bluez itself.
  Specifically, tracing the initialization with btmon on Raspbian and
  Ubuntu, the stack consistently fails when attempting to "Set Default
  PHY" on the latter. Curiously, under Ubuntu the adapter also appears
  to lack a MAC address.

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

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

[Kernel-packages] [Bug 1899802] Re: [Ubuntu 21.04 FEAT] mpt3sas: Request to include the patch set which supports topology where zoning is enabled in expander

[Jeff Lane]

** Also affects: linux (Ubuntu Hirsute)
   Importance: Undecided
   Status: Opinion

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

** Also affects: linux (Ubuntu Groovy)
   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/1899802

Title:
  [Ubuntu 21.04 FEAT] mpt3sas: Request to include the patch set which
  supports topology where zoning is enabled in expander

Status in linux package in Ubuntu:
  Opinion
Status in linux source package in Focal:
  New
Status in linux source package in Groovy:
  New
Status in linux source package in Hirsute:
  Opinion

Bug description:
  Request to include patch set "PATCH 00/14] mpt3sas: Add support for
  multi-port path topology" which will support the topologies where
  zoning is enabled in the expander as shown below,

  Zone 1 Zone 2
   |-|   ||
   |  HD1 . HD25 |   | HD26 ..HD50|
   | |==| |
   | |   |   |  | |
   | |  Expander| |
   | |==| |
   |   | |   ||   |
   |---|-|   ||---|
 x8|  |x8 
___|__|___
|HBA |
||
   
  Current driver doesn't support this type of topology and will add only one 
zoned drives to the OS. So to support these types of topology we need below 
patch set in the driver.
  https://marc.info/?l=linux-scsi&m=160226366707807&w=2

  So, requesting you include this patch for next upcoming Ubuntu kernel
  release.

  Currently we have posted this patch set to upstream community and they
  yet to review this patch set. Meanwhile If I get the base kernel
  source code for next upcoming Ubuntu kernel then I can prepare the
  patches over this base kernel source and share it in this BZ.

  Thanks,
  Sreekanth

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

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

[Kernel-packages] [Bug 1852493] Re: Freeze on suspend (Acer SF314-57)

[Norbert Lanzenberger]

What I forgot to add, with Windows the notebook sometimes does not want
to go to sleep. It turns the screen off, but stays running in idle
(keyboard light is on, fan is slightly audible). It did this right after
I installed Windows and all necessary drivers, but before I even
installed a single program.

 Even now, it happens about every other time I want to suspend the
notebook. Maybe there's something wrong with the chipset of this model.
Acer support was not able to help me.

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

Title:
  Freeze on suspend (Acer SF314-57)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I freshly installed Ubuntu Budgie 19.10 today after receiving my new
  notebook. However, when putting the system to suspend (or hibernate),
  the screen goes off and the system freezes. The fan keeps running,
  keyboard backlight and power led are on. Sometimes, when pressing a
  button, I can get the screen to turn back on, but its frozen as well
  (no mouse movement, clock stuck etc.)

  So far I tried increasing the swap file size, however this did not
  help. I also livebooted Ubuntu 19.10 and tried suspend, but I had the
  same issue.

  Could this be a problem of my fairly new chipset (Intel i7 1065G7)?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  norbert1508 F pulseaudio
   /dev/snd/pcmC0D0p:   norbert1508 F...m pulseaudio
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-13 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  MachineType: Acer Swift SF314-57
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic 
root=/dev/mapper/vgubuntu--budgie-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-23-generic N/A
   linux-backports-modules-5.3.0-23-generic  N/A
   linux-firmware1.183.2
  Tags:  eoan
  Uname: Linux 5.3.0-23-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: 09/05/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Floris_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.07
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.07:bd09/05/2019:svnAcer:pnSwiftSF314-57:pvrV1.07:rvnIL:rnFloris_IL:rvrV1.07:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-57
  dmi.product.sku: 
  dmi.product.version: V1.07
  dmi.sys.vendor: Acer

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Lenovo-V14-IIL: Touchpad not found under (K)ubuntu 20.04.1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello all together!

  In a new Lenovo V14-IIL i found after installing (K)ubuntu 20.04.1 and
  apt-get update && apt-get upgrade, that a

  cat /proc/bus/input/devices

  does not schow any touchpad. Therefore i followed the recommondations
  in 
  https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo

  See here my output from cat /proc/bus/input/devices

  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
  U: Uniq=
  H: Handlers=event0 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=PNP0C0C/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

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

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input4
  U: Uniq=
  H: Handlers=kbd event4 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0003 Vendor=050d Product=3201 Version=0110
  N: Name="Belkin Corporation Flip CC"
  P: Phys=usb-:00:14.0-9.2/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-9/1-9.2/1-9.2:1.0/0003:050D:3201.0001/input/input5
  U: Uniq=
  H: Handlers=kbd event5 leds 
  B: PROP=0
  B: EV=20013
  B: KEY=2 e 0
  B: MSC=10
  B: LED=80

  I: Bus=0003 Vendor=045e Product=0745 Version=0111
  N: Name="Microsoft Microsoft® 2.4GHz Transceiver v8.0"
  P: Phys=usb-:00:14.0-9.3/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-9/1-9.3/1-9.3:1.0/0003:045E:0745.0002/input/input6
  U: Uniq=
  H: Handlers=sysrq kbd event6 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=10007 ff8007ff febeffdff3cf fffe
  B: MSC=10
  B: LED=7

  I: Bus=0003 Vendor=045e Product=0745 Version=0111
  N: Name="Microsoft Microsoft® 2.4GHz Transceiver v8.0 Mouse"
  P: Phys=usb-:00:14.0-9.3/input1
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-9/1-9.3/1-9.3:1.1/0003:045E:0745.0003/input/input7
  U: Uniq=
  H: Handlers=mouse0 event7 
  B: PROP=0
  B: EV=17
  B: KEY=1f 0 0 0 0
  B: REL=1943
  B: MSC=10

  I: Bus=0003 Vendor=045e Product=0745 Version=0111
  N: Name="Microsoft Microsoft® 2.4GHz Transceiver v8.0 Consumer Control"
  P: Phys=usb-:00:14.0-9.3/input1
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-9/1-9.3/1-9.3:1.1/0003:045E:0745.0003/input/input8
  U: Uniq=
  H: Handlers=kbd event8 
  B: PROP=0
  B: EV=1f
  B: KEY=3f000301ff 0 0 48317aff32d bfd6 1 130ff38b17c000 
677bfad9415fed 19ed6804400 1002
  B: REL=1040
  B: ABS=1
  B: MSC=10

  I: Bus=0003 Vendor=045e Product=0745 Version=0111
  N: Name="Microsoft Microsoft® 2.4GHz Transceiver v8.0 Consumer Control"
  P: Phys=usb-:00:14.0-9.3/input2
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-9/1-9.3/1-9.3:1.2/0003:045E:0745.0004/input/input9
  U: Uniq=
  H: Handlers=sysrq kbd event9 
  B: PROP=0
  B: EV=10001f
  B: KEY=3f000301ff 0 0 48317aff32d bfd6 1 130ff38b17c007 
7bfad9415fff ffbeffdfffef fffe
  B: REL=1040
  B: ABS=1
  B: MSC=10

  I: Bus=0003 Vendor=045e Product=0745 Version=0111
  N: Name="Microsoft Microsoft® 2.4GHz Transceiver v8.0 System Control"
  P: Phys=usb-:00:14.0-9.3/input2
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-9/1-9.3/1-9.3:1.2/0003:045E:0745.0004/input/input11
  U: Uniq=
  H: Handlers=kbd event10 
  B: PROP=0
  B: EV=1b
  B: KEY=400100 12 0 8 4010cc00 101680 0
  B: ABS=100
  B: MSC=10

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Ideapad extra buttons"
  P: Phys=ideapad/input0
  S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input12
  U: Uniq=
  H: Handlers=rfkill kbd event11 
  B: PROP=0
  B: EV=13
  B: 

[Kernel-packages] [Bug 1904229] [NEW] Lenovo-V14-IIL: Touchpad not found under (K)ubuntu 20.04.1

[Karl Testano]

Public bug reported:

Hello all together!

In a new Lenovo V14-IIL i found after installing (K)ubuntu 20.04.1 and
apt-get update && apt-get upgrade, that a

cat /proc/bus/input/devices

does not schow any touchpad. Therefore i followed the recommondations
in 
https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo

See here my output from cat /proc/bus/input/devices

I: Bus=0019 Vendor= Product=0005 Version=
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
U: Uniq=
H: Handlers=event0 
B: PROP=0
B: EV=21
B: SW=1

I: Bus=0019 Vendor= Product=0001 Version=
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
U: Uniq=
H: Handlers=kbd event1 
B: PROP=0
B: EV=3
B: KEY=10 0

I: Bus=0019 Vendor= Product=0001 Version=
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
U: Uniq=
H: Handlers=kbd event2 
B: PROP=0
B: EV=3
B: KEY=10 0

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

I: Bus=0019 Vendor= Product=0006 Version=
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input4
U: Uniq=
H: Handlers=kbd event4 
B: PROP=0
B: EV=3
B: KEY=3e000b 0 0 0

I: Bus=0003 Vendor=050d Product=3201 Version=0110
N: Name="Belkin Corporation Flip CC"
P: Phys=usb-:00:14.0-9.2/input0
S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-9/1-9.2/1-9.2:1.0/0003:050D:3201.0001/input/input5
U: Uniq=
H: Handlers=kbd event5 leds 
B: PROP=0
B: EV=20013
B: KEY=2 e 0
B: MSC=10
B: LED=80

I: Bus=0003 Vendor=045e Product=0745 Version=0111
N: Name="Microsoft Microsoft® 2.4GHz Transceiver v8.0"
P: Phys=usb-:00:14.0-9.3/input0
S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-9/1-9.3/1-9.3:1.0/0003:045E:0745.0002/input/input6
U: Uniq=
H: Handlers=sysrq kbd event6 leds 
B: PROP=0
B: EV=120013
B: KEY=10007 ff8007ff febeffdff3cf fffe
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=045e Product=0745 Version=0111
N: Name="Microsoft Microsoft® 2.4GHz Transceiver v8.0 Mouse"
P: Phys=usb-:00:14.0-9.3/input1
S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-9/1-9.3/1-9.3:1.1/0003:045E:0745.0003/input/input7
U: Uniq=
H: Handlers=mouse0 event7 
B: PROP=0
B: EV=17
B: KEY=1f 0 0 0 0
B: REL=1943
B: MSC=10

I: Bus=0003 Vendor=045e Product=0745 Version=0111
N: Name="Microsoft Microsoft® 2.4GHz Transceiver v8.0 Consumer Control"
P: Phys=usb-:00:14.0-9.3/input1
S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-9/1-9.3/1-9.3:1.1/0003:045E:0745.0003/input/input8
U: Uniq=
H: Handlers=kbd event8 
B: PROP=0
B: EV=1f
B: KEY=3f000301ff 0 0 48317aff32d bfd6 1 130ff38b17c000 
677bfad9415fed 19ed6804400 1002
B: REL=1040
B: ABS=1
B: MSC=10

I: Bus=0003 Vendor=045e Product=0745 Version=0111
N: Name="Microsoft Microsoft® 2.4GHz Transceiver v8.0 Consumer Control"
P: Phys=usb-:00:14.0-9.3/input2
S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-9/1-9.3/1-9.3:1.2/0003:045E:0745.0004/input/input9
U: Uniq=
H: Handlers=sysrq kbd event9 
B: PROP=0
B: EV=10001f
B: KEY=3f000301ff 0 0 48317aff32d bfd6 1 130ff38b17c007 
7bfad9415fff ffbeffdfffef fffe
B: REL=1040
B: ABS=1
B: MSC=10

I: Bus=0003 Vendor=045e Product=0745 Version=0111
N: Name="Microsoft Microsoft® 2.4GHz Transceiver v8.0 System Control"
P: Phys=usb-:00:14.0-9.3/input2
S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-9/1-9.3/1-9.3:1.2/0003:045E:0745.0004/input/input11
U: Uniq=
H: Handlers=kbd event10 
B: PROP=0
B: EV=1b
B: KEY=400100 12 0 8 4010cc00 101680 0
B: ABS=100
B: MSC=10

I: Bus=0019 Vendor= Product= Version=
N: Name="Ideapad extra buttons"
P: Phys=ideapad/input0
S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input12
U: Uniq=
H: Handlers=rfkill kbd event11 
B: PROP=0
B: EV=13
B: KEY=81000800100c03 4430 0 2
B: MSC=10

I: Bus=0003 Vendor=174f Product=1176 Version=0028
N: Name="Integrated Camera: Integrated C"
P: Phys=usb-:00:14.0-5/button
S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/input/input13
U: Uniq=
H: Handlers=kbd event12 
B: PROP=0
B: EV=3
B: KEY=10 0 0 0

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input14
U: Uniq=
H: Handlers=event13 
B: PROP=0
B: EV=21
B: SW=10

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH Headphone"
P: Phys=ALSA
S: S

[Kernel-packages] [Bug 1852493] Re: Freeze on suspend (Acer SF314-57)

[Norbert Lanzenberger]

As said before, after switching to deep suspend it was working.

Due too homeschooling, I unfortunately had to install Windows on my
machine :( , so I can't give you an update how it's working with 20.10.

I did have Ubuntu 20.04 installed, but it did not bring any improvements
to the issue. As soon as I can become a full time Linux user again, imma
install Ubuntu and update you guys.

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

Title:
  Freeze on suspend (Acer SF314-57)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I freshly installed Ubuntu Budgie 19.10 today after receiving my new
  notebook. However, when putting the system to suspend (or hibernate),
  the screen goes off and the system freezes. The fan keeps running,
  keyboard backlight and power led are on. Sometimes, when pressing a
  button, I can get the screen to turn back on, but its frozen as well
  (no mouse movement, clock stuck etc.)

  So far I tried increasing the swap file size, however this did not
  help. I also livebooted Ubuntu 19.10 and tried suspend, but I had the
  same issue.

  Could this be a problem of my fairly new chipset (Intel i7 1065G7)?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  norbert1508 F pulseaudio
   /dev/snd/pcmC0D0p:   norbert1508 F...m pulseaudio
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-13 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  MachineType: Acer Swift SF314-57
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic 
root=/dev/mapper/vgubuntu--budgie-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-23-generic N/A
   linux-backports-modules-5.3.0-23-generic  N/A
   linux-firmware1.183.2
  Tags:  eoan
  Uname: Linux 5.3.0-23-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: 09/05/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Floris_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.07
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.07:bd09/05/2019:svnAcer:pnSwiftSF314-57:pvrV1.07:rvnIL:rnFloris_IL:rvrV1.07:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-57
  dmi.product.sku: 
  dmi.product.version: V1.07
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1904225] Re: Use ACPI S5 for reboot

[Kai-Heng Feng]

** Tags added: oem-priority originate-from-1901983 stella

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

Title:
  Use ACPI S5 for reboot

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in linux-oem-5.6 source package in Focal:
  Confirmed
Status in linux source package in Groovy:
  Confirmed
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  [Impact]
  On some HP laptops, BIOS hotkeys don't work right after reboot, becuase
  OS doesn't call _PTS to indicate ACPI it's rebooting.

  [Fix]
  Follow Windows and use S5 for reboot.

  [Test case]
  Reboot and see if hotkeys like F10/F11 can trigger BIOS functions.
  Hotkeys work great with the patch applied. 

  [Where problems could occur]
  If there are platforms don't expect S5 for reboot then there could be
  unexpected result.
  However Windows uses S5 so that's rather unlikely.

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

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

[Kernel-packages] [Bug 1902093] Re: Introduce the new NVIDIA 455 series

[Lau]

> Is there a build for Focal that could already be tested? I can only
find one for Groovy.

I see it in recommended now. Thanks to everyone who worked on this!

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

Title:
  Introduce the new NVIDIA 455 series

Status in linux package in Ubuntu:
  Confirmed
Status in linux-restricted-modules package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux-restricted-modules source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-455 source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-455 source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed
Status in linux-restricted-modules source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-455 source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

    * New upstream release:
  - Added support for the following GPUs:
  GeForce RTX 3070
  - Added support for using an NVIDIA-driven display as a PRIME
    Display Offload sink with a PRIME Display Offload source driven
    by the xf86-video-intel driver.
  - Fixed a bug in a Vulkan barrier optimization that allowed some
    back-to-back copies to run unordered.
  - Fixed a performance regression in the NVIDIA X driver which
    affected some X11 RENDER extension use cases.
  - Added AMD Secure Memory Encryption compatibility.
    * debian/templates/control.in:
  - Set support level to NFB instead of Beta.
  - Add support for CUDA 11.

  Note: this will be the initial release for Bionic and Focal.

  
  Changelog entries for the linux-restricted-modules:

  UBUNTU: [Packaging] NVIDIA -- provide the nvidia-prebuilt-kernel
  virtual package

  Make all the NVIDIA drivers, except for 390, provide the 
nvidia-prebuilt-kernel
  virtual package.

  This allows adding a generic dependency on the signed modules.

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

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

[Kernel-packages] [Bug 1852493] Re: Freeze on suspend (Acer SF314-57)

[Adams Jensen]

Any updates or progress on this issue?

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

Title:
  Freeze on suspend (Acer SF314-57)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I freshly installed Ubuntu Budgie 19.10 today after receiving my new
  notebook. However, when putting the system to suspend (or hibernate),
  the screen goes off and the system freezes. The fan keeps running,
  keyboard backlight and power led are on. Sometimes, when pressing a
  button, I can get the screen to turn back on, but its frozen as well
  (no mouse movement, clock stuck etc.)

  So far I tried increasing the swap file size, however this did not
  help. I also livebooted Ubuntu 19.10 and tried suspend, but I had the
  same issue.

  Could this be a problem of my fairly new chipset (Intel i7 1065G7)?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  norbert1508 F pulseaudio
   /dev/snd/pcmC0D0p:   norbert1508 F...m pulseaudio
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-13 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  MachineType: Acer Swift SF314-57
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic 
root=/dev/mapper/vgubuntu--budgie-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-23-generic N/A
   linux-backports-modules-5.3.0-23-generic  N/A
   linux-firmware1.183.2
  Tags:  eoan
  Uname: Linux 5.3.0-23-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: 09/05/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Floris_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.07
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.07:bd09/05/2019:svnAcer:pnSwiftSF314-57:pvrV1.07:rvnIL:rnFloris_IL:rvrV1.07:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-57
  dmi.product.sku: 
  dmi.product.version: V1.07
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1904225] Re: Use ACPI S5 for reboot

[Kai-Heng Feng]

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

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

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

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

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

Title:
  Use ACPI S5 for reboot

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in linux-oem-5.6 source package in Focal:
  Confirmed
Status in linux source package in Groovy:
  Confirmed
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  [Impact]
  On some HP laptops, BIOS hotkeys don't work right after reboot, becuase
  OS doesn't call _PTS to indicate ACPI it's rebooting.

  [Fix]
  Follow Windows and use S5 for reboot.

  [Test case]
  Reboot and see if hotkeys like F10/F11 can trigger BIOS functions.
  Hotkeys work great with the patch applied. 

  [Where problems could occur]
  If there are platforms don't expect S5 for reboot then there could be
  unexpected result.
  However Windows uses S5 so that's rather unlikely.

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

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

[Kernel-packages] [Bug 1904225] [NEW] Use ACPI S5 for reboot

[Kai-Heng Feng]

Public bug reported:

[Impact]
On some HP laptops, BIOS hotkeys don't work right after reboot, becuase
OS doesn't call _PTS to indicate ACPI it's rebooting.

[Fix]
Follow Windows and use S5 for reboot.

[Test case]
Reboot and see if hotkeys like F10/F11 can trigger BIOS functions.
Hotkeys work great with the patch applied. 

[Where problems could occur]
If there are platforms don't expect S5 for reboot then there could be
unexpected result.
However Windows uses S5 so that's rather unlikely.

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

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

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

** Affects: linux-oem-5.6 (Ubuntu Focal)
 Importance: Undecided
 Status: Confirmed

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

** Affects: linux-oem-5.6 (Ubuntu Groovy)
 Importance: Undecided
 Status: Invalid

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

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

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

** Changed in: linux-oem-5.6 (Ubuntu Groovy)
   Status: New => Invalid

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

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

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

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

** Changed in: linux-oem-5.6 (Ubuntu Focal)
   Status: New => Confirmed

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

Title:
  Use ACPI S5 for reboot

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in linux-oem-5.6 source package in Focal:
  Confirmed
Status in linux source package in Groovy:
  Confirmed
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  [Impact]
  On some HP laptops, BIOS hotkeys don't work right after reboot, becuase
  OS doesn't call _PTS to indicate ACPI it's rebooting.

  [Fix]
  Follow Windows and use S5 for reboot.

  [Test case]
  Reboot and see if hotkeys like F10/F11 can trigger BIOS functions.
  Hotkeys work great with the patch applied. 

  [Where problems could occur]
  If there are platforms don't expect S5 for reboot then there could be
  unexpected result.
  However Windows uses S5 so that's rather unlikely.

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

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

[Kernel-packages] [Bug 1903200] Re: Ubuntu is unable to detect one of my GPUs

[Kai-Heng Feng]

Can you please attach output of `prime-select query`?

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

Title:
  Ubuntu is unable to detect one of my GPUs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an MSI laptop which was working fine with Ubuntu 18, but I
  decided to upgrade. It has one of these dual graphics setups, which
  and Intel HD 630 and a NVIDIA GTX 1060 6GB. On Ubuntu 18, I simply get
  the NVIDIA GPU to work by selecting its drivers on the "Additional
  Drivers" tab under "Software and Updates", but on this version of
  Ubuntu, my GPU doesn't appear there any more.

  Also, if I type this in the console: $ lspci | grep -i --color
  'vga\|3d\|2d'

  This is the only line I get: 00:02.0 VGA compatible controller: Intel
  Corporation HD Graphics 630 (rev 04)

  Just in case, my laptop model is this: https://es.msi.com/Laptop
  /GL72VR-7RFX

  I also have Windows on dual boot and the GPU works perfectly fine
  there. Also, it is not disabled on the BIOS or something like that. I
  don't think that is even possible on my BIOS either.

  $ lspci -k | grep -EA3 'VGA|3D|Display'

  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
DeviceName:  Onboard IGD
Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 630
Kernel driver in use: i915

  
  $ lspci

  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 05)
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core 
Processor PCIe Controller (x16) (rev 05)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
  00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset 
Family USB 3.0 xHCI Controller (rev 31)
  00:14.2 Signal processing controller: Intel Corporation 100 Series/C230 
Series Chipset Family Thermal Subsystem (rev 31)
  00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series 
Chipset Family MEI Controller #1 (rev 31)
  00:17.0 SATA controller: Intel Corporation HM170/QM170 Chipset SATA 
Controller [AHCI Mode] (rev 31)
  00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family 
PCI Express Root Port #1 (rev f1)
  00:1c.3 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family 
PCI Express Root Port #4 (rev f1)
  00:1c.4 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family 
PCI Express Root Port #5 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation HM175 Chipset LPC/eSPI Controller (rev 
31)
  00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset 
Family Power Management Controller (rev 31)
  00:1f.3 Audio device: Intel Corporation CM238 HD Audio Controller (rev 31)
  00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus 
(rev 31)
  02:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3168NGW 
[Stone Peak] (rev 10)
  03:00.0 Ethernet controller: Qualcomm Atheros Killer E2400 Gigabit Ethernet 
Controller (rev 10)
  04:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host 
Controller

  
  Looking at the output, I don't know why it says that my processor is an Intel 
Xeon... it's actually a i7-7700HQ.

  Here is a thread on the forum with more people experiencing this issue:
  https://ubuntuforums.org/showthread.php?t=2443007

  Any help would be appreciated.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  5 20:18:37 2020
  DistUpgraded: 2020-05-08 15:27:01,107 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso 
hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 450.80.02, 5.4.0-51-generic, x86_64: installed
   nvidia, 450.80.02, 5.4.0-52-generic, x86_64: installed
   virtualbox, 6.1.10, 5.4.0-51-generic, x86_64: installed
   virtualbox, 6.1.10, 5.4.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 630 
[1462:11d7]
  InstallationDate: Installed on 2018-10-02 (765 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Micro-Star Inte

[Kernel-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400

[David Krauser]

@tmolloy, thank you for circling back around. I'm glad the patches worked for 
you :-)
Note that there are other (unrelated) packages in @waveform's PPA that may get 
installed with an apt upgrade. I don't know what the state of those packages 
are. I disabled the PPA after installing bluez, just to be sure I didn't 
unintentionally install the other packages.

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

Title:
  [SRU] Bluetooth won't activate on the pi 400

Status in bluez package in Ubuntu:
  Triaged
Status in bluez source package in Hirsute:
  Triaged

Bug description:
  [Impact]

  Without these patches, Bluetooth is inoperable on the recently
  released Raspberry Pi 400.

  [Test Case]

  * Boot the Ubuntu Desktop for Pi image on a Pi 400.
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is not enabled and attempting to activate it fails
  * sudo add-apt-repository ppa:waveform/pi-bluetooth
  * sudo apt update
  * sudo apt install bluez
  * sudo reboot
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, 
mobile phones, headphones, etc.) can connect and operate correctly 

  [Regression Potential]

  Extremely low (on groovy in particular, this has the same version of
  bluez as hirsute). The only significant risk is to non-Pi platforms or
  dongles which also use the Broadcom 43xx (or Cypress 305) chips for
  Bluetooth which might be inadvertently affected by these patches.

  [Original Description]

  The new Pi 400 has a slightly different Wifi/BT chip to the Pi4.
  Whilst wifi works happily, Bluetooth fails to operate. This doesn't
  appear to be an issue with either the firmware (the latest versions
  from upstream Raspbian have been tried), or the kernel (a known-good
  raspi kernel has been tested under Ubuntu), but with Bluez itself.
  Specifically, tracing the initialization with btmon on Raspbian and
  Ubuntu, the stack consistently fails when attempting to "Set Default
  PHY" on the latter. Curiously, under Ubuntu the adapter also appears
  to lack a MAC address.

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

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

[Kernel-packages] [Bug 1904221] [NEW] Ask 8821C Bluetooth controller to drop old firmware

[Kai-Heng Feng]

Public bug reported:

[Impact]
Some platforms may keep USB power in S3/S4/S5, so Realtek 8821C retains
its firmware even with a cold boot.

[Fix]
Use vendor command to drop firmware if the version is old.

[Test case]
Use dmesg to check if new firmware is loaded.
With the patch applied, we can find new firmware is loaded.

[Where problems could occur]
There's a 200ms delay which can slow down when BT controller is opened
by userspace first time.

** Affects: linux (Ubuntu)
 Importance: Medium
 Status: Confirmed

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

** Affects: linux (Ubuntu Focal)
 Importance: Medium
 Status: Confirmed

** Affects: linux-oem-5.6 (Ubuntu Focal)
 Importance: Medium
 Status: Confirmed

** Affects: linux (Ubuntu Groovy)
 Importance: Medium
 Status: Confirmed

** Affects: linux-oem-5.6 (Ubuntu Groovy)
 Importance: Undecided
 Status: Invalid

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

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

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

** Changed in: linux-oem-5.6 (Ubuntu Groovy)
   Status: New => Invalid

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

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

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

** Changed in: linux-oem-5.6 (Ubuntu Focal)
   Status: New => Confirmed

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

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

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

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

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

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

Title:
  Ask 8821C Bluetooth controller to drop old firmware

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in linux-oem-5.6 source package in Focal:
  Confirmed
Status in linux source package in Groovy:
  Confirmed
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  [Impact]
  Some platforms may keep USB power in S3/S4/S5, so Realtek 8821C retains
  its firmware even with a cold boot.

  [Fix]
  Use vendor command to drop firmware if the version is old.

  [Test case]
  Use dmesg to check if new firmware is loaded.
  With the patch applied, we can find new firmware is loaded.

  [Where problems could occur]
  There's a 200ms delay which can slow down when BT controller is opened
  by userspace first time.

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

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

[Kernel-packages] [Bug 1864871] Re: Failed to init Intel sound card in 20.04

[Anton]

Update on the initial report: currently with 5.4.0-53 sound card is
initialized without any workarounds. But only output dynamics works,
reported microphone issue here:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1904213

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

Title:
  Failed to init Intel sound card in 20.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After installing current 20.04 release on ThinkBook 13s IML with Intel
  audio card there is no sound available because sound card not detected
  (only dummy output available in sound settings):

  $ alsamixer 
  cannot open mixer: No such file or directory

  $ lspci -nnk |grep -A2 audio
  lspci: Unable to load libkmod resources: error -12
  00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device 
[8086:02c8]
Subsystem: Lenovo Device [17aa:3816]
Kernel driver in use: sof-audio-pci
  00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:02a3]
Subsystem: Lenovo Device [17aa:3819]

  $ pacmd list-cards 
  0 card(s) available.

  $ dmesg |grep sof
  [0.755398] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [0.755400] software IO TLB: mapped [mem 0x7d91d000-0x8191d000] (64MB)
  [2.142149] systemd[1]: Mounting Mount unit for software-boutique, 
revision 54...
  [2.333772] systemd[1]: Mounted Mount unit for software-boutique, revision 
54.
  [2.770307] sof-audio-pci :00:1f.3: warning: No matching ASoC machine 
driver found
  [2.770316] sof-audio-pci :00:1f.3: DSP detected with PCI 
class/subclass/prog-if 0x040100
  [2.770473] sof-audio-pci :00:1f.3: use msi interrupt mode
  [2.770696] sof-audio-pci :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [2.779359] sof-audio-pci :00:1f.3: hda codecs found, mask 5
  [2.779360] sof-audio-pci :00:1f.3: using HDA machine driver 
skl_hda_dsp_generic now
  [2.817051] sof-audio-pci :00:1f.3: Direct firmware load for 
intel/sof/sof-cnl.ri failed with error -2
  [2.817054] sof-audio-pci :00:1f.3: error: request firmware 
intel/sof/sof-cnl.ri failed err: -2
  [2.817057] sof-audio-pci :00:1f.3: error: failed to load DSP firmware 
-2
  [2.817058] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: 
-2

  I've found similar bug reported here:
  https://bugs.archlinux.org/task/64720

  As a workaround I've added `snd_hda_intel.dmic_detect=0` to boot
  options and after that sound card successfully detected and started
  working.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-14-generic 5.4.0-14.17
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: MATE
  Date: Wed Feb 26 19:22:05 2020
  InstallationDate: Installed on 2020-02-25 (1 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200221)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:0c02 Elan Microelectronics Corp. ELAN:Fingerprint
   Bus 001 Device 002: ID 04f2:b61e Chicony Electronics Co., Ltd Integrated 
Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20RR
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=94f1e507-a44a-46a8-9163-548d27303afb ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  SourcePackage: linux-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CQCN24WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 13s-IML
  dmi.modalias: 
dmi:bvnLENOVO:bvrCQCN24WW:bd10/29/2019:svnLENOVO:pn20RR:pvrLenovoThinkBook13s-IML:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook13s-IML:
  dmi.product.family: ThinkBook 13s-IML
  dmi.product.name: 20RR
  dmi.product.sku: LENOVO_MT_20RR_BU_idea_FM_ThinkBook 13s-IML
  dmi.product.version: Lenovo ThinkBook 13s-IML
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1901406] Re: Lenovo T490 extremely show with Ubuntu 20.20 running kernel 5.8

[matiaslaporte]

I just wanted to chime in and say I have the same problem, also with a
T490, although the processor is i7-8565U CPU @ 1.80GHz and I am running
Kubuntu 20.10. Currently running kernel 5.8.0-28.

If there's any way I can help, let me know.

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

Title:
  Lenovo T490 extremely show with Ubuntu 20.20 running kernel 5.8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 20.04 to 20.20 on my laptop, the machine became
  extremely slow. After a days work I noticed that it never got any
  faster, and the machine was a lot colder than usual. Running cat
  /proc/cpuinfo and sudo cpupower frequency-info I noticed that the CPU
  was locked to 400Mhz.

  After some googling I found reports of people having trouble with CPU
  frequency governors on kernel 5.8. I tried to add intel_pstate=active
  to grub, but that didn't help.

  My short term workaround is to choose the old 5.4 kernel from 20.04.
  With this kernel everything is snappy again! Currently it's running at
  3.2 Ghz with little load.

  CPU info from /proc/cpuinfo (with kernel 5.4):

  processor : 0
  vendor_id : GenuineIntel
  cpu family: 6
  model : 142
  model name: Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz
  stepping  : 12
  microcode : 0xd6
  cpu MHz   : 4551.153
  cache size: 8192 KB
  physical id   : 0
  siblings  : 8
  core id   : 0
  cpu cores : 4
  apicid: 0
  initial apicid: 0
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 22
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb 
rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est 
tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch 
cpuid_fault epb invpcid_single ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow 
vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms 
invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves 
dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear 
flush_l1d arch_capabilities
  bugs  : spectre_v1 spectre_v2 spec_store_bypass swapgs taa 
itlb_multihit srbds
  bogomips  : 4199.88
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 39 bits physical, 48 bits virtual
  power management:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hennikul   2402 F pulseaudio
   /dev/snd/pcmC0D0p:   hennikul   2402 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2019-09-02 (418 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20N2CTO1WW
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-25-generic 
root=UUID=a36f1344-fd6c-40ef-a397-57f5a57594df ro intel_pstate=active quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  Tags:  groovy wayland-session
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (2 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/19/2020
  dmi.bios.release: 1.61
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2IET83W (1.61 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20N2CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2IET83W(1.61):bd01/19/2020:br1.61:efr1.16:svnLENOVO:pn20N2CTO1WW:pvrThinkPadT490:rvnLENOVO:rn20N2CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T490
  dmi.product.name: 20N2CTO1WW
  dmi.product.sku: LENOVO_MT_20N2_BU_Think_FM_ThinkPad T490
  dmi.product.version: ThinkPad T490
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1903397] Re: Groovy 5.8 kernel hangs on boot on CPUs with eLLC

[Jouni Mettala]

** Tags added: kernel-fixed-upstream

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

Title:
  Groovy 5.8 kernel hangs on boot on CPUs with eLLC

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  5.8 kernel hangs on boot on my PC with Intel Core i7-5775C.
  Bug is already fixed upstream:
  https://gitlab.freedesktop.org/drm/intel/-/issues/2381
  https://bugzilla.kernel.org/show_bug.cgi?id=208737
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.10-rc1&id=1664ffee760a5d98952318fdd9b198fae396d660
  Please backport the fix.
  Thanks!

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

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

[Kernel-packages] [Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code

[Sebastien Bacher]

Unsubscribing sponsors for now, Alex are you still working on that?
Please subscribe the team back if you get something ready for upload

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

Title:
  [bionic]blutoothd segfault when you cancel the keyboard pairing during
  the dialog for pairing code

Status in OEM Priority Project:
  In Progress
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Bionic:
  In Progress
Status in bluez source package in Eoan:
  Fix Released
Status in bluez source package in Focal:
  Fix Released
Status in bluez source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  This patch is for this issue:
  steps: 
  1. pair bluetooth keyboard 
  2. see the dialog asking user input the code for pairing. 
  3. press "esc" to cancel it. 
  4. blutoothd segfault shows in dmesg after a while. 
  5. Bluetooth shows off on setting UI of right top corner. dmesg shows: [ 
978.138593] bluetoothd[1569]: segfault at 0 ip 55564abe0a06 sp 
7ffe4bec6410 error 4 in bluetoothd[55564ab77000+f3000]

  
  [Test Case]

   1. pair bluetooth keyboard
   2. see the dialog asking user input the code for pairing.
   3. press "esc" to cancel it.
   4. the bluetooth should still work to pair another bluetooth device.

  [Regression Potential]

   * This patch workaround the case that a queue node was created but
  not yet assigned function before user input pairing keycode. If the
  user cancel the paring before inputting pairing keycode then assign
  the function pointer a dummy 'direct_match'.

  * Bluetoothd responses to Bluetooth functions and "queue" is a shared
  common data structure, so in case of regression happens then blutoothd
  systemd service would be crashed.

   * We can verify this by operating add/remove BT devices to trigger
  queue operations.

   * I verified on target machine BIOS ID:0983 on BT mouse, keyboard,
  headset on pairing, remove and functionality checking.

  [Other Info]

   * NO.

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

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

[Kernel-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400

[Sebastien Bacher]

There is no intend here to block any fix for stable serie but in case
that was not clear enough or if the SRU team didn't feel comfortable
with hirsute lacking behind and I uploaded back the patches but I'm
tagging the bug as 'block-proposed' instead which should be enough
incensitive to sort out

** Tags added: block-proposed

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

Title:
  [SRU] Bluetooth won't activate on the pi 400

Status in bluez package in Ubuntu:
  Triaged
Status in bluez source package in Hirsute:
  Triaged

Bug description:
  [Impact]

  Without these patches, Bluetooth is inoperable on the recently
  released Raspberry Pi 400.

  [Test Case]

  * Boot the Ubuntu Desktop for Pi image on a Pi 400.
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is not enabled and attempting to activate it fails
  * sudo add-apt-repository ppa:waveform/pi-bluetooth
  * sudo apt update
  * sudo apt install bluez
  * sudo reboot
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, 
mobile phones, headphones, etc.) can connect and operate correctly 

  [Regression Potential]

  Extremely low (on groovy in particular, this has the same version of
  bluez as hirsute). The only significant risk is to non-Pi platforms or
  dongles which also use the Broadcom 43xx (or Cypress 305) chips for
  Bluetooth which might be inadvertently affected by these patches.

  [Original Description]

  The new Pi 400 has a slightly different Wifi/BT chip to the Pi4.
  Whilst wifi works happily, Bluetooth fails to operate. This doesn't
  appear to be an issue with either the firmware (the latest versions
  from upstream Raspbian have been tried), or the kernel (a known-good
  raspi kernel has been tested under Ubuntu), but with Bluez itself.
  Specifically, tracing the initialization with btmon on Raspbian and
  Ubuntu, the stack consistently fails when attempting to "Set Default
  PHY" on the latter. Curiously, under Ubuntu the adapter also appears
  to lack a MAC address.

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

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

[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension

[JXT]

Is anything going on with this? It's been quite a while. I recently
retested and the r8169 still will not wake for 80+ seconds upon wake.

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

Title:
  r8169 ethernet card don't work after returning from suspension

Status in Linux:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-kernel-headers package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  Ethernet r8169 stops working after system resumed from suspend.

  [Test]
  User confirmed these patches fix the issue. r8169 continues to work
  after resume from suspend.

  [Regression Potential]
  Medium. The fix is limited to one device, all patches are in mainline.
  The WOL default change might cause regression for users that depend on
  BIOS settings. We can advice them to use userspace tool (systemd,
  ethtool, etc.) instead.

  ===Original Bug Report===
  I have noticed that the network stopped working on my desktop after I've 
suspended the system and woke it up. On dmesg there are messages like:

  [  150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
  [  150.944101] do_IRQ: 3.37 No irq handler for vector
  [  150.944105] r8169 :01:00.0 enp1s0: link down
  [  150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready

  When using Xenial (from a different install), this problem is not
  happening. This is happening on Bionic.

  There are only two ways to restore connectivity:
  1) Reboot the system;
  2) Remove the r8169 module and reinsert it with modprobe.

  The motherboard is a AsRock H55M-LE and the Ethernet controller is:

  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.172
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Mar  2 00:21:57 2018
  Dependencies:

  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-10-generic.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1153 F pulseaudio
   /dev/snd/controlC1:  usuario1153 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26'
     Mixer name : 'VIA VT1818S'
     Components : 'HDA:11060440,18492818,0010'
     Controls  : 40
     Simple ctrls  : 17
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27'
     Mixer name : 'ATI R6xx HDMI'
     Components : 'HDA:1002aa01,00aa0100,00100200'
     Controls  : 7
     Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
     Capabilities: pswitch pswitch-joined
     Playback channels: Mono
     Mono: Playback [on]
  CurrentDesktop: LXDE
  Dependencies:

  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-firmware 1.172
  PackageArchitecture: all
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz 
root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:

  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: H55M-LE
  dmi.board.vendor: ASRock
  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.:bvrP1.80:bd10/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrTo

[Kernel-packages] [Bug 1903397] Re: Groovy 5.8 kernel hangs on boot on CPUs with eLLC

[John Smith]

The fix is backported to 5.9 kernel.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.9.8&id=7bc462243188e05cc976587bc9942e7c05241140
5.8 is EOL.
Will the fix be backported to Groovy 5.8 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/1903397

Title:
  Groovy 5.8 kernel hangs on boot on CPUs with eLLC

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  5.8 kernel hangs on boot on my PC with Intel Core i7-5775C.
  Bug is already fixed upstream:
  https://gitlab.freedesktop.org/drm/intel/-/issues/2381
  https://bugzilla.kernel.org/show_bug.cgi?id=208737
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.10-rc1&id=1664ffee760a5d98952318fdd9b198fae396d660
  Please backport the fix.
  Thanks!

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

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

[Kernel-packages] [Bug 1874194] Re: Ubuntu 20.04 HDMI connected, no boot

[Andrew Osetrov]

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

I have last Ubuntu 20.10 on an DEXP Atlas H158 ( Core i7 6700HQ,  Nvidia
GeForce 940M + Intel HD 530). And removing "quiet splash" does not help
me with that bug. Have to remove HDMI cable from my notebook before
every boot.

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

Title:
  Ubuntu 20.04 HDMI connected, no boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Ubuntu 20.04 (using the image created on 20 april) on
  my Dell XPS15 9560. This laptop has a Intel / nVidia combo.

  The problem i am facing is that when i have an external monitor
  connected to the laptop through the HDMI connector of the laptop,
  Ubuntu does not boot and hangs on the splash screen. I have not found
  any way to get logging on any kind.

  Before i was running Ubuntu 18.04 and did not have any problems with
  the monitor and HDMI cable. After boot is finished (without monitor
  connected) inserting the HDMI cable works fine and i can use the
  monitor and laptop screen without any problem.

  I have installed the preferred nVida proprietary driver. Also it does
  not matter if booting with nVidia selected or Intel selected.

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

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

[Kernel-packages] [Bug 1904186] Missing required logs.

[Ubuntu Kernel Bot]

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

apport-collect 1904186

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

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

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

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

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

Title:
  Linux kernel 5.8 is now EOL on kernel.org

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  According to kernel.org, the 5.8 branch of the Linux kernel is now
  End-Of-Life (EOL).

  This mean it will not be supported as much as the 5.9 branch will.

  It should be better to switch Groovy and Hisute to 5.9 branch.

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

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

[Kernel-packages] [Bug 1904013] Re: qualcomm atheros bluetooth simultaneously

[Qingfeng]

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

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

Title:
  qualcomm atheros bluetooth simultaneously

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My System is Ubuntu 20.04 and kernel 5.4.0-53. My net card is Qualcomm 
Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01), with 
driver ath9k,  and it workes well for Wifi and BT respectively. However, when 
I'm using wifi, open BT, and then I lost net. After turn off BT, wifi can work 
correctly again. What should I do to connet BT device while wifi is connected. 
Thanks.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  feng   1680 F pulseaudio
   /dev/snd/pcmC0D0p:   feng   1680 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-10 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. GL552VW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-53-generic 
root=UUID=73f53186-435a-4e1a-9472-ac1e48065224 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-53-generic N/A
   linux-backports-modules-5.4.0-53-generic  N/A
   linux-firmware1.187.4
  Tags:  focal
  Uname: Linux 5.4.0-53-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: 09/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL552VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL552VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.300:bd09/06/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL552VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1904186] [NEW] Linux kernel 5.8 is now EOL on kernel.org

[David Girault]

Public bug reported:

According to kernel.org, the 5.8 branch of the Linux kernel is now End-
Of-Life (EOL).

This mean it will not be supported as much as the 5.9 branch will.

It should be better to switch Groovy and Hisute to 5.9 branch.

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

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

Title:
  Linux kernel 5.8 is now EOL on kernel.org

Status in linux package in Ubuntu:
  New

Bug description:
  According to kernel.org, the 5.8 branch of the Linux kernel is now
  End-Of-Life (EOL).

  This mean it will not be supported as much as the 5.9 branch will.

  It should be better to switch Groovy and Hisute to 5.9 branch.

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

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

[Kernel-packages] [Bug 1903048] Re: Bluetooth won't activate on the pi 400

[Tony Molloy]

Just to close the loop, I've just made fresh SD and USB boot disks from
the latest current Mate 20.10 image and both don't have working
Bluetooth, Ive updated both with the ppa and now both do work and I can
use mouse and headphones with no problems. I have no idea why my
original USB boot of Mate 20.10 didnt work after patching, there must be
another problem with it as well, my apologies for any confusion caused
by that.

Martin and Alan have been nagging us 'ordinary' people to get involved
and contribute where we can to help you out if possible, that's all I
was trying to do. Thanks for the patch, hope you get it upstreamed, etc OK.

Best wishes

Tony

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

Title:
  [SRU] Bluetooth won't activate on the pi 400

Status in bluez package in Ubuntu:
  Triaged
Status in bluez source package in Hirsute:
  Triaged

Bug description:
  [Impact]

  Without these patches, Bluetooth is inoperable on the recently
  released Raspberry Pi 400.

  [Test Case]

  * Boot the Ubuntu Desktop for Pi image on a Pi 400.
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is not enabled and attempting to activate it fails
  * sudo add-apt-repository ppa:waveform/pi-bluetooth
  * sudo apt update
  * sudo apt install bluez
  * sudo reboot
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, 
mobile phones, headphones, etc.) can connect and operate correctly 

  [Regression Potential]

  Extremely low (on groovy in particular, this has the same version of
  bluez as hirsute). The only significant risk is to non-Pi platforms or
  dongles which also use the Broadcom 43xx (or Cypress 305) chips for
  Bluetooth which might be inadvertently affected by these patches.

  [Original Description]

  The new Pi 400 has a slightly different Wifi/BT chip to the Pi4.
  Whilst wifi works happily, Bluetooth fails to operate. This doesn't
  appear to be an issue with either the firmware (the latest versions
  from upstream Raspbian have been tried), or the kernel (a known-good
  raspi kernel has been tested under Ubuntu), but with Bluez itself.
  Specifically, tracing the initialization with btmon on Raspbian and
  Ubuntu, the stack consistently fails when attempting to "Set Default
  PHY" on the latter. Curiously, under Ubuntu the adapter also appears
  to lack a MAC address.

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

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

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

[Qingfeng]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1904013/+attachment/5434143/+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/1904013

Title:
  qualcomm atheros bluetooth simultaneously

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My System is Ubuntu 20.04 and kernel 5.4.0-53. My net card is Qualcomm 
Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01), with 
driver ath9k,  and it workes well for Wifi and BT respectively. However, when 
I'm using wifi, open BT, and then I lost net. After turn off BT, wifi can work 
correctly again. What should I do to connet BT device while wifi is connected. 
Thanks.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  feng   1680 F pulseaudio
   /dev/snd/pcmC0D0p:   feng   1680 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-10 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. GL552VW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-53-generic 
root=UUID=73f53186-435a-4e1a-9472-ac1e48065224 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-53-generic N/A
   linux-backports-modules-5.4.0-53-generic  N/A
   linux-firmware1.187.4
  Tags:  focal
  Uname: Linux 5.4.0-53-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: 09/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL552VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL552VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.300:bd09/06/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL552VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[Qingfeng]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1904013/+attachment/5434141/+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/1904013

Title:
  qualcomm atheros bluetooth simultaneously

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My System is Ubuntu 20.04 and kernel 5.4.0-53. My net card is Qualcomm 
Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01), with 
driver ath9k,  and it workes well for Wifi and BT respectively. However, when 
I'm using wifi, open BT, and then I lost net. After turn off BT, wifi can work 
correctly again. What should I do to connet BT device while wifi is connected. 
Thanks.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  feng   1680 F pulseaudio
   /dev/snd/pcmC0D0p:   feng   1680 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-10 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. GL552VW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-53-generic 
root=UUID=73f53186-435a-4e1a-9472-ac1e48065224 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-53-generic N/A
   linux-backports-modules-5.4.0-53-generic  N/A
   linux-firmware1.187.4
  Tags:  focal
  Uname: Linux 5.4.0-53-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: 09/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL552VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL552VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.300:bd09/06/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL552VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[Qingfeng]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1904013/+attachment/5434144/+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/1904013

Title:
  qualcomm atheros bluetooth simultaneously

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My System is Ubuntu 20.04 and kernel 5.4.0-53. My net card is Qualcomm 
Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01), with 
driver ath9k,  and it workes well for Wifi and BT respectively. However, when 
I'm using wifi, open BT, and then I lost net. After turn off BT, wifi can work 
correctly again. What should I do to connet BT device while wifi is connected. 
Thanks.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  feng   1680 F pulseaudio
   /dev/snd/pcmC0D0p:   feng   1680 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-10 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. GL552VW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-53-generic 
root=UUID=73f53186-435a-4e1a-9472-ac1e48065224 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-53-generic N/A
   linux-backports-modules-5.4.0-53-generic  N/A
   linux-firmware1.187.4
  Tags:  focal
  Uname: Linux 5.4.0-53-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: 09/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL552VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL552VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.300:bd09/06/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL552VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[Qingfeng]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1904013/+attachment/5434142/+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/1904013

Title:
  qualcomm atheros bluetooth simultaneously

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My System is Ubuntu 20.04 and kernel 5.4.0-53. My net card is Qualcomm 
Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01), with 
driver ath9k,  and it workes well for Wifi and BT respectively. However, when 
I'm using wifi, open BT, and then I lost net. After turn off BT, wifi can work 
correctly again. What should I do to connet BT device while wifi is connected. 
Thanks.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  feng   1680 F pulseaudio
   /dev/snd/pcmC0D0p:   feng   1680 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-10 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. GL552VW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-53-generic 
root=UUID=73f53186-435a-4e1a-9472-ac1e48065224 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-53-generic N/A
   linux-backports-modules-5.4.0-53-generic  N/A
   linux-firmware1.187.4
  Tags:  focal
  Uname: Linux 5.4.0-53-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: 09/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL552VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL552VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.300:bd09/06/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL552VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[Qingfeng]

apport information

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

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

Title:
  qualcomm atheros bluetooth simultaneously

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My System is Ubuntu 20.04 and kernel 5.4.0-53. My net card is Qualcomm 
Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01), with 
driver ath9k,  and it workes well for Wifi and BT respectively. However, when 
I'm using wifi, open BT, and then I lost net. After turn off BT, wifi can work 
correctly again. What should I do to connet BT device while wifi is connected. 
Thanks.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  feng   1680 F pulseaudio
   /dev/snd/pcmC0D0p:   feng   1680 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-10 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. GL552VW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-53-generic 
root=UUID=73f53186-435a-4e1a-9472-ac1e48065224 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-53-generic N/A
   linux-backports-modules-5.4.0-53-generic  N/A
   linux-firmware1.187.4
  Tags:  focal
  Uname: Linux 5.4.0-53-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: 09/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL552VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL552VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.300:bd09/06/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL552VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[Qingfeng]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1904013/+attachment/5434137/+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/1904013

Title:
  qualcomm atheros bluetooth simultaneously

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My System is Ubuntu 20.04 and kernel 5.4.0-53. My net card is Qualcomm 
Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01), with 
driver ath9k,  and it workes well for Wifi and BT respectively. However, when 
I'm using wifi, open BT, and then I lost net. After turn off BT, wifi can work 
correctly again. What should I do to connet BT device while wifi is connected. 
Thanks.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  feng   1680 F pulseaudio
   /dev/snd/pcmC0D0p:   feng   1680 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-10 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. GL552VW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-53-generic 
root=UUID=73f53186-435a-4e1a-9472-ac1e48065224 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-53-generic N/A
   linux-backports-modules-5.4.0-53-generic  N/A
   linux-firmware1.187.4
  Tags:  focal
  Uname: Linux 5.4.0-53-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: 09/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL552VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL552VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.300:bd09/06/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL552VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[Qingfeng]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1904013/+attachment/5434133/+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/1904013

Title:
  qualcomm atheros bluetooth simultaneously

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My System is Ubuntu 20.04 and kernel 5.4.0-53. My net card is Qualcomm 
Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01), with 
driver ath9k,  and it workes well for Wifi and BT respectively. However, when 
I'm using wifi, open BT, and then I lost net. After turn off BT, wifi can work 
correctly again. What should I do to connet BT device while wifi is connected. 
Thanks.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  feng   1680 F pulseaudio
   /dev/snd/pcmC0D0p:   feng   1680 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-10 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. GL552VW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-53-generic 
root=UUID=73f53186-435a-4e1a-9472-ac1e48065224 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-53-generic N/A
   linux-backports-modules-5.4.0-53-generic  N/A
   linux-firmware1.187.4
  Tags:  focal
  Uname: Linux 5.4.0-53-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: 09/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL552VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL552VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.300:bd09/06/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL552VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[Qingfeng]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1904013/+attachment/5434136/+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/1904013

Title:
  qualcomm atheros bluetooth simultaneously

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My System is Ubuntu 20.04 and kernel 5.4.0-53. My net card is Qualcomm 
Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01), with 
driver ath9k,  and it workes well for Wifi and BT respectively. However, when 
I'm using wifi, open BT, and then I lost net. After turn off BT, wifi can work 
correctly again. What should I do to connet BT device while wifi is connected. 
Thanks.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  feng   1680 F pulseaudio
   /dev/snd/pcmC0D0p:   feng   1680 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-10 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. GL552VW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-53-generic 
root=UUID=73f53186-435a-4e1a-9472-ac1e48065224 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-53-generic N/A
   linux-backports-modules-5.4.0-53-generic  N/A
   linux-firmware1.187.4
  Tags:  focal
  Uname: Linux 5.4.0-53-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: 09/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL552VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL552VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.300:bd09/06/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL552VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[Qingfeng]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1904013/+attachment/5434130/+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/1904013

Title:
  qualcomm atheros bluetooth simultaneously

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My System is Ubuntu 20.04 and kernel 5.4.0-53. My net card is Qualcomm 
Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01), with 
driver ath9k,  and it workes well for Wifi and BT respectively. However, when 
I'm using wifi, open BT, and then I lost net. After turn off BT, wifi can work 
correctly again. What should I do to connet BT device while wifi is connected. 
Thanks.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  feng   1680 F pulseaudio
   /dev/snd/pcmC0D0p:   feng   1680 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-10 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. GL552VW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-53-generic 
root=UUID=73f53186-435a-4e1a-9472-ac1e48065224 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-53-generic N/A
   linux-backports-modules-5.4.0-53-generic  N/A
   linux-firmware1.187.4
  Tags:  focal
  Uname: Linux 5.4.0-53-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: 09/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL552VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL552VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.300:bd09/06/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL552VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[Qingfeng]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1904013/+attachment/5434131/+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/1904013

Title:
  qualcomm atheros bluetooth simultaneously

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My System is Ubuntu 20.04 and kernel 5.4.0-53. My net card is Qualcomm 
Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01), with 
driver ath9k,  and it workes well for Wifi and BT respectively. However, when 
I'm using wifi, open BT, and then I lost net. After turn off BT, wifi can work 
correctly again. What should I do to connet BT device while wifi is connected. 
Thanks.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  feng   1680 F pulseaudio
   /dev/snd/pcmC0D0p:   feng   1680 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-10 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. GL552VW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-53-generic 
root=UUID=73f53186-435a-4e1a-9472-ac1e48065224 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-53-generic N/A
   linux-backports-modules-5.4.0-53-generic  N/A
   linux-firmware1.187.4
  Tags:  focal
  Uname: Linux 5.4.0-53-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: 09/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL552VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL552VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.300:bd09/06/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL552VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[Qingfeng]

apport information

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

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

Title:
  qualcomm atheros bluetooth simultaneously

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My System is Ubuntu 20.04 and kernel 5.4.0-53. My net card is Qualcomm 
Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01), with 
driver ath9k,  and it workes well for Wifi and BT respectively. However, when 
I'm using wifi, open BT, and then I lost net. After turn off BT, wifi can work 
correctly again. What should I do to connet BT device while wifi is connected. 
Thanks.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  feng   1680 F pulseaudio
   /dev/snd/pcmC0D0p:   feng   1680 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-10 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. GL552VW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-53-generic 
root=UUID=73f53186-435a-4e1a-9472-ac1e48065224 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-53-generic N/A
   linux-backports-modules-5.4.0-53-generic  N/A
   linux-firmware1.187.4
  Tags:  focal
  Uname: Linux 5.4.0-53-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: 09/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL552VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL552VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.300:bd09/06/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL552VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[Qingfeng]

apport information

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

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

Title:
  qualcomm atheros bluetooth simultaneously

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My System is Ubuntu 20.04 and kernel 5.4.0-53. My net card is Qualcomm 
Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01), with 
driver ath9k,  and it workes well for Wifi and BT respectively. However, when 
I'm using wifi, open BT, and then I lost net. After turn off BT, wifi can work 
correctly again. What should I do to connet BT device while wifi is connected. 
Thanks.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  feng   1680 F pulseaudio
   /dev/snd/pcmC0D0p:   feng   1680 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-10 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. GL552VW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-53-generic 
root=UUID=73f53186-435a-4e1a-9472-ac1e48065224 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-53-generic N/A
   linux-backports-modules-5.4.0-53-generic  N/A
   linux-firmware1.187.4
  Tags:  focal
  Uname: Linux 5.4.0-53-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: 09/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL552VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL552VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.300:bd09/06/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL552VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[Qingfeng]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1904013/+attachment/5434128/+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/1904013

Title:
  qualcomm atheros bluetooth simultaneously

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My System is Ubuntu 20.04 and kernel 5.4.0-53. My net card is Qualcomm 
Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01), with 
driver ath9k,  and it workes well for Wifi and BT respectively. However, when 
I'm using wifi, open BT, and then I lost net. After turn off BT, wifi can work 
correctly again. What should I do to connet BT device while wifi is connected. 
Thanks.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  feng   1680 F pulseaudio
   /dev/snd/pcmC0D0p:   feng   1680 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-10 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. GL552VW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-53-generic 
root=UUID=73f53186-435a-4e1a-9472-ac1e48065224 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-53-generic N/A
   linux-backports-modules-5.4.0-53-generic  N/A
   linux-firmware1.187.4
  Tags:  focal
  Uname: Linux 5.4.0-53-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: 09/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL552VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL552VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.300:bd09/06/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL552VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[Qingfeng]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1904013/+attachment/5434140/+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/1904013

Title:
  qualcomm atheros bluetooth simultaneously

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My System is Ubuntu 20.04 and kernel 5.4.0-53. My net card is Qualcomm 
Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01), with 
driver ath9k,  and it workes well for Wifi and BT respectively. However, when 
I'm using wifi, open BT, and then I lost net. After turn off BT, wifi can work 
correctly again. What should I do to connet BT device while wifi is connected. 
Thanks.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  feng   1680 F pulseaudio
   /dev/snd/pcmC0D0p:   feng   1680 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-10 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. GL552VW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-53-generic 
root=UUID=73f53186-435a-4e1a-9472-ac1e48065224 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-53-generic N/A
   linux-backports-modules-5.4.0-53-generic  N/A
   linux-firmware1.187.4
  Tags:  focal
  Uname: Linux 5.4.0-53-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: 09/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL552VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL552VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.300:bd09/06/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL552VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[Qingfeng]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1904013/+attachment/5434138/+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/1904013

Title:
  qualcomm atheros bluetooth simultaneously

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My System is Ubuntu 20.04 and kernel 5.4.0-53. My net card is Qualcomm 
Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01), with 
driver ath9k,  and it workes well for Wifi and BT respectively. However, when 
I'm using wifi, open BT, and then I lost net. After turn off BT, wifi can work 
correctly again. What should I do to connet BT device while wifi is connected. 
Thanks.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  feng   1680 F pulseaudio
   /dev/snd/pcmC0D0p:   feng   1680 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-10 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. GL552VW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-53-generic 
root=UUID=73f53186-435a-4e1a-9472-ac1e48065224 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-53-generic N/A
   linux-backports-modules-5.4.0-53-generic  N/A
   linux-firmware1.187.4
  Tags:  focal
  Uname: Linux 5.4.0-53-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: 09/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL552VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL552VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.300:bd09/06/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL552VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[Qingfeng]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1904013/+attachment/5434139/+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/1904013

Title:
  qualcomm atheros bluetooth simultaneously

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My System is Ubuntu 20.04 and kernel 5.4.0-53. My net card is Qualcomm 
Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01), with 
driver ath9k,  and it workes well for Wifi and BT respectively. However, when 
I'm using wifi, open BT, and then I lost net. After turn off BT, wifi can work 
correctly again. What should I do to connet BT device while wifi is connected. 
Thanks.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  feng   1680 F pulseaudio
   /dev/snd/pcmC0D0p:   feng   1680 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-10 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. GL552VW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-53-generic 
root=UUID=73f53186-435a-4e1a-9472-ac1e48065224 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-53-generic N/A
   linux-backports-modules-5.4.0-53-generic  N/A
   linux-firmware1.187.4
  Tags:  focal
  Uname: Linux 5.4.0-53-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: 09/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL552VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL552VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.300:bd09/06/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL552VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[Qingfeng]

apport information

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

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

Title:
  qualcomm atheros bluetooth simultaneously

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My System is Ubuntu 20.04 and kernel 5.4.0-53. My net card is Qualcomm 
Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01), with 
driver ath9k,  and it workes well for Wifi and BT respectively. However, when 
I'm using wifi, open BT, and then I lost net. After turn off BT, wifi can work 
correctly again. What should I do to connet BT device while wifi is connected. 
Thanks.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  feng   1680 F pulseaudio
   /dev/snd/pcmC0D0p:   feng   1680 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-10 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. GL552VW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-53-generic 
root=UUID=73f53186-435a-4e1a-9472-ac1e48065224 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-53-generic N/A
   linux-backports-modules-5.4.0-53-generic  N/A
   linux-firmware1.187.4
  Tags:  focal
  Uname: Linux 5.4.0-53-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: 09/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL552VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL552VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.300:bd09/06/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL552VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[Qingfeng]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1904013/+attachment/5434129/+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/1904013

Title:
  qualcomm atheros bluetooth simultaneously

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My System is Ubuntu 20.04 and kernel 5.4.0-53. My net card is Qualcomm 
Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01), with 
driver ath9k,  and it workes well for Wifi and BT respectively. However, when 
I'm using wifi, open BT, and then I lost net. After turn off BT, wifi can work 
correctly again. What should I do to connet BT device while wifi is connected. 
Thanks.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  feng   1680 F pulseaudio
   /dev/snd/pcmC0D0p:   feng   1680 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-10 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. GL552VW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-53-generic 
root=UUID=73f53186-435a-4e1a-9472-ac1e48065224 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-53-generic N/A
   linux-backports-modules-5.4.0-53-generic  N/A
   linux-firmware1.187.4
  Tags:  focal
  Uname: Linux 5.4.0-53-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: 09/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL552VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL552VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.300:bd09/06/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL552VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1904013] Re: qualcomm atheros bluetooth simultaneously

[Qingfeng]

apport information

** Tags added: apport-collected focal

** Description changed:

- My System is Ubuntu 20.04 and kernel 5.4.0-53. My net card is Qualcomm
- Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01),
- with driver ath9k,  and it workes well for Wifi and BT respectively.
- However, when I'm using wifi, open BT, and then I lost net. After turn
- off BT, wifi can work correctly again. What should I do to connet BT
- device while wifi is connected. Thanks.
+ My System is Ubuntu 20.04 and kernel 5.4.0-53. My net card is Qualcomm 
Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01), with 
driver ath9k,  and it workes well for Wifi and BT respectively. However, when 
I'm using wifi, open BT, and then I lost net. After turn off BT, wifi can work 
correctly again. What should I do to connet BT device while wifi is connected. 
Thanks.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.11
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  feng   1680 F pulseaudio
+  /dev/snd/pcmC0D0p:   feng   1680 F...m pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-11-10 (2 days ago)
+ InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
+ MachineType: ASUSTeK COMPUTER INC. GL552VW
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-53-generic 
root=UUID=73f53186-435a-4e1a-9472-ac1e48065224 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
+ RelatedPackageVersions:
+  linux-restricted-modules-5.4.0-53-generic N/A
+  linux-backports-modules-5.4.0-53-generic  N/A
+  linux-firmware1.187.4
+ Tags:  focal
+ Uname: Linux 5.4.0-53-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: 09/06/2016
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: GL552VW.300
+ dmi.board.asset.tag: ATN12345678901234567
+ dmi.board.name: GL552VW
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: 1.0
+ dmi.chassis.asset.tag: ATN12345678901234567
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: ASUSTeK COMPUTER INC.
+ dmi.chassis.version: 1.0
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.300:bd09/06/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
+ dmi.product.family: GL
+ dmi.product.name: GL552VW
+ dmi.product.sku: ASUS-NotebookSKU
+ dmi.product.version: 1.0
+ dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1904013/+attachment/5434127/+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/1904013

Title:
  qualcomm atheros bluetooth simultaneously

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My System is Ubuntu 20.04 and kernel 5.4.0-53. My net card is Qualcomm 
Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01), with 
driver ath9k,  and it workes well for Wifi and BT respectively. However, when 
I'm using wifi, open BT, and then I lost net. After turn off BT, wifi can work 
correctly again. What should I do to connet BT device while wifi is connected. 
Thanks.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  feng   1680 F pulseaudio
   /dev/snd/pcmC0D0p:   feng   1680 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-10 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. GL552VW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-53-generic 
root=UUID=73f53186-435a-4e1a-9472-ac1e48065224 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-53-generic N/A
   linux-backports-modules-5.4.0-53-generic  N/A
   linux-firmware1.187.4
  Tags:  focal
  Uname: Linux 5.4.0-53-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: 09/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL552VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL552VW

[Kernel-packages] [Bug 1904054] Re: kernel 5.8 general protection fault at boot

[Colin Ian King]

I may be useful to add "debug ignore_loglevel" to the kernel boot
command line to get more debugging information during boot to see which
module is tripping this issue.

edit the /etc/default/grub (as the root user) and add the debug and
ignore_loglevel keywords to the GRUB_CMDLINE_LINUX_DEFAULT

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash debug ignore_loglevel"

then run:

sudo update-grub

and reboot. Can you then attach the full kernel log.

Thanks.

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

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

Title:
  kernel 5.8 general protection fault at boot

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu kernel version 5.8.0-28 (as well as the previous 5.8.0-26)
  crashes at boot with many general protection faults, on my Intel NUC
  10. Ubuntu kernel version 5.4.0-52 did not exhibit this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-28-generic 5.8.0-28.30
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  benp   2912 F pulseaudio
   /dev/snd/controlC1:  benp   2912 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 12 11:51:07 2020
  InstallationDate: Installed on 2020-10-08 (35 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Intel(R) Client Systems NUC10i7FNH
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash crashkernel=512M-:192M
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.190.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2020-10-28 (15 days ago)
  dmi.bios.date: 08/17/2020
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: FNCML357.0045.2020.0817.1709
  dmi.board.asset.tag: Default string
  dmi.board.name: NUC10i7FNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K61360-302
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrFNCML357.0045.2020.0817.1709:bd08/17/2020:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: FN
  dmi.product.name: NUC10i7FNH
  dmi.product.sku: BXNUC10i7FNH
  dmi.product.version: K61081-302
  dmi.sys.vendor: Intel(R) Client Systems

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

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

[Kernel-packages] [Bug 1904164] [NEW] package libnvidia-common-450-server 450.51.06-0ubuntu0.20.04.2 failed to install/upgrade: trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.8

[Daksh grover]

Public bug reported:

idk system reported the problem

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libnvidia-common-450-server 450.51.06-0ubuntu0.20.04.2
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Nov 13 14:57:19 2020
Dependencies:
 
DuplicateSignature:
 package:libnvidia-common-450-server:450.51.06-0ubuntu0.20.04.2
 Unpacking libnvidia-common-450-server (450.80.02-0ubuntu0.20.04.3) over 
(450.51.06-0ubuntu0.20.04.2) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-BmAFYy/24-libnvidia-common-450-server_450.80.02-0ubuntu0.20.04.3_all.deb
 (--unpack):
  trying to overwrite 
'/usr/share/nvidia/nvidia-application-profiles-450.80.02-key-documentation', 
which is also in package libnvidia-common-450 450.80.02-0ubuntu0.20.04.2
ErrorMessage: trying to overwrite 
'/usr/share/nvidia/nvidia-application-profiles-450.80.02-key-documentation', 
which is also in package libnvidia-common-450 450.80.02-0ubuntu0.20.04.2
InstallationDate: Installed on 2020-08-28 (76 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: nvidia-graphics-drivers-450-server
Title: package libnvidia-common-450-server 450.51.06-0ubuntu0.20.04.2 failed to 
install/upgrade: trying to overwrite 
'/usr/share/nvidia/nvidia-application-profiles-450.80.02-key-documentation', 
which is also in package libnvidia-common-450 450.80.02-0ubuntu0.20.04.2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal package-conflict

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

Title:
  package libnvidia-common-450-server 450.51.06-0ubuntu0.20.04.2 failed
  to install/upgrade: trying to overwrite '/usr/share/nvidia/nvidia-
  application-profiles-450.80.02-key-documentation', which is also in
  package libnvidia-common-450 450.80.02-0ubuntu0.20.04.2

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

Bug description:
  idk system reported the problem

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libnvidia-common-450-server 450.51.06-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Nov 13 14:57:19 2020
  Dependencies:
   
  DuplicateSignature:
   package:libnvidia-common-450-server:450.51.06-0ubuntu0.20.04.2
   Unpacking libnvidia-common-450-server (450.80.02-0ubuntu0.20.04.3) over 
(450.51.06-0ubuntu0.20.04.2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-BmAFYy/24-libnvidia-common-450-server_450.80.02-0ubuntu0.20.04.3_all.deb
 (--unpack):
trying to overwrite 
'/usr/share/nvidia/nvidia-application-profiles-450.80.02-key-documentation', 
which is also in package libnvidia-common-450 450.80.02-0ubuntu0.20.04.2
  ErrorMessage: trying to overwrite 
'/usr/share/nvidia/nvidia-application-profiles-450.80.02-key-documentation', 
which is also in package libnvidia-common-450 450.80.02-0ubuntu0.20.04.2
  InstallationDate: Installed on 2020-08-28 (76 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: nvidia-graphics-drivers-450-server
  Title: package libnvidia-common-450-server 450.51.06-0ubuntu0.20.04.2 failed 
to install/upgrade: trying to overwrite 
'/usr/share/nvidia/nvidia-application-profiles-450.80.02-key-documentation', 
which is also in package libnvidia-common-450 450.80.02-0ubuntu0.20.04.2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400

[Sebastien Bacher]

@Matthieu, @Dave, thanks for the comments and details.

I'm not blocking work to land, the 20.10 SRU could be accepted now and I didn't 
revert in that serie.
The SRU team tries to ensure the fix is in the new serie so it doesn't get 
forgotten/regress when next version is out but I think it's pretty clear we are 
going to sort out the review details, that's not a blocker and SRU team has 
been happy in the past to let things in with the understand than $newserie is 
being sorted out

> If upstream say "yes" to the patches, without further discussion: that's
> great, but there'd presumably still be some delay before another version
> makes its way down to us, so we'd be applying *some* patch to make it work in 
> the interim.

Again I'm not asking for the patches to be reviewed or accepted upstream
before they are uploaded to Ubuntu, I'm just asking for them to be sent
upstream and the reference to the email/report/merge request to be added
to the patches. It would probably have been less work to just do it
rather than type a long explanation here on why we need to distro patch
in any case (which I never  disagreed with)

Sorry again but we have been bitten too often in similar situation where
people never upstreamed the work when they said they would because they
got busy with other things, and we are the ones paying the maintainance
cost later on.

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

Title:
  [SRU] Bluetooth won't activate on the pi 400

Status in bluez package in Ubuntu:
  Triaged
Status in bluez source package in Hirsute:
  Triaged

Bug description:
  [Impact]

  Without these patches, Bluetooth is inoperable on the recently
  released Raspberry Pi 400.

  [Test Case]

  * Boot the Ubuntu Desktop for Pi image on a Pi 400.
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is not enabled and attempting to activate it fails
  * sudo add-apt-repository ppa:waveform/pi-bluetooth
  * sudo apt update
  * sudo apt install bluez
  * sudo reboot
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, 
mobile phones, headphones, etc.) can connect and operate correctly 

  [Regression Potential]

  Extremely low (on groovy in particular, this has the same version of
  bluez as hirsute). The only significant risk is to non-Pi platforms or
  dongles which also use the Broadcom 43xx (or Cypress 305) chips for
  Bluetooth which might be inadvertently affected by these patches.

  [Original Description]

  The new Pi 400 has a slightly different Wifi/BT chip to the Pi4.
  Whilst wifi works happily, Bluetooth fails to operate. This doesn't
  appear to be an issue with either the firmware (the latest versions
  from upstream Raspbian have been tried), or the kernel (a known-good
  raspi kernel has been tested under Ubuntu), but with Bluez itself.
  Specifically, tracing the initialization with btmon on Raspbian and
  Ubuntu, the stack consistently fails when attempting to "Set Default
  PHY" on the latter. Curiously, under Ubuntu the adapter also appears
  to lack a MAC address.

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

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

[Kernel-packages] [Bug 1896091] Re: [i915] Noise-like lines of graphics corruption when moving windows in Xorg sessions

[Kai-Heng Feng]

** Description changed:

  == SRU Justification ==
  [Impact]
  Noise-like lines of graphics corruption when moving windows in Xorg
  sessions.
  
  [Fix]
  Revert "UBUNTU: SAUCE: drm/i915: Synchronize active and retire
  callbacks".
  
  [Test]
  Daniel van Vugt confirmed reverting the commit fixes the issue.
  I can also reproduce the issue on one of my system, I can confirm it
  fixes the issue too.
  
  [Where problems could occur]
  Race condition the commit solves may appear again.
- However it was to solve the issue on 5.4, and the race could already be
- solved on 5.8.
+ The commit was reverted and replaced by an upstream fix, which is already 
included in 5.8. So it should be rather safe here.
  
  == Original Bug Report ==
  
  I left my desktop (T480s thinkpad docked to ThinkVision P24h-10)
  unattended for a while, and then got the error message and now have
  funny lines on activity, e.g. red lines flashing on top of gnome-shell
  bar when switching windows, or white blocks/lines around typing text.
  
  This is the second or third time it happened, reboot fixes it until the
  error pops up again.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-19-generic 5.8.0-19.20
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jak5052 F pulseaudio
   /dev/snd/controlC1:  jak5052 F pulseaudio
   /dev/snd/pcmC1D0p:   jak5052 F...m pulseaudio
   /dev/snd/controlC0:  jak5052 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Thu Sep 17 19:14:11 2020
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2018-03-14 (917 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-19-generic N/A
   linux-backports-modules-5.8.0-19-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2020
  dmi.bios.release: 1.42
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET65W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  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.ec.firmware.release: 1.20
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET65W(1.42):bd06/04/2020:br1.42:efr1.20:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jak5052 F pulseaudio
   /dev/snd/controlC1:  jak5052 F pulseaudio
   /dev/snd/pcmC1D0p:   jak5052 F...m pulseaudio
   /dev/snd/controlC0:  jak5052 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2018-03-14 (917 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-19-generic N/A
   linux-backports-modules-5.8.0-19-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fax input kvm lpadmin lxd plugdev sambashare sbuild 
sudo
  _MarkForUpload: True
  dmi.bios.date: 06/04/2020
  dmi.bios.release: 1.42
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET65W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: 

[Kernel-packages] [Bug 1877533] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From mihaj...@de.ibm.com 2020-11-13 04:03 EDT---
This is a setup without crypto cards (Secure Execution guests don't support 
passthrough yet). I think that we can live with the new kdump default settings, 
as I wouldn't want to suggest putting half of the memory away for kdump on 
small VMs. The recommendation should be to use pbkdf2 for machines < 4GB 
without crypto cards. Ideally, the tools would emit a warning when configuring 
the command line. Alternatively, this could be documented in the Installation 
Guide.

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

Title:
  [20.10 FEAT] Increase the crashkernel setting if the root volume is
  luks2-encrypted

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Invalid
Status in makedumpfile source package in Focal:
  In Progress
Status in linux source package in Groovy:
  Invalid
Status in makedumpfile source package in Groovy:
  In Progress

Bug description:
  Description:
  In case the volume containing the root filesystem is encrypted using LUKS2 
the memory used while unlocking the volume may exceed the size allocated to the 
kdump kernel. This will lead to a failure while processing kdump and the dump 
file will not be stored. Unfortunately, this condition may not be detected by a 
client before a problem occurs.
  The request is to have the kdump package installation script check for LUKS2 
encryption (more precisely for Argon2i PBKDF, which is the root cause of the 
high memory usage). If the condition is met, the installation procedure should 
increase the crashkernel parameter to a higher value (>=512M)or issue a 
warning, if the system memory is insufficient to reserve enough crashkernel 
memory.

  Business Case:
  Pervasive Encryption and Secure Execution require encryption of the 
filesystems in order to keep customer data secure at all times. With the 
increasing usage of these technologies, the number of kdump will rise too, 
typically at inconvenient times, when the kdump is triggered due to a real 
customer issue.
  With the suggested change, the number of customer complaints and effort to 
handle them will be reduced.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions

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