[Kernel-packages] [Bug 1811419] Re: linux: 4.15.0-44.47 -proposed tracker

[Łukasz Zemczak]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux: 4.15.0-44.47 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
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 snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
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:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux 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

  backports: bug 1811429 (linux-azure), bug 1811430 (linux-aws-hwe), bug 
1811431 (linux-azure), bug 1811432 (linux-gcp), bug 1811434 (linux-hwe), bug 
1811435 (linux-hwe-edge), bug 1811436 (linux-oracle)
  derivatives: bug 1811420 (linux-raspi2), bug 1811421 (linux-oem), bug 1811422 
(linux-aws), bug 1811423 (linux-azure), bug 1811424 (linux-gcp), bug 1811425 
(linux-kvm), bug 1811427 (linux-oracle)
  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed -- release to Proposed ready
  phase-changed: Monday, 14. January 2019 21:04 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/1811419/+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 1811419] Re: linux: 4.15.0-44.47 -proposed tracker

[Łukasz Zemczak]

** Changed in: kernel-sru-workflow/promote-to-proposed
   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/1811419

Title:
  linux: 4.15.0-44.47 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-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 Committed
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 snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
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:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux 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

  backports: bug 1811429 (linux-azure), bug 1811430 (linux-aws-hwe), bug 
1811431 (linux-azure), bug 1811432 (linux-gcp), bug 1811434 (linux-hwe), bug 
1811435 (linux-hwe-edge), bug 1811436 (linux-oracle)
  derivatives: bug 1811420 (linux-raspi2), bug 1811421 (linux-oem), bug 1811422 
(linux-aws), bug 1811423 (linux-azure), bug 1811424 (linux-gcp), bug 1811425 
(linux-kvm), bug 1811427 (linux-oracle)
  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed -- release to Proposed in progress
  phase-changed: Tuesday, 15. January 2019 08:32 UTC
  reason:
promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811419/+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 1811406] Re: linux: 4.18.0-14.15 -proposed tracker

[Łukasz Zemczak]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux: 4.18.0-14.15 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-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 Committed
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 upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux 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

  backports: bug 1811407 (linux-hwe), bug 1811408 (linux-hwe-edge), bug 1811409 
(linux-aws-edge), bug 1811410 (linux-azure-edge), bug 1811411 (linux-gcp-edge), 
bug 1811418 (linux-azure-edge)
  derivatives: bug 1811412 (linux-raspi2), bug 1811414 (linux-aws), bug 1811415 
(linux-azure), bug 1811416 (linux-gcp), bug 1811417 (linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed -- release to Proposed in progress
  phase-changed: Tuesday, 15. January 2019 08:32 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811406/+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 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

[Alex Garel]

*-display
 description: VGA compatible controller
 produit: Skylake GT2 [HD Graphics 520]
 fabriquant: Intel Corporation
 identifiant matériel: 2
 information bus: pci@:00:02.0
 version: 07
 bits: 64 bits
 horloge: 33MHz
 fonctionnalités: pciexpress msi pm vga_controller bus_master 
cap_list rom
 configuration: driver=i915 latency=0
 ressources: irq:125 mémoire:de00-deff 
mémoire:c000-cfff portE/S:f000(ta
ille=64) mémoire:c-d

I don't have an external graphic card but I often plug / unplug my
computer on an external display.

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

Title:
  Unable to unlock the desktop session: systemd-logind: got pause for
  13:69

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  When this issue happens, you won't be able to unlock your desktop session (VT 
works fine).
  This happened twice today for me, one is after a suspend, one is just a 
screen lock. Not sure what is the trigger yet.

  Syndrome:
  On the login screen after typing the correct password, you will see a small 
circle keep spinning and that's it. I need to restart my computer to get it 
back to normal.

  
  In the syslog this error message looks fishy:
  Aug  8 10:44:57 Leggiero gnome-shell[2118]: g_array_unref: assertion 'array' 
failed

  
  This is part of the syslog fetching from a VT after a GUI unlock attempt 
(session 24 is the desktop login attempt):

  Aug  8 10:44:42 Leggiero systemd[1]: Started Session 24 of user sam.
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 226:0
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) AIGLX: 
Resuming AIGLX clients after VT switch
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
EDID vendor "AUO", prod id 4204
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Printing DDC gathered Modelines:
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Modeline "1366x768"x0.0   76.20  1366 1404 1426 1590  768 771 777 798 +hsync 
-vsync (47.9 kHz eP)
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Modeline "1366x768"x0.0   76.20  1366 1404 1426 1988  768 771 777 798 +hsync 
-vsync (38.3 kHz e)
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:78
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - 
Dell WMI hotkeys: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - 
Dell WMI hotkeys: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:66
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2  - 
Sleep Button: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2  - 
Sleep Button: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:79
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - 
Integrated_Webcam_HD: Integrate: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - 
Integrated_Webcam_HD: Integrate: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:68
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4  - AT 
Translated Set 2 keyboard: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4  - AT 
Translated Set 2 keyboard: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:67
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3  - 
Power Button: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3  - 
Power Button: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:71
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7  - 
AlpsPS/2 ALPS GlidePoint: is tagged by udev as: Touchpad
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7  - 
AlpsPS/2 ALPS GlidePoint: device is a touchpad
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:72
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8  - 
DELL Wireless hotkeys: is tagged by udev as: Keyboard
  Aug  8 10:44:5

[Kernel-packages] [Bug 1811419] Re: linux: 4.15.0-44.47 -proposed tracker

[Brad Figg]

** 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
  
  backports: bug 1811429 (linux-azure), bug 1811430 (linux-aws-hwe), bug 
1811431 (linux-azure), bug 1811432 (linux-gcp), bug 1811434 (linux-hwe), bug 
1811435 (linux-hwe-edge), bug 1811436 (linux-oracle)
  derivatives: bug 1811420 (linux-raspi2), bug 1811421 (linux-oem), bug 1811422 
(linux-aws), bug 1811423 (linux-azure), bug 1811424 (linux-gcp), bug 1811425 
(linux-kvm), bug 1811427 (linux-oracle)
  -- swm properties --
  boot-testing-requested: true
- phase: Promote to Proposed -- release to Proposed ready
- phase-changed: Monday, 14. January 2019 21:04 UTC
+ phase: Promote to Proposed -- release to Proposed in progress
+ phase-changed: Tuesday, 15. January 2019 08:32 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed

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

Title:
  linux: 4.15.0-44.47 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-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 Committed
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 snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
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:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux 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

  backports: bug 1811429 (linux-azure), bug 1811430 (linux-aws-hwe), bug 
1811431 (linux-azure), bug 1811432 (linux-gcp), bug 1811434 (linux-hwe), bug 
1811435 (linux-hwe-edge), bug 1811436 (linux-oracle)
  derivatives: bug 1811420 (linux-raspi2), bug 1811421 (linux-oem), bug 1811422 
(linux-aws), bug 1811423 (linux-azure), bug 1811424 (linux-gcp), bug 1811425 
(linux-kvm), bug 1811427 (linux-oracle)
  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed -- release to Proposed in progress
  phase-changed: Tuesday, 15. January 2019 08:32 UTC
  reason:
promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811419/+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 1811406] Re: linux: 4.18.0-14.15 -proposed tracker

[Brad Figg]

** 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
  
  backports: bug 1811407 (linux-hwe), bug 1811408 (linux-hwe-edge), bug 1811409 
(linux-aws-edge), bug 1811410 (linux-azure-edge), bug 1811411 (linux-gcp-edge), 
bug 1811418 (linux-azure-edge)
  derivatives: bug 1811412 (linux-raspi2), bug 1811414 (linux-aws), bug 1811415 
(linux-azure), bug 1811416 (linux-gcp), bug 1811417 (linux-kvm)
  -- swm properties --
  boot-testing-requested: true
- phase: Promote to Proposed -- release to Proposed ready
- phase-changed: Monday, 14. January 2019 20:04 UTC
+ phase: Promote to Proposed -- release to Proposed in progress
+ phase-changed: Tuesday, 15. January 2019 08:32 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- review 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/1811406

Title:
  linux: 4.18.0-14.15 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-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 Committed
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 upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux 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

  backports: bug 1811407 (linux-hwe), bug 1811408 (linux-hwe-edge), bug 1811409 
(linux-aws-edge), bug 1811410 (linux-azure-edge), bug 1811411 (linux-gcp-edge), 
bug 1811418 (linux-azure-edge)
  derivatives: bug 1811412 (linux-raspi2), bug 1811414 (linux-aws), bug 1811415 
(linux-azure), bug 1811416 (linux-gcp), bug 1811417 (linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed -- release to Proposed in progress
  phase-changed: Tuesday, 15. January 2019 08:32 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811406/+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 1811406] Re: linux: 4.18.0-14.15 -proposed tracker

[Łukasz Zemczak]

** Changed in: kernel-sru-workflow/promote-to-proposed
   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/1811406

Title:
  linux: 4.18.0-14.15 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-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 Committed
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 upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux 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

  backports: bug 1811407 (linux-hwe), bug 1811408 (linux-hwe-edge), bug 1811409 
(linux-aws-edge), bug 1811410 (linux-azure-edge), bug 1811411 (linux-gcp-edge), 
bug 1811418 (linux-azure-edge)
  derivatives: bug 1811412 (linux-raspi2), bug 1811414 (linux-aws), bug 1811415 
(linux-azure), bug 1811416 (linux-gcp), bug 1811417 (linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed -- release to Proposed in progress
  phase-changed: Tuesday, 15. January 2019 08:32 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811406/+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 1805079] Re: click/pop noise in the headphone on several lenovo laptops

[Hui Wang]

Realtek told me that in the alc285, the pin 0x1d is for PC beep in, if
PC beep in has noise, it will affect speaker or headphone, set the
pinctl of 0x1d to 0x0 is helpful to reduce the noise or close the pc
peep in passthrough by setting 0x57d7 to Node 0x20 COEF index 0x36.

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

Title:
  click/pop noise in the headphone on several lenovo laptops

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]
  Lenovo told us that some linux uers reported headphone noise on Lenovo's
  website. After investigating, we found those Lenovo laptop mdoels all
  have the codec of alc285, and we can reproduce the noise problem too.

  [Fix]
  Don't use the DAC of headphone, let headphone share the DAC with speaker,
  the noise disappears.

  [Test Case]
  After applying this patch, we tested on Lenovo P52, P72, X1 carbon and X1
  Yoda2, no noise anymore

  [Regression Potential]
  Low. This patch only apply to several lenovo machines, and after applying
  this patch, both speaker and headphone still work very well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805079/+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 1811777] [NEW] Fix non-working pinctrl-intel

[Kai-Heng Feng]

Public bug reported:

[Impact]
Intel pinctrl doesn't work.
There's a WWAN card needs to use pinctrl to reset itself after firmware update. 
Currently we can't use pinctrl to reset it.

[Fix]
Translate GPIO to pinctrl pins correctly.

[Test]
The WWAN reset function works once the fix is applied.

[Regression Potential]
Low. Limits to pinctrl-intel and it's in mainline for a while.

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

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


** Tags: originate-from-1800987 somerville

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

Title:
  Fix non-working pinctrl-intel

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

Bug description:
  [Impact]
  Intel pinctrl doesn't work.
  There's a WWAN card needs to use pinctrl to reset itself after firmware 
update. Currently we can't use pinctrl to reset it.

  [Fix]
  Translate GPIO to pinctrl pins correctly.

  [Test]
  The WWAN reset function works once the fix is applied.

  [Regression Potential]
  Low. Limits to pinctrl-intel and it's in mainline for a while.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1811777/+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 1811777] Missing required logs.

[Ubuntu Kernel Bot]

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

apport-collect 1811777

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

Title:
  Fix non-working pinctrl-intel

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

Bug description:
  [Impact]
  Intel pinctrl doesn't work.
  There's a WWAN card needs to use pinctrl to reset itself after firmware 
update. Currently we can't use pinctrl to reset it.

  [Fix]
  Translate GPIO to pinctrl pins correctly.

  [Test]
  The WWAN reset function works once the fix is applied.

  [Regression Potential]
  Low. Limits to pinctrl-intel and it's in mainline for a while.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1811777/+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 1810214] [NEW] [ZenBook UX433FA_UX433FA, Realtek ALC294, Speaker, Internal] No sound at all

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

There is no sound whatsoever while the controls all seems to indicate
the playback is working. The patop's internal speaker, headphones, even
bluetooth is not outputting any sound. Trying to upgrade the kernel to
two different versions had no effect. There simply is no sound output
nor is there any indication the microphone is working either, but
without sound output that's hard to confirm. There are not issues with
sounds when I boot into Windows

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
Uname: Linux 4.19.13-041913-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mac1193 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan  1 14:18:09 2019
InstallationDate: Installed on 2018-12-30 (2 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mac1193 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [ZenBook UX433FA_UX433FA, Realtek ALC294, Speaker, Internal] No sound at 
all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/19/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX433FA.204
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX433FA
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.:bvrUX433FA.204:bd09/19/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FA_UX433FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ZenBook
dmi.product.name: ZenBook UX433FA_UX433FA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Affects: linux (Ubuntu)
 Importance: High
 Status: Fix Committed


** Tags: amd64 apport-bug bionic wayland-session
-- 
[ZenBook UX433FA_UX433FA, Realtek ALC294, Speaker, Internal] No sound at all
https://bugs.launchpad.net/bugs/1810214
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 1811777] Re: Fix non-working pinctrl-intel

[AceLan Kao]

** Tags added: originate-from-1800987 somerville

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

Title:
  Fix non-working pinctrl-intel

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

Bug description:
  [Impact]
  Intel pinctrl doesn't work.
  There's a WWAN card needs to use pinctrl to reset itself after firmware 
update. Currently we can't use pinctrl to reset it.

  [Fix]
  Translate GPIO to pinctrl pins correctly.

  [Test]
  The WWAN reset function works once the fix is applied.

  [Regression Potential]
  Low. Limits to pinctrl-intel and it's in mainline for a while.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1811777/+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 1811419] Re: linux: 4.15.0-44.47 -proposed tracker

[Brad Figg]

** 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
  
  backports: bug 1811429 (linux-azure), bug 1811430 (linux-aws-hwe), bug 
1811431 (linux-azure), bug 1811432 (linux-gcp), bug 1811434 (linux-hwe), bug 
1811435 (linux-hwe-edge), bug 1811436 (linux-oracle)
  derivatives: bug 1811420 (linux-raspi2), bug 1811421 (linux-oem), bug 1811422 
(linux-aws), bug 1811423 (linux-azure), bug 1811424 (linux-gcp), bug 1811425 
(linux-kvm), bug 1811427 (linux-oracle)
  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed -- release to Proposed in progress
  phase-changed: Tuesday, 15. January 2019 08:32 UTC
  reason:
-   promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed
+   promote-to-proposed: Ongoing -- packages copies requested

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

Title:
  linux: 4.15.0-44.47 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-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 Committed
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 snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
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:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux 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

  backports: bug 1811429 (linux-azure), bug 1811430 (linux-aws-hwe), bug 
1811431 (linux-azure), bug 1811432 (linux-gcp), bug 1811434 (linux-hwe), bug 
1811435 (linux-hwe-edge), bug 1811436 (linux-oracle)
  derivatives: bug 1811420 (linux-raspi2), bug 1811421 (linux-oem), bug 1811422 
(linux-aws), bug 1811423 (linux-azure), bug 1811424 (linux-gcp), bug 1811425 
(linux-kvm), bug 1811427 (linux-oracle)
  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed -- release to Proposed in progress
  phase-changed: Tuesday, 15. January 2019 08:32 UTC
  reason:
promote-to-proposed: Ongoing -- packages copies requested

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811419/+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 1811406] Re: linux: 4.18.0-14.15 -proposed tracker

[Brad Figg]

** 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
  
  backports: bug 1811407 (linux-hwe), bug 1811408 (linux-hwe-edge), bug 1811409 
(linux-aws-edge), bug 1811410 (linux-azure-edge), bug 1811411 (linux-gcp-edge), 
bug 1811418 (linux-azure-edge)
  derivatives: bug 1811412 (linux-raspi2), bug 1811414 (linux-aws), bug 1811415 
(linux-azure), bug 1811416 (linux-gcp), bug 1811417 (linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed -- release to Proposed in progress
  phase-changed: Tuesday, 15. January 2019 08:32 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Ongoing -- packages copies requested

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

Title:
  linux: 4.18.0-14.15 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-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 Committed
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 upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux 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

  backports: bug 1811407 (linux-hwe), bug 1811408 (linux-hwe-edge), bug 1811409 
(linux-aws-edge), bug 1811410 (linux-azure-edge), bug 1811411 (linux-gcp-edge), 
bug 1811418 (linux-azure-edge)
  derivatives: bug 1811412 (linux-raspi2), bug 1811414 (linux-aws), bug 1811415 
(linux-azure), bug 1811416 (linux-gcp), bug 1811417 (linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed -- release to Proposed in progress
  phase-changed: Tuesday, 15. January 2019 08:32 UTC
  reason:
promote-to-proposed: Ongoing -- packages copies requested

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811406/+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 1810214] Re: [ZenBook UX433FA_UX433FA, Realtek ALC294, Speaker, Internal] No sound at all

[Sebastien Bacher]

Looks like it should be fixed with that kernel commit
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/sound/pci/hda/patch_realtek.c?id=0bea4cc8383519f78f3f74caca7bdebdfb346d3b

** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)

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

** Changed in: linux (Ubuntu)
   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/1810214

Title:
  [ZenBook UX433FA_UX433FA, Realtek ALC294, Speaker, Internal] No sound
  at all

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  There is no sound whatsoever while the controls all seems to indicate
  the playback is working. The patop's internal speaker, headphones,
  even bluetooth is not outputting any sound. Trying to upgrade the
  kernel to two different versions had no effect. There simply is no
  sound output nor is there any indication the microphone is working
  either, but without sound output that's hard to confirm. There are not
  issues with sounds when I boot into Windows

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.19.13-041913-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mac1193 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan  1 14:18:09 2019
  InstallationDate: Installed on 2018-12-30 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mac1193 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook UX433FA_UX433FA, Realtek ALC294, Speaker, Internal] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX433FA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX433FA
  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.:bvrUX433FA.204:bd09/19/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FA_UX433FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX433FA_UX433FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214/+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 1811254] Re: HP ProBook 470 G5, LED's in Hotkeys f5, f8 and f11 without function

[kuehhe1]

Hello,
my on-board search for other hotkey LED-issues led me to this bug report: 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705586

but the solution to the file: /etc/modprobe.d/alsa-base.conf

to supplement the entry: options snd-hda-intel mode = mute-led-gpio

did not lead to the solution here. Presumably, the failure results from
a different ubuntu-version and/or a another kernel.

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

Title:
  HP ProBook 470 G5, LED's in Hotkeys f5, f8 and f11 without function

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Notebook: HP ProBook 470 G5 (3KZ03EA)
  Distro: Linux Mint 19.1 Tessa
  Desktop: Cinnamon 4.0.8
  Kernel: 4.15.0-43-generic x86_64 bits: 64

  The functions of all hotkeys are given, but the LEDs in the f5 LS-
  mute, f8 micro-mute and f11 wireless on/off buttons do not show the
  status.  The LED in f11 is permanently lit.

  This is my first bug report to launchpad and I ask for leniency and
  troubleshooting support.

  I created 11 logs, unfortunately the upload did not work at once:

  acpi_listen.txt
  apt-cache-policy
  dmesg.log
  lsb_release
  lsinput.log
  lspci-vnvn.log
  udev-db.txt
  version.log
  xev keypress test.txt
  xkbcomp.txt
  xkbmap.txt

  Information: This problem was previously discussed on
  linuxmintusers.de:
  https://www.linuxmintusers.de/index.php?topic=51737.msg710376#msg710376

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+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 1506914] Re: 8086:0416 [Asus G550JK] Changing screen brightness not working using keyboard shortcut Fn+F5/F6

[Pander]

Vidvranjek, is this still a problem or did you find upstream link as
Christopher asked for? Otherwise, please close this bug.

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

Title:
  8086:0416 [Asus G550JK] Changing screen brightness not working using
  keyboard shortcut Fn+F5/F6

Status in linux package in Ubuntu:
  Triaged

Bug description:
  WORKAROUND: Change in /etc/default/grub :
  GRUB_CMDLINE_LINUX_DEFAULT=""

  to:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi="

  run $ sudo update-grub
  reboot

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Oct 16 17:27:47 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus: bbswitch, 0.7, 3.19.0-30-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:11cd]
     Subsystem: ASUSTeK Computer Inc. Device [1043:11cd]
  JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] 
failed with exit code 1: No journal files were found.
  MachineType: ASUSTeK COMPUTER INC. G550JK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic.efi.signed 
root=UUID=9a6cce6e-ddfb-40c7-a64c-823140602164 ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G550JK.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G550JK
  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.:bvrG550JK.204:bd08/11/2014:svnASUSTeKCOMPUTERINC.:pnG550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: G550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Sat Oct 10 11:46:59 2015
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [GLAMOR] failed to initialise EGL
   NOUVEAU(G0): Error creating GPU channel: -19
   NOUVEAU(G0): Error initialising acceleration.  Falling back to NoAccel
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12876
   vendor SDC
  xserver.version: 2:1.17.1-0ubuntu3.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506914/+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 1811785] [NEW] NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840

[Jean De Gyns]

Public bug reported:

On ubuntu 18.04.1 :

1°) With 4.15.0-43 two default namespaces in raw mode are visible while
there shouldn't be any but no settings change could be applied.

root@server:~# ndctl list -R
[
  {
"dev":"region1",
"size":103079215104,
"available_size":0,
"type":"pmem",
"numa_node":1,
"persistence_domain":"unknown"
  },
  {
"dev":"region0",
"size":103079215104,
"available_size":0,
"type":"pmem",
"numa_node":0,
"persistence_domain":"unknown"
  }
]

root@server:~# ndctl list
[
  {
"dev":"namespace1.0",
"mode":"raw",
"size":103079215104,
"sector_size":512,
"blockdev":"pmem1",
"numa_node":1
  },
  {
"dev":"namespace0.0",
"mode":"raw",
"size":103079215104,
"sector_size":512,
"blockdev":"pmem0",
"numa_node":0
  }
]

root@server:~# ndctl create-namespace --reconfig=namespace1.0 --type=pmem 
--mode=sector -f
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem11: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_index: nmem11: label area (1024) too small to host 
(256 byte) labels
libndctl: sizeof_namespace_ind

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

[Ubuntu Kernel Bot]

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

apport-collect 1811785

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

Title:
  NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840

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

Bug description:
  On ubuntu 18.04.1 :

  1°) With 4.15.0-43 two default namespaces in raw mode are visible
  while there shouldn't be any but no settings change could be applied.

  root@server:~# ndctl list -R
  [
{
  "dev":"region1",
  "size":103079215104,
  "available_size":0,
  "type":"pmem",
  "numa_node":1,
  "persistence_domain":"unknown"
},
{
  "dev":"region0",
  "size":103079215104,
  "available_size":0,
  "type":"pmem",
  "numa_node":0,
  "persistence_domain":"unknown"
}
  ]

  root@server:~# ndctl list
  [
{
  "dev":"namespace1.0",
  "mode":"raw",
  "size":103079215104,
  "sector_size":512,
  "blockdev":"pmem1",
  "numa_node":1
},
{
  "dev":"namespace0.0",
  "mode":"raw",
  "size":103079215104,
  "sector_size":512,
  "blockdev":"pmem0",
  "numa_node":0
}
  ]

  root@server:~# ndctl create-namespace --reconfig=namespace1.0 --type=pmem 
--mode=sector -f
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof

[Kernel-packages] [Bug 1811425] Re: linux-kvm: 4.15.0-1029.29 -proposed tracker

[Łukasz Zemczak]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux-kvm: 4.15.0-1029.29 -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 promote-to-proposed series:
  Fix Committed
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 upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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: 1811419
  phase: Promote to Proposed -- release to Proposed in progress
  phase-changed: Tuesday, 15. January 2019 09:31 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811425/+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 1810619] Re: Sleep mode doesn't work

[Kai-Heng Feng]

> About 4 - 6 hours.
Do you mean a fully charged battery only lasts 4 ~ 6 hours?

> With 4.18-10, I don't have this behavior. Is it right ?
Yes, this is right. The default on keyboard wakeup changes.

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

Title:
  Sleep mode doesn't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Dell XPS 13 laptop (9370), the sleep mode dosn't work anymore with 
linux-image-4.18.0-13.
  The screen goes off correctly but any touch resume the laptop.

  This is the log :
  Jan  5 11:15:25 skeleton systemd[1]: Reached target Sleep.
  Jan  5 11:15:25 skeleton systemd[1]: Starting Suspend...
  Jan  5 11:15:25 skeleton systemd[1]: Starting Network Manager Script 
Dispatcher Service...
  Jan  5 11:15:25 skeleton systemd-sleep[6229]: Suspending system...
  Jan  5 11:15:25 skeleton kernel: [ 6176.006021] PM: suspend entry (s2idle)
  an  5 11:15:25 skeleton dbus-daemon[1051]: [system] Successfully activated 
service 'org.freedesktop.nm_dispatcher'
  Jan  5 11:15:25 skeleton systemd[1]: Started Network Manager Script 
Dispatcher Service.
  Jan  5 11:15:25 skeleton nm-dispatcher: req:1 'down' [wlp2s0]: new request (1 
scripts)
  Jan  5 11:15:25 skeleton nm-dispatcher: req:1 'down' [wlp2s0]: start running 
ordered scripts...

  [...]
  Resume :

  Jan  5 12:00:02 skeleton kernel: [ 6176.006023] PM: Syncing filesystems ... 
done.
  Jan  5 12:00:02 skeleton kernel: [ 6176.016581] Freezing user space processes 
... (elapsed 0.088 seconds) done.
  Jan  5 12:00:02 skeleton kernel: [ 6176.104653] OOM killer disabled.
  Jan  5 12:00:02 skeleton kernel: [ 6176.104654] Freezing remaining freezable 
tasks ... (elapsed 0.001 seconds) done.
  Jan  5 12:00:02 skeleton kernel: [ 6176.106070] Suspending console(s) (use 
no_console_suspend to debug)
  Jan  5 12:00:02 skeleton kernel: [ 8852.990035] OOM killer enabled.
  Jan  5 12:00:02 skeleton kernel: [ 8852.990037] Restarting tasks ... done.
  Jan  5 12:00:02 skeleton kernel: [ 8853.015639] r8152 2-1.2:1.0 
enxe4b97acfa7e9: carrier on
  Jan  5 12:00:02 skeleton kernel: [ 8853.084055] PM: suspend exit


  
  With linux-image-4.18.0-10, it works correcly (but no with 4.18.0-11 and 
4.18.0-12).
  Thanks,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810619/+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 1798776] Re: kvm_stat : missing python dependency

[Stefan Bader]

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

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

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

Title:
  kvm_stat : missing python dependency

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  New

Bug description:
  After installing linux-tools-host, the included kvm_stat utility won't
  work:

  root@ubuntu:~# kvm_stat 
  -bash: /usr/bin/kvm_stat: /usr/bin/python: bad interpreter: No such file or 
directory

  Reason is that there is apparently no dependency on a python package
  from the linux-tools-host package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1798776/+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 1811425] Re: linux-kvm: 4.15.0-1029.29 -proposed tracker

[Brad Figg]

** 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: 1811419
- phase: Promote to Proposed -- release to Proposed ready
- phase-changed: Monday, 14. January 2019 22:30 UTC
+ phase: Promote to Proposed -- release to Proposed in progress
+ phase-changed: Tuesday, 15. January 2019 09:31 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- review 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/1811425

Title:
  linux-kvm: 4.15.0-1029.29 -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 promote-to-proposed series:
  Fix Committed
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 upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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: 1811419
  phase: Promote to Proposed -- release to Proposed in progress
  phase-changed: Tuesday, 15. January 2019 09:31 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811425/+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 1811425] Re: linux-kvm: 4.15.0-1029.29 -proposed tracker

[Łukasz Zemczak]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

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

Title:
  linux-kvm: 4.15.0-1029.29 -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 promote-to-proposed series:
  Fix Committed
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 upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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: 1811419
  phase: Promote to Proposed -- release to Proposed in progress
  phase-changed: Tuesday, 15. January 2019 09:31 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811425/+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 1811414] Re: linux-aws: 4.18.0-1008.10 -proposed tracker

[Łukasz Zemczak]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux-aws: 4.18.0-1008.10 -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 promote-to-proposed series:
  In Progress
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 upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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: 1811406
  phase: Promote to Proposed -- release to Proposed ready
  phase-changed: Tuesday, 15. January 2019 02:04 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/1811414/+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 1806343] Re: FN+F3/F4 does not modify keyboard backlight brightness.

[Pander]

Same problem with Lubuntu 18.10 on ASUS Zenbook UX31A. It loads asus kernel 
modules:
- asus_nb_wmi
- asus_wmi
- asus_wireless

Used to work with all versions in the last five years prior to 18.10.
The manual echo commands listed at the the top do work.

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

Title:
  FN+F3/F4 does not modify keyboard backlight brightness.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  acpi_listen does not output anything to terminal when pressing key
  combination.

  Keyboard backlight has worked on older versions (I believe 18.04 or
  earlier.)

  I can manually toggle with:

  echo 0 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness
  echo 1 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness
  echo 2 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness
  echo 3 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness

  for varying degrees of brightness.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-11-28 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181128)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  disco
  Uname: Linux 4.19.6-041906-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  duck   3632 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-11-28 (22 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181128)
  MachineType: ASUSTeK COMPUTER INC. GL502VMK
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic 
root=/dev/mapper/vg0-root ro quiet splash acpi_osi= acpi_backlight=native 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  Tags:  disco
  Uname: Linux 4.18.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL502VMK.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL502VMK
  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.:bvrGL502VMK.305:bd07/03/2017:svnASUSTeKCOMPUTERINC.:pnGL502VMK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VMK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL502VMK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806343/+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 1802652] Re: keyboard backlight not working on Asus GM501

[Pander]

see also https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806343

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

Title:
  keyboard backlight not working on Asus GM501

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The keyboard lights and most of the F keys aren't working.
  Kernel = 4.15.0-20-generic
  System linux mint 19

  ls -hal /sys/class/leds/
  total 0
  drwxr-xr-x  2 root root 0 Nov 10 15:47 .
  drwxr-xr-x 72 root root 0 Nov 10 15:43 ..
  lrwxrwxrwx  1 root root 0 Nov 10 15:43 asus::lightbar -> 
../../devices/platform/asus-nb-wmi/leds/asus::lightbar
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 asus-wireless::airplane -> 
../../devices/LNXSYSTM:00/LNXSYBUS:00/ATK4002:00/leds/asus-wireless::airplane
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input4::capslock -> 
../../devices/platform/i8042/serio0/input/input4/input4::capslock
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input4::numlock -> 
../../devices/platform/i8042/serio0/input/input4/input4::numlock
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input4::scrolllock -> 
../../devices/platform/i8042/serio0/input/input4/input4::scrolllock
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input7::capslock -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0001/input/input7/input7::capslock
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input7::compose -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0001/input/input7/input7::compose
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input7::kana -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0001/input/input7/input7::kana
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input7::numlock -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0001/input/input7/input7::numlock
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input7::scrolllock -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0001/input/input7/input7::scrolllock
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input8::capslock -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0002/input/input8/input8::capslock
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input8::compose -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0002/input/input8/input8::compose
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input8::kana -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0002/input/input8/input8::kana
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input8::numlock -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0002/input/input8/input8::numlock
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input8::scrolllock -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0002/input/input8/input8::scrolllock
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 phy0-led -> 
../../devices/pci:00/:00:14.3/leds/phy0-led

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802652/+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 1806343] Re: FN+F3/F4 does not modify keyboard backlight brightness.

[Pander]

See also https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802652

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

Title:
  FN+F3/F4 does not modify keyboard backlight brightness.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  acpi_listen does not output anything to terminal when pressing key
  combination.

  Keyboard backlight has worked on older versions (I believe 18.04 or
  earlier.)

  I can manually toggle with:

  echo 0 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness
  echo 1 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness
  echo 2 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness
  echo 3 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness

  for varying degrees of brightness.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-11-28 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181128)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  disco
  Uname: Linux 4.19.6-041906-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  duck   3632 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-11-28 (22 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181128)
  MachineType: ASUSTeK COMPUTER INC. GL502VMK
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic 
root=/dev/mapper/vg0-root ro quiet splash acpi_osi= acpi_backlight=native 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  Tags:  disco
  Uname: Linux 4.18.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL502VMK.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL502VMK
  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.:bvrGL502VMK.305:bd07/03/2017:svnASUSTeKCOMPUTERINC.:pnGL502VMK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VMK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL502VMK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806343/+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 1811788] [NEW] Thermald 1.8 does not install default config

[Pablo Catalina]

Public bug reported:

I created a backport of the 1.8 package for Ubuntu Cosmic. After
installing it, I noted that it does not install a default config file,
so it renders and error:

ene 15 10:29:25 pcatalin-lnx systemd[1]: Started Thermal Daemon Service.
ene 15 10:29:25 pcatalin-lnx thermald[22175]: 22 CPUID levels; 
family:model:stepping 0x6:9e:a (6:158:10)
ene 15 10:29:25 pcatalin-lnx thermald[22175]: Polling mode is enabled: 4
ene 15 10:29:25 pcatalin-lnx thermald[22175]: sensor id 12 : No temp sysfs for 
reading raw temp
ene 15 10:29:25 pcatalin-lnx thermald[22175]: sensor id 12 : No temp sysfs for 
reading raw temp
ene 15 10:29:25 pcatalin-lnx thermald[22175]: sensor id 12 : No temp sysfs for 
reading raw temp
ene 15 10:29:25 pcatalin-lnx thermald[22175]: I/O warning : failed to load 
external entity "/etc/thermald/thermal-conf.xml"
ene 15 10:29:25 pcatalin-lnx thermald[22175]: error: could not parse file 
/etc/thermald/thermal-conf.xml
ene 15 10:29:25 pcatalin-lnx thermald[22175]: sysfs open failed
ene 15 10:29:25 pcatalin-lnx thermald[22175]: I/O warning : failed to load 
external entity "/etc/thermald/thermal-conf.xml"
ene 15 10:29:25 pcatalin-lnx thermald[22175]: error: could not parse file 
/etc/thermald/thermal-conf.xml
ene 15 10:29:25 pcatalin-lnx thermald[22175]: I/O warning : failed to load 
external entity "/etc/thermald/thermal-conf.xml"
ene 15 10:29:25 pcatalin-lnx thermald[22175]: error: could not parse file 
/etc/thermald/thermal-conf.xml


I suggest to install a default configuration on /etc/thermald/thermal-conf.xml

** Affects: thermald (Ubuntu)
 Importance: Undecided
 Status: Invalid

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

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

Title:
  Thermald 1.8 does not install default config

Status in thermald package in Ubuntu:
  Invalid

Bug description:
  I created a backport of the 1.8 package for Ubuntu Cosmic. After
  installing it, I noted that it does not install a default config file,
  so it renders and error:

  ene 15 10:29:25 pcatalin-lnx systemd[1]: Started Thermal Daemon Service.
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: 22 CPUID levels; 
family:model:stepping 0x6:9e:a (6:158:10)
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: Polling mode is enabled: 4
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: sensor id 12 : No temp sysfs 
for reading raw temp
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: sensor id 12 : No temp sysfs 
for reading raw temp
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: sensor id 12 : No temp sysfs 
for reading raw temp
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: I/O warning : failed to load 
external entity "/etc/thermald/thermal-conf.xml"
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: error: could not parse file 
/etc/thermald/thermal-conf.xml
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: sysfs open failed
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: I/O warning : failed to load 
external entity "/etc/thermald/thermal-conf.xml"
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: error: could not parse file 
/etc/thermald/thermal-conf.xml
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: I/O warning : failed to load 
external entity "/etc/thermald/thermal-conf.xml"
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: error: could not parse file 
/etc/thermald/thermal-conf.xml

  
  I suggest to install a default configuration on /etc/thermald/thermal-conf.xml

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1811788/+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 1803360] Re: Fanless systems with DPTF shutdown before using any passive cooling device

[Colin Ian King]

The xenial version of thermald does not support the INT340X, so I'm
reluctant to back port the fix as I need to add the INT340X support in
which is quite a few changes.  As this is adding extra functionality to
thermald I believe this falls outside the remit of a SRU.

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

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

Title:
  Fanless systems with DPTF shutdown before using any passive cooling
  device

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Xenial:
  New
Status in thermald source package in Bionic:
  In Progress
Status in thermald source package in Cosmic:
  In Progress
Status in thermald source package in Disco:
  Fix Released

Bug description:
  == SRU Justification, Cosmic, Bionic, Xenial ==

  There are some new fanless platforms use DPTF's virtual sensor instead
  of INT340X devices.

  Because of that, the _PSV is no longer in use, at least not directly,
  hence its value may set higher then _CRT. To a fanless system that means
  no cooling device gets activated before _CRT, so the system will be
  considered overheated by Linux kernel, and gets shutdown by the kernel.

  == Fix ==
   
  Upstream fix 
https://github.com/intel/thermal_daemon/commit/97976782dd26b4d592ccb97eb89c2a3a871a22a9

  == Testing ==

  Exercise CPUs on a fanless INT340X device with _CRT ACPI objects and
  try and reach the trip point. Without the fix thermal overrun occurs
  and this trips CPU shutdown. With the fix, thermald will start to
  throttle the system and get it out of the thermal overrun zone.

  == Regression Potential ==

  This modifies the behavior for just INT340X devices with ACPI _CRT
  objects, specifically, now to honor this setting.  This is a small
  subset of devices with these objects and the change will in face make
  thermald catch systems before they hit thermal overrun, so the risk of
  regression is small. This fix also has been reviewed by the thermal
  experts at Intel, so it seems like a very reasonable workaround for
  these specific use cases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1803360/+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 1811414] Re: linux-aws: 4.18.0-1008.10 -proposed tracker

[Łukasz Zemczak]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

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

Title:
  linux-aws: 4.18.0-1008.10 -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 promote-to-proposed series:
  Fix Committed
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 upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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: 1811406
  phase: Promote to Proposed -- release to Proposed ready
  phase-changed: Tuesday, 15. January 2019 02:04 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/1811414/+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 1811788] Re: Thermald 1.8 does not install default config

[Pablo Catalina]

Sorry, thermald works fine without this config file ;)

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

Title:
  Thermald 1.8 does not install default config

Status in thermald package in Ubuntu:
  Invalid

Bug description:
  I created a backport of the 1.8 package for Ubuntu Cosmic. After
  installing it, I noted that it does not install a default config file,
  so it renders and error:

  ene 15 10:29:25 pcatalin-lnx systemd[1]: Started Thermal Daemon Service.
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: 22 CPUID levels; 
family:model:stepping 0x6:9e:a (6:158:10)
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: Polling mode is enabled: 4
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: sensor id 12 : No temp sysfs 
for reading raw temp
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: sensor id 12 : No temp sysfs 
for reading raw temp
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: sensor id 12 : No temp sysfs 
for reading raw temp
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: I/O warning : failed to load 
external entity "/etc/thermald/thermal-conf.xml"
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: error: could not parse file 
/etc/thermald/thermal-conf.xml
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: sysfs open failed
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: I/O warning : failed to load 
external entity "/etc/thermald/thermal-conf.xml"
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: error: could not parse file 
/etc/thermald/thermal-conf.xml
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: I/O warning : failed to load 
external entity "/etc/thermald/thermal-conf.xml"
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: error: could not parse file 
/etc/thermald/thermal-conf.xml

  
  I suggest to install a default configuration on /etc/thermald/thermal-conf.xml

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1811788/+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 1796573] Re: Keyboard backlight not working on ubuntu 18.10, but works on 18.04

[Pander]

There are two 'versions' of this issue. One for users with
/sys/class/leds/*::kbd_backlight* and one for users missing
/sys/class/leds/*::kbd_backlight*

I do have /sys/class/leds/*::kbd_backlight* and upower 0.99.8-2ubuntu0
does not solve the issue. I can change the keyboard leds via the command
line, but not via the fn keys.

Where should that be reported upstream? With upower?

Please, see also
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806343
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802652

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

Title:
  Keyboard backlight not working on ubuntu 18.10, but works on 18.04

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

Bug description:
  1) 18.10
  2) 
  3) keyboard backlight turns on
  4) nothing

  I have ASUS s14 s406ua laptop and I can't turn my keyboard backlight
  on...

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nadavshabtai   2215 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  7 19:21:02 2018
  InstallationDate: Installed on 2018-09-28 (9 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 13d3:3500 IMC Networks 
   Bus 001 Device 002: ID 13d3:56a2 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X406UAR
  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.18.0-8-generic 
root=UUID=35bafd0c-f18c-4cc0-9146-d0f9f77447ff ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-09-28 (9 days ago)
  dmi.bios.date: 04/24/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X406UAR.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X406UAR
  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.:bvrX406UAR.309:bd04/24/2018:svnASUSTeKCOMPUTERINC.:pnX406UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX406UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: X406UAR
  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/1796573/+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 1811415] Re: linux-azure: 4.18.0-1008.8 -proposed tracker

[Łukasz Zemczak]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux-azure: 4.18.0-1008.8 -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:
  In Progress
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:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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: 1811406
  phase: Promote to Proposed -- release to Proposed in progress
  phase-changed: Tuesday, 15. January 2019 10:01 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811415/+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 1802652] Re: keyboard backlight not working on Asus GM501

[Pander]

and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796573

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

Title:
  keyboard backlight not working on Asus GM501

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The keyboard lights and most of the F keys aren't working.
  Kernel = 4.15.0-20-generic
  System linux mint 19

  ls -hal /sys/class/leds/
  total 0
  drwxr-xr-x  2 root root 0 Nov 10 15:47 .
  drwxr-xr-x 72 root root 0 Nov 10 15:43 ..
  lrwxrwxrwx  1 root root 0 Nov 10 15:43 asus::lightbar -> 
../../devices/platform/asus-nb-wmi/leds/asus::lightbar
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 asus-wireless::airplane -> 
../../devices/LNXSYSTM:00/LNXSYBUS:00/ATK4002:00/leds/asus-wireless::airplane
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input4::capslock -> 
../../devices/platform/i8042/serio0/input/input4/input4::capslock
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input4::numlock -> 
../../devices/platform/i8042/serio0/input/input4/input4::numlock
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input4::scrolllock -> 
../../devices/platform/i8042/serio0/input/input4/input4::scrolllock
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input7::capslock -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0001/input/input7/input7::capslock
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input7::compose -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0001/input/input7/input7::compose
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input7::kana -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0001/input/input7/input7::kana
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input7::numlock -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0001/input/input7/input7::numlock
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input7::scrolllock -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0001/input/input7/input7::scrolllock
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input8::capslock -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0002/input/input8/input8::capslock
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input8::compose -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0002/input/input8/input8::compose
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input8::kana -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0002/input/input8/input8::kana
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input8::numlock -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0002/input/input8/input8::numlock
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input8::scrolllock -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0002/input/input8/input8::scrolllock
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 phy0-led -> 
../../devices/pci:00/:00:14.3/leds/phy0-led

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802652/+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 1796573] Re: Keyboard backlight not working on ubuntu 18.10, but works on 18.04

[Daniel van Vugt]

Pander,

In that case we require a separate bug report from your affected laptop
to get its specific details. To do that please run this on the affected
laptop:

  ubuntu-bug linux

and create a new bug.

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

Title:
  Keyboard backlight not working on ubuntu 18.10, but works on 18.04

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

Bug description:
  1) 18.10
  2) 
  3) keyboard backlight turns on
  4) nothing

  I have ASUS s14 s406ua laptop and I can't turn my keyboard backlight
  on...

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nadavshabtai   2215 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  7 19:21:02 2018
  InstallationDate: Installed on 2018-09-28 (9 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 13d3:3500 IMC Networks 
   Bus 001 Device 002: ID 13d3:56a2 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X406UAR
  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.18.0-8-generic 
root=UUID=35bafd0c-f18c-4cc0-9146-d0f9f77447ff ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-09-28 (9 days ago)
  dmi.bios.date: 04/24/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X406UAR.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X406UAR
  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.:bvrX406UAR.309:bd04/24/2018:svnASUSTeKCOMPUTERINC.:pnX406UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX406UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: X406UAR
  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/1796573/+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 1806343] Re: FN+F3/F4 does not modify keyboard backlight brightness.

[Pander]

and and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796573

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

Title:
  FN+F3/F4 does not modify keyboard backlight brightness.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  acpi_listen does not output anything to terminal when pressing key
  combination.

  Keyboard backlight has worked on older versions (I believe 18.04 or
  earlier.)

  I can manually toggle with:

  echo 0 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness
  echo 1 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness
  echo 2 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness
  echo 3 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness

  for varying degrees of brightness.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-11-28 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181128)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  disco
  Uname: Linux 4.19.6-041906-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  duck   3632 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-11-28 (22 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181128)
  MachineType: ASUSTeK COMPUTER INC. GL502VMK
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic 
root=/dev/mapper/vg0-root ro quiet splash acpi_osi= acpi_backlight=native 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  Tags:  disco
  Uname: Linux 4.18.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL502VMK.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL502VMK
  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.:bvrGL502VMK.305:bd07/03/2017:svnASUSTeKCOMPUTERINC.:pnGL502VMK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VMK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL502VMK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806343/+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 1811425] Re: linux-kvm: 4.15.0-1029.29 -proposed tracker

[Brad Figg]

** 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: 1811419
  phase: Promote to Proposed -- release to Proposed in progress
  phase-changed: Tuesday, 15. January 2019 09:31 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

Title:
  linux-kvm: 4.15.0-1029.29 -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 promote-to-proposed series:
  Fix Committed
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 upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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: 1811419
  phase: Promote to Proposed -- release to Proposed in progress
  phase-changed: Tuesday, 15. January 2019 09:31 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811425/+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 1811415] Re: linux-azure: 4.18.0-1008.8 -proposed tracker

[Brad Figg]

** 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: 1811406
- phase: Promote to Proposed -- release to Proposed ready
- phase-changed: Tuesday, 15. January 2019 03:31 UTC
+ phase: Promote to Proposed -- release to Proposed in progress
+ phase-changed: Tuesday, 15. January 2019 10:01 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- review 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/1811415

Title:
  linux-azure: 4.18.0-1008.8 -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:
  In Progress
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:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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: 1811406
  phase: Promote to Proposed -- release to Proposed in progress
  phase-changed: Tuesday, 15. January 2019 10:01 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811415/+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 1811414] Re: linux-aws: 4.18.0-1008.10 -proposed tracker

[Brad Figg]

** 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: 1811406
- phase: Promote to Proposed -- release to Proposed ready
- phase-changed: Tuesday, 15. January 2019 02:04 UTC
+ phase: Promote to Proposed -- release to Proposed in progress
+ phase-changed: Tuesday, 15. January 2019 10:03 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

Title:
  linux-aws: 4.18.0-1008.10 -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 promote-to-proposed series:
  Fix Committed
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 upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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: 1811406
  phase: Promote to Proposed -- release to Proposed in progress
  phase-changed: Tuesday, 15. January 2019 10:03 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811414/+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 1811419] Re: linux: 4.15.0-44.47 -proposed tracker

[Brad Figg]

** 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
  
  backports: bug 1811429 (linux-azure), bug 1811430 (linux-aws-hwe), bug 
1811431 (linux-azure), bug 1811432 (linux-gcp), bug 1811434 (linux-hwe), bug 
1811435 (linux-hwe-edge), bug 1811436 (linux-oracle)
  derivatives: bug 1811420 (linux-raspi2), bug 1811421 (linux-oem), bug 1811422 
(linux-aws), bug 1811423 (linux-azure), bug 1811424 (linux-gcp), bug 1811425 
(linux-kvm), bug 1811427 (linux-oracle)
  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed -- release to Proposed in progress
  phase-changed: Tuesday, 15. January 2019 08:32 UTC
  reason:
-   promote-to-proposed: Ongoing -- packages copies requested
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

Title:
  linux: 4.15.0-44.47 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-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 Committed
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 snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
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:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux 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

  backports: bug 1811429 (linux-azure), bug 1811430 (linux-aws-hwe), bug 
1811431 (linux-azure), bug 1811432 (linux-gcp), bug 1811434 (linux-hwe), bug 
1811435 (linux-hwe-edge), bug 1811436 (linux-oracle)
  derivatives: bug 1811420 (linux-raspi2), bug 1811421 (linux-oem), bug 1811422 
(linux-aws), bug 1811423 (linux-azure), bug 1811424 (linux-gcp), bug 1811425 
(linux-kvm), bug 1811427 (linux-oracle)
  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed -- release to Proposed in progress
  phase-changed: Tuesday, 15. January 2019 08:32 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811419/+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 1803360] Re: Fanless systems with DPTF shutdown before using any passive cooling device

[Kai-Heng Feng]

Ok, then we can leave Xenial out.

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

Title:
  Fanless systems with DPTF shutdown before using any passive cooling
  device

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Xenial:
  New
Status in thermald source package in Bionic:
  In Progress
Status in thermald source package in Cosmic:
  In Progress
Status in thermald source package in Disco:
  Fix Released

Bug description:
  == SRU Justification, Cosmic, Bionic, Xenial ==

  There are some new fanless platforms use DPTF's virtual sensor instead
  of INT340X devices.

  Because of that, the _PSV is no longer in use, at least not directly,
  hence its value may set higher then _CRT. To a fanless system that means
  no cooling device gets activated before _CRT, so the system will be
  considered overheated by Linux kernel, and gets shutdown by the kernel.

  == Fix ==
   
  Upstream fix 
https://github.com/intel/thermal_daemon/commit/97976782dd26b4d592ccb97eb89c2a3a871a22a9

  == Testing ==

  Exercise CPUs on a fanless INT340X device with _CRT ACPI objects and
  try and reach the trip point. Without the fix thermal overrun occurs
  and this trips CPU shutdown. With the fix, thermald will start to
  throttle the system and get it out of the thermal overrun zone.

  == Regression Potential ==

  This modifies the behavior for just INT340X devices with ACPI _CRT
  objects, specifically, now to honor this setting.  This is a small
  subset of devices with these objects and the change will in face make
  thermald catch systems before they hit thermal overrun, so the risk of
  regression is small. This fix also has been reviewed by the thermal
  experts at Intel, so it seems like a very reasonable workaround for
  these specific use cases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1803360/+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 1811785] Re: NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840

[JulietDeltaGolf]

apport information

** Tags added: apport-collected bionic

** Description changed:

  On ubuntu 18.04.1 :
  
  1°) With 4.15.0-43 two default namespaces in raw mode are visible while
  there shouldn't be any but no settings change could be applied.
  
  root@server:~# ndctl list -R
  [
{
  "dev":"region1",
  "size":103079215104,
  "available_size":0,
  "type":"pmem",
  "numa_node":1,
  "persistence_domain":"unknown"
},
{
  "dev":"region0",
  "size":103079215104,
  "available_size":0,
  "type":"pmem",
  "numa_node":0,
  "persistence_domain":"unknown"
}
  ]
  
  root@server:~# ndctl list
  [
{
  "dev":"namespace1.0",
  "mode":"raw",
  "size":103079215104,
  "sector_size":512,
  "blockdev":"pmem1",
  "numa_node":1
},
{
  "dev":"namespace0.0",
  "mode":"raw",
  "size":103079215104,
  "sector_size":512,
  "blockdev":"pmem0",
  "numa_node":0
}
  ]
  
  root@server:~# ndctl create-namespace --reconfig=namespace1.0 --type=pmem 
--mode=sector -f
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 by

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

[JulietDeltaGolf]

apport information

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

Title:
  NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840

Status in linux package in Ubuntu:
  Confirmed
Status in ndctl package in Ubuntu:
  New

Bug description:
  On ubuntu 18.04.1 :

  1°) With 4.15.0-43 two default namespaces in raw mode are visible
  while there shouldn't be any but no settings change could be applied.

  root@server:~# ndctl list -R
  [
{
  "dev":"region1",
  "size":103079215104,
  "available_size":0,
  "type":"pmem",
  "numa_node":1,
  "persistence_domain":"unknown"
},
{
  "dev":"region0",
  "size":103079215104,
  "available_size":0,
  "type":"pmem",
  "numa_node":0,
  "persistence_domain":"unknown"
}
  ]

  root@server:~# ndctl list
  [
{
  "dev":"namespace1.0",
  "mode":"raw",
  "size":103079215104,
  "sector_size":512,
  "blockdev":"pmem1",
  "numa_node":1
},
{
  "dev":"namespace0.0",
  "mode":"raw",
  "size":103079215104,
  "sector_size":512,
  "blockdev":"pmem0",
  "numa_node":0
}
  ]

  root@server:~# ndctl create-namespace --reconfig=namespace1.0 --type=pmem 
--mode=sector -f
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
 

[Kernel-packages] [Bug 1811785] Dependencies.txt

[JulietDeltaGolf]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1811785/+attachment/5229227/+files/Dependencies.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/1811785

Title:
  NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840

Status in linux package in Ubuntu:
  Confirmed
Status in ndctl package in Ubuntu:
  New

Bug description:
  On ubuntu 18.04.1 :

  1°) With 4.15.0-43 two default namespaces in raw mode are visible
  while there shouldn't be any but no settings change could be applied.

  root@server:~# ndctl list -R
  [
{
  "dev":"region1",
  "size":103079215104,
  "available_size":0,
  "type":"pmem",
  "numa_node":1,
  "persistence_domain":"unknown"
},
{
  "dev":"region0",
  "size":103079215104,
  "available_size":0,
  "type":"pmem",
  "numa_node":0,
  "persistence_domain":"unknown"
}
  ]

  root@server:~# ndctl list
  [
{
  "dev":"namespace1.0",
  "mode":"raw",
  "size":103079215104,
  "sector_size":512,
  "blockdev":"pmem1",
  "numa_node":1
},
{
  "dev":"namespace0.0",
  "mode":"raw",
  "size":103079215104,
  "sector_size":512,
  "blockdev":"pmem0",
  "numa_node":0
}
  ]

  root@server:~# ndctl create-namespace --reconfig=namespace1.0 --type=pmem 
--mode=sector -f
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256

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

[JulietDeltaGolf]

apport information

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

Title:
  NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840

Status in linux package in Ubuntu:
  Confirmed
Status in ndctl package in Ubuntu:
  New

Bug description:
  On ubuntu 18.04.1 :

  1°) With 4.15.0-43 two default namespaces in raw mode are visible
  while there shouldn't be any but no settings change could be applied.

  root@server:~# ndctl list -R
  [
{
  "dev":"region1",
  "size":103079215104,
  "available_size":0,
  "type":"pmem",
  "numa_node":1,
  "persistence_domain":"unknown"
},
{
  "dev":"region0",
  "size":103079215104,
  "available_size":0,
  "type":"pmem",
  "numa_node":0,
  "persistence_domain":"unknown"
}
  ]

  root@server:~# ndctl list
  [
{
  "dev":"namespace1.0",
  "mode":"raw",
  "size":103079215104,
  "sector_size":512,
  "blockdev":"pmem1",
  "numa_node":1
},
{
  "dev":"namespace0.0",
  "mode":"raw",
  "size":103079215104,
  "sector_size":512,
  "blockdev":"pmem0",
  "numa_node":0
}
  ]

  root@server:~# ndctl create-namespace --reconfig=namespace1.0 --type=pmem 
--mode=sector -f
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
 

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

[JulietDeltaGolf]

apport information

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

Title:
  NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840

Status in linux package in Ubuntu:
  Confirmed
Status in ndctl package in Ubuntu:
  New

Bug description:
  On ubuntu 18.04.1 :

  1°) With 4.15.0-43 two default namespaces in raw mode are visible
  while there shouldn't be any but no settings change could be applied.

  root@server:~# ndctl list -R
  [
{
  "dev":"region1",
  "size":103079215104,
  "available_size":0,
  "type":"pmem",
  "numa_node":1,
  "persistence_domain":"unknown"
},
{
  "dev":"region0",
  "size":103079215104,
  "available_size":0,
  "type":"pmem",
  "numa_node":0,
  "persistence_domain":"unknown"
}
  ]

  root@server:~# ndctl list
  [
{
  "dev":"namespace1.0",
  "mode":"raw",
  "size":103079215104,
  "sector_size":512,
  "blockdev":"pmem1",
  "numa_node":1
},
{
  "dev":"namespace0.0",
  "mode":"raw",
  "size":103079215104,
  "sector_size":512,
  "blockdev":"pmem0",
  "numa_node":0
}
  ]

  root@server:~# ndctl create-namespace --reconfig=namespace1.0 --type=pmem 
--mode=sector -f
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small t

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

[JulietDeltaGolf]

apport information

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

Title:
  NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840

Status in linux package in Ubuntu:
  Confirmed
Status in ndctl package in Ubuntu:
  New

Bug description:
  On ubuntu 18.04.1 :

  1°) With 4.15.0-43 two default namespaces in raw mode are visible
  while there shouldn't be any but no settings change could be applied.

  root@server:~# ndctl list -R
  [
{
  "dev":"region1",
  "size":103079215104,
  "available_size":0,
  "type":"pmem",
  "numa_node":1,
  "persistence_domain":"unknown"
},
{
  "dev":"region0",
  "size":103079215104,
  "available_size":0,
  "type":"pmem",
  "numa_node":0,
  "persistence_domain":"unknown"
}
  ]

  root@server:~# ndctl list
  [
{
  "dev":"namespace1.0",
  "mode":"raw",
  "size":103079215104,
  "sector_size":512,
  "blockdev":"pmem1",
  "numa_node":1
},
{
  "dev":"namespace0.0",
  "mode":"raw",
  "size":103079215104,
  "sector_size":512,
  "blockdev":"pmem0",
  "numa_node":0
}
  ]

  root@server:~# ndctl create-namespace --reconfig=namespace1.0 --type=pmem 
--mode=sector -f
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels

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

[JulietDeltaGolf]

apport information

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

Title:
  NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840

Status in linux package in Ubuntu:
  Confirmed
Status in ndctl package in Ubuntu:
  New

Bug description:
  On ubuntu 18.04.1 :

  1°) With 4.15.0-43 two default namespaces in raw mode are visible
  while there shouldn't be any but no settings change could be applied.

  root@server:~# ndctl list -R
  [
{
  "dev":"region1",
  "size":103079215104,
  "available_size":0,
  "type":"pmem",
  "numa_node":1,
  "persistence_domain":"unknown"
},
{
  "dev":"region0",
  "size":103079215104,
  "available_size":0,
  "type":"pmem",
  "numa_node":0,
  "persistence_domain":"unknown"
}
  ]

  root@server:~# ndctl list
  [
{
  "dev":"namespace1.0",
  "mode":"raw",
  "size":103079215104,
  "sector_size":512,
  "blockdev":"pmem1",
  "numa_node":1
},
{
  "dev":"namespace0.0",
  "mode":"raw",
  "size":103079215104,
  "sector_size":512,
  "blockdev":"pmem0",
  "numa_node":0
}
  ]

  root@server:~# ndctl create-namespace --reconfig=namespace1.0 --type=pmem 
--mode=sector -f
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 b

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

[JulietDeltaGolf]

apport information

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

Title:
  NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840

Status in linux package in Ubuntu:
  Confirmed
Status in ndctl package in Ubuntu:
  New

Bug description:
  On ubuntu 18.04.1 :

  1°) With 4.15.0-43 two default namespaces in raw mode are visible
  while there shouldn't be any but no settings change could be applied.

  root@server:~# ndctl list -R
  [
{
  "dev":"region1",
  "size":103079215104,
  "available_size":0,
  "type":"pmem",
  "numa_node":1,
  "persistence_domain":"unknown"
},
{
  "dev":"region0",
  "size":103079215104,
  "available_size":0,
  "type":"pmem",
  "numa_node":0,
  "persistence_domain":"unknown"
}
  ]

  root@server:~# ndctl list
  [
{
  "dev":"namespace1.0",
  "mode":"raw",
  "size":103079215104,
  "sector_size":512,
  "blockdev":"pmem1",
  "numa_node":1
},
{
  "dev":"namespace0.0",
  "mode":"raw",
  "size":103079215104,
  "sector_size":512,
  "blockdev":"pmem0",
  "numa_node":0
}
  ]

  root@server:~# ndctl create-namespace --reconfig=namespace1.0 --type=pmem 
--mode=sector -f
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256

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

[JulietDeltaGolf]

apport information

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

Title:
  NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840

Status in linux package in Ubuntu:
  Confirmed
Status in ndctl package in Ubuntu:
  New

Bug description:
  On ubuntu 18.04.1 :

  1°) With 4.15.0-43 two default namespaces in raw mode are visible
  while there shouldn't be any but no settings change could be applied.

  root@server:~# ndctl list -R
  [
{
  "dev":"region1",
  "size":103079215104,
  "available_size":0,
  "type":"pmem",
  "numa_node":1,
  "persistence_domain":"unknown"
},
{
  "dev":"region0",
  "size":103079215104,
  "available_size":0,
  "type":"pmem",
  "numa_node":0,
  "persistence_domain":"unknown"
}
  ]

  root@server:~# ndctl list
  [
{
  "dev":"namespace1.0",
  "mode":"raw",
  "size":103079215104,
  "sector_size":512,
  "blockdev":"pmem1",
  "numa_node":1
},
{
  "dev":"namespace0.0",
  "mode":"raw",
  "size":103079215104,
  "sector_size":512,
  "blockdev":"pmem0",
  "numa_node":0
}
  ]

  root@server:~# ndctl create-namespace --reconfig=namespace1.0 --type=pmem 
--mode=sector -f
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof

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

[JulietDeltaGolf]

apport information

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

Title:
  NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840

Status in linux package in Ubuntu:
  Confirmed
Status in ndctl package in Ubuntu:
  New

Bug description:
  On ubuntu 18.04.1 :

  1°) With 4.15.0-43 two default namespaces in raw mode are visible
  while there shouldn't be any but no settings change could be applied.

  root@server:~# ndctl list -R
  [
{
  "dev":"region1",
  "size":103079215104,
  "available_size":0,
  "type":"pmem",
  "numa_node":1,
  "persistence_domain":"unknown"
},
{
  "dev":"region0",
  "size":103079215104,
  "available_size":0,
  "type":"pmem",
  "numa_node":0,
  "persistence_domain":"unknown"
}
  ]

  root@server:~# ndctl list
  [
{
  "dev":"namespace1.0",
  "mode":"raw",
  "size":103079215104,
  "sector_size":512,
  "blockdev":"pmem1",
  "numa_node":1
},
{
  "dev":"namespace0.0",
  "mode":"raw",
  "size":103079215104,
  "sector_size":512,
  "blockdev":"pmem0",
  "numa_node":0
}
  ]

  root@server:~# ndctl create-namespace --reconfig=namespace1.0 --type=pmem 
--mode=sector -f
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 

[Kernel-packages] [Bug 1811423] Re: linux-azure: 4.15.0-1037.39 -proposed tracker

[Brad Figg]

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

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: In Progress => 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 --
  kernel-stable-master-bug: 1811419
  phase: Packaging -- packaging in progress
  phase-changed: Monday, 14. January 2019 16:01 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- builds not complete

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

Title:
  linux-azure: 4.15.0-1037.39 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1811419
  phase: Packaging -- packaging in progress
  phase-changed: Monday, 14. January 2019 16:01 UTC
  reason:
prepare-package-meta: Pending -- package not yet uploaded
promote-to-proposed: Ongoing -- builds not complete

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811423/+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 1811415] Re: linux-azure: 4.18.0-1008.8 -proposed tracker

[Łukasz Zemczak]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

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

Title:
  linux-azure: 4.18.0-1008.8 -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:
  Fix Committed
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:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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: 1811406
  phase: Promote to Proposed -- release to Proposed in progress
  phase-changed: Tuesday, 15. January 2019 10:01 UTC
  reason:
promote-to-proposed: Ongoing -- packages copies requested

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811415/+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 1811415] Re: linux-azure: 4.18.0-1008.8 -proposed tracker

[Brad Figg]

** 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: 1811406
  phase: Promote to Proposed -- release to Proposed in progress
  phase-changed: Tuesday, 15. January 2019 10:01 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Ongoing -- packages copies requested

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

Title:
  linux-azure: 4.18.0-1008.8 -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:
  Fix Committed
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:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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: 1811406
  phase: Promote to Proposed -- release to Proposed in progress
  phase-changed: Tuesday, 15. January 2019 10:01 UTC
  reason:
promote-to-proposed: Ongoing -- packages copies requested

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811415/+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 1806766] Re: [Regression] crashkernel fails on HiSilicon D05

[Brad Figg]

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

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

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


** Tags added: verification-needed-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/1806766

Title:
  [Regression] crashkernel fails on HiSilicon D05

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

Bug description:
  [Impact]
  kdump support isn't usable on HiSilicon D05 systems. This previously worked 
in bionic.

  [Test Case]
  sudo apt install linux-crashdump
  echo 'GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT 
crashkernel=512M"' | \
    sudo tee /etc/default/grub.d/kdump-tools.cfg
  sudo update-grub
  sudo reboot
  echo 1 | sudo tee /proc/sys/kernel/sysrq
  echo c | sudo tee /proc/sysrq-trigger

  On failure:
  [2.362261] [ cut here ]
  [2.362263] [CRTC:29:crtc-0] vblank wait timed out
  [2.362294] WARNING: CPU: 0 PID: 143 at 
drivers/gpu/drm/drm_atomic_helper.c:1386 
drm_atomic_helper_wait_for_vblanks.part.9+0x280/0x290 [drm_kms_helper]
  [2.362295] Modules linked in: hibmc_drm(+) ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops drm hisi_sas_v2_hw(+) hisi_sas_main 
ehci_platform libsas scsi_transport_sas
  [2.362309] CPU: 0 PID: 143 Comm: systemd-udevd Tainted: G C   
 4.19.0-7-generic #8-Ubuntu
  [2.362310] Hardware name: Huawei TaiShan 2280 /BC11SPCD, BIOS 1.50 
06/01/2018
  [2.362312] pstate: 6045 (nZCv daif +PAN -UAO)
  [2.362324] pc : drm_atomic_helper_wait_for_vblanks.part.9+0x280/0x290 
[drm_kms_helper]
  [2.362335] lr : drm_atomic_helper_wait_for_vblanks.part.9+0x280/0x290 
[drm_kms_helper]
  [2.362336] sp : 0a2fb1f0
  [2.362337] x29: 0a2fb1f0 x28: 0001 
  [2.362339] x27:  x26: 0001 
  [2.362342] x25: 0038 x24: 8000208c5800 
  [2.362344] x23:  x22: 0001 
  [2.362346] x21: 80001eebb818 x20: 800025b18600 
  [2.362349] x19:  x18: 0001 
  [2.362351] x17:  x16:  
  [2.362353] x15:  x14: 09848708 
  [2.362355] x13: 0074 x12: 09a12000 
  [2.362357] x11: 0986d000 x10: 09a122f8 
  [2.362359] x9 : 0001 x8 : 09a15104 
  [2.362361] x7 :  x6 : 004ce5700bb7 
  [2.362363] x5 : 00ff x4 :  
  [2.362365] x3 :  x2 :  
  [2.362367] x1 : 0b15ae454042e100 x0 :  
  [2.362370] Call trace:
  [2.362381]  drm_atomic_helper_wait_for_vblanks.part.9+0x280/0x290 
[drm_kms_helper]
  [2.362392]  drm_atomic_helper_commit_tail+0x68/0x80 [drm_kms_helper]
  [2.362402]  commit_tail+0x7c/0x80 [drm_kms_helper]
  [2.362413]  drm_atomic_helper_commit+0xd8/0x150 [drm_kms_helper]
  [2.362440]  drm_atomic_commit+0x54/0x60 [drm]
  [2.362451]  restore_fbdev_mode_atomic+0x184/0x1f8 [drm_kms_helper]
  [2.362461]  restore_fbdev_mode+0x48/0x190 [drm_kms_helper]
  [2.362472]  drm_fb_helper_restore_fbdev_mode_unlocked+0x78/0xd8 
[drm_kms_helper]
  [2.362482]  drm_fb_helper_set_par+0x34/0x60 [drm_kms_helper]
  [2.362488]  fbcon_init+0x3ac/0x4f0
  [2.362491]  visual_init+0xb8/0x110
  [2.362492]  do_bind_con_driver+0x1ec/0x3a8
  [2.362494]  do_take_over_console+0x148/0x208
  [2.362495]  do_fbcon_takeover+0x70/0xd8
  [2.362497]  fbcon_event_notify+0x838/0x8a8
  [2.362501]  notifier_call_chain+0x5c/0x98
  [2.362502]  blocking_notifier_call_chain+0x64/0x88
  [2.362504]  fb_notifier_call_chain+0x30/0x40
  [2.362506]  register_framebuffer+0x22c/0x328
  [2.362516]  __drm_fb_helper_initial_config_and_unlock+0x210/0x408 
[drm_kms_helper]
  [2.362526]  drm_fb_helper_initial_config+0x4c/0x58 [drm_kms_helper]
  [2.362530]  hibmc_fbdev_init+0x88/0x190 [hibmc_drm]
  [2.362534]  hibmc_pci_probe+0x228/0x3c8 [hibmc_drm]
  [2.362537]  local_pci_probe+0x44/0xa8
  [2.362539]  pci_device_probe+0x194/0x1a8
  [2.362541]  really_probe+0x21c/0x3b8
  [2.362543]  driver_probe_device+0xe4/0x138
  [2.362544]  __driver_attach+0xe4/0x150

[Kernel-packages] [Bug 1806838] Re: Workaround CSS timeout on AMD SNPS 3.0 xHC

[Brad Figg]

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

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

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


** Tags added: verification-needed-cosmic

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

Title:
  Workaround CSS timeout on AMD SNPS 3.0 xHC

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

Bug description:
  [Impact]
  Raven Ridge xHC may fail to suspend, causes the USB stops working, and blocks 
the system entering system-wide suspend.

  [Fix]
  It's a hardware/firmware bug, workarounded by bailing out suspend function if 
it ever fails, and reset the xHC in next resume function.

  [Test]
  After applying the patch, the USB works, and the system can enter S3 
consecutively.

  [Regression Potential]
  Minimal. This workaround only applies to AMD Raven Ridge xHC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1806838/+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 1805085] Re: Fix and issue that LG I2C touchscreen stops working after reboot

[Brad Figg]

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

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

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


** Tags added: verification-needed-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/1805085

Title:
  Fix and issue that LG I2C touchscreen stops working after reboot

Status in HWE Next:
  New
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
Status in linux source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  LG I2C touchscreen stops working after reboot.

  [Fix]
  Disable runtime PM for the touchscreen, which doesn't work well with 
consecutive ON/SLEEP commands.

  [Test]
  The touchscreen works well after reboot, when runtime PM is disabled.

  [Regression Potential]
  None. This is a new device and the fix is limited to this particular device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1805085/+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 1781533] Re: SATA device is not going to DEVSLP

[Brad Figg]

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

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

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


** Tags added: verification-needed-cosmic

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

Title:
  SATA device is not going to DEVSLP

Status in HWE Next:
  Triaged
Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Committed
Status in linux-oem source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Any of the platforms we’ve been seeing SATA problems not going to deepest 
state leads to other devices not getting there during long idle or s2idle. And 
it also prevents the system from entering deeper PC state other than PC3.

  [Fix]
  Suggested from Intel and Dell to contains the following 4 commits,
  and all of 4 commits are in v4.19-rc1
  https://patchwork.kernel.org/patch/10502285/
  https://patchwork.kernel.org/patch/10502287/
  https://patchwork.kernel.org/patch/10535781/
  https://patchwork.kernel.org/patch/10535783/

  [Test]
  Verified the power consumption on some new platforms, it improves the SATA 
HDD power consumption around 0.5w during long idle.

  [Regression Potential]
  Low, the DEVSLP function is already validated when shipped with SLP_S0
  support.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1781533/+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 1805081] Re: Add pointstick support for Cirque Touchpad

[Brad Figg]

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

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

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


** Tags added: verification-needed-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/1805081

Title:
  Add pointstick support for Cirque Touchpad

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
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:
  Incomplete

Bug description:
  [Impact]
  Cirque Touchpad works but its pointstick doesn't work.

  [Test]
  With the fix the pointstick starts working.

  [Fix]
  Need to use MT_CLS_WIN_8_DUAL to let PTP driver use pointstick as a mouse.

  [Regression Potential]
  None. This is a new device and the fix is limited to this particular device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1805081/+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 1808318] Re: powerpc test in ubuntu_kernel_selftest failed on Cosmic P8/P9

[Brad Figg]

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

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

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


** Tags added: verification-needed-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/1808318

Title:
  powerpc test in ubuntu_kernel_selftest failed on Cosmic P8/P9

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  == Justification ==
  Commit b2d35fa5fc80 ("selftests: add headers_install to lib.mk")
  introduced a requirement that Makefiles more than one level below the
  selftests directory need to define top_srcdir, but it didn't update
  any of the powerpc Makefiles.

  This broke building all the powerpc selftests with eg:

    make[1]: Entering directory '/src/linux/tools/testing/selftests/powerpc'
    BUILD_TARGET=/src/linux/tools/testing/selftests/powerpc/alignment; mkdir -p 
$BUILD_TARGET; make OUTPUT=$BUILD_TARGET -k -C alignment all
    make[2]: Entering directory 
'/src/linux/tools/testing/selftests/powerpc/alignment'
    ../../lib.mk:20: ../../../../scripts/subarch.include: No such file or 
directory
    make[2]: *** No rule to make target '../../../../scripts/subarch.include'.
    make[2]: Failed to remake makefile '../../../../scripts/subarch.include'.
    Makefile:38: recipe for target 'alignment' failed

  == Fix ==
  7e0cf1c983b5 (selftests/powerpc: Fix Makefiles for headers_install change)
  It can be cherry-picked for Cosmic. And it's already landed in Disco.

  == Regression Potential ==
  None, this just fixes the broken build issue for the test. Nothing else will 
be affected.

  
  ===
  This test passed with 4.18.0-12 on the last cycle [1]
  But failed with the proposed 4.18.0-13 this time.

  Test failed to build because of a missing include file:
  50.   ../../lib.mk:20: ../../../../scripts/subarch.include: No such file or 
directory

  Tried to reproduce this cycle with 4.18.0-12 first and this can be
  reproduced as well.

  39.   make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc'
  40.   
BUILD_TARGET=/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment;
 mkdir -p $BUILD_TARGET; make OUTPUT=$BUILD_TARGET -k -C alignment all
  41.   make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment'
  42.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 copy_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/copy_unaligned
  43.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 copy_first_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c 
-o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/copy_first_unaligned
  44.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 paste_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/paste_unaligned
  45.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 paste_last_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c 
-o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/paste_last_unaligned
  46.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 alignment_handler.c 

[Kernel-packages] [Bug 1802248] Re: Disable LPM for Raydium Touchscreens

[Brad Figg]

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

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

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


** Tags added: verification-needed-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/1802248

Title:
  Disable LPM for Raydium Touchscreens

Status in HWE Next:
  New
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
Status in linux source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  Raydium touchscreens don't work on LPM capable platforms.

  [Test]
  Raydium touchscreens start to work with the patch.

  [Fix]
  Disable LPM for Raydium touchscreens.

  [Regression Potential]
  Low. Limits to specific Raydium touchscreens. Also, USB runtime PM
  (SeletiveSuspend) still works, so disabling LPM doesn't really increase
  power consumption.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1802248/+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 1805079] Re: click/pop noise in the headphone on several lenovo laptops

[Brad Figg]

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

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

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


** Tags added: verification-needed-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/1805079

Title:
  click/pop noise in the headphone on several lenovo laptops

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]
  Lenovo told us that some linux uers reported headphone noise on Lenovo's
  website. After investigating, we found those Lenovo laptop mdoels all
  have the codec of alc285, and we can reproduce the noise problem too.

  [Fix]
  Don't use the DAC of headphone, let headphone share the DAC with speaker,
  the noise disappears.

  [Test Case]
  After applying this patch, we tested on Lenovo P52, P72, X1 carbon and X1
  Yoda2, no noise anymore

  [Regression Potential]
  Low. This patch only apply to several lenovo machines, and after applying
  this patch, both speaker and headphone still work very well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805079/+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 1811406] Re: linux: 4.18.0-14.15 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => In Progress

** 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
  
  backports: bug 1811407 (linux-hwe), bug 1811408 (linux-hwe-edge), bug 1811409 
(linux-aws-edge), bug 1811410 (linux-azure-edge), bug 1811411 (linux-gcp-edge), 
bug 1811418 (linux-azure-edge)
  derivatives: bug 1811412 (linux-raspi2), bug 1811414 (linux-aws), bug 1811415 
(linux-azure), bug 1811416 (linux-gcp), bug 1811417 (linux-kvm)
  -- swm properties --
  boot-testing-requested: true
- phase: Promote to Proposed -- release to Proposed in progress
- phase-changed: Tuesday, 15. January 2019 08:32 UTC
+ bugs-spammed: true
+ phase: Testing -- verification-testing in progress
+ phase-changed: Tuesday, 15. January 2019 10:32 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages copies requested
+   automated-testing: Ongoing -- testing in progress
+   certification-testing: Ongoing -- testing in progress
+   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/1811406

Title:
  linux: 4.18.0-14.15 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
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 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

  backports: bug 1811407 (linux-hwe), bug 1811408 (linux-hwe-edge), bug 1811409 
(linux-aws-edge), bug 1811410 (linux-azure-edge), bug 1811411 (linux-gcp-edge), 
bug 1811418 (linux-azure-edge)
  derivatives: bug 1811412 (linux-raspi2), bug 1811414 (linux-aws), bug 1811415 
(linux-azure), bug 1811416 (linux-gcp), bug 1811417 (linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing -- verification-testing in progress
  phase-changed: Tuesday, 15. January 2019 10:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
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/1811406/+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 1804588] Re: Power consumption during s2idle is higher than long idle (Intel SSDPEKKF)

[Brad Figg]

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

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

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


** Tags added: verification-needed-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/1804588

Title:
  Power consumption during s2idle is higher than long idle (Intel
  SSDPEKKF)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  New
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:
  In Progress

Bug description:
  [Impact]
  On new systems that facilitate s2idle, we observed the power consumption 
raises higher than long idle does during s2idle with Intel NVMe SSDPEKKF.

  Short idle: 6
  Long idle: 2
  S2I: 4.8

  [Fix]
  Windows doesn't put nvme to D3 in modern standby, and uses its own APST 
feature to do the power management. To leverage its APST feature during s2idle, 
we can't disable nvme device while suspending, too.
  So, here is what we did on the driver, 1. prevent nvme from entering D3, 2. 
prevent nvme from being disabled when suspending.

  [Test]
  Verified on the new Intel NVMe, it fixes the power consumption issue with no 
regression. And the power consumption decreases to 2.8W during s2idle.

  [Regression Potential]
  Low, the patches only applied to specific nvme module, and from our test, the 
system is still stable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1804588/+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 1807686] Re: efi-lockdown patch causes -EPERM for some debugfs files even though CONFIG_LOCK_DOWN_KERNEL is not set

[Brad Figg]

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

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

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


** Tags added: verification-needed-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/1807686

Title:
  efi-lockdown patch causes -EPERM for some debugfs files even though
  CONFIG_LOCK_DOWN_KERNEL is not set

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  == Comment: #0 - Dominik Klein  - 2018-12-10 
03:58:10 ==
  There seems to be a bug in the efi-lockdown patch as applied on top of 
vanilla for Cosmic kernels:
  
http://kernel.ubuntu.com/git/ubuntu/ubuntu-cosmic.git/commit/fs/debugfs/file.c?id=a1ba65da9ceae481c154bfd1a2c1550e4566d986

  Also seems to be present for Disco as of today:
  
http://kernel.ubuntu.com/git/ubuntu/ubuntu-disco.git/commit/fs/debugfs/file.c?id=a1ba65da9ceae481c154bfd1a2c1550e4566d986

  The problem is that part of the patch modifies kernel behavior
  independently of CONFIG_LOCK_DOWN_KERNEL being set or not causing
  issues on two debugfs files on s390x.

  Vasily Gorbik has already analyzed the problem and has posted a proposed fix 
here:
  https://lkml.org/lkml/2018/11/21/634
  https://lkml.org/lkml/2018/11/21/635

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1807686/+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 1806850] Re: Fix Terminus USB hub that may breaks connected USB devices after S3

[Brad Figg]

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

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

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


** Tags added: verification-needed-cosmic

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

Title:
  Fix Terminus USB hub that may breaks connected USB devices after S3

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

Bug description:
  [Impact]
  USB devices connected to Terminus USB hub stop working after S3.

  [Fix]
  The Terminus hub seems to have a rather slow reset command, so we need to 
wait for extra time before doing any further action.

  [Test]
  After applying the fix, USB devices connected to the HUB no longer stop 
functioning after S3.

  [Regression Potential]
  Low. Although the fix affects all devices connect to the HUB, it has no 
functional change other than imposes longer delay time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1806850/+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 1807334] Re: Add support for ALC3277 codec on new Dell edge gateways

[Brad Figg]

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

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

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


** Tags added: verification-needed-cosmic

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

Title:
  Add support for ALC3277 codec on new Dell edge gateways

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  Fix Committed
Status in linux-oem source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Invalid

Bug description:
  
  [Impact]
  The Dell Edge IoT Gateway is based on kabylake, and the audio codec is alc3277
  which is connected to kabylake PCH via SSP0, there is no ASoC machine driver
  for this board, so the audio (line-out and line-in) can't work.

  
  [Fix]
  write a ASoC machine driver for this board, and this driver is based on
  the existing driver kbl_rt5663_max98927.c

  
  [Test Case]
  play sound via line-out jack, record sound via line-in jack, all work well.

  
  [Regression Potential]
  Very low, this machine driver is specific to Dell Edge IoT Gateway. Only
  the machine with the HID:10EC3277 in the BIOS can use this driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1807334/+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 1805775] Re: PC SN720 NVMe WDC 256GB consumes more power in S2Idle than during long idle

[Brad Figg]

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

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

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


** Tags added: verification-needed-cosmic

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

Title:
  PC SN720 NVMe WDC 256GB consumes more power in S2Idle than during long
  idle

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

Bug description:
  [Impact]
  On new systems that facilitate s2idle, we observed the power consumption 
raises higher than long idle does during s2idle with Western Digital PC SN720 
NVMe SSD SDAPNTW-256G.

  Short idle: 5.3
  Long idle: 3.0
  S2I: 5.07

  [Fix]
  Windows doesn't put nvme to D3 in modern standby, and uses its own APST 
feature to do the power management. To leverage its APST feature during s2idle, 
we can't disable nvme device while suspending, too.
  So, here is what we did on the driver, 1. prevent nvme from entering D3, 2. 
prevent nvme from being disabled when suspending.

  [Test]
  Verified on the WD NVMe, it fixes the power consumption issue with no 
regression. And the power consumption decreases to 1.66W during s2idle.

  [Regression Potential]
  Low, the patches only applied to specific nvme module, and from our test, the 
system is still stable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1805775/+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 1794387] Re: Colour banding in HP Pavilion 15-n233sl integrated display

[Brad Figg]

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

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

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


** Tags added: verification-needed-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/1794387

Title:
  Colour banding in HP Pavilion 15-n233sl integrated display

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

Bug description:
  Colour bandind is visible everywhere in the system, and it appeared
  after I had my integrated monitor replaced. I believe it's not a
  hardware problem, since booting with 'nomodeset' works as expected.

  There were already two similar bugs,
  https://bugs.launchpad.net/bugs/1749420 and
  https://bugs.launchpad.net/bugs/1788308, but the fixes provided for
  those bugs did not work for my specific monitor.

  I'm running Ubuntu 18.04 with kernel linux-image-4.15.0-34-generic,
  installing linux-image-4.18.8 with UKUU didn't help.

  I attached the results of running
  sudo get-edid | parse-edid in a file named edid.txt
  sudo get-edid | edid-decode in a file named edid-decoded.txt
  cat /proc/version_signature in version.log
  sudo lspci -vnvn in lspci-vnvn.log.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matt   1796 F pulseaudio
   /dev/snd/controlC1:  matt   1796 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: KDE neon 18.04
  InstallationDate: Installed on 2018-09-27 (0 days ago)
  InstallationMedia: neon devunstable "Bionic" - Build amd64 LIVE Binary 
20180924-13:08
  Lsusb:
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 002: ID 04f2:b40e Chicony Electronics Co., Ltd HP Truevision 
HD camera
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=c3f61207-d13e-474b-a499-98030ddef8e1 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-34-generic N/A
   linux-backports-modules-4.15.0-34-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-34-generic x86_64
  UnreportableReason: Questa segnalazione riguarda un pacchetto che non è 
installato.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  _MarkForUpload: False
  dmi.bios.date: 03/13/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.71
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2166
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 29.42
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.71:bd03/13/2017:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr098B1140410620180:rvnHewlett-Packard:rn2166:rvr29.42:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.version: 098B1140410620180
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794387/+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 1806335] Re: Enable new Realtek card reader

[Brad Figg]

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

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

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


** Tags added: verification-needed-cosmic

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

Title:
  Enable new Realtek card reader

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

Bug description:
  [Impact]
  USB Storage based Realtek card reader doesn't work, because the usb-storage 
module tries to use it in UAS mode instead of using "ums-realtek".

  [Fix]
  Add new IDs to ums-realtek driver.
  In addition to that, we add a new module knob, "enable_mmc=", to 
enable/disable MMC, as vendors may not pay MMC royalties. "enable_mmc" defaults 
to 1.

  [Test]
  After applying the patch, the card reader works, and verified "enable_mmc=" 
can enable/disable MMC support.

  [Regression Potential]
  Minimal. This SRU enables two specific card readers that don't work as UAS, 
the new module knob only introduces new behavior when enable_mmc=0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1806335/+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 1805607] Re: Power leakage at S5 with Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter

[Brad Figg]

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

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

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


** Tags added: verification-needed-cosmic

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

Title:
  Power leakage at S5 with Qualcomm Atheros QCA9377 802.11ac Wireless
  Network Adapter

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

Bug description:
  [Impact]
  It drains power more than 0.5 Watt after power off(S5) the machine with 
QCA9377 wifi card. The power consumption should be lower than 0.5 Watt, or it 
won't pass E-star 7.

  [Fix]
  Qualcomm provides this fix, and the power consumption becomes 0.23 Watt at 
S5. This fix doesn't submit to upstream yet, Qualcomm is still working on it.

  [Test]
  Verified on Dell machines, it works.

  [Regression Potential]
  Low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1805607/+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 1807333] Re: Add support for 0cf3:535b QCA_ROME device

[Brad Figg]

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

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

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


** Tags added: verification-needed-cosmic

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

Title:
  Add support for 0cf3:535b QCA_ROME device

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

Bug description:
  == Impact ==
  0cf3:535b is not full functioning with the current in-kernel driver. For 
example, it doesn't work with a BLE keyboard.

  == Fix ==
  It is a QCA_ROME device. Should mark it so in the device ID table to make it 
work properly.

  == Test Case ==
  Try to use this module with a BLE keyboard. It is expected to work without 
problem, but instead it can't even find the keyboard.

  == Risk of Regression ==
  Very low. This is already in upstream, and proved working in QA lab.

  
  Device info:

  T:  Bus=01 Lev=01 Prnt=01 Port=03 Cnt=02 Dev#=  3 Spd=12   MxCh= 0
  D:  Ver= 2.01 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=0cf3 ProdID=535b Rev= 0.01
  C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
  I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  E:  Ad=81(I) Atr=03(Int.) MxPS=  16 Ivl=1ms
  E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
  E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
  I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  E:  Ad=83(I) Atr=01(Isoc) MxPS=   0 Ivl=1ms
  E:  Ad=03(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1807333/+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 1798583] Re: the new Steam Controller driver breaks it on Steam

[Brad Figg]

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

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

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


** Tags added: verification-needed-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/1798583

Title:
  the new Steam Controller driver breaks it on Steam

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  New steam-hid driver breaks Unity games.

  [Fix]
  Quote from the commit message:
  "With this commit, when a HID client starts, the input device is removed;
  when the HID client ends the input device is recreated."

  [Test]
  A guy from Valve comfirms the backport works.

  [Regression Potential]
  Low. This fix is specific to hid-steam, which is a new driver introduced
  in v4.18.

  ===Original Bug Report===
  The new hid_steam driver in kernel 4.18 breaks the use of it within Steam.

  Games either:
  - Crash
  - Don't detect it at all
  - Only pick it up as player 2

  To get it working as normal, it needs blacklisting currently.

  See here: https://www.gamingonlinux.com/articles/the-steam-controller-
  on-ubuntu-1810-and-other-distributions-using-linux-kernel-418-needs-
  quick-a-fix.12775

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  liam   2492 F pulseaudio
   /dev/snd/controlC0:  liam   2492 F pulseaudio
   /dev/snd/controlC1:  liam   2492 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 18 12:49:44 2018
  InstallationDate: Installed on 2017-10-18 (364 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
  IwConfig:
   lono wireless extensions.

   enp5s0no wireless extensions.

   eno1  no wireless extensions.
  MachineType: ASUS All Series
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2a8676f3-0045-4e66-9cd1-186ffc6a8c2a ro quiet splash vt.handoff=1
  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
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (0 days ago)
  dmi.bios.date: 08/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1901
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH X99
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: PCS
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1901:bd08/10/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1798583/+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 1811200] Re: Add Cavium ThunderX2 SoC UNCORE PMU driver

[Brad Figg]

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

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

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


** Tags added: verification-needed-cosmic

** Tags added: verification-needed-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/1811200

Title:
  Add Cavium ThunderX2 SoC UNCORE PMU driver

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
Status in linux source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  No driver for PMU of L3 cache controller (L3C) and the DDR4 Memory Controller 
(DMC) for Cavium ThunderX2 SoC

  [Test Case]
  sudo perf stat -a -e \
  > uncore_dmc_0/cnt_cycles/,\
  > uncore_dmc_0/data_transfers/,\
  > uncore_dmc_0/read_txns/,\
  > uncore_dmc_0/write_txns/ sleep 1

  sudo perf stat -a -e \
  > uncore_l3c_0/read_request/,\
  > uncore_l3c_0/read_hit/,\
  > uncore_l3c_0/inv_request/,\
  > uncore_l3c_0/inv_hit/ sleep 1

  sudo perf stat -a -e uncore_dmc_0/cnt_cycles/ sleep 1

  [Fix]
  Backport patches
  82975c46da  perf: Export perf_event_update_userpage (only for bionic)
  d6310a3f33  Documentation: perf: Add documentation for ThunderX2 PMU uncore 
driver
  69c32972d5  drivers/perf: Add Cavium ThunderX2 SoC UNCORE PMU driver
  and enable CONFIG_THUNDERX2_PMU=m

  [Regression Risk]
  This driver only loaded when CAV901C in ACPI table, lowest risk for other 
platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811200/+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 1811094] Re: iptables connlimit allows more connections than the limit when using multiple CPUs

[Brad Figg]

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

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

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

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

Title:
  iptables connlimit allows more connections than the limit when using
  multiple CPUs

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

Bug description:
  [Impact]

   * The iptables connection count/limit rules can be breached
     with multithreaded network driver/server/client (common)
     due to a race in the conncount/connlimit code.

   * For example:

     # iptables -A INPUT -p tcp -m tcp --syn --dport  \
   -m connlimit --connlimit-above 2000 --connlimit-mask 0 \
   -j DROP

   * The fix is a backport from an upstream commit that resolves
     the problem (plus dependencies for a cleaner backport) that
     address the race condition:

     commit b36e4523d4d5 ("netfilter: nf_conncount: fix garbage
     collection confirm race").

  [Test Case]

   * Server-side: (relevant kernel side)
     (limit TCP port  to only 2000 connections)

     # iptables -A INPUT -p tcp -m tcp --syn --dport  \
   -m connlimit --connlimit-above 2000 --connlimit-mask 0 \
   -j DROP

     # ulimit -SHn 65000   # increase number of open files
     # ruby server.rb  # multi-threaded server

   * Client-side:

     # ulimit -SHn 65000
     # ruby client.rb<# threads>
     

   * Results with Original kernel:
     (client achieves target of 6000 connections > limit of 2000 connections)

     # ruby client.rb 10.230.56.100  6000 3
     1
     2
     3
     <...>
     6000
     Target reached. Thread finishing
     6001
     Target reached. Thread finishing
     6002
     Target reached. Thread finishing
     Threads done. 6002 connections
     press enter to exit

   * Results with Modified kernel:
     (client is limited to 2000 connections, and times out afterward)

     # ruby client.rb 10.230.56.100  6000 3
     1
     2
     3
     <...>
     2000
     <... blocks for a few minutes ...>
     failed to create connection: Connection timed out - connect(2) for 
"10.230.56.100" port 
     failed to create connection: Connection timed out - connect(2) for 
"10.230.56.100" port 
     failed to create connection: Connection timed out - connect(2) for 
"10.230.56.100" port 
     Threads done. 2000 connections
     press enter to exit

   * Test cases possibly available upon request,
     depending on original author's permission.

  [Regression Potential]

   * The patchset has been reviewed by a netfilter maintainer [1] in
     stable mailing list, and was considered OK for 4.14, and that's
     essentially the same backport for 4.15 and 4.4.

   * The changes are limited to netfilter connlimit/conncount (names
     change between older/newer kernel versions).

  [Other Info]

   * The backport for 4.14 [2] is applied as of 4.14.92.

  [1] https://www.spinics.net/lists/stable/msg276883.html
  [2] https://www.spinics.net/lists/stable/msg276910.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811094/+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 1811055] Re: Support new Realtek ethernet chips

[Brad Figg]

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

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

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

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

Title:
  Support new Realtek ethernet chips

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
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:
  Incomplete

Bug description:
  [Impact]
  New Realtek ethernet chips don't work.

  [Fix]
  Add new IDs to r8169.ko.

  [Test]
  The r8169 is loaded for the Realtek ethernet chip.
  It works, and I haven't seen any issues so far.
   
  [Regression Potential]
  Low. New IDs to existing driver, no functional change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1811055/+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 1810891] Re: audio output has constant noise on a Dell machine

[Brad Figg]

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

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

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

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

Title:
  audio output has constant noise on a Dell machine

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
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:
  Invalid

Bug description:

  [Impact]
  the audio output (headpohne, lineout and internal speaker) has constant
  noise when playing sound.

  [Fix]
  Set the pin configuration and some secret coeff registers, the noise
  disappears. This patch is written by Realtek engineer and is upstreamd
  already.

  
  [Test Case]
  play sound via internal speaker, lineout and headphone, no noise anymore.

  
  [Regression Potential]
  Very low, this patch is upstreamd for a while, no regression is reported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1810891/+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 1810781] Re: mpt3sas - driver using the wrong register to update a queue index in FW

[Brad Figg]

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

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

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

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

Title:
  mpt3sas - driver using the wrong register to update a queue index in
  FW

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
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 Released

Bug description:
  [Impact]

  * Adapter resets periodically during high-load activity.

  * I/O stalls until reset/reinit is complete (latency) and I/O performance
  degrades across cluster (e.g., low throughput from data spread over nodes).

  * The mpt3sas driver relies in a FW queue (Reply Post Descriptor
  Queue) in the I/O completion path; there's a MMIO register that driver
  uses to flag an empty entry in such queue, called Reply Post Host
  Index. This value is updated during the driver interrupt routine [in
  _base_interrupt() function].

  * Happens that there are 2 registers representing the Reply Post Host
  Index according to the type of the adapter. They are differentiated in
  the driver through the "ioc->combined_reply_queue" check. By the MPI
  specification (vendor spec), driver should use this combined reply
  queue according to the number of maximum MSI-X vectors that the
  adapter exposes and the spec version (SAS 3.0 vs SAS 3.5).

  * Currently, this is wrong checked for a class of adapters, which was fixed 
in the upstream
  kernel commit 2b48be65685a [0]. Without this commit, we can observe 
spontaneous resets in the
  driver due to queue overflow (FW is not aware that there are free entries in 
the Reply Post Descriptor Queue). The dmesg log will show the following output 
in case of this error:

    mpt3sas_cm0: fault_state(0x2100)!
    mpt3sas_cm0: sending diag reset !!
    mpt3sas_cm0: diag reset: SUCCESS
  [followed by a lot of driver messages as result of the reset procedure]

  * During these resets, I/O is stalled so it may affect performance.

  [Test Case]

  * It's not trivial to test the problem, but given a machine with an
  affected device, an I/O benchmark like FIO could be used to exercise
  the I/O path in a heavy way and trigger the issue.

  * We have reports that the adapter "LSI Logic / Symbios Logic Device
  [1000:00ac]" is affected by the issue.  And this commit resolved the
  problem.

  [Regression Potential]

  * This is a long-term issue from the mpt3sas driver, affecting only a
  class of adapters of this vendor. Since it's a clearly bug, the fix is
  necessary. The potential of regressions is unknown, but likely low -
  it changes the register used for the index updates given some set of
  characteristics of the adapter (according to the spec.), which
  restricts even more the scope of this patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810781/+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 1811055] Re: Support new Realtek ethernet chips

[Brad Figg]

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

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

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


** Tags added: verification-needed-cosmic

** Tags added: verification-needed-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/1811055

Title:
  Support new Realtek ethernet chips

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
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:
  Incomplete

Bug description:
  [Impact]
  New Realtek ethernet chips don't work.

  [Fix]
  Add new IDs to r8169.ko.

  [Test]
  The r8169 is loaded for the Realtek ethernet chip.
  It works, and I haven't seen any issues so far.
   
  [Regression Potential]
  Low. New IDs to existing driver, no functional change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1811055/+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 1811416] Re: linux-gcp: 4.18.0-1006.7 -proposed tracker

[Stefan Bader]

** Summary changed:

- linux-gcp:  -proposed tracker
+ linux-gcp: 4.18.0-1006.7 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader 
(smb)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader 
(smb)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader 
(smb)

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

Title:
  linux-gcp: 4.18.0-1006.7 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1811406
  phase: Packaging -- ready to package
  phase-changed: Monday, 14. January 2019 10:01 UTC
  reason:
prepare-package: Pending -- version not specified

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811416/+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 1810998] Re: CPU hard lockup with rigorous writes to NVMe drive

[Brad Figg]

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

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

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

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

Title:
  CPU hard lockup with rigorous writes to NVMe drive

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * Users may experience cpu hard lockups when performing
     rigorous writes to NVMe drives.

   * The fix addresses an scheduling issue in the original
     implementation of wbt/writeback throttling

   * The fix is commit 2887e41b910b ("blk-wbt: Avoid lock
     contention and thundering herd issue in wbt_wait"),
     plus its fix commit 38cfb5a45ee0 ("blk-wbt: improve
     waking of tasks").

   * Plus a few dependency commits for each fix.

   * Backports are trivial: mainly replace rq_wait_inc_below()
     with the equivalent atomic_inc_below(), and maintain the
     __wbt_done() signature, both due to the lack of commit
     a79050434b45 ("blk-rq-qos: refactor out common elements
     of blk-wbt"), that changes lots of other/unrelated code.

  [Test Case]

   * This command has been reported to reproduce the problem:

     $ sudo iozone -R -s 5G -r 1m -S 2048 -i 0 -G -c -o -l 128 -u 128 -t
  128

   * It generates stack traces as below in the original kernel,
     and does not generate them in the modified/patched kernel.

   * The user/reporter verified the test kernel with these patches
     resolved the problem.

   * The developer verified in 2 systems (4-core and 24-core but
     no NVMe) for regressions, and no error messages were logged
     to dmesg.

  [Regression Potential]

   * The regression potential is contained within writeback
     throttling mechanism (block/blk-wbt.*).

   * The commits have been verified for fixes in later commits in
     linux-next as of 2019-01-08 and all known fix commits are in.

  [Other Info]

   * The problem has been introduced with the blk-wbt mechanism,
     in v4.10-rc1, and the fix commits in v4.19-rc1 and -rc2,
     so only Bionic and Cosmic needs this.

  [Stack Traces]

  [ 393.628647] NMI watchdog: Watchdog detected hard LOCKUP on cpu 30
  ...
  [ 393.628704] CPU: 30 PID: 0 Comm: swapper/30 Tainted: P OE 4.15.0-20-generic 
#21-Ubuntu
  ...
  [ 393.628720] Call Trace:
  [ 393.628721] 
  [ 393.628724] enqueue_task_fair+0x6c/0x7f0
  [ 393.628726] ? __update_load_avg_blocked_se.isra.37+0xd1/0x150
  [ 393.628728] ? __update_load_avg_blocked_se.isra.37+0xd1/0x150
  [ 393.628731] activate_task+0x57/0xc0
  [ 393.628735] ? sched_clock+0x9/0x10
  [ 393.628736] ? sched_clock+0x9/0x10
  [ 393.628738] ttwu_do_activate+0x49/0x90
  [ 393.628739] try_to_wake_up+0x1df/0x490
  [ 393.628741] default_wake_function+0x12/0x20
  [ 393.628743] autoremove_wake_function+0x12/0x40
  [ 393.628744] __wake_up_common+0x73/0x130
  [ 393.628745] __wake_up_common_lock+0x80/0xc0
  [ 393.628746] __wake_up+0x13/0x20
  [ 393.628749] __wbt_done.part.21+0xa4/0xb0
  [ 393.628749] wbt_done+0x72/0xa0
  [ 393.628753] blk_mq_free_request+0xca/0x1a0
  [ 393.628755] blk_mq_end_request+0x48/0x90
  [ 393.628760] nvme_complete_rq+0x23/0x120 [nvme_core]
  [ 393.628763] nvme_pci_complete_rq+0x7a/0x130 [nvme]
  [ 393.628764] __blk_mq_complete_request+0xd2/0x140
  [ 393.628766] blk_mq_complete_request+0x18/0x20
  [ 393.628767] nvme_process_cq+0xe1/0x1b0 [nvme]
  [ 393.628768] nvme_irq+0x23/0x50 [nvme]
  [ 393.628772] __handle_irq_event_percpu+0x44/0x1a0
  [ 393.628773] handle_irq_event_percpu+0x32/0x80
  [ 393.628774] handle_irq_event+0x3b/0x60
  [ 393.628778] handle_edge_irq+0x7c/0x190
  [ 393.628779] handle_irq+0x20/0x30
  [ 393.628783] do_IRQ+0x46/0xd0
  [ 393.628784] common_interrupt+0x84/0x84
  [ 393.628785] 
  ...
  [ 393.628794] ? cpuidle_enter_state+0x97/0x2f0
  [ 393.628796] cpuidle_enter+0x17/0x20
  [ 393.628797] call_cpuidle+0x23/0x40
  [ 393.628798] do_idle+0x18c/0x1f0
  [ 393.628799] cpu_startup_entry+0x73/0x80
  [ 393.628802] start_secondary+0x1a6/0x200
  [ 393.628804] secondary_startup_64+0xa5/0xb0
  [ 393.628805] Code: ...

  [ 405.981597] nvme nvme1: I/O 393 QID 6 timeout, completion polled

  [ 435.597209] INFO: rcu_sched detected stalls on CPUs/tasks:
  [ 435.602858] 30-...0: (1 GPs behind) idle=e26/1/0 softirq=6834/6834 fqs=4485
  [ 435.610203] (detected by 8, t=15005 jiffies,

[Kernel-packages] [Bug 1811335] Re: ELAN900C:00 04F3:2844 touchscreen doesn't work

[Brad Figg]

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

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

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


** Tags added: verification-needed-cosmic

** Tags added: verification-needed-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/1811335

Title:
  ELAN900C:00 04F3:2844 touchscreen doesn't work

Status in HWE Next:
  New
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]
  [ELAN900C:00 04F3:2844] doesn't work

  [Fix]
  It works under kernel v4.19, so after bisect the kernel and got the first bad 
commit
     e50d95e2ad12 pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H 
variant

  [Test]
  Verified on the DELL machine, the touchscreen works well.

  [Regression Potential]
  Low, the 2 commits are all
 Fixes: a663ccf0fea1 ("pinctrl: intel: Add Intel Cannon Lake PCH-H pin 
controller support")
  Should be safe to be included.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1811335/+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 1811337] Re: To reduce the Realtek USB cardreader power consumption

[Brad Figg]

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

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

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

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

Title:
  To reduce the Realtek USB cardreader power consumption

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

Bug description:
  [Impact]
  Realtek USB cardreader consumes more than 1 Watt during long idle if it's not 
suspended. And it's runtime PM functions are available after v4.20.

  [Fix]
  To avoid conflicts, have to backport some patches for mmc core.

  [Test]
  Note: Inside () are the previous value (non-patch)
  Sort idle: 7.76W (7.88)
  Long idle: 4.658W (5.79)
  S3: 0.5W (0.5)
  S5: 0.20W (0.208)

  [Regression Potential]
  Low, most commits are for rtsx_usb_{sdmmc,ms} and are all small changes.

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

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

[Kernel-packages] [Bug 1810702] Re: HP mobile workstations with hybrid graphics support, can not directly output to external monitors by dGPU

[Brad Figg]

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

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

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


** Tags added: verification-needed-bionic

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

Title:
  HP mobile workstations with hybrid graphics support, can not directly
  output to external monitors by dGPU

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

Bug description:
  For HP Inc. mobile workstation with hybrid graphics support, dGPU can 
directly output to external monitors; however, Nvidia and AMD's Linux drivers 
aren't able to support this feature.
  
  The OEM _OSI string "Linux-HPI-Hybrid-Graphics" is used by BIOS to implement 
dGPU direct output to external monitors.

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

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

[Kernel-packages] [Bug 1811094] Re: iptables connlimit allows more connections than the limit when using multiple CPUs

[Brad Figg]

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

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

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


** Tags added: verification-needed-cosmic

** Tags added: verification-needed-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/1811094

Title:
  iptables connlimit allows more connections than the limit when using
  multiple CPUs

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

Bug description:
  [Impact]

   * The iptables connection count/limit rules can be breached
     with multithreaded network driver/server/client (common)
     due to a race in the conncount/connlimit code.

   * For example:

     # iptables -A INPUT -p tcp -m tcp --syn --dport  \
   -m connlimit --connlimit-above 2000 --connlimit-mask 0 \
   -j DROP

   * The fix is a backport from an upstream commit that resolves
     the problem (plus dependencies for a cleaner backport) that
     address the race condition:

     commit b36e4523d4d5 ("netfilter: nf_conncount: fix garbage
     collection confirm race").

  [Test Case]

   * Server-side: (relevant kernel side)
     (limit TCP port  to only 2000 connections)

     # iptables -A INPUT -p tcp -m tcp --syn --dport  \
   -m connlimit --connlimit-above 2000 --connlimit-mask 0 \
   -j DROP

     # ulimit -SHn 65000   # increase number of open files
     # ruby server.rb  # multi-threaded server

   * Client-side:

     # ulimit -SHn 65000
     # ruby client.rb<# threads>
     

   * Results with Original kernel:
     (client achieves target of 6000 connections > limit of 2000 connections)

     # ruby client.rb 10.230.56.100  6000 3
     1
     2
     3
     <...>
     6000
     Target reached. Thread finishing
     6001
     Target reached. Thread finishing
     6002
     Target reached. Thread finishing
     Threads done. 6002 connections
     press enter to exit

   * Results with Modified kernel:
     (client is limited to 2000 connections, and times out afterward)

     # ruby client.rb 10.230.56.100  6000 3
     1
     2
     3
     <...>
     2000
     <... blocks for a few minutes ...>
     failed to create connection: Connection timed out - connect(2) for 
"10.230.56.100" port 
     failed to create connection: Connection timed out - connect(2) for 
"10.230.56.100" port 
     failed to create connection: Connection timed out - connect(2) for 
"10.230.56.100" port 
     Threads done. 2000 connections
     press enter to exit

   * Test cases possibly available upon request,
     depending on original author's permission.

  [Regression Potential]

   * The patchset has been reviewed by a netfilter maintainer [1] in
     stable mailing list, and was considered OK for 4.14, and that's
     essentially the same backport for 4.15 and 4.4.

   * The changes are limited to netfilter connlimit/conncount (names
     change between older/newer kernel versions).

  [Other Info]

   * The backport for 4.14 [2] is applied as of 4.14.92.

  [1] https://www.spinics.net/lists/stable/msg276883.html
  [2] https://www.spinics.net/lists/stable/msg276910.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811094/+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 1810891] Re: audio output has constant noise on a Dell machine

[Brad Figg]

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

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

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


** Tags added: verification-needed-cosmic

** Tags added: verification-needed-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/1810891

Title:
  audio output has constant noise on a Dell machine

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
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:
  Invalid

Bug description:

  [Impact]
  the audio output (headpohne, lineout and internal speaker) has constant
  noise when playing sound.

  [Fix]
  Set the pin configuration and some secret coeff registers, the noise
  disappears. This patch is written by Realtek engineer and is upstreamd
  already.

  
  [Test Case]
  play sound via internal speaker, lineout and headphone, no noise anymore.

  
  [Regression Potential]
  Very low, this patch is upstreamd for a while, no regression is reported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1810891/+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 1810892] Re: lineout jack can't work on a Dell machine

[Brad Figg]

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

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

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


** Tags added: verification-needed-cosmic

** Tags added: verification-needed-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/1810892

Title:
  lineout jack can't work on a Dell machine

Status in HWE Next:
  New
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
Status in linux source package in Disco:
  Fix Committed

Bug description:
  
  [Impact]
  The rear lineout jack can't work. If users plug a headphone or audio
  cable into the lineout jack, nothing happens, the audio still output
  from internal speaker. The expected behaviour is the lineout is
  active and the sound is routed to lineout jack from internal speaker.

  [Fix]
  apply the ALC274_FIXUP_DELL_AIO_LINEOUT_VERB, this will set the
  lineout pin to be a correct configuration value.

  
  [Test Case]
  plug headphone into the rear lineout jack, system can detect lineout
  jack is plugged and the audio output is routed to lineout jack from
  internal speaker.

  
  [Regression Potential]
  Very low, this patch is specific to one Dell machine model.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1810892/+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 1811335] Re: ELAN900C:00 04F3:2844 touchscreen doesn't work

[Brad Figg]

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

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

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

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

Title:
  ELAN900C:00 04F3:2844 touchscreen doesn't work

Status in HWE Next:
  New
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]
  [ELAN900C:00 04F3:2844] doesn't work

  [Fix]
  It works under kernel v4.19, so after bisect the kernel and got the first bad 
commit
     e50d95e2ad12 pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H 
variant

  [Test]
  Verified on the DELL machine, the touchscreen works well.

  [Regression Potential]
  Low, the 2 commits are all
 Fixes: a663ccf0fea1 ("pinctrl: intel: Add Intel Cannon Lake PCH-H pin 
controller support")
  Should be safe to be included.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1811335/+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 1811200] Re: Add Cavium ThunderX2 SoC UNCORE PMU driver

[Brad Figg]

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

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

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

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

Title:
  Add Cavium ThunderX2 SoC UNCORE PMU driver

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
Status in linux source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  No driver for PMU of L3 cache controller (L3C) and the DDR4 Memory Controller 
(DMC) for Cavium ThunderX2 SoC

  [Test Case]
  sudo perf stat -a -e \
  > uncore_dmc_0/cnt_cycles/,\
  > uncore_dmc_0/data_transfers/,\
  > uncore_dmc_0/read_txns/,\
  > uncore_dmc_0/write_txns/ sleep 1

  sudo perf stat -a -e \
  > uncore_l3c_0/read_request/,\
  > uncore_l3c_0/read_hit/,\
  > uncore_l3c_0/inv_request/,\
  > uncore_l3c_0/inv_hit/ sleep 1

  sudo perf stat -a -e uncore_dmc_0/cnt_cycles/ sleep 1

  [Fix]
  Backport patches
  82975c46da  perf: Export perf_event_update_userpage (only for bionic)
  d6310a3f33  Documentation: perf: Add documentation for ThunderX2 PMU uncore 
driver
  69c32972d5  drivers/perf: Add Cavium ThunderX2 SoC UNCORE PMU driver
  and enable CONFIG_THUNDERX2_PMU=m

  [Regression Risk]
  This driver only loaded when CAV901C in ACPI table, lowest risk for other 
platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811200/+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 1810781] Re: mpt3sas - driver using the wrong register to update a queue index in FW

[Brad Figg]

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

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

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


** Tags added: verification-needed-cosmic

** Tags added: verification-needed-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/1810781

Title:
  mpt3sas - driver using the wrong register to update a queue index in
  FW

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
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 Released

Bug description:
  [Impact]

  * Adapter resets periodically during high-load activity.

  * I/O stalls until reset/reinit is complete (latency) and I/O performance
  degrades across cluster (e.g., low throughput from data spread over nodes).

  * The mpt3sas driver relies in a FW queue (Reply Post Descriptor
  Queue) in the I/O completion path; there's a MMIO register that driver
  uses to flag an empty entry in such queue, called Reply Post Host
  Index. This value is updated during the driver interrupt routine [in
  _base_interrupt() function].

  * Happens that there are 2 registers representing the Reply Post Host
  Index according to the type of the adapter. They are differentiated in
  the driver through the "ioc->combined_reply_queue" check. By the MPI
  specification (vendor spec), driver should use this combined reply
  queue according to the number of maximum MSI-X vectors that the
  adapter exposes and the spec version (SAS 3.0 vs SAS 3.5).

  * Currently, this is wrong checked for a class of adapters, which was fixed 
in the upstream
  kernel commit 2b48be65685a [0]. Without this commit, we can observe 
spontaneous resets in the
  driver due to queue overflow (FW is not aware that there are free entries in 
the Reply Post Descriptor Queue). The dmesg log will show the following output 
in case of this error:

    mpt3sas_cm0: fault_state(0x2100)!
    mpt3sas_cm0: sending diag reset !!
    mpt3sas_cm0: diag reset: SUCCESS
  [followed by a lot of driver messages as result of the reset procedure]

  * During these resets, I/O is stalled so it may affect performance.

  [Test Case]

  * It's not trivial to test the problem, but given a machine with an
  affected device, an I/O benchmark like FIO could be used to exercise
  the I/O path in a heavy way and trigger the issue.

  * We have reports that the adapter "LSI Logic / Symbios Logic Device
  [1000:00ac]" is affected by the issue.  And this commit resolved the
  problem.

  [Regression Potential]

  * This is a long-term issue from the mpt3sas driver, affecting only a
  class of adapters of this vendor. Since it's a clearly bug, the fix is
  necessary. The potential of regressions is unknown, but likely low -
  it changes the register used for the index updates given some set of
  characteristics of the adapter (according to the spec.), which
  restricts even more the scope of this patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810781/+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 1811419] Re: linux: 4.15.0-44.47 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

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

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

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => In Progress

** 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
  
  backports: bug 1811429 (linux-azure), bug 1811430 (linux-aws-hwe), bug 
1811431 (linux-azure), bug 1811432 (linux-gcp), bug 1811434 (linux-hwe), bug 
1811435 (linux-hwe-edge), bug 1811436 (linux-oracle)
  derivatives: bug 1811420 (linux-raspi2), bug 1811421 (linux-oem), bug 1811422 
(linux-aws), bug 1811423 (linux-azure), bug 1811424 (linux-gcp), bug 1811425 
(linux-kvm), bug 1811427 (linux-oracle)
  -- swm properties --
  boot-testing-requested: true
- phase: Promote to Proposed -- release to Proposed in progress
- phase-changed: Tuesday, 15. January 2019 08:32 UTC
+ bugs-spammed: true
+ phase: Promote to Proposed -- snap release to edge ready
+ phase-changed: Tuesday, 15. January 2019 10:36 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   certification-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   snap-release-to-beta: Pending -- snap not in 18/beta channel
+   snap-release-to-edge: Pending -- snap not in 18/edge channel
+   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/1811419

Title:
  linux: 4.15.0-44.47 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
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 package in Ubuntu:
  Invalid
Status in linux 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

  backports: bug 1811429 (linux-azure), bug 1811430 (linux-aws-hwe), bug 
1811431 (linux-azure), bug 1811432 (linux-gcp), bug 1811434 (linux-hwe), bug 
1811435 (linux-hwe-edge), bug 1811436 (linux-oracle)
  derivatives: bug 1811420 (linux-raspi2), bug 1811421 (linux-oem), bug 1811422 
(linux-aws), bug 1811423 (linux-azure), bug 1811424 (linux-gcp), bug 1811425 
(linux-kvm), bug 1811427 (linux-oracle)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promote to Proposed -- snap release to edge ready
  phase-changed: Tuesday, 15. January 2019 10:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
sn

[Kernel-packages] [Bug 1810457] Re: Update hisilicon SoC-specific drivers

[Brad Figg]

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

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

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


** Tags added: verification-needed-cosmic

** Tags added: verification-needed-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/1810457

Title:
  Update hisilicon SoC-specific drivers

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
Status in linux source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  Drivers for the HiSilicon Hi1616 and Hi1620 SoCs continue to be under active 
development, including both hardware enablement and bug fix patches. With the 
amount of flux involved, identifying and cherry-picking individual patches 
would be more error prone then re-syncing with current upstream.

  [Test Case]
  The Ubuntu server certification suite, which includes network and storage 
tests.

  [Fix]
  Backport the localized driver changes up to v5.0-rc1.

  [Regression Risk]
  These changes are restricted to the hns and hisi_sas drivers, which only 
impact the D05 and D06 server development board platforms. To mitigate this 
risk, we have explicitly tested the proposed changes on these 2 platforms - 
changes are staged in ppa:pearl2-team/test. Of course, there is risk that these 
changes introduced regressions that our testing did not catch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457/+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 1810998] Re: CPU hard lockup with rigorous writes to NVMe drive

[Brad Figg]

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

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

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


** Tags added: verification-needed-cosmic

** Tags added: verification-needed-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/1810998

Title:
  CPU hard lockup with rigorous writes to NVMe drive

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * Users may experience cpu hard lockups when performing
     rigorous writes to NVMe drives.

   * The fix addresses an scheduling issue in the original
     implementation of wbt/writeback throttling

   * The fix is commit 2887e41b910b ("blk-wbt: Avoid lock
     contention and thundering herd issue in wbt_wait"),
     plus its fix commit 38cfb5a45ee0 ("blk-wbt: improve
     waking of tasks").

   * Plus a few dependency commits for each fix.

   * Backports are trivial: mainly replace rq_wait_inc_below()
     with the equivalent atomic_inc_below(), and maintain the
     __wbt_done() signature, both due to the lack of commit
     a79050434b45 ("blk-rq-qos: refactor out common elements
     of blk-wbt"), that changes lots of other/unrelated code.

  [Test Case]

   * This command has been reported to reproduce the problem:

     $ sudo iozone -R -s 5G -r 1m -S 2048 -i 0 -G -c -o -l 128 -u 128 -t
  128

   * It generates stack traces as below in the original kernel,
     and does not generate them in the modified/patched kernel.

   * The user/reporter verified the test kernel with these patches
     resolved the problem.

   * The developer verified in 2 systems (4-core and 24-core but
     no NVMe) for regressions, and no error messages were logged
     to dmesg.

  [Regression Potential]

   * The regression potential is contained within writeback
     throttling mechanism (block/blk-wbt.*).

   * The commits have been verified for fixes in later commits in
     linux-next as of 2019-01-08 and all known fix commits are in.

  [Other Info]

   * The problem has been introduced with the blk-wbt mechanism,
     in v4.10-rc1, and the fix commits in v4.19-rc1 and -rc2,
     so only Bionic and Cosmic needs this.

  [Stack Traces]

  [ 393.628647] NMI watchdog: Watchdog detected hard LOCKUP on cpu 30
  ...
  [ 393.628704] CPU: 30 PID: 0 Comm: swapper/30 Tainted: P OE 4.15.0-20-generic 
#21-Ubuntu
  ...
  [ 393.628720] Call Trace:
  [ 393.628721] 
  [ 393.628724] enqueue_task_fair+0x6c/0x7f0
  [ 393.628726] ? __update_load_avg_blocked_se.isra.37+0xd1/0x150
  [ 393.628728] ? __update_load_avg_blocked_se.isra.37+0xd1/0x150
  [ 393.628731] activate_task+0x57/0xc0
  [ 393.628735] ? sched_clock+0x9/0x10
  [ 393.628736] ? sched_clock+0x9/0x10
  [ 393.628738] ttwu_do_activate+0x49/0x90
  [ 393.628739] try_to_wake_up+0x1df/0x490
  [ 393.628741] default_wake_function+0x12/0x20
  [ 393.628743] autoremove_wake_function+0x12/0x40
  [ 393.628744] __wake_up_common+0x73/0x130
  [ 393.628745] __wake_up_common_lock+0x80/0xc0
  [ 393.628746] __wake_up+0x13/0x20
  [ 393.628749] __wbt_done.part.21+0xa4/0xb0
  [ 393.628749] wbt_done+0x72/0xa0
  [ 393.628753] blk_mq_free_request+0xca/0x1a0
  [ 393.628755] blk_mq_end_request+0x48/0x90
  [ 393.628760] nvme_complete_rq+0x23/0x120 [nvme_core]
  [ 393.628763] nvme_pci_complete_rq+0x7a/0x130 [nvme]
  [ 393.628764] __blk_mq_complete_request+0xd2/0x140
  [ 393.628766] blk_mq_complete_request+0x18/0x20
  [ 393.628767] nvme_process_cq+0xe1/0x1b0 [nvme]
  [ 393.628768] nvme_irq+0x23/0x50 [nvme]
  [ 393.628772] __handle_irq_event_percpu+0x44/0x1a0
  [ 393.628773] handle_irq_event_percpu+0x32/0x80
  [ 393.628774] handle_irq_event+0x3b/0x60
  [ 393.628778] handle_edge_irq+0x7c/0x190
  [ 393.628779] handle_irq+0x20/0x30
  [ 393.628783] do_IRQ+0x46/0xd0
  [ 393.628784] common_interrupt+0x84/0x84
  [ 393.628785] 
  ...
  [ 393.628794] ? cpuidle_enter_state+0x97/0x2f0
  [ 393.628796] cpuidle_enter+0x17/0x20
  [ 393.628797] call_cpuidle+0x23/0x40
  [ 393.628798] do_idle+0x18c/0x1f0
  [ 393.628799] cpu_startup_entry+0x73/0x80
  [ 393.628802] start_secondary+0x1a6/0x200
  [ 393.628804] secondary_startup_64+0xa5/0xb0
  [ 393.628805] Code: ...

  [ 405.981597] nvme nvme1: I/O 393 QID 6 timeout, completion polled

  [ 435.597209] INFO: rcu_sched detected stalls on CPUs/tasks:
  [ 435.602858] 30-...0: (1 GPs behind) i

[Kernel-packages] [Bug 1811337] Re: To reduce the Realtek USB cardreader power consumption

[Brad Figg]

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

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

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


** Tags added: verification-needed-cosmic

** Tags added: verification-needed-bionic

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

Title:
  To reduce the Realtek USB cardreader power consumption

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

Bug description:
  [Impact]
  Realtek USB cardreader consumes more than 1 Watt during long idle if it's not 
suspended. And it's runtime PM functions are available after v4.20.

  [Fix]
  To avoid conflicts, have to backport some patches for mmc core.

  [Test]
  Note: Inside () are the previous value (non-patch)
  Sort idle: 7.76W (7.88)
  Long idle: 4.658W (5.79)
  S3: 0.5W (0.5)
  S5: 0.20W (0.208)

  [Regression Potential]
  Low, most commits are for rtsx_usb_{sdmmc,ms} and are all small changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1811337/+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 1810892] Re: lineout jack can't work on a Dell machine

[Brad Figg]

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

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

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

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

Title:
  lineout jack can't work on a Dell machine

Status in HWE Next:
  New
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
Status in linux source package in Disco:
  Fix Committed

Bug description:
  
  [Impact]
  The rear lineout jack can't work. If users plug a headphone or audio
  cable into the lineout jack, nothing happens, the audio still output
  from internal speaker. The expected behaviour is the lineout is
  active and the sound is routed to lineout jack from internal speaker.

  [Fix]
  apply the ALC274_FIXUP_DELL_AIO_LINEOUT_VERB, this will set the
  lineout pin to be a correct configuration value.

  
  [Test Case]
  plug headphone into the rear lineout jack, system can detect lineout
  jack is plugged and the audio output is routed to lineout jack from
  internal speaker.

  
  [Regression Potential]
  Very low, this patch is specific to one Dell machine model.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1810892/+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 1809847] Re: Ethernet[10ec:8136] doesn't work after S3 with kernel 4.15.0.43.64

[Brad Figg]

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

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

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

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

Title:
  Ethernet[10ec:8136] doesn't work after S3 with kernel 4.15.0.43.64

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
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]
  The Ethernet works after S3 with kernel 4.15.0-33.36, and fails with kernel 
4.15.0.43.64.
  There is no interrupt while plug/unplug Ethernet cable after S3, so it looks 
like a regression after 4.15.0-33.36.

  [Fix]
  Check changelog and found there are 2 commits introduced from 4.15.0-35.38 
might be suspicious
    * r8169 no internet after suspending (LP: #1779817)
  - r8169: don't use MSI-X on RTL8168g
  - r8169: don't use MSI-X on RTL8106e
  And check the upstream log and found the 2 MSI-X commits had been all 
reverted, since below commit claims it fixes the MSI-X interrupt issue which is 
already in Bionic kernel.
     083874549fdf PCI: Reprogram bridge prefetch registers on resume
  So, I reverted the 2 MSI-X commits and found the Ethernet works again after 
S3.

  [Regression Potential]
  Low, the 2 disable MSI-X commits are workarounds, and now we have proper way 
to fix the issue, so it should be fine to revert them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1809847/+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 1801102] Re: Bionic shows incorrect warning about number of pointers in TFD

[Brad Figg]

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

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

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


** Tags added: verification-needed-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/1801102

Title:
  Bionic shows incorrect warning about number of pointers in TFD

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

Bug description:
  ===SRU Justification===
  [Impact]
  iwlwifi spews "Too many chunks: 20" in dmesg.

  [Fix] 
  From the patch description:
  "
  When we free the TFD, we check its number of valid pointers
  and make sure it doesn't exceed the number of pointers the
  hardware support.
  This check had an off by one bug: it is perfectly valid to
  free the 20 pointers if the TFD has 20 pointers.
  "

  [Test]
  User confirms the patch solves the problem.

  [Regression Potential]
  Low. The fix is limited to iwlwifi, and the patch is in mainline for a
  while.

  ===Original Bug Report===
  Hi:

  I am having the same issue i.e. when downloading torrent with
  KTorrent. Please include this fix https://www.spinics.net/lists/linux-
  wireless/msg169994.html in the release kernel.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801102/+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 1805802] Re: [UBUNTU] qeth: fix length check in SNMP processing

[Brad Figg]

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

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

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

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

Title:
  [UBUNTU] qeth: fix length check in SNMP processing

Status in Ubuntu on IBM z Systems:
  Fix Committed
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
Status in linux source package in Disco:
  Fix Committed

Bug description:
  == SRU Justification ==
  The response for a SNMP request can consist of multiple parts,
which the cmd callback stages into a kernel buffer until all
parts have been received. If the callback detects that the
staging buffer provides insufficient space, it bails out with
error.
This processing is buggy for the first part of the response -
while it initially checks for a length of 'data_len', it later
copies an additional amount of
'offsetof(struct qeth_snmp_cmd, data)' bytes.

  
  == Fix ==
  9a764c1e5968 ("s390/qeth: fix length check in SNMP processing")

  == Regression Potential ==
  Low.  Changes limited to s390.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  
  == Original bug description ==

  Description:  qeth: fix length check in SNMP processing
  Symptom:  Undefined behaviour.
  Problem:  The response for a SNMP request can consist of multiple parts,
    which the cmd callback stages into a kernel buffer until all
    parts have been received. If the callback detects that the
    staging buffer provides insufficient space, it bails out with
    error.
    This processing is buggy for the first part of the response -
    while it initially checks for a length of 'data_len', it later
    copies an additional amount of
    'offsetof(struct qeth_snmp_cmd, data)' bytes.
  Solution: Fix the calculation of 'data_len' for the first part of the
    response.
  Upstream-ID:  9a764c1e59684c0358e16ccaafd870629f2cfe67

  Should be applied to all Ubuntu Releases in Service

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1805802/+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 1807757] Re: Drivers: hv: vmbus: Offload the handling of channels to two workqueues

[Brad Figg]

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

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

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


** Tags added: verification-needed-cosmic

** Tags added: verification-needed-bionic

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

Title:
  Drivers: hv: vmbus: Offload the handling of channels to two workqueues

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  In Progress
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:
  == SRU Justification ==

  Microsoft has identified a multiple-NIC-deadlock issue on Hyper-V VMs.  This 
bug is fixed by the following commit, which is in mainline as of v4.20-rc6:
  37c2578c0c40 ("Drivers: hv: vmbus: Offload the handling of channels to two 
workqueues")

  A second commit is also needed to prevent a deadlock with single NIC VMs.  
This commit is in mainline as of 4.19-rc3:
  e04e7a7bbd4b ("hv_netvsc: Fix a deadlock by getting rtnl lock earlier in 
netvsc_probe()")

  The Disco development release has been rebased to upstream 4.19,  and
  it already has commit eceb0596548.  Disco only needs 37c2578c0c40.

  Cosmic does not require any dependent commits, just the two
  above(37c2578c0c40, e04e7a7bbd4b).

  linux-azure and Bionic(4.15+ kernels) require the following five dependent 
commits:
  4.18-rc1 - 7bf7bb37f16a ("hv_netvsc: fix network namespace issues with VF 
support")
  4.18-rc4 - 3ffe64f1a641 ("hv_netvsc: split sub-channel setup into async and 
sync")
  4.19-rc1 - 50229128727f ("Drivers: hv: vmbus: Fix the offer_in_progress in 
vmbus_process_offer()")
  4.19-rc3 - e04e7a7bbd4b ("hv_netvsc: Fix a deadlock by getting rtnl lock 
earlier in netvsc_probe()")
  4.19-rc4 - 6712cc9c2211 ("vmbus: don't return values for uninitalized 
channels")


  == Fixes ==
  ("Dependent commits mentioned above, based on Ubuntu release")

  e04e7a7bbd4b ("hv_netvsc: Fix a deadlock by getting rtnl lock earlier
  in netvsc_probe()")

  37c2578c0c40 ("Drivers: hv: vmbus: Offload the handling of channels to
  two workqueues")

  == Regression Potential ==
  Low.  Limited to hyperv.

  == Test Case ==

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807757/+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