[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

** Also affects: oem-priority/trusty
   Importance: Undecided
   Status: New

** Also affects: oem-priority/wily
   Importance: Undecided
   Status: New

** Changed in: oem-priority/wily
   Status: New => Fix Released

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

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in OEM Priority Project wily series:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in debian-installer source package in Trusty:
  New
Status in linux source package in Trusty:
  Fix Committed
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in debian-installer source package in Vivid:
  New
Status in linux source package in Vivid:
  Fix Committed
Status in debian-installer source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * The users can not use netboot.iso to install Ubuntu on eMMC
  storage.

  [Test Case]

   * Download netboot.iso of trusty/utopic/vivid from 
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-amd64/current/images/
   * Use netboot.iso to burn an installation CD/DVD or make an installation USB 
stick.
   * Use this installation media on a platform with eMMC storage to install 
Ubuntu system.

  [Regression Potential]

   * None

  [Other Info]

   * None

  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

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

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

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

This issue also needs to update the debian-installer in
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-
amd64/current/images/ or we can not verify it.

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

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in OEM Priority Project wily series:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in debian-installer source package in Trusty:
  New
Status in linux source package in Trusty:
  Fix Committed
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in debian-installer source package in Vivid:
  New
Status in linux source package in Vivid:
  Fix Committed
Status in debian-installer source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * The users can not use netboot.iso to install Ubuntu on eMMC
  storage.

  [Test Case]

   * Download netboot.iso of trusty/utopic/vivid from 
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-amd64/current/images/
   * Use netboot.iso to burn an installation CD/DVD or make an installation USB 
stick.
   * Use this installation media on a platform with eMMC storage to install 
Ubuntu system.

  [Regression Potential]

   * None

  [Other Info]

   * None

  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

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

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

[Kernel-packages] [Bug 1381625] Re: Adjust brightness to lowest value caused screen whole black

[Shih-Yuan Lee]

** Bug watch added: GNOME Bug Tracker #744278
   https://bugzilla.gnome.org/show_bug.cgi?id=744278

** Also affects: unity-settings-daemon via
   https://bugzilla.gnome.org/show_bug.cgi?id=744278
   Importance: Unknown
   Status: Unknown

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

Title:
  Adjust brightness to lowest value caused screen whole black

Status in HWE Next:
  Confirmed
Status in Unity Settings Daemon:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  When adjusting screen brightness to lowest value, it turns screen
  backlight off.

  [Test Case]

  1. Install Image
  2. Press System's brightness hotkey to adjust the brightness level to the 
lowest or
  3. Go to System "Settings" -> "Brightness & Lock" to adjust brightness level 
to the lowest
  4. Check if the screen display still has backlight

  Expected results: There is still screen backlight

  Actual results: Sceen backlight is turned off

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

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

[Kernel-packages] [Bug 1381625] Re: Adjust brightness to lowest value caused screen whole black

[Shih-Yuan Lee]

This bug probably targets on how to avoid this driver behavior's change.

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

Title:
  Adjust brightness to lowest value caused screen whole black

Status in HWE Next:
  Confirmed
Status in Unity Settings Daemon:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Won't Fix

Bug description:
  [Impact]

  When adjusting screen brightness to lowest value, it turns screen
  backlight off.

  [Test Case]

  1. Install Image
  2. Press System's brightness hotkey to adjust the brightness level to the 
lowest or
  3. Go to System "Settings" -> "Brightness & Lock" to adjust brightness level 
to the lowest
  4. Check if the screen display still has backlight

  Expected results: There is still screen backlight

  Actual results: Sceen backlight is turned off

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

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

[Kernel-packages] [Bug 1381625] Re: Adjust brightness to lowest value caused screen whole black

[Shih-Yuan Lee]

Since Linux kernel v3.18-rc1, it contains

commit e6755fb78e8f20ecadf2a4080084121336624ad9
Author: Jani Nikula 
Date:   Tue Aug 12 17:11:42 2014 +0300

drm/i915: switch off backlight for backlight class 0 brightness

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

Title:
  Adjust brightness to lowest value caused screen whole black

Status in HWE Next:
  Confirmed
Status in Unity Settings Daemon:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Won't Fix

Bug description:
  [Impact]

  When adjusting screen brightness to lowest value, it turns screen
  backlight off.

  [Test Case]

  1. Install Image
  2. Press System's brightness hotkey to adjust the brightness level to the 
lowest or
  3. Go to System "Settings" -> "Brightness & Lock" to adjust brightness level 
to the lowest
  4. Check if the screen display still has backlight

  Expected results: There is still screen backlight

  Actual results: Sceen backlight is turned off

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

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

[Kernel-packages] [Bug 1381625] Re: Adjust brightness to lowest value caused screen whole black

[Shih-Yuan Lee]

Reverting that commit can easily fix this issue or we need to fix all
userspace programs related to the brightness control.

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

Title:
  Adjust brightness to lowest value caused screen whole black

Status in HWE Next:
  Confirmed
Status in Unity Settings Daemon:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Won't Fix

Bug description:
  [Impact]

  When adjusting screen brightness to lowest value, it turns screen
  backlight off.

  [Test Case]

  1. Install Image
  2. Press System's brightness hotkey to adjust the brightness level to the 
lowest or
  3. Go to System "Settings" -> "Brightness & Lock" to adjust brightness level 
to the lowest
  4. Check if the screen display still has backlight

  Expected results: There is still screen backlight

  Actual results: Sceen backlight is turned off

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

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

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

** Changed in: oem-priority/trusty
   Status: Fix Committed => Fix Released

** Changed in: oem-priority
   Status: Fix Committed => Fix Released

** Changed in: debian-installer (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project trusty series:
  Fix Released
Status in OEM Priority Project wily series:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in debian-installer source package in Trusty:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in debian-installer source package in Vivid:
  New
Status in linux source package in Vivid:
  Fix Released
Status in debian-installer source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * The users can not use netboot.iso to install Ubuntu on eMMC
  storage.

  [Test Case]

   * Download netboot.iso of trusty/utopic/vivid from 
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-amd64/current/images/
   * Use netboot.iso to burn an installation CD/DVD or make an installation USB 
stick.
   * Use this installation media on a platform with eMMC storage to install 
Ubuntu system.

  [Regression Potential]

   * None

  [Other Info]

   * None

  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

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

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

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

I didn't use any preseed config. I just download the mini.iso and make an 
installation USB stick by it.
Then I plug the USB stick into a laptop that only has an eMMC system storage 
inside to do the installation test manually.
During the installation, I will connect to Internet to download other udeb 
packages and this is the usual usage for mini.iso.

http://archive.ubuntu.com/ubuntu/dists/wily-proposed/main/installer-
amd64/current/images/netboot/mini.iso works and /proc/version_signature
shows "Ubuntu 4.2.0-16.19-generic 4.2.3".

http://archive.ubuntu.com/ubuntu/dists/vivid-proposed/main/installer-
amd64/current/images/netboot/mini.iso doesn't work and
/proc/version_signature shows "Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6".

http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-
amd64/current/images/vivid-netboot/mini.iso works and
/proc/version_signature shows "Ubuntu 3.19.0-32.37~14.04.1-generic
3.19.8-ckt7".

http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-
amd64/current/images/utopic-netboot/mini.iso doesn't work and
/proc/version_signature shows "Ubuntu 3.16.0-52.71~14.04.1-generic
3.16.7-ckt8".

http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-
amd64/current/images/netboot/mini.iso works and /proc/version_signature
shows "Ubuntu 3.13.0-67.110-generic 3.13.11-ckt27".

It is expected that "Ubuntu 3.13.0-67.110-generic 3.13.11-ckt27",
"Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7" and "Ubuntu
4.2.0-16.19-generic 4.2.3" work and "Ubuntu 3.19.0-30.33-generic
3.19.8-ckt6" doesn't work.

It is not expected that "Ubuntu 3.16.0-52.71~14.04.1-generic
3.16.7-ckt8" doesn't work but we don't maintain utopic now so it is
probably OK.

The only problem left now is that http://archive.ubuntu.com/ubuntu/dists
/vivid-proposed/main/installer-amd64/current/images/netboot/mini.iso is
not up to date.

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

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project trusty series:
  Fix Released
Status in OEM Priority Project wily series:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in debian-installer source package in Trusty:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in debian-installer source package in Vivid:
  New
Status in linux source package in Vivid:
  Fix Released
Status in debian-installer source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * The users can not use netboot.iso to install Ubuntu on eMMC
  storage.

  [Test Case]

   * Download netboot.iso of trusty/utopic/vivid from 
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-amd64/current/images/
   * Use netboot.iso to burn an installation CD/DVD or make an installation USB 
stick.
   * Use this installation media on a platform with eMMC storage to install 
Ubuntu system.

  [Regression Potential]

   * None

  [Other Info]

   * None

  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

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

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

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

** Changed in: debian-installer (Ubuntu Trusty)
   Status: New => Fix Released

** Changed in: oem-priority/trusty
   Status: In Progress => Fix Released

** Changed in: debian-installer (Ubuntu Trusty)
   Status: Fix Released => Fix Committed

** Changed in: oem-priority/trusty
   Status: Fix Released => Fix Committed

** Changed in: oem-priority
   Status: In Progress => Fix Committed

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

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in OEM Priority Project:
  Fix Committed
Status in OEM Priority Project trusty series:
  Fix Committed
Status in OEM Priority Project wily series:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in debian-installer source package in Trusty:
  Fix Committed
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in debian-installer source package in Vivid:
  New
Status in linux source package in Vivid:
  Fix Released
Status in debian-installer source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * The users can not use netboot.iso to install Ubuntu on eMMC
  storage.

  [Test Case]

   * Download netboot.iso of trusty/utopic/vivid from 
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-amd64/current/images/
   * Use netboot.iso to burn an installation CD/DVD or make an installation USB 
stick.
   * Use this installation media on a platform with eMMC storage to install 
Ubuntu system.

  [Regression Potential]

   * None

  [Other Info]

   * None

  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

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

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

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

http://archive.ubuntu.com/ubuntu/dists/trusty-updates/main/installer-
amd64/current/images/vivid-netboot/mini.iso works and
/proc/version_signature shows "Ubuntu 3.19.0-32.37~14.04.1-generic
3.19.8-ckt7".

http://archive.ubuntu.com/ubuntu/dists/trusty-updates/main/installer-
amd64/current/images/netboot/mini.iso works and /proc/version_signature
shows "Ubuntu 3.13.0-67.110-generic 3.13.11-ckt27".

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

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project trusty series:
  Fix Released
Status in OEM Priority Project wily series:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in debian-installer source package in Trusty:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in debian-installer source package in Vivid:
  New
Status in linux source package in Vivid:
  Fix Released
Status in debian-installer source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * The users can not use netboot.iso to install Ubuntu on eMMC
  storage.

  [Test Case]

   * Download netboot.iso of trusty/utopic/vivid from 
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-amd64/current/images/
   * Use netboot.iso to burn an installation CD/DVD or make an installation USB 
stick.
   * Use this installation media on a platform with eMMC storage to install 
Ubuntu system.

  [Regression Potential]

   * None

  [Other Info]

   * None

  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

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

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

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

** Changed in: oem-priority/trusty
   Status: New => Fix Released

** Changed in: oem-priority/trusty
   Status: Fix Released => In Progress

** Changed in: oem-priority
   Status: New => In Progress

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

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project trusty series:
  In Progress
Status in OEM Priority Project wily series:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in debian-installer source package in Trusty:
  New
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in debian-installer source package in Vivid:
  New
Status in linux source package in Vivid:
  Fix Released
Status in debian-installer source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * The users can not use netboot.iso to install Ubuntu on eMMC
  storage.

  [Test Case]

   * Download netboot.iso of trusty/utopic/vivid from 
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-amd64/current/images/
   * Use netboot.iso to burn an installation CD/DVD or make an installation USB 
stick.
   * Use this installation media on a platform with eMMC storage to install 
Ubuntu system.

  [Regression Potential]

   * None

  [Other Info]

   * None

  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

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

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

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

Could you help to update the debian-installer netboot images, such as
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-
amd64/current/images/vivid-netboot/mini.iso and
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-
amd64/current/images/netboot/mini.iso so I can verify this issue?

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

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in OEM Priority Project wily series:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in debian-installer source package in Trusty:
  New
Status in linux source package in Trusty:
  Fix Committed
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in debian-installer source package in Vivid:
  New
Status in linux source package in Vivid:
  Fix Committed
Status in debian-installer source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * The users can not use netboot.iso to install Ubuntu on eMMC
  storage.

  [Test Case]

   * Download netboot.iso of trusty/utopic/vivid from 
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-amd64/current/images/
   * Use netboot.iso to burn an installation CD/DVD or make an installation USB 
stick.
   * Use this installation media on a platform with eMMC storage to install 
Ubuntu system.

  [Regression Potential]

   * None

  [Other Info]

   * None

  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

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

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

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

** Description changed:

  [Impact]
  
-  * The users can not use netboot.iso to install Ubuntu on eMMC storage.
+  * The users can not use netboot.iso to install Ubuntu on eMMC storage.
  
  [Test Case]
  
-  * Download netboot.iso from 
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-amd64/current/images/
-  * Use netboot.iso to burn an installation CD/DVD or make an installation USB 
stick.
-  * Use this installation media on a platform with eMMC storage to install 
Ubuntu system.
+  * Download netboot.iso of trusty/utopic/vivid from 
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-amd64/current/images/
+  * Use netboot.iso to burn an installation CD/DVD or make an installation USB 
stick.
+  * Use this installation media on a platform with eMMC storage to install 
Ubuntu system.
  
  [Regression Potential]
  
-  * None
+  * None
  
  [Other Info]
-  
-  * None
+ 
+  * None
  
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

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

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in debian-installer source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * The users can not use netboot.iso to install Ubuntu on eMMC
  storage.

  [Test Case]

   * Download netboot.iso of trusty/utopic/vivid from 
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-amd64/current/images/
   * Use netboot.iso to burn an installation CD/DVD or make an installation USB 
stick.
   * Use this installation media on a platform with eMMC storage to install 
Ubuntu system.

  [Regression Potential]

   * None

  [Other Info]

   * None

  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1502772/+subscriptions

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

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

** Description changed:

+ [Impact]
+ 
+  * The users can not use netboot.iso to install Ubuntu on eMMC storage.
+ 
+ [Test Case]
+ 
+  * Download netboot.iso from 
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-amd64/current/images/
+  * Use netboot.iso to burn an installation CD/DVD or make an installation USB 
stick.
+  * Use this installation media on a platform with eMMC storage to install 
Ubuntu system.
+ 
+ [Regression Potential]
+ 
+  * None
+ 
+ [Other Info]
+  
+  * None
+ 
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

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

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in debian-installer source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * The users can not use netboot.iso to install Ubuntu on eMMC
  storage.

  [Test Case]

   * Download netboot.iso from 
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-amd64/current/images/
   * Use netboot.iso to burn an installation CD/DVD or make an installation USB 
stick.
   * Use this installation media on a platform with eMMC storage to install 
Ubuntu system.

  [Regression Potential]

   * None

  [Other Info]
   
   * None

  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1502772/+subscriptions

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

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

** Changed in: debian-installer (Ubuntu Wily)
   Status: New => Fix Released

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

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in debian-installer source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1502772/+subscriptions

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

[Kernel-packages] [Bug 1502772] [NEW] Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

Public bug reported:

Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

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

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in linux package in Ubuntu:
  New

Bug description:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

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

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

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

** Also affects: debian-installer (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/1502772

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in debian-installer package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1502772/+subscriptions

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

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

This issue also affects trusty.

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

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in debian-installer package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in debian-installer source package in Wily:
  New
Status in linux source package in Wily:
  Fix Committed

Bug description:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1502772/+subscriptions

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

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

** Tags added: trusty vivid wily

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

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in debian-installer package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in debian-installer source package in Wily:
  New
Status in linux source package in Wily:
  Fix Committed

Bug description:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1502772/+subscriptions

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

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

** Tags removed: verification-done-vivid
** Tags added: verification-failed-vivid

** Tags added: verification-done-wily

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

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project trusty series:
  Fix Released
Status in OEM Priority Project wily series:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in debian-installer source package in Trusty:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in debian-installer source package in Vivid:
  New
Status in linux source package in Vivid:
  Fix Released
Status in debian-installer source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * The users can not use netboot.iso to install Ubuntu on eMMC
  storage.

  [Test Case]

   * Download netboot.iso of trusty/utopic/vivid from 
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-amd64/current/images/
   * Use netboot.iso to burn an installation CD/DVD or make an installation USB 
stick.
   * Use this installation media on a platform with eMMC storage to install 
Ubuntu system.

  [Regression Potential]

   * None

  [Other Info]

   * None

  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

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

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

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

** No longer affects: debian-installer (Ubuntu Vivid)

** Tags removed: verification-failed-vivid vivid

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

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project trusty series:
  Fix Released
Status in OEM Priority Project wily series:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in debian-installer source package in Trusty:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in debian-installer source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * The users can not use netboot.iso to install Ubuntu on eMMC
  storage.

  [Test Case]

   * Download netboot.iso of trusty/utopic/vivid from 
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-amd64/current/images/
   * Use netboot.iso to burn an installation CD/DVD or make an installation USB 
stick.
   * Use this installation media on a platform with eMMC storage to install 
Ubuntu system.

  [Regression Potential]

   * None

  [Other Info]

   * None

  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

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

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

[Kernel-packages] [Bug 1559870] Re: mmc_select_hs400 failed, error -74

[Shih-Yuan Lee]

commit 1815e61b1a7efe81017a883e817292daf7d2f922
Author: Adrian Hunter 
Date:   Wed Oct 28 14:25:40 2015 +0200

mmc: mmc: Improve reliability of mmc_select_hs200()
   
Currently mmc_select_hs200() uses __mmc_switch() which checks the
success of the switch to HS200 mode using CMD13 (SEND_STATUS).
The problem is that it does that using the timing settings of legacy
mode.  That is prone to error, not least because the timing parameters
for legacy mode are tighter than the timing parameters for HS200 mode.
   
In the case when CMD13 polling is used (i.e. not MMC_CAP_WAIT_WHILE_BUSY)
with the switch command, it must be assumed that using different modes on
the card and host must work.
   
However in the case when CMD13 polling is not used
(i.e. MMC_CAP_WAIT_WHILE_BUSY) mmc_select_hs200() can be made more
reliable by setting the host to the correct timing before sending CMD13.
   
This patch does that.
   
A complication is that the caller, mmc_select_timing(), will ignore a
switch error (indicated by -EBADMSG), assume the old mode is valid
and continue, so the old timing must be restored in that case.
   
Signed-off-by: Adrian Hunter 
Cc:  # 4.2+
Tested-by: Alim Akhtar 
Signed-off-by: Ulf Hansson 

commit 51b12f7764fa8bb464cbd0f7bbd3a408d21ade16
Author: Adrian Hunter 
Date:   Wed Oct 28 14:25:41 2015 +0200

mmc: mmc: Fix HS setting in mmc_select_hs400()
   
mmc_select_hs400() begins with the card and host in HS200 mode.
Therefore, any commands sent to the card should use HS200 timing.
It is incorrect to set the host to High Speed (HS) timing before
sending the switch command.  Doing so is unreliable because
the timing parameters for HS mode are tighter than the timing
parameters for HS200 mode.  Thus the HS timings should be set
only after the card has switched mode.
   
However, it is not unreasonable first to reduce the frequency to
the HS mode frequency, which should make the switch command and
subsequent CMD13 commands more reliable.
   
This patch does that.
   
Signed-off-by: Adrian Hunter 
Cc:  # 4.2+
Tested-by: Alim Akhtar 
Signed-off-by: Ulf Hansson 

commit 974007aaf240aa195b31c34cfdb013524a2dcfca
Author: Adrian Hunter 
Date:   Wed Oct 28 14:25:42 2015 +0200

mmc: mmc: Move mmc_switch_status()
   
Move the mmc_switch_status() function in preparation for calling it
in mmc_select_hs400().
   
Signed-off-by: Adrian Hunter 
Cc:  # 4.2+
Tested-by: Alim Akhtar 
Signed-off-by: Ulf Hansson 

commit d23029332c3d51fb5ac117ba5cde4dc0a3ec3fa6
Author: Adrian Hunter 
Date:   Wed Oct 28 14:25:43 2015 +0200

mmc: mmc: Improve reliability of mmc_select_hs400()
   
mmc_select_hs400() calls __mmc_switch() which checks the switch is
successful using CMD13 (SEND_STATUS).  The problem is that it does that
using the timing settings of the previous mode.  That is prone to error,
especially when switching from HS to HS400 because the timing parameters
for HS mode are tighter than the timing parameters for HS400 mode.
   
In the case when CMD13 polling is used (i.e. not MMC_CAP_WAIT_WHILE_BUSY)
with the switch command, it must be assumed that using different modes on
the card and host must work.
   
However in the case when CMD13 polling is not used
(i.e. MMC_CAP_WAIT_WHILE_BUSY) mmc_select_hs400() can be made more
reliable by setting the host to the correct timing before sending CMD13.
   
This patch does that.
   
Signed-off-by: Adrian Hunter 
Cc:  # 4.2+
Tested-by: Alim Akhtar 
Signed-off-by: Ulf Hansson 

commit 1ca896856281d3f1ad4f6f7d4e32e2943452de23
Author: Adrian Hunter 
Date:   Thu Nov 26 14:00:45 2015 +0200

mmc: sdhci-pci: Do not default to 33 Ohm driver strength for Intel SPT
   
In some cases, the stronger 33 Ohm driver strength must not be used
so it is not a suitable default.  Change it to the standard default
50 Ohm value.
   
The patch applies to v4.2+ except the file name changed.  It is
drivers/mmc/host/sdhci-pci.c prior to v.4.4.
   
Signed-off-by: Adrian Hunter 
Cc: sta...@vger.kernel.org # v4.2+
Signed-off-by: Ulf Hansson 

commit adb24d42a516bca8b9741ed21206509daaab5b13
Author: Wenkai Du 
Date:   Thu Nov 26 14:00:44 2015 +0200

mmc: mmc: Fix incorrect 

[Kernel-packages] [Bug 1559870] [NEW] mmc_select_hs400 failed, error -74

[Shih-Yuan Lee]

Public bug reported:

I used "Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)" from 
http://cdimage.ubuntu.com/daily-live/current/.
But it can not find the built-in eMMC storage and it shows the following 
messages.

[   12.355182] sdhci-pci :00:1e.4: No vmmc regulator found
[   12.355185] sdhci-pci :00:1e.4: No vqmmc regulator found
[   12.358331] mmc0: SDHCI controller on PCI [:00:1e.4] using ADMA 64-bit
[   12.359549] sdhci-pci :00:1e.6: No vmmc regulator found
[   12.359552] sdhci-pci :00:1e.6: No vqmmc regulator found
[   12.362713] mmc1: SDHCI controller on PCI [:00:1e.6] using ADMA 64-bit
[   12.472768] mmc0: MAN_BKOPS_EN bit is not set
[   12.489132] mmc0: mmc_select_hs400 failed, error -74
[   12.489134] mmc0: error -74 whilst initialising MMC card
[   12.601333] mmc0: MAN_BKOPS_EN bit is not set
[   12.617263] mmc0: mmc_select_hs400 failed, error -74
[   12.617280] mmc0: error -74 whilst initialising MMC card
[   12.745957] mmc0: MAN_BKOPS_EN bit is not set
[   12.764502] mmc0: mmc_select_hs400 failed, error -74
[   12.764519] mmc0: error -74 whilst initialising MMC card
[   12.923969] mmc0: MAN_BKOPS_EN bit is not set
[   12.948561] mmc0: mmc_select_hs400 failed, error -74
[   12.948580] mmc0: error -74 whilst initialising MMC card

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-10-generic 4.4.0-10.25
ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
Uname: Linux 4.4.0-10-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CasperVersion: 1.367
CurrentDesktop: Unity
Date: Mon Mar 21 06:20:39 2016
LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.board.name: STCK2MV64CC
dmi.product.name: STCK2MV64CC

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


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

Title:
  mmc_select_hs400 failed, error -74

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I used "Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)" from 
http://cdimage.ubuntu.com/daily-live/current/.
  But it can not find the built-in eMMC storage and it shows the following 
messages.

  [   12.355182] sdhci-pci :00:1e.4: No vmmc regulator found
  [   12.355185] sdhci-pci :00:1e.4: No vqmmc regulator found
  [   12.358331] mmc0: SDHCI controller on PCI [:00:1e.4] using ADMA 64-bit
  [   12.359549] sdhci-pci :00:1e.6: No vmmc regulator found
  [   12.359552] sdhci-pci :00:1e.6: No vqmmc regulator found
  [   12.362713] mmc1: SDHCI controller on PCI [:00:1e.6] using ADMA 64-bit
  [   12.472768] mmc0: MAN_BKOPS_EN bit is not set
  [   12.489132] mmc0: mmc_select_hs400 failed, error -74
  [   12.489134] mmc0: error -74 whilst initialising MMC card
  [   12.601333] mmc0: MAN_BKOPS_EN bit is not set
  [   12.617263] mmc0: mmc_select_hs400 failed, error -74
  [   12.617280] mmc0: error -74 whilst initialising MMC card
  [   12.745957] mmc0: MAN_BKOPS_EN bit is not set
  [   12.764502] mmc0: mmc_select_hs400 failed, error -74
  [   12.764519] mmc0: error -74 whilst initialising MMC card
  [   12.923969] mmc0: MAN_BKOPS_EN bit is not set
  [   12.948561] mmc0: mmc_select_hs400 failed, error -74
  [   12.948580] mmc0: error -74 whilst initialising MMC card

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.367
  CurrentDesktop: Unity
  Date: Mon Mar 21 06:20:39 2016
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.board.name: STCK2MV64CC
  dmi.product.name: STCK2MV64CC

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

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

[Kernel-packages] [Bug 1559870] Re: mmc_select_hs400 failed, error -74

[Shih-Yuan Lee]

The patches in comment #3 can be found in the v4.5 kernel.

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

Title:
  mmc_select_hs400 failed, error -74

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I used "Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)" from 
http://cdimage.ubuntu.com/daily-live/current/.
  But it can not find the built-in eMMC storage and it shows the following 
messages.

  [   12.355182] sdhci-pci :00:1e.4: No vmmc regulator found
  [   12.355185] sdhci-pci :00:1e.4: No vqmmc regulator found
  [   12.358331] mmc0: SDHCI controller on PCI [:00:1e.4] using ADMA 64-bit
  [   12.359549] sdhci-pci :00:1e.6: No vmmc regulator found
  [   12.359552] sdhci-pci :00:1e.6: No vqmmc regulator found
  [   12.362713] mmc1: SDHCI controller on PCI [:00:1e.6] using ADMA 64-bit
  [   12.472768] mmc0: MAN_BKOPS_EN bit is not set
  [   12.489132] mmc0: mmc_select_hs400 failed, error -74
  [   12.489134] mmc0: error -74 whilst initialising MMC card
  [   12.601333] mmc0: MAN_BKOPS_EN bit is not set
  [   12.617263] mmc0: mmc_select_hs400 failed, error -74
  [   12.617280] mmc0: error -74 whilst initialising MMC card
  [   12.745957] mmc0: MAN_BKOPS_EN bit is not set
  [   12.764502] mmc0: mmc_select_hs400 failed, error -74
  [   12.764519] mmc0: error -74 whilst initialising MMC card
  [   12.923969] mmc0: MAN_BKOPS_EN bit is not set
  [   12.948561] mmc0: mmc_select_hs400 failed, error -74
  [   12.948580] mmc0: error -74 whilst initialising MMC card

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.367
  CurrentDesktop: Unity
  Date: Mon Mar 21 06:20:39 2016
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.board.name: STCK2MV64CC
  dmi.product.name: STCK2MV64CC

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

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

[Kernel-packages] [Bug 1559870] Re: mmc_select_hs400 failed, error -74

[Shih-Yuan Lee]

These patches are mentioned in an email thread by Adrian Hunter (one of the 
primary maintainers of the MMC module in the kernel).
I will do some check for these patches.
Before I confirm which patches are needed, I set this issue incomplete 
temporarily.
This issue was reported also existed in Ubuntu 15.10, however I tested the 
mainline kernel v4.5 and it works fine.

** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1559870

Title:
  mmc_select_hs400 failed, error -74

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I used "Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)" from 
http://cdimage.ubuntu.com/daily-live/current/.
  But it can not find the built-in eMMC storage and it shows the following 
messages.

  [   12.355182] sdhci-pci :00:1e.4: No vmmc regulator found
  [   12.355185] sdhci-pci :00:1e.4: No vqmmc regulator found
  [   12.358331] mmc0: SDHCI controller on PCI [:00:1e.4] using ADMA 64-bit
  [   12.359549] sdhci-pci :00:1e.6: No vmmc regulator found
  [   12.359552] sdhci-pci :00:1e.6: No vqmmc regulator found
  [   12.362713] mmc1: SDHCI controller on PCI [:00:1e.6] using ADMA 64-bit
  [   12.472768] mmc0: MAN_BKOPS_EN bit is not set
  [   12.489132] mmc0: mmc_select_hs400 failed, error -74
  [   12.489134] mmc0: error -74 whilst initialising MMC card
  [   12.601333] mmc0: MAN_BKOPS_EN bit is not set
  [   12.617263] mmc0: mmc_select_hs400 failed, error -74
  [   12.617280] mmc0: error -74 whilst initialising MMC card
  [   12.745957] mmc0: MAN_BKOPS_EN bit is not set
  [   12.764502] mmc0: mmc_select_hs400 failed, error -74
  [   12.764519] mmc0: error -74 whilst initialising MMC card
  [   12.923969] mmc0: MAN_BKOPS_EN bit is not set
  [   12.948561] mmc0: mmc_select_hs400 failed, error -74
  [   12.948580] mmc0: error -74 whilst initialising MMC card

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.367
  CurrentDesktop: Unity
  Date: Mon Mar 21 06:20:39 2016
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.board.name: STCK2MV64CC
  dmi.product.name: STCK2MV64CC

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

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

[Kernel-packages] [Bug 1559870] Re: mmc_select_hs400 failed, error -74

[Shih-Yuan Lee]

I tested Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) and there is 
no problem now.
3efcd738cff03d2d579e08f55117111d *ubuntu-16.04-beta2-desktop-amd64.iso

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1559870

Title:
  mmc_select_hs400 failed, error -74

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I used "Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)" from 
http://cdimage.ubuntu.com/daily-live/current/.
  But it can not find the built-in eMMC storage and it shows the following 
messages.

  [   12.355182] sdhci-pci :00:1e.4: No vmmc regulator found
  [   12.355185] sdhci-pci :00:1e.4: No vqmmc regulator found
  [   12.358331] mmc0: SDHCI controller on PCI [:00:1e.4] using ADMA 64-bit
  [   12.359549] sdhci-pci :00:1e.6: No vmmc regulator found
  [   12.359552] sdhci-pci :00:1e.6: No vqmmc regulator found
  [   12.362713] mmc1: SDHCI controller on PCI [:00:1e.6] using ADMA 64-bit
  [   12.472768] mmc0: MAN_BKOPS_EN bit is not set
  [   12.489132] mmc0: mmc_select_hs400 failed, error -74
  [   12.489134] mmc0: error -74 whilst initialising MMC card
  [   12.601333] mmc0: MAN_BKOPS_EN bit is not set
  [   12.617263] mmc0: mmc_select_hs400 failed, error -74
  [   12.617280] mmc0: error -74 whilst initialising MMC card
  [   12.745957] mmc0: MAN_BKOPS_EN bit is not set
  [   12.764502] mmc0: mmc_select_hs400 failed, error -74
  [   12.764519] mmc0: error -74 whilst initialising MMC card
  [   12.923969] mmc0: MAN_BKOPS_EN bit is not set
  [   12.948561] mmc0: mmc_select_hs400 failed, error -74
  [   12.948580] mmc0: error -74 whilst initialising MMC card

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.367
  CurrentDesktop: Unity
  Date: Mon Mar 21 06:20:39 2016
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.board.name: STCK2MV64CC
  dmi.product.name: STCK2MV64CC

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

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

[Kernel-packages] [Bug 1625932] Re: Backlight does not change when adjust it higher than 50% after S3

[Shih-Yuan Lee]

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

Title:
  Backlight does not change when adjust it higher than 50% after S3

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

Bug description:
  Backlight does not change when adjust it higher than 50% after S3

  Steps:
  1. Install ubuntu 16.04 and boot into OS
  2. suspend system
  3. resume system from S3
  4. Try to adjust brightness level

  Expected results: Backlight should be changed when adjust it

  Actual results: Backlight does not change when adjust it higher than
  50% after S3

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

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

[Kernel-packages] [Bug 1676747] Re: Enable lspcon on i915

[Shih-Yuan Lee]

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

Title:
  Enable lspcon on i915

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

Bug description:
  Some new machine comes with both HDMI and DP (not DP over TB), in this
  case, lspcon support is required to make HDMI work.

  The patch series cover letter has  more information:
  https://patchwork.freedesktop.org/series/4756/

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

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

[Kernel-packages] [Bug 1705633] Re: [8087:0a2b] Failed to load bluetooth firmware(might affect some other Intel bt devices)

[Shih-Yuan Lee]

4.4.0-93.116 can fix the Bluetooth firmware loading issue for 8087:0a2b.

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

Title:
  [8087:0a2b] Failed to load bluetooth firmware(might affect some other
  Intel bt devices)

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

Bug description:
  [Impact]
  After this linux-firmware bug[1] update the firmware files, it removes 
intel/ibt-11-16.{ddc,sfi} and add intel/ibt-12-16.{ddc,sfi}, but in btusb 
driver, it hardcoded the hw_variant as 11. So we got this kind of error after 
the linux-firmware package updated and lost the bt functions.

  [5.516003] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [5.516181] bluetooth hci0: Direct firmware load for intel/ibt-11-16.sfi 
failed with error -2
  [5.516183] Bluetooth: hci0: Failed to load Intel firmware file (-2)

  [Fix]
  This patch uses a hw_variant variable to replace the hardcoded 11.

  [Test Case]
  Verified on the machine has this issue, and confirm this patch works.

  [Regression Potential]
  The hw_variant variable has shown up since kernel 3.10 in this commit
 dffd30e Bluetooth: Add support for Intel Bluetooth device [8087:07dc]
  So, we don't have to worry about old chips don't contains this info, since it 
exists
  and be used for a very long time.

  1. https://bugs.launchpad.net/ubuntu/+source/linux-
  firmware/+bug/1686815

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

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

[Kernel-packages] [Bug 1702685] Re: No wifi connectivity with kernel 4.4.0-83 if ath9k-msi dkms is installed

[Shih-Yuan Lee]

** Changed in: oem-priority
   Status: In Progress => Fix Committed

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

Title:
  No wifi connectivity with kernel 4.4.0-83 if ath9k-msi dkms is
  installed

Status in OEM Priority Project:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have wifi connectivity with the previous kernel if I choose it from
  the GRUB screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-83-generic 4.4.0-83.106
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vasa1  2000 F pulseaudio
  CRDA:
   country IN: DFS-JP
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5170 - 5250 @ 80), (N/A, 20), (N/A)
(5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 20), (N/A)
  CurrentDesktop: Unity
  Date: Thu Jul  6 18:21:07 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  HibernationDevice: RESUME=UUID=087adc85-f179-4429-9373-e2227f37cb9a
  InstallationDate: Installed on 2017-01-02 (185 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Inspiron 15-3567
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic.efi.signed 
root=UUID=30e6bdd2-27bf-4ef2-8076-333d24f18336 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-83-generic N/A
   linux-backports-modules-4.4.0-83-generic  N/A
   linux-firmware1.157.11
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.07.00
  dmi.board.name: 0FGN4M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.07.00:bd04/07/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0FGN4M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 15-3567
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1699651] Re: KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device

[Shih-Yuan Lee]

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

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

Title:
  KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  Steps:
  1. Install Ubuntu 16.04
  2. Search BT 4.0 devices

  Expected results: KILLER1435-S BT can search BT 4.0 devide normally

  Actual results: KILLER1435-S BT cannot search BT 4.0 devide

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

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

[Kernel-packages] [Bug 1699651] Re: KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device

[Shih-Yuan Lee]

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

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

Title:
  KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  Steps:
  1. Install Ubuntu 16.04
  2. Search BT 4.0 devices

  Expected results: KILLER1435-S BT can search BT 4.0 devide normally

  Actual results: KILLER1435-S BT cannot search BT 4.0 devide

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

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

[Kernel-packages] [Bug 1699651] Re: KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device

[Shih-Yuan Lee]

I have verified the kernels from {xenial, yakkety, zesty,
artful}-proposed and they do fix the problem.

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

Title:
  KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  Steps:
  1. Install Ubuntu 16.04
  2. Search BT 4.0 devices

  Expected results: KILLER1435-S BT can search BT 4.0 devide normally

  Actual results: KILLER1435-S BT cannot search BT 4.0 devide

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

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

[Kernel-packages] [Bug 1699651] Re: KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device

[Shih-Yuan Lee]

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

Title:
  KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  Steps:
  1. Install Ubuntu 16.04
  2. Search BT 4.0 devices

  Expected results: KILLER1435-S BT can search BT 4.0 devide normally

  Actual results: KILLER1435-S BT cannot search BT 4.0 devide

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

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

[Kernel-packages] [Bug 1702685] Re: No wifi connectivity with kernel 4.4.0-83 if ath9k-msi dkms is installed

[Shih-Yuan Lee]

** Changed in: oem-priority
   Status: Confirmed => In Progress

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

Title:
  No wifi connectivity with kernel 4.4.0-83 if ath9k-msi dkms is
  installed

Status in OEM Priority Project:
  In Progress
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have wifi connectivity with the previous kernel if I choose it from
  the GRUB screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-83-generic 4.4.0-83.106
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vasa1  2000 F pulseaudio
  CRDA:
   country IN: DFS-JP
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5170 - 5250 @ 80), (N/A, 20), (N/A)
(5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 20), (N/A)
  CurrentDesktop: Unity
  Date: Thu Jul  6 18:21:07 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  HibernationDevice: RESUME=UUID=087adc85-f179-4429-9373-e2227f37cb9a
  InstallationDate: Installed on 2017-01-02 (185 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Inspiron 15-3567
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic.efi.signed 
root=UUID=30e6bdd2-27bf-4ef2-8076-333d24f18336 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-83-generic N/A
   linux-backports-modules-4.4.0-83-generic  N/A
   linux-firmware1.157.11
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.07.00
  dmi.board.name: 0FGN4M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.07.00:bd04/07/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0FGN4M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 15-3567
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1762385] Re: dell_wmi: Unknown key codes

[Shih-Yuan Lee]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Tags added: oem-bug-1769562

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

Title:
  dell_wmi: Unknown key codes

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Cosmic:
  New

Bug description:
  [Impact]

   * Bogus keycode messages produced by the kernel / user annoyance
   * rfkill keyboard shortcuts not working as intended on some Dell machines

  [Test Case]

   * check that there are no spurious kernel messages about unknown keys
  in journalctl upon RFKill key presses

   * check that RFKill key presses work correctly and kill/restore RF
  capabilities

  [Regression Potential]

   * The change is scoped to particular SKUs and thus should only affect them
   * It is related to matching gsd support, which is in-place on xenial and up

  [Solution]
  Cherrypick upstream commit 
https://github.com/systemd/systemd/commit/cab01e9ecf1c69656785e64f5fc94cd4ed09e57f

  [Original Bug report]

  RFKill key produces these messages in kernel log:

  dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed

  This key code is a notification and should be added as KEY_IGNORE
  here:
  https://github.com/torvalds/linux/blob/master/drivers/platform/x86
  /dell-wmi.c#L263

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmig   2737 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 18:09:03 2018
  InstallationDate: Installed on 2018-03-27 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  MachineType: Dell Inc. Inspiron 5379
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic 
root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   linux-backports-modules-4.15.0-15-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 0C6J64
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5379
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1763748] Re: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50

[Shih-Yuan Lee]

Some steps to install the kernel on
https://people.canonical.com/~khfeng/lp1763748-rtl/.

1. Download all Debian packages from
https://people.canonical.com/~khfeng/lp1763748-rtl/

2. Open a GNOME Terminal by Ctrl+Alt+t.

3. Execute the following command in GNOME terminal to check if all
Debian packages are already here to install.

$ ls -l ~/Download/
total 64428
-rw-rw-r-- 1 sylee sylee  1147000 May 11 13:34 
linux-headers-4.15.0-22-generic_4.15.0-22.23_amd64.deb
-rw-rw-r-- 1 sylee sylee 11028116 May 11 13:35 
linux-headers-4.15.0-22_4.15.0-22.23_all.deb
-rw-rw-r-- 1 sylee sylee  7953156 May 11 13:35 
linux-image-unsigned-4.15.0-22-generic_4.15.0-22.23_amd64.deb
-rw-rw-r-- 1 sylee sylee 12978460 May 11 13:35 
linux-modules-4.15.0-22-generic_4.15.0-22.23_amd64.deb
-rw-rw-r-- 1 sylee sylee 32836820 May 11 13:36 
linux-modules-extra-4.15.0-22-generic_4.15.0-22.23_amd64.deb

4. Execute the following command in GNOME terminal to install the kernel

$ sudo dpkg -i Download/linux*.deb

5. Reboot the system to use the new kernel.

P.S. If you want to remove the testing kernel, just execute `sudo apt
purge linux-headers-4.15.0-22 linux-headers-4.15.0-22-generic linux-
image-unsigned-4.15.0-22-generic linux-modules-4.15.0-22-generic linux-
modules-extra-4.15.0-22-generic`.

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

Title:
  Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working
  in DELL XPS 13 9370 with firmware 1.50

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The webcam is detected by the system, but no applications detect it.

  sudo lsusb -v: (relevant part)
  Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp.
  Device Descriptor:
    bLength18
    bDescriptorType 1
    bcdUSB   2.01
    bDeviceClass  239 Miscellaneous Device
    bDeviceSubClass 2 ?
    bDeviceProtocol 1 Interface Association
    bMaxPacketSize064
    idVendor   0x0bda Realtek Semiconductor Corp.
    idProduct  0x58f4
    bcdDevice   72.79
    iManufacturer   3 CN0FFMHCLOG0081SB0M1A01
    iProduct1 Integrated_Webcam_HD
    iSerial 2 200901010001

  In syslog (firmware can be seen in first line - 1.50):
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.126546] uvcvideo: Found UVC 1.50 
device Integrated_Webcam_HD (0bda:58f4)
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.126908] usbcore: registered new 
interface driver btusb
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127128] uvcvideo: UVC non 
compliance - GET_DEF(PROBE) not supported. Enabling workaround.
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127462] uvcvideo: Failed to query 
(129) UVC probe control : -75 (exp. 34).
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127464] uvcvideo: Failed to 
initialize the device (-5).
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.128061] uvcvideo: Unknown video 
format 0032-0002-0010-8000-00aa00389b71
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.128065] uvcvideo: Found UVC 1.50 
device Integrated_Webcam_HD (0bda:58f4)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: 
boot/vmlinuz-4.15.0-13-generic]
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wgarcia2145 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Apr 13 16:59:02 2018
  HibernationDevice: RESUME=UUID=a6f64150-e0a5-4c6b-9097-b8f98b14bdcc
  InstallationDate: Installed on 2018-04-09 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408)
  MachineType: Dell Inc. XPS 13 9370
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=226e4127-5c15-4a18-8062-74ba83b57515 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1760106] Re: FFe: Enable configuring resume offset via sysfs

[Shih-Yuan Lee]

** Also affects: oem-priority
   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/1760106

Title:
  FFe: Enable configuring resume offset via sysfs

Status in OEM Priority Project:
  New
Status in klibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Committed
Status in klibc source package in Bionic:
  New
Status in linux source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in klibc source package in Cosmic:
  New
Status in linux source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * Cannot hibernate & resume from a swapfile

  [Test Case]

   * Create or enlarge swapfile to be big enough for hibernation
   * Attempt to hibernate and resume

  [Regression Potential]

   * Hibernation is not reliable technology in itself, and multiple
  things may cause failure to resume. Thus it is sufficient to validate
  this bug after swapfile is attempted for hibernation and the disk
  offset kernel parameter is modified. Irrespective if actual suspending
  or resume were successful or not.

  [Other Info]
   
   * Original bug report

  In 4.17 a new attribute is introduced to configure the hibernation
  resume offset. Since Ubuntu enables a swapfile by default this
  attribute is important to be able to make hibernation work "out of the
  box".

  The patch in the kernel is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next=355064675f1c997cea017ea64c8f2c216e5425d9

  Systemd support for adopting this change is available here:
  https://github.com/systemd/systemd/pull/8406
  As of 3/30/18 it's not yet been merged however.

  Klibc support for adopting this change is available here:
  https://www.zytor.com/pipermail/klibc/2018-March/003986.html

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

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

[Kernel-packages] [Bug 1732056] Re: Touchpad stops working after a few seconds in Lenovo ideapad 320

[Shih-Yuan Lee]

Ubuntu 17.04 is not supported since January 13, 2018.
Please check https://wiki.ubuntu.com/Releases for "End of Life date".

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

Title:
  Touchpad stops working after a few seconds in Lenovo ideapad 320

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed

Bug description:
  === SRU Justifications ===

  [Impact]
  Touchpad freezes after a brief usage.

  [Fix]
  Quote from the commit log:
  "The stale cached value written at the final stage undoes the masking.
  Fix this by re-reading the register before clearing the interrupt.

  I also spotted that the interrupt-clearing code can race against
  amd_gpio_irq_mask() / amd_gpio_irq_unmask(), so add locking there.
  Presumably this race was leading to the loss of interrupts."

  [Test Case]
  Touchpad no longer freezes on ideapad 320-15ABR, a new Dell Latitude and
  a new Dell Inspiron.

  [Regression Potential]
  Low. It limits to AMD laptops

  === Original Bug Report ===

  I have installed ubuntu bionic on a Lenovo ideapad 320. The touchpad
  stops working a few seconds after I log in.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rebeca 1440 F pulseaudio
   /dev/snd/controlC0:  rebeca 1440 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 13 20:03:41 2017
  InstallationDate: Installed on 2017-09-22 (53 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918)
  MachineType: LENOVO 80XS
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=1e55f665-bd98-4113-9ae8-ec766bfc424f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-11-14 (0 days ago)
  dmi.bios.date: 05/22/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5QCN16WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15ABR
  dmi.modalias: 
dmi:bvnLENOVO:bvr5QCN16WW:bd05/22/2017:svnLENOVO:pn80XS:pvrLenovoideapad320-15ABR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15ABR:
  dmi.product.family: ideapad 320-15ABR
  dmi.product.name: 80XS
  dmi.product.version: Lenovo ideapad 320-15ABR
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1800413] [NEW] It can not use nvidia-settings to switch from the power saving mode to the performance mode

[Shih-Yuan Lee]

Public bug reported:

I try to use nvidia-settings 410.73-0ubuntu0~gpu18.04.1 in 
ppa:graphics-drivers/ppa to switch from the power saving mode to the 
performance mode on Ubuntu 18.04.
But it failed.

$ nvidia-settings

ERROR: NVIDIA driver is not loaded

ERROR: Unable to load info from any available system

However `prime-select nvidia` still works fine.

Private Bug: https://bugs.launchpad.net/bugs/1800081

** Affects: nvidia-drivers-ubuntu
 Importance: Undecided
 Status: Confirmed

** Affects: oem-priority
 Importance: Undecided
 Status: Confirmed

** Affects: nvidia-settings (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: bionic somerville

** Also affects: nvidia-drivers-ubuntu
   Importance: Undecided
   Status: New

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Tags added: bionic somerville

** Description changed:

  I try to use nvidia-settings 410.73-0ubuntu0~gpu18.04.1 in 
ppa:graphics-drivers/ppa to switch from the power saving mode to the 
performance mode on Ubuntu 18.04.
  But it failed.
  
  $ nvidia-settings
  
  ERROR: NVIDIA driver is not loaded
  
  ERROR: Unable to load info from any available system
  
  However `prime-select nvidia` still works fine.
+ 
+ Private Bug: https://bugs.launchpad.net/bugs/1800081

** Changed in: nvidia-drivers-ubuntu
   Status: New => Confirmed

** Changed in: oem-priority
   Status: New => Confirmed

** Changed in: nvidia-settings (Ubuntu)
   Status: New => Confirmed

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

Title:
  It can not use nvidia-settings to switch from the power saving mode to
  the performance mode

Status in NVIDIA Drivers Ubuntu:
  Confirmed
Status in OEM Priority Project:
  Confirmed
Status in nvidia-settings package in Ubuntu:
  Confirmed

Bug description:
  I try to use nvidia-settings 410.73-0ubuntu0~gpu18.04.1 in 
ppa:graphics-drivers/ppa to switch from the power saving mode to the 
performance mode on Ubuntu 18.04.
  But it failed.

  $ nvidia-settings

  ERROR: NVIDIA driver is not loaded

  ERROR: Unable to load info from any available system

  However `prime-select nvidia` still works fine.

  Private Bug: https://bugs.launchpad.net/bugs/1800081

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1800413/+subscriptions

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

[Kernel-packages] [Bug 1800413] Re: It can not use nvidia-settings to switch from the power saving mode to the performance mode

[Shih-Yuan Lee]

** Description changed:

  I try to use nvidia-settings 410.73-0ubuntu0~gpu18.04.1 in 
ppa:graphics-drivers/ppa to switch from the power saving mode to the 
performance mode on Ubuntu 18.04.
  But it failed.
  
+ 
  $ nvidia-settings
  
  ERROR: NVIDIA driver is not loaded
  
  ERROR: Unable to load info from any available system
+ 
  
  However `prime-select nvidia` still works fine.
  
  Private Bug: https://bugs.launchpad.net/bugs/1800081

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

Title:
  It can not use nvidia-settings to switch from the power saving mode to
  the performance mode

Status in NVIDIA Drivers Ubuntu:
  Confirmed
Status in OEM Priority Project:
  Confirmed
Status in nvidia-settings package in Ubuntu:
  Confirmed

Bug description:
  I try to use nvidia-settings 410.73-0ubuntu0~gpu18.04.1 in 
ppa:graphics-drivers/ppa to switch from the power saving mode to the 
performance mode on Ubuntu 18.04.
  But it failed.

  
  $ nvidia-settings

  ERROR: NVIDIA driver is not loaded

  ERROR: Unable to load info from any available system
  

  However `prime-select nvidia` still works fine.

  Private Bug: https://bugs.launchpad.net/bugs/1800081

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1800413/+subscriptions

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

[Kernel-packages] [Bug 1800413] Re: It can not use nvidia-settings to switch from the power saving mode to the performance mode

[Shih-Yuan Lee]

** Description changed:

  I try to use nvidia-settings 410.73-0ubuntu0~gpu18.04.1 in 
ppa:graphics-drivers/ppa to switch from the power saving mode to the 
performance mode on Ubuntu 18.04.
  But it failed.
  
  
  $ nvidia-settings
  
  ERROR: NVIDIA driver is not loaded
  
  ERROR: Unable to load info from any available system
  
  
- However `prime-select nvidia` still works fine.
+ However `prime-select nvidia` still works fine and there is no such
+ issue by nvidia-settings 390.77-0ubuntu0.18.04.1 in bionic-updates.
  
  Private Bug: https://bugs.launchpad.net/bugs/1800081

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

Title:
  It can not use nvidia-settings to switch from the power saving mode to
  the performance mode

Status in NVIDIA Drivers Ubuntu:
  Confirmed
Status in OEM Priority Project:
  Confirmed
Status in nvidia-settings package in Ubuntu:
  Confirmed

Bug description:
  I try to use nvidia-settings 410.73-0ubuntu0~gpu18.04.1 in 
ppa:graphics-drivers/ppa to switch from the power saving mode to the 
performance mode on Ubuntu 18.04.
  But it failed.

  
  $ nvidia-settings

  ERROR: NVIDIA driver is not loaded

  ERROR: Unable to load info from any available system
  

  However `prime-select nvidia` still works fine and there is no such
  issue by nvidia-settings 390.77-0ubuntu0.18.04.1 in bionic-updates.

  Private Bug: https://bugs.launchpad.net/bugs/1800081

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1800413/+subscriptions

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

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

[Shih-Yuan Lee]

I have verified the kernel on the 2386:4B33 i2c touchscreen and it does
fix the problem.

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

Title:
  Fix I2C touchpanels' interrupt storms after system suspend

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1822715] Re: Need a meta package to add necessary X stack support for Intel ICL to Bionic

[Shih-Yuan Lee]

** Summary changed:

- Need a meta package to add necessary X stack support for Intel ICL to Bionic 
Edit
+ Need a meta package to add necessary X stack support for Intel ICL to 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/1822715

Title:
  Need a meta package to add necessary X stack support for Intel ICL to
  Bionic

Status in linux-oem package in Ubuntu:
  Invalid

Bug description:
  - In preparation of the 18.04osp1 base image, we need to a meta
  package that adds necessary X stack support for Intel ICL to Bionic

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

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

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

[Shih-Yuan Lee]

apport information

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

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

Title:
  BT advertising packet wakes up the system from S3 and suspend-to-idle

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A generic issue which happens on Intel BT(8087:0aaa) and Atheros 
BT(0cf3:e005)(0cf3:e007).
  Once the system has paired with BT4 devices(disconnected), the system will be 
waken up randomly from S3/s2idle while receiving advertising packet from any 
random BT4 devices in the environment which are even not paired/connected.

  By removing all previously paired BT4 devices(disconnected) from BT
  menu can fix this issue.

  The advertising packet could be none connectable undirected or
  connectable undirected.

  And the BT4 devices we found can reproduce this issue are
  1. Microsoft Surface 1678
  2. Logitech K375s
  3. Microsoft Designer Mouse
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1539 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-08-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 0bda:5658 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 3300
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-8-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.181
  Tags:  eoan
  Uname: Linux 5.2.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/07/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0FN010
  dmi.board.vendor: Dell Inc.
  dmi.board.version: D02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd05/07/2019:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn0FN010:rvrD02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3300
  dmi.product.sku: 08BB
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1839124] Re: BT advertising packet wakes up the system from S3 and suspend-to-idle

[Shih-Yuan Lee]

apport information

** Tags added: originate-from-1798023 somerville

** Tags added: apport-collected eoan

** Description changed:

  A generic issue which happens on Intel BT(8087:0aaa) and Atheros 
BT(0cf3:e005)(0cf3:e007).
  Once the system has paired with BT4 devices(disconnected), the system will be 
waken up randomly from S3/s2idle while receiving advertising packet from any 
random BT4 devices in the environment which are even not paired/connected.
  
  By removing all previously paired BT4 devices(disconnected) from BT menu
  can fix this issue.
  
  The advertising packet could be none connectable undirected or
  connectable undirected.
  
  And the BT4 devices we found can reproduce this issue are
  1. Microsoft Surface 1678
  2. Logitech K375s
  3. Microsoft Designer Mouse
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu7
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  u  1539 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 19.10
+ InstallationDate: Installed on 2019-08-06 (0 days ago)
+ InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications 
+  Bus 001 Device 002: ID 0bda:5658 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: Dell Inc. Latitude 3300
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-8-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
+ RelatedPackageVersions:
+  linux-restricted-modules-5.2.0-8-generic N/A
+  linux-backports-modules-5.2.0-8-generic  N/A
+  linux-firmware   1.181
+ Tags:  eoan
+ Uname: Linux 5.2.0-8-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 05/07/2019
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 1.4.0
+ dmi.board.name: 0FN010
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: D02
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd05/07/2019:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn0FN010:rvrD02:cvnDellInc.:ct10:cvr:
+ dmi.product.family: Latitude
+ dmi.product.name: Latitude 3300
+ dmi.product.sku: 08BB
+ dmi.sys.vendor: Dell Inc.

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

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

Title:
  BT advertising packet wakes up the system from S3 and suspend-to-idle

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A generic issue which happens on Intel BT(8087:0aaa) and Atheros 
BT(0cf3:e005)(0cf3:e007).
  Once the system has paired with BT4 devices(disconnected), the system will be 
waken up randomly from S3/s2idle while receiving advertising packet from any 
random BT4 devices in the environment which are even not paired/connected.

  By removing all previously paired BT4 devices(disconnected) from BT
  menu can fix this issue.

  The advertising packet could be none connectable undirected or
  connectable undirected.

  And the BT4 devices we found can reproduce this issue are
  1. Microsoft Surface 1678
  2. Logitech K375s
  3. Microsoft Designer Mouse
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1539 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-08-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 0bda:5658 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 3300
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-8-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   

[Kernel-packages] [Bug 1839124] IwConfig.txt

[Shih-Yuan Lee]

apport information

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

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

Title:
  BT advertising packet wakes up the system from S3 and suspend-to-idle

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A generic issue which happens on Intel BT(8087:0aaa) and Atheros 
BT(0cf3:e005)(0cf3:e007).
  Once the system has paired with BT4 devices(disconnected), the system will be 
waken up randomly from S3/s2idle while receiving advertising packet from any 
random BT4 devices in the environment which are even not paired/connected.

  By removing all previously paired BT4 devices(disconnected) from BT
  menu can fix this issue.

  The advertising packet could be none connectable undirected or
  connectable undirected.

  And the BT4 devices we found can reproduce this issue are
  1. Microsoft Surface 1678
  2. Logitech K375s
  3. Microsoft Designer Mouse
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1539 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-08-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 0bda:5658 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 3300
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-8-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.181
  Tags:  eoan
  Uname: Linux 5.2.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/07/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0FN010
  dmi.board.vendor: Dell Inc.
  dmi.board.version: D02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd05/07/2019:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn0FN010:rvrD02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3300
  dmi.product.sku: 08BB
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1839124] CRDA.txt

[Shih-Yuan Lee]

apport information

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

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

Title:
  BT advertising packet wakes up the system from S3 and suspend-to-idle

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A generic issue which happens on Intel BT(8087:0aaa) and Atheros 
BT(0cf3:e005)(0cf3:e007).
  Once the system has paired with BT4 devices(disconnected), the system will be 
waken up randomly from S3/s2idle while receiving advertising packet from any 
random BT4 devices in the environment which are even not paired/connected.

  By removing all previously paired BT4 devices(disconnected) from BT
  menu can fix this issue.

  The advertising packet could be none connectable undirected or
  connectable undirected.

  And the BT4 devices we found can reproduce this issue are
  1. Microsoft Surface 1678
  2. Logitech K375s
  3. Microsoft Designer Mouse
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1539 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-08-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 0bda:5658 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 3300
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-8-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.181
  Tags:  eoan
  Uname: Linux 5.2.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/07/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0FN010
  dmi.board.vendor: Dell Inc.
  dmi.board.version: D02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd05/07/2019:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn0FN010:rvrD02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3300
  dmi.product.sku: 08BB
  dmi.sys.vendor: Dell Inc.

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

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

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

[Shih-Yuan Lee]

apport information

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

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

Title:
  BT advertising packet wakes up the system from S3 and suspend-to-idle

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A generic issue which happens on Intel BT(8087:0aaa) and Atheros 
BT(0cf3:e005)(0cf3:e007).
  Once the system has paired with BT4 devices(disconnected), the system will be 
waken up randomly from S3/s2idle while receiving advertising packet from any 
random BT4 devices in the environment which are even not paired/connected.

  By removing all previously paired BT4 devices(disconnected) from BT
  menu can fix this issue.

  The advertising packet could be none connectable undirected or
  connectable undirected.

  And the BT4 devices we found can reproduce this issue are
  1. Microsoft Surface 1678
  2. Logitech K375s
  3. Microsoft Designer Mouse
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1539 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-08-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 0bda:5658 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 3300
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-8-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.181
  Tags:  eoan
  Uname: Linux 5.2.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/07/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0FN010
  dmi.board.vendor: Dell Inc.
  dmi.board.version: D02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd05/07/2019:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn0FN010:rvrD02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3300
  dmi.product.sku: 08BB
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1839124] PulseList.txt

[Shih-Yuan Lee]

apport information

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

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

Title:
  BT advertising packet wakes up the system from S3 and suspend-to-idle

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A generic issue which happens on Intel BT(8087:0aaa) and Atheros 
BT(0cf3:e005)(0cf3:e007).
  Once the system has paired with BT4 devices(disconnected), the system will be 
waken up randomly from S3/s2idle while receiving advertising packet from any 
random BT4 devices in the environment which are even not paired/connected.

  By removing all previously paired BT4 devices(disconnected) from BT
  menu can fix this issue.

  The advertising packet could be none connectable undirected or
  connectable undirected.

  And the BT4 devices we found can reproduce this issue are
  1. Microsoft Surface 1678
  2. Logitech K375s
  3. Microsoft Designer Mouse
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1539 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-08-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 0bda:5658 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 3300
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-8-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.181
  Tags:  eoan
  Uname: Linux 5.2.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/07/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0FN010
  dmi.board.vendor: Dell Inc.
  dmi.board.version: D02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd05/07/2019:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn0FN010:rvrD02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3300
  dmi.product.sku: 08BB
  dmi.sys.vendor: Dell Inc.

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

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

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

[Shih-Yuan Lee]

apport information

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

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

Title:
  BT advertising packet wakes up the system from S3 and suspend-to-idle

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A generic issue which happens on Intel BT(8087:0aaa) and Atheros 
BT(0cf3:e005)(0cf3:e007).
  Once the system has paired with BT4 devices(disconnected), the system will be 
waken up randomly from S3/s2idle while receiving advertising packet from any 
random BT4 devices in the environment which are even not paired/connected.

  By removing all previously paired BT4 devices(disconnected) from BT
  menu can fix this issue.

  The advertising packet could be none connectable undirected or
  connectable undirected.

  And the BT4 devices we found can reproduce this issue are
  1. Microsoft Surface 1678
  2. Logitech K375s
  3. Microsoft Designer Mouse
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1539 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-08-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 0bda:5658 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 3300
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-8-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.181
  Tags:  eoan
  Uname: Linux 5.2.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/07/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0FN010
  dmi.board.vendor: Dell Inc.
  dmi.board.version: D02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd05/07/2019:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn0FN010:rvrD02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3300
  dmi.product.sku: 08BB
  dmi.sys.vendor: Dell Inc.

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

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

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

[Shih-Yuan Lee]

apport information

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

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

Title:
  BT advertising packet wakes up the system from S3 and suspend-to-idle

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A generic issue which happens on Intel BT(8087:0aaa) and Atheros 
BT(0cf3:e005)(0cf3:e007).
  Once the system has paired with BT4 devices(disconnected), the system will be 
waken up randomly from S3/s2idle while receiving advertising packet from any 
random BT4 devices in the environment which are even not paired/connected.

  By removing all previously paired BT4 devices(disconnected) from BT
  menu can fix this issue.

  The advertising packet could be none connectable undirected or
  connectable undirected.

  And the BT4 devices we found can reproduce this issue are
  1. Microsoft Surface 1678
  2. Logitech K375s
  3. Microsoft Designer Mouse
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1539 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-08-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 0bda:5658 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 3300
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-8-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.181
  Tags:  eoan
  Uname: Linux 5.2.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/07/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0FN010
  dmi.board.vendor: Dell Inc.
  dmi.board.version: D02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd05/07/2019:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn0FN010:rvrD02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3300
  dmi.product.sku: 08BB
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1839124] RfKill.txt

[Shih-Yuan Lee]

apport information

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

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

Title:
  BT advertising packet wakes up the system from S3 and suspend-to-idle

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A generic issue which happens on Intel BT(8087:0aaa) and Atheros 
BT(0cf3:e005)(0cf3:e007).
  Once the system has paired with BT4 devices(disconnected), the system will be 
waken up randomly from S3/s2idle while receiving advertising packet from any 
random BT4 devices in the environment which are even not paired/connected.

  By removing all previously paired BT4 devices(disconnected) from BT
  menu can fix this issue.

  The advertising packet could be none connectable undirected or
  connectable undirected.

  And the BT4 devices we found can reproduce this issue are
  1. Microsoft Surface 1678
  2. Logitech K375s
  3. Microsoft Designer Mouse
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1539 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-08-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 0bda:5658 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 3300
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-8-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.181
  Tags:  eoan
  Uname: Linux 5.2.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/07/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0FN010
  dmi.board.vendor: Dell Inc.
  dmi.board.version: D02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd05/07/2019:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn0FN010:rvrD02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3300
  dmi.product.sku: 08BB
  dmi.sys.vendor: Dell Inc.

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

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

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

[Shih-Yuan Lee]

apport information

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

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

Title:
  BT advertising packet wakes up the system from S3 and suspend-to-idle

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A generic issue which happens on Intel BT(8087:0aaa) and Atheros 
BT(0cf3:e005)(0cf3:e007).
  Once the system has paired with BT4 devices(disconnected), the system will be 
waken up randomly from S3/s2idle while receiving advertising packet from any 
random BT4 devices in the environment which are even not paired/connected.

  By removing all previously paired BT4 devices(disconnected) from BT
  menu can fix this issue.

  The advertising packet could be none connectable undirected or
  connectable undirected.

  And the BT4 devices we found can reproduce this issue are
  1. Microsoft Surface 1678
  2. Logitech K375s
  3. Microsoft Designer Mouse
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1539 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-08-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 0bda:5658 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 3300
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-8-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.181
  Tags:  eoan
  Uname: Linux 5.2.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/07/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0FN010
  dmi.board.vendor: Dell Inc.
  dmi.board.version: D02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd05/07/2019:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn0FN010:rvrD02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3300
  dmi.product.sku: 08BB
  dmi.sys.vendor: Dell Inc.

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

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

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

[Shih-Yuan Lee]

apport information

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

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

Title:
  BT advertising packet wakes up the system from S3 and suspend-to-idle

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A generic issue which happens on Intel BT(8087:0aaa) and Atheros 
BT(0cf3:e005)(0cf3:e007).
  Once the system has paired with BT4 devices(disconnected), the system will be 
waken up randomly from S3/s2idle while receiving advertising packet from any 
random BT4 devices in the environment which are even not paired/connected.

  By removing all previously paired BT4 devices(disconnected) from BT
  menu can fix this issue.

  The advertising packet could be none connectable undirected or
  connectable undirected.

  And the BT4 devices we found can reproduce this issue are
  1. Microsoft Surface 1678
  2. Logitech K375s
  3. Microsoft Designer Mouse
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1539 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-08-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 0bda:5658 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 3300
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-8-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.181
  Tags:  eoan
  Uname: Linux 5.2.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/07/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0FN010
  dmi.board.vendor: Dell Inc.
  dmi.board.version: D02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd05/07/2019:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn0FN010:rvrD02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3300
  dmi.product.sku: 08BB
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1839124] ProcCpuinfo.txt

[Shih-Yuan Lee]

apport information

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

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

Title:
  BT advertising packet wakes up the system from S3 and suspend-to-idle

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A generic issue which happens on Intel BT(8087:0aaa) and Atheros 
BT(0cf3:e005)(0cf3:e007).
  Once the system has paired with BT4 devices(disconnected), the system will be 
waken up randomly from S3/s2idle while receiving advertising packet from any 
random BT4 devices in the environment which are even not paired/connected.

  By removing all previously paired BT4 devices(disconnected) from BT
  menu can fix this issue.

  The advertising packet could be none connectable undirected or
  connectable undirected.

  And the BT4 devices we found can reproduce this issue are
  1. Microsoft Surface 1678
  2. Logitech K375s
  3. Microsoft Designer Mouse
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1539 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-08-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 0bda:5658 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 3300
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-8-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.181
  Tags:  eoan
  Uname: Linux 5.2.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/07/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0FN010
  dmi.board.vendor: Dell Inc.
  dmi.board.version: D02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd05/07/2019:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn0FN010:rvrD02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3300
  dmi.product.sku: 08BB
  dmi.sys.vendor: Dell Inc.

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

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

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

[Shih-Yuan Lee]

apport information

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

** Changed in: oem-priority
   Status: New => Triaged

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

** Changed in: oem-priority
 Assignee: (unassigned) => Shih-Yuan Lee (fourdollars)

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

Title:
  BT advertising packet wakes up the system from S3 and suspend-to-idle

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A generic issue which happens on Intel BT(8087:0aaa) and Atheros 
BT(0cf3:e005)(0cf3:e007).
  Once the system has paired with BT4 devices(disconnected), the system will be 
waken up randomly from S3/s2idle while receiving advertising packet from any 
random BT4 devices in the environment which are even not paired/connected.

  By removing all previously paired BT4 devices(disconnected) from BT
  menu can fix this issue.

  The advertising packet could be none connectable undirected or
  connectable undirected.

  And the BT4 devices we found can reproduce this issue are
  1. Microsoft Surface 1678
  2. Logitech K375s
  3. Microsoft Designer Mouse
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1539 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-08-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 0bda:5658 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 3300
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-8-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.181
  Tags:  eoan
  Uname: Linux 5.2.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/07/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0FN010
  dmi.board.vendor: Dell Inc.
  dmi.board.version: D02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd05/07/2019:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn0FN010:rvrD02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3300
  dmi.product.sku: 08BB
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1839124] [NEW] BT advertising packet wakes up the system from S3 and suspend-to-idle

[Shih-Yuan Lee]

Public bug reported:

A generic issue which happens on Intel BT(8087:0aaa) and Atheros 
BT(0cf3:e005)(0cf3:e007).
Once the system has paired with BT4 devices(disconnected), the system will be 
waken up randomly from S3/s2idle while receiving advertising packet from any 
random BT4 devices in the environment which are even not paired/connected.

By removing all previously paired BT4 devices(disconnected) from BT menu
can fix this issue.

The advertising packet could be none connectable undirected or
connectable undirected.

And the BT4 devices we found can reproduce this issue are
1. Microsoft Surface 1678
2. Logitech K375s
3. Microsoft Designer Mouse
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  u  1539 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2019-08-06 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications 
 Bus 001 Device 002: ID 0bda:5658 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude 3300
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-8-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
RelatedPackageVersions:
 linux-restricted-modules-5.2.0-8-generic N/A
 linux-backports-modules-5.2.0-8-generic  N/A
 linux-firmware   1.181
Tags:  eoan
Uname: Linux 5.2.0-8-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/07/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.0
dmi.board.name: 0FN010
dmi.board.vendor: Dell Inc.
dmi.board.version: D02
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd05/07/2019:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn0FN010:rvrD02:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 3300
dmi.product.sku: 08BB
dmi.sys.vendor: Dell Inc.

** Affects: oem-priority
 Importance: Critical
 Assignee: Shih-Yuan Lee (fourdollars)
 Status: Triaged

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


** Tags: apport-collected eoan originate-from-1798023 somerville

** Attachment added: "btmon.log"
   https://bugs.launchpad.net/bugs/1839124/+attachment/5281154/+files/btmon.log

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Bug watch added: Linux Kernel Bug Tracker #200039
   https://bugzilla.kernel.org/show_bug.cgi?id=200039

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

Title:
  BT advertising packet wakes up the system from S3 and suspend-to-idle

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  A generic issue which happens on Intel BT(8087:0aaa) and Atheros 
BT(0cf3:e005)(0cf3:e007).
  Once the system has paired with BT4 devices(disconnected), the system will be 
waken up randomly from S3/s2idle while receiving advertising packet from any 
random BT4 devices in the environment which are even not paired/connected.

  By removing all previously paired BT4 devices(disconnected) from BT
  menu can fix this issue.

  The advertising packet could be none connectable undirected or
  connectable undirected.

  And the BT4 devices we found can reproduce this issue are
  1. Microsoft Surface 1678
  2. Logitech K375s
  3. Microsoft Designer Mouse
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1539 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-08-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 0bda:5658 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 3300
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdL

[Kernel-packages] [Bug 1839124] Re: BT advertising packet wakes up the system from S3 and suspend-to-idle

[Shih-Yuan Lee]

Upstream bug https://bugzilla.kernel.org/show_bug.cgi?id=200039

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

Title:
  BT advertising packet wakes up the system from S3 and suspend-to-idle

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  A generic issue which happens on Intel BT(8087:0aaa) and Atheros 
BT(0cf3:e005)(0cf3:e007).
  Once the system has paired with BT4 devices(disconnected), the system will be 
waken up randomly from S3/s2idle while receiving advertising packet from any 
random BT4 devices in the environment which are even not paired/connected.

  By removing all previously paired BT4 devices(disconnected) from BT
  menu can fix this issue.

  The advertising packet could be none connectable undirected or
  connectable undirected.

  And the BT4 devices we found can reproduce this issue are
  1. Microsoft Surface 1678
  2. Logitech K375s
  3. Microsoft Designer Mouse
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1539 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-08-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 0bda:5658 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 3300
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-8-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.181
  Tags:  eoan
  Uname: Linux 5.2.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/07/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0FN010
  dmi.board.vendor: Dell Inc.
  dmi.board.version: D02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd05/07/2019:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn0FN010:rvrD02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3300
  dmi.product.sku: 08BB
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1847979] Re: package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed to install/upgrade: trying to overwrite '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is a

[Shih-Yuan Lee]

** Changed in: oem-priority
   Status: In Progress => Fix Released

** Changed in: oem-priority
 Assignee: Shih-Yuan Lee (fourdollars) => (unassigned)

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

Title:
  package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed
  to install/upgrade: trying to overwrite
  '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package
  xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1

Status in OEM Priority Project:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-435 source package in Bionic:
  Fix Released

Bug description:
  There is some problem when upgrading NVIDIA graphics driver from 418
  to 430.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-1024.27-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1024-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Mon Oct 14 04:57:53 2019
  Dependencies:
   gcc-8-base 8.3.0-6ubuntu1~18.04.1
   libc6 2.27-3ubuntu1
   libgcc1 1:8.3.0-6ubuntu1~18.04.1
   libnvidia-cfg1-430 430.26-0ubuntu0.18.04.2
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-worm+X09
  DuplicateSignature:
   package:xserver-xorg-video-nvidia-430:430.26-0ubuntu0.18.04.2
   Unpacking xserver-xorg-video-nvidia-430 (430.26-0ubuntu0.18.04.2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-WH1Eoi/29-xserver-xorg-video-nvidia-430_430.26-0ubuntu0.18.04.2_amd64.deb
 (--unpack):
trying to overwrite '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is 
also in package xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1
  ErrorMessage: trying to overwrite 
'/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package 
xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1
  InstallationDate: Installed on 2019-10-14 (0 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.12
  SourcePackage: nvidia-graphics-drivers-430
  Title: package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed 
to install/upgrade: trying to overwrite 
'/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package 
xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1847979] Re: package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed to install/upgrade: trying to overwrite '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is a

[Shih-Yuan Lee]

I enabled bionic-proposed channel to upgrade the system and there is no
confliction.

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

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

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

Title:
  package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed
  to install/upgrade: trying to overwrite
  '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package
  xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1

Status in OEM Priority Project:
  In Progress
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-430 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-435 source package in Bionic:
  New

Bug description:
  There is some problem when upgrading NVIDIA graphics driver from 418
  to 430.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-1024.27-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1024-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Mon Oct 14 04:57:53 2019
  Dependencies:
   gcc-8-base 8.3.0-6ubuntu1~18.04.1
   libc6 2.27-3ubuntu1
   libgcc1 1:8.3.0-6ubuntu1~18.04.1
   libnvidia-cfg1-430 430.26-0ubuntu0.18.04.2
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-worm+X09
  DuplicateSignature:
   package:xserver-xorg-video-nvidia-430:430.26-0ubuntu0.18.04.2
   Unpacking xserver-xorg-video-nvidia-430 (430.26-0ubuntu0.18.04.2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-WH1Eoi/29-xserver-xorg-video-nvidia-430_430.26-0ubuntu0.18.04.2_amd64.deb
 (--unpack):
trying to overwrite '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is 
also in package xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1
  ErrorMessage: trying to overwrite 
'/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package 
xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1
  InstallationDate: Installed on 2019-10-14 (0 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.12
  SourcePackage: nvidia-graphics-drivers-430
  Title: package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed 
to install/upgrade: trying to overwrite 
'/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package 
xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1848555] Re: Add Intel Comet Lake ethernet support

[Shih-Yuan Lee]

** Tags added: originate-from-1849456

** Also affects: oem-priority
   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/1848555

Title:
  Add Intel Comet Lake ethernet support

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Won't Fix
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Incomplete
Status in linux-oem-osp1 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Incomplete
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix

Bug description:
  [Impact]
  e1000e.ko doesn't load for Intel CML ethernet.

  [Fix]
  Add missing ID for the device.

  [Test]
  The driver loads and works once the ID is added.

  [Regression Potential]
  Minimal. Only adds some IDs, no functional change at all.

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

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

[Kernel-packages] [Bug 1854156] Re: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel

[Shih-Yuan Lee]

find -name *.html | while read manifest; do grep oem-wifi-intel-
iwlwifi-.*-dkms $manifest -H; done | tee ~/oem-wifi-intel-iwlwifi-
dkms.log

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

Title:
  [8086:24f3] intel Corporation Wireless 8260  regression of
  4.4.0-170-generic proposed kernel

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  In Progress

Bug description:
  When connecting bg-open wifi, the system will freeze.

  Hardware: Dell Precision 5720 AIO (CID 201701-25364)
  Kernel: 4.4.0-170-generic #199-Ubuntu SMP Thu Nov 14 01:45:04 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux
  Image: pre-installed image (xenial 4.4 based)

  
  [Steps to Reproduce]
  1. install the target image
  2. when the system is ready, connect to wifi(bg-open channel) over 
network-manager applet.

  [Expected Result]
  Connection established

  [Actual Result]
  System freezed

  [Reproducing Rate]
  100% (5 out of 5)

  [Additional Info]
  I was sometimes able to catch the following kernel oops

  
  Nov 27 18:40:01 201701-25364 kernel: [  600.497340] [ cut here 
]
  Nov 27 18:40:01 201701-25364 kernel: [  600.497345] WARNING: CPU: 0 PID: 30 
at /build/linux-AweC5P/linux-4.4.0/block/blk-mq.c:794 
__blk_mq_run_hw_queue+0x305/0x3a0()
  Nov 27 18:40:01 201701-25364 kernel: [  600.497346] Modules linked in: nvram 
msr rfcomm cmac bnep uvcvideo videobuf2_vmalloc videobuf2_memops btusb 
videobuf2_v4l2 videobuf2_core btrtl v4l2_common btbcm btintel videodev 
bluetooth m
  edia ecdh_generic input_leds joydev hid_multitouch arc4 dell_led 
i2c_designware_platform i2c_designware_core dell_wmi snd_hda_codec_realtek(OE) 
sparse_keymap snd_hda_codec_generic(OE) i915_bpo dcdbas dell_smm_hwmon 
intel_ips drm_k
  ms_helper intel_rapl x86_pkg_temp_thermal iwlmvm(OE) intel_powerclamp 
coretemp drm kvm_intel mac80211(OE) i2c_algo_bit fb_sys_fops syscopyarea kvm 
sysfillrect sysimgblt snd_hda_intel(OE) snd_hda_codec(OE) irqbypass 
snd_hda_core(OE
  ) crct10dif_pclmul crc32_pclmul snd_hwdep ghash_clmulni_intel aesni_intel 
aes_x86_64 lrw snd_pcm gf128mul iwlwifi(OE) glue_helper ablk_helper cryptd 
snd_seq_midi snd_seq_midi_event cfg80211(OE) snd_rawmidi snd_seq serio_raw 
snd_se
  q_device snd_timer rtsx_pci_ms compat(OE) snd memstick idma64 soundcore 
virt_dma mei_me intel_lpss_pci mei shpchp intel_lpss 8250_fintek mac_hid 
acpi_pad parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror 
dm_region_h
  ash dm_log hid_generic usbhid hid mmc_block uas usb_storage rtsx_pci_sdmmc 
psmouse e1000e ptp pps_core rtsx_pci ahci nvme libahci wmi video fjes
  Nov 27 18:40:01 201701-25364 kernel: [  600.497418] CPU: 0 PID: 30 Comm: 
kworker/4:0H Tainted: G   OE   4.4.0-170-generic #199-Ubuntu
  Nov 27 18:40:01 201701-25364 kernel: [  600.497419] Hardware name: Dell Inc. 
Precision 5720 AIO/, BIOS 2.3.6 01/31/2018
  Nov 27 18:40:01 201701-25364 kernel: [  600.497421] Workqueue: kblockd 
blk_mq_run_work_fn
  Nov 27 18:40:01 201701-25364 kernel: [  600.497422]  0286 
3b6f2186023dc8e9 8808394dbd30 8140cde1
  Nov 27 18:40:01 201701-25364 kernel: [  600.497424]   
81d07a88 8808394dbd68 81086492
  Nov 27 18:40:01 201701-25364 kernel: [  600.497425]  880831d52400 
8808394dbda0 88085dd15f80 88085dd1b400
  Nov 27 18:40:01 201701-25364 kernel: [  600.497427] Call Trace:
  Nov 27 18:40:01 201701-25364 kernel: [  600.497430]  [] 
dump_stack+0x63/0x82
  Nov 27 18:40:01 201701-25364 kernel: [  600.497433]  [] 
warn_slowpath_common+0x82/0xc0
  Nov 27 18:40:01 201701-25364 kernel: [  600.497435]  [] 
warn_slowpath_null+0x1a/0x20
  Nov 27 18:40:01 201701-25364 kernel: [  600.497436]  [] 
__blk_mq_run_hw_queue+0x305/0x3a0
  Nov 27 18:40:01 201701-25364 kernel: [  600.497439]  [] ? 
__schedule+0x301/0x810
  Nov 27 18:40:01 201701-25364 kernel: [  600.497440]  [] ? 
__schedule+0x30d/0x810
  Nov 27 18:40:01 201701-25364 kernel: [  600.497441]  [] ? 
__schedule+0x301/0x810
  Nov 27 18:40:01 201701-25364 kernel: [  600.497443]  [] 
blk_mq_run_work_fn+0x12/0x20
  Nov 27 18:40:01 201701-25364 kernel: [  600.497445]  [] 
process_one_work+0x16b/0x4e0
  Nov 27 18:40:01 201701-25364 kernel: [  600.497446]  [] 
worker_thread+0x4e/0x590
  Nov 27 18:40:01 201701-25364 kernel: [  600.497447]  [] ? 
process_one_work+0x4e0/0x4e0
  Nov 27 18:40:01 201701-25364 kernel: [  600.497449]  [] 
kthread+0xe7/0x100
  Nov 27 18:40:01 201701-25364 kernel: [  600.497450]  [] ? 
__schedule+0x301/0x810
  Nov 27 18:40:01 201701-25364 kernel: [  600.497452]  [] ? 
kthread_create_on_node+0x1e0/0x1e0
  Nov 27 18:40:01 201701-25364 kernel: [  600.497454]  [] 
ret_from_fork+0x55/0x80
  Nov 27 18:40:01 201701-25364 kernel: [  600.497456]  [] ? 
kthread_create_on_node+0x1e0/0x1e0
  Nov 27 18:40:01 

[Kernel-packages] [Bug 1862734] Re: Failed to suspend once ever paired with BLE devices: PM: Device 0000:00:14.0 failed to suspend async: error -16

[Shih-Yuan Lee]

I have verified linux-firmware 1.173.16 in bionic-proposed and it does
fix this problem.

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

Title:
  Failed to suspend once ever paired with BLE devices: PM: Device
  :00:14.0 failed to suspend async: error -16

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux-firmware source package in Disco:
  Won't Fix

Bug description:
  [Impact]
  Similar to bug 1858776 and bug 1850738, Intel(R) Wireless-AC 9560 160MHz, 
REV=0x354 [8086:02f0] subsystem [8086:4034] btusb may fail system suspend with 
following error messages in dmesg:

  [4.880979] Bluetooth: hci0: Bootloader revision 0.1 build 0 week 30 2018
  [4.881987] Bluetooth: hci0: Device revision is 2
  [4.881988] Bluetooth: hci0: Secure boot is enabled
  [4.881989] Bluetooth: hci0: OTP lock is enabled
  [4.881990] Bluetooth: hci0: API lock is enabled
  [4.881991] Bluetooth: hci0: Debug lock is disabled
  [4.881992] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [4.883480] Bluetooth: hci0: Found device firmware: intel/ibt-19-0-1.sfi
  ...
  [   71.387652] PM: suspend entry (s2idle)
  [   71.387655] PM: Syncing filesystems ... done.
  [   71.395449] Freezing user space processes ...
  [   71.770699] Bluetooth: hci0: advertising data len corrected
  [   72.330683] (elapsed 0.920 seconds) done.
  [   72.330689] OOM killer disabled.
  [   72.330690] Freezing remaining freezable tasks ... (elapsed 0.014 seconds) 
done.
  [   72.345132] printk: Suspending console(s) (use no_console_suspend to debug)
  [   72.399557] pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16
  [   72.399566] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -16
  [   72.399730] PM: Device :00:14.0 failed to suspend async: error -16
  [   72.425583] PM: Some devices failed to suspend, or early wake event 
detected
  [   72.486631] Bluetooth: hci0: advertising data len corrected
  [   72.611800] OOM killer enabled.
  [   72.611802] Restarting tasks ... done.
  [   72.629308] thermal thermal_zone5: failed to read out thermal zone (-61)
  [   72.663376] PM: suspend exit
  [   72.663413] PM: suspend entry (s2idle)

  This can be fixed by upgrading intel/ibt-19-0-1.sfi to REL0318 from
  upstream commit c0ca980cee32.

  [Test case]
  install the firmware update, check that suspend works

  [Regression potential]
  Firmware is firmware, regressions are possible.

  ---
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.173.14
  ProcVersionSignature: Ubuntu 5.0.0-1037.42-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1037-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1583 F pulseaudio
  Date: Tue Feb 11 02:05:47 2020
  Dependencies:

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-arya+X37
  InstallationDate: Installed on 2020-01-06 (35 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  MachineType: Dell Inc. Latitude 7410
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1037-oem-osp1 
root=UUID=fd4c84f6-205f-4fb2-9225-bb232ba08e38 ro quiet splash vt.handoff=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-1037-oem-osp1 N/A
   linux-backports-modules-5.0.0-1037-oem-osp1  N/A
   linux-firmware   1.173.14
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.4.7
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.4.7:bd12/30/2019:svnDellInc.:pnLatitude7410:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7410
  dmi.product.sku: 09BE
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1862734] Re: Failed to suspend once ever paired with BLE devices: PM: Device 0000:00:14.0 failed to suspend async: error -16

[Shih-Yuan Lee]

** Tags added: originate-from-1858621

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

Title:
  Failed to suspend once ever paired with BLE devices: PM: Device
  :00:14.0 failed to suspend async: error -16

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Bionic:
  In Progress
Status in linux-firmware source package in Disco:
  Won't Fix

Bug description:
  Similar to bug 1858776 and bug 1850738, Intel(R) Wireless-AC 9560
  160MHz, REV=0x354 [8086:02f0] subsystem [8086:4034] btusb may fail
  system suspend with following error messages in dmesg:

  [4.880979] Bluetooth: hci0: Bootloader revision 0.1 build 0 week 30 2018
  [4.881987] Bluetooth: hci0: Device revision is 2
  [4.881988] Bluetooth: hci0: Secure boot is enabled
  [4.881989] Bluetooth: hci0: OTP lock is enabled
  [4.881990] Bluetooth: hci0: API lock is enabled
  [4.881991] Bluetooth: hci0: Debug lock is disabled
  [4.881992] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [4.883480] Bluetooth: hci0: Found device firmware: intel/ibt-19-0-1.sfi
  ...
  [   71.387652] PM: suspend entry (s2idle)
  [   71.387655] PM: Syncing filesystems ... done.
  [   71.395449] Freezing user space processes ... 
  [   71.770699] Bluetooth: hci0: advertising data len corrected
  [   72.330683] (elapsed 0.920 seconds) done.
  [   72.330689] OOM killer disabled.
  [   72.330690] Freezing remaining freezable tasks ... (elapsed 0.014 seconds) 
done.
  [   72.345132] printk: Suspending console(s) (use no_console_suspend to debug)
  [   72.399557] pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16
  [   72.399566] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -16
  [   72.399730] PM: Device :00:14.0 failed to suspend async: error -16
  [   72.425583] PM: Some devices failed to suspend, or early wake event 
detected
  [   72.486631] Bluetooth: hci0: advertising data len corrected
  [   72.611800] OOM killer enabled.
  [   72.611802] Restarting tasks ... done.
  [   72.629308] thermal thermal_zone5: failed to read out thermal zone (-61)
  [   72.663376] PM: suspend exit
  [   72.663413] PM: suspend entry (s2idle)

  This can be fixed by upgrading intel/ibt-19-0-1.sfi to REL0318 from
  upstream commit c0ca980cee32.

  ---
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.173.14
  ProcVersionSignature: Ubuntu 5.0.0-1037.42-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1037-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1583 F pulseaudio
  Date: Tue Feb 11 02:05:47 2020
  Dependencies:

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-arya+X37
  InstallationDate: Installed on 2020-01-06 (35 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  MachineType: Dell Inc. Latitude 7410
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1037-oem-osp1 
root=UUID=fd4c84f6-205f-4fb2-9225-bb232ba08e38 ro quiet splash vt.handoff=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-1037-oem-osp1 N/A
   linux-backports-modules-5.0.0-1037-oem-osp1  N/A
   linux-firmware   1.173.14
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.4.7
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.4.7:bd12/30/2019:svnDellInc.:pnLatitude7410:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7410
  dmi.product.sku: 09BE
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1871812] Re: Can not see the storage with Intel RAID On mode enabled on Intel Comet Lake

[Shih-Yuan Lee]

Dell XPS 13 7390 has the same problem.

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

Title:
  Can not see the storage with Intel RAID On mode enabled on Intel Comet
  Lake

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Can not see the storage on Dell Latitude 5310 with Intel RAID On mode
  enabled in the BIOS.

  The Dell Latitude 5310 is an Intel Comet Lake platform, which missing
  the ID[1] in the kernel.

  [1] https://lore.kernel.org/lkml/20191128081041.6948-1-jian-
  h...@endlessm.com/.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1536 F pulseaudio
  CasperVersion: 1.442
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 09:55:02 2020
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200405)
  MachineType: Dell Inc. Latitude 5310
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed quiet splash --- toram
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.4.12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.4.12:bd01/09/2020:svnDellInc.:pnLatitude5310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5310
  dmi.product.sku: 099F
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1871812] [NEW] Can not see the storage with Intel RAID On mode enabled on Intel Comet Lake

[Shih-Yuan Lee]

Public bug reported:

Can not see the storage on Dell Latitude 5310 with Intel RAID On mode
enabled in the BIOS.

The Dell Latitude 5310 is an Intel Comet Lake platform, which missing
the ID[1] in the kernel.

[1] https://lore.kernel.org/lkml/20191128081041.6948-1-jian-
h...@endlessm.com/.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-21-generic 5.4.0-21.25
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ubuntu 1536 F pulseaudio
CasperVersion: 1.442
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr  9 09:55:02 2020
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200405)
MachineType: Dell Inc. Latitude 5310
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed 
quiet splash --- toram
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-21-generic N/A
 linux-backports-modules-5.4.0-21-generic  N/A
 linux-firmware1.187
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/09/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.4.12
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr0.4.12:bd01/09/2020:svnDellInc.:pnLatitude5310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 5310
dmi.product.sku: 099F
dmi.sys.vendor: Dell Inc.

** Affects: oem-priority
 Importance: Critical
 Status: New

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


** Tags: amd64 apport-bug focal

** Description changed:

- Can not see the storage with Intel RAID On mode enabled
+ Can not see the storage on Dell Latitude 5310 with Intel RAID On mode enabled
+ It seems to lack of 
https://lore.kernel.org/lkml/20191128081041.6948-1-jian-h...@endlessm.com/.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  ubuntu 1536 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  ubuntu 1536 F pulseaudio
  CasperVersion: 1.442
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 09:55:02 2020
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200405)
  MachineType: Dell Inc. Latitude 5310
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=C.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=C.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed quiet splash --- toram
  RelatedPackageVersions:
-  linux-restricted-modules-5.4.0-21-generic N/A
-  linux-backports-modules-5.4.0-21-generic  N/A
-  linux-firmware1.187
+  linux-restricted-modules-5.4.0-21-generic N/A
+  linux-backports-modules-5.4.0-21-generic  N/A
+  linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.4.12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.4.12:bd01/09/2020:svnDellInc.:pnLatitude5310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5310
  dmi.product.sku: 099F
  dmi.sys.vendor: Dell Inc.

** Also affects: oem-priority
   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/1871812

Title:
  Can not see the storage with Intel RAID On mode enabled on Intel Comet
  Lake

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Can not see the storage on Dell Latitude 5310 with Intel RAID On mode
  enabled in the BIOS.

  The Dell Latitude 5310 is an Intel Comet Lake platform, which missing
  the ID[1] in the kernel.

  [1] https://lore.kernel.org/lkml/20191128081041.6948-1-jian-
  h...@endlessm.com/.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: 

[Kernel-packages] [Bug 1871811] Re: Can not see the storage on Dell Latitude 5310 with Intel RAID On mode enabled

[Shih-Yuan Lee]

** No longer affects: linux (Ubuntu)

** Project changed: oem-priority => null-and-void

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

Title:
  Can not see the storage on Dell Latitude 5310 with Intel RAID On mode
  enabled

Status in NULL Project:
  New

Bug description:
  Can not see the storage on Dell Latitude 5310 with Intel RAID On mode enabled
  It seems to lack of 
https://lore.kernel.org/lkml/20191128081041.6948-1-jian-h...@endlessm.com/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/null-and-void/+bug/1871811/+subscriptions

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

[Kernel-packages] [Bug 1871811] [NEW] Can not see the storage on Dell Latitude 5310 with Intel RAID On mode enabled

[Shih-Yuan Lee]

Public bug reported:

Can not see the storage on Dell Latitude 5310 with Intel RAID On mode enabled
It seems to lack of 
https://lore.kernel.org/lkml/20191128081041.6948-1-jian-h...@endlessm.com/.

** Affects: null-and-void
 Importance: High
 Status: New

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Summary changed:

- Can not see the storage with Intel RAID On mode enabled
+ Can not see the storage on Dell Latitude 5310 with Intel RAID On mode enabled

** Description changed:

- Can not see the storage for Comet Lake PCH RAID with Intel RAID On mode 
enabled
+ Can not see the storage on Dell Latitude 5310 with Intel RAID On mode enabled
  It seems to miss 
https://lore.kernel.org/lkml/20191128081041.6948-1-jian-h...@endlessm.com/.

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

Title:
  Can not see the storage on Dell Latitude 5310 with Intel RAID On mode
  enabled

Status in NULL Project:
  New

Bug description:
  Can not see the storage on Dell Latitude 5310 with Intel RAID On mode enabled
  It seems to lack of 
https://lore.kernel.org/lkml/20191128081041.6948-1-jian-h...@endlessm.com/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/null-and-void/+bug/1871811/+subscriptions

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

[Kernel-packages] [Bug 1871811] Re: Can not see the storage on Dell Latitude 5310 with Intel RAID On mode enabled

[Shih-Yuan Lee]

** Description changed:

  Can not see the storage on Dell Latitude 5310 with Intel RAID On mode enabled
- It seems to miss 
https://lore.kernel.org/lkml/20191128081041.6948-1-jian-h...@endlessm.com/.
+ It seems to lack of 
https://lore.kernel.org/lkml/20191128081041.6948-1-jian-h...@endlessm.com/.

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

Title:
  Can not see the storage on Dell Latitude 5310 with Intel RAID On mode
  enabled

Status in NULL Project:
  New

Bug description:
  Can not see the storage on Dell Latitude 5310 with Intel RAID On mode enabled
  It seems to lack of 
https://lore.kernel.org/lkml/20191128081041.6948-1-jian-h...@endlessm.com/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/null-and-void/+bug/1871811/+subscriptions

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

[Kernel-packages] [Bug 1890772] Re: Some external 4K monitor is not working properly

[Shih-Yuan Lee]

Regaring comment #26, I am using PX UH-1.2MX HDMI 2.0 certified Premium
High Speed cable so the cable's quality should not be a problem.

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

Title:
  Some external 4K monitor is not working properly

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  The bug is originated from,
  https://bugs.launchpad.net/somerville/+bug/1887915/
  https://bugs.launchpad.net/somerville/+bug/1886778

  It has some problem when user connect to external 4K monitor with refresh 
rate 60.
  The problem can be solved by lower the bpc, or lower the refresh rate.

  `xrandr --output DP-3 --set "max bpc" 8`

  Would like to open this bug to open discussion for enhancing user experience.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:09fc]
     Subsystem: Dell GP107M [GeForce MX350] [1028:09fc]
  InstallationDate: Installed on 2020-08-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  Package: xorg 1:7.7+19ubuntu14 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Tags: third-party-packages focal ubuntu
  Uname: Linux 5.6.0-1021-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1890772] Re: Some external 4K monitor is not working properly

[Shih-Yuan Lee]

My monitor is EDID 1.3 and it has the same problem.

edid-decode (hex):

00 ff ff ff ff ff ff 00 41 0c 8f c1 bd 07 00 00 
08 1d 01 03 80 3c 22 78 2a 67 a1 a5 55 4d a2 27 
0e 50 54 bf ef 00 d1 c0 b3 00 95 00 81 80 81 40 
81 c0 01 01 01 01 4d d0 00 a0 f0 70 3e 80 30 20 
35 00 55 50 21 00 00 1a a3 66 00 a0 f0 70 1f 80 
30 20 35 00 55 50 21 00 00 1a 00 00 00 fc 00 50 
48 4c 20 32 37 36 45 38 56 0a 20 20 00 00 00 fd 
00 17 50 1e a0 3c 00 0a 20 20 20 20 20 20 01 72 

02 03 33 f1 4c 90 04 03 1f 13 01 12 5d 5e 5f 60 
61 23 09 07 07 83 01 00 00 6d 03 0c 00 10 00 38 
78 20 00 60 01 02 03 67 d8 5d c4 01 78 80 03 e3 
0f 00 0c 56 5e 00 a0 a0 a0 29 50 30 20 35 00 55 
50 21 00 00 1e 02 3a 80 18 71 38 2d 40 58 2c 45 
00 55 50 21 00 00 1e 01 1d 00 72 51 d0 1e 20 6e 
28 55 00 55 50 21 00 00 1e 4d 6c 80 a0 70 70 3e 
80 30 20 3a 00 55 50 21 00 00 1a 00 00 00 00 4e 



EDID version: 1.3
Manufacturer: PHL Model 49551 Serial Number 1981
Made in week 8 of 2019
Digital display
Maximum image size: 60 cm x 34 cm
Gamma: 2.20
DPMS levels: Off
RGB color display
First detailed timing is preferred timing
Color Characteristics
  Red:   0.6455, 0.3339
  Green: 0.3017, 0.6357
  Blue:  0.1542, 0.0566
  White: 0.3125, 0.3291
Established Timings I & II
720x40070.082 Hz   9:531.467 kHz  28.320 MHz (IBM)
640x48059.940 Hz   4:331.469 kHz  25.175 MHz (DMT)
640x48066.667 Hz   4:335.000 kHz  30.240 MHz (Apple)
640x48072.809 Hz   4:337.861 kHz  31.500 MHz (DMT)
640x48075.000 Hz   4:337.500 kHz  31.500 MHz (DMT)
800x60056.250 Hz   4:335.156 kHz  36.000 MHz (DMT)
800x60060.317 Hz   4:337.879 kHz  40.000 MHz (DMT)
800x60072.188 Hz   4:348.077 kHz  50.000 MHz (DMT)
800x60075.000 Hz   4:346.875 kHz  49.500 MHz (DMT)
832x62474.551 Hz   4:349.726 kHz  57.284 MHz (Apple)
   1024x76860.004 Hz   4:348.363 kHz  65.000 MHz (DMT)
   1024x76870.069 Hz   4:356.476 kHz  75.000 MHz (DMT)
   1024x76875.029 Hz   4:360.023 kHz  78.750 MHz (DMT)
   1280x1024   75.025 Hz   5:479.976 kHz 135.000 MHz (DMT)
Standard Timings
   1920x1080   60.000 Hz  16:967.500 kHz 148.500 MHz (DMT)
   1680x1050   59.954 Hz  16:10   65.290 kHz 146.250 MHz (DMT)
   1440x90059.887 Hz  16:10   55.935 kHz 106.500 MHz (DMT)
   1280x1024   60.020 Hz   5:463.981 kHz 108.000 MHz (DMT)
   1280x96060.000 Hz   4:360.000 kHz 108.000 MHz (DMT)
   1280x72060.000 Hz  16:945.000 kHz  74.250 MHz (DMT)
Detailed mode: Clock 533.250 MHz, 597 mm x 336 mm
   3840 3888 3920 4000 ( 48  32  80)
   2160 2163 2168  (  3   5  54)
   +hsync -vsync
   VertFreq: 59.997 Hz, HorFreq: 133.312 kHz
Detailed mode: Clock 262.750 MHz, 597 mm x 336 mm
   3840 3888 3920 4000 ( 48  32  80)
   2160 2163 2168 2191 (  3   5  23)
   +hsync -vsync
   VertFreq: 29.981 Hz, HorFreq: 65.688 kHz
Display Product Name: PHL 276E8V
Display Range Limits
  Monitor ranges (GTF): 23-80 Hz V, 30-160 kHz H, max dotclock 600 MHz
Has 1 extension block
Checksum: 0x72



CTA-861 Extension Block Revision 3
Underscans PC formats by default
Basic audio support
Supports YCbCr 4:4:4
Supports YCbCr 4:2:2
1 native detailed modes
47 bytes of CTA data blocks
  Video Data Block
 1920x1080   60.000 Hz  16:967.500 kHz 148.500 MHz (VIC  16, native)
 1280x72060.000 Hz  16:945.000 kHz  74.250 MHz (VIC   4)
  720x48059.940 Hz  16:931.469 kHz  27.000 MHz (VIC   3)
 1920x1080   50.000 Hz  16:956.250 kHz 148.500 MHz (VIC  31)
 1280x72050.000 Hz  16:937.500 kHz  74.250 MHz (VIC  19)
  640x48059.940 Hz   4:331.469 kHz  25.175 MHz (VIC   1)
  720x57650.000 Hz  16:931.250 kHz  27.000 MHz (VIC  18)
 3840x2160   24.000 Hz  16:954.000 kHz 297.000 MHz (VIC  93)
 3840x2160   25.000 Hz  16:956.250 kHz 297.000 MHz (VIC  94)
 3840x2160   30.000 Hz  16:967.500 kHz 297.000 MHz (VIC  95)
 3840x2160   50.000 Hz  16:9   112.500 kHz 594.000 MHz (VIC  96)
 3840x2160   60.000 Hz  16:9   135.000 kHz 594.000 MHz (VIC  97)
  Audio Data Block
Linear PCM, max channels 2
  Supported sample rates (kHz): 48 44.1 32
  Supported sample sizes (bits): 24 20 16
  Speaker Allocation Data Block
Speaker map:
  FL/FR - Front Left/Right
  Vendor-Specific Data Block, OUI 0x000c03 (HDMI)
Source physical address 1.0.0.0
DC_36bit
DC_30bit
DC_Y444
Maximum TMDS clock: 600 MHz
Extended HDMI video details:
  HDMI VICs:
 3840x2160   30.000 Hz  16:967.500 kHz 297.000 MHz (HDMI VIC 1)
 3840x2160   25.000 Hz  16:956.250 kHz 297.000 MHz (HDMI VIC 2)
 3840x2160   24.000 Hz  16:954.000 kHz 297.000 MHz (HDMI VIC 3)
  Vendor-Specific Data Block, OUI 0xc45dd8 (HDMI Forum)
Version: 1
Maximum TMDS Character Rate: 600 MHz
SCDC 

[Kernel-packages] [Bug 1914374] Re: Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image

[Shih-Yuan Lee]

I saw oem-stella.cmit-meowth-meta 20.04ubuntu11 in 
http://hp.archive.canonical.com/dists/focal/stella.cmit/binary-amd64/Packages 
depends on oem-fix-gfx-nvidia-1868199, but I can not find 
oem-fix-gfx-nvidia-1868199 on http://hp.archive.canonical.com/pool/public/o/. 
So the dependencies of oem-stella.cmit-meowth-meta in OEM archive is broken.

Have we checked the installation without Internet? Will it still fail?

** Also affects: oem-priority
   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/1914374

Title:
  Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image

Status in OEM Priority Project:
  New
Status in ubiquity package in Ubuntu:
  Invalid
Status in ubuntu-drivers-common package in Ubuntu:
  In Progress
Status in ubiquity source package in Focal:
  Invalid
Status in ubuntu-drivers-common source package in Focal:
  In Progress
Status in ubiquity source package in Groovy:
  Invalid
Status in ubuntu-drivers-common source package in Groovy:
  New

Bug description:
  I've installed the focal-desktop-amd64.iso image with SHA-256 sum
  b928163990d9e148605c230c5d3e7bc563bb67269d551f741abc804553f3477c from
  http://cdimage.ubuntu.com/focal/daily-live/20210202.1/ on the HP ZBook
  15 G7 laptop (CID 202009-28216).

  There are multiple issues:

  * The graphical desktop isn't launched. The screen remains black except for a 
cursor blinking erratically in the top left corner of the screen. If I hammer 
Control+Alt+F[12345] for a while, the graphical desktop starts eventually.
  * The screen resolution is 3840x2160 but there is no scaling, so everything 
is tiny.
  * The touchpad does not work.
  * WLAN does not work.
  * Ethernet does not work. I tried two dongles (a USB A as well as a USB C 
dongle).
  * No sound.

  $ cat /proc/version_signature
  Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18

  $ lsb_release -rd
  Description:Ubuntu 20.04.2 LTS
  Release:20.04

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

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

[Kernel-packages] [Bug 1935892] Re: OEM 5.6 kernel is now transited to 5.10 but pre-signed nvidia is not and cause no nvidia driver after oem kernel transition

[Shih-Yuan Lee]

linux-modules-nvidia-460-oem-20.04 needs to become a dummy transitional package 
of linux-modules-nvidia-460-oem-20.04b.
Just like linux-oem-20.04 has become a dummy transitional package of 
linux-oem-20.04b.

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

Title:
  OEM 5.6 kernel is now transited to 5.10 but pre-signed nvidia is not
  and cause no nvidia driver after oem kernel transition

Status in OEM Priority Project:
  New
Status in linux-restricted-modules-oem-5.6 package in Ubuntu:
  New

Bug description:
  If end user install nvidia driver using 20.04.2 stock image without
  connecting network and they will get the 5.6 oem kernel + 5.6 nvidia
  driver (linux-modules-nvidia-*).

  After the installation, the user will get 5.10 kernel + nvidia pre-
  signed 5.6 driver after dist-upgrade.

  It will cause there is no nvidia driver in the system.

  Below shows the candidates packages:

  # apt policy linux-oem-20.04
  linux-oem-20.04:
    Installed: (none)
    Candidate: 5.10.0.1034.35
    Version table:
   5.10.0.1034.35 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
   5.10.0.1033.34 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   5.6.0.1007.7 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  # apt policy linux-modules-nvidia-460-oem-20.04
  linux-modules-nvidia-460-oem-20.04:
    Installed: (none)
    Candidate: 5.6.0-1056.60
    Version table:
   5.6.0-1056.60 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/restricted amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 
Packages

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

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

[Kernel-packages] [Bug 1849947] Re: Dell XPS 13 (7390) Display Flickering - 19.10

[Shih-Yuan Lee]

** Changed in: oem-priority
   Status: New => Fix Released

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

Title:
  Dell XPS 13 (7390) Display Flickering - 19.10

Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  Hi there,
  I recently purchased a Dell XPS 13 7390 (Developer Edition). I decided to 
replace 18.4 LTS with 19.10 and so far it has been pretty smooth. However, 
there is one issue which occurs frequently whereby the display flickers and 
becomes unusable. The best way to describe the appearance is that the image 
becomes heavily distorted. 

  Sometimes it only happens for a split second, other times it is
  permanently distorted. When this happens, simply closing the laptop
  lip and re-opening seems to put the display back into it's correct
  state.

  I didn't experience this issue on 18.04 LTS which is why I believe
  it's a Software Bug within 19.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 26 11:11:43 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0962]
  InstallationDate: Installed on 2019-10-25 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. XPS 13 7390
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 0G2D0W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd08/23/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Kernel-packages] [Bug 1857409] Re: alsa/sof: load different firmware on different platforms

[Shih-Yuan Lee]

** Changed in: oem-priority
   Status: New => Fix Released

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

Title:
  alsa/sof: load different firmware on different platforms

Status in HWE Next:
  New
Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  In our ubuntu kernel, the sof driver will load the sof-cnl.ri (firmware)
  on all platforms, but mainline kernel already supported the multi
  firmwares on differnt platforms, and OEM project needs us to
  support the mutli-firmware names in the ubuntu kernel

  [Fix]
  cherry-pick 3 upstream patches, then on cnl platforms, it will
  load sof-cnl.ri, on cml platfomrs, it will load sof-cml.ri, on cfl
  platforms, it will load sof-cfl.ri

  
  [Test Case]
  Prepare the firmware from https://github.com/thesofproject/linux-firmware
  master branch, then boot the kernel with these patches.

  [Regression Risk]
  Low, just let different platforms load differnt firmware, and these
  patches are in the upstream kernel.

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


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

[Kernel-packages] [Bug 1875254] Re: Intermittent display blackouts on event

[Shih-Yuan Lee]

** Changed in: oem-priority
   Status: New => Fix Released

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

Title:
  Intermittent display blackouts on event

Status in HWE Next:
  New
Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-osp1 source package in Focal:
  Invalid

Bug description:
  [Impact]
  When audio device enters runpm D3(idle for 7 seconds) and then wakes it up to 
make a sound, it flicks the screen.
  This behavior could be observed while plug/remove AC cable or USB disk, or 
open a terminal and press backsapce key.

  [Fix]
  This issue could be fixed by this commit, it fixes the flicker during 
boot-time, but it also fixes the flicker during rumtime wakeup.
  1ee48a61aa57 drm/i915: Limit audio CDCLK>=2*BCLK constraint back to GLK only

  Audio drivers communicate with i915 over HDA bus multiple times during system 
boot-up and each of these transactions result in matching
  get_power/put_power calls to i915, and depending on the platform,
  a modeset change causing visible flicker.
  
  GLK is the only platform with minimum CDCLK significantly lower
  than BCLK, and thus for GLK setting a higher CDCLK is mandatory.

  For other platforms, minimum CDCLK is close but below 2*BCLK
  (e.g. on ICL, CDCLK=176.4kHz with BCLK=96kHz). Spec-wise the constraint
  should be set, but in practise no communication errors have been
  reported and the downside if set is the flicker observed at boot-time.

  [Test]
  Verified on Dell XPS 13 9300

  [Regression Potential]
  Low, it fixes below commit which contains in ubuntu kernel and should have 
been applied on ubuntu kernel, too.
  Fixes: f6ec9483091f ("drm/i915: extend audio CDCLK>=2*BCLK constraint to more 
platforms")

  =

  Issues with the screen going black for a second on certain events on a dell 
XPS 9370 2 in 1, especially when on battery.
  Seems to be a known bug in arch 
(https://wiki.archlinux.org/index.php/Dell_XPS_13_2-in-1_(7390)).
  Last 5.6.7 kernel tested and the issues has disappears but pb with sound card.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lucie  2232 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. XPS 13 7390 2-in-1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=056fd229-d014-4b3b-a581-1b646105d1ed ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/02/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.1
  dmi.board.name: 06CDVY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.1:bd03/02/2020:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms

[Shih-Yuan Lee]

I confirmed that linux-oem-20.04d 5.14.0.1015.15 in focal-proposed can
make the MIPI camera workable.

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

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

Title:
  Support Intel IPU6 MIPI camera on Alder Lake platforms

Status in HWE Next:
  New
Status in OEM Priority Project:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-firmware source package in Focal:
  In Progress
Status in linux-oem-5.14 source package in Focal:
  In Progress
Status in linux source package in Jammy:
  Incomplete
Status in linux-firmware source package in Jammy:
  In Progress
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  == kernel driver SRU ==

  [SRU Justification]

  [Impact]

  To support Intel IPU6 MIPI camera on Alder Lake platforms.

  [Fix]

  Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has
  been addressed by bug 1921345 and 1939539. They are backported from
  https://github.com/intel/ipu6-drivers.

  Further works to enable IPU6 camera on Alder Lake platforms depend on a
  few more fixes from same ipu6-drivers repository, as well as an extra
  https://github.com/intel/ivsc-driver for Intel Vision Sensing
  Controller(IVSC).

  [Test Case]

  This depends on an integral of enablement components inclusive of the
  kernel drivers that are being proposed, firmware, updates for the
  userspace camera hardware abstration layer library and a gstreamer
  element as what we have for Tiger Lake platforms.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  [Other Info]

  Jammy is planned, but yet the support for 5.15 kernel is not yet started
  from Intel side.

  == linux-firmware SRU ==

  [SRU Justification]

  [Impact]

  Intel IPU6 MIPI camera on Alder Lake platform takes a different fw
  blob.

  [Fix]

  While Intel has no intention to upstream IPU6 driver before kernel
  camera is out, it's available in
  https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its
  main branch.

  [Test Case]

  This would take both kernel and firmware fixes, as well as updates for
  the userspace middleware, gstreamer element plugin, to enable the device.
  With all of them in position, one should be able to browse camera with
  legacy camera apps like cheese.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  == original bug report ==

  This depends on following componenets:
  * ipu6ep firmware in 
https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d
  * Intel VSC fw version 1.2.3.439 (not yet available publicly)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-12-20 (7 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 9320
  Package: linux-firmware 1.187.23+staging.38 [origin: unknown]
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem 
root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-2013-oem N/A
   linux-backports-modules-5.14.0-2013-oem  N/A
   linux-firmware   1.187.23+staging.38
  Tags: third-party-packages focal
  Uname: Linux 5.14.0-2013-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 0.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.2.7
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Kernel-packages] [Bug 1956426] Re: MIssing firmware for Intel Visual Sensing Controller

[Shih-Yuan Lee]

I have checked linux-firmware 1.187.25 in focal-proposed and it can
enable the MIPI camera on the laptop.

** Tags added: verification-done-focal

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

Title:
  MIssing firmware for Intel Visual Sensing Controller

Status in OEM Priority Project:
  Fix Committed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  Fix Committed
Status in linux-firmware source package in Jammy:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]

  Need firmware blob for Intel Visual Sensing Controller for IPU6 cameras on
  Intel Alder Lake platforms.

  [Fix]

  Two commits from upstream repo https://github.com/intel/ivsc-firmware main
  branch. While Intel has no plan to upstream their IPU6 driver before
  kernel camera API is out, the firmware blobs will probably stay where they
  are until the plan changed.

  [Test Case]

  This would take both kernel and firmware fixes, as well as updates for
  the userspace middleware, gstreamer element plugin, to enable the device.
  With all of them in position, one should be able to browse camera with
  legacy camera apps like cheese.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  [Other Info]

  This is a follow-up for bug 1955383, which at the time being SRU-ed, Intel
  has not yet published these ivsc fw for redistribution.

  Focal is nomiated to support oem-5.14 kernel.

  == original bug report ==

  This is a followup for bug 1955383 that ivsc firmware was not publicly
  released at the time submitting other Intel IPU6 works for Alder Lake
  platform. They're now available in https://github.com/intel/ivsc-
  firmware

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


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

[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms

[Shih-Yuan Lee]

@Shengyao,

Please check LP: #1955689 instead.

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

Title:
  Support Intel IPU6 MIPI camera on Alder Lake platforms

Status in HWE Next:
  New
Status in OEM Priority Project:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-firmware source package in Focal:
  Fix Committed
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Incomplete
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  == kernel driver SRU ==

  [SRU Justification]

  [Impact]

  To support Intel IPU6 MIPI camera on Alder Lake platforms.

  [Fix]

  Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has
  been addressed by bug 1921345 and 1939539. They are backported from
  https://github.com/intel/ipu6-drivers.

  Further works to enable IPU6 camera on Alder Lake platforms depend on a
  few more fixes from same ipu6-drivers repository, as well as an extra
  https://github.com/intel/ivsc-driver for Intel Vision Sensing
  Controller(IVSC).

  [Test Case]

  This depends on an integral of enablement components inclusive of the
  kernel drivers that are being proposed, firmware, updates for the
  userspace camera hardware abstration layer library and a gstreamer
  element as what we have for Tiger Lake platforms.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  [Other Info]

  Jammy is planned, but yet the support for 5.15 kernel is not yet started
  from Intel side.

  == linux-firmware SRU ==

  [SRU Justification]

  [Impact]

  Intel IPU6 MIPI camera on Alder Lake platform takes a different fw
  blob.

  [Fix]

  While Intel has no intention to upstream IPU6 driver before kernel
  camera is out, it's available in
  https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its
  main branch.

  [Test Case]

  This would take both kernel and firmware fixes, as well as updates for
  the userspace middleware, gstreamer element plugin, to enable the device.
  With all of them in position, one should be able to browse camera with
  legacy camera apps like cheese.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  == original bug report ==

  This depends on following componenets:
  * ipu6ep firmware in 
https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d
  * Intel VSC fw version 1.2.3.439 (not yet available publicly)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-12-20 (7 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 9320
  Package: linux-firmware 1.187.23+staging.38 [origin: unknown]
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem 
root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-2013-oem N/A
   linux-backports-modules-5.14.0-2013-oem  N/A
   linux-firmware   1.187.23+staging.38
  Tags: third-party-packages focal
  Uname: Linux 5.14.0-2013-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 0.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.2.7
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.2.7:bd12/02/2021:br0.2:svnDellInc.:pnXPS9320:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0AF3:
  dmi.product.family: XPS
  dmi.product.name: XPS 9320
  

[Kernel-packages] [Bug 1955689] Re: Add Bluetooth support for Qualcomm WCN6856

[Shih-Yuan Lee]

** Tags added: oem-priority originate-from-1939648 sutton

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

Title:
  Add Bluetooth support for Qualcomm WCN6856

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-firmware source package in Focal:
  Fix Committed
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Confirmed
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [Impact]
  WCN6856 Bluetooth doesn't work.

  [Fix]
  Backport firmware blobs and driver support to make it work by loading
  correct firmwares.
   
  [Test]
  Bluetooth scanning and pairing work, and continue to do so after several
  suspend/resume cycles.

  [Where problems could occur]
  The upstream version of btusb_generate_qca_nvm_name() adds several
  missing le*_to_cpu() macros, so if this device was ever used on a Big
  Endian system, this is a behavioral change.

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


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

[Kernel-packages] [Bug 1956426] Re: MIssing firmware for Intel Visual Sensing Controller

[Shih-Yuan Lee]

** Tags added: oem-priority originate-from-1949435 somerville

** Changed in: oem-priority
   Status: New => Fix Committed

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

** Changed in: oem-priority
 Assignee: (unassigned) => Shih-Yuan Lee (fourdollars)

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

Title:
  MIssing firmware for Intel Visual Sensing Controller

Status in OEM Priority Project:
  Fix Committed
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux-firmware source package in Focal:
  Fix Committed
Status in linux-firmware source package in Jammy:
  Fix Committed

Bug description:
  [SRU Justification]

  [Impact]

  Need firmware blob for Intel Visual Sensing Controller for IPU6 cameras on
  Intel Alder Lake platforms.

  [Fix]

  Two commits from upstream repo https://github.com/intel/ivsc-firmware main
  branch. While Intel has no plan to upstream their IPU6 driver before
  kernel camera API is out, the firmware blobs will probably stay where they
  are until the plan changed.

  [Test Case]

  This would take both kernel and firmware fixes, as well as updates for
  the userspace middleware, gstreamer element plugin, to enable the device.
  With all of them in position, one should be able to browse camera with
  legacy camera apps like cheese.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  [Other Info]

  This is a follow-up for bug 1955383, which at the time being SRU-ed, Intel
  has not yet published these ivsc fw for redistribution.

  Focal is nomiated to support oem-5.14 kernel.

  == original bug report ==

  This is a followup for bug 1955383 that ivsc firmware was not publicly
  released at the time submitting other Intel IPU6 works for Alder Lake
  platform. They're now available in https://github.com/intel/ivsc-
  firmware

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


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

[Kernel-packages] [Bug 1938531] Re: support signed v4l2loopback dkms build

[Shih-Yuan Lee]

** Tags added: oem-priority originate-from-1949435 somerville

** Changed in: oem-priority
   Status: New => In Progress

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

** Changed in: oem-priority
 Assignee: (unassigned) => Shih-Yuan Lee (fourdollars)

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

Title:
  support signed v4l2loopback dkms build

Status in OEM Priority Project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  In Progress
Status in linux-oem-5.13 source package in Focal:
  In Progress
Status in linux-oem-5.14 source package in Focal:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]

  v4l2loopback is used as a critical role on Intel IPU6 camera platforms,
  which takes userspace middleware involvements to correctly configure
  hardware sensors. While all the legacy camera applications are not yet
  learned how to support libcamera, v4l2loopback and a v4l2-relayd step in
  as a video streaming proxy for backward compatibility.

  To preinstall v4l2loopback kernel module on secureboot systems, signed
  modules should be used.

  [Fix]

  All Ubuntu specific changes to enable signed v4l2loopback dkms builds.

  [Test Case]

  Install signed modules package and check `modinfo v4l2loopback`.

  [Where problems could occur]

  N/A.

  [Other Info]

  This adds current revision of v4l2loopback in the ubuntu archive. While
  some other fixes are also needed for v4l2loopback/focal, expects version
  bumps recently.

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


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

[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms

[Shih-Yuan Lee]

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

** Changed in: oem-priority
   Status: New => In Progress

** Changed in: oem-priority
 Assignee: (unassigned) => Shih-Yuan Lee (fourdollars)

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

Title:
  Support Intel IPU6 MIPI camera on Alder Lake platforms

Status in HWE Next:
  New
Status in OEM Priority Project:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-firmware source package in Focal:
  In Progress
Status in linux-oem-5.14 source package in Focal:
  In Progress
Status in linux source package in Jammy:
  Incomplete
Status in linux-firmware source package in Jammy:
  In Progress
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  == kernel driver SRU ==

  [SRU Justification]

  [Impact]

  To support Intel IPU6 MIPI camera on Alder Lake platforms.

  [Fix]

  Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has
  been addressed by bug 1921345 and 1939539. They are backported from
  https://github.com/intel/ipu6-drivers.

  Further works to enable IPU6 camera on Alder Lake platforms depend on a
  few more fixes from same ipu6-drivers repository, as well as an extra
  https://github.com/intel/ivsc-driver for Intel Vision Sensing
  Controller(IVSC).

  [Test Case]

  This depends on an integral of enablement components inclusive of the
  kernel drivers that are being proposed, firmware, updates for the
  userspace camera hardware abstration layer library and a gstreamer
  element as what we have for Tiger Lake platforms.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  [Other Info]

  Jammy is planned, but yet the support for 5.15 kernel is not yet started
  from Intel side.

  == linux-firmware SRU ==

  [SRU Justification]

  [Impact]

  Intel IPU6 MIPI camera on Alder Lake platform takes a different fw
  blob.

  [Fix]

  While Intel has no intention to upstream IPU6 driver before kernel
  camera is out, it's available in
  https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its
  main branch.

  [Test Case]

  This would take both kernel and firmware fixes, as well as updates for
  the userspace middleware, gstreamer element plugin, to enable the device.
  With all of them in position, one should be able to browse camera with
  legacy camera apps like cheese.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  == original bug report ==

  This depends on following componenets:
  * ipu6ep firmware in 
https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d
  * Intel VSC fw version 1.2.3.439 (not yet available publicly)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-12-20 (7 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 9320
  Package: linux-firmware 1.187.23+staging.38 [origin: unknown]
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem 
root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-2013-oem N/A
   linux-backports-modules-5.14.0-2013-oem  N/A
   linux-firmware   1.187.23+staging.38
  Tags: third-party-packages focal
  Uname: Linux 5.14.0-2013-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 0.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.2.7
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modali

[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms

[Shih-Yuan Lee]

@Stuart Pook (slp110264)

Please DON'T use ppa:oem-solutions-group/intel-ipu6 because it is a
development PPA that it will often break the MIPI camera during the
development.

You can use `sudo add-apt-repository --remove ppa:oem-solutions-
group/intel-ipu6` to remove it.

However there may still be some broken packages in your system that you
need to downgrade/remove them manually.

The simple way is to reinstall Ubuntu 22.04.3 on your Dell XPS 13 9320
again and upgrade the whole system to the latest.

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

Title:
  Support Intel IPU6 MIPI camera on Alder Lake platforms

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  == kernel driver SRU ==

  [SRU Justification]

  [Impact]

  To support Intel IPU6 MIPI camera on Alder Lake platforms.

  [Fix]

  Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has
  been addressed by bug 1921345 and 1939539. They are backported from
  https://github.com/intel/ipu6-drivers.

  Further works to enable IPU6 camera on Alder Lake platforms depend on a
  few more fixes from same ipu6-drivers repository, as well as an extra
  https://github.com/intel/ivsc-driver for Intel Vision Sensing
  Controller(IVSC).

  [Test Case]

  This depends on an integral of enablement components inclusive of the
  kernel drivers that are being proposed, firmware, updates for the
  userspace camera hardware abstration layer library and a gstreamer
  element as what we have for Tiger Lake platforms.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  [Other Info]

  Jammy is planned, but yet the support for 5.15 kernel is not yet started
  from Intel side.

  == linux-firmware SRU ==

  [SRU Justification]

  [Impact]

  Intel IPU6 MIPI camera on Alder Lake platform takes a different fw
  blob.

  [Fix]

  While Intel has no intention to upstream IPU6 driver before kernel
  camera is out, it's available in
  https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its
  main branch.

  [Test Case]

  This would take both kernel and firmware fixes, as well as updates for
  the userspace middleware, gstreamer element plugin, to enable the device.
  With all of them in position, one should be able to browse camera with
  legacy camera apps like cheese.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  == original bug report ==

  This depends on following componenets:
  * ipu6ep firmware in 
https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d
  * Intel VSC fw version 1.2.3.439 (not yet available publicly)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-12-20 (7 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 9320
  Package: linux-firmware 1.187.23+staging.38 [origin: unknown]
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem 
root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-2013-oem N/A
   linux-backports-modules-5.14.0-2013-oem  N/A
   linux-firmware   1.187.23+staging.38
  Tags: third-party-packages focal
  Uname: Linux 5.14.0-2013-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No 

[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms

[Shih-Yuan Lee]

linux/5.15.0-28.29 kernel in jammy-proposed has the kernel panic on Dell
Latitude 9420.

** Tags removed: verification-done-jammy
** Tags added: verification-failed-jammy

** Attachment added: "PXL_20220429_040458788.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1955383/+attachment/5584835/+files/PXL_20220429_040458788.jpg

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

Title:
  Support Intel IPU6 MIPI camera on Alder Lake platforms

Status in HWE Next:
  New
Status in OEM Priority Project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Invalid
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  In Progress

Bug description:
  == kernel driver SRU ==

  [SRU Justification]

  [Impact]

  To support Intel IPU6 MIPI camera on Alder Lake platforms.

  [Fix]

  Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has
  been addressed by bug 1921345 and 1939539. They are backported from
  https://github.com/intel/ipu6-drivers.

  Further works to enable IPU6 camera on Alder Lake platforms depend on a
  few more fixes from same ipu6-drivers repository, as well as an extra
  https://github.com/intel/ivsc-driver for Intel Vision Sensing
  Controller(IVSC).

  [Test Case]

  This depends on an integral of enablement components inclusive of the
  kernel drivers that are being proposed, firmware, updates for the
  userspace camera hardware abstration layer library and a gstreamer
  element as what we have for Tiger Lake platforms.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  [Other Info]

  Jammy is planned, but yet the support for 5.15 kernel is not yet started
  from Intel side.

  == linux-firmware SRU ==

  [SRU Justification]

  [Impact]

  Intel IPU6 MIPI camera on Alder Lake platform takes a different fw
  blob.

  [Fix]

  While Intel has no intention to upstream IPU6 driver before kernel
  camera is out, it's available in
  https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its
  main branch.

  [Test Case]

  This would take both kernel and firmware fixes, as well as updates for
  the userspace middleware, gstreamer element plugin, to enable the device.
  With all of them in position, one should be able to browse camera with
  legacy camera apps like cheese.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  == original bug report ==

  This depends on following componenets:
  * ipu6ep firmware in 
https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d
  * Intel VSC fw version 1.2.3.439 (not yet available publicly)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-12-20 (7 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 9320
  Package: linux-firmware 1.187.23+staging.38 [origin: unknown]
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem 
root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-2013-oem N/A
   linux-backports-modules-5.14.0-2013-oem  N/A
   linux-firmware   1.187.23+staging.38
  Tags: third-party-packages focal
  Uname: Linux 5.14.0-2013-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  

[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms

[Shih-Yuan Lee]

Dell XPS 13 Plus (9320) is a certified platform for Ubuntu 20.04 and Ubuntu 
22.04 now.
Please don't use ppa:oem-solutions-group/intel-ipu6.
Please remove those packages from ppa:oem-solutions-group/intel-ipu6, and then 
install oem-somerville-tentacool-meta from Ubuntu archive instead.
ppa:oem-solutions-group/intel-ipu6 is a development PPA for Intel IPU6 camera 
support.

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

Title:
  Support Intel IPU6 MIPI camera on Alder Lake platforms

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  == kernel driver SRU ==

  [SRU Justification]

  [Impact]

  To support Intel IPU6 MIPI camera on Alder Lake platforms.

  [Fix]

  Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has
  been addressed by bug 1921345 and 1939539. They are backported from
  https://github.com/intel/ipu6-drivers.

  Further works to enable IPU6 camera on Alder Lake platforms depend on a
  few more fixes from same ipu6-drivers repository, as well as an extra
  https://github.com/intel/ivsc-driver for Intel Vision Sensing
  Controller(IVSC).

  [Test Case]

  This depends on an integral of enablement components inclusive of the
  kernel drivers that are being proposed, firmware, updates for the
  userspace camera hardware abstration layer library and a gstreamer
  element as what we have for Tiger Lake platforms.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  [Other Info]

  Jammy is planned, but yet the support for 5.15 kernel is not yet started
  from Intel side.

  == linux-firmware SRU ==

  [SRU Justification]

  [Impact]

  Intel IPU6 MIPI camera on Alder Lake platform takes a different fw
  blob.

  [Fix]

  While Intel has no intention to upstream IPU6 driver before kernel
  camera is out, it's available in
  https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its
  main branch.

  [Test Case]

  This would take both kernel and firmware fixes, as well as updates for
  the userspace middleware, gstreamer element plugin, to enable the device.
  With all of them in position, one should be able to browse camera with
  legacy camera apps like cheese.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  == original bug report ==

  This depends on following componenets:
  * ipu6ep firmware in 
https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d
  * Intel VSC fw version 1.2.3.439 (not yet available publicly)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-12-20 (7 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 9320
  Package: linux-firmware 1.187.23+staging.38 [origin: unknown]
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem 
root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-2013-oem N/A
   linux-backports-modules-5.14.0-2013-oem  N/A
   linux-firmware   1.187.23+staging.38
  Tags: third-party-packages focal
  Uname: Linux 5.14.0-2013-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 0.2

[Kernel-packages] [Bug 1983574] [NEW] /sys/devices/system/cpu/cpufreq/policy0/base_frequency is missing for Intel(R) Core(TM) i7-4785T CPU @ 2.20GHz

[Shih-Yuan Lee]

Public bug reported:

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
$ lsb_release -rd
Description:Ubuntu 20.04.4 LTS
Release:20.04

2) The version of the package you are using, via 'apt-cache policy pkgname' or 
by checking in Software Center
$ apt-cache policy linux-image-5.15.0-43-generic
linux-image-5.15.0-43-generic:
  Installed: 5.15.0-43.46~20.04.1
  Candidate: 5.15.0-43.46~20.04.1
  Version table:
 *** 5.15.0-43.46~20.04.1 500
500 http://mirror01.idc.hinet.net/ubuntu focal-updates/main amd64 
Packages
500 http://mirror01.idc.hinet.net/ubuntu focal-security/main amd64 
Packages
100 /var/lib/dpkg/status

3) What you expected to happen
/sys/devices/system/cpu/cpufreq/policy0/base_frequency should exist.

4) What happened instead
/sys/devices/system/cpu/cpufreq/policy0/base_frequency doesn't exist.
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-09-22 (1047 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: linux-image-5.15.0-43-generic 5.15.0-43.46~20.04.1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
Tags:  focal
Uname: Linux 5.15.0-43-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-20 (836 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd microk8s plugdev 
sambashare sbuild sudo
_MarkForUpload: True

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


** Tags: apport-collected focal

** Tags added: apport-collected

** Description changed:

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04
  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt-cache policy linux-image-5.15.0-43-generic
  linux-image-5.15.0-43-generic:
Installed: 5.15.0-43.46~20.04.1
Candidate: 5.15.0-43.46~20.04.1
Version table:
   *** 5.15.0-43.46~20.04.1 500
  500 http://mirror01.idc.hinet.net/ubuntu focal-updates/main amd64 
Packages
  500 http://mirror01.idc.hinet.net/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
  
  3) What you expected to happen
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency should exist.
  
  4) What happened instead
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency doesn't exist.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.24
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2019-09-22 (1047 days ago)
+ InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
+ Package: linux-image-5.15.0-43-generic 5.15.0-43.46~20.04.1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
+ Tags:  focal
+ Uname: Linux 5.15.0-43-generic x86_64
+ UpgradeStatus: Upgraded to focal on 2020-04-20 (836 days ago)
+ UserGroups: adm cdrom dip docker libvirt lpadmin lxd microk8s plugdev 
sambashare sbuild sudo
+ _MarkForUpload: True

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

Title:
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency is missing for
  Intel(R) Core(TM) i7-4785T CPU @ 2.20GHz

Status in linux-hwe-5.15 package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt-cache policy linux-image-5.15.0-43-generic
  linux-image-5.15.0-43-generic:
Installed: 5.15.0-43.46~20.04.1
Candidate: 5.15.0-43.46~20.04.1
Version table:
   *** 5.15.0-43.46~20.04.1 500
  500 http://mirror01.idc.hinet.net/ubuntu focal-updates/main amd64 
Packages
  500 http://mirror01.idc.hinet.net/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency should exist.

  4) What happened instead
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency doesn't exist.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-09-22 (1047 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: linux-image-5.15.0-43-generic 

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

[Shih-Yuan Lee]

apport information

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

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

Title:
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency is missing for
  Intel(R) Core(TM) i7-4785T CPU @ 2.20GHz

Status in linux-hwe-5.15 package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt-cache policy linux-image-5.15.0-43-generic
  linux-image-5.15.0-43-generic:
Installed: 5.15.0-43.46~20.04.1
Candidate: 5.15.0-43.46~20.04.1
Version table:
   *** 5.15.0-43.46~20.04.1 500
  500 http://mirror01.idc.hinet.net/ubuntu focal-updates/main amd64 
Packages
  500 http://mirror01.idc.hinet.net/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency should exist.

  4) What happened instead
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency doesn't exist.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-09-22 (1047 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: linux-image-5.15.0-43-generic 5.15.0-43.46~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Tags:  focal
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-20 (836 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd microk8s plugdev 
sambashare sbuild sudo
  _MarkForUpload: True

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


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

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

[Shih-Yuan Lee]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1983574/+attachment/5607008/+files/Dependencies.txt

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

Title:
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency is missing for
  Intel(R) Core(TM) i7-4785T CPU @ 2.20GHz

Status in linux-hwe-5.15 package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt-cache policy linux-image-5.15.0-43-generic
  linux-image-5.15.0-43-generic:
Installed: 5.15.0-43.46~20.04.1
Candidate: 5.15.0-43.46~20.04.1
Version table:
   *** 5.15.0-43.46~20.04.1 500
  500 http://mirror01.idc.hinet.net/ubuntu focal-updates/main amd64 
Packages
  500 http://mirror01.idc.hinet.net/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency should exist.

  4) What happened instead
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency doesn't exist.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-09-22 (1047 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: linux-image-5.15.0-43-generic 5.15.0-43.46~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Tags:  focal
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-20 (836 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd microk8s plugdev 
sambashare sbuild sudo
  _MarkForUpload: True

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


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

[Kernel-packages] [Bug 1983574] ProcEnviron.txt

[Shih-Yuan Lee]

apport information

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

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

Title:
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency is missing for
  Intel(R) Core(TM) i7-4785T CPU @ 2.20GHz

Status in linux-hwe-5.15 package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt-cache policy linux-image-5.15.0-43-generic
  linux-image-5.15.0-43-generic:
Installed: 5.15.0-43.46~20.04.1
Candidate: 5.15.0-43.46~20.04.1
Version table:
   *** 5.15.0-43.46~20.04.1 500
  500 http://mirror01.idc.hinet.net/ubuntu focal-updates/main amd64 
Packages
  500 http://mirror01.idc.hinet.net/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency should exist.

  4) What happened instead
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency doesn't exist.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-09-22 (1047 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: linux-image-5.15.0-43-generic 5.15.0-43.46~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Tags:  focal
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-20 (836 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd microk8s plugdev 
sambashare sbuild sudo
  _MarkForUpload: True

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


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

[Kernel-packages] [Bug 1983574] Re: /sys/devices/system/cpu/cpufreq/policy0/base_frequency is missing for Intel(R) Core(TM) i7-4785T CPU @ 2.20GHz

[Shih-Yuan Lee]

base_frequency will only exist if the HWP feature is enabled in the
processor, i.e there is a 'hwp' in the flags of /proc/cpuinfo.

Refer to https://www.kernel.org/doc/html/v5.0/admin-
guide/pm/intel_pstate.html

** Changed in: linux-hwe-5.15 (Ubuntu)
   Status: New => Invalid

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

Title:
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency is missing for
  Intel(R) Core(TM) i7-4785T CPU @ 2.20GHz

Status in linux-hwe-5.15 package in Ubuntu:
  Invalid

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt-cache policy linux-image-5.15.0-43-generic
  linux-image-5.15.0-43-generic:
Installed: 5.15.0-43.46~20.04.1
Candidate: 5.15.0-43.46~20.04.1
Version table:
   *** 5.15.0-43.46~20.04.1 500
  500 http://mirror01.idc.hinet.net/ubuntu focal-updates/main amd64 
Packages
  500 http://mirror01.idc.hinet.net/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency should exist.

  4) What happened instead
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency doesn't exist.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-09-22 (1047 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: linux-image-5.15.0-43-generic 5.15.0-43.46~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Tags:  focal
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-20 (836 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd microk8s plugdev 
sambashare sbuild sudo
  _MarkForUpload: True

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


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

[Kernel-packages] [Bug 1998154] Re: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive

[Shih-Yuan Lee]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

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

Title:
  dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under
  universe archive

Status in OEM Priority Project:
  New
Status in dkms package in Ubuntu:
  New

Bug description:
  [Description]

  The latest dkms(2.8.7-2ubuntu2.1) depends on gcc-12 which is in
  universe archive.

  https://packages.ubuntu.com/search?keywords=gcc-12
  gcc-12 is under main for kinect, and the patches are cherry-picked from 
kinect/stable, I suppose it is a mistake for jammy in universe.

  [debian/changelog]

  dkms (2.8.7-2ubuntu2.1) jammy; urgency=medium

  Cherry-pick patches from kinetic/stable to address building dkms
  modules correctly for HWE kernels (LP: #1991664):

  Fix dkms-autopkgtest when a given dkms package is built into the
  kernel already of the same version. (i.e. zfs-linux on Ubuntu).

  Use exact compiler for dkms as used to build the kernel, when
  possible.

  Depend on gcc-12 to build modules for HWE kernels correctly.

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


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

[Kernel-packages] [Bug 2002763] Re: Missing how to uninstall (back to generic kernel) in OEMKernel wiki

[Shih-Yuan Lee]

Dell Precision 5560 is managed by oem-somerville-pidgey-meta.
Dell XPS 13 9310 is managed by oem-somerville-bulbasaur-meta.

You can simply purge those Debian packages and then reboot the system to use 
the generic kernel.
`sudo apt-get purge oem-somerville-pidgey-meta` or `sudo apt-get purge 
oem-somerville-bulbasaur-meta`.

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

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

Title:
  Missing how to uninstall (back to generic kernel) in OEMKernel wiki

Status in linux-oem-5.10 package in Ubuntu:
  Invalid

Bug description:
  In OEMKernel wiki(https://wiki.ubuntu.com/Kernel/OEMKernel), How to install 
is documented, but how to uninstall OEMKernel or back to the generic kernel?
  It's not documented.

  Maybe that's why this issue is fired:
  https://ubuntuforums.org/showthread.php?t=2470860

  And I also take almost harf an hour to search and still cannot find
  how to back to the generic kernel.

  Here is my case:
  Confirmed with HighPoint just now, their Linux driver cann't support OEM 
Kernel currently. So I want to back to the generic kernel. But how? shoudn't be 
documented in Wiki?

  Thanks!

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


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

[Kernel-packages] [Bug 2007875] Re: Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently

[Shih-Yuan Lee]

** Changed in: oem-somerville-tentacool-meta (Ubuntu Jammy)
   Status: Confirmed => Invalid

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

Title:
  Ubuntu 22.04 XPS 13 plus 9320  kernel 6.0 OEM and 5.19 breaks wifi
  frequently

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in oem-somerville-tentacool-meta package in Ubuntu:
  Invalid
Status in linux-firmware source package in Jammy:
  Fix Released
Status in oem-somerville-tentacool-meta source package in Jammy:
  Invalid
Status in linux-firmware source package in Kinetic:
  Fix Released
Status in oem-somerville-tentacool-meta source package in Kinetic:
  Invalid
Status in linux-firmware source package in Lunar:
  Fix Released
Status in oem-somerville-tentacool-meta source package in Lunar:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  backport-iwlwifi-dkms/kinetic is being built into hwe-5.19 kernel, and
  -73 firmware are supported bug missing. On one user reported issue,
  this fixes WiFi stability on 5G band.

  [Fix]

  New upstreamed firmware revision fixes this issue.

  [Test Case]

  1. Boot hwe-5.19 kernel
  2. iwlwifi-so-a0-gf-a0-73.ucode firmware should be loaded
  3. Browse the web, usually takes between 1 and 5 minutes
  4. Networking will cut out

  [Where problems could occur]

  This affects only users need both backport-iwlwifi-dkms and hwe-5.19
  kernel on WiFi stability.

  [Other Info]

  While Kinetic and above have them all, only Jammy is nominated.

  == original bug report ==

  I'm using the stock Dell Ubuntu 22.04 image on my XPS 13 Plus (9320).
  Recently I received some kernel updates, the 5.19 kernel used in 22.10
  and a 6.0 oem kernel. Both updates break wifi. It seems to only do so
  on newer 5.7 GHz access points.

  1. Boot latest 6.0 oem kernel
  2. Browse the web, usually takes between 1 and 5 minutes.
  3. Networking will cut out.

  Disabling networking and starting again will fix it until it happens
  again in a few minutes. This will repeat indefinitely, essentially
  making wireless useless.

  The attached dmesg log reliably shows up when it fails, showing
  iwlwifi failing and a (network?) hardware reset request.

  It witnessed this happen months ago on 22.10, which led me to using
  the Dell stock 22.04 image. But it seems even the newer OEM kernel is
  affected.

  A workaround is to select the older 5.15 kernel in grub. I find on
  this laptop, one must hit escape precisely 1 second after seeing the
  Dell logo on boot. Alternatively one could edit /etc/grub/default and
  set a longer timeout.

  Let me know if this bug report would be better to go to Dell as a
  support request instead.

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


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

[Kernel-packages] [Bug 2060914] Re: kernel NULL pointer dereference in ipu6 driver

[Shih-Yuan Lee]

** Also affects: oem-priority
   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/2060914

Title:
  kernel NULL pointer dereference in ipu6 driver

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  pr 11 14:43:43 OCBYM2-DVT1-C3 kernel: BUG: kernel NULL pointer dereference, 
address: 
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: #PF: supervisor read access in kernel 
mode
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: #PF: error_code(0x) - not-present 
page
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: PGD 0 P4D 0 
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: Oops:  [#1] PREEMPT SMP NOPTI
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: CPU: 16 PID: 568 Comm: (udev-worker) 
Tainted: G   O   6.8.0-22-generic #22-Ubuntu
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: Hardware name: Dell Inc. Precision 
5490/, BIOS 1.1.0 02/07/2024
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RIP: 0010:__wake_up_common+0x2f/0xb0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: Code: 55 48 89 e5 41 57 41 56 41 55 41 
54 53 48 89 fb 48 83 c3 08 48 83 ec 08 48 8b 47 08 89 75 d4 89 55 d0 48 39 c3 
74 51 4d 89 c7 <4c> 8b 00 41 89 ce 48 8d 78 e8 4d 8d 68 e8 eb 25 74 0c 41 83 e4 
01
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RSP: 0018:b5ebc3063768 EFLAGS: 
00010086
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RAX:  RBX: 
8fb79e181d50 RCX: 
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RDX:  RSI: 
0003 RDI: 8fb79e181d48
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RBP: b5ebc3063798 R08: 
 R09: 
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: R10:  R11: 
 R12: 8fb79e181d48
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: R13: 0003 R14: 
0246 R15: 
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: FS:  77cceb6148c0() 
GS:8fc6cf60() knlGS:
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: CR2:  CR3: 
0001068ae003 CR4: 00f70ef0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: DR0:  DR1: 
 DR2: 
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: DR3:  DR6: 
07f0 DR7: 0400
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: PKRU: 5554
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: Call Trace:
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? show_regs+0x6d/0x80
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? __die+0x24/0x80
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? page_fault_oops+0x99/0x1b0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? do_user_addr_fault+0x2ee/0x6b0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? exc_page_fault+0x83/0x1b0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? asm_exc_page_fault+0x27/0x30
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? __wake_up_common+0x2f/0xb0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  __wake_up+0x37/0x70
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  __vb2_queue_cancel+0xcd/0x300 
[videobuf2_common]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  vb2_core_queue_release+0x23/0x70 
[videobuf2_common]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  vb2_queue_release+0xe/0x20 
[videobuf2_v4l2]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ipu_isys_queue_cleanup+0x12/0x20 
[intel_ipu6_isys]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ipu_isys_video_cleanup+0x2e/0x40 
[intel_ipu6_isys]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  
ipu_isys_csi2_be_soc_cleanup+0x37/0x50 [intel_ipu6_isys]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  isys_unregister_subdevices+0x40/0xa0 
[intel_ipu6_isys]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  isys_probe+0x5c5/0xb80 
[intel_ipu6_isys]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? kernfs_create_link+0x66/0xe0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ipu_bus_probe+0x72/0x130 [intel_ipu6]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  really_probe+0x1c4/0x410
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  __driver_probe_device+0x8c/0x180
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  driver_probe_device+0x24/0xd0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  __driver_attach+0x10b/0x210
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? __pfx___driver_attach+0x10/0x10
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  bus_for_each_dev+0x8a/0xf0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  driver_attach+0x1e/0x30
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  bus_add_driver+0x156/0x260
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  driver_register+0x5e/0x130
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? __pfx_isys_driver_init+0x10/0x10 
[intel_ipu6_isys]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ipu_bus_register_driver+0x16/0x20 
[intel_ipu6]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: