[Kernel-packages] [Bug 1832564] Re: linux-kvm: 4.15.0-1037.37 -proposed tracker

2019-06-19 Thread Jesse Sung
** Summary changed:

- linux-kvm:  -proposed tracker
+ linux-kvm: 4.15.0-1037.37 -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) => Jesse Sung 
(wenchien)

** 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) => Jesse Sung 
(wenchien)

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

Title:
  linux-kvm: 4.15.0-1037.37 -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 promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Bionic:
  New

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

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

  -- swm properties --
  kernel-stable-master-bug: 1832578
  phase: Ready for Packaging
  phase-changed: Monday, 17. June 2019 22:38 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

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


[Kernel-packages] [Bug 1829170] Re: linux-snapdragon: 5.0.0-1013.13 -proposed tracker

2019-05-16 Thread Jesse Sung
** Summary changed:

- linux-snapdragon:  -proposed tracker
+ linux-snapdragon: 5.0.0-1013.13 -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) => Jesse Sung 
(wenchien)

** 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) => Jesse Sung 
(wenchien)

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

Title:
  linux-snapdragon: 5.0.0-1013.13 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Disco:
  New

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

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

  -- swm properties --
  kernel-stable-master-bug: 1829173
  phase: Packaging
  phase-changed: Thursday, 16. May 2019 10:33 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded

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

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


[Kernel-packages] [Bug 1821290] Re: Pop noise when headset is plugged in or removed from GHS/Line-out jack

2019-05-06 Thread Jesse Sung
** Changed in: linux (Ubuntu)
   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/1821290

Title:
  Pop noise when headset is plugged in or removed from GHS/Line-out jack

Status in HWE Next:
  Fix Released
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:
  == SRU Justification ==

  * Impact:
  There's unpleasant pop noise when headset is plugged in or removed from 
GHS/Line-out jack.

  * Fix:
  Issue can be fixed by these four patches. All of them are accepted by 
upstream.
  - 4d4b0c52 - ALSA: hda/realtek - Add unplug function into unplug state of 
Headset Mode for ALC225
  - d1dd4211 - ALSA: hda/realtek - Disable headset Mic VREF for headset mode of 
ALC225
  - 136824ef - ALSA: hda/realtek - Add support headset mode for DELL WYSE AIO
  - da484d00 - ALSA: hda/realtek - Add support headset mode for New DELL WYSE NB

  * Testcase:
  Connect/remove a headset to/from the jack and see if there's noise.

  * Risk of Regression:
  Low since these patches only affect specific platforms.

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

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


[Kernel-packages] [Bug 1821290] Re: Pop noise when headset is plugged in or removed from GHS/Line-out jack

2019-05-06 Thread Jesse Sung
** Tags removed: verification-needed-bionic verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic

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

Title:
  Pop noise when headset is plugged in or removed from GHS/Line-out jack

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  == SRU Justification ==

  * Impact:
  There's unpleasant pop noise when headset is plugged in or removed from 
GHS/Line-out jack.

  * Fix:
  Issue can be fixed by these four patches. All of them are accepted by 
upstream.
  - 4d4b0c52 - ALSA: hda/realtek - Add unplug function into unplug state of 
Headset Mode for ALC225
  - d1dd4211 - ALSA: hda/realtek - Disable headset Mic VREF for headset mode of 
ALC225
  - 136824ef - ALSA: hda/realtek - Add support headset mode for DELL WYSE AIO
  - da484d00 - ALSA: hda/realtek - Add support headset mode for New DELL WYSE NB

  * Testcase:
  Connect/remove a headset to/from the jack and see if there's noise.

  * Risk of Regression:
  Low since these patches only affect specific platforms.

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

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


[Kernel-packages] [Bug 1826340] Re: linux-gcp: 4.15.0-1031.33 -proposed tracker

2019-04-26 Thread Jesse Sung
** Summary changed:

- linux-gcp:  -proposed tracker
+ linux-gcp: 4.15.0-1031.33 -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) => Jesse Sung 
(wenchien)

** 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) => Jesse Sung 
(wenchien)

** 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) => Jesse Sung 
(wenchien)

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

Title:
  linux-gcp: 4.15.0-1031.33 -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 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 verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  New

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

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

  backports: bug 1826339 (xenial/linux-gcp)

  -- swm properties --
  kernel-stable-master-bug: 1826358
  phase: Packaging
  phase-changed: Friday, 26. April 2019 07:39 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

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

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


[Kernel-packages] [Bug 1821290] Re: Pop noise when headset is plugged in or removed from GHS/Line-out jack

2019-04-17 Thread Jesse Sung
We have 136824ef and da484d00 in Disco kernel through stable kernel
updates.

** Changed in: hwe-next
   Status: New => Fix Released

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Jesse Sung (wenchien)

** Changed in: linux (Ubuntu Cosmic)
 Assignee: (unassigned) => Jesse Sung (wenchien)

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

** Changed in: linux (Ubuntu Cosmic)
   Status: New => 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/1821290

Title:
  Pop noise when headset is plugged in or removed from GHS/Line-out jack

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

Bug description:
  == SRU Justification ==

  * Impact:
  There's unpleasant pop noise when headset is plugged in or removed from 
GHS/Line-out jack.

  * Fix:
  Issue can be fixed by these four patches. All of them are accepted by 
upstream.
  - 4d4b0c52 - ALSA: hda/realtek - Add unplug function into unplug state of 
Headset Mode for ALC225
  - d1dd4211 - ALSA: hda/realtek - Disable headset Mic VREF for headset mode of 
ALC225
  - 136824ef - ALSA: hda/realtek - Add support headset mode for DELL WYSE AIO
  - da484d00 - ALSA: hda/realtek - Add support headset mode for New DELL WYSE NB

  * Testcase:
  Connect/remove a headset to/from the jack and see if there's noise.

  * Risk of Regression:
  Low since these patches only affect specific platforms.

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

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


[Kernel-packages] [Bug 1821276] Re: Add support for MAC address pass through on RTL8153-BD

2019-04-17 Thread Jesse Sung
** Tags removed: verification-needed-bionic verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic

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

** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  Add support for MAC address pass through on RTL8153-BD

Status in HWE Next:
  Fix Released
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:
  == SRU Justification ==

  * Impact:
  RTL8153-BD is used in Dell DA300 type-C dongle and should be added to the 
whitelist of devices to activate MAC address passthrough.

  * Fix:
  Two commits in upstream need to be applied in order to support this feature. 
Both of them are in 5.0.

  commit 8e29d23e28ee7fb995a00c1ca7e1a4caf5070b12
  Author: David Chen david.ch...@dell.com
  Date: Sat Feb 16 17:16:42 2019 +0800

  r8152: Add support for MAC address pass through on RTL8153-BD

  commit c286909fe5458f69e533c845b757fd2c35064d26
  Author: David Chen david.ch...@dell.com
  Date: Wed Feb 20 13:47:19 2019 +0800

  r8152: Fix an error on RTL8153-BD MAC Address Passthrough support

  * Testcase:
  BIOS settings must be properly set before verifying.
  1.[Settings][POST Behavior][MAC Address Pass-Through]: Passthrough MAC Address
  2. There should be two MAC addresses in BIOS settings, ex: 
[Settings][General][System Information]
  Attach the dongle and see if MAC passthrough works.

  * Risk of Regression:
  Clean cherry-pick from mainline, and only add specific hardware to the 
whitelist. Risk is low.

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

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


[Kernel-packages] [Bug 1821290] Re: Pop noise when headset is plugged in or removed from GHS/Line-out jack

2019-03-22 Thread Jesse Sung
The first two patches, 4d4b0c52 and d1dd4211, are in 5.0-rc2.
The other two are in 5.1-rc1.

** Changed in: hwe-next
 Assignee: (unassigned) => Jesse Sung (wenchien)

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

Title:
  Pop noise when headset is plugged in or removed from GHS/Line-out jack

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  == SRU Justification ==

  * Impact:
  There's unpleasant pop noise when headset is plugged in or removed from 
GHS/Line-out jack.

  * Fix:
  Issue can be fixed by these four patches. All of them are accepted by 
upstream.
  - 4d4b0c52 - ALSA: hda/realtek - Add unplug function into unplug state of 
Headset Mode for ALC225
  - d1dd4211 - ALSA: hda/realtek - Disable headset Mic VREF for headset mode of 
ALC225
  - 136824ef - ALSA: hda/realtek - Add support headset mode for DELL WYSE AIO
  - da484d00 - ALSA: hda/realtek - Add support headset mode for New DELL WYSE NB

  * Testcase:
  Connect/remove a headset to/from the jack and see if there's noise.

  * Risk of Regression:
  Low since these patches only affect specific platforms.

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

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


[Kernel-packages] [Bug 1821290] [NEW] Pop noise when headset is plugged in or removed from GHS/Line-out jack

2019-03-22 Thread Jesse Sung
Public bug reported:

== SRU Justification ==

* Impact:
There's unpleasant pop noise when headset is plugged in or removed from 
GHS/Line-out jack.

* Fix:
Issue can be fixed by these four patches. All of them are accepted by upstream.
- 4d4b0c52 - ALSA: hda/realtek - Add unplug function into unplug state of 
Headset Mode for ALC225
- d1dd4211 - ALSA: hda/realtek - Disable headset Mic VREF for headset mode of 
ALC225
- 136824ef - ALSA: hda/realtek - Add support headset mode for DELL WYSE AIO
- da484d00 - ALSA: hda/realtek - Add support headset mode for New DELL WYSE NB

* Testcase:
Connect/remove a headset to/from the jack and see if there's noise.

* Risk of Regression:
Low since these patches only affect specific platforms.

** Affects: hwe-next
 Importance: Undecided
 Assignee: Jesse Sung (wenchien)
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Jesse Sung (wenchien)
 Status: In Progress


** Tags: carson originate-from-1812330

** Tags added: carson originate-from-1812330

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

Title:
  Pop noise when headset is plugged in or removed from GHS/Line-out jack

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  == SRU Justification ==

  * Impact:
  There's unpleasant pop noise when headset is plugged in or removed from 
GHS/Line-out jack.

  * Fix:
  Issue can be fixed by these four patches. All of them are accepted by 
upstream.
  - 4d4b0c52 - ALSA: hda/realtek - Add unplug function into unplug state of 
Headset Mode for ALC225
  - d1dd4211 - ALSA: hda/realtek - Disable headset Mic VREF for headset mode of 
ALC225
  - 136824ef - ALSA: hda/realtek - Add support headset mode for DELL WYSE AIO
  - da484d00 - ALSA: hda/realtek - Add support headset mode for New DELL WYSE NB

  * Testcase:
  Connect/remove a headset to/from the jack and see if there's noise.

  * Risk of Regression:
  Low since these patches only affect specific platforms.

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

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


[Kernel-packages] [Bug 1821276] [NEW] Add support for MAC address pass through on RTL8153-BD

2019-03-21 Thread Jesse Sung
Public bug reported:

== SRU Justification ==

* Impact:
RTL8153-BD is used in Dell DA300 type-C dongle and should be added to the 
whitelist of devices to activate MAC address passthrough.

* Fix:
Two commits in upstream need to be applied in order to support this feature. 
Both of them are in 5.0.

commit 8e29d23e28ee7fb995a00c1ca7e1a4caf5070b12
Author: David Chen david.ch...@dell.com
Date: Sat Feb 16 17:16:42 2019 +0800

r8152: Add support for MAC address pass through on RTL8153-BD

commit c286909fe5458f69e533c845b757fd2c35064d26
Author: David Chen david.ch...@dell.com
Date: Wed Feb 20 13:47:19 2019 +0800

r8152: Fix an error on RTL8153-BD MAC Address Passthrough support

* Testcase:
BIOS settings must be properly set before verifying.
1.[Settings][POST Behavior][MAC Address Pass-Through]: Passthrough MAC Address
2. There should be two MAC addresses in BIOS settings, ex: 
[Settings][General][System Information]
Attach the dongle and see if MAC passthrough works.

* Risk of Regression:
Clean cherry-pick from mainline, and only add specific hardware to the 
whitelist. Risk is low.

** Affects: hwe-next
 Importance: Undecided
 Assignee: Jesse Sung (wenchien)
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Jesse Sung (wenchien)
 Status: In Progress

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

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


** Tags: carson originate-from-1817252

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

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

** Tags added: carson originate-from-1817252

** Changed in: hwe-next
 Assignee: (unassigned) => Jesse Sung (wenchien)

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

Title:
  Add support for MAC address pass through on RTL8153-BD

Status in HWE Next:
  New
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:
  == SRU Justification ==

  * Impact:
  RTL8153-BD is used in Dell DA300 type-C dongle and should be added to the 
whitelist of devices to activate MAC address passthrough.

  * Fix:
  Two commits in upstream need to be applied in order to support this feature. 
Both of them are in 5.0.

  commit 8e29d23e28ee7fb995a00c1ca7e1a4caf5070b12
  Author: David Chen david.ch...@dell.com
  Date: Sat Feb 16 17:16:42 2019 +0800

  r8152: Add support for MAC address pass through on RTL8153-BD

  commit c286909fe5458f69e533c845b757fd2c35064d26
  Author: David Chen david.ch...@dell.com
  Date: Wed Feb 20 13:47:19 2019 +0800

  r8152: Fix an error on RTL8153-BD MAC Address Passthrough support

  * Testcase:
  BIOS settings must be properly set before verifying.
  1.[Settings][POST Behavior][MAC Address Pass-Through]: Passthrough MAC Address
  2. There should be two MAC addresses in BIOS settings, ex: 
[Settings][General][System Information]
  Attach the dongle and see if MAC passthrough works.

  * Risk of Regression:
  Clean cherry-pick from mainline, and only add specific hardware to the 
whitelist. Risk is low.

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

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


[Kernel-packages] [Bug 1780066] Re: [Bionic] Disk IO hangs when using BFQ as io scheduler

2019-03-21 Thread Jesse Sung
** Changed in: linux (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [Bionic] Disk IO hangs when using BFQ as io scheduler

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

Bug description:
  When BFQ is used, disk IO will hang some seconds after boot. This was
  also reported in some public MLs [1][2]. The fix is already in
  mainline, but it's not available in 4.15.

  [1] https://lkml.org/lkml/2017/12/1/80
  [2] https://groups.google.com/forum/#!topic/bfq-iosched/nB2cVfDMSOU

  == SRU Justification ==

  Impact:
  Disk IO hangs several seconds after booting with a bionic Ubuntu kernel

  Fix:
  Three patches are cherry-picked for SRU. "block, bfq: add requeue-request 
hook" is the fix, while the other two are cleanups and make the whole fixes 
clean cherry-picks.

  Testcase:
  Boot the kernel with BFQ as IO scheduler.

  Risk of Regression:
  Clean cherry-picks from upstream so the risk should be fairly low.

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

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


[Kernel-packages] [Bug 1819653] Re: linux-aws: 4.4.0-1078.88 -proposed tracker

2019-03-15 Thread Jesse Sung
** Summary changed:

- linux-aws:  -proposed tracker
+ linux-aws: 4.4.0-1078.88 -proposed tracker

** 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) => Jesse Sung 
(wenchien)

** 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) => Jesse Sung 
(wenchien)

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

Title:
  linux-aws: 4.4.0-1078.88 -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 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:
  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 Xenial:
  New

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

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

  -- swm properties --
  kernel-stable-master-bug: 1819660
  phase: Ready for Packaging
  phase-changed: Thursday, 14. March 2019 12:37 UTC
  reason:
prepare-package: Pending -- version not specified

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

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


[Kernel-packages] [Bug 1816782] Re: linux-azure: 4.18.0-1012.12~18.04.1 -proposed tracker

2019-02-21 Thread Jesse Sung
** Summary changed:

- linux-azure:  -proposed tracker
+ linux-azure: 4.18.0-1012.12~18.04.1 -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) => Jesse Sung 
(wenchien)

** 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) => Jesse Sung 
(wenchien)

** 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) => Jesse Sung 
(wenchien)

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

Title:
  linux-azure: 4.18.0-1012.12~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  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 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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in 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: 1814749
  phase: Packaging
  phase-changed: Thursday, 21. February 2019 15:38 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

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

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


[Kernel-packages] [Bug 1807333] Re: Add support for 0cf3:535b QCA_ROME device

2019-01-24 Thread Jesse Sung
** Tags removed: verification-needed-bionic verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-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 1807342] Re: Add support for Dell DW5821e WWAN/GPS module

2019-01-24 Thread Jesse Sung
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  Add support for Dell DW5821e WWAN/GPS module

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
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

Bug description:
  == Impact ==
  DW5821e doesn't work in Bionic.

  == Fix ==
  Three commits are required to support it. All of them are already in the 
mainline kernel.

  == Test Case ==
  With the command
  $ sudo mmcli -L
  the device should be listed as a modem.

  == Risk of Regression ==
  Very low. it only adds the device ID to the right driver.

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

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


[Kernel-packages] [Bug 1808768] Re: Initrd of pc-kernel snap contains out-of-date packages

2019-01-02 Thread Jesse Sung
** Tags added: dawson originate-from-1808480

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

Title:
  Initrd of pc-kernel snap contains out-of-date packages

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

Bug description:
  The build script does not install package updates during generate the
  pc-kernel snap.

  I met this bug #1783810 when I was verify my Ubuntu Core 18 image on KVM.
  The system stuck at resizing the writable partition. the resize script of 
initrd called sgdisk to achieve the resizing. Inside sgdisk, it use libuuid1 to 
get random bytes and generate UUIDs. After I extracted the kernel snap, I found 
it is still using libuuid1 2.31.1-0.4ubuntu3 which is not the latest version. 
At this moment, Bionic has 2.31.1-0.4ubuntu3.2.
  Then I added commands to make the build script installing package updates. 
After that, the system can boot correctly without any problem.

  I am wondering if there is any concern to pull updates before
  building?

  The attachment is my patch to pull updates.

  Snippet of console output, before patch
  [2.491404] usbcore: registered new interface driver usb-storage
  [2.503788] sdhci: Secure Digital Host Controller Interface driver
  [2.505627] sdhci: Copyright(c) Pierre Ossman
  [2.548485] initrd: found more than 10% free space on disk, resizing 
/dev/sda3
  [2.550345] initrd: partition to full disk size, see /dev/kmsg for details
  [2.912472] clocksource: tsc: mask: 0x max_cycles: 
0x255b2dea34c, max_idle_ns: 440795243480 ns
  ## several keystrokes here, or the boot process won't continue
  [  351.361426] random: crng init done
  [  351.423462] fixing backup GPT
  [  352.435735] systemd-udevd[240]: passed device to netlink monitor 
0x55e45653e330
  [  352.443221]  sda: sda1 sda2 sda3
  [  352.445486] The operation has completed successfully.

  Snippet of console output, after patch
  [2.548203] usbcore: registered new interface driver usb-storage
  [2.561439] sdhci: Secure Digital Host Controller Interface driver
  [2.562878] sdhci: Copyright(c) Pierre Ossman
  [2.602093] initrd: found more than 10% free space on disk, resizing 
/dev/sda3
  [2.603900] initrd: partition to full disk size, see /dev/kmsg for details
  ## block a few seconds, until timeout.
  [2.912418] clocksource: tsc: mask: 0x max_cycles: 
0x255b2dea34c, max_idle_ns: 440795243480 ns
  [9.174552] random: fast init done
  [9.179127] random: parted: uninitialized urandom read (16 bytes read)
  [9.183726] random: parted: uninitialized urandom read (16 bytes read)
  [9.190606] random: parted: uninitialized urandom read (16 bytes read)
  [9.230419] fixing backup GPT
  [9.236989] random: crng init done
  [9.238102] random: 5 urandom warning(s) missed due to ratelimiting
  [   10.245047] systemd-udevd[259]: passed device to netlink monitor 
0x56376c45b150
  [   10.253093]  sda: sda1 sda2 sda3
  [   10.256202] The operation has completed successfully.

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

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


[Kernel-packages] [Bug 1810223] [NEW] i2c-designware stops working after S4 on CHT platforms

2019-01-01 Thread Jesse Sung
Public bug reported:

== Impact ==
The i2c-designware stops working after S4 thus I2C devices connected to it 
can't be accessed.
[  272.628526] PM: Timekeeping suspended for 115.313 seconds
[  272.633110] ACPI: Waking up from system sleep state S4
[  272.655524] PM: noirq restore of devices complete after 19.377 msecs
[  272.775692] i2c_designware 80860F41:00: Unknown Synopsys component type: 
0x
[  272.876322] PM: early restore of devices complete after 219.859 msecs
...
[  273.060760] i2c_designware 80860F41:00: timeout waiting for bus ready
[  274.214314] i2c_designware 80860F41:00: timeout in disabling adapter

== Fix ==
This happens after these two commits:
* 36c27d206b21 - PM: i2c-designware-platdrv: Optimize power management 
(2018-12-07 16:21:11 +0800)
* 489cd2fafa2d - PM: i2c-designware-platdrv: Use DPM_FLAG_SMART_PREPARE 
(2018-12-07 16:21:11 +0800)
Until there's a proper fix for them, both of them need to be reverted in order 
to make S4 works again.

== Test Case ==
Boot with the kernel, S4, and then wake the system up.

== Risk of Regression ==
Risk should be low since we're removing new features.

** Affects: linux-oem (Ubuntu)
 Importance: Undecided
 Assignee: Jesse Sung (wenchien)
 Status: In Progress

** Summary changed:

- i2c-dw stops working after S4 on CHT platforms
+ i2c-designware stops working after S4 on CHT platforms

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

Title:
  i2c-designware stops working after S4 on CHT platforms

Status in linux-oem package in Ubuntu:
  In Progress

Bug description:
  == Impact ==
  The i2c-designware stops working after S4 thus I2C devices connected to it 
can't be accessed.
  [  272.628526] PM: Timekeeping suspended for 115.313 seconds
  [  272.633110] ACPI: Waking up from system sleep state S4
  [  272.655524] PM: noirq restore of devices complete after 19.377 msecs
  [  272.775692] i2c_designware 80860F41:00: Unknown Synopsys component type: 
0x
  [  272.876322] PM: early restore of devices complete after 219.859 msecs
  ...
  [  273.060760] i2c_designware 80860F41:00: timeout waiting for bus ready
  [  274.214314] i2c_designware 80860F41:00: timeout in disabling adapter

  == Fix ==
  This happens after these two commits:
  * 36c27d206b21 - PM: i2c-designware-platdrv: Optimize power management 
(2018-12-07 16:21:11 +0800)
  * 489cd2fafa2d - PM: i2c-designware-platdrv: Use DPM_FLAG_SMART_PREPARE 
(2018-12-07 16:21:11 +0800)
  Until there's a proper fix for them, both of them need to be reverted in 
order to make S4 works again.

  == Test Case ==
  Boot with the kernel, S4, and then wake the system up.

  == Risk of Regression ==
  Risk should be low since we're removing new features.

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

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


[Kernel-packages] [Bug 1807339] Re: Add HMS CAN driver for Dell Edge Gateways

2018-12-11 Thread Jesse Sung
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  Add HMS CAN driver for Dell Edge Gateways

Status in HWE Next:
  New
Status in linux-oem package in Ubuntu:
  In Progress

Bug description:
  == Impact ==
  The HMS CAN device on Dell Edge Gateways doesn't work with linux-oem in 
Bionic. We used to have a driver for 4.4 from IHV integrated in Xenial. For 
4.15 there's a new release for that.

  == Fix ==
  Integrate the new release from IHV.

  == Test Case ==
  Check if the device binds to a driver.

  == Risk of Regression ==
  The driver binds to certain USB IDs thus should be reasonably low.

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

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


[Kernel-packages] [Bug 1807339] Re: Add HMS CAN driver for Dell Edge Gateways

2018-12-07 Thread Jesse Sung
** Tags removed: originate-from-1784570
** Tags added: originate-from-1807357

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

Title:
  Add HMS CAN driver for Dell Edge Gateways

Status in HWE Next:
  New
Status in linux-oem package in Ubuntu:
  In Progress

Bug description:
  == Impact ==
  The HMS CAN device on Dell Edge Gateways doesn't work with linux-oem in 
Bionic. We used to have a driver for 4.4 from IHV integrated in Xenial. For 
4.15 there's a new release for that.

  == Fix ==
  Integrate the new release from IHV.

  == Test Case ==
  Check if the device binds to a driver.

  == Risk of Regression ==
  The driver binds to certain USB IDs thus should be reasonably low.

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

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


[Kernel-packages] [Bug 1807339] Re: Add HMS CAN driver for Dell Edge Gateways

2018-12-07 Thread Jesse Sung
** Description changed:

- The HMS CAN device on Dell Edge Gateways doesn't work with linux-oem in
- Bionic. We used to have a driver for 4.4 from IHV integrated in Xenial.
- For 4.15 there's a new release for that. Let's integrate the driver in
- order to provide support for this device.
+ == Impact ==
+ The HMS CAN device on Dell Edge Gateways doesn't work with linux-oem in 
Bionic. We used to have a driver for 4.4 from IHV integrated in Xenial. For 
4.15 there's a new release for that.
+ 
+ == Fix ==
+ Integrate the new release from IHV.
+ 
+ == Test Case ==
+ Check if the device binds to a driver.
+ 
+ == Risk of Regression ==
+ The driver binds to certain USB IDs thus should be reasonably low.

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

Title:
  Add HMS CAN driver for Dell Edge Gateways

Status in HWE Next:
  New
Status in linux-oem package in Ubuntu:
  In Progress

Bug description:
  == Impact ==
  The HMS CAN device on Dell Edge Gateways doesn't work with linux-oem in 
Bionic. We used to have a driver for 4.4 from IHV integrated in Xenial. For 
4.15 there's a new release for that.

  == Fix ==
  Integrate the new release from IHV.

  == Test Case ==
  Check if the device binds to a driver.

  == Risk of Regression ==
  The driver binds to certain USB IDs thus should be reasonably low.

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

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


[Kernel-packages] [Bug 1807339] Re: Add HMS CAN driver for Dell Edge Gateways

2018-12-07 Thread Jesse Sung
** Description changed:

- Need to integrate the driver released from the vendor.
+ The HMS CAN device on Dell Edge Gateways doesn't work with linux-oem in
+ Bionic. We used to have a driver for 4.4 from IHV integrated in Xenial.
+ For 4.15 there's a new release for that. Let's integrate the driver in
+ order to provide support for this device.

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

Title:
  Add HMS CAN driver for Dell Edge Gateways

Status in HWE Next:
  New
Status in linux-oem package in Ubuntu:
  In Progress

Bug description:
  == Impact ==
  The HMS CAN device on Dell Edge Gateways doesn't work with linux-oem in 
Bionic. We used to have a driver for 4.4 from IHV integrated in Xenial. For 
4.15 there's a new release for that.

  == Fix ==
  Integrate the new release from IHV.

  == Test Case ==
  Check if the device binds to a driver.

  == Risk of Regression ==
  The driver binds to certain USB IDs thus should be reasonably low.

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

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


[Kernel-packages] [Bug 1807339] Re: Add HMS CAN driver for Dell Edge Gateways

2018-12-07 Thread Jesse Sung
** Summary changed:

- Add HMS CAN driver for new Dell Edge Gateways
+ Add HMS CAN driver for Dell Edge Gateways

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

Title:
  Add HMS CAN driver for Dell Edge Gateways

Status in HWE Next:
  New
Status in linux-oem package in Ubuntu:
  In Progress

Bug description:
  The HMS CAN device on Dell Edge Gateways doesn't work with linux-oem
  in Bionic. We used to have a driver for 4.4 from IHV integrated in
  Xenial. For 4.15 there's a new release for that. Let's integrate the
  driver in order to provide support for this device.

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

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


[Kernel-packages] [Bug 1807342] [NEW] Add support for Dell DW5821e WWAN/GPS module

2018-12-07 Thread Jesse Sung
Public bug reported:

== Impact ==
DW5821e doesn't work in Bionic.

== Fix ==
Three commits are required to support it. All of them are already in the 
mainline kernel.

== Test Case ==
With the command
$ sudo mmcli -L
the device should be listed as a modem.

== Risk of Regression ==
Very low. it only adds the device ID to the right driver.

** Affects: hwe-next
 Importance: Undecided
 Status: Fix Released

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Jesse Sung (wenchien)
 Status: In Progress

** Affects: linux-oem (Ubuntu)
 Importance: Undecided
 Assignee: Jesse Sung (wenchien)
 Status: In Progress


** Tags: originate-from-1784578 plano

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

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

** Changed in: linux-oem (Ubuntu)
 Assignee: (unassigned) => Jesse Sung (wenchien)

** Tags added: originate-from-1784578 plano

** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  Add support for Dell DW5821e WWAN/GPS module

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem package in Ubuntu:
  In Progress

Bug description:
  == Impact ==
  DW5821e doesn't work in Bionic.

  == Fix ==
  Three commits are required to support it. All of them are already in the 
mainline kernel.

  == Test Case ==
  With the command
  $ sudo mmcli -L
  the device should be listed as a modem.

  == Risk of Regression ==
  Very low. it only adds the device ID to the right driver.

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

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


[Kernel-packages] [Bug 1807339] [NEW] Add HMS CAN driver for new Dell Edge Gateways

2018-12-06 Thread Jesse Sung
Public bug reported:

Need to integrate the driver released from the vendor.

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

** Affects: linux-oem (Ubuntu)
 Importance: Undecided
 Assignee: Jesse Sung (wenchien)
 Status: In Progress


** Tags: originate-from-1784570 plano

** Tags added: originate-from-1784570 plano

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

Title:
  Add HMS CAN driver for new Dell Edge Gateways

Status in HWE Next:
  New
Status in linux-oem package in Ubuntu:
  In Progress

Bug description:
  Need to integrate the driver released from the vendor.

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

-- 
Mailing list: https://launchpad.net/~kernel-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

2018-12-06 Thread Jesse Sung
** Changed in: hwe-next
   Status: New => Fix Released

-- 
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:
  In Progress
Status in linux-oem package in Ubuntu:
  In Progress

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 1807334] [NEW] Add support for ALC3277 codec on new Dell edge gateways

2018-12-06 Thread Jesse Sung
Public bug reported:

There are two audio jacks on the device, one for Line-in and the other
for Line-out.

Audio over these jacks is supported through Realtek ALC3277 (RT5660)
audio codec connected to the Processor/SoC over I2C. While the kernel
already has the driver for the Codec, we still need a machine driver to
connect audio FrontEnds provided by the Codec to the Intel SST Audio
BackEnds.

** Affects: hwe-next
 Importance: Undecided
 Assignee: Hui Wang (hui.wang)
 Status: In Progress

** Affects: linux-oem (Ubuntu)
 Importance: Undecided
 Assignee: Hui Wang (hui.wang)
 Status: In Progress


** Tags: originate-from-1792502 plano

** Tags added: originate-from-1792502 plano

** Changed in: hwe-next
   Status: New => In Progress

** Changed in: hwe-next
 Assignee: (unassigned) => Hui Wang (hui.wang)

-- 
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-oem package in Ubuntu:
  In Progress

Bug description:
  There are two audio jacks on the device, one for Line-in and the other
  for Line-out.

  Audio over these jacks is supported through Realtek ALC3277 (RT5660)
  audio codec connected to the Processor/SoC over I2C. While the kernel
  already has the driver for the Codec, we still need a machine driver
  to connect audio FrontEnds provided by the Codec to the Intel SST
  Audio BackEnds.

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 1807333] Re: Add support for 0cf3:535b QCA_ROME device

2018-12-06 Thread Jesse Sung
The commit is already in 4.20.

-- 
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:
  In Progress
Status in linux-oem package in Ubuntu:
  In Progress

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 1807333] [NEW] Add support for 0cf3:535b QCA_ROME device

2018-12-06 Thread Jesse Sung
Public bug reported:

== 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

** Affects: hwe-next
 Importance: Undecided
 Status: Fix Released

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Jesse Sung (wenchien)
 Status: In Progress

** Affects: linux-oem (Ubuntu)
 Importance: Undecided
 Assignee: Jesse Sung (wenchien)
 Status: In Progress


** Tags: originate-from-1806345 plano

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

** Changed in: linux-oem (Ubuntu)
 Assignee: (unassigned) => Jesse Sung (wenchien)

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

** Tags added: originate-from-1806345 plano

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

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

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem package in Ubuntu:
  In Progress

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 1803942] Re: System randomly hangs during suspend when mei_wdt is loaded

2018-11-28 Thread Jesse Sung
This is caused by 876dcb relies on dev->driver to tell if
__device_release_driver() was completed by other callers while calling
remove(). But drivers like mei_wdt will set dev->driver to NULL after
its remove() completes, thus it would do return instead of continuing
__device_release_driver().

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

Title:
  System randomly hangs during suspend when mei_wdt is loaded

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  Problem description:
  System randomly hangs during suspend when mei_wdt is loaded.

  Platform:
  Intel Dawson Canyon I5 (NUC7i5DNHE) and I7 (NUC7i7DNHE)

  Test procedure:
  1. Install Ubuntu 18.04 and do apt full-upgrade

  2. Enable mei_wdt:
  $ sudo modprobe mei_wdt

  3. Do system S3 test:
  $ sudo systemctl suspend
  or
  $ sudo rtcwake -v -m mem -s 15

  4. Afterward, I noticed that somehow system will hang during
  suspend/resume.

  Expect result:
  Suspend/resume won't impact system.

  Actual result:
  System will hang during S3 test.

  Additional info:
  - BIOS version: V57
  - Another i3 platform (NUC7i3DNHNC) doesn't have this issue.

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

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


[Kernel-packages] [Bug 1803942] Re: System randomly hangs during suspend when mei_wdt is loaded

2018-11-19 Thread Jesse Sung
** Tags added: dawson originate-from-1803076

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

Title:
  System randomly hangs during suspend when mei_wdt is loaded

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

Bug description:
  Problem description:
  System randomly hangs during suspend when mei_wdt is loaded.

  Platform:
  Intel Dawson Canyon I5 (NUC7i5DNHE) and I7 (NUC7i7DNHE)

  Test procedure:
  1. Install Ubuntu 18.04 and do apt full-upgrade

  2. Enable mei_wdt:
  $ sudo modprobe mei_wdt

  3. Do system S3 test:
  $ sudo systemctl suspend
  or
  $ sudo rtcwake -v -m mem -s 15

  4. Afterward, I noticed that somehow system will hang during
  suspend/resume.

  Expect result:
  Suspend/resume won't impact system.

  Actual result:
  System will hang during S3 test.

  Additional info:
  - BIOS version: V57
  - Another i3 platform (NUC7i3DNHNC) doesn't have this issue.

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

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


[Kernel-packages] [Bug 1803942] Re: System randomly hangs during suspend when mei_wdt is loaded

2018-11-18 Thread Jesse Sung
** 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/1803942

Title:
  System randomly hangs during suspend when mei_wdt is loaded

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Problem description:
  System randomly hangs during suspend when mei_wdt is loaded.

  Platform:
  Intel Dawson Canyon I5 (NUC7i5DNHE) and I7 (NUC7i7DNHE)

  Test procedure:
  1. Install Ubuntu 18.04 and do apt full-upgrade

  2. Enable mei_wdt:
  $ sudo modprobe mei_wdt

  3. Do system S3 test:
  $ sudo systemctl suspend
  or
  $ sudo rtcwake -v -m mem -s 15

  4. Afterward, I noticed that somehow system will hang during
  suspend/resume.

  Expect result:
  Suspend/resume won't impact system.

  Actual result:
  System will hang during S3 test.

  Additional info:
  - BIOS version: V57
  - Another i3 platform (NUC7i3DNHNC) doesn't have this issue.

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

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


[Kernel-packages] [Bug 1803335] Re: linux-headers-4.18.0-1004-azure contains links to non-existing targets

2018-11-15 Thread Jesse Sung
** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Jesse Sung (wenchien)

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

Title:
  linux-headers-4.18.0-1004-azure contains links to non-existing targets

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  $ ls /usr/src/linux-azure-edge-headers-4.18.0-1004
  ls: cannot access '/usr/src/linux-azure-edge-headers-4.18.0-1004': No such 
file or directory

  $ ll /usr/src/linux-headers-4.18.0-1004-azure
  total 1240
  drwxr-xr-x 8 root root   4096 Nov 14 11:19 ./
  drwxr-xr-x 5 root root   4096 Nov 14 11:19 ../
  -rw-r--r-- 1 root root 136487 Oct 25 13:59 .config
  -rw-r--r-- 1 root root 130326 Oct 25 13:59 .config.old
  -rw-r--r-- 1 root root   1229 Oct 25 13:59 .missing-syscalls.d
  drwxr-xr-x 2 root root   4096 Oct 25 13:59 .tmp_versions/
  lrwxrwxrwx 1 root root 53 Oct 25 13:59 Documentation -> 
../linux-azure-edge-headers-4.18.0-1004/Documentation
  lrwxrwxrwx 1 root root 46 Oct 25 13:59 Kbuild -> 
../linux-azure-edge-headers-4.18.0-1004/Kbuild
  lrwxrwxrwx 1 root root 47 Oct 25 13:59 Kconfig -> 
../linux-azure-edge-headers-4.18.0-1004/Kconfig
  lrwxrwxrwx 1 root root 48 Oct 25 13:59 Makefile -> 
../linux-azure-edge-headers-4.18.0-1004/Makefile
  -rw-r--r-- 1 root root 952862 Oct 25 13:59 Module.symvers
  drwxr-xr-x 3 root root   4096 Nov 14 11:19 arch/
  lrwxrwxrwx 1 root root 45 Oct 25 13:59 block -> 
../linux-azure-edge-headers-4.18.0-1004/block
  lrwxrwxrwx 1 root root 45 Oct 25 13:59 certs -> 
../linux-azure-edge-headers-4.18.0-1004/certs
  lrwxrwxrwx 1 root root 46 Oct 25 13:59 crypto -> 
../linux-azure-edge-headers-4.18.0-1004/crypto
  lrwxrwxrwx 1 root root 47 Oct 25 13:59 drivers -> 
../linux-azure-edge-headers-4.18.0-1004/drivers
  lrwxrwxrwx 1 root root 48 Oct 25 13:59 firmware -> 
../linux-azure-edge-headers-4.18.0-1004/firmware
  lrwxrwxrwx 1 root root 42 Oct 25 13:59 fs -> 
../linux-azure-edge-headers-4.18.0-1004/fs
  drwxr-xr-x 4 root root   4096 Nov 14 11:19 include/
  lrwxrwxrwx 1 root root 44 Oct 25 13:59 init -> 
../linux-azure-edge-headers-4.18.0-1004/init
  lrwxrwxrwx 1 root root 43 Oct 25 13:59 ipc -> 
../linux-azure-edge-headers-4.18.0-1004/ipc
  drwxr-xr-x 2 root root   4096 Nov 14 11:19 kernel/
  lrwxrwxrwx 1 root root 43 Oct 25 13:59 lib -> 
../linux-azure-edge-headers-4.18.0-1004/lib
  lrwxrwxrwx 1 root root 42 Oct 25 13:59 mm -> 
../linux-azure-edge-headers-4.18.0-1004/mm
  lrwxrwxrwx 1 root root 43 Oct 25 13:59 net -> 
../linux-azure-edge-headers-4.18.0-1004/net
  lrwxrwxrwx 1 root root 47 Oct 25 13:59 samples -> 
../linux-azure-edge-headers-4.18.0-1004/samples
  drwxr-xr-x 6 root root  12288 Nov 14 11:19 scripts/
  lrwxrwxrwx 1 root root 48 Oct 25 13:59 security -> 
../linux-azure-edge-headers-4.18.0-1004/security
  lrwxrwxrwx 1 root root 45 Oct 25 13:59 sound -> 
../linux-azure-edge-headers-4.18.0-1004/sound
  lrwxrwxrwx 1 root root 43 Oct 25 13:59 spl -> 
../linux-azure-edge-headers-4.18.0-1004/spl
  drwxr-xr-x 3 root root   4096 Nov 14 11:19 tools/
  lrwxrwxrwx 1 root root 46 Oct 25 13:59 ubuntu -> 
../linux-azure-edge-headers-4.18.0-1004/ubuntu
  lrwxrwxrwx 1 root root 43 Oct 25 13:59 usr -> 
../linux-azure-edge-headers-4.18.0-1004/usr
  lrwxrwxrwx 1 root root 44 Oct 25 13:59 virt -> 
../linux-azure-edge-headers-4.18.0-1004/virt
  lrwxrwxrwx 1 root root 43 Oct 25 13:59 zfs -> 
../linux-azure-edge-headers-4.18.0-1004/zfs

  $ uname -a
  Linux b-la-edge-azure-edge-4-18-0-Basic-A1-qrt-kernel-security 
4.18.0-1004-azure #4~18.04.1-Ubuntu SMP Thu Oct 25 14:25:41 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

  $ dpkg -l | grep header
  ii  execstack0.0.20131005-1   
   amd64ELF GNU_STACK program header editing utility
  ii  linux-azure-headers-4.15.0-1030  4.15.0-1030.31   
   all  Header files related to Linux kernel version 4.15.0
  ii  linux-azure-headers-4.18.0-1004  4.18.0-1004.4~18.04.1
   all  Header files related to Linux kernel version 4.18.0
  ii  linux-headers-4.15.0-1030-azure  4.15.0-1030.31   
   amd64Linux kernel headers for version 4.15.0 on 64 bit x86 
SMP
  ii  linux-headers-4.18.0-1004-azure  4.18.0-1004.4~18.04.1
   amd64Linux kernel headers for version 4.18.0 on 64 bit x86 
SMP
  ii  linux-headers-azure  4.15.0.1030.30   
   amd64Linux kernel headers for Azure systems.
  ii  linux-headers-azure-edge 4.18.0.1004.5
   amd64Linux kernel headers for Azure systems.


[Kernel-packages] [Bug 1802260] Re: Please include modules for NVMe and USB HID in pc-kernel snap initrd

2018-11-09 Thread Jesse Sung
** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Jesse Sung (wenchien)

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

Title:
  Please include modules for NVMe and USB HID in pc-kernel snap initrd

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When trying Ubuntu Core with the pc-kernel snap, the system showed
  'cannot find writable partition'. The system was stopped at the initrd
  stage and didn't accept any input.

  My system is using a NVMe disk and it seems the pc-kernel doesn't
  provide the related modules in its initrd. Also, it's not possible to
  enter the initramfs environment because of the lacking of USB HID
  modules.

  Is it possible to include these two categories of drivers in the
  initrd of pc-kernel, please?

  Verified both 4.4 and 4.15 (track 18) have the same issue.
  $ squashfuse pc-kernel_162.snap pc-kernel
  $ lsinitramfs pc-kernel/initrd.img |grep -E 'nvme|usbhid'
  [nothing is showed]
  $ fusermount -u pc-kernel
  $ squashfuse pc-kernel_165.snap pc-kernel
  $ lsinitramfs pc-kernel/initrd.img |grep -E 'nvme|usbhid'
  [nothing is showed]
  $ fusermount -u pc-kernel

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

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


[Kernel-packages] [Bug 1798332] Re: Support Edge Gateway's Bluetooth LED

2018-10-29 Thread Jesse Sung
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic

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

Title:
  Support Edge Gateway's Bluetooth LED

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  In Progress

Bug description:
  == Impact ==
  The Bluetooth LED of Marvell 88W8897 is not enabled by default (there's no 
code for controlling LED). It is requested to be ON and OFF when the radio is 
on and off accordingly.

  == Fix ==
  The LEDs are connected to GPIO pins on the Marvell WiFi/Bluetooth combo 
module, thus they can only be controlled via firmware.

  == Test Case ==
  # hciconfig hci0 [on|off]
  and see if the LEDs work properly.

  == Risk of Regression ==
  PCI sub IDs of the host bridge are used to determine if we're really running 
on an Edge Gateway, and we already have these patches in Xenial kernels quite a 
while. Risk should be reasonably low.

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

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


[Kernel-packages] [Bug 1798330] Re: Support Edge Gateway's WIFI LED

2018-10-29 Thread Jesse Sung
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic

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

Title:
  Support Edge Gateway's WIFI LED

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  In Progress

Bug description:
  == Impact ==
  The WIFI LED of Marvell 88W8897 is not enabled by default (there's no code 
for controlling LED in mwifiex). It is requested to be ON and OFF when the 
radio is on and off accordingly.

  == Fix ==
  The LEDs are connected to GPIO pins on the Marvell WiFi/Bluetooth combo 
module, thus they can only be controlled via firmware.

  == Test Case ==
  # ifconfig wlan0 [on|off]
  and see if the LEDs work properly.

  == Risk of Regression ==
  PCI sub IDs of the host bridge are used to determine if we're really running 
on an Edge Gateway, and we already have these patches in Xenial kernels quite a 
while. Risk should be reasonably low.

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

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


[Kernel-packages] [Bug 1798332] Re: Support Edge Gateway's Bluetooth LED

2018-10-25 Thread Jesse Sung
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  Support Edge Gateway's Bluetooth LED

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  In Progress

Bug description:
  == Impact ==
  The Bluetooth LED of Marvell 88W8897 is not enabled by default (there's no 
code for controlling LED). It is requested to be ON and OFF when the radio is 
on and off accordingly.

  == Fix ==
  The LEDs are connected to GPIO pins on the Marvell WiFi/Bluetooth combo 
module, thus they can only be controlled via firmware.

  == Test Case ==
  # hciconfig hci0 [on|off]
  and see if the LEDs work properly.

  == Risk of Regression ==
  PCI sub IDs of the host bridge are used to determine if we're really running 
on an Edge Gateway, and we already have these patches in Xenial kernels quite a 
while. Risk should be reasonably low.

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

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


[Kernel-packages] [Bug 1798330] Re: Support Edge Gateway's WIFI LED

2018-10-25 Thread Jesse Sung
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  Support Edge Gateway's WIFI LED

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  In Progress

Bug description:
  == Impact ==
  The WIFI LED of Marvell 88W8897 is not enabled by default (there's no code 
for controlling LED in mwifiex). It is requested to be ON and OFF when the 
radio is on and off accordingly.

  == Fix ==
  The LEDs are connected to GPIO pins on the Marvell WiFi/Bluetooth combo 
module, thus they can only be controlled via firmware.

  == Test Case ==
  # ifconfig wlan0 [on|off]
  and see if the LEDs work properly.

  == Risk of Regression ==
  PCI sub IDs of the host bridge are used to determine if we're really running 
on an Edge Gateway, and we already have these patches in Xenial kernels quite a 
while. Risk should be reasonably low.

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

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


[Kernel-packages] [Bug 1798330] [NEW] Support Edge Gateway's WIFI LED

2018-10-17 Thread Jesse Sung
Public bug reported:

== Impact ==
The WIFI LED of Marvell 88W8897 is not enabled by default (there's no code for 
controlling LED in mwifiex). It is requested to be ON and OFF when the radio is 
on and off accordingly.

== Fix ==
The LEDs are connected to GPIO pins on the Marvell WiFi/Bluetooth combo module, 
thus they can only be controlled via firmware.

== Test Case ==
# ifconfig wlan0 [on|off]
and see if the LEDs work properly.

== Risk of Regression ==
PCI sub IDs of the host bridge are used to determine if we're really running on 
an Edge Gateway, and we already have these patches in Xenial kernels quite a 
while. Risk should be reasonably low.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Jesse Sung (wenchien)
 Status: 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/1798330

Title:
  Support Edge Gateway's WIFI LED

Status in linux package in Ubuntu:
  In Progress

Bug description:
  == Impact ==
  The WIFI LED of Marvell 88W8897 is not enabled by default (there's no code 
for controlling LED in mwifiex). It is requested to be ON and OFF when the 
radio is on and off accordingly.

  == Fix ==
  The LEDs are connected to GPIO pins on the Marvell WiFi/Bluetooth combo 
module, thus they can only be controlled via firmware.

  == Test Case ==
  # ifconfig wlan0 [on|off]
  and see if the LEDs work properly.

  == Risk of Regression ==
  PCI sub IDs of the host bridge are used to determine if we're really running 
on an Edge Gateway, and we already have these patches in Xenial kernels quite a 
while. Risk should be reasonably low.

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

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


[Kernel-packages] [Bug 1798332] [NEW] Support Edge Gateway's Bluetooth LED

2018-10-17 Thread Jesse Sung
Public bug reported:

== Impact ==
The Bluetooth LED of Marvell 88W8897 is not enabled by default (there's no code 
for controlling LED). It is requested to be ON and OFF when the radio is on and 
off accordingly.

== Fix ==
The LEDs are connected to GPIO pins on the Marvell WiFi/Bluetooth combo module, 
thus they can only be controlled via firmware.

== Test Case ==
# hciconfig hci0 [on|off]
and see if the LEDs work properly.

== Risk of Regression ==
PCI sub IDs of the host bridge are used to determine if we're really running on 
an Edge Gateway, and we already have these patches in Xenial kernels quite a 
while. Risk should be reasonably low.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Jesse Sung (wenchien)
 Status: 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/1798332

Title:
  Support Edge Gateway's Bluetooth LED

Status in linux package in Ubuntu:
  In Progress

Bug description:
  == Impact ==
  The Bluetooth LED of Marvell 88W8897 is not enabled by default (there's no 
code for controlling LED). It is requested to be ON and OFF when the radio is 
on and off accordingly.

  == Fix ==
  The LEDs are connected to GPIO pins on the Marvell WiFi/Bluetooth combo 
module, thus they can only be controlled via firmware.

  == Test Case ==
  # hciconfig hci0 [on|off]
  and see if the LEDs work properly.

  == Risk of Regression ==
  PCI sub IDs of the host bridge are used to determine if we're really running 
on an Edge Gateway, and we already have these patches in Xenial kernels quite a 
while. Risk should be reasonably low.

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

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


[Kernel-packages] [Bug 1792309] Re: Fix I2C touchpanels' interrupt storms after system suspend

2018-09-13 Thread Jesse Sung
** Tags added: originate-from-1788106 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/1792309

Title:
  Fix I2C touchpanels' interrupt storms after system suspend

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

Bug description:
  [Impact]
  Some I2C touchpanels generate IRQ storm after system suspend/resume.

  [Test]
  After applying the fix, the IRQ storm stops generated by Raydium touchpanels.

  [Fix]
  Instead of requesting i2c reset, simply requesting the device to power on. 
The HID over I2C spec doesn't specify how the device should do upon resume from 
suspend, so some devices expect a power on instead of reset.

  [Regression Potential]
  Low. I tested other vendors' touchpanels, didn't observe any side effect.

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

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


[Kernel-packages] [Bug 1740231] Re: Add support for Realtek WiFi device [10ec:c821]

2018-09-12 Thread Jesse Sung
Unfortunately this won't make it to the bionic kernel. For 4.15, as a
temporary solution, please try
https://launchpad.net/~wenchien/+archive/ubuntu/rtl8821c .

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

Title:
  Add support for Realtek WiFi device [10ec:c821]

Status in HWE Next:
  Fix Released
Status in HWE Next bionic series:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  PCI ID: 10ec:c821

  The off-tree driver is attached.

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

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


[Kernel-packages] [Bug 1784835] Re: [Bionic] Bluetooth: Support RTL8723D and RTL8821C Devices

2018-09-12 Thread Jesse Sung
** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: hwe-next
   Status: In Progress => Fix Released

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

Title:
  [Bionic] Bluetooth: Support RTL8723D and RTL8821C Devices

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  SRU Justification

  * Impact:
  These devices can be found in some laptops. They don't work with the btusb in 
bionic but still the btusb would be loaded.

  * Fix:
  There's a commit in upstream that makes btusb support these devices.

  commit 907f84990924bf3a8d248c040dabeb5127ae6938
  Author: Alex Lu 
  Date:   Sun Feb 11 12:24:33 2018 -0600

  Bluetooth: btrtl: Add RTL8723D and RTL8821C devices
  
  The Bluetooth parts of RTL8723D and RTL8723B share the same lmp
  subversion, thus we need to check both lmp subversion and hci revision
  to distinguish the two. The same situation is true for RTL8821A and
  RTL8821C. Accordingly, the selection code is revised.
  
  To improve maintainability, a new id_table struct is defined, and an
  array of such structs is constructed. Adding a new device can thus be
  as simple as adding another value to the table.
  
  Signed-off-by: Alex Lu 
  Signed-off-by: Larry Finger 
  Signed-off-by: Marcel Holtmann 

  * Risk of Regression:
  It's just one clean cherry-pick from upstream to extend devices supported by 
btrtl. The potential risk should be low.

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

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


[Kernel-packages] [Bug 1784835] Re: [Bionic] Bluetooth: Support RTL8723D and RTL8821C Devices

2018-09-04 Thread Jesse Sung
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  [Bionic] Bluetooth: Support RTL8723D and RTL8821C Devices

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  SRU Justification

  * Impact:
  These devices can be found in some laptops. They don't work with the btusb in 
bionic but still the btusb would be loaded.

  * Fix:
  There's a commit in upstream that makes btusb support these devices.

  commit 907f84990924bf3a8d248c040dabeb5127ae6938
  Author: Alex Lu 
  Date:   Sun Feb 11 12:24:33 2018 -0600

  Bluetooth: btrtl: Add RTL8723D and RTL8821C devices
  
  The Bluetooth parts of RTL8723D and RTL8723B share the same lmp
  subversion, thus we need to check both lmp subversion and hci revision
  to distinguish the two. The same situation is true for RTL8821A and
  RTL8821C. Accordingly, the selection code is revised.
  
  To improve maintainability, a new id_table struct is defined, and an
  array of such structs is constructed. Adding a new device can thus be
  as simple as adding another value to the table.
  
  Signed-off-by: Alex Lu 
  Signed-off-by: Larry Finger 
  Signed-off-by: Marcel Holtmann 

  * Risk of Regression:
  It's just one clean cherry-pick from upstream to extend devices supported by 
btrtl. The potential risk should be low.

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

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


[Kernel-packages] [Bug 1780066] Re: [Bionic] Disk IO hangs when using BFQ as io scheduler

2018-08-07 Thread Jesse Sung
** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Committed

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

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

Title:
  [Bionic] Disk IO hangs when using BFQ as io scheduler

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

Bug description:
  When BFQ is used, disk IO will hang some seconds after boot. This was
  also reported in some public MLs [1][2]. The fix is already in
  mainline, but it's not available in 4.15.

  [1] https://lkml.org/lkml/2017/12/1/80
  [2] https://groups.google.com/forum/#!topic/bfq-iosched/nB2cVfDMSOU

  == SRU Justification ==

  Impact:
  Disk IO hangs several seconds after booting with a bionic Ubuntu kernel

  Fix:
  Three patches are cherry-picked for SRU. "block, bfq: add requeue-request 
hook" is the fix, while the other two are cleanups and make the whole fixes 
clean cherry-picks.

  Testcase:
  Boot the kernel with BFQ as IO scheduler.

  Risk of Regression:
  Clean cherry-picks from upstream so the risk should be fairly low.

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

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


[Kernel-packages] [Bug 1784835] [NEW] [Bionic] Bluetooth: Support RTL8723D and RTL8821C Devices

2018-08-01 Thread Jesse Sung
Public bug reported:

SRU Justification

* Impact:
These devices can be found in some laptops. They don't work with the btusb in 
bionic but still the btusb would be loaded.

* Fix:
There's a commit in upstream that makes btusb support these devices.

commit 907f84990924bf3a8d248c040dabeb5127ae6938
Author: Alex Lu 
Date:   Sun Feb 11 12:24:33 2018 -0600

Bluetooth: btrtl: Add RTL8723D and RTL8821C devices

The Bluetooth parts of RTL8723D and RTL8723B share the same lmp
subversion, thus we need to check both lmp subversion and hci revision
to distinguish the two. The same situation is true for RTL8821A and
RTL8821C. Accordingly, the selection code is revised.

To improve maintainability, a new id_table struct is defined, and an
array of such structs is constructed. Adding a new device can thus be
as simple as adding another value to the table.

Signed-off-by: Alex Lu 
Signed-off-by: Larry Finger 
Signed-off-by: Marcel Holtmann 

* Risk of Regression:
It's just one clean cherry-pick from upstream to extend devices supported by 
btrtl. The potential risk should be low.

** Affects: hwe-next
 Importance: Undecided
 Assignee: Jesse Sung (wenchien)
 Status: In Progress

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Jesse Sung (wenchien)
 Status: In Progress


** Tags: originate-from-1783463 stella

** Tags added: originate-from-1783463 stella

** Changed in: hwe-next
 Assignee: (unassigned) => Jesse Sung (wenchien)

** Changed in: hwe-next
   Status: New => 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/1784835

Title:
  [Bionic] Bluetooth: Support RTL8723D and RTL8821C Devices

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  SRU Justification

  * Impact:
  These devices can be found in some laptops. They don't work with the btusb in 
bionic but still the btusb would be loaded.

  * Fix:
  There's a commit in upstream that makes btusb support these devices.

  commit 907f84990924bf3a8d248c040dabeb5127ae6938
  Author: Alex Lu 
  Date:   Sun Feb 11 12:24:33 2018 -0600

  Bluetooth: btrtl: Add RTL8723D and RTL8821C devices
  
  The Bluetooth parts of RTL8723D and RTL8723B share the same lmp
  subversion, thus we need to check both lmp subversion and hci revision
  to distinguish the two. The same situation is true for RTL8821A and
  RTL8821C. Accordingly, the selection code is revised.
  
  To improve maintainability, a new id_table struct is defined, and an
  array of such structs is constructed. Adding a new device can thus be
  as simple as adding another value to the table.
  
  Signed-off-by: Alex Lu 
  Signed-off-by: Larry Finger 
  Signed-off-by: Marcel Holtmann 

  * Risk of Regression:
  It's just one clean cherry-pick from upstream to extend devices supported by 
btrtl. The potential risk should be low.

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

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


[Kernel-packages] [Bug 1780066] Re: [Bionic] Disk IO hangs when using BFQ as io scheduler

2018-07-30 Thread Jesse Sung
** Description changed:

  When BFQ is used, disk IO will hang some seconds after boot. This was
  also reported in some public MLs [1][2]. The fix is already in mainline,
  but it's not available in 4.15.
  
  [1] https://lkml.org/lkml/2017/12/1/80
  [2] https://groups.google.com/forum/#!topic/bfq-iosched/nB2cVfDMSOU
  
- 
  == SRU Justification ==
  
- Three patches are cherry-picked for SRU. "block, bfq: add requeue-
- request hook" is the fix, while the other two are cleanups and make the
- whole fixes clean cherry-picks.
+ Impact:
+ Disk IO hangs several seconds after booting with a bionic Ubuntu kernel
+ 
+ Fix:
+ Three patches are cherry-picked for SRU. "block, bfq: add requeue-request 
hook" is the fix, while the other two are cleanups and make the whole fixes 
clean cherry-picks.
+ 
+ Testcase:
+ Boot the kernel with BFQ as IO scheduler.
+ 
+ Risk of Regression:
+ Clean cherry-picks from upstream so the risk should be fairly low.

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

Title:
  [Bionic] Disk IO hangs when using BFQ as io scheduler

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  New

Bug description:
  When BFQ is used, disk IO will hang some seconds after boot. This was
  also reported in some public MLs [1][2]. The fix is already in
  mainline, but it's not available in 4.15.

  [1] https://lkml.org/lkml/2017/12/1/80
  [2] https://groups.google.com/forum/#!topic/bfq-iosched/nB2cVfDMSOU

  == SRU Justification ==

  Impact:
  Disk IO hangs several seconds after booting with a bionic Ubuntu kernel

  Fix:
  Three patches are cherry-picked for SRU. "block, bfq: add requeue-request 
hook" is the fix, while the other two are cleanups and make the whole fixes 
clean cherry-picks.

  Testcase:
  Boot the kernel with BFQ as IO scheduler.

  Risk of Regression:
  Clean cherry-picks from upstream so the risk should be fairly low.

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

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


[Kernel-packages] [Bug 1780066] Re: [Bionic] Disk IO hangs when using BFQ as io scheduler

2018-07-27 Thread Jesse Sung
** Description changed:

  When BFQ is used, disk IO will hang some seconds after boot. This was
  also reported in some public MLs [1][2]. The fix is already in mainline,
  but it's not available in 4.15.
  
  [1] https://lkml.org/lkml/2017/12/1/80
  [2] https://groups.google.com/forum/#!topic/bfq-iosched/nB2cVfDMSOU
+ 
+ 
+ == SRU Justification ==
+ 
+ Three patches are cherry-picked for SRU. "block, bfq: add requeue-
+ request hook" is the fix, while the other two are cleanups and make the
+ whole fixes clean cherry-picks.

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

Title:
  [Bionic] Disk IO hangs when using BFQ as io scheduler

Status in linux package in Ubuntu:
  In Progress

Bug description:
  When BFQ is used, disk IO will hang some seconds after boot. This was
  also reported in some public MLs [1][2]. The fix is already in
  mainline, but it's not available in 4.15.

  [1] https://lkml.org/lkml/2017/12/1/80
  [2] https://groups.google.com/forum/#!topic/bfq-iosched/nB2cVfDMSOU

  
  == SRU Justification ==

  Three patches are cherry-picked for SRU. "block, bfq: add requeue-
  request hook" is the fix, while the other two are cleanups and make
  the whole fixes clean cherry-picks.

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

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


[Kernel-packages] [Bug 1780066] [NEW] [Bionic] Disk IO hangs when using BFQ as io scheduler

2018-07-04 Thread Jesse Sung
Public bug reported:

When BFQ is used, disk IO will hang some seconds after boot. This was
also reported in some public MLs [1][2]. The fix is already in mainline,
but it's not available in 4.15.

[1] https://lkml.org/lkml/2017/12/1/80
[2] https://groups.google.com/forum/#!topic/bfq-iosched/nB2cVfDMSOU

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Jesse Sung (wenchien)
 Status: 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/1780066

Title:
  [Bionic] Disk IO hangs when using BFQ as io scheduler

Status in linux package in Ubuntu:
  In Progress

Bug description:
  When BFQ is used, disk IO will hang some seconds after boot. This was
  also reported in some public MLs [1][2]. The fix is already in
  mainline, but it's not available in 4.15.

  [1] https://lkml.org/lkml/2017/12/1/80
  [2] https://groups.google.com/forum/#!topic/bfq-iosched/nB2cVfDMSOU

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

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


[Kernel-packages] [Bug 1769671] Re: [Xenial] Kernels OOPS when mwifiex is in AP mode

2018-07-04 Thread Jesse Sung
** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [Xenial] Kernels OOPS when mwifiex is in AP mode

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

Bug description:
  There's quite a chance to find kernel oops when mwifiex is in AP mode.
  Previously two workaround commits were added in the Xenial kernel,
  8a034f97a28dba62026343eef7992766c91273a7 and
  f21d12781c88413aec7ee44983f05b1cdf90662f, to mitigate this issue. The
  original report can be found at
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1712746 .

  Now that a fix has been merged in mainline, it's time to revert the
  workaround and apply the fix:

  commit c61cfe49f0f0f0d1f8b56d0b045838d597e8c3a3
  Author: Limin Zhu 
  Date:   Thu Nov 30 14:22:34 2017 +0800

  mwifiex: cfg80211: do not change virtual interface during scan processing
  
  (1) Change virtual interface operation in cfg80211 process reset and
  reinitilize private data structure.
  (2) Scan result event processed in main process will dereference private
  data structure concurrently, ocassionly crash the kernel.
  
  The cornel case could be trigger by below steps:
  (1) wpa_cli mlan0 scan
  (2) ./hostapd mlan0.conf
  
  Cfg80211 asynchronous scan procedure is not all the time operated
  under rtnl lock, here we add the protect to serialize the cfg80211
  scan and change_virtual interface operation.
  
  Signed-off-by: Limin Zhu 
  Signed-off-by: Xinming Hu 
  Signed-off-by: Kalle Valo 

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

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


[Kernel-packages] [Bug 1771919] Re: Support Realtek Bluetooth [0bda:c024]

2018-06-14 Thread Jesse Sung
** Changed in: linux-oem (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Support Realtek Bluetooth [0bda:c024]

Status in HWE Next:
  New
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  The driver rtk-btusb is already in ubuntu/rtl8821ce-bt. All we need to
  support this device is to add the ID to the driver and blacklist it in
  btusb.

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

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


[Kernel-packages] [Bug 1483101] Re: Broadcom bluetooth modules sometimes fail to initialize

2018-06-08 Thread Jesse Sung
@jason108:

This patch has been landed in upstream since 4.11, so, yes, we have it
in bionic.

>From the log in askubuntu, there's a line:
"[   31.964068] Bluetooth: hci0: BCM: Patch command 0a0a failed (-110)"
This indicates that something goes wrong when the driver is sending firmware to 
the module. It is different from the bug we have here.

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

Title:
  Broadcom bluetooth modules sometimes fail to initialize

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  This message can be found in dmesg:
  [ 15.080247] Bluetooth: hci0 command 0x1001 tx timeout

  Currently known affected modules:
  * 0a5c:216a
  * 0a5c:6410
  * 0a5c:6412

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

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


[Kernel-packages] [Bug 1769671] Re: [Xenial] Kernels OOPS when mwifiex is in AP mode

2018-05-30 Thread Jesse Sung
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  [Xenial] Kernels OOPS when mwifiex is in AP mode

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  There's quite a chance to find kernel oops when mwifiex is in AP mode.
  Previously two workaround commits were added in the Xenial kernel,
  8a034f97a28dba62026343eef7992766c91273a7 and
  f21d12781c88413aec7ee44983f05b1cdf90662f, to mitigate this issue. The
  original report can be found at
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1712746 .

  Now that a fix has been merged in mainline, it's time to revert the
  workaround and apply the fix:

  commit c61cfe49f0f0f0d1f8b56d0b045838d597e8c3a3
  Author: Limin Zhu 
  Date:   Thu Nov 30 14:22:34 2017 +0800

  mwifiex: cfg80211: do not change virtual interface during scan processing
  
  (1) Change virtual interface operation in cfg80211 process reset and
  reinitilize private data structure.
  (2) Scan result event processed in main process will dereference private
  data structure concurrently, ocassionly crash the kernel.
  
  The cornel case could be trigger by below steps:
  (1) wpa_cli mlan0 scan
  (2) ./hostapd mlan0.conf
  
  Cfg80211 asynchronous scan procedure is not all the time operated
  under rtnl lock, here we add the protect to serialize the cfg80211
  scan and change_virtual interface operation.
  
  Signed-off-by: Limin Zhu 
  Signed-off-by: Xinming Hu 
  Signed-off-by: Kalle Valo 

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

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


[Kernel-packages] [Bug 1771919] Re: Support Realtek Bluetooth [0bda:c024]

2018-05-17 Thread Jesse Sung
** Tags added: originate-from-1765295 sutton

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

Title:
  Support Realtek Bluetooth [0bda:c024]

Status in HWE Next:
  New
Status in linux-oem package in Ubuntu:
  In Progress

Bug description:
  The driver rtk-btusb is already in ubuntu/rtl8821ce-bt. All we need to
  support this device is to add the ID to the driver and blacklist it in
  btusb.

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

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


[Kernel-packages] [Bug 1771919] [NEW] Support Realtek Bluetooth [0bda:c024]

2018-05-17 Thread Jesse Sung
Public bug reported:

The driver rtk-btusb is already in ubuntu/rtl8821ce-bt. All we need to
support this device is to add the ID to the driver and blacklist it in
btusb.

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

** Affects: linux-oem (Ubuntu)
 Importance: Undecided
 Assignee: Jesse Sung (wenchien)
 Status: In Progress


** Tags: originate-from-1765295 sutton

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

Title:
  Support Realtek Bluetooth [0bda:c024]

Status in HWE Next:
  New
Status in linux-oem package in Ubuntu:
  In Progress

Bug description:
  The driver rtk-btusb is already in ubuntu/rtl8821ce-bt. All we need to
  support this device is to add the ID to the driver and blacklist it in
  btusb.

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

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


[Kernel-packages] [Bug 1769671] Re: [Xenial] Kernels OOPS when mwifiex is in AP mode

2018-05-07 Thread Jesse Sung
This fix has been merged in bionic/master via the stable update 4.15.11
so only Xenial is affected.

** Summary changed:

- [Xenial/Bionic] Kernels OOPS when mwifiex is in AP mode
+ [Xenial] Kernels OOPS when mwifiex is in AP mode

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

Title:
  [Xenial] Kernels OOPS when mwifiex is in AP mode

Status in linux package in Ubuntu:
  In Progress

Bug description:
  There's quite a chance to find kernel oops when mwifiex is in AP mode.
  Previously two workaround commits were added in the Xenial kernel,
  8a034f97a28dba62026343eef7992766c91273a7 and
  f21d12781c88413aec7ee44983f05b1cdf90662f, to mitigate this issue. The
  original report can be found at
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1712746 .

  Now that a fix has been merged in mainline, it's time to revert the
  workaround and apply the fix:

  commit c61cfe49f0f0f0d1f8b56d0b045838d597e8c3a3
  Author: Limin Zhu 
  Date:   Thu Nov 30 14:22:34 2017 +0800

  mwifiex: cfg80211: do not change virtual interface during scan processing
  
  (1) Change virtual interface operation in cfg80211 process reset and
  reinitilize private data structure.
  (2) Scan result event processed in main process will dereference private
  data structure concurrently, ocassionly crash the kernel.
  
  The cornel case could be trigger by below steps:
  (1) wpa_cli mlan0 scan
  (2) ./hostapd mlan0.conf
  
  Cfg80211 asynchronous scan procedure is not all the time operated
  under rtnl lock, here we add the protect to serialize the cfg80211
  scan and change_virtual interface operation.
  
  Signed-off-by: Limin Zhu 
  Signed-off-by: Xinming Hu 
  Signed-off-by: Kalle Valo 

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

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


[Kernel-packages] [Bug 1769671] [NEW] [Xenial] Kernels OOPS when mwifiex is in AP mode

2018-05-07 Thread Jesse Sung
Public bug reported:

There's quite a chance to find kernel oops when mwifiex is in AP mode.
Previously two workaround commits were added in the Xenial kernel,
8a034f97a28dba62026343eef7992766c91273a7 and
f21d12781c88413aec7ee44983f05b1cdf90662f, to mitigate this issue. The
original report can be found at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1712746 .

Now that a fix has been merged in mainline, it's time to revert the
workaround and apply the fix:

commit c61cfe49f0f0f0d1f8b56d0b045838d597e8c3a3
Author: Limin Zhu <limin...@marvell.com>
Date:   Thu Nov 30 14:22:34 2017 +0800

mwifiex: cfg80211: do not change virtual interface during scan processing

(1) Change virtual interface operation in cfg80211 process reset and
reinitilize private data structure.
(2) Scan result event processed in main process will dereference private
data structure concurrently, ocassionly crash the kernel.

The cornel case could be trigger by below steps:
(1) wpa_cli mlan0 scan
(2) ./hostapd mlan0.conf

Cfg80211 asynchronous scan procedure is not all the time operated
under rtnl lock, here we add the protect to serialize the cfg80211
scan and change_virtual interface operation.

Signed-off-by: Limin Zhu <limin...@marvell.com>
Signed-off-by: Xinming Hu <h...@marvell.com>
Signed-off-by: Kalle Valo <kv...@codeaurora.org>

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Jesse Sung (wenchien)
 Status: 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/1769671

Title:
  [Xenial] Kernels OOPS when mwifiex is in AP mode

Status in linux package in Ubuntu:
  In Progress

Bug description:
  There's quite a chance to find kernel oops when mwifiex is in AP mode.
  Previously two workaround commits were added in the Xenial kernel,
  8a034f97a28dba62026343eef7992766c91273a7 and
  f21d12781c88413aec7ee44983f05b1cdf90662f, to mitigate this issue. The
  original report can be found at
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1712746 .

  Now that a fix has been merged in mainline, it's time to revert the
  workaround and apply the fix:

  commit c61cfe49f0f0f0d1f8b56d0b045838d597e8c3a3
  Author: Limin Zhu <limin...@marvell.com>
  Date:   Thu Nov 30 14:22:34 2017 +0800

  mwifiex: cfg80211: do not change virtual interface during scan processing
  
  (1) Change virtual interface operation in cfg80211 process reset and
  reinitilize private data structure.
  (2) Scan result event processed in main process will dereference private
  data structure concurrently, ocassionly crash the kernel.
  
  The cornel case could be trigger by below steps:
  (1) wpa_cli mlan0 scan
  (2) ./hostapd mlan0.conf
  
  Cfg80211 asynchronous scan procedure is not all the time operated
  under rtnl lock, here we add the protect to serialize the cfg80211
  scan and change_virtual interface operation.
  
  Signed-off-by: Limin Zhu <limin...@marvell.com>
  Signed-off-by: Xinming Hu <h...@marvell.com>
  Signed-off-by: Kalle Valo <kv...@codeaurora.org>

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

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


[Kernel-packages] [Bug 1733281] Re: ubuntu/xr-usb-serial didn't get built in zesty and artful

2018-04-09 Thread Jesse Sung
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful

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

Title:
  ubuntu/xr-usb-serial didn't get built in zesty and artful

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Fix Committed
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-azure-edge source package in Artful:
  Invalid

Bug description:
  The ubuntu/xr-usb-serial is expected to be built for i386 and x86_64,
  and in ubuntu/Makefile it says:

  ifneq ($(filter $(ARCH), i386 x86_64),)
  obj-y += xr-usb-serial/
  endif

  Since ARCH is x86 for both i386 and x86_64, this condition will never
  be true thus the module will never get a chance to be built.

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

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


[Kernel-packages] [Bug 1736393] Re: [Artful][Wyse 3040] System hang when trying to enable an offlined CPU core

2018-04-03 Thread Jesse Sung
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful

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

Title:
  [Artful][Wyse 3040] System hang when trying to enable an offlined CPU
  core

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

Bug description:
  1. disable cpu[1-3] $ echo 0 > /sys/devices/system/cpu/cpu[1-3]/online
  2. enable cpu[1-3] $ echo 1 > /sys/devices/system/cpu/cpu[1-3]/online

  System will hang on step 2.

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

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


[Kernel-packages] [Bug 1744077] Re: $(LOCAL_ENV_CC) and $(LOCAL_ENV_DISTCC_HOSTS) should be properly quoted

2018-04-03 Thread Jesse Sung
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  $(LOCAL_ENV_CC) and $(LOCAL_ENV_DISTCC_HOSTS) should be properly
  quoted

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  Kernel will fail to build if there's a space in either $(LOCAL_ENV_CC)
  or $(LOCAL_ENV_DISTCC_HOSTS), for example if someone trying to use
  LOCAL_ENV_CC="ccache gcc".

  This is caused by the line in debian/rules.d/0-common-vars.mk which both of 
them are passed without quote:
  kmake += CC=$(LOCAL_ENV_CC) DISTCC_HOSTS=$(LOCAL_ENV_DISTCC_HOSTS)

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

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


[Kernel-packages] [Bug 1744058] Re: [Artful] Realtek ALC225: 2 secs noise when a headset plugged in

2018-04-03 Thread Jesse Sung
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful

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

Title:
  [Artful] Realtek ALC225: 2 secs noise when a headset plugged in

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Fix Committed

Bug description:
  There is a noise last for about 2 secs when a headset is plugged in.

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

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


[Kernel-packages] [Bug 1744077] Re: $(LOCAL_ENV_CC) and $(LOCAL_ENV_DISTCC_HOSTS) should be properly quoted

2018-04-03 Thread Jesse Sung
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful

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

Title:
  $(LOCAL_ENV_CC) and $(LOCAL_ENV_DISTCC_HOSTS) should be properly
  quoted

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  Kernel will fail to build if there's a space in either $(LOCAL_ENV_CC)
  or $(LOCAL_ENV_DISTCC_HOSTS), for example if someone trying to use
  LOCAL_ENV_CC="ccache gcc".

  This is caused by the line in debian/rules.d/0-common-vars.mk which both of 
them are passed without quote:
  kmake += CC=$(LOCAL_ENV_CC) DISTCC_HOSTS=$(LOCAL_ENV_DISTCC_HOSTS)

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

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


[Kernel-packages] [Bug 1725154] Re: mwifiex cannot connect to wifi AP when keeping wireless connection idle for more than 60 seconds

2018-03-26 Thread Jesse Sung
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  mwifiex cannot connect to wifi AP when keeping wireless connection
  idle for more than 60 seconds

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  New
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  Issue happens every time we get connected to any WPA network and stay
  idle for more than 60 seconds.

  We are working with upstream for a real fix:
  https://www.spinics.net/lists/linux-wireless/msg167017.html, please
  don't triage.

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

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


[Kernel-packages] [Bug 1733281] Re: ubuntu/xr-usb-serial didn't get built in zesty and artful

2018-01-23 Thread Jesse Sung
** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  ubuntu/xr-usb-serial didn't get built in zesty and artful

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

Bug description:
  The ubuntu/xr-usb-serial is expected to be built for i386 and x86_64,
  and in ubuntu/Makefile it says:

  ifneq ($(filter $(ARCH), i386 x86_64),)
  obj-y += xr-usb-serial/
  endif

  Since ARCH is x86 for both i386 and x86_64, this condition will never
  be true thus the module will never get a chance to be built.

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

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


[Kernel-packages] [Bug 1736393] Re: [Artful][Wyse 3040] System hang when trying to enable an offlined CPU core

2018-01-23 Thread Jesse Sung
** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [Artful][Wyse 3040] System hang when trying to enable an offlined CPU
  core

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  1. disable cpu[1-3] $ echo 0 > /sys/devices/system/cpu/cpu[1-3]/online
  2. enable cpu[1-3] $ echo 1 > /sys/devices/system/cpu/cpu[1-3]/online

  System will hang on step 2.

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

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


[Kernel-packages] [Bug 1744077] [NEW] $(LOCAL_ENV_CC) and $(LOCAL_ENV_DISTCC_HOSTS) should be properly quoted

2018-01-18 Thread Jesse Sung
Public bug reported:

Kernel will fail to build if there's a space in either $(LOCAL_ENV_CC)
or $(LOCAL_ENV_DISTCC_HOSTS), for example if someone trying to use
LOCAL_ENV_CC="ccache gcc".

This is caused by the line in debian/rules.d/0-common-vars.mk which both of 
them are passed without quote:
kmake += CC=$(LOCAL_ENV_CC) DISTCC_HOSTS=$(LOCAL_ENV_DISTCC_HOSTS)

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Jesse Sung (wenchien)
 Status: 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/1744077

Title:
  $(LOCAL_ENV_CC) and $(LOCAL_ENV_DISTCC_HOSTS) should be properly
  quoted

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Kernel will fail to build if there's a space in either $(LOCAL_ENV_CC)
  or $(LOCAL_ENV_DISTCC_HOSTS), for example if someone trying to use
  LOCAL_ENV_CC="ccache gcc".

  This is caused by the line in debian/rules.d/0-common-vars.mk which both of 
them are passed without quote:
  kmake += CC=$(LOCAL_ENV_CC) DISTCC_HOSTS=$(LOCAL_ENV_DISTCC_HOSTS)

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

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


[Kernel-packages] [Bug 1744058] [NEW] [Artful] Realtek ALC225: 2 secs noise when a headset plugged in

2018-01-18 Thread Jesse Sung
Public bug reported:

There is a noise last for about 2 secs when a headset is plugged in.

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

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Jesse Sung (wenchien)
 Status: In Progress


** Tags: carson originate-from-1741466

** Tags added: carson originate-from-1741466

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

Title:
  [Artful] Realtek ALC225: 2 secs noise when a headset plugged in

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  There is a noise last for about 2 secs when a headset is plugged in.

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

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


[Kernel-packages] [Bug 1712746] Re: mwifiex causes kernel oops when AP mode is enabled

2017-12-20 Thread Jesse Sung
** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: hwe-next
   Status: In Progress => Fix Released

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

Title:
  mwifiex causes kernel oops when AP mode is enabled

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  When it's in AP mode, there's quite a chance to find kernel oops
  during reboot.

  This is caused by the wiphy may be NULL for some reason. It's likely a
  bug in mwifiex. We've already pinged Marvell and Murata. Before
  there's a real fix available, we should check wiphy before accessing
  it.

  I've tried a 4.13-rc6 kernel. Though it has oops for NULL pointer
  deference too, it happens in a different function in mwifiex. Thus the
  workaround for Xenial may or may not help for other series. Will need
  to reproduce this issue with Zesty and then we can decide whether this
  workaround should be applied to Zesty.

  [   30.701441] BUG: unable to handle kernel NULL pointer dereference at 
00f0
  [   30.709511] IP: [] mwifiex_get_cfp+0x49/0x150 [mwifiex]
  [   30.716494] PGD 0
  [   30.718575] Oops:  [#1] SMP
  [   30.721918] Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conni
  [   30.836915] CPU: 1 PID: 679 Comm: kworker/u5:0 Not tainted 
4.4.0-57-generic #78-Ubuntu
  [   30.845018] Hardware name: Dell Inc. Edge Gateway 5000/  , BIOS 
01.05.00 10/18/2016
  [   30.853218] Workqueue: MWIFIEX_WORK_QUEUE mwifiex_main_work_queue [mwifiex]
  [   30.860362] task: 880077c11980 ti: 880075e48000 task.ti: 
880075e48000
  [   30.868018] RIP: 0010:[]  [] 
mwifiex_get_cfp+0x49/0x150 [mwifiex]
  [   30.877484] RSP: 0018:880075e4bbf8  EFLAGS: 00010202
  [   30.882920] RAX:  RBX: 0004 RCX: 
0004
  [   30.890221] RDX: 001000110010 RSI: 0004 RDI: 
0004
  [   30.897520] RBP: 880075e4bc28 R08: 0003 R09: 
0001
  [   30.904821] R10: 0001 R11: 02ff R12: 
0095
  [   30.912123] R13:  R14: 880075e4 R15: 
0095
  [   30.919425] FS:  () GS:88007130() 
knlGS:
  [   30.927701] CS:  0010 DS:  ES:  CR0: 8005003b
  [   30.933581] CR2: 00f0 CR3: 01e0a000 CR4: 
001006e0
  [   30.940882] Stack:
  [   30.942944]  0118 880075e4 8800750c4000 
880075e3ed59
  [   30.950592]  0095 880075e3ee01 880075e4bcd0 
c05846fc
  [   30.958232]   880075e4bc50 8140bcb5 
880075e4bc70
  [   30.965873] Call Trace:
  [   30.968397]  [] 
mwifiex_parse_single_response_buf+0x1fc/0x560 [mwifiex]
  [   30.976772]  [] ? find_next_bit+0x15/0x20
  [   30.982490]  [] 
mwifiex_handle_event_ext_scan_report+0x15c/0x340 [mwifiex]
  [   30.991139]  [] mwifiex_process_sta_event+0x276/0xb40 
[mwifiex]
  [   30.998806]  [] mwifiex_process_event+0x102/0x1c0 
[mwifiex]
  [   31.006120]  [] mwifiex_main_process+0x5de/0x8d0 
[mwifiex]
  [   31.013346]  [] mwifiex_main_work_queue+0x1f/0x30 
[mwifiex]
  [   31.020650]  [] process_one_work+0x165/0x480
  [   31.026624]  [] worker_thread+0x4b/0x4c0
  [   31.032240]  [] ? process_one_work+0x480/0x480
  [   31.038387]  [] kthread+0xd8/0xf0
  [   31.043384]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [   31.050071]  [] ret_from_fork+0x3f/0x70
  [   31.055596]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [   31.062276] Code: 85 c9 0f 84 ef 00 00 00 40 0f b6 de 49 89 fe 41 89 cd 89 
df 41 89 d4 e8 46 f1 00 00 84 c0 49 8b 86 e0 13 00 00 0f 84 98 00
  [   31.082756] RIP  [] mwifiex_get_cfp+0x49/0x150 [mwifiex]
  [   31.089820]  RSP 
  [   31.093392] CR2: 00f0
  [   31.096787] ---[ end trace f3a762be5787f138 ]---

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

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


[Kernel-packages] [Bug 1736393] Re: [Artful][Wyse 3040] System hang when trying to enable an offlined CPU core

2017-12-05 Thread Jesse Sung
** Tags added: carson originate-from-1703492

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

Title:
  [Artful][Wyse 3040] System hang when trying to enable an offlined CPU
  core

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  1. disable cpu[1-3] $ echo 0 > /sys/devices/system/cpu/cpu[1-3]/online
  2. enable cpu[1-3] $ echo 1 > /sys/devices/system/cpu/cpu[1-3]/online

  System will hang on step 2.

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

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


[Kernel-packages] [Bug 1736393] [NEW] [Artful][Wyse 3040] System hang when trying to enable an offlined CPU core

2017-12-05 Thread Jesse Sung
Public bug reported:

1. disable cpu[1-3] $ echo 0 > /sys/devices/system/cpu/cpu[1-3]/online
2. enable cpu[1-3] $ echo 1 > /sys/devices/system/cpu/cpu[1-3]/online

System will hang on step 2.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Jesse Sung (wenchien)
 Status: 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/1736393

Title:
  [Artful][Wyse 3040] System hang when trying to enable an offlined CPU
  core

Status in linux package in Ubuntu:
  In Progress

Bug description:
  1. disable cpu[1-3] $ echo 0 > /sys/devices/system/cpu/cpu[1-3]/online
  2. enable cpu[1-3] $ echo 1 > /sys/devices/system/cpu/cpu[1-3]/online

  System will hang on step 2.

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

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


[Kernel-packages] [Bug 1721511] Re: [Xenial] update OpenNSL kernel modules to 6.5.10

2017-11-21 Thread Jesse Sung
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  [Xenial] update OpenNSL kernel modules to 6.5.10

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Currently we have 6.4.10 in the Xenial kernel. The latest OpenNSL
  Sep-27 release[1] updates kernel modules to 6.5.10.

  Since the module doesn't load automatically, this update shouldn't
  have any impact for people don't use the module.

  For the module itself, it loads without problem on a test system.

  [1] https://github.com/Broadcom-Switch/OpenNSL/tree/v3.4.1.5

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

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


[Kernel-packages] [Bug 1733281] [NEW] ubuntu/xr-usb-serial didn't get built in zesty and artful

2017-11-20 Thread Jesse Sung
Public bug reported:

The ubuntu/xr-usb-serial is expected to be built for i386 and x86_64,
and in ubuntu/Makefile it says:

ifneq ($(filter $(ARCH), i386 x86_64),)
obj-y += xr-usb-serial/
endif

Since ARCH is x86 for both i386 and x86_64, this condition will never be
true thus the module will never get a chance to be built.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Jesse Sung (wenchien)
 Status: 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/1733281

Title:
  ubuntu/xr-usb-serial didn't get built in zesty and artful

Status in linux package in Ubuntu:
  In Progress

Bug description:
  The ubuntu/xr-usb-serial is expected to be built for i386 and x86_64,
  and in ubuntu/Makefile it says:

  ifneq ($(filter $(ARCH), i386 x86_64),)
  obj-y += xr-usb-serial/
  endif

  Since ARCH is x86 for both i386 and x86_64, this condition will never
  be true thus the module will never get a chance to be built.

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

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


[Kernel-packages] [Bug 1721511] Re: [Xenial] update OpenNSL kernel modules to 6.5.10

2017-11-17 Thread Jesse Sung
** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [Xenial] update OpenNSL kernel modules to 6.5.10

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Currently we have 6.4.10 in the Xenial kernel. The latest OpenNSL
  Sep-27 release[1] updates kernel modules to 6.5.10.

  Since the module doesn't load automatically, this update shouldn't
  have any impact for people don't use the module.

  For the module itself, it loads without problem on a test system.

  [1] https://github.com/Broadcom-Switch/OpenNSL/tree/v3.4.1.5

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

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


[Kernel-packages] [Bug 1723915] Re: [Artful] Some Dell Monitors Doesn't Work Well with Dell/Wyse 3040

2017-11-13 Thread Jesse Sung
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful

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

Title:
  [Artful] Some Dell Monitors Doesn't Work Well with Dell/Wyse 3040

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  Fix Committed

Bug description:
  Dell Wyse 3040 box with Cherry Trail shows a blank monitor output and
  other display issues (eg. flickering after changing resolution) with a
  certain Dell DP monitors (E-series).

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

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


[Kernel-packages] [Bug 1723916] Re: [Artful] Add support for Dell/Wyse 3040 audio codec

2017-11-13 Thread Jesse Sung
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful

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

Title:
  [Artful] Add support for Dell/Wyse 3040 audio codec

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  Fix Committed

Bug description:
  The rt5760 on Wyse 3040 requires some extra code to work.

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

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


[Kernel-packages] [Bug 1718388] Re: Fix OpenNSL GPL bugs found by CoverityScan static analysis

2017-11-10 Thread Jesse Sung
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  Fix OpenNSL GPL bugs found by CoverityScan static analysis

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Static analysis on the ubuntu/opennsl drivers in Xenial have picked up
  various bugs. These need fixing.

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

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


[Kernel-packages] [Bug 1724215] Re: linux-euclid: 4.4.0-9019.20 -proposed tracker

2017-11-03 Thread Jesse Sung
The reason `apt dist-upgrade` doesn't install the new kernel is that the
meta packages don't get updated and still point to 9018.

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

Title:
  linux-euclid: 4.4.0-9019.20 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-9019.20 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
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1721511] Re: [Xenial] update OpenNSL kernel modules to 6.5.10

2017-10-24 Thread Jesse Sung
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  [Xenial] update OpenNSL kernel modules to 6.5.10

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Currently we have 6.4.10 in the Xenial kernel. The latest OpenNSL
  Sep-27 release[1] updates kernel modules to 6.5.10.

  Since the module doesn't load automatically, this update shouldn't
  have any impact for people don't use the module.

  For the module itself, it loads without problem on a test system.

  [1] https://github.com/Broadcom-Switch/OpenNSL/tree/v3.4.1.5

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

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


[Kernel-packages] [Bug 1723916] Re: [Artful] Add support for Dell/Wyse 3040 audio codec

2017-10-16 Thread Jesse Sung
** Tags added: carson originate-from-172

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

Title:
  [Artful] Add support for Dell/Wyse 3040 audio codec

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  The rt5760 on Wyse 3040 requires some extra code to work.

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

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


[Kernel-packages] [Bug 1723913] [NEW] [Artful] Support headset mode for DELL WYSE

2017-10-16 Thread Jesse Sung
Public bug reported:

Enable headset mode support for WYSE(0x080c) platform.

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

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Jesse Sung (wenchien)
 Status: In Progress


** Tags: carson originate-from-1710814

** Tags added: carson originate-from-1710814

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

Title:
  [Artful] Support headset mode for DELL WYSE

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Enable headset mode support for WYSE(0x080c) platform.

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

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


[Kernel-packages] [Bug 1723915] Re: [Artful] Some Dell Monitors Doesn't Work Well with Dell/Wyse 3040

2017-10-16 Thread Jesse Sung
** Tags added: carson originate-from-1712056

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

Title:
  [Artful] Some Dell Monitors Doesn't Work Well with Dell/Wyse 3040

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Dell Wyse 3040 box with Cherry Trail shows a blank monitor output and
  other display issues (eg. flickering after changing resolution) with a
  certain Dell DP monitors (E-series).

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

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


[Kernel-packages] [Bug 1723915] [NEW] [Artful] Some Dell Monitors Doesn't Work Well with Dell/Wyse 3040

2017-10-16 Thread Jesse Sung
Public bug reported:

Dell Wyse 3040 box with Cherry Trail shows a blank monitor output and
other display issues (eg. flickering after changing resolution) with a
certain Dell DP monitors (E-series).

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Jesse Sung (wenchien)
 Status: 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/1723915

Title:
  [Artful] Some Dell Monitors Doesn't Work Well with Dell/Wyse 3040

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Dell Wyse 3040 box with Cherry Trail shows a blank monitor output and
  other display issues (eg. flickering after changing resolution) with a
  certain Dell DP monitors (E-series).

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

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


[Kernel-packages] [Bug 1723916] [NEW] [Artful] Add support for Dell/Wyse 3040 audio codec

2017-10-16 Thread Jesse Sung
Public bug reported:

The rt5760 on Wyse 3040 requires some extra code to work.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Jesse Sung (wenchien)
 Status: 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/1723916

Title:
  [Artful] Add support for Dell/Wyse 3040 audio codec

Status in linux package in Ubuntu:
  In Progress

Bug description:
  The rt5760 on Wyse 3040 requires some extra code to work.

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

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


[Kernel-packages] [Bug 1721511] Re: [Xenial] update OpenNSL kernel modules to 6.5.10

2017-10-05 Thread Jesse Sung
** Tags added: hohhot originate-from-1719941

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

Title:
  [Xenial] update OpenNSL kernel modules to 6.5.10

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Currently we have 6.4.10 in the Xenial kernel. The latest OpenNSL
  Sep-27 release[1] updates kernel modules to 6.5.10.

  Since the module doesn't load automatically, this update shouldn't
  have any impact for people don't use the module.

  For the module itself, it loads without problem on a test system.

  [1] https://github.com/Broadcom-Switch/OpenNSL/tree/v3.4.1.5

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

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


[Kernel-packages] [Bug 1721511] [NEW] [Xenial] update OpenNSL kernel modules to 6.5.10

2017-10-05 Thread Jesse Sung
Public bug reported:

Currently we have 6.4.10 in the Xenial kernel. The latest OpenNSL Sep-27
release[1] updates kernel modules to 6.5.10.

Since the module doesn't load automatically, this update shouldn't have
any impact for people don't use the module.

For the module itself, it loads without problem on a test system.

[1] https://github.com/Broadcom-Switch/OpenNSL/tree/v3.4.1.5

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Jesse Sung (wenchien)
 Status: 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/1721511

Title:
  [Xenial] update OpenNSL kernel modules to 6.5.10

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Currently we have 6.4.10 in the Xenial kernel. The latest OpenNSL
  Sep-27 release[1] updates kernel modules to 6.5.10.

  Since the module doesn't load automatically, this update shouldn't
  have any impact for people don't use the module.

  For the module itself, it loads without problem on a test system.

  [1] https://github.com/Broadcom-Switch/OpenNSL/tree/v3.4.1.5

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

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


[Kernel-packages] [Bug 1665783] Re: Include Broadcom GPL modules in Xenial Kernel

2017-09-06 Thread Jesse Sung
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  Include Broadcom GPL modules in Xenial Kernel

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Invalid

Bug description:
  Please include the OpenNSL GPL modules with the Kernel.
  These modules are located at https://github.com/Broadcom-Switch/OpenNSL.
  The latest SDK version is 6.5.6. 
  We would like to have the kernel modules included with the LTS Xenial kernel 
so that we can provide these modules to network vendors so that they don't have 
to compile them and taint our working kernel. 
  We would want to manage these modules so that we can perform updates and 
security fixes to the kernel and even use kernel-livepatch with these devices. 
  Currently, Network vendors compile and build these against older kernel's and 
then they cannot be patched or updated leaving network devices vulnerable to 
security threats that normally would be patched by our systems. By having us 
manage these modules, we can maintain security and compatibility with the 
kernel and the network vendors can use our native kernel with their software.

  The three modules that get built are linux-kernel-bde.ko, linux-user-
  bde,ko and linux-bcm-knet.ko.

  If you have any other questions, please don't hesitate to contact me.

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

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


[Kernel-packages] [Bug 1712024] Re: igb: Support using Broadcom 54616 as PHY

2017-09-06 Thread Jesse Sung
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

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

Title:
  igb: Support using Broadcom 54616 as PHY

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  The igb driver fails to work when using Broadcom 54616 as PHY.

  00:14.0 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)
  00:14.1 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)
  00:14.2 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)

  $ dmesg | grep igb
  [3.472655] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.3.0-k
  [3.480475] igb: Copyright (c) 2007-2014 Intel Corporation.
  [3.584768] igb: probe of :00:14.0 failed with error -2
  [3.965971] igb :00:14.1: added PHC on eth0
  [3.971066] igb :00:14.1: Intel(R) Gigabit Ethernet Network Connection
  [4.010706] igb :00:14.1: eth0: PBA No: 002000-000
  [4.016458] igb :00:14.1: Using MSI-X interrupts. 4 rx queue(s), 4 tx 
queue(s)
  [4.399662] igb :00:14.2: added PHC on eth1
  [4.404738] igb :00:14.2: Intel(R) Gigabit Ethernet Network Connection
  [4.412489] igb :00:14.2: eth1: PBA No: 002000-000
  [4.418235] igb :00:14.2: Using MSI-X interrupts. 4 rx queue(s), 4 tx 
queue(s)
  [4.428206] igb :00:14.1 enp0s20f1: renamed from eth0
  [4.465744] igb :00:14.2 enp0s20f2: renamed from eth1

  A patch can be found in OpenNetworkLinux:
  
https://github.com/opencomputeproject/OpenNetworkLinux/blob/master/packages/base/any/kernels/3.18.25/patches
  /driver-support-intel-igb-bcm54616-phy.patch

  It should be safe to include this in an SRU release since the new code
  is only functioning when certain ID is found.

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

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


[Kernel-packages] [Bug 1712746] Re: mwifiex causes kernel oops when AP mode is enabled

2017-09-06 Thread Jesse Sung
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  mwifiex causes kernel oops when AP mode is enabled

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  When it's in AP mode, there's quite a chance to find kernel oops
  during reboot.

  This is caused by the wiphy may be NULL for some reason. It's likely a
  bug in mwifiex. We've already pinged Marvell and Murata. Before
  there's a real fix available, we should check wiphy before accessing
  it.

  I've tried a 4.13-rc6 kernel. Though it has oops for NULL pointer
  deference too, it happens in a different function in mwifiex. Thus the
  workaround for Xenial may or may not help for other series. Will need
  to reproduce this issue with Zesty and then we can decide whether this
  workaround should be applied to Zesty.

  [   30.701441] BUG: unable to handle kernel NULL pointer dereference at 
00f0
  [   30.709511] IP: [] mwifiex_get_cfp+0x49/0x150 [mwifiex]
  [   30.716494] PGD 0
  [   30.718575] Oops:  [#1] SMP
  [   30.721918] Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conni
  [   30.836915] CPU: 1 PID: 679 Comm: kworker/u5:0 Not tainted 
4.4.0-57-generic #78-Ubuntu
  [   30.845018] Hardware name: Dell Inc. Edge Gateway 5000/  , BIOS 
01.05.00 10/18/2016
  [   30.853218] Workqueue: MWIFIEX_WORK_QUEUE mwifiex_main_work_queue [mwifiex]
  [   30.860362] task: 880077c11980 ti: 880075e48000 task.ti: 
880075e48000
  [   30.868018] RIP: 0010:[]  [] 
mwifiex_get_cfp+0x49/0x150 [mwifiex]
  [   30.877484] RSP: 0018:880075e4bbf8  EFLAGS: 00010202
  [   30.882920] RAX:  RBX: 0004 RCX: 
0004
  [   30.890221] RDX: 001000110010 RSI: 0004 RDI: 
0004
  [   30.897520] RBP: 880075e4bc28 R08: 0003 R09: 
0001
  [   30.904821] R10: 0001 R11: 02ff R12: 
0095
  [   30.912123] R13:  R14: 880075e4 R15: 
0095
  [   30.919425] FS:  () GS:88007130() 
knlGS:
  [   30.927701] CS:  0010 DS:  ES:  CR0: 8005003b
  [   30.933581] CR2: 00f0 CR3: 01e0a000 CR4: 
001006e0
  [   30.940882] Stack:
  [   30.942944]  0118 880075e4 8800750c4000 
880075e3ed59
  [   30.950592]  0095 880075e3ee01 880075e4bcd0 
c05846fc
  [   30.958232]   880075e4bc50 8140bcb5 
880075e4bc70
  [   30.965873] Call Trace:
  [   30.968397]  [] 
mwifiex_parse_single_response_buf+0x1fc/0x560 [mwifiex]
  [   30.976772]  [] ? find_next_bit+0x15/0x20
  [   30.982490]  [] 
mwifiex_handle_event_ext_scan_report+0x15c/0x340 [mwifiex]
  [   30.991139]  [] mwifiex_process_sta_event+0x276/0xb40 
[mwifiex]
  [   30.998806]  [] mwifiex_process_event+0x102/0x1c0 
[mwifiex]
  [   31.006120]  [] mwifiex_main_process+0x5de/0x8d0 
[mwifiex]
  [   31.013346]  [] mwifiex_main_work_queue+0x1f/0x30 
[mwifiex]
  [   31.020650]  [] process_one_work+0x165/0x480
  [   31.026624]  [] worker_thread+0x4b/0x4c0
  [   31.032240]  [] ? process_one_work+0x480/0x480
  [   31.038387]  [] kthread+0xd8/0xf0
  [   31.043384]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [   31.050071]  [] ret_from_fork+0x3f/0x70
  [   31.055596]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [   31.062276] Code: 85 c9 0f 84 ef 00 00 00 40 0f b6 de 49 89 fe 41 89 cd 89 
df 41 89 d4 e8 46 f1 00 00 84 c0 49 8b 86 e0 13 00 00 0f 84 98 00
  [   31.082756] RIP  [] mwifiex_get_cfp+0x49/0x150 [mwifiex]
  [   31.089820]  RSP 
  [   31.093392] CR2: 00f0
  [   31.096787] ---[ end trace f3a762be5787f138 ]---

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

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


[Kernel-packages] [Bug 1712024] Re: igb: Support using Broadcom 54616 as PHY

2017-08-24 Thread Jesse Sung
** Description changed:

  The igb driver fails to work when using Broadcom 54616 as PHY.
  
  00:14.0 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)
  00:14.1 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)
  00:14.2 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)
  
  $ dmesg | grep igb
  [3.472655] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.3.0-k
  [3.480475] igb: Copyright (c) 2007-2014 Intel Corporation.
  [3.584768] igb: probe of :00:14.0 failed with error -2
  [3.965971] igb :00:14.1: added PHC on eth0
  [3.971066] igb :00:14.1: Intel(R) Gigabit Ethernet Network Connection
  [4.010706] igb :00:14.1: eth0: PBA No: 002000-000
  [4.016458] igb :00:14.1: Using MSI-X interrupts. 4 rx queue(s), 4 tx 
queue(s)
  [4.399662] igb :00:14.2: added PHC on eth1
  [4.404738] igb :00:14.2: Intel(R) Gigabit Ethernet Network Connection
  [4.412489] igb :00:14.2: eth1: PBA No: 002000-000
  [4.418235] igb :00:14.2: Using MSI-X interrupts. 4 rx queue(s), 4 tx 
queue(s)
  [4.428206] igb :00:14.1 enp0s20f1: renamed from eth0
  [4.465744] igb :00:14.2 enp0s20f2: renamed from eth1
  
  A patch can be found in OpenNetworkLinux:
  
https://github.com/opencomputeproject/OpenNetworkLinux/blob/master/packages/base/any/kernels/3.18.25/patches
  /driver-support-intel-igb-bcm54616-phy.patch
+ 
+ It should be safe to include this in an SRU release since the new code
+ is only functioning when certain ID is found.

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

Title:
  igb: Support using Broadcom 54616 as PHY

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  The igb driver fails to work when using Broadcom 54616 as PHY.

  00:14.0 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)
  00:14.1 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)
  00:14.2 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)

  $ dmesg | grep igb
  [3.472655] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.3.0-k
  [3.480475] igb: Copyright (c) 2007-2014 Intel Corporation.
  [3.584768] igb: probe of :00:14.0 failed with error -2
  [3.965971] igb :00:14.1: added PHC on eth0
  [3.971066] igb :00:14.1: Intel(R) Gigabit Ethernet Network Connection
  [4.010706] igb :00:14.1: eth0: PBA No: 002000-000
  [4.016458] igb :00:14.1: Using MSI-X interrupts. 4 rx queue(s), 4 tx 
queue(s)
  [4.399662] igb :00:14.2: added PHC on eth1
  [4.404738] igb :00:14.2: Intel(R) Gigabit Ethernet Network Connection
  [4.412489] igb :00:14.2: eth1: PBA No: 002000-000
  [4.418235] igb :00:14.2: Using MSI-X interrupts. 4 rx queue(s), 4 tx 
queue(s)
  [4.428206] igb :00:14.1 enp0s20f1: renamed from eth0
  [4.465744] igb :00:14.2 enp0s20f2: renamed from eth1

  A patch can be found in OpenNetworkLinux:
  
https://github.com/opencomputeproject/OpenNetworkLinux/blob/master/packages/base/any/kernels/3.18.25/patches
  /driver-support-intel-igb-bcm54616-phy.patch

  It should be safe to include this in an SRU release since the new code
  is only functioning when certain ID is found.

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

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


[Kernel-packages] [Bug 1712746] Re: mwifiex causes kernel oops when AP mode is enabled

2017-08-24 Thread Jesse Sung
** Description changed:

  When it's in AP mode, there's quite a chance to find kernel oops during
  reboot.
  
+ This is caused by the wiphy may be NULL for some reason. It's likely a
+ bug in mwifiex. We've already pinged Marvell and Murata. Before there's
+ a real fix available, we should check wiphy before accessing it.
+ 
+ I've tried a 4.13-rc6 kernel. Though it has oops for NULL pointer
+ deference too, it happens in a different function in mwifiex. Thus the
+ workaround for Xenial may or may not help for other series. Will need to
+ reproduce this issue with Zesty and then we can decide whether this
+ workaround should be applied to Zesty.
+ 
  [   30.701441] BUG: unable to handle kernel NULL pointer dereference at 
00f0
  [   30.709511] IP: [] mwifiex_get_cfp+0x49/0x150 [mwifiex]
- [   30.716494] PGD 0 
- [   30.718575] Oops:  [#1] SMP 
+ [   30.716494] PGD 0
+ [   30.718575] Oops:  [#1] SMP
  [   30.721918] Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conni
  [   30.836915] CPU: 1 PID: 679 Comm: kworker/u5:0 Not tainted 
4.4.0-57-generic #78-Ubuntu
  [   30.845018] Hardware name: Dell Inc. Edge Gateway 5000/  , BIOS 
01.05.00 10/18/2016
  [   30.853218] Workqueue: MWIFIEX_WORK_QUEUE mwifiex_main_work_queue [mwifiex]
  [   30.860362] task: 880077c11980 ti: 880075e48000 task.ti: 
880075e48000
  [   30.868018] RIP: 0010:[]  [] 
mwifiex_get_cfp+0x49/0x150 [mwifiex]
  [   30.877484] RSP: 0018:880075e4bbf8  EFLAGS: 00010202
  [   30.882920] RAX:  RBX: 0004 RCX: 
0004
  [   30.890221] RDX: 001000110010 RSI: 0004 RDI: 
0004
  [   30.897520] RBP: 880075e4bc28 R08: 0003 R09: 
0001
  [   30.904821] R10: 0001 R11: 02ff R12: 
0095
  [   30.912123] R13:  R14: 880075e4 R15: 
0095
  [   30.919425] FS:  () GS:88007130() 
knlGS:
  [   30.927701] CS:  0010 DS:  ES:  CR0: 8005003b
  [   30.933581] CR2: 00f0 CR3: 01e0a000 CR4: 
001006e0
  [   30.940882] Stack:
  [   30.942944]  0118 880075e4 8800750c4000 
880075e3ed59
  [   30.950592]  0095 880075e3ee01 880075e4bcd0 
c05846fc
  [   30.958232]   880075e4bc50 8140bcb5 
880075e4bc70
  [   30.965873] Call Trace:
  [   30.968397]  [] 
mwifiex_parse_single_response_buf+0x1fc/0x560 [mwifiex]
  [   30.976772]  [] ? find_next_bit+0x15/0x20
  [   30.982490]  [] 
mwifiex_handle_event_ext_scan_report+0x15c/0x340 [mwifiex]
  [   30.991139]  [] mwifiex_process_sta_event+0x276/0xb40 
[mwifiex]
  [   30.998806]  [] mwifiex_process_event+0x102/0x1c0 
[mwifiex]
  [   31.006120]  [] mwifiex_main_process+0x5de/0x8d0 
[mwifiex]
  [   31.013346]  [] mwifiex_main_work_queue+0x1f/0x30 
[mwifiex]
  [   31.020650]  [] process_one_work+0x165/0x480
  [   31.026624]  [] worker_thread+0x4b/0x4c0
  [   31.032240]  [] ? process_one_work+0x480/0x480
  [   31.038387]  [] kthread+0xd8/0xf0
  [   31.043384]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [   31.050071]  [] ret_from_fork+0x3f/0x70
  [   31.055596]  [] ? kthread_create_on_node+0x1e0/0x1e0
- [   31.062276] Code: 85 c9 0f 84 ef 00 00 00 40 0f b6 de 49 89 fe 41 89 cd 89 
df 41 89 d4 e8 46 f1 00 00 84 c0 49 8b 86 e0 13 00 00 0f 84 98 00 
+ [   31.062276] Code: 85 c9 0f 84 ef 00 00 00 40 0f b6 de 49 89 fe 41 89 cd 89 
df 41 89 d4 e8 46 f1 00 00 84 c0 49 8b 86 e0 13 00 00 0f 84 98 00
  [   31.082756] RIP  [] mwifiex_get_cfp+0x49/0x150 [mwifiex]
  [   31.089820]  RSP 
  [   31.093392] CR2: 00f0
  [   31.096787] ---[ end trace f3a762be5787f138 ]---

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

Title:
  mwifiex causes kernel oops when AP mode is enabled

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  New

Bug description:
  When it's in AP mode, there's quite a chance to find kernel oops
  during reboot.

  This is caused by the wiphy may be NULL for some reason. It's likely a
  bug in mwifiex. We've already pinged Marvell and Murata. Before
  there's a real fix available, we should check wiphy before accessing
  it.

  I've tried a 4.13-rc6 kernel. Though it has oops for NULL pointer
  deference too, it happens in a different function in mwifiex. Thus the
  workaround for Xenial may or may not help for other series. Will need
  to reproduce this issue with Zesty and then we can decide whether this
  workaround should be applied to Zesty.

  [   30.701441] BUG: unable to handle kernel NULL pointer dereference at 
00f0
  [   30.709511] IP: [] mwifiex_get_cfp+0x49/0x150 

[Kernel-packages] [Bug 1712746] Re: mwifiex causes kernel oops when AP mode is enabled

2017-08-24 Thread Jesse Sung
** Changed in: hwe-next
 Assignee: (unassigned) => Jesse Sung (wenchien)

** Changed in: hwe-next
   Status: New => 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/1712746

Title:
  mwifiex causes kernel oops when AP mode is enabled

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  When it's in AP mode, there's quite a chance to find kernel oops
  during reboot.

  [   30.701441] BUG: unable to handle kernel NULL pointer dereference at 
00f0
  [   30.709511] IP: [] mwifiex_get_cfp+0x49/0x150 [mwifiex]
  [   30.716494] PGD 0 
  [   30.718575] Oops:  [#1] SMP 
  [   30.721918] Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conni
  [   30.836915] CPU: 1 PID: 679 Comm: kworker/u5:0 Not tainted 
4.4.0-57-generic #78-Ubuntu
  [   30.845018] Hardware name: Dell Inc. Edge Gateway 5000/  , BIOS 
01.05.00 10/18/2016
  [   30.853218] Workqueue: MWIFIEX_WORK_QUEUE mwifiex_main_work_queue [mwifiex]
  [   30.860362] task: 880077c11980 ti: 880075e48000 task.ti: 
880075e48000
  [   30.868018] RIP: 0010:[]  [] 
mwifiex_get_cfp+0x49/0x150 [mwifiex]
  [   30.877484] RSP: 0018:880075e4bbf8  EFLAGS: 00010202
  [   30.882920] RAX:  RBX: 0004 RCX: 
0004
  [   30.890221] RDX: 001000110010 RSI: 0004 RDI: 
0004
  [   30.897520] RBP: 880075e4bc28 R08: 0003 R09: 
0001
  [   30.904821] R10: 0001 R11: 02ff R12: 
0095
  [   30.912123] R13:  R14: 880075e4 R15: 
0095
  [   30.919425] FS:  () GS:88007130() 
knlGS:
  [   30.927701] CS:  0010 DS:  ES:  CR0: 8005003b
  [   30.933581] CR2: 00f0 CR3: 01e0a000 CR4: 
001006e0
  [   30.940882] Stack:
  [   30.942944]  0118 880075e4 8800750c4000 
880075e3ed59
  [   30.950592]  0095 880075e3ee01 880075e4bcd0 
c05846fc
  [   30.958232]   880075e4bc50 8140bcb5 
880075e4bc70
  [   30.965873] Call Trace:
  [   30.968397]  [] 
mwifiex_parse_single_response_buf+0x1fc/0x560 [mwifiex]
  [   30.976772]  [] ? find_next_bit+0x15/0x20
  [   30.982490]  [] 
mwifiex_handle_event_ext_scan_report+0x15c/0x340 [mwifiex]
  [   30.991139]  [] mwifiex_process_sta_event+0x276/0xb40 
[mwifiex]
  [   30.998806]  [] mwifiex_process_event+0x102/0x1c0 
[mwifiex]
  [   31.006120]  [] mwifiex_main_process+0x5de/0x8d0 
[mwifiex]
  [   31.013346]  [] mwifiex_main_work_queue+0x1f/0x30 
[mwifiex]
  [   31.020650]  [] process_one_work+0x165/0x480
  [   31.026624]  [] worker_thread+0x4b/0x4c0
  [   31.032240]  [] ? process_one_work+0x480/0x480
  [   31.038387]  [] kthread+0xd8/0xf0
  [   31.043384]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [   31.050071]  [] ret_from_fork+0x3f/0x70
  [   31.055596]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [   31.062276] Code: 85 c9 0f 84 ef 00 00 00 40 0f b6 de 49 89 fe 41 89 cd 89 
df 41 89 d4 e8 46 f1 00 00 84 c0 49 8b 86 e0 13 00 00 0f 84 98 00 
  [   31.082756] RIP  [] mwifiex_get_cfp+0x49/0x150 [mwifiex]
  [   31.089820]  RSP 
  [   31.093392] CR2: 00f0
  [   31.096787] ---[ end trace f3a762be5787f138 ]---

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

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


[Kernel-packages] [Bug 1712746] [NEW] mwifiex causes kernel oops when AP mode is enabled

2017-08-24 Thread Jesse Sung
Public bug reported:

When it's in AP mode, there's quite a chance to find kernel oops during
reboot.

[   30.701441] BUG: unable to handle kernel NULL pointer dereference at 
00f0
[   30.709511] IP: [] mwifiex_get_cfp+0x49/0x150 [mwifiex]
[   30.716494] PGD 0 
[   30.718575] Oops:  [#1] SMP 
[   30.721918] Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conni
[   30.836915] CPU: 1 PID: 679 Comm: kworker/u5:0 Not tainted 4.4.0-57-generic 
#78-Ubuntu
[   30.845018] Hardware name: Dell Inc. Edge Gateway 5000/  , BIOS 01.05.00 
10/18/2016
[   30.853218] Workqueue: MWIFIEX_WORK_QUEUE mwifiex_main_work_queue [mwifiex]
[   30.860362] task: 880077c11980 ti: 880075e48000 task.ti: 
880075e48000
[   30.868018] RIP: 0010:[]  [] 
mwifiex_get_cfp+0x49/0x150 [mwifiex]
[   30.877484] RSP: 0018:880075e4bbf8  EFLAGS: 00010202
[   30.882920] RAX:  RBX: 0004 RCX: 0004
[   30.890221] RDX: 001000110010 RSI: 0004 RDI: 0004
[   30.897520] RBP: 880075e4bc28 R08: 0003 R09: 0001
[   30.904821] R10: 0001 R11: 02ff R12: 0095
[   30.912123] R13:  R14: 880075e4 R15: 0095
[   30.919425] FS:  () GS:88007130() 
knlGS:
[   30.927701] CS:  0010 DS:  ES:  CR0: 8005003b
[   30.933581] CR2: 00f0 CR3: 01e0a000 CR4: 001006e0
[   30.940882] Stack:
[   30.942944]  0118 880075e4 8800750c4000 
880075e3ed59
[   30.950592]  0095 880075e3ee01 880075e4bcd0 
c05846fc
[   30.958232]   880075e4bc50 8140bcb5 
880075e4bc70
[   30.965873] Call Trace:
[   30.968397]  [] 
mwifiex_parse_single_response_buf+0x1fc/0x560 [mwifiex]
[   30.976772]  [] ? find_next_bit+0x15/0x20
[   30.982490]  [] 
mwifiex_handle_event_ext_scan_report+0x15c/0x340 [mwifiex]
[   30.991139]  [] mwifiex_process_sta_event+0x276/0xb40 
[mwifiex]
[   30.998806]  [] mwifiex_process_event+0x102/0x1c0 [mwifiex]
[   31.006120]  [] mwifiex_main_process+0x5de/0x8d0 [mwifiex]
[   31.013346]  [] mwifiex_main_work_queue+0x1f/0x30 [mwifiex]
[   31.020650]  [] process_one_work+0x165/0x480
[   31.026624]  [] worker_thread+0x4b/0x4c0
[   31.032240]  [] ? process_one_work+0x480/0x480
[   31.038387]  [] kthread+0xd8/0xf0
[   31.043384]  [] ? kthread_create_on_node+0x1e0/0x1e0
[   31.050071]  [] ret_from_fork+0x3f/0x70
[   31.055596]  [] ? kthread_create_on_node+0x1e0/0x1e0
[   31.062276] Code: 85 c9 0f 84 ef 00 00 00 40 0f b6 de 49 89 fe 41 89 cd 89 
df 41 89 d4 e8 46 f1 00 00 84 c0 49 8b 86 e0 13 00 00 0f 84 98 00 
[   31.082756] RIP  [] mwifiex_get_cfp+0x49/0x150 [mwifiex]
[   31.089820]  RSP 
[   31.093392] CR2: 00f0
[   31.096787] ---[ end trace f3a762be5787f138 ]---

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

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Jesse Sung (wenchien)
 Status: In Progress


** Tags: originate-from-1654549 plano

** Tags added: originate-from-1654549 plano

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

Title:
  mwifiex causes kernel oops when AP mode is enabled

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  When it's in AP mode, there's quite a chance to find kernel oops
  during reboot.

  [   30.701441] BUG: unable to handle kernel NULL pointer dereference at 
00f0
  [   30.709511] IP: [] mwifiex_get_cfp+0x49/0x150 [mwifiex]
  [   30.716494] PGD 0 
  [   30.718575] Oops:  [#1] SMP 
  [   30.721918] Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conni
  [   30.836915] CPU: 1 PID: 679 Comm: kworker/u5:0 Not tainted 
4.4.0-57-generic #78-Ubuntu
  [   30.845018] Hardware name: Dell Inc. Edge Gateway 5000/  , BIOS 
01.05.00 10/18/2016
  [   30.853218] Workqueue: MWIFIEX_WORK_QUEUE mwifiex_main_work_queue [mwifiex]
  [   30.860362] task: 880077c11980 ti: 880075e48000 task.ti: 
880075e48000
  [   30.868018] RIP: 0010:[]  [] 
mwifiex_get_cfp+0x49/0x150 [mwifiex]
  [   30.877484] RSP: 0018:880075e4bbf8  EFLAGS: 00010202
  [   30.882920] RAX:  RBX: 0004 RCX: 
0004
  [   30.890221] RDX: 001000110010 RSI: 0004 RDI: 
0004
  [   30.897520] RBP: 880075e4bc28 R08: 0003 R09: 
0001
  [   30.904821] R10: 0001 R11: 02ff R12: 
0095
  [   30.912123] R13:  R14: 880075e4 R15: 
0095
  [   30.919425] FS:  (

[Kernel-packages] [Bug 1712024] [NEW] igb: Support using Broadcom 54616 as PHY

2017-08-21 Thread Jesse Sung
Public bug reported:

The igb driver fails to work when using Broadcom 54616 as PHY.

00:14.0 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 03)
00:14.1 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 03)
00:14.2 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 03)

$ dmesg | grep igb
[3.472655] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.3.0-k
[3.480475] igb: Copyright (c) 2007-2014 Intel Corporation.
[3.584768] igb: probe of :00:14.0 failed with error -2
[3.965971] igb :00:14.1: added PHC on eth0
[3.971066] igb :00:14.1: Intel(R) Gigabit Ethernet Network Connection
[4.010706] igb :00:14.1: eth0: PBA No: 002000-000
[4.016458] igb :00:14.1: Using MSI-X interrupts. 4 rx queue(s), 4 tx 
queue(s)
[4.399662] igb :00:14.2: added PHC on eth1
[4.404738] igb :00:14.2: Intel(R) Gigabit Ethernet Network Connection
[4.412489] igb :00:14.2: eth1: PBA No: 002000-000
[4.418235] igb :00:14.2: Using MSI-X interrupts. 4 rx queue(s), 4 tx 
queue(s)
[4.428206] igb :00:14.1 enp0s20f1: renamed from eth0
[4.465744] igb :00:14.2 enp0s20f2: renamed from eth1

A patch can be found in OpenNetworkLinux:
https://github.com/opencomputeproject/OpenNetworkLinux/blob/master/packages/base/any/kernels/3.18.25/patches
/driver-support-intel-igb-bcm54616-phy.patch

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Jesse Sung (wenchien)
 Status: 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/1712024

Title:
  igb: Support using Broadcom 54616 as PHY

Status in linux package in Ubuntu:
  In Progress

Bug description:
  The igb driver fails to work when using Broadcom 54616 as PHY.

  00:14.0 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)
  00:14.1 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)
  00:14.2 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)

  $ dmesg | grep igb
  [3.472655] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.3.0-k
  [3.480475] igb: Copyright (c) 2007-2014 Intel Corporation.
  [3.584768] igb: probe of :00:14.0 failed with error -2
  [3.965971] igb :00:14.1: added PHC on eth0
  [3.971066] igb :00:14.1: Intel(R) Gigabit Ethernet Network Connection
  [4.010706] igb :00:14.1: eth0: PBA No: 002000-000
  [4.016458] igb :00:14.1: Using MSI-X interrupts. 4 rx queue(s), 4 tx 
queue(s)
  [4.399662] igb :00:14.2: added PHC on eth1
  [4.404738] igb :00:14.2: Intel(R) Gigabit Ethernet Network Connection
  [4.412489] igb :00:14.2: eth1: PBA No: 002000-000
  [4.418235] igb :00:14.2: Using MSI-X interrupts. 4 rx queue(s), 4 tx 
queue(s)
  [4.428206] igb :00:14.1 enp0s20f1: renamed from eth0
  [4.465744] igb :00:14.2 enp0s20f2: renamed from eth1

  A patch can be found in OpenNetworkLinux:
  
https://github.com/opencomputeproject/OpenNetworkLinux/blob/master/packages/base/any/kernels/3.18.25/patches
  /driver-support-intel-igb-bcm54616-phy.patch

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

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


[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

2017-06-21 Thread Jesse Sung
It happens when test for kernel in -proposed (in this case 4.10.0-23) is
not yet completed, and an important security issue must be addressed. In
this case 4.10.0-24 is based on a fully tested 4.10.0-22, and changes in
4.10.0-23 will be included in later release instead.

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

Title:
  bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10
  in XENIAL LTS

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux-hwe package in Ubuntu:
  Fix Released
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in linux-hwe source package in Xenial:
  Fix Released
Status in linux-hwe-edge source package in Xenial:
  Confirmed
Status in linux source package in Yakkety:
  Fix Released
Status in linux-hwe source package in Yakkety:
  Fix Committed
Status in linux-hwe-edge source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  In Progress
Status in linux-hwe source package in Zesty:
  Confirmed
Status in linux-hwe-edge source package in Zesty:
  Confirmed

Bug description:
  Since I upgraded the kernel from linux-image-4.8.0-46-generic to
  linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to
  change the MTU.

  It seems to be known bug already fixed:
  https://bugzilla.kernel.org/show_bug.cgi?id=194763

  # ip l sh eno49
  2: eno49:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh eno50
  3: eno50:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh bond0
  6: bond0:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l set mtu 9000 bond0
  RTNETLINK answers: Invalid argument

  root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog
  Apr  4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 
requested, hw max 1500

  # modinfo ixgbe
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko
  version:4.4.0-k
  license:GPL
  description:Intel(R) 10 Gigabit PCI Express Network Driver

  # modinfo bonding
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko
  author: Thomas Davis, tada...@lbl.gov and many others
  description:Ethernet Channel Bonding Driver, v3.7.1
  version:3.7.1

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

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


[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

2017-06-20 Thread Jesse Sung
4.10.0-24 is a 4.10.0-22 with CVE fix applied, that's why it doesn't
have the fix for openvswitch which is in 4.10.0-23.

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

Title:
  bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10
  in XENIAL LTS

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux-hwe package in Ubuntu:
  Fix Released
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in linux-hwe source package in Xenial:
  Fix Released
Status in linux-hwe-edge source package in Xenial:
  Confirmed
Status in linux source package in Yakkety:
  Fix Released
Status in linux-hwe source package in Yakkety:
  Fix Committed
Status in linux-hwe-edge source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  In Progress
Status in linux-hwe source package in Zesty:
  Confirmed
Status in linux-hwe-edge source package in Zesty:
  Confirmed

Bug description:
  Since I upgraded the kernel from linux-image-4.8.0-46-generic to
  linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to
  change the MTU.

  It seems to be known bug already fixed:
  https://bugzilla.kernel.org/show_bug.cgi?id=194763

  # ip l sh eno49
  2: eno49:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh eno50
  3: eno50:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh bond0
  6: bond0:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l set mtu 9000 bond0
  RTNETLINK answers: Invalid argument

  root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog
  Apr  4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 
requested, hw max 1500

  # modinfo ixgbe
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko
  version:4.4.0-k
  license:GPL
  description:Intel(R) 10 Gigabit PCI Express Network Driver

  # modinfo bonding
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko
  author: Thomas Davis, tada...@lbl.gov and many others
  description:Ethernet Channel Bonding Driver, v3.7.1
  version:3.7.1

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

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


[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

2017-06-08 Thread Jesse Sung
@shapemaker:

Since it's "fix committed" for lp:1691369, the fix will be included in
the next SRU release.

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

Title:
  bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10
  in XENIAL LTS

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux-hwe package in Ubuntu:
  Fix Released
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  New
Status in linux-hwe source package in Xenial:
  Fix Released
Status in linux-hwe-edge source package in Xenial:
  New
Status in linux source package in Yakkety:
  Fix Released
Status in linux-hwe source package in Yakkety:
  Fix Committed
Status in linux-hwe-edge source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  In Progress
Status in linux-hwe source package in Zesty:
  Confirmed
Status in linux-hwe-edge source package in Zesty:
  Confirmed

Bug description:
  Since I upgraded the kernel from linux-image-4.8.0-46-generic to
  linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to
  change the MTU.

  It seems to be known bug already fixed:
  https://bugzilla.kernel.org/show_bug.cgi?id=194763

  # ip l sh eno49
  2: eno49:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh eno50
  3: eno50:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh bond0
  6: bond0:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l set mtu 9000 bond0
  RTNETLINK answers: Invalid argument

  root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog
  Apr  4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 
requested, hw max 1500

  # modinfo ixgbe
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko
  version:4.4.0-k
  license:GPL
  description:Intel(R) 10 Gigabit PCI Express Network Driver

  # modinfo bonding
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko
  author: Thomas Davis, tada...@lbl.gov and many others
  description:Ethernet Channel Bonding Driver, v3.7.1
  version:3.7.1

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

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


[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

2017-06-08 Thread Jesse Sung
@vaaend:

@smb pointed out that it is part of the stable 4.10.16:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1691369

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

Title:
  bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10
  in XENIAL LTS

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux-hwe package in Ubuntu:
  Fix Released
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  New
Status in linux-hwe source package in Xenial:
  Fix Released
Status in linux-hwe-edge source package in Xenial:
  New
Status in linux source package in Yakkety:
  Fix Released
Status in linux-hwe source package in Yakkety:
  Fix Committed
Status in linux-hwe-edge source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  In Progress
Status in linux-hwe source package in Zesty:
  Confirmed
Status in linux-hwe-edge source package in Zesty:
  Confirmed

Bug description:
  Since I upgraded the kernel from linux-image-4.8.0-46-generic to
  linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to
  change the MTU.

  It seems to be known bug already fixed:
  https://bugzilla.kernel.org/show_bug.cgi?id=194763

  # ip l sh eno49
  2: eno49:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh eno50
  3: eno50:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh bond0
  6: bond0:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l set mtu 9000 bond0
  RTNETLINK answers: Invalid argument

  root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog
  Apr  4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 
requested, hw max 1500

  # modinfo ixgbe
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko
  version:4.4.0-k
  license:GPL
  description:Intel(R) 10 Gigabit PCI Express Network Driver

  # modinfo bonding
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko
  author: Thomas Davis, tada...@lbl.gov and many others
  description:Ethernet Channel Bonding Driver, v3.7.1
  version:3.7.1

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

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


[Kernel-packages] [Bug 1689497] Re: Add two firmware for Joule

2017-05-29 Thread Jesse Sung
A formal license file for the audio topology binary can be found at
https://github.com/01org/ref-os-iot/blob/master/meta-ref-os-iot/recipes-
kernel/linux-firmware/files/LICENSE.1a98-INTEL-EDK2-2-tplg

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

Title:
  Add two firmware for Joule

Status in linux-firmware package in Ubuntu:
  In Progress

Bug description:
  Two additional firmware files are required for Joule.

  One is the firmware for supporting MIPI camera. Firmware and its license can 
be found at
  
https://github.com/Intel-5xx-Camera/intel-camera-adaptation/blob/master/fw-ipu4-1.0.tar.gz

  The other is an audio topology binary. License for this file is
  attached.

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

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


[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

2017-05-23 Thread Jesse Sung
With 4.8.0-53 in -proposed, e1000e works without any problem.

$ uname -a
Linux cola 4.8.0-53-generic #56-Ubuntu SMP Tue May 16 00:23:44 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux

$ ifconfig eth1
...
UP BROADCAST RUNNING MULTICAST  MTU:9000  Metric:1
...

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

Title:
  bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10
  in XENIAL LTS

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux-hwe source package in Yakkety:
  Fix Committed
Status in linux-hwe-edge source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  In Progress
Status in linux-hwe source package in Zesty:
  Confirmed
Status in linux-hwe-edge source package in Zesty:
  Confirmed

Bug description:
  Since I upgraded the kernel from linux-image-4.8.0-46-generic to
  linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to
  change the MTU.

  It seems to be known bug already fixed:
  https://bugzilla.kernel.org/show_bug.cgi?id=194763

  # ip l sh eno49
  2: eno49:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh eno50
  3: eno50:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh bond0
  6: bond0:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l set mtu 9000 bond0
  RTNETLINK answers: Invalid argument

  root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog
  Apr  4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 
requested, hw max 1500

  # modinfo ixgbe
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko
  version:4.4.0-k
  license:GPL
  description:Intel(R) 10 Gigabit PCI Express Network Driver

  # modinfo bonding
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko
  author: Thomas Davis, tada...@lbl.gov and many others
  description:Ethernet Channel Bonding Driver, v3.7.1
  version:3.7.1

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

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


[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

2017-05-23 Thread Jesse Sung
These patches are in 4.8.0-53, which is in -proposed right now. It will
be available in -updates with next SRU release if everything goes well.

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

Title:
  bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10
  in XENIAL LTS

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux-hwe source package in Yakkety:
  Fix Committed
Status in linux-hwe-edge source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  In Progress
Status in linux-hwe source package in Zesty:
  Confirmed
Status in linux-hwe-edge source package in Zesty:
  Confirmed

Bug description:
  Since I upgraded the kernel from linux-image-4.8.0-46-generic to
  linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to
  change the MTU.

  It seems to be known bug already fixed:
  https://bugzilla.kernel.org/show_bug.cgi?id=194763

  # ip l sh eno49
  2: eno49:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh eno50
  3: eno50:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh bond0
  6: bond0:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l set mtu 9000 bond0
  RTNETLINK answers: Invalid argument

  root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog
  Apr  4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 
requested, hw max 1500

  # modinfo ixgbe
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko
  version:4.4.0-k
  license:GPL
  description:Intel(R) 10 Gigabit PCI Express Network Driver

  # modinfo bonding
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko
  author: Thomas Davis, tada...@lbl.gov and many others
  description:Ethernet Channel Bonding Driver, v3.7.1
  version:3.7.1

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

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


[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49, xenial-hwe)

2017-05-11 Thread Jesse Sung
Re-open zesty task because some patches are still missing (for example
the fix for openvswitch).

** Changed in: linux (Ubuntu Yakkety)
 Assignee: Joseph Salisbury (jsalisbury) => Jesse Sung (wenchien)

** Changed in: linux (Ubuntu Zesty)
   Status: Fix Released => In Progress

** Changed in: linux (Ubuntu Zesty)
 Assignee: (unassigned) => Jesse Sung (wenchien)

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

Title:
  bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or
  4.8.0-49, xenial-hwe)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  In Progress
Status in linux-hwe source package in Yakkety:
  Confirmed
Status in linux-hwe-edge source package in Yakkety:
  Confirmed
Status in linux source package in Zesty:
  In Progress
Status in linux-hwe source package in Zesty:
  Confirmed
Status in linux-hwe-edge source package in Zesty:
  Confirmed

Bug description:
  Since I upgraded the kernel from linux-image-4.8.0-46-generic to
  linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to
  change the MTU.

  It seems to be known bug already fixed:
  https://bugzilla.kernel.org/show_bug.cgi?id=194763

  # ip l sh eno49
  2: eno49: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh eno50
  3: eno50: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh bond0
  6: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l set mtu 9000 bond0
  RTNETLINK answers: Invalid argument

  root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog
  Apr  4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 
requested, hw max 1500

  # modinfo ixgbe
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko
  version:4.4.0-k
  license:GPL
  description:Intel(R) 10 Gigabit PCI Express Network Driver

  # modinfo bonding
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko
  author: Thomas Davis, tada...@lbl.gov and many others
  description:Ethernet Channel Bonding Driver, v3.7.1
  version:3.7.1

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

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


  1   2   3   >