[Kernel-packages] [Bug 1625805] Re: arm64 kernel panic for l2 mmu with unity8 session snap

[Iftikhar Ahmad]

My dragonboard environment info is

~$ snap list
NameVersion   Rev  Developer  Notes
dragonboard 16.04-0.1723   canonical  -
dragonboard-kernel  4.4.0-1024-3  9canonical  -
snapweb 0.21  17   canonical  -
ubuntu-core 16.04.1   759  canonical  -
unity8-session  0 x1  devmode

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

Title:
  arm64 kernel panic for l2 mmu with unity8 session snap

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

Bug description:
  we are running the unity8 session snap on amd64 without any problems.
  to setup and reproduce the problem follow the "on Dragonboard" section of 
  
https://docs.google.com/document/d/1o-jKITqUxRsujmN3OwRj3wRnn6dgblKuvrhKjeN8-Wc

  You can also find the panic signature at line 3276 of the attached
  syslog.

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

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

[Kernel-packages] [Bug 1625805] Re: arm64 kernel panic for l2 mmu with unity8 session snap

[Iftikhar Ahmad]

I tried running the unity8-session on DB as per the steps mentioned in above 
doc but process terminated as soon as it launched followed by several respawing 
messages. Please find attached the relevant syslog as well as terminal output 
after launching unity8-session is here 
https://paste.ubuntu.com/23254146/

** Attachment added: "syslog_unity8"
   
https://bugs.launchpad.net/snappy/+bug/1625805/+attachment/4751441/+files/syslog_unity8

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

Title:
  arm64 kernel panic for l2 mmu with unity8 session snap

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

Bug description:
  we are running the unity8 session snap on amd64 without any problems.
  to setup and reproduce the problem follow the "on Dragonboard" section of 
  
https://docs.google.com/document/d/1o-jKITqUxRsujmN3OwRj3wRnn6dgblKuvrhKjeN8-Wc

  You can also find the panic signature at line 3276 of the attached
  syslog.

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

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

[Kernel-packages] [Bug 1626604] modoc (ppc64el) - tests ran: 2, failed: 0

[Brad Figg]

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-97.144/modoc__3.13.0-97.144__2016-09-30_05-10-00/results-index.html

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

Title:
  linux: 3.13.0-97.144 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  Fix Released
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 3.13.0-97.144 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 --
  derivative-trackers-created: 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/1626604/+subscriptions

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

[Kernel-packages] [Bug 1392176] Re: mounts cgroups unconditionally which causes undesired effects with cpu hotplug

[bugproxy]

** Tags removed: targetmilestone-inin1510
** Tags added: targetmilestone-inin1604

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

Title:
  mounts cgroups unconditionally which causes undesired effects with cpu
  hotplug

Status in cgmanager package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Preeti U. Murthy  - 2014-10-20 
04:40:12 ==
  ---Problem Description---
  Systemd mounts cgroups explicitly every boot. Since the user had no say in 
it, undesired consequences are observed in reaction to cpu hotplug operations.  
Here is how.

  Systemd moves the tasks to the cgroup mounted by it. This cgroup 
automatically becomes the child of the root cgroup which is present by default. 
The children cgroups are not expected to remember their configured cpusets 
after hotplug operations in the kernel. Hence when cpus are taken offline and 
brought back online they are no longer used for load balancing of tasks and 
hence remain unused. 
 This is an undesired consequence because the user had not even asked for 
cgroups to be mounted, yet is not able to use the full capacity of the system.

  Only when the user himself creates cgroup hierarchies, should he be
  exposed to the side effects of cpu hotplug on cpusets. Else all online
  cpus must be made available to him which is not happening since
  systemd mounts cgroups on every boot.

  Hence please revert this feature or provide an explaination as to why this is 
being done.
   
  ---uname output---
  Linux tul181p1 3.16.0-18-generic #25-Ubuntu SMP Fri Sep 26 02:39:53 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Tuleta 8286-42A 
   ---Debugger---
  A debugger was configured, however the system did not enter into the debugger
   
  ---Steps to Reproduce---
   $ taskset -p $$
  $ 0-127
  $ echo 0 > /sys/devices/system/cpu/cpu7/online
  $ taskset -p $$
  $ 0-6,8-127
  $ echo 1 > /sys/devices/system/cpu/cpu7/online
  $ taskset -p $$
  $ 0-6,8-127
   
   
  Userspace tool common name: systemd 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: systemd_208-8ubuntu8_ppc64el.deb

  Userspace tool obtained from project website:   208-8ubuntu8

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

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

[Kernel-packages] [Bug 1629057] kernel02 (s390x.zVM) - tests ran: 1, failed: 1

[Brad Figg]

tests ran:   1, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-18.20/kernel02__4.8.0-18.20__2016-09-30_05-04-00/results-index.html

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

Title:
  linux: 4.8.0-19.21 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Confirmed
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-19.21 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
  derivative-trackers-created: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1629057] s2lp6g002 (s390x.zKVM) - tests ran: 1, failed: 1

[Brad Figg]

tests ran:   1, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-18.20/s2lp6g002__4.8.0-18.20__2016-09-30_05-03-00/results-index.html

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

Title:
  linux: 4.8.0-19.21 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Confirmed
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-19.21 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
  derivative-trackers-created: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1629057] Re: linux: 4.8.0-19.21 -proposed tracker

[Brad Figg]

tests ran:   1, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-18.20/s2lp4__4.8.0-18.20__2016-09-30_05-02-00/results-index.html

** Changed in: kernel-development-workflow/prepare-package-meta
   Status: Confirmed => Fix Released

** Changed in: kernel-development-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner 
(timg-tpi)

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

** Description changed:

  This bug is for tracking the 4.8.0-19.21 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 --
  derivative-trackers-created: true
  phase: Uploaded
+ kernel-phase:Uploaded
+ kernel-phase-changed:Friday, 30. September 2016 05:00 UTC

** Description changed:

  This bug is for tracking the 4.8.0-19.21 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
  derivative-trackers-created: true
  phase: Uploaded
- kernel-phase:Uploaded
- kernel-phase-changed:Friday, 30. September 2016 05:00 UTC

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

Title:
  linux: 4.8.0-19.21 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Confirmed
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-19.21 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
  derivative-trackers-created: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1627387] modoc (ppc64el) - tests ran: 1, failed: 1

[Brad Figg]

tests ran:   1, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-17.19/modoc__4.8.0-17.19__2016-09-30_04-48-00/results-index.html

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

Title:
  linux: 4.8.0-17.19 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Confirmed
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  This bug is for tracking the 4.8.0-17.19 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
  derivative-trackers-created: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1628279] Re: python utilities script suffix (.py) should be removed as per Policy 10.4

[Richard Laager]

The previous patch was here:
https://launchpadlibrarian.net/275709492/zfs-fix-filenames.debdiff

It probably still applies cleanly (aside for the changelog).

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

Title:
  python utilities script suffix (.py) should be removed as per Policy
  10.4

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  The zfs utilities scripts shipped with debian and ubuntu such as :

  * arc_summary.py : Provides a summary of the statistics
  https://github.com/zfsonlinux/zfs/blob/master/cmd/arc_summary

  * arcstat.py : Print out ZFS ARC Statistics exported via kstat(1)
  https://github.com/zfsonlinux/zfs/tree/master/cmd/arcstat

  * dbufstat.py : Print out statistics for all cached dmu buffers
  https://github.com/zfsonlinux/zfs/blob/master/cmd/dbufstat

  should be renamed according to Policy 10.4 :

  [https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts]

  "When scripts are installed into a directory in the system PATH, the
  script name should not include an extension such as .sh or .pl that
  denotes the scripting language currently used to implement it."

  Ideally, this should be fixed and upstreamed to Debian (or to zfslinux
  upstream) as well.

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

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

[Kernel-packages] [Bug 1628553] Re: Ubuntu 16.04.1 Install zfsutils-linux Panic Error, endless loop

[Richard Laager]

I think I got the numbers right, but in any case, this is the gist of the error:
PANIC: blkptr at 88040b993640 DVA 1 has invalid OFFSET 36830022909049856

What was the last version of ZFS-on-Linux (that you were using) that
works?

Was that the only version of ZFS you had ever used?

Can you attach the output of:
sudo zpool status
sudo zpool upgrade
sudo zdb

I assume you have swap on ZFS and this is breaking when it tries to access the 
swap dataset? If so, can you provide this output (substitute for rpool/swap as 
appropriate), which you should probably compress:
sudo zdb -d rpool/swap

I'm not sure that'll be enough information (as I'm not expert enough to
debug at this level), but it should be a start for me to take this to
someone else.

If it is happening with swap, try moving the swap dataset out of the way, and 
create a new one:
sudo zfs move rpool/swap rpool/swap-broken
sudo zfs create -V 4G -b $(getconf PAGESIZE) -o compression=zle \
  -o logbias=throughput -o sync=always \
  -o primarycache=metadata -o secondarycache=none \
  -o com.sun:auto-snapshot=false rpool/swap
sudo mkswap -f /dev/zvol/rpool/swap

This will hopefully get you working again on the latest ZFS. If you keep
the old dataset around, then we may still be able to debug how this
happened.

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

Title:
  Ubuntu 16.04.1 Install zfsutils-linux Panic Error, endless loop

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Fresh install of Ubuntu 16.04.1, installed all updates / upgrades for
  system before installing zfsutils-linux. The install processes all the
  way to Reached target Swap then has a PANIC error and loops endlessly.

  There is a zpool there already (was) with 3TB of data on it. This only
  happened after the system upgrade, so I reinstalled the boot drive /
  OS to see if it was just a issue with that, clearly it's an issue with
  the zfsutils-linux package for 16.04.1

  Package version installed zfsutils-linux 0.6.5.6-0ubuntu12

  Screenshot attached as I can't actually do anything once the boot gets
  to this stage:

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

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

[Kernel-packages] [Bug 1628968] Re: powerpc 4.8.0-17 fails to boot on PowerMac G5

[Adam Conrad]

Ahh, it was https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1557130

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

Title:
  powerpc 4.8.0-17 fails to boot on PowerMac G5

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

Bug description:
  Not much else to say. The system fails to complete booting, it gets
  stuck somewhere before network comes up; with errors in syslog about
  missing symbols for some modules (see
  http://paste.ubuntu.com/23251408/). Boots fine in 4.4.0-21:

  Sep 28 12:49:55 fujin kernel: [4.698092] uninorth_agp: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.715284] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.731545] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759718] drm: Unknown symbol ence_release 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759781] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.777863] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.798476] drm: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.815248] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.826136] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.846026] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.862106] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.882364] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.898322] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.914094] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.930108] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [5.396683] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [7.609956] autofs4: Unknown symbol 
cache_dir_open (err 0)
  Sep 28 12:49:55 fujin kernel: [7.610137] autofs4: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [9.989854] parport: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.405448] shpchp: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.684111] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.826081] rack_meter: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.953962] i2c_algo_bit: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.977975] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.010110] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.022857] soundcore: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.034422] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.049942] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.070474] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.085972] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.102451] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.118814] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.813073] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.820183] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   19.022406] bluetooth: Unknown symbol mcount 
(err 0)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=8c8a4ee6-57e4-4d02-9196-6c4620ee5883
  InstallationDate: Installed on 2016-09-28 (1 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release powerpc 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enP1p5s4f1  no wireless extensions.
   
   enP1p5s4f0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 1e54:2030 TypeMatrix 2030 USB Keyboard
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 003: ID 05ac:8207 Apple, Inc. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: root=UUID=fd6c3ae7-7de7-416e-8bed-b4513658ee6d ro quiet 
splash verbose
  ProcVersionSignature: Ubuntu 4.4.0-21.37-powerpc64-smp 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  

[Kernel-packages] [Bug 1628968] Re: powerpc 4.8.0-17 fails to boot on PowerMac G5

[Adam Conrad]

We had a veeery similar bug a year or two ago.  Going to have to
hunt down the reference and the commit that fixed it when I'm more
sober/awake.

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

Title:
  powerpc 4.8.0-17 fails to boot on PowerMac G5

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

Bug description:
  Not much else to say. The system fails to complete booting, it gets
  stuck somewhere before network comes up; with errors in syslog about
  missing symbols for some modules (see
  http://paste.ubuntu.com/23251408/). Boots fine in 4.4.0-21:

  Sep 28 12:49:55 fujin kernel: [4.698092] uninorth_agp: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.715284] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.731545] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759718] drm: Unknown symbol ence_release 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759781] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.777863] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.798476] drm: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.815248] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.826136] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.846026] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.862106] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.882364] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.898322] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.914094] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.930108] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [5.396683] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [7.609956] autofs4: Unknown symbol 
cache_dir_open (err 0)
  Sep 28 12:49:55 fujin kernel: [7.610137] autofs4: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [9.989854] parport: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.405448] shpchp: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.684111] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.826081] rack_meter: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.953962] i2c_algo_bit: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.977975] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.010110] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.022857] soundcore: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.034422] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.049942] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.070474] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.085972] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.102451] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.118814] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.813073] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.820183] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   19.022406] bluetooth: Unknown symbol mcount 
(err 0)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=8c8a4ee6-57e4-4d02-9196-6c4620ee5883
  InstallationDate: Installed on 2016-09-28 (1 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release powerpc 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enP1p5s4f1  no wireless extensions.
   
   enP1p5s4f0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 1e54:2030 TypeMatrix 2030 USB Keyboard
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 003: ID 05ac:8207 Apple, Inc. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: root=UUID=fd6c3ae7-7de7-416e-8bed-b4513658ee6d ro quiet 
splash verbose
  ProcVersionSignature: Ubuntu 4.4.0-21.37-powerpc64-smp 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: 

[Kernel-packages] [Bug 1629057] Re: linux: 4.8.0-19.21 -proposed tracker

[Brad Figg]

** Changed in: kernel-development-workflow/prepare-package
   Status: Confirmed => Fix Released

** Changed in: kernel-development-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Leann Ogasawara 
(leannogasawara)

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

Title:
  linux: 4.8.0-19.21 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-19.21 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 --
  derivative-trackers-created: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1629057] Re: linux: 4.8.0-19.21 -proposed tracker

[Brad Figg]

** Changed in: kernel-development-workflow/prepare-package-signed
   Status: Confirmed => Fix Released

** Changed in: kernel-development-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner 
(timg-tpi)

** Description changed:

  This bug is for tracking the 4.8.0-19.21 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
  
- kernel-phase-changed:Thursday, 29. September 2016 18:30 UTC
- kernel-phase:Packaging
- 
  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging
+ kernel-phase-changed:Friday, 30. September 2016 00:45 UTC
+ kernel-phase:Uploaded

** Description changed:

  This bug is for tracking the 4.8.0-19.21 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 --
  derivative-trackers-created: true
- phase: Packaging
- kernel-phase-changed:Friday, 30. September 2016 00:45 UTC
- kernel-phase:Uploaded
+ phase: Uploaded

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

Title:
  linux: 4.8.0-19.21 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-19.21 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 --
  derivative-trackers-created: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1628279] Re: python utilities script suffix (.py) should be removed as per Policy 10.4

[Eric Desrochers]

Following a discussion with Aron Xu, and he feels more comfortable with
the approach to rename the utilities during the debian/rules "build"
target before you get to the dh_install invocation.

Richard Laager, feel free to resubmit the patch that you did, otherwise
I'll do it on your behalf.

Eric

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

Title:
  python utilities script suffix (.py) should be removed as per Policy
  10.4

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  The zfs utilities scripts shipped with debian and ubuntu such as :

  * arc_summary.py : Provides a summary of the statistics
  https://github.com/zfsonlinux/zfs/blob/master/cmd/arc_summary

  * arcstat.py : Print out ZFS ARC Statistics exported via kstat(1)
  https://github.com/zfsonlinux/zfs/tree/master/cmd/arcstat

  * dbufstat.py : Print out statistics for all cached dmu buffers
  https://github.com/zfsonlinux/zfs/blob/master/cmd/dbufstat

  should be renamed according to Policy 10.4 :

  [https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts]

  "When scripts are installed into a directory in the system PATH, the
  script name should not include an extension such as .sh or .pl that
  denotes the scripting language currently used to implement it."

  Ideally, this should be fixed and upstreamed to Debian (or to zfslinux
  upstream) as well.

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

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

[Kernel-packages] [Bug 1602577] Re: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

[William Grant]

(For those playing at home, the boot failure in comment #25 was because
the m400 firmware preloads the dtb at 0x400300, which was clobbered
by the >16MiB kernel. The latest 4.8 builds are gzipped, so they're
short enough to leave it intact.)

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

Title:
  [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

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

Bug description:
  Hi,

  In order to investigate bug LP#1531768, we upgraded some arm64 compute
  nodes (swirlices) to a 4.4 kernel. I think it made the VMs work
  better, but the hosts became extremely unstable.

  After some time, getting a shell on them would be impossible.
  Connecting on the VSP, you'd get a prompt, and once you typed your
  username and password, you'd see the motd but the shell would never
  spawn.

  Because of these instability issues, all the arm64 compute nodes are
  now back on 4.2. However, we managed to capture "perf record" data
  when a host was failing. I'll attach it to the bug. Perhaps it will
  give you hints as to what we can do to help you troubleshoot this bug
  further.

  Once we have your instructions, we'll happily reboot one (or a few)
  nodes to 4.4 to continue troubleshooting.

  Thanks !
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 12 12:54 seq
   crw-rw 1 root audio 116, 33 Jul 12 12:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: arm64
  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: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l
  ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-41-generic N/A
   linux-backports-modules-4.2.0-41-generic  N/A
   linux-firmware1.127.22
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 4.2.0-41-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1575467] Re: [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts-utopic-vy2yyy/linux-lts-utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743 vlv_wait_port_rea

[mattias]

Sorry i typed The same massage twice

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1575467

Title:
  [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts-
  utopic-vy2yyy/linux-lts-
  utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743
  vlv_wait_port_ready+0x126/0x170 [i915]()

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

Bug description:
  After upgrading from stock Ubuntu 14.04 to 16.04 my laptop
  consistently freezes up and is unresponsive to keyboard or mouse. The
  only way is to do a hard shutdown. I'm usually in a browser when this
  happens, and often watching a video or two. It seems to happen more
  often in Google Chrome than Firefox, but it happens with both. It has
  happened at least once with no videos loaded. I haven’t observed it
  freeze / hang when I’m not in a browser, but that's mainly what i use
  my laptop for, so that's where most of my time is spent.

  Call trace:
  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575467/+attachment/4648682/+files/kern.log.2.gz

  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrew 1949 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=e8aaee7c-d956-4519-94f0-cf7aad745020
  InstallationDate: Installed on 2015-08-08 (263 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Dell Inc. Inspiron 3451
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=d01f07be-c906-4024-8eef-a58ba3935298 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (4 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 12/05/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0H4MK6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd12/05/2014:svnDellInc.:pnInspiron3451:pvrA00:rvnDellInc.:rn0H4MK6:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3451
  dmi.product.version: A00
  dmi.sys.vendor: Dell Inc.

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

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

Re: [Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

[Seth Forshee]

> Can you say whether it's the second problem that was breaking the desktop
> coming up on login?  IOW, I observed two problems.  One was a freeze during
> the boot process, and the other was a freeze during the login process
> (although the latter wasn't a total freeze, as ssh still worked).

As far as I can tell from the history here,
CONFIG_HARDENED_USERCOPY_PAGESPAN was responsible for the desktop not
coming up. Having the "rewind the stack before do_exit()" patch in
combination with that option prevented booting, becuase the usercopy
hardening created an oops that triggered the code paths affected by the
patch (but I'm still not sure what about that patch caused boot to
hang).

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

Title:
  4.8.0 kernels do not complete boot process on VM

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux-raspi2 source package in Yakkety:
  Fix Committed

Bug description:
  On my native amd64 box, 4.8.0-15 works just fine, but on my VMWare
  Fusion 8.5 system, none of the 4.8.0 kernels complete the boot
  process.  I tried 4.8.0-15 from yakkety and 4.8.0-16 from yakkety-
  proposed.

  Currently  I am seeing the last message in my console at boot up as:

  [ OK ] Started Bluetooth service

  and then... it just sits there.

  Through the use of snapshots, restores, and package bisects, I've
  definitively narrowed it to linux-generic linux-image-generic and
  linux-headers-generic.

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

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

[Kernel-packages] [Bug 1628976] Re: Ubuntu 16.10: Oops panic in move_page_tables/page_remove_rmap after running memory_stress_ng.

[Leann Ogasawara]

** Tags added: kernel-4.8

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

Title:
  Ubuntu 16.10: Oops panic in move_page_tables/page_remove_rmap after
  running memory_stress_ng.

Status in linux package in Ubuntu:
  New

Bug description:
  FYI Canonical:

  We have been seeing various page handling issues during memory stress
  in the 4.8 kernels.  The following is the most recent issue resulting
  in system panics on this host after the 4.8.0-17 update:

  == Comment: #17 - PAVITHRA R. PRAKASH - 2016-09-28 06:26:21 ==
  Hi,

  Tried running on 4.8.0-17-generic kernel. Getting below call trace and
  system crashes. Attaching logs.

  [ 2959.364333] Unable to handle kernel paging request for data at address 
0xf2fe4020
  [ 2959.364345] Faulting instruction address: 0xc02bb2a0
  [ 2959.364356] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 2959.364364] SMP NR_CPUS=2048 NUMA pSeries
  [ 2959.364377] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag 
udp_diag inet_diag unix_diag af_packet_diag netlink_diag bnx2x mdio libcrc32c 
pseries_rng vmx_crypto binfmt_misc ip_tables x_tables autofs4 ibmvscsi 
crc32c_vpmsum
  [ 2959.364441] CPU: 13 PID: 108 Comm: oom_reaper Not tainted 4.8.0-17-generic 
#19-Ubuntu
  [ 2959.364452] task: c004fbdf9c00 task.stack: c004fbe0
  [ 2959.364461] NIP: c02bb2a0 LR: c0300618 CTR: 
c009ca40
  [ 2959.364471] REGS: c004fbe036e0 TRAP: 0300   Not tainted  
(4.8.0-17-generic)
  [ 2959.364481] MSR: 80010280b033   
CR: 24028844  XER: 200c
  [ 2959.364526] CFAR: c0300614 DAR: f2fe4020 DSISR: 4000 
SOFTE: 1 
 GPR00: c0300618 c004fbe03960 c14e5e00 
f2fe4000 
 GPR04: 0001 0800  
c1665e00 
 GPR08: f900a196 0001 02fe4000 
 
 GPR12: 8800 c1b37500 0008 
c1ffe7ff 
 GPR16: c004f62a55f0 3fff9a00 3fff9900 
 
 GPR20: c004fbe03b80 c004e0713800 8e017c3302c0 
0001 
 GPR24: c000fb3614c8 c000fce9d990 c000fce9d6e4 
96a100f90b40 
 GPR28: f2fe4000 c000fb3614c8 0001 
f2fe4000 
  [ 2959.364673] NIP [c02bb2a0] page_remove_rmap+0x30/0x4b0
  [ 2959.364685] LR [c0300618] zap_huge_pmd+0xf8/0x480
  [ 2959.364692] Call Trace:
  [ 2959.364699] [c004fbe03960] [c004fbe039a0] 0xc004fbe039a0 
(unreliable)
  [ 2959.364714] [c004fbe039a0] [c0300618] zap_huge_pmd+0xf8/0x480
  [ 2959.364726] [c004fbe039f0] [c02a68d8] 
unmap_page_range+0xd08/0xee0
  [ 2959.364740] [c004fbe03b20] [c025c474] 
__oom_reap_task+0x204/0x2c0
  [ 2959.364752] [c004fbe03c80] [c025cda8] oom_reaper+0x1e8/0x300
  [ 2959.364765] [c004fbe03d80] [c00fd120] kthread+0x110/0x130
  [ 2959.364778] [c004fbe03e30] [c00098f0] 
ret_from_kernel_thread+0x5c/0x6c
  [ 2959.364788] Instruction dump:
  [ 2959.364796] 3c4c0123 3842ab90 7c0802a6 fba1ffe8 fbc1fff0 fbe1fff8 f8010010 
f821ffc1 
  [ 2959.364821] 7c7f1b78 7c9e2378 6000 6000  71480001 
392a 40820008 
  [ 2959.364871] ---[ end trace 178b14c6911b70dc ]---
  [ 2959.372762] 
  [ 2959.372798] Sending IPI to other CPUs
  [ 2959.373834] IPI complete

  Thanks,
  Pavithra

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

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

[Kernel-packages] [Bug 1628988] Re: ISST-LTE:Ubuntu1610: UbuntuKVM 16.10 guest crashed after 30 hours of stress testing

[Leann Ogasawara]

** Tags added: kernel-4.8

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

Title:
  ISST-LTE:Ubuntu1610: UbuntuKVM 16.10 guest crashed after 30 hours of
  stress testing

Status in linux package in Ubuntu:
  New

Bug description:
  After running Stress tests for 30 hours, Ubuntu16.10 KVM guest crashed
  and entered xmon.

  Guest Build:
  --
  4.8.0-16-generic

  Tests started on guest:
  --
  BASE: LTP Base tests.. 
  IO: admndisk, aio, fstest tests (on btrfs file system over 6 partitions of 2 
disks).
  TCP: TCP commands: telnet, ssh, rlogin, ping etc..

  XMON traces:
  --
  4:mon> t
  [c0017ffcf800] c024385c end_page_writeback+0x7c/0x120
  [c0017ffcf830] d22d8298 ext4_finish_bio+0x1f0/0x2e0 [ext4]
  [c0017ffcf910] d22d8928 ext4_end_bio+0x70/0x170 [ext4]
  [c0017ffcf9a0] c04c96cc bio_endio+0xfc/0x120
  [c0017ffcf9d0] c04d5f50 blk_update_request+0xf0/0x4d0
  [c0017ffcfa60] c06df2dc scsi_end_request+0x6c/0x260
  [c0017ffcfad0] c06e32a4 scsi_io_completion+0x2d4/0x740
  [c0017ffcfba0] c06d6714 scsi_finish_command+0x144/0x200
  [c0017ffcfc20] c06e25a8 scsi_softirq_done+0x198/0x200
  [c0017ffcfca0] c04e2e98 __blk_mq_complete_request_remote+0x38/0x50
  [c0017ffcfcd0] c0183e80 flush_smp_call_function_queue+0xd0/0x220
  [c0017ffcfd50] c0047aac smp_ipi_demux+0xac/0x110
  [c0017ffcfd90] c00738e4 icp_hv_ipi_action+0x64/0xd0
  [c0017ffcfe00] c01466d0 __handle_irq_event_percpu+0x90/0x340
  [c0017ffcfec0] c01469bc handle_irq_event_percpu+0x3c/0x90
  [c0017ffcff00] c014ced4 handle_percpu_irq+0x84/0xd0
  [c0017ffcff30] c0145664 generic_handle_irq+0x54/0x80
  [c0017ffcff60] c0015b20 __do_irq+0x80/0x230
  [c0017ffcff90] c002a2e0 call_do_irq+0x14/0x24
  [c0013073b210] c0015d68 do_IRQ+0x98/0x140
  [c0013073b260] c00026d8 hardware_interrupt_common+0x158/0x180
  --- Exception: 501 (Hardware Interrupt) at c008fe4c 
plpar_hcall_norets+0x1c/0x28
  [link register   ] c006c094 __spin_yield+0xa4/0xb0
  [c0013073b550] c0017fe28b00 (unreliable)
  [c0013073b5c0] c0949758 _raw_spin_lock_irqsave+0x128/0x130
  [c0013073b600] d17222cc ibmvscsi_queuecommand+0x54/0x4b0 
[ibmvscsi]
  [c0013073b6b0] c06dfc80 scsi_dispatch_cmd+0x140/0x370
  [c0013073b730] c06e1ad0 scsi_queue_rq+0x770/0x920
  [c0013073b800] c04e62f4 __blk_mq_run_hw_queue+0x2e4/0x570
  [c0013073b910] c04e5fc8 blk_mq_run_hw_queue+0xf8/0x140
  [c0013073b940] c04e8f90 blk_mq_flush_plug_list+0x160/0x1b0
  [c0013073b9c0] c04d7fbc blk_flush_plug_list+0xfc/0x2b0
  [c0013073ba30] c04d8708 blk_finish_plug+0x58/0x80
  [c0013073ba60] d22d270c ext4_writepages+0x6c4/0xe60 [ext4]
  [c0013073bbf0] c025ae80 do_writepages+0x60/0xc0
  [c0013073bc20] c0246c18 __filemap_fdatawrite_range+0x108/0x190
  [c0013073bcc0] c0246f20 filemap_write_and_wait_range+0x70/0xf0
  [c0013073bd00] d22c5944 ext4_sync_file+0x24c/0x5a0 [ext4]
  [c0013073bd60] c0365a28 vfs_fsync_range+0x78/0x130
  [c0013073bdb0] c0365b90 do_fsync+0x60/0xb0
  [c0013073be00] c0366000 SyS_fsync+0x30/0x50
  [c0013073be30] c00095e0 system_call+0x38/0x108
  --- Exception: c00 (System Call) at 3fff7b26cc98
  SP (3fffc42b5280) is in userspace
  4:mon> e
  cpu 0x4: Vector: 300 (Data Access) at [c0017ffcf520]
  pc: c025b4ec: test_clear_page_writeback+0x1ec/0x300
  lr: c025b4c0: test_clear_page_writeback+0x1c0/0x300
  sp: c0017ffcf7a0
 msr: 80009033
 dar: 2d0
   dsisr: 4000
current = 0xc00036f59880
paca= 0xc7b82400   softe: 0irq_happened: 0x09
  pid   = 1102, comm = create_datafile
  Linux version 4.8.0-16-generic (buildd@bos01-ppc64el-007) (gcc version 6.2.0 
20160914 (Ubuntu 6.2.0-3ubuntu15) ) #17-Ubuntu SMP Thu Sep 22 22:45:44 UTC 2016 
(Ubuntu 4.8.0-16.17-generic 4.8.0-rc7)
  4:mon>
  4:mon>
  4:mon> r
  R00 = c025b4c0   R16 = 0550
  R01 = c0017ffcf7a0   R17 = 7fff
  R02 = c10af400   R18 = 
  R03 =    R19 = c00172e35b00
  R04 =    R20 = c00035f831b0
  R05 = ffe0   R21 = 0001
  R06 = fffe   R22 = 0002
  R07 = f800   R23 = 0400
  R08 = 00017f18   R24 = 
  R09 =    R25 = c10f00c4
  R10 = 00017f18   R26 = 
  R11 = 0230   R27 = c00072873518
  R12 = 

Re: [Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

[Barry Warsaw]

Thanks for the extra details Seth.

Can you say whether it's the second problem that was breaking the desktop
coming up on login?  IOW, I observed two problems.  One was a freeze during
the boot process, and the other was a freeze during the login process
(although the latter wasn't a total freeze, as ssh still worked).

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

Title:
  4.8.0 kernels do not complete boot process on VM

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux-raspi2 source package in Yakkety:
  Fix Committed

Bug description:
  On my native amd64 box, 4.8.0-15 works just fine, but on my VMWare
  Fusion 8.5 system, none of the 4.8.0 kernels complete the boot
  process.  I tried 4.8.0-15 from yakkety and 4.8.0-16 from yakkety-
  proposed.

  Currently  I am seeing the last message in my console at boot up as:

  [ OK ] Started Bluetooth service

  and then... it just sits there.

  Through the use of snapshots, restores, and package bisects, I've
  definitively narrowed it to linux-generic linux-image-generic and
  linux-headers-generic.

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

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

[Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

[Seth Forshee]

I just wanted to add a note here to clarify things a little bit, since
from the comments here it's all a bit muddled. There are two loosely
related things happening.

The first problem, which is fixed by setting
CONFIG_HARDENED_USERCOPY_PAGESPAN=n, is that some security enhancements
were added in kernel version 4.8 related to copying memory from
userspace. One of these hardening features was to check for copies from
userspace which cross a page boundary, and when this happens the kernel
logs an error and terminates the running task immediately by causing it
to oops. This turned out to be too aggressive for now, because the
vmwgfx module is doing these sorts of memory copies from userspace.
Therefore when CONFIG_HARDENED_USERCOPY_PAGESPAN was enabled and the
kernel booted in VMWare Fusion, Barry was getting an oops.

This triggered the second problem. There's also a patch in 4.8 which
aims to make oopsing behave more reliably by calling do_exit() with a
clean stack, and this seems to be causing some sort of problems on
VMWare Fusion when the kernel oopses. The exact nature of those problems
isn't yet clear. Fixing the problem above side steps the problems caused
by this patch as it prevents the oops from happening, however I suspect
that the problem remains.

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

Title:
  4.8.0 kernels do not complete boot process on VM

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux-raspi2 source package in Yakkety:
  Fix Committed

Bug description:
  On my native amd64 box, 4.8.0-15 works just fine, but on my VMWare
  Fusion 8.5 system, none of the 4.8.0 kernels complete the boot
  process.  I tried 4.8.0-15 from yakkety and 4.8.0-16 from yakkety-
  proposed.

  Currently  I am seeing the last message in my console at boot up as:

  [ OK ] Started Bluetooth service

  and then... it just sits there.

  Through the use of snapshots, restores, and package bisects, I've
  definitively narrowed it to linux-generic linux-image-generic and
  linux-headers-generic.

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

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

[Kernel-packages] [Bug 344878] Re: file name too long when creating new file (ecryptfs_lookup: lookup_one_len() returned [-36] on lower_dentry)

[frans daniel]

Long too path error!
"Long path tool" is very helpful for this problem. You can solve this problem 
like copy, delete, long path files by using this tool.
I used to have similar problems too, but after using "long path tool" 
everything was solved.

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

Title:
  file name too long when creating new file (ecryptfs_lookup:
  lookup_one_len() returned [-36] on lower_dentry)

Status in eCryptfs:
  Fix Released
Status in ecryptfs-utils package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in ecryptfs-utils source package in Natty:
  Won't Fix
Status in linux source package in Natty:
  Won't Fix
Status in ecryptfs-utils source package in Oneiric:
  Won't Fix
Status in linux source package in Oneiric:
  Won't Fix
Status in ecryptfs-utils source package in Precise:
  Invalid
Status in linux source package in Precise:
  Fix Released

Bug description:
  ===
  IMPORTANT: eCryptfs can only store filenames of up to 143 characters when 
filename encryption is enabled. The remaining 112 characters are used for 
storing metadata such as the encrypted filename prefix, the signature of the 
filename encryption key, and an identifier for the cipher used, as well as 
random bytes to make /foo/file and /bar/file encrypt to different ciphertext 
and padding bytes to achieve proper cipher block size alignment.

  This bug is considered 'fixed' by the upstream maintainers. The
  eCryptfs kernel error message has been reduced to a debug level log
  message and eCryptfs now correctly reports its maximum supported
  filename length through the statfs() syscall. This is all that can be
  done without implementing a completely new encrypted filename design.
  A design that allows 255 character filenames without introducing other
  design limitations has not been identified and no one is currently
  working to come up with such a design.

  Please do not add comments or create new bugs saying that mv reports
  'File name too long' or that you can't create a long filename in your
  eCryptfs mounts. It is an unfortunate design limitation that cannot be
  avoided at this time.

  Please do create new bugs when an application generates filenames that are 
too long to be stored in an eCryptfs mount. The application may be able to use 
the statfs() syscall to check the filename length limits of eCryptfs. Note that 
this does not include something like a torrent or ftp client trying to download 
a file with a long filename. The application is not generating the filename in 
those cases, it is just downloading the file that the user told it to download.
  ===

  When trying to create a new file with a relatively long filename (f. ex. 
dfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqb.txt)
  I get an error: file name to long, when in fact the file name is not to long, 
but the encrypted name created for this file is to long, so, the file was not 
created.

  this is no problem when I try to create a file, but when I'm copying a
  lot of files to my home folder I get some: filename to long error's
  and it's hard to fix (first locate the file, create shorter name, move
  again)

  so, maybe you could create a check for to long filenames?

  I'm using ext4 here...

  mv 
dfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqb.txt
 /home/jens/
  mv: cannot stat 
`/home/jens/dfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqb.txt':
 File name too long

  libecryptfs0:
    Installed: 71-0ubuntu2
    Candidate: 71-0ubuntu2
    Version table:
   *** 71-0ubuntu2 0
  500 http://be.archive.ubuntu.com jaunty/main Packages
  100 /var/lib/dpkg/status

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

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

[Kernel-packages] [Bug 1611124] Re: W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915

[Seth Forshee]

@emk2203 - Intel still has not released this firmware publicly anywhere
that I can find, and that firmware specifically is only going to help if
you have a kaby lake processor.

What you should do is open a new bug following one of these crashes by
running 'ubuntu-bug linux' in a terminal. This will attach your machine
information and logs to help us understand the problems you're seeing.
Thanks!

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

Title:
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin
  for module i915

Status in xen:
  Unknown
Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  $sudo dpkg -i linux-image-4.8.0-040800rc1-lowlatency

  [...]

  update-initramfs: Generating /boot/initrd.img-4.8.0-040800rc1-lowlatency
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for 
module i915
  W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module 
i915

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-firmware 1.159
  Uname: Linux 4.8.0-040800rc1-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  Date: Mon Aug  8 17:50:38 2016
  Dependencies:
   
  InstallationDate: Installed on 2015-07-26 (379 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

[Tim Gardner]

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

** Changed in: linux-raspi2 (Ubuntu Yakkety)
   Status: New => Fix Committed

** Changed in: linux-raspi2 (Ubuntu Yakkety)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  4.8.0 kernels do not complete boot process on VM

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux-raspi2 source package in Yakkety:
  Fix Committed

Bug description:
  On my native amd64 box, 4.8.0-15 works just fine, but on my VMWare
  Fusion 8.5 system, none of the 4.8.0 kernels complete the boot
  process.  I tried 4.8.0-15 from yakkety and 4.8.0-16 from yakkety-
  proposed.

  Currently  I am seeing the last message in my console at boot up as:

  [ OK ] Started Bluetooth service

  and then... it just sits there.

  Through the use of snapshots, restores, and package bisects, I've
  definitively narrowed it to linux-generic linux-image-generic and
  linux-headers-generic.

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

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

Re: [Kernel-packages] [Bug 1561474] Re: Bluetooth will be disable after resume from suspend on Xenial

[erintiransom]

Yes, sometimes.

Something else that's curious: sometimes I have a problem with the graphics
after Ubuntu wakes up from sleep, there is a black box around all menus and
anything I point out with the mouse. I found a complicated solution years
ago -this happened in Ubuntu 15.10 too- but recently I found it's easier to
switch to any terminal (CTRL + ALT + F2 / F3 / ... not F7) and go back to
the GUI (CTRL + ALT + F7). This fixes the problem with the graphic card
(NVIDIA something). The curious thing, though, is that it sometimes will
ALSO fix the problem with the bluetooth. Only sometimes. WEIRD.

El dj., 29 set. 2016 a les 21:25, Przemyslaw Kujawski ()
va escriure:

> I can confirm that sometimes  bluetooth is enabled after system resume.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1611188).
> https://bugs.launchpad.net/bugs/1561474
>
> Title:
>   Bluetooth will be disable after resume from suspend on Xenial
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1561474/+subscriptions
>
-- 
Israel Planagumà
israelplanag...@gmail.com

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

Title:
  Bluetooth will be disable after resume from suspend on Xenial

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201208-11536 Dell Latitude 6430u

  The Bluetooth will be disabled after resume from suspend.
  You will need to use "hciconfig hci0 reset" to enable it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-15-generic 4.4.0-15.31
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1202 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 24 19:14:07 2016
  HibernationDevice: RESUME=UUID=25c03762-079c-4c6d-aedb-ec768318a6bf
  InstallationDate: Installed on 2016-03-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  MachineType: Dell Inc. Latitude 6430U
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=18cfda3e-4f3d-40cf-8e7e-a83030819487 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/15/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.asset.tag: 1234567
  dmi.board.name: 0MN74V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X01
  dmi.chassis.asset.tag: 1234567
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd11/15/2012:svnDellInc.:pnLatitude6430U:pvr01:rvnDellInc.:rn0MN74V:rvrX01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 6430U
  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/1561474/+subscriptions

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

[Kernel-packages] [Bug 1619592] Re: Lenovo g50-30 Elantech Touchpad stops working after some time in ubuntu 16.04

[aswin venugopal]

I have solved the issue by installing xserver-xorg-input-libinput.

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

Title:
  Lenovo g50-30 Elantech Touchpad stops working after some time in
  ubuntu 16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The elantech touchpad works on booting into the system but stops
  working after sometime.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-36-generic 4.4.0-36.55
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aswin  3895 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep  2 15:24:26 2016
  HibernationDevice: RESUME=UUID=d6fbfa44-941c-448e-a1b4-d5a0ddd4e37e
  InstallationDate: Installed on 2015-12-08 (268 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: LENOVO 80G0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=10532e9a-374a-4f9b-ae32-8da8ed306fb5 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-08-31 (1 days ago)
  dmi.bios.date: 10/21/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: NANANANANO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN44WW:bd10/21/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.name: 80G0
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1628968] Re: powerpc 4.8.0-17 fails to boot on PowerMac G5

[Tim Gardner]

One thing I noticed is that the missing symbol references are truncated
from the original, e.g.,

mcount -> _mcount
cache_dir_open -> dcache_dir_open
iffies -> jiffies
ence_release -> fence_release

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

Title:
  powerpc 4.8.0-17 fails to boot on PowerMac G5

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

Bug description:
  Not much else to say. The system fails to complete booting, it gets
  stuck somewhere before network comes up; with errors in syslog about
  missing symbols for some modules (see
  http://paste.ubuntu.com/23251408/). Boots fine in 4.4.0-21:

  Sep 28 12:49:55 fujin kernel: [4.698092] uninorth_agp: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.715284] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.731545] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759718] drm: Unknown symbol ence_release 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759781] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.777863] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.798476] drm: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.815248] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.826136] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.846026] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.862106] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.882364] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.898322] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.914094] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.930108] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [5.396683] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [7.609956] autofs4: Unknown symbol 
cache_dir_open (err 0)
  Sep 28 12:49:55 fujin kernel: [7.610137] autofs4: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [9.989854] parport: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.405448] shpchp: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.684111] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.826081] rack_meter: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.953962] i2c_algo_bit: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.977975] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.010110] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.022857] soundcore: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.034422] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.049942] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.070474] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.085972] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.102451] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.118814] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.813073] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.820183] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   19.022406] bluetooth: Unknown symbol mcount 
(err 0)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=8c8a4ee6-57e4-4d02-9196-6c4620ee5883
  InstallationDate: Installed on 2016-09-28 (1 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release powerpc 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enP1p5s4f1  no wireless extensions.
   
   enP1p5s4f0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 1e54:2030 TypeMatrix 2030 USB Keyboard
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 003: ID 05ac:8207 Apple, Inc. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: root=UUID=fd6c3ae7-7de7-416e-8bed-b4513658ee6d ro quiet 
splash verbose
  ProcVersionSignature: Ubuntu 4.4.0-21.37-powerpc64-smp 4.4.6
  PulseList: Error: 

[Kernel-packages] [Bug 1561474] Re: Bluetooth will be disable after resume from suspend on Xenial

[Przemyslaw Kujawski]

I can confirm that sometimes  bluetooth is enabled after system resume.

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

Title:
  Bluetooth will be disable after resume from suspend on Xenial

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201208-11536 Dell Latitude 6430u

  The Bluetooth will be disabled after resume from suspend.
  You will need to use "hciconfig hci0 reset" to enable it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-15-generic 4.4.0-15.31
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1202 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 24 19:14:07 2016
  HibernationDevice: RESUME=UUID=25c03762-079c-4c6d-aedb-ec768318a6bf
  InstallationDate: Installed on 2016-03-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  MachineType: Dell Inc. Latitude 6430U
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=18cfda3e-4f3d-40cf-8e7e-a83030819487 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/15/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.asset.tag: 1234567
  dmi.board.name: 0MN74V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X01
  dmi.chassis.asset.tag: 1234567
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd11/15/2012:svnDellInc.:pnLatitude6430U:pvr01:rvnDellInc.:rn0MN74V:rvrX01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 6430U
  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/1561474/+subscriptions

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

[Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

[Tim Gardner]

UBUNTU: [Config] CONFIG_HARDENED_USERCOPY_PAGESPAN=n

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

Title:
  4.8.0 kernels do not complete boot process on VM

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  On my native amd64 box, 4.8.0-15 works just fine, but on my VMWare
  Fusion 8.5 system, none of the 4.8.0 kernels complete the boot
  process.  I tried 4.8.0-15 from yakkety and 4.8.0-16 from yakkety-
  proposed.

  Currently  I am seeing the last message in my console at boot up as:

  [ OK ] Started Bluetooth service

  and then... it just sits there.

  Through the use of snapshots, restores, and package bisects, I've
  definitively narrowed it to linux-generic linux-image-generic and
  linux-headers-generic.

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

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

[Kernel-packages] [Bug 1575467] Re: [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts-utopic-vy2yyy/linux-lts-utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743 vlv_wait_port_rea

[mattias]

Bug still exist in ubuntu 16.04 kernel 4.4.0-38-generic i tryied The
intel_idle.cstate_max=1 is dosnt work

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1575467

Title:
  [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts-
  utopic-vy2yyy/linux-lts-
  utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743
  vlv_wait_port_ready+0x126/0x170 [i915]()

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

Bug description:
  After upgrading from stock Ubuntu 14.04 to 16.04 my laptop
  consistently freezes up and is unresponsive to keyboard or mouse. The
  only way is to do a hard shutdown. I'm usually in a browser when this
  happens, and often watching a video or two. It seems to happen more
  often in Google Chrome than Firefox, but it happens with both. It has
  happened at least once with no videos loaded. I haven’t observed it
  freeze / hang when I’m not in a browser, but that's mainly what i use
  my laptop for, so that's where most of my time is spent.

  Call trace:
  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575467/+attachment/4648682/+files/kern.log.2.gz

  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrew 1949 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=e8aaee7c-d956-4519-94f0-cf7aad745020
  InstallationDate: Installed on 2015-08-08 (263 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Dell Inc. Inspiron 3451
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=d01f07be-c906-4024-8eef-a58ba3935298 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (4 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 12/05/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0H4MK6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd12/05/2014:svnDellInc.:pnInspiron3451:pvrA00:rvnDellInc.:rn0H4MK6:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3451
  dmi.product.version: A00
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1611124] Re: W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915

[emk2203]

Please re-open. 4.8 is now the official Yakkety kernel, running 4.8.0-17
and encountering this bug.

i915 crashes often, significantly affecting the machine.

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

Title:
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin
  for module i915

Status in xen:
  Unknown
Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  $sudo dpkg -i linux-image-4.8.0-040800rc1-lowlatency

  [...]

  update-initramfs: Generating /boot/initrd.img-4.8.0-040800rc1-lowlatency
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for 
module i915
  W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module 
i915

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-firmware 1.159
  Uname: Linux 4.8.0-040800rc1-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  Date: Mon Aug  8 17:50:38 2016
  Dependencies:
   
  InstallationDate: Installed on 2015-07-26 (379 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1628546] Re: 4.4.0-40-generic no prompts for disk encryption + loops on dots load screen

[Alexandre]

Ah, that makes sense, NVMe is pretty common on newer (Dell among others)
laptops.

Thanks! :)

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

Title:
  4.4.0-40-generic no prompts for disk encryption + loops on dots load
  screen

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

Bug description:
  Since the upgrade to Ubuntu's 16.04.1 Linux kernel 4.4.0-40.60, it is 
impossible to boot my machine with full root encryption. 
  It will keep loading the purple Ubuntu "dots" loading screen for ages and 
stay there.

  There is no issue rebooting back with kernel 4.4.0-38.57.

  I tried recreating the initramfs to no avail:
  update-initramfs -d -u -k 4.4.0-40-generic

  Hardware is a Dell Laptop: XPS13 9350 16GB/i7/512GB SSD.

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

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

[Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

[Barry Warsaw]

FWIW, I posted to the Fusion forums:

https://communities.vmware.com/message/2623359#2623359

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

Title:
  4.8.0 kernels do not complete boot process on VM

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  On my native amd64 box, 4.8.0-15 works just fine, but on my VMWare
  Fusion 8.5 system, none of the 4.8.0 kernels complete the boot
  process.  I tried 4.8.0-15 from yakkety and 4.8.0-16 from yakkety-
  proposed.

  Currently  I am seeing the last message in my console at boot up as:

  [ OK ] Started Bluetooth service

  and then... it just sits there.

  Through the use of snapshots, restores, and package bisects, I've
  definitively narrowed it to linux-generic linux-image-generic and
  linux-headers-generic.

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

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

[Kernel-packages] [Bug 1566302] Re: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16

[Glen]

Upgraded to 16.04 this morning, issue did not exist before today. kernel
4.4.0-38-generic, pc is no-name Intel core 2 duo cpu e7300 s.66GHz x 2,
graphics Gallium 0.4 on ATI RV370, no bluetooth, no wireless. System
will not recover from sleep or hibernate.

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

Title:
  Ubuntu 16.04: Suspend freezes the system after upgrade to linux image
  4.4.0-16

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  I'm using ubuntu 16.04 on a XPS 15 9550.

  Suspend/resume worked flawlessly with linux image 4.4.0-15, and after
  standard upgrade yesterday (5/04/2016) which installed image 4.4.0-16,
  the system freezes when attempting a suspend. I get  no response from
  the system (nor keyboard, nor screen, nor touchpad), but it gets very
  hot, so that it must be running something.

  Booting with 4.4.0-15 makes the suspend to work perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-16-generic 4.4.0-16.32
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  macias 1770 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Tue Apr  5 14:56:17 2016
  HibernationDevice: RESUME=UUID=4180adfa-3852-4a96-86b4-f3696448c743
  InstallationDate: Installed on 2016-03-07 (28 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed 
root=UUID=673f4658-75f8-4c01-bcd8-0af860269699 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1566302] Re: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16

[Glen]

This is a serious issue for me, I don't want to restart my computer
every 10 minutes!

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

Title:
  Ubuntu 16.04: Suspend freezes the system after upgrade to linux image
  4.4.0-16

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  I'm using ubuntu 16.04 on a XPS 15 9550.

  Suspend/resume worked flawlessly with linux image 4.4.0-15, and after
  standard upgrade yesterday (5/04/2016) which installed image 4.4.0-16,
  the system freezes when attempting a suspend. I get  no response from
  the system (nor keyboard, nor screen, nor touchpad), but it gets very
  hot, so that it must be running something.

  Booting with 4.4.0-15 makes the suspend to work perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-16-generic 4.4.0-16.32
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  macias 1770 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Tue Apr  5 14:56:17 2016
  HibernationDevice: RESUME=UUID=4180adfa-3852-4a96-86b4-f3696448c743
  InstallationDate: Installed on 2016-03-07 (28 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed 
root=UUID=673f4658-75f8-4c01-bcd8-0af860269699 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

[Joseph Salisbury]

This config option is intended to be used only while trying to find
anything that copies from userspace with cross page boundaries, and it
looks like some vmware driver was doing exactly that.

** Bug watch added: Red Hat Bugzilla #1373326
   https://bugzilla.redhat.com/show_bug.cgi?id=1373326

** Also affects: linux via
   https://bugzilla.redhat.com/show_bug.cgi?id=1373326
   Importance: Unknown
   Status: Unknown

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

Title:
  4.8.0 kernels do not complete boot process on VM

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  On my native amd64 box, 4.8.0-15 works just fine, but on my VMWare
  Fusion 8.5 system, none of the 4.8.0 kernels complete the boot
  process.  I tried 4.8.0-15 from yakkety and 4.8.0-16 from yakkety-
  proposed.

  Currently  I am seeing the last message in my console at boot up as:

  [ OK ] Started Bluetooth service

  and then... it just sits there.

  Through the use of snapshots, restores, and package bisects, I've
  definitively narrowed it to linux-generic linux-image-generic and
  linux-headers-generic.

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

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

[Kernel-packages] [Bug 1629057] Re: linux: 4.8.0-19.21 -proposed tracker

[Brad Figg]

** Changed in: kernel-development-workflow/prepare-package
   Status: New => Confirmed

** Changed in: kernel-development-workflow/prepare-package-meta
   Status: New => Confirmed

** Changed in: kernel-development-workflow/prepare-package-signed
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 4.8.0-19.21 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
+ 
+ kernel-phase-changed:Thursday, 29. September 2016 18:30 UTC
+ kernel-phase:Packaging

** Description changed:

  This bug is for tracking the 4.8.0-19.21 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
  
  kernel-phase-changed:Thursday, 29. September 2016 18:30 UTC
  kernel-phase:Packaging
+ 
+ -- swm properties --
+ derivative-trackers-created: true
+ phase: Packaging

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

Title:
  linux: 4.8.0-19.21 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-19.21 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

  kernel-phase-changed:Thursday, 29. September 2016 18:30 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

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

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

[Kernel-packages] [Bug 1575467] Re: [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts-utopic-vy2yyy/linux-lts-utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743 vlv_wait_port_rea

[mattias]

Running ubuntu 16.04 kernel 4.4.0-38-generic tryed The intel_idle.cstate_max=1
It dont work bug still active

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1575467

Title:
  [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts-
  utopic-vy2yyy/linux-lts-
  utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743
  vlv_wait_port_ready+0x126/0x170 [i915]()

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

Bug description:
  After upgrading from stock Ubuntu 14.04 to 16.04 my laptop
  consistently freezes up and is unresponsive to keyboard or mouse. The
  only way is to do a hard shutdown. I'm usually in a browser when this
  happens, and often watching a video or two. It seems to happen more
  often in Google Chrome than Firefox, but it happens with both. It has
  happened at least once with no videos loaded. I haven’t observed it
  freeze / hang when I’m not in a browser, but that's mainly what i use
  my laptop for, so that's where most of my time is spent.

  Call trace:
  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575467/+attachment/4648682/+files/kern.log.2.gz

  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrew 1949 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=e8aaee7c-d956-4519-94f0-cf7aad745020
  InstallationDate: Installed on 2015-08-08 (263 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Dell Inc. Inspiron 3451
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=d01f07be-c906-4024-8eef-a58ba3935298 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (4 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 12/05/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0H4MK6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd12/05/2014:svnDellInc.:pnInspiron3451:pvrA00:rvnDellInc.:rn0H4MK6:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3451
  dmi.product.version: A00
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

[Joseph Salisbury]

@Vinson Lee, it looks like you were correct about that option!

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

Title:
  4.8.0 kernels do not complete boot process on VM

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

Bug description:
  On my native amd64 box, 4.8.0-15 works just fine, but on my VMWare
  Fusion 8.5 system, none of the 4.8.0 kernels complete the boot
  process.  I tried 4.8.0-15 from yakkety and 4.8.0-16 from yakkety-
  proposed.

  Currently  I am seeing the last message in my console at boot up as:

  [ OK ] Started Bluetooth service

  and then... it just sits there.

  Through the use of snapshots, restores, and package bisects, I've
  definitively narrowed it to linux-generic linux-image-generic and
  linux-headers-generic.

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

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

[Kernel-packages] [Bug 1629057] [NEW] linux: 4.8.0-19.21 -proposed tracker

[Tim Gardner]

Public bug reported:

This bug is for tracking the 4.8.0-19.21 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

kernel-phase-changed:Thursday, 29. September 2016 18:30 UTC
kernel-phase:Packaging

-- swm properties --
derivative-trackers-created: true
phase: Packaging

** Affects: kernel-development-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-development-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-development-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-development-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-development-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

** Affects: kernel-development-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Yakkety)
 Importance: Medium
 Status: Confirmed


** Tags: block-proposed kernel-release-tracking-bug yakkety

** Tags added: kernel-release-tracking-bug

** Tags added: block-proposed

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

** Tags added: yakkety

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

** Also affects: kernel-development-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/promote-to-release
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/regression-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-development-workflow
   Status: New => In Progress

** Changed in: kernel-development-workflow
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/promote-to-proposed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

** Changed in: kernel-development-workflow/regression-testing
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/regression-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

[Kernel-packages] [Bug 1628546] Re: 4.4.0-40-generic no prompts for disk encryption + loops on dots load screen

[Joseph Salisbury]

Thanks for testing.  That is good news.  There was only one commit added
to -41 and that seems to be the fix for this bug:


commit e9820e415895bdd9cfd21f87e80e3e0a10f131f0
Author: Kamal Mostafa 
Date:   Mon Sep 26 15:29:52 2016 -0700

UBUNTU: (fix) NVMe: Don't unmap controller registers on reset


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

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

Title:
  4.4.0-40-generic no prompts for disk encryption + loops on dots load
  screen

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

Bug description:
  Since the upgrade to Ubuntu's 16.04.1 Linux kernel 4.4.0-40.60, it is 
impossible to boot my machine with full root encryption. 
  It will keep loading the purple Ubuntu "dots" loading screen for ages and 
stay there.

  There is no issue rebooting back with kernel 4.4.0-38.57.

  I tried recreating the initramfs to no avail:
  update-initramfs -d -u -k 4.4.0-40-generic

  Hardware is a Dell Laptop: XPS13 9350 16GB/i7/512GB SSD.

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

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

[Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

[Joseph Salisbury]

I built a Yakkety test kernel with CONFIG_HARDENED_USERCOPY_PAGESPAN
disabled.

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1627198

Can you test that kernel and report back if it has the bug or not?

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

Title:
  4.8.0 kernels do not complete boot process on VM

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

Bug description:
  On my native amd64 box, 4.8.0-15 works just fine, but on my VMWare
  Fusion 8.5 system, none of the 4.8.0 kernels complete the boot
  process.  I tried 4.8.0-15 from yakkety and 4.8.0-16 from yakkety-
  proposed.

  Currently  I am seeing the last message in my console at boot up as:

  [ OK ] Started Bluetooth service

  and then... it just sits there.

  Through the use of snapshots, restores, and package bisects, I've
  definitively narrowed it to linux-generic linux-image-generic and
  linux-headers-generic.

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

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

[Kernel-packages] [Bug 1628204] modoc (ppc64el) - tests ran: 1, failed: 1

[Brad Figg]

tests ran:   1, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-41.61/modoc__4.4.0-41.61__2016-09-29_17-35-00/results-index.html

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

Title:
  linux: 4.4.0-41.61 -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 Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-41.61 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
  derivative-trackers-created: 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/1628204/+subscriptions

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

[Kernel-packages] [Bug 1628204] dwalin (amd64) - tests ran: 64, failed: 0

[Brad Figg]

tests ran:  64, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-41.61/dwalin__4.4.0-41.61__2016-09-29_16-34-00/results-index.html

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

Title:
  linux: 4.4.0-41.61 -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 Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-41.61 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
  derivative-trackers-created: 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/1628204/+subscriptions

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

[Kernel-packages] [Bug 1628336] Re: mount-image-callback cannot mount partitioned disk image

[Tim Gardner]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
 Assignee: Stefan Bader (smb)
   Status: Confirmed

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

Title:
  mount-image-callback cannot mount partitioned disk image

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

Bug description:
  This fails on 4.8.0-17-generic and passes on 4.4.0-9136-generic

  $ sudo apt-get update
  $ sudo apt-get install -qy cloud-image-utils
  $ wget 
http://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-disk1.img
  $ cp xenial-server-cloudimg-amd64-disk1.img disk.img
  $ sudo mount-image-callback xenial-server-cloudimg-amd64-disk1.img -v ls 
_MOUNTPOINT_
  replaced string _MOUNTPOINT_ in arguments arg 1
  waiting on pidfile for /dev/nbd0 in /sys/block/nbd0/pid
  connected xenial-server-cloudimg-amd64-disk1.img (qcow2) to /dev/nbd0. 
waiting for device.
  partitioned disk.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  gave up on waiting for /dev/nbd0p1
  $ echo $?
  1

  On an identical system other than 'apt-get install linux-virtual' to
  get the new kernel, you see:

  $ uname -r
  4.4.0-9136-generic

  $ sudo mount-image-callback disk.img -v ls _MOUNTPOINT_
  replaced string _MOUNTPOINT_ in arguments arg 1
  waiting on pidfile for /dev/nbd0 in /sys/block/nbd0/pid
  connected disk.img (qcow2) to /dev/nbd0. waiting for device.
  partitioned disk.
  mounted /dev/nbd0p1 via qemu-nbd /dev/nbd0
  invoking: MOUNTPOINT=/tmp/mount-image-callback.Y8D4lk/mp ls 
/tmp/mount-image-callback.Y8D4lk/mp
  bin   etc lib   media  proc  sbin  sys  var
  boot  homelib64   mntroot  snap  tmp  vmlinuz
  dev   initrd.img  lost+found  optrun   srv   usr
  cmd returned 0. unmounting /tmp/mount-image-callback.Y8D4lk/mp

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-17-generic 4.8.0-17.19
  ProcVersionSignature: User Name 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 27 19:04 seq
   crw-rw 1 root audio 116, 33 Sep 27 19:04 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Sep 28 00:58:49 2016
  Ec2AMI: ami-0438
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=072136f3-5666-4381-83bd-8d7175059be3 ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1~cloud0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-vivid
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1~cloud0:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr12.0.3:cvnQEMU:ct1:cvrpc-i440fx-vivid:
  dmi.product.name: OpenStack Nova
  dmi.product.version: 12.0.3
  dmi.sys.vendor: OpenStack Foundation

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

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

[Kernel-packages] [Bug 1628336] Re: mount-image-callback cannot mount partitioned disk image

[Stefan Bader]

Looking further into it, this is somehow caused by changes to the nbd
module. Before 4.8 it was actually not creating any uevents on its own.
Still there were events to be seen. With 4.8 they code changed to
generate a change event, but also will delay the capacity change until
the moment the socket is connected. And this seems to prevent whatever
is otherwise producing the change event and triggering a partition scan.
The nbd driver itself does not do that (like for example the loop driver
does). So it could be that this had ever worked only because of the
mysterious helper.

It seems that reverting a bit back to change the capacity as soon as it
is set by ioctl (there are three ioctls which do this, so the values
likely get touched multiple times, too) will again get the partition
detected reliably. Not sure this can be guaranteed always...

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

Title:
  mount-image-callback cannot mount partitioned disk image

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

Bug description:
  This fails on 4.8.0-17-generic and passes on 4.4.0-9136-generic

  $ sudo apt-get update
  $ sudo apt-get install -qy cloud-image-utils
  $ wget 
http://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-disk1.img
  $ cp xenial-server-cloudimg-amd64-disk1.img disk.img
  $ sudo mount-image-callback xenial-server-cloudimg-amd64-disk1.img -v ls 
_MOUNTPOINT_
  replaced string _MOUNTPOINT_ in arguments arg 1
  waiting on pidfile for /dev/nbd0 in /sys/block/nbd0/pid
  connected xenial-server-cloudimg-amd64-disk1.img (qcow2) to /dev/nbd0. 
waiting for device.
  partitioned disk.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  gave up on waiting for /dev/nbd0p1
  $ echo $?
  1

  On an identical system other than 'apt-get install linux-virtual' to
  get the new kernel, you see:

  $ uname -r
  4.4.0-9136-generic

  $ sudo mount-image-callback disk.img -v ls _MOUNTPOINT_
  replaced string _MOUNTPOINT_ in arguments arg 1
  waiting on pidfile for /dev/nbd0 in /sys/block/nbd0/pid
  connected disk.img (qcow2) to /dev/nbd0. waiting for device.
  partitioned disk.
  mounted /dev/nbd0p1 via qemu-nbd /dev/nbd0
  invoking: MOUNTPOINT=/tmp/mount-image-callback.Y8D4lk/mp ls 
/tmp/mount-image-callback.Y8D4lk/mp
  bin   etc lib   media  proc  sbin  sys  var
  boot  homelib64   mntroot  snap  tmp  vmlinuz
  dev   initrd.img  lost+found  optrun   srv   usr
  cmd returned 0. unmounting /tmp/mount-image-callback.Y8D4lk/mp

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-17-generic 4.8.0-17.19
  ProcVersionSignature: User Name 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 27 19:04 seq
   crw-rw 1 root audio 116, 33 Sep 27 19:04 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Sep 28 00:58:49 2016
  Ec2AMI: ami-0438
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=072136f3-5666-4381-83bd-8d7175059be3 ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1~cloud0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-vivid
  dmi.modalias: 

[Kernel-packages] [Bug 1628988] Guest lotg9 XML file

[bugproxy]

Default Comment by Bridge

** Attachment added: "Guest lotg9 XML file"
   
https://bugs.launchpad.net/bugs/1628988/+attachment/4751128/+files/lotg9_xml.txt

** Changed in: ubuntu
 Assignee: (unassigned) => Taco Screen team (taco-screen-team)

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

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

Title:
  ISST-LTE:Ubuntu1610: UbuntuKVM 16.10 guest crashed after 30 hours of
  stress testing

Status in linux package in Ubuntu:
  New

Bug description:
  After running Stress tests for 30 hours, Ubuntu16.10 KVM guest crashed
  and entered xmon.

  Guest Build:
  --
  4.8.0-16-generic

  Tests started on guest:
  --
  BASE: LTP Base tests.. 
  IO: admndisk, aio, fstest tests (on btrfs file system over 6 partitions of 2 
disks).
  TCP: TCP commands: telnet, ssh, rlogin, ping etc..

  XMON traces:
  --
  4:mon> t
  [c0017ffcf800] c024385c end_page_writeback+0x7c/0x120
  [c0017ffcf830] d22d8298 ext4_finish_bio+0x1f0/0x2e0 [ext4]
  [c0017ffcf910] d22d8928 ext4_end_bio+0x70/0x170 [ext4]
  [c0017ffcf9a0] c04c96cc bio_endio+0xfc/0x120
  [c0017ffcf9d0] c04d5f50 blk_update_request+0xf0/0x4d0
  [c0017ffcfa60] c06df2dc scsi_end_request+0x6c/0x260
  [c0017ffcfad0] c06e32a4 scsi_io_completion+0x2d4/0x740
  [c0017ffcfba0] c06d6714 scsi_finish_command+0x144/0x200
  [c0017ffcfc20] c06e25a8 scsi_softirq_done+0x198/0x200
  [c0017ffcfca0] c04e2e98 __blk_mq_complete_request_remote+0x38/0x50
  [c0017ffcfcd0] c0183e80 flush_smp_call_function_queue+0xd0/0x220
  [c0017ffcfd50] c0047aac smp_ipi_demux+0xac/0x110
  [c0017ffcfd90] c00738e4 icp_hv_ipi_action+0x64/0xd0
  [c0017ffcfe00] c01466d0 __handle_irq_event_percpu+0x90/0x340
  [c0017ffcfec0] c01469bc handle_irq_event_percpu+0x3c/0x90
  [c0017ffcff00] c014ced4 handle_percpu_irq+0x84/0xd0
  [c0017ffcff30] c0145664 generic_handle_irq+0x54/0x80
  [c0017ffcff60] c0015b20 __do_irq+0x80/0x230
  [c0017ffcff90] c002a2e0 call_do_irq+0x14/0x24
  [c0013073b210] c0015d68 do_IRQ+0x98/0x140
  [c0013073b260] c00026d8 hardware_interrupt_common+0x158/0x180
  --- Exception: 501 (Hardware Interrupt) at c008fe4c 
plpar_hcall_norets+0x1c/0x28
  [link register   ] c006c094 __spin_yield+0xa4/0xb0
  [c0013073b550] c0017fe28b00 (unreliable)
  [c0013073b5c0] c0949758 _raw_spin_lock_irqsave+0x128/0x130
  [c0013073b600] d17222cc ibmvscsi_queuecommand+0x54/0x4b0 
[ibmvscsi]
  [c0013073b6b0] c06dfc80 scsi_dispatch_cmd+0x140/0x370
  [c0013073b730] c06e1ad0 scsi_queue_rq+0x770/0x920
  [c0013073b800] c04e62f4 __blk_mq_run_hw_queue+0x2e4/0x570
  [c0013073b910] c04e5fc8 blk_mq_run_hw_queue+0xf8/0x140
  [c0013073b940] c04e8f90 blk_mq_flush_plug_list+0x160/0x1b0
  [c0013073b9c0] c04d7fbc blk_flush_plug_list+0xfc/0x2b0
  [c0013073ba30] c04d8708 blk_finish_plug+0x58/0x80
  [c0013073ba60] d22d270c ext4_writepages+0x6c4/0xe60 [ext4]
  [c0013073bbf0] c025ae80 do_writepages+0x60/0xc0
  [c0013073bc20] c0246c18 __filemap_fdatawrite_range+0x108/0x190
  [c0013073bcc0] c0246f20 filemap_write_and_wait_range+0x70/0xf0
  [c0013073bd00] d22c5944 ext4_sync_file+0x24c/0x5a0 [ext4]
  [c0013073bd60] c0365a28 vfs_fsync_range+0x78/0x130
  [c0013073bdb0] c0365b90 do_fsync+0x60/0xb0
  [c0013073be00] c0366000 SyS_fsync+0x30/0x50
  [c0013073be30] c00095e0 system_call+0x38/0x108
  --- Exception: c00 (System Call) at 3fff7b26cc98
  SP (3fffc42b5280) is in userspace
  4:mon> e
  cpu 0x4: Vector: 300 (Data Access) at [c0017ffcf520]
  pc: c025b4ec: test_clear_page_writeback+0x1ec/0x300
  lr: c025b4c0: test_clear_page_writeback+0x1c0/0x300
  sp: c0017ffcf7a0
 msr: 80009033
 dar: 2d0
   dsisr: 4000
current = 0xc00036f59880
paca= 0xc7b82400   softe: 0irq_happened: 0x09
  pid   = 1102, comm = create_datafile
  Linux version 4.8.0-16-generic (buildd@bos01-ppc64el-007) (gcc version 6.2.0 
20160914 (Ubuntu 6.2.0-3ubuntu15) ) #17-Ubuntu SMP Thu Sep 22 22:45:44 UTC 2016 
(Ubuntu 4.8.0-16.17-generic 4.8.0-rc7)
  4:mon>
  4:mon>
  4:mon> r
  R00 = c025b4c0   R16 = 0550
  R01 = c0017ffcf7a0   R17 = 7fff
  R02 = c10af400   R18 = 
  R03 =    R19 = c00172e35b00
  R04 =    R20 = c00035f831b0
  R05 = ffe0   R21 = 0001
  R06 = fffe   R22 = 0002
  R07 

[Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

[Joseph Salisbury]

I built the next test kernel, up to the following commit:
ed18adc1cdd00a5c55a20fbdaed4804660772281

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1627198

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

Thanks in advance

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

Title:
  4.8.0 kernels do not complete boot process on VM

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

Bug description:
  On my native amd64 box, 4.8.0-15 works just fine, but on my VMWare
  Fusion 8.5 system, none of the 4.8.0 kernels complete the boot
  process.  I tried 4.8.0-15 from yakkety and 4.8.0-16 from yakkety-
  proposed.

  Currently  I am seeing the last message in my console at boot up as:

  [ OK ] Started Bluetooth service

  and then... it just sits there.

  Through the use of snapshots, restores, and package bisects, I've
  definitively narrowed it to linux-generic linux-image-generic and
  linux-headers-generic.

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

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

[Kernel-packages] [Bug 1628968] Re: powerpc 4.8.0-17 fails to boot on PowerMac G5

[Tim Gardner]

This is quite odd. The symbol references in all of the module objects
appear correct as they do in Module.symvers

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

Title:
  powerpc 4.8.0-17 fails to boot on PowerMac G5

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

Bug description:
  Not much else to say. The system fails to complete booting, it gets
  stuck somewhere before network comes up; with errors in syslog about
  missing symbols for some modules (see
  http://paste.ubuntu.com/23251408/). Boots fine in 4.4.0-21:

  Sep 28 12:49:55 fujin kernel: [4.698092] uninorth_agp: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.715284] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.731545] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759718] drm: Unknown symbol ence_release 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759781] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.777863] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.798476] drm: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.815248] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.826136] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.846026] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.862106] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.882364] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.898322] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.914094] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.930108] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [5.396683] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [7.609956] autofs4: Unknown symbol 
cache_dir_open (err 0)
  Sep 28 12:49:55 fujin kernel: [7.610137] autofs4: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [9.989854] parport: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.405448] shpchp: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.684111] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.826081] rack_meter: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.953962] i2c_algo_bit: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.977975] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.010110] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.022857] soundcore: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.034422] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.049942] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.070474] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.085972] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.102451] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.118814] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.813073] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.820183] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   19.022406] bluetooth: Unknown symbol mcount 
(err 0)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=8c8a4ee6-57e4-4d02-9196-6c4620ee5883
  InstallationDate: Installed on 2016-09-28 (1 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release powerpc 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enP1p5s4f1  no wireless extensions.
   
   enP1p5s4f0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 1e54:2030 TypeMatrix 2030 USB Keyboard
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 003: ID 05ac:8207 Apple, Inc. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: root=UUID=fd6c3ae7-7de7-416e-8bed-b4513658ee6d ro quiet 
splash verbose
  ProcVersionSignature: Ubuntu 4.4.0-21.37-powerpc64-smp 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or 

[Kernel-packages] [Bug 1628988] [NEW] ISST-LTE:Ubuntu1610: UbuntuKVM 16.10 guest crashed after 30 hours of stress testing

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

After running Stress tests for 30 hours, Ubuntu16.10 KVM guest crashed
and entered xmon.

Guest Build:
--
4.8.0-16-generic

Tests started on guest:
--
BASE: LTP Base tests.. 
IO: admndisk, aio, fstest tests (on btrfs file system over 6 partitions of 2 
disks).
TCP: TCP commands: telnet, ssh, rlogin, ping etc..

XMON traces:
--
4:mon> t
[c0017ffcf800] c024385c end_page_writeback+0x7c/0x120
[c0017ffcf830] d22d8298 ext4_finish_bio+0x1f0/0x2e0 [ext4]
[c0017ffcf910] d22d8928 ext4_end_bio+0x70/0x170 [ext4]
[c0017ffcf9a0] c04c96cc bio_endio+0xfc/0x120
[c0017ffcf9d0] c04d5f50 blk_update_request+0xf0/0x4d0
[c0017ffcfa60] c06df2dc scsi_end_request+0x6c/0x260
[c0017ffcfad0] c06e32a4 scsi_io_completion+0x2d4/0x740
[c0017ffcfba0] c06d6714 scsi_finish_command+0x144/0x200
[c0017ffcfc20] c06e25a8 scsi_softirq_done+0x198/0x200
[c0017ffcfca0] c04e2e98 __blk_mq_complete_request_remote+0x38/0x50
[c0017ffcfcd0] c0183e80 flush_smp_call_function_queue+0xd0/0x220
[c0017ffcfd50] c0047aac smp_ipi_demux+0xac/0x110
[c0017ffcfd90] c00738e4 icp_hv_ipi_action+0x64/0xd0
[c0017ffcfe00] c01466d0 __handle_irq_event_percpu+0x90/0x340
[c0017ffcfec0] c01469bc handle_irq_event_percpu+0x3c/0x90
[c0017ffcff00] c014ced4 handle_percpu_irq+0x84/0xd0
[c0017ffcff30] c0145664 generic_handle_irq+0x54/0x80
[c0017ffcff60] c0015b20 __do_irq+0x80/0x230
[c0017ffcff90] c002a2e0 call_do_irq+0x14/0x24
[c0013073b210] c0015d68 do_IRQ+0x98/0x140
[c0013073b260] c00026d8 hardware_interrupt_common+0x158/0x180
--- Exception: 501 (Hardware Interrupt) at c008fe4c 
plpar_hcall_norets+0x1c/0x28
[link register   ] c006c094 __spin_yield+0xa4/0xb0
[c0013073b550] c0017fe28b00 (unreliable)
[c0013073b5c0] c0949758 _raw_spin_lock_irqsave+0x128/0x130
[c0013073b600] d17222cc ibmvscsi_queuecommand+0x54/0x4b0 [ibmvscsi]
[c0013073b6b0] c06dfc80 scsi_dispatch_cmd+0x140/0x370
[c0013073b730] c06e1ad0 scsi_queue_rq+0x770/0x920
[c0013073b800] c04e62f4 __blk_mq_run_hw_queue+0x2e4/0x570
[c0013073b910] c04e5fc8 blk_mq_run_hw_queue+0xf8/0x140
[c0013073b940] c04e8f90 blk_mq_flush_plug_list+0x160/0x1b0
[c0013073b9c0] c04d7fbc blk_flush_plug_list+0xfc/0x2b0
[c0013073ba30] c04d8708 blk_finish_plug+0x58/0x80
[c0013073ba60] d22d270c ext4_writepages+0x6c4/0xe60 [ext4]
[c0013073bbf0] c025ae80 do_writepages+0x60/0xc0
[c0013073bc20] c0246c18 __filemap_fdatawrite_range+0x108/0x190
[c0013073bcc0] c0246f20 filemap_write_and_wait_range+0x70/0xf0
[c0013073bd00] d22c5944 ext4_sync_file+0x24c/0x5a0 [ext4]
[c0013073bd60] c0365a28 vfs_fsync_range+0x78/0x130
[c0013073bdb0] c0365b90 do_fsync+0x60/0xb0
[c0013073be00] c0366000 SyS_fsync+0x30/0x50
[c0013073be30] c00095e0 system_call+0x38/0x108
--- Exception: c00 (System Call) at 3fff7b26cc98
SP (3fffc42b5280) is in userspace
4:mon> e
cpu 0x4: Vector: 300 (Data Access) at [c0017ffcf520]
pc: c025b4ec: test_clear_page_writeback+0x1ec/0x300
lr: c025b4c0: test_clear_page_writeback+0x1c0/0x300
sp: c0017ffcf7a0
   msr: 80009033
   dar: 2d0
 dsisr: 4000
  current = 0xc00036f59880
  paca= 0xc7b82400   softe: 0irq_happened: 0x09
pid   = 1102, comm = create_datafile
Linux version 4.8.0-16-generic (buildd@bos01-ppc64el-007) (gcc version 6.2.0 
20160914 (Ubuntu 6.2.0-3ubuntu15) ) #17-Ubuntu SMP Thu Sep 22 22:45:44 UTC 2016 
(Ubuntu 4.8.0-16.17-generic 4.8.0-rc7)
4:mon>
4:mon>
4:mon> r
R00 = c025b4c0   R16 = 0550
R01 = c0017ffcf7a0   R17 = 7fff
R02 = c10af400   R18 = 
R03 =    R19 = c00172e35b00
R04 =    R20 = c00035f831b0
R05 = ffe0   R21 = 0001
R06 = fffe   R22 = 0002
R07 = f800   R23 = 0400
R08 = 00017f18   R24 = 
R09 =    R25 = c10f00c4
R10 = 00017f18   R26 = 
R11 = 0230   R27 = c00072873518
R12 = 0001   R28 = c37fcdf8
R13 = c7b82400   R29 = 0001
R14 =    R30 = c00072873500
R15 =    R31 = f02423c0
pc  = c025b4ec test_clear_page_writeback+0x1ec/0x300
cfar= c09497c4 _raw_spin_unlock_irqrestore+0x64/0xb0
lr  = c025b4c0 test_clear_page_writeback+0x1c0/0x300
msr = 80009033   cr  = 2808
ctr = c02437e0   xer = 2000   trap =  300
dar = 

[Kernel-packages] [Bug 1628204] dwalin (amd64) - tests ran: 2, failed: 0

[Brad Figg]

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-41.61/dwalin__4.4.0-41.61__2016-09-29_15-41-00/results-index.html

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

Title:
  linux: 4.4.0-41.61 -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 Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-41.61 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
  derivative-trackers-created: 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/1628204/+subscriptions

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

[Kernel-packages] [Bug 1627574] s2lp6g002 (s390x.zKVM) - tests ran: 64, failed: 0

[Brad Figg]

tests ran:  64, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-18.20/s2lp6g002__4.8.0-18.20__2016-09-29_15-27-00/results-index.html

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

Title:
  linux: 4.8.0-18.20 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 27. September 2016 08:45 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

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

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

[Kernel-packages] [Bug 1628204] s2lp3 (s390x.LPAR) - tests ran: 64, failed: 0

[Brad Figg]

tests ran:  64, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-41.61/s2lp3__4.4.0-41.61__2016-09-29_15-24-00/results-index.html

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

Title:
  linux: 4.4.0-41.61 -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 Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-41.61 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
  derivative-trackers-created: 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/1628204/+subscriptions

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

[Kernel-packages] [Bug 1628976] sosreport after 4.8.0-17 update

[bugproxy]

Default Comment by Bridge

** Attachment added: "sosreport after 4.8.0-17 update"
   
https://bugs.launchpad.net/bugs/1628976/+attachment/4751102/+files/sosreport-alp10.146511-20160929101834.tar.xz

** Changed in: ubuntu
 Assignee: (unassigned) => Taco Screen team (taco-screen-team)

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

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

Title:
  Ubuntu 16.10: Oops panic in move_page_tables/page_remove_rmap after
  running memory_stress_ng.

Status in linux package in Ubuntu:
  New

Bug description:
  FYI Canonical:

  We have been seeing various page handling issues during memory stress
  in the 4.8 kernels.  The following is the most recent issue resulting
  in system panics on this host after the 4.8.0-17 update:

  == Comment: #17 - PAVITHRA R. PRAKASH - 2016-09-28 06:26:21 ==
  Hi,

  Tried running on 4.8.0-17-generic kernel. Getting below call trace and
  system crashes. Attaching logs.

  [ 2959.364333] Unable to handle kernel paging request for data at address 
0xf2fe4020
  [ 2959.364345] Faulting instruction address: 0xc02bb2a0
  [ 2959.364356] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 2959.364364] SMP NR_CPUS=2048 NUMA pSeries
  [ 2959.364377] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag 
udp_diag inet_diag unix_diag af_packet_diag netlink_diag bnx2x mdio libcrc32c 
pseries_rng vmx_crypto binfmt_misc ip_tables x_tables autofs4 ibmvscsi 
crc32c_vpmsum
  [ 2959.364441] CPU: 13 PID: 108 Comm: oom_reaper Not tainted 4.8.0-17-generic 
#19-Ubuntu
  [ 2959.364452] task: c004fbdf9c00 task.stack: c004fbe0
  [ 2959.364461] NIP: c02bb2a0 LR: c0300618 CTR: 
c009ca40
  [ 2959.364471] REGS: c004fbe036e0 TRAP: 0300   Not tainted  
(4.8.0-17-generic)
  [ 2959.364481] MSR: 80010280b033   
CR: 24028844  XER: 200c
  [ 2959.364526] CFAR: c0300614 DAR: f2fe4020 DSISR: 4000 
SOFTE: 1 
 GPR00: c0300618 c004fbe03960 c14e5e00 
f2fe4000 
 GPR04: 0001 0800  
c1665e00 
 GPR08: f900a196 0001 02fe4000 
 
 GPR12: 8800 c1b37500 0008 
c1ffe7ff 
 GPR16: c004f62a55f0 3fff9a00 3fff9900 
 
 GPR20: c004fbe03b80 c004e0713800 8e017c3302c0 
0001 
 GPR24: c000fb3614c8 c000fce9d990 c000fce9d6e4 
96a100f90b40 
 GPR28: f2fe4000 c000fb3614c8 0001 
f2fe4000 
  [ 2959.364673] NIP [c02bb2a0] page_remove_rmap+0x30/0x4b0
  [ 2959.364685] LR [c0300618] zap_huge_pmd+0xf8/0x480
  [ 2959.364692] Call Trace:
  [ 2959.364699] [c004fbe03960] [c004fbe039a0] 0xc004fbe039a0 
(unreliable)
  [ 2959.364714] [c004fbe039a0] [c0300618] zap_huge_pmd+0xf8/0x480
  [ 2959.364726] [c004fbe039f0] [c02a68d8] 
unmap_page_range+0xd08/0xee0
  [ 2959.364740] [c004fbe03b20] [c025c474] 
__oom_reap_task+0x204/0x2c0
  [ 2959.364752] [c004fbe03c80] [c025cda8] oom_reaper+0x1e8/0x300
  [ 2959.364765] [c004fbe03d80] [c00fd120] kthread+0x110/0x130
  [ 2959.364778] [c004fbe03e30] [c00098f0] 
ret_from_kernel_thread+0x5c/0x6c
  [ 2959.364788] Instruction dump:
  [ 2959.364796] 3c4c0123 3842ab90 7c0802a6 fba1ffe8 fbc1fff0 fbe1fff8 f8010010 
f821ffc1 
  [ 2959.364821] 7c7f1b78 7c9e2378 6000 6000  71480001 
392a 40820008 
  [ 2959.364871] ---[ end trace 178b14c6911b70dc ]---
  [ 2959.372762] 
  [ 2959.372798] Sending IPI to other CPUs
  [ 2959.373834] IPI complete

  Thanks,
  Pavithra

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

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

[Kernel-packages] [Bug 1628968] Re: powerpc 4.8.0-17 fails to boot on PowerMac G5

[Tim Gardner]

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

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

** Changed in: linux (Ubuntu Yakkety)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  powerpc 4.8.0-17 fails to boot on PowerMac G5

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

Bug description:
  Not much else to say. The system fails to complete booting, it gets
  stuck somewhere before network comes up; with errors in syslog about
  missing symbols for some modules (see
  http://paste.ubuntu.com/23251408/). Boots fine in 4.4.0-21:

  Sep 28 12:49:55 fujin kernel: [4.698092] uninorth_agp: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.715284] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.731545] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759718] drm: Unknown symbol ence_release 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759781] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.777863] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.798476] drm: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.815248] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.826136] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.846026] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.862106] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.882364] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.898322] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.914094] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.930108] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [5.396683] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [7.609956] autofs4: Unknown symbol 
cache_dir_open (err 0)
  Sep 28 12:49:55 fujin kernel: [7.610137] autofs4: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [9.989854] parport: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.405448] shpchp: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.684111] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.826081] rack_meter: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.953962] i2c_algo_bit: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.977975] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.010110] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.022857] soundcore: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.034422] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.049942] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.070474] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.085972] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.102451] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.118814] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.813073] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.820183] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   19.022406] bluetooth: Unknown symbol mcount 
(err 0)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=8c8a4ee6-57e4-4d02-9196-6c4620ee5883
  InstallationDate: Installed on 2016-09-28 (1 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release powerpc 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enP1p5s4f1  no wireless extensions.
   
   enP1p5s4f0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 1e54:2030 TypeMatrix 2030 USB Keyboard
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 003: ID 05ac:8207 Apple, Inc. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: root=UUID=fd6c3ae7-7de7-416e-8bed-b4513658ee6d ro quiet 
splash verbose
  ProcVersionSignature: Ubuntu 

[Kernel-packages] [Bug 1627574] s2lp6g002 (s390x.zKVM) - tests ran: 136, failed: 27

[Brad Figg]

tests ran: 136, failed: 27;
  
http://kernel.ubuntu.com/testing/4.8.0-18.20/s2lp6g002__4.8.0-18.20__2016-09-29_14-54-00/results-index.html

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

Title:
  linux: 4.8.0-18.20 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 27. September 2016 08:45 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

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

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

[Kernel-packages] [Bug 1627574] s2lp6g002 (s390x.zKVM) - tests ran: 2, failed: 0

[Brad Figg]

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-18.20/s2lp6g002__4.8.0-18.20__2016-09-29_15-25-00/results-index.html

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

Title:
  linux: 4.8.0-18.20 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 27. September 2016 08:45 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

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

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

[Kernel-packages] [Bug 1628204] s2lp3 (s390x.LPAR) - tests ran: 2, failed: 0

[Brad Figg]

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-41.61/s2lp3__4.4.0-41.61__2016-09-29_15-21-00/results-index.html

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

Title:
  linux: 4.4.0-41.61 -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 Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-41.61 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
  derivative-trackers-created: 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/1628204/+subscriptions

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

[Kernel-packages] [Bug 1628204] s2lp3 (s390x.LPAR) - tests ran: 136, failed: 27

[Brad Figg]

tests ran: 136, failed: 27;
  
http://kernel.ubuntu.com/testing/4.4.0-41.61/s2lp3__4.4.0-41.61__2016-09-29_14-51-00/results-index.html

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

Title:
  linux: 4.4.0-41.61 -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 Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-41.61 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
  derivative-trackers-created: 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/1628204/+subscriptions

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

[Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

[Joseph Salisbury]

I built the next test kernel, up to the following commit:
1bd4403d86a1c06cb6cc9ac87664a0c9d3413d51

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1627198

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

Thanks in advance

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

Title:
  4.8.0 kernels do not complete boot process on VM

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

Bug description:
  On my native amd64 box, 4.8.0-15 works just fine, but on my VMWare
  Fusion 8.5 system, none of the 4.8.0 kernels complete the boot
  process.  I tried 4.8.0-15 from yakkety and 4.8.0-16 from yakkety-
  proposed.

  Currently  I am seeing the last message in my console at boot up as:

  [ OK ] Started Bluetooth service

  and then... it just sits there.

  Through the use of snapshots, restores, and package bisects, I've
  definitively narrowed it to linux-generic linux-image-generic and
  linux-headers-generic.

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

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

[Kernel-packages] [Bug 1628968] ProcEnviron.txt

[Mathieu Trudel-Lapierre]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1628968/+attachment/4751087/+files/ProcEnviron.txt

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

Title:
  powerpc 4.8.0-17 fails to boot on PowerMac G5

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

Bug description:
  Not much else to say. The system fails to complete booting, it gets
  stuck somewhere before network comes up; with errors in syslog about
  missing symbols for some modules (see
  http://paste.ubuntu.com/23251408/). Boots fine in 4.4.0-21:

  Sep 28 12:49:55 fujin kernel: [4.698092] uninorth_agp: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.715284] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.731545] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759718] drm: Unknown symbol ence_release 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759781] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.777863] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.798476] drm: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.815248] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.826136] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.846026] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.862106] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.882364] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.898322] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.914094] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.930108] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [5.396683] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [7.609956] autofs4: Unknown symbol 
cache_dir_open (err 0)
  Sep 28 12:49:55 fujin kernel: [7.610137] autofs4: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [9.989854] parport: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.405448] shpchp: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.684111] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.826081] rack_meter: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.953962] i2c_algo_bit: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.977975] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.010110] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.022857] soundcore: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.034422] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.049942] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.070474] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.085972] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.102451] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.118814] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.813073] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.820183] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   19.022406] bluetooth: Unknown symbol mcount 
(err 0)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=8c8a4ee6-57e4-4d02-9196-6c4620ee5883
  InstallationDate: Installed on 2016-09-28 (1 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release powerpc 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enP1p5s4f1  no wireless extensions.
   
   enP1p5s4f0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 1e54:2030 TypeMatrix 2030 USB Keyboard
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 003: ID 05ac:8207 Apple, Inc. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: root=UUID=fd6c3ae7-7de7-416e-8bed-b4513658ee6d ro quiet 
splash verbose
  ProcVersionSignature: Ubuntu 4.4.0-21.37-powerpc64-smp 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 

[Kernel-packages] [Bug 1628976] [NEW] Ubuntu 16.10: Oops panic in move_page_tables/page_remove_rmap after running memory_stress_ng.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

FYI Canonical:

We have been seeing various page handling issues during memory stress in
the 4.8 kernels.  The following is the most recent issue resulting in
system panics on this host after the 4.8.0-17 update:

== Comment: #17 - PAVITHRA R. PRAKASH - 2016-09-28 06:26:21 ==
Hi,

Tried running on 4.8.0-17-generic kernel. Getting below call trace and
system crashes. Attaching logs.

[ 2959.364333] Unable to handle kernel paging request for data at address 
0xf2fe4020
[ 2959.364345] Faulting instruction address: 0xc02bb2a0
[ 2959.364356] Oops: Kernel access of bad area, sig: 11 [#1]
[ 2959.364364] SMP NR_CPUS=2048 NUMA pSeries
[ 2959.364377] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag 
udp_diag inet_diag unix_diag af_packet_diag netlink_diag bnx2x mdio libcrc32c 
pseries_rng vmx_crypto binfmt_misc ip_tables x_tables autofs4 ibmvscsi 
crc32c_vpmsum
[ 2959.364441] CPU: 13 PID: 108 Comm: oom_reaper Not tainted 4.8.0-17-generic 
#19-Ubuntu
[ 2959.364452] task: c004fbdf9c00 task.stack: c004fbe0
[ 2959.364461] NIP: c02bb2a0 LR: c0300618 CTR: c009ca40
[ 2959.364471] REGS: c004fbe036e0 TRAP: 0300   Not tainted  
(4.8.0-17-generic)
[ 2959.364481] MSR: 80010280b033   
CR: 24028844  XER: 200c
[ 2959.364526] CFAR: c0300614 DAR: f2fe4020 DSISR: 4000 
SOFTE: 1 
   GPR00: c0300618 c004fbe03960 c14e5e00 
f2fe4000 
   GPR04: 0001 0800  
c1665e00 
   GPR08: f900a196 0001 02fe4000 
 
   GPR12: 8800 c1b37500 0008 
c1ffe7ff 
   GPR16: c004f62a55f0 3fff9a00 3fff9900 
 
   GPR20: c004fbe03b80 c004e0713800 8e017c3302c0 
0001 
   GPR24: c000fb3614c8 c000fce9d990 c000fce9d6e4 
96a100f90b40 
   GPR28: f2fe4000 c000fb3614c8 0001 
f2fe4000 
[ 2959.364673] NIP [c02bb2a0] page_remove_rmap+0x30/0x4b0
[ 2959.364685] LR [c0300618] zap_huge_pmd+0xf8/0x480
[ 2959.364692] Call Trace:
[ 2959.364699] [c004fbe03960] [c004fbe039a0] 0xc004fbe039a0 
(unreliable)
[ 2959.364714] [c004fbe039a0] [c0300618] zap_huge_pmd+0xf8/0x480
[ 2959.364726] [c004fbe039f0] [c02a68d8] 
unmap_page_range+0xd08/0xee0
[ 2959.364740] [c004fbe03b20] [c025c474] __oom_reap_task+0x204/0x2c0
[ 2959.364752] [c004fbe03c80] [c025cda8] oom_reaper+0x1e8/0x300
[ 2959.364765] [c004fbe03d80] [c00fd120] kthread+0x110/0x130
[ 2959.364778] [c004fbe03e30] [c00098f0] 
ret_from_kernel_thread+0x5c/0x6c
[ 2959.364788] Instruction dump:
[ 2959.364796] 3c4c0123 3842ab90 7c0802a6 fba1ffe8 fbc1fff0 fbe1fff8 f8010010 
f821ffc1 
[ 2959.364821] 7c7f1b78 7c9e2378 6000 6000  71480001 392a 
40820008 
[ 2959.364871] ---[ end trace 178b14c6911b70dc ]---
[ 2959.372762] 
[ 2959.372798] Sending IPI to other CPUs
[ 2959.373834] IPI complete

Thanks,
Pavithra

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
 Status: New


** Tags: architecture-ppc64le bugnameltc-146511 severity-high 
targetmilestone-inin---
-- 
Ubuntu 16.10: Oops panic in move_page_tables/page_remove_rmap after running 
memory_stress_ng.
https://bugs.launchpad.net/bugs/1628976
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

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

[Mathieu Trudel-Lapierre]

apport information

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

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

Title:
  powerpc 4.8.0-17 fails to boot on PowerMac G5

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

Bug description:
  Not much else to say. The system fails to complete booting, it gets
  stuck somewhere before network comes up; with errors in syslog about
  missing symbols for some modules (see
  http://paste.ubuntu.com/23251408/). Boots fine in 4.4.0-21:

  Sep 28 12:49:55 fujin kernel: [4.698092] uninorth_agp: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.715284] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.731545] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759718] drm: Unknown symbol ence_release 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759781] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.777863] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.798476] drm: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.815248] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.826136] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.846026] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.862106] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.882364] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.898322] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.914094] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.930108] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [5.396683] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [7.609956] autofs4: Unknown symbol 
cache_dir_open (err 0)
  Sep 28 12:49:55 fujin kernel: [7.610137] autofs4: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [9.989854] parport: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.405448] shpchp: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.684111] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.826081] rack_meter: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.953962] i2c_algo_bit: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.977975] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.010110] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.022857] soundcore: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.034422] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.049942] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.070474] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.085972] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.102451] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.118814] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.813073] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.820183] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   19.022406] bluetooth: Unknown symbol mcount 
(err 0)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=8c8a4ee6-57e4-4d02-9196-6c4620ee5883
  InstallationDate: Installed on 2016-09-28 (1 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release powerpc 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enP1p5s4f1  no wireless extensions.
   
   enP1p5s4f0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 1e54:2030 TypeMatrix 2030 USB Keyboard
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 003: ID 05ac:8207 Apple, Inc. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: root=UUID=fd6c3ae7-7de7-416e-8bed-b4513658ee6d ro quiet 
splash verbose
  ProcVersionSignature: Ubuntu 4.4.0-21.37-powerpc64-smp 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 

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

[Mathieu Trudel-Lapierre]

apport information

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

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

Title:
  powerpc 4.8.0-17 fails to boot on PowerMac G5

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

Bug description:
  Not much else to say. The system fails to complete booting, it gets
  stuck somewhere before network comes up; with errors in syslog about
  missing symbols for some modules (see
  http://paste.ubuntu.com/23251408/). Boots fine in 4.4.0-21:

  Sep 28 12:49:55 fujin kernel: [4.698092] uninorth_agp: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.715284] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.731545] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759718] drm: Unknown symbol ence_release 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759781] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.777863] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.798476] drm: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.815248] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.826136] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.846026] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.862106] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.882364] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.898322] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.914094] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.930108] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [5.396683] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [7.609956] autofs4: Unknown symbol 
cache_dir_open (err 0)
  Sep 28 12:49:55 fujin kernel: [7.610137] autofs4: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [9.989854] parport: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.405448] shpchp: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.684111] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.826081] rack_meter: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.953962] i2c_algo_bit: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.977975] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.010110] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.022857] soundcore: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.034422] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.049942] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.070474] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.085972] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.102451] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.118814] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.813073] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.820183] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   19.022406] bluetooth: Unknown symbol mcount 
(err 0)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=8c8a4ee6-57e4-4d02-9196-6c4620ee5883
  InstallationDate: Installed on 2016-09-28 (1 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release powerpc 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enP1p5s4f1  no wireless extensions.
   
   enP1p5s4f0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 1e54:2030 TypeMatrix 2030 USB Keyboard
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 003: ID 05ac:8207 Apple, Inc. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: root=UUID=fd6c3ae7-7de7-416e-8bed-b4513658ee6d ro quiet 
splash verbose
  ProcVersionSignature: Ubuntu 4.4.0-21.37-powerpc64-smp 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 

[Kernel-packages] [Bug 1628968] AlsaInfo.txt

[Mathieu Trudel-Lapierre]

apport information

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

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

Title:
  powerpc 4.8.0-17 fails to boot on PowerMac G5

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

Bug description:
  Not much else to say. The system fails to complete booting, it gets
  stuck somewhere before network comes up; with errors in syslog about
  missing symbols for some modules (see
  http://paste.ubuntu.com/23251408/). Boots fine in 4.4.0-21:

  Sep 28 12:49:55 fujin kernel: [4.698092] uninorth_agp: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.715284] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.731545] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759718] drm: Unknown symbol ence_release 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759781] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.777863] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.798476] drm: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.815248] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.826136] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.846026] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.862106] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.882364] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.898322] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.914094] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.930108] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [5.396683] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [7.609956] autofs4: Unknown symbol 
cache_dir_open (err 0)
  Sep 28 12:49:55 fujin kernel: [7.610137] autofs4: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [9.989854] parport: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.405448] shpchp: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.684111] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.826081] rack_meter: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.953962] i2c_algo_bit: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.977975] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.010110] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.022857] soundcore: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.034422] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.049942] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.070474] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.085972] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.102451] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.118814] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.813073] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.820183] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   19.022406] bluetooth: Unknown symbol mcount 
(err 0)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=8c8a4ee6-57e4-4d02-9196-6c4620ee5883
  InstallationDate: Installed on 2016-09-28 (1 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release powerpc 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enP1p5s4f1  no wireless extensions.
   
   enP1p5s4f0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 1e54:2030 TypeMatrix 2030 USB Keyboard
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 003: ID 05ac:8207 Apple, Inc. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: root=UUID=fd6c3ae7-7de7-416e-8bed-b4513658ee6d ro quiet 
splash verbose
  ProcVersionSignature: Ubuntu 4.4.0-21.37-powerpc64-smp 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 

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

[Mathieu Trudel-Lapierre]

apport information

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

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

Title:
  powerpc 4.8.0-17 fails to boot on PowerMac G5

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

Bug description:
  Not much else to say. The system fails to complete booting, it gets
  stuck somewhere before network comes up; with errors in syslog about
  missing symbols for some modules (see
  http://paste.ubuntu.com/23251408/). Boots fine in 4.4.0-21:

  Sep 28 12:49:55 fujin kernel: [4.698092] uninorth_agp: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.715284] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.731545] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759718] drm: Unknown symbol ence_release 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759781] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.777863] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.798476] drm: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.815248] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.826136] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.846026] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.862106] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.882364] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.898322] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.914094] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.930108] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [5.396683] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [7.609956] autofs4: Unknown symbol 
cache_dir_open (err 0)
  Sep 28 12:49:55 fujin kernel: [7.610137] autofs4: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [9.989854] parport: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.405448] shpchp: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.684111] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.826081] rack_meter: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.953962] i2c_algo_bit: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.977975] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.010110] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.022857] soundcore: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.034422] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.049942] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.070474] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.085972] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.102451] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.118814] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.813073] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.820183] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   19.022406] bluetooth: Unknown symbol mcount 
(err 0)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=8c8a4ee6-57e4-4d02-9196-6c4620ee5883
  InstallationDate: Installed on 2016-09-28 (1 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release powerpc 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enP1p5s4f1  no wireless extensions.
   
   enP1p5s4f0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 1e54:2030 TypeMatrix 2030 USB Keyboard
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 003: ID 05ac:8207 Apple, Inc. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: root=UUID=fd6c3ae7-7de7-416e-8bed-b4513658ee6d ro quiet 
splash verbose
  ProcVersionSignature: Ubuntu 4.4.0-21.37-powerpc64-smp 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio 

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

[Mathieu Trudel-Lapierre]

apport information

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

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

Title:
  powerpc 4.8.0-17 fails to boot on PowerMac G5

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

Bug description:
  Not much else to say. The system fails to complete booting, it gets
  stuck somewhere before network comes up; with errors in syslog about
  missing symbols for some modules (see
  http://paste.ubuntu.com/23251408/). Boots fine in 4.4.0-21:

  Sep 28 12:49:55 fujin kernel: [4.698092] uninorth_agp: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.715284] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.731545] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759718] drm: Unknown symbol ence_release 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759781] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.777863] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.798476] drm: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.815248] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.826136] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.846026] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.862106] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.882364] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.898322] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.914094] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.930108] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [5.396683] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [7.609956] autofs4: Unknown symbol 
cache_dir_open (err 0)
  Sep 28 12:49:55 fujin kernel: [7.610137] autofs4: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [9.989854] parport: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.405448] shpchp: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.684111] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.826081] rack_meter: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.953962] i2c_algo_bit: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.977975] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.010110] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.022857] soundcore: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.034422] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.049942] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.070474] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.085972] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.102451] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.118814] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.813073] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.820183] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   19.022406] bluetooth: Unknown symbol mcount 
(err 0)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=8c8a4ee6-57e4-4d02-9196-6c4620ee5883
  InstallationDate: Installed on 2016-09-28 (1 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release powerpc 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enP1p5s4f1  no wireless extensions.
   
   enP1p5s4f0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 1e54:2030 TypeMatrix 2030 USB Keyboard
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 003: ID 05ac:8207 Apple, Inc. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: root=UUID=fd6c3ae7-7de7-416e-8bed-b4513658ee6d ro quiet 
splash verbose
  ProcVersionSignature: Ubuntu 4.4.0-21.37-powerpc64-smp 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 

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

[Mathieu Trudel-Lapierre]

apport information

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

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

Title:
  powerpc 4.8.0-17 fails to boot on PowerMac G5

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

Bug description:
  Not much else to say. The system fails to complete booting, it gets
  stuck somewhere before network comes up; with errors in syslog about
  missing symbols for some modules (see
  http://paste.ubuntu.com/23251408/). Boots fine in 4.4.0-21:

  Sep 28 12:49:55 fujin kernel: [4.698092] uninorth_agp: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.715284] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.731545] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759718] drm: Unknown symbol ence_release 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759781] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.777863] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.798476] drm: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.815248] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.826136] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.846026] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.862106] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.882364] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.898322] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.914094] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.930108] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [5.396683] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [7.609956] autofs4: Unknown symbol 
cache_dir_open (err 0)
  Sep 28 12:49:55 fujin kernel: [7.610137] autofs4: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [9.989854] parport: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.405448] shpchp: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.684111] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.826081] rack_meter: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.953962] i2c_algo_bit: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.977975] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.010110] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.022857] soundcore: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.034422] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.049942] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.070474] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.085972] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.102451] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.118814] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.813073] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.820183] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   19.022406] bluetooth: Unknown symbol mcount 
(err 0)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=8c8a4ee6-57e4-4d02-9196-6c4620ee5883
  InstallationDate: Installed on 2016-09-28 (1 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release powerpc 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enP1p5s4f1  no wireless extensions.
   
   enP1p5s4f0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 1e54:2030 TypeMatrix 2030 USB Keyboard
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 003: ID 05ac:8207 Apple, Inc. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: root=UUID=fd6c3ae7-7de7-416e-8bed-b4513658ee6d ro quiet 
splash verbose
  ProcVersionSignature: Ubuntu 4.4.0-21.37-powerpc64-smp 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: 

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

[Mathieu Trudel-Lapierre]

apport information

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

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

Title:
  powerpc 4.8.0-17 fails to boot on PowerMac G5

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

Bug description:
  Not much else to say. The system fails to complete booting, it gets
  stuck somewhere before network comes up; with errors in syslog about
  missing symbols for some modules (see
  http://paste.ubuntu.com/23251408/). Boots fine in 4.4.0-21:

  Sep 28 12:49:55 fujin kernel: [4.698092] uninorth_agp: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.715284] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.731545] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759718] drm: Unknown symbol ence_release 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759781] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.777863] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.798476] drm: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.815248] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.826136] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.846026] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.862106] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.882364] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.898322] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.914094] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.930108] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [5.396683] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [7.609956] autofs4: Unknown symbol 
cache_dir_open (err 0)
  Sep 28 12:49:55 fujin kernel: [7.610137] autofs4: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [9.989854] parport: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.405448] shpchp: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.684111] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.826081] rack_meter: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.953962] i2c_algo_bit: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.977975] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.010110] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.022857] soundcore: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.034422] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.049942] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.070474] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.085972] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.102451] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.118814] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.813073] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.820183] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   19.022406] bluetooth: Unknown symbol mcount 
(err 0)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=8c8a4ee6-57e4-4d02-9196-6c4620ee5883
  InstallationDate: Installed on 2016-09-28 (1 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release powerpc 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enP1p5s4f1  no wireless extensions.
   
   enP1p5s4f0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 1e54:2030 TypeMatrix 2030 USB Keyboard
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 003: ID 05ac:8207 Apple, Inc. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: root=UUID=fd6c3ae7-7de7-416e-8bed-b4513658ee6d ro quiet 
splash verbose
  ProcVersionSignature: Ubuntu 4.4.0-21.37-powerpc64-smp 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio 

[Kernel-packages] [Bug 1628968] JournalErrors.txt

[Mathieu Trudel-Lapierre]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1628968/+attachment/4751084/+files/JournalErrors.txt

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

Title:
  powerpc 4.8.0-17 fails to boot on PowerMac G5

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

Bug description:
  Not much else to say. The system fails to complete booting, it gets
  stuck somewhere before network comes up; with errors in syslog about
  missing symbols for some modules (see
  http://paste.ubuntu.com/23251408/). Boots fine in 4.4.0-21:

  Sep 28 12:49:55 fujin kernel: [4.698092] uninorth_agp: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.715284] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.731545] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759718] drm: Unknown symbol ence_release 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759781] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.777863] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.798476] drm: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.815248] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.826136] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.846026] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.862106] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.882364] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.898322] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.914094] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.930108] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [5.396683] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [7.609956] autofs4: Unknown symbol 
cache_dir_open (err 0)
  Sep 28 12:49:55 fujin kernel: [7.610137] autofs4: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [9.989854] parport: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.405448] shpchp: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.684111] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.826081] rack_meter: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.953962] i2c_algo_bit: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.977975] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.010110] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.022857] soundcore: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.034422] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.049942] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.070474] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.085972] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.102451] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.118814] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.813073] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.820183] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   19.022406] bluetooth: Unknown symbol mcount 
(err 0)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=8c8a4ee6-57e4-4d02-9196-6c4620ee5883
  InstallationDate: Installed on 2016-09-28 (1 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release powerpc 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enP1p5s4f1  no wireless extensions.
   
   enP1p5s4f0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 1e54:2030 TypeMatrix 2030 USB Keyboard
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 003: ID 05ac:8207 Apple, Inc. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: root=UUID=fd6c3ae7-7de7-416e-8bed-b4513658ee6d ro quiet 
splash verbose
  ProcVersionSignature: Ubuntu 4.4.0-21.37-powerpc64-smp 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: 

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

[Mathieu Trudel-Lapierre]

apport information

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

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

Title:
  powerpc 4.8.0-17 fails to boot on PowerMac G5

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

Bug description:
  Not much else to say. The system fails to complete booting, it gets
  stuck somewhere before network comes up; with errors in syslog about
  missing symbols for some modules (see
  http://paste.ubuntu.com/23251408/). Boots fine in 4.4.0-21:

  Sep 28 12:49:55 fujin kernel: [4.698092] uninorth_agp: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.715284] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.731545] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759718] drm: Unknown symbol ence_release 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759781] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.777863] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.798476] drm: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.815248] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.826136] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.846026] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.862106] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.882364] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.898322] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.914094] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.930108] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [5.396683] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [7.609956] autofs4: Unknown symbol 
cache_dir_open (err 0)
  Sep 28 12:49:55 fujin kernel: [7.610137] autofs4: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [9.989854] parport: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.405448] shpchp: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.684111] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.826081] rack_meter: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.953962] i2c_algo_bit: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.977975] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.010110] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.022857] soundcore: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.034422] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.049942] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.070474] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.085972] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.102451] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.118814] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.813073] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.820183] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   19.022406] bluetooth: Unknown symbol mcount 
(err 0)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=8c8a4ee6-57e4-4d02-9196-6c4620ee5883
  InstallationDate: Installed on 2016-09-28 (1 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release powerpc 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enP1p5s4f1  no wireless extensions.
   
   enP1p5s4f0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 1e54:2030 TypeMatrix 2030 USB Keyboard
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 003: ID 05ac:8207 Apple, Inc. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: root=UUID=fd6c3ae7-7de7-416e-8bed-b4513658ee6d ro quiet 
splash verbose
  ProcVersionSignature: Ubuntu 4.4.0-21.37-powerpc64-smp 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 

[Kernel-packages] [Bug 1628968] [NEW] powerpc 4.8.0-17 fails to boot on PowerMac G5

[Mathieu Trudel-Lapierre]

Public bug reported:

Not much else to say. The system fails to complete booting, it gets
stuck somewhere before network comes up; with errors in syslog about
missing symbols for some modules (see
http://paste.ubuntu.com/23251408/). Boots fine in 4.4.0-21:

Sep 28 12:49:55 fujin kernel: [4.698092] uninorth_agp: Unknown symbol 
mcount (err 0)
Sep 28 12:49:55 fujin kernel: [4.715284] pps_core: Unknown symbol mcount 
(err 0)
Sep 28 12:49:55 fujin kernel: [4.731545] pps_core: Unknown symbol mcount 
(err 0)
Sep 28 12:49:55 fujin kernel: [4.759718] drm: Unknown symbol ence_release 
(err 0)
Sep 28 12:49:55 fujin kernel: [4.759781] hid: Unknown symbol mcount (err 0)
Sep 28 12:49:55 fujin kernel: [4.777863] ata_generic: Unknown symbol mcount 
(err 0)
Sep 28 12:49:55 fujin kernel: [4.798476] drm: Unknown symbol mcount (err 0)
Sep 28 12:49:55 fujin kernel: [4.815248] windfarm_core: Unknown symbol 
mcount (err 0)
Sep 28 12:49:55 fujin kernel: [4.826136] windfarm_core: Unknown symbol 
mcount (err 0)
Sep 28 12:49:55 fujin kernel: [4.846026] windfarm_core: Unknown symbol 
mcount (err 0)
Sep 28 12:49:55 fujin kernel: [4.862106] windfarm_core: Unknown symbol 
mcount (err 0)
Sep 28 12:49:55 fujin kernel: [4.882364] firewire_core: Unknown symbol 
mcount (err 0)
Sep 28 12:49:55 fujin kernel: [4.898322] hid: Unknown symbol mcount (err 0)
Sep 28 12:49:55 fujin kernel: [4.914094] hid: Unknown symbol mcount (err 0)
Sep 28 12:49:55 fujin kernel: [4.930108] hid: Unknown symbol mcount (err 0)
Sep 28 12:49:55 fujin kernel: [5.396683] windfarm_core: Unknown symbol 
mcount (err 0)
Sep 28 12:49:55 fujin kernel: [7.609956] autofs4: Unknown symbol 
cache_dir_open (err 0)
Sep 28 12:49:55 fujin kernel: [7.610137] autofs4: Unknown symbol mcount 
(err 0)
Sep 28 12:49:55 fujin kernel: [9.989854] parport: Unknown symbol mcount 
(err 0)
Sep 28 12:49:55 fujin kernel: [   16.405448] shpchp: Unknown symbol mcount (err 
0)
Sep 28 12:49:55 fujin kernel: [   16.684111] ata_generic: Unknown symbol mcount 
(err 0)
Sep 28 12:49:55 fujin kernel: [   16.826081] rack_meter: Unknown symbol mcount 
(err 0)
Sep 28 12:49:55 fujin kernel: [   16.953962] i2c_algo_bit: Unknown symbol 
mcount (err 0)
Sep 28 12:49:55 fujin kernel: [   16.977975] pps_core: Unknown symbol mcount 
(err 0)
Sep 28 12:49:55 fujin kernel: [   17.010110] uio: Unknown symbol mcount (err 0)
Sep 28 12:49:55 fujin kernel: [   17.022857] soundcore: Unknown symbol mcount 
(err 0)
Sep 28 12:49:55 fujin kernel: [   17.034422] firewire_core: Unknown symbol 
mcount (err 0)
Sep 28 12:49:55 fujin kernel: [   17.049942] windfarm_core: Unknown symbol 
mcount (err 0)
Sep 28 12:49:55 fujin kernel: [   17.070474] uio: Unknown symbol mcount (err 0)
Sep 28 12:49:55 fujin kernel: [   17.085972] windfarm_core: Unknown symbol 
mcount (err 0)
Sep 28 12:49:55 fujin kernel: [   17.102451] windfarm_core: Unknown symbol 
mcount (err 0)
Sep 28 12:49:55 fujin kernel: [   17.118814] uio: Unknown symbol mcount (err 0)
Sep 28 12:49:55 fujin kernel: [   17.813073] hid: Unknown symbol mcount (err 0)
Sep 28 12:49:55 fujin kernel: [   17.820183] hid: Unknown symbol mcount (err 0)
Sep 28 12:49:55 fujin kernel: [   19.022406] bluetooth: Unknown symbol mcount 
(err 0)
--- 
ApportVersion: 2.20.3-0ubuntu7
Architecture: powerpc
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.10
HibernationDevice: RESUME=UUID=8c8a4ee6-57e4-4d02-9196-6c4620ee5883
InstallationDate: Installed on 2016-09-28 (1 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release powerpc 
(20160420.1)
IwConfig:
 lono wireless extensions.
 
 enP1p5s4f1  no wireless extensions.
 
 enP1p5s4f0  no wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 002: ID 1e54:2030 TypeMatrix 2030 USB Keyboard
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 003: ID 05ac:8207 Apple, Inc. 
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Package: linux (not installed)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: root=UUID=fd6c3ae7-7de7-416e-8bed-b4513658ee6d ro quiet 
splash verbose
ProcVersionSignature: Ubuntu 4.4.0-21.37-powerpc64-smp 4.4.6
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-21-powerpc64-smp N/A
 linux-backports-modules-4.4.0-21-powerpc64-smp  N/A
 linux-firmware  1.161
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags:  yakkety
Uname: Linux 4.4.0-21-powerpc64-smp ppc64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Tim Gardner 

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

[Mathieu Trudel-Lapierre]

apport information

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

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

Title:
  powerpc 4.8.0-17 fails to boot on PowerMac G5

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

Bug description:
  Not much else to say. The system fails to complete booting, it gets
  stuck somewhere before network comes up; with errors in syslog about
  missing symbols for some modules (see
  http://paste.ubuntu.com/23251408/). Boots fine in 4.4.0-21:

  Sep 28 12:49:55 fujin kernel: [4.698092] uninorth_agp: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.715284] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.731545] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759718] drm: Unknown symbol ence_release 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759781] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.777863] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.798476] drm: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.815248] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.826136] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.846026] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.862106] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.882364] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.898322] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.914094] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.930108] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [5.396683] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [7.609956] autofs4: Unknown symbol 
cache_dir_open (err 0)
  Sep 28 12:49:55 fujin kernel: [7.610137] autofs4: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [9.989854] parport: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.405448] shpchp: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.684111] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.826081] rack_meter: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.953962] i2c_algo_bit: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.977975] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.010110] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.022857] soundcore: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.034422] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.049942] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.070474] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.085972] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.102451] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.118814] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.813073] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.820183] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   19.022406] bluetooth: Unknown symbol mcount 
(err 0)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=8c8a4ee6-57e4-4d02-9196-6c4620ee5883
  InstallationDate: Installed on 2016-09-28 (1 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release powerpc 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enP1p5s4f1  no wireless extensions.
   
   enP1p5s4f0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 1e54:2030 TypeMatrix 2030 USB Keyboard
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 003: ID 05ac:8207 Apple, Inc. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: root=UUID=fd6c3ae7-7de7-416e-8bed-b4513658ee6d ro quiet 
splash verbose
  ProcVersionSignature: Ubuntu 4.4.0-21.37-powerpc64-smp 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio 

[Kernel-packages] [Bug 1602577] Re: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

[Martin Pitt]

My two instances have been up and idle for 1:30 hours by now. They don't
have any actual lxd workload due to bug 1628946 (juju deploy currently
fails), but the original hang bug actually happened on idle boxes. Thus,
so far so good :-)

I'll check again tomorrow.

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

Title:
  [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

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

Bug description:
  Hi,

  In order to investigate bug LP#1531768, we upgraded some arm64 compute
  nodes (swirlices) to a 4.4 kernel. I think it made the VMs work
  better, but the hosts became extremely unstable.

  After some time, getting a shell on them would be impossible.
  Connecting on the VSP, you'd get a prompt, and once you typed your
  username and password, you'd see the motd but the shell would never
  spawn.

  Because of these instability issues, all the arm64 compute nodes are
  now back on 4.2. However, we managed to capture "perf record" data
  when a host was failing. I'll attach it to the bug. Perhaps it will
  give you hints as to what we can do to help you troubleshoot this bug
  further.

  Once we have your instructions, we'll happily reboot one (or a few)
  nodes to 4.4 to continue troubleshooting.

  Thanks !
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 12 12:54 seq
   crw-rw 1 root audio 116, 33 Jul 12 12:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: arm64
  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: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l
  ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-41-generic N/A
   linux-backports-modules-4.2.0-41-generic  N/A
   linux-firmware1.127.22
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 4.2.0-41-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1628279] Re: python utilities script suffix (.py) should be removed as per Policy 10.4

[Eric Desrochers]

Note that this is based on a comment previously made by Adam that can be
found here :

https://bugs.launchpad.net/ubuntu/+source/zfs-
linux/+bug/1574342/comments/19

Eric

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

Title:
  python utilities script suffix (.py) should be removed as per Policy
  10.4

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  The zfs utilities scripts shipped with debian and ubuntu such as :

  * arc_summary.py : Provides a summary of the statistics
  https://github.com/zfsonlinux/zfs/blob/master/cmd/arc_summary

  * arcstat.py : Print out ZFS ARC Statistics exported via kstat(1)
  https://github.com/zfsonlinux/zfs/tree/master/cmd/arcstat

  * dbufstat.py : Print out statistics for all cached dmu buffers
  https://github.com/zfsonlinux/zfs/blob/master/cmd/dbufstat

  should be renamed according to Policy 10.4 :

  [https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts]

  "When scripts are installed into a directory in the system PATH, the
  script name should not include an extension such as .sh or .pl that
  denotes the scripting language currently used to implement it."

  Ideally, this should be fixed and upstreamed to Debian (or to zfslinux
  upstream) as well.

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

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

[Kernel-packages] [Bug 1628204] s2lp3 (s390x.LPAR) - tests ran: 83, failed: 1

[Brad Figg]

tests ran:  83, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-41.61/s2lp3__4.4.0-41.61__2016-09-29_14-26-00/results-index.html

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

Title:
  linux: 4.4.0-41.61 -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 Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-41.61 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
  derivative-trackers-created: 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/1628204/+subscriptions

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

[Kernel-packages] [Bug 1627574] s2lp6g002 (s390x.zKVM) - tests ran: 83, failed: 4

[Brad Figg]

tests ran:  83, failed: 4;
  
http://kernel.ubuntu.com/testing/4.8.0-18.20/s2lp6g002__4.8.0-18.20__2016-09-29_14-26-00/results-index.html

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

Title:
  linux: 4.8.0-18.20 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 27. September 2016 08:45 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

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

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

[Kernel-packages] [Bug 1628204] dwalin (amd64) - tests ran: 83, failed: 30

[Brad Figg]

tests ran:  83, failed: 30;
  
http://kernel.ubuntu.com/testing/4.4.0-41.61/dwalin__4.4.0-41.61__2016-09-29_10-30-00/results-index.html

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

Title:
  linux: 4.4.0-41.61 -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 Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-41.61 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
  derivative-trackers-created: 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/1628204/+subscriptions

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

[Kernel-packages] [Bug 1616107] Re: Kernel oops + system freeze on network-bridge shutdown

[Launchpad Bug Tracker]

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

** Changed in: bridge-utils (Ubuntu Xenial)
   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/1616107

Title:
  Kernel oops + system freeze on network-bridge shutdown

Status in bridge-utils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in bridge-utils source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in bridge-utils source package in Yakkety:
  Confirmed

Bug description:
  A Kernel oops leaves Ubuntu 16.04 unusable when a network bridge is
  brought down on a HPE 530SFP+ 10GBit NIC that uses bnx2x as a driver.
  This error does not appear in Ubuntu 14.04 however.

  The error is reproducible whenever issuing the commands "shutdown",
  "service networking stop" or "brctl delbr br0". Manually creating the
  bridge and subsequently bringing it down results in the same error.

  /var/log/kern.log:
  [...]
  Aug 23 15:09:46 base1 kernel: [  617.996677] device ens1f0 left promiscuous 
mode
  Aug 23 15:09:46 base1 kernel: [  617.996699] br0: port 1(ens1f0) entered 
disabled state
  Aug 23 15:09:46 base1 kernel: [  617.996730] BUG: unable to handle kernel 
NULL pointer dereference at 00d2
  Aug 23 15:09:46 base1 kernel: [  618.008306] IP: [] 
__vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.020549] PGD 10374c0067 PUD 1033927067 
PMD 0
  Aug 23 15:09:46 base1 kernel: [  618.032773] Oops: 0002 [#1] SMP
  Aug 23 15:09:46 base1 kernel: [  618.044434] Modules linked in: nls_iso8859_1 
ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm irqbypass sb_edac edac_core joydev bridge stp llc input_leds hpilo lpc_ich 
ioatdma ipmi_si ipmi_msghandler shpchp mac_hid acpi_power_meter ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear 
raid1 hid_generic crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw 
gf128mul glue_helper ablk_helper cryptd igb usbhid hid bnx2x dca ahci 
i2c_algo_bit vxlan libahci ip6_udp_tunnel udp_tunnel ptp pps_core mdio 
libcrc32c wmi fjes
  Aug 23 15:09:46 base1 kernel: [  618.058563] CPU: 3 PID: 4049 Comm: brctl Not 
tainted 4.4.0-34-generic #53-Ubuntu
  Aug 23 15:09:46 base1 kernel: [  618.058564] Hardware name: HP ProLiant DL120 
Gen9/ProLiant DL120 Gen9, BIOS P86 05/05/2016
  Aug 23 15:09:46 base1 kernel: [  618.058574] task: 881030676040 ti: 
8810341e4000 task.ti: 8810341e4000
  Aug 23 15:09:46 base1 kernel: [  618.058576] RIP: 0010:[]  
[] __vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058754] RSP: 0018:8810341e7d68  
EFLAGS: 00010206
  Aug 23 15:09:46 base1 kernel: [  618.058769] RAX:  RBX: 
 RCX: 
  Aug 23 15:09:46 base1 kernel: [  618.058774] RDX: 881038470848 RSI: 
 RDI: 
  Aug 23 15:09:46 base1 kernel: [  618.058775] RBP: 8810341e7d78 R08: 
 R09: 8170d949
  Aug 23 15:09:46 base1 kernel: [  618.058776] R10: ead61340 R11: 
8810329d2c00 R12: 00c0
  Aug 23 15:09:46 base1 kernel: [  618.058777] R13: 881030044000 R14: 
881038470840 R15: 
  Aug 23 15:09:46 base1 kernel: [  618.058782] FS:  7f9aebc94700() 
GS:88107fcc() knlGS:
  Aug 23 15:09:46 base1 kernel: [  618.058789] CS:  0010 DS:  ES:  CR0: 
80050033
  Aug 23 15:09:46 base1 kernel: [  618.058790] CR2: 00d2 CR3: 
00102fe83000 CR4: 001406e0
  Aug 23 15:09:46 base1 kernel: [  618.058802] Stack:
  Aug 23 15:09:46 base1 kernel: [  618.058806]   
8810356a4c00 8810341e7d98 c0489258
  Aug 23 15:09:46 base1 kernel: [  618.058822]  8810356a4c00 
881038470840 8810341e7dc0 c0479bd8
  Aug 23 15:09:46 base1 kernel: [  618.058825]  881038470838 
881038470848 88103847 8810341e7df8
  Aug 23 15:09:46 base1 kernel: [  618.058827] Call Trace:
  Aug 23 15:09:46 base1 kernel: [  618.058863]  [] 
nbp_vlan_flush+0x28/0x65 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058870]  [] 
del_nbp+0x98/0x130 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058889]  [] 
br_dev_delete+0x42/0xb0 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058895]  [] 
br_del_bridge+0x4a/0x70 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058911]  [] 
br_ioctl_deviceless_stub+0x153/0x230 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058984]  [] ? 
security_file_alloc+0x33/0x50
  Aug 23 15:09:46 base1 kernel: [  618.059095]  [] 
sock_ioctl+0x215/0x290
  Aug 23 15:09:46 base1 kernel: [  618.059121]  [] 

[Kernel-packages] [Bug 1616107] Re: Kernel oops + system freeze on network-bridge shutdown

[Launchpad Bug Tracker]

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

** Changed in: bridge-utils (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/1616107

Title:
  Kernel oops + system freeze on network-bridge shutdown

Status in bridge-utils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in bridge-utils source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in bridge-utils source package in Yakkety:
  Confirmed

Bug description:
  A Kernel oops leaves Ubuntu 16.04 unusable when a network bridge is
  brought down on a HPE 530SFP+ 10GBit NIC that uses bnx2x as a driver.
  This error does not appear in Ubuntu 14.04 however.

  The error is reproducible whenever issuing the commands "shutdown",
  "service networking stop" or "brctl delbr br0". Manually creating the
  bridge and subsequently bringing it down results in the same error.

  /var/log/kern.log:
  [...]
  Aug 23 15:09:46 base1 kernel: [  617.996677] device ens1f0 left promiscuous 
mode
  Aug 23 15:09:46 base1 kernel: [  617.996699] br0: port 1(ens1f0) entered 
disabled state
  Aug 23 15:09:46 base1 kernel: [  617.996730] BUG: unable to handle kernel 
NULL pointer dereference at 00d2
  Aug 23 15:09:46 base1 kernel: [  618.008306] IP: [] 
__vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.020549] PGD 10374c0067 PUD 1033927067 
PMD 0
  Aug 23 15:09:46 base1 kernel: [  618.032773] Oops: 0002 [#1] SMP
  Aug 23 15:09:46 base1 kernel: [  618.044434] Modules linked in: nls_iso8859_1 
ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm irqbypass sb_edac edac_core joydev bridge stp llc input_leds hpilo lpc_ich 
ioatdma ipmi_si ipmi_msghandler shpchp mac_hid acpi_power_meter ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear 
raid1 hid_generic crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw 
gf128mul glue_helper ablk_helper cryptd igb usbhid hid bnx2x dca ahci 
i2c_algo_bit vxlan libahci ip6_udp_tunnel udp_tunnel ptp pps_core mdio 
libcrc32c wmi fjes
  Aug 23 15:09:46 base1 kernel: [  618.058563] CPU: 3 PID: 4049 Comm: brctl Not 
tainted 4.4.0-34-generic #53-Ubuntu
  Aug 23 15:09:46 base1 kernel: [  618.058564] Hardware name: HP ProLiant DL120 
Gen9/ProLiant DL120 Gen9, BIOS P86 05/05/2016
  Aug 23 15:09:46 base1 kernel: [  618.058574] task: 881030676040 ti: 
8810341e4000 task.ti: 8810341e4000
  Aug 23 15:09:46 base1 kernel: [  618.058576] RIP: 0010:[]  
[] __vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058754] RSP: 0018:8810341e7d68  
EFLAGS: 00010206
  Aug 23 15:09:46 base1 kernel: [  618.058769] RAX:  RBX: 
 RCX: 
  Aug 23 15:09:46 base1 kernel: [  618.058774] RDX: 881038470848 RSI: 
 RDI: 
  Aug 23 15:09:46 base1 kernel: [  618.058775] RBP: 8810341e7d78 R08: 
 R09: 8170d949
  Aug 23 15:09:46 base1 kernel: [  618.058776] R10: ead61340 R11: 
8810329d2c00 R12: 00c0
  Aug 23 15:09:46 base1 kernel: [  618.058777] R13: 881030044000 R14: 
881038470840 R15: 
  Aug 23 15:09:46 base1 kernel: [  618.058782] FS:  7f9aebc94700() 
GS:88107fcc() knlGS:
  Aug 23 15:09:46 base1 kernel: [  618.058789] CS:  0010 DS:  ES:  CR0: 
80050033
  Aug 23 15:09:46 base1 kernel: [  618.058790] CR2: 00d2 CR3: 
00102fe83000 CR4: 001406e0
  Aug 23 15:09:46 base1 kernel: [  618.058802] Stack:
  Aug 23 15:09:46 base1 kernel: [  618.058806]   
8810356a4c00 8810341e7d98 c0489258
  Aug 23 15:09:46 base1 kernel: [  618.058822]  8810356a4c00 
881038470840 8810341e7dc0 c0479bd8
  Aug 23 15:09:46 base1 kernel: [  618.058825]  881038470838 
881038470848 88103847 8810341e7df8
  Aug 23 15:09:46 base1 kernel: [  618.058827] Call Trace:
  Aug 23 15:09:46 base1 kernel: [  618.058863]  [] 
nbp_vlan_flush+0x28/0x65 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058870]  [] 
del_nbp+0x98/0x130 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058889]  [] 
br_dev_delete+0x42/0xb0 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058895]  [] 
br_del_bridge+0x4a/0x70 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058911]  [] 
br_ioctl_deviceless_stub+0x153/0x230 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058984]  [] ? 
security_file_alloc+0x33/0x50
  Aug 23 15:09:46 base1 kernel: [  618.059095]  [] 
sock_ioctl+0x215/0x290
  Aug 23 15:09:46 base1 kernel: [  618.059121]  [] 

[Kernel-packages] [Bug 1627574] s2lp6g002 (s390x.zKVM) - tests ran: 19, failed: 7

[Brad Figg]

tests ran:  19, failed: 7;
  
http://kernel.ubuntu.com/testing/4.8.0-18.20/s2lp6g002__4.8.0-18.20__2016-09-29_14-14-00/results-index.html

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

Title:
  linux: 4.8.0-18.20 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 27. September 2016 08:45 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

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

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

[Kernel-packages] [Bug 1628204] s2lp3 (s390x.LPAR) - tests ran: 19, failed: 7

[Brad Figg]

tests ran:  19, failed: 7;
  
http://kernel.ubuntu.com/testing/4.4.0-41.61/s2lp3__4.4.0-41.61__2016-09-29_14-14-00/results-index.html

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

Title:
  linux: 4.4.0-41.61 -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 Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-41.61 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
  derivative-trackers-created: 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/1628204/+subscriptions

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

Re: [Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

[Barry Warsaw]

On Sep 29, 2016, at 03:20 AM, Joseph Salisbury wrote:

>I built the next test kernel, up to the following commit:
>1eccfa090eaea22558570054bbdc147817e1df5e

201609282035 boots, does not give me a desktop, and I see the crash in the
syslog.

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

Title:
  4.8.0 kernels do not complete boot process on VM

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

Bug description:
  On my native amd64 box, 4.8.0-15 works just fine, but on my VMWare
  Fusion 8.5 system, none of the 4.8.0 kernels complete the boot
  process.  I tried 4.8.0-15 from yakkety and 4.8.0-16 from yakkety-
  proposed.

  Currently  I am seeing the last message in my console at boot up as:

  [ OK ] Started Bluetooth service

  and then... it just sits there.

  Through the use of snapshots, restores, and package bisects, I've
  definitively narrowed it to linux-generic linux-image-generic and
  linux-headers-generic.

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

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

[Kernel-packages] [Bug 1627574] s2lp6g002 (s390x.zKVM) - tests ran: 32, failed: 1

[Brad Figg]

tests ran:  32, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-18.20/s2lp6g002__4.8.0-18.20__2016-09-29_12-48-00/results-index.html

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

Title:
  linux: 4.8.0-18.20 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 27. September 2016 08:45 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

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

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

[Kernel-packages] [Bug 1628204] s2lp3 (s390x.LPAR) - tests ran: 4, failed: 3

[Brad Figg]

tests ran:   4, failed: 3;
  
http://kernel.ubuntu.com/testing/4.4.0-41.61/s2lp3__4.4.0-41.61__2016-09-29_13-38-00/results-index.html

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

Title:
  linux: 4.4.0-41.61 -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 Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-41.61 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
  derivative-trackers-created: 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/1628204/+subscriptions

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

[Kernel-packages] [Bug 1602577] Re: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

[Junien Fridrick]

It's booting \o/ We're trying to replicate the instability, we'll let
you know.

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

Title:
  [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

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

Bug description:
  Hi,

  In order to investigate bug LP#1531768, we upgraded some arm64 compute
  nodes (swirlices) to a 4.4 kernel. I think it made the VMs work
  better, but the hosts became extremely unstable.

  After some time, getting a shell on them would be impossible.
  Connecting on the VSP, you'd get a prompt, and once you typed your
  username and password, you'd see the motd but the shell would never
  spawn.

  Because of these instability issues, all the arm64 compute nodes are
  now back on 4.2. However, we managed to capture "perf record" data
  when a host was failing. I'll attach it to the bug. Perhaps it will
  give you hints as to what we can do to help you troubleshoot this bug
  further.

  Once we have your instructions, we'll happily reboot one (or a few)
  nodes to 4.4 to continue troubleshooting.

  Thanks !
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 12 12:54 seq
   crw-rw 1 root audio 116, 33 Jul 12 12:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: arm64
  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: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l
  ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-41-generic N/A
   linux-backports-modules-4.2.0-41-generic  N/A
   linux-firmware1.127.22
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 4.2.0-41-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1628204] s2lp3 (s390x.LPAR) - tests ran: 10, failed: 1

[Brad Figg]

tests ran:  10, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-41.61/s2lp3__4.4.0-41.61__2016-09-29_13-07-00/results-index.html

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

Title:
  linux: 4.4.0-41.61 -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 Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-41.61 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
  derivative-trackers-created: 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/1628204/+subscriptions

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

[Kernel-packages] [Bug 1628204] s2lp3 (s390x.LPAR) - tests ran: 1, failed: 1

[Brad Figg]

tests ran:   1, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-41.61/s2lp3__4.4.0-41.61__2016-09-29_13-05-00/results-index.html

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

Title:
  linux: 4.4.0-41.61 -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 Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-41.61 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
  derivative-trackers-created: 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/1628204/+subscriptions

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

[Kernel-packages] [Bug 1627387] s2lp6g002 (s390x.zKVM) - tests ran: 1, failed: 1

[Brad Figg]

tests ran:   1, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-18.20/s2lp6g002__4.8.0-18.20__2016-09-29_12-46-00/results-index.html

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

Title:
  linux: 4.8.0-17.19 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Confirmed
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  This bug is for tracking the 4.8.0-17.19 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
  derivative-trackers-created: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1619552] Re: Failed to acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such file or directory)

[Tim Gardner]

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

** Tags removed: verification-done-xenial
** Tags added: verification-needed-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/1619552

Title:
  Failed to acknowledge elog:
  /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such file or
  directory)

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

Bug description:
  == Comment: #0 - Mukesh K. Ojha  - 2016-09-02 02:10:14 ==
  ---Problem Description---
  Kernel is failed to free the kobject while acknowledging the error log which 
has been notified two times.
   
  Contact Information = Contact Information =  mukeo...@in.ibm.com 
   
  ---uname output---
  Ubuntu 16.04.01 LTS
   
  Machine Type = All power machine 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   
  Steps to reproduce:
  1.Boot the system to petitboot.
  2. Issue FSP Soft reset of Service Processor From ASMI page.
  3. After FSP comes up, boot the system to host OS.
  4. In the host OS seen the failure to acknowledge for one of elog.

  
  root@p8wookie ~]# service opal_errd status
  Redirecting to /bin/systemctl status  opal_errd.service
  opal_errd.service - opal_errd (PowerNV platform error handling) Service
 Loaded: loaded (/usr/lib/systemd/system/opal_errd.service; enabled)
 Active: active (running) since Wed 2016-08-03 07:55:03 CDT; 2min 4s ago
Process: 3452 ExecStart=/usr/libexec/ppc64-diag/opal_errd start 
(code=exited, status=0/SUCCESS)
   Main PID: 3497 (opal_errd)
 CGroup: /system.slice/opal_errd.service
 ??3497 /usr/sbin/opal_errd

  Aug 03 07:57:03 p8wookie.aus.stglabs.ibm.com ELOG[3497]: 
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service 
action required
  Aug 03 07:57:03 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to 
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such 
file or directory)
  Aug 03 07:57:04 p8wookie.aus.stglabs.ibm.com ELOG[3497]: 
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service 
action required
  Aug 03 07:57:04 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to 
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such 
file or directory)
  Aug 03 07:57:05 p8wookie.aus.stglabs.ibm.com ELOG[3497]: 
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service 
action required
  Aug 03 07:57:05 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to 
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such 
file or directory)
  Aug 03 07:57:06 p8wookie.aus.stglabs.ibm.com ELOG[3497]: 
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service 
action required
  Aug 03 07:57:06 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to 
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such 
file or directory)
  Aug 03 07:57:07 p8wookie.aus.stglabs.ibm.com ELOG[3497]: 
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service 
action required
  Aug 03 07:57:07 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to 
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such 
file or directory)


  
  [root@p8wookie ~]# cd /sys/firmware/opal/elog/
  [root@p8wookie elog]# ls
  0x5018d709
  [root@p8wookie elog]# 
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for Contact Information =  mukeo...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.

  == Comment: #1 - Mukesh K. Ojha  - 2016-09-02 02:12:45 ==
  Upstream commit :

  commit a9cbf0b2195b695cbcaa4e2770948c212e9a
  Author: Mukesh Ojha 
  Date:   Mon Aug 22 12:17:44 2016 +0530

  powerpc/powernv : Drop reference added by kset_find_obj()
  
  In a situation, where Linux kernel gets notified about duplicate error log
  from OPAL, it is been observed that kernel fails to remove sysfs entries
  (/sys/firmware/opal/elog/0x) of such error logs. This is because,
  we currently search the error log/dump kobject in the kset list via
  'kset_find_obj()' routine. Which eventually increment the reference count
  by one, once it founds the kobject.

  
  Above patch is the solution of this bugzilla.

  Kindly pull this patch in for both Ubuntu 16.04 LTS and Ubuntu 16.10.

  -Mukesh

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

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

[Kernel-packages] [Bug 1628279] Re: python utilities script suffix (.py) should be removed as per Policy 10.4

[Eric Desrochers]

** Changed in: zfs-linux (Ubuntu)
   Importance: Medium => Low

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

Title:
  python utilities script suffix (.py) should be removed as per Policy
  10.4

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  The zfs utilities scripts shipped with debian and ubuntu such as :

  * arc_summary.py : Provides a summary of the statistics
  https://github.com/zfsonlinux/zfs/blob/master/cmd/arc_summary

  * arcstat.py : Print out ZFS ARC Statistics exported via kstat(1)
  https://github.com/zfsonlinux/zfs/tree/master/cmd/arcstat

  * dbufstat.py : Print out statistics for all cached dmu buffers
  https://github.com/zfsonlinux/zfs/blob/master/cmd/dbufstat

  should be renamed according to Policy 10.4 :

  [https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts]

  "When scripts are installed into a directory in the system PATH, the
  script name should not include an extension such as .sh or .pl that
  denotes the scripting language currently used to implement it."

  Ideally, this should be fixed and upstreamed to Debian (or to zfslinux
  upstream) as well.

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

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

Re: [Kernel-packages] [Bug 1611078] Re: Support snaps inside of lxd containers

[Mark Shuttleworth]

Thanks guys, can't wait to see this in action :)

Mark

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

Title:
  Support snaps inside of lxd containers

Status in lxd:
  Unknown
Status in Snappy:
  Fix Committed
Status in apparmor package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in lxd package in Ubuntu:
  Fix Committed

Bug description:
  I tried following the instructions on snapcraft.io and got a failure.
  See the output below.  I've also attached the relevant output from
  running "journalctl -xe".

  uname: Linux 3.19.0-65-generic x86_64
  release: Ubuntu 16.04
  package: snapd 2.11+0.16.04

  Notably, I'm running this in an LXD container (version: 2.0.0.rc9).

  -

  $ sudo snap install hello-world
  64.75 MB / 64.75 MB 
[==]
 100.00 % 2.85 MB/s 

  error: cannot perform the following tasks:
  - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] 
failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See 
"systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for 
details.
  )
  $ ls -la /snap
  total 4K
  drwxr-xr-x 3 root root 4096 Aug  8 17:49 ubuntu-core
  $ ls -la /snap/ubuntu-core/
  total 4K
  drwxr-xr-x 2 root root 4096 Aug  8 17:49 122
  $ ls -la /snap/ubuntu-core/122/
  total 0K
  $ systemctl status "snap-ubuntu\\x2dcore-122.mount"
  ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core
 Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; 
enabled; vendor preset: enabled)
 Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min 
ago
  Where: /snap/ubuntu-core/122
   What: /var/lib/snapd/snaps/ubuntu-core_122.snap
Process: 31781 ExecMount=/bin/mount 
/var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs 
(code=exited, status=32)

  Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core...
  Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount 
failed: Unknown error -1
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount 
process exited, code=exited status=32
  Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for 
ubuntu-core.
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit 
entered failed state.

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

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

[Kernel-packages] [Bug 1628279] Re: python utilities script suffix (.py) should be removed as per Policy 10.4

[Eric Desrochers]

I look at the dh_exec approach and that requires the following :

· The package must be using compatibility level 9 or later (see debhelper(7))
· The package will need a build-dependency on dh-exec.
· The install file must be marked as executable.

Debian unstable is already at compat "9"

v9 also seems to be the recommended mode of operation.

reference:
https://www.mankier.com/1/dh_install
https://www.mankier.com/7/debhelper

The other method, would be to rename the utilities during the
debian/rules "build" target before you get to the dh_install invocation.

I'll have a look at both approaches.

Eric

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

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

Title:
  python utilities script suffix (.py) should be removed as per Policy
  10.4

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  The zfs utilities scripts shipped with debian and ubuntu such as :

  * arc_summary.py : Provides a summary of the statistics
  https://github.com/zfsonlinux/zfs/blob/master/cmd/arc_summary

  * arcstat.py : Print out ZFS ARC Statistics exported via kstat(1)
  https://github.com/zfsonlinux/zfs/tree/master/cmd/arcstat

  * dbufstat.py : Print out statistics for all cached dmu buffers
  https://github.com/zfsonlinux/zfs/blob/master/cmd/dbufstat

  should be renamed according to Policy 10.4 :

  [https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts]

  "When scripts are installed into a directory in the system PATH, the
  script name should not include an extension such as .sh or .pl that
  denotes the scripting language currently used to implement it."

  Ideally, this should be fixed and upstreamed to Debian (or to zfslinux
  upstream) as well.

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

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

[Kernel-packages] [Bug 1574125] Re: [Lenovo G50-70] suspend not working after upgrade

[Slither]

I've also tried upgrading to kernel 4.6 as suggested in comment #58 and
still have the same problem.

$ uname -a
Linux NAS 4.6.0-040600-generic #201606100558 SMP Fri Jun 10 10:01:15 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  [Lenovo G50-70] suspend not working after upgrade

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Upgraded from Ubuntu 15.10 where suspend workes flawlessly. After
  upgrade, putting machine in suspend turns the monitor black and
  everything seem to be off, though the fan still spins, the power light
  is on and the battery is trained. Nothing seem to wake it up (Meaning
  different key combinations - trying to get a shell by Ctrl+Alt+F1, for
  example; pressing power, any other key).

  Unsure how to try to get it working since I have to kill the power by
  pressing down the power button, then restarting it (it then does a
  drive scan for errors).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maria  2076 F pulseaudio
   /dev/snd/controlC1:  maria  2076 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Apr 24 00:07:49 2016
  HibernationDevice: RESUME=UUID=cc1bb3f2-abd6-41ad-b36e-62190fc5faaa
  InstallationDate: Installed on 2016-01-31 (83 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20351
  ProcEnviron:
   LANGUAGE=sv
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (2 days ago)
  dmi.bios.date: 04/02/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ACN25WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoG50-70:
  dmi.product.name: 20351
  dmi.product.version: Lenovo G50-70
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1613270] Re: Cannot power down system

[Brian Knutsson]

Thank you for all your help.

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

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

Title:
  Cannot power down system

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I cannot do a shutdown of the system. It never turns off my computer.

  If I track the shutdown process, it ends with:
  System: Power down

  And then nothing happends except for the internal fans normally speeds
  up, but it does not turn off the PC.

  I can do a reboot without problems.

  I tried the dev kernel version 4.8.0 (amd64) but it did not solve the
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bfk5288 F pulseaudio
   /dev/snd/controlC1:  bfk5288 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Aug 15 14:22:07 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=1d553aaa-5506-4fdd-b6e4-2da0c11fb7f8
  InstallationDate: Installed on 2016-03-10 (157 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  MachineType: Apple Inc. MacBookPro11,5
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=980d5758-068c-4c32-8f18-ac0d9c15855b ro quiet splash acpi=force 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP114.88Z.0172.B06.1509021656
  dmi.board.name: Mac-06F11F11946D27C5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,5
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-06F11F11946D27C5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B06.1509021656:bd09/02/2015:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5:
  dmi.product.name: MacBookPro11,5
  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/1613270/+subscriptions

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

[Kernel-packages] [Bug 1607920] Re: zfs services fail on firstboot if zfs-utils is integrated into the deployment image

[Eric Desrochers]

** Description changed:

  [Impact]
  
   * zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image.
  
   * Output from systemd -
  sudo systemctl --failed
  UNIT LOAD ACTIVE SUB DESCRIPTION
  ● zfs-import-scan.service loaded failed failed Import ZFS pools by device 
scanning
  ● zfs-mount.service loaded failed failed Mount ZFS filesystems
  
   * This is particularly frustrating for users who use automated
  monitoring as it means virtual machines must always be restarted before
  showing as clean.
  
   * This failure is due to zfs services starting up before /etc/mtab has
  a chance to be symlinked to /proc/mounts.
  
  [Test Case]
  
   1. Grab a stock xenial image, and unpack it and add zfs-utils to it.  Repack 
it.
   2. Boot machine
   3. Check systemctl --failed.
  
  [Regression Potential]
  
   * none expected, patch has been intensively tested by the upsteam zfs
  test script suite.
  
   * This is a upstream commit merge in 0.7.0.
  
   * A ubuntu package has been tested (including the upstream commit) by a
  user of the community facing this bug, and confirmed it addresses the
  problem (see comment #7).
  
  [Other Info]
  
-  * Upstream commit :
- 
https://github.com/zfsonlinux/zfs/commit/792517389fad5c495a2738b61c2e9c65dedaaa9a
+ * The "reading" is redirected to /proc/self/mounts. 
+ The writing to /etc/mtab. Some distros still need that. The current hope is 
to replace the writing (and maybe reading) with libmount, in a second phase.
+ 
+ 
+  * Upstream commit : 
https://github.com/zfsonlinux/zfs/commit/792517389fad5c495a2738b61c2e9c65dedaaa9a
  
   * Upstream bug: https://github.com/zfsonlinux/zfs/issues/4680
  
-  
-  * Debian bug : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839071
+  * Debian bug : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839071

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

Title:
  zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image

Status in sysvinit package in Ubuntu:
  Won't Fix
Status in zfs-linux package in Ubuntu:
  In Progress
Status in sysvinit source package in Xenial:
  Won't Fix
Status in zfs-linux source package in Xenial:
  In Progress

Bug description:
  [Impact]

   * zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image.

   * Output from systemd -
  sudo systemctl --failed
  UNIT LOAD ACTIVE SUB DESCRIPTION
  ● zfs-import-scan.service loaded failed failed Import ZFS pools by device 
scanning
  ● zfs-mount.service loaded failed failed Mount ZFS filesystems

   * This is particularly frustrating for users who use automated
  monitoring as it means virtual machines must always be restarted
  before showing as clean.

   * This failure is due to zfs services starting up before /etc/mtab
  has a chance to be symlinked to /proc/mounts.

  [Test Case]

   1. Grab a stock xenial image, and unpack it and add zfs-utils to it.  Repack 
it.
   2. Boot machine
   3. Check systemctl --failed.

  [Regression Potential]

   * none expected, patch has been intensively tested by the upsteam zfs
  test script suite.

   * This is a upstream commit merge in 0.7.0.

   * A ubuntu package has been tested (including the upstream commit) by
  a user of the community facing this bug, and confirmed it addresses
  the problem (see comment #7).

  [Other Info]

  * The "reading" is redirected to /proc/self/mounts. 
  The writing to /etc/mtab. Some distros still need that. The current hope is 
to replace the writing (and maybe reading) with libmount, in a second phase.

  
   * Upstream commit : 
https://github.com/zfsonlinux/zfs/commit/792517389fad5c495a2738b61c2e9c65dedaaa9a

   * Upstream bug: https://github.com/zfsonlinux/zfs/issues/4680

   * Debian bug : https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=839071

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

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

[Kernel-packages] [Bug 1574125] Re: [Lenovo G50-70] suspend not working after upgrade

[Slither]

I'm having the same issue as described in this bug.

$ uname -a
Linux NAS 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux

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

Title:
  [Lenovo G50-70] suspend not working after upgrade

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Upgraded from Ubuntu 15.10 where suspend workes flawlessly. After
  upgrade, putting machine in suspend turns the monitor black and
  everything seem to be off, though the fan still spins, the power light
  is on and the battery is trained. Nothing seem to wake it up (Meaning
  different key combinations - trying to get a shell by Ctrl+Alt+F1, for
  example; pressing power, any other key).

  Unsure how to try to get it working since I have to kill the power by
  pressing down the power button, then restarting it (it then does a
  drive scan for errors).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maria  2076 F pulseaudio
   /dev/snd/controlC1:  maria  2076 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Apr 24 00:07:49 2016
  HibernationDevice: RESUME=UUID=cc1bb3f2-abd6-41ad-b36e-62190fc5faaa
  InstallationDate: Installed on 2016-01-31 (83 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20351
  ProcEnviron:
   LANGUAGE=sv
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (2 days ago)
  dmi.bios.date: 04/02/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ACN25WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoG50-70:
  dmi.product.name: 20351
  dmi.product.version: Lenovo G50-70
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1628204] modoc (ppc64el) - tests ran: 64, failed: 0

[Brad Figg]

tests ran:  64, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-41.61/modoc__4.4.0-41.61__2016-09-29_11-05-00/results-index.html

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

Title:
  linux: 4.4.0-41.61 -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 Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-41.61 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
  derivative-trackers-created: 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/1628204/+subscriptions

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

[Kernel-packages] [Bug 1628204] modoc (ppc64el) - tests ran: 2, failed: 0

[Brad Figg]

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-41.61/modoc__4.4.0-41.61__2016-09-29_10-35-00/results-index.html

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

Title:
  linux: 4.4.0-41.61 -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 Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-41.61 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
  derivative-trackers-created: 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/1628204/+subscriptions

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