[Kernel-packages] [Bug 1828657] Re: Slow resume after lid close/open

2019-10-12 Thread Brian LePage
It looks like there have been some changes in this area of the Linux
kernel sometime around July, so I tried updating to the 5.4.0-rc2
upstream kernel today.  This updated kernel appears to fix the issue
I've been having.  I'll run with the 5.4.0-rc2 kernel for now.
Hopefully the update that fixed the slow resume issue will be included
in the next Ubuntu release.

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

Title:
  Slow resume after lid close/open

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Summary
  1.) Release Info:
  Description: Ubuntu 19.04
  Release:  19.04
  2.) Package version: linux-image-5.0.0-13-generic
  3.) Expected behavior: Computer resumes shortly after opening lid.
  4.) Actual behavior: Computer takes ~2 minutes to resume after opening lid.

  I have installed Ubuntu 19.04 (Disco Dingo) on my Lenovo Flex 6-11IGM.
  I found that when it resumes from sleep after opening the lid, it
  takes a long time to resume (~2 minutes).

  While experimenting with the upstream kernel releases, I found that
  the problem was introduced with version 5.0.5 version of the Linux
  kernel; the problem does not occur when I run version 5.0.4.

  I've narrowed the culprit down to the following commit in the upstream
  kernel:

  a57af6d07... ALSA: hda - Enforces runtime_resume after S3 and S4 for
  each codec

  This change was applied to the ubuntu kernel with commit
  9c51afaceb61459d2becac8fb32c860bb084e643.

  The following messages appear in the system log upon resume with the
  released ubuntu kernel:

  May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: snd_hda_intel :00:0e.0: 
azx_get_response timeout, switching to polling mode: last cmd=0x20bf8100
  May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: hid-sensor-hub 
001F:8086:22D8.0003: timeout waiting for response from ISHTP device
  May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: snd_hda_intel :00:0e.0: 
No response from codec, disabling MSI: last cmd=0x20bf8100
  May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: snd_hda_codec_hdmi 
hdaudioC0D2: Unable to sync register 0x2f0d00. -11

  These messages do not appear in the system log upon resume when
  running with upstream kernel version 5.0.4.

  I have upgraded the system BIOS to the latest from Lenovo (6qcn47ww),
  but the problem persists.

  For now, I will run with the 5.0.4 version of the upstream kernel, as
  I am not experiencing any issues with it.

  Thank you.

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

-- 
Mailing list: https://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 1847892] Missing required logs.

2019-10-12 Thread 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 1847892

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

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

Title:
  large performance regression (~30-40%) in wifi with 19.10 / 5.3 kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Probably relevant:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795116

  Card is an RTL8723BE.

  On 16.04 with the HWE stack, after 1795116 was fixed performance was a
  stable 75-80Mb/s.

  Linux 4.15.0-55-generic #60~16.04.2-Ubuntu SMP Thu Jul 4 09:03:09 UTC 2019 
x86_64
  Fri 26-Jul-19 12:28
  sent 459,277,171 bytes  received 35 bytes  9,278,327.39 bytes/sec

  Linux 4.15.0-55-generic #60~16.04.2-Ubuntu SMP Thu Jul 4 09:03:09 UTC 2019 
x86_64
  Sat 27-Jul-19 01:23
  sent 459,277,171 bytes  received 35 bytes  10,320,836.09 bytes/sec

  On 18.04, performance was still a stable 75-80Mb/s.

  After updating to 19.10, performance is typically ~50Mb/s, or about a
  37% regression.

  $ iwconfig wlan0
  wlan0 IEEE 802.11  ESSID:"**"  
Mode:Managed  Frequency:2.442 GHz  Access Point: 4C:60:DE:FB:A8:AB  
 
Bit Rate=150 Mb/s   Tx-Power=20 dBm   
Retry short limit:7   RTS thr=2347 B   Fragment thr:off
Power Management:on
Link Quality=59/70  Signal level=-51 dBm  
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
Tx excessive retries:0  Invalid misc:315   Missed beacon:0

  $ ./wifibench.sh 
  Linux 5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:46:08 UTC 2019 x86_64
  Sat 12-Oct-19 20:30
  sent 459,277,171 bytes  received 35 bytes  5,566,996.44 bytes/sec

  $ iwconfig wlan0 
  wlan0 IEEE 802.11  ESSID:"**"  
Mode:Managed  Frequency:2.442 GHz  Access Point: 4C:60:DE:FB:A8:AB  
 
Bit Rate=150 Mb/s   Tx-Power=20 dBm   
Retry short limit:7   RTS thr=2347 B   Fragment thr:off
Power Management:on
Link Quality=68/70  Signal level=-42 dBm  
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
Tx excessive retries:0  Invalid misc:315   Missed beacon:0

  So no corrupted packets or etc during that transfer.

  $ ifconfig wlan0
  wlan0: flags=4163  mtu 1500
  inet 192.168.1.33  netmask 255.255.255.0  broadcast 192.168.1.255
  ether dc:85:de:e4:17:a3  txqueuelen 1000  (Ethernet)
  RX packets 56608204  bytes 79066485957 (79.0 GB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 21634510  bytes 8726094217 (8.7 GB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  No issues of any kind in the week that it's been up. Just terrible
  performance.

  I'm painfully aware of all the module's parameters etc, and have tried
  them all, with no change in the results outside of typical wifi
  variance.

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

-- 
Mailing list: https://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 1847892] [NEW] large performance regression (~30-40%) in wifi with 19.10 / 5.3 kernel

2019-10-12 Thread arQon
Public bug reported:

Probably relevant:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795116

Card is an RTL8723BE.

On 16.04 with the HWE stack, after 1795116 was fixed performance was a
stable 75-80Mb/s.

Linux 4.15.0-55-generic #60~16.04.2-Ubuntu SMP Thu Jul 4 09:03:09 UTC 2019 
x86_64
Fri 26-Jul-19 12:28
sent 459,277,171 bytes  received 35 bytes  9,278,327.39 bytes/sec

Linux 4.15.0-55-generic #60~16.04.2-Ubuntu SMP Thu Jul 4 09:03:09 UTC 2019 
x86_64
Sat 27-Jul-19 01:23
sent 459,277,171 bytes  received 35 bytes  10,320,836.09 bytes/sec

On 18.04, performance was still a stable 75-80Mb/s.

After updating to 19.10, performance is typically ~50Mb/s, or about a
37% regression.

$ iwconfig wlan0
wlan0 IEEE 802.11  ESSID:"**"  
  Mode:Managed  Frequency:2.442 GHz  Access Point: 4C:60:DE:FB:A8:AB   
  Bit Rate=150 Mb/s   Tx-Power=20 dBm   
  Retry short limit:7   RTS thr=2347 B   Fragment thr:off
  Power Management:on
  Link Quality=59/70  Signal level=-51 dBm  
  Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
  Tx excessive retries:0  Invalid misc:315   Missed beacon:0

$ ./wifibench.sh 
Linux 5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:46:08 UTC 2019 x86_64
Sat 12-Oct-19 20:30
sent 459,277,171 bytes  received 35 bytes  5,566,996.44 bytes/sec

$ iwconfig wlan0 
wlan0 IEEE 802.11  ESSID:"**"  
  Mode:Managed  Frequency:2.442 GHz  Access Point: 4C:60:DE:FB:A8:AB   
  Bit Rate=150 Mb/s   Tx-Power=20 dBm   
  Retry short limit:7   RTS thr=2347 B   Fragment thr:off
  Power Management:on
  Link Quality=68/70  Signal level=-42 dBm  
  Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
  Tx excessive retries:0  Invalid misc:315   Missed beacon:0

So no corrupted packets or etc during that transfer.

$ ifconfig wlan0
wlan0: flags=4163  mtu 1500
inet 192.168.1.33  netmask 255.255.255.0  broadcast 192.168.1.255
ether dc:85:de:e4:17:a3  txqueuelen 1000  (Ethernet)
RX packets 56608204  bytes 79066485957 (79.0 GB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 21634510  bytes 8726094217 (8.7 GB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

No issues of any kind in the week that it's been up. Just terrible
performance.

I'm painfully aware of all the module's parameters etc, and have tried
them all, with no change in the results outside of typical wifi
variance.

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


** Tags: bionic eoan regression rtl8723be wifi

** Project changed: ubuntu-mate => linux (Ubuntu)

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

Title:
  large performance regression (~30-40%) in wifi with 19.10 / 5.3 kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Probably relevant:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795116

  Card is an RTL8723BE.

  On 16.04 with the HWE stack, after 1795116 was fixed performance was a
  stable 75-80Mb/s.

  Linux 4.15.0-55-generic #60~16.04.2-Ubuntu SMP Thu Jul 4 09:03:09 UTC 2019 
x86_64
  Fri 26-Jul-19 12:28
  sent 459,277,171 bytes  received 35 bytes  9,278,327.39 bytes/sec

  Linux 4.15.0-55-generic #60~16.04.2-Ubuntu SMP Thu Jul 4 09:03:09 UTC 2019 
x86_64
  Sat 27-Jul-19 01:23
  sent 459,277,171 bytes  received 35 bytes  10,320,836.09 bytes/sec

  On 18.04, performance was still a stable 75-80Mb/s.

  After updating to 19.10, performance is typically ~50Mb/s, or about a
  37% regression.

  $ iwconfig wlan0
  wlan0 IEEE 802.11  ESSID:"**"  
Mode:Managed  Frequency:2.442 GHz  Access Point: 4C:60:DE:FB:A8:AB  
 
Bit Rate=150 Mb/s   Tx-Power=20 dBm   
Retry short limit:7   RTS thr=2347 B   Fragment thr:off
Power Management:on
Link Quality=59/70  Signal level=-51 dBm  
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
Tx excessive retries:0  Invalid misc:315   Missed beacon:0

  $ ./wifibench.sh 
  Linux 5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:46:08 UTC 2019 x86_64
  Sat 12-Oct-19 20:30
  sent 459,277,171 bytes  received 35 bytes  5,566,996.44 bytes/sec

  $ iwconfig wlan0 
  wlan0 IEEE 802.11  ESSID:"**"  
Mode:Managed  Frequency:2.442 GHz  Access Point: 4C:60:DE:FB:A8:AB  
 
Bit Rate=150 Mb/s   Tx-Power=20 dBm   
Retry short limit:7   RTS thr=2347 B   Fragment thr:off
Power Management:on
Link Quality=68/70  Signal level=-42 dBm  
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
Tx excessive retries:0  Invalid misc:315   Missed beacon:0

  So no corrupted packets or etc during that transfer.

  $ ifconfig wlan0
  wlan0: flags=4163  mtu 1500
  inet 192.168.1.33 

[Kernel-packages] [Bug 1847892] [NEW] large performance regression (~30-40%) in wifi with 19.10 / 5.3 kernel

2019-10-12 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Probably relevant:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795116

Card is an RTL8723BE.

On 16.04 with the HWE stack, after 1795116 was fixed performance was a
stable 75-80Mb/s.

Linux 4.15.0-55-generic #60~16.04.2-Ubuntu SMP Thu Jul 4 09:03:09 UTC 2019 
x86_64
Fri 26-Jul-19 12:28
sent 459,277,171 bytes  received 35 bytes  9,278,327.39 bytes/sec

Linux 4.15.0-55-generic #60~16.04.2-Ubuntu SMP Thu Jul 4 09:03:09 UTC 2019 
x86_64
Sat 27-Jul-19 01:23
sent 459,277,171 bytes  received 35 bytes  10,320,836.09 bytes/sec

On 18.04, performance was still a stable 75-80Mb/s.

After updating to 19.10, performance is typically ~50Mb/s, or about a
37% regression.

$ iwconfig wlan0
wlan0 IEEE 802.11  ESSID:"**"  
  Mode:Managed  Frequency:2.442 GHz  Access Point: 4C:60:DE:FB:A8:AB   
  Bit Rate=150 Mb/s   Tx-Power=20 dBm   
  Retry short limit:7   RTS thr=2347 B   Fragment thr:off
  Power Management:on
  Link Quality=59/70  Signal level=-51 dBm  
  Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
  Tx excessive retries:0  Invalid misc:315   Missed beacon:0

$ ./wifibench.sh 
Linux 5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:46:08 UTC 2019 x86_64
Sat 12-Oct-19 20:30
sent 459,277,171 bytes  received 35 bytes  5,566,996.44 bytes/sec

$ iwconfig wlan0 
wlan0 IEEE 802.11  ESSID:"**"  
  Mode:Managed  Frequency:2.442 GHz  Access Point: 4C:60:DE:FB:A8:AB   
  Bit Rate=150 Mb/s   Tx-Power=20 dBm   
  Retry short limit:7   RTS thr=2347 B   Fragment thr:off
  Power Management:on
  Link Quality=68/70  Signal level=-42 dBm  
  Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
  Tx excessive retries:0  Invalid misc:315   Missed beacon:0

So no corrupted packets or etc during that transfer.

$ ifconfig wlan0
wlan0: flags=4163  mtu 1500
inet 192.168.1.33  netmask 255.255.255.0  broadcast 192.168.1.255
ether dc:85:de:e4:17:a3  txqueuelen 1000  (Ethernet)
RX packets 56608204  bytes 79066485957 (79.0 GB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 21634510  bytes 8726094217 (8.7 GB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

No issues of any kind in the week that it's been up. Just terrible
performance.

I'm painfully aware of all the module's parameters etc, and have tried
them all, with no change in the results outside of typical wifi
variance.

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


** Tags: eoan regression rtl8723be wifi
-- 
large performance regression (~30-40%) in wifi with 19.10 / 5.3 kernel
https://bugs.launchpad.net/bugs/1847892
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
Mailing list: https://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 1835660] Re: initramfs unpacking failed

2019-10-12 Thread tom
Changing to gzip is bad. 19.10 switched over to lz4 because it's way
faster decompressing, which makes for faster boots!

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

Title:
  initramfs unpacking failed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  "initramfs unpacking failed: Decoding failed",  message appears on
  boot up.

  If I "update-initramfs" using gzip instead of lz, then boot up passes
  without decoding failed message.

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

-- 
Mailing list: https://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 1847293] Re: eoan/linux-gcp: 5.3.0-1004.4 -proposed tracker

2019-10-12 Thread Ubuntu Kernel Bot
All tasks have been completed and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow
   Status: In Progress => Fix Released

** Tags removed: kernel-release-tracking-bug-live

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

Title:
  eoan/linux-gcp: 5.3.0-1004.4 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Fix Released
Status in linux-gcp source package in Eoan:
  Fix Released

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1847298
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Complete
  phase-changed: Sunday, 13. October 2019 03:26 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847293/+subscriptions

-- 
Mailing list: https://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 1839166] Re: Bios is not setting CPU cores to maximum frequency

2019-10-12 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Bios is not setting CPU cores to maximum frequency

Status in linux package in Ubuntu:
  Expired

Bug description:
  We are hitting below customer issue as explained briefly below.
   
  “
  UCS C220 M5
  Firmware 4.0(2f) - standalone
  Ubuntu 16.04.5 LTS with 4.15.0-29-generic kernel (HWE)
   
  The customer is looking to force the CPU frequency to stay on max value. 
Ubuntu detects variable speeds (the CPU cores are going down to 800 MHz):
   
  Bios is not setting all CPU cores to maximum frequency in Ubuntu.
  Bios settings are as below.
   
  - Disabled Intel speedstep
  - Disabled TurboBoost
  - Limited to C0/C1 only with disabled extended states
  - Disabled P states, or reduced as much as possible
  - Set profiles to max performance
  - Control for CPU performance is done via BIOS, not OS
  - CPU performance is Enterprise
   
  The issue is also not seen on another C220 M5SX without NVMe drives running 
3.1(3i). Same kernel version for Ubuntu.
  Downgrading the firmware on one of the affected C220 M5s doesn't resolve the 
issue.”
   
  All the cores are running on max frequency after applying the below command 
at the OS level:
   
  tuned-adm profile latency-performance
   
  “

  So please let us know is this BIOS or Ubuntu issue?

  I . will attach logs soon.

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

-- 
Mailing list: https://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 1847292] Re: eoan/linux-azure: 5.3.0-1003.3 -proposed tracker

2019-10-12 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-release
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1847298
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Signoff
  phase-changed: Sunday, 13. October 2019 02:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-release: Pending -- ready to copy
stakeholder-signoff: Stalled -- waiting for signoff
  variant: debs

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

Title:
  eoan/linux-azure: 5.3.0-1003.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Eoan:
  Fix Released

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1847298
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Signoff
  phase-changed: Sunday, 13. October 2019 02:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
stakeholder-signoff: Stalled -- waiting for signoff
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847292/+subscriptions

-- 
Mailing list: https://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 1847293] Re: eoan/linux-gcp: 5.3.0-1004.4 -proposed tracker

2019-10-12 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-release
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1847298
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
- phase: Ready for Promote to Release
- phase-changed: Sunday, 13. October 2019 02:41 UTC
+ phase: Complete
+ phase-changed: Sunday, 13. October 2019 03:26 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
- reason:
-   promote-to-release: Pending -- ready to copy
  variant: debs

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

Title:
  eoan/linux-gcp: 5.3.0-1004.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Fix Released
Status in linux-gcp source package in Eoan:
  Fix Released

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1847298
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Complete
  phase-changed: Sunday, 13. October 2019 03:26 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847293/+subscriptions

-- 
Mailing list: https://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 1847292] Re: eoan/linux-azure: 5.3.0-1003.3 -proposed tracker

2019-10-12 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-azure - 5.3.0-1003.3

---
linux-azure (5.3.0-1003.3) eoan; urgency=medium

  * eoan/linux-azure: 5.3.0-1003.3 -proposed tracker (LP: #1847292)

  * Use pyhon3-sphinx instead of python-sphinx for building html docs
(LP: #1845808)
- [Packaging] Update sphinx build dependencies to python3 packages

  * Add bpftool to linux-tools-common (LP: #1774815)
- [Debian] Enable bpftool in linux-tools

  * Miscellaneous Ubuntu changes
- update dkms package versions

  [ Ubuntu: 5.3.0-18.19 ]

  * eoan/linux: 5.3.0-18.19 -proposed tracker (LP: #1847298)
  * Enable the Dragonboards out of Eoan/master arm64 kernel (LP: #1846704)
- [Packaging] arm64: snapdragon: introduce a snapdragon flavour
- [Packaging] arm64: snapdragon: switch kernel format to Image
- [Config] arm64: snapdragon: CONFIG_PINCTRL_MSM8916=y
- [Config] arm64: snapdragon: CONFIG_PINCTRL_MSM8994=y
- [Config] arm64: snapdragon: CONFIG_PINCTRL_MSM8996=y
- [Config] arm64: snapdragon: CONFIG_PINCTRL_MSM8998=y
- [Config] arm64: snapdragon: CONFIG_REGULATOR_QCOM_RPMH=y
- [Config] arm64: snapdragon: CONFIG_QCOM_BAM_DMA=y
- [Config] arm64: snapdragon: CONFIG_QCOM_HIDMA_MGMT=y
- [Config] arm64: snapdragon: CONFIG_QCOM_HIDMA=y
- [Config] arm64: snapdragon: CONFIG_COMMON_CLK_QCOM=y
- [Config] arm64: snapdragon: CONFIG_QCOM_CLK_RPMH=y
- [Config] arm64: snapdragon: CONFIG_MSM_GCC_8916=y
- [Config] arm64: snapdragon: CONFIG_MSM_GCC_8994=y
- [Config] arm64: snapdragon: CONFIG_MSM_MMCC_8996=y
- [Config] arm64: snapdragon: CONFIG_MSM_GCC_8998=y
- [Config] arm64: snapdragon: CONFIG_HWSPINLOCK_QCOM=y
- [Config] arm64: snapdragon: CONFIG_QCOM_APCS_IPC=y
- [Config] arm64: snapdragon: CONFIG_RPMSG_QCOM_GLINK_RPM=y
- [Config] arm64: snapdragon: CONFIG_QCOM_GENI_SE=y
- [Config] arm64: snapdragon: CONFIG_QCOM_SMEM=y
- [Config] arm64: snapdragon: CONFIG_QCOM_SMD_RPM=y
- [Config] arm64: snapdragon: CONFIG_QCOM_SMP2P=y
- [Config] arm64: snapdragon: CONFIG_QCOM_SMSM=y
- [Config] arm64: snapdragon: CONFIG_QCOM_QFPROM=y
- [Config] arm64: snapdragon: CONFIG_SERIAL_QCOM_GENI=y
- [Config] arm64: snapdragon: CONFIG_QCOM_TSENS=y
- [Config] arm64: snapdragon: CONFIG_REGULATOR_QCOM_SMD_RPM=y
- [Config] arm64: snapdragon: CONFIG_QCOM_CLK_SMD_RPM=y
- [Config] arm64: snapdragon: CONFIG_RPMSG_QCOM_SMD=y
- [Config] arm64: snapdragon: CONFIG_MFD_QCOM_RPM=y
- [Config] arm64: snapdragon: CONFIG_SCSI_UFSHCD=y
- [Config] arm64: snapdragon: CONFIG_SCSI_UFSHCD_PLATFORM=y
- [Config] arm64: snapdragon: CONFIG_SCSI_UFS_HISI=y
- [Config] arm64: snapdragon: CONFIG_MMC_SDHCI=y
- [Config] arm64: snapdragon: CONFIG_MMC_SDHCI_PLTFM=y
- [Config] arm64: snapdragon: CONFIG_MMC_SDHCI_MSM=y
- [Config] arm64: snapdragon: CONFIG_REGULATOR_QCOM_SPMI=y
- [Config] arm64: snapdragon: CONFIG_PINCTRL_QCOM_SPMI_PMIC=y
- [Config] arm64: snapdragon: CONFIG_PHY_QCOM_USB_HS=y
- [Config] arm64: snapdragon: CONFIG_PHY_QCOM_QMP=y
- [Config] arm64: snapdragon: CONFIG_PHY_QCOM_UFS=y
- [Config] arm64: snapdragon: CONFIG_PHY_QCOM_USB_HSIC=y
- [Config] arm64: snapdragon: CONFIG_USB_CHIPIDEA_OF=y
- [Config] arm64: snapdragon: CONFIG_USB_EHCI_HCD_PLATFORM=y
- [Config] arm64: snapdragon: CONFIG_EXTCON_USB_GPIO=y
- [Config] arm64: snapdragon: CONFIG_REGULATOR_FIXED_VOLTAGE=y
- [Config] arm64: snapdragon: CONFIG_LEDS_GPIO=y
- [Config] arm64: snapdragon: CONFIG_USB_HSIC_USB3503=y
- [Config] arm64: snapdragon: CONFIG_USB_NET_DRIVERS=y
- [Config] arm64: snapdragon: CONFIG_USB_OTG=y
- [Config] arm64: snapdragon: CONFIG_USB_XHCI_PLATFORM=y
- [Config] arm64: snapdragon: CONFIG_USB_OHCI_HCD_PLATFORM=y
- [Config] arm64: snapdragon: CONFIG_USB_MUSB_HDRC=y
- [Config] arm64: snapdragon: CONFIG_USB_DWC3=y
- [Config] arm64: snapdragon: CONFIG_USB_DWC3_PCI=y
- [Config] arm64: snapdragon: CONFIG_USB_DWC3_OF_SIMPLE=y
- [Config] arm64: snapdragon: CONFIG_USB_DWC3_QCOM=y
- [Config] arm64: snapdragon: CONFIG_LEDS_PWM=y
- [Config] arm64: snapdragon: CONFIG_LEDS_TRIGGER_HEARTBEAT=y
- [Config] arm64: snapdragon: CONFIG_LEDS_TRIGGER_DEFAULT_ON=y
- [Config] arm64: snapdragon: CONFIG_QCOM_A53PLL=y
- [Config] arm64: snapdragon: CONFIG_QCOM_CLK_APCS_MSM8916=y
- [Config] arm64: snapdragon: CONFIG_NLS_ISO8859_1=y
- [Config] arm64: snapdragon: CONFIG_USB_USBNET=y
- [Config] arm64: snapdragon: CONFIG_CRYPTO_DEV_QCOM_RNG=y
- [Config] arm64: snapdragon: CONFIG_POWER_RESET_QCOM_PON=y
- [Config] arm64: snapdragon: CONFIG_INPUT_PM8941_PWRKEY=y
- [Config] arm64: snapdragon: CONFIG_KEYBOARD_GPIO=y
- [Config] arm64: snapdragon: CONFIG_RTC_DRV_PM8XXX=y

 -- Paolo Pisati   Thu, 10 Oct 2019 11:14:34
+0200

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

-- 
You received this bug notification because you are a 

[Kernel-packages] [Bug 1847293] Re: eoan/linux-gcp: 5.3.0-1004.4 -proposed tracker

2019-10-12 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-gcp - 5.3.0-1004.4

---
linux-gcp (5.3.0-1004.4) eoan; urgency=medium

  * eoan/linux-gcp: 5.3.0-1004.4 -proposed tracker (LP: #1847293)

  * Use pyhon3-sphinx instead of python-sphinx for building html docs
(LP: #1845808)
- [Packaging] Update sphinx build dependencies to python3 packages

  [ Ubuntu: 5.3.0-18.19 ]

  * eoan/linux: 5.3.0-18.19 -proposed tracker (LP: #1847298)
  * Enable the Dragonboards out of Eoan/master arm64 kernel (LP: #1846704)
- [Packaging] arm64: snapdragon: introduce a snapdragon flavour
- [Packaging] arm64: snapdragon: switch kernel format to Image
- [Config] arm64: snapdragon: CONFIG_PINCTRL_MSM8916=y
- [Config] arm64: snapdragon: CONFIG_PINCTRL_MSM8994=y
- [Config] arm64: snapdragon: CONFIG_PINCTRL_MSM8996=y
- [Config] arm64: snapdragon: CONFIG_PINCTRL_MSM8998=y
- [Config] arm64: snapdragon: CONFIG_REGULATOR_QCOM_RPMH=y
- [Config] arm64: snapdragon: CONFIG_QCOM_BAM_DMA=y
- [Config] arm64: snapdragon: CONFIG_QCOM_HIDMA_MGMT=y
- [Config] arm64: snapdragon: CONFIG_QCOM_HIDMA=y
- [Config] arm64: snapdragon: CONFIG_COMMON_CLK_QCOM=y
- [Config] arm64: snapdragon: CONFIG_QCOM_CLK_RPMH=y
- [Config] arm64: snapdragon: CONFIG_MSM_GCC_8916=y
- [Config] arm64: snapdragon: CONFIG_MSM_GCC_8994=y
- [Config] arm64: snapdragon: CONFIG_MSM_MMCC_8996=y
- [Config] arm64: snapdragon: CONFIG_MSM_GCC_8998=y
- [Config] arm64: snapdragon: CONFIG_HWSPINLOCK_QCOM=y
- [Config] arm64: snapdragon: CONFIG_QCOM_APCS_IPC=y
- [Config] arm64: snapdragon: CONFIG_RPMSG_QCOM_GLINK_RPM=y
- [Config] arm64: snapdragon: CONFIG_QCOM_GENI_SE=y
- [Config] arm64: snapdragon: CONFIG_QCOM_SMEM=y
- [Config] arm64: snapdragon: CONFIG_QCOM_SMD_RPM=y
- [Config] arm64: snapdragon: CONFIG_QCOM_SMP2P=y
- [Config] arm64: snapdragon: CONFIG_QCOM_SMSM=y
- [Config] arm64: snapdragon: CONFIG_QCOM_QFPROM=y
- [Config] arm64: snapdragon: CONFIG_SERIAL_QCOM_GENI=y
- [Config] arm64: snapdragon: CONFIG_QCOM_TSENS=y
- [Config] arm64: snapdragon: CONFIG_REGULATOR_QCOM_SMD_RPM=y
- [Config] arm64: snapdragon: CONFIG_QCOM_CLK_SMD_RPM=y
- [Config] arm64: snapdragon: CONFIG_RPMSG_QCOM_SMD=y
- [Config] arm64: snapdragon: CONFIG_MFD_QCOM_RPM=y
- [Config] arm64: snapdragon: CONFIG_SCSI_UFSHCD=y
- [Config] arm64: snapdragon: CONFIG_SCSI_UFSHCD_PLATFORM=y
- [Config] arm64: snapdragon: CONFIG_SCSI_UFS_HISI=y
- [Config] arm64: snapdragon: CONFIG_MMC_SDHCI=y
- [Config] arm64: snapdragon: CONFIG_MMC_SDHCI_PLTFM=y
- [Config] arm64: snapdragon: CONFIG_MMC_SDHCI_MSM=y
- [Config] arm64: snapdragon: CONFIG_REGULATOR_QCOM_SPMI=y
- [Config] arm64: snapdragon: CONFIG_PINCTRL_QCOM_SPMI_PMIC=y
- [Config] arm64: snapdragon: CONFIG_PHY_QCOM_USB_HS=y
- [Config] arm64: snapdragon: CONFIG_PHY_QCOM_QMP=y
- [Config] arm64: snapdragon: CONFIG_PHY_QCOM_UFS=y
- [Config] arm64: snapdragon: CONFIG_PHY_QCOM_USB_HSIC=y
- [Config] arm64: snapdragon: CONFIG_USB_CHIPIDEA_OF=y
- [Config] arm64: snapdragon: CONFIG_USB_EHCI_HCD_PLATFORM=y
- [Config] arm64: snapdragon: CONFIG_EXTCON_USB_GPIO=y
- [Config] arm64: snapdragon: CONFIG_REGULATOR_FIXED_VOLTAGE=y
- [Config] arm64: snapdragon: CONFIG_LEDS_GPIO=y
- [Config] arm64: snapdragon: CONFIG_USB_HSIC_USB3503=y
- [Config] arm64: snapdragon: CONFIG_USB_NET_DRIVERS=y
- [Config] arm64: snapdragon: CONFIG_USB_OTG=y
- [Config] arm64: snapdragon: CONFIG_USB_XHCI_PLATFORM=y
- [Config] arm64: snapdragon: CONFIG_USB_OHCI_HCD_PLATFORM=y
- [Config] arm64: snapdragon: CONFIG_USB_MUSB_HDRC=y
- [Config] arm64: snapdragon: CONFIG_USB_DWC3=y
- [Config] arm64: snapdragon: CONFIG_USB_DWC3_PCI=y
- [Config] arm64: snapdragon: CONFIG_USB_DWC3_OF_SIMPLE=y
- [Config] arm64: snapdragon: CONFIG_USB_DWC3_QCOM=y
- [Config] arm64: snapdragon: CONFIG_LEDS_PWM=y
- [Config] arm64: snapdragon: CONFIG_LEDS_TRIGGER_HEARTBEAT=y
- [Config] arm64: snapdragon: CONFIG_LEDS_TRIGGER_DEFAULT_ON=y
- [Config] arm64: snapdragon: CONFIG_QCOM_A53PLL=y
- [Config] arm64: snapdragon: CONFIG_QCOM_CLK_APCS_MSM8916=y
- [Config] arm64: snapdragon: CONFIG_NLS_ISO8859_1=y
- [Config] arm64: snapdragon: CONFIG_USB_USBNET=y
- [Config] arm64: snapdragon: CONFIG_CRYPTO_DEV_QCOM_RNG=y
- [Config] arm64: snapdragon: CONFIG_POWER_RESET_QCOM_PON=y
- [Config] arm64: snapdragon: CONFIG_INPUT_PM8941_PWRKEY=y
- [Config] arm64: snapdragon: CONFIG_KEYBOARD_GPIO=y
- [Config] arm64: snapdragon: CONFIG_RTC_DRV_PM8XXX=y

  [ Ubuntu: 5.3.0-17.18 ]

  * eoan/linux: 5.3.0-17.18 -proposed tracker (LP: #1846641)
  * CVE-2019-17056
- nfc: enforce CAP_NET_RAW for raw sockets
  * CVE-2019-17055
- mISDN: enforce CAP_NET_RAW for raw sockets
  * CVE-2019-17054
- appletalk: enforce CAP_NET_RAW for raw sockets
  * CVE-2019-17053
- ieee802154: enforce CAP_NET_RAW for raw sockets
  

[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed

2019-10-12 Thread vmc
as of 10/12/2019 eoan 19.10, Ubuntu, Lubuntu, Xubuntu still have this
issue.

What I do to "fix" it is change:

COMPRESS=lz4, to COMPRESS=gzip, @:

/etc/initramfs-tools/initramfs.conf,  then

 sudo update-initramfs -u.

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

Title:
  initramfs unpacking failed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  "initramfs unpacking failed: Decoding failed",  message appears on
  boot up.

  If I "update-initramfs" using gzip instead of lz, then boot up passes
  without decoding failed message.

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

-- 
Mailing list: https://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 1847291] Re: eoan/linux-aws: 5.3.0-1003.3 -proposed tracker

2019-10-12 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1847298
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
- phase: Testing
- phase-changed: Saturday, 12. October 2019 09:45 UTC
+ phase: Ready for Testing
+ phase-changed: Sunday, 13. October 2019 02:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  eoan/linux-aws: 5.3.0-1003.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux-aws source package in Eoan:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1847298
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Ready for Testing
  phase-changed: Sunday, 13. October 2019 02:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847291/+subscriptions

-- 
Mailing list: https://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 1847292] Re: eoan/linux-azure: 5.3.0-1003.3 -proposed tracker

2019-10-12 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** Changed in: kernel-sru-workflow/promote-to-release
   Status: New => Confirmed

** Tags removed: block-proposed-eoan

** Tags removed: block-proposed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1847298
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Testing
- phase-changed: Friday, 11. October 2019 23:25 UTC
+ phase: Ready for Signoff
+ phase-changed: Sunday, 13. October 2019 02:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
+   promote-to-release: Pending -- ready to copy
stakeholder-signoff: Stalled -- waiting for signoff
  variant: debs

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

Title:
  eoan/linux-azure: 5.3.0-1003.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-azure source package in Eoan:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1847298
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Signoff
  phase-changed: Sunday, 13. October 2019 02:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-release: Pending -- ready to copy
stakeholder-signoff: Stalled -- waiting for signoff
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847292/+subscriptions

-- 
Mailing list: https://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 1847293] Re: eoan/linux-gcp: 5.3.0-1004.4 -proposed tracker

2019-10-12 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/promote-to-release
   Status: New => Confirmed

** Tags removed: block-proposed-eoan

** Tags removed: block-proposed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1847298
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
- phase: Ready for Testing
- phase-changed: Saturday, 12. October 2019 13:45 UTC
+ phase: Ready for Promote to Release
+ phase-changed: Sunday, 13. October 2019 02:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Ongoing -- testing in progress
+   promote-to-release: Pending -- ready to copy
  variant: debs

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

Title:
  eoan/linux-gcp: 5.3.0-1004.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Confirmed
Status in linux-gcp source package in Eoan:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1847298
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Ready for Promote to Release
  phase-changed: Sunday, 13. October 2019 02:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-release: Pending -- ready to copy
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847293/+subscriptions

-- 
Mailing list: https://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 1847293] Re: eoan/linux-gcp: 5.3.0-1004.4 -proposed tracker

2019-10-12 Thread Seth Forshee
** Tags added: regression-testing-passed

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

Title:
  eoan/linux-gcp: 5.3.0-1004.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Confirmed
Status in linux-gcp source package in Eoan:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1847298
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Ready for Promote to Release
  phase-changed: Sunday, 13. October 2019 02:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-release: Pending -- ready to copy
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847293/+subscriptions

-- 
Mailing list: https://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 1847292] Re: eoan/linux-azure: 5.3.0-1003.3 -proposed tracker

2019-10-12 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1847298
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Friday, 11. October 2019 23:25 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
-   regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Stalled -- waiting for signoff
  variant: debs

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

Title:
  eoan/linux-azure: 5.3.0-1003.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-azure source package in Eoan:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1847298
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Signoff
  phase-changed: Sunday, 13. October 2019 02:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-release: Pending -- ready to copy
stakeholder-signoff: Stalled -- waiting for signoff
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847292/+subscriptions

-- 
Mailing list: https://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 1847292] Re: eoan/linux-azure: 5.3.0-1003.3 -proposed tracker

2019-10-12 Thread Seth Forshee
** Tags added: regression-testing-passed

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

Title:
  eoan/linux-azure: 5.3.0-1003.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-azure source package in Eoan:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1847298
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Signoff
  phase-changed: Sunday, 13. October 2019 02:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-release: Pending -- ready to copy
stakeholder-signoff: Stalled -- waiting for signoff
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847292/+subscriptions

-- 
Mailing list: https://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 1722478] Re: Two-finger scrolling and click-and-drag no longer works after resuming from suspend

2019-10-12 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: kmod (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/1722478

Title:
  Two-finger scrolling and click-and-drag no longer works after resuming
  from suspend

Status in Linux:
  Confirmed
Status in kmod package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I own a Thinkpad T440p onto which I have had Debian 9 running without
  hardware issues. I have recently installed Ubuntu 17.10 final beta to
  test it out, but two-finger scrolling does not work at the moment. It
  used to work out-of-the-box from the final beta iso, but a subsequent
  update broke it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ghislain  10620 F pulseaudio
   /dev/snd/controlC0:  ghislain  10620 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 10 09:20:01 2017
  HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e
  InstallationDate: Installed on 2017-10-05 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: LENOVO 20AN00C1UK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic 
root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET83WW (2.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AN00C1UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440p
  dmi.product.name: 20AN00C1UK
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1722478] Re: Two-finger scrolling and click-and-drag no longer works after resuming from suspend

2019-10-12 Thread ljetibo
ThinkPad T580, trying to fix random secondary mouse button click events
had me try out the xinput-xwe-18.04 package when I noticed the same
problem. Randomly timed middle button clicks had not gone away.

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

Title:
  Two-finger scrolling and click-and-drag no longer works after resuming
  from suspend

Status in Linux:
  Confirmed
Status in kmod package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I own a Thinkpad T440p onto which I have had Debian 9 running without
  hardware issues. I have recently installed Ubuntu 17.10 final beta to
  test it out, but two-finger scrolling does not work at the moment. It
  used to work out-of-the-box from the final beta iso, but a subsequent
  update broke it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ghislain  10620 F pulseaudio
   /dev/snd/controlC0:  ghislain  10620 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 10 09:20:01 2017
  HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e
  InstallationDate: Installed on 2017-10-05 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: LENOVO 20AN00C1UK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic 
root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET83WW (2.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AN00C1UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440p
  dmi.product.name: 20AN00C1UK
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1847290] Re: eoan/linux-raspi2: 5.3.0-1007.8 -proposed tracker

2019-10-12 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/promote-to-release
   Status: New => Confirmed

** Tags removed: block-proposed-eoan

** Tags removed: block-proposed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1847298
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
- phase: Testing
- phase-changed: Friday, 11. October 2019 21:41 UTC
+ phase: Ready for Promote to Release
+ phase-changed: Saturday, 12. October 2019 23:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
+   promote-to-release: Pending -- ready to copy
  variant: debs

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

Title:
  eoan/linux-raspi2: 5.3.0-1007.8 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Confirmed
Status in linux-raspi2 source package in Eoan:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1847298
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Ready for Promote to Release
  phase-changed: Saturday, 12. October 2019 23:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-release: Pending -- ready to copy
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847290/+subscriptions

-- 
Mailing list: https://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 1654448] Re: Dell XPS 13 9350/9360 headphone audio hiss

2019-10-12 Thread Ionut Negru
The same happen with my XPS 13. Since a couple of days I have noticed
this annoying hiss. I use Ubuntu 19.04.

The workaround also fixes the issue for me (amixer -c 0 set 'Headphone
Mic Boost',0 1)

Regards

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

Title:
  Dell XPS 13 9350/9360 headphone audio hiss

Status in Dell Sputnik:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+subscriptions

-- 
Mailing list: https://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 1840571] Re: ubuntu 18.04.3 startup purple screen blink and could not start with kernel 5.0.0+

2019-10-12 Thread Seiichi Nakashima
Today I resetup parttion sda1 to use backup at amd pc(AMD Athlon(tm) II X2 250).
I restart PC, purple screen blink occur many times.

when start normal timing, I use update-grub commad to set up grub environment.
and select Ubuntu, with Linux 5.0.0-27-generic(recovery mode) start PC normal.

I cannot understand what case to occur purple screen blink,
and recovery it.

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

Title:
  ubuntu 18.04.3 startup purple screen blink and could not start with
  kernel 5.0.0+

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I update ubuntu by software-updater.
  I update kernel 5.0.0-25, and reboot ubuntu system,
  but startup purple screen blink for ever,and could not login.
  I reboot kernel 5.0.0-23(before kernel), and login.

  as kernel 5.0.0-23, sometime same event occured,
  but I reset PC, next time restart normaly.

  I upload syslog file.

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2019-05-31 (83 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190421)
  Package: gnome-shell 3.28.4-0ubuntu18.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
  Tags: bionic third-party-packages
  Uname: Linux 5.0.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-05-31 (86 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190421)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 5.3.0-050300rc6-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-05-31 (89 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190421)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 5.3.0-050300rc6-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1355 F pulseaudio
   /dev/snd/controlC1:  nakasima   1355 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-05-31 (93 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190421)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic 
root=UUID=1c4b1b7d-1ae2-412e-ac5e-dca7d317b129 ro ipv6.disable=1 quiet splash 
ipv6.disable=1 vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-27-generic N/A
   linux-backports-modules-5.0.0-27-generic  N/A
   linux-firmware1.173.9
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.0.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/18/2010
  

[Kernel-packages] [Bug 1847711] Re: Move zsys tags from org.zsys to com.ubuntu.zsys

2019-10-12 Thread Launchpad Bug Tracker
This bug was fixed in the package grubzfs-testsuite - 0.4.5

---
grubzfs-testsuite (0.4.5) eoan; urgency=medium

  * Move our identifier to com.ubuntu
As we are not going to own org.zsys, move our identifier under
com.ubuntu.zsys (LP: #1847711)

 -- Didier Roche   Fri, 11 Oct 2019 15:55:19 +0200

** Changed in: grubzfs-testsuite (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: grub2 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Move zsys tags from org.zsys to com.ubuntu.zsys

Status in grub2 package in Ubuntu:
  Fix Released
Status in grubzfs-testsuite package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zsys package in Ubuntu:
  Fix Released

Bug description:
  As we are not going to own in the end org.zsys, move our identifier
  tags to com.ubuntu.zsys.

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

-- 
Mailing list: https://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 1847711] Re: Move zsys tags from org.zsys to com.ubuntu.zsys

2019-10-12 Thread Launchpad Bug Tracker
This bug was fixed in the package grub2 - 2.04-1ubuntu12

---
grub2 (2.04-1ubuntu12) eoan; urgency=medium

  * Move our identifier to com.ubuntu
As we are not going to own org.zsys, move our identifier under
com.ubuntu.zsys (LP: #1847711)

 -- Didier Roche   Fri, 11 Oct 2019 15:57:47 +0200

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

Title:
  Move zsys tags from org.zsys to com.ubuntu.zsys

Status in grub2 package in Ubuntu:
  Fix Released
Status in grubzfs-testsuite package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zsys package in Ubuntu:
  Fix Released

Bug description:
  As we are not going to own in the end org.zsys, move our identifier
  tags to com.ubuntu.zsys.

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

-- 
Mailing list: https://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 1844962] Re: apparent memory usage regression - not getting freed?

2019-10-12 Thread Joe Barnett
patch update: https://lists.freedesktop.org/archives/amd-
gfx/2019-October/041187.html  (also see review in
https://lists.freedesktop.org/archives/amd-gfx/2019-October/041194.html)

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

Title:
  apparent memory usage regression - not getting freed?

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In eoan on a 5.3 kernel, have noticed a few incidents of the system
  becoming sluggish/unresponsive, which appears to be caused by low
  available memory.  top is reporting 13 of 16G are "used", but adding
  up the memory reported by top sorted by memory usage appears like it
  should be closer to 3-4G "used".

  Attaching two top screenshots, one shows 3.3G used and system behaving
  well, the other shows 14G used and system lagging.  In both cases,
  approximately the same programs are being run taking up approximately
  the same amount of resident memory, so not sure where all the memory
  usage is coming from.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-10-generic 5.3.0-10.11
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jbarnett   5046 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Sep 22 21:26:02 2019
  InstallationDate: Installed on 2019-08-17 (37 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai 
   Bus 001 Device 004: ID 27c6:5395 HTMicroelectronics Goodix Fingerprint 
Device 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9575
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-10-generic 
root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash 
usbcore.dyndbg=+p vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-10-generic N/A
   linux-backports-modules-5.3.0-10-generic  N/A
   linux-firmware1.182
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-09-18 (4 days ago)
  dmi.bios.date: 10/10/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.0
  dmi.board.name: 0N338G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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 1847801] Re: bionic/linux-oem: 4.15.0-1059.68 -proposed tracker

2019-10-12 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1846131
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Ready for Promote to Proposed
  phase-changed: Saturday, 12. October 2019 06:56 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Stalled -- ready for review
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1059.68 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1846131
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Ready for Promote to Proposed
  phase-changed: Saturday, 12. October 2019 06:56 UTC
  reason:
promote-to-proposed: Stalled -- ready for review
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847801/+subscriptions

-- 
Mailing list: https://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 1847711] Re: Move zsys tags from org.zsys to com.ubuntu.zsys

2019-10-12 Thread Launchpad Bug Tracker
This bug was fixed in the package zsys - 0.2.2

---
zsys (0.2.2) eoan; urgency=medium

  * Move identifier tags to com.ubuntu.zsys (LP: #1847711)

 -- Didier Roche   Fri, 11 Oct 2019 08:25:04 +0200

** Changed in: zsys (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Move zsys tags from org.zsys to com.ubuntu.zsys

Status in grub2 package in Ubuntu:
  Fix Committed
Status in grubzfs-testsuite package in Ubuntu:
  Fix Committed
Status in ubiquity package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zsys package in Ubuntu:
  Fix Released

Bug description:
  As we are not going to own in the end org.zsys, move our identifier
  tags to com.ubuntu.zsys.

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

-- 
Mailing list: https://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 1845454] Re: Kernel panic in tpm_ functions when booting kernel 5.3 in Ubuntu 19.10 (but 5.2 works)

2019-10-12 Thread Matthias Harter
Works for me, too. Thanks!

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

Title:
  Kernel panic in tpm_ functions when booting kernel 5.3 in Ubuntu 19.10
  (but 5.2 works)

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  SRU Justification

  Impact: Some systems are getting kernel panics during boot while
  parsing tpm event logs from the firmware. This happens only when the
  tpm and secure boot are both enabled in the firmware.

  Fix: 3 patches which are currently applied to the upstream EFI
  maintainer tree.

  Test Case: On an affected system, booting a 5.3-based kernel will
  panic during boot when the tpm and secure boot are enabled. A patched
  kernel will boot successfully. The patches have been verified to fix
  the issue on a gen 6 Lenovo X1 Carbon.

  Regression Potential: If the patches have bugs they could cause
  regressions on systems not currently experiencing issues. The patches
  are pretty straightforward though, so I believe the risk is minimal
  and (given the severity of the issue on affected hardware) acceptable.

  ---

  Image: http://cdimage.ubuntu.com/daily-live/20190926/eoan-desktop-amd64.iso
  Device: Dell XPS 13 7390 (201908-27305)

  When trying to start the live session ("try Ubuntu") or trying to
  install the ISO ("install Ubuntu"), the boot process stops within 1
  second with a kernel panic (see attached screenshot).

  The system could boot with a previous version of Eoan image:
  2019-09-09 09:11 (kernel 5.3.0-10)

  Workaround: disable TPM2 in the BIOS.

  /!\ Please note: the information below (and the attached file  
ProcCpuinfoMinimal.txt) come from a 18.04 live session, since I cannot boot 
anything with 19.10 beta image.
  ==
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: syslinux 3:6.03+dfsg1-2
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 26 07:41:16 2019
  Dependencies:
   gcc-8-base 8.3.0-6ubuntu1~18.04.1
   libc6 2.27-3ubuntu1
   libgcc1 1:8.3.0-6ubuntu1~18.04.1
   mtools 4.0.18-2ubuntu1
   syslinux-common 3:6.03+dfsg1-2
  LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: syslinux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1842865] Re: Xubuntu 18.04 sometimes freezes when turned on on logo

2019-10-12 Thread Maxim Smih
** Description changed:

  Sometimes, when I turn off the computer, it hangs on the logo. I can not
  turn off the computer using alt + SysRq + REISUO. The light on the
  system unit continues to light, and the fan runs. This is a problem with
- kernel 5.0, 5.3
+ kernel 5.0, 5.3.
+ 
+ There is no such problem with the 4.15 kernel. It happens that after 90
+ seconds it turns off. And with a new core, he writes that he will turn
+ off after 90 seconds, but he will not turn off.
  
  Here is the error:
  info: task systemd shutdown:1 blocked for more than 120 seconds
  Not tainted 5.0.0-20-generic #21-Ubuntu
  «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message
  
  https://ibb.co/PcYvDLq
  https://ibb.co/4JMGwvC
  
  sudo dmesg|grep ACPI|less -  https://pastebin.com/PZxRGNyJ
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Пакет: gvfs 1.36.1-0ubuntu1.3.3
  ProcVersionSign ature: Ubuntu 5.0.0-27. 28 ~ 18,04. 1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Архитектура: amd64
  CurrentDesktop: XFCE
  Дата: Четверг 5 09:44:35 2019 Дата
  установки: установлено в 2019-08 -09 (26 дней назад)
  InstallationMedia: Xubuntu 18.04.2 LTS «Бионический бобр» - выпуск amd64 
(20190210)
  ProcEnviron:
   LANGUAGE = ru_UA: ru
   PATH = (пользовательский, нет пользователя)
   XDG_RUNTIME_ DIR = 
   LANG = ru_UA.UTF -8
   SHELL = / bin / bash
  SourcePackage: gvfs
  UpgradeStatus: журнал обновления отсутствует (возможно, новая установка)
  ---
  Тип проблемы: ошибка
  ApportVersion: 2.20.9-0ubuntu7.7
  Архитектура: amd64
  AudioDevicesInUse:
   КОМАНДА ДОСТУПА ПОЛЬЗОВАТЕЛЯ PID
   / dev / snd / controlC0: макс. 1055 F  pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Установлен 2019-08-09 (37 дней назад)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Выпуск amd64 
(20190210)
  IwConfig:
   enp0s25 без беспроводных расширений.
  
   enp7s4 нет беспроводных расширений.
  
   нет никаких беспроводных расширений.
  Тип машины: Hewlett-Packard HP Compaq dc5800 Microtower
  Пакет: Linux (не установлен)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE = / загрузки / vmlinuz- 4.15.0- 62-общий корень 
= UUID = 8c77fe78- d1d9-4452- aca0-eb1f844041 22 ро тихий всплеск vt.handoff = 1
  ProcVersionSign ature: Ubuntu 4.15.0- 62,69-родовое 4.15.18
  RelatedPackageV ersions:
   linux- restricted- modules- 4.15.0- 62-родовое N / A
   linux- backports- modules- 4.15.0 - 62-типовой N / A
   linux-прошивка 1.173.9
  RfKill:
  
  Теги: bionic
  Uname: Linux 4.15.0-62-generic x86_64
  UpgradeStatus: нет журнала обновления (возможно, новая установка)
  Группы пользователей: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 26.10.2015
  dmi. bios.vendor: Hewlett-Packard
  dmi.bios.version: 786F2 v01.60
  dmi.board. asset.tag: CZC8107S1Y
  dmi.board.name: 2820h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis. asset.tag: CZC8107S1Y
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: dmi: bvnHewlett- Packard: bvr786F2v01. 60: bd10 / 26/2015: 
svnHewlett- Packard:pnHPCompaqdc580 0Microtower: pvr: rvnHewlett- Packard: 
rn2820h: rvr: cvnHewlett- Packard: ct6: cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dvtwelet dv00 от компании HP
  :

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1842865

Title:
  Xubuntu 18.04 sometimes freezes when turned on on logo

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes, when I turn off the computer, it hangs on the logo. I can
  not turn off the computer using alt + SysRq + REISUO. The light on the
  system unit continues to light, and the fan runs. This is a problem
  with kernel 5.0, 5.3.

  There is no such problem with the 4.15 kernel. It happens that after
  90 seconds it turns off. And with a new core, he writes that he will
  turn off after 90 seconds, but he will not turn off.

  Here is the error:
  info: task systemd shutdown:1 blocked for more than 120 seconds
  Not tainted 5.0.0-20-generic #21-Ubuntu
  «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message

  https://ibb.co/PcYvDLq
  https://ibb.co/4JMGwvC

  sudo dmesg|grep ACPI|less -  https://pastebin.com/PZxRGNyJ

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Пакет: gvfs 1.36.1-0ubuntu1.3.3
  ProcVersionSign ature: Ubuntu 5.0.0-27. 28 ~ 18,04. 1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Архитектура: amd64
  CurrentDesktop: XFCE
  Дата: Четверг 5 09:44:35 2019 Дата
  установки: установлено в 2019-08 -09 (26 дней назад)
  InstallationMedia: Xubuntu 18.04.2 LTS «Бионический бобр» - выпуск amd64 
(20190210)
  ProcEnviron:
   LANGUAGE = ru_UA: ru
   PATH = (пользовательский, нет пользователя)
   XDG_RUNTIME_ DIR = 
   LANG = ru_UA.UTF -8
   SHELL = / 

[Kernel-packages] [Bug 1737934] Re: Samsung SM961 NVMe SSD randomly unmounts/loses connection/unavailable

2019-10-12 Thread Sebastian
Same problem with T470s and SAMSUNG MZVLW1T0HMLH-000L7

sqid : 0
cmdid: 0x18
status_field : 0x4004(INVALID_FIELD: A reserved coded value or an unsupported 
value in a defined field)
parm_err_loc : 0x2c
lba  : 0
nsid : 0
vs   : 0
cs   : 0
.

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

Title:
  Samsung SM961 NVMe SSD randomly unmounts/loses connection/unavailable

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Seems related to these bugs:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
  https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1682704
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748

  Problem:
  At seemingly random times my computer (brand new Lenovo Thinkpad T470) seems 
to lose access to the Samsung SM961 256GB SSD drive it has inside. When this 
happens the whole OS freezes up and when I try to power down I see a black 
terminal-like screen that prints the following errors:

  EXT4-fs error (device nvme0n1p2): ext4_find_entry:1431: inode #7471275
  (or #741278): comm gmain (or systemd-journal or ...): reading
  directory iblock 0

  This error seems to be repeated endlessly, though I've only let it go
  for a few minutes. No other errors are printed.

  This is the only drive it has.
  I don't know if this occurs in Windows too since I removed Windows and 
installed Ubuntu immediatly after updating the BIOS.

  Info:
  Distro: Ubuntu MATE 17.10

  sudo uname -r
  4.13.0-19-generic

  sudo nvme get-feature -f 0x0c -H /dev/nvme0 (with latency set to 250)
  get-feature:0xc (Autonomous Power State Transition), Current value:0x01
Autonomous Power State Transition Enable (APSTE): Enabled
Auto PST Entries.
Entry[ 0]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 1]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 2]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 3]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 4]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 5]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 6]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 7]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 8]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 9]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[10]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[11]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[12]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[13]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[14]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[15]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[16]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[17]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0

[Kernel-packages] [Bug 1844021] Re: Suspend stopped working from 4.4.0-157 onwards

2019-10-12 Thread diddly
keihengfeng, thank you, the new packages you made worked for me and
solved the suspend issue on the affected laptop.

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

Title:
  Suspend stopped working from 4.4.0-157 onwards

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading the kernel above 4.4.0-154, starting with 4.4.0-157,
  suspend does not work for me anymore. Never had such an issue in the
  last 6 years.

  This is the relevant output when suspend fails:
  [  328.25] PM: Suspending system (mem)
  [  328.288902] Suspending console(s) (use no_console_suspend to debug)
  [  328.289118] wlp1s0: deauthenticating from xx:xx:xx:xx:xx:xx by local 
choice (Reason: 3=DEAUTH_LEAVING)
  [  328.289209] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
  [  328.289570] sd 0:0:0:0: [sda] Synchronizing SCSI cache
  [  328.289600] sd 0:0:0:0: [sda] Stopping disk
  [  328.291700] sd 1:0:0:0: [sdb] Stopping disk
  [  328.312413] xhci_hcd :03:00.0: WARN: xHC save state timeout
  [  328.312456] suspend_common(): xhci_pci_suspend+0x0/0x70 returns -110
  [  328.312461] pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -110
  [  328.312465] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -110
  [  328.312483] PM: Device :03:00.0 failed to suspend async: error -110
  [  328.848109] PM: Some devices failed to suspend, or early wake event 
detected

  This is my relevant lspci -v output:

  03:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host 
Controller (prog-if 30 [XHCI])
   Subsystem: Samsung Electronics Co Ltd ASM1042 SuperSpeed USB Host Controller
   Flags: bus master, fast devsel, latency 0, IRQ 16
   Memory at f050 (64-bit, non-prefetchable) [size=32K]
   Capabilities: 
   Kernel driver in use: xhci_hcd

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

-- 
Mailing list: https://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 1847293] Re: eoan/linux-gcp: 5.3.0-1004.4 -proposed tracker

2019-10-12 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1847298
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
- phase: Testing
- phase-changed: Saturday, 12. October 2019 09:46 UTC
+ phase: Ready for Testing
+ phase-changed: Saturday, 12. October 2019 13:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  eoan/linux-gcp: 5.3.0-1004.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Confirmed
Status in linux-gcp source package in Eoan:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1847298
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Ready for Testing
  phase-changed: Saturday, 12. October 2019 13:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847293/+subscriptions

-- 
Mailing list: https://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 1846131] Re: bionic/linux: 4.15.0-66.75 -proposed tracker

2019-10-12 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Thursday, 03. October 2019 10:54 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1846110
bionic/linux-fips: bug 1846119
bionic/linux-gke-4.15: bug 1846114
bionic/linux-ibm-gt: bug 1846116
bionic/linux-kvm: bug 1846115
-   bionic/linux-oem: bug 1846106, bug 1847801
+   bionic/linux-oem: bug 1847801
bionic/linux-oracle: bug 1846118
bionic/linux-raspi2: bug 1846103
bionic/linux-snapdragon: bug 1846105
bionic/linux/pc-kernel: bug 1846099
bionic/linux/pc-lowlatency-kernel: bug 1846100
xenial/linux-azure: bug 1846123
xenial/linux-gcp: bug 1846126
xenial/linux-hwe: bug 1846130
  variant: debs

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

Title:
  bionic/linux: 4.15.0-66.75 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Thursday, 03. October 2019 10:54 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1846110
bionic/linux-fips: bug 1846119
bionic/linux-gke-4.15: bug 1846114
bionic/linux-ibm-gt: bug 1846116
bionic/linux-kvm: bug 1846115
bionic/linux-oem: bug 1847801
bionic/linux-oracle: bug 1846118
bionic/linux-raspi2: bug 1846103
bionic/linux-snapdragon: bug 1846105
bionic/linux/pc-kernel: bug 1846099
bionic/linux/pc-lowlatency-kernel: bug 1846100
xenial/linux-azure: bug 1846123
xenial/linux-gcp: bug 1846126
xenial/linux-hwe: bug 1846130
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846131/+subscriptions

-- 
Mailing list: https://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 1818547] Re: hid-sensor-hub spamming dmesg in 4.20

2019-10-12 Thread Nikita Koval
Also affects Dell XPS / Ubuntu Eoan 5.3.0-18-generic #19-Ubuntu

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

Title:
  hid-sensor-hub spamming dmesg in 4.20

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  [ 406.165461] hid-sensor-hub 001F:8086:22D8.0002: hid_field_extract() called 
with n (192) > 32! (kworker/5:1)

  [Fix]
  Let HID core allow longer input report length.

  [Test]
  User confirmed the fix works.

  [Regression Potential]
  Low. Longer input report length is now considered valid, shorter input
  report length doesn't get touched.

  === Original Bug Report ===

  Dmesg is a constant barrage of the same error:
  ```
  [  406.165461] hid-sensor-hub 001F:8086:22D8.0002: hid_field_extract() called 
with n (192) > 32! (kworker/5:1)
  ```

  This does not occur in 4.19 but does occur in all mainline 4.20
  releases including 4.20.13 (linux-image-unsigned-4.20.13-042013).
  Tested with both Ubuntu's included libinput 1.10 and an updated
  libinput 1.12.

  Hardware (from lspci) includes a synaptic touchpad. Having the xorg
  synaptic driver installed makes no difference.

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

-- 
Mailing list: https://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 1847292] Re: eoan/linux-azure: 5.3.0-1003.3 -proposed tracker

2019-10-12 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1847298
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Friday, 11. October 2019 23:25 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
-   stakeholder-signoff: Pending -- waiting for signoff
+   stakeholder-signoff: Stalled -- waiting for signoff
  variant: debs

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

Title:
  eoan/linux-azure: 5.3.0-1003.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-azure source package in Eoan:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1847298
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Friday, 11. October 2019 23:25 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Stalled -- waiting for signoff
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847292/+subscriptions

-- 
Mailing list: https://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 1847291] Re: eoan/linux-aws: 5.3.0-1003.3 -proposed tracker

2019-10-12 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Incomplete => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1847298
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
- phase: Promote to Proposed
- phase-changed: Friday, 11. October 2019 20:07 UTC
+ phase: Testing
+ phase-changed: Saturday, 12. October 2019 09:45 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
regression-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  eoan/linux-aws: 5.3.0-1003.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux-aws source package in Eoan:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1847298
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Saturday, 12. October 2019 09:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847291/+subscriptions

-- 
Mailing list: https://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 1847293] Re: eoan/linux-gcp: 5.3.0-1004.4 -proposed tracker

2019-10-12 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Incomplete => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1847298
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
- phase: Promote to Proposed
- phase-changed: Friday, 11. October 2019 20:54 UTC
+ phase: Testing
+ phase-changed: Saturday, 12. October 2019 09:46 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
regression-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  eoan/linux-gcp: 5.3.0-1004.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Confirmed
Status in linux-gcp source package in Eoan:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1847298
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Saturday, 12. October 2019 09:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847293/+subscriptions

-- 
Mailing list: https://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 1842265] Re: No sound inputs from the external microphone and headset on a Dell machine

2019-10-12 Thread Hui Wang
** Tags removed: verification-needed-bionic verification-needed-disco
** Tags added: verification-done-bionic verification-done-disco

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

Title:
  No sound inputs from the external microphone and headset on a Dell
  machine

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Invalid

Bug description:
  [Impact]
  When we plug an external mic/headset-mic, the system can't
  detect it and as a result can't record sound from it.

  [Fix]
  Apply an existing fixup to fix this issue.

  [Test Case]
  After applying the patch, plug an external mic or headset-mic,
  system can detect it and can record the sound from it too.

  
  [Regression Risk]
  Low. just add an existing fixup to this new machine.

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

-- 
Mailing list: https://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 1847291] Re: eoan/linux-aws: 5.3.0-1003.3 -proposed tracker

2019-10-12 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1847298
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Promote to Proposed
  phase-changed: Friday, 11. October 2019 20:07 UTC
  reason:
automated-testing: Stalled -- testing FAILED
-   promote-to-proposed: Stalled -- packages are in the wrong component
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
regression-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  eoan/linux-aws: 5.3.0-1003.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Incomplete
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux-aws source package in Eoan:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1847298
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Promote to Proposed
  phase-changed: Friday, 11. October 2019 20:07 UTC
  reason:
automated-testing: Stalled -- testing FAILED
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
regression-testing: Ongoing -- testing in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847291/+subscriptions

-- 
Mailing list: https://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 1847293] Re: eoan/linux-gcp: 5.3.0-1004.4 -proposed tracker

2019-10-12 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1847298
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Promote to Proposed
  phase-changed: Friday, 11. October 2019 20:54 UTC
  reason:
automated-testing: Ongoing -- testing in progress
-   promote-to-proposed: Stalled -- packages are in the wrong component
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
regression-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  eoan/linux-gcp: 5.3.0-1004.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Incomplete
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Confirmed
Status in linux-gcp source package in Eoan:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1847298
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Promote to Proposed
  phase-changed: Friday, 11. October 2019 20:54 UTC
  reason:
automated-testing: Ongoing -- testing in progress
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
regression-testing: Ongoing -- testing in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847293/+subscriptions

-- 
Mailing list: https://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 1844798] Re: [SRU][OEM-B]UBUNTU: SAUCE: enable adjusting brightness on some samsung OLED panels

2019-10-12 Thread Alex Tu
** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   Importance: Undecided => High

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

Title:
  [SRU][OEM-B]UBUNTU: SAUCE: enable adjusting brightness on some samsung
  OLED panels

Status in OEM Priority Project:
  New
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux-oem source package in Bionic:
  Fix Committed

Bug description:
  SRU justification:

  [Impact]
  OLED backlight is not supported by the current kernel.
  brightness can't be adjusted.

  [Fix]
  Fix max brightness value;
  Follow samsung panel's spec to enable dpcd and
  support adjusting brightness on OLED.

  [Test]
  Verified on several laptops, backlight on and brightness is adjusted.

  [Regression Potential]
  Medium, change is limited to specific hardware feature.
  Verified on no dpcd support laptops, no regression found yet.

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

-- 
Mailing list: https://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 1847838] Missing required logs.

2019-10-12 Thread 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 1847838

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

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

Title:
  [Ubuntu 19.10-regression] USB3.1 test failed on CFL-1S8

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

Bug description:
  Description:

  PLY02:~ # for i in `lspci | grep -i usb | awk '{print $1}'`;do lspci -s $i 
-v;done;
  00:14.0 USB controller: Intel Corporation C620 Series Chipset Family USB 3.0 
xHCI Controller (rev 03) (prog-if 30 [XHCI])
  Subsystem: Intel Corporation C620 Series Chipset Family USB 3.0 xHCI 
Controller
  Flags: bus master, medium devsel, latency 0, IRQ 34, NUMA node 0
  Memory at 3830 (64-bit, non-prefetchable) [size=64K]
  Capabilities: [70] Power Management version 2
  Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+
  Kernel driver in use: xhci_hcd

  PLY02:~ # lsusb -t'
  /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M --- 
1M
  |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M  
-- 1M and should use driver uas instead of usb-storage.
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
  |__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/5p, 480M
  |__ Port 1: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 
1.5M
  |__ Port 1: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 
1.5M
  |__ Port 5: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
  |__ Port 5: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M

  
  Target Kernel: TBD
  Target Release: 19.10

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

-- 
Mailing list: https://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 1847838] Re: [Ubuntu 19.10] USB3.1 test failed on CFL-1S8

2019-10-12 Thread quanxian
correct result, should be like this
linux-s5lz:~ # for i in `lspci | grep -i usb | awk '{print $1}'`;do lspci -s $i 
-v;done;
00:14.0 USB controller: Intel Corporation Device a36d (rev 10) (prog-if 30 
[XHCI])
Subsystem: Intel Corporation Device 7270
Flags: bus master, medium devsel, latency 0, IRQ 127
Memory at 9190 (64-bit, non-prefetchable) [size=64K]
Capabilities: [70] Power Management version 2
Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+
Capabilities: [90] Vendor Specific Information: Len=14 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

linux-s5lz:~ # lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 1M
|__ Port 5: Dev 2, If 0, Class=Mass Storage, Driver=uas, 1M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
|__ Port 2: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 2: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M

** Summary changed:

- [Ubuntu 19.10] USB3.1 test failed on CFL-1S8
+ [Ubuntu 19.10-regression] USB3.1 test failed on CFL-1S8

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

Title:
  [Ubuntu 19.10-regression] USB3.1 test failed on CFL-1S8

Status in intel:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Description:

  PLY02:~ # for i in `lspci | grep -i usb | awk '{print $1}'`;do lspci -s $i 
-v;done;
  00:14.0 USB controller: Intel Corporation C620 Series Chipset Family USB 3.0 
xHCI Controller (rev 03) (prog-if 30 [XHCI])
  Subsystem: Intel Corporation C620 Series Chipset Family USB 3.0 xHCI 
Controller
  Flags: bus master, medium devsel, latency 0, IRQ 34, NUMA node 0
  Memory at 3830 (64-bit, non-prefetchable) [size=64K]
  Capabilities: [70] Power Management version 2
  Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+
  Kernel driver in use: xhci_hcd

  PLY02:~ # lsusb -t'
  /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M --- 
1M
  |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M  
-- 1M and should use driver uas instead of usb-storage.
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
  |__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/5p, 480M
  |__ Port 1: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 
1.5M
  |__ Port 1: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 
1.5M
  |__ Port 5: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
  |__ Port 5: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M

  
  Target Kernel: TBD
  Target Release: 19.10

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

-- 
Mailing list: https://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 1847838] Re: [Ubuntu 19.10-regression] USB3.1 test failed on CFL-1S8

2019-10-12 Thread quanxian
19.04 doesn't have 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/1847838

Title:
  [Ubuntu 19.10-regression] USB3.1 test failed on CFL-1S8

Status in intel:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Description:

  PLY02:~ # for i in `lspci | grep -i usb | awk '{print $1}'`;do lspci -s $i 
-v;done;
  00:14.0 USB controller: Intel Corporation C620 Series Chipset Family USB 3.0 
xHCI Controller (rev 03) (prog-if 30 [XHCI])
  Subsystem: Intel Corporation C620 Series Chipset Family USB 3.0 xHCI 
Controller
  Flags: bus master, medium devsel, latency 0, IRQ 34, NUMA node 0
  Memory at 3830 (64-bit, non-prefetchable) [size=64K]
  Capabilities: [70] Power Management version 2
  Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+
  Kernel driver in use: xhci_hcd

  PLY02:~ # lsusb -t'
  /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M --- 
1M
  |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M  
-- 1M and should use driver uas instead of usb-storage.
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
  |__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/5p, 480M
  |__ Port 1: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 
1.5M
  |__ Port 1: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 
1.5M
  |__ Port 5: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
  |__ Port 5: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M

  
  Target Kernel: TBD
  Target Release: 19.10

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

-- 
Mailing list: https://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 1847838] [NEW] [Ubuntu 19.10-regression] USB3.1 test failed on CFL-1S8

2019-10-12 Thread quanxian
Public bug reported:

Description:

PLY02:~ # for i in `lspci | grep -i usb | awk '{print $1}'`;do lspci -s $i 
-v;done;
00:14.0 USB controller: Intel Corporation C620 Series Chipset Family USB 3.0 
xHCI Controller (rev 03) (prog-if 30 [XHCI])
Subsystem: Intel Corporation C620 Series Chipset Family USB 3.0 xHCI 
Controller
Flags: bus master, medium devsel, latency 0, IRQ 34, NUMA node 0
Memory at 3830 (64-bit, non-prefetchable) [size=64K]
Capabilities: [70] Power Management version 2
Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+
Kernel driver in use: xhci_hcd

PLY02:~ # lsusb -t'
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M --- 1M
|__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M  -- 
1M and should use driver uas instead of usb-storage.
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
|__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/5p, 480M
|__ Port 1: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 
1.5M
|__ Port 1: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 
1.5M
|__ Port 5: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 5: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M


Target Kernel: TBD
Target Release: 19.10

** Affects: intel
 Importance: Undecided
 Status: New

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


** Tags: intel-kernel-19.10

** Also 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/1847838

Title:
  [Ubuntu 19.10-regression] USB3.1 test failed on CFL-1S8

Status in intel:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Description:

  PLY02:~ # for i in `lspci | grep -i usb | awk '{print $1}'`;do lspci -s $i 
-v;done;
  00:14.0 USB controller: Intel Corporation C620 Series Chipset Family USB 3.0 
xHCI Controller (rev 03) (prog-if 30 [XHCI])
  Subsystem: Intel Corporation C620 Series Chipset Family USB 3.0 xHCI 
Controller
  Flags: bus master, medium devsel, latency 0, IRQ 34, NUMA node 0
  Memory at 3830 (64-bit, non-prefetchable) [size=64K]
  Capabilities: [70] Power Management version 2
  Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+
  Kernel driver in use: xhci_hcd

  PLY02:~ # lsusb -t'
  /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M --- 
1M
  |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M  
-- 1M and should use driver uas instead of usb-storage.
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
  |__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/5p, 480M
  |__ Port 1: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 
1.5M
  |__ Port 1: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 
1.5M
  |__ Port 5: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
  |__ Port 5: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M

  
  Target Kernel: TBD
  Target Release: 19.10

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

-- 
Mailing list: https://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 1846106] Re: bionic/linux-oem: 4.15.0-1058.67 -proposed tracker

2019-10-12 Thread Ubuntu Kernel Bot
*** This bug is a duplicate of bug 1847801 ***
https://bugs.launchpad.net/bugs/1847801

** This bug has been marked a duplicate of bug 1847801
   bionic/linux-oem: 4.15.0-1059.68 -proposed tracker

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

Title:
  bionic/linux-oem: 4.15.0-1058.67 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1846131
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Signoff
  phase-changed: Wednesday, 09. October 2019 13:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846106/+subscriptions

-- 
Mailing list: https://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 1847801] Re: bionic/linux-oem: 4.15.0-1059.68 -proposed tracker

2019-10-12 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-bionic

** Tags added: block-proposed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1846131
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
- phase: Holding before Promote to Proposed
- phase-changed: Saturday, 12. October 2019 04:21 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Saturday, 12. October 2019 06:56 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,meta:depwait,signed:depwait
- replaces: bug 1846106
+   promote-to-proposed: Pending -- ready for review
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1059.68 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1846131
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Ready for Promote to Proposed
  phase-changed: Saturday, 12. October 2019 06:56 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847801/+subscriptions

-- 
Mailing list: https://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 1847801] Re: bionic/linux-oem: 4.15.0-1059.68 -proposed tracker

2019-10-12 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1846131
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Holding before Promote to Proposed
  phase-changed: Saturday, 12. October 2019 04:21 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,meta:depwait,signed:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,meta:depwait,signed:depwait
  replaces: bug 1846106
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1059.68 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  kernel-stable-master-bug: 1846131
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Holding before Promote to Proposed
  phase-changed: Saturday, 12. October 2019 04:21 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,meta:depwait,signed:depwait
  replaces: bug 1846106
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847801/+subscriptions

-- 
Mailing list: https://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 1787857] Re: USB mouse cursor lags after random time of correct behaviour

2019-10-12 Thread Eric Detheridge
I encountered this recently under Ubuntu 16.04.5 with Linux
4.15.0-65-lowlatency with an AMD A8-3870k APU. In the most recent case
the machine was fine for nearly a week until I was reading a large
amount of data off a usb stick. By moving my mouse receiver to a USB 3.0
port I was able to make the mouse work normally again without having to
reboot.

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

Title:
  USB mouse cursor lags after random time of correct behaviour

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

Bug description:
  I installed Ubuntu Studio 18.04.1 LTS. After the first apt-get update I 
noticed the following behaviour:
  after havig logged in, my USB mouse works normally for about ten seconds, 
then the cursor starts lagging a lot which makes the mouse pretty much unusable.
  The last dmesg always contain lines these: (more in attached file)

  [<9e659b0c>] irq_default_primary_handler threaded 
[] usb_hcd_irq
  [<9e659b0c>] irq_default_primary_handler threaded 
[] _rtl_pci_interrupt [rtl_pci]
  Disabling IRQ #18

  Out of frustration & curiosity I disabled most autostart apps
  (Settings > Session ... > Autostart) and re-enabled them after
  rebooting. Since then I rarely encounter the lagging cursor. If I open
  Settings > Mouse & Touchpad and toggle any option on/off the cursor
  starts lagging.

  How can make the cursor work reliably?
  Some comment in dmesg mentions "irqpoll" boot option

  Ubuntu Studio 18.04.1
  4.15.0-20-lowlatency #21-Ubuntu SMP PREEMPT

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

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