date:20170307

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-11.13-generic/amaura__4.10.0-11.13__2017-03-08_03-11-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/1669127

Title:
  linux: 4.10.0-11.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
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:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.10.0-11.13 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 --
  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-development-workflow/+bug/1669127/+subscriptions

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

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

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1670938

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

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

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

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

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

Title:
  Not working post install on Vmware workstation 12

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Installed Ubuntu 16.10 on VMware workstations 12. The booting up is
  very slow and after logging in, only the wallpaper comes up and no
  icons or anything come up or work.

  Host configuration : Win7 64bit, 4 gb ram.
  Guest configuration : 12GB hdd space, 1.6 GB ram, one core one processor, 
swap enabled, scsi, LSI.

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

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

[Kernel-packages] [Bug 1572801] Re: Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10

2017-03-07 Thread WindTux

with KDE Neon there are not problems of Excessive consumption... is
unity or gnome 3.18 the problem...

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

Title:
  Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10

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

Bug description:
  Ubuntu 16.04 64bit ISO number 20160420.1
  unity version 7.4.0+16.04.20160415-0ubuntu1
  Ubuntu 16.04 64bit ram usage has increase dramatically over Ubuntu 15.10
  Ubuntu 16.04 ram roughly 1 GB Ubuntu15.10 can be tuned to 420, 450 MB
  Ubuntu 16.04 with unity uses 1GB whereas Kubuntu 16.04 is using 420MB live usb

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.376
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Apr 21 01:44:22 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  GsettingsChanges:
   b'org.compiz.core' b'outputs' b"['1920x1080+0+0']"
   b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 
'place', 'regex', 'resize', 'session', 'snap', 'vpswitch', 'wall', 'animation', 
'commands', 'compiztoolbox', 'copytex', 'fade', 'grid', 'imgpng', 'mousepoll', 
'move', 'scale', 'unitymtgrabhandles', 'workarounds', 'expo', 'ezoom', 
'unityshell']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- 
cdrom-detect/try-usb=true noprompt
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/03/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2004
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2004:bd06/03/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PLUS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Apr 21 01:37:17 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Kernel-packages] [Bug 1670938] [NEW] Not working post install on Vmware workstation 12

2017-03-07 Thread arptiw

Public bug reported:

Hi,

Installed Ubuntu 16.10 on VMware workstations 12. The booting up is very
slow and after logging in, only the wallpaper comes up and no icons or
anything come up or work.

Host configuration : Win7 64bit, 4 gb ram.
Guest configuration : 12GB hdd space, 1.6 GB ram, one core one processor, swap 
enabled, scsi, LSI.

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

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

Title:
  Not working post install on Vmware workstation 12

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,

  Installed Ubuntu 16.10 on VMware workstations 12. The booting up is
  very slow and after logging in, only the wallpaper comes up and no
  icons or anything come up or work.

  Host configuration : Win7 64bit, 4 gb ram.
  Guest configuration : 12GB hdd space, 1.6 GB ram, one core one processor, 
swap enabled, scsi, LSI.

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

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

[Kernel-packages] [Bug 1599681] Re: ceph-osd process hung and blocked ps listings

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  ceph-osd process hung and blocked ps listings

Status in ceph package in Ubuntu:
  Expired
Status in linux package in Ubuntu:
  Expired

Bug description:
  We ran into a situation over the past couple of days where we had 2
  different ceph-osd nodes crash in such a way that they caused ps
  listing to hang when enumerating the process.  Both had a call trace
  associated with them:

  Node 1:
  Jul  4 07:46:15 provider-cs-03 kernel: [4188396.493011] ceph-osdD 
882029a67b90 0  5312  1 0x0004
  Jul  4 07:46:15 provider-cs-03 kernel: [4188396.590564]  882029a67b90 
881037cb8000 8820284f3700 882029a68000
  Jul  4 07:46:16 provider-cs-03 kernel: [4188396.688603]  88203296e5a8 
88203296e5c0 0015 8820284f3700
  Jul  4 07:46:16 provider-cs-03 kernel: [4188396.789329]  882029a67ba8 
817ec495 8820284f3700 882029a67bf8
  Jul  4 07:46:16 provider-cs-03 kernel: [4188396.891376] Call Trace:
  Jul  4 07:46:16 provider-cs-03 kernel: [4188396.939271]  [] 
schedule+0x35/0x80
  Jul  4 07:46:16 provider-cs-03 kernel: [4188396.989957]  [] 
rwsem_down_read_failed+0xea/0x120
  Jul  4 07:46:16 provider-cs-03 kernel: [4188397.041502]  [] 
call_rwsem_down_read_failed+0x14/0x30
  Jul  4 07:46:16 provider-cs-03 kernel: [4188397.092616]  [] 
? __clear_user+0x25/0x50
  Jul  4 07:46:16 provider-cs-03 kernel: [4188397.141510]  [] 
? __clear_user+0x25/0x50
  Jul  4 07:46:16 provider-cs-03 kernel: [4188397.189877]  [] 
? down_read+0x20/0x30
  Jul  4 07:46:16 provider-cs-03 kernel: [4188397.237513]  [] 
__do_page_fault+0x398/0x430
  Jul  4 07:46:16 provider-cs-03 kernel: [4188397.285588]  [] 
do_page_fault+0x22/0x30
  Jul  4 07:46:16 provider-cs-03 kernel: [4188397.332936]  [] 
page_fault+0x28/0x30
  Jul  4 07:46:16 provider-cs-03 kernel: [4188397.379495]  [] 
? __clear_user+0x25/0x50
  Jul  4 07:46:16 provider-cs-03 kernel: [4188397.426400]  [] 
copy_fpstate_to_sigframe+0x118/0x1d0
  Jul  4 07:46:16 provider-cs-03 kernel: [4188397.474904]  [] 
get_sigframe.isra.7.constprop.9+0x12d/0x150
  Jul  4 07:46:16 provider-cs-03 kernel: [4188397.563204]  [] 
do_signal+0x1e8/0x6d0
  Jul  4 07:46:16 provider-cs-03 kernel: [4188397.609783]  [] 
? __sys_sendmsg+0x42/0x80
  Jul  4 07:46:16 provider-cs-03 kernel: [4188397.656633]  [] 
? handle_mm_fault+0x250/0x540
  Jul  4 07:46:16 provider-cs-03 kernel: [4188397.703785]  [] 
exit_to_usermode_loop+0x59/0xa2
  Jul  4 07:46:17 provider-cs-03 kernel: [4188397.751367]  [] 
syscall_return_slowpath+0x4e/0x60
  Jul  4 07:46:17 provider-cs-03 kernel: [4188397.799369]  [] 
int_ret_from_sys_call+0x25/0x8f

  Node 2:
  [733869.727139] CPU: 17 PID: 1735127 Comm: ceph-osd Not tainted 
4.4.0-15-generic #31-Ubuntu
  [733869.796954] Hardware name: Dell Inc. PowerEdge R730/0H21J3, BIOS 1.3.6 
06/03/2015
  [733869.927182] task: 881841dc6e00 ti: 8810cc0a task.ti: 
8810cc0a
  [733870.059139] RIP: 0010:[]  [] 
task_numa_find_cpu+0x2cd/0x710
  [733870.192753] RSP: :8810cc0a3bd8  EFLAGS: 00010257
  [733870.260298] RAX:  RBX: 8810cc0a3c78 RCX: 
0012
  [733870.389322] RDX:  RSI:  RDI: 
8810210a0e00
  [733870.517883] RBP: 8810cc0a3c40 R08: 0006 R09: 
013e
  [733870.646335] R10: 03b4 R11: 001f R12: 
881018118000
  [733870.774514] R13: 0006 R14: 8810210a0e00 R15: 
0379
  [733870.902262] FS:  7fdcfab03700() GS:88203e60() 
knlGS:
  [733871.031347] CS:  0010 DS:  ES:  CR0: 80050033
  [733871.097820] CR2: 7fdcfab02c20 CR3: 001029204000 CR4: 
001406e0
  [733871.223381] Stack:
  [733871.282453]  8810cc0a3c40 811f04ce 88102f6e9680 
0012
  [733871.404947]  0077 008f 00016d40 
0006
  [733871.527250]  881841dc6e00 8810cc0a3c78 01ac 
01b8
  [733871.649648] Call Trace:
  [733871.707884]  [] ? migrate_page_copy+0x21e/0x530
  [733871.770946]  [] task_numa_migrate+0x43e/0x9b0
  [733871.832808]  [] ? page_add_anon_rmap+0x10/0x20
  [733871.893897]  [] numa_migrate_preferred+0x79/0x80
  [733871.954283]  [] task_numa_fault+0x7f4/0xd40
  [733872.013128]  [] handle_mm_fault+0xbc0/0x1820
  [733872.071309]  [] ? do_futex+0x120/0x500
  [733872.128149]  [] ? __fget_light+0x25/0x60
  [733872.184044]  [] __do_page_fault+0x197/0x400
  [733872.239300]  [] do_page_fault+0x22/0x30
  [733872.293001]  [] page_fault+0x28/0x30
  [733872.345187] Code: d0 4c 89 f7 e8 95 c7 ff ff 49 8b 84 24 d8 01 00 00 49 
8b 76 78 31 d2 49

[Kernel-packages] [Bug 1599681] Re: ceph-osd process hung and blocked ps listings

[Expired for ceph (Ubuntu) because there has been no activity for 60
days.]

** Changed in: ceph (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  ceph-osd process hung and blocked ps listings

Status in ceph package in Ubuntu:
  Expired
Status in linux package in Ubuntu:
  Expired

Bug description:
  We ran into a situation over the past couple of days where we had 2
  different ceph-osd nodes crash in such a way that they caused ps
  listing to hang when enumerating the process.  Both had a call trace
  associated with them:

  Node 1:
  Jul  4 07:46:15 provider-cs-03 kernel: [4188396.493011] ceph-osdD 
882029a67b90 0  5312  1 0x0004
  Jul  4 07:46:15 provider-cs-03 kernel: [4188396.590564]  882029a67b90 
881037cb8000 8820284f3700 882029a68000
  Jul  4 07:46:16 provider-cs-03 kernel: [4188396.688603]  88203296e5a8 
88203296e5c0 0015 8820284f3700
  Jul  4 07:46:16 provider-cs-03 kernel: [4188396.789329]  882029a67ba8 
817ec495 8820284f3700 882029a67bf8
  Jul  4 07:46:16 provider-cs-03 kernel: [4188396.891376] Call Trace:
  Jul  4 07:46:16 provider-cs-03 kernel: [4188396.939271]  [] 
schedule+0x35/0x80
  Jul  4 07:46:16 provider-cs-03 kernel: [4188396.989957]  [] 
rwsem_down_read_failed+0xea/0x120
  Jul  4 07:46:16 provider-cs-03 kernel: [4188397.041502]  [] 
call_rwsem_down_read_failed+0x14/0x30
  Jul  4 07:46:16 provider-cs-03 kernel: [4188397.092616]  [] 
? __clear_user+0x25/0x50
  Jul  4 07:46:16 provider-cs-03 kernel: [4188397.141510]  [] 
? __clear_user+0x25/0x50
  Jul  4 07:46:16 provider-cs-03 kernel: [4188397.189877]  [] 
? down_read+0x20/0x30
  Jul  4 07:46:16 provider-cs-03 kernel: [4188397.237513]  [] 
__do_page_fault+0x398/0x430
  Jul  4 07:46:16 provider-cs-03 kernel: [4188397.285588]  [] 
do_page_fault+0x22/0x30
  Jul  4 07:46:16 provider-cs-03 kernel: [4188397.332936]  [] 
page_fault+0x28/0x30
  Jul  4 07:46:16 provider-cs-03 kernel: [4188397.379495]  [] 
? __clear_user+0x25/0x50
  Jul  4 07:46:16 provider-cs-03 kernel: [4188397.426400]  [] 
copy_fpstate_to_sigframe+0x118/0x1d0
  Jul  4 07:46:16 provider-cs-03 kernel: [4188397.474904]  [] 
get_sigframe.isra.7.constprop.9+0x12d/0x150
  Jul  4 07:46:16 provider-cs-03 kernel: [4188397.563204]  [] 
do_signal+0x1e8/0x6d0
  Jul  4 07:46:16 provider-cs-03 kernel: [4188397.609783]  [] 
? __sys_sendmsg+0x42/0x80
  Jul  4 07:46:16 provider-cs-03 kernel: [4188397.656633]  [] 
? handle_mm_fault+0x250/0x540
  Jul  4 07:46:16 provider-cs-03 kernel: [4188397.703785]  [] 
exit_to_usermode_loop+0x59/0xa2
  Jul  4 07:46:17 provider-cs-03 kernel: [4188397.751367]  [] 
syscall_return_slowpath+0x4e/0x60
  Jul  4 07:46:17 provider-cs-03 kernel: [4188397.799369]  [] 
int_ret_from_sys_call+0x25/0x8f

  Node 2:
  [733869.727139] CPU: 17 PID: 1735127 Comm: ceph-osd Not tainted 
4.4.0-15-generic #31-Ubuntu
  [733869.796954] Hardware name: Dell Inc. PowerEdge R730/0H21J3, BIOS 1.3.6 
06/03/2015
  [733869.927182] task: 881841dc6e00 ti: 8810cc0a task.ti: 
8810cc0a
  [733870.059139] RIP: 0010:[]  [] 
task_numa_find_cpu+0x2cd/0x710
  [733870.192753] RSP: :8810cc0a3bd8  EFLAGS: 00010257
  [733870.260298] RAX:  RBX: 8810cc0a3c78 RCX: 
0012
  [733870.389322] RDX:  RSI:  RDI: 
8810210a0e00
  [733870.517883] RBP: 8810cc0a3c40 R08: 0006 R09: 
013e
  [733870.646335] R10: 03b4 R11: 001f R12: 
881018118000
  [733870.774514] R13: 0006 R14: 8810210a0e00 R15: 
0379
  [733870.902262] FS:  7fdcfab03700() GS:88203e60() 
knlGS:
  [733871.031347] CS:  0010 DS:  ES:  CR0: 80050033
  [733871.097820] CR2: 7fdcfab02c20 CR3: 001029204000 CR4: 
001406e0
  [733871.223381] Stack:
  [733871.282453]  8810cc0a3c40 811f04ce 88102f6e9680 
0012
  [733871.404947]  0077 008f 00016d40 
0006
  [733871.527250]  881841dc6e00 8810cc0a3c78 01ac 
01b8
  [733871.649648] Call Trace:
  [733871.707884]  [] ? migrate_page_copy+0x21e/0x530
  [733871.770946]  [] task_numa_migrate+0x43e/0x9b0
  [733871.832808]  [] ? page_add_anon_rmap+0x10/0x20
  [733871.893897]  [] numa_migrate_preferred+0x79/0x80
  [733871.954283]  [] task_numa_fault+0x7f4/0xd40
  [733872.013128]  [] handle_mm_fault+0xbc0/0x1820
  [733872.071309]  [] ? do_futex+0x120/0x500
  [733872.128149]  [] ? __fget_light+0x25/0x60
  [733872.184044]  [] __do_page_fault+0x197/0x400
  [733872.239300]  [] do_page_fault+0x22/0x30
  [733872.293001]  [] page_fault+0x28/0x30
  [733872.345187] Code: d0 4c 89 f7 e8 95 c7 ff ff 49 8b 84 24 d8 01 00 00 49 
8b 76 78 31 d2 49 0f

[Kernel-packages] [Bug 1654142] Re: package linux-image-4.4.0-36-generic 4.4.0-36.55 failed to install/upgrade: package linux-image-4.4.0-36-generic is not ready for configuration cannot configure (cu

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package linux-image-4.4.0-36-generic 4.4.0-36.55 failed to
  install/upgrade: package linux-image-4.4.0-36-generic is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in linux package in Ubuntu:
  Expired

Bug description:
  as below

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-36-generic 4.4.0-36.55
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic i686
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hariharanpv   1970 F pulseaudio
  Date: Thu Jan  5 10:30:11 2017
  DpkgHistoryLog:
   Start-Date: 2017-01-05  10:27:35
   Requested-By: hariharanpv (1000)
   Install: ubuntu-minimal:i386 (1.361), vim-tiny:i386 (2:7.4.1689-3ubuntu1.2, 
automatic)
   Upgrade: libnss3-nssdb:i386 (2:3.23-0ubuntu0.16.04.1, 
2:3.26.2-0ubuntu0.16.04.2), grub-common:i386 (2.02~beta2-36ubuntu3.2, 
2.02~beta2-36ubuntu3.6), grub2-common:i386 (2.02~beta2-36ubuntu3.2, 
2.02~beta2-36ubuntu3.6), grub-pc:i386 (2.02~beta2-36ubuntu3.2, 
2.02~beta2-36ubuntu3.6), grub-pc-bin:i386 (2.02~beta2-36ubuntu3.2, 
2.02~beta2-36ubuntu3.6), unattended-upgrades:i386 (0.90ubuntu0.2, 
0.90ubuntu0.3), libnss3:i386 (2:3.23-0ubuntu0.16.04.1, 
2:3.26.2-0ubuntu0.16.04.2)
  DuplicateSignature:
   package:linux-image-4.4.0-36-generic:4.4.0-36.55
   Processing triggers for ureadahead (0.100.0-19) ...
   ureadahead will be reprofiled on next reboot
   dpkg: error processing package linux-image-4.4.0-36-generic (--configure):
package linux-image-4.4.0-36-generic is not ready for configuration
  ErrorMessage: package linux-image-4.4.0-36-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
  HibernationDevice: RESUME=UUID=3e4794e3-fc53-48c0-8613-1430184209b2
  InstallationDate: Installed on 2016-07-19 (169 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
   
   enx00a0c60788e0  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. G31M-S2L
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=b3754a70-f9b9-48e0-8254-b49e4715bf18 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.6
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.4.0-36-generic 4.4.0-36.55 failed to 
install/upgrade: package linux-image-4.4.0-36-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/03/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F8b DL
  dmi.board.name: G31M-S2L
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF8bDL:bd11/03/2008:svnGigabyteTechnologyCo.,Ltd.:pnG31M-S2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG31M-S2L:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G31M-S2L
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

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

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1663637

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

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

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

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

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

Title:
  Image flickering on eDP screen since 4.4.0-59 kernel upgrade

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Image on my HiDPI 4K eDP screen (HP zbook 15) is flickering since I
  upgraded my kernel to 4.4.0-59.

  With 4.4.0-53 kernel, everything is ok.

  I have try :
- 4.4.0-59
- 4.4.0-62
- 4.8.0-36 (from linux-generic-hwe-16.04)

  All of us make my eDP screen flickering when it was alone. Because the
  amazing things is here : when my laptop is docked and get two other
  screen (one fullHD and one 2K), everything get back to normal. Even on
  my eDP 4K screen !

  I don't know how to know where the problem come from. Kernel ?
  radeon.ko ? xorg-video-radeon ? Gnome Shell ? Is amdgpu.ko usable ?
  How to test it ? ... need help.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-generic-hwe-16.04 4.8.0.36.8
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Feb 10 16:09:52 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-meta-hwe
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (294 days ago)

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

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

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

This change was made by a bot.

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

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

Title:
  Laptop wakes up from sleep mode after seconds

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Laptop wakes up from sleep mode after seconds

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-39-generic 4.8.0-39.42
  ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
  Uname: Linux 4.8.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode icp zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   BEN.PID ZUGR.  BEFEHL
   /dev/snd/controlC0:  richter   18063 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Mar  8 04:57:54 2017
  HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a
  InstallationDate: Installed on 2015-12-12 (451 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20221
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-39-generic 
root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro 
rootflags=subvol=ubuntu-main-root
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-39-generic N/A
   linux-backports-modules-4.8.0-39-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-17 (141 days ago)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 71CN51WW(V1.21)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z500 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
  dmi.product.name: 20221
  dmi.product.version: Lenovo IdeaPad Z500 Touch
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1670930] [NEW] Laptop wakes up from sleep mode after seconds

2017-03-07 Thread Karl-Philipp Richter

Public bug reported:

Laptop wakes up from sleep mode after seconds

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-39-generic 4.8.0-39.42
ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
Uname: Linux 4.8.0-39-generic x86_64
NonfreeKernelModules: zfs zunicode icp zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 BEN.PID ZUGR.  BEFEHL
 /dev/snd/controlC0:  richter   18063 F pulseaudio
CurrentDesktop: Unity
Date: Wed Mar  8 04:57:54 2017
HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a
InstallationDate: Installed on 2015-12-12 (451 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: LENOVO 20221
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-39-generic 
root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro 
rootflags=subvol=ubuntu-main-root
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-39-generic N/A
 linux-backports-modules-4.8.0-39-generic  N/A
 linux-firmware1.161.1
SourcePackage: linux
UpgradeStatus: Upgraded to yakkety on 2016-10-17 (141 days ago)
dmi.bios.date: 07/12/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 71CN51WW(V1.21)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: INVALID
dmi.board.vendor: LENOVO
dmi.board.version: 3193WIN8 STD MLT
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad Z500 Touch
dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
dmi.product.name: 20221
dmi.product.version: Lenovo IdeaPad Z500 Touch
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug yakkety

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

Title:
  Laptop wakes up from sleep mode after seconds

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Laptop wakes up from sleep mode after seconds

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-39-generic 4.8.0-39.42
  ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
  Uname: Linux 4.8.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode icp zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   BEN.PID ZUGR.  BEFEHL
   /dev/snd/controlC0:  richter   18063 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Mar  8 04:57:54 2017
  HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a
  InstallationDate: Installed on 2015-12-12 (451 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20221
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-39-generic 
root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro 
rootflags=subvol=ubuntu-main-root
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-39-generic N/A
   linux-backports-modules-4.8.0-39-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-17 (141 days ago)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 71CN51WW(V1.21)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z500 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
  dmi.product.name: 20221
  dmi.product.version: Lenovo IdeaPad Z500 Touch
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1666316] Re: Windows become unclickable (transparent for mouse clicks) after resume from sleep

2017-03-07 Thread Alberto Salvia Novella

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

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

Title:
  Windows become unclickable (transparent for mouse clicks) after resume
  from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Windows become unclickable (transparent for mouse clicks) after resume from 
the sleep mode. Both system and JVM windows can't capture mouse clicks 
including clicks on the title bar after resuming from the sleep mode. Unity 
panel works fine, new applications can be started and they do not have this 
issue, i.e. new windows are fully functional.
  This bug appears seldom and is hardly reproducible (like #1651520).

  This bug is a minor security vulnerability because clicking on the
  foreground non-clickable window, a user performs actual click on the
  background window (or desktop shortcuts) and anything can be
  initiated/started that the user has right, but was not intended to do.

  
  Notes:
  This bug might relate to
  #1651520 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651520) 
except in 4.4.0-62, except 1) the windows' content now is not damaged and 
visually indistinguishable from the fully functional windows and 2) windows in 
#1651520 had destroyed content, but were clickable.
  Neither this bug nor #1651520 appear in the 4.9.3 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-62-generic 4.4.0-62.83
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lav3136 F pulseaudio
   /dev/snd/controlC0:  lav3136 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Feb 20 21:14:20 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-25 (849 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 20A8S28400
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=daa4b3a5-47b3-4c16-a1de-2dde0c540c4a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-62-generic N/A
   linux-backports-modules-4.4.0-62-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-09-11 (162 days ago)
  dmi.bios.date: 06/06/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GRET39WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20A8S28400
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGRET39WW(1.16):bd06/06/2014:svnLENOVO:pn20A8S28400:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A8S28400:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20A8S28400
  dmi.product.version: ThinkPad X1 Carbon 2nd
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd reports "Not enough handles to register service" at start

2017-03-07 Thread Alberto Salvia Novella

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

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

Title:
  15:10 and 16.04: bluetoothd reports "Not enough handles to register
  service" at start

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On 15:10 after the bluetooth service has been stopped and restarted it
  is not possible to scan or connect to devices:

  $ sudo systemctl start bluetooth
  $ journalctl --unit=bluetooth | tail -n 19 | awk '{$1="";$2="";$4="";print 
$0}'
23:31:53  systemd[1]: Starting Bluetooth service...
23:31:53  bluetoothd[16647]: Bluetooth daemon 5.33
23:31:53  systemd[1]: Started Bluetooth service.
23:31:53  bluetoothd[16647]: Starting SDP server
23:31:53  bluetoothd[16647]: Bluetooth management interface 1.9 initialized
23:31:53  bluetoothd[16647]: Failed to obtain handles for "Service Changed" 
characteristic
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Error adding Link Loss service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Current Time Service could not be registered
23:31:53  bluetoothd[16647]: gatt-time-server: Input/output error (5)
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Sap driver initialization failed.
23:31:53  bluetoothd[16647]: sap-server: Operation not permitted (1)
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSource
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSink

  And

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.NotReady

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

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

[Kernel-packages] [Bug 1663637] Re: Image flickering on eDP screen since 4.4.0-59 kernel upgrade

2017-03-07 Thread Steve Beattie

** Package changed: linux-meta-hwe (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/1663637

Title:
  Image flickering on eDP screen since 4.4.0-59 kernel upgrade

Status in linux package in Ubuntu:
  New

Bug description:
  Image on my HiDPI 4K eDP screen (HP zbook 15) is flickering since I
  upgraded my kernel to 4.4.0-59.

  With 4.4.0-53 kernel, everything is ok.

  I have try :
- 4.4.0-59
- 4.4.0-62
- 4.8.0-36 (from linux-generic-hwe-16.04)

  All of us make my eDP screen flickering when it was alone. Because the
  amazing things is here : when my laptop is docked and get two other
  screen (one fullHD and one 2K), everything get back to normal. Even on
  my eDP 4K screen !

  I don't know how to know where the problem come from. Kernel ?
  radeon.ko ? xorg-video-radeon ? Gnome Shell ? Is amdgpu.ko usable ?
  How to test it ? ... need help.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-generic-hwe-16.04 4.8.0.36.8
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Feb 10 16:09:52 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-meta-hwe
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (294 days ago)

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

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

[Kernel-packages] [Bug 1663637] [NEW] Image flickering on eDP screen since 4.4.0-59 kernel upgrade

You have been subscribed to a public bug:

Image on my HiDPI 4K eDP screen (HP zbook 15) is flickering since I
upgraded my kernel to 4.4.0-59.

With 4.4.0-53 kernel, everything is ok.

I have try :
  - 4.4.0-59
  - 4.4.0-62
  - 4.8.0-36 (from linux-generic-hwe-16.04)

All of us make my eDP screen flickering when it was alone. Because the
amazing things is here : when my laptop is docked and get two other
screen (one fullHD and one 2K), everything get back to normal. Even on
my eDP 4K screen !

I don't know how to know where the problem come from. Kernel ? radeon.ko
? xorg-video-radeon ? Gnome Shell ? Is amdgpu.ko usable ? How to test it
? ... need help.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-generic-hwe-16.04 4.8.0.36.8
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Feb 10 16:09:52 2017
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-meta-hwe
UpgradeStatus: Upgraded to xenial on 2016-04-21 (294 days ago)

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


** Tags: amd64 apport-bug xenial
-- 
Image flickering on eDP screen since 4.4.0-59 kernel upgrade
https://bugs.launchpad.net/bugs/1663637
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 1664663] Re: [Hyper-V] kvp daemon start failure on Zesty

2017-03-07 Thread Stuart Miller

I have also seen this in 16.04.2, with the same symptoms as the OP.

Restarting the service (sudo systemctl restart hv-kvp-daemon.service)
seems to have fixed this problem across reboots.

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

Title:
  [Hyper-V] kvp daemon start failure on Zesty

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

Bug description:
  Hello,

  On Ubuntu Server 17.04 daily from Febr 14th we see that the KVP daemon
  although it is enabled in systemd, it fails to start at system boot.

  This is shown by error: "KVP: read failed; error:9 Bad file
  descriptor"

  I then manually ran the kvp binary, it returned the KVP data, and it's also 
automatically loading at boot. However, this is of course not the normal 
behavior.
  17.04 daily from Febr 14th is the first build we covered, so I cannot say if 
this is a regression introduced only at some point in 17.04 dailies.

  In syslog these are the only messages for KVP:
  Feb 14 08:01:22 ubuntu systemd[1]: Started Hyper-V KVP Protocol Daemon.
  Feb 14 08:01:22 ubuntu KVP: KVP starting; pid is:1837
  Feb 14 08:01:22 ubuntu KVP: KVP LIC Version: 3.1
  Feb 14 08:02:31 ubuntu KVP: read failed; error:9 Bad file descriptor

  
  systemd status:
  root@ubuntu:~# systemctl status hv-kvp-daemon.service
  ● hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon
 Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Tue 2017-02-14 08:02:31 PST; 1min 
41s ago
   Main PID: 1837 (code=exited, status=1/FAILURE)
CPU: 4ms

  Feb 14 08:01:22 ubuntu systemd[1]: Started Hyper-V KVP Protocol Daemon.
  Feb 14 08:01:22 ubuntu KVP[1837]: KVP starting; pid is:1837
  Feb 14 08:01:22 ubuntu KVP[1837]: KVP LIC Version: 3.1
  Feb 14 08:02:31 ubuntu systemd[1]: hv-kvp-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Feb 14 08:02:31 ubuntu systemd[1]: hv-kvp-daemon.service: Unit entered failed 
state.
  Feb 14 08:02:31 ubuntu systemd[1]: hv-kvp-daemon.service: Failed with result 
'exit-code'.

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

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

[Kernel-packages] [Bug 1661695] Re: screen flickering raedon

2017-03-07 Thread louiedog

@jsalisbur I found the exact commit that fixes this issue for SI cards

in case anyone else comes across this:

https://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git
/mainline-crack/commit/?id=29a73d906bd386839015602c4bd35ef2e3531abc

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

Title:
  screen flickering raedon

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  4.4.0-53 WORKS FINE

  4.4.0-62 DOES NOT WORK (screen flickers)

  It seems there is a problem with powersafe:

  With auto:
  echo auto > /sys/class/drm/card0/device/power_dpm_force_performance_level

  you will see heavy screen flickering on higher display resolutions

  With low or high:
  echo low > /sys/class/drm/card0/device/power_dpm_force_performance_level or
  echo high > /sys/class/drm/card0/device/power_dpm_force_performance_level

  there is no screen flickering

  And having performance level set to HIGH at all times is not a
  workaround because it wears out the card. :(

  details:

  Linux CINNAMON 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

  ```
  Vendor: X.Org (0x1002)
  Device: AMD PITCAIRN (DRM 2.43.0 / 4.4.0-62-generic, LLVM 5.0.0) (0x6811)
  Version: 17.1.0
  Accelerated: yes
  Video memory: 2048MB
  Unified memory: no
  Preferred profile: core (0x1)
  Max core profile version: 4.2
  Max compat profile version: 3.0
  Max GLES1 profile version: 1.1
  Max GLES[23] profile version: 3.0
  OpenGL vendor string: X.Org
  OpenGL renderer string: Gallium 0.4 on AMD PITCAIRN (DRM 2.43.0 / 
4.4.0-62-generic, LLVM 5.0.0)
  OpenGL core profile version string: 4.2 (Core Profile) Mesa 17.1.0-devel - 
padoka PPA
  OpenGL core profile shading language version string: 4.20
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile

  ```
  ---
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  atomi  3734 F pulseaudio
   /dev/snd/controlC0:  atomi  3734 F pulseaudio
   /dev/snd/controlC1:  atomi  3734 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.1
  HibernationDevice: RESUME=UUID=30254b0c-14d7-4c0e-9168-a8d492fa027b
  InstallationDate: Installed on 2016-12-27 (37 days ago)
  InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=41cc7dce-52e8-4b29-9347-60afc0a7d0ed ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-53-generic N/A
   linux-backports-modules-4.4.0-53-generic  N/A
   linux-firmware1.157.6
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  Tags:  serena
  Uname: Linux 4.4.0-53-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/23/2013
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FA
  dmi.board.name: GA-78LMT-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1669620] Re: Reboot when resume from suspend

2017-03-07 Thread tim474

I tested with 4.10.0, and I have the same problem.

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

Title:
Reboot when resume from suspend

Status in linux package in Ubuntu:
Incomplete

Bug description:
When I resume my computer from suspend2ram, after about 2 seconds it
shutdowns and after about 3 seconds swithces on, and system starts to
boot from GRUB as it was poweroff.

But if I resume my computer right away after it was suspended, it
resumes properly. I occur this problem if some amount of time passed
between suspend and resume.

And I didn't reproduce this problem when lightdm was stopped (but the
screen is black after resume, but I can login via SSH). But with
launched X Server the problem occurs both with nouveau and Nvidia
proprietary driver.

There is not this problem on Ubuntu 14.04 (it is installed on this
computer too but without madm and root partition encryption).

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-generic 4.4.0.64.68
ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
Uname: Linux 4.4.0-64-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: tim2077 F pulseaudio
CurrentDesktop: XFCE
Date: Fri Mar 3 02:43:35 2017
EcryptfsInUse: Yes
IwConfig:
tun0 no wireless extensions.

lono wireless extensions.

enp4s0no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. EP43-DS3L
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic
root=UUID=77b30501-4b3e-4223-8e1c-ee51e9f214d7 ro
RelatedPackageVersions:
linux-restricted-modules-4.4.0-64-generic N/A
linux-backports-modules-4.4.0-64-generic N/A
linux-firmware1.157.8
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/08/2008
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F5
dmi.board.name: EP43-DS3L
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias:
dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd07/08/2008:svnGigabyteTechnologyCo.,Ltd.:pnEP43-DS3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP43-DS3L:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: EP43-DS3L
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1670624] Re: Official 16.04 HWE 4.8 kernels do not boot (4.4 was booting)

2017-03-07 Thread Evren Yurtesen

When I was installing the kernel it complained about possibly missing firmware 
files for amdgpu.
Then it failed first but I blacklisted amdgpu module and it booted.

Then I tried to install amdgpu-pro but that couldn't compile the module
since it doesnt support 4.11. But I think it may have installed some
firmware files and I could load the amdgpu module after boot.

But, then I decided to try to disable amdgpu for 4.8 (worst idea ever!).
Apparently everytime I boot 4.8, it destroys something from the hard
drive. It somehow managed to loose /var/lib/dpkg first but after few
reboots, completely lost the whole partition and even grub didnt start.
I am never putting 4.8 again!

So, for now, I can't really test anything anymore since ubuntu self-
destructed itself. Luckily windows and freebsd are still working. Maybe
I wait for Zesty before re-installing.

About 4.11 kernel:

I can tell that at last the basic keyboard was working in Linux/Ubuntu.
Because with 4.4 it was skipping keypresses.

The touchpad was much better, but still somewhat strange. Things like
double tap and two-finger scrolling didn't work. At least mouse cursor
was not jumping around randomly from time to time.

The WIFI didn't work, I had to install rtlwifi_new driver from github.

The hard drive was super slow, maybe even slower than before. I saw
0.6mbyte/s performance when I ran sysbench.

The CPU fan was going full speed and laptop got hot. (least of my
worries but it happened...)

I would like to help more but I don't know what I can do at this stage.
I am not even sure why amdgpu module was loaded, because the APU has sea
islands gpu, I thought this was disabled by default? Did this change in
4.11?

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

Title:
  Official 16.04 HWE 4.8 kernels do not boot (4.4 was booting)

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

Bug description:
  The machine is the same machine as in this bug report:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616830

  In mid 2016 I tested 4.8 kernels on that machine and they did not boot. (and 
same errors apply to current situation)
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616830/comments/5

  Also Ubuntu 16.10 and newer releases do not boot anymore (as reported by a 
user, I think it is due to kernel). He also reports the same errors with the 
4.8 kernel.
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616830/comments/15

  It seems that official release kernels still have the same problems
  and nothing was fixed.

  There seem to be many problems with Ubuntu on Carrizo, black screens,
  random freezes. I myself experienced, keyboard problems (keyboard
  sometimes do not register keystrokes), touchpad works strangely,
  random freeze with caps-lock blinking, low disk performance (max
  1.3mbytes/sec) and much more.

  I do not understand how hardware support can be getting worse and
  worse, but that seems to be the case.

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

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

[Kernel-packages] [Bug 1670696] Re: Typo in error msg when no crashkernel memory reservation is set

** Description changed:

  [Impact]
  
-  * There is a typo in ERRMSG of function show_mem_usage affecting Xenial
- and Zesty AND Debian.
+  * There is a typo in ERRMSG of function show_mem_usage affecting
+ Xenial/Zesty, Debian and makedumpfile upstream.
  
  This should be :
  "show_mem_usage: No memory is reserved for crashkernel!"
  
  instead of :
  "show_mem_usage: No memory is reserved for crashkenrel!"
  
- The typo is located here in src code for Xenial and Zesty (devel
- release) AND Debian:
+ The typo is located here in src code :
+ 
  
  # filename : makedumpfile.c
- 10447 int show_mem_usage(void)
- 10448 {
- 10449 uint64_t vmcoreinfo_addr, vmcoreinfo_len;
- 10450 struct cycle cycle = {0};
- 10451
- 10452 if (!is_crashkernel_mem_reserved()) {
- 10453 ERRMSG("No memory is reserved for crashkenrel!\n");
- 10454 return FALSE;
- 10455 }
+ -
+ int show_mem_usage(void)
+  {
+  uint64_t vmcoreinfo_addr, vmcoreinfo_len;
+  struct cycle cycle = {0};
+ 
+  if (!is_crashkernel_mem_reserved()) {
+  ERRMSG("No memory is reserved for crashkenrel!\n");
+  return FALSE;
+  }
+ -
  
  [Test Case]
  
   * Take a system with no crashkernel memory reservation set
   * run command : makedumpfile --mem-usage /proc/kcore
  
   * Error message :
  show_mem_usage: No memory is reserved for crashkenrel!
  
  [Regression Potential]
  
   * No regression, it is a trivial change with no behavioural change.
  
  [Other Info]
  
  * Upstream:
  Patch has been submitted upstream (ML :ke...@lists.infradead.org)
  
  * Debian bug :
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857051

** Description changed:

  [Impact]
  
   * There is a typo in ERRMSG of function show_mem_usage affecting
  Xenial/Zesty, Debian and makedumpfile upstream.
  
  This should be :
  "show_mem_usage: No memory is reserved for crashkernel!"
  
  instead of :
  "show_mem_usage: No memory is reserved for crashkenrel!"
  
  The typo is located here in src code :
  
- 
  # filename : makedumpfile.c
  -
- int show_mem_usage(void)
-  {
-  uint64_t vmcoreinfo_addr, vmcoreinfo_len;
-  struct cycle cycle = {0};
+ int show_mem_usage(void)
+  {
+  uint64_t vmcoreinfo_addr, vmcoreinfo_len;
+  struct cycle cycle = {0};
  
-  if (!is_crashkernel_mem_reserved()) {
-  ERRMSG("No memory is reserved for crashkenrel!\n");
-  return FALSE;
-  }
+  if (!is_crashkernel_mem_reserved()) {
+    ==>  ERRMSG("No memory is reserved for crashkenrel!\n");
+  return FALSE;
+  }
  -
  
  [Test Case]
  
   * Take a system with no crashkernel memory reservation set
   * run command : makedumpfile --mem-usage /proc/kcore
  
   * Error message :
  show_mem_usage: No memory is reserved for crashkenrel!
  
  [Regression Potential]
  
   * No regression, it is a trivial change with no behavioural change.
  
  [Other Info]
  
  * Upstream:
  Patch has been submitted upstream (ML :ke...@lists.infradead.org)
  
  * Debian bug :
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857051

** Changed in: makedumpfile (Ubuntu Xenial)
   Importance: Low => Medium

** Changed in: makedumpfile (Ubuntu Zesty)
   Importance: Low => Medium

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

Title:
  Typo in error msg when no crashkernel memory reservation is set

Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Xenial:
  In Progress
Status in makedumpfile source package in Zesty:
  In Progress

Bug description:
  [Impact]

   * There is a typo in ERRMSG of function show_mem_usage affecting
  Xenial/Zesty, Debian and makedumpfile upstream.

  This should be :
  "show_mem_usage: No memory is reserved for crashkernel!"

  instead of :
  "show_mem_usage: No memory is reserved for crashkenrel!"

  The typo is located here in src code :

  # filename : makedumpfile.c
  -
  int show_mem_usage(void)
   {
   uint64_t vmcoreinfo_addr, vmcoreinfo_len;
   struct cycle cycle = {0};

   if (!is_crashkernel_mem_reserved()) {
     ==>  ERRMSG("No memory is reserved for crashkenrel!\n");
   return FALSE;
   }
  -

  [Test Case]

   * Take a system with no crashkernel memory reservation set
   * run command : makedumpfile --mem-usage /proc/kcore

   * Error message :
  show_mem_usage: No memory is reserved for crashkenrel!

  [Regression Potential]

   * No regression, it is a trivial change with no behavioural change.

  [Other Info]

  * Upstream:
  Patch has been submitted upstream (ML :ke...@lists.infradead.org)

  * Debian bug :

[Kernel-packages] [Bug 1670800] Re: Power9 kernel: add virtualization patches

2017-03-07 Thread Breno Leitão

Thanks Tim. We would like to target all these POWER9 bugs to yakkety
also. Do you think it is feasible?

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

Title:
  Power9 kernel: add virtualization patches

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

Bug description:
  Dear Canonical,

  Please add the following patches for POWER9:

  From powerpc/next tree:

cc3d2940133d24000e2866b21e03ce32adfead0a - powerpc/64: Enable use of
  radix MMU under hypervisor on POWER9

6ae3f8ad2017079292cb49c8959b527bcbcbefed - powerpc: Add POWER9
  architected mode to cputable

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

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

[Kernel-packages] [Bug 1670634] Re: blk-mq: possible deadlock on CPU hot(un)plug

Douglas - The patch referred to in LP #1662673 ("percpu-refcount: fix
reference leak during percpu-atomic transition") is in
Ubuntu-4.4.0-65.86 which has yet to be 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/1670634

Title:
  blk-mq: possible deadlock on CPU hot(un)plug

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Carsten Jacobi  - 2017-03-07 03:35:31 ==
  I'm evaluating Ubuntu-Xenial on z for development purposes, the test system 
is installed in an LPAR with one FCP-LUN which is accessable by 4 pathes (all 
pathes are configured).
  The system hangs regularly when I make packages with "pdebuild" using the 
pbuilder packaging suit.
  The local Linux development team helped me out with a pre-analysis that I can 
post here (thanks a lot for that):

  With the default settings and under a certain workload,
  blk_mq seems to get into a presumed "deadlock".
  Possibly this happens on CPU hot(un)plug.

  After the I/O stalled, a dump was pulled manually.
  The following information is from the crash dump pre-analysis.

  $ zgetdump -i dump.0
  General dump info:
Dump format: elf
Version: 1
UTS node name..: mclint
UTS kernel release.: 4.4.0-65-generic
UTS kernel version.: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
System arch: s390x (64 bit)
CPU count (online).: 2
Dump memory range..: 8192 MB
  Memory map:
 - 0001b831afff (7043 MB)
0001b831b000 - 0001 (1149 MB)

  Things look similarly with HWE kernel ubuntu16.04-4.8.0-34.36~16.04.1.

KERNEL: vmlinux.full
  DUMPFILE: dump.0
  CPUS: 2
  DATE: Fri Mar  3 14:31:07 2017
UPTIME: 02:11:20
  LOAD AVERAGE: 13.00, 12.92, 11.37
 TASKS: 411
  NODENAME: mclint
   RELEASE: 4.4.0-65-generic
   VERSION: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
   MACHINE: s390x  (unknown Mhz)
MEMORY: 7.8 GB
 PANIC: ""
   PID: 0
   COMMAND: "swapper/0"
  TASK: bad528  (1 of 2)  [THREAD_INFO: b78000]
   CPU: 0
 STATE: TASK_RUNNING (ACTIVE)
  INFO: no panic task found

  crash> dev -d
  MAJOR GENDISKNAME   REQUEST_QUEUE  TOTAL ASYNC  SYNC   DRV
  ...
  8 1e1d6d800  sda1e1d51210  0 23151 4294944145 
N/A(MQ)
  8 1e4e06800  sdc2081b180 23148 4294944148 
N/A(MQ)
  8 1f07800sdb20c75680 23195 4294944101 
N/A(MQ)
  8 1e4e06000  sdd1e4e31210  0 23099 4294944197 
N/A(MQ)
252 1e1d6c800  dm-0   1e1d51b18  9 1 8 
N/A(MQ)
  ...

  So both dm-mpath and sd have requests pending in their block multiqueue.
  The large numbers of sd look strange and seem to be the unsigned formatting 
of the values shown for async multiplied by -1.

  [0.798256] Linux version 4.4.0-65-generic (buildd@z13-011) (gcc version 
5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #86-Ubuntu SMP Thu Feb 23 
17:54:37 UTC 2017 (Ubuntu 4.4.0-65.86-generic 4.4.49)
  [0.798262] setup: Linux is running natively in 64-bit mode
  [0.798290] setup: Max memory size: 8192MB
  [0.798298] setup: Reserving 196MB of memory at 7996MB for crashkernel 
(System RAM: 7996MB)

  [0.836923] Kernel command line: root=/dev/mapper/mclint_vg-root
  rootflags=subvol=@ crashkernel=196M BOOT_IMAGE=0

  [ 5281.179428] INFO: task xfsaild/dm-11:1604 blocked for more than 120 
seconds.
  [ 5281.179437]   Not tainted 4.4.0-65-generic #86-Ubuntu
  [ 5281.179438] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 5281.179440] xfsaild/dm-11   D 007bcf52 0  1604  2 
0x
  [ 5281.179444]0001e931c230 001a6964 0001e6f9b958 
0001e6f9b9d8
0001e15795f0 0001e6f9b988 00ce8c00 
0001ea805c70
0001ea805c00 00ba5ed0 0001e931c1d0 
0001e1579b20
0001ea805c00 0001e15795f0 0001ea805c00 

007d3978 007bc9f8 0001e6f9b9d8 
0001e6f9ba40
  [ 5281.179454] Call Trace:
  [ 5281.179461] ([<007bc9f8>] __schedule+0x300/0x810)
  [ 5281.179462]  [<007bcf52>] schedule+0x4a/0xb0
  [ 5281.179465]  [<007c02aa>] schedule_timeout+0x232/0x2a8
  [ 5281.179466]  [<007bde50>] wait_for_common+0x110/0x1c8
  [ 5281.179472]  [<0017b602>] flush_work+0x42/0x58
  [ 5281.179564]  [<03ff805e14ba>] xlog_cil_force_lsn+0x7a/0x238 [xfs]
  [ 5281.179589]  [<03ff805dee82>] _xfs_log_force+0x9a/0x2e8 [xfs]
  [ 5281.179615]  [<03ff805df114>] xfs_log_force+0x44/0x100

[Kernel-packages] [Bug 1670800] Re: Power9 kernel: add virtualization patches

commit cc3d2940133d24000e2866b21e03ce32adfead0a was applied as part of
bug http://bugs.launchpad.net/bugs/1670315

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

** Changed in: linux (Ubuntu Zesty)
   Status: New => Fix Committed

** Changed in: linux (Ubuntu Zesty)
 Assignee: Taco Screen team (taco-screen-team) => 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/1670800

Title:
  Power9 kernel: add virtualization patches

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

Bug description:
  Dear Canonical,

  Please add the following patches for POWER9:

  From powerpc/next tree:

cc3d2940133d24000e2866b21e03ce32adfead0a - powerpc/64: Enable use of
  radix MMU under hypervisor on POWER9

6ae3f8ad2017079292cb49c8959b527bcbcbefed - powerpc: Add POWER9
  architected mode to cputable

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

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

[Kernel-packages] [Bug 1629613] Re: [Dell XPS 13] SynPS/2 Synaptics TouchPad not recognized after upgrade from 14.04 to 16.04

2017-03-07 Thread Alessandro Volpi

After a an apt-get update the touchpad has totally quit working, also
with the previously known working kernel 4.4.0-62-generic.

It is not an hardware issue, since the touchpad works perfectly with
trusty and kernel 3.13 ...

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

Title:
  [Dell XPS 13] SynPS/2 Synaptics TouchPad not recognized after upgrade
  from 14.04 to 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  * Touchpad doesn't work at all (No response from the Touchpad)
  * Tried using external mouse and it works fine
  * Cannot find "SynPS/2 Synaptics TouchPad" in "cat /proc/bus/input/devices"

  
  OS:   Ubuntu 16.04.1 LTS
  kernel version: 4.4.0-38-generic
  Laptop Model:   Dell XPS 13 - 9

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

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

[Kernel-packages] [Bug 1667920] Re: login screen freeze

2017-03-07 Thread Alexandru Chirvasitu

Quick update: upgraded to 4.4.0-66 just now, and it behaves a little
differently; both the standard and the upstart versions consistently
freeze *after* login.

I always get enough time to enter the password and clear the initial
login screen, but then it freezes in seconds.

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

Title:
  login screen freeze

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Running an up-to-date (as of Feb 25 2017) 16.04 / Unity on an old MSI
  U160 netbook.

  After a recent update to kernel 4.4.0-63 I have started getting frozen
  login screens. The touchpad and keyboard are completely dead (before I
  ever get to enter my password), and my only way out is to force
  shutdown.

  I can start GRUB on boot and go for an earlier version instead, but
  everything past 4.4.0-62 freezes in the same fashion (that's what I'm
  currently running as a temporary fix); a newer update to 4.4.0-64 has
  not fixed the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-64-generic 4.4.0-64.85
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chirvasitua   1841 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Feb 25 03:42:57 2017
  HibernationDevice: RESUME=UUID=5e60245a-50f2-4f9c-97b2-d68560e38218
  InstallationDate: Installed on 2015-10-18 (495 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-N051
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=250be7ea-5182-43d2-b638-5c4a933b4942 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-62-generic N/A
   linux-backports-modules-4.4.0-62-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: EN051IMS.100
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-N051
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrEN051IMS.100:bd02/06/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-N051:pvrTobefilledbyO.E.M.:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-N051:rvrTobefilledbyO.E.M.:cvnMICRO-STARINTERNATIONALCO.,LTD:ct9:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-N051
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

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

-- 
Mailing list: https://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 1670800] [NEW] Power9 kernel: add virtualization patches

2017-03-07 Thread Michael Hohnbaum

Leann,

Some more Power9 enablement patches.

 Michael


On 03/07/2017 11:19 AM, Launchpad Bug Tracker wrote:
> bugproxy (bugproxy) has assigned this bug to you for Ubuntu:
>
> Dear Canonical,
>
> Please add the following patches for POWER9:
>
> >From powerpc/next tree:
>
>cc3d2940133d24000e2866b21e03ce32adfead0a - powerpc/64: Enable use of
> radix MMU under hypervisor on POWER9
>
>6ae3f8ad2017079292cb49c8959b527bcbcbefed - powerpc: Add POWER9
> architected mode to cputable
>
> ** Affects: ubuntu
>   Importance: Undecided
>   Assignee: Taco Screen team (taco-screen-team)
>   Status: New
>
>
> ** Tags: architecture-ppc64le bugnameltc-152323 severity-medium 
> targetmilestone-inin1704

-- 
Michael Hohnbaum
OIL Program Manager
Power (ppc64el) Development Project Manager
Canonical, Ltd.

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

Title:
  Power9 kernel: add virtualization patches

Status in linux package in Ubuntu:
  New

Bug description:
  Dear Canonical,

  Please add the following patches for POWER9:

  From powerpc/next tree:

cc3d2940133d24000e2866b21e03ce32adfead0a - powerpc/64: Enable use of
  radix MMU under hypervisor on POWER9

6ae3f8ad2017079292cb49c8959b527bcbcbefed - powerpc: Add POWER9
  architected mode to cputable

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

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

[Kernel-packages] [Bug 1670800] [NEW] Power9 kernel: add virtualization patches

Public bug reported:

Dear Canonical,

Please add the following patches for POWER9:

>From powerpc/next tree:

  cc3d2940133d24000e2866b21e03ce32adfead0a - powerpc/64: Enable use of
radix MMU under hypervisor on POWER9

  6ae3f8ad2017079292cb49c8959b527bcbcbefed - powerpc: Add POWER9
architected mode to cputable

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


** Tags: architecture-ppc64le bugnameltc-152323 severity-medium 
targetmilestone-inin1704

** Tags added: architecture-ppc64le bugnameltc-152323 severity-medium
targetmilestone-inin1704

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

Title:
  Power9 kernel: add virtualization patches

Status in linux package in Ubuntu:
  New

Bug description:
  Dear Canonical,

  Please add the following patches for POWER9:

  From powerpc/next tree:

cc3d2940133d24000e2866b21e03ce32adfead0a - powerpc/64: Enable use of
  radix MMU under hypervisor on POWER9

6ae3f8ad2017079292cb49c8959b527bcbcbefed - powerpc: Add POWER9
  architected mode to cputable

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

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

[Kernel-packages] [Bug 1670800] [NEW] Power9 kernel: add virtualization patches

You have been subscribed to a public bug:

Dear Canonical,

Please add the following patches for POWER9:

>From powerpc/next tree:

  cc3d2940133d24000e2866b21e03ce32adfead0a - powerpc/64: Enable use of
radix MMU under hypervisor on POWER9

  6ae3f8ad2017079292cb49c8959b527bcbcbefed - powerpc: Add POWER9
architected mode to cputable

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


** Tags: architecture-ppc64le bugnameltc-152323 severity-medium 
targetmilestone-inin1704
-- 
Power9 kernel: add virtualization patches
https://bugs.launchpad.net/bugs/1670800
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 1670726] Re: h-prod does not function across cores

https://lists.ubuntu.com/archives/kernel-team/2017-March/082895.html

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

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

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

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

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

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

** Changed in: linux (Ubuntu Zesty)
   Status: Fix Released => 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/1670726

Title:
  h-prod does not function across cores

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  There is a  performance problem issue with h-prod. I can see that
  h-prod calls are only waking hardware threads from a h-cede call when
  the caller is on the same core as the thread being awoken (sibling
  theads).  For cross core prods the target thread remains in h-cede
  until its next decrementer interrupt.  That is causing guest OS some
  significant dispatching delays.

   The fix is now upstream as commit 8464c8842de2 ("KVM: PPC: Book3S HV:
  Fix H_PROD to actually wake the target vcpu", 2016-12-06) in
  v4.11-rc1.

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

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

[Kernel-packages] [Bug 1670518] Re: [Hyper-V] Missing PCI patches breaking SR-IOV hot remove

2017-03-07 Thread Marcelo Cerri

Patches already included on the custom azure kernel.

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

Title:
  [Hyper-V] Missing PCI patches breaking SR-IOV hot remove

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

Bug description:
  Looks like the rebase work missed some prerequisite patches in
  drivers/pci/host/pci-hyperv.c

  (Needed for SR-IOV in Azure on lts-xenial, HWE, and custom)

  commit 0de8ce3ee8e38cc66683438f715c79a2cc69539e
  Author: Long Li 
  Date:   Tue Nov 8 14:04:38 2016 -0800

  PCI: hv: Allocate physically contiguous hypercall params buffer

  hv_do_hypercall() assumes that we pass a segment from a physically
  contiguous buffer.  A buffer allocated on the stack may not work if
  CONFIG_VMAP_STACK=y is set.

  Use kmalloc() to allocate this buffer.

  
  commit 542ccf4551fa019a8ae9dfb7c8cd7e73a3d7e614
  Author: Tobias Klauser 
  Date:   Mon Oct 31 12:04:09 2016 +0100

  PCI: hv: Make unnecessarily global IRQ masking functions static

  Make hv_irq_mask() and hv_irq_unmask() static as they are only used in
  pci-hyperv.c

  This fixes a sparse warning.

  commit e74d2ebdda33b3bdd1826b5b92e9aa45bdf92bb3
  Author: Dexuan Cui 
  Date:   Thu Nov 10 07:19:52 2016 +

  PCI: hv: Delete the device earlier from hbus->children for hot-
  remove

  After we send a PCI_EJECTION_COMPLETE message to the host, the host will
  immediately send us a PCI_BUS_RELATIONS message with
  relations->device_count == 0, so pci_devices_present_work(), running on
  another thread, can find the being-ejected device, mark the
  hpdev->reported_missing to true, and run list_move_tail()/list_del() for
  the device -- this races hv_eject_device_work() -> list_del().

  Move the list_del() in hv_eject_device_work() to an earlier place, i.e.,
  before we send PCI_EJECTION_COMPLETE, so later the
  pci_devices_present_work() can't see the device.

  
  commit 17978524a636d007e6b929304ae3eb5ea0371019
  Author: Dexuan Cui 
  Date:   Thu Nov 10 07:18:47 2016 +

  PCI: hv: Fix hv_pci_remove() for hot-remove

  1. We don't really need such a big on-stack buffer when sending the
  teardown_packet: vmbus_sendpacket() here only uses sizeof(struct
  pci_message).

  2. In the hot-remove case (PCI_EJECT), after we send PCI_EJECTION_COMPLETE
  to the host, the host will send a RESCIND_CHANNEL message to us and the
  host won't access the per-channel ringbuffer any longer, so we needn't 
send
  PCI_RESOURCES_RELEASED/PCI_BUS_D0EXIT to the host, and we shouldn't expect
  the host's completion message of PCI_BUS_D0EXIT, which will never come.

  3. We should send PCI_BUS_D0EXIT after
  hv_send_resources_released().

  Signed-off-by: Dexuan Cui 
  Signed-off-by: Bjorn Helgaas 
  Reviewed-by: Jake Oshins 
  Acked-by: K. Y. Srinivasan 
  CC: Haiyang Zhang 
  CC: Vitaly Kuznetsov 

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

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

[Kernel-packages] [Bug 1670706] Re: Kernel Call Trace After Disabling an ath10k Wireless Device

2017-03-07 Thread Dmitrii Shcherbakov

Cannot reliably reproduce it even on the same kernel - will keep trying.

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

Title:
  Kernel Call Trace After Disabling an ath10k Wireless Device

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Disabled a wireless adapter via NetworkManager. Got a kernel trace in
  dmesg.

  3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
  Network Adapter (rev 32)

  uname -r
  4.10.0-9-generic

  https://paste.ubuntu.com/24131142/

  There are also usb hot-plug messages in between ath10k related ones -
  this is because I disabled a wireless adapter and immediately plugged
  in a usb type-c dock so don't mind those.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-9-generic 4.10.0-9.11
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dima   3007 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar  7 17:28:37 2017
  InstallationDate: Installed on 2017-02-27 (8 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
  MachineType: Razer Blade
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-9-generic.efi.signed 
root=UUID=3f515c94-cd91-48b4-80f6-84ec24cb7b8f ro rootflags=subvol=@ quiet 
button.lid_init_state=open pcie_aspm=off
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-9-generic N/A
   linux-backports-modules-4.10.0-9-generic  N/A
   linux-firmware1.163
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2017
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.00
  dmi.board.name: Razer
  dmi.board.vendor: Razer
  dmi.chassis.type: 9
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr1.00:bd01/10/2017:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
  dmi.product.name: Blade
  dmi.product.version: 6.06
  dmi.sys.vendor: Razer

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

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

[Kernel-packages] [Bug 1625222] Re: d-i is missing usb support for platforms that use the xhci-platform driver

This bug was fixed in the package debian-installer -
20101020ubuntu318.42

---
debian-installer (20101020ubuntu318.42) trusty; urgency=medium

  * Drop support for removed keystone kernel (LP: #1623090)
  * Move master kernels to 3.13.0-110.
  * Move lts-xenial kernels to 4.4.0-64 (LP: #1625222)

 -- Adam Conrad   Tue, 28 Feb 2017 09:32:13 -0700

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

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

Title:
  d-i is missing usb support for platforms that use the xhci-platform
  driver

Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in debian-installer source package in Trusty:
  Fix Released
Status in linux source package in Trusty:
  Invalid
Status in debian-installer source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in debian-installer source package in Yakkety:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in debian-installer source package in Zesty:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  Any platform that gets usb support from the xhci-platform driver does not 
have usb enabled in d-i.

  [Test Case]
  Boot into d-i and attempt to use a usb device, i.e. keyboard.

  [Regression Risk]
  Extremely low as this is a driver that is already present in the kernel.

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

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

[Kernel-packages] [Bug 1616830] Re: Bad disk performance with AMD Carrizo FCH controllers

** Tags added: kernel-da-key

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

Title:
  Bad disk performance with AMD Carrizo FCH controllers

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I have had a problem where importing database was much slower in a
  dual-boot machine when booted into ubuntu compared to running ubuntu
  inside virtualbox in windows 10. It seems Ubuntu does not like Amd
  carrizo fch

  I collected some information and posted here (and attached as text file to 
report):
  https://answers.launchpad.net/ubuntu/+question/360373

  To put it short, the disk performs up to 10 times better inside
  virtualbox. (yes I thought about caches but VM box also has half the
  memory and they must favor ubuntu running on real hardware with twice
  ram)

  I believe this is a kernel/driver related problem since it directly
  effects disk performance.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-34-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jobgo  3381 F pulseaudio
   /dev/snd/controlC0:  jobgo  3381 F pulseaudio
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Date: Thu Aug 25 12:36:05 2016
  HibernationDevice: RESUME=UUID=ba38c925-a729-4e33-a08f-a7573abd2826
  InstallationDate: Installed on 2016-08-23 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: HP HP Pavilion Notebook
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed 
root=UUID=cd8e7352-609f-4ebd-83ba-24335f6eece9 ro
  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-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.17
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 80B5
  dmi.board.vendor: HP
  dmi.board.version: 81.29
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.17:bd03/09/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B5:rvr81.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1670544] Re: [Hyper-V] Rebase Hyper-V to the upstream 4.10 kernel

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

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

** Tags added: kernel-da-key kernel-hyper-v

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

Title:
  [Hyper-V] Rebase Hyper-V to the upstream 4.10 kernel

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Catching up with upstream 4.10 Hyper-V, files:
  arch/x86/kernel/cpu/mshyperv.c
  arch/x86/include/asm/mshyperv.h
  arch/x86/include/uapi/asm/hyperv.h
  include/linux/hyperv.h
  drivers/hv/channel.c
  drivers/hv/channel_mgmt.c
  drivers/hv/connection.c
  drivers/hv/hv_balloon.c
  drivers/hv/hv.c
  drivers/hv/hv_fcopy.c
  drivers/hv/hv_kvp.c
  drivers/hv/hv_snapshot.c
  drivers/hv/hv_util.c
  drivers/hv/hv_utils_transport.c
  drivers/hv/hv_utils_transport.h
  drivers/hv/hyperv_vmbus.h
  drivers/hv/ring_buffer.c
  drivers/hv/vmbus_drv.c
  tools/hv/hv_fcopy_daemon.c
  tools/hv/hv_get_dhcp_info.sh
  tools/hv/hv_get_dns_info.sh
  tools/hv/hv_kvp_daemon.c
  tools/hv/hv_set_ifconfig.sh
  tools/hv/hv_vss_daemon.c
  tools/hv/lsvmbus
  drivers/input/serio/hyperv-keyboard.c
  drivers/net/hyperv/hyperv_net.h
  drivers/net/hyperv/netvsc.c
  drivers/net/hyperv/netvsc_drv.c
  drivers/net/hyperv/rndis_filter.c
  drivers/scsi/storvsc_drv.c
  drivers/hid/hid-hyperv.c
  drivers/pci/host/pci-hyperv.c
  drivers/video/fbdev/hyperv_fb.c
  drivers/uio/uio_hv_generic.c

  Here is the delta from 4.9 to 4.10:
  mshyperv.c : commit a5a1d1c2914b5316924c7893eb683a5420ebd3be : 
clocksource: Use a plain u64 instead of cycle_t
  hyperv.h : commit 433e19cf33d34bb6751c874a9c00980552fe508c : Drivers: hv: 
vmbus: finally fix hv_need_to_signal_on_read()
  hyperv.h : commit f45be72c8ec0b85263d1fe1e6c681d8c87e198e6 : hyperv: Fix 
spelling of HV_UNKOWN
  hyperv.h : commit fc76936d3ea5720a6e0948a08381b803a68deb28 : vmbus: add 
support for dynamic device id's
  hyperv.h : commit 1f6ee4e7d83586c8b10bd4f2f4346353d04ce884 : Drivers: hv: 
vmbus: On write cleanup the logic to interrupt the host
  hyperv.h : commit fa32ff6576623616c1751562edaed8c164ca5199 : Drivers: hv: 
ring_buffer: count on wrap around mappings in get_next_pkt_raw() (v2)
  channel.c : commit 1f6ee4e7d83586c8b10bd4f2f4346353d04ce884 : Drivers: 
hv: vmbus: On write cleanup the logic to interrupt the host
  channel.c : commit 3372592a140db69fd63837e81f048ab4abf8111e : Drivers: 
hv: vmbus: On the read path cleanup the logic to interrupt the host
  channel_mgmt.c : commit f45be72c8ec0b85263d1fe1e6c681d8c87e198e6 : 
hyperv: Fix spelling of HV_UNKOWN
  channel_mgmt.c : commit abd1026da4a7700a8db370947f75cd17b6ae6f76 : hv: 
acquire vmbus_connection.channel_mutex in vmbus_free_channels()
  channel_mgmt.c : commit 74198eb4a42c4a3c4fbef08fa01a291a282f7c2e : 
Drivers: hv: vmbus: Base host signaling strictly on the ring state
  connection.c : commit 95096f2fbd10186d3e78a328b327afc71428f65f : 
uio-hv-generic: new userspace i/o driver for VMBus
  hv_balloon.c : commit b3bb97b8a49f3c489134793705bc636c7883e777 : Drivers: 
hv: balloon: Add logging for dynamic memory operations
  hv_balloon.c : commit 8500096017e3a1baadbdefe8b84a99117472af46 : Drivers: 
hv: balloon: Fix info request to show max page count
  hv_balloon.c : commit 8ba8c0a111083bfe53f7a8a0e2f14fd12eb2e030 : Drivers: 
hv: balloon: Disable hot add when CONFIG_MEMORY_HOTPLUG is not set
  hv.c : commit a5a1d1c2914b5316924c7893eb683a5420ebd3be : clocksource: Use 
a plain u64 instead of cycle_t
  hv.c : commit 6ffc4b85358f6b7d252420cfa5862312cf5f83d8 : hv: change 
clockevents unbind tactics
  hv_snapshot.c : commit b357fd3908c1191f2f56e38aa77f2aecdae18bc8 : 
Drivers: hv: vss: Operation timeouts should match host expectation
  hv_snapshot.c : commit 23d2cc0c29eb0e7c6fe4cac88098306c31c40208 : 
Drivers: hv: vss: Improve log messages.
  hv_util.c : commit 3da0401b4d0e17aea7526db0235d98fa535d903e : Drivers: 
hv: utils: Fix the mapping between host version and protocol to use
  hyperv_vmbus.h : commit d7edd31ba9a661f1a3f357b43e84e84e5fad9538 : 
Drivers: hv: utils: reduce HV_UTIL_NEGO_TIMEOUT timeout
  ring_buffer.c : commit 433e19cf33d34bb6751c874a9c00980552fe508c : 
Drivers: hv: vmbus: finally fix hv_need_to_signal_on_read()
  vmbus_drv.c : commit fc76936d3ea5720a6e0948a08381b803a68deb28 : vmbus: 
add support for dynamic device id's
  vmbus_drv.c : commit f6b2db084b65b9dc0f910bc48d5f77c0e5166dc6 : vmbus: 
make sysfs names consistent with PCI
  hv_fcopy_daemon.c : commit 0c38cda64aecb4a821210bb2d3d04092c181c0ae : 
tools: hv: remove unnecessary header files and netlink related code
  hv_kvp_daemon.c : commit 0c38cda64aecb4a821210bb2d3d04092c181c0ae : 
tools: hv: remove unnecessary header files and netlink related code
  hv_kvp_daemon.c : commit 51b68128ef55200fbe03d82c9ac5722f255e58b7 :

[Kernel-packages] [Bug 1670624] Re: Official 16.04 HWE 4.8 kernels do not boot (4.4 was booting)

Can you see if the 4.11-rc1 kernel will boot?  It is available from:
 http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc1/

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

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

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

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

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

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

** Tags added: kernel-da-key

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

Title:
  Official 16.04 HWE 4.8 kernels do not boot (4.4 was booting)

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

Bug description:
  The machine is the same machine as in this bug report:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616830

  In mid 2016 I tested 4.8 kernels on that machine and they did not boot. (and 
same errors apply to current situation)
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616830/comments/5

  Also Ubuntu 16.10 and newer releases do not boot anymore (as reported by a 
user, I think it is due to kernel). He also reports the same errors with the 
4.8 kernel.
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616830/comments/15

  It seems that official release kernels still have the same problems
  and nothing was fixed.

  There seem to be many problems with Ubuntu on Carrizo, black screens,
  random freezes. I myself experienced, keyboard problems (keyboard
  sometimes do not register keystrokes), touchpad works strangely,
  random freeze with caps-lock blinking, low disk performance (max
  1.3mbytes/sec) and much more.

  I do not understand how hardware support can be getting worse and
  worse, but that seems to be the case.

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

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

[Kernel-packages] [Bug 1625222] Re: d-i is missing usb support for platforms that use the xhci-platform driver

This bug was fixed in the package debian-installer - 20101020ubuntu483.2

---
debian-installer (20101020ubuntu483.2) yakkety; urgency=medium

  * Move master kernels to 4.8.0-39 (LP: #1625222)

 -- Adam Conrad   Tue, 28 Feb 2017 09:47:37 -0700

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

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

Title:
  d-i is missing usb support for platforms that use the xhci-platform
  driver

Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in debian-installer source package in Trusty:
  Fix Released
Status in linux source package in Trusty:
  Invalid
Status in debian-installer source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in debian-installer source package in Yakkety:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in debian-installer source package in Zesty:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  Any platform that gets usb support from the xhci-platform driver does not 
have usb enabled in d-i.

  [Test Case]
  Boot into d-i and attempt to use a usb device, i.e. keyboard.

  [Regression Risk]
  Extremely low as this is a driver that is already present in the kernel.

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

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

[Kernel-packages] [Bug 1625222] Update Released

2017-03-07 Thread Adam Conrad

The verification of the Stable Release Update for debian-installer has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  d-i is missing usb support for platforms that use the xhci-platform
  driver

Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in debian-installer source package in Trusty:
  Fix Released
Status in linux source package in Trusty:
  Invalid
Status in debian-installer source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in debian-installer source package in Yakkety:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in debian-installer source package in Zesty:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  Any platform that gets usb support from the xhci-platform driver does not 
have usb enabled in d-i.

  [Test Case]
  Boot into d-i and attempt to use a usb device, i.e. keyboard.

  [Regression Risk]
  Extremely low as this is a driver that is already present in the kernel.

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

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

[Kernel-packages] [Bug 1669127] Re: linux: 4.10.0-11.13 -proposed tracker

2017-03-07 Thread Adam Conrad

** Tags added: block-proposed

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

Title:
  linux: 4.10.0-11.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
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:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.10.0-11.13 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 --
  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-development-workflow/+bug/1669127/+subscriptions

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

[Kernel-packages] [Bug 1654708] Re: Trying to reinstall ZFS on Xenial. Cannot mount existing zpool with identifier from /mnt/disk/by-id/xxxx

2017-03-07 Thread John Bridges

I just upgraded from 14.04 to 16.04  4.4.0-64-generic

At first the modprobe zfs seemed to work if done manually after boot.
Once I removed zfsutils-linux, and re-installed it would no longer work.
I tried multiple variations of removing and re-adding ZFS, and did purge all 
old ZFS versions from Trusty install.

The only fix I could get to function was to modify the source for zpl_xattr.c
There were two calls to posix_acl_valid, one in __zpl_xattr_acl_set_access, and 
one in __zpl_xattr_acl_set_default.
I changed them as described above, and did dpkg-reconfigure zfs-dkms

The ZFS kernel module would not load until I rebooted, then it all came
up and mounted my ZFS pools automatically.

It appears this fix is already in the master ZFS on Linux source:
https://github.com/zfsonlinux/zfs/blob/master/module/zfs/zpl_xattr.c

Hopefully this will end up in Ubuntu soon?

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

Title:
  Trying to reinstall ZFS on Xenial. Cannot mount existing zpool with
  identifier from /mnt/disk/by-id/

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  zfs-dkms 0.6.5.6-0ubuntu15

  I cant mount/install my zpool. so i tried reinstalling zfslinux-utils,
  which gives me three error messages like this: "zfs-mount.service is a
  disabled" or a static unit, not starting it."...

  If something doesn't work I try googling error messages. most answers
  not totally like my problem but related to dkms, so I tried loading
  zfs-dkms and reinstalling zfslinux-utils.

  I created the zpool with id from /mnt/disk/by-id/ - which is zfs good-
  practice. This may be causing problems with the mount. I dont know...

  Cheers.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: zfs-dkms 0.6.5.6-0ubuntu15
  ProcVersionSignature: Ubuntu 4.4.0-58.79-generic 4.4.35
  Uname: Linux 4.4.0-58-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  DKMSKernelVersion: 4.4.0-58-generic
  Date: Sat Jan  7 15:58:15 2017
  DuplicateSignature: 
dkms:zfs-dkms:0.6.5.6-0ubuntu15:/var/lib/dkms/zfs/0.6.5.6/build/module/zfs/zpl_xattr.c:1284:12:
 error: too few arguments to function ‘posix_acl_valid’
  InstallationDate: Installed on 2016-12-26 (12 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Beta amd64 (20161225)
  PackageVersion: 0.6.5.6-0ubuntu15
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: zfs-linux
  Title: zfs-dkms 0.6.5.6-0ubuntu15: zfs kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1670706] Re: Kernel Call Trace After Disabling an ath10k Wireless Device

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

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc1/

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

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

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

Title:
  Kernel Call Trace After Disabling an ath10k Wireless Device

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Disabled a wireless adapter via NetworkManager. Got a kernel trace in
  dmesg.

  3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
  Network Adapter (rev 32)

  uname -r
  4.10.0-9-generic

  https://paste.ubuntu.com/24131142/

  There are also usb hot-plug messages in between ath10k related ones -
  this is because I disabled a wireless adapter and immediately plugged
  in a usb type-c dock so don't mind those.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-9-generic 4.10.0-9.11
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dima   3007 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar  7 17:28:37 2017
  InstallationDate: Installed on 2017-02-27 (8 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
  MachineType: Razer Blade
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-9-generic.efi.signed 
root=UUID=3f515c94-cd91-48b4-80f6-84ec24cb7b8f ro rootflags=subvol=@ quiet 
button.lid_init_state=open pcie_aspm=off
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-9-generic N/A
   linux-backports-modules-4.10.0-9-generic  N/A
   linux-firmware1.163
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2017
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.00
  dmi.board.name: Razer
  dmi.board.vendor: Razer
  dmi.chassis.type: 9
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr1.00:bd01/10/2017:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
  dmi.product.name: Blade
  dmi.product.version: 6.06
  dmi.sys.vendor: Razer

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

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

[Kernel-packages] [Bug 1670634] Re: blk-mq: possible deadlock on CPU hot(un)plug

2017-03-07 Thread Douglas Miller

This looks a lot like the problem in LP #1662673, but that fix is
supposed to be in kernel 4.4.0-65-generic. Might be worth confirming
though. Or perhaps confirming that the fix actually works on the Z
architecture (depends on how the architecture/compiler handles 'bool').

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

Title:
  blk-mq: possible deadlock on CPU hot(un)plug

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Carsten Jacobi  - 2017-03-07 03:35:31 ==
  I'm evaluating Ubuntu-Xenial on z for development purposes, the test system 
is installed in an LPAR with one FCP-LUN which is accessable by 4 pathes (all 
pathes are configured).
  The system hangs regularly when I make packages with "pdebuild" using the 
pbuilder packaging suit.
  The local Linux development team helped me out with a pre-analysis that I can 
post here (thanks a lot for that):

  With the default settings and under a certain workload,
  blk_mq seems to get into a presumed "deadlock".
  Possibly this happens on CPU hot(un)plug.

  After the I/O stalled, a dump was pulled manually.
  The following information is from the crash dump pre-analysis.

  $ zgetdump -i dump.0
  General dump info:
Dump format: elf
Version: 1
UTS node name..: mclint
UTS kernel release.: 4.4.0-65-generic
UTS kernel version.: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
System arch: s390x (64 bit)
CPU count (online).: 2
Dump memory range..: 8192 MB
  Memory map:
 - 0001b831afff (7043 MB)
0001b831b000 - 0001 (1149 MB)

  Things look similarly with HWE kernel ubuntu16.04-4.8.0-34.36~16.04.1.

KERNEL: vmlinux.full
  DUMPFILE: dump.0
  CPUS: 2
  DATE: Fri Mar  3 14:31:07 2017
UPTIME: 02:11:20
  LOAD AVERAGE: 13.00, 12.92, 11.37
 TASKS: 411
  NODENAME: mclint
   RELEASE: 4.4.0-65-generic
   VERSION: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
   MACHINE: s390x  (unknown Mhz)
MEMORY: 7.8 GB
 PANIC: ""
   PID: 0
   COMMAND: "swapper/0"
  TASK: bad528  (1 of 2)  [THREAD_INFO: b78000]
   CPU: 0
 STATE: TASK_RUNNING (ACTIVE)
  INFO: no panic task found

  crash> dev -d
  MAJOR GENDISKNAME   REQUEST_QUEUE  TOTAL ASYNC  SYNC   DRV
  ...
  8 1e1d6d800  sda1e1d51210  0 23151 4294944145 
N/A(MQ)
  8 1e4e06800  sdc2081b180 23148 4294944148 
N/A(MQ)
  8 1f07800sdb20c75680 23195 4294944101 
N/A(MQ)
  8 1e4e06000  sdd1e4e31210  0 23099 4294944197 
N/A(MQ)
252 1e1d6c800  dm-0   1e1d51b18  9 1 8 
N/A(MQ)
  ...

  So both dm-mpath and sd have requests pending in their block multiqueue.
  The large numbers of sd look strange and seem to be the unsigned formatting 
of the values shown for async multiplied by -1.

  [0.798256] Linux version 4.4.0-65-generic (buildd@z13-011) (gcc version 
5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #86-Ubuntu SMP Thu Feb 23 
17:54:37 UTC 2017 (Ubuntu 4.4.0-65.86-generic 4.4.49)
  [0.798262] setup: Linux is running natively in 64-bit mode
  [0.798290] setup: Max memory size: 8192MB
  [0.798298] setup: Reserving 196MB of memory at 7996MB for crashkernel 
(System RAM: 7996MB)

  [0.836923] Kernel command line: root=/dev/mapper/mclint_vg-root
  rootflags=subvol=@ crashkernel=196M BOOT_IMAGE=0

  [ 5281.179428] INFO: task xfsaild/dm-11:1604 blocked for more than 120 
seconds.
  [ 5281.179437]   Not tainted 4.4.0-65-generic #86-Ubuntu
  [ 5281.179438] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 5281.179440] xfsaild/dm-11   D 007bcf52 0  1604  2 
0x
  [ 5281.179444]0001e931c230 001a6964 0001e6f9b958 
0001e6f9b9d8
0001e15795f0 0001e6f9b988 00ce8c00 
0001ea805c70
0001ea805c00 00ba5ed0 0001e931c1d0 
0001e1579b20
0001ea805c00 0001e15795f0 0001ea805c00 

007d3978 007bc9f8 0001e6f9b9d8 
0001e6f9ba40
  [ 5281.179454] Call Trace:
  [ 5281.179461] ([<007bc9f8>] __schedule+0x300/0x810)
  [ 5281.179462]  [<007bcf52>] schedule+0x4a/0xb0
  [ 5281.179465]  [<007c02aa>] schedule_timeout+0x232/0x2a8
  [ 5281.179466]  [<007bde50>] wait_for_common+0x110/0x1c8
  [ 5281.179472]  [<0017b602>] flush_work+0x42/0x58
  [ 5281.179564]  [<03ff805e14ba>] xlog_cil_force_lsn+0x7a/0x238 [xfs]
  [ 5281.179589]

[Kernel-packages] [Bug 1648388] Re: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting

@Lo, It sounds like the 4.10-rc3 kernel exhibits the bug on 16.04 but
not on 14.04, is that correct?  That might indicate the bug outside of
the kernel.

Can you test the 4.11-rc1 kernel with 16.04?  That kernel can be downloaded 
from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc1/


It might also be worth while to test the current daily iso image from:
Desktop:
http://cdimage.ubuntu.com/daily-live/current/
Server:
http://cdimage.ubuntu.com/ubuntu-server/daily/current/

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

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

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

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

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

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

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

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

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

Title:
  Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system
  hangs while rebooting

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

Bug description:
  Install Ubuntu16.04 in RAID1 created by Intel RSTe no matter legacy mode or 
UEFI mode.
  System hangs while rebooting

  Not found the issue in RAID0
  No issue on Ubuntu14.04
  Driver-OS inbox support

  Below as error messages
  ===
  INFO:  task systemd-shutdow:1 blocked for more than 120 seconds.
  Not tainted 4.4.0-21-generic #37-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

  INFO:  task  jbd2/md126p2-8:1732 blocked for more than 120 seconds.
  Not tainted 4.4.0-21-generic #37-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

  INFO:  task ext4lazyinit:1873 blocked for more than 120 seconds.
  Not tainted 4.4.0-21-generic #37-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

  INFO:  task kworker/u66:4:3139 blocked for more than 120 seconds.
  Not tainted 4.4.0-21-generic #37-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  ===

  WORKAROUND: edit /etc/sysctl.conf with follow commands and the system don't 
hang while rebooting:
  vm.dirty_background_ratio=5
  vm.dirty_ratio=10
  kernel.panic=3
  kernel.hung_task_panic=1
  kernel.hung_task_timeout_secs=30

  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=f578df47-a1b8-4e66-bd37-904f943eb01b
  InstallationDate: Installed on 2016-12-15 (10 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  MachineType: Dell DCS6430G
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=bc552762-1955-44b8-a83e-2a414f0e0bd1 ro
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 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-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 03/22/2016
  dmi.bios.vendor: Dell
  dmi.bios.version: 2.0.3
  dmi.board.name: 038VV0
  dmi.board.vendor: Dell
  dmi.board.version: X01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell
  dmi.modalias: 
dmi:bvnDell:bvr2.0.3:bd03/22/2016:svnDell:pnDCS6430G:pvr:rvnDell:rn038VV0:rvrX01:cvnDell:ct23:cvr:
  dmi.product.name: DCS6430G
  dmi.sys.vendor: Dell

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

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

[Kernel-packages] [Bug 1670518] Re: [Hyper-V] Missing PCI patches breaking SR-IOV hot remove

https://lists.ubuntu.com/archives/kernel-team/2017-March/082889.html

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

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

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

Title:
  [Hyper-V] Missing PCI patches breaking SR-IOV hot remove

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

Bug description:
  Looks like the rebase work missed some prerequisite patches in
  drivers/pci/host/pci-hyperv.c

  (Needed for SR-IOV in Azure on lts-xenial, HWE, and custom)

  commit 0de8ce3ee8e38cc66683438f715c79a2cc69539e
  Author: Long Li 
  Date:   Tue Nov 8 14:04:38 2016 -0800

  PCI: hv: Allocate physically contiguous hypercall params buffer

  hv_do_hypercall() assumes that we pass a segment from a physically
  contiguous buffer.  A buffer allocated on the stack may not work if
  CONFIG_VMAP_STACK=y is set.

  Use kmalloc() to allocate this buffer.

  
  commit 542ccf4551fa019a8ae9dfb7c8cd7e73a3d7e614
  Author: Tobias Klauser 
  Date:   Mon Oct 31 12:04:09 2016 +0100

  PCI: hv: Make unnecessarily global IRQ masking functions static

  Make hv_irq_mask() and hv_irq_unmask() static as they are only used in
  pci-hyperv.c

  This fixes a sparse warning.

  commit e74d2ebdda33b3bdd1826b5b92e9aa45bdf92bb3
  Author: Dexuan Cui 
  Date:   Thu Nov 10 07:19:52 2016 +

  PCI: hv: Delete the device earlier from hbus->children for hot-
  remove

  After we send a PCI_EJECTION_COMPLETE message to the host, the host will
  immediately send us a PCI_BUS_RELATIONS message with
  relations->device_count == 0, so pci_devices_present_work(), running on
  another thread, can find the being-ejected device, mark the
  hpdev->reported_missing to true, and run list_move_tail()/list_del() for
  the device -- this races hv_eject_device_work() -> list_del().

  Move the list_del() in hv_eject_device_work() to an earlier place, i.e.,
  before we send PCI_EJECTION_COMPLETE, so later the
  pci_devices_present_work() can't see the device.

  
  commit 17978524a636d007e6b929304ae3eb5ea0371019
  Author: Dexuan Cui 
  Date:   Thu Nov 10 07:18:47 2016 +

  PCI: hv: Fix hv_pci_remove() for hot-remove

  1. We don't really need such a big on-stack buffer when sending the
  teardown_packet: vmbus_sendpacket() here only uses sizeof(struct
  pci_message).

  2. In the hot-remove case (PCI_EJECT), after we send PCI_EJECTION_COMPLETE
  to the host, the host will send a RESCIND_CHANNEL message to us and the
  host won't access the per-channel ringbuffer any longer, so we needn't 
send
  PCI_RESOURCES_RELEASED/PCI_BUS_D0EXIT to the host, and we shouldn't expect
  the host's completion message of PCI_BUS_D0EXIT, which will never come.

  3. We should send PCI_BUS_D0EXIT after
  hv_send_resources_released().

  Signed-off-by: Dexuan Cui 
  Signed-off-by: Bjorn Helgaas 
  Reviewed-by: Jake Oshins 
  Acked-by: K. Y. Srinivasan 
  CC: Haiyang Zhang 
  CC: Vitaly Kuznetsov 

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

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

[Kernel-packages] [Bug 1670518] Re: [Hyper-V] Missing PCI patches breaking SR-IOV hot remove

https://lists.ubuntu.com/archives/kernel-team/2017-March/082884.html

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

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

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

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

Title:
  [Hyper-V] Missing PCI patches breaking SR-IOV hot remove

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

Bug description:
  Looks like the rebase work missed some prerequisite patches in
  drivers/pci/host/pci-hyperv.c

  (Needed for SR-IOV in Azure on lts-xenial, HWE, and custom)

  commit 0de8ce3ee8e38cc66683438f715c79a2cc69539e
  Author: Long Li 
  Date:   Tue Nov 8 14:04:38 2016 -0800

  PCI: hv: Allocate physically contiguous hypercall params buffer

  hv_do_hypercall() assumes that we pass a segment from a physically
  contiguous buffer.  A buffer allocated on the stack may not work if
  CONFIG_VMAP_STACK=y is set.

  Use kmalloc() to allocate this buffer.

  
  commit 542ccf4551fa019a8ae9dfb7c8cd7e73a3d7e614
  Author: Tobias Klauser 
  Date:   Mon Oct 31 12:04:09 2016 +0100

  PCI: hv: Make unnecessarily global IRQ masking functions static

  Make hv_irq_mask() and hv_irq_unmask() static as they are only used in
  pci-hyperv.c

  This fixes a sparse warning.

  commit e74d2ebdda33b3bdd1826b5b92e9aa45bdf92bb3
  Author: Dexuan Cui 
  Date:   Thu Nov 10 07:19:52 2016 +

  PCI: hv: Delete the device earlier from hbus->children for hot-
  remove

  After we send a PCI_EJECTION_COMPLETE message to the host, the host will
  immediately send us a PCI_BUS_RELATIONS message with
  relations->device_count == 0, so pci_devices_present_work(), running on
  another thread, can find the being-ejected device, mark the
  hpdev->reported_missing to true, and run list_move_tail()/list_del() for
  the device -- this races hv_eject_device_work() -> list_del().

  Move the list_del() in hv_eject_device_work() to an earlier place, i.e.,
  before we send PCI_EJECTION_COMPLETE, so later the
  pci_devices_present_work() can't see the device.

  
  commit 17978524a636d007e6b929304ae3eb5ea0371019
  Author: Dexuan Cui 
  Date:   Thu Nov 10 07:18:47 2016 +

  PCI: hv: Fix hv_pci_remove() for hot-remove

  1. We don't really need such a big on-stack buffer when sending the
  teardown_packet: vmbus_sendpacket() here only uses sizeof(struct
  pci_message).

  2. In the hot-remove case (PCI_EJECT), after we send PCI_EJECTION_COMPLETE
  to the host, the host will send a RESCIND_CHANNEL message to us and the
  host won't access the per-channel ringbuffer any longer, so we needn't 
send
  PCI_RESOURCES_RELEASED/PCI_BUS_D0EXIT to the host, and we shouldn't expect
  the host's completion message of PCI_BUS_D0EXIT, which will never come.

  3. We should send PCI_BUS_D0EXIT after
  hv_send_resources_released().

  Signed-off-by: Dexuan Cui 
  Signed-off-by: Bjorn Helgaas 
  Reviewed-by: Jake Oshins 
  Acked-by: K. Y. Srinivasan 
  CC: Haiyang Zhang 
  CC: Vitaly Kuznetsov 

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

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

[Kernel-packages] [Bug 1669127] Re: linux: 4.10.0-11.13 -proposed tracker

** Tags removed: block-proposed

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

Title:
  linux: 4.10.0-11.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
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:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.10.0-11.13 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 --
  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-development-workflow/+bug/1669127/+subscriptions

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

[Kernel-packages] [Bug 1349740] Re: acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM

2017-03-07 Thread Colin Ian King

@SunBear. I very much doubt PCIe ASPM being disabled is any connection
with the USB charging not working.

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

Title:
  acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM

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

Bug description:
  [0.183201] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-6-generic 3.16.0-6.11
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2878 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Jul 29 04:47:24 2014
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2014-04-27 (92 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic 
root=UUID=13144268-2374-4154-83f1-c35d81306190 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-6-generic N/A
   linux-backports-modules-3.16.0-6-generic  N/A
   linux-firmware1.132
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1670508] Re: CIFS: Enable encryption for SMB3

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

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

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

Title:
  CIFS: Enable encryption for SMB3

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

Bug description:
  There has been work upstream to enable encryption support for SMB3
  connections. This is a particularly valuable (and commonly requested)
  feature with the Azure Files service as encryption is required to
  connect to an Azure Files storage share from on-prem or from a
  different Azure region.

  The relevant commits are as follows:

  CIFS: Fix possible use after free in demultiplex thread
  Commit 61cfac6f267dabcf2740a7ec8a0295833b28b5f5

  CIFS: Allow to switch on encryption with seal mount option
  Commit ae6f8dd4d0c87bfb72da9d9b56342adf53e69c31

  CIFS: Add capability to decrypt big read responses
  Commit c42a6abe3012832a68a371dabe17c2ced97e62ad

  CIFS: Decrypt and process small encrypted packets
  Commit 4326ed2f6a16ae9d33e4209b540dc9a371aba840

  CIFS: Add copy into pages callback for a read operation
  Commit d70b9104b1ca586f73aaf59426756cec3325a40e

  CIFS: Add mid handle callback
  Commit 9b7c18a2d4b798963ea80f6769701dcc4c24b55e

  CIFS: Add transform header handling callbacks
  Commit 9bb17e0916a03ab901fb684e874d77a1e96b3d1e

  CIFS: Encrypt SMB3 requests before sending
  Commit 026e93dc0a3eefb0be060bcb9ecd8d7a7fd5c398

  CIFS: Enable encryption during session setup phase
  Commit cabfb3680f78981d26c078a26e5c748531257ebb

  CIFS: Add capability to transform requests before sending
  Commit 7fb8986e7449d0a5cebd84d059927afa423fbf85

  CIFS: Separate RFC1001 length processing for SMB2 read
  Commit b8f57ee8aad414a3122bff72d7968a94baacb9b6

  CIFS: Separate SMB2 sync header processing
  Commit cb200bd6264a80c04e09e8635fa4f3901cabdaef

  CIFS: Send RFC1001 length in a separate iov
  Commit 738f9de5cdb9175c19d24cfdf90b4543fc3b47bf

  CIFS: Make send_cancel take rqst as argument
  Commit fb2036d817584df42504910fe104f68517e8990e

  CIFS: Make SendReceive2() takes resp iov
  Commit da502f7df03d2d0b416775f92ae022f3f82bedd5

  CIFS: Separate SMB2 header structure
  Commit 31473fc4f9653b73750d3792ffce6a6e1bdf0da7

  cifs: Add soft dependencies
  Commit b9be76d585d48cb25af8db0d35e1ef9030fbe13a

  cifs: Only select the required crypto modules
  Commit 3692304bba6164be3810afd41b84ecb0e1e41db1

  cifs: Simplify SMB2 and SMB311 dependencies
  Commit c1ecea87471bbb614f8121e00e5787f363140365

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

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

[Kernel-packages] [Bug 1349740] Re: acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM

2017-03-07 Thread SunBear

I am reporting the same issue in UBUNTU 16.04 LTS 4.4.0-64-generic. 
[0.186376] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM

I noticed the following messages preceding this error message.
[0.144970] ACPI FADT declares the system doesn't support PCIe ASPM, so 
disable it
[0.172842] ACPI: Interpreter enabled
[0.172864] ACPI: (supports S0 S3 S4 S5)
[0.172865] ACPI: Using IOAPIC for interrupt routing
[0.172885] PCI: Using host bridge windows from ACPI; if necessary, use 
"pci=nocrs" and report a bug

In my BIOS setting, I have "Charging USB devices in Power State S5" as
"Enabled". However, my USB still do not have power. I would like to know
if the error is the reason for why I can't get power from my USB during
suspend/hibernation mode.


$ dmesg | grep acpi
[0.00] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[0.00] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
[0.00] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
[0.00] ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
[0.00] ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1])
[0.00] ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1])
[0.00] ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1])
[0.00] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
[0.144971] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[0.186356] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM 
Segments MSI]
[0.186376] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
[0.198599] acpiphp: Slot [1] registered
[0.198650] acpiphp: Slot [1-1] registered
[0.198695] acpiphp: Slot [1-2] registered
[0.222862] clocksource: acpi_pm: mask: 0xff max_cycles: 0xff, 
max_idle_ns: 2085701024 ns


$ dmesg | grep ACPI
[0.00] BIOS-e820: [mem 0xb295f000-0xb2994fff] ACPI data
[0.00] BIOS-e820: [mem 0xb2d37000-0xb2d37fff] ACPI NVS
[0.00] BIOS-e820: [mem 0xc2546000-0xc2558fff] ACPI data
[0.00] BIOS-e820: [mem 0xc2a14000-0xc2d3bfff] ACPI NVS
[0.00] efi:  ACPI 2.0=0xb295f000  ACPI=0xb295f000  SMBIOS=0xc3205000  
SMBIOS 3.0=0xc3204000  ESRT=0xbe11a098 
[0.00] ACPI: Early table checksum verification disabled
[0.00] ACPI: RSDP 0xB295F000 24 (v02 ALASKA)
[0.00] ACPI: XSDT 0xB295F0A8 CC (v01 ALASKA A M I
01072009 AMI  00010013)
[0.00] ACPI: FACP 0xB2988600 000114 (v06 ALASKA A M I
01072009 AMI  00010013)
[0.00] ACPI: DSDT 0xB295F210 0293EF (v02 ALASKA A M I
01072009 INTL 20160422)
[0.00] ACPI: FACS 0xC2D3BC40 40
[0.00] ACPI: APIC 0xB2988718 BC (v03 ALASKA A M I
01072009 AMI  00010013)
[0.00] ACPI: FPDT 0xB29887D8 44 (v01 ALASKA A M I
01072009 AMI  00010013)
[0.00] ACPI: DMAR 0xB2993F68 A8 (v01 INTEL  SKL  
0001 INTL 0001)
[0.00] ACPI: MCFG 0xB2988878 3C (v01 ALASKA A M I
01072009 MSFT 0097)
[0.00] ACPI: SSDT 0xB29888B8 000390 (v01 SataRe SataTabl 
1000 INTL 20160422)
[0.00] ACPI: FIDT 0xB2988C48 9C (v01 ALASKA A M I
01072009 AMI  00010013)
[0.00] ACPI: SSDT 0xB2988CE8 003041 (v02 SaSsdt SaSsdt   
3000 INTL 20160422)
[0.00] ACPI: SSDT 0xB298BD30 002544 (v02 PegSsd PegSsdt  
1000 INTL 20160422)
[0.00] ACPI: HPET 0xB298E278 38 (v01 INTEL  SKL  
0001 MSFT 005F)
[0.00] ACPI: SSDT 0xB298E2B0 000E3B (v02 INTEL  Ther_Rvp 
1000 INTL 20160422)
[0.00] ACPI: SSDT 0xB298F0F0 000B1D (v02 INTEL  xh_rvp08 
 INTL 20160422)
[0.00] ACPI: UEFI 0xB298FC10 42 (v01 INTEL  EDK2 
0002  0113)
[0.00] ACPI: SSDT 0xB298FC58 000EDE (v02 CpuRef CpuSsdt  
3000 INTL 20160422)
[0.00] ACPI: LPIT 0xB2990B38 94 (v01 INTEL  SKL  
 MSFT 005F)
[0.00] ACPI: WSMT 0xB2990BD0 28 (v01 INTEL  SKL  
 MSFT 005F)
[0.00] ACPI: SSDT 0xB2990BF8 00029F (v02 INTEL  sensrhub 
 INTL 20160422)
[0.00] ACPI: SSDT 0xB2990E98 003002 (v02 INTEL  PtidDevc 
1000 INTL 20160422)
[0.00] ACPI: DBGP 0xB2993EA0 34 (v01 INTEL   
0002 MSFT 005F)
[0.00] ACPI: DBG2 0xB2993ED8 54 (v00 INTEL   
0002 MSFT 005F)
[0.00] ACPI: BGRT 0xB2993F30 38 (v01 ALASKA A M I
01072009 AMI  00010013)
[0.00] ACPI: Local APIC address 0xfee0
[0.00] ACPI: PM-Timer IO Port: 0x1808
[0.00] ACPI: Local APIC address 0xfee0
[0.00] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[0.00] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
[

[Kernel-packages] [Bug 1670490] Re: FC Adapter (LPe32000-based) prints "iotag out of range", goes offline, and delays boot a lot (Ubuntu17.04/Emulex/lpfc))

https://lists.ubuntu.com/archives/kernel-team/2017-March/082882.html

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

** Changed in: linux (Ubuntu Zesty)
   Status: New => Fix Committed

** Changed in: linux (Ubuntu Zesty)
 Assignee: Taco Screen team (taco-screen-team) => Tim Gardner (timg-tpi)

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

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

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

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

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

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

Title:
  FC Adapter (LPe32000-based) prints "iotag out of range", goes offline,
  and delays boot a lot (Ubuntu17.04/Emulex/lpfc))

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

Bug description:
  ---Problem Description---
  FC Adapter goes offline and produces the call traces while booting into OS, 
on assigning the LUNs to it.
   
  ---uname output---
  Linux ltciofvtr-firestone1 4.9.0-12-generic #13-Ubuntu SMP Tue Jan 10 
12:52:39 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
   
  FC Redfish Adapter(32 GB) is going offline on assigning the Luns to it. 
Adapter shows online till pettitboot and even Luns are also vissible in 
pettitboot.
  once selecting the OS from pettitboot and booting into it, it produces call 
traces and also few lpfc errors. attached the comple console logs FYR.
  The FC switch to which the Redfish adapter is connected is a 16 GB switch and 
the adapter is of 32 GB. According to me this parameter should not have any 
concern as the adapter has to support backward compatibility. 

  ---Steps to Reproduce---
  1. install the adapter in a server. and connect it to FC switch (16 GB)
  2. create zone and assign the LUNS to it from V7000.
  3. reboot the OS

  
  root@ltciofvtr-firestone1:~# ll /sys/class/fc_host/
  total 0
  drwxr-xr-x  2 root root 0 Jan 25 04:22 ./
  drwxr-xr-x 72 root root 0 Jan 25 03:50 ../
  lrwxrwxrwx  1 root root 0 Jan 25 04:13 host10 -> 
../../devices/pci0001:00/0001:00:00.0/0001:01:00.1/host10/fc_host/host10/
  lrwxrwxrwx  1 root root 0 Jan 25 04:13 host6 -> 
../../devices/pci:00/:00:00.0/:01:00.0/host6/fc_host/host6/
  lrwxrwxrwx  1 root root 0 Jan 25 04:13 host8 -> 
../../devices/pci:00/:00:00.0/:01:00.1/host8/fc_host/host8/
  lrwxrwxrwx  1 root root 0 Jan 25 04:13 host9 -> 
../../devices/pci0001:00/0001:00:00.0/0001:01:00.0/host9/fc_host/host9/
  root@ltciofvtr-firestone1:~# 
  root@ltciofvtr-firestone1:~# cat /sys/class/fc_host/host6/port_state 
  Offline
  root@ltciofvtr-firestone1:~# cat /sys/class/fc_host/host8/port_state 
  Offline
  root@ltciofvtr-firestone1:~# cat /sys/class/fc_host/host9/port_state 
  Online
  root@ltciofvtr-firestone1:~# cat /sys/class/fc_host/host10/port_state 
  Online
  root@ltciofvtr-firestone1:~# 
  root@ltciofvtr-firestone1:~# lspci -nn | grep -i fibre
  :01:00.0 Fibre Channel [0c04]: Emulex Corporation Lancer Gen6: LPe32000 
Fibre Channel Host Adapter [10df:e300] (rev 01)
  :01:00.1 Fibre Channel [0c04]: Emulex Corporation Lancer Gen6: LPe32000 
Fibre Channel Host Adapter [10df:e300] (rev 01)
  0001:01:00.0 Fibre Channel [0c04]: Emulex Corporation Lancer-X: LightPulse 
Fibre Channel Host Adapter [10df:e200] (rev 10)
  0001:01:00.1 Fibre Channel [0c04]: Emulex Corporation Lancer-X: LightPulse 
Fibre Channel Host Adapter [10df:e200] (rev 10)
  root@ltciofvtr-firestone1:~# 

  
  Device driver error code:
   [  537.317563] lpfc :01:00.1: 1:0338 IOCB wait timeout error - no wake 
response Data x3c
  [  537.317755] lpfc :01:00.1: 1:(0):0727 TMF FCP_LUN_RESET to TGT 1 LUN 0 
failed (0, 0) iocb_flag x206
  [  537.317934] lpfc :01:00.1: 1:(0):0713 SCSI layer issued Device Reset 
(1, 0) return x2007
  [  537.318005] lpfc :01:00.1: 1:0372 iotag x0 is out off range: max iotag 
(x880)
  [  551.653563] lpfc :01:00.0: 0:(0):0748 abort handler timed out waiting 
for abortng I/O (xri:x149) to complete: ret 0x2003, ID 1, LUN 1
  [  551.653795] lpfc :01:00.0: 0:0372 iotag x0 is out off range: max iotag 
(x880)
  [  598.757557] lpfc :01:00.1: 1:0338 IOCB wait timeout error - no wake 
response Data x3c
  [  598.757766] lpfc :01:00.1: 1:(0):0727 TMF FCP_LUN_RESET to TGT 1 LUN 1 
failed (0, 0) iocb_flag x206
  [  598.757946] lpfc :01:00.1: 1:(0):0713 SCSI layer issued Device

[Kernel-packages] [Bug 1670634] Comment bridged from LTC Bugzilla

--- Comment From heinz-werner_se...@de.ibm.com 2017-03-07 11:44 EDT---
Please provide Debug-Info to this IBM_BOX folder
https://ibm.box.com/s/y10o4u7bcvc6nk7rgk2gfmk039ii5d1i
After Debugging this folder will be deleted.

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

Title:
  blk-mq: possible deadlock on CPU hot(un)plug

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Carsten Jacobi  - 2017-03-07 03:35:31 ==
  I'm evaluating Ubuntu-Xenial on z for development purposes, the test system 
is installed in an LPAR with one FCP-LUN which is accessable by 4 pathes (all 
pathes are configured).
  The system hangs regularly when I make packages with "pdebuild" using the 
pbuilder packaging suit.
  The local Linux development team helped me out with a pre-analysis that I can 
post here (thanks a lot for that):

  With the default settings and under a certain workload,
  blk_mq seems to get into a presumed "deadlock".
  Possibly this happens on CPU hot(un)plug.

  After the I/O stalled, a dump was pulled manually.
  The following information is from the crash dump pre-analysis.

  $ zgetdump -i dump.0
  General dump info:
Dump format: elf
Version: 1
UTS node name..: mclint
UTS kernel release.: 4.4.0-65-generic
UTS kernel version.: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
System arch: s390x (64 bit)
CPU count (online).: 2
Dump memory range..: 8192 MB
  Memory map:
 - 0001b831afff (7043 MB)
0001b831b000 - 0001 (1149 MB)

  Things look similarly with HWE kernel ubuntu16.04-4.8.0-34.36~16.04.1.

KERNEL: vmlinux.full
  DUMPFILE: dump.0
  CPUS: 2
  DATE: Fri Mar  3 14:31:07 2017
UPTIME: 02:11:20
  LOAD AVERAGE: 13.00, 12.92, 11.37
 TASKS: 411
  NODENAME: mclint
   RELEASE: 4.4.0-65-generic
   VERSION: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
   MACHINE: s390x  (unknown Mhz)
MEMORY: 7.8 GB
 PANIC: ""
   PID: 0
   COMMAND: "swapper/0"
  TASK: bad528  (1 of 2)  [THREAD_INFO: b78000]
   CPU: 0
 STATE: TASK_RUNNING (ACTIVE)
  INFO: no panic task found

  crash> dev -d
  MAJOR GENDISKNAME   REQUEST_QUEUE  TOTAL ASYNC  SYNC   DRV
  ...
  8 1e1d6d800  sda1e1d51210  0 23151 4294944145 
N/A(MQ)
  8 1e4e06800  sdc2081b180 23148 4294944148 
N/A(MQ)
  8 1f07800sdb20c75680 23195 4294944101 
N/A(MQ)
  8 1e4e06000  sdd1e4e31210  0 23099 4294944197 
N/A(MQ)
252 1e1d6c800  dm-0   1e1d51b18  9 1 8 
N/A(MQ)
  ...

  So both dm-mpath and sd have requests pending in their block multiqueue.
  The large numbers of sd look strange and seem to be the unsigned formatting 
of the values shown for async multiplied by -1.

  [0.798256] Linux version 4.4.0-65-generic (buildd@z13-011) (gcc version 
5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #86-Ubuntu SMP Thu Feb 23 
17:54:37 UTC 2017 (Ubuntu 4.4.0-65.86-generic 4.4.49)
  [0.798262] setup: Linux is running natively in 64-bit mode
  [0.798290] setup: Max memory size: 8192MB
  [0.798298] setup: Reserving 196MB of memory at 7996MB for crashkernel 
(System RAM: 7996MB)

  [0.836923] Kernel command line: root=/dev/mapper/mclint_vg-root
  rootflags=subvol=@ crashkernel=196M BOOT_IMAGE=0

  [ 5281.179428] INFO: task xfsaild/dm-11:1604 blocked for more than 120 
seconds.
  [ 5281.179437]   Not tainted 4.4.0-65-generic #86-Ubuntu
  [ 5281.179438] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 5281.179440] xfsaild/dm-11   D 007bcf52 0  1604  2 
0x
  [ 5281.179444]0001e931c230 001a6964 0001e6f9b958 
0001e6f9b9d8
0001e15795f0 0001e6f9b988 00ce8c00 
0001ea805c70
0001ea805c00 00ba5ed0 0001e931c1d0 
0001e1579b20
0001ea805c00 0001e15795f0 0001ea805c00 

007d3978 007bc9f8 0001e6f9b9d8 
0001e6f9ba40
  [ 5281.179454] Call Trace:
  [ 5281.179461] ([<007bc9f8>] __schedule+0x300/0x810)
  [ 5281.179462]  [<007bcf52>] schedule+0x4a/0xb0
  [ 5281.179465]  [<007c02aa>] schedule_timeout+0x232/0x2a8
  [ 5281.179466]  [<007bde50>] wait_for_common+0x110/0x1c8
  [ 5281.179472]  [<0017b602>] flush_work+0x42/0x58
  [ 5281.179564]  [<03ff805e14ba>] xlog_cil_force_lsn+0x7a/0x238 [xfs]
  [ 5281.179589]  [<03ff805dee82>] _xfs_log_force+0x9a/0x2e8 [xfs]
  [

[Kernel-packages] [Bug 1670696] Re: Typo in error msg when no crashkernel memory reservation is set

** Description changed:

  [Impact]
  
   * There is a typo in ERRMSG of function show_mem_usage affecting Xenial
  and Zesty AND Debian.
  
  This should be :
  "show_mem_usage: No memory is reserved for crashkernel!"
  
  instead of :
  "show_mem_usage: No memory is reserved for crashkenrel!"
  
  The typo is located here in src code for Xenial and Zesty (devel
  release) AND Debian:
  
  # filename : makedumpfile.c
  10447 int show_mem_usage(void)
  10448 {
  10449 uint64_t vmcoreinfo_addr, vmcoreinfo_len;
  10450 struct cycle cycle = {0};
  10451
  10452 if (!is_crashkernel_mem_reserved()) {
  10453 ERRMSG("No memory is reserved for crashkenrel!\n");
  10454 return FALSE;
  10455 }
  
  [Test Case]
  
   * Take a system with no crashkernel memory reservation set
   * run command : makedumpfile --mem-usage /proc/kcore
  
   * Error message :
  show_mem_usage: No memory is reserved for crashkenrel!
  
  [Regression Potential]
  
   * No regression, it is a trivial change with no behavioural change.
  
  [Other Info]
  
- * Debian bug : 
+ * Upstream:
+ Patch has been submitted upstream (ML :ke...@lists.infradead.org)
+ 
+ * Debian bug :
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857051

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

Title:
  Typo in error msg when no crashkernel memory reservation is set

Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Xenial:
  In Progress
Status in makedumpfile source package in Zesty:
  In Progress

Bug description:
  [Impact]

   * There is a typo in ERRMSG of function show_mem_usage affecting
  Xenial and Zesty AND Debian.

  This should be :
  "show_mem_usage: No memory is reserved for crashkernel!"

  instead of :
  "show_mem_usage: No memory is reserved for crashkenrel!"

  The typo is located here in src code for Xenial and Zesty (devel
  release) AND Debian:

  # filename : makedumpfile.c
  10447 int show_mem_usage(void)
  10448 {
  10449 uint64_t vmcoreinfo_addr, vmcoreinfo_len;
  10450 struct cycle cycle = {0};
  10451
  10452 if (!is_crashkernel_mem_reserved()) {
  10453 ERRMSG("No memory is reserved for crashkenrel!\n");
  10454 return FALSE;
  10455 }

  [Test Case]

   * Take a system with no crashkernel memory reservation set
   * run command : makedumpfile --mem-usage /proc/kcore

   * Error message :
  show_mem_usage: No memory is reserved for crashkenrel!

  [Regression Potential]

   * No regression, it is a trivial change with no behavioural change.

  [Other Info]

  * Upstream:
  Patch has been submitted upstream (ML :ke...@lists.infradead.org)

  * Debian bug :
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857051

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

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

[Kernel-packages] [Bug 1670634] Re: blk-mq: possible deadlock on CPU hot(un)plug

2017-03-07 Thread Frank Heimes

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: ubuntu-z-systems
   Importance: Undecided => High

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

Title:
  blk-mq: possible deadlock on CPU hot(un)plug

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Carsten Jacobi  - 2017-03-07 03:35:31 ==
  I'm evaluating Ubuntu-Xenial on z for development purposes, the test system 
is installed in an LPAR with one FCP-LUN which is accessable by 4 pathes (all 
pathes are configured).
  The system hangs regularly when I make packages with "pdebuild" using the 
pbuilder packaging suit.
  The local Linux development team helped me out with a pre-analysis that I can 
post here (thanks a lot for that):

  With the default settings and under a certain workload,
  blk_mq seems to get into a presumed "deadlock".
  Possibly this happens on CPU hot(un)plug.

  After the I/O stalled, a dump was pulled manually.
  The following information is from the crash dump pre-analysis.

  $ zgetdump -i dump.0
  General dump info:
Dump format: elf
Version: 1
UTS node name..: mclint
UTS kernel release.: 4.4.0-65-generic
UTS kernel version.: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
System arch: s390x (64 bit)
CPU count (online).: 2
Dump memory range..: 8192 MB
  Memory map:
 - 0001b831afff (7043 MB)
0001b831b000 - 0001 (1149 MB)

  Things look similarly with HWE kernel ubuntu16.04-4.8.0-34.36~16.04.1.

KERNEL: vmlinux.full
  DUMPFILE: dump.0
  CPUS: 2
  DATE: Fri Mar  3 14:31:07 2017
UPTIME: 02:11:20
  LOAD AVERAGE: 13.00, 12.92, 11.37
 TASKS: 411
  NODENAME: mclint
   RELEASE: 4.4.0-65-generic
   VERSION: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
   MACHINE: s390x  (unknown Mhz)
MEMORY: 7.8 GB
 PANIC: ""
   PID: 0
   COMMAND: "swapper/0"
  TASK: bad528  (1 of 2)  [THREAD_INFO: b78000]
   CPU: 0
 STATE: TASK_RUNNING (ACTIVE)
  INFO: no panic task found

  crash> dev -d
  MAJOR GENDISKNAME   REQUEST_QUEUE  TOTAL ASYNC  SYNC   DRV
  ...
  8 1e1d6d800  sda1e1d51210  0 23151 4294944145 
N/A(MQ)
  8 1e4e06800  sdc2081b180 23148 4294944148 
N/A(MQ)
  8 1f07800sdb20c75680 23195 4294944101 
N/A(MQ)
  8 1e4e06000  sdd1e4e31210  0 23099 4294944197 
N/A(MQ)
252 1e1d6c800  dm-0   1e1d51b18  9 1 8 
N/A(MQ)
  ...

  So both dm-mpath and sd have requests pending in their block multiqueue.
  The large numbers of sd look strange and seem to be the unsigned formatting 
of the values shown for async multiplied by -1.

  [0.798256] Linux version 4.4.0-65-generic (buildd@z13-011) (gcc version 
5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #86-Ubuntu SMP Thu Feb 23 
17:54:37 UTC 2017 (Ubuntu 4.4.0-65.86-generic 4.4.49)
  [0.798262] setup: Linux is running natively in 64-bit mode
  [0.798290] setup: Max memory size: 8192MB
  [0.798298] setup: Reserving 196MB of memory at 7996MB for crashkernel 
(System RAM: 7996MB)

  [0.836923] Kernel command line: root=/dev/mapper/mclint_vg-root
  rootflags=subvol=@ crashkernel=196M BOOT_IMAGE=0

  [ 5281.179428] INFO: task xfsaild/dm-11:1604 blocked for more than 120 
seconds.
  [ 5281.179437]   Not tainted 4.4.0-65-generic #86-Ubuntu
  [ 5281.179438] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 5281.179440] xfsaild/dm-11   D 007bcf52 0  1604  2 
0x
  [ 5281.179444]0001e931c230 001a6964 0001e6f9b958 
0001e6f9b9d8
0001e15795f0 0001e6f9b988 00ce8c00 
0001ea805c70
0001ea805c00 00ba5ed0 0001e931c1d0 
0001e1579b20
0001ea805c00 0001e15795f0 0001ea805c00 

007d3978 007bc9f8 0001e6f9b9d8 
0001e6f9ba40
  [ 5281.179454] Call Trace:
  [ 5281.179461] ([<007bc9f8>] __schedule+0x300/0x810)
  [ 5281.179462]  [<007bcf52>] schedule+0x4a/0xb0
  [ 5281.179465]  [<007c02aa>] schedule_timeout+0x232/0x2a8
  [ 5281.179466]  [<007bde50>] wait_for_common+0x110/0x1c8
  [ 5281.179472]  [<0017b602>] flush_work+0x42/0x58
  [ 5281.179564]  [<03ff805e14ba>] xlog_cil_force_lsn+0x7a/0x238 [xfs]
  [ 5281.179589]  [<03ff805dee82>] _xfs_log_force+0x9a/0x2e8 [xfs]
  [ 5281.179615]  [<03ff805df114>] xfs_log_force+0x44/0x100

[Kernel-packages] [Bug 1670696] Re: Typo in error msg when no crashkernel memory reservation is set

Zesty debdiff

** Patch added: "zesty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1670696/+attachment/4832994/+files/zesty_makedumpfile.debdiff

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

Title:
  Typo in error msg when no crashkernel memory reservation is set

Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Xenial:
  In Progress
Status in makedumpfile source package in Zesty:
  In Progress

Bug description:
  [Impact]

   * There is a typo in ERRMSG of function show_mem_usage affecting
  Xenial and Zesty AND Debian.

  This should be :
  "show_mem_usage: No memory is reserved for crashkernel!"

  instead of :
  "show_mem_usage: No memory is reserved for crashkenrel!"

  The typo is located here in src code for Xenial and Zesty (devel
  release) AND Debian:

  # filename : makedumpfile.c
  10447 int show_mem_usage(void)
  10448 {
  10449 uint64_t vmcoreinfo_addr, vmcoreinfo_len;
  10450 struct cycle cycle = {0};
  10451
  10452 if (!is_crashkernel_mem_reserved()) {
  10453 ERRMSG("No memory is reserved for crashkenrel!\n");
  10454 return FALSE;
  10455 }

  [Test Case]

   * Take a system with no crashkernel memory reservation set
   * run command : makedumpfile --mem-usage /proc/kcore

   * Error message :
  show_mem_usage: No memory is reserved for crashkenrel!

  [Regression Potential]

   * No regression, it is a trivial change with no behavioural change.

  [Other Info]

  * Debian bug : 
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857051

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

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

[Kernel-packages] [Bug 1670696] Re: Typo in error msg when no crashkernel memory reservation is set

Xenial debdiff

** Patch added: "xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1670696/+attachment/4832995/+files/xenial_makedumpfile.debdiff

** Description changed:

  [Impact]
  
   * There is a typo in ERRMSG of function show_mem_usage affecting Xenial
  and Zesty AND Debian.
  
  This should be :
  "show_mem_usage: No memory is reserved for crashkernel!"
  
  instead of :
  "show_mem_usage: No memory is reserved for crashkenrel!"
+ 
+ The typo is located here in src code for Xenial and Zesty (devel
+ release) AND Debian:
+ 
+ # filename : makedumpfile.c
+ 10447 int show_mem_usage(void)
+ 10448 {
+ 10449 uint64_t vmcoreinfo_addr, vmcoreinfo_len;
+ 10450 struct cycle cycle = {0};
+ 10451
+ 10452 if (!is_crashkernel_mem_reserved()) {
+ 10453 ERRMSG("No memory is reserved for crashkenrel!\n");
+ 10454 return FALSE;
+ 10455 }
  
  [Test Case]
  
   * Take a system with no crashkernel memory reservation set
   * run command : makedumpfile --mem-usage /proc/kcore
  
   * Error message :
  show_mem_usage: No memory is reserved for crashkenrel!
  
  [Regression Potential]
  
   * No regression, it is a trivial change with no behavioural change.
  
  [Other Info]
  
- The typo is located here in src code for Xenial and Zesty (devel
- release) AND Debian:
- 
- # filename : makedumpfile.c
- 10447 int show_mem_usage(void)
- 10448 {
- 10449 uint64_t vmcoreinfo_addr, vmcoreinfo_len;
- 10450 struct cycle cycle = {0};
- 10451
- 10452 if (!is_crashkernel_mem_reserved()) {
- 10453 ERRMSG("No memory is reserved for crashkenrel!\n");
- 10454 return FALSE;
- 10455 }
- 
- * Debian bug : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857051
+ * Debian bug : 
+ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857051

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

Title:
  Typo in error msg when no crashkernel memory reservation is set

Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Xenial:
  In Progress
Status in makedumpfile source package in Zesty:
  In Progress

Bug description:
  [Impact]

   * There is a typo in ERRMSG of function show_mem_usage affecting
  Xenial and Zesty AND Debian.

  This should be :
  "show_mem_usage: No memory is reserved for crashkernel!"

  instead of :
  "show_mem_usage: No memory is reserved for crashkenrel!"

  The typo is located here in src code for Xenial and Zesty (devel
  release) AND Debian:

  # filename : makedumpfile.c
  10447 int show_mem_usage(void)
  10448 {
  10449 uint64_t vmcoreinfo_addr, vmcoreinfo_len;
  10450 struct cycle cycle = {0};
  10451
  10452 if (!is_crashkernel_mem_reserved()) {
  10453 ERRMSG("No memory is reserved for crashkenrel!\n");
  10454 return FALSE;
  10455 }

  [Test Case]

   * Take a system with no crashkernel memory reservation set
   * run command : makedumpfile --mem-usage /proc/kcore

   * Error message :
  show_mem_usage: No memory is reserved for crashkenrel!

  [Regression Potential]

   * No regression, it is a trivial change with no behavioural change.

  [Other Info]

  * Debian bug : 
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857051

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

-- 
Mailing list: https://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 1670726] [NEW] h-prod does not function across cores

2017-03-07 Thread Michael Hohnbaum

Leann,

A kernel patch request from IBM.

   Michael


On 03/07/2017 07:29 AM, Launchpad Bug Tracker wrote:
> bugproxy (bugproxy) has assigned this bug to you for Ubuntu:
>
> There is a  performance problem issue with h-prod. I can see that h-prod
> calls are only waking hardware threads from a h-cede call when the
> caller is on the same core as the thread being awoken (sibling theads).
> For cross core prods the target thread remains in h-cede until its next
> decrementer interrupt.  That is causing guest OS some significant
> dispatching delays.
>
>   The fix is now upstream as commit 8464c8842de2 ("KVM: PPC: Book3S HV:
> Fix H_PROD to actually wake the target vcpu", 2016-12-06) in v4.11-rc1.
>
> ** Affects: ubuntu
>   Importance: Undecided
>   Assignee: Taco Screen team (taco-screen-team)
>   Status: New
>
>
> ** Tags: architecture-ppc64le bugnameltc-152309 severity-high 
> targetmilestone-inin16042

-- 
Michael Hohnbaum
OIL Program Manager
Power (ppc64el) Development Project Manager
Canonical, Ltd.

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

Title:
  h-prod does not function across cores

Status in linux package in Ubuntu:
  New

Bug description:
  There is a  performance problem issue with h-prod. I can see that
  h-prod calls are only waking hardware threads from a h-cede call when
  the caller is on the same core as the thread being awoken (sibling
  theads).  For cross core prods the target thread remains in h-cede
  until its next decrementer interrupt.  That is causing guest OS some
  significant dispatching delays.

   The fix is now upstream as commit 8464c8842de2 ("KVM: PPC: Book3S HV:
  Fix H_PROD to actually wake the target vcpu", 2016-12-06) in
  v4.11-rc1.

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

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

[Kernel-packages] [Bug 1572801] Re: Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10

2017-03-07 Thread tomsk

So where is fix? There is no fix 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/1572801

Title:
  Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10

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

Bug description:
  Ubuntu 16.04 64bit ISO number 20160420.1
  unity version 7.4.0+16.04.20160415-0ubuntu1
  Ubuntu 16.04 64bit ram usage has increase dramatically over Ubuntu 15.10
  Ubuntu 16.04 ram roughly 1 GB Ubuntu15.10 can be tuned to 420, 450 MB
  Ubuntu 16.04 with unity uses 1GB whereas Kubuntu 16.04 is using 420MB live usb

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.376
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Apr 21 01:44:22 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  GsettingsChanges:
   b'org.compiz.core' b'outputs' b"['1920x1080+0+0']"
   b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 
'place', 'regex', 'resize', 'session', 'snap', 'vpswitch', 'wall', 'animation', 
'commands', 'compiztoolbox', 'copytex', 'fade', 'grid', 'imgpng', 'mousepoll', 
'move', 'scale', 'unitymtgrabhandles', 'workarounds', 'expo', 'ezoom', 
'unityshell']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- 
cdrom-detect/try-usb=true noprompt
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/03/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2004
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2004:bd06/03/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PLUS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Apr 21 01:37:17 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Kernel-packages] [Bug 1670696] Re: Typo in error msg when no crashkernel memory reservation is set

** Changed in: makedumpfile (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: makedumpfile (Ubuntu Xenial)
 Assignee: (unassigned) => Eric Desrochers (slashd)

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

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

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

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

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

Title:
  Typo in error msg when no crashkernel memory reservation is set

Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Xenial:
  In Progress
Status in makedumpfile source package in Zesty:
  In Progress

Bug description:
  [Impact]

   * There is a typo in ERRMSG of function show_mem_usage affecting
  Xenial and Zesty AND Debian.

  This should be :
  "show_mem_usage: No memory is reserved for crashkernel!"

  instead of :
  "show_mem_usage: No memory is reserved for crashkenrel!"

  [Test Case]

   * Take a system with no crashkernel memory reservation set
   * run command : makedumpfile --mem-usage /proc/kcore

   * Error message :
  show_mem_usage: No memory is reserved for crashkenrel!

  [Regression Potential]

   * No regression, it is a trivial change with no behavioural change.

  [Other Info]

  The typo is located here in src code for Xenial and Zesty (devel
  release) AND Debian:

  # filename : makedumpfile.c
  10447 int show_mem_usage(void)
  10448 {
  10449 uint64_t vmcoreinfo_addr, vmcoreinfo_len;
  10450 struct cycle cycle = {0};
  10451
  10452 if (!is_crashkernel_mem_reserved()) {
  10453 ERRMSG("No memory is reserved for crashkenrel!\n");
  10454 return FALSE;
  10455 }

  * Debian bug : https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=857051

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

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

[Kernel-packages] [Bug 1670726] [NEW] h-prod does not function across cores

Public bug reported:

There is a  performance problem issue with h-prod. I can see that h-prod
calls are only waking hardware threads from a h-cede call when the
caller is on the same core as the thread being awoken (sibling theads).
For cross core prods the target thread remains in h-cede until its next
decrementer interrupt.  That is causing guest OS some significant
dispatching delays.

 The fix is now upstream as commit 8464c8842de2 ("KVM: PPC: Book3S HV:
Fix H_PROD to actually wake the target vcpu", 2016-12-06) in v4.11-rc1.

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


** Tags: architecture-ppc64le bugnameltc-152309 severity-high 
targetmilestone-inin16042

** Tags added: architecture-ppc64le bugnameltc-152309 severity-high
targetmilestone-inin16042

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

Title:
  h-prod does not function across cores

Status in linux package in Ubuntu:
  New

Bug description:
  There is a  performance problem issue with h-prod. I can see that
  h-prod calls are only waking hardware threads from a h-cede call when
  the caller is on the same core as the thread being awoken (sibling
  theads).  For cross core prods the target thread remains in h-cede
  until its next decrementer interrupt.  That is causing guest OS some
  significant dispatching delays.

   The fix is now upstream as commit 8464c8842de2 ("KVM: PPC: Book3S HV:
  Fix H_PROD to actually wake the target vcpu", 2016-12-06) in
  v4.11-rc1.

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

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

[Kernel-packages] [Bug 1670726] [NEW] h-prod does not function across cores

You have been subscribed to a public bug:

There is a  performance problem issue with h-prod. I can see that h-prod
calls are only waking hardware threads from a h-cede call when the
caller is on the same core as the thread being awoken (sibling theads).
For cross core prods the target thread remains in h-cede until its next
decrementer interrupt.  That is causing guest OS some significant
dispatching delays.

 The fix is now upstream as commit 8464c8842de2 ("KVM: PPC: Book3S HV:
Fix H_PROD to actually wake the target vcpu", 2016-12-06) in v4.11-rc1.

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


** Tags: architecture-ppc64le bugnameltc-152309 severity-high 
targetmilestone-inin16042
-- 
h-prod does not function across cores
https://bugs.launchpad.net/bugs/1670726
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 1667081] Re: Nvlink2: Additional patches

2017-03-07 Thread Seth Forshee

https://lists.ubuntu.com/archives/kernel-team/2017-March/082880.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/1667081

Title:
  Nvlink2: Additional patches

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

Bug description:
  Hello Canonical,

  Could you please integrate the patches to enable NVLink2 in Ubuntu?

  They are, so far:

  
   commit 616badd2fb499320d3ac3b54462f55dededd0e0f
Author: Alistair Popple 
Date:   Tue Jan 10 15:41:44 2017 +1100

powerpc/powernv: Use OPAL call for TCE kill on NVLink2

Add detection of NPU2 PHBs. NPU2/NVLink2 has a different register
layout for the TCE kill register therefore TCE invalidation should be
done via the OPAL call rather than using the register directly as it
is for PHB3 and NVLink1. This changes TCE invalidation to use the OPAL
call in the case of a NPU2 PHB model.

  
  commit 1d0761d2557d1540727723e4f05395d53321d555
  Author: Alistair Popple 
  Date:   Wed Dec 14 13:36:51 2016 +1100

  powerpc/powernv: Initialise nest mmu
  
  POWER9 contains an off core mmu called the nest mmu (NMMU). This is
  used by other hardware units on the chip to translate virtual
  addresses into real addresses. The unit attempting an address
  translation provides the majority of the context required for the
  translation request except for the base address of the partition table
  (ie. the PTCR) which needs to be programmed into the NMMU.
  
  This patch adds a call to OPAL to set the PTCR for the nest mmu in
  opal_init().
  

  These patches are, still, in the powerpc-next tree.

  == Comment: #2 - Breno Henrique Leitao  - 2017-02-22 
13:33:59 ==
  In order to support NVLink2, the memory hotplugs should be applied also, they 
are:

  0d0a4bc powerpc/mm: unstub radix__vmemmap_remove_mapping()
  4b5d62c powerpc/mm: add radix__remove_section_mapping()
  6cc2734 powerpc/mm: add radix__create_section_mapping()
  b5200ec powerpc/mm: refactor radix physical page mapping
  32b53c0 powerpc/mm: Fix memory hotplug BUG() on radix
  c3352cb dt: add documentation of "hotpluggable" memory property
  41a9ada of/fdt: mark hotpluggable memory
  114cf3c mm: enable CONFIG_MOVABLE_NODE on non-x86 arches
  39fa104 mm: remove x86-only restriction of movable_node
  4a3bac4 powerpc/mm: allow memory hotplug into a memoryless node

  Note that you need to set CONFIG_MOVABLE_NODE=y.

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

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

[Kernel-packages] [Bug 1670696] Re: Typo in error msg when no crashkernel memory reservation is set

Patch has been submitted to Debian

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

Title:
  Typo in error msg when no crashkernel memory reservation is set

Status in makedumpfile package in Ubuntu:
  New
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Zesty:
  New

Bug description:
  [Impact]

   * There is a typo in ERRMSG of function show_mem_usage affecting
  Xenial and Zesty AND Debian.

  This should be :
  "show_mem_usage: No memory is reserved for crashkernel!"

  instead of :
  "show_mem_usage: No memory is reserved for crashkenrel!"

  [Test Case]

   * Take a system with no crashkernel memory reservation set
   * run command : makedumpfile --mem-usage /proc/kcore

   * Error message :
  show_mem_usage: No memory is reserved for crashkenrel!

  [Regression Potential]

   * No regression, it is a trivial change with no behavioural change.

  [Other Info]

  The typo is located here in src code for Xenial and Zesty (devel
  release) AND Debian:

  # filename : makedumpfile.c
  10447 int show_mem_usage(void)
  10448 {
  10449 uint64_t vmcoreinfo_addr, vmcoreinfo_len;
  10450 struct cycle cycle = {0};
  10451
  10452 if (!is_crashkernel_mem_reserved()) {
  10453 ERRMSG("No memory is reserved for crashkenrel!\n");
  10454 return FALSE;
  10455 }

  * Debian bug : https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=857051

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

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

[Kernel-packages] [Bug 1670696] Re: Typo in error msg when no crashkernel memory reservation is set

** Description changed:

  [Impact]
  
   * There is a typo in ERRMSG of function show_mem_usage affecting Xenial
  and Zesty AND Debian.
  
  This should be :
- "show_mem_usage: No memory is reserved for crashkernel!" 
+ "show_mem_usage: No memory is reserved for crashkernel!"
  
  instead of :
  "show_mem_usage: No memory is reserved for crashkenrel!"
  
  [Test Case]
  
   * Take a system with no crashkernel memory reservation set
   * run command : makedumpfile --mem-usage /proc/kcore
  
   * Error message :
  show_mem_usage: No memory is reserved for crashkenrel!
  
  [Regression Potential]
  
   * No regression, it is a trivial change with no behavioural change.
  
  [Other Info]
  
  The typo is located here in src code for Xenial and Zesty (devel
  release) AND Debian:
  
  # filename : makedumpfile.c
  10447 int show_mem_usage(void)
  10448 {
  10449 uint64_t vmcoreinfo_addr, vmcoreinfo_len;
  10450 struct cycle cycle = {0};
  10451
  10452 if (!is_crashkernel_mem_reserved()) {
  10453 ERRMSG("No memory is reserved for crashkenrel!\n");
  10454 return FALSE;
  10455 }
+ 
+ * Debian bug : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857051

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

Title:
  Typo in error msg when no crashkernel memory reservation is set

Status in makedumpfile package in Ubuntu:
  New
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Zesty:
  New

Bug description:
  [Impact]

   * There is a typo in ERRMSG of function show_mem_usage affecting
  Xenial and Zesty AND Debian.

  This should be :
  "show_mem_usage: No memory is reserved for crashkernel!"

  instead of :
  "show_mem_usage: No memory is reserved for crashkenrel!"

  [Test Case]

   * Take a system with no crashkernel memory reservation set
   * run command : makedumpfile --mem-usage /proc/kcore

   * Error message :
  show_mem_usage: No memory is reserved for crashkenrel!

  [Regression Potential]

   * No regression, it is a trivial change with no behavioural change.

  [Other Info]

  The typo is located here in src code for Xenial and Zesty (devel
  release) AND Debian:

  # filename : makedumpfile.c
  10447 int show_mem_usage(void)
  10448 {
  10449 uint64_t vmcoreinfo_addr, vmcoreinfo_len;
  10450 struct cycle cycle = {0};
  10451
  10452 if (!is_crashkernel_mem_reserved()) {
  10453 ERRMSG("No memory is reserved for crashkenrel!\n");
  10454 return FALSE;
  10455 }

  * Debian bug : https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=857051

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

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

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

This change was made by a bot.

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

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

Title:
  Kernel Call Trace After Disabling an ath10k Wireless Device

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Disabled a wireless adapter via NetworkManager. Got a kernel trace in
  dmesg.

  3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
  Network Adapter (rev 32)

  uname -r
  4.10.0-9-generic

  https://paste.ubuntu.com/24131142/

  There are also usb hot-plug messages in between ath10k related ones -
  this is because I disabled a wireless adapter and immediately plugged
  in a usb type-c dock so don't mind those.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-9-generic 4.10.0-9.11
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dima   3007 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar  7 17:28:37 2017
  InstallationDate: Installed on 2017-02-27 (8 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
  MachineType: Razer Blade
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-9-generic.efi.signed 
root=UUID=3f515c94-cd91-48b4-80f6-84ec24cb7b8f ro rootflags=subvol=@ quiet 
button.lid_init_state=open pcie_aspm=off
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-9-generic N/A
   linux-backports-modules-4.10.0-9-generic  N/A
   linux-firmware1.163
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2017
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.00
  dmi.board.name: Razer
  dmi.board.vendor: Razer
  dmi.chassis.type: 9
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr1.00:bd01/10/2017:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
  dmi.product.name: Blade
  dmi.product.version: 6.06
  dmi.sys.vendor: Razer

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

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

[Kernel-packages] [Bug 1670696] Re: Typo in error msg when no crashkernel memory reservation is set

2017-03-07 Thread Louis Bouchard

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

** Also affects: makedumpfile (Ubuntu Zesty)
   Importance: Low
 Assignee: Eric Desrochers (slashd)
   Status: New

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

Title:
  Typo in error msg when no crashkernel memory reservation is set

Status in makedumpfile package in Ubuntu:
  New
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Zesty:
  New

Bug description:
  [Impact]

   * There is a typo in ERRMSG of function show_mem_usage affecting
  Xenial and Zesty AND Debian.

  This should be :
  "show_mem_usage: No memory is reserved for crashkernel!" 

  instead of :
  "show_mem_usage: No memory is reserved for crashkenrel!"

  [Test Case]

   * Take a system with no crashkernel memory reservation set
   * run command : makedumpfile --mem-usage /proc/kcore

   * Error message :
  show_mem_usage: No memory is reserved for crashkenrel!

  [Regression Potential]

   * No regression, it is a trivial change with no behavioural change.

  [Other Info]

  The typo is located here in src code for Xenial and Zesty (devel
  release) AND Debian:

  # filename : makedumpfile.c
  10447 int show_mem_usage(void)
  10448 {
  10449 uint64_t vmcoreinfo_addr, vmcoreinfo_len;
  10450 struct cycle cycle = {0};
  10451
  10452 if (!is_crashkernel_mem_reserved()) {
  10453 ERRMSG("No memory is reserved for crashkenrel!\n");
  10454 return FALSE;
  10455 }

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

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

[Kernel-packages] [Bug 1670696] Re: Error msg typo when no crashkernel memory reservation

** Description changed:

  [Impact]
  
   * There is a typo in ERRMSG of function show_mem_usage affecting Xenial
  and Zesty AND Debian.
  
- This should be "show_mem_usage: No memory is reserved for crashkernel!" 
instead of :
- "show_mem_usage: No memory is reserved for crashkenrel!"
+ This should be :
+ "show_mem_usage: No memory is reserved for crashkernel!" 
+ 
+ instead of :
+ "show_mem_usage: No memory is reserved for crashkenrel!"
  
  [Test Case]
  
   * Take a system with no crashkernel memory reservation set
   * run command : makedumpfile --mem-usage /proc/kcore
  
   * Error message :
  show_mem_usage: No memory is reserved for crashkenrel!
  
  [Regression Potential]
  
   * No regression, it is a trivial change with no behavioural change.
  
  [Other Info]
  
  The typo is located here in src code for Xenial and Zesty (devel
  release) AND Debian:
  
  # filename : makedumpfile.c
  10447 int show_mem_usage(void)
  10448 {
  10449 uint64_t vmcoreinfo_addr, vmcoreinfo_len;
  10450 struct cycle cycle = {0};
  10451
  10452 if (!is_crashkernel_mem_reserved()) {
  10453 ERRMSG("No memory is reserved for crashkenrel!\n");
  10454 return FALSE;
  10455 }

** Summary changed:

- Error msg typo when no crashkernel memory reservation
+ Typo in error msg when no crashkernel memory reservation is set

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

Title:
  Typo in error msg when no crashkernel memory reservation is set

Status in makedumpfile package in Ubuntu:
  New

Bug description:
  [Impact]

   * There is a typo in ERRMSG of function show_mem_usage affecting
  Xenial and Zesty AND Debian.

  This should be :
  "show_mem_usage: No memory is reserved for crashkernel!" 

  instead of :
  "show_mem_usage: No memory is reserved for crashkenrel!"

  [Test Case]

   * Take a system with no crashkernel memory reservation set
   * run command : makedumpfile --mem-usage /proc/kcore

   * Error message :
  show_mem_usage: No memory is reserved for crashkenrel!

  [Regression Potential]

   * No regression, it is a trivial change with no behavioural change.

  [Other Info]

  The typo is located here in src code for Xenial and Zesty (devel
  release) AND Debian:

  # filename : makedumpfile.c
  10447 int show_mem_usage(void)
  10448 {
  10449 uint64_t vmcoreinfo_addr, vmcoreinfo_len;
  10450 struct cycle cycle = {0};
  10451
  10452 if (!is_crashkernel_mem_reserved()) {
  10453 ERRMSG("No memory is reserved for crashkenrel!\n");
  10454 return FALSE;
  10455 }

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

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

[Kernel-packages] [Bug 1670706] [NEW] Kernel Call Trace After Disabling an ath10k Wireless Device

2017-03-07 Thread Dmitrii Shcherbakov

Public bug reported:

Disabled a wireless adapter via NetworkManager. Got a kernel trace in
dmesg.

3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
Network Adapter (rev 32)

uname -r
4.10.0-9-generic

https://paste.ubuntu.com/24131142/

There are also usb hot-plug messages in between ath10k related ones -
this is because I disabled a wireless adapter and immediately plugged in
a usb type-c dock so don't mind those.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-9-generic 4.10.0-9.11
ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
Uname: Linux 4.10.0-9-generic x86_64
NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dima   3007 F pulseaudio
CurrentDesktop: Unity:Unity7
Date: Tue Mar  7 17:28:37 2017
InstallationDate: Installed on 2017-02-27 (8 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
MachineType: Razer Blade
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-9-generic.efi.signed 
root=UUID=3f515c94-cd91-48b4-80f6-84ec24cb7b8f ro rootflags=subvol=@ quiet 
button.lid_init_state=open pcie_aspm=off
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-9-generic N/A
 linux-backports-modules-4.10.0-9-generic  N/A
 linux-firmware1.163
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/10/2017
dmi.bios.vendor: Razer
dmi.bios.version: 1.00
dmi.board.name: Razer
dmi.board.vendor: Razer
dmi.chassis.type: 9
dmi.chassis.vendor: Razer
dmi.modalias: 
dmi:bvnRazer:bvr1.00:bd01/10/2017:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
dmi.product.name: Blade
dmi.product.version: 6.06
dmi.sys.vendor: Razer

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


** Tags: amd64 apport-bug zesty

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

Title:
  Kernel Call Trace After Disabling an ath10k Wireless Device

Status in linux package in Ubuntu:
  New

Bug description:
  Disabled a wireless adapter via NetworkManager. Got a kernel trace in
  dmesg.

  3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
  Network Adapter (rev 32)

  uname -r
  4.10.0-9-generic

  https://paste.ubuntu.com/24131142/

  There are also usb hot-plug messages in between ath10k related ones -
  this is because I disabled a wireless adapter and immediately plugged
  in a usb type-c dock so don't mind those.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-9-generic 4.10.0-9.11
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dima   3007 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar  7 17:28:37 2017
  InstallationDate: Installed on 2017-02-27 (8 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
  MachineType: Razer Blade
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-9-generic.efi.signed 
root=UUID=3f515c94-cd91-48b4-80f6-84ec24cb7b8f ro rootflags=subvol=@ quiet 
button.lid_init_state=open pcie_aspm=off
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-9-generic N/A
   linux-backports-modules-4.10.0-9-generic  N/A
   linux-firmware1.163
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2017
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.00
  dmi.board.name: Razer
  dmi.board.vendor: Razer
  dmi.chassis.type: 9
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr1.00:bd01/10/2017:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
  dmi.product.name: Blade
  dmi.product.version: 6.06
  dmi.sys.vendor: Razer

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

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

[Kernel-packages] [Bug 1670696] [NEW] Error msg typo when no crashkernel memory reservation

Public bug reported:

[Impact]

 * There is a typo in ERRMSG of function show_mem_usage affecting Xenial
and Zesty AND Debian.

This should be "show_mem_usage: No memory is reserved for crashkernel!" 
instead of :
"show_mem_usage: No memory is reserved for crashkenrel!"

[Test Case]

 * Take a system with no crashkernel memory reservation set
 * run command : makedumpfile --mem-usage /proc/kcore

 * Error message :
show_mem_usage: No memory is reserved for crashkenrel!

[Regression Potential]

 * No regression, it is a trivial change with no behavioural change.

[Other Info]

The typo is located here in src code for Xenial and Zesty (devel
release) AND Debian:

# filename : makedumpfile.c
10447 int show_mem_usage(void)
10448 {
10449 uint64_t vmcoreinfo_addr, vmcoreinfo_len;
10450 struct cycle cycle = {0};
10451
10452 if (!is_crashkernel_mem_reserved()) {
10453 ERRMSG("No memory is reserved for crashkenrel!\n");
10454 return FALSE;
10455 }

** Affects: makedumpfile (Ubuntu)
 Importance: Low
 Assignee: Eric Desrochers (slashd)
 Status: New

** Changed in: makedumpfile (Ubuntu)
   Importance: Undecided => Low

** Changed in: makedumpfile (Ubuntu)
 Assignee: (unassigned) => Eric Desrochers (slashd)

** Description changed:

  [Impact]
  
-  * There is a typo in ERRMSG of function show_mem_usage affecting Xenial and 
Zesty.
-
- This should be "show_mem_usage: No memory is reserved for crashkernel!" 
instead of :
- "show_mem_usage: No memory is reserved for crashkenrel!"
+  * There is a typo in ERRMSG of function show_mem_usage affecting Xenial
+ and Zesty AND Debian.
+ 
+ This should be "show_mem_usage: No memory is reserved for crashkernel!" 
instead of :
+ "show_mem_usage: No memory is reserved for crashkenrel!"
  
  [Test Case]
  
-  * Take a system with no crashkernel memory reservation set
-  * run command : makedumpfile --mem-usage /proc/kcore
+  * Take a system with no crashkernel memory reservation set
+  * run command : makedumpfile --mem-usage /proc/kcore
  
-  * Error message :
+  * Error message :
  show_mem_usage: No memory is reserved for crashkenrel!
  
+ [Regression Potential]
  
- [Regression Potential] 
- 
-  * No regression, it is a trivial change with no behavioural change.
+  * No regression, it is a trivial change with no behavioural change.
  
  [Other Info]
  
  The typo is located here in src code for Xenial and Zesty (devel
- release) :
+ release) AND Debian:
  
  # filename : makedumpfile.c
  10447 int show_mem_usage(void)
  10448 {
  10449 uint64_t vmcoreinfo_addr, vmcoreinfo_len;
  10450 struct cycle cycle = {0};
- 10451 
+ 10451
  10452 if (!is_crashkernel_mem_reserved()) {
  10453 ERRMSG("No memory is reserved for crashkenrel!\n");
  10454 return FALSE;
  10455 }

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

Title:
  Error msg typo when no crashkernel memory reservation

Status in makedumpfile package in Ubuntu:
  New

Bug description:
  [Impact]

   * There is a typo in ERRMSG of function show_mem_usage affecting
  Xenial and Zesty AND Debian.

  This should be "show_mem_usage: No memory is reserved for crashkernel!" 
instead of :
  "show_mem_usage: No memory is reserved for crashkenrel!"

  [Test Case]

   * Take a system with no crashkernel memory reservation set
   * run command : makedumpfile --mem-usage /proc/kcore

   * Error message :
  show_mem_usage: No memory is reserved for crashkenrel!

  [Regression Potential]

   * No regression, it is a trivial change with no behavioural change.

  [Other Info]

  The typo is located here in src code for Xenial and Zesty (devel
  release) AND Debian:

  # filename : makedumpfile.c
  10447 int show_mem_usage(void)
  10448 {
  10449 uint64_t vmcoreinfo_addr, vmcoreinfo_len;
  10450 struct cycle cycle = {0};
  10451
  10452 if (!is_crashkernel_mem_reserved()) {
  10453 ERRMSG("No memory is reserved for crashkenrel!\n");
  10454 return FALSE;
  10455 }

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

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

[Kernel-packages] [Bug 1651248] Comment bridged from LTC Bugzilla

--- Comment From lagar...@br.ibm.com 2017-03-07 09:03 EDT---
Making Carol's comment public

---

I ran for 5 days with 4.8.0-40-generic and 2 guests with 8 VFs each
guest and it ran ok.

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

Title:
  Ubuntu16.10-KVM:Big configuration with multiple guests running SRIOV
  VFs caused KVM host hung and all KVM guests down.

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  Hello Canonical.

  This appears to be related to LP1636330

  There are additional patches we would like picked up once they
  accepted upstream:

  http://www.spinics.net/lists/kvm/msg141747.html

  [PATCH 1/5] KVM: PPC: XICS cleanup: remove XICS_RM_REJECT
  [PATCH 2/5] KVM: PPC: XICS: correct the real mode ICP rejecting counter
  [PATCH 3/5] KVM: PPC: XICS: Fix potential resend twice issue
  [PATCH 4/5] KVM: PPC: XICS: Implement ICS P/Q states
  [PATCH 5/5] KVM: PPC: XICS: Don't lock twice when doing check resend

  
  Bug history context:

  == Comment: #1 - Application Cdeadmin  - 2016-10-17 11:05:07 ==
   State: Open by: nguyenp on 17 October 2016 09:54:13 

  Ubuntu16.10-KVM host:
  =
  tul612p01.aus.stglabs.ibm.com

  Problem Description:
  ===
  I set up a big configure with multiple guests running SRIOV on tul612fp1 
system. For VFs, I created 64 of them on Ubuntu16.10-KVM host (32 VFs per 
port). I have 6 guests total (mix of ubuntu16.10 and ubuntu16.04.01 guests). I 
assigned 4 VFs for each guest.

  I kicked off network tests on VFs on all guests late Friday night. The test 
ran good on Friday night then it all failed on sometime on Saturday night. 
Right now, all guests are currently are down. Another bad part is that the 
Ubuntu-KVM host is currently hung. So the whole system is very much down. I 
could not get to neither the KVM host nor any guest.
   
  I have talked to my team leads, Siraj I. and Brian C. about the problem this 
morning. They want me to open the defect so that I/O developer to looking into 
the SRIOV problem on Ubuntu16.10-KVM again.

  == Comment: #11 - Paul Nguyen - 2016-10-18 17:55:40 ==
  Worked with Carol earlier today on the SRIOV configuration on this tul612 
system.  Thanks for your help, Carol !

  I just want to document the differences of this configuration .vs. previous 
run configuration. So that we can keep track of what we have tried.
   

  Here are the differences:

  1) In this configuration, Carol installed patch driver on KVM host to
  avoid the BUG_ON.

  2) To avoid missing interrupt issue, Carol told me to reduce the
  number of VFs to 16 VFs per port. (on previous run, I had 32 VFs per
  port which was 64 VFs total for 2 ports of the adapter)

  3) Also Carol wanted to reduce number of guests down to 4 guests.
(on previous run, I had 6 guests running and 4 VFs per guest)

  4) Carol also configured NUMA for the 4 guests.
 
16

  


  
  All SRIOV tests have been running good for about 3 hours already.  Let's see 
how long it hit the problem.

  == Comment: #12 - Paul Nguyen - 2016-10-19 10:15:50 ==
  I have 4 guests running SRIOV and 2 guests hit with TX timeout problem last 
night.  The other 2 guests seem running fine.

  
  tul612p05_unbuntu1610 guest:
  
  tul612p05.aus.stglabs.ibm.com

  [Tue Oct 18 15:15:42 2016] nfsd: peername failed (err 107)!
  [Tue Oct 18 16:04:06 2016] hrtimer: interrupt took 12062308 ns
  [Wed Oct 19 00:28:52 2016] NETDEV WATCHDOG: enp0s4 (mlx5_core): transmit 
queue 2 timed out
  [Wed Oct 19 00:28:52 2016] [ cut here ]
  [Wed Oct 19 00:28:52 2016] WARNING: CPU: 13 PID: 28503 at 
/build/linux-PXWOzW/linux-4.8.0/net/sched/sch_generic.c:316 
dev_watchdog+0x380/0x390
  [Wed Oct 19 00:28:52 2016] Modules linked in: iptable_filter rdma_ucm(OE) 
ib_ucm(OE) rdma_cm(OE) iw_cm(OE) configfs ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) 
ib_umad(OE) mlx5_ib(OE) mlx4_ib(OE) ib_sa(OE) ib_mad(OE) ib_core(OE) 
ib_addr(OE) ib_netlink(OE) mlx4_en(OE) mlx4_core(OE) vmx_crypto binfmt_misc 
nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 ibmvscsi 
crc32c_vpmsum mlx5_core(OE) mlx_compat(OE)
  [Wed Oct 19 00:28:52 2016] CPU: 13 PID: 28503 Comm: hxecpu Tainted: G 
  OE   4.8.0-22-generic #24-Ubuntu
  [Wed Oct 19 00:28:52 2016] task: c001db237000 task.stack: c001db294000
  [Wed Oct 19 00:28:52 2016] NIP: c0a4e7a0 LR: c0a4e79c CTR: 

  [Wed Oct 19 00:28:52 2016] REGS: c001db297820 TRAP: 0700   Tainted: G 
  OE(4.8.0-22-generic)
  [Wed Oct 19 00:28:52 2016] MSR: 80029033   CR: 
22000822  XER: 2000
  [Wed Oct 19 00:28:52 2016]

[Kernel-packages] [Bug 1669127] kernel03 (s390x.zVM) - tests ran: 10, failed: 1

tests ran:  10, failed: 1;
  
http://kernel.ubuntu.com/testing/4.10.0-11.13-generic/kernel03__4.10.0-11.13__2017-03-07_13-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/1669127

Title:
  linux: 4.10.0-11.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
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:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.10.0-11.13 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 --
  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-development-workflow/+bug/1669127/+subscriptions

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

[Kernel-packages] [Bug 1667081] Re: Nvlink2: Additional patches

2017-03-07 Thread Seth Forshee

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

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

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

** Changed in: linux (Ubuntu Yakkety)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  Nvlink2: Additional patches

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

Bug description:
  Hello Canonical,

  Could you please integrate the patches to enable NVLink2 in Ubuntu?

  They are, so far:

  
   commit 616badd2fb499320d3ac3b54462f55dededd0e0f
Author: Alistair Popple 
Date:   Tue Jan 10 15:41:44 2017 +1100

powerpc/powernv: Use OPAL call for TCE kill on NVLink2

Add detection of NPU2 PHBs. NPU2/NVLink2 has a different register
layout for the TCE kill register therefore TCE invalidation should be
done via the OPAL call rather than using the register directly as it
is for PHB3 and NVLink1. This changes TCE invalidation to use the OPAL
call in the case of a NPU2 PHB model.

  
  commit 1d0761d2557d1540727723e4f05395d53321d555
  Author: Alistair Popple 
  Date:   Wed Dec 14 13:36:51 2016 +1100

  powerpc/powernv: Initialise nest mmu
  
  POWER9 contains an off core mmu called the nest mmu (NMMU). This is
  used by other hardware units on the chip to translate virtual
  addresses into real addresses. The unit attempting an address
  translation provides the majority of the context required for the
  translation request except for the base address of the partition table
  (ie. the PTCR) which needs to be programmed into the NMMU.
  
  This patch adds a call to OPAL to set the PTCR for the nest mmu in
  opal_init().
  

  These patches are, still, in the powerpc-next tree.

  == Comment: #2 - Breno Henrique Leitao  - 2017-02-22 
13:33:59 ==
  In order to support NVLink2, the memory hotplugs should be applied also, they 
are:

  0d0a4bc powerpc/mm: unstub radix__vmemmap_remove_mapping()
  4b5d62c powerpc/mm: add radix__remove_section_mapping()
  6cc2734 powerpc/mm: add radix__create_section_mapping()
  b5200ec powerpc/mm: refactor radix physical page mapping
  32b53c0 powerpc/mm: Fix memory hotplug BUG() on radix
  c3352cb dt: add documentation of "hotpluggable" memory property
  41a9ada of/fdt: mark hotpluggable memory
  114cf3c mm: enable CONFIG_MOVABLE_NODE on non-x86 arches
  39fa104 mm: remove x86-only restriction of movable_node
  4a3bac4 powerpc/mm: allow memory hotplug into a memoryless node

  Note that you need to set CONFIG_MOVABLE_NODE=y.

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

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

[Kernel-packages] [Bug 1669127] kernel03 (s390x.zVM) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-11.13-generic/kernel03__4.10.0-11.13__2017-03-07_12-52-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/1669127

Title:
  linux: 4.10.0-11.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
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:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.10.0-11.13 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 --
  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-development-workflow/+bug/1669127/+subscriptions

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

[Kernel-packages] [Bug 1670634] Re: blk-mq: possible deadlock on CPU hot(un)plug

2017-03-07 Thread Frank Heimes

** Tags removed: bot-comment
** Tags added: s390x

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

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

Title:
  blk-mq: possible deadlock on CPU hot(un)plug

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Carsten Jacobi  - 2017-03-07 03:35:31 ==
  I'm evaluating Ubuntu-Xenial on z for development purposes, the test system 
is installed in an LPAR with one FCP-LUN which is accessable by 4 pathes (all 
pathes are configured).
  The system hangs regularly when I make packages with "pdebuild" using the 
pbuilder packaging suit.
  The local Linux development team helped me out with a pre-analysis that I can 
post here (thanks a lot for that):

  With the default settings and under a certain workload,
  blk_mq seems to get into a presumed "deadlock".
  Possibly this happens on CPU hot(un)plug.

  After the I/O stalled, a dump was pulled manually.
  The following information is from the crash dump pre-analysis.

  $ zgetdump -i dump.0
  General dump info:
Dump format: elf
Version: 1
UTS node name..: mclint
UTS kernel release.: 4.4.0-65-generic
UTS kernel version.: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
System arch: s390x (64 bit)
CPU count (online).: 2
Dump memory range..: 8192 MB
  Memory map:
 - 0001b831afff (7043 MB)
0001b831b000 - 0001 (1149 MB)

  Things look similarly with HWE kernel ubuntu16.04-4.8.0-34.36~16.04.1.

KERNEL: vmlinux.full
  DUMPFILE: dump.0
  CPUS: 2
  DATE: Fri Mar  3 14:31:07 2017
UPTIME: 02:11:20
  LOAD AVERAGE: 13.00, 12.92, 11.37
 TASKS: 411
  NODENAME: mclint
   RELEASE: 4.4.0-65-generic
   VERSION: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
   MACHINE: s390x  (unknown Mhz)
MEMORY: 7.8 GB
 PANIC: ""
   PID: 0
   COMMAND: "swapper/0"
  TASK: bad528  (1 of 2)  [THREAD_INFO: b78000]
   CPU: 0
 STATE: TASK_RUNNING (ACTIVE)
  INFO: no panic task found

  crash> dev -d
  MAJOR GENDISKNAME   REQUEST_QUEUE  TOTAL ASYNC  SYNC   DRV
  ...
  8 1e1d6d800  sda1e1d51210  0 23151 4294944145 
N/A(MQ)
  8 1e4e06800  sdc2081b180 23148 4294944148 
N/A(MQ)
  8 1f07800sdb20c75680 23195 4294944101 
N/A(MQ)
  8 1e4e06000  sdd1e4e31210  0 23099 4294944197 
N/A(MQ)
252 1e1d6c800  dm-0   1e1d51b18  9 1 8 
N/A(MQ)
  ...

  So both dm-mpath and sd have requests pending in their block multiqueue.
  The large numbers of sd look strange and seem to be the unsigned formatting 
of the values shown for async multiplied by -1.

  [0.798256] Linux version 4.4.0-65-generic (buildd@z13-011) (gcc version 
5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #86-Ubuntu SMP Thu Feb 23 
17:54:37 UTC 2017 (Ubuntu 4.4.0-65.86-generic 4.4.49)
  [0.798262] setup: Linux is running natively in 64-bit mode
  [0.798290] setup: Max memory size: 8192MB
  [0.798298] setup: Reserving 196MB of memory at 7996MB for crashkernel 
(System RAM: 7996MB)

  [0.836923] Kernel command line: root=/dev/mapper/mclint_vg-root
  rootflags=subvol=@ crashkernel=196M BOOT_IMAGE=0

  [ 5281.179428] INFO: task xfsaild/dm-11:1604 blocked for more than 120 
seconds.
  [ 5281.179437]   Not tainted 4.4.0-65-generic #86-Ubuntu
  [ 5281.179438] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 5281.179440] xfsaild/dm-11   D 007bcf52 0  1604  2 
0x
  [ 5281.179444]0001e931c230 001a6964 0001e6f9b958 
0001e6f9b9d8
0001e15795f0 0001e6f9b988 00ce8c00 
0001ea805c70
0001ea805c00 00ba5ed0 0001e931c1d0 
0001e1579b20
0001ea805c00 0001e15795f0 0001ea805c00 

007d3978 007bc9f8 0001e6f9b9d8 
0001e6f9ba40
  [ 5281.179454] Call Trace:
  [ 5281.179461] ([<007bc9f8>] __schedule+0x300/0x810)
  [ 5281.179462]  [<007bcf52>] schedule+0x4a/0xb0
  [ 5281.179465]  [<007c02aa>] schedule_timeout+0x232/0x2a8
  [ 5281.179466]  [<007bde50>] wait_for_common+0x110/0x1c8
  [ 5281.179472]  [<0017b602>] flush_work+0x42/0x58
  [ 5281.179564]  [<03ff805e14ba>] xlog_cil_force_lsn+0x7a/0x238 [xfs]
  [ 5281.179589]  [<03ff805dee82>] _xfs_log_force+0x9a/0x2e8 [xfs]
  [ 5281.179615]  [<03ff805df114>] xfs_log_force+0x44/0x100

[Kernel-packages] [Bug 1670634] [NEW] blk-mq: possible deadlock on CPU hot(un)plug

You have been subscribed to a public bug:

== Comment: #0 - Carsten Jacobi  - 2017-03-07 03:35:31 ==
I'm evaluating Ubuntu-Xenial on z for development purposes, the test system is 
installed in an LPAR with one FCP-LUN which is accessable by 4 pathes (all 
pathes are configured).
The system hangs regularly when I make packages with "pdebuild" using the 
pbuilder packaging suit.
The local Linux development team helped me out with a pre-analysis that I can 
post here (thanks a lot for that):

With the default settings and under a certain workload,
blk_mq seems to get into a presumed "deadlock".
Possibly this happens on CPU hot(un)plug.

After the I/O stalled, a dump was pulled manually.
The following information is from the crash dump pre-analysis.

$ zgetdump -i dump.0
General dump info:
  Dump format: elf
  Version: 1
  UTS node name..: mclint
  UTS kernel release.: 4.4.0-65-generic
  UTS kernel version.: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
  System arch: s390x (64 bit)
  CPU count (online).: 2
  Dump memory range..: 8192 MB
Memory map:
   - 0001b831afff (7043 MB)
  0001b831b000 - 0001 (1149 MB)

Things look similarly with HWE kernel ubuntu16.04-4.8.0-34.36~16.04.1.

  KERNEL: vmlinux.full
DUMPFILE: dump.0
CPUS: 2
DATE: Fri Mar  3 14:31:07 2017
  UPTIME: 02:11:20
LOAD AVERAGE: 13.00, 12.92, 11.37
   TASKS: 411
NODENAME: mclint
 RELEASE: 4.4.0-65-generic
 VERSION: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
 MACHINE: s390x  (unknown Mhz)
  MEMORY: 7.8 GB
   PANIC: ""
 PID: 0
 COMMAND: "swapper/0"
TASK: bad528  (1 of 2)  [THREAD_INFO: b78000]
 CPU: 0
   STATE: TASK_RUNNING (ACTIVE)
INFO: no panic task found

crash> dev -d
MAJOR GENDISKNAME   REQUEST_QUEUE  TOTAL ASYNC  SYNC   DRV
...
8 1e1d6d800  sda1e1d51210  0 23151 4294944145 
N/A(MQ)
8 1e4e06800  sdc2081b180 23148 4294944148 
N/A(MQ)
8 1f07800sdb20c75680 23195 4294944101 
N/A(MQ)
8 1e4e06000  sdd1e4e31210  0 23099 4294944197 
N/A(MQ)
  252 1e1d6c800  dm-0   1e1d51b18  9 1 8 N/A(MQ)
...

So both dm-mpath and sd have requests pending in their block multiqueue.
The large numbers of sd look strange and seem to be the unsigned formatting of 
the values shown for async multiplied by -1.

[0.798256] Linux version 4.4.0-65-generic (buildd@z13-011) (gcc version 
5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #86-Ubuntu SMP Thu Feb 23 
17:54:37 UTC 2017 (Ubuntu 4.4.0-65.86-generic 4.4.49)
[0.798262] setup: Linux is running natively in 64-bit mode
[0.798290] setup: Max memory size: 8192MB
[0.798298] setup: Reserving 196MB of memory at 7996MB for crashkernel 
(System RAM: 7996MB)

[0.836923] Kernel command line: root=/dev/mapper/mclint_vg-root
rootflags=subvol=@ crashkernel=196M BOOT_IMAGE=0

[ 5281.179428] INFO: task xfsaild/dm-11:1604 blocked for more than 120 seconds.
[ 5281.179437]   Not tainted 4.4.0-65-generic #86-Ubuntu
[ 5281.179438] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[ 5281.179440] xfsaild/dm-11   D 007bcf52 0  1604  2 0x
[ 5281.179444]0001e931c230 001a6964 0001e6f9b958 
0001e6f9b9d8
  0001e15795f0 0001e6f9b988 00ce8c00 
0001ea805c70
  0001ea805c00 00ba5ed0 0001e931c1d0 
0001e1579b20
  0001ea805c00 0001e15795f0 0001ea805c00 

  007d3978 007bc9f8 0001e6f9b9d8 
0001e6f9ba40
[ 5281.179454] Call Trace:
[ 5281.179461] ([<007bc9f8>] __schedule+0x300/0x810)
[ 5281.179462]  [<007bcf52>] schedule+0x4a/0xb0
[ 5281.179465]  [<007c02aa>] schedule_timeout+0x232/0x2a8
[ 5281.179466]  [<007bde50>] wait_for_common+0x110/0x1c8
[ 5281.179472]  [<0017b602>] flush_work+0x42/0x58
[ 5281.179564]  [<03ff805e14ba>] xlog_cil_force_lsn+0x7a/0x238 [xfs]
[ 5281.179589]  [<03ff805dee82>] _xfs_log_force+0x9a/0x2e8 [xfs]
[ 5281.179615]  [<03ff805df114>] xfs_log_force+0x44/0x100 [xfs]
[ 5281.179640]  [<03ff805ec668>] xfsaild+0x170/0x798 [xfs]
[ 5281.179643]  [<0018335a>] kthread+0x10a/0x110
[ 5281.179645]  [<007c0ff6>] kernel_thread_starter+0x6/0xc
[ 5281.179646]  [<007c0ff0>] kernel_thread_starter+0x0/0xc

see below

[ 5281.179664] INFO: task cpuplugd:2260 blocked for more than 120 seconds.
[ 5281.179665]   Not tainted 4.4.0-65-generic #86-Ubuntu
[ 5281.179666] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[ 5281.179668] cpuplugdD 007bcf52 0  2260  1 0x
[ 5281.179670]

[Kernel-packages] [Bug 1669127] kernel03 (s390x.zVM) - tests ran: 3, failed: 0

tests ran:   3, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-11.13-generic/kernel03__4.10.0-11.13__2017-03-07_12-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/1669127

Title:
  linux: 4.10.0-11.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
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:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.10.0-11.13 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 --
  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-development-workflow/+bug/1669127/+subscriptions

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

[Kernel-packages] [Bug 1669127] kernel03 (s390x.zVM) - tests ran: 39, failed: 3

tests ran:  39, failed: 3;
  
http://kernel.ubuntu.com/testing/4.10.0-11.13-generic/kernel03__4.10.0-11.13__2017-03-07_11-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/1669127

Title:
  linux: 4.10.0-11.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
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:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.10.0-11.13 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 --
  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-development-workflow/+bug/1669127/+subscriptions

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

[Kernel-packages] [Bug 1670624] Re: Official 16.04 HWE 4.8 kernels do not boot (4.4 was booting)

2017-03-07 Thread Evren Yurtesen

@brad-figg The kernel does not complete boot. I can't boot into the
system, can you tell me how can I run apport-collect?

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

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

Title:
  Official 16.04 HWE 4.8 kernels do not boot (4.4 was booting)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The machine is the same machine as in this bug report:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616830

  In mid 2016 I tested 4.8 kernels on that machine and they did not boot. (and 
same errors apply to current situation)
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616830/comments/5

  Also Ubuntu 16.10 and newer releases do not boot anymore (as reported by a 
user, I think it is due to kernel). He also reports the same errors with the 
4.8 kernel.
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616830/comments/15

  It seems that official release kernels still have the same problems
  and nothing was fixed.

  There seem to be many problems with Ubuntu on Carrizo, black screens,
  random freezes. I myself experienced, keyboard problems (keyboard
  sometimes do not register keystrokes), touchpad works strangely,
  random freeze with caps-lock blinking, low disk performance (max
  1.3mbytes/sec) and much more.

  I do not understand how hardware support can be getting worse and
  worse, but that seems to be the case.

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

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

[Kernel-packages] [Bug 1659340] Re: Linux kernel 4.8 hangs at boot up

2017-03-07 Thread Norbert Tretkowski

I got the update to 4.8.0-40.43 on 2017-03-02, but now it is no longer
available.

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

Title:
  Linux kernel 4.8 hangs at boot up

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

Bug description:
  I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot,
  Windows 10 and Ubuntu 16.10.

  Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45.
  When I try to start with any of the 4.8.0 kernels delivered with regular
  Ubuntu updates, they all hang after printing

Läser in Linux 4.8.0-34-generic ...
Läser in initial ramdisk ...

  Sorry for the partly Swedish text. I guess that the lines would start with
  "Loading" instead of "Läser in" on an English version.

  The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34
  and with -generic, -generic (upstart) and -generic (recovery mode).

  After a while the fan runs at full speed, as if the processor is working
  hard, but nothing happens.

  After I've tried in vain to start with Linux 4.8.0-xx, and then starts
  with 4.4.0-45, the following errors are usually printed:

  [  2.511733] usb 4-3: string descriptor 0 read error: -22
  [  3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight 
controller
  /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks
  [ 21.335117] usb 4-3: string descriptor 0 read error: -22

  When a successful start has not been immediately preceded by a failed start,
  only the line beginning "/dev/sda7" is printed.

  I have previously commented on bug #1635447. As recommended there, I've
  also tested with the upstream kernel 4.10-rc3. It worked just as bad as
  4.8.0.

  I tried to report this bug with 'ubuntu-bug linux' after I had booted with
  the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45-
  generic is not an official Ubuntu package.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  kjell  2022 F pulseaudio
   /dev/snd/controlC1:  kjell  2022 F pulseaudio
   /dev/snd/controlC0:  kjell  2022 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb
  InstallationDate: Installed on 2013-09-25 (1218 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V5-551G
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.4.0-45-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/11/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Havok
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire V5-551G
  dmi.product.version: V2.14
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1669127] kernel03 (s390x.zVM) - tests ran: 16, failed: 4

tests ran:  16, failed: 4;
  
http://kernel.ubuntu.com/testing/4.10.0-11.13-generic/kernel03__4.10.0-11.13__2017-03-07_10-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/1669127

Title:
  linux: 4.10.0-11.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
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:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.10.0-11.13 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 --
  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-development-workflow/+bug/1669127/+subscriptions

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

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

tests ran:  64, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-11.13-generic/s2lp6g003__4.10.0-11.13__2017-03-07_10-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/1669127

Title:
  linux: 4.10.0-11.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
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:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.10.0-11.13 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 --
  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-development-workflow/+bug/1669127/+subscriptions

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

[Kernel-packages] [Bug 1669127] kernel03 (s390x.zVM) - tests ran: 141, failed: 28

tests ran: 141, failed: 28;
  
http://kernel.ubuntu.com/testing/4.10.0-11.13-generic/kernel03__4.10.0-11.13__2017-03-07_10-22-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/1669127

Title:
  linux: 4.10.0-11.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
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:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.10.0-11.13 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 --
  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-development-workflow/+bug/1669127/+subscriptions

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

[Kernel-packages] [Bug 1669127] kernel03 (s390x.zVM) - tests ran: 2, failed: 0

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-11.13-generic/kernel03__4.10.0-11.13__2017-03-07_10-19-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/1669127

Title:
  linux: 4.10.0-11.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
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:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.10.0-11.13 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 --
  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-development-workflow/+bug/1669127/+subscriptions

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

[Kernel-packages] [Bug 1669127] kernel03 (s390x.zVM) - tests ran: 64, failed: 0

tests ran:  64, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-11.13-generic/kernel03__4.10.0-11.13__2017-03-07_10-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/1669127

Title:
  linux: 4.10.0-11.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
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:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.10.0-11.13 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 --
  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-development-workflow/+bug/1669127/+subscriptions

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

[Kernel-packages] [Bug 1670624] [NEW] Official 16.04 HWE 4.8 kernels do not boot (4.4 was booting)

2017-03-07 Thread Evren Yurtesen

Public bug reported:

The machine is the same machine as in this bug report:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616830

In mid 2016 I tested 4.8 kernels on that machine and they did not boot. (and 
same errors apply to current situation)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616830/comments/5

Also Ubuntu 16.10 and newer releases do not boot anymore (as reported by a 
user, I think it is due to kernel). He also reports the same errors with the 
4.8 kernel.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616830/comments/15

It seems that official release kernels still have the same problems and
nothing was fixed.

There seem to be many problems with Ubuntu on Carrizo, black screens,
random freezes. I myself experienced, keyboard problems (keyboard
sometimes do not register keystrokes), touchpad works strangely, random
freeze with caps-lock blinking, low disk performance (max 1.3mbytes/sec)
and much more.

I do not understand how hardware support can be getting worse and worse,
but that seems to be the case.

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


** Tags: 4.8 amd carrizo linux-image

** Attachment added: "rps20170307_115150.jpg"
   
https://bugs.launchpad.net/bugs/1670624/+attachment/4832788/+files/rps20170307_115150.jpg

** Tags removed: am
** Tags added: amd linux-image

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

Title:
  Official 16.04 HWE 4.8 kernels do not boot (4.4 was booting)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The machine is the same machine as in this bug report:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616830

  In mid 2016 I tested 4.8 kernels on that machine and they did not boot. (and 
same errors apply to current situation)
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616830/comments/5

  Also Ubuntu 16.10 and newer releases do not boot anymore (as reported by a 
user, I think it is due to kernel). He also reports the same errors with the 
4.8 kernel.
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616830/comments/15

  It seems that official release kernels still have the same problems
  and nothing was fixed.

  There seem to be many problems with Ubuntu on Carrizo, black screens,
  random freezes. I myself experienced, keyboard problems (keyboard
  sometimes do not register keystrokes), touchpad works strangely,
  random freeze with caps-lock blinking, low disk performance (max
  1.3mbytes/sec) and much more.

  I do not understand how hardware support can be getting worse and
  worse, but that seems to be the case.

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

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

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

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1670624

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

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

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

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

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

Title:
  Official 16.04 HWE 4.8 kernels do not boot (4.4 was booting)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The machine is the same machine as in this bug report:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616830

  In mid 2016 I tested 4.8 kernels on that machine and they did not boot. (and 
same errors apply to current situation)
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616830/comments/5

  Also Ubuntu 16.10 and newer releases do not boot anymore (as reported by a 
user, I think it is due to kernel). He also reports the same errors with the 
4.8 kernel.
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616830/comments/15

  It seems that official release kernels still have the same problems
  and nothing was fixed.

  There seem to be many problems with Ubuntu on Carrizo, black screens,
  random freezes. I myself experienced, keyboard problems (keyboard
  sometimes do not register keystrokes), touchpad works strangely,
  random freeze with caps-lock blinking, low disk performance (max
  1.3mbytes/sec) and much more.

  I do not understand how hardware support can be getting worse and
  worse, but that seems to be the case.

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

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

[Kernel-packages] [Bug 1647936] Re: Raspberry Pi 3: a small rainbow square on the top right of screen

2017-03-07 Thread Oliver Grawert

https://github.com/snapcore/pi3-gadget/commit/8b88f06ab5681d0ff41704a7813665a0203cbafc
for reference

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

Title:
  Raspberry Pi 3: a small rainbow square on the top right of screen

Status in Snappy:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid

Bug description:
  I'm working on the WD/nextcloud project, and found this issue

  Download the UC16 for Raspberry Pi 3 from 
http://releases.ubuntu.com/ubuntu-core/16/ubuntu-core-16-pi3.img.xz
  unxz , dd the image to sd card and boot up the system.
  There is a small rainbow square on top right of HDMI monitor.

  From RPI forum: https://www.raspberrypi.org/forums/viewtopic.php?t=82373
  If the voltage is under 4.65V, firmware displays a rainbow square on top 
right of screen and power LED goes off.
  But for UC16 the rainbow square is always there even the voltage is 
sufficient, but the power LED works properly.

  So I also check 
  1. Ubuntu server for RPI3 from here: https://wiki.ubuntu.com/ARM/RaspberryPi
  This RPI3 image works properly (if the voltage is not sufficient, rainbow 
square shows on the top right of screen, if it's sufficient,  
  no rainbow square shows up)
   2. Rasbian (jessie lite): 
https://downloads.raspberrypi.org/raspbian_lite_latest
  This works properly too, and the official Rasbian was released with the 
latest firmware, so the rainbow square changes to a 
  lighting icon

  It looks the firmware might be old in UC16? so the under-voltage
  warning doesn't display correctly.

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

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

[Kernel-packages] [Bug 1647936] Re: Raspberry Pi 3: a small rainbow square on the top right of screen

2017-03-07 Thread Oliver Grawert

the gadget snap in edge has this fix since a while already, it just did
not make it into a stable image yet.

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

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

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

Title:
  Raspberry Pi 3: a small rainbow square on the top right of screen

Status in Snappy:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid

Bug description:
  I'm working on the WD/nextcloud project, and found this issue

  Download the UC16 for Raspberry Pi 3 from 
http://releases.ubuntu.com/ubuntu-core/16/ubuntu-core-16-pi3.img.xz
  unxz , dd the image to sd card and boot up the system.
  There is a small rainbow square on top right of HDMI monitor.

  From RPI forum: https://www.raspberrypi.org/forums/viewtopic.php?t=82373
  If the voltage is under 4.65V, firmware displays a rainbow square on top 
right of screen and power LED goes off.
  But for UC16 the rainbow square is always there even the voltage is 
sufficient, but the power LED works properly.

  So I also check 
  1. Ubuntu server for RPI3 from here: https://wiki.ubuntu.com/ARM/RaspberryPi
  This RPI3 image works properly (if the voltage is not sufficient, rainbow 
square shows on the top right of screen, if it's sufficient,  
  no rainbow square shows up)
   2. Rasbian (jessie lite): 
https://downloads.raspberrypi.org/raspbian_lite_latest
  This works properly too, and the official Rasbian was released with the 
latest firmware, so the rainbow square changes to a 
  lighting icon

  It looks the firmware might be old in UC16? so the under-voltage
  warning doesn't display correctly.

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

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

[Kernel-packages] [Bug 1669127] kernel03 (s390x.zVM) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-11.13-generic/kernel03__4.10.0-11.13__2017-03-07_09-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/1669127

Title:
  linux: 4.10.0-11.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
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:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.10.0-11.13 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 --
  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-development-workflow/+bug/1669127/+subscriptions

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

[Kernel-packages] [Bug 1667828] Comment bridged from LTC Bugzilla

--- Comment From julian.wiedm...@de.ibm.com 2017-03-07 03:38 EDT---
Frank, please note the second part of the APAR description:

2: When a virtual NIC reflects the characteristics of the
NIC via the QUERY_CARD_INFO assist, the port speed and lan
type could be improved.

Problem conclusion
2: The QUERY_CARD_INFO simulation was updated to reflect a
LAN type of Fiber and a speed of 10 Gigabit.

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

Title:
  Network device on z/VM instance incorrectly reports line speed

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Line speed is incorrectly reported on z/VM instances in /sys when
  compared to what is claimed to be supported and advertised.

  for example, ethtool shows supported and advertised speeds of 1000Mb/s
  but /sys is only indicating 10Mb/s.

  ubuntu@hwe0008:~$ ethtool enc600
  Settings for enc600:
  Supported ports: [ TP ]
  Supported link modes:   10baseT/Half 10baseT/Full 
  100baseT/Half 100baseT/Full 
  1000baseT/Half 1000baseT/Full 
  Supported pause frame use: No
  Supports auto-negotiation: Yes
  Advertised link modes:  10baseT/Half 10baseT/Full 
  100baseT/Half 100baseT/Full 
  1000baseT/Half 1000baseT/Full 
  Advertised pause frame use: No
  Advertised auto-negotiation: Yes
  Speed: 10Mb/s
  Duplex: Full
  Port: Twisted Pair
  PHYAD: 0
  Transceiver: internal
  Auto-negotiation: on
  MDI-X: Unknown
  Cannot get wake-on-lan settings: Operation not permitted
  Link detected: yes
  ubuntu@hwe0008:~$ cat /sys/class/net/enc600/speed 
  10

  I'm presuming this issue lies somewhere in the qeth driver:
  P: /devices/qeth/0.0.0600/net/enc600
  E: DEVPATH=/devices/qeth/0.0.0600/net/enc600
  E: ID_NET_DRIVER=qeth_l2
  E: ID_NET_LINK_FILE=/lib/systemd/network/99-default.link
  E: ID_NET_NAME=enc600
  E: ID_NET_NAME_MAC=enx02280b04
  E: ID_NET_NAME_PATH=enc600
  E: ID_PATH=ccwgroup-0.0.0600
  E: ID_PATH_TAG=ccwgroup-0_0_0600
  E: IFINDEX=2
  E: INTERFACE=enc600
  E: SUBSYSTEM=net
  E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/enc600 
/sys/subsystem/net/devices/enc600
  E: TAGS=:systemd:
  E: USEC_INITIALIZED=3784115

  This is not an issue on my LPAR that uses the same drivers (but also
  adds ctcm and zfcp, so maybe therein lies the difference in speed
  reporting?)

  In any case, if the speeds cannot be correctly reported, they shouldn't be 
reported at all.  virtio handles this by setting speed to -1:
  ubuntu@s1lp9g003:~$ cat /sys/class/net/eth0/speed 
  -1
  ubuntu@s1lp9g003:~$ ethtool eth0
  Settings for eth0:
Supported ports: [ ]
Supported link modes:   Not reported
Supported pause frame use: No
Supports auto-negotiation: No
Advertised link modes:  Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Speed: Unknown!
Duplex: Unknown! (255)
Port: Other
PHYAD: 0
Transceiver: internal
Auto-negotiation: off
  Cannot get wake-on-lan settings: Operation not permitted
Link detected: yes

  That last example is a 1Gb/s interface on a z/KVM instance.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.8.0-36-generic 4.8.0-36.36~16.04.1
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic s390x
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: s390x
  Date: Fri Feb 24 17:08:59 2017
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1667828] Re: Network device on z/VM instance incorrectly reports line speed

2017-03-07 Thread Frank Heimes

We currently don't have APAR VM65785 or PTF UM34782 installed in our z/VM 6.3, 
because it looks like it's more z/OS and IP v6 related:
- according to the brief description "VSwitch error x'E00A' for IPv6 Address In 
use on LAN" (taken from here: http://www.vm.ibm.com/virtualnetwork/mntlvl63.html
- and also from the detailed description: 
http://www-01.ibm.com/support/docview.wss?uid=isg1VM65785

Anyway, if this APAR goes beyond the description we may consider to
apply this.

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

Title:
  Network device on z/VM instance incorrectly reports line speed

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Line speed is incorrectly reported on z/VM instances in /sys when
  compared to what is claimed to be supported and advertised.

  for example, ethtool shows supported and advertised speeds of 1000Mb/s
  but /sys is only indicating 10Mb/s.

  ubuntu@hwe0008:~$ ethtool enc600
  Settings for enc600:
  Supported ports: [ TP ]
  Supported link modes:   10baseT/Half 10baseT/Full 
  100baseT/Half 100baseT/Full 
  1000baseT/Half 1000baseT/Full 
  Supported pause frame use: No
  Supports auto-negotiation: Yes
  Advertised link modes:  10baseT/Half 10baseT/Full 
  100baseT/Half 100baseT/Full 
  1000baseT/Half 1000baseT/Full 
  Advertised pause frame use: No
  Advertised auto-negotiation: Yes
  Speed: 10Mb/s
  Duplex: Full
  Port: Twisted Pair
  PHYAD: 0
  Transceiver: internal
  Auto-negotiation: on
  MDI-X: Unknown
  Cannot get wake-on-lan settings: Operation not permitted
  Link detected: yes
  ubuntu@hwe0008:~$ cat /sys/class/net/enc600/speed 
  10

  I'm presuming this issue lies somewhere in the qeth driver:
  P: /devices/qeth/0.0.0600/net/enc600
  E: DEVPATH=/devices/qeth/0.0.0600/net/enc600
  E: ID_NET_DRIVER=qeth_l2
  E: ID_NET_LINK_FILE=/lib/systemd/network/99-default.link
  E: ID_NET_NAME=enc600
  E: ID_NET_NAME_MAC=enx02280b04
  E: ID_NET_NAME_PATH=enc600
  E: ID_PATH=ccwgroup-0.0.0600
  E: ID_PATH_TAG=ccwgroup-0_0_0600
  E: IFINDEX=2
  E: INTERFACE=enc600
  E: SUBSYSTEM=net
  E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/enc600 
/sys/subsystem/net/devices/enc600
  E: TAGS=:systemd:
  E: USEC_INITIALIZED=3784115

  This is not an issue on my LPAR that uses the same drivers (but also
  adds ctcm and zfcp, so maybe therein lies the difference in speed
  reporting?)

  In any case, if the speeds cannot be correctly reported, they shouldn't be 
reported at all.  virtio handles this by setting speed to -1:
  ubuntu@s1lp9g003:~$ cat /sys/class/net/eth0/speed 
  -1
  ubuntu@s1lp9g003:~$ ethtool eth0
  Settings for eth0:
Supported ports: [ ]
Supported link modes:   Not reported
Supported pause frame use: No
Supports auto-negotiation: No
Advertised link modes:  Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Speed: Unknown!
Duplex: Unknown! (255)
Port: Other
PHYAD: 0
Transceiver: internal
Auto-negotiation: off
  Cannot get wake-on-lan settings: Operation not permitted
Link detected: yes

  That last example is a 1Gb/s interface on a z/KVM instance.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.8.0-36-generic 4.8.0-36.36~16.04.1
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic s390x
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: s390x
  Date: Fri Feb 24 17:08:59 2017
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1669127] secchi (amd64) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-11.13-generic/secchi__4.10.0-11.13__2017-03-07_07-50-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/1669127

Title:
  linux: 4.10.0-11.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
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:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.10.0-11.13 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 --
  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-development-workflow/+bug/1669127/+subscriptions

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

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