[Kernel-packages] [Bug 1814744] Re: linux-gcp: 4.15.0-1028.29~16.04.1 -proposed tracker

2019-02-27 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  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: 1814726
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:19 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1028
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-gcp: 4.15.0-1028.29~16.04.1 -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:
  Invalid
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-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  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: 1814726
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:19 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1028
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

-- 
Mailing list: https://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 1814759] Re: linux-gcp: 4.18.0-1007.8 -proposed tracker

2019-02-27 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  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: 1814749
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:26 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-gcp: 4.18.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 certification-testing series:
  Invalid
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-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  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: 1814749
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:26 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

-- 
Mailing list: https://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 1814731] Re: linux-aws: 4.15.0-1033.35 -proposed tracker

2019-02-27 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  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: 1814726
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:15 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-aws: 4.15.0-1033.35 -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:
  Invalid
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-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  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: 1814726
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:15 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

-- 
Mailing list: https://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 1818025] Re: ethernet card not detected

2019-02-27 Thread Daniel van Vugt
** Package changed: alsa-driver (Ubuntu) => 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/1818025

Title:
  ethernet card not detected

Status in linux package in Ubuntu:
  New

Bug description:
  06:00.0 Network controller: Intel Corporation Wireless 3160 (rev 83)
  07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI 
Express Fast/Gigabit Ethernet controller (rev 07) Device: eth0 
-
Type:  Wired
Driver:r8169
State: unavailable
Default:   no
HW Address:28:F1:0E:27:81:D1

Capabilities:
  Carrier Detect:  yes
  Speed:   100 Mb/s

Wired Properties
  Carrier: off

  It does not see the ethernet controller card. I cannot use Wi-Fi anymore. 
Need it asap.
  Please help.
  Thank you in advance.

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

-- 
Mailing list: https://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 1818025] [NEW] ethernet card not detected

2019-02-27 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

06:00.0 Network controller: Intel Corporation Wireless 3160 (rev 83)
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI 
Express Fast/Gigabit Ethernet controller (rev 07) Device: eth0 
-
  Type:  Wired
  Driver:r8169
  State: unavailable
  Default:   no
  HW Address:28:F1:0E:27:81:D1

  Capabilities:
Carrier Detect:  yes
Speed:   100 Mb/s

  Wired Properties
Carrier: off

It does not see the ethernet controller card. I cannot use Wi-Fi anymore. Need 
it asap.
Please help.
Thank you in advance.

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

-- 
ethernet card not detected
https://bugs.launchpad.net/bugs/1818025
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 1818020] Missing required logs.

2019-02-27 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 1818020

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

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

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

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

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

Title:
  linux 4.18.0-16.17 ADT test failure with linux 4.18.0-16.17

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/amd64/l/linux/20190228_005729_c9941@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/i386/l/linux/20190227_214624_c9941@/log.gz

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

-- 
Mailing list: https://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 1818024] Re: linux-gcp 4.15.0-1028.29~16.04.1 ADT test failure with linux-gcp 4.15.0-1028.29~16.04.1

2019-02-27 Thread Khaled El Mously
2 failures that were pre-existing:

ubuntu_kernel_selftests.cpu-hotplug
ubuntu_kernel_selftests.seccomp

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

Title:
  linux-gcp 4.15.0-1028.29~16.04.1 ADT test failure with linux-gcp
  4.15.0-1028.29~16.04.1

Status in linux-gcp package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux-gcp/20190215_192509_f47b0@/log.gz

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

-- 
Mailing list: https://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 1818024] [NEW] linux-gcp 4.15.0-1028.29~16.04.1 ADT test failure with linux-gcp 4.15.0-1028.29~16.04.1

2019-02-27 Thread Khaled El Mously
Public bug reported:

Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux-gcp/20190215_192509_f47b0@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  linux-gcp 4.15.0-1028.29~16.04.1 ADT test failure with linux-gcp
  4.15.0-1028.29~16.04.1

Status in linux-gcp package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux-gcp/20190215_192509_f47b0@/log.gz

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

-- 
Mailing list: https://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 1818021] Re: linux-aws 4.15.0-1033.35 ADT test failure with linux-aws 4.15.0-1033.35

2019-02-27 Thread Khaled El Mously
Failures in:

ubuntu_kernel_selftests.seccomp
ubuntu_kernel_selftests.timers
ubuntu_kernel_selftests.memfd
ubuntu_kernel_selftests.net


All were failing previously too

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

Title:
  linux-aws 4.15.0-1033.35 ADT test failure with linux-aws
  4.15.0-1033.35

Status in linux-aws package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/linux-aws/20190227_142738_ce0f2@/log.gz

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

-- 
Mailing list: https://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 1818020] [NEW] linux 4.18.0-16.17 ADT test failure with linux 4.18.0-16.17

2019-02-27 Thread Khaled El Mously
Public bug reported:

Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/amd64/l/linux/20190228_005729_c9941@/log.gz
i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/i386/l/linux/20190227_214624_c9941@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  linux 4.18.0-16.17 ADT test failure with linux 4.18.0-16.17

Status in linux package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/amd64/l/linux/20190228_005729_c9941@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/i386/l/linux/20190227_214624_c9941@/log.gz

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

-- 
Mailing list: https://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 1818021] [NEW] linux-aws 4.15.0-1033.35 ADT test failure with linux-aws 4.15.0-1033.35

2019-02-27 Thread Khaled El Mously
Public bug reported:

Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/linux-aws/20190227_142738_ce0f2@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  linux-aws 4.15.0-1033.35 ADT test failure with linux-aws
  4.15.0-1033.35

Status in linux-aws package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/linux-aws/20190227_142738_ce0f2@/log.gz

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

-- 
Mailing list: https://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 1730782] Re: [Bug] [KNL] ~5x slowdown of application when attaching by perf on KNL

2019-02-27 Thread quanxian
** Description changed:

  Description:
  
  Workload slows down for default sampling cycles in KNL. There are some 
processing in perf that's single threaded and bottlenecked when number of cores 
really go up.
  A second issue is that things slow down when we issue
  perf record – workload
  vs
  perf record -a – workload
  
  Patch is submitted for review
  
  https://www.spinics.net/lists/kernel/msg2552460.html
  https://www.spinics.net/lists/kernel/msg2552461.html
  https://www.spinics.net/lists/kernel/msg2552462.html
  https://www.spinics.net/lists/kernel/msg2552463.html
  
- Target kernel: TBD
+ Target kernel: 5.2
  Target Release: 19.04

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

Title:
  [Bug] [KNL] ~5x slowdown of application when attaching by perf on KNL

Status in intel:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  Description:

  Workload slows down for default sampling cycles in KNL. There are some 
processing in perf that's single threaded and bottlenecked when number of cores 
really go up.
  A second issue is that things slow down when we issue
  perf record – workload
  vs
  perf record -a – workload

  Patch is submitted for review

  https://www.spinics.net/lists/kernel/msg2552460.html
  https://www.spinics.net/lists/kernel/msg2552461.html
  https://www.spinics.net/lists/kernel/msg2552462.html
  https://www.spinics.net/lists/kernel/msg2552463.html

  Target kernel: 5.2
  Target Release: 19.04

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

-- 
Mailing list: https://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 1816947] Re: [Dell XPS L321X] Touchpad not working after last apt-get upgrade

2019-02-27 Thread opensas
I installed the following deb files:

linux-headers-4.13.0-19_4.13.0-19.22_all.deb
linux-headers-4.13.0-19-generic_4.13.0-19.22_amd64.deb
linux-image-4.13.0-19-generic_4.13.0-19.22_amd64.deb
linux-image-extra-4.13.0-19-generic_4.13.0-19.22_amd64.deb

Now I'm running

$ uname -a
Linux bionic 4.13.0-19-generic #22-Ubuntu SMP Mon Dec 4 11:58:07 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

and the bug IS STILL present.

Any other idea?

BTW, perhaps this might help:

$ lsmod
Module  Size  Used by
ccm20480  3
rfcomm 77824  4
bnep   20480  2
snd_hda_codec_hdmi 49152  1
snd_hda_codec_realtek94208  1
snd_hda_codec_generic73728  1 snd_hda_codec_realtek
intel_rapl 20480  0
x86_pkg_temp_thermal16384  0
intel_powerclamp   16384  0
coretemp   16384  0
kvm_intel 200704  0
hid_generic16384  0
joydev 20480  0
kvm   581632  1 kvm_intel
irqbypass  16384  1 kvm
crct10dif_pclmul   16384  0
crc32_pclmul   16384  0
ghash_clmulni_intel16384  0
pcbc   16384  0
dell_laptop20480  0
snd_hda_intel  40960  3
aesni_intel   188416  2
snd_hda_codec 126976  4 
snd_hda_intel,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek
aes_x86_64 20480  1 aesni_intel
crypto_simd16384  1 aesni_intel
snd_hda_core   81920  5 
snd_hda_intel,snd_hda_codec,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek
snd_hwdep  20480  1 snd_hda_codec
glue_helper16384  1 aesni_intel
snd_pcm98304  4 
snd_hda_intel,snd_hda_codec,snd_hda_core,snd_hda_codec_hdmi
cryptd 24576  3 crypto_simd,ghash_clmulni_intel,aesni_intel
intel_cstate   20480  0
intel_rapl_perf16384  0
arc4   16384  2
snd_seq_midi   16384  0
iwldvm229376  0
snd_seq_midi_event 16384  1 snd_seq_midi
mac80211  778240  1 iwldvm
snd_rawmidi32768  1 snd_seq_midi
btusb  45056  0
btrtl  16384  1 btusb
wmi_bmof   16384  0
snd_seq65536  2 snd_seq_midi_event,snd_seq_midi
btbcm  16384  1 btusb
iwlwifi   249856  1 iwldvm
input_leds 16384  0
dell_wmi   16384  0
dell_smbios16384  2 dell_wmi,dell_laptop
dcdbas 16384  1 dell_smbios
sparse_keymap  16384  1 dell_wmi
btintel16384  1 btusb
serio_raw  16384  0
bluetooth 540672  31 btrtl,btintel,bnep,btbcm,rfcomm,btusb
snd_seq_device 16384  3 snd_seq,snd_rawmidi,snd_seq_midi
uvcvideo   90112  0
snd_timer  32768  2 snd_seq,snd_pcm
videobuf2_vmalloc  16384  1 uvcvideo
usbhid 49152  0
videobuf2_memops   16384  1 videobuf2_vmalloc
hid   118784  2 hid_generic,usbhid
ecdh_generic   24576  1 bluetooth
snd81920  17 
snd_hda_intel,snd_hwdep,snd_seq,snd_hda_codec,snd_timer,snd_rawmidi,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_seq_device,snd_hda_codec_realtek,snd_pcm
videobuf2_v4l2 24576  1 uvcvideo
cfg80211  610304  3 iwlwifi,mac80211,iwldvm
acpi_als   16384  0
videobuf2_core 40960  2 uvcvideo,videobuf2_v4l2
soundcore  16384  1 snd
mei_me 40960  0
lpc_ich24576  0
shpchp 36864  0
kfifo_buf  16384  1 acpi_als
mei98304  1 mei_me
videodev  176128  3 uvcvideo,videobuf2_core,videobuf2_v4l2
industrialio   69632  2 acpi_als,kfifo_buf
intel_smartconnect 16384  0
media  40960  2 uvcvideo,videodev
mac_hid16384  0
sch_fq_codel   20480  5
parport_pc 32768  0
ppdev  20480  0
lp 20480  0
parport49152  3 lp,parport_pc,ppdev
ip_tables  24576  0
x_tables   40960  1 ip_tables
autofs440960  2
i915 1798144  11
i2c_algo_bit   16384  1 i915
drm_kms_helper167936  1 i915
syscopyarea16384  1 drm_kms_helper
sysfillrect16384  1 drm_kms_helper
sysimgblt  16384  1 drm_kms_helper
ahci   36864  4
fb_sys_fops16384  1 drm_kms_helper
psmouse   147456  0
drm   356352  5 i915,drm_kms_helper
libahci32768  1 ahci
wmi24576  2 dell_wmi,wmi_bmof
video  40960  3 dell_wmi,dell_laptop,i915

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

Title:
  [Dell XPS L321X] Touchpad not working after last apt-get upgrade

Status in libinput pac

[Kernel-packages] [Bug 1605433] Re: [Dell Alienware 17 R3] FN+F11 Enable/Disable touchpad not working

2019-02-27 Thread Christopher M. Penalver
adin:

1) To clarify, when you first installed Ubuntu 16.04 were you able to
toggle the touchpad?

2) Have you tested any release older than 16.04?

3) To keep this relevant to upstream, one would want to periodically
check for, and test the latest mainline kernel (now 5.0-rc8) as it is
released. Could you please advise?

4) It wouldn't hurt to keep an updated BIOS as it helps to further root
cause (and security best practice).

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

Title:
  [Dell Alienware 17 R3] FN+F11 Enable/Disable touchpad not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The touchpad does not work as expected. It can't be enabled or
  disabled through FN+F11 combination.

  The light (in the pad) always turns on, regardless of its non
  functionality.

  The problem seems related to bug #1523738, and some say solution #24
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523738/comments/24)
  works, but it didn't for me.

  WORKAROUND: Executing the following via a terminal allows one to disable and 
enable the touchpad:
  xinput set-prop 13 "Device Enabled" 1
  xinput set-prop 13 "Device Enabled" 0

  But it only works if it is enabled from the beginning from the systems
  configuration GUI. If it is disabled, it doesn't do the expected
  behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.14
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Thu Jul 21 21:07:42 2016
  InstallationDate: Installed on 2016-07-03 (18 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-manager.release-upgrades: 
2016-07-16T11:29:07.694480
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adin   4247 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=c0bba13c-6fa5-4545-a7ee-cd58b1e6e3bd
  InstallationDate: Installed on 2016-07-03 (24 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Alienware Alienware 17 R3
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=dc6d8cac-eff1-4dce-97fd-949d7268d2d9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.2.3
  dmi.board.name: Alienware 17 R3
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.2.3:bd11/11/2015:svnAlienware:pnAlienware17R3:pvr1.2.3:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:
  dmi.product.name: Alienware 17 R3
  dmi.product.version: 1.2.3
  dmi.sys.vendor: Alienware

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

-- 
Mailing list: https://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 929244] Re: Cannot connect to wireless network in 12.04

2019-02-27 Thread Christopher M. Penalver
** No longer affects: linux (Ubuntu)

** Project changed: linux => linux (Ubuntu)

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

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

** Changed in: linux (Ubuntu)
 Remote watch: Linux Kernel Bug Tracker #42843 => None

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

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

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

Title:
  Cannot connect to wireless network in 12.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My wireless network is listed in Network Manager, but upon entering
  the password it tries to connect and then re-prompts for a password. I
  can connect fine in Ubuntu 10.10/Fedora 16.

  Steps to reproduce:
  1. Select wireless network in Network Manager (802.11g with WPA2 in my case)
  2. Watch the network icon animate while it tries to connect
  3. Dialog box re-prompts for password

  My wireless card details:

  01:08.0 Network controller: Ralink corp. RT2561/RT61 802.11g PCI
Subsystem: Linksys WMP54G v4.1
Flags: bus master, slow devsel, latency 32, IRQ 18
Memory at dbff8000 (32-bit, non-prefetchable) [size=32K]
Capabilities: 
Kernel driver in use: rt61pci
Kernel modules: rt61pci

  dmesg output immediately after connection failed:

  [  422.332069] wlan0: authenticate with 00:26:f2:05:ad:dc (try 1)
  [  422.334473] wlan0: authenticated
  [  422.348049] wlan0: associate with 00:26:f2:05:ad:dc (try 1)
  [  422.350844] wlan0: deauthenticated from 00:26:f2:05:ad:dc (Reason: 6)
  [  507.012093] wlan0: authenticate with 00:26:f2:05:ad:dc (try 1)
  [  507.015078] wlan0: authenticated
  [  507.017076] wlan0: failed to insert Dummy STA entry for the AP (error -17)

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

-- 
Mailing list: https://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 1043403] Re: Wireless not active during installation or after boot

2019-02-27 Thread Christopher M. Penalver
** No longer affects: linux (Ubuntu)

** Project changed: linux => linux (Ubuntu)

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

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

** Changed in: linux (Ubuntu)
 Remote watch: Linux Kernel Bug Tracker #46721 => None

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

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

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

Title:
  Wireless not active during installation or after boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The i386 has a  Ralink corp. RT2561/RT61 802.11g PCI wireless card.
  However, the installation process seems unable to use it to find any
  wireless networks, not even open networks.  Same goes after booting
  and trying manually.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 3.5.0-13.13-generic 3.5.3
  Uname: Linux 3.5.0-13-generic i686
  ApportVersion: 2.5.1-0ubuntu2
  Architecture: i386
  Date: Wed Aug 29 18:50:47 2012
  InstallCmdLine: file=/cdrom/preseed/lubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash --
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120828)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  AcpiTables:

  ApportVersion: 2.5.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   27.408464] init: lightdm main process (943) terminated with 
status 1
  DistroRelease: Ubuntu 12.10
  HibernationDevice: RESUME=UUID=2a0d5ff8-7854-49fd-91e2-be4326cfc418
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120828)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Packard Bell Computers International Packard Bell EasyNote
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-13-generic 
root=UUID=1e64a51f-2f5b-4d0f-bb43-88c03014c8b4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.5.0-13.13-generic 3.5.3
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-13-generic N/A
   linux-backports-modules-3.5.0-13-generic  N/A
   linux-firmware1.90
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: yes
  Tags:  quantal
  Uname: Linux 3.5.0-13-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: /08/0520
  dmi.bios.vendor: Insyde Software Corporation
  dmi.bios.version: R1.01
  dmi.board.asset.tag: 87654321
  dmi.board.name: NEC Versa Premium
  dmi.board.vendor: NEC COMPUTERS INTERNATIONAL
  dmi.board.version: 5a
  dmi.chassis.asset.tag: 12345678
  dmi.chassis.type: 5
  dmi.modalias: 
dmi:bvnInsydeSoftwareCorporation:bvrR1.01:bd/08/0520:svnPackardBellComputersInternational:pnPackardBellEasyNote:pvrPB42BD0291:rvnNECCOMPUTERSINTERNATIONAL:rnNECVersaPremium:rvr5a:cvn:ct5:cvrI:
  dmi.product.name: Packard Bell EasyNote
  dmi.product.version: PB42BD0291
  dmi.sys.vendor: Packard Bell Computers International

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

-- 
Mailing list: https://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 1814760] Re: linux-kvm: 4.18.0-1008.8 -proposed tracker

2019-02-27 Thread Brad Figg
** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  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: 1814749
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:28 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-kvm: 4.18.0-1008.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 certification-testing series:
  Invalid
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-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  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: 1814749
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:28 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

-- 
Mailing list: https://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 1814749] Re: linux: 4.18.0-16.17 -proposed tracker

2019-02-27 Thread Sean Feole
** Tags added: regression-testing-passed

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

Title:
  linux: 4.18.0-16.17 -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:
  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-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  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

  backports: bug 1814750 (linux-hwe), bug 1814751 (linux-hwe-edge), bug 1814752 
(linux-aws-edge), bug 1814754 (linux-gcp-edge), bug 1814761 (linux-azure-edge), 
bug 1817536 (bionic/linux-azure-edge)
  derivatives: bug 1816782 (linux-azure), bug 1814755 (linux-raspi2), bug 
1814757 (linux-aws), bug 1814759 (linux-gcp), bug 1814760 (linux-kvm)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:22 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

-- 
Mailing list: https://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 1814749] Re: linux: 4.18.0-16.17 -proposed tracker

2019-02-27 Thread Brad Figg
** 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
  
  backports: bug 1814750 (linux-hwe), bug 1814751 (linux-hwe-edge), bug 1814752 
(linux-aws-edge), bug 1814754 (linux-gcp-edge), bug 1814761 (linux-azure-edge), 
bug 1817536 (bionic/linux-azure-edge)
  derivatives: bug 1816782 (linux-azure), bug 1814755 (linux-raspi2), bug 
1814757 (linux-aws), bug 1814759 (linux-gcp), bug 1814760 (linux-kvm)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:22 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
-   regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux: 4.18.0-16.17 -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:
  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-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  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

  backports: bug 1814750 (linux-hwe), bug 1814751 (linux-hwe-edge), bug 1814752 
(linux-aws-edge), bug 1814754 (linux-gcp-edge), bug 1814761 (linux-azure-edge), 
bug 1817536 (bionic/linux-azure-edge)
  derivatives: bug 1816782 (linux-azure), bug 1814755 (linux-raspi2), bug 
1814757 (linux-aws), bug 1814759 (linux-gcp), bug 1814760 (linux-kvm)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:22 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

-- 
Mailing list: https://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 1814760] Re: linux-kvm: 4.18.0-1008.8 -proposed tracker

2019-02-27 Thread Sean Feole
** Tags added: regression-testing-passed

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

Title:
  linux-kvm: 4.18.0-1008.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 certification-testing series:
  Invalid
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-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  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: 1814749
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:28 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

-- 
Mailing list: https://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 1043403] [NEW] Wireless not active during installation or after boot

2019-02-27 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

The i386 has a  Ralink corp. RT2561/RT61 802.11g PCI wireless card.
However, the installation process seems unable to use it to find any
wireless networks, not even open networks.  Same goes after booting and
trying manually.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 3.5.0-13.13-generic 3.5.3
Uname: Linux 3.5.0-13-generic i686
ApportVersion: 2.5.1-0ubuntu2
Architecture: i386
Date: Wed Aug 29 18:50:47 2012
InstallCmdLine: file=/cdrom/preseed/lubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash --
InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120828)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
---
AcpiTables:

ApportVersion: 2.5.1-0ubuntu2
Architecture: i386
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
CurrentDmesg: [   27.408464] init: lightdm main process (943) terminated with 
status 1
DistroRelease: Ubuntu 12.10
HibernationDevice: RESUME=UUID=2a0d5ff8-7854-49fd-91e2-be4326cfc418
InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120828)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Packard Bell Computers International Packard Bell EasyNote
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-13-generic 
root=UUID=1e64a51f-2f5b-4d0f-bb43-88c03014c8b4 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.5.0-13.13-generic 3.5.3
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-13-generic N/A
 linux-backports-modules-3.5.0-13-generic  N/A
 linux-firmware1.90
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: yes
Tags:  quantal
Uname: Linux 3.5.0-13-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: /08/0520
dmi.bios.vendor: Insyde Software Corporation
dmi.bios.version: R1.01
dmi.board.asset.tag: 87654321
dmi.board.name: NEC Versa Premium
dmi.board.vendor: NEC COMPUTERS INTERNATIONAL
dmi.board.version: 5a
dmi.chassis.asset.tag: 12345678
dmi.chassis.type: 5
dmi.modalias: 
dmi:bvnInsydeSoftwareCorporation:bvrR1.01:bd/08/0520:svnPackardBellComputersInternational:pnPackardBellEasyNote:pvrPB42BD0291:rvnNECCOMPUTERSINTERNATIONAL:rnNECVersaPremium:rvr5a:cvn:ct5:cvrI:
dmi.product.name: Packard Bell EasyNote
dmi.product.version: PB42BD0291
dmi.sys.vendor: Packard Bell Computers International

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


** Tags: apport-bug apport-collected i386 iso-testing 
kernel-bug-exists-upstream needs-upstream-testing quantal
-- 
Wireless not active during installation or after boot
https://bugs.launchpad.net/bugs/1043403
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 929244] [NEW] Cannot connect to wireless network in 12.04

2019-02-27 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

My wireless network is listed in Network Manager, but upon entering the
password it tries to connect and then re-prompts for a password. I can
connect fine in Ubuntu 10.10/Fedora 16.

Steps to reproduce:
1. Select wireless network in Network Manager (802.11g with WPA2 in my case)
2. Watch the network icon animate while it tries to connect
3. Dialog box re-prompts for password

My wireless card details:

01:08.0 Network controller: Ralink corp. RT2561/RT61 802.11g PCI
Subsystem: Linksys WMP54G v4.1
Flags: bus master, slow devsel, latency 32, IRQ 18
Memory at dbff8000 (32-bit, non-prefetchable) [size=32K]
Capabilities: 
Kernel driver in use: rt61pci
Kernel modules: rt61pci

dmesg output immediately after connection failed:

[  422.332069] wlan0: authenticate with 00:26:f2:05:ad:dc (try 1)
[  422.334473] wlan0: authenticated
[  422.348049] wlan0: associate with 00:26:f2:05:ad:dc (try 1)
[  422.350844] wlan0: deauthenticated from 00:26:f2:05:ad:dc (Reason: 6)
[  507.012093] wlan0: authenticate with 00:26:f2:05:ad:dc (try 1)
[  507.015078] wlan0: authenticated
[  507.017076] wlan0: failed to insert Dummy STA entry for the AP (error -17)

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


** Tags: bot-comment bot-stop-nagging kernel-bug-exists-upstream kernel-da-key 
kernel-wifi needs-kernel-logs needs-upstream-testing precise regression-release
-- 
Cannot connect to wireless network in 12.04
https://bugs.launchpad.net/bugs/929244
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 1817912] Re: alsa-util.c: Function snd_pcm_avail() returns a value that is extraordinarily large: 370196 bytes (2098 мс).

2019-02-27 Thread Daniel van Vugt
** Also affects: pulseaudio (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: pulseaudio (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/1817912

Title:
  alsa-util.c: Function snd_pcm_avail() returns a value that is
  extraordinarily large: 370196 bytes (2098 мс).

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-utils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  An old issue with ALSA is still present in Ubuntu 16.04.6.
  The system became extraordinarily slow and hangs at total in around a minute 
while playing a music (around a few hours in my case).

  [15:38:51]
  [root@ThinkPad/var/log]#grep "alsa-sink-CX20751/2 Analog" syslog
  Feb 27 14:58:50 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Function snd_pcm_avail() returns a value that is extraordinarily 
large: 370196 bytes (2098 мс).
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Most likely this is a bug in the ALSA driver «snd_hda_intel». 
Please report this issue to the ALSA developers.
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: snd_pcm_dump():
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Soft volume PCM
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Control: PCM Playback Volume
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: min_dB: -51
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: max_dB: 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: resolution: 256
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Its setup is:
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   stream   : PLAYBACK
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   access   : MMAP_INTERLEAVED
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   format   : S16_LE
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   subformat: STD
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   channels : 2
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   rate : 44100
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   exact rate   : 44100 (44100/1)
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   msbits   : 16
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   buffer_size  : 16384
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   period_size  : 8192
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   period_time  : 185759
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   tstamp_mode  : ENABLE
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   tstamp_type  : MONOTONIC
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   period_step  : 1
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   avail_min: 15680
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   period_event : 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   start_threshold  : -1
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   stop_threshold   : 4611686018427387904
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   silence_threshold: 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   silence_size : 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   boundary : 4611686018427387904
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Slave: Hardware PCM card 1 'HDA Intel PCH' device 0 subdevice 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Its setup is:
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   stream   : PLAYBACK
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   access   : MMAP_INTERLEAVED
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:

[Kernel-packages] [Bug 1817038] Re: linux-azure: 4.15.0-1040.44 -proposed tracker

2019-02-27 Thread Brad Figg
** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  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: 1814726
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
-   regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.15.0-1040.44 -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:
  Invalid
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-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  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: 1814726
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

-- 
Mailing list: https://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 1817038] Re: linux-azure: 4.15.0-1040.44 -proposed tracker

2019-02-27 Thread Sean Feole
** 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/1817038

Title:
  linux-azure: 4.15.0-1040.44 -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:
  Invalid
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-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  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: 1814726
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

-- 
Mailing list: https://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 1652504] Re: Recent updates broke Ubuntu on Raspberry Pi 3

2019-02-27 Thread Chris E
*** This bug is a duplicate of bug 1652270 ***
https://bugs.launchpad.net/bugs/1652270

As of upgrading between 16.04 and 18.04.2 the fdt_addr has changed
again, I was able to fix this via the following, first cat boot.scr on
the primary partition, there's a bunch of binary at the start of the
file followed by fdt_addr_r 0x0300

Use that as the base value on config.txt:

device_tree_address=0x0300

You do not need to set device_tree_end, this got the pi booting again.

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

Title:
  Recent updates broke Ubuntu on Raspberry Pi 3

Status in flash-kernel package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  I've been running Raspberry Pi 3 with Ubuntu as described here 
https://wiki.ubuntu.com/ARM/RaspberryPi

  I've installed Ubuntu 16.04 and then upgraded to 16.10 and have been
  using this setup successfully since October up until last week.
  Unfortunately one of the latest kernel updates broke the installation
  and I found out the same happened for Ubuntu 16.04 LTS - and therefore
  I can no longer run up-to-date Ubuntu installation (with updated
  kernel) on my RPI.

  I am getting this error:
  Error image is not a fdt - must reset the board to recover

  I also tried this but it didn't help me:
  https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=168838

  Now I know running Ubuntu on RPI3 this way is not officially
  supported, but since Ubuntu Snappy is supported I thought someone here
  could know what is going on.

  Thank you very much.

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

-- 
Mailing list: https://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 1652270] Re: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2

2019-02-27 Thread Chris E
This is related to bug #1652504 and the answer #16 there is a more
detailed explanation of #65 above:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652504/comments/16

As of 18.04.2 the fdt_addr has changed again, I was able to fix this via
the following, first cat boot.scr on the primary partition, there's a
bunch of binary at the start of the file followed by fdt_addr_r
0x0300 - this is the new device tree address.

Use that as the base value on config.txt:

device_tree_address=0x0300

You do not need to set device_tree_end, this got the pi booting again.

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

Title:
  Could not boot into RPi3 with kernel 4.4.0-1038-raspi2

Status in linux-raspi2 package in Ubuntu:
  Confirmed

Bug description:
  This issue was reported in this mailing list thread first
  https://lists.ubuntu.com/archives/snapcraft/2016-December/002138.html

  Hardware: RPi3
  Image: 
http://www.finnie.org/software/raspberrypi/ubuntu-rpi3/ubuntu-16.04-preinstalled-server-armhf+raspi3.img.xz

  [Steps to Reproduce]
  1. Install the image in an SD card. Use it to boot into the system.
  2. Issue the command "sudo apt-get update; sudo apt-get install 
linux-image-4.4.0-1038-raspi2 linux-headers-4.4.0-1038-raspi2 
linux-raspi2-headers-4.4.0-1038 -y"
  3. Reboot

  [Expected Result]
  Boot into the system with kernel 4.4.0-1038-raspi2

  [Actual Result]
  The system stop at the booting session with the message 'Starting kernel...' 
and never goes to the login session.

  [Additional Info]

  4.4.0-1029-raspi2 and 4.4.0-1034-raspi2 were used as the forementioned
  apt installation steps. They work well. They could go to the login
  session and ready for use.

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

-- 
Mailing list: https://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 1817971] Status changed to Confirmed

2019-02-27 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  Ubuntu freezes and do not respond to mouseclicks or keyboard.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The mouse moves on the screen but it is not possible to click on
  anything and ctrl+alt+F1 doesn't do anything. I think it happens more
  often when VS code is open.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joakim 1857 F pulseaudio
   /dev/snd/controlC1:  joakim 1857 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 27 15:42:12 2019
  InstallationDate: Installed on 2019-02-07 (20 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=7da0b25e-0d4f-48bf-8785-730733ff3aee ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4024
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX X470-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4024:bd09/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX470-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

-- 
Mailing list: https://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 1817971] [NEW] Ubuntu freezes and do not respond to mouseclicks or keyboard.

2019-02-27 Thread Joakim Edin
Public bug reported:

The mouse moves on the screen but it is not possible to click on
anything and ctrl+alt+F1 doesn't do anything. I think it happens more
often when VS code is open.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-45-generic 4.15.0-45.48
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  joakim 1857 F pulseaudio
 /dev/snd/controlC1:  joakim 1857 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 27 15:42:12 2019
InstallationDate: Installed on 2019-02-07 (20 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: System manufacturer System Product Name
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=7da0b25e-0d4f-48bf-8785-730733ff3aee ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-45-generic N/A
 linux-backports-modules-4.15.0-45-generic  N/A
 linux-firmware 1.173.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/07/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4024
dmi.board.asset.tag: Default string
dmi.board.name: ROG STRIX X470-F GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4024:bd09/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX470-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug 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/1817971

Title:
  Ubuntu freezes and do not respond to mouseclicks or keyboard.

Status in linux package in Ubuntu:
  New

Bug description:
  The mouse moves on the screen but it is not possible to click on
  anything and ctrl+alt+F1 doesn't do anything. I think it happens more
  often when VS code is open.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joakim 1857 F pulseaudio
   /dev/snd/controlC1:  joakim 1857 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 27 15:42:12 2019
  InstallationDate: Installed on 2019-02-07 (20 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=7da0b25e-0d4f-48bf-8785-730733ff3aee ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4024
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX X470-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4024:bd09/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX470-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

-- 
Mailing list: https://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 1817969] [NEW] hns3 nic speed may not match optical port speed

2019-02-27 Thread dann frazier
Public bug reported:

[Impact]
The onboard optical NICs on HiSilicon D06 systems do not adjust to match the 
actual optical module speed.

[Test Case]
Verify that linked speed of interface matches the optical port speed.

[Fix]
5d497936756fa net: hns3: Config NIC port speed same as that of optical module

[Regression Risk]
Fix is restricted to a driver that is only used for the Hi1620 SoC. Note: for 
pre-GA hardware, this does require a firmware fix as well. Without it, users 
will see messages like this on the console:

[ 769.833818] hns3 :bd:00.0: get sfp speed failed -5

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

** Affects: linux (Ubuntu Cosmic)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

** Affects: linux (Ubuntu Disco)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

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

** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
 Assignee: dann frazier (dannf)
   Status: In Progress

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

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => dann frazier (dannf)

** Changed in: linux (Ubuntu Cosmic)
 Assignee: (unassigned) => dann frazier (dannf)

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

Title:
  hns3 nic speed may not match optical port speed

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress
Status in linux source package in Disco:
  In Progress

Bug description:
  [Impact]
  The onboard optical NICs on HiSilicon D06 systems do not adjust to match the 
actual optical module speed.

  [Test Case]
  Verify that linked speed of interface matches the optical port speed.

  [Fix]
  5d497936756fa net: hns3: Config NIC port speed same as that of optical module

  [Regression Risk]
  Fix is restricted to a driver that is only used for the Hi1620 SoC. Note: for 
pre-GA hardware, this does require a firmware fix as well. Without it, users 
will see messages like this on the console:

  [ 769.833818] hns3 :bd:00.0: get sfp speed failed -5

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

-- 
Mailing list: https://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 1817784] Re: libsas disks can have non-unique by-path names

2019-02-27 Thread Khaled El Mously
** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

** Changed in: linux (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

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

Title:
  libsas disks can have non-unique by-path names

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  Multiple disks in a system can end up having the same BY_PATH name, making 
the corresponding symlinks in /dev/disk/by-path non-unique. This can result in 
a user performing an operation on the wrong disk, possibly resulting in data 
loss.

  [Test Case]
  $ ls -l /dev/disk/by-path/
  total 0
  lrwxrwxrwx 1 root root  9 Feb 13 12:26 
platform-HISI0162:01-sas-exp0x500e004aaa1f-phy0-lun-0 -> ../../sdb
  lrwxrwxrwx 1 root root 10 Feb 13 12:26 
platform-HISI0162:01-sas-exp0x500e004aaa1f-phy0-lun-0-part1 -> ../../sdb1
  lrwxrwxrwx 1 root root 10 Feb 13 12:26 
platform-HISI0162:01-sas-exp0x500e004aaa1f-phy0-lun-0-part2 -> ../../sdb2
  lrwxrwxrwx 1 root root 10 Feb 13 12:26 
platform-HISI0162:01-sas-exp0x500e004aaa1f-phy0-lun-0-part3 -> ../../sdc3

  
  Notice that there is no symlink for /dev/sdc.

  [Fix]
  ffeafdd2bf0b2 scsi: libsas: Fix rphy phy_identifier for PHYs with end devices 
attached

  [Regression Risk]
  This may change the by-path symlinks for disks on the system. While the new 
name would be the correct one - users maybe relying on the incorrect version. 
This could result in an unbootable system, requiring manual intervention to 
repair.

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

-- 
Mailing list: https://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 1817968] [NEW] Add support for SAS disk LED on D06 systems

2019-02-27 Thread dann frazier
*** This bug is a duplicate of bug 1774467 ***
https://bugs.launchpad.net/bugs/1774467

Public bug reported:

[Impact]
LEDs on directly attached disks on the HiSilicon D06 system do not work.

[Test Case]
blinkenlights ;)

[Fix]
428f1b3424f4f scsi: hisi_sas: Add LED feature for v3 hw

[Regression Risk]
Change is restricted to a driver for a specific ARM server SoC, on which we've 
directly regression tested.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => dann frazier (dannf)

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

** This bug has been marked a duplicate of bug 1774467
   hisi_sas: Support newer v3 hardware

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

Title:
  Add support for SAS disk LED on D06 systems

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress

Bug description:
  [Impact]
  LEDs on directly attached disks on the HiSilicon D06 system do not work.

  [Test Case]
  blinkenlights ;)

  [Fix]
  428f1b3424f4f scsi: hisi_sas: Add LED feature for v3 hw

  [Regression Risk]
  Change is restricted to a driver for a specific ARM server SoC, on which 
we've directly regression tested.

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

-- 
Mailing list: https://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 1812099] Re: 4.18.0 thinkpad_acpi : thresholds for BAT1 not writable

2019-02-27 Thread Khaled El Mously
** Changed in: linux (Ubuntu Cosmic)
   Status: New => Fix Committed

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

Title:
  4.18.0 thinkpad_acpi : thresholds for BAT1 not writable

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  [Problem description]
  Kernel 4.17 introduced a new interface to set charge thresholds: The 
interface remained unchanged with 4.18. There's a bug preventing writing the 
charge thresholds for the secondary battery (BAT1).

  [Impact]
  ThinkPads with two batteries (ThinkPad "power bridge") e.g.
  X240, T440(s), X250, T450(s), X260, T460(s), X270, T470(s) et al.

  [Steps to reproduce]
  echo 42 > /sys/class/power_supply/BAT1/charge_start_threshold
  bash: echo: write error: No such device 

  echo 42 > /sys/class/power_supply/BAT0/charge_start_threshold
  -- primary battery works!

  [Fix]
  Problem was fixed in 4.19:
  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/platform/x86/thinkpad_acpi.c?h=v4.19.15&id=d22296d9c38fd29a96bb5079fb8d17cee278f40e

  I propose to cherry-pick the patch for 4.18.

  [Test Case]
  See above, a patched 4.18 works for T450s.

  [Regression Potential]
  Low. This patch only applies to several ThinkPad machines, and after applying
  this patch, charge_start/stop_threshold work for BAT0 and BAT.

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

-- 
Mailing list: https://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 1817200] Re: Trackpad is not recognized.

2019-02-27 Thread Khaled El Mously
** Changed in: linux (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  Trackpad is not recognized.

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  === SRU Justification ===
  [Impact]
  Touchpad on Walmart Overpowered laptop doesn't work.

  [Fix]
  Quote the commit message:
  "The gpio base for GPP-E was set incorrectly to 258 instead of 256"

  [Test]
  User confirm the commit makes the touchpad work.

  [Regression Potential]
  Low. This commit is in upstream stable for a while.
  === Original Bug Report ===
  Trackpad is not recognized in linux for
  Overpowered laptop model OP-LP1 (sold by Walmart)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  d  2135 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 21 14:01:39 2019
  InstallationDate: Installed on 2019-02-21 (0 days ago)
  InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: OVERPOWERED OP-LP1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=abb2aee4-3166-41d9-8ac4-14a5a3fccc92 ro acpi_osi=! "acpi_osi=Windows 
2009" blacklist=nouveau elevator=deadline drmdebug=0xe quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N.1.02
  dmi.board.asset.tag: Standard
  dmi.board.name: GK5CN4Z
  dmi.board.vendor: OVERPOWERED
  dmi.board.version: Standard
  dmi.chassis.asset.tag: Standard
  dmi.chassis.type: 10
  dmi.chassis.vendor: Standard
  dmi.chassis.version: Standard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN.1.02:bd09/26/2018:svnOVERPOWERED:pnOP-LP1:pvrStandard:rvnOVERPOWERED:rnGK5CN4Z:rvrStandard:cvnStandard:ct10:cvrStandard:
  dmi.product.family: OP-LP
  dmi.product.name: OP-LP1
  dmi.product.version: Standard
  dmi.sys.vendor: OVERPOWERED

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

-- 
Mailing list: https://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 1817918] Re: Hard lockups due to unrestricted lapic timer delay

2019-02-27 Thread Khaled El Mously
** Changed in: linux (Ubuntu Xenial)
   Status: Confirmed => Fix Committed

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

Title:
  Hard lockups due to unrestricted lapic timer delay

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  * There is a long-time report of an issue with the TSC delay present
  in wait_lapic_expire() - basically the guest could have an expiration
  timer configured in a way it induces host to wait a long time (with
  preemption disabled), so there's a potential scenario for host lockups.

  * The stack trace we have access (from an user report of this issue)
  is (summarized) below:

  NMI watchdog: Watchdog detected hard LOCKUP on cpu 16
  [...]
  CPU: 16 PID: 3024910 Comm: CPU 0/KVM Not tainted 4.4.0-139-generic #165-Ubuntu
  RIP: 0010:[]  [] delay_tsc+0x20/0x60
  [...]
   __delay+0x15/0x20
  wait_lapic_expire+0xc3/0x150 [kvm]
  vcpu_enter_guest+0x743/0x11d0 [kvm]
  kvm_arch_vcpu_ioctl_run+0xe6/0x410 [kvm]
  kvm_vcpu_ioctl+0x33d/0x620 [kvm]
  do_vfs_ioctl+0x2af/0x4b0
  ? __do_page_fault+0x1c1/0x410
  ? fire_user_return_notifiers+0x3e/0x50
  SyS_ioctl+0x79/0x90
  entry_SYSCALL_64_fastpath+0x22/0xc1

  This matches the reported problem in the KVM mailing-list:
  https://marc.info/?l=kvm&m=146374488028339

  * A fix was proposed in the above thread, but discarded in favor of the
  following approach: https://marc.info/?l=kvm&m=146647260109315
  The patch was merged in Linus tree, hence we hereby request the SRU:
  b606f189c7d5 ("KVM: LAPIC: cap __delay at lapic_timer_advance_ns").
  There's one additional patch needed, which is just the header adjustment
  for exporting a necessary function.

  * The patch is missing only in 4.4 kernel series; Bionic (4.15) and
  the other newer releases have the patch already.

  [Test Case]

  * Unfortunately this is a hard to reproduce issue; we have reports of
  this lockup from an user, hence the SRU request here.
  Also, the patch was introduced originally in kernel 4.7, approx. 2.5 years
  ago. So, we are confident that community is running this code long enough
  without errors reported. Also, checked in the Linus tree and no fixes
  for this code were introduced since kernel 4.7.

  [Regression Potential]

  * The code modification requested here affects the amount of delay in
  a specific timer; the patch introduces a maximum time for delay, preventing 
unbounded delays in host.
  The regression potential is considered low, and given the nature of the
  modification, latency issues in guests are likely to be the most problematic 
regression potential we have.

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

-- 
Mailing list: https://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 1814726] Re: linux: 4.15.0-46.49 -proposed tracker

2019-02-27 Thread Brad Figg
** 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
  
  backports: bug 1814741 (linux-azure), bug 1814742 (linux-aws-hwe), bug 
1814743 (linux-azure), bug 1817551 (xenial/linux-azure-edge)
  derivatives: bug 1814728 (linux-raspi2), bug 1814730 (linux-oem), bug 1814731 
(linux-aws)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:28 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux: 4.15.0-46.49 -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:
  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-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
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

  backports: bug 1814741 (linux-azure), bug 1814742 (linux-aws-hwe), bug 
1814743 (linux-azure), bug 1817551 (xenial/linux-azure-edge)
  derivatives: bug 1814728 (linux-raspi2), bug 1814730 (linux-oem), bug 1814731 
(linux-aws)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:28 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

-- 
Mailing list: https://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 1814726] Re: linux: 4.15.0-46.49 -proposed tracker

2019-02-27 Thread Sean Feole
** Tags added: regression-testing-passed

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

Title:
  linux: 4.15.0-46.49 -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:
  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-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
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

  backports: bug 1814741 (linux-azure), bug 1814742 (linux-aws-hwe), bug 
1814743 (linux-azure), bug 1817551 (xenial/linux-azure-edge)
  derivatives: bug 1814728 (linux-raspi2), bug 1814730 (linux-oem), bug 1814731 
(linux-aws)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:28 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

-- 
Mailing list: https://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 1817944] Re: Kubuntu 18.04 does not display through mini-DP port on lenovo Helix 2

2019-02-27 Thread udippel
For completeness, here the Xorg-log. It looks pretty similar to the log
of that FreeDesktop bug 106017; that is trying for ages to get the
display up. There it leads to heavy flicker, and here it leads to a
fail.

** Attachment added: "EDID_not_found"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817944/+attachment/5242145/+files/EDID_not_found

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

Title:
  Kubuntu 18.04 does not display through mini-DP port on lenovo Helix 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (This is probably related to bug 1816860, but with different hardware
  and a different appearance, so it is filed separately.)

  Using the levovo Helix 2 attached to its Pro keyboard, it is not possible to 
activate the monitor as attached. 
  The monitor is attached with a mini-DP-to-HDMI cable to the monitor (SONY), 
and is - in this case, contrary to the bug mentioned before - detected as can 
be seen by xrandr.
  But then it gives up after some time (see attachment of System Settings 
started from CLI and Xorg.log:
  $ tail /var/log/Xorg.0.log
  [   970.977] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)  

  [   973.083] (II) modeset(0): EDID vendor "LGD", prod id 1121 


  [   973.083] (II) modeset(0): Printing DDC gathered Modelines:


  [   973.083] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1009.658] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1009.658] (II) modeset(0): Printing DDC gathered Modelines:
  [  1009.658] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1099.146] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1099.146] (II) modeset(0): Printing DDC gathered Modelines:
  [  1099.146] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)

  (and so it continues).

  Connecting the tablet of the convertable itself with a micro-HDMI-to-HDMI to 
that same monitor works fine, however.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1872 F pulseaudio
   /dev/snd/controlC0:  udippel1872 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (11 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1817944] Re: Kubuntu 18.04 does not display through mini-DP port on lenovo Helix 2

2019-02-27 Thread udippel
Nope, again.
After some 5 or 10 minutes of working, the screen began to look like the old 
TV-sets not being synchronized (diagonal coloured bars), and then it went away 
completely. 

Before writing this message here, I let it run for half an hour or so, and it 
shows the display in xrandr, and then it doesn't show it. "You see it, and then 
you don't".
This here is like when xrandr shwos the display:

$ xrandr 
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 256mm x 144mm
   1920x1080 59.99 +  59.97*   59.9659.93  
   1680x1050 59.9559.88  
   1600x1024 60.17  
   1400x1050 59.98  
   1600x900  59.9959.9459.9559.82  
   1280x1024 60.02  
   1440x900  59.89  
   1400x900  59.9659.88  
   1280x960  60.00  
   1440x810  60.0059.97  
   1368x768  59.8859.85  
   1360x768  59.8059.96  
   1280x800  59.9959.9759.8159.91  
   1152x864  60.00  
   1280x720  60.0059.9959.8659.74  
   1024x768  60.0460.00  
   960x720   60.00  
   928x696   60.05  
   896x672   60.01  
   1024x576  59.9559.9659.9059.82  
   960x600   59.9360.00  
   960x540   59.9659.9959.6359.82  
   800x600   60.0060.3256.25  
   840x525   60.0159.88  
   864x486   59.9259.57  
   800x512   60.17  
   700x525   59.98  
   800x450   59.9559.82  
   640x512   60.02  
   720x450   59.89  
   700x450   59.9659.88  
   640x480   60.0059.94  
   720x405   59.5158.99  
   684x384   59.8859.85  
   680x384   59.8059.96  
   640x400   59.8859.98  
   576x432   60.06  
   640x360   59.8659.8359.8459.32  
   512x384   60.00  
   512x288   60.0059.92  
   480x270   59.6359.82  
   400x300   60.3256.34  
   432x243   59.9259.57  
   320x240   60.05  
   360x202   59.5159.13  
   320x180   59.8459.32  
HDMI-1 disconnected (normal left inverted right x axis y axis)
HDMI-2 connected (normal left inverted right x axis y axis)
   1920x1080 60.00 +  50.0059.9430.0024.0029.9723.98  
   1920x1080i60.0050.0059.94  
   1280x1024 60.02  
   1280x720  60.0050.0030.0059.9429.9724.0023.98  
   1024x768  60.00  
   800x600   60.32  
   720x576   50.00  
   720x576i  50.00  
   720x480   60.0059.94  
   720x480i  60.0059.94  
   640x480   60.0059.94 

The System Settings in kubuntu never shows it (or I never saw it?)

Here I was lucky, and found xrandr between 'connected' and
'disconnected'. It looks crazy that it shows 'disconnected' and at the
same time givestiming information, doesn't it?:

DMI-2 disconnected (normal left inverted right x axis y axis)
  1920x1080 (0xa1) 148.500MHz +HSync +VSync
h: width  1920 start 2008 end 2052 total 2200 skew0 clock  67.50KHz
v: height 1080 start 1084 end 1089 total 1125   clock  60.00Hz
  1920x1080 (0xa2) 148.500MHz +HSync +VSync
h: width  1920 start 2448 end 2492 total 2640 skew0 clock  56.25KHz
v: height 1080 start 1084 end 1089 total 1125   clock  50.00Hz
  1920x1080 (0xa3) 148.352MHz +HSync +VSync
h: width  1920 start 2008 end 2052 total 2200 skew0 clock  67.43KHz
v: height 1080 start 1084 end 1089 total 1125   clock  59.94Hz
  1920x1080i (0xa4) 74.250MHz +HSync +VSync Interlace
h: width  1920 start 2008 end 2052 total 2200 skew0 clock  33.75KHz
v: height 1080 start 1084 end 1094 total 1125   clock  60.00Hz
  1920x1080i (0xa5) 74.250MHz +HSync +VSync Interlace
h: width  1920 start 2448 end 2492 total 2640 skew0 clock  28.12KHz
v: height 1080 start 1084 end 1094 total 1125   clock  50.00Hz
  1920x1080 (0xa6) 74.250MHz +HSync +VSync
h: width  1920 start 2008 end 2052 total 2200 skew0 clock  33.75KHz
v: height 1080 start 1084 end 1089 total 1125   clock  30.00Hz
  1920x1080 (0xa7) 74.250MHz +HSync +VSync
h: width  1920 start 2558 end 2602 total 2750 skew0 clock  27.00KHz
v: height 1080 start 1084 end 1089 total 1125   clock  24.00Hz
  1920x1080i (0xa8) 74.176MHz +HSync +VSync Interlace
h: width  1920 start 2008 end 2052 total 2200 skew0 clock  33.72KHz
v: height 1080 start 1084 end 1094 total 1125   clock  59.94Hz
  1920x1080 (0xa9) 74.176MHz +HSync +VSync
h: width  1920 start 2008 end 2052 total 2200 skew0 clock  33.72KHz
v: height 1080 start 1084 end 1089 total 1125   clock  29.97Hz
  1920x1080 (0xaa) 74.176MHz +HSync +VSync
h: width  1920 start 2558 end 2602 total 2750 skew0 clock  26.97KHz
v: height 1080 s

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

2019-02-27 Thread udippel
apport information

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

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

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

Title:
  Kubuntu 18.04 does not display through mini-DP port on lenovo Helix 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (This is probably related to bug 1816860, but with different hardware
  and a different appearance, so it is filed separately.)

  Using the levovo Helix 2 attached to its Pro keyboard, it is not possible to 
activate the monitor as attached. 
  The monitor is attached with a mini-DP-to-HDMI cable to the monitor (SONY), 
and is - in this case, contrary to the bug mentioned before - detected as can 
be seen by xrandr.
  But then it gives up after some time (see attachment of System Settings 
started from CLI and Xorg.log:
  $ tail /var/log/Xorg.0.log
  [   970.977] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)  

  [   973.083] (II) modeset(0): EDID vendor "LGD", prod id 1121 


  [   973.083] (II) modeset(0): Printing DDC gathered Modelines:


  [   973.083] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1009.658] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1009.658] (II) modeset(0): Printing DDC gathered Modelines:
  [  1009.658] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1099.146] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1099.146] (II) modeset(0): Printing DDC gathered Modelines:
  [  1099.146] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)

  (and so it continues).

  Connecting the tablet of the convertable itself with a micro-HDMI-to-HDMI to 
that same monitor works fine, however.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1872 F pulseaudio
   /dev/snd/controlC0:  udippel1872 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (11 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1816106] Re: 4.15.0-1037 does not see all PCI devices on GPU VMs

2019-02-27 Thread Marcelo Cerri
** Also affects: linux-azure (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: linux-azure (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** No longer affects: linux-azure (Ubuntu Bionic)

** Also affects: linux-azure (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: linux-azure (Ubuntu Xenial)
   Status: New => Fix Released

** Changed in: linux-azure (Ubuntu Cosmic)
   Status: New => Fix Released

** Changed in: linux-azure (Ubuntu Xenial)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

** Changed in: linux-azure (Ubuntu Cosmic)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

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

Title:
  4.15.0-1037 does not see all PCI devices on GPU VMs

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released

Bug description:
  Host changes have altered how the PCI GUID is presented to the guest
  and the patches for PCI IDs in 4.15.0-1037 do not properly handle the
  new condition.

  Impact:
  Instances with multiple GPUs are only seeing one.

  Workaround:
  4.15.0-1036 does not have this behavior.

  Additional info:

  The commit in 4.15.0-1037 responsible is " - PCI: hv: Make sure the
  bus domain is really unique"

  The immediate action requested is to back out this patch on 4.15.0 (azure):
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/commit/?h=master-next&id=b9ae54076a78d01659c4d0f0a558cdb4056f0d13

  The same thing on 4.18:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/commit/?h=azure-edge-next&id=29927dfb7f69bcf2ae7fd1cda10997e646a5189c

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

-- 
Mailing list: https://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 1817944] ProcEnviron.txt

2019-02-27 Thread udippel
apport information

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

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

Title:
  Kubuntu 18.04 does not display through mini-DP port on lenovo Helix 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (This is probably related to bug 1816860, but with different hardware
  and a different appearance, so it is filed separately.)

  Using the levovo Helix 2 attached to its Pro keyboard, it is not possible to 
activate the monitor as attached. 
  The monitor is attached with a mini-DP-to-HDMI cable to the monitor (SONY), 
and is - in this case, contrary to the bug mentioned before - detected as can 
be seen by xrandr.
  But then it gives up after some time (see attachment of System Settings 
started from CLI and Xorg.log:
  $ tail /var/log/Xorg.0.log
  [   970.977] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)  

  [   973.083] (II) modeset(0): EDID vendor "LGD", prod id 1121 


  [   973.083] (II) modeset(0): Printing DDC gathered Modelines:


  [   973.083] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1009.658] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1009.658] (II) modeset(0): Printing DDC gathered Modelines:
  [  1009.658] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1099.146] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1099.146] (II) modeset(0): Printing DDC gathered Modelines:
  [  1099.146] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)

  (and so it continues).

  Connecting the tablet of the convertable itself with a micro-HDMI-to-HDMI to 
that same monitor works fine, however.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1872 F pulseaudio
   /dev/snd/controlC0:  udippel1872 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (11 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1817944] PulseList.txt

2019-02-27 Thread udippel
apport information

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

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

Title:
  Kubuntu 18.04 does not display through mini-DP port on lenovo Helix 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (This is probably related to bug 1816860, but with different hardware
  and a different appearance, so it is filed separately.)

  Using the levovo Helix 2 attached to its Pro keyboard, it is not possible to 
activate the monitor as attached. 
  The monitor is attached with a mini-DP-to-HDMI cable to the monitor (SONY), 
and is - in this case, contrary to the bug mentioned before - detected as can 
be seen by xrandr.
  But then it gives up after some time (see attachment of System Settings 
started from CLI and Xorg.log:
  $ tail /var/log/Xorg.0.log
  [   970.977] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)  

  [   973.083] (II) modeset(0): EDID vendor "LGD", prod id 1121 


  [   973.083] (II) modeset(0): Printing DDC gathered Modelines:


  [   973.083] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1009.658] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1009.658] (II) modeset(0): Printing DDC gathered Modelines:
  [  1009.658] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1099.146] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1099.146] (II) modeset(0): Printing DDC gathered Modelines:
  [  1099.146] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)

  (and so it continues).

  Connecting the tablet of the convertable itself with a micro-HDMI-to-HDMI to 
that same monitor works fine, however.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1872 F pulseaudio
   /dev/snd/controlC0:  udippel1872 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (11 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1817944] CRDA.txt

2019-02-27 Thread udippel
apport information

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

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

Title:
  Kubuntu 18.04 does not display through mini-DP port on lenovo Helix 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (This is probably related to bug 1816860, but with different hardware
  and a different appearance, so it is filed separately.)

  Using the levovo Helix 2 attached to its Pro keyboard, it is not possible to 
activate the monitor as attached. 
  The monitor is attached with a mini-DP-to-HDMI cable to the monitor (SONY), 
and is - in this case, contrary to the bug mentioned before - detected as can 
be seen by xrandr.
  But then it gives up after some time (see attachment of System Settings 
started from CLI and Xorg.log:
  $ tail /var/log/Xorg.0.log
  [   970.977] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)  

  [   973.083] (II) modeset(0): EDID vendor "LGD", prod id 1121 


  [   973.083] (II) modeset(0): Printing DDC gathered Modelines:


  [   973.083] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1009.658] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1009.658] (II) modeset(0): Printing DDC gathered Modelines:
  [  1009.658] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1099.146] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1099.146] (II) modeset(0): Printing DDC gathered Modelines:
  [  1099.146] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)

  (and so it continues).

  Connecting the tablet of the convertable itself with a micro-HDMI-to-HDMI to 
that same monitor works fine, however.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1872 F pulseaudio
   /dev/snd/controlC0:  udippel1872 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (11 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1817944] CurrentDmesg.txt

2019-02-27 Thread udippel
apport information

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

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

Title:
  Kubuntu 18.04 does not display through mini-DP port on lenovo Helix 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (This is probably related to bug 1816860, but with different hardware
  and a different appearance, so it is filed separately.)

  Using the levovo Helix 2 attached to its Pro keyboard, it is not possible to 
activate the monitor as attached. 
  The monitor is attached with a mini-DP-to-HDMI cable to the monitor (SONY), 
and is - in this case, contrary to the bug mentioned before - detected as can 
be seen by xrandr.
  But then it gives up after some time (see attachment of System Settings 
started from CLI and Xorg.log:
  $ tail /var/log/Xorg.0.log
  [   970.977] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)  

  [   973.083] (II) modeset(0): EDID vendor "LGD", prod id 1121 


  [   973.083] (II) modeset(0): Printing DDC gathered Modelines:


  [   973.083] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1009.658] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1009.658] (II) modeset(0): Printing DDC gathered Modelines:
  [  1009.658] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1099.146] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1099.146] (II) modeset(0): Printing DDC gathered Modelines:
  [  1099.146] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)

  (and so it continues).

  Connecting the tablet of the convertable itself with a micro-HDMI-to-HDMI to 
that same monitor works fine, however.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1872 F pulseaudio
   /dev/snd/controlC0:  udippel1872 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (11 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1817944] ProcCpuinfoMinimal.txt

2019-02-27 Thread udippel
apport information

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

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

Title:
  Kubuntu 18.04 does not display through mini-DP port on lenovo Helix 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (This is probably related to bug 1816860, but with different hardware
  and a different appearance, so it is filed separately.)

  Using the levovo Helix 2 attached to its Pro keyboard, it is not possible to 
activate the monitor as attached. 
  The monitor is attached with a mini-DP-to-HDMI cable to the monitor (SONY), 
and is - in this case, contrary to the bug mentioned before - detected as can 
be seen by xrandr.
  But then it gives up after some time (see attachment of System Settings 
started from CLI and Xorg.log:
  $ tail /var/log/Xorg.0.log
  [   970.977] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)  

  [   973.083] (II) modeset(0): EDID vendor "LGD", prod id 1121 


  [   973.083] (II) modeset(0): Printing DDC gathered Modelines:


  [   973.083] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1009.658] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1009.658] (II) modeset(0): Printing DDC gathered Modelines:
  [  1009.658] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1099.146] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1099.146] (II) modeset(0): Printing DDC gathered Modelines:
  [  1099.146] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)

  (and so it continues).

  Connecting the tablet of the convertable itself with a micro-HDMI-to-HDMI to 
that same monitor works fine, however.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1872 F pulseaudio
   /dev/snd/controlC0:  udippel1872 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (11 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1817944] Lsusb.txt

2019-02-27 Thread udippel
apport information

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

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

Title:
  Kubuntu 18.04 does not display through mini-DP port on lenovo Helix 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (This is probably related to bug 1816860, but with different hardware
  and a different appearance, so it is filed separately.)

  Using the levovo Helix 2 attached to its Pro keyboard, it is not possible to 
activate the monitor as attached. 
  The monitor is attached with a mini-DP-to-HDMI cable to the monitor (SONY), 
and is - in this case, contrary to the bug mentioned before - detected as can 
be seen by xrandr.
  But then it gives up after some time (see attachment of System Settings 
started from CLI and Xorg.log:
  $ tail /var/log/Xorg.0.log
  [   970.977] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)  

  [   973.083] (II) modeset(0): EDID vendor "LGD", prod id 1121 


  [   973.083] (II) modeset(0): Printing DDC gathered Modelines:


  [   973.083] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1009.658] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1009.658] (II) modeset(0): Printing DDC gathered Modelines:
  [  1009.658] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1099.146] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1099.146] (II) modeset(0): Printing DDC gathered Modelines:
  [  1099.146] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)

  (and so it continues).

  Connecting the tablet of the convertable itself with a micro-HDMI-to-HDMI to 
that same monitor works fine, however.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1872 F pulseaudio
   /dev/snd/controlC0:  udippel1872 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (11 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1817944] UdevDb.txt

2019-02-27 Thread udippel
apport information

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

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

Title:
  Kubuntu 18.04 does not display through mini-DP port on lenovo Helix 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (This is probably related to bug 1816860, but with different hardware
  and a different appearance, so it is filed separately.)

  Using the levovo Helix 2 attached to its Pro keyboard, it is not possible to 
activate the monitor as attached. 
  The monitor is attached with a mini-DP-to-HDMI cable to the monitor (SONY), 
and is - in this case, contrary to the bug mentioned before - detected as can 
be seen by xrandr.
  But then it gives up after some time (see attachment of System Settings 
started from CLI and Xorg.log:
  $ tail /var/log/Xorg.0.log
  [   970.977] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)  

  [   973.083] (II) modeset(0): EDID vendor "LGD", prod id 1121 


  [   973.083] (II) modeset(0): Printing DDC gathered Modelines:


  [   973.083] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1009.658] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1009.658] (II) modeset(0): Printing DDC gathered Modelines:
  [  1009.658] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1099.146] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1099.146] (II) modeset(0): Printing DDC gathered Modelines:
  [  1099.146] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)

  (and so it continues).

  Connecting the tablet of the convertable itself with a micro-HDMI-to-HDMI to 
that same monitor works fine, however.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1872 F pulseaudio
   /dev/snd/controlC0:  udippel1872 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (11 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1817944] ProcModules.txt

2019-02-27 Thread udippel
apport information

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

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

Title:
  Kubuntu 18.04 does not display through mini-DP port on lenovo Helix 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (This is probably related to bug 1816860, but with different hardware
  and a different appearance, so it is filed separately.)

  Using the levovo Helix 2 attached to its Pro keyboard, it is not possible to 
activate the monitor as attached. 
  The monitor is attached with a mini-DP-to-HDMI cable to the monitor (SONY), 
and is - in this case, contrary to the bug mentioned before - detected as can 
be seen by xrandr.
  But then it gives up after some time (see attachment of System Settings 
started from CLI and Xorg.log:
  $ tail /var/log/Xorg.0.log
  [   970.977] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)  

  [   973.083] (II) modeset(0): EDID vendor "LGD", prod id 1121 


  [   973.083] (II) modeset(0): Printing DDC gathered Modelines:


  [   973.083] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1009.658] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1009.658] (II) modeset(0): Printing DDC gathered Modelines:
  [  1009.658] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1099.146] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1099.146] (II) modeset(0): Printing DDC gathered Modelines:
  [  1099.146] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)

  (and so it continues).

  Connecting the tablet of the convertable itself with a micro-HDMI-to-HDMI to 
that same monitor works fine, however.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1872 F pulseaudio
   /dev/snd/controlC0:  udippel1872 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (11 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1817944] ProcInterrupts.txt

2019-02-27 Thread udippel
apport information

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

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

Title:
  Kubuntu 18.04 does not display through mini-DP port on lenovo Helix 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (This is probably related to bug 1816860, but with different hardware
  and a different appearance, so it is filed separately.)

  Using the levovo Helix 2 attached to its Pro keyboard, it is not possible to 
activate the monitor as attached. 
  The monitor is attached with a mini-DP-to-HDMI cable to the monitor (SONY), 
and is - in this case, contrary to the bug mentioned before - detected as can 
be seen by xrandr.
  But then it gives up after some time (see attachment of System Settings 
started from CLI and Xorg.log:
  $ tail /var/log/Xorg.0.log
  [   970.977] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)  

  [   973.083] (II) modeset(0): EDID vendor "LGD", prod id 1121 


  [   973.083] (II) modeset(0): Printing DDC gathered Modelines:


  [   973.083] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1009.658] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1009.658] (II) modeset(0): Printing DDC gathered Modelines:
  [  1009.658] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1099.146] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1099.146] (II) modeset(0): Printing DDC gathered Modelines:
  [  1099.146] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)

  (and so it continues).

  Connecting the tablet of the convertable itself with a micro-HDMI-to-HDMI to 
that same monitor works fine, however.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1872 F pulseaudio
   /dev/snd/controlC0:  udippel1872 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (11 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1817944] ProcCpuinfo.txt

2019-02-27 Thread udippel
apport information

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

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

Title:
  Kubuntu 18.04 does not display through mini-DP port on lenovo Helix 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (This is probably related to bug 1816860, but with different hardware
  and a different appearance, so it is filed separately.)

  Using the levovo Helix 2 attached to its Pro keyboard, it is not possible to 
activate the monitor as attached. 
  The monitor is attached with a mini-DP-to-HDMI cable to the monitor (SONY), 
and is - in this case, contrary to the bug mentioned before - detected as can 
be seen by xrandr.
  But then it gives up after some time (see attachment of System Settings 
started from CLI and Xorg.log:
  $ tail /var/log/Xorg.0.log
  [   970.977] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)  

  [   973.083] (II) modeset(0): EDID vendor "LGD", prod id 1121 


  [   973.083] (II) modeset(0): Printing DDC gathered Modelines:


  [   973.083] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1009.658] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1009.658] (II) modeset(0): Printing DDC gathered Modelines:
  [  1009.658] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1099.146] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1099.146] (II) modeset(0): Printing DDC gathered Modelines:
  [  1099.146] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)

  (and so it continues).

  Connecting the tablet of the convertable itself with a micro-HDMI-to-HDMI to 
that same monitor works fine, however.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1872 F pulseaudio
   /dev/snd/controlC0:  udippel1872 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (11 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1817944] RfKill.txt

2019-02-27 Thread udippel
apport information

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

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

Title:
  Kubuntu 18.04 does not display through mini-DP port on lenovo Helix 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (This is probably related to bug 1816860, but with different hardware
  and a different appearance, so it is filed separately.)

  Using the levovo Helix 2 attached to its Pro keyboard, it is not possible to 
activate the monitor as attached. 
  The monitor is attached with a mini-DP-to-HDMI cable to the monitor (SONY), 
and is - in this case, contrary to the bug mentioned before - detected as can 
be seen by xrandr.
  But then it gives up after some time (see attachment of System Settings 
started from CLI and Xorg.log:
  $ tail /var/log/Xorg.0.log
  [   970.977] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)  

  [   973.083] (II) modeset(0): EDID vendor "LGD", prod id 1121 


  [   973.083] (II) modeset(0): Printing DDC gathered Modelines:


  [   973.083] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1009.658] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1009.658] (II) modeset(0): Printing DDC gathered Modelines:
  [  1009.658] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1099.146] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1099.146] (II) modeset(0): Printing DDC gathered Modelines:
  [  1099.146] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)

  (and so it continues).

  Connecting the tablet of the convertable itself with a micro-HDMI-to-HDMI to 
that same monitor works fine, however.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1872 F pulseaudio
   /dev/snd/controlC0:  udippel1872 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (11 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1817944] Lspci.txt

2019-02-27 Thread udippel
apport information

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

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

Title:
  Kubuntu 18.04 does not display through mini-DP port on lenovo Helix 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (This is probably related to bug 1816860, but with different hardware
  and a different appearance, so it is filed separately.)

  Using the levovo Helix 2 attached to its Pro keyboard, it is not possible to 
activate the monitor as attached. 
  The monitor is attached with a mini-DP-to-HDMI cable to the monitor (SONY), 
and is - in this case, contrary to the bug mentioned before - detected as can 
be seen by xrandr.
  But then it gives up after some time (see attachment of System Settings 
started from CLI and Xorg.log:
  $ tail /var/log/Xorg.0.log
  [   970.977] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)  

  [   973.083] (II) modeset(0): EDID vendor "LGD", prod id 1121 


  [   973.083] (II) modeset(0): Printing DDC gathered Modelines:


  [   973.083] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1009.658] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1009.658] (II) modeset(0): Printing DDC gathered Modelines:
  [  1009.658] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1099.146] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1099.146] (II) modeset(0): Printing DDC gathered Modelines:
  [  1099.146] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)

  (and so it continues).

  Connecting the tablet of the convertable itself with a micro-HDMI-to-HDMI to 
that same monitor works fine, however.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1872 F pulseaudio
   /dev/snd/controlC0:  udippel1872 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (11 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1817944] IwConfig.txt

2019-02-27 Thread udippel
apport information

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

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

Title:
  Kubuntu 18.04 does not display through mini-DP port on lenovo Helix 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (This is probably related to bug 1816860, but with different hardware
  and a different appearance, so it is filed separately.)

  Using the levovo Helix 2 attached to its Pro keyboard, it is not possible to 
activate the monitor as attached. 
  The monitor is attached with a mini-DP-to-HDMI cable to the monitor (SONY), 
and is - in this case, contrary to the bug mentioned before - detected as can 
be seen by xrandr.
  But then it gives up after some time (see attachment of System Settings 
started from CLI and Xorg.log:
  $ tail /var/log/Xorg.0.log
  [   970.977] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)  

  [   973.083] (II) modeset(0): EDID vendor "LGD", prod id 1121 


  [   973.083] (II) modeset(0): Printing DDC gathered Modelines:


  [   973.083] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1009.658] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1009.658] (II) modeset(0): Printing DDC gathered Modelines:
  [  1009.658] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1099.146] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1099.146] (II) modeset(0): Printing DDC gathered Modelines:
  [  1099.146] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)

  (and so it continues).

  Connecting the tablet of the convertable itself with a micro-HDMI-to-HDMI to 
that same monitor works fine, however.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1872 F pulseaudio
   /dev/snd/controlC0:  udippel1872 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (11 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1817944] Re: Kubuntu 18.04 does not display through mini-DP port on lenovo Helix 2

2019-02-27 Thread udippel
apport information

** Tags added: apport-collected

** Description changed:

  (This is probably related to bug 1816860, but with different hardware
  and a different appearance, so it is filed separately.)
  
  Using the levovo Helix 2 attached to its Pro keyboard, it is not possible to 
activate the monitor as attached. 
  The monitor is attached with a mini-DP-to-HDMI cable to the monitor (SONY), 
and is - in this case, contrary to the bug mentioned before - detected as can 
be seen by xrandr.
  But then it gives up after some time (see attachment of System Settings 
started from CLI and Xorg.log:
  $ tail /var/log/Xorg.0.log
  [   970.977] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)  

  [   973.083] (II) modeset(0): EDID vendor "LGD", prod id 1121 


  [   973.083] (II) modeset(0): Printing DDC gathered Modelines:


  [   973.083] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1009.658] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1009.658] (II) modeset(0): Printing DDC gathered Modelines:
  [  1009.658] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1099.146] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1099.146] (II) modeset(0): Printing DDC gathered Modelines:
  [  1099.146] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  
  (and so it continues).
  
- Connecting the tablet of the convertable itself with a micro-HDMI-to-
- HDMI to that same monitor works fine, however.
+ Connecting the tablet of the convertable itself with a micro-HDMI-to-HDMI to 
that same monitor works fine, however.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.5
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  udippel1872 F pulseaudio
+  /dev/snd/controlC0:  udippel1872 F pulseaudio
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 18.04
+ HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
+ InstallationDate: Installed on 2019-02-16 (11 days ago)
+ InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
+ MachineType: LENOVO 20CHS10P02
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-45-generic N/A
+  linux-backports-modules-4.15.0-45-generic  N/A
+  linux-firmware 1.173.3
+ Tags:  bionic
+ Uname: Linux 4.15.0-45-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 10/31/2018
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: N17ETA2W (2.02 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 20CHS10P02
+ dmi.board.vendor: LENOVO
+ dmi.board.version: SDK0E50510 WIN
+ dmi.chassis.asset.tag: No Asset Information
+ dmi.chassis.type: 11
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: None
+ dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
+ dmi.product.family: ThinkPad Helix 2nd
+ dmi.product.name: 20CHS10P02
+ dmi.product.version: ThinkPad Helix 2nd
+ dmi.sys.vendor: LENOVO

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

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

Title:
  Kubuntu 18.04 does not display through mini-DP port on lenovo Helix 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (This is probably related to bug 1816860, but with different hardware
  and a different appearance, so it is filed separately.)

  Using the levovo Helix 2 attached to its Pro keyboard, it is not possible to 
activate the monitor as attached. 
  The monitor is attached with a mini-DP-to-HDMI cable to the monitor (SONY), 
and is - in this case, contrary to the bug mentioned before - detected as can 
be seen by xrandr.
  But then it gives up after some time (see attachment of System Settings 
started f

[Kernel-packages] [Bug 1817918] Re: Hard lockups due to unrestricted lapic timer delay

2019-02-27 Thread Guilherme G. Piccoli
SRU request sent to the kernel team mailing list:
https://lists.ubuntu.com/archives/kernel-team/2019-February/098872.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/1817918

Title:
  Hard lockups due to unrestricted lapic timer delay

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

Bug description:
  [Impact]

  * There is a long-time report of an issue with the TSC delay present
  in wait_lapic_expire() - basically the guest could have an expiration
  timer configured in a way it induces host to wait a long time (with
  preemption disabled), so there's a potential scenario for host lockups.

  * The stack trace we have access (from an user report of this issue)
  is (summarized) below:

  NMI watchdog: Watchdog detected hard LOCKUP on cpu 16
  [...]
  CPU: 16 PID: 3024910 Comm: CPU 0/KVM Not tainted 4.4.0-139-generic #165-Ubuntu
  RIP: 0010:[]  [] delay_tsc+0x20/0x60
  [...]
   __delay+0x15/0x20
  wait_lapic_expire+0xc3/0x150 [kvm]
  vcpu_enter_guest+0x743/0x11d0 [kvm]
  kvm_arch_vcpu_ioctl_run+0xe6/0x410 [kvm]
  kvm_vcpu_ioctl+0x33d/0x620 [kvm]
  do_vfs_ioctl+0x2af/0x4b0
  ? __do_page_fault+0x1c1/0x410
  ? fire_user_return_notifiers+0x3e/0x50
  SyS_ioctl+0x79/0x90
  entry_SYSCALL_64_fastpath+0x22/0xc1

  This matches the reported problem in the KVM mailing-list:
  https://marc.info/?l=kvm&m=146374488028339

  * A fix was proposed in the above thread, but discarded in favor of the
  following approach: https://marc.info/?l=kvm&m=146647260109315
  The patch was merged in Linus tree, hence we hereby request the SRU:
  b606f189c7d5 ("KVM: LAPIC: cap __delay at lapic_timer_advance_ns").
  There's one additional patch needed, which is just the header adjustment
  for exporting a necessary function.

  * The patch is missing only in 4.4 kernel series; Bionic (4.15) and
  the other newer releases have the patch already.

  [Test Case]

  * Unfortunately this is a hard to reproduce issue; we have reports of
  this lockup from an user, hence the SRU request here.
  Also, the patch was introduced originally in kernel 4.7, approx. 2.5 years
  ago. So, we are confident that community is running this code long enough
  without errors reported. Also, checked in the Linus tree and no fixes
  for this code were introduced since kernel 4.7.

  [Regression Potential]

  * The code modification requested here affects the amount of delay in
  a specific timer; the patch introduces a maximum time for delay, preventing 
unbounded delays in host.
  The regression potential is considered low, and given the nature of the
  modification, latency issues in guests are likely to be the most problematic 
regression potential we have.

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

-- 
Mailing list: https://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 1817918] Re: Hard lockups due to unrestricted lapic timer delay

2019-02-27 Thread Guilherme G. Piccoli
** Description changed:

- There is a report of hard lockup induced by a long delay in lapic expiration 
timer.
- We'll provide SRU request here for merging the fixes in 4.4 kernel.
+ [Impact]
+ 
+ * There is a long-time report of an issue with the TSC delay present
+ in wait_lapic_expire() - basically the guest could have an expiration
+ timer configured in a way it induces host to wait a long time (with
+ preemption disabled), so there's a potential scenario for host lockups.
+ 
+ * The stack trace we have access (from an user report of this issue)
+ is (summarized) below:
+ 
+ NMI watchdog: Watchdog detected hard LOCKUP on cpu 16
+ [...]
+ CPU: 16 PID: 3024910 Comm: CPU 0/KVM Not tainted 4.4.0-139-generic #165-Ubuntu
+ RIP: 0010:[]  [] delay_tsc+0x20/0x60
+ [...]
+  __delay+0x15/0x20
+ wait_lapic_expire+0xc3/0x150 [kvm]
+ vcpu_enter_guest+0x743/0x11d0 [kvm]
+ kvm_arch_vcpu_ioctl_run+0xe6/0x410 [kvm]
+ kvm_vcpu_ioctl+0x33d/0x620 [kvm]
+ do_vfs_ioctl+0x2af/0x4b0
+ ? __do_page_fault+0x1c1/0x410
+ ? fire_user_return_notifiers+0x3e/0x50
+ SyS_ioctl+0x79/0x90
+ entry_SYSCALL_64_fastpath+0x22/0xc1
+ 
+ This matches the reported problem in the KVM mailing-list:
+ https://marc.info/?l=kvm&m=146374488028339
+ 
+ * A fix was proposed in the above thread, but discarded in favor of the
+ following approach: https://marc.info/?l=kvm&m=146647260109315
+ The patch was merged in Linus tree, hence we hereby request the SRU:
+ b606f189c7d5 ("KVM: LAPIC: cap __delay at lapic_timer_advance_ns").
+ There's one additional patch needed, which is just the header adjustment
+ for exporting a necessary function.
+ 
+ * The patch is missing only in 4.4 kernel series; Bionic (4.15) and the
+ other newer releases have the patch already.
+ 
+ [Test Case]
+ 
+ * Unfortunately this is a hard to reproduce issue; we have reports of
+ this lockup from an user, hence the SRU request here.
+ Also, the patch was introduced originally in kernel 4.7, approx. 2.5 years
+ ago. So, we are confident that community is running this code long enough
+ without errors reported. Also, checked in the Linus tree and no fixes
+ for this code were introduced since kernel 4.7.
+ 
+ [Regression Potential]
+ 
+ * The code modification requested here affects the amount of delay in
+ a specific timer; the patch introduces a maximum time for delay, preventing 
unbounded delays in host.
+ The regression potential is considered low, and given the nature of the
+ modification, latency issues in guests are likely to be the most problematic 
regression potential we have.

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

Title:
  Hard lockups due to unrestricted lapic timer delay

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

Bug description:
  [Impact]

  * There is a long-time report of an issue with the TSC delay present
  in wait_lapic_expire() - basically the guest could have an expiration
  timer configured in a way it induces host to wait a long time (with
  preemption disabled), so there's a potential scenario for host lockups.

  * The stack trace we have access (from an user report of this issue)
  is (summarized) below:

  NMI watchdog: Watchdog detected hard LOCKUP on cpu 16
  [...]
  CPU: 16 PID: 3024910 Comm: CPU 0/KVM Not tainted 4.4.0-139-generic #165-Ubuntu
  RIP: 0010:[]  [] delay_tsc+0x20/0x60
  [...]
   __delay+0x15/0x20
  wait_lapic_expire+0xc3/0x150 [kvm]
  vcpu_enter_guest+0x743/0x11d0 [kvm]
  kvm_arch_vcpu_ioctl_run+0xe6/0x410 [kvm]
  kvm_vcpu_ioctl+0x33d/0x620 [kvm]
  do_vfs_ioctl+0x2af/0x4b0
  ? __do_page_fault+0x1c1/0x410
  ? fire_user_return_notifiers+0x3e/0x50
  SyS_ioctl+0x79/0x90
  entry_SYSCALL_64_fastpath+0x22/0xc1

  This matches the reported problem in the KVM mailing-list:
  https://marc.info/?l=kvm&m=146374488028339

  * A fix was proposed in the above thread, but discarded in favor of the
  following approach: https://marc.info/?l=kvm&m=146647260109315
  The patch was merged in Linus tree, hence we hereby request the SRU:
  b606f189c7d5 ("KVM: LAPIC: cap __delay at lapic_timer_advance_ns").
  There's one additional patch needed, which is just the header adjustment
  for exporting a necessary function.

  * The patch is missing only in 4.4 kernel series; Bionic (4.15) and
  the other newer releases have the patch already.

  [Test Case]

  * Unfortunately this is a hard to reproduce issue; we have reports of
  this lockup from an user, hence the SRU request here.
  Also, the patch was introduced originally in kernel 4.7, approx. 2.5 years
  ago. So, we are confident that community is running this code long enough
  without errors reported. Also, checked in the Linus tree and no fixes
  for this code were introduced since kernel 4.7.

  [Regression Potential]

  * The code modification requested here affects 

[Kernel-packages] [Bug 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6

2019-02-27 Thread Brian Murray
** Changed in: linux-firmware (Ubuntu Bionic)
   Status: Fix Committed => Incomplete

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

Title:
  iwlwifi  Intel 8265 firmware crashing on lenovo x1 Gen 6

Status in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in The Bionic Beaver:
  New
Status in linux-firmware source package in Bionic:
  Incomplete
Status in The Cosmic Cuttlefish:
  New
Status in linux-firmware source package in Cosmic:
  Incomplete

Bug description:
  SRU Justification:
  ===
  [Impact]
  repeated crashes of the Intel 8265 wireless card on a Lenovo X1 Gen6.

  [Fix]
  New iwlwifi firmware fix it.

  [Test]
  Bug reporter verified with positive result.

  [Regression Potential]
  Upstream fix, low risk.
  Bug reporter confirms fix.

  
  Original bug report:
  =

  Seeing repeated crashes of the Intel 8265 wireless card on a Lenovo X1
  Gen6.

  Firmware: 36.7596afd4.0

  Dec 13 11:53:36 james-x1 kernel: [  856.840159] wlp2s0: send auth to 
60:38:e0:70:a2:11 (try 1/3)
  Dec 13 11:53:36 james-x1 kernel: [  856.844875] iwlwifi :02:00.0: 
Microcode SW error detected.  Restarting 0x200.
  Dec 13 11:53:36 james-x1 kernel: [  856.845015] iwlwifi :02:00.0: Start 
IWL Error Log Dump:
  Dec 13 11:53:36 james-x1 kernel: [  856.845018] iwlwifi :02:00.0: Status: 
0x0100, count: 6
  Dec 13 11:53:36 james-x1 kernel: [  856.845021] iwlwifi :02:00.0: Loaded 
firmware version: 36.7596afd4.0
  Dec 13 11:53:36 james-x1 kernel: [  856.845024] iwlwifi :02:00.0: 
0x1006 | ADVANCED_SYSASSERT
  Dec 13 11:53:36 james-x1 kernel: [  856.845026] iwlwifi :02:00.0: 
0x02F0 | trm_hw_status0
  Dec 13 11:53:36 james-x1 kernel: [  856.845029] iwlwifi :02:00.0: 
0x | trm_hw_status1
  Dec 13 11:53:36 james-x1 kernel: [  856.845031] iwlwifi :02:00.0: 
0x000248DC | branchlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845034] iwlwifi :02:00.0: 
0x0003A7DA | interruptlink1
  Dec 13 11:53:36 james-x1 kernel: [  856.845036] iwlwifi :02:00.0: 
0x | interruptlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845039] iwlwifi :02:00.0: 
0xFEDA | data1
  Dec 13 11:53:36 james-x1 kernel: [  856.845041] iwlwifi :02:00.0: 
0xDEADBEEF | data2
  Dec 13 11:53:36 james-x1 kernel: [  856.845044] iwlwifi :02:00.0: 
0xDEADBEEF | data3
  Dec 13 11:53:36 james-x1 kernel: [  856.845046] iwlwifi :02:00.0: 
0x0007E1DC | beacon time
  Dec 13 11:53:36 james-x1 kernel: [  856.845048] iwlwifi :02:00.0: 
0x003B0850 | tsf low
  Dec 13 11:53:36 james-x1 kernel: [  856.845051] iwlwifi :02:00.0: 
0x | tsf hi
  Dec 13 11:53:36 james-x1 kernel: [  856.845053] iwlwifi :02:00.0: 
0x | time gp1
  Dec 13 11:53:36 james-x1 kernel: [  856.845055] iwlwifi :02:00.0: 
0x003B0852 | time gp2
  Dec 13 11:53:36 james-x1 kernel: [  856.845058] iwlwifi :02:00.0: 
0x0001 | uCode revision type
  Dec 13 11:53:36 james-x1 kernel: [  856.845060] iwlwifi :02:00.0: 
0x0024 | uCode version major
  Dec 13 11:53:36 james-x1 kernel: [  856.845063] iwlwifi :02:00.0: 
0x7596AFD4 | uCode version minor
  Dec 13 11:53:36 james-x1 kernel: [  856.845065] iwlwifi :02:00.0: 
0x0230 | hw version
  Dec 13 11:53:36 james-x1 kernel: [  856.845068] iwlwifi :02:00.0: 
0x18489000 | board version
  Dec 13 11:53:36 james-x1 kernel: [  856.845070] iwlwifi :02:00.0: 
0x0501001C | hcmd
  Dec 13 11:53:36 james-x1 kernel: [  856.845072] iwlwifi :02:00.0: 
0x00023008 | isr0
  Dec 13 11:53:36 james-x1 kernel: [  856.845075] iwlwifi :02:00.0: 
0x000D | isr1
  Dec 13 11:53:36 james-x1 kernel: [  856.845077] iwlwifi :02:00.0: 
0x08001802 | isr2
  Dec 13 11:53:36 james-x1 kernel: [  856.845080] iwlwifi :02:00.0: 
0x0041FDC0 | isr3
  Dec 13 11:53:36 james-x1 kernel: [  856.845082] iwlwifi :02:00.0: 
0x | isr4
  Dec 13 11:53:36 james-x1 kernel: [  856.845084] iwlwifi :02:00.0: 
0x00580118 | last cmd Id
  Dec 13 11:53:36 james-x1 kernel: [  856.845087] iwlwifi :02:00.0: 
0x | wait_event
  Dec 13 11:53:36 james-x1 kernel: [  856.845089] iwlwifi :02:00.0: 
0x76DD | l2p_control
  Dec 13 11:53:36 james-x1 kernel: [  856.845091] iwlwifi :02:00.0: 
0x0020 | l2p_duration
  Dec 13 11:53:36 james-x1 kernel: [  856.845094] iwlwifi :02:00.0: 
0x | l2p_mhvalid
  Dec 13 11:53:36 james-x1 kernel: [  856.845096] iwlwifi :02:00.0: 
0x00A0 | l2p_addr_match
  Dec 13 11:53:36 james-x1 kernel: [  856.845099] iwlwifi :02:00.0: 
0x000D | lmpm_pmg_sel
  Dec 13 11:53:36 james-x1 kernel: [  856.845101] iwlwifi :02:00.0: 
0x22040707 | timestamp
  Dec 13 11:53:36 james-x1 kernel: [  856.845103] iwlwifi :02:00.0: 
0x6070 | flow_handler
  Dec 13 11:53:36 james-x1 kernel: [  856.845170] iwlwifi :02:

[Kernel-packages] [Bug 1817944] Re: Kubuntu 18.04 does not display through mini-DP port on lenovo Helix 2

2019-02-27 Thread udippel
Is it possible to remove a bug report, please?
I very much do hope so. Reason: I had bought a new cable mini-DP to HDMI 
(deleyCon), and found it also not working when booting to W10. Just rushed out 
and bought another one, another brand, and it works.

My face is red (I ought to have thought of and swapped the cable!), and
would appreciate a brown bag.

I can only offer my excuses!

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

Title:
  Kubuntu 18.04 does not display through mini-DP port on lenovo Helix 2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  (This is probably related to bug 1816860, but with different hardware
  and a different appearance, so it is filed separately.)

  Using the levovo Helix 2 attached to its Pro keyboard, it is not possible to 
activate the monitor as attached. 
  The monitor is attached with a mini-DP-to-HDMI cable to the monitor (SONY), 
and is - in this case, contrary to the bug mentioned before - detected as can 
be seen by xrandr.
  But then it gives up after some time (see attachment of System Settings 
started from CLI and Xorg.log:
  $ tail /var/log/Xorg.0.log
  [   970.977] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)  

  [   973.083] (II) modeset(0): EDID vendor "LGD", prod id 1121 


  [   973.083] (II) modeset(0): Printing DDC gathered Modelines:


  [   973.083] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1009.658] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1009.658] (II) modeset(0): Printing DDC gathered Modelines:
  [  1009.658] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1099.146] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1099.146] (II) modeset(0): Printing DDC gathered Modelines:
  [  1099.146] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)

  (and so it continues).

  Connecting the tablet of the convertable itself with a micro-HDMI-to-
  HDMI to that same monitor works fine, however.

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

-- 
Mailing list: https://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 1814736] Re: linux-kvm: 4.15.0-1030.30 -proposed tracker

2019-02-27 Thread Brad Figg
** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  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: 1814726
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:21 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-kvm: 4.15.0-1030.30 -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:
  Invalid
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-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  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: 1814726
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:21 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

-- 
Mailing list: https://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 1816782] Re: linux-azure: 4.18.0-1012.12~18.04.1 -proposed tracker

2019-02-27 Thread Joshua R. Poulson
I'm seeing a regression in 4.18.0-1012 on my GPU instances:
jrp@jrp1804un:~$ lspci
lspci: sysfs_scan: Invalid domain c810bada
jrp@jrp1804un:~$ nvidia-smi
No devices were found

This works on 4.18.0-1006

I think there was a conflict backing out LP 1816106

Thanks, --jrp

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

Title:
  linux-azure: 4.18.0-1012.12~18.04.1 -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:
  Invalid
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-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  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: 1814749
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:13 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

-- 
Mailing list: https://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 1814736] Re: linux-kvm: 4.15.0-1030.30 -proposed tracker

2019-02-27 Thread Sean Feole
** Tags added: regression-testing-passed

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

Title:
  linux-kvm: 4.15.0-1030.30 -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:
  Invalid
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-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  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: 1814726
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:21 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

-- 
Mailing list: https://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 1817036] Re: linux-azure: 4.15.0-1040.44~14.04.1 -proposed tracker

2019-02-27 Thread Sean Feole
** Tags removed: 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/1817036

Title:
  linux-azure: 4.15.0-1040.44~14.04.1 -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:
  Invalid
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:
  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 stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  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: 1814726
  phase: Ready for Promote to Proposed
  phase-changed: Tuesday, 26. February 2019 14:18 UTC
  reason:
promote-to-proposed: Pending -- ready for review

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

-- 
Mailing list: https://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 1793901] Re: kernel oops in bcache module

2019-02-27 Thread Mauricio Faria de Oliveira
For documentation purposes, this is the block device setup
configured in the system to debug/test/fix/verify the bug.

disk partitioning:

# fdisk /dev/sdb # create sdb1 and sbd2, 100G each.

bcache backing device: LVM volume in partition 1

# pvcreate /dev/sdb1
# vgcreate vg-test /dev/sdb1
# lvcreate vg-test -n lv-test --size 99G

bcache caching device: partition 2

# make-bcache -B /dev/mapper/vg--test-lv--test
# make-bcache -C /dev/sdb2

bcache attach:

# bcache-super-show /dev/sdb2 | grep cset.uuid
cset.uuid 73f95583-561c-408f-a93a-4cbd2498f5c8

# echo 73f95583-561c-408f-a93a-4cbd2498f5c8 >
/sys/block/bcache0/bcache/attach

bcache writeback mode (important):

# echo writeback > /sys/block/bcache0/bcache/cache_mode

block device topology:

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 931.5G 0 disk
├─sdb2 8:18 0 100G 0 part
│ └─bcache0 252:0 0 99G 0 disk /test
└─sdb1 8:17 0 100G 0 part
└─vg--test-lv--test 253:0 0 99G 0 lvm
└─bcache0 252:0 0 99G 0 disk /test
sda 8:0 0 931.5G 0 disk
├─sda2 8:2 0 931G 0 part /
└─sda1 8:1 0 512M 0 part /boot/efi

filesystem

# mkfs.ext4 /dev/bcache0

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

Title:
  kernel oops in bcache module

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  SRU Justification
  =

  [Impact]

  Some users see panics like the following when performing fstrim on a
  bcached volume:

  [  529.803060] BUG: unable to handle kernel NULL pointer dereference at 
0008
  [  530.183928] #PF error: [normal kernel read fault]
  [  530.412392] PGD 801f42163067 P4D 801f42163067 PUD 1f42168067 PMD 0
  [  530.750887] Oops:  [#1] SMP PTI
  [  530.920869] CPU: 10 PID: 4167 Comm: fstrim Kdump: loaded Not tainted 
5.0.0-rc1+ #3
  [  531.290204] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, 
BIOS P89 12/27/2015
  [  531.693137] RIP: 0010:blk_queue_split+0x148/0x620
  [  531.922205] Code: 60 38 89 55 a0 45 31 db 45 31 f6 45 31 c9 31 ff 89 4d 98 
85 db 0f 84 7f 04 00 00 44 8b 6d 98 4c 89 ee 48 c1 e6 04 49 03 70 78 <8b> 46 08 
44 8b 56 0c 48
  8b 16 44 29 e0 39 d8 48 89 55 a8 0f 47 c3
  [  532.838634] RSP: 0018:b9b708df39b0 EFLAGS: 00010246
  [  533.093571] RAX:  RBX: 00046000 RCX: 

  [  533.441865] RDX: 0200 RSI:  RDI: 

  [  533.789922] RBP: b9b708df3a48 R08: 940d3b3fdd20 R09: 

  [  534.137512] R10: b9b708df3958 R11:  R12: 

  [  534.485329] R13:  R14:  R15: 
940d39212020
  [  534.833319] FS:  7efec26e3840() GS:940d1f48() 
knlGS:
  [  535.224098] CS:  0010 DS:  ES:  CR0: 80050033
  [  535.504318] CR2: 0008 CR3: 001f4e256004 CR4: 
001606e0
  [  535.851759] Call Trace:
  [  535.970308]  ? mempool_alloc_slab+0x15/0x20
  [  536.174152]  ? bch_data_insert+0x42/0xd0 [bcache]
  [  536.403399]  blk_mq_make_request+0x97/0x4f0
  [  536.607036]  generic_make_request+0x1e2/0x410
  [  536.819164]  submit_bio+0x73/0x150
  [  536.980168]  ? submit_bio+0x73/0x150
  [  537.149731]  ? bio_associate_blkg_from_css+0x3b/0x60
  [  537.391595]  ? _cond_resched+0x1a/0x50
  [  537.573774]  submit_bio_wait+0x59/0x90
  [  537.756105]  blkdev_issue_discard+0x80/0xd0
  [  537.959590]  ext4_trim_fs+0x4a9/0x9e0
  [  538.137636]  ? ext4_trim_fs+0x4a9/0x9e0
  [  538.324087]  ext4_ioctl+0xea4/0x1530
  [  538.497712]  ? _copy_to_user+0x2a/0x40
  [  538.679632]  do_vfs_ioctl+0xa6/0x600
  [  538.853127]  ? __do_sys_newfstat+0x44/0x70
  [  539.051951]  ksys_ioctl+0x6d/0x80
  [  539.212785]  __x64_sys_ioctl+0x1a/0x20
  [  539.394918]  do_syscall_64+0x5a/0x110
  [  539.568674]  entry_SYSCALL_64_after_hwframe+0x44/0xa9

  [Fix]

  Under certain conditions, the test for whether an operation should be
  written back to the underlying device was incorrect. Specifically, in
  should_writeback(), we were hitting a case where an optimisation for
  partial stripe conditions was returning true and so should_writeback()
  was returning true early. This caused the code to go down an incorrect
  path and create bios that contained NULL pointers.

  To fix this issue, make sure that should_writeback() on a discard op
  never returns true.

  
  [Test Case]

  We have observed it on some systems where both:
  1) LVM/devmapper is involved (bcache backing device is LVM volume) and
  2) writeback cache is involved (bcache cache_mode is writeback)

  Not every machine exhibits the bug. On one machine that does exhibit
  the bug, we can reliabl

[Kernel-packages] [Bug 1793901] Re: kernel oops in bcache module

2019-02-27 Thread Mauricio Faria de Oliveira
trusty-proposed:
---

verification successful.
executed the reproducer 3x on the system used to debug/test/fix this problem.
no bug/oops observed.

root@petilil:~# uname -rv
3.13.0-166-generic #216-Ubuntu SMP Thu Feb 7 14:07:53 UTC 2019

root@petilil:~# echo writeback > /sys/block/bcache0/bcache/cache_mode
root@petilil:~# mount /dev/bcache0 /test
root@petilil:~# for i in {0..10}; do file="$(mktemp /test/zero.XXX)"; dd 
if=/dev/zero of="$file" bs=1M count=256; sync; rm $file; done; fstrim -v /test
<...>
/test: 96.8 GiB (103898910720 bytes) trimmed

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

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

Title:
  kernel oops in bcache module

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  SRU Justification
  =

  [Impact]

  Some users see panics like the following when performing fstrim on a
  bcached volume:

  [  529.803060] BUG: unable to handle kernel NULL pointer dereference at 
0008
  [  530.183928] #PF error: [normal kernel read fault]
  [  530.412392] PGD 801f42163067 P4D 801f42163067 PUD 1f42168067 PMD 0
  [  530.750887] Oops:  [#1] SMP PTI
  [  530.920869] CPU: 10 PID: 4167 Comm: fstrim Kdump: loaded Not tainted 
5.0.0-rc1+ #3
  [  531.290204] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, 
BIOS P89 12/27/2015
  [  531.693137] RIP: 0010:blk_queue_split+0x148/0x620
  [  531.922205] Code: 60 38 89 55 a0 45 31 db 45 31 f6 45 31 c9 31 ff 89 4d 98 
85 db 0f 84 7f 04 00 00 44 8b 6d 98 4c 89 ee 48 c1 e6 04 49 03 70 78 <8b> 46 08 
44 8b 56 0c 48
  8b 16 44 29 e0 39 d8 48 89 55 a8 0f 47 c3
  [  532.838634] RSP: 0018:b9b708df39b0 EFLAGS: 00010246
  [  533.093571] RAX:  RBX: 00046000 RCX: 

  [  533.441865] RDX: 0200 RSI:  RDI: 

  [  533.789922] RBP: b9b708df3a48 R08: 940d3b3fdd20 R09: 

  [  534.137512] R10: b9b708df3958 R11:  R12: 

  [  534.485329] R13:  R14:  R15: 
940d39212020
  [  534.833319] FS:  7efec26e3840() GS:940d1f48() 
knlGS:
  [  535.224098] CS:  0010 DS:  ES:  CR0: 80050033
  [  535.504318] CR2: 0008 CR3: 001f4e256004 CR4: 
001606e0
  [  535.851759] Call Trace:
  [  535.970308]  ? mempool_alloc_slab+0x15/0x20
  [  536.174152]  ? bch_data_insert+0x42/0xd0 [bcache]
  [  536.403399]  blk_mq_make_request+0x97/0x4f0
  [  536.607036]  generic_make_request+0x1e2/0x410
  [  536.819164]  submit_bio+0x73/0x150
  [  536.980168]  ? submit_bio+0x73/0x150
  [  537.149731]  ? bio_associate_blkg_from_css+0x3b/0x60
  [  537.391595]  ? _cond_resched+0x1a/0x50
  [  537.573774]  submit_bio_wait+0x59/0x90
  [  537.756105]  blkdev_issue_discard+0x80/0xd0
  [  537.959590]  ext4_trim_fs+0x4a9/0x9e0
  [  538.137636]  ? ext4_trim_fs+0x4a9/0x9e0
  [  538.324087]  ext4_ioctl+0xea4/0x1530
  [  538.497712]  ? _copy_to_user+0x2a/0x40
  [  538.679632]  do_vfs_ioctl+0xa6/0x600
  [  538.853127]  ? __do_sys_newfstat+0x44/0x70
  [  539.051951]  ksys_ioctl+0x6d/0x80
  [  539.212785]  __x64_sys_ioctl+0x1a/0x20
  [  539.394918]  do_syscall_64+0x5a/0x110
  [  539.568674]  entry_SYSCALL_64_after_hwframe+0x44/0xa9

  [Fix]

  Under certain conditions, the test for whether an operation should be
  written back to the underlying device was incorrect. Specifically, in
  should_writeback(), we were hitting a case where an optimisation for
  partial stripe conditions was returning true and so should_writeback()
  was returning true early. This caused the code to go down an incorrect
  path and create bios that contained NULL pointers.

  To fix this issue, make sure that should_writeback() on a discard op
  never returns true.

  
  [Test Case]

  We have observed it on some systems where both:
  1) LVM/devmapper is involved (bcache backing device is LVM volume) and
  2) writeback cache is involved (bcache cache_mode is writeback)

  Not every machine exhibits the bug. On one machine that does exhibit
  the bug, we can reliably reproduce it with:

   # echo writeback > /sys/block/bcache0/bcache/cache_mode
   # mount /dev/bcache0 /test
   # for i in {0..10}; do file="$(mktemp /test/zero.XXX)"; dd if=/dev/zero 
of="$file" bs=1M count=256; sync; rm $file; done; fstrim -v /test

  
  [Regression Potential]

  This could affect any device where bcache is used.

  In mitigation, however: the patch is simple, is limited to considering
  discard operations. The patch has been accepted upstream [1] a

[Kernel-packages] [Bug 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep

2019-02-27 Thread mx80
I have the same problem on Asus Zenbook UX433F. With s2idle, suspend the
battery drain rate is 3.3W, while in deep it's 1.2W. (Powered on, it's
about 6W). So if I suspend it when the battery is half empty, it'll be
dead overnight.

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

Title:
  Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It seems that the Dell 9370 is set to go into s2idle mode rather than
  deep sleep, forgoing significant power savings.

  I have confirmed this by suspending and then checking:
  sudo journalctl | grep "PM: suspend" | tail -2. If the output is

  PM: suspend entry (s2idle)
  PM: suspend exit

  cat /sys/power/mem_sleep showed

  [s2idle] deep

  As a temporary fix, I typed 
  echo deep > /sys/power/mem_sleep 
  as a root user (sudo -i). 

  Then the output of cat /sys/power/mem_sleep was
  s2idle [deep]

  After suspending now, 
  sudo journalctl | grep "PM: suspend" | tail -2 returns

  PM: suspend entry (deep)
  PM: suspend exit

  I have made this permanent by editing 
  /etc/default/grub

  and replacing
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
  with
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep"

  then regenerating my grub configuration (sudo grub-mkconfig -o
  /boot/grub/grub.cfg).

  This appears to be working with no ill effects.

  Credit to https://askubuntu.com/a/1036122/470077

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron-work   3672 F pulseaudio
   /dev/snd/pcmC0D0p:   aaron-work   3672 F...m pulseaudio
  Date: Tue Dec 18 09:52:44 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=/dev/ubuntu-vg/swap_1
  InstallationDate: Installed on 2018-09-04 (104 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  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 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep 
vt.handoff=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.175.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-10-26 (52 days ago)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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 1809993] Re: Lenovo X1C6 trackpad functions broken

2019-02-27 Thread Kai-Heng Feng
Thanks.

Please re-open this if it happens again.

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

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

Title:
  Lenovo X1C6 trackpad functions broken

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Summary:
  After kernel update the trackpad advanced functions, like two finger 
scrolling and mouse acceleration have stopped working.

  Expected Result:
  Two finer scroll works and the mouse has acceleration features work

  Actual Result:
  Two finer scroll works and the mouse has acceleration features do not work

  Steps to reproduce:
  1. Lenovo X1C6 (LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET59W (1.34 ) 
11/08/2018)
  2. Install 18.04 LTS
  3. config-4.15.0-42-generic acceleration works, while 
config-4.15.0-43-generic does not

  This appears to be some sort of regression or change in behavior between 
kernel versions.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  powersj1597 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1eb43198-8ef5-4035-8b81-74c3e2936ad7
  InstallationDate: Installed on 2018-12-06 (22 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KHCTO1WW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET59W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET59W(1.34):bd11/08/2018:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1793901] Re: kernel oops in bcache module

2019-02-27 Thread Mauricio Faria de Oliveira
xenial-proposed:
---

verification successful.
executed the reproducer 3x on the system used to debug/test/fix this problem.
no bug/oops observed.

root@petilil:~# uname -rv
4.4.0-143-generic #169-Ubuntu SMP Thu Feb 7 07:56:38 UTC 2019


root@petilil:~# echo writeback > /sys/block/bcache0/bcache/cache_mode
root@petilil:~# mount /dev/bcache0 /test
root@petilil:~# for i in {0..10}; do file="$(mktemp /test/zero.XXX)"; dd 
if=/dev/zero of="$file" bs=1M count=256; sync; rm $file; done; fstrim -v /test
<...>
/test: 96.8 GiB (103898910720 bytes) trimmed


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

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

Title:
  kernel oops in bcache module

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  SRU Justification
  =

  [Impact]

  Some users see panics like the following when performing fstrim on a
  bcached volume:

  [  529.803060] BUG: unable to handle kernel NULL pointer dereference at 
0008
  [  530.183928] #PF error: [normal kernel read fault]
  [  530.412392] PGD 801f42163067 P4D 801f42163067 PUD 1f42168067 PMD 0
  [  530.750887] Oops:  [#1] SMP PTI
  [  530.920869] CPU: 10 PID: 4167 Comm: fstrim Kdump: loaded Not tainted 
5.0.0-rc1+ #3
  [  531.290204] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, 
BIOS P89 12/27/2015
  [  531.693137] RIP: 0010:blk_queue_split+0x148/0x620
  [  531.922205] Code: 60 38 89 55 a0 45 31 db 45 31 f6 45 31 c9 31 ff 89 4d 98 
85 db 0f 84 7f 04 00 00 44 8b 6d 98 4c 89 ee 48 c1 e6 04 49 03 70 78 <8b> 46 08 
44 8b 56 0c 48
  8b 16 44 29 e0 39 d8 48 89 55 a8 0f 47 c3
  [  532.838634] RSP: 0018:b9b708df39b0 EFLAGS: 00010246
  [  533.093571] RAX:  RBX: 00046000 RCX: 

  [  533.441865] RDX: 0200 RSI:  RDI: 

  [  533.789922] RBP: b9b708df3a48 R08: 940d3b3fdd20 R09: 

  [  534.137512] R10: b9b708df3958 R11:  R12: 

  [  534.485329] R13:  R14:  R15: 
940d39212020
  [  534.833319] FS:  7efec26e3840() GS:940d1f48() 
knlGS:
  [  535.224098] CS:  0010 DS:  ES:  CR0: 80050033
  [  535.504318] CR2: 0008 CR3: 001f4e256004 CR4: 
001606e0
  [  535.851759] Call Trace:
  [  535.970308]  ? mempool_alloc_slab+0x15/0x20
  [  536.174152]  ? bch_data_insert+0x42/0xd0 [bcache]
  [  536.403399]  blk_mq_make_request+0x97/0x4f0
  [  536.607036]  generic_make_request+0x1e2/0x410
  [  536.819164]  submit_bio+0x73/0x150
  [  536.980168]  ? submit_bio+0x73/0x150
  [  537.149731]  ? bio_associate_blkg_from_css+0x3b/0x60
  [  537.391595]  ? _cond_resched+0x1a/0x50
  [  537.573774]  submit_bio_wait+0x59/0x90
  [  537.756105]  blkdev_issue_discard+0x80/0xd0
  [  537.959590]  ext4_trim_fs+0x4a9/0x9e0
  [  538.137636]  ? ext4_trim_fs+0x4a9/0x9e0
  [  538.324087]  ext4_ioctl+0xea4/0x1530
  [  538.497712]  ? _copy_to_user+0x2a/0x40
  [  538.679632]  do_vfs_ioctl+0xa6/0x600
  [  538.853127]  ? __do_sys_newfstat+0x44/0x70
  [  539.051951]  ksys_ioctl+0x6d/0x80
  [  539.212785]  __x64_sys_ioctl+0x1a/0x20
  [  539.394918]  do_syscall_64+0x5a/0x110
  [  539.568674]  entry_SYSCALL_64_after_hwframe+0x44/0xa9

  [Fix]

  Under certain conditions, the test for whether an operation should be
  written back to the underlying device was incorrect. Specifically, in
  should_writeback(), we were hitting a case where an optimisation for
  partial stripe conditions was returning true and so should_writeback()
  was returning true early. This caused the code to go down an incorrect
  path and create bios that contained NULL pointers.

  To fix this issue, make sure that should_writeback() on a discard op
  never returns true.

  
  [Test Case]

  We have observed it on some systems where both:
  1) LVM/devmapper is involved (bcache backing device is LVM volume) and
  2) writeback cache is involved (bcache cache_mode is writeback)

  Not every machine exhibits the bug. On one machine that does exhibit
  the bug, we can reliably reproduce it with:

   # echo writeback > /sys/block/bcache0/bcache/cache_mode
   # mount /dev/bcache0 /test
   # for i in {0..10}; do file="$(mktemp /test/zero.XXX)"; dd if=/dev/zero 
of="$file" bs=1M count=256; sync; rm $file; done; fstrim -v /test

  
  [Regression Potential]

  This could affect any device where bcache is used.

  In mitigation, however: the patch is simple, is limited to considering
  discard operations. The patch has been accepted upstream [1] 

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

2019-02-27 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 1817944

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

Title:
  Kubuntu 18.04 does not display through mini-DP port on lenovo Helix 2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  (This is probably related to bug 1816860, but with different hardware
  and a different appearance, so it is filed separately.)

  Using the levovo Helix 2 attached to its Pro keyboard, it is not possible to 
activate the monitor as attached. 
  The monitor is attached with a mini-DP-to-HDMI cable to the monitor (SONY), 
and is - in this case, contrary to the bug mentioned before - detected as can 
be seen by xrandr.
  But then it gives up after some time (see attachment of System Settings 
started from CLI and Xorg.log:
  $ tail /var/log/Xorg.0.log
  [   970.977] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)  

  [   973.083] (II) modeset(0): EDID vendor "LGD", prod id 1121 


  [   973.083] (II) modeset(0): Printing DDC gathered Modelines:


  [   973.083] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1009.658] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1009.658] (II) modeset(0): Printing DDC gathered Modelines:
  [  1009.658] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1099.146] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1099.146] (II) modeset(0): Printing DDC gathered Modelines:
  [  1099.146] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)

  (and so it continues).

  Connecting the tablet of the convertable itself with a micro-HDMI-to-
  HDMI to that same monitor works fine, however.

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

-- 
Mailing list: https://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 1793901] Re: kernel oops in bcache module

2019-02-27 Thread Mauricio Faria de Oliveira
bionic-proposed:
---

verification successful.
executed the reproducer 3x on the system used to debug/test/fix this problem.
no bug/oops observed.

root@petilil:~# uname -rv
4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019

root@petilil:~# echo writeback > /sys/block/bcache0/bcache/cache_mode
root@petilil:~# mount /dev/bcache0 /test
root@petilil:~# for i in {0..10}; do file="$(mktemp /test/zero.XXX)"; dd 
if=/dev/zero of="$file" bs=1M count=256; sync; rm $file; done; fstrim -v /test
<...>
/test: 96.8 GiB (103898910720 bytes) trimmed


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

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

Title:
  kernel oops in bcache module

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  SRU Justification
  =

  [Impact]

  Some users see panics like the following when performing fstrim on a
  bcached volume:

  [  529.803060] BUG: unable to handle kernel NULL pointer dereference at 
0008
  [  530.183928] #PF error: [normal kernel read fault]
  [  530.412392] PGD 801f42163067 P4D 801f42163067 PUD 1f42168067 PMD 0
  [  530.750887] Oops:  [#1] SMP PTI
  [  530.920869] CPU: 10 PID: 4167 Comm: fstrim Kdump: loaded Not tainted 
5.0.0-rc1+ #3
  [  531.290204] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, 
BIOS P89 12/27/2015
  [  531.693137] RIP: 0010:blk_queue_split+0x148/0x620
  [  531.922205] Code: 60 38 89 55 a0 45 31 db 45 31 f6 45 31 c9 31 ff 89 4d 98 
85 db 0f 84 7f 04 00 00 44 8b 6d 98 4c 89 ee 48 c1 e6 04 49 03 70 78 <8b> 46 08 
44 8b 56 0c 48
  8b 16 44 29 e0 39 d8 48 89 55 a8 0f 47 c3
  [  532.838634] RSP: 0018:b9b708df39b0 EFLAGS: 00010246
  [  533.093571] RAX:  RBX: 00046000 RCX: 

  [  533.441865] RDX: 0200 RSI:  RDI: 

  [  533.789922] RBP: b9b708df3a48 R08: 940d3b3fdd20 R09: 

  [  534.137512] R10: b9b708df3958 R11:  R12: 

  [  534.485329] R13:  R14:  R15: 
940d39212020
  [  534.833319] FS:  7efec26e3840() GS:940d1f48() 
knlGS:
  [  535.224098] CS:  0010 DS:  ES:  CR0: 80050033
  [  535.504318] CR2: 0008 CR3: 001f4e256004 CR4: 
001606e0
  [  535.851759] Call Trace:
  [  535.970308]  ? mempool_alloc_slab+0x15/0x20
  [  536.174152]  ? bch_data_insert+0x42/0xd0 [bcache]
  [  536.403399]  blk_mq_make_request+0x97/0x4f0
  [  536.607036]  generic_make_request+0x1e2/0x410
  [  536.819164]  submit_bio+0x73/0x150
  [  536.980168]  ? submit_bio+0x73/0x150
  [  537.149731]  ? bio_associate_blkg_from_css+0x3b/0x60
  [  537.391595]  ? _cond_resched+0x1a/0x50
  [  537.573774]  submit_bio_wait+0x59/0x90
  [  537.756105]  blkdev_issue_discard+0x80/0xd0
  [  537.959590]  ext4_trim_fs+0x4a9/0x9e0
  [  538.137636]  ? ext4_trim_fs+0x4a9/0x9e0
  [  538.324087]  ext4_ioctl+0xea4/0x1530
  [  538.497712]  ? _copy_to_user+0x2a/0x40
  [  538.679632]  do_vfs_ioctl+0xa6/0x600
  [  538.853127]  ? __do_sys_newfstat+0x44/0x70
  [  539.051951]  ksys_ioctl+0x6d/0x80
  [  539.212785]  __x64_sys_ioctl+0x1a/0x20
  [  539.394918]  do_syscall_64+0x5a/0x110
  [  539.568674]  entry_SYSCALL_64_after_hwframe+0x44/0xa9

  [Fix]

  Under certain conditions, the test for whether an operation should be
  written back to the underlying device was incorrect. Specifically, in
  should_writeback(), we were hitting a case where an optimisation for
  partial stripe conditions was returning true and so should_writeback()
  was returning true early. This caused the code to go down an incorrect
  path and create bios that contained NULL pointers.

  To fix this issue, make sure that should_writeback() on a discard op
  never returns true.

  
  [Test Case]

  We have observed it on some systems where both:
  1) LVM/devmapper is involved (bcache backing device is LVM volume) and
  2) writeback cache is involved (bcache cache_mode is writeback)

  Not every machine exhibits the bug. On one machine that does exhibit
  the bug, we can reliably reproduce it with:

   # echo writeback > /sys/block/bcache0/bcache/cache_mode
   # mount /dev/bcache0 /test
   # for i in {0..10}; do file="$(mktemp /test/zero.XXX)"; dd if=/dev/zero 
of="$file" bs=1M count=256; sync; rm $file; done; fstrim -v /test

  
  [Regression Potential]

  This could affect any device where bcache is used.

  In mitigation, however: the patch is simple, is limited to considering
  discard operations. The patch has been accepted upstream [1] an

[Kernel-packages] [Bug 1817036] Re: linux-azure: 4.15.0-1040.44~14.04.1 -proposed tracker

2019-02-27 Thread Sean Feole
** 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/1817036

Title:
  linux-azure: 4.15.0-1040.44~14.04.1 -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:
  Invalid
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:
  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 stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  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: 1814726
  phase: Ready for Promote to Proposed
  phase-changed: Tuesday, 26. February 2019 14:18 UTC
  reason:
promote-to-proposed: Pending -- ready for review

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

-- 
Mailing list: https://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 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370

2019-02-27 Thread Raphael Kimmig
I'll gladly try any patches, if that would be helpful to you. I do
however not use ubuntu, so the kernel in #50 is not really an option.

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

Title:
  Missing wifi and bluetooth after sleep on XPS 9370

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  I have XPS9370 with self-installed Ubuntu 18.10 (not project sputnik) with 
Killer 1435 wireless module.
  And sometimes I find wifi and bluetooth missing after sleep. I cannot exactly 
define preconditions, but it seems there are following steps to reproduce the 
issue
  1. Connect something via bluetooth  (I use bluetooth headset)
  2. Send laptop to sleep
  3. Wake it and find wifi and bluetooth missing.

  I have to mention that I have also been experienced bluetooth only
  missing, but it somehow transformed to the issue with both wireless
  devices.

  Dmesg after waking up with the issue attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kao2362 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-09-22 (33 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 012: ID 0489:e0a2 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=34230cbd-d3d2-4cb8-855a-307883bc35ea ro quiet splash 
mem_sleep_default=deep video=1920x1080 usbcore.dyndbg=+p vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0VM1FG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0VM1FG:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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 1793901] Re: kernel oops in bcache module

2019-02-27 Thread Mauricio Faria de Oliveira
cosmic-proposed:
---

verification successful.
executed the reproducer 3x on the system used to debug/test/fix this problem.
no bug/oops observed.

root@petilil:~# uname -rv
4.18.0-16-generic #17-Ubuntu SMP Fri Feb 8 00:06:57 UTC 2019

root@petilil:~# echo writeback > /sys/block/bcache0/bcache/cache_mode
root@petilil:~# mount /dev/bcache0 /test
root@petilil:~# for i in {0..10}; do file="$(mktemp /test/zero.XXX)"; dd 
if=/dev/zero of="$file" bs=1M count=256; sync; rm $file; done; fstrim -v /test
<...>
/test: 96.8 GiB (103898910720 bytes) trimmed


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

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

Title:
  kernel oops in bcache module

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  SRU Justification
  =

  [Impact]

  Some users see panics like the following when performing fstrim on a
  bcached volume:

  [  529.803060] BUG: unable to handle kernel NULL pointer dereference at 
0008
  [  530.183928] #PF error: [normal kernel read fault]
  [  530.412392] PGD 801f42163067 P4D 801f42163067 PUD 1f42168067 PMD 0
  [  530.750887] Oops:  [#1] SMP PTI
  [  530.920869] CPU: 10 PID: 4167 Comm: fstrim Kdump: loaded Not tainted 
5.0.0-rc1+ #3
  [  531.290204] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, 
BIOS P89 12/27/2015
  [  531.693137] RIP: 0010:blk_queue_split+0x148/0x620
  [  531.922205] Code: 60 38 89 55 a0 45 31 db 45 31 f6 45 31 c9 31 ff 89 4d 98 
85 db 0f 84 7f 04 00 00 44 8b 6d 98 4c 89 ee 48 c1 e6 04 49 03 70 78 <8b> 46 08 
44 8b 56 0c 48
  8b 16 44 29 e0 39 d8 48 89 55 a8 0f 47 c3
  [  532.838634] RSP: 0018:b9b708df39b0 EFLAGS: 00010246
  [  533.093571] RAX:  RBX: 00046000 RCX: 

  [  533.441865] RDX: 0200 RSI:  RDI: 

  [  533.789922] RBP: b9b708df3a48 R08: 940d3b3fdd20 R09: 

  [  534.137512] R10: b9b708df3958 R11:  R12: 

  [  534.485329] R13:  R14:  R15: 
940d39212020
  [  534.833319] FS:  7efec26e3840() GS:940d1f48() 
knlGS:
  [  535.224098] CS:  0010 DS:  ES:  CR0: 80050033
  [  535.504318] CR2: 0008 CR3: 001f4e256004 CR4: 
001606e0
  [  535.851759] Call Trace:
  [  535.970308]  ? mempool_alloc_slab+0x15/0x20
  [  536.174152]  ? bch_data_insert+0x42/0xd0 [bcache]
  [  536.403399]  blk_mq_make_request+0x97/0x4f0
  [  536.607036]  generic_make_request+0x1e2/0x410
  [  536.819164]  submit_bio+0x73/0x150
  [  536.980168]  ? submit_bio+0x73/0x150
  [  537.149731]  ? bio_associate_blkg_from_css+0x3b/0x60
  [  537.391595]  ? _cond_resched+0x1a/0x50
  [  537.573774]  submit_bio_wait+0x59/0x90
  [  537.756105]  blkdev_issue_discard+0x80/0xd0
  [  537.959590]  ext4_trim_fs+0x4a9/0x9e0
  [  538.137636]  ? ext4_trim_fs+0x4a9/0x9e0
  [  538.324087]  ext4_ioctl+0xea4/0x1530
  [  538.497712]  ? _copy_to_user+0x2a/0x40
  [  538.679632]  do_vfs_ioctl+0xa6/0x600
  [  538.853127]  ? __do_sys_newfstat+0x44/0x70
  [  539.051951]  ksys_ioctl+0x6d/0x80
  [  539.212785]  __x64_sys_ioctl+0x1a/0x20
  [  539.394918]  do_syscall_64+0x5a/0x110
  [  539.568674]  entry_SYSCALL_64_after_hwframe+0x44/0xa9

  [Fix]

  Under certain conditions, the test for whether an operation should be
  written back to the underlying device was incorrect. Specifically, in
  should_writeback(), we were hitting a case where an optimisation for
  partial stripe conditions was returning true and so should_writeback()
  was returning true early. This caused the code to go down an incorrect
  path and create bios that contained NULL pointers.

  To fix this issue, make sure that should_writeback() on a discard op
  never returns true.

  
  [Test Case]

  We have observed it on some systems where both:
  1) LVM/devmapper is involved (bcache backing device is LVM volume) and
  2) writeback cache is involved (bcache cache_mode is writeback)

  Not every machine exhibits the bug. On one machine that does exhibit
  the bug, we can reliably reproduce it with:

   # echo writeback > /sys/block/bcache0/bcache/cache_mode
   # mount /dev/bcache0 /test
   # for i in {0..10}; do file="$(mktemp /test/zero.XXX)"; dd if=/dev/zero 
of="$file" bs=1M count=256; sync; rm $file; done; fstrim -v /test

  
  [Regression Potential]

  This could affect any device where bcache is used.

  In mitigation, however: the patch is simple, is limited to considering
  discard operations. The patch has been accepted upstream [1] an

[Kernel-packages] [Bug 1816783] Re: linux-azure: 4.18.0-1012.12 -proposed tracker

2019-02-27 Thread Sean Feole
** 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/1816783

Title:
  linux-azure: 4.18.0-1012.12 -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:
  Invalid
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-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  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: 1814749
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:17 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

-- 
Mailing list: https://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 1816783] Re: linux-azure: 4.18.0-1012.12 -proposed tracker

2019-02-27 Thread Brad Figg
** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  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: 1814749
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:17 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.18.0-1012.12 -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:
  Invalid
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-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  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: 1814749
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:17 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

-- 
Mailing list: https://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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

2019-02-27 Thread Brian Murray
Hello Agustin, or anyone else affected,

Accepted gnome-control-center into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/gnome-control-center/1:3.28.2-0ubuntu0.18.04.3 in a few hours, and then
in the -proposed repository.

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

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

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

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

** Changed in: gnome-control-center (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in upower source package in Bionic:
  Incomplete
Status in gnome-control-center source package in Cosmic:
  Fix Released
Status in gnome-shell source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Released
Status in upower source package in Cosmic:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.produc

Re: [Kernel-packages] [Bug 1816947] Re: [Dell XPS L321X] Touchpad not working after last apt-get upgrade

2019-02-27 Thread opensas
Thanks for the tip (I didn't know which packages to include), I'll give it
a try asap

On Wed, Feb 27, 2019 at 12:20 PM Timo Aaltonen 
wrote:

> Yes, in #43 you said that you tested 4.13.0-19.22 but didn't seem to
> install the package with the drivers (linux-image-extra). If you do,
> does it work like the live version did?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1816947
>
> Title:
>   [Dell XPS L321X] Touchpad not working after last apt-get upgrade
>
> Status in libinput package in Ubuntu:
>   Invalid
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   The touchpad doesn't work unless the cursor is moved slowly.
>
>   WORKAROUND: Execute at a terminal:
>   sudo modprobe -r psmouse
>   sudo modprobe psmouse proto=imps
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 19.04
>   Package: xorg 1:7.7+19ubuntu8
>   ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
>   Uname: Linux 4.18.0-11-generic x86_64
>   ApportVersion: 2.20.10-0ubuntu19
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CasperVersion: 1.402
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Thu Feb 21 02:56:45 2019
>   DistUpgraded: Fresh install
>   DistroCodename: disco
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes
>   GraphicsCard:
>Intel Corporation 2nd Generation Core Processor Family Integrated
> Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
>  Subsystem: Dell 2nd Generation Core Processor Family Integrated
> Graphics Controller [1028:052e]
>   LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
>   MachineType: Dell Inc. Dell System XPS L321X
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=C.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper
> initrd=/casper/initrd quiet splash --- maybe-ubiquity
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 12/27/2011
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: A01
>   dmi.board.vendor: Dell Inc.
>   dmi.chassis.type: 8
>   dmi.chassis.vendor: Dell Inc.
>   dmi.chassis.version: 0.1
>   dmi.modalias:
> dmi:bvnDellInc.:bvrA01:bd12/27/2011:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
>   dmi.product.family: HuronRiver System
>   dmi.product.name: Dell System XPS L321X
>   dmi.product.sku: System SKUNumber
>   dmi.sys.vendor: Dell Inc.
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.97-1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.2-1ubuntu1
>   version.libgl1-mesa-glx: libgl1-mesa-glx N/A
>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20180925-2
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
>   ---
>   ProblemType: Bug
>   ApportVersion: 2.20.9-0ubuntu7.5
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CasperVersion: 1.394
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   DistUpgraded: Fresh install
>   DistroCodename: bionic
>   DistroRelease: Ubuntu 18.04
>   DistroVariant: ubuntu
>   GraphicsCard:
>Intel Corporation 2nd Generation Core Processor Family Integrated
> Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
>  Subsystem: Dell 2nd Generation Core Processor Family Integrated
> Graphics Controller [1028:052e]
>   LiveMediaBuild: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
> (20190210)
>   MachineType: Dell Inc. Dell System XPS L321X
>   Package: libinput (not installed)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper
> initrd=/casper/initrd quiet splash --- maybe-ubiquity
>   ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
>   Tags:  bionic ubuntu
>   Uname: Linux 4.18.0-15-generic x86_64
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>   dmi.bios.date: 12/27/2011
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: A01
>   dmi.board.vendor: Dell Inc.
>   dmi.chassis.type: 8
>   dmi.chassis.vendor: Dell Inc.
>   dmi.chassis.version: 0.1
>   dmi.modalias:
> dmi:bvnDellInc.:bvrA01:bd12/27/2011:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
>   dmi.product.family: HuronRiver System
>   dmi.product.name: Dell System XPS L321X
>   dmi.product.sku: System SKUNumbe

[Kernel-packages] [Bug 1817944] [NEW] Kubuntu 18.04 does not display through mini-DP port on lenovo Helix 2

2019-02-27 Thread udippel
Public bug reported:

(This is probably related to bug 1816860, but with different hardware
and a different appearance, so it is filed separately.)

Using the levovo Helix 2 attached to its Pro keyboard, it is not possible to 
activate the monitor as attached. 
The monitor is attached with a mini-DP-to-HDMI cable to the monitor (SONY), and 
is - in this case, contrary to the bug mentioned before - detected as can be 
seen by xrandr.
But then it gives up after some time (see attachment of System Settings started 
from CLI and Xorg.log:
$ tail /var/log/Xorg.0.log
[   970.977] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 2000 
2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)   
   
[   973.083] (II) modeset(0): EDID vendor "LGD", prod id 1121   

  
[   973.083] (II) modeset(0): Printing DDC gathered Modelines:  

  
[   973.083] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 2000 
2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
[  1009.658] (II) modeset(0): EDID vendor "LGD", prod id 1121
[  1009.658] (II) modeset(0): Printing DDC gathered Modelines:
[  1009.658] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 2000 
2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
[  1099.146] (II) modeset(0): EDID vendor "LGD", prod id 1121
[  1099.146] (II) modeset(0): Printing DDC gathered Modelines:
[  1099.146] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 2000 
2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)

(and so it continues).

Connecting the tablet of the convertable itself with a micro-HDMI-to-
HDMI to that same monitor works fine, however.

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

** Attachment added: "System Settings started from command line to see what 
happens"
   
https://bugs.launchpad.net/bugs/1817944/+attachment/5242093/+files/Settings_waiting

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

Title:
  Kubuntu 18.04 does not display through mini-DP port on lenovo Helix 2

Status in linux package in Ubuntu:
  New

Bug description:
  (This is probably related to bug 1816860, but with different hardware
  and a different appearance, so it is filed separately.)

  Using the levovo Helix 2 attached to its Pro keyboard, it is not possible to 
activate the monitor as attached. 
  The monitor is attached with a mini-DP-to-HDMI cable to the monitor (SONY), 
and is - in this case, contrary to the bug mentioned before - detected as can 
be seen by xrandr.
  But then it gives up after some time (see attachment of System Settings 
started from CLI and Xorg.log:
  $ tail /var/log/Xorg.0.log
  [   970.977] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)  

  [   973.083] (II) modeset(0): EDID vendor "LGD", prod id 1121 


  [   973.083] (II) modeset(0): Printing DDC gathered Modelines:


  [   973.083] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1009.658] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1009.658] (II) modeset(0): Printing DDC gathered Modelines:
  [  1009.658] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)
  [  1099.146] (II) modeset(0): EDID vendor "LGD", prod id 1121
  [  1099.146] (II) modeset(0): Printing DDC gathered Modelines:
  [  1099.146] (II) modeset(0): Modeline "1920x1080"x0.0  138.12  1920 1968 
2000 2052  1080 1083 1089 1122 +hsync -vsync (67.3 kHz eP)

  (and so it continues).

  Connecting the tablet of the convertable itself with a micro-HDMI-to-
  HDMI to that same monitor works fine, however.

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

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


Re: [Kernel-packages] [Bug 1815808] Re: Thunderbolt Ethernet high-traffic exception

2019-02-27 Thread Gene Olson
Great!   Thank you!

Be warned that Dell might blow you off.  Last I looked, they do not
officially support Linux on the XP 15.  However they do support Linux on
some other systems that use the TB-10, including the very popular XP 13.  I
would *guess* those systems will reproduce the same problem.

On Tue, Feb 26, 2019 at 11:50 PM Kai-Heng Feng 
wrote:

> The TB16's ASMedia xHC (USB controller) dies:
> [89535.271614] xhci_hcd :0a:00.0: xHCI host not responding to stop
> endpoint command.
> [89535.271945] xhci_hcd :0a:00.0: xHCI host controller not responding,
> assume dead
>
> I'll escalate this issue to Dell.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1815808
>
> Title:
>   Thunderbolt Ethernet high-traffic exception
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Running iperf3 on Dell XP-15 with TB-10 Thunderbolt dock causes a
>   kernel exception and ethernet failure after about 30 seconds.
>
>   Easy to reproduce.  Connect to another machine via Gig-E and run
>   iperf3 in either direction until the problem occurs.  Should run 900+
>   Mb in either direction.  On one occasion I also lost the USB ports.
>   However the display continues to work.
>
>   
>   # uname -a
>   Linux hauser 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC
> 2019 x86_64 x86_64 x86_64 GNU/Linux
>   # apt install iperf3
>   # iperf3 -s
>
>   
>   # apt install iperf3
>   # iperf3 -c my-machine -t 1000 # send to my machine
>   # iperf3 -c my-machine -t 1000 -R  # receive data from my machine
>
>   When the bitrate drops to zero, look in syslog for the exception.
>
>   Note: Until recently the TB-10 Ethernet would not receive full speed.
>   (prior to -43 kernel) Did not see this problem before the Ethernet
>   performance increased.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: linux-image-4.15.0-45-generic 4.15.0-45.48
>   ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
>   Uname: Linux 4.15.0-45-generic x86_64
>   NonfreeKernelModules: nvidia_modeset nvidia
>   ApportVersion: 2.20.9-0ubuntu7.5
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  gene   1994 F pulseaudio
>   CurrentDesktop: ubuntu:GNOME
>   Date: Wed Feb 13 13:54:28 2019
>   HibernationDevice: RESUME=UUID=d15ecb23-8691-42a1-9909-a56f934b536c
>   InstallationDate: Installed on 2018-11-19 (86 days ago)
>   InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
> (20180725)
>   MachineType: Dell Inc. XPS 15 9570
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic
> root=UUID=a73e2d3e-5ce3-4130-917d-d116c1316153 ro net.ifnames=0
> mem_sleep_default=deep
>   RelatedPackageVersions:
>linux-restricted-modules-4.15.0-45-generic N/A
>linux-backports-modules-4.15.0-45-generic  N/A
>linux-firmware 1.173.3
>   SourcePackage: linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 12/25/2018
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 1.7.0
>   dmi.board.name: 02MJVY
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn02MJVY:rvrA00:cvnDellInc.:ct10:cvr:
>   dmi.product.family: XPS
>   dmi.product.name: XPS 15 9570
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815808/+subscriptions
>

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

Title:
  Thunderbolt Ethernet high-traffic exception

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running iperf3 on Dell XP-15 with TB-10 Thunderbolt dock causes a
  kernel exception and ethernet failure after about 30 seconds.

  Easy to reproduce.  Connect to another machine via Gig-E and run
  iperf3 in either direction until the problem occurs.  Should run 900+
  Mb in either direction.  On one occasion I also lost the USB ports.
  However the display continues to work.

  
  # uname -a
  Linux hauser 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux
  # apt install iperf3
  # iperf3 -s

  
  # apt install iperf3
  # iperf3 -c my-machine -t 1000 # send to my machine
  # iperf3 -c my-machine -t 1000 -R  # receive data from my machine

  When the bitrate drops to zero, look in syslog for the exception.

  Note: Until recently the TB-10 Ethernet would not receive full speed.
  (prior to -43 kernel) Did not see this problem before the Ethernet
  performance increased.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-

[Kernel-packages] [Bug 1814757] Re: linux-aws: 4.18.0-1010.12 -proposed tracker

2019-02-27 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  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: 1814749
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:25 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-aws: 4.18.0-1010.12 -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:
  Invalid
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-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  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: 1814749
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:25 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

-- 
Mailing list: https://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 1809993] Re: Lenovo X1C6 trackpad functions broken

2019-02-27 Thread Joshua Powers
I am running 4.15.0-45 for the record

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

Title:
  Lenovo X1C6 trackpad functions broken

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Summary:
  After kernel update the trackpad advanced functions, like two finger 
scrolling and mouse acceleration have stopped working.

  Expected Result:
  Two finer scroll works and the mouse has acceleration features work

  Actual Result:
  Two finer scroll works and the mouse has acceleration features do not work

  Steps to reproduce:
  1. Lenovo X1C6 (LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET59W (1.34 ) 
11/08/2018)
  2. Install 18.04 LTS
  3. config-4.15.0-42-generic acceleration works, while 
config-4.15.0-43-generic does not

  This appears to be some sort of regression or change in behavior between 
kernel versions.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  powersj1597 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1eb43198-8ef5-4035-8b81-74c3e2936ad7
  InstallationDate: Installed on 2018-12-06 (22 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KHCTO1WW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET59W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET59W(1.34):bd11/08/2018:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1809993] Re: Lenovo X1C6 trackpad functions broken

2019-02-27 Thread Joshua Powers
It does not, feel free to close this

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

Title:
  Lenovo X1C6 trackpad functions broken

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Summary:
  After kernel update the trackpad advanced functions, like two finger 
scrolling and mouse acceleration have stopped working.

  Expected Result:
  Two finer scroll works and the mouse has acceleration features work

  Actual Result:
  Two finer scroll works and the mouse has acceleration features do not work

  Steps to reproduce:
  1. Lenovo X1C6 (LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET59W (1.34 ) 
11/08/2018)
  2. Install 18.04 LTS
  3. config-4.15.0-42-generic acceleration works, while 
config-4.15.0-43-generic does not

  This appears to be some sort of regression or change in behavior between 
kernel versions.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  powersj1597 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1eb43198-8ef5-4035-8b81-74c3e2936ad7
  InstallationDate: Installed on 2018-12-06 (22 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KHCTO1WW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET59W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET59W(1.34):bd11/08/2018:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1814738] Re: linux-oracle: 4.15.0-1009.11 -proposed tracker

2019-02-27 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  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: 1814726
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:30 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-oracle: 4.15.0-1009.11 -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:
  Invalid
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-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-oracle package in Ubuntu:
  Fix Released
Status in linux-oracle source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  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: 1814726
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:30 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

-- 
Mailing list: https://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 1817772] Re: package linux-signed-image-4.4.0-101-generic 4.4.0-101.124 failed to install/upgrade: package linux-signed-image-4.4.0-101-generic is not ready for configuration ca

2019-02-27 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package linux-signed-image-4.4.0-101-generic 4.4.0-101.124 failed to
  install/upgrade: package linux-signed-image-4.4.0-101-generic is not
  ready for configuration  cannot configure (current status 'half-
  installed')

Status in linux-signed package in Ubuntu:
  New

Bug description:
  package linux-signed-image-4.4.0-101-generic 4.4.0-101.12

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-signed-image-4.4.0-101-generic 4.4.0-101.124
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Mon Feb 25 18:20:27 2019
  DpkgHistoryLog:
   Start-Date: 2019-02-25  18:20:18
   Requested-By: lucio (1000)
   Upgrade: libgs9:amd64 (9.26~dfsg+0-0ubuntu0.16.04.5, 
9.26~dfsg+0-0ubuntu0.16.04.6), ghostscript:amd64 (9.26~dfsg+0-0ubuntu0.16.04.5, 
9.26~dfsg+0-0ubuntu0.16.04.6), ghostscript-x:amd64 
(9.26~dfsg+0-0ubuntu0.16.04.5, 9.26~dfsg+0-0ubuntu0.16.04.6), 
libgs9-common:amd64 (9.26~dfsg+0-0ubuntu0.16.04.5, 9.26~dfsg+0-0ubuntu0.16.04.6)
  DuplicateSignature:
   package:linux-signed-image-4.4.0-101-generic:4.4.0-101.124
   Processing triggers for libc-bin (2.23-0ubuntu11) ...
   dpkg: error processing package linux-signed-image-4.4.0-101-generic 
(--configure):
package linux-signed-image-4.4.0-101-generic is not ready for configuration
  ErrorMessage: package linux-signed-image-4.4.0-101-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2015-03-13 (1445 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.29ubuntu0.1
  SourcePackage: linux-signed
  Title: package linux-signed-image-4.4.0-101-generic 4.4.0-101.124 failed to 
install/upgrade: package linux-signed-image-4.4.0-101-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1817772] Re: package linux-signed-image-4.4.0-101-generic 4.4.0-101.124 failed to install/upgrade: package linux-signed-image-4.4.0-101-generic is not ready for configuration ca

2019-02-27 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  package linux-signed-image-4.4.0-101-generic 4.4.0-101.124 failed to
  install/upgrade: package linux-signed-image-4.4.0-101-generic is not
  ready for configuration  cannot configure (current status 'half-
  installed')

Status in linux-signed package in Ubuntu:
  New

Bug description:
  package linux-signed-image-4.4.0-101-generic 4.4.0-101.12

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-signed-image-4.4.0-101-generic 4.4.0-101.124
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Mon Feb 25 18:20:27 2019
  DpkgHistoryLog:
   Start-Date: 2019-02-25  18:20:18
   Requested-By: lucio (1000)
   Upgrade: libgs9:amd64 (9.26~dfsg+0-0ubuntu0.16.04.5, 
9.26~dfsg+0-0ubuntu0.16.04.6), ghostscript:amd64 (9.26~dfsg+0-0ubuntu0.16.04.5, 
9.26~dfsg+0-0ubuntu0.16.04.6), ghostscript-x:amd64 
(9.26~dfsg+0-0ubuntu0.16.04.5, 9.26~dfsg+0-0ubuntu0.16.04.6), 
libgs9-common:amd64 (9.26~dfsg+0-0ubuntu0.16.04.5, 9.26~dfsg+0-0ubuntu0.16.04.6)
  DuplicateSignature:
   package:linux-signed-image-4.4.0-101-generic:4.4.0-101.124
   Processing triggers for libc-bin (2.23-0ubuntu11) ...
   dpkg: error processing package linux-signed-image-4.4.0-101-generic 
(--configure):
package linux-signed-image-4.4.0-101-generic is not ready for configuration
  ErrorMessage: package linux-signed-image-4.4.0-101-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2015-03-13 (1445 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.29ubuntu0.1
  SourcePackage: linux-signed
  Title: package linux-signed-image-4.4.0-101-generic 4.4.0-101.124 failed to 
install/upgrade: package linux-signed-image-4.4.0-101-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1814738] Re: linux-oracle: 4.15.0-1009.11 -proposed tracker

2019-02-27 Thread Brad Figg
** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  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: 1814726
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:30 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
-   regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-oracle: 4.15.0-1009.11 -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:
  Invalid
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-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-oracle package in Ubuntu:
  Fix Released
Status in linux-oracle source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  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: 1814726
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:30 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

-- 
Mailing list: https://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 1814738] Re: linux-oracle: 4.15.0-1009.11 -proposed tracker

2019-02-27 Thread Sean Feole
** Tags added: regression-testing-passed

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

Title:
  linux-oracle: 4.15.0-1009.11 -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:
  Invalid
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-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-oracle package in Ubuntu:
  Fix Released
Status in linux-oracle source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  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: 1814726
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:30 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

-- 
Mailing list: https://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 1814747] Re: linux-oracle: 4.15.0-1009.11~16.04.1 -proposed tracker

2019-02-27 Thread Brad Figg
** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  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: 1814726
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:20 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
-   regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-oracle: 4.15.0-1009.11~16.04.1 -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:
  Invalid
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-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  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: 1814726
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:20 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

-- 
Mailing list: https://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 1816782] Re: linux-azure: 4.18.0-1012.12~18.04.1 -proposed tracker

2019-02-27 Thread Sean Feole
** 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/1816782

Title:
  linux-azure: 4.18.0-1012.12~18.04.1 -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:
  Invalid
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-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  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: 1814749
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:13 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

-- 
Mailing list: https://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 1816782] Re: linux-azure: 4.18.0-1012.12~18.04.1 -proposed tracker

2019-02-27 Thread Brad Figg
** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  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: 1814749
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:13 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.18.0-1012.12~18.04.1 -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:
  Invalid
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-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  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: 1814749
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:13 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

-- 
Mailing list: https://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 1814747] Re: linux-oracle: 4.15.0-1009.11~16.04.1 -proposed tracker

2019-02-27 Thread Sean Feole
** Tags added: regression-testing-passed

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

Title:
  linux-oracle: 4.15.0-1009.11~16.04.1 -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:
  Invalid
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-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  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: 1814726
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:20 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

-- 
Mailing list: https://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 1812099] Re: 4.18.0 thinkpad_acpi : thresholds for BAT1 not writable

2019-02-27 Thread Stefan Bader
** Changed in: linux (Ubuntu Cosmic)
   Importance: Undecided => Medium

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

Title:
  4.18.0 thinkpad_acpi : thresholds for BAT1 not writable

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Cosmic:
  New

Bug description:
  [Problem description]
  Kernel 4.17 introduced a new interface to set charge thresholds: The 
interface remained unchanged with 4.18. There's a bug preventing writing the 
charge thresholds for the secondary battery (BAT1).

  [Impact]
  ThinkPads with two batteries (ThinkPad "power bridge") e.g.
  X240, T440(s), X250, T450(s), X260, T460(s), X270, T470(s) et al.

  [Steps to reproduce]
  echo 42 > /sys/class/power_supply/BAT1/charge_start_threshold
  bash: echo: write error: No such device 

  echo 42 > /sys/class/power_supply/BAT0/charge_start_threshold
  -- primary battery works!

  [Fix]
  Problem was fixed in 4.19:
  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/platform/x86/thinkpad_acpi.c?h=v4.19.15&id=d22296d9c38fd29a96bb5079fb8d17cee278f40e

  I propose to cherry-pick the patch for 4.18.

  [Test Case]
  See above, a patched 4.18 works for T450s.

  [Regression Potential]
  Low. This patch only applies to several ThinkPad machines, and after applying
  this patch, charge_start/stop_threshold work for BAT0 and BAT.

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

-- 
Mailing list: https://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 1785171] Re: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection

2019-02-27 Thread Tjareson Toland
Hello,
same issue here on Ubuntu 18.04 with 
driver: e1000e
version: 3.2.6-k
firmware-version: 0.5-4
expansion-rom-version: 
bus-info: :00:1f.6
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no

I can change the EEE settings of the network adapter. But after a couple of 
minutes it still slows down to unusable.
# ethtool --show-eee eno2
EEE Settings for eno2:
EEE status: disabled
Tx LPI: 17 (us)
Supported EEE link modes:  100baseT/Full 
   1000baseT/Full 
Advertised EEE link modes:  100baseT/Full 
1000baseT/Full 
Link partner advertised EEE link modes:  100baseT/Full 
 1000baseT/Full 

Cheers,
Tjareson

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

Title:
  Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver
  keeps Dropping Internet Connection

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  I've turned up many, many new server and workstation systems over the
  years on both Linux and Windows. Never seen anything like this
  behaviour I'm witnessing on Ubuntu Server 18.04 before where I simply
  lose Internet connectivity while using a browser.  Ethernet interfaces
  usually either work or they don't work.

  I've configured the Intel I219-V Ethernet interface (wired Ethernet
  connection, there is no wifi on this system) using the e1000e driver
  for Ubuntu.  The Ethernet connection is configured to use
  NetworkManager via Netplan on Ubuntu 18.04 LTS Server version.  ASRock
  Z370m Pro4 motherboard.

  The Ethernet interface will drop the Internet connectivity when I'm
  using either the Firefox or Chrome browser.  It usually happens when
  I'm using the search features of the browser. I can't figure out what
  would cause this type of behaviour.  When the Internet connection
  drops, the only way to get back Internet connectivity is to disconnect
  the wired connection using the Ubuntu features and then re-connect
  (this restarts the NetworkManager service I notice).

  In the NetworkManager logs I do notice an "auth" error about a file or
  directory not found. I've never seen that before.

  Note:  The auth error does not coincide with the loss of Internet
  connectivity, but it does proceed it.  Often there can be many hours
  between the auth error and the actual loss of Internet connectivity.

  After I reconnect the connection (via re-starting the NetworkManager
  service) all will be fine for up to a day or so, but then I stress
  test it with a bunch of searches using the browser and usually I can
  get the Internet connectivity to drop again.  Repeat the disconnect
  and reconnect process again (aka re-start NetworkManager) and the
  Internet connectivity will be fine again.  The longest I've seen it go
  without an "Internet connectivity drop" issue is about 36 hours.

  I notice that the e1000e driver does not list the I219-V as a
  supported Ethernet interface in the Intel documentation for the Linux
  version of the driver.  I'm not sure why that is.  The I219-V is
  supposed to used another driver, but it's not clear there's a Linux
  version for of the driver for the I219-V.

  I'm really disappointed that I've run into this issue with Ubuntu
  Server LTS 18.04 on this motherboard.  I had CentOS Server 7.4 (my
  standard server OS, a great Linux distro) on this same motherboard for
  a week with no issues, so I know the motherboard and the I219-V
  Ethernet interface are 100% good hardware wise and can work properly.
  CentOS 7.4 uses NetworkManager as the default for managing the
  Ethernet interface.

  The only reason I'm using Ubuntu Server 18.04 on this motherboard is
  because of a specific package that Ubuntu has a newer packaged version
  than CentOS. CentOS is extremely stable when it comes to basic server
  functionality.

  Hopefully, this bug with the I219-V Ethernet interface using the
  e1000e drive for Linux can be verified and a fix rolled out.

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

-- 
Mailing list: https://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 1816947] Re: [Dell XPS L321X] Touchpad not working after last apt-get upgrade

2019-02-27 Thread Timo Aaltonen
Yes, in #43 you said that you tested 4.13.0-19.22 but didn't seem to
install the package with the drivers (linux-image-extra). If you do,
does it work like the live version did?

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

Title:
  [Dell XPS L321X] Touchpad not working after last apt-get upgrade

Status in libinput package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The touchpad doesn't work unless the cursor is moved slowly.

  WORKAROUND: Execute at a terminal:
  sudo modprobe -r psmouse
  sudo modprobe psmouse proto=imps

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.402
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 21 02:56:45 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:052e]
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  MachineType: Dell Inc. Dell System XPS L321X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd12/27/2011:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L321X
  dmi.product.sku: System SKUNumber
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.394
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:052e]
  LiveMediaBuild: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
  MachineType: Dell Inc. Dell System XPS L321X
  Package: libinput (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Tags:  bionic ubuntu
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/27/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd12/27/2011:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L321X
  dmi.product.sku: System SKUNumber
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input

[Kernel-packages] [Bug 1817918] [NEW] Hard lockups due to unrestricted lapic timer delay

2019-02-27 Thread Guilherme G. Piccoli
Public bug reported:

There is a report of hard lockup induced by a long delay in lapic expiration 
timer.
We'll provide SRU request here for merging the fixes in 4.4 kernel.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Guilherme G. Piccoli (gpiccoli)
 Status: Confirmed

** Affects: linux (Ubuntu Xenial)
 Importance: High
 Assignee: Guilherme G. Piccoli (gpiccoli)
 Status: Confirmed

** Affects: linux (Ubuntu Bionic)
 Importance: Low
 Assignee: Guilherme G. Piccoli (gpiccoli)
 Status: Fix Released


** Tags: sts

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

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

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

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

Title:
  Hard lockups due to unrestricted lapic timer delay

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

Bug description:
  There is a report of hard lockup induced by a long delay in lapic expiration 
timer.
  We'll provide SRU request here for merging the fixes in 4.4 kernel.

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

-- 
Mailing list: https://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 1795453] Re: [SRU] IO's are issued with incorrect Scatter Gather Buffer

2019-02-27 Thread Marcelo Cerri
** Changed in: linux (Ubuntu)
   Status: Fix Released => Fix Committed

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

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

Title:
  [SRU] IO's are issued with incorrect Scatter Gather Buffer

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect 
Scatter Gather Buffer address .

  i.e

   OS is sending the IO with 64 bit Scatter Gather Buffer address , such
  that if we add the length with buffer address then it causes the roll
  over .

  Here is the data we captured in our driver (Printed the SGE details
  which was sent by OS)

  sgl_ptr->Address = f000
  [14547.313240]
  sgl_ptr->Length = 1000
  [14547.313241]
  sge_count = 18
  [14547.313242]
  cmd->index = 9d9

  Note : This issue is observed only when virtualization is enabled

  Product : Broadcom (LSI) Megaraid H840 controller

  
  [Test Case]
  Steps found in comment #60
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/comments/60

  
  [Regression Potential]

  The patches in Comment #59 have been accepted upstream.

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/comments/59


  [Other Info]

  Product : Broadcom (LSI) Megaraid H840 controller
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7415
  dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415
  dmi.sys.vendor: Dell Inc.
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  d

[Kernel-packages] [Bug 929244] Re: Cannot connect to wireless network in 12.04

2019-02-27 Thread Bug Watch Updater
Launchpad has imported 2 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=42843.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2012-03-01T16:36:57+00:00 aquaglow wrote:

Created attachment 72509
Apport generated log of information.

My wireless network is listed in Network Manager, but upon entering the
password it tries to connect and then re-prompts for a password. I could
previously connect fine in Ubuntu 10.10/Fedora 16.

This issue occured in the stock Ubuntu 3.2.0 kernel (issue raised here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/929244), and also
in the mainline 3.3.0 kernel when I tried that instead.

Steps to reproduce:
1. Select wireless network in Network Manager (802.11g with WPA2 in my case)
2. Watch the network icon animate while it tries to connect
3. Dialog box re-prompts for password

My wireless card details:

01:08.0 Network controller: Ralink corp. RT2561/RT61 802.11g PCI
 Subsystem: Linksys WMP54G v4.1
 Flags: bus master, slow devsel, latency 32, IRQ 18
 Memory at dbff8000 (32-bit, non-prefetchable) [size=32K]
 Capabilities: 
 Kernel driver in use: rt61pci
 Kernel modules: rt61pci

dmesg output immediately after connection failed:

[ 422.332069] wlan0: authenticate with 00:26:f2:05:ad:dc (try 1)
[ 422.334473] wlan0: authenticated
[ 422.348049] wlan0: associate with 00:26:f2:05:ad:dc (try 1)
[ 422.350844] wlan0: deauthenticated from 00:26:f2:05:ad:dc (Reason: 6)
[ 507.012093] wlan0: authenticate with 00:26:f2:05:ad:dc (try 1)
[ 507.015078] wlan0: authenticated
[ 507.017076] wlan0: failed to insert Dummy STA entry for the AP (error -17)

Attached is the apport generated log.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/929244/comments/11


On 2017-03-06T19:59:08+00:00 szg wrote:

Please try this bug with latest kernel image.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/929244/comments/26

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

Title:
  Cannot connect to wireless network in 12.04

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

Bug description:
  My wireless network is listed in Network Manager, but upon entering
  the password it tries to connect and then re-prompts for a password. I
  can connect fine in Ubuntu 10.10/Fedora 16.

  Steps to reproduce:
  1. Select wireless network in Network Manager (802.11g with WPA2 in my case)
  2. Watch the network icon animate while it tries to connect
  3. Dialog box re-prompts for password

  My wireless card details:

  01:08.0 Network controller: Ralink corp. RT2561/RT61 802.11g PCI
Subsystem: Linksys WMP54G v4.1
Flags: bus master, slow devsel, latency 32, IRQ 18
Memory at dbff8000 (32-bit, non-prefetchable) [size=32K]
Capabilities: 
Kernel driver in use: rt61pci
Kernel modules: rt61pci

  dmesg output immediately after connection failed:

  [  422.332069] wlan0: authenticate with 00:26:f2:05:ad:dc (try 1)
  [  422.334473] wlan0: authenticated
  [  422.348049] wlan0: associate with 00:26:f2:05:ad:dc (try 1)
  [  422.350844] wlan0: deauthenticated from 00:26:f2:05:ad:dc (Reason: 6)
  [  507.012093] wlan0: authenticate with 00:26:f2:05:ad:dc (try 1)
  [  507.015078] wlan0: authenticated
  [  507.017076] wlan0: failed to insert Dummy STA entry for the AP (error -17)

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

-- 
Mailing list: https://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 1043403] Re: Wireless not active during installation or after boot

2019-02-27 Thread Bug Watch Updater
Launchpad has imported 4 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=46721.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2012-08-30T16:45:07+00:00 lars.nooden+kernel wrote:

Created attachment 78811
dmesg

The i386 has a Ralink corp. RT2561/RT61 802.11g PCI wireless card.
However, the installation process seems unable to use it to find any
wireless networks, not even open networks. Same goes after booting and
trying manually.  This is true even with the new kernel:

# uname -a
Linux easynote 3.6.0-030600rc3-generic #201208221735 SMP Wed Aug 22 21:45:31 
UTC 2012 i686 i686 i686 GNU/Linux

# rfkill list all
0: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: yes

What information is needed to make a proper bug report?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043403/comments/22


On 2012-08-30T19:59:46+00:00 alan wrote:

[   15.649864] rt61pci :00:06.0: enabling device ( -> 0002)
[   15.649882] rt61pci :00:06.0: can't find IRQ for PCI INT A; please try 
using pci=biosirq
[   15.649900] rt61pci :00:06.0: setting latency timer to 64

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043403/comments/24


On 2012-08-31T07:32:38+00:00 lars.nooden+kernel wrote:

Created attachment 78861
dmesg after pci=biosirq

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043403/comments/25


On 2012-08-31T07:34:19+00:00 lars.nooden+kernel wrote:

I tried setting pci=biosirq in the grub menu and the only difference I
see is that the consoles vanish.  I can still log in via ssh though.

# rfkill list all
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043403/comments/26

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

Title:
  Wireless not active during installation or after boot

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

Bug description:
  The i386 has a  Ralink corp. RT2561/RT61 802.11g PCI wireless card.
  However, the installation process seems unable to use it to find any
  wireless networks, not even open networks.  Same goes after booting
  and trying manually.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 3.5.0-13.13-generic 3.5.3
  Uname: Linux 3.5.0-13-generic i686
  ApportVersion: 2.5.1-0ubuntu2
  Architecture: i386
  Date: Wed Aug 29 18:50:47 2012
  InstallCmdLine: file=/cdrom/preseed/lubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash --
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120828)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  AcpiTables:

  ApportVersion: 2.5.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   27.408464] init: lightdm main process (943) terminated with 
status 1
  DistroRelease: Ubuntu 12.10
  HibernationDevice: RESUME=UUID=2a0d5ff8-7854-49fd-91e2-be4326cfc418
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120828)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Packard Bell Computers International Packard Bell EasyNote
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-13-generic 
root=UUID=1e64a51f-2f5b-4d0f-bb43-88c03014c8b4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.5.0-13.13-generic 3.5.3
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-13-generic N/A
   linux-backports-modules-3.5.0-13-generic  N/A
   linux-firmware1.90
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: yes
  Tags:  quantal
  Uname: Linux 3.5.0-13-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: /08/0520
  dmi.

[Kernel-packages] [Bug 1814734] Re: linux-gcp: 4.15.0-1028.29 -proposed tracker

2019-02-27 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  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: 1814726
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1028
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-gcp: 4.15.0-1028.29 -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:
  Invalid
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-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  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: 1814726
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1028
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

-- 
Mailing list: https://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 1239459]

2019-02-27 Thread jimmiegentry99
Excellent Work, Good job! Thanks for sharing this
http://idmcrack.us/idm-serial-key-2/
https://pfcbwp.com/idm-crack-serial-keys/
https://softpc.org/idm-crack-serial-key-version/
https://idealcrack.us/idm-crack-key-serial-patch-full-download/
https://idealcrack.com/idm-universal-crack/
https://4crack.pw/idm-crack-serial-keys-download/
https://softwarepatch.pw/idm-license-key-easy-to-use-interface/
https://crackedlicense.com/idm-crack-keygen-serial-key-download/
idm avec crack
idm latest version free download with crack
idm 6.26 build 7 crack
idm 6.26 full crack
idm latest version with crack free download
idm terbaru crack
download idm latest version with crack
idm 6.21 crack
cách crack idm
idm 6.27 full crack
crack idm 6.21
download idm full crack kuyhaa
idm downloader with crack
download idm full crack 2016
free idm crack
free idm download with crack
idm 6.29 build 2 crack
download idm with crack and patch
idm crack latest
idm crack only
download idm full crack 2017
idm 6.25 build 21 crack patch full version
idm full crack terbaru
latest idm 7.1 with crack
how to crack idm 6.25
telecharger crack idm
idm filehippo with crack
download idm crack terbaru
telecharger idm crack gratuit complet
descargar idm con crack
idm permanent crack
idm pro crack
idm universal crack download

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

Title:
  1814:3290 [Asus X200CA] wifi doesn't connect or disconnects after few
  seconds

Status in Linux:
  Won't Fix
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  With the new 3.11.0-12-generic kernel, wifi has problems to connect with many 
errors like these:
  Oct 13 23:50:03 ubuntotto kernel: [ 1186.580726] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:50:03 ubuntotto kernel: [ 1186.740659] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
  Oct 13 23:50:04 ubuntotto kernel: [ 1186.900544] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:50:04 ubuntotto kernel: [ 1187.060571] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
  Oct 13 23:50:04 ubuntotto kernel: [ 1187.096576] ieee80211 phy0: 
rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 0
  Oct 13 23:50:05 ubuntotto kernel: [ 1188.280106] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:50:05 ubuntotto kernel: [ 1188.440128] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
  Oct 13 23:51:06 ubuntotto kernel: [ 1249.560697] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:51:06 ubuntotto kernel: [ 1249.720644] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
  Oct 13 23:51:07 ubuntotto kernel: [ 1249.880590] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:51:07 ubuntotto kernel: [ 1250.040543] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-12-generic 3.11.0-12.19
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrea 1791 F pulseaudio
  Date: Sun Oct 13 23:45:04 2013
  HibernationDevice: RESUME=UUID=297ef090-5420-41f6-8439-f1254f3e9e15
  InstallationDate: Installed on 2013-10-12 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: ASUSTeK COMPUTER INC. X200CA
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=088f2a7d-b78f-4bdd-a184-754b70a3184a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-12-generic N/A
   linux-backports-modules-3.11.0-12-generic  N/A
   linux-firmware 1.116
  SourcePackage: linux
  UpgradeStatus: Upgraded to saucy on 2013-10-13 (0 days ago)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200CA.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX200CA.208:bd09/18/2013:svnASUSTeKCOMPUTERINC.:pnX200CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X200CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

  1   2   >