date:20171215

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

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

Title:
  linux: 4.4.0-105.128 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1737918,1737919
  derivatives: 1737920,1737921,1737922,1737923,1737925,1737927
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Thursday, 14. December 2017 12:03 UTC

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1737911] Re: linux: 3.13.0-138.187 -proposed tracker

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

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

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

Title:
  linux: 3.13.0-138.187 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

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

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

  backports: 1737913
  derivatives:
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Wednesday, 13. December 2017 14:33 UTC

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1738334] Re: hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add io_mem_pfn callback")

2017-12-15 Thread Zhanglei Mao

This patch need to merged and fixed for the release 16.04.04. The final
SRU4 windows is 8 Dec. to 6 Jan 2018.

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

Title:
  hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add
  io_mem_pfn callback")

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ea642c3216cb ("drm/ttm: add io_mem_pfn callback") is incomplete: the
  hisilicon hibmc driver does not contain the callback and so X does not
  start.

  Discussion and potential fix at https://lists.freedesktop.org/archives
  /dri-devel/2017-November/159002.html

  This affects Artful, upstream has not landed on a solution yet as far
  as I can tell, so lets backport the first proposed small fix.

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

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

[Kernel-packages] [Bug 1737934] Re: Samsung SM961 NVMe SSD randomly unmounts/loses connection/unavailable

2017-12-15 Thread Lode Lesage

Here you go:

sudo nvme id-ctrl /dev/nvme0
NVME Identify Controller:
vid : 0x144d
ssvid   : 0x144d
sn  : S35ENX0JA13385  
mn  : SAMSUNG MZVLW256HEHP-000L7  
fr  : 4L7QCXB7
rab : 2
ieee: 002538
cmic: 0
mdts: 0
cntlid  : 2
ver : 10200
rtd3r   : 186a0
rtd3e   : 4c4b40
oaes: 0
oacs: 0x17
acl : 7
aerl: 3
frmw: 0x16
lpa : 0x3
elpe: 63
npss: 4
avscc   : 0x1
apsta   : 0x1
wctemp  : 342
cctemp  : 345
mtfa: 0
hmpre   : 0
hmmin   : 0
tnvmcap : 256060514304
unvmcap : 0
rpmbs   : 0
sqes: 0x66
cqes: 0x44
nn  : 1
oncs: 0x1f
fuses   : 0
fna : 0x4
vwc : 0x1
awun: 255
awupf   : 0
nvscc   : 1
acwu: 0
sgls: 0
subnqn  : 
ps0 : mp:7.60W operational enlat:0 exlat:0 rrt:0 rrl:0
  rwt:0 rwl:0 idle_power:- active_power:-
ps1 : mp:6.00W operational enlat:0 exlat:0 rrt:1 rrl:1
  rwt:1 rwl:1 idle_power:- active_power:-
ps2 : mp:5.10W operational enlat:0 exlat:0 rrt:2 rrl:2
  rwt:2 rwl:2 idle_power:- active_power:-
ps3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3
  rwt:3 rwl:3 idle_power:- active_power:-
ps4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4
  rwt:4 rwl:4 idle_power:- active_power:-

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

Title:
  Samsung SM961 NVMe SSD randomly unmounts/loses connection/unavailable

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Seems related to these bugs:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
  https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1682704
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748

  Problem:
  At seemingly random times my computer (brand new Lenovo Thinkpad T470) seems 
to lose access to the Samsung SM961 256GB SSD drive it has inside. When this 
happens the whole OS freezes up and when I try to power down I see a black 
terminal-like screen that prints the following errors:

  EXT4-fs error (device nvme0n1p2): ext4_find_entry:1431: inode #7471275
  (or #741278): comm gmain (or systemd-journal or ...): reading
  directory iblock 0

  This error seems to be repeated endlessly, though I've only let it go
  for a few minutes. No other errors are printed.

  This is the only drive it has.
  I don't know if this occurs in Windows too since I removed Windows and 
installed Ubuntu immediatly after updating the BIOS.

  Info:
  Distro: Ubuntu MATE 17.10

  sudo uname -r
  4.13.0-19-generic

  sudo nvme get-feature -f 0x0c -H /dev/nvme0 (with latency set to 250)
  get-feature:0xc (Autonomous Power State Transition), Current value:0x01
Autonomous Power State Transition Enable (APSTE): Enabled
Auto PST Entries.
Entry[ 0]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 1]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 2]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 3]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 4]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 5]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 6]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 7]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 8]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 9]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[10]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[11]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entr

[Kernel-packages] [Bug 1738334] Re: hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add io_mem_pfn callback")

2017-12-15 Thread Zhanglei Mao

Notes and some more detail for this bug/patch:

The bug is from/caused by 4.12 DRM architecture,  the main line  commit
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v4.15-rc3&id=ea642c3216cb2a60d1c0e760ae47ee85c9c16447

It will cause x-window start hanged, the detail bug are
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1698700

The fix path link are here: https://lists.freedesktop.org/archives/dri-
devel/2017-November/159002.html

This patch only change Huawei driver, it will not affect any other
vendors.

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

Title:
  hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add
  io_mem_pfn callback")

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ea642c3216cb ("drm/ttm: add io_mem_pfn callback") is incomplete: the
  hisilicon hibmc driver does not contain the callback and so X does not
  start.

  Discussion and potential fix at https://lists.freedesktop.org/archives
  /dri-devel/2017-November/159002.html

  This affects Artful, upstream has not landed on a solution yet as far
  as I can tell, so lets backport the first proposed small fix.

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

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

[Kernel-packages] [Bug 1737934] Re: Samsung SM961 NVMe SSD randomly unmounts/loses connection/unavailable

2017-12-15 Thread Kai-Heng Feng

Can you try "nvme_core.default_ps_max_latency_us=1500"? This will
disable ps4, which causes lots of troubles.

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

Title:
  Samsung SM961 NVMe SSD randomly unmounts/loses connection/unavailable

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Seems related to these bugs:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
  https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1682704
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748

  Problem:
  At seemingly random times my computer (brand new Lenovo Thinkpad T470) seems 
to lose access to the Samsung SM961 256GB SSD drive it has inside. When this 
happens the whole OS freezes up and when I try to power down I see a black 
terminal-like screen that prints the following errors:

  EXT4-fs error (device nvme0n1p2): ext4_find_entry:1431: inode #7471275
  (or #741278): comm gmain (or systemd-journal or ...): reading
  directory iblock 0

  This error seems to be repeated endlessly, though I've only let it go
  for a few minutes. No other errors are printed.

  This is the only drive it has.
  I don't know if this occurs in Windows too since I removed Windows and 
installed Ubuntu immediatly after updating the BIOS.

  Info:
  Distro: Ubuntu MATE 17.10

  sudo uname -r
  4.13.0-19-generic

  sudo nvme get-feature -f 0x0c -H /dev/nvme0 (with latency set to 250)
  get-feature:0xc (Autonomous Power State Transition), Current value:0x01
Autonomous Power State Transition Enable (APSTE): Enabled
Auto PST Entries.
Entry[ 0]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 1]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 2]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 3]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 4]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 5]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 6]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 7]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 8]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 9]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[10]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[11]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[12]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[13]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[14]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[15]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[16]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[17]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[18]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0

[Kernel-packages] [Bug 1737911] Re: linux: 3.13.0-138.187 -proposed tracker

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

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

Title:
  linux: 3.13.0-138.187 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

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

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

  backports: 1737913
  derivatives:
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Wednesday, 13. December 2017 14:33 UTC

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1737934] Re: Samsung SM961 NVMe SSD randomly unmounts/loses connection/unavailable

2017-12-15 Thread Lode Lesage

I tried it but the problem happened again, twice, quite quickly after
booting.

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

Title:
  Samsung SM961 NVMe SSD randomly unmounts/loses connection/unavailable

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Seems related to these bugs:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
  https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1682704
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748

  Problem:
  At seemingly random times my computer (brand new Lenovo Thinkpad T470) seems 
to lose access to the Samsung SM961 256GB SSD drive it has inside. When this 
happens the whole OS freezes up and when I try to power down I see a black 
terminal-like screen that prints the following errors:

  EXT4-fs error (device nvme0n1p2): ext4_find_entry:1431: inode #7471275
  (or #741278): comm gmain (or systemd-journal or ...): reading
  directory iblock 0

  This error seems to be repeated endlessly, though I've only let it go
  for a few minutes. No other errors are printed.

  This is the only drive it has.
  I don't know if this occurs in Windows too since I removed Windows and 
installed Ubuntu immediatly after updating the BIOS.

  Info:
  Distro: Ubuntu MATE 17.10

  sudo uname -r
  4.13.0-19-generic

  sudo nvme get-feature -f 0x0c -H /dev/nvme0 (with latency set to 250)
  get-feature:0xc (Autonomous Power State Transition), Current value:0x01
Autonomous Power State Transition Enable (APSTE): Enabled
Auto PST Entries.
Entry[ 0]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 1]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 2]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 3]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 4]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 5]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 6]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 7]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 8]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 9]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[10]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[11]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[12]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[13]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[14]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[15]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[16]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[17]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[18]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[19]

[Kernel-packages] [Bug 1737934] Re: Samsung SM961 NVMe SSD randomly unmounts/loses connection/unavailable

2017-12-15 Thread Kai-Heng Feng

Sorry, I re-read your bug description, do have the same issue on
"nvme_core.default_ps_max_latency_us=0", which disable APST completely?

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

Title:
  Samsung SM961 NVMe SSD randomly unmounts/loses connection/unavailable

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Seems related to these bugs:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
  https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1682704
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748

  Problem:
  At seemingly random times my computer (brand new Lenovo Thinkpad T470) seems 
to lose access to the Samsung SM961 256GB SSD drive it has inside. When this 
happens the whole OS freezes up and when I try to power down I see a black 
terminal-like screen that prints the following errors:

  EXT4-fs error (device nvme0n1p2): ext4_find_entry:1431: inode #7471275
  (or #741278): comm gmain (or systemd-journal or ...): reading
  directory iblock 0

  This error seems to be repeated endlessly, though I've only let it go
  for a few minutes. No other errors are printed.

  This is the only drive it has.
  I don't know if this occurs in Windows too since I removed Windows and 
installed Ubuntu immediatly after updating the BIOS.

  Info:
  Distro: Ubuntu MATE 17.10

  sudo uname -r
  4.13.0-19-generic

  sudo nvme get-feature -f 0x0c -H /dev/nvme0 (with latency set to 250)
  get-feature:0xc (Autonomous Power State Transition), Current value:0x01
Autonomous Power State Transition Enable (APSTE): Enabled
Auto PST Entries.
Entry[ 0]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 1]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 2]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 3]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 4]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 5]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 6]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 7]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 8]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 9]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[10]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[11]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[12]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[13]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[14]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[15]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[16]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[17]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[18]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS):

[Kernel-packages] [Bug 1737934] Re: Samsung SM961 NVMe SSD randomly unmounts/loses connection/unavailable

2017-12-15 Thread Lode Lesage

No problem, I am very grateful for your help!

As I said in the "What have I tried"-section (sorry if it got lost in
all the info, I tried to give as much as possible), yes I have tried
that and yes I have the same problem. It seems to be worse actually when
I put 0 as latency.

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

Title:
  Samsung SM961 NVMe SSD randomly unmounts/loses connection/unavailable

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Seems related to these bugs:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
  https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1682704
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748

  Problem:
  At seemingly random times my computer (brand new Lenovo Thinkpad T470) seems 
to lose access to the Samsung SM961 256GB SSD drive it has inside. When this 
happens the whole OS freezes up and when I try to power down I see a black 
terminal-like screen that prints the following errors:

  EXT4-fs error (device nvme0n1p2): ext4_find_entry:1431: inode #7471275
  (or #741278): comm gmain (or systemd-journal or ...): reading
  directory iblock 0

  This error seems to be repeated endlessly, though I've only let it go
  for a few minutes. No other errors are printed.

  This is the only drive it has.
  I don't know if this occurs in Windows too since I removed Windows and 
installed Ubuntu immediatly after updating the BIOS.

  Info:
  Distro: Ubuntu MATE 17.10

  sudo uname -r
  4.13.0-19-generic

  sudo nvme get-feature -f 0x0c -H /dev/nvme0 (with latency set to 250)
  get-feature:0xc (Autonomous Power State Transition), Current value:0x01
Autonomous Power State Transition Enable (APSTE): Enabled
Auto PST Entries.
Entry[ 0]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 1]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 2]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 3]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 4]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 5]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 6]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 7]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 8]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 9]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[10]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[11]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[12]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[13]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[14]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[15]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[16]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[17]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.

[Kernel-packages] [Bug 1738334] Re: hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add io_mem_pfn callback")

2017-12-15 Thread Daniel Axtens

** Description changed:

- ea642c3216cb ("drm/ttm: add io_mem_pfn callback") is incomplete: the
- hisilicon hibmc driver does not contain the callback and so X does not
- start.
+ [SRU Justification]
  
- Discussion and potential fix at https://lists.freedesktop.org/archives
- /dri-devel/2017-November/159002.html
+ [Impact]
+ On Artful kernels, X fails to start and a kernel splat is printed.
  
- This affects Artful, upstream has not landed on a solution yet as far as
- I can tell, so lets backport the first proposed small fix.
+ This is cbecause ea642c3216cb ("drm/ttm: add io_mem_pfn callback") is
+ incomplete: the hisilicon hibmc driver does not contain the callback and
+ so the kernel tries to execute code at NULL.
+ 
+ [Fix]
+ There is a discussion and potential fix at 
https://lists.freedesktop.org/archives/dri-devel/2017-November/159002.html The 
fix hasn't landed yet and it looks like they're going to re-engineer the entire 
section instead.
+ 
+ Rather than wait for that and deal with the massive regression
+ potential, the fix I have picked to submit is very very minimal and
+ touches only hibmc.
+ 
+ [Regression Potential]
+ Minimal - fix only touches hibmc driver. Tested on D05 board.
+ 
+ [Testcase]
+ Install patched kernel, try to start X. If it succeeds, the fix works. If 
there's a kernel splat, the fix does not work.
+ 
+ [Notes]
+ HiSilicon would really like this fix in Artful in such time so that when the 
next 16.04 point release ships in February, the HWE kernel will work with Xorg.

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

Title:
  hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add
  io_mem_pfn callback")

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [SRU Justification]

  [Impact]
  On Artful kernels, X fails to start and a kernel splat is printed.

  This is cbecause ea642c3216cb ("drm/ttm: add io_mem_pfn callback") is
  incomplete: the hisilicon hibmc driver does not contain the callback
  and so the kernel tries to execute code at NULL.

  [Fix]
  There is a discussion and potential fix at 
https://lists.freedesktop.org/archives/dri-devel/2017-November/159002.html The 
fix hasn't landed yet and it looks like they're going to re-engineer the entire 
section instead.

  Rather than wait for that and deal with the massive regression
  potential, the fix I have picked to submit is very very minimal and
  touches only hibmc.

  [Regression Potential]
  Minimal - fix only touches hibmc driver. Tested on D05 board.

  [Testcase]
  Install patched kernel, try to start X. If it succeeds, the fix works. If 
there's a kernel splat, the fix does not work.

  [Notes]
  HiSilicon would really like this fix in Artful in such time so that when the 
next 16.04 point release ships in February, the HWE kernel will work with Xorg.

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

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

[Kernel-packages] [Bug 1737918] Re: linux-aws: 4.4.0-1007.7 -proposed tracker

2017-12-15 Thread Thadeu Lima de Souza Cascardo

** Summary changed:

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

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de 
Souza Cascardo (cascardo)

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de 
Souza Cascardo (cascardo)

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

Title:
  linux-aws: 4.4.0-1007.7 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1737916
  phase: Packaging

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

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

[Kernel-packages] [Bug 1737920] Re: linux-aws: 4.4.0-1045.54 -proposed tracker

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

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

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

Title:
  linux-aws: 4.4.0-1045.54 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1737916
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1737920] Re: linux-aws: 4.4.0-1045.54 -proposed tracker

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

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

Title:
  linux-aws: 4.4.0-1045.54 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1737916
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-15 Thread fardin behboud

in answer to post #120

I am not affected by ubuntu 17.1 
I got affected by ubuntu 18.04(developers version).
in fact i start to install it 4 hours after release.
if there is a problem in ubuntu 17.1 development then it is logical also for 
18.04 users.

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

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

Bug description:
  Hi all,

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

   UPDATE (01/12/2017) 

  LENOVO machines affected so far (please add your affected model to
  this list):

  Lenovo Y50-70
  Lenovo G40-30
  Lenovo U31-70
  Lenovo G50-70
  Lenovo Z50-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo G50-80
  Lenovo S20-30
  Lenovo Yoga 2 11" - 20332
  Lenovo B40-70
  Lenovo Z51-70
  Lenovo B50-70
  Lenovo Flex-10

  The bug also affects Acer Aspire E5-771G.

  ---

  Temporary workaround:
  https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t
  -Save-Settings-Or-Exit/m-p/3853208#M157885

  ---

  result from apport-collect 1734147:

  ---

  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tob1608 F pulseaudio
   /dev/snd/controlC0:  tob1608 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO

  ---

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

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

[Kernel-packages] [Bug 1638862] Re: [Dell Latitude E5460] bluetooth is not supported on 16.04.1.

2017-12-15 Thread highvolt

I had the same issue, and used the sfi file from the windows version.
The main issue is that your card is revision 4 and the linux-firmware only has 
the firmware for revision 5.

You only need to decompress the file and copy the two files into
/lib/firmware/intel and perform an hard reboot. And bluetooth should
start working right away.

Anyone knows whats the best way to get these files pushed to mainline
linux-firmware package?



** Attachment added: "sfi and ddc file from windows driver"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638862/+attachment/5022965/+files/ibt-11-4.tar.xz

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

Title:
  [Dell Latitude E5460] bluetooth is not supported on 16.04.1.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dell Latitude E5460 (CID 201507-18776)

  Ubuntu 16.04.1
  (updated to kernel 4.4.0-45-generic)

  [Steps to reproduce]
  1. Install Ubuntu 16.04.1 via Live USB.
  2. On desktop, open the terminal to issue the command to check the status[1].
  3. Open Bluetooth setup window.
  4. Update the system and do the same steps from 1~3.

  [Expected Result]
  Bluetooth setup window is ready for you to setup bluetooth devices.

  [Actual Result]
  The bluetooth setup window shows "Bluetooth is disabled".


  [1]

  ubuntu@201507-18776:~$ rfkill list
  0: hci0: Bluetooth
   Soft blocked: no
   Hard blocked: no
  1: dell-wifi: Wireless LAN
   Soft blocked: no
   Hard blocked: no
  2: dell-bluetooth: Bluetooth
   Soft blocked: no
   Hard blocked: no
  3: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: no

  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-45-generic 4.4.0-45.66
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1523 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Nov  3 17:56:50 2016
  HibernationDevice: RESUME=UUID=e104534d-b5db-4ef1-9955-2b8178924bcb
  InstallationDate: Installed on 2016-11-02 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Latitude E5470
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=a02ea97e-ff66-470f-aa17-74a60670faa1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.157.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.6
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.6:bd01/10/2016:svnDellInc.:pnLatitudeE5470:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5470
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1738219] Re: the kernel is blackholing IPv6 packets to linkdown nexthops

2017-12-15 Thread Saverio Proto

I tested the packages on Xenial:

; uname -a
Linux s0006 4.4.0-103-generic #126~lp1738219 SMP Thu Dec 14 16:37:03 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

It LGTM. The bug is fixed when using this kernel.

thank you

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

Title:
  the kernel is blackholing IPv6 packets to linkdown nexthops

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  When the 'ignore_routes_with_linkdown' sysctl is set, we should not
  consider linkdown nexthops during route lookup.

  While the code correctly verifies that the initially selected route
  ('match') has a carrier, it does not perform the same check in the
  subsequent multipath selection, resulting in a potential packet loss.

  In case the chosen route does not have a carrier and the sysctl is set,
  choose the initially selected route.

  Fixed in the upstream kernel with patch:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bbfcd77631573ac4a9f57eb6169e04256a111bc1

  I think this patch must be backported to stable kernel in Xenial. I
  tested in patching the Ubuntu Xenial 4.4.0-21-generic and it works for
  me.

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

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

[Kernel-packages] [Bug 1737916] Re: linux: 4.4.0-105.128 -proposed tracker

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

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

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

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

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

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1737918,1737919
  derivatives: 1737920,1737921,1737922,1737923,1737925,1737927
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Thursday, 14. December 2017 12:03 UTC
- 
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Friday, 15. December 2017 12:33 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1737918,1737919
  derivatives: 1737920,1737921,1737922,1737923,1737925,1737927
  -- swm properties --
  boot-testing-requested: true
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Friday, 15. December 2017 12:33 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux: 4.4.0-105.128 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1737918,1737919
  derivatives: 1737920,1737921,1737922,1737923,1737925,1737927
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1737916] Re: linux: 4.4.0-105.128 -proposed tracker

2017-12-15 Thread Steve Beattie

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

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux: 4.4.0-105.128 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1737918,1737919
  derivatives: 1737920,1737921,1737922,1737923,1737925,1737927
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1737913] Re: linux-lts-trusty: 3.13.0-138.187~precise1 -proposed tracker

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

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

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

Title:
  linux-lts-trusty: 3.13.0-138.187~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1737911
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1737918] Re: linux-aws: 4.4.0-1007.7 -proposed tracker

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1737916
  phase: Packaging
+ kernel-stable-phase-changed:Friday, 15. December 2017 13:33 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1737916
- phase: Packaging
- kernel-stable-phase-changed:Friday, 15. December 2017 13:33 UTC
- kernel-stable-phase:Uploaded
+ phase: Uploaded

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

Title:
  linux-aws: 4.4.0-1007.7 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1737916
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1737640] Re: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures

2017-12-15 Thread Narinder Gupta

The workaround by adding the proposed repository into package
repositories in MAAS worked for me.

** Also affects: opnfv
   Importance: Undecided
   Status: New

** Changed in: opnfv
   Status: New => Fix Committed

** Changed in: opnfv
   Importance: Undecided => Critical

** Changed in: opnfv
 Assignee: (unassigned) => Narinder Gupta (narindergupta)

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

Title:
  /usr/sbin/fanctl: arithmetic expression: expecting primary |
  unconfigured interfaces cause ifup failures

Status in juju:
  Triaged
Status in OPNFV:
  Fix Committed
Status in ubuntu-fan package in Ubuntu:
  Confirmed
Status in ubuntu-fan source package in Xenial:
  Fix Committed

Bug description:
  I'm seeing this error as the status of multiple containers in my
  deploy:

  http://paste.ubuntu.com/26166720/

  I can't connect to the parent machines anymore either - it seems
  networking is totally hosed on the machines.

  This is with juju 2.3.1.

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

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

[Kernel-packages] [Bug 1738263] Re: Touchpad not working and locking CPU

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

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

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

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

Title:
  Touchpad not working and locking CPU

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Notebook: ASUS GL703VD
  Touchpad: probably ELAN clickpad

  it seems to be connected to i2c bus

  the modules loaded are elan_i2c and multitouch_hid

  the multitouch hid module take almost 100% of cpu and the mouse cursor
  moves badly (loosing it for a second or 2 then resuming) also feature
  clicks and doubleclicks and sensitivity problems.

  doing rmmod hid-multitouch.ko (or rmmod multitouch_hid) and
  blacklisting the module solves the cpu problem but obviously the
  touchoad is dead.

  SEVERITY VERY HIGH
  It probably affects many other ASUS models.

  (the touchpad works perfectly in windows 10 by the way)

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

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

[Kernel-packages] [Bug 1737911] Re: linux: 3.13.0-138.187 -proposed tracker

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

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

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

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1737913
  derivatives:
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Wednesday, 13. December 2017 14:33 UTC
- 
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Friday, 15. December 2017 14:33 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1737913
  derivatives:
  -- swm properties --
  boot-testing-requested: true
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Friday, 15. December 2017 14:33 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux: 3.13.0-138.187 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

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

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

  backports: 1737913
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1737920] Re: linux-aws: 4.4.0-1045.54 -proposed tracker

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

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

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

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

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

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1737916
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Friday, 15. December 2017 14:30 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1737916
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Friday, 15. December 2017 14:30 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux-aws: 4.4.0-1045.54 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1737916
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1738067] Re: cfg80211 crashes when trying to connect to encrypted access point

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.15 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc3


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

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

Title:
  cfg80211 crashes when trying to connect to encrypted access point

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am using Xubuntu 16.04 with the latest software.

  # Steps to reproduce

  1. Select specific access point in the dropdown menu of the default graphical 
network manager’s “indicator”.
  2. Enter WiFi encryption password.

  # What I expected

  A connection to the access point is established.

  # What happened instead

  1. Wait a few seconds.
  2. The window for password entry opened.
  3. After entering the password again, go to 1.

  I checked `dmesg`. This is what it reported to me:

  [  539.742755] [ cut here ]
  [  539.742780] WARNING: CPU: 0 PID: 6 at 
/build/linux-yM3O3R/linux-4.4.0/net/wireless/sme.c:728 
__cfg80211_connect_result+0x3b2/0x420 [cfg80211]()
  [  539.742781] Modules linked in: rfcomm bnep rtsx_usb_ms memstick dell_wmi 
sparse_keymap dell_laptop dcdbas dell_smm_hwmon snd_hda_codec_hdmi 
snd_hda_codec_conexant snd_hda_codec_generic snd_hda_intel snd_hda_codec 
snd_hda_core snd_hwdep snd_pcm btusb btrtl btbcm btintel bluetooth intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp snd_seq_midi snd_seq_midi_event 
wl(POE) kvm_intel uvcvideo kvm snd_rawmidi videobuf2_vmalloc videobuf2_memops 
irqbypass videobuf2_v4l2 videobuf2_core v4l2_common input_leds videodev joydev 
serio_raw media snd_seq snd_seq_device snd_timer cfg80211 snd soundcore shpchp 
lpc_ich mei_me mei mac_hid dell_smo8800 parport_pc ppdev lp parport autofs4 
drbg ansi_cprng algif_skcipher af_alg dm_crypt rtsx_usb_sdmmc rtsx_usb 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel
  [  539.742818]  i915 aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd 
i2c_algo_bit drm_kms_helper syscopyarea psmouse sysfillrect sysimgblt 
fb_sys_fops drm ahci r8169 libahci mii wmi video fjes
  [  539.742831] CPU: 0 PID: 6 Comm: kworker/u16:0 Tainted: PW  OE   
4.4.0-103-generic #126-Ubuntu
  [  539.742832] Hardware name: Dell Inc. Vostro 3560/05GV6H, BIOS A07 
05/17/2012
  [  539.742843] Workqueue: cfg80211 cfg80211_event_work [cfg80211]
  [  539.742844]  0286 b07824d3e76384b6 880149c1fca0 
813fb523
  [  539.742847]   c03faf30 880149c1fcd8 
810812e2
  [  539.742849]  8801472b7800   
8801470bb000
  [  539.742851] Call Trace:
  [  539.742856]  [] dump_stack+0x63/0x90
  [  539.742859]  [] warn_slowpath_common+0x82/0xc0
  [  539.742861]  [] warn_slowpath_null+0x1a/0x20
  [  539.742874]  [] __cfg80211_connect_result+0x3b2/0x420 
[cfg80211]
  [  539.742885]  [] cfg80211_process_wdev_events+0x13f/0x1b0 
[cfg80211]
  [  539.742895]  [] cfg80211_process_rdev_events+0x32/0x70 
[cfg80211]
  [  539.742904]  [] cfg80211_event_work+0x1e/0x30 [cfg80211]
  [  539.742908]  [] process_one_work+0x165/0x480
  [  539.742910]  [] worker_thread+0x4b/0x4d0
  [  539.742912]  [] ? process_one_work+0x480/0x480
  [  539.742914]  [] kthread+0xe5/0x100
  [  539.742916]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [  539.742921]  [] ret_from_fork+0x3f/0x70
  [  539.742922]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [  539.742924] ---[ end trace 447e5e9ec93ecc5d ]---

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

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

[Kernel-packages] [Bug 1730550] Re: e1000e in 4.4.0-97-generic breaks 82574L under heavy load.

2017-12-15 Thread Iain Buclaw

Thanks.

By the way, also confirming that the patch works here (have been running
the patched kernel for 3 days now). Running on hardware Super Micro
X9SCL with an Intel 82574L NIC.

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

Title:
  e1000e in 4.4.0-97-generic breaks 82574L under heavy load.

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  In Progress

Bug description:
  
  == SRU Justification ==
  This issue was first reported on the netdev email list by Lennart Sorensen:
  https://www.mail-archive.com/netdev@vger.kernel.org/msg178170.html

  Commit 16ecba59bc333d6282ee057fb02339f77a880beb causes link drops on
  the 82574L under heavy load.

  "Unfortunately this commit changed the driver to assume
  that the Other Causes interrupt can only mean link state change and
  hence sets the flag that (unfortunately) means both link is down and link
  state should be checked. Since this now happens 3000 times per second,
  the chances of it happening while the watchdog_task is checking the link
  state becomes pretty high, and it if does happen to coincice, then the
  watchdog_task will reset the adapter, which causes a real loss of link."

  The original reported experienced this issue on a Supermicro X7SPA-HF-D525 
server board. 
  However, the bug is now seen on many servers running X9DBL-1F server boards. 

  This bug is fixed by commits 19110cfbb34 and 4aea7a5c5e9, which were both 
added
  to mainline in v4.15-rc1.

  The commit that introduced this bug,16ecba5, was added to mainlien in 
v4.5-rc1.  However,
  Xenial recived this commit as well as commit 531ff577a.  Bionic master-next 
does not need
  these commits, since it got them via bug 1735843 and the 4.14.3 updates.

  == Fixes ==
  19110cfbb34 ("e1000e: Separate signaling for link check/link up")
  4aea7a5c5e9 ("e1000e: Avoid receiver overrun interrupt bursts")

  == Regression Potential ==
  These commits are specific to e1000.

  == Test Case ==
  A test kernel was built with these patches and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  == Original Bug Descriptio ==
  This issue was first reported on the netdev email list by Lennart Sorensen:
  https://www.mail-archive.com/netdev@vger.kernel.org/msg178170.html

  Commit 16ecba59bc333d6282ee057fb02339f77a880beb causes link drops on
  the 82574L under heavy load.

  "Unfortunately this commit changed the driver to assume
  that the Other Causes interrupt can only mean link state change and
  hence sets the flag that (unfortunately) means both link is down and link
  state should be checked.  Since this now happens 3000 times per second,
  the chances of it happening while the watchdog_task is checking the link
  state becomes pretty high, and it if does happen to coincice, then the
  watchdog_task will reset the adapter, which causes a real loss of link."

  A fix for this issue was accepted into the net-next branch, along with
  other e1000e/igb patches:
  https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-
  next.git/commit/?id=f44dea3421b47d355a835e9cfcc59ca7318575a9

  The original reported experienced this issue on a Supermicro X7SPA-
  HF-D525 server board. We see this issue on many servers running X9DBL-
  1F server boards. Both boards use the Intel 82574L for the network
  interfaces.  We see messages like this under heavy load:

  [Nov 6 15:42] e1000e: eth0 NIC Link is Down
  [  +0.001670] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [Nov 6 16:10] e1000e: eth0 NIC Link is Down
  [  +0.008505] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [Nov 7 00:49] e1000e: eth0 NIC Link is Down
  [  +2.235111] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx

  We have confirmed that the connected switch sees the link drops also,
  to these are not false alarms from the e1000e driver.

  # lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  I could not cleanly apply the net-next patch to 4.4.0 so I tested with just 
the following cherry picked changes on the latest 4.4.0 kernel source package.
  https://patchwork.ozlabs.org/patch/823942/
  https://patchwork.ozlabs.org/patch/823945/
  https://patchwork.ozlabs.org/patch/823940/
  https://patchwork.ozlabs.org/patch/823941/
  https://patchwork.ozlabs.org/patch/823939/

  Although it's my understanding the first two are the critical ones for
  the race condition. I have been running with the patches e1000e kernel
  driver, under network load for 7 days and I no longer see the network
  interface drops.

  Could we pull these changes into the Ubuntu 4.4.0 kernel ?

  Thanks
  ---
  AlsaDevices:
   total 0
   crw-rw 1

[Kernel-packages] [Bug 1738219] Re: the kernel is blackholing IPv6 packets to linkdown nexthops

SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2017-December/088930.html

** Description changed:

+ == SRU Justification ==
  When the 'ignore_routes_with_linkdown' sysctl is set, we should not
  consider linkdown nexthops during route lookup.
  
  While the code correctly verifies that the initially selected route
  ('match') has a carrier, it does not perform the same check in the
  subsequent multipath selection, resulting in a potential packet loss.
  
  In case the chosen route does not have a carrier and the sysctl is set,
  choose the initially selected route.
  
- Fixed in the upstream kernel with patch:
+ This is a regression introduced by commit 35103d11173b in 4.3-rc1.  Commit
+ bbfcd7763 resolves this regression and is mainline as of 4.15-rc1.
  
- 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bbfcd77631573ac4a9f57eb6169e04256a111bc1
+ == Fix ==
+ commit bbfcd77631573ac4a9f57eb6169e04256a111bc1
+ Author: Ido Schimmel 
+ Date:   Tue Nov 21 09:50:12 2017 +0200
  
- I think this patch must be backported to stable kernel in Xenial. I
- tested in patching the Ubuntu Xenial 4.4.0-21-generic and it works for
- me.
+ ipv6: Do not consider linkdown nexthops during multipath
+ 
+ == Regression Potential ==
+ This fix is specific to ipv6 and fixes a current regression.
+ 
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug 
reporter.
+ The bug reporter states the test kernel resolved the bug.

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

Title:
  the kernel is blackholing IPv6 packets to linkdown nexthops

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  == SRU Justification ==
  When the 'ignore_routes_with_linkdown' sysctl is set, we should not
  consider linkdown nexthops during route lookup.

  While the code correctly verifies that the initially selected route
  ('match') has a carrier, it does not perform the same check in the
  subsequent multipath selection, resulting in a potential packet loss.

  In case the chosen route does not have a carrier and the sysctl is set,
  choose the initially selected route.

  This is a regression introduced by commit 35103d11173b in 4.3-rc1.  Commit
  bbfcd7763 resolves this regression and is mainline as of 4.15-rc1.

  == Fix ==
  commit bbfcd77631573ac4a9f57eb6169e04256a111bc1
  Author: Ido Schimmel 
  Date:   Tue Nov 21 09:50:12 2017 +0200

  ipv6: Do not consider linkdown nexthops during multipath

  == Regression Potential ==
  This fix is specific to ipv6 and fixes a current regression.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

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

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

[Kernel-packages] [Bug 1734243] Please test proposed package

Hello AceLan, or anyone else affected,

Accepted linux-firmware into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.157.15 in a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

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

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

Title:
  Intel 9260/9462/9560 firmware support

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-firmware source package in Zesty:
  Fix Committed
Status in linux-firmware source package in Artful:
  Fix Committed

Bug description:
  SRU Justification
  [Impact]
  Intel 9260/9462/9560 require new firmwares to enable them.

  [ 7.492326] iwlwifi :00:0c.0: Direct firmware load for 
iwlwifi-9000-pu-a0-jf-b0-33.ucode failed with error -2
  [ 7.492349] iwlwifi :00:0c.0: Direct firmware load for 
iwlwifi-9000-pu-a0-jf-b0-32.ucode failed with error -2
  [ 7.492362] iwlwifi :00:0c.0: Direct firmware load for 
iwlwifi-9000-pu-a0-jf-b0-31.ucode failed with error -2
  [ 7.492375] iwlwifi :00:0c.0: Direct firmware load for 
iwlwifi-9000-pu-a0-jf-b0-30.ucode failed with error -2
  [ 7.492378] iwlwifi :00:0c.0: no suitable firmware found!

  For v4.13 kernel, it uses firmware version 33, so we only need this.

  commit c4276b65390d32d33c8263a7e3c8be0db8cccad4 (tag: 
refs/tags/iwlwifi-fw-2017-11-03)
  Author: Luca Coelho 
  Date:   Fri Oct 13 14:22:26 2017 +0300

  iwlwifi: add firmware version 33 for new 9000 series

  Build number: WFFW53774_R30_FW610294

  Revision number: 610294

  Signed-off-by: Luca Coelho 

  [Test Case]
  After applying the firmwares, confirm the 9260/9560 can connect to 6 
different APs(bg/n/ac * open/wap)

  [Regression Potential]
  There is no regression for the new devices and new firmwares.

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

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

[Kernel-packages] [Bug 1729389] Please test proposed package

Hello Jeppe, or anyone else affected,

Accepted linux-firmware into artful-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.169.2 in a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, details of your
testing will help us make a better decision.

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

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

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  New
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  New
Status in linux-firmware source package in Artful:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Bluetooth peripherals work initially but stop working shortly
  with Linux 4.13.

  Fix: Updated firmware from Intel containing a fix for the issue.

  Regression Potential: Any firmware updates may bring regressions,
  however this is a bug fix update and therefore regression potential is
  expected to be minimal.

  ---

  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  ---
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp.
   Bus 001 Device 005: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 13d3:5664 IMC Networks
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
    UP RUNNING PSCAN ISCAN INQUIRY
    RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
    TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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

[Kernel-packages] [Bug 1737911] Re: linux: 3.13.0-138.187 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   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/1737911

Title:
  linux: 3.13.0-138.187 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

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

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

  backports: 1737913
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1734243] Please test proposed package

Hello AceLan, or anyone else affected,

Accepted linux-firmware into artful-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.169.2 in a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, details of your
testing will help us make a better decision.

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

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

Title:
  Intel 9260/9462/9560 firmware support

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-firmware source package in Zesty:
  Fix Committed
Status in linux-firmware source package in Artful:
  Fix Committed

Bug description:
  SRU Justification
  [Impact]
  Intel 9260/9462/9560 require new firmwares to enable them.

  [ 7.492326] iwlwifi :00:0c.0: Direct firmware load for 
iwlwifi-9000-pu-a0-jf-b0-33.ucode failed with error -2
  [ 7.492349] iwlwifi :00:0c.0: Direct firmware load for 
iwlwifi-9000-pu-a0-jf-b0-32.ucode failed with error -2
  [ 7.492362] iwlwifi :00:0c.0: Direct firmware load for 
iwlwifi-9000-pu-a0-jf-b0-31.ucode failed with error -2
  [ 7.492375] iwlwifi :00:0c.0: Direct firmware load for 
iwlwifi-9000-pu-a0-jf-b0-30.ucode failed with error -2
  [ 7.492378] iwlwifi :00:0c.0: no suitable firmware found!

  For v4.13 kernel, it uses firmware version 33, so we only need this.

  commit c4276b65390d32d33c8263a7e3c8be0db8cccad4 (tag: 
refs/tags/iwlwifi-fw-2017-11-03)
  Author: Luca Coelho 
  Date:   Fri Oct 13 14:22:26 2017 +0300

  iwlwifi: add firmware version 33 for new 9000 series

  Build number: WFFW53774_R30_FW610294

  Revision number: 610294

  Signed-off-by: Luca Coelho 

  [Test Case]
  After applying the firmwares, confirm the 9260/9560 can connect to 6 
different APs(bg/n/ac * open/wap)

  [Regression Potential]
  There is no regression for the new devices and new firmwares.

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

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

[Kernel-packages] [Bug 1728523] Please test proposed package

Hello AceLan, or anyone else affected,

Accepted linux-firmware into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.157.15 in a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

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

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

Title:
  QCA6174A XR cannot find any WiFi AP

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

Bug description:
  SRU Justification
  [Impact]
  Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e]
  Atheros QCA6174 can't find any WiFi APs and got below message in dmesg

  [   16.158772] ath10k_pci :02:00.0: failed to enable dynamic BW: -11
  [   22.162575] ath10k_pci :02:00.0: could not suspend target (-11)
  [   27.533002] ath10k_pci :02:00.0: failed to enable dynamic BW: -11
  [   33.535958] ath10k_pci :02:00.0: could not suspend target (-11)
  [   38.890790] ath10k_pci :02:00.0: failed to enable dynamic BW: -11
  [   44.893968] ath10k_pci :02:00.0: could not suspend target (-11)
  [   46.358194] i2c_designware i2c_designware.0: controller timed out
  [   47.358231] i2c_designware i2c_designware.0: controller timed out
  [   48.358506] i2c_designware i2c_designware.0: controller timed out
  [   49.566240] i2c_designware i2c_designware.2: controller timed out
  [   50.566862] i2c_designware i2c_designware.2: controller timed out
  [   51.566307] i2c_designware i2c_designware.2: controller timed out
  [   52.670330] i2c_designware i2c_designware.3: controller timed out
  [   53.670775] i2c_designware i2c_designware.3: controller timed out
  [   54.670427] i2c_designware i2c_designware.3: controller timed out
  [   60.326619] ath10k_pci :02:00.0: failed to enable dynamic BW: -11
  [   66.327117] ath10k_pci :02:00.0: could not suspend target (-11)
  [   71.678943] ath10k_pci :02:00.0: failed to enable dynamic BW: -11
  [   77.679084] ath10k_pci :02:00.0: could not suspend target (-11)

  It requires updated firmwares to enable it.

  [Test Case]
  After applying the required firmwares, it can search APs and connect to the 
network.

  [Regression Potential]
  Although the new firmware overwrite the old one, considering it exists in 
linux-firmware git tree and didn't get any update for 3 month, it should be 
good with no regression.

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

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

[Kernel-packages] [Bug 1729389] Please test proposed package

Hello Jeppe, or anyone else affected,

Accepted linux-firmware into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.157.15 in a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

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

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

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  New
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  New
Status in linux-firmware source package in Artful:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Bluetooth peripherals work initially but stop working shortly
  with Linux 4.13.

  Fix: Updated firmware from Intel containing a fix for the issue.

  Regression Potential: Any firmware updates may bring regressions,
  however this is a bug fix update and therefore regression potential is
  expected to be minimal.

  ---

  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  ---
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp.
   Bus 001 Device 005: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 13d3:5664 IMC Networks
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
    UP RUNNING PSCAN ISCAN INQUIRY
    RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
    TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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

[Kernel-packages] [Bug 1734243] Please test proposed package

Hello AceLan, or anyone else affected,

Accepted linux-firmware into zesty-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.164.3 in a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-zesty to verification-done-zesty. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-zesty. In either case, details of your testing
will help us make a better decision.

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

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

Title:
  Intel 9260/9462/9560 firmware support

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-firmware source package in Zesty:
  Fix Committed
Status in linux-firmware source package in Artful:
  Fix Committed

Bug description:
  SRU Justification
  [Impact]
  Intel 9260/9462/9560 require new firmwares to enable them.

  [ 7.492326] iwlwifi :00:0c.0: Direct firmware load for 
iwlwifi-9000-pu-a0-jf-b0-33.ucode failed with error -2
  [ 7.492349] iwlwifi :00:0c.0: Direct firmware load for 
iwlwifi-9000-pu-a0-jf-b0-32.ucode failed with error -2
  [ 7.492362] iwlwifi :00:0c.0: Direct firmware load for 
iwlwifi-9000-pu-a0-jf-b0-31.ucode failed with error -2
  [ 7.492375] iwlwifi :00:0c.0: Direct firmware load for 
iwlwifi-9000-pu-a0-jf-b0-30.ucode failed with error -2
  [ 7.492378] iwlwifi :00:0c.0: no suitable firmware found!

  For v4.13 kernel, it uses firmware version 33, so we only need this.

  commit c4276b65390d32d33c8263a7e3c8be0db8cccad4 (tag: 
refs/tags/iwlwifi-fw-2017-11-03)
  Author: Luca Coelho 
  Date:   Fri Oct 13 14:22:26 2017 +0300

  iwlwifi: add firmware version 33 for new 9000 series

  Build number: WFFW53774_R30_FW610294

  Revision number: 610294

  Signed-off-by: Luca Coelho 

  [Test Case]
  After applying the firmwares, confirm the 9260/9560 can connect to 6 
different APs(bg/n/ac * open/wap)

  [Regression Potential]
  There is no regression for the new devices and new firmwares.

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

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

[Kernel-packages] [Bug 1729085] Re: [18.04] Missing vNIC module in the installer

2017-12-15 Thread Seth Forshee

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

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

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

Title:
  [18.04] Missing vNIC module in the installer

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Mirroring over for 18.04 installer.

  Canonical:  Please add the ibmvnic module to the installer for 18.04.

  Thank you.

  == Comment: #0 - YUECHANG E. MEI  - 2017-02-27 11:33:10 ==
  ---Problem Description---
  We tried to install ubuntu 16.04.2 by using vNIC. When we tried to load the 
installer, we saw an issue. Comment from bug 144675, it looks like the ibmvnic 
module is not included in 16.04.2 or 17.04 installer. 

GNU GRUB  version 2.02~beta2-vlan1

   
++
   | Install Ubuntu 17.04 GA w/ multipath and preseed   
|
   | Install Ubuntu 17.04 GA w/ multipath   
|
   | Install Ubuntu 17.04 GA w/ preseed 
|
   |*Install Ubuntu Yakkety (16.10 development) 
|
   | Install Ubuntu Yakkety (16.10 w/ multipath)
|
   | Install Ubuntu 16.04 GA
|
   | Install Ubuntu 16.04 GA w/ multipath   
|
   | Install Ubuntu 16.04 GA w/ preseed 
|
   | Install Ubuntu 16.04 GA w/ multipath and preseed   
|
   | Install Ubuntu 14.04.4 LTS 
|
   | Install Ubuntu 14.04.5 LTS 
|
   | Rescue mode
|
   
++

Use the ^ and v keys to select which entry is highlighted.
Press enter to boot the selected OS, `e' to edit the commands
before booting or `c' for a command-line.


 ?? [!!] Download debconf preconfiguration file ??
 ?   ?
 ? Failed to retrieve the preconfiguration file  ?
 ? The file needed for preconfiguration could not be retrieved from  ?
 ? http://10.33.11.31/distros/ubuntu/preseed.cfg. The installation will  ?
 ? proceed in non-automated mode.?
 ?   ?
 ? ?
 ?   ?
 ?
  but then we cannot go any further...drop to the shell and we do not see any 
ibmvnic loaded, try to load it is not found. 

  ~ # lsmod|grep ibm
  ibmveth31190  0
  ~ # modprobe ibmvnic
  modprobe: FATAL: Module ibmvnic not found in directory 
/lib/modules/4.4.0-21-generic
  ~ #
   
  ---boot type---
  Network boot
   
  ---bootloader---
  grub
   
  ---Point of failure---
  Failed during boot of installer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1729085/+subscriptions

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

[Kernel-packages] [Bug 1706247] Re: Add support for 16g huge pages on Ubuntu 16.04.2 PowerNV

** Summary changed:

- It should not be possible to turn on 16g huge pages on Ubuntu 16.04.2 PowerNV
+ Add support for 16g huge pages on Ubuntu 16.04.2 PowerNV

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

Title:
  Add support for 16g huge pages on Ubuntu 16.04.2 PowerNV

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  In Progress

Bug description:
  16G Huge Pages are not supported on PowerNV (bare metal) installations. 
Ubuntu 16.04.2 still allows 16G huge pages to be turned on.
   
  Contact Information = Mike Hollinger (mchol...@us.ibm.com) 
   
  ---uname output---
  Linux aprilmin4 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:53:54 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8335-GTB 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Add the following to the kernel boot args (either via editing the 
petitboot boot option manually, or updating /boot/grub/grub.cfg:

  default_hugepagesz=16G hugepagesz=16G hugepages=4

  2. Boot Linux
  3. Observe that the kernel believes 16G huge pages are available:
  ubuntu@aprilmin7:~$ cat /proc/meminfo | grep -i huge
  AnonHugePages:475136 kB
  HugePages_Total:   0
  HugePages_Free:0
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:   16777216 kB
  ubuntu@aprilmin7:~$ ls /sys/devices/system/node/node0/hugepages
  hugepages-1024kB  hugepages-16384kB  hugepages-16777216kB

   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for Mike Hollinger (mchol...@us.ibm.com): 
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.

  
  This may be recreated on any bare metal POWER8 server with Ubuntu 16.04.2; I 
haven't checked other versions of Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1706247/+subscriptions

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

[Kernel-packages] [Bug 1706247] Re: Add support for 16g huge pages on Ubuntu 16.04.2 PowerNV

SRU request submitted for Artful:
https://lists.ubuntu.com/archives/kernel-team/2017-December/088932.html

The Xenial and Zesty SRU request will also be sent shortly.

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

Title:
  Add support for 16g huge pages on Ubuntu 16.04.2 PowerNV

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  In Progress

Bug description:
  16G Huge Pages are not supported on PowerNV (bare metal) installations. 
Ubuntu 16.04.2 still allows 16G huge pages to be turned on.
   
  Contact Information = Mike Hollinger (mchol...@us.ibm.com) 
   
  ---uname output---
  Linux aprilmin4 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:53:54 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8335-GTB 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Add the following to the kernel boot args (either via editing the 
petitboot boot option manually, or updating /boot/grub/grub.cfg:

  default_hugepagesz=16G hugepagesz=16G hugepages=4

  2. Boot Linux
  3. Observe that the kernel believes 16G huge pages are available:
  ubuntu@aprilmin7:~$ cat /proc/meminfo | grep -i huge
  AnonHugePages:475136 kB
  HugePages_Total:   0
  HugePages_Free:0
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:   16777216 kB
  ubuntu@aprilmin7:~$ ls /sys/devices/system/node/node0/hugepages
  hugepages-1024kB  hugepages-16384kB  hugepages-16777216kB

   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for Mike Hollinger (mchol...@us.ibm.com): 
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.

  
  This may be recreated on any bare metal POWER8 server with Ubuntu 16.04.2; I 
haven't checked other versions of Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1706247/+subscriptions

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

[Kernel-packages] [Bug 1731031] Re: Kernel Oops with 17.10

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

Title:
  Kernel Oops with 17.10

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

Bug description:
  have captured dmesg just before oops

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Nov  8 20:41:14 2017
  DistUpgraded: 2017-11-07 01:49:14,657 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: kubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.10.0-38-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.13.0-16-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller 
[106b:011a]
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1762): WARNING **: Failed to 
load user image: Failed to open file '/home/hmeyer/.face': No such file or 
directory
  MachineType: Apple Inc. MacBookPro11,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=fbc61d79-8b51-4801-8e2b-175ff6daa14f ro quiet splash apparmor=0 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-11-07 (1 days ago)
  dmi.bios.date: 02/22/2016
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B17.1602221718
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B17.1602221718:bd02/22/2016:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.family: Mac
  dmi.product.name: MacBookPro11,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Nov  8 20:39:06 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2
  xserver.video_driver: modeset

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

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

[Kernel-packages] [Bug 1737913] Re: linux-lts-trusty: 3.13.0-138.187~precise1 -proposed tracker

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

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

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

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1737911
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Friday, 15. December 2017 15:33 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1737911
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Friday, 15. December 2017 15:33 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux-lts-trusty: 3.13.0-138.187~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1737911
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1734744] Re: OOM killer with kernel 4.4.0-92

2017-12-15 Thread Willem

I tested with kernel:4.4.105-0404105-generic and could not reproduced

** Tags added: kernel-fixed-upstream

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

Title:
  OOM killer with kernel 4.4.0-92

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

Bug description:
  When putting pressure on a Linux Node in Azure we see OOM killers (similar 
to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842 but not this 
is a different kernel)
  Reverting the kernel to 4.4.0-57 fixes the problem.

  dmesg and kernel.log attached
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 11 15:21 seq
   crw-rw 1 root audio 116, 33 Dec 11 15:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic 
root=UUID=512611f4-b05a-4d8a-b743-438b71c5385d ro console=tty1 console=ttyS0 
earlyprintk=ttyS0 rootdelay=300
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-92-generic N/A
   linux-backports-modules-4.4.0-92-generic  N/A
   linux-firmware1.157.13
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images xenial uec-images
  Uname: Linux 4.4.0-92-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/02/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090007
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.uuid: D88904A9-DF88-454F-9F50-7A8DE8964445
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1737640] Re: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures

2017-12-15 Thread Nicholas Skaggs

** Changed in: juju
   Status: Triaged => Invalid

** Tags removed: verification-needed

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

Title:
  /usr/sbin/fanctl: arithmetic expression: expecting primary |
  unconfigured interfaces cause ifup failures

Status in juju:
  Invalid
Status in OPNFV:
  Fix Committed
Status in ubuntu-fan package in Ubuntu:
  Confirmed
Status in ubuntu-fan source package in Xenial:
  Fix Committed

Bug description:
  I'm seeing this error as the status of multiple containers in my
  deploy:

  http://paste.ubuntu.com/26166720/

  I can't connect to the parent machines anymore either - it seems
  networking is totally hosed on the machines.

  This is with juju 2.3.1.

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

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

[Kernel-packages] [Bug 1738263] Re: Touchpad not working and locking CPU

2017-12-15 Thread Zibri Soft

By the way the ID of this trackpad is: ELAN1200  04F3:3090

Is there any solution? Even a work-around would be good.

One thing: the trackpad works inside uefi bios.. is not possible to use
it talking to the bios instead of i2c directly?

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

Title:
  Touchpad not working and locking CPU

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Notebook: ASUS GL703VD
  Touchpad: probably ELAN clickpad

  it seems to be connected to i2c bus

  the modules loaded are elan_i2c and multitouch_hid

  the multitouch hid module take almost 100% of cpu and the mouse cursor
  moves badly (loosing it for a second or 2 then resuming) also feature
  clicks and doubleclicks and sensitivity problems.

  doing rmmod hid-multitouch.ko (or rmmod multitouch_hid) and
  blacklisting the module solves the cpu problem but obviously the
  touchoad is dead.

  SEVERITY VERY HIGH
  It probably affects many other ASUS models.

  (the touchpad works perfectly in windows 10 by the way)

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

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

[Kernel-packages] [Bug 1731031] Re: Kernel Oops with 17.10

That is correct.  Ubuntu starts with the mainline kernel and adds
patches on top.  From your testing, it appears the bug may have been
introduce by an Ubuntu SAUCE patch, since you cannot reproduce it with
any of the upstream kernels.

We should figure out which Ubuntu kernel version introduced the bug.  We
can then perform a kernel bisect to identify the exact patch that caused
this.

The call trace looks similar to what is happening in bug 1734327.  Can you see 
if the bug you are seeing happens with the test kernel I built for that bug:
http://kernel.ubuntu.com/~jsalisbury/lp1731031/

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

Title:
  Kernel Oops with 17.10

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

Bug description:
  have captured dmesg just before oops

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Nov  8 20:41:14 2017
  DistUpgraded: 2017-11-07 01:49:14,657 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: kubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.10.0-38-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.13.0-16-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller 
[106b:011a]
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1762): WARNING **: Failed to 
load user image: Failed to open file '/home/hmeyer/.face': No such file or 
directory
  MachineType: Apple Inc. MacBookPro11,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=fbc61d79-8b51-4801-8e2b-175ff6daa14f ro quiet splash apparmor=0 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-11-07 (1 days ago)
  dmi.bios.date: 02/22/2016
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B17.1602221718
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B17.1602221718:bd02/22/2016:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.family: Mac
  dmi.product.name: MacBookPro11,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Nov  8 20:39:06 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2
  xserver.video_driver: modeset

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

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

[Kernel-packages] [Bug 1626299] Re: ACPI Errors in dmesg, battery monitor shows empty

2017-12-15 Thread Andrea

This problem is not solved yet, i tried many ways (changing kernel and so on), 
even after upgrading the bios to the latest (1.09).
I tried Ubuntu 14, Ubuntu 16, Ubuntu 17, many kernel versions in Manjaro KDE.

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

Title:
  ACPI Errors in dmesg, battery monitor shows empty

Status in linux package in Ubuntu:
  Expired

Bug description:
  I am using Xubuntu, and the power manager show an empty battery at all
  times, regardless of battery level. I essentially have no indicators
  of how much power my laptop has left. Once I run out of power, the
  laptop obviously shuts down causing data corruption.

  my dmesg shows:

  [   10.587295] ACPI Error: No handler for Region [PMRG] (88015a0c0090) 
[GenericSerialBus] (20150930/evregion-163)
  [   10.587303] ACPI Error: Region GenericSerialBus (ID=9) has no handler 
(20150930/exfldio-297)
  [   10.587309] ACPI Error: Method parse/execution failed [\_SB.TAMB._TMP] 
(Node 88015a0f7208), AE_NOT_EXIST (20150930/psparse-542)
  [   10.587325] thermal thermal_zone0: failed to read out thermal zone (-5)
  [   10.598876] ACPI Error: No handler for Region [PMRG] (88015a0c0090) 
[GenericSerialBus] (20150930/evregion-163)
  [   10.598882] ACPI Error: Region GenericSerialBus (ID=9) has no handler 
(20150930/exfldio-297)
  [   10.598886] ACPI Error: Method parse/execution failed [\_SB.TEFN._TMP] 
(Node 88015a0f76e0), AE_NOT_EXIST (20150930/psparse-542)
  [   10.598898] thermal thermal_zone1: failed to read out thermal zone (-5)
  [   10.600460] ACPI Error: No handler for Region [PMRG] (88015a0c0090) 
[GenericSerialBus] (20150930/evregion-163)
  [   10.600465] ACPI Error: Region GenericSerialBus (ID=9) has no handler 
(20150930/exfldio-297)
  [   10.600469] ACPI Error: Method parse/execution failed [\_SB.TSKN._TMP] 
(Node 88015a0f94b0), AE_NOT_EXIST (20150930/psparse-542)
  [   10.600479] thermal thermal_zone2: failed to read out thermal zone (-5)

  later it shows:

  [   11.235601] acer_wmi: Enabling Launch Manager failed: 0xe4 - 0x0

  
  It's unfortunate to never know how much power is left, as one might imagine.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  coder  1607 F pulseaudio
   /dev/snd/controlC1:  coder  1607 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Sep 22 00:34:51 2016
  HibernationDevice: RESUME=UUID=c0846449-28bd-4d6a-9ccb-732cf1582f3a
  InstallationDate: Installed on 2016-09-08 (13 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Acer Aspire SW5-173
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/11/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.08
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Crepe
  dmi.board.vendor: Acer
  dmi.board.version: V1.08
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.08
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.08:bd04/11/2016:svnAcer:pnAspireSW5-173:pvrV1.08:rvnAcer:rnCrepe:rvrV1.08:cvnAcer:ct9:cvrV1.08:
  dmi.product.name: Aspire SW5-173
  dmi.product.version: V1.08
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1737911] Re: linux: 3.13.0-138.187 -proposed tracker

2017-12-15 Thread Steve Beattie

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

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux: 3.13.0-138.187 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

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

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

  backports: 1737913
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1737913] Re: linux-lts-trusty: 3.13.0-138.187~precise1 -proposed tracker

2017-12-15 Thread Steve Beattie

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

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux-lts-trusty: 3.13.0-138.187~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1737911
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1737918] Re: linux-aws: 4.4.0-1007.7 -proposed tracker

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

** Tags added: block-proposed-trusty

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1737916
  phase: Uploaded

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

Title:
  linux-aws: 4.4.0-1007.7 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1737916
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel opps destroying interfaces on i386

2017-12-15 Thread Greg Rose

James Page asked me to post some findings here:

Here’s the trace I’m getting (same as one in comment #10:

[ 5152.142936] device s1 left promiscuous mode
[ 5152.427823] BUG: unable to handle kernel NULL pointer dereference at   (null)
[ 5152.428422] IP: rtmsg_ifa+0x30/0xd0
[ 5152.428816] *pdpt = 33f65001 *pde = 
[ 5152.428820]
[ 5152.429682] Oops:  [#1] SMP
[ 5152.430046] Modules linked in: veth netconsole openvswitch nf_conntrack_ipv6 
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack ppdev snd_hda_codec_generic snd_hda_intel snd_hda_codec joydev 
snd_hda_core snd_hwdep snd_pcm input_leds serio_raw snd_timer snd pvpanic 
parport_pc i2c_piix4 soundcore mac_hid parport sch_fq_codel ib_iser rdma_cm 
iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
qxl ttm crc32_pclmul drm_kms_helper pcbc aesni_intel syscopyarea aes_i586 
sysfillrect crypto_simd sysimgblt fb_sys_fops psmouse cryptd virtio_net 
virtio_blk drm pata_acpi floppy
[ 5152.433348] CPU: 1 PID: 90 Comm: kworker/u4:3 Tainted: GW   
4.13.0-16-generic #19-Ubuntu
[ 5152.433852] Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011
[ 5152.434346] Workqueue: netns cleanup_net
[ 5152.434816] task: f17aa100 task.stack: f4ef
[ 5152.435302] EIP: rtmsg_ifa+0x30/0xd0
[ 5152.435780] EFLAGS: 00010246 CPU: 1
[ 5152.436254] EAX:  EBX:  ECX:  EDX: 014000c0
[ 5152.436764] ESI:  EDI: f063a6c0 EBP: f4ef1dcc ESP: f4ef1db4
[ 5152.437267]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[ 5152.437780] CR0: 80050033 CR2:  CR3: 33c3f4a0 CR4: 001406f0
[ 5152.438311] Call Trace:
[ 5152.438816]  __inet_del_ifa+0xbb/0x260
[ 5152.439344]  ? igmpv3_clear_delrec+0x28/0xa0
[ 5152.439868]  inetdev_event+0x22f/0x4e0
[ 5152.440401]  ? skb_dequeue+0x5b/0x70
[ 5152.440934]  ? wireless_nlevent_flush+0x4c/0x90
[ 5152.441487]  notifier_call_chain+0x4e/0x70
[ 5152.442016]  raw_notifier_call_chain+0x11/0x20
[ 5152.442554]  call_netdevice_notifiers_info+0x2a/0x60
[ 5152.443097]  rollback_registered_many+0x21c/0x380
[ 5152.443646]  unregister_netdevice_many.part.102+0x10/0x80
[ 5152.444180]  default_device_exit_batch+0x134/0x160
[ 5152.444709]  ? do_wait_intr_irq+0x80/0x80
[ 5152.445223]  ops_exit_list.isra.8+0x4d/0x60
[ 5152.445744]  cleanup_net+0x18e/0x260
[ 5152.446264]  process_one_work+0x1a0/0x390
[ 5152.446790]  worker_thread+0x37/0x440
[ 5152.447321]  kthread+0xf3/0x110
[ 5152.447843]  ? process_one_work+0x390/0x390
[ 5152.448380]  ? kthread_create_on_node+0x20/0x20
[ 5152.448919]  ret_from_fork+0x19/0x24
[ 5152.449462] Code: 55 89 e5 57 56 53 89 d7 89 ce 83 ec 0c 85 c9 89 45 e8 c7 
45 f0 00 00 00 00 74 06 8b 41 08 89 45 f0 8b 47 0c 31 c9 ba c0 00 40 01 <8b> 00 
8b 80 20 03 00 00 6a ff 89 45 ec b8 60 00 00 00 e8 19 46
[ 5152.450719] EIP: rtmsg_ifa+0x30/0xd0 SS:ESP: 0068:f4ef1db4
[ 5152.451308] CR2: 
[ 5152.451885] ---[ end trace 5cdfc95a5b343f5c ]---

Looks to me like 4.13 is missing this set of patches from Cong Wang:

commit 623859ae06b85cabba79ce78f0d49e67783d4c34
Merge: 8f56246 35c55fc
Author: David S. Miller 
Date:   Thu Nov 9 10:03:10 2017 +0900

Merge branch 'net-sched-race-fix'

Cong Wang says:


net_sched: close the race between call_rcu() and cleanup_net()

This patchset tries to fix the race between call_rcu() and
cleanup_net() again. Without holding the netns refcnt the
tc_action_net_exit() in netns workqueue could be called before
filter destroy works in tc filter workqueue. This patchset
moves the netns refcnt from tc actions to tcf_exts, without
breaking per-netns tc actions.

Patch 1 reverts the previous fix, patch 2 introduces two new
API's to help to address the bug and the rest patches switch
to the new API's. Please see each patch for details.

I was not able to reproduce this bug, but now after adding
some delay in filter destroy work I manage to trigger the
crash. After this patchset, the crash is not reproducible
any more and the debugging printk's show the order is expected
too.


Fixes: ddf97ccdd7cb ("net_sched: add network namespace support for tc action
Reported-by: Lucas Bates 
Cc: Lucas Bates 
Cc: Jamal Hadi Salim 
Cc: Jiri Pirko 
Signed-off-by: Cong Wang 
Signed-off-by: David S. Miller 

Note the comment he makes about “filter destroy work” and how the final
function in the trace is __inet_del_ifa().  As you can see from the
trace the machine is executing the netns cleanup_net() function when the
panic occurs.  This series of patches has not been backported to the
4.13.16 kernel.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

Re: [Kernel-packages] [Bug 1737671] Re: Blu-ray burner no longer detected

2017-12-15 Thread Roald Strauss

Hi Joseph,


Sorry I haven't had time to test this yet. Things are kinda hectic here 
in December.

But I got kernel 4.4.0-104-generic just now and can report that the 
problem is still there.

Will see if I can find time to try that upstream thingy at some point, 
but to be honest I'm probably giving it a low priority because it seems 
complicated.


- Roald



Den 12-12-2017 kl. 22:00 skrev Joseph Salisbury:
> Would it be possible for you to test the latest upstream kernel? Refer
> tohttps://wiki.ubuntu.com/KernelMainlineBuilds  . Please test the latest
> v4.15 kernel[0].
>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> Once testing of the upstream kernel is complete, please mark this bug as
> "Confirmed".
>
>
> Thanks in advance.
>
> [0]http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc3
>
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> -- You received this bug notification because you are subscribed to 
> the bug report. https://bugs.launchpad.net/bugs/1737671 Title: Blu-ray 
> burner no longer detected Status in linux package in Ubuntu: 
> Incomplete Bug description: Linux Kernel 97 is the last kernel in 
> which my Blu-ray burner is still detected. Booting with all following 
> kernels makes it undetectable, and I can't use it. ProblemType: Bug 
> DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-103-generic 
> 4.4.0-103.126 ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 
> 4.4.98 Uname: Linux 4.4.0-103-generic x86_64 ApportVersion: 
> 2.20.1-0ubuntu2.14 Architecture: amd64 AudioDevicesInUse: USER PID 
> ACCESS COMMAND /dev/snd/controlC0: misthalu 1913 F pulseaudio 
> CurrentDesktop: Unity Date: Tue Dec 12 08:00:12 2017 
> HibernationDevice: RESUME=UUID=d22d1aa7-36b9-44ab-936e-f713d1f79a40 
> InstallationDate: Installed on 2016-05-19 (571 days ago) 
> InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
> (20160420.1) IwConfig: lo no wireless extensions. enp8s0 no wireless 
> extensions. MachineType: Gigabyte Technology Co., Ltd. Z170X-Gaming 3 
> ProcFB: 0 inteldrmfb ProcKernelCmdLine: 
> BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic 
> root=UUID=9b2e1b7a-2bbd-4a36-990f-6ba56f567b2d ro quiet splash 
> vt.handoff=7 RelatedPackageVersions: 
> linux-restricted-modules-4.4.0-103-generic N/A 
> linux-backports-modules-4.4.0-103-generic N/A linux-firmware 1.157.14 
> RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present 
> (probably fresh install) dmi.bios.date: 07/24/2015 dmi.bios.vendor: 
> American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To 
> be filled by O.E.M. dmi.board.name: Z170X-Gaming 3 dmi.board.vendor: 
> Gigabyte Technology Co., Ltd. dmi.board.version: x.x 
> dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 
> dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be 
> Filled By O.E.M. dmi.modalias: 
> dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Gaming3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming3:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
>  
> dmi.product.name: Z170X-Gaming 3 dmi.product.version: To be filled by 
> O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage 
> notifications about this bug go to: 
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737671/+subscriptions 
>

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

Title:
  Blu-ray burner no longer detected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Linux Kernel 97 is the last kernel in which my Blu-ray burner is still
  detected. Booting with all following kernels makes it undetectable,
  and I can't use it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-103-generic 4.4.0-103.126
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  Uname: Linux 4.4.0-103-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  misthalu   1913 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Dec 12 08:00:12 2017
  HibernationDevice: RESUME=UUID=d22d1aa7-36b9-44ab-936e-f713d1f79a40
  InstallationDate: Installed on 2016-05-19 (571 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp8s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Z170X-Gaming 3
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic 
root=UUID=9b2e1b7a-2bbd-4a36-990f-6ba56f567b2d ro quiet splash vt.handof

[Kernel-packages] [Bug 1738404] [NEW] Bluetooth sound extreme low quality

You have been subscribed to a public bug:

I upgraded today from ubuntu 17.04 to ubuntu 17.10.

I use 3 different bluetooth audio devices ( BT earphones, BT speaker, BT
BOSE Soundlink speaker) , all of them worked properly on 17.04.

Since the upgrade, the sound gets continuous interruptions/cracking. 
These sound interruptions and cracking are so annoying that I cannot keep on 
listening to music.
I could relate this to the fact that a new BT stack has replaced the former in 
Ubuntu.

If I use wired devices (hdmi connected screen+audio, the sound quality is good 
and as before) so the issue is related to the use of the new Bluetooth stack.
I have not found a way to parameterise it neither.

I have not found any similar report. "apport" seems not ot exist in
thise version, I cannot find and execute it.

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


** Tags: bot-comment
-- 
Bluetooth sound extreme low quality
https://bugs.launchpad.net/bugs/1738404
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to bluez in Ubuntu.

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

[Kernel-packages] [Bug 1738404] Re: Bluetooth sound extreme low quality

2017-12-15 Thread Paul White

** Package changed: ubuntu => bluez (Ubuntu)

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

Title:
  Bluetooth sound extreme low quality

Status in bluez package in Ubuntu:
  New

Bug description:
  I upgraded today from ubuntu 17.04 to ubuntu 17.10.

  I use 3 different bluetooth audio devices ( BT earphones, BT speaker,
  BT BOSE Soundlink speaker) , all of them worked properly on 17.04.

  Since the upgrade, the sound gets continuous interruptions/cracking. 
  These sound interruptions and cracking are so annoying that I cannot keep on 
listening to music.
  I could relate this to the fact that a new BT stack has replaced the former 
in Ubuntu.

  If I use wired devices (hdmi connected screen+audio, the sound quality is 
good and as before) so the issue is related to the use of the new Bluetooth 
stack.
  I have not found a way to parameterise it neither.

  I have not found any similar report. "apport" seems not ot exist in
  thise version, I cannot find and execute it.

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

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

[Kernel-packages] [Bug 1380046] Re: [AV200 - Xonar STX, playback] Loud pop when switching to headphones

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [AV200 - Xonar STX, playback] Loud pop when switching to headphones

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

Bug description:
  When switching the port to either headphone ports from the speaker
  port there is a loud pop in the headphones. When I am playing music
  through the speakers at 100% volume and then switch, I can hear the
  music at a very loud volume through the headphones for a fraction of a
  second before dropping to the proper headphones volume which is much
  lower. Even if I mute the output before switching ports there is still
  a pop although not nearly as loud.

  I believe this is a driver issue (oxygen/virtuoso). The Essense STX
  uses a relay to switch between the speaker and headphones ports. I am
  guessing the the power for the speaker (line out) port is much higher
  than that used for the headphones port and the drivers need to mute
  the sound at a hardware level before switching to elmininate the pop.
  On Windows when switching to and from speaker and headphones port the
  output would be muted for almost a second as the port was switched so
  there was no pop. On Ubuntu there is no delay when switching ports. I
  have looked at the driver source code and there is an anti_pop_delay
  of 800 milliseconds used on the Xonar init method. I think this same
  delay should probably be added when switching to the headphone ports.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  michael   20842 F pulseaudio
   /dev/snd/controlC0:  michael   20842 F pulseaudio
   /dev/snd/pcmC0D0p:   michael   20842 F...m pulseaudio
   /dev/snd/controlC1:  michael   20842 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Oct 11 22:50:15 2014
  InstallationDate: Installed on 2014-10-07 (3 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:STX successful
  Symptom_Card: HD Webcam C910 - USB Device 0x46d:0x821
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [AV200 - Xonar STX, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1401
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1401:bd08/20/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael2404 F pulseaudio
   /dev/snd/controlC2:  michael2404 F pulseaudio
   /dev/snd/controlC1:  michael2404 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=89201542-3d78-4588-9f0f-3725c7c22875
  InstallationDate: Installed on 2014-10-07 (5 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=fbc05121-3d98-42ce-8073-986171e4b73f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:
   
  Tags:  trusty trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom di

[Kernel-packages] [Bug 1380046] Re: [AV200 - Xonar STX, playback] Loud pop when switching to headphones

2017-12-15 Thread Adam Hulin

I'm also affected of this issue.

I found this partial(?) solution to this on github:
https://gist.github.com/kevinlekiller/f533f4d1f7318a7cf81a

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

Title:
  [AV200 - Xonar STX, playback] Loud pop when switching to headphones

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

Bug description:
  When switching the port to either headphone ports from the speaker
  port there is a loud pop in the headphones. When I am playing music
  through the speakers at 100% volume and then switch, I can hear the
  music at a very loud volume through the headphones for a fraction of a
  second before dropping to the proper headphones volume which is much
  lower. Even if I mute the output before switching ports there is still
  a pop although not nearly as loud.

  I believe this is a driver issue (oxygen/virtuoso). The Essense STX
  uses a relay to switch between the speaker and headphones ports. I am
  guessing the the power for the speaker (line out) port is much higher
  than that used for the headphones port and the drivers need to mute
  the sound at a hardware level before switching to elmininate the pop.
  On Windows when switching to and from speaker and headphones port the
  output would be muted for almost a second as the port was switched so
  there was no pop. On Ubuntu there is no delay when switching ports. I
  have looked at the driver source code and there is an anti_pop_delay
  of 800 milliseconds used on the Xonar init method. I think this same
  delay should probably be added when switching to the headphone ports.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  michael   20842 F pulseaudio
   /dev/snd/controlC0:  michael   20842 F pulseaudio
   /dev/snd/pcmC0D0p:   michael   20842 F...m pulseaudio
   /dev/snd/controlC1:  michael   20842 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Oct 11 22:50:15 2014
  InstallationDate: Installed on 2014-10-07 (3 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:STX successful
  Symptom_Card: HD Webcam C910 - USB Device 0x46d:0x821
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [AV200 - Xonar STX, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1401
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1401:bd08/20/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael2404 F pulseaudio
   /dev/snd/controlC2:  michael2404 F pulseaudio
   /dev/snd/controlC1:  michael2404 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=89201542-3d78-4588-9f0f-3725c7c22875
  InstallationDate: Installed on 2014-10-07 (5 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=fbc05121-3d98-42ce-8073-986171e4b73f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:
   
  Tags:  trusty trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cd

[Kernel-packages] [Bug 1737640] Re: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures

2017-12-15 Thread Nicholas Skaggs

** Tags added: verification-done

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

Title:
  /usr/sbin/fanctl: arithmetic expression: expecting primary |
  unconfigured interfaces cause ifup failures

Status in juju:
  Invalid
Status in OPNFV:
  Fix Committed
Status in ubuntu-fan package in Ubuntu:
  Confirmed
Status in ubuntu-fan source package in Xenial:
  Fix Committed

Bug description:
  I'm seeing this error as the status of multiple containers in my
  deploy:

  http://paste.ubuntu.com/26166720/

  I can't connect to the parent machines anymore either - it seems
  networking is totally hosed on the machines.

  This is with juju 2.3.1.

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

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

[Kernel-packages] [Bug 1738224] Re: Suspend broken after kernel upgrade

2017-12-15 Thread Jeffrey Bouter

Updating my XPS to the latest firmware (I was only one release behind)
has resolved the issue.

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

Title:
  Suspend broken after kernel upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My machine (XPS 13 9360) won't go into suspend properly after
  upgrading from linux-image-4.13.0-17-generic to linux-
  image-4.13.0-19-generic.

  This affects both suspend through lid close and "systemctl suspend".
  Screen goes off, power led remains lit. Then after some time the
  screen comes back on, is stuck and lets me wait for a few before
  becoming responsive again.

  Booting back into 4.13.0-17 resolved the issue.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeffrey1963 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5
  InstallationDate: Installed on 2017-10-18 (56 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker input libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.3.1
  dmi.board.name: 0839Y6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.3.1:bd10/03/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1738224] Re: Suspend broken after kernel upgrade

2017-12-15 Thread Jeffrey Bouter

Nevermind. Only worked once. After a reboot, just to check, the issue
still persists. Both on battery and on regular power.

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

Title:
  Suspend broken after kernel upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My machine (XPS 13 9360) won't go into suspend properly after
  upgrading from linux-image-4.13.0-17-generic to linux-
  image-4.13.0-19-generic.

  This affects both suspend through lid close and "systemctl suspend".
  Screen goes off, power led remains lit. Then after some time the
  screen comes back on, is stuck and lets me wait for a few before
  becoming responsive again.

  Booting back into 4.13.0-17 resolved the issue.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeffrey1963 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5
  InstallationDate: Installed on 2017-10-18 (56 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker input libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.3.1
  dmi.board.name: 0839Y6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.3.1:bd10/03/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1668105] Re: xhci_hcd module turns off usb host controller on boot

2017-12-15 Thread raffraffraff

I'm also using a MacBook Pro 2015, but with Ubuntu 17.10. I'm not seeing
exactly the same symptoms. Specifically, I do not get 'Assuming host is
dying, halting host.'

I do get these symptoms:
1. On boot, each key press takes about 8 seconds (affects Mac restore and Grub,
making it almost impossible to use them). By the time the Linux kernel starts,
everything speeds up, and I have no problem entering a luks passphrase.
2. Very occasionally my keyboard and mouse completely stop working and I have
to reboot
3. Resuming from sleep, there is a 3-4 minutes period where USB devices won't
work and I get a ton of "xhci_hcd :00:14.0: Timeout while waiting for setup
device command" messages.

I've had these issues since 16.04 I think.

I'm also going to compile a kernel with xhci_hcd as a module and then
blacklist (just to test).

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

Title:
xhci_hcd module turns off usb host controller on boot

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

Bug description:
So we know this xhci_kcd was always shit in that it turns off the
console usb keyboard for long running computers and that it on abrupt
termination of Linux puts usb in a 12x slower mode. It is buggy, it
was always buggy, and its getting worse.

With Linux 4.8.0-37, this crappy software decides to halt the host
controller on boot, ie. turn off the console keyboard preventing any
boot. I cannot think of any situation where anyone would want their
host controller halted.

This is MacBook Pro 2015. So, it's already broken in UEFI-grub as it
always was, ie. every key press takes 8 seconds, but you only need
two, so you can boot in 16 s.

I tried to disable the xhci_kcd crap by using kernel parameter
noxhci_port_switch or modprobe.blacklist=xhci_hcd neither which works.

Because it has crap in UEFI, the computer will not boot any external
hard drive or usb fob. The only thing that works is Apple rescue that
gets rid of the xhci garbage, and the boot os x immediately after
that.

So the log output
xhci_hcd :00:14.0: Timeout while waiting for setup device command
xhci_hcd :00:14.0: xHCI host not responding to stop endpoint command.
- and a bit later:
xhci_hcd :00:14.0: Assuming host is dying, halting host.
xhci_hcd :00:14.0: HC died; cleaning up

This clown programming of Linux has to stop. Why would anyone ever want their
host controller halted?
---
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: foxyboy5662 F pulseaudio
/dev/snd/controlC0: foxyboy5662 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 16.10
HibernationDevice: RESUME=/dev/mapper/C89-SWAP
MachineType: Apple Inc. MacBookPro12,1
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-39-generic
root=/dev/mapper/C89-RFS ro i915.enable_rc6=0
ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
RelatedPackageVersions:
linux-restricted-modules-4.8.0-39-generic N/A
linux-backports-modules-4.8.0-39-generic N/A
linux-firmware1.161.1
Tags: yakkety
Uname: Linux 4.8.0-39-generic x86_64
UpgradeStatus: Upgraded to yakkety on 2016-11-16 (108 days ago)
UserGroups: adm docker libvirt libvirtd sudo
_MarkForUpload: True
dmi.bios.date: 10/26/2015
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP121.88Z.0167.B15.1510261437
dmi.board.name: Mac-E43C1C25D4880AD6
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro12,1
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-E43C1C25D4880AD6
dmi.modalias:
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B15.1510261437:bd10/26/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
dmi.product.name: MacBookPro12,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-15 Thread Steve Langasek

** Description changed:

  Hi all,
  
  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.
  
  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.
  
  Moreover (and most important) USB booting is not possible anymore since
  USB is not recognized. It's very serious, since our machines do not have
  a CDROM.
  
  Lenovo forums at the moment are full of topics regading this issue.
  
  Thank you!!
  
   UPDATE (01/12/2017) 
  
  LENOVO machines affected so far (please add your affected model to this
  list):
  
  Lenovo Y50-70
  Lenovo G40-30
  Lenovo U31-70
  Lenovo G50-70
  Lenovo Z50-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo G50-80
  Lenovo S20-30
  Lenovo Yoga 2 11" - 20332
  Lenovo B40-70
  Lenovo Z51-70
  Lenovo B50-70
  Lenovo Flex-10
+ Lenova Yoga 33-11 IBR
  
  The bug also affects Acer Aspire E5-771G.
  
  ---
  
  Temporary workaround:
  https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t
  -Save-Settings-Or-Exit/m-p/3853208#M157885
  
  ---
  
  result from apport-collect 1734147:
  
  ---
  
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tob1608 F pulseaudio
   /dev/snd/controlC0:  tob1608 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO
  
  ---

** Description changed:

  Hi all,
  
  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.
  
  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.
  
  Moreover (and most important) USB booting is not possible anymore since
  USB is not recognized. It's very serious, since our machines do not have
  a CDROM.
  
  Lenovo forums at the moment are full of topics regading this issue.
  
  Thank you!!
  
   UPDATE (01/12/2017) 
  
  LENOVO machines affected so far (please add your affected model to this
  list):
  
  Lenovo Y50-70
  Lenovo G40-30
  Lenovo U31-70
  Lenovo G50-70
  Lenovo Z50-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo G50-80
  Lenovo S20-30
  Lenovo Yoga 2 11" - 20332
  Lenovo B40-70
  Lenovo Z51-70
  Lenovo B50-70
  Lenovo Flex-10
- Lenova Yoga 33-11 IBR
  
  The bug also affects Acer Aspire E5-771G.
  
  ---
  
  Temporary workaround:
  https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t
  -Save-Settings-Or-Exit/m-p/3853208#M157885
  
  ---
  
  result from apport-collect 1734147:
  
  ---
  
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tob1608 F pulseaudio
   /dev/snd/controlC0:  tob1608 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-sess

[Kernel-packages] [Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react

2017-12-15 Thread Jeppe Bundsgaard

Sorry for not having provided an update - I have been away from my mouse and 
keyboard for some time.
It has been working fine with linux 4.13.12-041312-generic for a few days. 
Now, I have downloaded and installed the linux-firmware 1.169.2 - I'll see how 
the mouse and keyboard reacts when I am back home.

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

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  New
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  New
Status in linux-firmware source package in Artful:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Bluetooth peripherals work initially but stop working shortly
  with Linux 4.13.

  Fix: Updated firmware from Intel containing a fix for the issue.

  Regression Potential: Any firmware updates may bring regressions,
  however this is a bug fix update and therefore regression potential is
  expected to be minimal.

  ---

  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  ---
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp.
   Bus 001 Device 005: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 13d3:5664 IMC Networks
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
    UP RUNNING PSCAN ISCAN INQUIRY
    RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
    TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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

[Kernel-packages] [Bug 1738480] [NEW] Bionic update to v4.14.6 stable release

2017-12-15 Thread Seth Forshee

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The v4.14.6 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the v4.14.6 stable release shall be
applied:

usb: gadget: udc: renesas_usb3: fix number of the pipes
usb: gadget: core: Fix ->udc_set_speed() speed handling
serdev: ttyport: add missing receive_buf sanity checks
serdev: ttyport: fix NULL-deref on hangup
serdev: ttyport: fix tty locking in close
usb: f_fs: Force Reserved1=1 in OS_DESC_EXT_COMPAT
can: mcba_usb: fix device disconnect bug
can: peak/pci: fix potential bug when probe() fails
can: flexcan: fix VF610 state transition issue
can: ti_hecc: Fix napi poll return value for repoll
can: kvaser_usb: free buf in error paths
can: kvaser_usb: Fix comparison bug in kvaser_usb_read_bulk_callback()
can: kvaser_usb: ratelimit errors if incomplete messages are received
can: kvaser_usb: cancel urb on -EPIPE and -EPROTO
can: mcba_usb: cancel urb on -EPROTO
can: ems_usb: cancel urb on -EPIPE and -EPROTO
can: esd_usb2: cancel urb on -EPIPE and -EPROTO
can: usb_8dev: cancel urb on -EPIPE and -EPROTO
can: peak/pcie_fd: fix potential bug in restarting tx queue
virtio: release virtio index when fail to device_register
iio: stm32: fix adc/trigger link error
iio: health: max30102: Temperature should be in milli Celsius
iio: adc: cpcap: fix incorrect validation
iio: adc: meson-saradc: fix the bit_idx of the adc_en clock
iio: adc: meson-saradc: initialize the bandgap correctly on older SoCs
iio: adc: meson-saradc: Meson8 and Meson8b do not have REG11 and REG13
pinctrl: armada-37xx: Fix direction_output() callback behavior
Drivers: hv: vmbus: Fix a rescind issue
hv: kvp: Avoid reading past allocated blocks from KVP file
firmware: cleanup FIRMWARE_IN_KERNEL message
firmware: vpd: Destroy vpd sections in remove function
firmware: vpd: Tie firmware kobject to device lifetime
firmware: vpd: Fix platform driver and device registration/unregistration
isa: Prevent NULL dereference in isa_bus driver callbacks
scsi: dma-mapping: always provide dma_get_cache_alignment
scsi: use dma_get_cache_alignment() as minimum DMA alignment
scsi: libsas: align sata_device's rps_resp on a cacheline
efi: Move some sysfs files to be read-only by root
efi/esrt: Use memunmap() instead of kfree() to free the remapping
ASN.1: fix out-of-bounds read when parsing indefinite length item
ASN.1: check for error from ASN1_OP_END__ACT actions
KEYS: add missing permission check for request_key() destination
KEYS: reject NULL restriction string when type is specified
X.509: reject invalid BIT STRING for subjectPublicKey
X.509: fix comparisons of ->pkey_algo
x86/idt: Load idt early in start_secondary
x86/PCI: Make broadcom_postcore_init() check acpi_disabled
KVM: x86: fix APIC page invalidation
btrfs: fix missing error return in btrfs_drop_snapshot
btrfs: handle errors while updating refcounts in update_ref_for_cow
ALSA: hda/realtek - New codec support for ALC257
ALSA: pcm: prevent UAF in snd_pcm_info
ALSA: seq: Remove spurious WARN_ON() at timer check
ALSA: usb-audio: Fix out-of-bound error
ALSA: usb-audio: Add check return value for usb_string()
iommu/vt-d: Fix scatterlist offset handling
smp/hotplug: Move step CPUHP_AP_SMPCFD_DYING to the correct place
s390: always save and restore all registers on context switch
s390/mm: fix off-by-one bug in 5-level page table handling
s390: fix compat system call table
KVM: s390: Fix skey emulation permission check
Revert "powerpc: Do not call ppc_md.panic in fadump panic notifier"
powerpc/64s: Initialize ISAv3 MMU registers before setting partition table
iwlwifi: mvm: mark MIC stripped MPDUs
iwlwifi: mvm: don't use transmit queue hang detection when it is not possible
iwlwifi: mvm: flush queue before deleting ROC
iwlwifi: add new cards for 9260 and 22000 series
iwlwifi: mvm: fix packet injection
iwlwifi: mvm: enable RX offloading with TKIP and WEP
brcmfmac: change driver unbind order of the sdio function devices
kdb: Fix handling of kallsyms_symbol_next() return value
md/r5cache: move mddev_lock() out of r5c_journal_mode_set()
drm/bridge: analogix dp: Fix runtime PM state in get_modes() callback
drm/exynos: gem: Drop NONCONTIG flag for buffers allocated without IOMMU
drm/i915: Fix vblank timestamp/frame counter jumps on gen2
media: dvb: i2c transfers over usb cannot be done from stack
media: rc: sir_ir: detect presence of port
media: rc: partial revert of "media: rc: per-protocol repeat period"
arm64: KVM: fix VTTBR_BADDR_MASK BUG_ON off-by-one
arm: KVM: Fix VTTBR_BADDR_MASK BUG_ON off-by-one
KVM:

[Kernel-packages] [Bug 1738483] [NEW] package linux-image-4.4.0-104-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

2017-12-15 Thread WaltSullivan

Public bug reported:

In the middle of a Software Update, this happened.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-104-generic (not installed)
ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
Uname: Linux 4.4.0-103-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.14
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  w316673 F pulseaudio
 /dev/snd/seq:timidity   1726 F timidity
Date: Fri Dec 15 10:29:58 2017
ErrorMessage: subprocess new pre-installation script returned error exit status 
128
HibernationDevice: RESUME=UUID=152f6ef7-3554-422a-aad2-1224361fd43f
InstallationDate: Installed on 2013-01-23 (1786 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
MachineType: Dell Inc. Inspiron 530s
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic 
root=UUID=83a64b80-5a37-4659-b797-221b88ef41f8 ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.14
RfKill:
 
SourcePackage: linux
Title: package linux-image-4.4.0-104-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/12/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.16
dmi.board.name: 0RY007
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: OEM
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.16:bd12/12/2008:svnDellInc.:pnInspiron530s:pvr:rvnDellInc.:rn0RY007:rvr:cvnDellInc.:ct3:cvrOEM:
dmi.product.name: Inspiron 530s
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-package 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/1738483

Title:
  package linux-image-4.4.0-104-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  New

Bug description:
  In the middle of a Software Update, this happened.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-104-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  Uname: Linux 4.4.0-103-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  w316673 F pulseaudio
   /dev/snd/seq:timidity   1726 F timidity
  Date: Fri Dec 15 10:29:58 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=152f6ef7-3554-422a-aad2-1224361fd43f
  InstallationDate: Installed on 2013-01-23 (1786 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: Dell Inc. Inspiron 530s
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic 
root=UUID=83a64b80-5a37-4659-b797-221b88ef41f8 ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.14
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.4.0-104-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No u

[Kernel-packages] [Bug 1721676] Re: implement errno action logging in seccomp for strict mode with snaps

2017-12-15 Thread Tyler Hicks

The snapd pull request is located here:
https://github.com/snapcore/snapd/pull/3998/

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

Title:
  implement errno action logging in seccomp for strict mode with snaps

Status in Snappy:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  A requirement for snappy is that security sandbox violations against
  policy are logged. In this manner learning tools can be written to
  parse the logs, etc and make developing on snappy easier.

  The current default seccomp action, in strict mode. is to kill the
  snap's thread that violated the policy but this is unfriendly to the
  developer and to the user. The desired action is to block the illegal
  system call and return an error with errno set to EPERM. However,
  seccomp does not emit log events when it takes that action. Seccomp
  should be updated to emit log events when taking the SECCOMP_RET_ERRNO
  action and then snappy can switch to the using that action when
  blocking illegal system calls.

  [Impact]

  Snapd needs a way to log SECCOMP_RET_ERRNO seccomp actions in order to
  have a more friendly strict mode. Such functionality has been merged
  upstream into 4.14-rc2.

  No libseccomp changes are needed at this time since snap-confine loads
  the BPF filter directly into the kernel without using libseccomp.

  [Test Case]

  Running the libseccomp "live" tests will exercise the kernel's seccomp
  enforcement and help to help catch any regressions. Note that on
  Artful, there's an existing test failure (20-live-
  basic_die%%002-1):

  $ sudo apt build-dep -y libseccomp
  $ sudo apt install -y cython
  $ apt source libseccomp
  $ cd libseccomp-*
  $ autoreconf -ivf && ./configure --enable-python && make check-build
  $ (cd tests && ./regression -T live)

  All tests should pass on zesty (12 tests) and xenial (10 tests). On artful, 
you'll see one pre-existing failure:
  ...
  Test 20-live-basic_die%%002-1 result: FAILURE 20-live-basic_die TRAP 
rc=159
  ...
  Regression Test Summary
   tests run: 12
   tests skipped: 0
   tests passed: 11
   tests failed: 1
   tests errored: 0
  

  

  Running the seccomp kernel selftests is also a great to exercise
  seccomp and the kernel patch set proposed for the SRU includes
  additional seccomp selftests. To build, enter into the root of the
  kernel source tree and build the seccomp test binary:

  $ make -C tools/testing/selftests TARGETS=seccomp

  Now you can execute tools/testing/selftests/seccomp/seccomp_bpf or
  even copy it to a test machine and run it there. On Xenial, 54/54
  tests should pass and 58/58 should pass on Zesty.

  

  Now we can run a single test to verify that SECCOMP_RET_ERRNO is
  logged when the application opts into it. First, verify that "errno"
  is listed in the actions_logged sysctl:

  $ cat /proc/sys/kernel/seccomp/actions_logged
  kill trap errno trace log

  Now, build and run the test program:

  $ gcc -o lp1721676-kernel-test lp1721676-kernel-test.c
  $ ./lp1721676-kernel-test
  SUCCESS: getpid() failed as expected: Operation not permitted

  It should have generated a message like this in /var/log/syslog:

  kernel: [79338.804966] audit: type=1326 audit(1507259221.875:27):
  auid=1000 uid=1000 gid=1000 ses=5 pid=3091 comm="lp1721676-kerne"
  exe="/home/tyhicks/lp1721676-kernel-test" sig=0 arch=c03e
  syscall=39 compat=0 ip=0x7fb91829c499 code=0x5

  Disable errno logging in the sysctl:

  $ echo kill trap trace log | sudo tee /proc/sys/kernel/seccomp/actions_logged
  kill trap trace log

  Rerun the test program and ensure that nothing was logged this time.

  [Regression Potential]

  The kernel patches received a lot of review between Kees and some
  others interested in improved seccomp logging. I authored the patches
  and feel comfortable/confident with my backported versions. They do
  not change the behavior of seccomp logging by default but offer ways
  applications to opt into more logging and, on the flipside, ways for
  the administrator to quite any additional logging.

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

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

[Kernel-packages] [Bug 1738483] Re: package linux-image-4.4.0-104-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

2017-12-15 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-4.4.0-104-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  New

Bug description:
  In the middle of a Software Update, this happened.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-104-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  Uname: Linux 4.4.0-103-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  w316673 F pulseaudio
   /dev/snd/seq:timidity   1726 F timidity
  Date: Fri Dec 15 10:29:58 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=152f6ef7-3554-422a-aad2-1224361fd43f
  InstallationDate: Installed on 2013-01-23 (1786 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: Dell Inc. Inspiron 530s
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic 
root=UUID=83a64b80-5a37-4659-b797-221b88ef41f8 ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.14
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.4.0-104-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.16
  dmi.board.name: 0RY007
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.16:bd12/12/2008:svnDellInc.:pnInspiron530s:pvr:rvnDellInc.:rn0RY007:rvr:cvnDellInc.:ct3:cvrOEM:
  dmi.product.name: Inspiron 530s
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1738483] Status changed to Confirmed

This change was made by a bot.

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

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

Title:
  package linux-image-4.4.0-104-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In the middle of a Software Update, this happened.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-104-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  Uname: Linux 4.4.0-103-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  w316673 F pulseaudio
   /dev/snd/seq:timidity   1726 F timidity
  Date: Fri Dec 15 10:29:58 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=152f6ef7-3554-422a-aad2-1224361fd43f
  InstallationDate: Installed on 2013-01-23 (1786 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: Dell Inc. Inspiron 530s
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic 
root=UUID=83a64b80-5a37-4659-b797-221b88ef41f8 ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.14
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.4.0-104-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.16
  dmi.board.name: 0RY007
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.16:bd12/12/2008:svnDellInc.:pnInspiron530s:pvr:rvnDellInc.:rn0RY007:rvr:cvnDellInc.:ct3:cvrOEM:
  dmi.product.name: Inspiron 530s
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1738490] [NEW] current boot config dims screen during initramfs

2017-12-15 Thread Tessa

Public bug reported:

This is a weird one. Shortly after moving to 17.10, my laptop has
started dimming its internal screen to minimum brightness at the start
of initramfs execution. shortly thereafter it restores it to normal
brightness, but that only happens *after* typing in encrypted filesystem
passwords, so the password dialogues are practically invisible. Not sure
why its doing this, but whatever's restoring the brightness should do it
before prompting for filesystem mounting so these prompts are actually
visible.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-generic 4.13.0.19.20
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tessa 17026 F pulseaudio
 /dev/snd/controlC1:  tessa 17026 F pulseaudio
CurrentDesktop: GNOME
Date: Fri Dec 15 13:44:02 2017
InstallationDate: Installed on 2016-07-08 (524 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Apple Inc. MacBookPro11,4
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic.efi.signed 
root=ZFS=rpool/root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-19-generic N/A
 linux-backports-modules-4.13.0-19-generic  N/A
 linux-firmware 1.169.1
SourcePackage: linux
UpgradeStatus: Upgraded to artful on 2017-10-19 (57 days ago)
dmi.bios.date: 08/08/2017
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP114.88Z.0177.B00.1708080033
dmi.board.name: Mac-06F11FD93F0323C5
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,4
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-06F11FD93F0323C5
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP114.88Z.0177.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro11,4
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  current boot config dims screen during initramfs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a weird one. Shortly after moving to 17.10, my laptop has
  started dimming its internal screen to minimum brightness at the start
  of initramfs execution. shortly thereafter it restores it to normal
  brightness, but that only happens *after* typing in encrypted
  filesystem passwords, so the password dialogues are practically
  invisible. Not sure why its doing this, but whatever's restoring the
  brightness should do it before prompting for filesystem mounting so
  these prompts are actually visible.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-generic 4.13.0.19.20
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tessa 17026 F pulseaudio
   /dev/snd/controlC1:  tessa 17026 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Dec 15 13:44:02 2017
  InstallationDate: Installed on 2016-07-08 (524 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Apple Inc. MacBookPro11,4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic.efi.signed 
root=ZFS=rpool/root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-19 (57 days ago)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP114.88Z.0177.B00.1708080033
  dmi.board.name: Mac-06F11FD93F0323C5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,4
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-06F11FD93F0323C5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP114.88Z.0177.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro11,4
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs

[Kernel-packages] [Bug 1738491] [NEW] touchpad not working

2017-12-15 Thread gm

Public bug reported:

chuwi Lapbook Air touch pad not working

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

** Patch added: "Log Files"
   
https://bugs.launchpad.net/bugs/1738491/+attachment/5023238/+files/Logg%20Files.zip

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

Title:
  touchpad not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  chuwi Lapbook Air touch pad not working

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

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

[Kernel-packages] [Bug 1738490] Status changed to Confirmed

This change was made by a bot.

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

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

Title:
  current boot config dims screen during initramfs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a weird one. Shortly after moving to 17.10, my laptop has
  started dimming its internal screen to minimum brightness at the start
  of initramfs execution. shortly thereafter it restores it to normal
  brightness, but that only happens *after* typing in encrypted
  filesystem passwords, so the password dialogues are practically
  invisible. Not sure why its doing this, but whatever's restoring the
  brightness should do it before prompting for filesystem mounting so
  these prompts are actually visible.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-generic 4.13.0.19.20
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tessa 17026 F pulseaudio
   /dev/snd/controlC1:  tessa 17026 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Dec 15 13:44:02 2017
  InstallationDate: Installed on 2016-07-08 (524 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Apple Inc. MacBookPro11,4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic.efi.signed 
root=ZFS=rpool/root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-19 (57 days ago)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP114.88Z.0177.B00.1708080033
  dmi.board.name: Mac-06F11FD93F0323C5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,4
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-06F11FD93F0323C5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP114.88Z.0177.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro11,4
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

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

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

apport-collect 1738491

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

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

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

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

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

Title:
  touchpad not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  chuwi Lapbook Air touch pad not working

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

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

[Kernel-packages] [Bug 1738491] Re: touchpad not working

2017-12-15 Thread gm

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

Title:
  touchpad not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  chuwi Lapbook Air touch pad not working

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

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

[Kernel-packages] [Bug 1738497] [NEW] Falkor erratum 1041 needs workaround

2017-12-15 Thread dann frazier

Public bug reported:

[Impact]
A hardware issue can lead to a kernel crash or unexpected behavior.

[Test Case]
The issue presents itself most commonly as a boot-time crash. It doesn't effect 
all Falkor CPUs, and only rarely occurs on CPUs that are effected.

[Regression Risk]
The fix is entirely in arm64 code, mitigating the risk to other architectures. 
The biggest regression risk is performance, as the workaround involves adding 
an instruction barrier prior to disabling the MMU.

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

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

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

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

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

** Summary changed:

- Falkor erratum 1041 needs wworkaround
+ Falkor erratum 1041 needs workaround

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

Title:
  Falkor erratum 1041 needs workaround

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Zesty:
  Incomplete
Status in linux source package in Artful:
  Incomplete

Bug description:
  [Impact]
  A hardware issue can lead to a kernel crash or unexpected behavior.

  [Test Case]
  The issue presents itself most commonly as a boot-time crash. It doesn't 
effect all Falkor CPUs, and only rarely occurs on CPUs that are effected.

  [Regression Risk]
  The fix is entirely in arm64 code, mitigating the risk to other 
architectures. The biggest regression risk is performance, as the workaround 
involves adding an instruction barrier prior to disabling the MMU.

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

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

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

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

apport-collect 1738497

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

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

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

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

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

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

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

Title:
  Falkor erratum 1041 needs workaround

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  In Progress

Bug description:
  [Impact]
  A hardware issue can lead to a kernel crash or unexpected behavior.

  [Test Case]
  The issue presents itself most commonly as a boot-time crash. It doesn't 
effect all Falkor CPUs, and only rarely occurs on CPUs that are effected.

  [Regression Risk]
  The fix is entirely in arm64 code, mitigating the risk to other 
architectures. The biggest regression risk is performance, as the workaround 
involves adding an instruction barrier prior to disabling the MMU.

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

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

[Kernel-packages] [Bug 1738497] Re: Falkor erratum 1041 needs workaround

2017-12-15 Thread dann frazier

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

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

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

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

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

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

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

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

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

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

Title:
  Falkor erratum 1041 needs workaround

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  In Progress

Bug description:
  [Impact]
  A hardware issue can lead to a kernel crash or unexpected behavior.

  [Test Case]
  The issue presents itself most commonly as a boot-time crash. It doesn't 
effect all Falkor CPUs, and only rarely occurs on CPUs that are effected.

  [Regression Risk]
  The fix is entirely in arm64 code, mitigating the risk to other 
architectures. The biggest regression risk is performance, as the workaround 
involves adding an instruction barrier prior to disabling the MMU.

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

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

[Kernel-packages] [Bug 1738491] Re: touchpad not working

2017-12-15 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  touchpad not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  chuwi Lapbook Air touch pad not working

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

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

[Kernel-packages] [Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react

2017-12-15 Thread Michael

Fixed for me.

Tested version: http://de.archive.ubuntu.com/ubuntu artful-proposed/main
amd64 linux-firmware all 1.169.2

It finally stays connected with my bluetooth device. Also there is no
freeze when I open the bluetooth settings, nor when I block/unblock via
rfkill. Also I did not experience any deadlock yet while shutdown.

I will keep that version, until it is official released. If there is any
complication I will report back.

Thanks for the good work.

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

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  New
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  New
Status in linux-firmware source package in Artful:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Bluetooth peripherals work initially but stop working shortly
  with Linux 4.13.

  Fix: Updated firmware from Intel containing a fix for the issue.

  Regression Potential: Any firmware updates may bring regressions,
  however this is a bug fix update and therefore regression potential is
  expected to be minimal.

  ---

  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  ---
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp.
   Bus 001 Device 005: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 13d3:5664 IMC Networks
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
    UP RUNNING PSCAN ISCAN INQUIRY
    RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
    TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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

[Kernel-packages] [Bug 1723583] Re: BUG: unable to handle kernel NULL pointer dereference at 00000004

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  BUG: unable to handle kernel NULL pointer dereference at 0004

Status in linux package in Ubuntu:
  Expired

Bug description:
  Just booted up computer.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  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 i686
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  charlie2351 F pulseaudio
  Date: Sat Oct 14 09:11:41 2017
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location EIP: bio_uncopy_user+0xc3/0x140 SS:ESP: 0068:f43c5d0c
  Failure: oops
  InstallationDate: Installed on 2017-07-28 (77 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 
(20170725.1)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: NOVATECH LTD PERSONAL COMPUTER
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=650586f6-4f8f-4d72-853f-15154b747716 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: BUG: unable to handle kernel NULL pointer dereference at 0004
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: xxx-xxx
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnPERSONALCOMPUTER:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: PERSONAL COMPUTER
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD

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

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

[Kernel-packages] [Bug 1722677] Re: Touch Screen NOT working

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Touch Screen NOT working

Status in linux package in Ubuntu:
  Expired

Bug description:
  Ubuntu 17.10 Beta 2. Dell Venue 11 pro 7139. 
  Touchscreen does not work after installing OS from live USB. It did not work 
on USB either. There is zero touchscreen functionality.

  Workaroud: Must put computer to sleep, and then wake from sleep for
  touchscreen to work.

  Please Note: In this edition of 17.10, tilt sensors work perfectly
  without having to put the computer to sleep (an old bug). Also note,
  wifi works perfectly after resuming from sleep (another old bug fixed
  :)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-15-generic 4.13.0-15.16
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  troll  1255 F pulseaudio
   /dev/snd/controlC0:  troll  1255 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 10 18:54:29 2017
  InstallationDate: Installed on 2017-09-30 (10 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic.efi.signed 
root=UUID=cdb5516d-c1f9-4c0b-8869-35a9db498fa1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-15-generic N/A
   linux-backports-modules-4.13.0-15-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0RFDKW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0RFDKW:rvrA01:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1724079] Re: bluetooth applet hangs - 17.10 artful

[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  bluetooth applet hangs - 17.10 artful

Status in bluez package in Ubuntu:
  Expired

Bug description:
  ubuntu 17.10 
  bluez 5.46-0ubuntu3

  after failing to search for bluetooth mouse, bluetooth applet crashes. 
  restarting bluetooth.service yields "adapter not found" message upon trying 
to turn on bluetooth.

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

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

[Kernel-packages] [Bug 1723607] Re: TouchPad don't work

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  TouchPad don't work

Status in linux package in Ubuntu:
  Expired

Bug description:
  I've got a MSI gl62 6qf and my touchpad isn't recognize by (I think) kernel 
even when I list /proc/bus/input/devices :
  {
  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input0
  U: Uniq=
  H: Handlers=sysrq kbd event0 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=60070290 8380207af040d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0003 Vendor=0738 Product=1722 Version=0111
  N: Name="Mad Catz Mad Catz R.A.T. Pro S"
  P: Phys=usb-:00:14.0-3/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/0003:0738:1722.0001/input/input1
  U: Uniq=Example#
  H: Handlers=mouse0 event1 
  B: PROP=0
  B: EV=17
  B: KEY=1fff 0 0 0 0
  B: REL=103
  B: MSC=10

  I: Bus=0003 Vendor=0738 Product=1722 Version=0111
  N: Name="Mad Catz Mad Catz R.A.T. Pro S"
  P: Phys=usb-:00:14.0-3/input2
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.2/0003:0738:1722.0003/input/input2
  U: Uniq=Example#
  H: Handlers=sysrq kbd event2 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=10007 ff9f207ac14057ff febeffdfffef fffe
  B: MSC=10
  B: LED=1f

  I: Bus=0003 Vendor=0738 Product=1722 Version=0111
  N: Name="Mad Catz Mad Catz R.A.T. Pro S"
  P: Phys=usb-:00:14.0-3/input3
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.3/0003:0738:1722.0004/input/input3
  U: Uniq=Example#
  H: Handlers=kbd event3 
  B: PROP=0
  B: EV=1f
  B: KEY=3007f 0 0 48317aff32d bf56 1 130f938b17c000 
677bfad9415fed 9ed6804400 1002
  B: REL=40
  B: ABS=1
  B: MSC=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Mic"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input4
  U: Uniq=
  H: Handlers=event4 
  B: PROP=0
  B: EV=21
  B: SW=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Headphone"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input5
  U: Uniq=
  H: Handlers=event5 
  B: PROP=0
  B: EV=21
  B: SW=4

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=3"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input6
  U: Uniq=
  H: Handlers=event6 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=7"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input7
  U: Uniq=
  H: Handlers=event7 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=8"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input8
  U: Uniq=
  H: Handlers=event8 
  B: PROP=0
  B: EV=21
  B: SW=140
  }
  I just see my USB mouse

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-37-generic 4.10.0-37.41
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oki28z 1747 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Sat Oct 14 15:52:52 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-06-05 (130 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0738:1722 Mad Catz, Inc. 
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Micro-Star International Co., Ltd. GL62 6QF
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=829d6917-902a-40ab-87c7-2badd49a97f0 ro priority=low acpi=off 
i8042.reset quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/29/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J5IMS.114
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J5
  dmi.board.v

[Kernel-packages] [Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Confirmed
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Confirmed
Status in linux-firmware source package in Artful:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Bluetooth peripherals work initially but stop working shortly
  with Linux 4.13.

  Fix: Updated firmware from Intel containing a fix for the issue.

  Regression Potential: Any firmware updates may bring regressions,
  however this is a bug fix update and therefore regression potential is
  expected to be minimal.

  ---

  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  ---
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp.
   Bus 001 Device 005: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 13d3:5664 IMC Networks
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
    UP RUNNING PSCAN ISCAN INQUIRY
    RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
    TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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

[Kernel-packages] [Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react