[Kernel-packages] [Bug 1945938] Re: [impish] Remove the downstream xr-usb-uart driver

[Shrirang Bagul]

** Tags removed: verification-needed-focal verification-needed-impish
** Tags added: verification-done-focal verification-done-impish

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

Title:
  [impish] Remove the downstream xr-usb-uart driver

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

Bug description:
  [Impact]

  The xr-usb-serial custom (downstream vendor) driver was added in Xenial LTS 
kernel
  to add support for USB UART chips:
  Family: USB UART
  Part Numbers:
  XR21V1410, XR21V1412, XR21V1414,
  XR21B1411, XR21B1420, XR21B1422,
  XR21B1424, XR22801, XR22802,
  XR22804

  [Fix]
  In 5.13.x, support for these devices was added to the kernel via. following 
patch series:
  Link: https://lore.kernel.org/all/20210412095557.1213-1-jo...@kernel.org/

  There have been long term maintenance challenges with the downstream vendor 
driver
  over the period of time (since 4.4.y based Xenial LTS). Now that upstream 
driver
  supports most of the above part numbers, let's remove this redundant 
out-of-tree driver.

  [Test]
  The driver was functionally verified to work fine with XR21V1412. The support 
for
  other chips with part numbers mentioned above are also supported with the 
above
  patch series.

  [Where problems could occur]
  The downstream driver was designed to work with specific BIOS configs only
  defined on an IoT GW project which is locked to use only Xenial ESM and 
Bionic LTS
  kernels, there is a low chance of regression on the Impish series.

  [This is a tracking bug, please do not triage]

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


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

[Kernel-packages] [Bug 1945938] Re: [impish] Remove the downstream xr-usb-uart driver

[Shrirang Bagul]

** Description changed:

  [Impact]
  
  The xr-usb-serial custom (downstream vendor) driver was added in Xenial LTS 
kernel
  to add support for USB UART chips:
  Family: USB UART
  Part Numbers:
  XR21V1410, XR21V1412, XR21V1414,
  XR21B1411, XR21B1420, XR21B1422,
  XR21B1424, XR22801, XR22802,
  XR22804
  
  [Fix]
  In 5.13.x, support for these devices was added to the kernel via. following 
patch series:
  Link: https://lore.kernel.org/all/20210412095557.1213-1-jo...@kernel.org/
  
  There have been long term maintenance challenges with the downstream vendor 
driver
  over the period of time (since 4.4.y based Xenial LTS). Now that upstream 
driver
  supports most of the above part numbers, let's remove this redundant 
out-of-tree driver.
  
  [Test]
  The driver was functionally verified to work fine with XR21V1412. The support 
for
  other chips with part numbers mentioned above are also supported with the 
above
  patch series.
  
  [Where problems could occur]
  The downstream driver was designed to work with specific BIOS configs only
  defined on an IoT GW project which is locked to use only Xenial ESM and 
Bionic LTS
  kernels, there is a low chance of regression on the Impish series.
+ 
+ [This is a tracking bug, please do not triage]

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

Title:
  [impish] Remove the downstream xr-usb-uart driver

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Impish:
  Confirmed

Bug description:
  [Impact]

  The xr-usb-serial custom (downstream vendor) driver was added in Xenial LTS 
kernel
  to add support for USB UART chips:
  Family: USB UART
  Part Numbers:
  XR21V1410, XR21V1412, XR21V1414,
  XR21B1411, XR21B1420, XR21B1422,
  XR21B1424, XR22801, XR22802,
  XR22804

  [Fix]
  In 5.13.x, support for these devices was added to the kernel via. following 
patch series:
  Link: https://lore.kernel.org/all/20210412095557.1213-1-jo...@kernel.org/

  There have been long term maintenance challenges with the downstream vendor 
driver
  over the period of time (since 4.4.y based Xenial LTS). Now that upstream 
driver
  supports most of the above part numbers, let's remove this redundant 
out-of-tree driver.

  [Test]
  The driver was functionally verified to work fine with XR21V1412. The support 
for
  other chips with part numbers mentioned above are also supported with the 
above
  patch series.

  [Where problems could occur]
  The downstream driver was designed to work with specific BIOS configs only
  defined on an IoT GW project which is locked to use only Xenial ESM and 
Bionic LTS
  kernels, there is a low chance of regression on the Impish series.

  [This is a tracking bug, please do not triage]

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


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

[Kernel-packages] [Bug 1945938] Re: [impish] Remove the downstream xr-usb-uart driver

[Shrirang Bagul]

** Description changed:

  [Impact]
  
- The xr-usb-serial custom (downstream vendor) driver was added in Xenial LTS 
kernel 
+ The xr-usb-serial custom (downstream vendor) driver was added in Xenial LTS 
kernel
  to add support for USB UART chips:
  Family: USB UART
  Part Numbers:
- XR21V1410, XR21V1412, XR21V1414,
- XR21B1411, XR21B1420, XR21B1422,
- XR21B1424, XR22801, XR22802,
- XR22804
+ XR21V1410, XR21V1412, XR21V1414,
+ XR21B1411, XR21B1420, XR21B1422,
+ XR21B1424, XR22801, XR22802,
+ XR22804
  
  [Fix]
  In 5.13.x, support for these devices was added to the kernel via. following 
patch series:
  Link: https://lore.kernel.org/all/20210412095557.1213-1-jo...@kernel.org/
  
  There have been long term maintenance challenges with the downstream vendor 
driver
- over the period of time (since 4.4.y based Xenial LTS). Now that upstream 
driver 
+ over the period of time (since 4.4.y based Xenial LTS). Now that upstream 
driver
  supports most of the above part numbers, let's remove this redundant 
out-of-tree driver.
  
  [Test]
  The driver was functionally verified to work fine with XR21V1412. The support 
for
- other chips with part numbers mentioned above are also supported with the 
above 
+ other chips with part numbers mentioned above are also supported with the 
above
  patch series.
  
  [Where problems could occur]
- Low. The downstream driver was designed to work with specific BIOS configs 
only 
+ The downstream driver was designed to work with specific BIOS configs only
  defined on an IoT GW project which is locked to use only Xenial ESM and 
Bionic LTS
  kernels, there is a low chance of regression on the Impish series.

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

Title:
  [impish] Remove the downstream xr-usb-uart driver

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Impish:
  Confirmed

Bug description:
  [Impact]

  The xr-usb-serial custom (downstream vendor) driver was added in Xenial LTS 
kernel
  to add support for USB UART chips:
  Family: USB UART
  Part Numbers:
  XR21V1410, XR21V1412, XR21V1414,
  XR21B1411, XR21B1420, XR21B1422,
  XR21B1424, XR22801, XR22802,
  XR22804

  [Fix]
  In 5.13.x, support for these devices was added to the kernel via. following 
patch series:
  Link: https://lore.kernel.org/all/20210412095557.1213-1-jo...@kernel.org/

  There have been long term maintenance challenges with the downstream vendor 
driver
  over the period of time (since 4.4.y based Xenial LTS). Now that upstream 
driver
  supports most of the above part numbers, let's remove this redundant 
out-of-tree driver.

  [Test]
  The driver was functionally verified to work fine with XR21V1412. The support 
for
  other chips with part numbers mentioned above are also supported with the 
above
  patch series.

  [Where problems could occur]
  The downstream driver was designed to work with specific BIOS configs only
  defined on an IoT GW project which is locked to use only Xenial ESM and 
Bionic LTS
  kernels, there is a low chance of regression on the Impish series.

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


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

[Kernel-packages] [Bug 1945938] [NEW] [impish] Remove the downstream xr-usb-uart driver

[Shrirang Bagul]

Public bug reported:

[Impact]

The xr-usb-serial custom (downstream vendor) driver was added in Xenial LTS 
kernel 
to add support for USB UART chips:
Family: USB UART
Part Numbers:
XR21V1410, XR21V1412, XR21V1414,
XR21B1411, XR21B1420, XR21B1422,
XR21B1424, XR22801, XR22802,
XR22804

[Fix]
In 5.13.x, support for these devices was added to the kernel via. following 
patch series:
Link: https://lore.kernel.org/all/20210412095557.1213-1-jo...@kernel.org/

There have been long term maintenance challenges with the downstream vendor 
driver
over the period of time (since 4.4.y based Xenial LTS). Now that upstream 
driver 
supports most of the above part numbers, let's remove this redundant 
out-of-tree driver.

[Test]
The driver was functionally verified to work fine with XR21V1412. The support 
for
other chips with part numbers mentioned above are also supported with the above 
patch series.

[Where problems could occur]
Low. The downstream driver was designed to work with specific BIOS configs only 
defined on an IoT GW project which is locked to use only Xenial ESM and Bionic 
LTS
kernels, there is a low chance of regression on the Impish series.

** Affects: linux (Ubuntu)
 Importance: High
 Status: Confirmed

** Affects: linux (Ubuntu Impish)
 Importance: High
 Status: Confirmed

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

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

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

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

Title:
  [impish] Remove the downstream xr-usb-uart driver

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Impish:
  Confirmed

Bug description:
  [Impact]

  The xr-usb-serial custom (downstream vendor) driver was added in Xenial LTS 
kernel 
  to add support for USB UART chips:
  Family: USB UART
  Part Numbers:
  XR21V1410, XR21V1412, XR21V1414,
  XR21B1411, XR21B1420, XR21B1422,
  XR21B1424, XR22801, XR22802,
  XR22804

  [Fix]
  In 5.13.x, support for these devices was added to the kernel via. following 
patch series:
  Link: https://lore.kernel.org/all/20210412095557.1213-1-jo...@kernel.org/

  There have been long term maintenance challenges with the downstream vendor 
driver
  over the period of time (since 4.4.y based Xenial LTS). Now that upstream 
driver 
  supports most of the above part numbers, let's remove this redundant 
out-of-tree driver.

  [Test]
  The driver was functionally verified to work fine with XR21V1412. The support 
for
  other chips with part numbers mentioned above are also supported with the 
above 
  patch series.

  [Where problems could occur]
  Low. The downstream driver was designed to work with specific BIOS configs 
only 
  defined on an IoT GW project which is locked to use only Xenial ESM and 
Bionic LTS
  kernels, there is a low chance of regression on the Impish series.

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


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

[Kernel-packages] [Bug 1906770] Re: Kernel 5.4.0-56 Wi-Fi does not connect

[Shrirang Bagul]

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

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

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

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

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

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Shrirang Bagul (shrirang-bagul)

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

Title:
  Kernel 5.4.0-56 Wi-Fi does not connect

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress

Bug description:
  After updating to 5.4.0-56 (generic) on Mint 19.3, Wi-Fi cannot
  complete connection to network with Netgear A6210 USB adapter
  (Mediatek MT7612U chipset). Network manager can see available
  networks, but attempting to connect to a network stalls on
  "connecting" and does not complete connection. Reverting to 5.4.0-54
  solves problem. I did not see this problem after updating to 5.4.0-56
  on a 10-year-old Toshiba Satellite laptop (also Mint 19.3), so it
  appears related to the Netgear/Mediatek hardware.

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

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

[Kernel-packages] [Bug 1906770] Re: Kernel 5.4.0-56 Wi-Fi does not connect

[Shrirang Bagul]

A test kernel compiled with the patch in comment#13 is uploaded to:
https://people.canonical.com/~shrirang-bagul/lp1906770/

Give it a try and verify if this fixes the issue

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

Title:
  Kernel 5.4.0-56 Wi-Fi does not connect

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating to 5.4.0-56 (generic) on Mint 19.3, Wi-Fi cannot
  complete connection to network with Netgear A6210 USB adapter
  (Mediatek MT7612U chipset). Network manager can see available
  networks, but attempting to connect to a network stalls on
  "connecting" and does not complete connection. Reverting to 5.4.0-54
  solves problem. I did not see this problem after updating to 5.4.0-56
  on a 10-year-old Toshiba Satellite laptop (also Mint 19.3), so it
  appears related to the Netgear/Mediatek hardware.

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

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

[Kernel-packages] [Bug 1863314] Re: xenial/linux-cascade: 4.4.0-1015.17 -proposed tracker

[Shrirang Bagul]

** Summary changed:

- xenial/linux-cascade:  -proposed tracker
+ xenial/linux-cascade: 4.4.0-1015.17 -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) => Shrirang Bagul 
(shrirang-bagul)

** 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) => Shrirang Bagul 
(shrirang-bagul)

** 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) => Shrirang Bagul 
(shrirang-bagul)

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

Title:
  xenial/linux-cascade: 4.4.0-1015.17 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
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-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

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: 1865106
  packages:
main: linux-cascade
meta: linux-meta-cascade
signed: linux-signed-cascade
  phase: Packaging
  phase-changed: Monday, 02. March 2020 09:35 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
  trackers:
xenial/linux-cascade/cascade-kernel: bug 1863313
  variant: debs

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

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

[Kernel-packages] [Bug 1864413] Re: [bionic] Support Redpine RS9113 Wifi+BT chip on Dell Edge 300x IoT Gateways

[Shrirang Bagul]

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

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

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

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

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

Title:
  [bionic] Support Redpine RS9113 Wifi+BT chip on Dell Edge 300x IoT
  Gateways

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  [Impact]
  To support RS9113 Wifi+BT chip on Dell Edge 300x IoT Gateways.

  [Fixes]
  Most of the patches are already upstream (either Accepted or under review) 
and being
  tracked here:
  https://patchwork.kernel.org/project/linux-wireless/list/?state=*=rsi%3A

  SAUCE patches have been tested by Canonical CE-QA (based on
  Ubuntu-4.15.0-73.82).

  [Regression Potential]
  Low. We've carried these patches in the linux-oem (4.15.y) kernel for more 
than 2 years.
  Also, the impact is limited to the Redpine RS9113 Wifi+BT with following 
VID/PID
  { SDIO_DEVICE(0x041B, 0x9330) }.

  [Note]
  linux-oem SRU tracking bug link: http://bugs.launchpad.net/bugs/1657682

  This bug is used for tracking purposes, please do not triage.

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

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

[Kernel-packages] [Bug 1864413] [NEW] [bionic] Support Redpine RS9113 Wifi+BT chip on Dell Edge 300x IoT Gateways

[Shrirang Bagul]

Public bug reported:

[Impact]
To support RS9113 Wifi+BT chip on Dell Edge 300x IoT Gateways.

[Fixes]
Most of the patches are already upstream (either Accepted or under review) and 
being
tracked here:
https://patchwork.kernel.org/project/linux-wireless/list/?state=*=rsi%3A

SAUCE patches have been tested by Canonical CE-QA (based on
Ubuntu-4.15.0-73.82).

[Regression Potential]
Low. We've carried these patches in the linux-oem (4.15.y) kernel for more than 
2 years.
Also, the impact is limited to the Redpine RS9113 Wifi+BT with following VID/PID
{ SDIO_DEVICE(0x041B, 0x9330) }.

[Note]
linux-oem SRU tracking bug link: http://bugs.launchpad.net/bugs/1657682

This bug is used for tracking purposes, please do not triage.

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

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


** Tags: bionic

** Description changed:

  [Impact]
- To support RS9113 Wifi+BT chip on Dell Edge 300x IoT Gateways. 
+ To support RS9113 Wifi+BT chip on Dell Edge 300x IoT Gateways.
  
  [Fixes]
  Most of the patches are already upstream (either Accepted or under review) 
and being
  tracked here:
  https://patchwork.kernel.org/project/linux-wireless/list/?state=*=rsi%3A
  
  SAUCE patches have been tested by Canonical CE-QA (based on
  Ubuntu-4.15.0-73.82).
  
  [Regression Potential]
  Low. We've carried these patches in the linux-oem (4.15.y) kernel for more 
than 2 years.
  Also, the impact is limited to the Redpine RS9113 Wifi+BT with following 
VID/PID
  { SDIO_DEVICE(0x041B, 0x9330) }.
  
+ [Note]
+ linux-oem SRU tracking bug link: http://bugs.launchpad.net/bugs/1657682
+ 
  This bug is used for tracking purposes, please do not triage.

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

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

Title:
  [bionic] Support Redpine RS9113 Wifi+BT chip on Dell Edge 300x IoT
  Gateways

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

Bug description:
  [Impact]
  To support RS9113 Wifi+BT chip on Dell Edge 300x IoT Gateways.

  [Fixes]
  Most of the patches are already upstream (either Accepted or under review) 
and being
  tracked here:
  https://patchwork.kernel.org/project/linux-wireless/list/?state=*=rsi%3A

  SAUCE patches have been tested by Canonical CE-QA (based on
  Ubuntu-4.15.0-73.82).

  [Regression Potential]
  Low. We've carried these patches in the linux-oem (4.15.y) kernel for more 
than 2 years.
  Also, the impact is limited to the Redpine RS9113 Wifi+BT with following 
VID/PID
  { SDIO_DEVICE(0x041B, 0x9330) }.

  [Note]
  linux-oem SRU tracking bug link: http://bugs.launchpad.net/bugs/1657682

  This bug is used for tracking purposes, please do not triage.

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

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

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

[Shrirang Bagul]

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

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

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

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

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

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

Title:
  [bionic]  Add HMS CAN driver for Dell Edge Gateways

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

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.

  linux-oem bug: https://launchpad.net/bugs/1807339

  This bug is for tracking only, please don't triage.

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

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

[Kernel-packages] [Bug 1864157] [NEW] [bionic] Add HMS CAN driver for Dell Edge Gateways

[Shrirang Bagul]

Public bug reported:

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

linux-oem bug: https://launchpad.net/bugs/1807339

This bug is for tracking only, please don't triage.

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

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

Title:
  [bionic]  Add HMS CAN driver for Dell Edge Gateways

Status in linux package in Ubuntu:
  New

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.

  linux-oem bug: https://launchpad.net/bugs/1807339

  This bug is for tracking only, please don't triage.

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

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

[Kernel-packages] [Bug 1864147] Re: [bionic] Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

[Shrirang Bagul]

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

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

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

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

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

Title:
  [bionic]  Support Intel Atom (Baytrail-I) HS-UART serdev slaves over
  tty

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  [SRU Justification]

  [Impact]
  Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

  On systems using Intel Atom (Baytrail-I) SoC's, slave devices connected on
  HSUART1/2 ports are described by the ACPI BIOS as virtual hardware using
  HID's INT3511/INT3512.

  As a consequence, HW manufacturers have complete freedom to install any
  devices on-board as long as they can be accessed over serial tty
  interface. Once such device is Dell Edge 3002 IoT Gateway which sports
  ZigBee & GPS devices on the HS-UART ports 1 & 2 respectively.

  Post 4.15, with CONFIG_SERIAL_DEV_BUS=y, serdev port controller driver
  handles the enumeration for the slaves connected on these ports. Also,
  /dev/ttySx device nodes for these ports are no longer exposed to the
  userspace.

  [Fixes]
  This patchset allows the skipped virtual UART's with ACPI HID's mentioned
  above to be enumerated as ttyHSx port.

  [Regression Potential]
  Low. This driver binds only to Intel Atom E38XX (Baytrail-I) virtual serial
  ports on the Dell Edge 300x GW. These updates are being carried in the
  linux-oem (4.15.y) kernel for more than 2 years without any regressions.

  [Note]
  This driver has been submitted upstream and is under review. This issue has
  been identified as a regression in 4.15 and multiple solutions are being
  explored. Meanwhile, to support customer and maintain release schedule,
  this driver needs to be in Ubuntu 4.15 based kernels.
  More info:
  https://marc.info/?t=15245587167=1=2

  linux-oem buglink: http://bugs.launchpad.net/bugs/1690362

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

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

[Kernel-packages] [Bug 1864147] [NEW] [bionic] Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

[Shrirang Bagul]

Public bug reported:

[SRU Justification]

[Impact]
Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

On systems using Intel Atom (Baytrail-I) SoC's, slave devices connected on
HSUART1/2 ports are described by the ACPI BIOS as virtual hardware using
HID's INT3511/INT3512.

As a consequence, HW manufacturers have complete freedom to install any
devices on-board as long as they can be accessed over serial tty
interface. Once such device is Dell Edge 3002 IoT Gateway which sports
ZigBee & GPS devices on the HS-UART ports 1 & 2 respectively.

Post 4.15, with CONFIG_SERIAL_DEV_BUS=y, serdev port controller driver
handles the enumeration for the slaves connected on these ports. Also,
/dev/ttySx device nodes for these ports are no longer exposed to the
userspace.

[Fixes]
This patchset allows the skipped virtual UART's with ACPI HID's mentioned
above to be enumerated as ttyHSx port.

[Regression Potential]
Low. This driver binds only to Intel Atom E38XX (Baytrail-I) virtual serial
ports on the Dell Edge 300x GW. These updates are being carried in the
linux-oem (4.15.y) kernel for more than 2 years without any regressions.

[Note]
This driver has been submitted upstream and is under review. This issue has
been identified as a regression in 4.15 and multiple solutions are being
explored. Meanwhile, to support customer and maintain release schedule,
this driver needs to be in Ubuntu 4.15 based kernels.
More info:
https://marc.info/?t=15245587167=1=2

linux-oem buglink: http://bugs.launchpad.net/bugs/1690362

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

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

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

** Description changed:

  [SRU Justification]
  
  [Impact]
  Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty
  
  On systems using Intel Atom (Baytrail-I) SoC's, slave devices connected on
  HSUART1/2 ports are described by the ACPI BIOS as virtual hardware using
  HID's INT3511/INT3512.
  
  As a consequence, HW manufacturers have complete freedom to install any
  devices on-board as long as they can be accessed over serial tty
  interface. Once such device is Dell Edge 3002 IoT Gateway which sports
  ZigBee & GPS devices on the HS-UART ports 1 & 2 respectively.
  
  Post 4.15, with CONFIG_SERIAL_DEV_BUS=y, serdev port controller driver
  handles the enumeration for the slaves connected on these ports. Also,
  /dev/ttySx device nodes for these ports are no longer exposed to the
  userspace.
  
  [Fixes]
  This patchset allows the skipped virtual UART's with ACPI HID's mentioned
  above to be enumerated as ttyHSx port.
  
  [Regression Potential]
  Low. This driver binds only to Intel Atom E38XX (Baytrail-I) virtual serial
  ports on the Dell Edge 300x GW. These updates are being carried in the
  linux-oem (4.15.y) kernel for more than 2 years without any regressions.
  
  [Note]
  This driver has been submitted upstream and is under review. This issue has
  been identified as a regression in 4.15 and multiple solutions are being
  explored. Meanwhile, to support customer and maintain release schedule,
  this driver needs to be in Ubuntu 4.15 based kernels.
  More info:
  https://marc.info/?t=15245587167=1=2
  
- linux-oem buglink: http://bugs.launchpad.net/bugs/ 1690362
+ linux-oem buglink: http://bugs.launchpad.net/bugs/1690362

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

Title:
  [bionic]  Support Intel Atom (Baytrail-I) HS-UART serdev slaves over
  tty

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

Bug description:
  [SRU Justification]

  [Impact]
  Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

  On systems using Intel Atom (Baytrail-I) SoC's, slave devices connected on
  HSUART1/2 ports are described by the ACPI BIOS as virtual hardware using
  HID's INT3511/INT3512.

  As a consequence, HW manufacturers have complete freedom to install any
  devices on-board as long as they can be accessed over serial tty
  interface. Once such device is Dell Edge 3002 IoT Gateway which sports
  ZigBee & GPS devices on the HS-UART ports 1 & 2 respectively.

  Post 4.15, with CONFIG_SERIAL_DEV_BUS=y, serdev port controller driver
  handles the enumeration for the slaves connected on these ports. Also,
  /dev/ttySx device nodes for these ports are no longer exposed to the
  userspace.

  [Fixes]
  This patchset allows the skipped virtual UART's with ACPI HID's mentioned
  above to be enumerated as ttyHSx port.

  [Regression Potential]
  Low. This driver binds only to Intel Atom E38XX (Baytrail-I) virtual serial
  ports on the Dell Edge 300x GW. These updates are being carried in the
  linux-oem (4.15.y) kernel for more than 2 years without any regressions.

  [Note]

[Kernel-packages] [Bug 1863834] [NEW] [bionic] updates to Exar USB serial driver

[Shrirang Bagul]

Public bug reported:

[SRU Justification]

[Impact]
This update adds the latest vendor release version on the Exar USB serial 
device.

[Fixes]
New features include:
1. Fix for RX fail after wake-up from sleep (S3/S4)
2. Removes unnecessary debug messages

Changelog:

Version 1B, 11/6/2015
Fixed Bug: The conditional logic to support kernel 3.9 was
incorrect(line 396 in xr_usb_serial_common.c).

Version 1A, 1/9/2015
This driver will work with any USB UART function in these Exar devices:
XR21V1410/1412/1414
XR21B1411
XR21B1420/1422/1424
XR22801/802/804

Exar serial devices are typically enumerated as /dev/ttyXRUSB[0-3].

[Regression Potential]
Low. This driver binds to Exar USB Serial devices on the Dell Edge 300x GW.
These updates are being carried in the linux-oem (4.15.y) kernel for more than 
2 years without any regressions.

This bug is for tracking purposes only, please don't triage.

** Affects: linux (Ubuntu)
 Importance: High
 Status: Confirmed

** Affects: linux (Ubuntu Bionic)
 Importance: High
 Status: Confirmed

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

** Description changed:

  [SRU Justification]
  
  [Impact]
  This update adds the latest vendor release version on the Exar USB serial 
device.
  
  [Fixes]
  New features include:
  1. Fix for RX fail after wake-up from sleep (S3/S4)
  2. Removes unnecessary debug messages
  
  Changelog:
  
  Version 1B, 11/6/2015
  Fixed Bug: The conditional logic to support kernel 3.9 was
  incorrect(line 396 in xr_usb_serial_common.c).
  
  Version 1A, 1/9/2015
  This driver will work with any USB UART function in these Exar devices:
  XR21V1410/1412/1414
  XR21B1411
  XR21B1420/1422/1424
  XR22801/802/804
  
  Exar serial devices are typically enumerated as /dev/ttyXRUSB[0-3].
  
  [Regression Potential]
- Low. This driver binds to Exar USB Serial devices on the Dell Edge 300x GW. 
+ Low. This driver binds to Exar USB Serial devices on the Dell Edge 300x GW.
  These updates are being carried in the linux-oem (4.15.y) kernel for more 
than 2 years without any regressions.
+ 
+ This bug is for tracking purposes only, please don't triage.

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

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

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

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

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

Title:
  [bionic] updates to Exar USB serial driver

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  [SRU Justification]

  [Impact]
  This update adds the latest vendor release version on the Exar USB serial 
device.

  [Fixes]
  New features include:
  1. Fix for RX fail after wake-up from sleep (S3/S4)
  2. Removes unnecessary debug messages

  Changelog:

  Version 1B, 11/6/2015
  Fixed Bug: The conditional logic to support kernel 3.9 was
  incorrect(line 396 in xr_usb_serial_common.c).

  Version 1A, 1/9/2015
  This driver will work with any USB UART function in these Exar devices:
  XR21V1410/1412/1414
  XR21B1411
  XR21B1420/1422/1424
  XR22801/802/804

  Exar serial devices are typically enumerated as /dev/ttyXRUSB[0-3].

  [Regression Potential]
  Low. This driver binds to Exar USB Serial devices on the Dell Edge 300x GW.
  These updates are being carried in the linux-oem (4.15.y) kernel for more 
than 2 years without any regressions.

  This bug is for tracking purposes only, please don't triage.

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

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

[Kernel-packages] [Bug 1863732] Re: [bionic] hts221 sensor stops working after resume from S3/S4

[Shrirang Bagul]

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

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

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

Title:
  [bionic]  hts221 sensor stops working after resume from S3/S4

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  [SRU Justification]

  [Impact]

  Dell Edge 300x IoT Gateways have a relative humidity sensor hts221.
  The sensor stops working (and reports stale values) after the system
  resumes from suspend-to-ram/suspend-to-disk PM states.

  == Fix ==
  AV_CONF register (RH & TEMP. oversampling ratio's) and CTRL1 register (ODR & 
BDU settings) values are lost after suspend.

  While the change in AV_CONF updates the sensor resolution modes
  (overriding the user configuration before the device went to suspend);
  loss of the contents of the CTRL1 register leads to failure in reading
  sensor

  This patch restores the AV_CONF & CTRL1 registers after

  Already submitted upstream for both 4.17.y and 4.14.y (LTS) for review:
  4.17.y: https://marc.info/?t=15245587167=1=2
  4.14.y: https://marc.info/?t=15250624201=1=2

  However, the issue is only affecting the Dell GW and not ST micro
  devel. boards.

  == Risk of Regression ==
  Low.Tthe bug affects only the Dell GW and the patch is being carried in 
linux-oem (4.15.y) since last 2 years without any regression.

  linux-oem buglink: https://bugs.launchpad.net/bugs/1769658

  This bug is for tracking purposes only, please don't triage.

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

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

[Kernel-packages] [Bug 1863732] [NEW] [bionic] hts221 sensor stops working after resume from S3/S4

[Shrirang Bagul]

Public bug reported:

[SRU Justification]

[Impact]

Dell Edge 300x IoT Gateways have a relative humidity sensor hts221. The
sensor stops working (and reports stale values) after the system resumes
from suspend-to-ram/suspend-to-disk PM states.

== Fix ==
AV_CONF register (RH & TEMP. oversampling ratio's) and CTRL1 register (ODR & 
BDU settings) values are lost after suspend.

While the change in AV_CONF updates the sensor resolution modes
(overriding the user configuration before the device went to suspend);
loss of the contents of the CTRL1 register leads to failure in reading
sensor

This patch restores the AV_CONF & CTRL1 registers after

Already submitted upstream for both 4.17.y and 4.14.y (LTS) for review:
4.17.y: https://marc.info/?t=15245587167=1=2
4.14.y: https://marc.info/?t=15250624201=1=2

However, the issue is only affecting the Dell GW and not ST micro devel.
boards.

== Risk of Regression ==
Low.Tthe bug affects only the Dell GW and the patch is being carried in 
linux-oem (4.15.y) since last 2 years without any regression.

linux-oem buglink: https://bugs.launchpad.net/bugs/1769658

This bug is for tracking purposes only, please don't triage.

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

** Affects: linux (Ubuntu Bionic)
 Importance: High
 Status: Confirmed

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

** Description changed:

  [SRU Justification]
  
  [Impact]
  
  Dell Edge 300x IoT Gateways have a relative humidity sensor hts221. The
  sensor stops working (and reports stale values) after the system resumes
  from suspend-to-ram/suspend-to-disk PM states.
  
  == Fix ==
  AV_CONF register (RH & TEMP. oversampling ratio's) and CTRL1 register (ODR & 
BDU settings) values are lost after suspend.
- 
- While the change in AV_CONF updates the sensor resolution modes (overriding 
the user configuration before the device went to suspend); loss of the contents 
of the CTRL1 register leads to failure in reading sensor 
+ 
+ While the change in AV_CONF updates the sensor resolution modes
+ (overriding the user configuration before the device went to suspend);
+ loss of the contents of the CTRL1 register leads to failure in reading
+ sensor
  
  This patch restores the AV_CONF & CTRL1 registers after
  
  Already submitted upstream for both 4.17.y and 4.14.y (LTS) for review:
  4.17.y: https://marc.info/?t=15245587167=1=2
  4.14.y: https://marc.info/?t=15250624201=1=2
  
  However, the issue is only affecting the Dell GW and not ST micro devel.
  boards.
  
  == Risk of Regression ==
  Low.Tthe bug affects only the Dell GW and the patch is being carried in 
linux-oem (4.15.y) since last 2 years without any regression.
  
+ linux-oem buglink: https://bugs.launchpad.net/ubuntu/+source/linux-
+ oem/+bug/1769658
+ 
  This bug is for tracking purposes only, please don't triage.

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

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

** Description changed:

  [SRU Justification]
  
  [Impact]
  
  Dell Edge 300x IoT Gateways have a relative humidity sensor hts221. The
  sensor stops working (and reports stale values) after the system resumes
  from suspend-to-ram/suspend-to-disk PM states.
  
  == Fix ==
  AV_CONF register (RH & TEMP. oversampling ratio's) and CTRL1 register (ODR & 
BDU settings) values are lost after suspend.
  
  While the change in AV_CONF updates the sensor resolution modes
  (overriding the user configuration before the device went to suspend);
  loss of the contents of the CTRL1 register leads to failure in reading
  sensor
  
  This patch restores the AV_CONF & CTRL1 registers after
  
  Already submitted upstream for both 4.17.y and 4.14.y (LTS) for review:
  4.17.y: https://marc.info/?t=15245587167=1=2
  4.14.y: https://marc.info/?t=15250624201=1=2
  
  However, the issue is only affecting the Dell GW and not ST micro devel.
  boards.
  
  == Risk of Regression ==
  Low.Tthe bug affects only the Dell GW and the patch is being carried in 
linux-oem (4.15.y) since last 2 years without any regression.
  
- linux-oem buglink: https://bugs.launchpad.net/ubuntu/+source/linux-
- oem/+bug/1769658
+ linux-oem buglink: https://bugs.launchpad.net/bugs/1769658
  
  This bug is for tracking purposes only, please don't triage.

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

Title:
  [bionic]  hts221 sensor stops working after resume from S3/S4

Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  Confirmed

Bug description:
  [SRU Justification]

  [Impact]

  Dell Edge 300x IoT Gateways have a relative humidity sensor hts221.
  The sensor stops working (and reports stale values) after the system
  resumes from suspend-to-ram/suspend-to-disk PM 

[Kernel-packages] [Bug 1861109] Re: xenial/linux-cascade: 4.4.0-1014.16 -proposed tracker

[Shrirang Bagul]

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Jesse Sung (wenchien) => Shrirang Bagul (shrirang-bagul)

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Jesse Sung (wenchien) => Shrirang Bagul (shrirang-bagul)

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Jesse Sung (wenchien) => Shrirang Bagul (shrirang-bagul)

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

Title:
  xenial/linux-cascade: 4.4.0-1014.16 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
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-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

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: 1861122
  packages:
main: linux-cascade
meta: linux-meta-cascade
signed: linux-signed-cascade
  phase: Packaging
  phase-changed: Wednesday, 05. February 2020 08:01 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  trackers:
xenial/linux-cascade/cascade-kernel: bug 1861108
  variant: debs

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

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

[Kernel-packages] [Bug 1854825] Re: xenial/linux-cascade: 4.4.0-1012.14 -proposed tracker

[Shrirang Bagul]

** Summary changed:

- xenial/linux-cascade:  -proposed tracker
+ xenial/linux-cascade: 4.4.0-1012.14 -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) => Shrirang Bagul 
(shrirang-bagul)

** 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) => Shrirang Bagul 
(shrirang-bagul)

** 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) => Shrirang Bagul 
(shrirang-bagul)

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

Title:
  xenial/linux-cascade: 4.4.0-1012.14 -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 prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

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: 1854835
  packages:
main: linux-cascade
meta: linux-meta-cascade
signed: linux-signed-cascade
  phase: Packaging
  phase-changed: Thursday, 05. December 2019 10:42 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
  variant: debs

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

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

[Kernel-packages] [Bug 1842433] Re: bionic: support derivative linux-fde kernel

[Shrirang Bagul]

Fixed in linux-fde (4.15.0-1001.2)

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

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

Title:
  bionic: support derivative linux-fde kernel

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Impact:

  Several Ubuntu core projects which require UEFI secure boot with full disk 
encryption enabled.
  The linux-fde derivative kernel which satisfies this requirement by providing 
a kernel binary with an embedded initramfs.

  kmods to support HW crypto, filesystems, HW random number generation, etc. 
The requirement for some of these modules to be built-in comes from:
  1. 
https://bazaar.launchpad.net/~snappy-dev/initramfs-tools-ubuntu-core/trunk/view/head:/modules/modules.amd64
  2. 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-snap/+git/bionic/commit/Makefile?id=6c3c9030bbae7f1a5c1a1773424431fe2c6c

  The purpose of this bug is essentially used to track the kernel config
  changes introduced on top of the amd64-generic Bionic kernel.

  Regression Potential:
  Low. The kernel will be maintained as a derivative kernel.

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

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

[Kernel-packages] [Bug 1853556] Re: [ifc6640][db820c] enable support for UFS drive

[Shrirang Bagul]

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

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

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

Title:
  [ifc6640][db820c] enable support for UFS drive

Status in linux-snapdragon package in Ubuntu:
  New
Status in linux-snapdragon source package in Bionic:
  Confirmed
Status in linux-snapdragon source package in Eoan:
  New

Bug description:
  The Inforce 6640 and Dragonboard 820 have a Universal Flash Storage
  (UFS) drive on board. This is a tracking bug for enabling kernel
  support on these platforms.

  [Impact]
  Both Dragonboard 820c and Inforce 6640 (based on Snapdragon820 SoC) have a
  Universal Flash Drive on-board. These patches fix the instabiliy issues and
  enable support for the UFS. 

  [Fix]
  Fix the bring-up of the QMP PHY shared between the UFS and the PCIE ports.
  This patch set reverts patches picked-up from Linaro development tree and
  replaces them with necessary updates from upstream mainline and stable kernel
  trees.

  [Test Case]
  Test kernel based on Ubuntu-snapdragon-4.15.0-1068.75 was verified on both the
  DB820c and IFC6640. 

  [Regression Risk]
  Low. Kernel configs enabling the UFS were disabled in previous versions.

  This is a tracking bug, please don't triage

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

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

[Kernel-packages] [Bug 1853556] Re: [ifc6640][db820c] enable support for UFS drive

[Shrirang Bagul]

** Description changed:

  The Inforce 6640 and Dragonboard 820 have a Universal Flash Storage
  (UFS) drive on board. This is a tracking bug for enabling kernel support
  on these platforms.
  
+ [Impact]
+ Both Dragonboard 820c and Inforce 6640 (based on Snapdragon820 SoC) have a
+ Universal Flash Drive on-board. These patches fix the instabiliy issues and
+ enable support for the UFS. 
+ 
+ [Fix]
+ Fix the bring-up of the QMP PHY shared between the UFS and the PCIE ports.
+ This patch set reverts patches picked-up from Linaro development tree and
+ replaces them with necessary updates from upstream mainline and stable kernel
+ trees.
+ 
+ [Test Case]
+ Test kernel based on Ubuntu-snapdragon-4.15.0-1068.75 was verified on both the
+ DB820c and IFC6640. 
+ 
+ [Regression Risk]
+ Low. Kernel configs enabling the UFS were disabled in previous versions.
  
  This is a tracking bug, please don't triage

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

Title:
  [ifc6640][db820c] enable support for UFS drive

Status in linux-snapdragon package in Ubuntu:
  New
Status in linux-snapdragon source package in Bionic:
  New
Status in linux-snapdragon source package in Eoan:
  New

Bug description:
  The Inforce 6640 and Dragonboard 820 have a Universal Flash Storage
  (UFS) drive on board. This is a tracking bug for enabling kernel
  support on these platforms.

  [Impact]
  Both Dragonboard 820c and Inforce 6640 (based on Snapdragon820 SoC) have a
  Universal Flash Drive on-board. These patches fix the instabiliy issues and
  enable support for the UFS. 

  [Fix]
  Fix the bring-up of the QMP PHY shared between the UFS and the PCIE ports.
  This patch set reverts patches picked-up from Linaro development tree and
  replaces them with necessary updates from upstream mainline and stable kernel
  trees.

  [Test Case]
  Test kernel based on Ubuntu-snapdragon-4.15.0-1068.75 was verified on both the
  DB820c and IFC6640. 

  [Regression Risk]
  Low. Kernel configs enabling the UFS were disabled in previous versions.

  This is a tracking bug, please don't triage

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

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

[Kernel-packages] [Bug 1853556] [NEW] [ifc6640][db820c] enable support for UFS drive

[Shrirang Bagul]

Public bug reported:

The Inforce 6640 and Dragonboard 820 have a Universal Flash Storage
(UFS) drive on board. This is a tracking bug for enabling kernel support
on these platforms.


This is a tracking bug, please don't triage

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

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

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

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

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

** Description changed:

  The Inforce 6640 and Dragonboard 820 have a Universal Flash Storage
  (UFS) drive on board. This is a tracking bug for enabling kernel support
  on these platforms.
+ 
+ 
+ This is a tracking bug, please don't triage

** Summary changed:

- [ifc6640][db820c] enalbe support for UFS drive
+ [ifc6640][db820c] enable support for UFS drive

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

Title:
  [ifc6640][db820c] enable support for UFS drive

Status in linux-snapdragon package in Ubuntu:
  New
Status in linux-snapdragon source package in Bionic:
  New
Status in linux-snapdragon source package in Eoan:
  New

Bug description:
  The Inforce 6640 and Dragonboard 820 have a Universal Flash Storage
  (UFS) drive on board. This is a tracking bug for enabling kernel
  support on these platforms.

  
  This is a tracking bug, please don't triage

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

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

[Kernel-packages] [Bug 1847969] Re: [Packaging] Support building Flattened Image Tree (FIT) kernels

[Shrirang Bagul]

** 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/1847969

Title:
  [Packaging] Support building Flattened Image Tree (FIT) kernels

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

Bug description:
  [Impact]
  Flexible and powerful format based on Flattened Image Tree -- FIT (similar
  to Flattened Device Tree). It allows the use of images with multiple
  components (several kernels, ramdisks, etc.), with contents protected by
  SHA1, MD5 or CRC32, etc.
  More details: 
https://gitlab.denx.de/u-boot/u-boot/blob/master/doc/uImage.FIT/howto.txt

  The packaging changes will add support for building a FIT kernel
  binary blob which can be subsequently signed. These FIT-signed kernels
  will be consumed by snapcraft recipes to build kernel snaps for
  platforms with U-Boot bootloader enforcing secure boot.

  [Regression Potential]
  Minimal.

  This bug is for tracking purposes only, do not triage.

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

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

[Kernel-packages] [Bug 1847969] Re: [Packaging] Support building Flattened Image Tree (FIT) kernels

[Shrirang Bagul]

** 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/1847969

Title:
  [Packaging] Support building Flattened Image Tree (FIT) kernels

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

Bug description:
  [Impact]
  Flexible and powerful format based on Flattened Image Tree -- FIT (similar
  to Flattened Device Tree). It allows the use of images with multiple
  components (several kernels, ramdisks, etc.), with contents protected by
  SHA1, MD5 or CRC32, etc.
  More details: 
https://gitlab.denx.de/u-boot/u-boot/blob/master/doc/uImage.FIT/howto.txt

  The packaging changes will add support for building a FIT kernel
  binary blob which can be subsequently signed. These FIT-signed kernels
  will be consumed by snapcraft recipes to build kernel snaps for
  platforms with U-Boot bootloader enforcing secure boot.

  [Regression Potential]
  Minimal.

  This bug is for tracking purposes only, do not triage.

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

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

[Kernel-packages] [Bug 1847969] Re: [Packaging] Support building Flattened Image Tree (FIT) kernels

[Shrirang Bagul]

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

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

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

Title:
  [Packaging] Support building Flattened Image Tree (FIT) kernels

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  [Impact]
  Flexible and powerful format based on Flattened Image Tree -- FIT (similar
  to Flattened Device Tree). It allows the use of images with multiple
  components (several kernels, ramdisks, etc.), with contents protected by
  SHA1, MD5 or CRC32, etc.
  More details: 
https://gitlab.denx.de/u-boot/u-boot/blob/master/doc/uImage.FIT/howto.txt

  The packaging changes will add support for building a FIT kernel
  binary blob which can be subsequently signed. These FIT-signed kernels
  will be consumed by snapcraft recipes to build kernel snaps for
  platforms with U-Boot bootloader enforcing secure boot.

  [Regression Potential]
  Minimal.

  This bug is for tracking purposes only, do not triage.

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

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

[Kernel-packages] [Bug 1847969] [NEW] [Packaging] Support building Flattened Image Tree (FIT) kernels

[Shrirang Bagul]

Public bug reported:

[Impact]
Flexible and powerful format based on Flattened Image Tree -- FIT (similar
to Flattened Device Tree). It allows the use of images with multiple
components (several kernels, ramdisks, etc.), with contents protected by
SHA1, MD5 or CRC32, etc.
More details: 
https://gitlab.denx.de/u-boot/u-boot/blob/master/doc/uImage.FIT/howto.txt

The packaging changes will add support for building a FIT kernel binary
blob which can be subsequently signed. These FIT-signed kernels will be
consumed by snapcraft recipes to build kernel snaps for platforms with
U-Boot bootloader enforcing secure boot.

[Regression Potential]
Minimal.

This bug is for tracking purposes only, do not triage.

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

** Affects: linux (Ubuntu Xenial)
 Importance: Undecided
 Status: Confirmed

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

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

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

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

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

** Description changed:

  [Impact]
  Flexible and powerful format based on Flattened Image Tree -- FIT (similar
  to Flattened Device Tree). It allows the use of images with multiple
  components (several kernels, ramdisks, etc.), with contents protected by
- SHA1, MD5 or CRC32.
+ SHA1, MD5 or CRC32, etc.
  More details: 
https://gitlab.denx.de/u-boot/u-boot/blob/master/doc/uImage.FIT/howto.txt
+ 
+ The packaging changes will add support to building a FIT kernel blob
+ which can be subsequently signed. These FIT-signed kernels will be
+ consumed by snapcraft recipes to build kernel snaps for platforms with
+ U-Boot bootloader enforcing secure boot.
  
  [Regression Potential]
  Minimal.
+ 
+ This bug is for tracking purposes only, do not triage.

** Description changed:

  [Impact]
  Flexible and powerful format based on Flattened Image Tree -- FIT (similar
  to Flattened Device Tree). It allows the use of images with multiple
  components (several kernels, ramdisks, etc.), with contents protected by
  SHA1, MD5 or CRC32, etc.
  More details: 
https://gitlab.denx.de/u-boot/u-boot/blob/master/doc/uImage.FIT/howto.txt
  
- The packaging changes will add support to building a FIT kernel blob
- which can be subsequently signed. These FIT-signed kernels will be
+ The packaging changes will add support for building a FIT kernel binary
+ blob which can be subsequently signed. These FIT-signed kernels will be
  consumed by snapcraft recipes to build kernel snaps for platforms with
  U-Boot bootloader enforcing secure boot.
  
  [Regression Potential]
  Minimal.
  
  This bug is for tracking purposes only, do not triage.

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

Title:
  [Packaging] Support building Flattened Image Tree (FIT) kernels

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  [Impact]
  Flexible and powerful format based on Flattened Image Tree -- FIT (similar
  to Flattened Device Tree). It allows the use of images with multiple
  components (several kernels, ramdisks, etc.), with contents protected by
  SHA1, MD5 or CRC32, etc.
  More details: 
https://gitlab.denx.de/u-boot/u-boot/blob/master/doc/uImage.FIT/howto.txt

  The packaging changes will add support for building a FIT kernel
  binary blob which can be subsequently signed. These FIT-signed kernels
  will be consumed by snapcraft recipes to build kernel snaps for
  platforms with U-Boot bootloader enforcing secure boot.

  [Regression Potential]
  Minimal.

  This bug is for tracking purposes only, do not triage.

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

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

[Kernel-packages] [Bug 1842433] Re: bionic: support derivative linux-fde kernel

[Shrirang Bagul]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Shrirang Bagul (shrirang-bagul)

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

Title:
  bionic: support derivative linux-fde kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Impact:

  Several Ubuntu core projects which require UEFI secure boot with full disk 
encryption enabled.
  The linux-fde derivative kernel which satisfies this requirement by providing 
a kernel binary with an embedded initramfs.

  kmods to support HW crypto, filesystems, HW random number generation, etc. 
The requirement for some of these modules to be built-in comes from:
  1. 
https://bazaar.launchpad.net/~snappy-dev/initramfs-tools-ubuntu-core/trunk/view/head:/modules/modules.amd64
  2. 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-snap/+git/bionic/commit/Makefile?id=6c3c9030bbae7f1a5c1a1773424431fe2c6c

  The purpose of this bug is essentially used to track the kernel config
  changes introduced on top of the amd64-generic Bionic kernel.

  Regression Potential:
  Low. The kernel will be maintained as a derivative kernel.

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

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

[Kernel-packages] [Bug 1842433] Re: bionic: support derivative linux-fde kernel

[Shrirang Bagul]

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

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

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

Title:
  bionic: support derivative linux-fde kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Impact:

  Several Ubuntu core projects which require UEFI secure boot with full disk 
encryption enabled.
  The linux-fde derivative kernel which satisfies this requirement by providing 
a kernel binary with an embedded initramfs.

  kmods to support HW crypto, filesystems, HW random number generation, etc. 
The requirement for some of these modules to be built-in comes from:
  1. 
https://bazaar.launchpad.net/~snappy-dev/initramfs-tools-ubuntu-core/trunk/view/head:/modules/modules.amd64
  2. 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-snap/+git/bionic/commit/Makefile?id=6c3c9030bbae7f1a5c1a1773424431fe2c6c

  The purpose of this bug is essentially used to track the kernel config
  changes introduced on top of the amd64-generic Bionic kernel.

  Regression Potential:
  Low. The kernel will be maintained as a derivative kernel.

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

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

[Kernel-packages] [Bug 1842433] [NEW] bionic: support derivative linux-fde kernel

[Shrirang Bagul]

Public bug reported:

Impact:

Several Ubuntu core projects which require UEFI secure boot with full disk 
encryption enabled.
The linux-fde derivative kernel which satisfies this requirement by providing a 
kernel binary with an embedded initramfs.

kmods to support HW crypto, filesystems, HW random number generation, etc. The 
requirement for some of these modules to be built-in comes from:
1. 
https://bazaar.launchpad.net/~snappy-dev/initramfs-tools-ubuntu-core/trunk/view/head:/modules/modules.amd64
2. 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-snap/+git/bionic/commit/Makefile?id=6c3c9030bbae7f1a5c1a1773424431fe2c6c

The purpose of this bug is essentially used to track the kernel config
changes introduced on top of the amd64-generic Bionic kernel.

Regression Potential:
Low. The kernel will be maintained as a derivative kernel.

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

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

Title:
  bionic: support derivative linux-fde kernel

Status in linux package in Ubuntu:
  New

Bug description:
  Impact:

  Several Ubuntu core projects which require UEFI secure boot with full disk 
encryption enabled.
  The linux-fde derivative kernel which satisfies this requirement by providing 
a kernel binary with an embedded initramfs.

  kmods to support HW crypto, filesystems, HW random number generation, etc. 
The requirement for some of these modules to be built-in comes from:
  1. 
https://bazaar.launchpad.net/~snappy-dev/initramfs-tools-ubuntu-core/trunk/view/head:/modules/modules.amd64
  2. 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-snap/+git/bionic/commit/Makefile?id=6c3c9030bbae7f1a5c1a1773424431fe2c6c

  The purpose of this bug is essentially used to track the kernel config
  changes introduced on top of the amd64-generic Bionic kernel.

  Regression Potential:
  Low. The kernel will be maintained as a derivative kernel.

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

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

[Kernel-packages] [Bug 1840437] Re: Support cpufreq, thermal sensors & cooling cells on iMX6Q based Nitrogen6x board

[Shrirang Bagul]

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

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

Title:
  Support cpufreq, thermal sensors & cooling cells on iMX6Q based
  Nitrogen6x board

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  [Impact]
  We ship the armhf flavour of the Bionic kernel which supports the iMX6Q based 
Nitrogen6x board.
  The cpufreq, thermal sensors and cooling cells should be enabled for this 
board.

  [Fix]
  Backport upstream device tree patches to define the device nodes properly.

  [Test]
  Tested and verified on the Nitrogen6x board.

  [Regression Potential]
  Low. These patches update DT nodes with required properties for the 
imx6q_cpufreq and imx_thermal drivers function properly on the platform.

  This bug is for tracking purposes only, don't triage.

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

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

[Kernel-packages] [Bug 1840437] [NEW] Support cpufreq, thermal sensors & cooling cells on iMX6Q based Nitrogen6x board

[Shrirang Bagul]

Public bug reported:

[Impact]
We ship the armhf flavour of the Bionic kernel which supports the iMX6Q based 
Nitrogen6x board.
The cpufreq, thermal sensors and cooling cells should be enabled for this board.

[Fix]
Backport upstream device tree patches to define the device nodes properly.

[Test]
Tested and verified on the Nitrogen6x board.

[Regression Potential]
Low. These patches update DT nodes with required properties for the 
imx6q_cpufreq and imx_thermal drivers function properly on the platform.

This bug is for tracking purposes only, don't triage.

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

** Affects: linux (Ubuntu Bionic)
 Importance: High
 Status: Incomplete

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

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

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

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

Title:
  Support cpufreq, thermal sensors & cooling cells on iMX6Q based
  Nitrogen6x board

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

Bug description:
  [Impact]
  We ship the armhf flavour of the Bionic kernel which supports the iMX6Q based 
Nitrogen6x board.
  The cpufreq, thermal sensors and cooling cells should be enabled for this 
board.

  [Fix]
  Backport upstream device tree patches to define the device nodes properly.

  [Test]
  Tested and verified on the Nitrogen6x board.

  [Regression Potential]
  Low. These patches update DT nodes with required properties for the 
imx6q_cpufreq and imx_thermal drivers function properly on the platform.

  This bug is for tracking purposes only, don't triage.

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

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

[Kernel-packages] [Bug 1804360] Re: Redpine: firmware assert upon assoc timeout

[Shrirang Bagul]

** 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/1804360

Title:
  Redpine: firmware assert upon assoc timeout

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  SRU Justification
  -

  Impact:
  ---
firmware assert upon assoc timeout

  Test Case:
  --
  1) Bring up the Redpine Module in Coex mode 13.
  2) Try to do roaming between two AP's.
  3) At some point, When Association timeout happens and station tries to scan 
and
 observed below firmware assert.
 wlan0: authenticate with ac:a3:1e:a1:1e:85
 wlan0: send auth to ac:a3:1e:a1:1e:85 (try 1/3)
 wlan0: authenticated
 wlan0: associate with ac:a3:1e:a1:1e:85 (try 1/3)
 wlan0: associate with ac:a3:1e:a1:1e:85 (try 2/3)
 wlan0: associate with ac:a3:1e:a1:1e:85 (try 3/3)
 wlan0: association with ac:a3:1e:a1:1e:85 timed out
 ven_rsi_91x: rsi_disable_ps: Cannot accept disable PS in PS_NONE state
 ven_rsi_91x: rsi_interrupt_handler: ==> FIRMWARE Assert <==
 ven_rsi_91x: rsi_interrupt_handler: Firmware Status is 0xa
 IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

  RCA:
  
 Root cause: When association starts, driver is sending station add peer
 notify to firmware but when Association timeout happens, driver is not
 sending station peer delete to Firmware. Hence, FW is going into DEEP SLEEP
 in associated state, which is incorrect.

  Fix:
  
 Sending station delete peer notify when assoc timeout happens.

  Regression potential:
  -
 Ran roaming between two AP's for 20 hours and didn't see the issue. 

 This bug is for tracking purposes only, please don't triage.

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

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

[Kernel-packages] [Bug 1769610] Re: Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

[Shrirang Bagul]

@Dorian,

Can you please share the acpidump for IB8000 Atom Braswell board?

Also, please check if Debian 4.16.0-2 has CONFIG_SERIAL_DEV_BUS=y
enabled by default. If not, then ttySx ports on this kernel will not be
claimed by the Serdev bus sub-system.

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

Title:
  Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

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

Bug description:
  Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

  On systems using Intel Atom (Baytrail-I) SoC's, slave devices connected on
  HSUART1/2 ports are described by the ACPI BIOS as virtual hardware using
  HID's INT3511/INT3512 [1].

  As a consequence, HW manufacturers have complete freedom to install any
  devices on-board as long as they can be accessed over serial tty
  interface. Once such device is Dell Edge 3002 IoT Gateway which sports
  ZigBee & GPS devices on the HS-UART ports 1 & 2 respectively.

  Post 4.15, with CONFIG_SERIAL_DEV_BUS=y, serdev port controller driver
  handles the enumeration for the slaves connected on these ports. Also,
  /dev/ttySx device nodes for these ports are no longer exposed to the
  userspace.

  This driver has been submitted upstream and is under review. This issue has
  been identified as a regression in 4.15 and multiple solutions are being
  explored. Meanwhile, to support customer and maintain release schedule,
  this driver needs to be in Ubuntu 4.15 based kernels.

  The impact is limited to systems based on Intel Atom E38XX (Baytrail-I)
  SoC's.

  More info:
  https://marc.info/?t=15245587167=1=2

  Please don't triage, this bug is for tracking purposes only.

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

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

[Kernel-packages] [Bug 1769610] Re: Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

[Shrirang Bagul]

Following comment#8, changing tags back to verification-done-bionic

** Tags removed: verification-failed-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/1769610

Title:
  Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

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

Bug description:
  Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

  On systems using Intel Atom (Baytrail-I) SoC's, slave devices connected on
  HSUART1/2 ports are described by the ACPI BIOS as virtual hardware using
  HID's INT3511/INT3512 [1].

  As a consequence, HW manufacturers have complete freedom to install any
  devices on-board as long as they can be accessed over serial tty
  interface. Once such device is Dell Edge 3002 IoT Gateway which sports
  ZigBee & GPS devices on the HS-UART ports 1 & 2 respectively.

  Post 4.15, with CONFIG_SERIAL_DEV_BUS=y, serdev port controller driver
  handles the enumeration for the slaves connected on these ports. Also,
  /dev/ttySx device nodes for these ports are no longer exposed to the
  userspace.

  This driver has been submitted upstream and is under review. This issue has
  been identified as a regression in 4.15 and multiple solutions are being
  explored. Meanwhile, to support customer and maintain release schedule,
  this driver needs to be in Ubuntu 4.15 based kernels.

  The impact is limited to systems based on Intel Atom E38XX (Baytrail-I)
  SoC's.

  More info:
  https://marc.info/?t=15245587167=1=2

  Please don't triage, this bug is for tracking purposes only.

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

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

[Kernel-packages] [Bug 1782070] Re: [Redpine] Upgrades to improve throughput and stability

[Shrirang Bagul]

** 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/1782070

Title:
  [Redpine]  Upgrades to improve throughput and stability

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  Confirmed

Bug description:
  This is a tracking bug for several improvements for the Redpine RS9113
  Wifi+BT combo-device on Dell Edge 300X gateways using Ubuntu 18.04
  Server based image. Some of these upgrades are:

  1. WoWLAN support from S3/S4 and S5.
  2. Better radio throughput
  3. Stable operation
     - fixes to mitigate issues during driver module loading/un-loading
     - panics when resuming from hibernation

  These changes have been verified by QA and Dell/ODM.

  This bug is of tracking purposes only, please don't triage.

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

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

[Kernel-packages] [Bug 1781895] Re: Bluetooth: Redpine: Bionics: L2test transfer is failed to start in Ubuntu 18.04

[Shrirang Bagul]

** 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/1781895

Title:
  Bluetooth: Redpine: Bionics: L2test transfer is failed to start in
  Ubuntu 18.04

Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Triaged
Status in linux-oem source package in Bionic:
  New

Bug description:
  SRU Justification
  -

  Impact:
  ---
   Bluetooth l2test is not getting started with rsi driver.

  Test Case:
  --
   1. Insert redpine modules with dev_oper_mode=13/4/5/6/14.

   2. Check bluetooth device is created or not.
  $ hciconfig -a

   3. Insert other thirdparty module to run l2test.

   4. Enable piscan for both interfaces
  $ hciconfig -a hci0 piscan  # lets say, hci0 is created for Redpine
  $ hciconfig -a hci1 piscan  # lets say, hci1 is created for 
thirdparty BT device 

   5. Open two terminals and then, start l2test with below commands.
  Terminal 1: Keep rsi module is in Transmit mode.
 $ l2test -i hci0 -s 
  Terminal 2: Keep third party device is in receive mode
 $ l2test -i hci1 -r

   6. l2test will not run and will fail after few seconds

  Fix:
  
  skb->data is having some extra bytes rather than expected size , which is 
Incorrect. Hence, removed redundant bytes from skb using skb_trim().

  Regression petential:
  -
  Ran L2test for 2 hours and didn't see any issue.

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

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

[Kernel-packages] [Bug 1777850] Re: Redpine: Observed kernel panic while running soft-ap tests

[Shrirang Bagul]

Verified on Dell IoT Edge 300x kernel snap (r93) based on 4.4.0-132.158


** 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/1777850

Title:
  Redpine: Observed kernel panic while running soft-ap tests

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

Bug description:
  SRU Justification:
  --

  Impact:
  Kernel freezes/panic when running wireless tests for soft-ap

  Test case:
  1. Create a soft-ap upon reboot.

  2. Install Checkbox plano and :
 $ sudo snap install --devmode checkbox-plano

  3. Run below wifi-ap test case
 $ checkbox-plano.checkbox-cli run .*device 
.*wireless/caracalla-wifi_ap_.*wlan0_auto

  4. Upon 3-4 iteraions, observed kernel crash as below,
 [ 718.83244] BUG: unable to handle page request at 001067e38
 [ 718.83248] IP: cfg80211_scan_done+0xb0/0xc0 [cfg80211]
 [ 718.83971]  __ieee80211_scan_completed+0xb1/0x390 [mac80211]
 [ 718.84078]  ieee80211_scan_work+0x7e/0x480 [mac80211]
 [ 718.84098]  process_one_work+0x142/0x3d0
 [ 718.84111]  worker_thread+0x229/0x440
 [ 718.84122]  kthread+0xf5/0x130
 [ 718.84132]  ? process_one_work+0x3d0/0x3d0
 [ 718.84140]  ? kthread_associate_blkcg+0x90/0x90
 [ 718.84152]  ret_from_fork+0x35/0x40

  Fix:
  scan work function keeps running even after cancel_hw_scan() call.
  Issue is resolved by calling cancel_work_sync() in rsi_mac80211_stop().

  Regression Petential:
  Ran Step 3 in 30-times. Didn't see any kernel panic.

  This bug is for tracking purposes only, please don't triage.

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

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

[Kernel-packages] [Bug 1777858] Re: Redpine: Observed kernel panic while running wireless regressions tests

[Shrirang Bagul]

Verified on Dell IoT Edge 300x kernel snap (r93) based on 4.4.0-132.158


** 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/1777858

Title:
  Redpine: Observed kernel panic while running wireless regressions
  tests

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

Bug description:
  SRU Justification:
  --

  Impact:
  Kernel freezes/panic when running wireless tests

  Test case:
  1. Create a wireless soft-ap/station upon reboot.

  2. Install Checkbox plano and :
 $ sudo snap install --devmode checkbox-plano

  3. Run below wifi-ap test case
 $ checkbox-plano.checkbox-cli run .*device 
.*wireless/caracalla-wifi_ap_.*wlan0_auto

  4. Upon 3-4 iteraions, observed kernel crash as below,
 BUG: unable to handle kernel NULL pointer dereference at   
(null)
 IP: [] exit_creds+0x1f/0x50
 PGD 0
 Oops: 0002 [#1] SMP
 CPU: 0 PID: 6502 Comm: rmmod Tainted: G   OE   
4.4.0-128-generic #154-Ubuntu
 Hardware name: Dell Inc. Edge Gateway 3003/  , BIOS 01.00.00 
04/17/2017
 Stack:
 88007392e600 880075847dc0 8108160a 
 88007392e600 880075847de8 810a484b 880076127000
 88003cd3a800 880074f12a00 880075847e28 c09bed15
 Call Trace:
 [] __put_task_struct+0x5a/0x140
 [] kthread_stop+0x10b/0x110
 [] rsi_disconnect+0x2f5/0x300 [ven_rsi_sdio]
 [] ? __pm_runtime_resume+0x5b/0x80
 [] sdio_bus_remove+0x38/0x100
 [] __device_release_driver+0xa4/0x150
 [] driver_detach+0xb5/0xc0
 [] bus_remove_driver+0x55/0xd0
 [] driver_unregister+0x2c/0x50
 [] sdio_unregister_driver+0x1a/0x20
 [] rsi_module_exit+0x15/0x30 [ven_rsi_sdio]
 [] SyS_delete_module+0x1b8/0x210
 [] entry_SYSCALL_64_fastpath+0x1c/0xbb

  Fix:
  kthread_stop() is taking care of wait_for_completion() by default.
  No need of taking care separately.
  Issue is resolved by removing wait_for_completion() from rsi_disconnect().

  Regression Petential:
  Ran Step 3 in 30-times. Didn't see any kernel panic.

  This bug is for tracking purposes only, please don't triage.

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

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

[Kernel-packages] [Bug 1773400] Re: Redpine: wifi-ap stopped working after restart

[Shrirang Bagul]

Verified on Dell IoT Edge 300x kernel snap (r93) based on 4.4.0-132.158


** 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/1773400

Title:
  Redpine: wifi-ap stopped working after restart

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  SRU Justification:
  --

  Impact:
  Wi-Fi access point isn’t visible to outside devices after reboot

  Test Case:
  Configure Wi-Fi AP using setup wizard:
     $ sudo wifi-ap.setup-wizard

  Check configured AP settings:
     $ sudo wifi-ap.config get

     debug: false
     dhcp.lease-time: 12h
     dhcp.range-start: 10.0.60.2
     dhcp.range-stop: 10.0.60.200
     disabled: false
     share.disabled: false
     share.network-interface: wlan0
     wifi.address: 10.0.60.1
     wifi.channel: 6
     wifi.country-code:
     wifi.hostapd-driver: nl80211
     wifi.interface: wlan0
     wifi.interface-mode: direct
     wifi.netmask: ff00
     wifi.operation-mode: g
     wifi.security: wpa2
     wifi.security-passphrase: some-password
     wifi.ssid: dell-gateway

  Check in third-party stations. SSID is invisible.

  Restart AP and check its status:
     $ sudo wifi-ap.status restart-ap

  Check status of AP. It is showing true.
     $ sudo wifi-ap.status
     ap.active: true

  At this point also, Wi-Fi access point is not visible.

  Fix:
  Power save is enabled in AP mode. it must be disabled.

  Regression potential:
  Ran "wifi-ap.status restart-ap" command in every 1 minute and observed 
whether it is visible to third party devices are not. And it is behaving as 
expected.

  This patch is for tracking only, please don't triage.

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

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

[Kernel-packages] [Bug 1773410] Re: Redpine: Observed kernel panic while running wireless tests in regression mode

[Shrirang Bagul]

Verified on Dell IoT Edge 300x kernel snap (r93) based on 4.4.0-132.158

** 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/1773410

Title:
  Redpine: Observed kernel panic while running wireless tests in
  regression mode

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

Bug description:
  SRU Justification
  -

  Impact:
  Kernel freezes/panic when running wireless tests in regression

  Test case:
  1. Keep a wrong access-point name in sta.conf file and run the nmcli.
  2. There will be continuous scan will be happen and do remove the module 
using rmmod.sh script.
  3. When soft scan is happening in redpine driver, before connection. Some 
times, we have observed
     a kernel panic. like below
     [ 1171.913244] BUG: unable to handle page request at 001067e38
     [ 1171.913248] IP: cfg80211_scan_done+0xb0/0xc0 [cfg80211]
     [ 1171.913971]  __ieee80211_scan_completed+0xb1/0x390 [mac80211]
     [ 1171.914078]  ieee80211_scan_work+0x7e/0x480 [mac80211]
     [ 1171.914098]  process_one_work+0x142/0x3d0
     [ 1171.914111]  worker_thread+0x229/0x440
     [ 1171.914122]  kthread+0xf5/0x130
     [ 1171.914132]  ? process_one_work+0x3d0/0x3d0
     [ 1171.914140]  ? kthread_associate_blkcg+0x90/0x90
     [ 1171.914152]  ret_from_fork+0x35/0x40

  Fix:
  scan work function keeps running even after cancel_hw_scan() call.
  Issue is resolved by calling cancel_work_sync().

  Regression potential:
  Ran driver_crash.sh for 100 times and didn't see the issue.

  This bug is for tracking purposes only, please don't triage.

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

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

[Kernel-packages] [Bug 1781895] Re: Bluetooth: Redpine: Bionics: L2test transfer is failed to start in Ubuntu 18.04

[Shrirang Bagul]

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

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

Title:
  Bluetooth: Redpine: Bionics: L2test transfer is failed to start in
  Ubuntu 18.04

Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Triaged
Status in linux-oem source package in Bionic:
  New

Bug description:
  SRU Justification
  -

  Impact:
  ---
   Bluetooth l2test is not getting started with rsi driver.

  Test Case:
  --
   1. Insert redpine modules with dev_oper_mode=13/4/5/6/14.

   2. Check bluetooth device is created or not.
  $ hciconfig -a

   3. Insert other thirdparty module to run l2test.

   4. Enable piscan for both interfaces
  $ hciconfig -a hci0 piscan  # lets say, hci0 is created for Redpine
  $ hciconfig -a hci1 piscan  # lets say, hci1 is created for 
thirdparty BT device 

   5. Open two terminals and then, start l2test with below commands.
  Terminal 1: Keep rsi module is in Transmit mode.
 $ l2test -i hci0 -s 
  Terminal 2: Keep third party device is in receive mode
 $ l2test -i hci1 -r

   6. l2test will not run and will fail after few seconds

  Fix:
  
  skb->data is having some extra bytes rather than expected size , which is 
Incorrect. Hence, removed redundant bytes from skb using skb_trim().

  Regression petential:
  -
  Ran L2test for 2 hours and didn't see any issue.

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

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

[Kernel-packages] [Bug 1781895] Re: Bluetooth: Redpine: Bionics: L2test transfer is failed to start in Ubuntu 18.04

[Shrirang Bagul]

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

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

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

Title:
  Bluetooth: Redpine: Bionics: L2test transfer is failed to start in
  Ubuntu 18.04

Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Triaged
Status in linux-oem source package in Bionic:
  New

Bug description:
  SRU Justification
  -

  Impact:
  ---
   Bluetooth l2test is not getting started with rsi driver.

  Test Case:
  --
   1. Insert redpine modules with dev_oper_mode=13/4/5/6/14.

   2. Check bluetooth device is created or not.
  $ hciconfig -a

   3. Insert other thirdparty module to run l2test.

   4. Enable piscan for both interfaces
  $ hciconfig -a hci0 piscan  # lets say, hci0 is created for Redpine
  $ hciconfig -a hci1 piscan  # lets say, hci1 is created for 
thirdparty BT device 

   5. Open two terminals and then, start l2test with below commands.
  Terminal 1: Keep rsi module is in Transmit mode.
 $ l2test -i hci0 -s 
  Terminal 2: Keep third party device is in receive mode
 $ l2test -i hci1 -r

   6. l2test will not run and will fail after few seconds

  Fix:
  
  skb->data is having some extra bytes rather than expected size , which is 
Incorrect. Hence, removed redundant bytes from skb using skb_trim().

  Regression petential:
  -
  Ran L2test for 2 hours and didn't see any issue.

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

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

[Kernel-packages] [Bug 1783241] Re: [HMS] Upgrades to Support SocketCAN over USB on Dell IoT 300x Gateways

[Shrirang Bagul]

Latest Dell IoT 300x Gateway kernel snap (r93) based on kernel ver.
4.4.0-132.158 was tested and verified by CE-QA.

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

Title:
  [HMS] Upgrades to Support SocketCAN over USB on Dell IoT 300x Gateways

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

Bug description:
  Several scheduled upgrades to the HMS SocketCAN protocol driver over
  USB->CAN interface are required.

  SocketCAN support for USB->CAN devices was introduced in Ubuntu Xenial LTS 
kernel through following patch (BugLink: 
http://bugs.launchpad.net/bugs/1774563):
  cddf58207a3c UBUNTU: SAUCE: (no-up) Support IXXAT USB SocketCAN device

  == SRU Justification ==
  The scheduled upgrades include following changes:
  - support adapters for CL1 (Communication Layer for legacy devices) and
CL2 (current devices)
  - removed CAN-IDM100 support (Microchip Rev A microcontroller)
  - add CAN-IDM101 support (Microchip Rev B microcontroller)
  - add Error-Passive recognition
  - move CAN message handling to the core module
  - use ktime API for timestamps
  - fixes Linux kernel coding style issues

  == Fix ==
  UBUNTU: SAUCE: (no-up) upgrade IXXAT USB SocketCAN driver

  == Regression Potential ==
  Low. The driver will be built only for amd64 kernels and attach itself to 
IXXAT USB-CAN adapters with VID 0x08d8. Also, patches from the vendor (HMS) 
have already been tested by Dell/ODM, Canonical QA on Dell 300x Edge IoT 
gateways.

  This bug is for tracking purposes only, please do not triage.

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

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

[Kernel-packages] [Bug 1783241] Re: [HMS] Upgrades to Support SocketCAN over USB on Dell IoT 300x Gateways

[Shrirang Bagul]

caracalla-kernel snap (r93) based on kernel ver. 4.4.0-132.158 was
tested and verified by CE-QA.

** 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/1783241

Title:
  [HMS] Upgrades to Support SocketCAN over USB on Dell IoT 300x Gateways

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

Bug description:
  Several scheduled upgrades to the HMS SocketCAN protocol driver over
  USB->CAN interface are required.

  SocketCAN support for USB->CAN devices was introduced in Ubuntu Xenial LTS 
kernel through following patch (BugLink: 
http://bugs.launchpad.net/bugs/1774563):
  cddf58207a3c UBUNTU: SAUCE: (no-up) Support IXXAT USB SocketCAN device

  == SRU Justification ==
  The scheduled upgrades include following changes:
  - support adapters for CL1 (Communication Layer for legacy devices) and
CL2 (current devices)
  - removed CAN-IDM100 support (Microchip Rev A microcontroller)
  - add CAN-IDM101 support (Microchip Rev B microcontroller)
  - add Error-Passive recognition
  - move CAN message handling to the core module
  - use ktime API for timestamps
  - fixes Linux kernel coding style issues

  == Fix ==
  UBUNTU: SAUCE: (no-up) upgrade IXXAT USB SocketCAN driver

  == Regression Potential ==
  Low. The driver will be built only for amd64 kernels and attach itself to 
IXXAT USB-CAN adapters with VID 0x08d8. Also, patches from the vendor (HMS) 
have already been tested by Dell/ODM, Canonical QA on Dell 300x Edge IoT 
gateways.

  This bug is for tracking purposes only, please do not triage.

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

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

[Kernel-packages] [Bug 1783241] [NEW] [HMS] Upgrades to Support SocketCAN over USB on Dell IoT 300x Gateways

[Shrirang Bagul]

Public bug reported:

Several scheduled upgrades to the HMS SocketCAN protocol driver over
USB->CAN interface are required.

SocketCAN support for USB->CAN devices was introduced in Ubuntu Xenial LTS 
kernel through following patch (BugLink: 
http://bugs.launchpad.net/bugs/1774563):
cddf58207a3c UBUNTU: SAUCE: (no-up) Support IXXAT USB SocketCAN device

== SRU Justification ==
The scheduled upgrades include following changes:
- support adapters for CL1 (Communication Layer for legacy devices) and
  CL2 (current devices)
- removed CAN-IDM100 support (Microchip Rev A microcontroller)
- add CAN-IDM101 support (Microchip Rev B microcontroller)
- add Error-Passive recognition
- move CAN message handling to the core module
- use ktime API for timestamps
- fixes Linux kernel coding style issues

== Fix ==
UBUNTU: SAUCE: (no-up) upgrade IXXAT USB SocketCAN driver

== Regression Potential ==
Low. The driver will be built only for amd64 kernels and attach itself to IXXAT 
USB-CAN adapters with VID 0x08d8. Also, patches from the vendor (HMS) have 
already been tested by Dell/ODM, Canonical QA on Dell 300x Edge IoT gateways.

This bug is for tracking purposes only, please do not triage.

** Affects: linux (Ubuntu)
 Importance: Critical
 Status: Confirmed

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

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

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

Title:
  [HMS] Upgrades to Support SocketCAN over USB on Dell IoT 300x Gateways

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Several scheduled upgrades to the HMS SocketCAN protocol driver over
  USB->CAN interface are required.

  SocketCAN support for USB->CAN devices was introduced in Ubuntu Xenial LTS 
kernel through following patch (BugLink: 
http://bugs.launchpad.net/bugs/1774563):
  cddf58207a3c UBUNTU: SAUCE: (no-up) Support IXXAT USB SocketCAN device

  == SRU Justification ==
  The scheduled upgrades include following changes:
  - support adapters for CL1 (Communication Layer for legacy devices) and
CL2 (current devices)
  - removed CAN-IDM100 support (Microchip Rev A microcontroller)
  - add CAN-IDM101 support (Microchip Rev B microcontroller)
  - add Error-Passive recognition
  - move CAN message handling to the core module
  - use ktime API for timestamps
  - fixes Linux kernel coding style issues

  == Fix ==
  UBUNTU: SAUCE: (no-up) upgrade IXXAT USB SocketCAN driver

  == Regression Potential ==
  Low. The driver will be built only for amd64 kernels and attach itself to 
IXXAT USB-CAN adapters with VID 0x08d8. Also, patches from the vendor (HMS) 
have already been tested by Dell/ODM, Canonical QA on Dell 300x Edge IoT 
gateways.

  This bug is for tracking purposes only, please do not triage.

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

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

[Kernel-packages] [Bug 1774563] Re: [HMS] Support SocketCAN over USB on Dell IoT 300x Gateways

[Shrirang Bagul]

** Summary changed:

- Support SocketCAN over USB on Dell IoT 300x Gateways
+ [HMS] Support SocketCAN over USB on Dell IoT 300x Gateways

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

Title:
  [HMS] Support SocketCAN over USB on Dell IoT 300x Gateways

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

Bug description:
  This driver is from IXXAT and supports SocketCAN over USB.
  (https://www.ixxat.com)

  == SRU Justification ==
  Dell IoT 300x gateways support USB-CAN peripherals. Dell expects these 
devices also support the SocketCAN over USB and is working with HMS to develop 
and upstream the driver. Meanwhile, we'll have to carry this driver as a SAUCE 
patch to support our Ubuntu Core 16 release.

  == Fix ==
  UBUNTU: SAUCE: (no-up) Support IXXAT USB SocketCAN device

  == Regression Potential ==
  Low. The driver will be built only for amd64 kernels and attach itself to 
IXXAT USB-CAN adapters with VID 0x08d8.

  This bug is for tracking purposes only, please do not triage.

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

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

[Kernel-packages] [Bug 1782070] Re: [Redpine] Upgrades to improve throughput and stability

[Shrirang Bagul]

** Description changed:

  This is a tracking bug for several improvements for the Redpine RS9113
  Wifi+BT combo-device on Dell Edge 300X gateways using Ubuntu 18.04
  Server based image. Some of these upgrades are:
  
  1. WoWLAN support from S3/S4 and S5.
  2. Better radio throughput
  3. Stable operation
     - fixes to mitigate issues during driver module loading/un-loading
     - panics when resuming from hibernation
  
+ These changes have been verified by QA and Dell/ODM.
+ 
  This bug is of tracking purposes only, please don't triage.

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

Title:
  [Redpine]  Upgrades to improve throughput and stability

Status in linux-oem package in Ubuntu:
  Confirmed

Bug description:
  This is a tracking bug for several improvements for the Redpine RS9113
  Wifi+BT combo-device on Dell Edge 300X gateways using Ubuntu 18.04
  Server based image. Some of these upgrades are:

  1. WoWLAN support from S3/S4 and S5.
  2. Better radio throughput
  3. Stable operation
     - fixes to mitigate issues during driver module loading/un-loading
     - panics when resuming from hibernation

  These changes have been verified by QA and Dell/ODM.

  This bug is of tracking purposes only, please don't triage.

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

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

[Kernel-packages] [Bug 1782070] Re: [Redpine] Upgrades to improve throughput and stability

[Shrirang Bagul]

** Description changed:

  This is a tracking bug for several improvements for the Redpine RS9113
- Wifi+BT combo-device on Dell Edge 300X gateways. Some of these upgrades
- are:
+ Wifi+BT combo-device on Dell Edge 300X gateways using Ubuntu 18.04
+ Server based image. Some of these upgrades are:
  
  1. WoWLAN support from S3/S4 and S5.
  2. Better radio throughput
- 3. Stable operation 
-- fixes to mitigate issues during driver module loading/un-loading
-- panics when resuming from hibernation
+ 3. Stable operation
+    - fixes to mitigate issues during driver module loading/un-loading
+    - panics when resuming from hibernation
  
  This bug is of tracking purposes only, please don't triage.

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

Title:
  [Redpine]  Upgrades to improve throughput and stability

Status in linux-oem package in Ubuntu:
  Confirmed

Bug description:
  This is a tracking bug for several improvements for the Redpine RS9113
  Wifi+BT combo-device on Dell Edge 300X gateways using Ubuntu 18.04
  Server based image. Some of these upgrades are:

  1. WoWLAN support from S3/S4 and S5.
  2. Better radio throughput
  3. Stable operation
     - fixes to mitigate issues during driver module loading/un-loading
     - panics when resuming from hibernation

  These changes have been verified by QA and Dell/ODM.

  This bug is of tracking purposes only, please don't triage.

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

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

[Kernel-packages] [Bug 1782070] [NEW] [Redpine] Upgrades to improve throughput and stability

[Shrirang Bagul]

Public bug reported:

This is a tracking bug for several improvements for the Redpine RS9113
Wifi+BT combo-device on Dell Edge 300X gateways. Some of these upgrades
are:

1. WoWLAN support from S3/S4 and S5.
2. Better radio throughput
3. Stable operation 
   - fixes to mitigate issues during driver module loading/un-loading
   - panics when resuming from hibernation

This bug is of tracking purposes only, please don't triage.

** Affects: linux-oem (Ubuntu)
 Importance: Critical
 Status: Confirmed

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

** Changed in: linux-oem (Ubuntu)
   Importance: Undecided => Critical

** Changed in: linux-oem (Ubuntu)
   Importance: Critical => Undecided

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

** Changed in: linux-oem (Ubuntu)
   Importance: High => Critical

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

Title:
  [Redpine]  Upgrades to improve throughput and stability

Status in linux-oem package in Ubuntu:
  Confirmed

Bug description:
  This is a tracking bug for several improvements for the Redpine RS9113
  Wifi+BT combo-device on Dell Edge 300X gateways. Some of these
  upgrades are:

  1. WoWLAN support from S3/S4 and S5.
  2. Better radio throughput
  3. Stable operation 
 - fixes to mitigate issues during driver module loading/un-loading
 - panics when resuming from hibernation

  This bug is of tracking purposes only, please don't triage.

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

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

[Kernel-packages] [Bug 1769610] Re: Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

[Shrirang Bagul]

Not as long as this regression in Serdev is fixed.

In your case, the port controller /dev/ttyS6 is actually created by the
kernel, but not exposed to the user. So, ttyS6 cannot be re-claimed by
the Intel HS-UART driver.

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

Title:
  Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

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

Bug description:
  Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

  On systems using Intel Atom (Baytrail-I) SoC's, slave devices connected on
  HSUART1/2 ports are described by the ACPI BIOS as virtual hardware using
  HID's INT3511/INT3512 [1].

  As a consequence, HW manufacturers have complete freedom to install any
  devices on-board as long as they can be accessed over serial tty
  interface. Once such device is Dell Edge 3002 IoT Gateway which sports
  ZigBee & GPS devices on the HS-UART ports 1 & 2 respectively.

  Post 4.15, with CONFIG_SERIAL_DEV_BUS=y, serdev port controller driver
  handles the enumeration for the slaves connected on these ports. Also,
  /dev/ttySx device nodes for these ports are no longer exposed to the
  userspace.

  This driver has been submitted upstream and is under review. This issue has
  been identified as a regression in 4.15 and multiple solutions are being
  explored. Meanwhile, to support customer and maintain release schedule,
  this driver needs to be in Ubuntu 4.15 based kernels.

  The impact is limited to systems based on Intel Atom E38XX (Baytrail-I)
  SoC's.

  More info:
  https://marc.info/?t=15245587167=1=2

  Please don't triage, this bug is for tracking purposes only.

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

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

[Kernel-packages] [Bug 1769610] Re: Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

[Shrirang Bagul]

@Denis,

Then the /dev/ttyS6 may now appear as /dev/ttyHSx. Can you confirm this?

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

Title:
  Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

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

Bug description:
  Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

  On systems using Intel Atom (Baytrail-I) SoC's, slave devices connected on
  HSUART1/2 ports are described by the ACPI BIOS as virtual hardware using
  HID's INT3511/INT3512 [1].

  As a consequence, HW manufacturers have complete freedom to install any
  devices on-board as long as they can be accessed over serial tty
  interface. Once such device is Dell Edge 3002 IoT Gateway which sports
  ZigBee & GPS devices on the HS-UART ports 1 & 2 respectively.

  Post 4.15, with CONFIG_SERIAL_DEV_BUS=y, serdev port controller driver
  handles the enumeration for the slaves connected on these ports. Also,
  /dev/ttySx device nodes for these ports are no longer exposed to the
  userspace.

  This driver has been submitted upstream and is under review. This issue has
  been identified as a regression in 4.15 and multiple solutions are being
  explored. Meanwhile, to support customer and maintain release schedule,
  this driver needs to be in Ubuntu 4.15 based kernels.

  The impact is limited to systems based on Intel Atom E38XX (Baytrail-I)
  SoC's.

  More info:
  https://marc.info/?t=15245587167=1=2

  Please don't triage, this bug is for tracking purposes only.

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

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

[Kernel-packages] [Bug 1769610] Re: Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

[Shrirang Bagul]

@Denis,

Have you looked at the RFC patch submitted to linux-serial (see bug 
Description)?
The driver provided as fix for this issue will only attach if the BIOS on your 
HW describes virtual serial devices with HID's INT3511/INT3512.

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

Title:
  Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

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

Bug description:
  Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

  On systems using Intel Atom (Baytrail-I) SoC's, slave devices connected on
  HSUART1/2 ports are described by the ACPI BIOS as virtual hardware using
  HID's INT3511/INT3512 [1].

  As a consequence, HW manufacturers have complete freedom to install any
  devices on-board as long as they can be accessed over serial tty
  interface. Once such device is Dell Edge 3002 IoT Gateway which sports
  ZigBee & GPS devices on the HS-UART ports 1 & 2 respectively.

  Post 4.15, with CONFIG_SERIAL_DEV_BUS=y, serdev port controller driver
  handles the enumeration for the slaves connected on these ports. Also,
  /dev/ttySx device nodes for these ports are no longer exposed to the
  userspace.

  This driver has been submitted upstream and is under review. This issue has
  been identified as a regression in 4.15 and multiple solutions are being
  explored. Meanwhile, to support customer and maintain release schedule,
  this driver needs to be in Ubuntu 4.15 based kernels.

  The impact is limited to systems based on Intel Atom E38XX (Baytrail-I)
  SoC's.

  More info:
  https://marc.info/?t=15245587167=1=2

  Please don't triage, this bug is for tracking purposes only.

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

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

[Kernel-packages] [Bug 1777850] Re: Redpine: Observed kernel panic while running soft-ap tests

[Shrirang Bagul]

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

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

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

Title:
  Redpine: Observed kernel panic while running soft-ap tests

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  SRU Justification:
  --

  Impact:
  Kernel freezes/panic when running wireless tests for soft-ap

  Test case:
  1. Create a soft-ap upon reboot.

  2. Install Checkbox plano and :
 $ sudo snap install --devmode checkbox-plano

  3. Run below wifi-ap test case
 $ checkbox-plano.checkbox-cli run .*device 
.*wireless/caracalla-wifi_ap_.*wlan0_auto

  4. Upon 3-4 iteraions, observed kernel crash as below,
 [ 718.83244] BUG: unable to handle page request at 001067e38
 [ 718.83248] IP: cfg80211_scan_done+0xb0/0xc0 [cfg80211]
 [ 718.83971]  __ieee80211_scan_completed+0xb1/0x390 [mac80211]
 [ 718.84078]  ieee80211_scan_work+0x7e/0x480 [mac80211]
 [ 718.84098]  process_one_work+0x142/0x3d0
 [ 718.84111]  worker_thread+0x229/0x440
 [ 718.84122]  kthread+0xf5/0x130
 [ 718.84132]  ? process_one_work+0x3d0/0x3d0
 [ 718.84140]  ? kthread_associate_blkcg+0x90/0x90
 [ 718.84152]  ret_from_fork+0x35/0x40

  Fix:
  scan work function keeps running even after cancel_hw_scan() call.
  Issue is resolved by calling cancel_work_sync() in rsi_mac80211_stop().

  Regression Petential:
  Ran Step 3 in 30-times. Didn't see any kernel panic.

  This bug is for tracking purposes only, please don't triage.

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

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

[Kernel-packages] [Bug 1777858] Re: Redpine: Observed kernel panic while running wireless regressions tests

[Shrirang Bagul]

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

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

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

Title:
  Redpine: Observed kernel panic while running wireless regressions
  tests

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  SRU Justification:
  --

  Impact:
  Kernel freezes/panic when running wireless tests

  Test case:
  1. Create a wireless soft-ap/station upon reboot.

  2. Install Checkbox plano and :
 $ sudo snap install --devmode checkbox-plano

  3. Run below wifi-ap test case
 $ checkbox-plano.checkbox-cli run .*device 
.*wireless/caracalla-wifi_ap_.*wlan0_auto

  4. Upon 3-4 iteraions, observed kernel crash as below,
 BUG: unable to handle kernel NULL pointer dereference at   
(null)
 IP: [] exit_creds+0x1f/0x50
 PGD 0
 Oops: 0002 [#1] SMP
 CPU: 0 PID: 6502 Comm: rmmod Tainted: G   OE   
4.4.0-128-generic #154-Ubuntu
 Hardware name: Dell Inc. Edge Gateway 3003/  , BIOS 01.00.00 
04/17/2017
 Stack:
 88007392e600 880075847dc0 8108160a 
 88007392e600 880075847de8 810a484b 880076127000
 88003cd3a800 880074f12a00 880075847e28 c09bed15
 Call Trace:
 [] __put_task_struct+0x5a/0x140
 [] kthread_stop+0x10b/0x110
 [] rsi_disconnect+0x2f5/0x300 [ven_rsi_sdio]
 [] ? __pm_runtime_resume+0x5b/0x80
 [] sdio_bus_remove+0x38/0x100
 [] __device_release_driver+0xa4/0x150
 [] driver_detach+0xb5/0xc0
 [] bus_remove_driver+0x55/0xd0
 [] driver_unregister+0x2c/0x50
 [] sdio_unregister_driver+0x1a/0x20
 [] rsi_module_exit+0x15/0x30 [ven_rsi_sdio]
 [] SyS_delete_module+0x1b8/0x210
 [] entry_SYSCALL_64_fastpath+0x1c/0xbb

  Fix:
  kthread_stop() is taking care of wait_for_completion() by default.
  No need of taking care separately.
  Issue is resolved by removing wait_for_completion() from rsi_disconnect().

  Regression Petential:
  Ran Step 3 in 30-times. Didn't see any kernel panic.

  This bug is for tracking purposes only, please don't triage.

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

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

[Kernel-packages] [Bug 1774563] Re: Support SocketCAN over USB on Dell IoT 300x Gateways

[Shrirang Bagul]

** 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/1774563

Title:
  Support SocketCAN over USB on Dell IoT 300x Gateways

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

Bug description:
  This driver is from IXXAT and supports SocketCAN over USB.
  (https://www.ixxat.com)

  == SRU Justification ==
  Dell IoT 300x gateways support USB-CAN peripherals. Dell expects these 
devices also support the SocketCAN over USB and is working with HMS to develop 
and upstream the driver. Meanwhile, we'll have to carry this driver as a SAUCE 
patch to support our Ubuntu Core 16 release.

  == Fix ==
  UBUNTU: SAUCE: (no-up) Support IXXAT USB SocketCAN device

  == Regression Potential ==
  Low. The driver will be built only for amd64 kernels and attach itself to 
IXXAT USB-CAN adapters with VID 0x08d8.

  This bug is for tracking purposes only, please do not triage.

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

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

[Kernel-packages] [Bug 1772626] Re: [Redpine] HCI command timeout after resume from S4

[Shrirang Bagul]

** 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/1772626

Title:
  [Redpine] HCI command timeout after resume from S4

Status in HWE Next:
  Confirmed
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux-oem source package in Bionic:
  Fix Committed

Bug description:
  Redpine BT stops working after resume from S4.

  Symptoms:
  - The device list is increasing after resume. 
  - Error after command "hciconfig -a" which as:
  Can't read local name on hci0: Connection timed out (110)

  The reproduce steps:
  1) Go to hibernate mode
  $ sudo systemctl hibernate

  2) Wakeup system by power recycle

  3) Check the bluetooth list
  $ hciconfig -a
  hci1: Type: Primary Bus: SDIO
   BD Address: 00:23:A7:BF:34:F8 ACL MTU: 540:2 SCO MTU: 30:1
   DOWN
   RX bytes:574 acl:0 sco:0 events:30 errors:0
   TX bytes:0 acl:0 sco:0 commands:30 errors:0
   Features: 0x3f 0x02 0x04 0x4e 0xc8 0x0d 0x5b 0x87
   Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1
   Link policy: RSWITCH
   Link mode: SLAVE ACCEPT

  hci0: Type: Primary Bus: SDIO
   BD Address: 00:23:A7:BF:34:F8 ACL MTU: 540:2 SCO MTU: 30:1
   UP RUNNING
   RX bytes:1238 acl:0 sco:0 events:75 errors:0
   TX bytes:0 acl:0 sco:0 commands:75 errors:0
   Features: 0x3f 0x02 0x04 0x4e 0xc8 0x0d 0x5b 0x87
   Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1
   Link policy: RSWITCH
   Link mode: SLAVE ACCEPT
  Can't read local name on hci0: Connection timed out (110)

  4) Go to hibernate and wake again(as step 1-2)

  5) Try ifconfig command to check wifi device
  Result: command no response

  This bug is for tracking purposes only, please don't triage.

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

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

[Kernel-packages] [Bug 1774606] Re: [Redpine] Wifi AP does not work

[Shrirang Bagul]

** 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/1774606

Title:
  [Redpine] Wifi AP does not work

Status in HWE Next:
  New
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux-oem source package in Bionic:
  Fix Committed

Bug description:
  WiFi AP can not be enabled in Ubuntu Server 18.04 with Redpine driver
  for 4.15 kernel.

  Several issues were observed in Redpine driver which supports RS9113 Wifi+BT 
combo chip:
  1. 40Mhz connection issue
  2. Mode 1,13,14,4,6 change issue
  3. SoftAP failure issue

  This bug is of tracking purposes only, please don't triage.

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

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

[Kernel-packages] [Bug 1774606] Re: [Redpine] Wifi AP does not work

[Shrirang Bagul]

** Tags added: originate-from-1774299 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/1774606

Title:
  [Redpine] Wifi AP does not work

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

Bug description:
  WiFi AP can not be enabled in Ubuntu Server 18.04 with Redpine driver
  for 4.15 kernel.

  Several issues were observed in Redpine driver which supports RS9113 Wifi+BT 
combo chip:
  1. 40Mhz connection issue
  2. Mode 1,13,14,4,6 change issue
  3. SoftAP failure issue

  This bug is of tracking purposes only, please don't triage.

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

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

[Kernel-packages] [Bug 1774606] [NEW] [Redpine] Wifi AP does not work

[Shrirang Bagul]

Public bug reported:

WiFi AP can not be enabled in Ubuntu Server 18.04 with Redpine driver
for 4.15 kernel.

Several issues were observed in Redpine driver which supports RS9113 Wifi+BT 
combo chip:
1. 40Mhz connection issue
2. Mode 1,13,14,4,6 change issue
3. SoftAP failure issue

This bug is of tracking purposes only, please don't triage.

** Affects: linux-oem (Ubuntu)
 Importance: High
 Status: Confirmed

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

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

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

Title:
  [Redpine] Wifi AP does not work

Status in linux-oem package in Ubuntu:
  Confirmed

Bug description:
  WiFi AP can not be enabled in Ubuntu Server 18.04 with Redpine driver
  for 4.15 kernel.

  Several issues were observed in Redpine driver which supports RS9113 Wifi+BT 
combo chip:
  1. 40Mhz connection issue
  2. Mode 1,13,14,4,6 change issue
  3. SoftAP failure issue

  This bug is of tracking purposes only, please don't triage.

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

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

[Kernel-packages] [Bug 1774563] Re: Support SocketCAN over USB on Dell IoT 300x Gateways

[Shrirang Bagul]

** Description changed:

  This driver is from IXXAT and supports SocketCAN over USB.
  (https://www.ixxat.com)
  
  == SRU Justification ==
- Dell IoT 300x gateways support CAN peripherals over USB. Dell expects these 
devices also support the SocketCAN over USB and is working with HMS to develop 
and upstream the driver. Meanwhile, we'll have to carry this driver as a SAUCE 
patch to support our Ubuntu Core 16 release.
+ Dell IoT 300x gateways support USB-CAN peripherals. Dell expects these 
devices also support the SocketCAN over USB and is working with HMS to develop 
and upstream the driver. Meanwhile, we'll have to carry this driver as a SAUCE 
patch to support our Ubuntu Core 16 release.
  
  == Fix ==
  UBUNTU: SAUCE: (no-up) Support IXXAT USB SocketCAN device
  
  == Regression Potential ==
  Low. The driver will be built only for amd64 kernels and attach itself to 
IXXAT USB-CAN adapters with VID 0x08d8.
  
  This bug is for tracking purposes only, please do not triage.

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

Title:
  Support SocketCAN over USB on Dell IoT 300x Gateways

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This driver is from IXXAT and supports SocketCAN over USB.
  (https://www.ixxat.com)

  == SRU Justification ==
  Dell IoT 300x gateways support USB-CAN peripherals. Dell expects these 
devices also support the SocketCAN over USB and is working with HMS to develop 
and upstream the driver. Meanwhile, we'll have to carry this driver as a SAUCE 
patch to support our Ubuntu Core 16 release.

  == Fix ==
  UBUNTU: SAUCE: (no-up) Support IXXAT USB SocketCAN device

  == Regression Potential ==
  Low. The driver will be built only for amd64 kernels and attach itself to 
IXXAT USB-CAN adapters with VID 0x08d8.

  This bug is for tracking purposes only, please do not triage.

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

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

[Kernel-packages] [Bug 1774563] Re: Support SocketCAN over USB on Dell IoT 300x Gateways

[Shrirang Bagul]

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

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

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

Title:
  Support SocketCAN over USB on Dell IoT 300x Gateways

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This driver is from IXXAT and supports SocketCAN over USB.
  (https://www.ixxat.com)

  == SRU Justification ==
  Dell IoT 300x gateways support CAN peripherals over USB. Dell expects these 
devices also support the SocketCAN over USB and is working with HMS to develop 
and upstream the driver. Meanwhile, we'll have to carry this driver as a SAUCE 
patch to support our Ubuntu Core 16 release.

  == Fix ==
  UBUNTU: SAUCE: (no-up) Support IXXAT USB SocketCAN device

  == Regression Potential ==
  Low. The driver will be built only for amd64 kernels and attach itself to 
IXXAT USB-CAN adapters with VID 0x08d8.

  This bug is for tracking purposes only, please do not triage.

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

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

[Kernel-packages] [Bug 1774563] Re: Support SocketCAN over USB on Dell IoT 300x Gateways

[Shrirang Bagul]

** Description changed:

  This driver is from IXXAT and supports SocketCAN over USB.
  (https://www.ixxat.com)
  
+ == SRU Justification ==
+ Dell IoT 300x gateways support CAN peripherals over USB. Dell expects these 
devices also support the SocketCAN over USB. Dell is working with HMS to 
develop and upstream the driver. Meanwhile, we'll have to carry this driver as 
a SAUCE patch to support our Ubuntu Core 16 release.
+ 
+ == Fix ==
+ UBUNTU: SAUCE: (no-up) Support IXXAT USB SocketCAN device
+ 
+ == Regression Potential ==
+ Low. The driver will be built only for amd64 kernels and attach itself to 
IXXAT USB-CAN adapters with VID 0x08d8.
  
  This bug is for tracking purposes only, please do not triage.

** Description changed:

  This driver is from IXXAT and supports SocketCAN over USB.
  (https://www.ixxat.com)
  
  == SRU Justification ==
- Dell IoT 300x gateways support CAN peripherals over USB. Dell expects these 
devices also support the SocketCAN over USB. Dell is working with HMS to 
develop and upstream the driver. Meanwhile, we'll have to carry this driver as 
a SAUCE patch to support our Ubuntu Core 16 release.
+ Dell IoT 300x gateways support CAN peripherals over USB. Dell expects these 
devices also support the SocketCAN over USB and is working with HMS to develop 
and upstream the driver. Meanwhile, we'll have to carry this driver as a SAUCE 
patch to support our Ubuntu Core 16 release.
  
  == Fix ==
  UBUNTU: SAUCE: (no-up) Support IXXAT USB SocketCAN device
  
  == Regression Potential ==
  Low. The driver will be built only for amd64 kernels and attach itself to 
IXXAT USB-CAN adapters with VID 0x08d8.
  
  This bug is for tracking purposes only, please do not triage.

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

Title:
  Support SocketCAN over USB on Dell IoT 300x Gateways

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This driver is from IXXAT and supports SocketCAN over USB.
  (https://www.ixxat.com)

  == SRU Justification ==
  Dell IoT 300x gateways support CAN peripherals over USB. Dell expects these 
devices also support the SocketCAN over USB and is working with HMS to develop 
and upstream the driver. Meanwhile, we'll have to carry this driver as a SAUCE 
patch to support our Ubuntu Core 16 release.

  == Fix ==
  UBUNTU: SAUCE: (no-up) Support IXXAT USB SocketCAN device

  == Regression Potential ==
  Low. The driver will be built only for amd64 kernels and attach itself to 
IXXAT USB-CAN adapters with VID 0x08d8.

  This bug is for tracking purposes only, please do not triage.

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

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

[Kernel-packages] [Bug 1774563] [NEW] Support SocketCAN over USB on Dell IoT 300x Gateways

[Shrirang Bagul]

Public bug reported:

This driver is from IXXAT and supports SocketCAN over USB.
(https://www.ixxat.com)


This bug is for tracking purposes only, please do not triage.

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

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

Title:
  Support SocketCAN over USB on Dell IoT 300x Gateways

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This driver is from IXXAT and supports SocketCAN over USB.
  (https://www.ixxat.com)

  
  This bug is for tracking purposes only, please do not triage.

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

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

[Kernel-packages] [Bug 1773400] Re: Redpine: wifi-ap stopped working after restart

[Shrirang Bagul]

** Description changed:

  SRU Justification:
  --
  
  Impact:
- Wi-Fi access point isn’t visible to outside devices after reboot
+ Wi-Fi access point isn’t visible to outside devices after reboot
  
  Test Case:
- Configure Wi-Fi AP using setup wizard:
-$ sudo wifi-ap.setup-wizard
+ Configure Wi-Fi AP using setup wizard:
+    $ sudo wifi-ap.setup-wizard
  
- Check configured AP settings:
-$ sudo wifi-ap.config get
+ Check configured AP settings:
+    $ sudo wifi-ap.config get
  
-debug: false
-dhcp.lease-time: 12h
-dhcp.range-start: 10.0.60.2
-dhcp.range-stop: 10.0.60.200
-disabled: false
-share.disabled: false
-share.network-interface: wlan0
-wifi.address: 10.0.60.1
-wifi.channel: 6
-wifi.country-code:
-wifi.hostapd-driver: nl80211
-wifi.interface: wlan0
-wifi.interface-mode: direct
-wifi.netmask: ff00
-wifi.operation-mode: g
-wifi.security: wpa2
-wifi.security-passphrase: some-password
-wifi.ssid: dell-gateway
+    debug: false
+    dhcp.lease-time: 12h
+    dhcp.range-start: 10.0.60.2
+    dhcp.range-stop: 10.0.60.200
+    disabled: false
+    share.disabled: false
+    share.network-interface: wlan0
+    wifi.address: 10.0.60.1
+    wifi.channel: 6
+    wifi.country-code:
+    wifi.hostapd-driver: nl80211
+    wifi.interface: wlan0
+    wifi.interface-mode: direct
+    wifi.netmask: ff00
+    wifi.operation-mode: g
+    wifi.security: wpa2
+    wifi.security-passphrase: some-password
+    wifi.ssid: dell-gateway
  
- Restart AP and check its status:
-$ sudo wifi-ap.status restart-ap
+ Restart AP and check its status:
+    $ sudo wifi-ap.status restart-ap
  
- Check status of AP. It is showing true.
-$ sudo wifi-ap.status
-ap.active: true
+ Check status of AP. It is showing true.
+    $ sudo wifi-ap.status
+    ap.active: true
  
- At this point, Wi-Fi access point is not visible.  
-  
+ At this point, Wi-Fi access point is not visible.
+ 
  Fix:
- Power save is not enabled in AP mode and modified the same in source code.
+ Power save is not enabled in AP mode and modified the same in source code.
  
  Regression potential:
- Ran "wifi-ap.status restart-ap" command in every 1 minute and observed 
whether it is visible to third party devices are not. And it is behaving as 
expected.
+ Ran "wifi-ap.status restart-ap" command in every 1 minute and observed 
whether it is visible to third party devices are not. And it is behaving as 
expected.
+ 
+ This patch is for tracking only, please don't triage.

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

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

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

Title:
  Redpine: wifi-ap stopped working after restart

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  SRU Justification:
  --

  Impact:
  Wi-Fi access point isn’t visible to outside devices after reboot

  Test Case:
  Configure Wi-Fi AP using setup wizard:
     $ sudo wifi-ap.setup-wizard

  Check configured AP settings:
     $ sudo wifi-ap.config get

     debug: false
     dhcp.lease-time: 12h
     dhcp.range-start: 10.0.60.2
     dhcp.range-stop: 10.0.60.200
     disabled: false
     share.disabled: false
     share.network-interface: wlan0
     wifi.address: 10.0.60.1
     wifi.channel: 6
     wifi.country-code:
     wifi.hostapd-driver: nl80211
     wifi.interface: wlan0
     wifi.interface-mode: direct
     wifi.netmask: ff00
     wifi.operation-mode: g
     wifi.security: wpa2
     wifi.security-passphrase: some-password
     wifi.ssid: dell-gateway

  Restart AP and check its status:
     $ sudo wifi-ap.status restart-ap

  Check status of AP. It is showing true.
     $ sudo wifi-ap.status
     ap.active: true

  At this point, Wi-Fi access point is not visible.

  Fix:
  Power save is not enabled in AP mode and modified the same in source code.

  Regression potential:
  Ran "wifi-ap.status restart-ap" command in every 1 minute and observed 
whether it is visible to third party devices are not. And it is behaving as 
expected.

  This patch is for tracking only, please don't triage.

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

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

[Kernel-packages] [Bug 1773410] Re: Redpine: Observed kernel panic while when running wireless tests in regression mode

[Shrirang Bagul]

** Description changed:

  SRU Justification
  -
  
  Impact:
- Kernel freezes/panic when running wireless tests in regression
+ Kernel freezes/panic when running wireless tests in regression
  
  Test case:
- 1. Keep a wrong access-point name in sta.conf file and run the nmcli.
- 2. There will be continuous scan will be happen and do remove the module 
using rmmod.sh script.
- 3. When soft scan is happening in redpine driver, before connection. Some 
times, we have observed
-a kernel panic. like below
-[ 1171.913244] BUG: unable to handle page request at 001067e38
-[ 1171.913248] IP: cfg80211_scan_done+0xb0/0xc0 [cfg80211]
-[ 1171.913971]  __ieee80211_scan_completed+0xb1/0x390 [mac80211]
-[ 1171.914078]  ieee80211_scan_work+0x7e/0x480 [mac80211]
-[ 1171.914098]  process_one_work+0x142/0x3d0
-[ 1171.914111]  worker_thread+0x229/0x440
-[ 1171.914122]  kthread+0xf5/0x130
-[ 1171.914132]  ? process_one_work+0x3d0/0x3d0
-[ 1171.914140]  ? kthread_associate_blkcg+0x90/0x90
-[ 1171.914152]  ret_from_fork+0x35/0x40 
-  
+ 1. Keep a wrong access-point name in sta.conf file and run the nmcli.
+ 2. There will be continuous scan will be happen and do remove the module 
using rmmod.sh script.
+ 3. When soft scan is happening in redpine driver, before connection. Some 
times, we have observed
+    a kernel panic. like below
+    [ 1171.913244] BUG: unable to handle page request at 001067e38
+    [ 1171.913248] IP: cfg80211_scan_done+0xb0/0xc0 [cfg80211]
+    [ 1171.913971]  __ieee80211_scan_completed+0xb1/0x390 [mac80211]
+    [ 1171.914078]  ieee80211_scan_work+0x7e/0x480 [mac80211]
+    [ 1171.914098]  process_one_work+0x142/0x3d0
+    [ 1171.914111]  worker_thread+0x229/0x440
+    [ 1171.914122]  kthread+0xf5/0x130
+    [ 1171.914132]  ? process_one_work+0x3d0/0x3d0
+    [ 1171.914140]  ? kthread_associate_blkcg+0x90/0x90
+    [ 1171.914152]  ret_from_fork+0x35/0x40
+ 
  Fix:
- scan work function keeps running even after cancel_hw_scan() call.
- Issue is resolved by calling cancel_work_sync().
+ scan work function keeps running even after cancel_hw_scan() call.
+ Issue is resolved by calling cancel_work_sync().
  
  Regression potential:
- Ran driver_crash.sh for 100 times and didn't see the issue.
+ Ran driver_crash.sh for 100 times and didn't see the issue.
+ 
+ This bug is for tracking purposes only, please don't triage.

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

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

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

Title:
  Redpine: Observed kernel panic while when running wireless tests in
  regression mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  SRU Justification
  -

  Impact:
  Kernel freezes/panic when running wireless tests in regression

  Test case:
  1. Keep a wrong access-point name in sta.conf file and run the nmcli.
  2. There will be continuous scan will be happen and do remove the module 
using rmmod.sh script.
  3. When soft scan is happening in redpine driver, before connection. Some 
times, we have observed
     a kernel panic. like below
     [ 1171.913244] BUG: unable to handle page request at 001067e38
     [ 1171.913248] IP: cfg80211_scan_done+0xb0/0xc0 [cfg80211]
     [ 1171.913971]  __ieee80211_scan_completed+0xb1/0x390 [mac80211]
     [ 1171.914078]  ieee80211_scan_work+0x7e/0x480 [mac80211]
     [ 1171.914098]  process_one_work+0x142/0x3d0
     [ 1171.914111]  worker_thread+0x229/0x440
     [ 1171.914122]  kthread+0xf5/0x130
     [ 1171.914132]  ? process_one_work+0x3d0/0x3d0
     [ 1171.914140]  ? kthread_associate_blkcg+0x90/0x90
     [ 1171.914152]  ret_from_fork+0x35/0x40

  Fix:
  scan work function keeps running even after cancel_hw_scan() call.
  Issue is resolved by calling cancel_work_sync().

  Regression potential:
  Ran driver_crash.sh for 100 times and didn't see the issue.

  This bug is for tracking purposes only, please don't triage.

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

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

[Kernel-packages] [Bug 1772626] Re: [Redpine] HCI command timeout after resume from S4

[Shrirang Bagul]

** Tags added: originate-from-1771268 plano

** Changed in: hwe-next
   Status: New => Confirmed

** Changed in: hwe-next
   Importance: Undecided => Critical

** Changed in: hwe-next
   Importance: Critical => High

** Changed in: hwe-next
 Assignee: (unassigned) => Shrirang Bagul (shrirang-bagul)

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

Title:
  [Redpine] HCI command timeout after resume from S4

Status in HWE Next:
  Confirmed
Status in linux-oem package in Ubuntu:
  Confirmed

Bug description:
  Redpine BT stops working after resume from S4.

  Symptoms:
  - The device list is increasing after resume. 
  - Error after command "hciconfig -a" which as:
  Can't read local name on hci0: Connection timed out (110)

  The reproduce steps:
  1) Go to hibernate mode
  $ sudo systemctl hibernate

  2) Wakeup system by power recycle

  3) Check the bluetooth list
  $ hciconfig -a
  hci1: Type: Primary Bus: SDIO
   BD Address: 00:23:A7:BF:34:F8 ACL MTU: 540:2 SCO MTU: 30:1
   DOWN
   RX bytes:574 acl:0 sco:0 events:30 errors:0
   TX bytes:0 acl:0 sco:0 commands:30 errors:0
   Features: 0x3f 0x02 0x04 0x4e 0xc8 0x0d 0x5b 0x87
   Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1
   Link policy: RSWITCH
   Link mode: SLAVE ACCEPT

  hci0: Type: Primary Bus: SDIO
   BD Address: 00:23:A7:BF:34:F8 ACL MTU: 540:2 SCO MTU: 30:1
   UP RUNNING
   RX bytes:1238 acl:0 sco:0 events:75 errors:0
   TX bytes:0 acl:0 sco:0 commands:75 errors:0
   Features: 0x3f 0x02 0x04 0x4e 0xc8 0x0d 0x5b 0x87
   Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1
   Link policy: RSWITCH
   Link mode: SLAVE ACCEPT
  Can't read local name on hci0: Connection timed out (110)

  4) Go to hibernate and wake again(as step 1-2)

  5) Try ifconfig command to check wifi device
  Result: command no response

  This bug is for tracking purposes only, please don't triage.

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

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

[Kernel-packages] [Bug 1772626] [NEW] [Redpine] HCI command timeout after resume from S4

[Shrirang Bagul]

Public bug reported:

Redpine BT stops working after resume from S4.

Symptoms:
- The device list is increasing after resume. 
- Error after command "hciconfig -a" which as:
Can't read local name on hci0: Connection timed out (110)

The reproduce steps:
1) Go to hibernate mode
$ sudo systemctl hibernate

2) Wakeup system by power recycle

3) Check the bluetooth list
$ hciconfig -a
hci1: Type: Primary Bus: SDIO
 BD Address: 00:23:A7:BF:34:F8 ACL MTU: 540:2 SCO MTU: 30:1
 DOWN
 RX bytes:574 acl:0 sco:0 events:30 errors:0
 TX bytes:0 acl:0 sco:0 commands:30 errors:0
 Features: 0x3f 0x02 0x04 0x4e 0xc8 0x0d 0x5b 0x87
 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1
 Link policy: RSWITCH
 Link mode: SLAVE ACCEPT

hci0: Type: Primary Bus: SDIO
 BD Address: 00:23:A7:BF:34:F8 ACL MTU: 540:2 SCO MTU: 30:1
 UP RUNNING
 RX bytes:1238 acl:0 sco:0 events:75 errors:0
 TX bytes:0 acl:0 sco:0 commands:75 errors:0
 Features: 0x3f 0x02 0x04 0x4e 0xc8 0x0d 0x5b 0x87
 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1
 Link policy: RSWITCH
 Link mode: SLAVE ACCEPT
Can't read local name on hci0: Connection timed out (110)

4) Go to hibernate and wake again(as step 1-2)

5) Try ifconfig command to check wifi device
Result: command no response

This bug is for tracking purposes only, please don't triage.

** Affects: linux-oem (Ubuntu)
 Importance: Critical
 Status: Confirmed

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

** Changed in: linux-oem (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  [Redpine] HCI command timeout after resume from S4

Status in linux-oem package in Ubuntu:
  Confirmed

Bug description:
  Redpine BT stops working after resume from S4.

  Symptoms:
  - The device list is increasing after resume. 
  - Error after command "hciconfig -a" which as:
  Can't read local name on hci0: Connection timed out (110)

  The reproduce steps:
  1) Go to hibernate mode
  $ sudo systemctl hibernate

  2) Wakeup system by power recycle

  3) Check the bluetooth list
  $ hciconfig -a
  hci1: Type: Primary Bus: SDIO
   BD Address: 00:23:A7:BF:34:F8 ACL MTU: 540:2 SCO MTU: 30:1
   DOWN
   RX bytes:574 acl:0 sco:0 events:30 errors:0
   TX bytes:0 acl:0 sco:0 commands:30 errors:0
   Features: 0x3f 0x02 0x04 0x4e 0xc8 0x0d 0x5b 0x87
   Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1
   Link policy: RSWITCH
   Link mode: SLAVE ACCEPT

  hci0: Type: Primary Bus: SDIO
   BD Address: 00:23:A7:BF:34:F8 ACL MTU: 540:2 SCO MTU: 30:1
   UP RUNNING
   RX bytes:1238 acl:0 sco:0 events:75 errors:0
   TX bytes:0 acl:0 sco:0 commands:75 errors:0
   Features: 0x3f 0x02 0x04 0x4e 0xc8 0x0d 0x5b 0x87
   Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1
   Link policy: RSWITCH
   Link mode: SLAVE ACCEPT
  Can't read local name on hci0: Connection timed out (110)

  4) Go to hibernate and wake again(as step 1-2)

  5) Try ifconfig command to check wifi device
  Result: command no response

  This bug is for tracking purposes only, please don't triage.

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

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

[Kernel-packages] [Bug 1757443] Re: Redpine: BLE radio lost issue

[Shrirang Bagul]

After installing 1.173.1 from bionic-proposed:

$ apt list linux-firmware
Listing...
linux-firmware/bionic-proposed,now 1.173.1 all [installed,automatic]
linux-firmware/bionic 1.173 all


Redpine driver reports correct FW revision (1.6.1):

May 22 07:24:36 caracalla kernel: rsi_91x: 

May 22 07:24:36 caracalla kernel: rsi_91x: Firmware file: 
rsi/rs9113_wlan_bt_dual_mode.rps
May 22 07:24:36 caracalla kernel: rsi_91x: Operating mode: 13 [Wi-Fi 
STA + BT DUAL]
May 22 07:24:36 caracalla kernel: rsi_91x: FW Version: 1.6.1
May 22 07:24:36 caracalla kernel: rsi_91x: 

May 22 07:24:36 caracalla kernel: rsi_91x:  RSI Version Info 
==
May 22 07:24:36 caracalla kernel: rsi_91x: 



** 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-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1757443

Title:
  Redpine: BLE radio lost issue

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Triaged
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Incomplete
Status in linux-firmware source package in Bionic:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Radio stops capturing advertisements after several hours.

  Fix: Updated firmware.

  Test Case: See below.

  Regression Potential: Limited to specific hardware.

  ---

  Below are the steps to replicate the issue

  We are doing continuous BLE scanning and monitoring the advertisements
  from reference device. After long periods of capture (several hours),
  the radio stops capturing advertisements and won't start again until
  we power cycle the box or manually unload/load the module via modprobe

  This bug is for tracking purposes only, please don't triage.

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

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

[Kernel-packages] [Bug 1757443] Re: Redpine: BLE radio lost issue

[Shrirang Bagul]

** Tags added: verification-done-bionic

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

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

Title:
  Redpine: BLE radio lost issue

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Triaged
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Incomplete
Status in linux-firmware source package in Bionic:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Radio stops capturing advertisements after several hours.

  Fix: Updated firmware.

  Test Case: See below.

  Regression Potential: Limited to specific hardware.

  ---

  Below are the steps to replicate the issue

  We are doing continuous BLE scanning and monitoring the advertisements
  from reference device. After long periods of capture (several hours),
  the radio stops capturing advertisements and won't start again until
  we power cycle the box or manually unload/load the module via modprobe

  This bug is for tracking purposes only, please don't triage.

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

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

[Kernel-packages] [Bug 1657682] Re: Support latest Redpine WLAN/BT RS9113 driver

[Shrirang Bagul]

** 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/1657682

Title:
  Support latest Redpine WLAN/BT RS9113 driver

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

Bug description:
  Support latest Redpine WLAN/BT RS9113 driver in Ubuntu Xenial kernel.

  This is the latest version of the driver provided by Redpine. For now,
  this driver is enabled only on x86, x86_64 architectures. The impact
  is also restricted to { SDIO_DEVICE(0x041B, 0x9330) } chipsets.

  For linux-oem (4.15) bionic series:
  ~~
  To support RS9113 Wifi+BT chip on Dell Edge 300x IoT Gateways. Most of the
  patches are already upstream (either Accepted or under review) and being
  tracked here:
  https://patchwork.kernel.org/project/linux-wireless/list/?state=*=rsi%3A

  SAUCE patches have been tested by Canonical CE-QA (based on
  Ubuntu-4.15.0-16.17) and HWE is working with the Redpine to get them
  upstreamed to linux-wireless. For now, to meet the project schedule, we'll
  have to carry them in linux-oem.

  The impact is limited to the Redpine RS9113 Wifi+BT with following VID/PID
  { SDIO_DEVICE(0x041B, 0x9330) }.

  This bug is used for tracking purposes, please do not triage.

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

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

[Kernel-packages] [Bug 1769610] Re: Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

[Shrirang Bagul]

** 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/1769610

Title:
  Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux-oem source package in Bionic:
  New

Bug description:
  Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

  On systems using Intel Atom (Baytrail-I) SoC's, slave devices connected on
  HSUART1/2 ports are described by the ACPI BIOS as virtual hardware using
  HID's INT3511/INT3512 [1].

  As a consequence, HW manufacturers have complete freedom to install any
  devices on-board as long as they can be accessed over serial tty
  interface. Once such device is Dell Edge 3002 IoT Gateway which sports
  ZigBee & GPS devices on the HS-UART ports 1 & 2 respectively.

  Post 4.15, with CONFIG_SERIAL_DEV_BUS=y, serdev port controller driver
  handles the enumeration for the slaves connected on these ports. Also,
  /dev/ttySx device nodes for these ports are no longer exposed to the
  userspace.

  This driver has been submitted upstream and is under review. This issue has
  been identified as a regression in 4.15 and multiple solutions are being
  explored. Meanwhile, to support customer and maintain release schedule,
  this driver needs to be in Ubuntu 4.15 based kernels.

  The impact is limited to systems based on Intel Atom E38XX (Baytrail-I)
  SoC's.

  More info:
  https://marc.info/?t=15245587167=1=2

  Please don't triage, this bug is for tracking purposes only.

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

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

[Kernel-packages] [Bug 1769658] Re: hts221 sensor stops working after resume from S3/S4

[Shrirang Bagul]

** 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/1769658

Title:
  hts221 sensor stops working after resume from S3/S4

Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux-oem source package in Bionic:
  New

Bug description:
  Dell Edge 300x IoT Gateways have a relative humidity sensor hts221.
  The sensor stops working (and reports stale values) after the system
  resumes from suspend-to-ram/suspend-to-disk PM states.

  
  This bug is for tracking purposes only, please don't triage.

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

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

[Kernel-packages] [Bug 1753439] Re: Redpine: BLE scanning for nearby beacons per second is too low and result high loss rate.

[Shrirang Bagul]

The verification was done by Redpine, ODM and one of the Beta customers.

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

Title:
  Redpine: BLE scanning for nearby beacons per second is too low and
  result high loss rate.

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

Bug description:
  SRU Justification

  Impact: BLE scanning for nearby beacons per second is too low and
  result high loss rate.

  Fix: Updated firmware.

  Test Case: Test on affected hardware using instructions below.

  Regression Potential: Limited to specific hardware.

  ---

  Steps to replicate the issue:

  1. Power on the BT device, then change the terminal by "Ctil+F1" or open 
another putty to ssh SUT.
  2.Use command below to discover BLE device.
  $ sudo stdbuf -i0-o0 -e0 /snap/bluez/current/usr/bin/hcitool lescan 
--duplicates --passive | perl -nle 'print scalar(localtime), " ",$_'
  3. log as attachment.

  This bug is for tracking purposes only, do not triage.

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

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

[Kernel-packages] [Bug 1753439] Re: Redpine: BLE scanning for nearby beacons per second is too low and result high loss rate.

[Shrirang Bagul]

** 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-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1753439

Title:
  Redpine: BLE scanning for nearby beacons per second is too low and
  result high loss rate.

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

Bug description:
  SRU Justification

  Impact: BLE scanning for nearby beacons per second is too low and
  result high loss rate.

  Fix: Updated firmware.

  Test Case: Test on affected hardware using instructions below.

  Regression Potential: Limited to specific hardware.

  ---

  Steps to replicate the issue:

  1. Power on the BT device, then change the terminal by "Ctil+F1" or open 
another putty to ssh SUT.
  2.Use command below to discover BLE device.
  $ sudo stdbuf -i0-o0 -e0 /snap/bluez/current/usr/bin/hcitool lescan 
--duplicates --passive | perl -nle 'print scalar(localtime), " ",$_'
  3. log as attachment.

  This bug is for tracking purposes only, do not triage.

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

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

[Kernel-packages] [Bug 1757443] Re: Redpine: BLE radio lost issue

[Shrirang Bagul]

** Tags added: verification-done-xenial

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

Title:
  Redpine: BLE radio lost issue

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Triaged
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Incomplete
Status in linux-firmware source package in Bionic:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Radio stops capturing advertisements after several hours.

  Fix: Updated firmware.

  Test Case: See below.

  Regression Potential: Limited to specific hardware.

  ---

  Below are the steps to replicate the issue

  We are doing continuous BLE scanning and monitoring the advertisements
  from reference device. After long periods of capture (several hours),
  the radio stops capturing advertisements and won't start again until
  we power cycle the box or manually unload/load the module via modprobe

  This bug is for tracking purposes only, please don't triage.

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

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

[Kernel-packages] [Bug 1769658] [NEW] hts221 sensor stops working after resume from S3/S4

[Shrirang Bagul]

Public bug reported:

Dell Edge 300x IoT Gateways have a relative humidity sensor hts221. The
sensor stops working (and reports stale values) after the system resumes
from suspend-to-ram/suspend-to-disk PM states.


This bug is for tracking purposes only, please don't triage.

** Affects: linux-oem (Ubuntu)
 Importance: Critical
 Status: Confirmed

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

** Changed in: linux-oem (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  hts221 sensor stops working after resume from S3/S4

Status in linux-oem package in Ubuntu:
  Confirmed

Bug description:
  Dell Edge 300x IoT Gateways have a relative humidity sensor hts221.
  The sensor stops working (and reports stale values) after the system
  resumes from suspend-to-ram/suspend-to-disk PM states.

  
  This bug is for tracking purposes only, please don't triage.

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

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

[Kernel-packages] [Bug 1657682] Re: Support latest Redpine WLAN/BT RS9113 driver

[Shrirang Bagul]

** Description changed:

  Support latest Redpine WLAN/BT RS9113 driver in Ubuntu Xenial kernel.
  
  This is the latest version of the driver provided by Redpine. For now,
  this driver is enabled only on x86, x86_64 architectures. The impact is
  also restricted to { SDIO_DEVICE(0x041B, 0x9330) } chipsets.
  
+ For linux-oem (4.15) bionic series:
+ ~~
+ To support RS9113 Wifi+BT chip on Dell Edge 300x IoT Gateways. Most of the
+ patches are already upstream (either Accepted or under review) and being
+ tracked here:
+ https://patchwork.kernel.org/project/linux-wireless/list/?state=*=rsi%3A
+ 
+ SAUCE patches have been tested by Canonical CE-QA (based on
+ Ubuntu-4.15.0-16.17) and HWE is working with the Redpine to get them
+ upstreamed to linux-wireless. For now, to meet the project schedule, we'll
+ have to carry them in linux-oem.
+ 
+ The impact is limited to the Redpine RS9113 Wifi+BT with following VID/PID
+ { SDIO_DEVICE(0x041B, 0x9330) }.
+ 
  This bug is used for tracking purposes, please do not triage.

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

Title:
  Support latest Redpine WLAN/BT RS9113 driver

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

Bug description:
  Support latest Redpine WLAN/BT RS9113 driver in Ubuntu Xenial kernel.

  This is the latest version of the driver provided by Redpine. For now,
  this driver is enabled only on x86, x86_64 architectures. The impact
  is also restricted to { SDIO_DEVICE(0x041B, 0x9330) } chipsets.

  For linux-oem (4.15) bionic series:
  ~~
  To support RS9113 Wifi+BT chip on Dell Edge 300x IoT Gateways. Most of the
  patches are already upstream (either Accepted or under review) and being
  tracked here:
  https://patchwork.kernel.org/project/linux-wireless/list/?state=*=rsi%3A

  SAUCE patches have been tested by Canonical CE-QA (based on
  Ubuntu-4.15.0-16.17) and HWE is working with the Redpine to get them
  upstreamed to linux-wireless. For now, to meet the project schedule, we'll
  have to carry them in linux-oem.

  The impact is limited to the Redpine RS9113 Wifi+BT with following VID/PID
  { SDIO_DEVICE(0x041B, 0x9330) }.

  This bug is used for tracking purposes, please do not triage.

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

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

[Kernel-packages] [Bug 1657682] Re: Support latest Redpine WLAN/BT RS9113 driver

[Shrirang Bagul]

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

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

** Changed in: linux-oem (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  Support latest Redpine WLAN/BT RS9113 driver

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

Bug description:
  Support latest Redpine WLAN/BT RS9113 driver in Ubuntu Xenial kernel.

  This is the latest version of the driver provided by Redpine. For now,
  this driver is enabled only on x86, x86_64 architectures. The impact
  is also restricted to { SDIO_DEVICE(0x041B, 0x9330) } chipsets.

  This bug is used for tracking purposes, please do not triage.

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

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

[Kernel-packages] [Bug 1769610] Re: Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

[Shrirang Bagul]

** Description changed:

  Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty
  
  On systems using Intel Atom (Baytrail-I) SoC's, slave devices connected on
  HSUART1/2 ports are described by the ACPI BIOS as virtual hardware using
  HID's INT3511/INT3512 [1].
  
  As a consequence, HW manufacturers have complete freedom to install any
  devices on-board as long as they can be accessed over serial tty
  interface. Once such device is Dell Edge 3002 IoT Gateway which sports
  ZigBee & GPS devices on the HS-UART ports 1 & 2 respectively.
  
  Post 4.15, with CONFIG_SERIAL_DEV_BUS=y, serdev port controller driver
  handles the enumeration for the slaves connected on these ports. Also,
  /dev/ttySx device nodes for these ports are no longer exposed to the
  userspace.
  
+ This driver has been submitted upstream and is under review. This issue has
+ been identified as a regression in 4.15 and multiple solutions are being
+ explored. Meanwhile, to support customer and maintain release schedule,
+ this driver needs to be in Ubuntu 4.15 based kernels.
+ 
+ The impact is limited to systems based on Intel Atom E38XX (Baytrail-I)
+ SoC's.
+ 
+ More info:
+ https://marc.info/?t=15245587167=1=2
+ 
  Please don't triage, this bug is for tracking purposes only.

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

Title:
  Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

Status in linux-oem package in Ubuntu:
  Confirmed

Bug description:
  Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

  On systems using Intel Atom (Baytrail-I) SoC's, slave devices connected on
  HSUART1/2 ports are described by the ACPI BIOS as virtual hardware using
  HID's INT3511/INT3512 [1].

  As a consequence, HW manufacturers have complete freedom to install any
  devices on-board as long as they can be accessed over serial tty
  interface. Once such device is Dell Edge 3002 IoT Gateway which sports
  ZigBee & GPS devices on the HS-UART ports 1 & 2 respectively.

  Post 4.15, with CONFIG_SERIAL_DEV_BUS=y, serdev port controller driver
  handles the enumeration for the slaves connected on these ports. Also,
  /dev/ttySx device nodes for these ports are no longer exposed to the
  userspace.

  This driver has been submitted upstream and is under review. This issue has
  been identified as a regression in 4.15 and multiple solutions are being
  explored. Meanwhile, to support customer and maintain release schedule,
  this driver needs to be in Ubuntu 4.15 based kernels.

  The impact is limited to systems based on Intel Atom E38XX (Baytrail-I)
  SoC's.

  More info:
  https://marc.info/?t=15245587167=1=2

  Please don't triage, this bug is for tracking purposes only.

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

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

[Kernel-packages] [Bug 1769610] [NEW] Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

[Shrirang Bagul]

Public bug reported:

Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

On systems using Intel Atom (Baytrail-I) SoC's, slave devices connected on
HSUART1/2 ports are described by the ACPI BIOS as virtual hardware using
HID's INT3511/INT3512 [1].

As a consequence, HW manufacturers have complete freedom to install any
devices on-board as long as they can be accessed over serial tty
interface. Once such device is Dell Edge 3002 IoT Gateway which sports
ZigBee & GPS devices on the HS-UART ports 1 & 2 respectively.

Post 4.15, with CONFIG_SERIAL_DEV_BUS=y, serdev port controller driver
handles the enumeration for the slaves connected on these ports. Also,
/dev/ttySx device nodes for these ports are no longer exposed to the
userspace.

Please don't triage, this bug is for tracking purposes only.

** Affects: linux-oem (Ubuntu)
 Importance: Critical
 Status: Confirmed

** Description changed:

  Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty
  
+ On systems using Intel Atom (Baytrail-I) SoC's, slave devices connected on
+ HSUART1/2 ports are described by the ACPI BIOS as virtual hardware using
+ HID's INT3511/INT3512 [1].
+ 
+ As a consequence, HW manufacturers have complete freedom to install any
+ devices on-board as long as they can be accessed over serial tty
+ interface. Once such device is Dell Edge 3002 IoT Gateway which sports
+ ZigBee & GPS devices on the HS-UART ports 1 & 2 respectively.
+ 
+ Post 4.15, with CONFIG_SERIAL_DEV_BUS=y, serdev port controller driver
+ handles the enumeration for the slaves connected on these ports. Also,
+ /dev/ttySx device nodes for these ports are no longer exposed to the
+ userspace.
  
  Please don't triage, this bug is for tracking purposes only.

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

** Changed in: linux-oem (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

Status in linux-oem package in Ubuntu:
  Confirmed

Bug description:
  Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

  On systems using Intel Atom (Baytrail-I) SoC's, slave devices connected on
  HSUART1/2 ports are described by the ACPI BIOS as virtual hardware using
  HID's INT3511/INT3512 [1].

  As a consequence, HW manufacturers have complete freedom to install any
  devices on-board as long as they can be accessed over serial tty
  interface. Once such device is Dell Edge 3002 IoT Gateway which sports
  ZigBee & GPS devices on the HS-UART ports 1 & 2 respectively.

  Post 4.15, with CONFIG_SERIAL_DEV_BUS=y, serdev port controller driver
  handles the enumeration for the slaves connected on these ports. Also,
  /dev/ttySx device nodes for these ports are no longer exposed to the
  userspace.

  Please don't triage, this bug is for tracking purposes only.

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

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

[Kernel-packages] [Bug 1757443] Re: Redpine: BLE radio lost issue

[Shrirang Bagul]

For Xenial, when can we expect the Ubuntu-1.157.18 release?

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

Title:
  Redpine: BLE radio lost issue

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Triaged
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Incomplete
Status in linux-firmware source package in Bionic:
  Incomplete

Bug description:
  SRU Justification

  Impact: Radio stops capturing advertisements after several hours.

  Fix: Updated firmware.

  Test Case: See below.

  Regression Potential: Limited to specific hardware.

  ---

  Below are the steps to replicate the issue

  We are doing continuous BLE scanning and monitoring the advertisements
  from reference device. After long periods of capture (several hours),
  the radio stops capturing advertisements and won't start again until
  we power cycle the box or manually unload/load the module via modprobe

  This bug is for tracking purposes only, please don't triage.

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

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

[Kernel-packages] [Bug 1757443] Re: Redpine: BLE radio lost issue

[Shrirang Bagul]

Yes, for Bionic, Redpine will push their FW into upstream linux-
firmware.

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

Title:
  Redpine: BLE radio lost issue

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Triaged
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Incomplete
Status in linux-firmware source package in Bionic:
  Incomplete

Bug description:
  SRU Justification

  Impact: Radio stops capturing advertisements after several hours.

  Fix: Updated firmware.

  Test Case: See below.

  Regression Potential: Limited to specific hardware.

  ---

  Below are the steps to replicate the issue

  We are doing continuous BLE scanning and monitoring the advertisements
  from reference device. After long periods of capture (several hours),
  the radio stops capturing advertisements and won't start again until
  we power cycle the box or manually unload/load the module via modprobe

  This bug is for tracking purposes only, please don't triage.

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

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

[Kernel-packages] [Bug 1757443] Re: Redpine: BLE radio lost issue

[Shrirang Bagul]

The Bionic kernel will switch to the existing driver in the kernel
(http://kernel.ubuntu.com/git/ubuntu/ubuntu-
bionic.git/tree/drivers/net/wireless/rsi) to support RS9113 WiFi+BT
combo module on Dell Edge 300X IoT gateways.

HWE is working with Redpine to fix issues in this driver to for 18.04
server support.

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

Title:
  Redpine: BLE radio lost issue

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Triaged
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Incomplete
Status in linux-firmware source package in Bionic:
  Incomplete

Bug description:
  SRU Justification

  Impact: Radio stops capturing advertisements after several hours.

  Fix: Updated firmware.

  Test Case: See below.

  Regression Potential: Limited to specific hardware.

  ---

  Below are the steps to replicate the issue

  We are doing continuous BLE scanning and monitoring the advertisements
  from reference device. After long periods of capture (several hours),
  the radio stops capturing advertisements and won't start again until
  we power cycle the box or manually unload/load the module via modprobe

  This bug is for tracking purposes only, please don't triage.

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

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

[Kernel-packages] [Bug 1757435] Re: Redpine: WiFi scan stopping issue observed with BLE

[Shrirang Bagul]

** 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/1757435

Title:
  Redpine: WiFi scan stopping issue observed with BLE

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  SRU Justification:
  --

  Impact:
     WiFi scan stopping issue observed with BLE

  Test case:
     1)  Any PC (Ubuntu Desktop): setup iBeacon advertiser
     2)  Caracalla 3003 (Ubuntu Server/Core) run:
  ./scan.sh
   By default WiFi supplicant will run on Caracalla
   You can check the WiFi scan results by using below command
  iw dev wlan0 scan

   After 24hrs successful regression, we are unable to get the
  WiFi scan results by giving the above command

  Fix:
     Resolve this by waiting for the confirmation for a management packet from 
firmware.

  Regression potential:
  Below stress tests are conducted to ensure there is no issue in WiFi scan
  BLE Scan + WLAN scan
  BT Scan + WLAN scan
  BLE scan + WLAN connected

  Attached are BLE scripts.

  This bug is for tracking purposes only, please don't triage.

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

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

[Kernel-packages] [Bug 1675327] Re: Fix line-out port noise on Baytrail-I with RT5660 based sound card

[Shrirang Bagul]

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

** Changed in: linux-oem (Ubuntu)
   Importance: Undecided => Critical

** Changed in: linux-oem (Ubuntu)
 Assignee: (unassigned) => Shrirang Bagul (shrirang-bagul)

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

Title:
  Fix line-out port noise on Baytrail-I with RT5660 based sound card

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

Bug description:
  On Dell IoT gateways, Baytrail-I ASoC with RT5660(ALC3277) codec
  supports line-out port. However, the audio output has background
  noise.

  This bug is used for tracking purposes, please do not triage.

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

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

[Kernel-packages] [Bug 1675327] Re: Fix line-out port noise on Baytrail-I with RT5660 based sound card

[Shrirang Bagul]

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

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

Title:
  Fix line-out port noise on Baytrail-I with RT5660 based sound card

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

Bug description:
  On Dell IoT gateways, Baytrail-I ASoC with RT5660(ALC3277) codec
  supports line-out port. However, the audio output has background
  noise.

  This bug is used for tracking purposes, please do not triage.

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

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

[Kernel-packages] [Bug 1685133] Re: Fix RX fail issue on Exar USB serial driver after resume from S3/S4

[Shrirang Bagul]

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

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

** Changed in: linux-oem (Ubuntu)
 Assignee: (unassigned) => Shrirang Bagul (shrirang-bagul)

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

Title:
  Fix RX fail issue on Exar USB serial driver after resume from S3/S4

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

Bug description:
  Resolution of LP: #1645591 added support for Exar USB UART devices in
  Ubuntu Xenial kernel. However, the devices fail to RX data after
  system resumes from suspend-to-ram(S3) and suspend-to-disk(S4). This
  bug is to track the integration of the driver released by the vendor
  to fix this issue.

  Changelog:
  
  Version 1B, 11/6/2015
  Fixed Bug: The conditional logic to support kernel 3.9 was incorrect(line 396 
in xr_usb_serial_common.c).
  
  Version 1A, 1/9/2015
  This driver will work with any USB UART function in these Exar devices:
  XR21V1410/1412/1414
  XR21B1411
  XR21B1420/1422/1424
  XR22801/802/804

  Exar serial devices are typically enuremated as /dev/ttyXRUSB[0-3]

  This bug is used for tracking purposes, please do not triage.

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

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

[Kernel-packages] [Bug 1690362] Re: Exar usb-serial doesn't restore baud rate after resume from S3/S4

[Shrirang Bagul]

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

** Changed in: linux-oem (Ubuntu)
 Assignee: (unassigned) => Shrirang Bagul (shrirang-bagul)

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

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

Title:
  Exar usb-serial doesn't restore baud rate after resume from S3/S4

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

Bug description:
  Resume from suspend-to-ram and suspend-to-disk should restore data 
send/receive over Exar usb-serial ports. The XR21V1412 ports were using the 
hardware power-on default of 9600bps
  after resume from S3/S4. This patch re-initializes the baud rate and fixes 
the re-connection issues after resume from S3/S4.

  This bug is to track the integration of the driver released by the
  vendor to fix this issue.

  Changelog:

  Version 1B, 11/6/2015
  Fixed Bug: The conditional logic to support kernel 3.9 was incorrect(line 396 
in xr_usb_serial_common.c).

  Version 1A, 1/9/2015
  This driver will work with any USB UART function in these Exar devices:
  XR21V1410/1412/1414
  XR21B1411
  XR21B1420/1422/1424
  XR22801/802/804

  Exar serial devices are typically enuremated as /dev/ttyXRUSB[0-3]

  This bug is used for tracking purposes, please do not triage.

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

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

[Kernel-packages] [Bug 1736317] Re: ath10k: enhance rf signal strength

[Shrirang Bagul]

** 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/1736317

Title:
  ath10k: enhance rf signal strength

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

Bug description:
  ath10k: add max_tx_power for QCA6174 WLAN.RM.2.0 firmware
  QCA6174 WLAN.RM.2.0 firmware uses max_tx_power instead of using max_reg_power
  to set transmission power. The tx power was about -50dbm, after applying this
  change, it become -32dbm.

  Signed-off-by: Alan Liu 
  Signed-off-by: Kalle Valo 

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/ath/ath10k?id=513527c87a7feab2a5b31db07e5b07864d3c08f7

  This fix already included in Zesty/Artful/Bionic kernels.

  This bug is for tracking purposes only, please do not triage.

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

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

[Kernel-packages] [Bug 1757443] Re: Redpine: BLE radio lost issue

[Shrirang Bagul]

Required for both Xenial as well as Bionic.

** Description changed:

  Below are the steps to replicate the issue
  
  We are doing continuous BLE scanning and monitoring the advertisements
  from reference device. After long periods of capture (several hours),
  the radio stops capturing advertisements and won't start again until we
  power cycle the box or manually unload/load the module via modprobe
+ 
+ This bug is for tracking purposes only, please don't triage.

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

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

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

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

** Changed in: linux-firmware (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  Redpine: BLE radio lost issue

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Below are the steps to replicate the issue

  We are doing continuous BLE scanning and monitoring the advertisements
  from reference device. After long periods of capture (several hours),
  the radio stops capturing advertisements and won't start again until
  we power cycle the box or manually unload/load the module via modprobe

  This bug is for tracking purposes only, please don't triage.

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

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

[Kernel-packages] [Bug 1757435] Re: Redpine: WiFi scan stopping issue observed with BLE

[Shrirang Bagul]

** Description changed:

  Below is the procedure to reproduce this issue
  
+    1)  Any PC (Ubuntu Desktop): setup iBeacon advertiser
+    2)  Caracalla 3003 (Ubuntu Server/Core) run:
+ ./scan.sh
+  By default WiFi supplicant will run on Caracalla
+  You can check the WiFi scan results by using below command
+ iw dev wlan0 scan
  
-1)  Any PC (Ubuntu Desktop): setup iBeacon advertiser
-2)  Caracalla 3003 (Ubuntu Server/Core) run:
- ./scan.sh
-  By default WiFi supplicant will run on Caracalla
-  You can check the WiFi scan results by using below command
- iw dev wlan0 scan
- 
-  After 24hrs successful regression, we are unable to get the
+  After 24hrs successful regression, we are unable to get the
  WiFi scan results by giving the above command
  
- Attached are BLE scripts
+ Attached are BLE scripts.
+ 
+ This bug is for tracking purposes only, please don't triage.

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

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

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

Title:
  Redpine: WiFi scan stopping issue observed with BLE

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Below is the procedure to reproduce this issue

     1)  Any PC (Ubuntu Desktop): setup iBeacon advertiser
     2)  Caracalla 3003 (Ubuntu Server/Core) run:
  ./scan.sh
   By default WiFi supplicant will run on Caracalla
   You can check the WiFi scan results by using below command
  iw dev wlan0 scan

   After 24hrs successful regression, we are unable to get the
  WiFi scan results by giving the above command

  Attached are BLE scripts.

  This bug is for tracking purposes only, please don't triage.

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

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

[Kernel-packages] [Bug 1753439] Re: Redpine: BLE scanning for nearby beacons per second is too low and result high loss rate.

[Shrirang Bagul]

This firmware is required for in Bionic as well to support Dell Edge
300X devices in 18.04.

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

Title:
  Redpine: BLE scanning for nearby beacons per second is too low and
  result high loss rate.

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in linux-firmware source package in Xenial:
  Fix Committed

Bug description:
  Steps to replicate the issue:

  1. Power on the BT device, then change the terminal by "Ctil+F1" or open 
another putty to ssh SUT.
  2.Use command below to discover BLE device.
  $ sudo stdbuf -i0-o0 -e0 /snap/bluez/current/usr/bin/hcitool lescan 
--duplicates --passive | perl -nle 'print scalar(localtime), " ",$_'
  3. log as attachment.

  This bug is for tracking purposes only, do not triage.

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

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

[Kernel-packages] [Bug 1753439] Re: Redpine: BLE scanning for nearby beacons per second is too low and result high loss rate.

[Shrirang Bagul]

** Description changed:

  Steps to replicate the issue:
  
  1. Power on the BT device, then change the terminal by "Ctil+F1" or open 
another putty to ssh SUT.
  2.Use command below to discover BLE device.
  $ sudo stdbuf -i0-o0 -e0 /snap/bluez/current/usr/bin/hcitool lescan 
--duplicates --passive | perl -nle 'print scalar(localtime), " ",$_'
  3. log as attachment.
+ 
+ This bug is for tracking purposes only, do not triage.

** 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/1753439

Title:
  Redpine: BLE scanning for nearby beacons per second is too low and
  result high loss rate.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to replicate the issue:

  1. Power on the BT device, then change the terminal by "Ctil+F1" or open 
another putty to ssh SUT.
  2.Use command below to discover BLE device.
  $ sudo stdbuf -i0-o0 -e0 /snap/bluez/current/usr/bin/hcitool lescan 
--duplicates --passive | perl -nle 'print scalar(localtime), " ",$_'
  3. log as attachment.

  This bug is for tracking purposes only, do not triage.

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

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

[Kernel-packages] [Bug 1753438] Re: Redpine: Sometimes Wi-Fi connection shows "unavailable" after resume from WoWLAN S4. WLAN can be recover after reboot or reloading WIFI driver.

[Shrirang Bagul]

** Description changed:

  Following are steps to reproduce the issue:
  
  1. Ensure WoWLAN is enabled in BIOS.
  2. Initiate connection to an AP (using nmcli)
  3. Configure the device for WoWLAN, run the command:
- $ sudo iw phy phy0 wowlan enable magic-packet
+ $ sudo iw phy phy0 wowlan enable magic-packet
  4. Enter S4 (using hibernate)
  5. From another computer on the same network run the following command:
- $ wakeonlan {mac}
+ $ wakeonlan {mac}
  6. Check network states and WIFI shows "Unavailable"
+ 
+ This bug is for tracking purposes only, do not triage.

** 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/1753438

Title:
  Redpine: Sometimes Wi-Fi connection shows "unavailable" after resume
  from WoWLAN S4. WLAN can be recover after reboot or reloading WIFI
  driver.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Following are steps to reproduce the issue:

  1. Ensure WoWLAN is enabled in BIOS.
  2. Initiate connection to an AP (using nmcli)
  3. Configure the device for WoWLAN, run the command:
  $ sudo iw phy phy0 wowlan enable magic-packet
  4. Enter S4 (using hibernate)
  5. From another computer on the same network run the following command:
  $ wakeonlan {mac}
  6. Check network states and WIFI shows "Unavailable"

  This bug is for tracking purposes only, do not triage.

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

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

[Kernel-packages] [Bug 1738773] Re: Connection issue in Bluetooth SPP mode between a Dell Edge Gateway 3000 and an HC-05 BT module attached to Arduino Uno

[Shrirang Bagul]

** Tags added: verification-done-xenial

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

Title:
  Connection issue in Bluetooth SPP mode between a Dell Edge Gateway
  3000 and an HC-05 BT module attached to Arduino Uno

Status in linux package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in linux-firmware source package in Xenial:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Connection issue in Bluetooth SPP mode between a Dell Edge
  Gateway 3000 and an HC-05 BT module attached to Arduino Uno

  Fix: Updated firmware from Redpine containing a fix for the issue.

  Regression Potential: Below stress tests are conducted to ensure there is no 
regression with updated firmware
  BT mouse + BT keyboard
  BT mouse + BLE keyboard
  BT keyboard + BLE mouse
  BLE keyboard + BLE mouse
  BT mouse or keyboard + Wifi connected
  BT mouse + BT keyboard + WiFi connected
  BLE mouse + BLE keyboard + WiFi Connected
  BT mouse + BLE keyboard + Wifi connected
  BLE mouse + BT keyboard + Wifi connected
  (BT or BLE) mouse and/or (BT or BLE) keyboard + Wifi connected + Wifi Scan
  (BT or BLE) mouse and/or (BT or BLE) keyboard + Wifi connected + BT inquiry + 
BLE scan
  BT file transfer from mobile + WiFi connected

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

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

[Kernel-packages] [Bug 1742090] Re: Redpine: Wifi/BT not functioning after s3 resume

[Shrirang Bagul]

** Tags added: originate-from-1738169 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/1742090

Title:
  Redpine: Wifi/BT not functioning after s3 resume

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

Bug description:
  System cannot be waked by wowlan, but sometimes works.
  When the wowlan not works and system waked by other wakeup sources, after 
resume the wifi and BT would not functioning until reload driver.

  The driver/FW info:
  [ 395.217187] ven_rsi_91x:  RSI Version Info ==
  [ 395.217188] ven_rsi_91x: 
  [ 395.217192] ven_rsi_91x: FW Version : 1.5.4
  [ 395.217198] ven_rsi_91x: Driver Version : RS9113.NB0.NL.GNU.LNX.1.2
  [ 395.217200] ven_rsi_91x: Operating mode : 13 [Wi-Fi STA + BT DUAL]
  [ 395.217201] ven_rsi_91x: Firmware file : RS9113_WLAN_BT_DUAL_MODE.rps
  [ 395.217202] ven_rsi_91x: 

  Kernel version: 4.4.0-98-generic
  Kernel snap: caracalla-kernel version:4.4.0-98.121-1 revision:58
  BIOS version: 01.00.05 (Also tested with 01.00.03)
  Tested SKU: T, Media, GPA

  The reproduce steps:
  1. Enable Wowlan and Wol in BIOS
  2. Boot up Ubuntu core
  3. Connect to Wifi AP
  $ nmcli d wifi connect  password 
  4. Enable wowlan
  $ sudo iw phy phy0 wowlan enable magic-packet
  5. Enter suspend or hibernate
  $ sudo systemctl suspend
  or
  $ sudo systemctl hibernate
  6. Send wake signal from another machine
  # wakeonlan 
  or
  # sudo etherwake 
  7. If system not waked, try to wol or other wake source
  # wakeonlan 
  8. After resume, check the wifi/BT function, but not functioning.
  $ nmcli dev
  DEVICE TYPE STATE CONNECTION
  eth0 ethernet connected Wired connection 1
  wlan0 wifi disconnected --
  eth1 ethernet unavailable --
  cdc-wdm0 gsm unavailable --
  lo loopback unmanaged --
  $ nmcli dev wifi rescan
  $ nmcli dev wfii list
  No wifi APs found

  $ sudo bluetoothctl
  [NEW] Controller 00:23:A7:EA:65:64 0225399 [default]
  [bluetooth]# power on
  Failed to set power on: org.bluez.Error.Failed

  The not functioning issue can be fixed by reload driver.
  Also hibernate wakeup fails, and wake by other wake source. The Wifi/BT still 
functioning which could be the FW is reloaded by driver.

  This bug is only for tracking purporse, please do not triage.

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

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

[Kernel-packages] [Bug 1742094] Re: [16.04][classic] Redpine: wowlan feature doesn't work

[Shrirang Bagul]

** Tags added: originate-from-1736097 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/1742094

Title:
  [16.04][classic] Redpine: wowlan feature doesn't work

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

Bug description:
  Steps to reproduce:

   1. Ensure WoWLAN is enabled in BIOS.
   2. Initiate connection to an AP (using nmcli)
   3. Configure the device for WoWLAN, run the command:
  $ sudo iw phy phy0 wowlan enable magic-packet
   4. Enter S5/S4/S3 (using poweroff, etc.)
   5. From another computer on the same network run the following command:
  $ wakeonlan {mac} (in my case `wakeonlan 00:23:a7:ec:b4:04`)

  Expected result: the device starts/resume

  This bug is only for tracking purporse, please do not triage.

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

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

[Kernel-packages] [Bug 1742090] Re: Wifi/BT not functioning after s3 resume

[Shrirang Bagul]

** Description changed:

  System cannot be waked by wowlan, but sometimes works.
  When the wowlan not works and system waked by other wakeup sources, after 
resume the wifi and BT would not functioning until reload driver.
  
  The driver/FW info:
  [ 395.217187] ven_rsi_91x:  RSI Version Info ==
  [ 395.217188] ven_rsi_91x: 
  [ 395.217192] ven_rsi_91x: FW Version : 1.5.4
  [ 395.217198] ven_rsi_91x: Driver Version : RS9113.NB0.NL.GNU.LNX.1.2
  [ 395.217200] ven_rsi_91x: Operating mode : 13 [Wi-Fi STA + BT DUAL]
  [ 395.217201] ven_rsi_91x: Firmware file : RS9113_WLAN_BT_DUAL_MODE.rps
  [ 395.217202] ven_rsi_91x: 
  
  Kernel version: 4.4.0-98-generic
  Kernel snap: caracalla-kernel version:4.4.0-98.121-1 revision:58
  BIOS version: 01.00.05 (Also tested with 01.00.03)
  Tested SKU: T, Media, GPA
  
  The reproduce steps:
  1. Enable Wowlan and Wol in BIOS
  2. Boot up Ubuntu core
  3. Connect to Wifi AP
- $ nmcli d wifi connect  password 
+ $ nmcli d wifi connect  password 
  4. Enable wowlan
- $ sudo iw phy phy0 wowlan enable magic-packet
+ $ sudo iw phy phy0 wowlan enable magic-packet
  5. Enter suspend or hibernate
- $ sudo systemctl suspend
- or
- $ sudo systemctl hibernate
+ $ sudo systemctl suspend
+ or
+ $ sudo systemctl hibernate
  6. Send wake signal from another machine
- # wakeonlan 
- or
- # sudo etherwake 
+ # wakeonlan 
+ or
+ # sudo etherwake 
  7. If system not waked, try to wol or other wake source
- # wakeonlan 
+ # wakeonlan 
  8. After resume, check the wifi/BT function, but not functioning.
- $ nmcli dev
- DEVICE TYPE STATE CONNECTION
- eth0 ethernet connected Wired connection 1
- wlan0 wifi disconnected --
- eth1 ethernet unavailable --
- cdc-wdm0 gsm unavailable --
- lo loopback unmanaged --
- $ nmcli dev wifi rescan
- $ nmcli dev wfii list
- No wifi APs found
+ $ nmcli dev
+ DEVICE TYPE STATE CONNECTION
+ eth0 ethernet connected Wired connection 1
+ wlan0 wifi disconnected --
+ eth1 ethernet unavailable --
+ cdc-wdm0 gsm unavailable --
+ lo loopback unmanaged --
+ $ nmcli dev wifi rescan
+ $ nmcli dev wfii list
+ No wifi APs found
  
- $ sudo bluetoothctl
- [NEW] Controller 00:23:A7:EA:65:64 0225399 [default]
- [bluetooth]# power on
- Failed to set power on: org.bluez.Error.Failed
+ $ sudo bluetoothctl
+ [NEW] Controller 00:23:A7:EA:65:64 0225399 [default]
+ [bluetooth]# power on
+ Failed to set power on: org.bluez.Error.Failed
  
  The not functioning issue can be fixed by reload driver.
  Also hibernate wakeup fails, and wake by other wake source. The Wifi/BT still 
functioning which could be the FW is reloaded by driver.
+ 
+ This bug is only for tracking purporse, please do not triage.

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

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

** Summary changed:

- Wifi/BT not functioning after s3 resume
+ Redpine: Wifi/BT not functioning after s3 resume

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

Title:
  Redpine: Wifi/BT not functioning after s3 resume

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

Bug description:
  System cannot be waked by wowlan, but sometimes works.
  When the wowlan not works and system waked by other wakeup sources, after 
resume the wifi and BT would not functioning until reload driver.

  The driver/FW info:
  [ 395.217187] ven_rsi_91x:  RSI Version Info ==
  [ 395.217188] ven_rsi_91x: 
  [ 395.217192] ven_rsi_91x: FW Version : 1.5.4
  [ 395.217198] ven_rsi_91x: Driver Version : RS9113.NB0.NL.GNU.LNX.1.2
  [ 395.217200] ven_rsi_91x: Operating mode : 13 [Wi-Fi STA + BT DUAL]
  [ 395.217201] ven_rsi_91x: Firmware file : RS9113_WLAN_BT_DUAL_MODE.rps
  [ 395.217202] ven_rsi_91x: 

  Kernel version: 4.4.0-98-generic
  Kernel snap: caracalla-kernel version:4.4.0-98.121-1 revision:58
  BIOS version: 01.00.05 (Also tested with 01.00.03)
  Tested SKU: T, Media, GPA

  The reproduce steps:
  1. Enable Wowlan and Wol in BIOS
  2. Boot up Ubuntu core
  3. Connect to Wifi AP
  $ nmcli d wifi connect  password 
  4. Enable wowlan
  $ sudo iw phy phy0 wowlan enable magic-packet
  5. Enter suspend or hibernate
  $ sudo systemctl suspend
  or
  $ sudo systemctl hibernate
  6. Send wake signal from another machine
  # wakeonlan 
  or
  # sudo etherwake 
  7. If system not waked, try to wol or other wake source
  

[Kernel-packages] [Bug 1742094] Re: [16.04][classic] Redpine: wowlan feature doesn't work

[Shrirang Bagul]

** Summary changed:

- [16.04][classic] wowlan feature doesn't work
+ [16.04][classic] Redpine: wowlan feature doesn't work

** Description changed:

  Steps to reproduce:
  
-  1. Ensure WoWLAN is enabled in BIOS.
-  2. Initiate connection to an AP (using nmcli)
-  3. Configure the device for WoWLAN, run the command:
- $ sudo iw phy phy0 wowlan enable magic-packet
-  4. Enter S5/S4/S3 (using poweroff, etc.)
-  5. From another computer on the same network run the following command:
- $ wakeonlan {mac} (in my case `wakeonlan 00:23:a7:ec:b4:04`)
+  1. Ensure WoWLAN is enabled in BIOS.
+  2. Initiate connection to an AP (using nmcli)
+  3. Configure the device for WoWLAN, run the command:
+ $ sudo iw phy phy0 wowlan enable magic-packet
+  4. Enter S5/S4/S3 (using poweroff, etc.)
+  5. From another computer on the same network run the following command:
+ $ wakeonlan {mac} (in my case `wakeonlan 00:23:a7:ec:b4:04`)
  
  Expected result: the device starts/resume
+ 
+ This bug is only for tracking purporse, please do not triage.

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

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

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

Title:
  [16.04][classic] Redpine: wowlan feature doesn't work

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

Bug description:
  Steps to reproduce:

   1. Ensure WoWLAN is enabled in BIOS.
   2. Initiate connection to an AP (using nmcli)
   3. Configure the device for WoWLAN, run the command:
  $ sudo iw phy phy0 wowlan enable magic-packet
   4. Enter S5/S4/S3 (using poweroff, etc.)
   5. From another computer on the same network run the following command:
  $ wakeonlan {mac} (in my case `wakeonlan 00:23:a7:ec:b4:04`)

  Expected result: the device starts/resume

  This bug is only for tracking purporse, please do not triage.

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

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

[Kernel-packages] [Bug 1736317] Re: ath10k: enhance rf signal strength

[Shrirang Bagul]

** Description changed:

  ath10k: add max_tx_power for QCA6174 WLAN.RM.2.0 firmware
  QCA6174 WLAN.RM.2.0 firmware uses max_tx_power instead of using max_reg_power
  to set transmission power. The tx power was about -50dbm, after applying this
  change, it become -32dbm.
  
  Signed-off-by: Alan Liu 
  Signed-off-by: Kalle Valo 
  
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/ath/ath10k?id=513527c87a7feab2a5b31db07e5b07864d3c08f7
  
- Fix already applied to Zesty/Artful/Bionic kernels.
+ This fix already included in Zesty/Artful/Bionic kernels.
  
  This bug is for tracking purposes only, please do not triage.

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

Title:
  ath10k: enhance rf signal strength

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

Bug description:
  ath10k: add max_tx_power for QCA6174 WLAN.RM.2.0 firmware
  QCA6174 WLAN.RM.2.0 firmware uses max_tx_power instead of using max_reg_power
  to set transmission power. The tx power was about -50dbm, after applying this
  change, it become -32dbm.

  Signed-off-by: Alan Liu 
  Signed-off-by: Kalle Valo 

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/ath/ath10k?id=513527c87a7feab2a5b31db07e5b07864d3c08f7

  This fix already included in Zesty/Artful/Bionic kernels.

  This bug is for tracking purposes only, please do not triage.

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

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