Public bug reported:

Symptoms:

no hardware audio output device found by PulseAudio on eoan after I have
updated the system yesterday.


Works: linux-image-5.3.0-40-generic
Does not work: linux-image-5.3.0-42-generic


* I suspect this is somewhat related to the recent changes for SkyLake+ 
platforms between tags Ubuntu-5.3.0-40.32 and Ubuntu-5.3.0-42.34 (I am 
referring to the repo at 
<https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/eoan>).

* I am using the binary package from the Ubuntu repos, not a self-built
kernel.

* I can help with bisecting and testing if you like. If you like me to,
I need a piece of advice: is
<https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel> the proper up-to-
date documentation for building my Ubuntu kernel from the sources in the
git repo?


What I have tried so far:

I wanted to reload the sound module(s), so I ran the following command:

$ pulseaudio -k ; sudo rmmod snd_hda_intel snd_soc_skl_hda_dsp
snd_soc_skl_ssp_clk snd_soc_skl snd_soc_skl_ipc

Then I ran:

# modprobe snd-hda-intel


I found the following in my syslog (not totally sure about when exactly this 
happened – before or after the rmmod/modprobe):

(see attached file)


Output of ‘sudo lspci -vvnn’ (warning: on 5.3.0-40-generic! Because I am 
working in parallel and need a functioning audio setup right now; I can try 
this on another kernel in the evening if absolutely necessary, but this should 
suffice):

(see attached file)


If more information is necessary for proper debugging, please give me some 
instructions what to do. Thanks! ☺

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

** Attachment added: "excerpt from syslog, and output of ‘lspci -vvnn’"
   
https://bugs.launchpad.net/bugs/1868061/+attachment/5338694/+files/more_information

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

Title:
  linux-image-5.3.0-42-generic regression: no audio output on HP
  EliteBook 840 G6

Status in linux package in Ubuntu:
  New

Bug description:
  Symptoms:

  no hardware audio output device found by PulseAudio on eoan after I
  have updated the system yesterday.

  
  Works: linux-image-5.3.0-40-generic
  Does not work: linux-image-5.3.0-42-generic

  
  * I suspect this is somewhat related to the recent changes for SkyLake+ 
platforms between tags Ubuntu-5.3.0-40.32 and Ubuntu-5.3.0-42.34 (I am 
referring to the repo at 
<https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/eoan>).

  * I am using the binary package from the Ubuntu repos, not a self-
  built kernel.

  * I can help with bisecting and testing if you like. If you like me
  to, I need a piece of advice: is
  <https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel> the proper up-to-
  date documentation for building my Ubuntu kernel from the sources in
  the git repo?


  What I have tried so far:

  I wanted to reload the sound module(s), so I ran the following
  command:

  $ pulseaudio -k ; sudo rmmod snd_hda_intel snd_soc_skl_hda_dsp
  snd_soc_skl_ssp_clk snd_soc_skl snd_soc_skl_ipc

  Then I ran:

  # modprobe snd-hda-intel

  
  I found the following in my syslog (not totally sure about when exactly this 
happened – before or after the rmmod/modprobe):

  (see attached file)

  
  Output of ‘sudo lspci -vvnn’ (warning: on 5.3.0-40-generic! Because I am 
working in parallel and need a functioning audio setup right now; I can try 
this on another kernel in the evening if absolutely necessary, but this should 
suffice):

  (see attached file)

  
  If more information is necessary for proper debugging, please give me some 
instructions what to do. Thanks! ☺

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

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

Reply via email to