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

[Brad Figg]

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

apport-collect 1672344

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

Title:
  4.4.0-1008.17 - aws failed with kernel security test 152

Status in QA Regression Testing:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  test_152_sysctl_disables_apparmor_unpriv_userns failed on
  4.4.0-1008.17 - aws

  This issue can't be found on 4.4.0-67.88 generic kernel for aws.
  There was once a similar bug for this, please refer to bug 1636461

  As the kernel version here is bigger than '4.4.0-46', the expected
  return value is 0, but the test returned 1 instead.

  FAIL: test_152_sysctl_disables_apparmor_unpriv_userns 
(__main__.KernelSecurityTest)
  unprivileged_userns_apparmor_policy sysctl supported
  --
  Traceback (most recent call last):
  File "./test-kernel-security.py", line 1925, in 
test_152_sysctl_disables_apparmor_unpriv_userns
  self._test_sysctl_value('kernel/unprivileged_userns_apparmor_policy', 
expected, exists=exists)
  File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1182, in _test_sysctl_value
  self.assertEqual(value, expected, report)
  AssertionError: /proc/sys/kernel/unprivileged_userns_apparmor_policy is not 
0: 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1672344/+subscriptions

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

[Kernel-packages] [Bug 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash

[kristian]

I also have to say that the system where I experienced this error is not
with me anymore.

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

Title:
  14e4:4365 bcmwl-kernel source: fix for null pointer crash

Status in Dell Sputnik:
  Confirmed
Status in bcmwl package in Ubuntu:
  Fix Released
Status in bcmwl source package in Precise:
  Won't Fix
Status in bcmwl source package in Trusty:
  Fix Committed
Status in bcmwl source package in Vivid:
  Won't Fix
Status in bcmwl source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * bcmwl does not compile on new kernels (or HWE kernels)
   * bcmwl suffers from null reference bug 

  [Test Case]

   * public PPA provided to community and feedback
   * based on patch available to other distros
   * comment #42

  [Regression Potential]

   * for changes on kernel support it may not compile (tested with 3.2, 3.13, 
3.18 and 4.2)
   * for the null reference change -> proved to fix problem for community based 
on feedback

  [Other Info]

  Original bug description:

  The bcmwl package as of now misses one patch for a bug that occurs
  with BCM43142 and possibly other broadcom chipsets that will look like
  random disconnects, poor wifi signal and kernel warnings, See also
  #1379524.

  Adding the patch is a fairly simple process:

  * put the patch file in /usr/src/bcmwl-6.30.223.248+bdcom/patches
  * add the following line to  /usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf
  PATCH[7]="0014-null-pointer-crash.patch"
  * run: /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom 
/usr/share/bcmwl x86_64 $(uname -r)

  This has fixed the issue for me. Edit: I just wanted to add that I did
  not write the patch; I merely downloaded it from a paste that was
  linked from the respective AUR package.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 [modified: 
usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf]
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Thu Jan 29 13:15:17 2015
  InstallationDate: Installed on 2015-01-26 (3 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1671459] gonzo (amd64) - tests ran: 141, failed: 0

[Brad Figg]

tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-113.160~precise1-generic/gonzo__3.13.0-113.160~precise1__2017-03-13_09-44-00/results-index.html

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

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1671232
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3

[Maciej Dziardziel]

Huang YangWen: can you attach result of those command:

ls -l /sys/bus/acpi/devices/
sudo lspci -vvnn


I wonder what the differences between motherboards are. I suspect Gigabyte has 
something other boards don't have.

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

Title:
  System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 
motherboard,
  and it has a load of problems, starting with not being able to boot normally.

  During normal boot, on 16.10 as well as 17.04 beta:
  system doesn't boot normally, hangs with a lot of "unexpected irq trap at 
vector 07"
  messages displayed.

  
  Following advice from various places, I've tried:disable cpu freq governor 
and cpu handling in acpi settings

  1. add "acpi=off" to boot params

  That helps, allowing me to boot into recovery mode, though it leaves
  me with system seeing only one core, is really slow and still only
  boots in recovery mode.

  2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor
  and cpu handling in acpi settings. Boot with "quiet loglevel=3"
  option.

  That gets me even further - system sees all cores now. Still only recovery 
mode though,
  but its enough to get info for this bug report.

  Some observed problems:

  1. dmesg reports *a lot* of messages like this all the time:

  [  163.362068] ->handle_irq():  87a7e090, 
  [  163.362081] bad_chained_irq+0x0/0x40
  [  163.362089] ->handle_irq():  87a7e090, 
  [  163.362090] amd_gpio_irq_handler+0x0/0x200
  [  163.362090] ->irq_data.chip(): 88587e20, 
  [  163.362090] ioapic_ir_chip+0x0/0x120
  [  163.362090] ->action(): 884601c0
  [  163.362091]IRQ_NOPROBE set
  [  163.362099] ->handle_irq():  87a7e090, 
  [  163.362099] amd_gpio_irq_handler+0x0/0x200
  [  163.362100] ->irq_data.chip(): 88587e20, 
  [  163.362100] ioapic_ir_chip+0x0/0x120
  [  163.362101] ->action(): 884601c0

  I've tried to redirect dmesg to a file, stopped after a short while,
  it generated 400M of those.

  2. Systemd cannot start journald. Perhaps because it cannot cope with
  amount of kernel logs?

  3. Looking at pci, I've noticed something called AMDI0040
  (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010,
  AMDI0020, AMDI0030. Those however are mentioned in kernel source,
  kernel and google are completely silent about AMDI0040.

  
  Phoronix tested ryzen using different motherboard, and it worked better 
(though not well),
  so I suspect it is an issue with motherboard.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2015-08-06 (581 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-rc1-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[Oliver Grawert]

@anthony ... technically that would be me ... practically the gadget
will never update the firmware files (the firmware files as well as the
dtb are usually in a dead-lock with the kernel version)

i'm waiting for a solution for this from the core team before we can
move on ... your best bet is to use edge based images (kernel and
gadget) for the moment.

-- 
You 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

[Oliver Grawert]

@ying-chun the kernel snap only upgrades the kerne, modules and files in
/lib/firmware ...

the gadget snap only updates the gadget.yaml, snap.yaml and files not in
/boot (i.e. it excludes all bootloader bits by default). until there is
a solution for potential unbootable systems this will not change i fear.

-- 
You 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 1672361] crash_7.1.7-1_ppc64el.deb

[bugproxy]

Default Comment by Bridge

** Attachment added: "crash_7.1.7-1_ppc64el.deb"
   
https://bugs.launchpad.net/bugs/1672361/+attachment/4836960/+files/crash_7.1.7-1_ppc64el.deb

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

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

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

Title:
  Ubuntu 17.04: Crash tool fails with error "crash: invalid structure
  size: tnt".

Status in crash package in Ubuntu:
  New

Bug description:
  Please cherry pick

   Upstream commit 651c824ffe2fd7eb8e416dbf4ff5c9a1da6ef7c6
   commit 24a696228c56fd4354d29abe05b206373e0c8bfb

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

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

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

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-113.160~precise1-generic/onibi__3.13.0-113.160~precise1__2017-03-13_13-19-00/results-index.html

** Tags added: regression-testing-passed

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

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1671232
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1497428] Re: kernel BUG at /build/buildd/linux-3.13.0/mm/page_alloc.c:968

[Craig Watcham]

m4.10xl also looks good:

[7399124.202570] lp1497428: module verification failed: signature and/or  
required key missing - tainting kernel
[7399124.223762] pageblock_nr_pages 0x200
[7399124.226007] node 0 zone 0 info:
[7399124.227849] node 0 zone 0 provided page pfn 0xfff valid 1 present 1
[7399124.231173] node 0 zone 0 start pfn 0xe00 valid 1 present 1
[7399124.234120] node 0 zone 0 end pfn 0xfff valid 1 present 1
[7399124.237107] node 0 zone 0 page ea03ffc0 start_page 
ea038000 end_page ea03ffc0
[7399124.241777] node 0 zone 0 spans: provided pfn 1 start pfn 1 end pfn 1
[7399124.245160] node 0 zone 0 start pfn 0x1 spanned pages 0xfff end pfn 0x1000
[7399124.248725] node 0 zone 0 present pages 0xf9d managed pages 0xf88
[7399124.251852] node 0 start pfn 0x1 end pfn 0x2818000
[7399124.254459] node 0 normal pageblock multiple
[7399124.256792] node 0 zone 1 info:
[7399124.258611] node 0 zone 1 provided page pfn 0xf valid 0 present 0
[7399124.261926] node 0 zone 1 start pfn 0xffe00 valid 0 present 0
[7399124.264980] node 0 zone 1 end pfn 0xf valid 0 present 0
[7399124.267859] node 0 zone 1 page ea0003c0 start_page 
ea0003ff8000 end_page ea0003c0
[7399124.272375] node 0 zone 1 spans: provided pfn 1 start pfn 1 end pfn 1
[7399124.275627] node 0 zone 1 start pfn 0x1000 spanned pages 0xff000 end pfn 
0x10
[7399124.279624] node 0 zone 1 present pages 0xef000 managed pages 0xea2d3
[7399124.283191] node 0 start pfn 0x1 end pfn 0x2818000
[7399124.286066] node 0 normal pageblock multiple
[7399124.288556] node 0 zone 2 info:
[7399124.290734] node 0 zone 2 provided page pfn 0x2817fff valid 1 present 1
[7399124.294354] node 0 zone 2 start pfn 0x2817e00 valid 1 present 1
[7399124.297599] node 0 zone 2 end pfn 0x2817fff valid 1 present 1
[7399124.300895] node 0 zone 2 page ea00a05fffc0 start_page 
ea00a05f8000 end_page ea00a05fffc0
[7399124.305733] node 0 zone 2 spans: provided pfn 1 start pfn 1 end pfn 1
[7399124.309124] node 0 zone 2 start pfn 0x10 spanned pages 0x2718000 end 
pfn 0x2818000
[7399124.313552] node 0 zone 2 present pages 0x131 managed pages 0x12bf8e5
[7399124.317134] node 0 start pfn 0x1 end pfn 0x2818000
[7399124.319881] node 0 normal pageblock multiple
[7399124.322452] node 1 zone 2 info:
[7399124.324461] node 1 zone 2 provided page pfn 0x280 valid 1 present 1
[7399124.328042] node 1 zone 2 start pfn 0x280fe00 valid 1 present 1
[7399124.331418] node 1 zone 2 end pfn 0x280 valid 1 present 1
[7399124.334599] node 1 zone 2 page ea00a03fffc0 start_page 
ea00a03f8000 end_page ea00a03fffc0
[7399124.339371] node 1 zone 2 spans: provided pfn 1 start pfn 1 end pfn 1
[7399124.342829] node 1 zone 2 start pfn 0x141 spanned pages 0x140 end 
pfn 0x281
[7399124.347266] node 1 zone 2 present pages 0x140 managed pages 0x13af8ab
[7399124.350781] node 1 start pfn 0x141 end pfn 0x281
[7399124.353662] node 1 normal pageblock multiple

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

Title:
  kernel BUG at /build/buildd/linux-3.13.0/mm/page_alloc.c:968

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

Bug description:
  The kernel triggers a BUG when it finds it is in move_freepages() but
  the start and end pfns for the move are in different zones.

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

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

[Kernel-packages] [Bug 1672344] [NEW] 4.4.0-1008.17 - aws failed with kernel security test 152

[Po-Hsu Lin]

Public bug reported:

Test: test_152_sysctl_disables_apparmor_unpriv_userns failed on
4.4.0-1008.17 - aws

This issue can't be found on 4.4.0-67.88 generic kernel for aws.
There was once a similar bug for this, please refer to bug 1636461

FAIL: test_152_sysctl_disables_apparmor_unpriv_userns 
(__main__.KernelSecurityTest)
unprivileged_userns_apparmor_policy sysctl supported
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 1925, in 
test_152_sysctl_disables_apparmor_unpriv_userns
self._test_sysctl_value('kernel/unprivileged_userns_apparmor_policy', expected, 
exists=exists)
File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1182, in _test_sysctl_value
self.assertEqual(value, expected, report)
AssertionError: /proc/sys/kernel/unprivileged_userns_apparmor_policy is not 0: 1

** Affects: qa-regression-testing
 Importance: Undecided
 Status: New

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

** Also 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/1672344

Title:
  4.4.0-1008.17 - aws failed with kernel security test 152

Status in QA Regression Testing:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Test: test_152_sysctl_disables_apparmor_unpriv_userns failed on
  4.4.0-1008.17 - aws

  This issue can't be found on 4.4.0-67.88 generic kernel for aws.
  There was once a similar bug for this, please refer to bug 1636461

  FAIL: test_152_sysctl_disables_apparmor_unpriv_userns 
(__main__.KernelSecurityTest)
  unprivileged_userns_apparmor_policy sysctl supported
  --
  Traceback (most recent call last):
  File "./test-kernel-security.py", line 1925, in 
test_152_sysctl_disables_apparmor_unpriv_userns
  self._test_sysctl_value('kernel/unprivileged_userns_apparmor_policy', 
expected, exists=exists)
  File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1182, in _test_sysctl_value
  self.assertEqual(value, expected, report)
  AssertionError: /proc/sys/kernel/unprivileged_userns_apparmor_policy is not 
0: 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1672344/+subscriptions

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

[Kernel-packages] [Bug 1672361] [NEW] Ubuntu 17.04: Crash tool fails with error "crash: invalid structure size: tnt".

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Please cherry pick

 Upstream commit 651c824ffe2fd7eb8e416dbf4ff5c9a1da6ef7c6
 commit 24a696228c56fd4354d29abe05b206373e0c8bfb

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


** Tags: architecture-ppc64le bugnameltc-152263 severity-high 
targetmilestone-inin1704
-- 
Ubuntu 17.04: Crash tool fails with error "crash: invalid structure size: tnt".
https://bugs.launchpad.net/bugs/1672361
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to crash 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 1671459] gonzo (i386) - tests ran: 141, failed: 0

[Brad Figg]

tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-113.160~precise1-generic/gonzo__3.13.0-113.160~precise1__2017-03-13_10-50-00/results-index.html

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

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1671232
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1672344] Re: 4.4.0-1008.17 - aws failed with kernel security test 152

[Po-Hsu Lin]

** Description changed:

  Test: test_152_sysctl_disables_apparmor_unpriv_userns failed on
  4.4.0-1008.17 - aws
  
  This issue can't be found on 4.4.0-67.88 generic kernel for aws.
- There was once a bug for this, please refer to bug 1636461
+ There was once a similar bug for this, please refer to bug 1636461
  
  FAIL: test_152_sysctl_disables_apparmor_unpriv_userns 
(__main__.KernelSecurityTest)
  unprivileged_userns_apparmor_policy sysctl supported
  --
  Traceback (most recent call last):
  File "./test-kernel-security.py", line 1925, in 
test_152_sysctl_disables_apparmor_unpriv_userns
  self._test_sysctl_value('kernel/unprivileged_userns_apparmor_policy', 
expected, exists=exists)
  File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1182, in _test_sysctl_value
  self.assertEqual(value, expected, report)
  AssertionError: /proc/sys/kernel/unprivileged_userns_apparmor_policy is not 
0: 1

** Description changed:

  Test: test_152_sysctl_disables_apparmor_unpriv_userns failed on
  4.4.0-1008.17 - aws
  
  This issue can't be found on 4.4.0-67.88 generic kernel for aws.
  There was once a similar bug for this, please refer to bug 1636461
+ 
+ As the kernel version here is bigger than '4.4.0-46', the expected
+ return value is 0, but the test returned 1 instead.
+ 
  
  FAIL: test_152_sysctl_disables_apparmor_unpriv_userns 
(__main__.KernelSecurityTest)
  unprivileged_userns_apparmor_policy sysctl supported
  --
  Traceback (most recent call last):
  File "./test-kernel-security.py", line 1925, in 
test_152_sysctl_disables_apparmor_unpriv_userns
  self._test_sysctl_value('kernel/unprivileged_userns_apparmor_policy', 
expected, exists=exists)
  File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1182, in _test_sysctl_value
  self.assertEqual(value, expected, report)
  AssertionError: /proc/sys/kernel/unprivileged_userns_apparmor_policy is not 
0: 1

** Description changed:

- Test: test_152_sysctl_disables_apparmor_unpriv_userns failed on
- 4.4.0-1008.17 - aws
+ test_152_sysctl_disables_apparmor_unpriv_userns failed on 4.4.0-1008.17
+ - aws
  
  This issue can't be found on 4.4.0-67.88 generic kernel for aws.
  There was once a similar bug for this, please refer to bug 1636461
  
  As the kernel version here is bigger than '4.4.0-46', the expected
  return value is 0, but the test returned 1 instead.
- 
  
  FAIL: test_152_sysctl_disables_apparmor_unpriv_userns 
(__main__.KernelSecurityTest)
  unprivileged_userns_apparmor_policy sysctl supported
  --
  Traceback (most recent call last):
  File "./test-kernel-security.py", line 1925, in 
test_152_sysctl_disables_apparmor_unpriv_userns
  self._test_sysctl_value('kernel/unprivileged_userns_apparmor_policy', 
expected, exists=exists)
  File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1182, in _test_sysctl_value
  self.assertEqual(value, expected, report)
  AssertionError: /proc/sys/kernel/unprivileged_userns_apparmor_policy is not 
0: 1

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

Title:
  4.4.0-1008.17 - aws failed with kernel security test 152

Status in QA Regression Testing:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  test_152_sysctl_disables_apparmor_unpriv_userns failed on
  4.4.0-1008.17 - aws

  This issue can't be found on 4.4.0-67.88 generic kernel for aws.
  There was once a similar bug for this, please refer to bug 1636461

  As the kernel version here is bigger than '4.4.0-46', the expected
  return value is 0, but the test returned 1 instead.

  FAIL: test_152_sysctl_disables_apparmor_unpriv_userns 
(__main__.KernelSecurityTest)
  unprivileged_userns_apparmor_policy sysctl supported
  --
  Traceback (most recent call last):
  File "./test-kernel-security.py", line 1925, in 
test_152_sysctl_disables_apparmor_unpriv_userns
  self._test_sysctl_value('kernel/unprivileged_userns_apparmor_policy', 
expected, exists=exists)
  File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1182, in _test_sysctl_value
  self.assertEqual(value, expected, report)
  AssertionError: /proc/sys/kernel/unprivileged_userns_apparmor_policy is not 
0: 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1672344/+subscriptions

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

[Kernel-packages] [Bug 1671528] Re: Constant freezes

[chusrubi2]

I just installed the latest upstream kernel but since I cannot reproduce
this issue manually I need some time (1-5 days) of full testing in order
to update this bug report.

Thank you.

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

Title:
  Constant freezes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My computer freezes completely in random way. It can happen today or
  tomorrow, or three times today...

  I have to turn it off and start it again. Nothing works when it's
  frozen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-66-generic 4.4.0-66.87
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   jesusfuentes   1913 F...m pulseaudio
   /dev/snd/controlC0:  jesusfuentes   1913 F pulseaudio
  Date: Thu Mar  9 16:41:20 2017
  HibernationDevice: RESUME=UUID=53c06625-a100-4ccd-a914-41da0fa82e15
  InstallationDate: Installed on 2016-09-22 (167 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1d57:fa20 Xenta 
   Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook N24_25JU
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic 
root=UUID=7edaecc8-d2d8-4c12-8c38-98ae5d8debca ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=7
  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-66-generic N/A
   linux-backports-modules-4.4.0-66-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/03/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N24_25JU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd06/03/2016:svnNotebook:pnN24_25JU:pvrNotApplicable:rvnNotebook:rnN24_25JU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: N24_25JU
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Kernel-packages] [Bug 1672372] [NEW] Revert "UBUNTU: SAUCE: Disable timers selftest for now"

[Seth Forshee]

Public bug reported:

This shouldn't be needed anymore, and it wasn't really effective anyway
due to the way the kernel selftests are being invoked.

** Affects: linux (Ubuntu)
 Importance: Low
 Assignee: Seth Forshee (sforshee)
 Status: Fix Committed

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

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

Title:
  Revert "UBUNTU: SAUCE: Disable timers selftest for now"

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  This shouldn't be needed anymore, and it wasn't really effective
  anyway due to the way the kernel selftests are being invoked.

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

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

[Kernel-packages] [Bug 1671232] Re: linux: 3.13.0-113.160 -proposed tracker

[Brad Figg]

** Tags added: regression-testing-passed

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

Title:
  linux: 3.13.0-113.160 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.13.0-113.160 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 --
  backports: 1671459
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1672198] [NEW] RTL8723b Kernel driver not loading on normal boot.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I use a very low and laptop with a built in rtl8723b wifi card. I always
used the driver from lwfinger on github and that one worked well.

But now Ubuntu comes with a driver for this card but that does not work on 
normal boot.
Strange thing is this driver is initialised after resume from suspend.

So i blacklisted the kernel module with:
echo "blacklist rtl8xxxu" | sudo tee /etc/modprobe.d/rtl8xxxu.conf

and used the lwfinger driver from github again.

So with rtl8xxu driver wifi card does not work on normal boot but does
work when recovering from suspend to ram.

Thank you. Bye.

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


** Tags: bot-comment
-- 
RTL8723b Kernel driver not loading on normal boot.
https://bugs.launchpad.net/bugs/1672198
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 1671232] Re: linux: 3.13.0-113.160 -proposed tracker

[Brad Figg]

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

Title:
  linux: 3.13.0-113.160 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.13.0-113.160 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 --
  backports: 1671459
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1672397] [NEW] bcmwl 6.30.223.248+bdcom-0ubuntu0.2 ADT test failure with linux-lts-xenial 4.4.0-67.88~14.04.1

[Andy Whitcroft]

Public bug reported:

Testing failed on:
i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/b/bcmwl/20170310_122529_bc576@/log.gz

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


** Tags: kernel-adt-failure kernel-adt-failure-lts-trusty

** Tags added: kernel-adt-failure kernel-adt-failure-lts-trusty

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

Title:
  bcmwl 6.30.223.248+bdcom-0ubuntu0.2 ADT test failure with linux-lts-
  xenial 4.4.0-67.88~14.04.1

Status in bcmwl package in Ubuntu:
  New

Bug description:
  Testing failed on:
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/b/bcmwl/20170310_122529_bc576@/log.gz

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

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

[Kernel-packages] [Bug 1671063] Re: ubuntu_lttng_smoke_test failed on Yakkety s390x (zVM)

[Colin Ian King]

https://bugs.lttng.org/issues/1091

end of sudo lttng-sessiond -vvv shows that we have a vmalloc failure:

DEBUG1 - 14:25:37.954060 [10037/10081]: Woken up but nothing in the UST command 
queue (in thread_dispatch_ust_registration() at main.c:1891)
DEBUG1 - 14:25:37.954072 [10037/10082]: Got the wait shm fd 33 (in 
get_wait_shm() at shm.c:115)
DEBUG1 - 14:25:37.954074 [10037/10086]: Updating kernel poll set (in 
update_kernel_poll() at main.c:889)
DEBUG1 - 14:25:37.954100 [10037/10086]: Thread kernel polling (in 
thread_manage_kernel() at main.c:1099)
DEBUG1 - 14:25:37.953832 [10037/10087]: [load-session-thread] Load session (in 
thread_load_session() at load-session-thread.c:91)
DEBUG1 - 14:25:37.954079 [10037/10082]: Futex wait update active 1 (in 
futex_wait_update() at futex.c:66)
DEBUG1 - 14:25:37.954132 [10037/10082]: Accepting application registration (in 
thread_registration_apps() at main.c:2145)
DEBUG3 - 14:25:37.953889 [10037/10084]: [ust-thread] Manage notify polling (in 
ust_thread_manage_notify() at ust-thread.c:69)
DEBUG1 - 14:25:42.577842 [10037/10080]: Wait for client response (in 
thread_manage_clients() at main.c:)
DEBUG1 - 14:25:42.577865 [10037/10080]: Receiving data from client ... (in 
thread_manage_clients() at main.c:4489)
DEBUG1 - 14:25:42.577999 [10037/10080]: Processing client command 4 (in 
process_client_msg() at main.c:2980)
DEBUG1 - 14:25:42.578010 [10037/10080]: Syscall table listing. (in 
syscall_table_list() at syscall.c:280)
PERROR - 14:25:42.578021 [10037/10080]: syscall table list zmalloc: Cannot 
allocate memory (in syscall_table_list() at syscall.c:291)
DEBUG3 - 14:25:42.578027 [10037/10080]: Destroying syscall hash table. (in 
destroy_syscall_ht() at syscall.c:159)
DEBUG1 - 14:25:42.578030 [10037/10080]: Missing llm structure. Allocating one. 
(in process_client_msg() at main.c:4124)
DEBUG1 - 14:25:42.578032 [10037/10080]: Sending response (size: 20, retcode: 
Not enough memory (26)) (in thread_manage_clients() 

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

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

Title:
  ubuntu_lttng_smoke_test failed on Yakkety s390x (zVM)

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Two test cases failed on this arch:
  == lttng smoke test list kernel events ==
  PASSED (lttng list --kernel)
  Error: Unable to list system calls: Not enough memory
  Error: Command error
  FAILED (lttng list --kernel --syscall)
  FAILED (lttng list --kernel --syscall more output expected)
   
  == lttng smoke test trace open/close system calls ==
  ...
  FAILED (did not trace any open system calls)

  Please find attachment for complete log.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-40-generic 4.8.0-40.43
  ProcVersionSignature: Ubuntu 4.8.0-40.43-generic 4.8.17
  Uname: Linux 4.8.0-40-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Wed Mar  8 06:39:24 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=/dev/mapper/kl02vg01-root crashkernel=196M debug 
udev.log-priority=debug rd.udev.log_priority=debug BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-40-generic N/A
   linux-backports-modules-4.8.0-40-generic  N/A
   linux-firmware1.161.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1672198] Re: RTL8723b Kernel driver not loading on normal boot.

[Brian Murray]

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

Title:
  RTL8723b Kernel driver not loading on normal boot.

Status in linux package in Ubuntu:
  New

Bug description:
  I use a very low and laptop with a built in rtl8723b wifi card. I
  always used the driver from lwfinger on github and that one worked
  well.

  But now Ubuntu comes with a driver for this card but that does not work on 
normal boot.
  Strange thing is this driver is initialised after resume from suspend.

  So i blacklisted the kernel module with:
  echo "blacklist rtl8xxxu" | sudo tee /etc/modprobe.d/rtl8xxxu.conf

  and used the lwfinger driver from github again.

  So with rtl8xxu driver wifi card does not work on normal boot but does
  work when recovering from suspend to ram.

  Thank you. Bye.

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[Joshua R. Poulson]

Please include the stable release updates released this weekend
(v4.10.2). The following Hyper-V commits were included:

hyperv.h : commit ec6f27bd19e0f9142c71d293d4c3b381348550b7 : Drivers: hv: 
vmbus: Fix a rescind handling bug
channel.c : commit ec6f27bd19e0f9142c71d293d4c3b381348550b7 : Drivers: hv: 
vmbus: Fix a rescind handling bug
channel.c : commit 0fd8c1cb80a1403aab4f36de85804c44666a486d : Drivers: hv: 
vmbus: Raise retry/wait limits in vmbus_post_msg()
channel_mgmt.c : commit ec6f27bd19e0f9142c71d293d4c3b381348550b7 : Drivers: 
hv: vmbus: Fix a rescind handling bug
channel_mgmt.c : commit 0fd8c1cb80a1403aab4f36de85804c44666a486d : Drivers: 
hv: vmbus: Raise retry/wait limits in vmbus_post_msg()
connection.c : commit 0fd8c1cb80a1403aab4f36de85804c44666a486d : Drivers: 
hv: vmbus: Raise retry/wait limits in vmbus_post_msg()
hv.c : commit f791a7b4a7ae3a008a8af887b5a3f36ad1ac0574 : hv: don't reset 
hv_context.tsc_page on crash
hv.c : commit aa2765857f7411a960778afc1ed34cb57dc43f08 : hv: allocate synic 
pages for all present CPUs
hv.c : commit a34da99e9468a3990a8ca91bb9e502af61f95535 : hv: init 
percpu_list in hv_synic_alloc()
hv.c : commit 6ffc4b85358f6b7d252420cfa5862312cf5f83d8 : hv: change 
clockevents unbind tactics
hv_fcopy.c : commit 48dc52df9155443289f8bbf52f25a4214961ebee : Drivers: hv: 
util: Fcopy: Fix a rescind processing issue
hv_kvp.c : commit f38bcff3986238898806512863b0e9d675de45ee : Drivers: hv: 
util: kvp: Fix a rescind processing issue
hv_snapshot.c : commit 93919359467c6ce2f0f0ca4ad0f517b2d9bb03cf : Drivers: 
hv: util: Backup: Fix a rescind processing issue
hyperv_vmbus.h : commit 0fd8c1cb80a1403aab4f36de85804c44666a486d : Drivers: 
hv: vmbus: Raise retry/wait limits in vmbus_post_msg()
ring_buffer.c : commit 42b0681b7fe98556c1e4288e534368cc0bf607f9 : Drivers: 
hv: vmbus: Prevent sending data on a rescinded channel
storvsc_drv.c : commit 99b3ba253c8b7bf8635fc68b5371a8225371f47c : scsi: 
storvsc: use tagged SRB requests if supported by the device
storvsc_drv.c : commit e5fbe2328cc5c7211e4338b76f9004214b5bb663 : scsi: 
storvsc: properly set residual data length on errors
storvsc_drv.c : commit 0aeb049529f3573dd35a549f846e5f623899d480 : scsi: 
storvsc: properly handle SRB_ERROR when sense message is present
pci-hyperv.c : commit 91f5bce789d9083f1e24bc09b00c8c781c015835 : PCI: hv: 
Fix wslot_to_devfn() to fix warnings on device removal

-- 
You 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
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Triaged
Status in linux source package in Zesty:
  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: 

[Kernel-packages] [Bug 1671459] onibi (i386) - tests ran: 2, failed: 0

[Brad Figg]

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-113.160~precise1-generic/onibi__3.13.0-113.160~precise1__2017-03-13_14-27-00/results-index.html

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

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1671232
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

[Brad Figg]

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-113.160~precise1-generic/onibi__3.13.0-113.160~precise1__2017-03-13_14-04-00/results-index.html

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

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1671232
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-113.160~precise1-generic/onibi__3.13.0-113.160~precise1__2017-03-13_13-42-00/results-index.html

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

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

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1671232
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

-- 
Mailing list: https://launchpad.net/~kernel-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] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From jac...@de.ibm.com 2017-03-13 09:57 EDT---
Next iteration: I was able to make OpenAFS for the proposed kernel fixed and so 
I was able to start the next pdebuild job  and again I run into a hang 
scenario:

Mar 13 14:30:32 mclint multipathd[881]: mpatha: sda - tur checker timed out
Mar 13 14:30:32 mclint multipathd[881]: 8:0: reinstated
Mar 13 14:30:32 mclint multipathd[881]: mpatha: sdc - tur checker timed out
Mar 13 14:30:32 mclint multipathd[881]: 8:32: reinstated
Mar 13 14:30:33 mclint multipathd[881]: mpatha: sdb - tur checker timed out
Mar 13 14:30:33 mclint multipathd[881]: 8:16: reinstated
Mar 13 14:30:36 mclint multipathd[881]: mpatha: sdd - tur checker timed out
Mar 13 14:30:36 mclint rsyslogd-2007: action 'action 10' suspended, next retry 
is Mon Mar 13 14:32:06 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
Mar 13 14:30:36 mclint multipathd[881]: 8:48: reinstated

I just pulled a dump and compress it, eventually I'll upload it to Box.
I'll go on and try to reproduce this without OpenAFS and I'm very
confident that this hang is not related to AFS at all ...

General dump info:
Dump format: s390mv
Version: 5
Dump created...: Mon, 13 Mar 2017 14:42:39 +0100
Dump ended.: Mon, 13 Mar 2017 14:43:17 +0100
Dump CPU ID: 9efc729648000
UTS node name..: mclint
UTS kernel release.: 4.4.0-67-generic
UTS kernel version.: #88 SMP Wed Mar 8 14:48:51 UTC 2017
Build arch.: s390x (64 bit)
System arch: s390x (64 bit)
CPU count (online).: 2
CPU count (real)...: 4
Dump memory range..: 8192 MB
Real memory range..: 8192 MB

Memory map:
 - 0001b831afff (7043 MB)
0001b831b000 - 0001 (1149 MB)

Dump device info:
Volume 0: 0.0.8409 (online/active)
Volume 1: 0.0.840a (online/active)

-- 
You 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: 

[Kernel-packages] [Bug 1672397] Re: bcmwl 6.30.223.248+bdcom-0ubuntu0.2 ADT test failure with linux-lts-xenial 4.4.0-67.88~14.04.1

[Andy Whitcroft]

** Attachment added: "make.log"
   https://bugs.launchpad.net/bugs/1672397/+attachment/4837019/+files/make.log

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

Title:
  bcmwl 6.30.223.248+bdcom-0ubuntu0.2 ADT test failure with linux-lts-
  xenial 4.4.0-67.88~14.04.1

Status in bcmwl package in Ubuntu:
  New

Bug description:
  Testing failed on:
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/b/bcmwl/20170310_122529_bc576@/log.gz

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

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

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

[Brad Figg]

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

apport-collect 1672198

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

Title:
  RTL8723b Kernel driver not loading on normal boot.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use a very low and laptop with a built in rtl8723b wifi card. I
  always used the driver from lwfinger on github and that one worked
  well.

  But now Ubuntu comes with a driver for this card but that does not work on 
normal boot.
  Strange thing is this driver is initialised after resume from suspend.

  So i blacklisted the kernel module with:
  echo "blacklist rtl8xxxu" | sudo tee /etc/modprobe.d/rtl8xxxu.conf

  and used the lwfinger driver from github again.

  So with rtl8xxu driver wifi card does not work on normal boot but does
  work when recovering from suspend to ram.

  Thank you. Bye.

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

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

[Kernel-packages] [Bug 1559308] Re: Plugging HDMI screen in causes system hang

[Luís Fernando Heckler]

I was experimenting similar behaviour using kernel 4.6.0 x86_64 (linux
mint + cinnamon).

After upgrading to  4.8.0-040800-generic x86_64 seems fine now.

Regards
Luis F. Heckler

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

Title:
  Plugging HDMI screen in causes system hang

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I have a 4K UHD laptop screen and am running Ubuntu Gnome 16.04 Beta1
  using 4.4.0-13-generic and the Nouveau drivers.

  If I plug in an external HDMI monitor (FHD) either into either HDMI
  port (there's one on the machine and there's one available via a usb
  3.1 extra adaptor) then the whole system hangs, completely
  unresponsive and needing a hard reboot. Before hanging the 2nd display
  gets an image as expected, but the laptop's screen flashes randomly,
  sometimes you see weird artifacts. Then the hang comes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar 18 20:43:42 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06e4]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4]
  InstallationDate: Installed on 2016-03-15 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160225.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic.efi.signed 
root=UUID=b026feed-8801-44f4-9f3f-c245f4a1f25e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  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.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Mar 18 17:28:07 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   Unknown chipset: NV117
   SynPS/2 Synaptics TouchPad: Read error 19
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5182 
   vendor SHP
  xserver.version: 2:1.18.1-1ubuntu4

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

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

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

[Brad Figg]

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

Title:
  No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision
  5520

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My processor does not appear to be utilizing and idling states deeper
  than C3.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-66-generic 4.4.0-66.87
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  carl   2446 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 13 08:57:06 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  HibernationDevice: RESUME=UUID=65474558-ead3-4d66-85e5-b55f81978b88
  InstallationDate: Installed on 2017-03-09 (3 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IwConfig:
   lono wireless extensions.
   
   wlp2s0no wireless extensions.
  MachineType: Dell Inc. Precision 5520
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic.efi.signed 
root=UUID=d19efcb8-515b-494c-a236-ee0da23f2393 ro acpi_rev_override locale=C 
quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-66-generic N/A
   linux-backports-modules-4.4.0-66-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 0X41RR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1672439] Re: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520

[Carl Mueller]

~$ sudo powertop (Idle Stats tab)

  Package   | Core|CPU 0   CPU 4
POLL0.0%| POLL0.0%| POLL0.0%0.0 ms  0.0%
0.0 ms
C1  0.8%| C1  0.3%| C1  0.3%0.2 ms  0.4%
0.6 ms
C2 12.7%| C2  7.2%| C2 10.4%1.6 ms  4.0%
4.1 ms
C3 81.7%| C3 89.4%| C3 84.6%6.6 ms 94.0%
8.9 ms

| Core|CPU 1   CPU 5
| POLL0.0%| POLL0.0%0.0 ms  0.0%
0.0 ms
| C1  1.7%| C1  3.3%0.9 ms  0.1%
0.2 ms
| C2 15.7%| C2 26.0%1.8 ms  5.4%
2.0 ms
| C3 74.0%| C3 65.5%4.0 ms 82.4%   
25.2 ms

| Core|CPU 2   CPU 6
| POLL0.0%| POLL0.0%0.0 ms  0.0%
0.0 ms
| C1  0.7%| C1  1.1%0.2 ms  0.2%
0.2 ms
| C2 15.0%| C2 17.2%2.3 ms 12.7%
1.1 ms
| C3 81.0%| C3 78.7%5.4 ms 83.2%
7.9 ms

| Core|CPU 3   CPU 7
| POLL0.0%| POLL0.0%0.0 ms  0.0%
0.0 ms
| C1  0.4%| C1  0.8%0.2 ms  0.1%
0.1 ms
| C2 12.6%| C2 23.6%1.3 ms  1.7%
1.6 ms
| C3 81.8%| C3 69.1%4.7 ms 94.5%
9.4 ms

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

Title:
  No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision
  5520

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My processor does not appear to be utilizing and idling states deeper
  than C3.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-66-generic 4.4.0-66.87
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  carl   2446 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 13 08:57:06 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  HibernationDevice: RESUME=UUID=65474558-ead3-4d66-85e5-b55f81978b88
  InstallationDate: Installed on 2017-03-09 (3 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IwConfig:
   lono wireless extensions.
   
   wlp2s0no wireless extensions.
  MachineType: Dell Inc. Precision 5520
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic.efi.signed 
root=UUID=d19efcb8-515b-494c-a236-ee0da23f2393 ro acpi_rev_override locale=C 
quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-66-generic N/A
   linux-backports-modules-4.4.0-66-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 0X41RR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1672198] Re: RTL8723b Kernel driver not loading on normal boot.

[SB]

Because I do not have access to the machine running Ubuntu now i ran
apport from my machine which is identical and has the identical problem
with RTL8723 just it runs Linux Mint. As you can see I tried various
Kernel up to 4.9 and the problem is the same with any 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/1672198

Title:
  RTL8723b Kernel driver not loading on normal boot.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use a very low and laptop with a built in rtl8723b wifi card. I
  always used the driver from lwfinger on github and that one worked
  well.

  But now Ubuntu comes with a driver for this card but that does not work on 
normal boot.
  Strange thing is this driver is initialised after resume from suspend.

  So i blacklisted the kernel module with:
  echo "blacklist rtl8xxxu" | sudo tee /etc/modprobe.d/rtl8xxxu.conf

  and used the lwfinger driver from github again.

  So with rtl8xxu driver wifi card does not work on normal boot but does
  work when recovering from suspend to ram.

  Thank you. Bye.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.1
  InstallationDate: Installed on 2016-12-23 (79 days ago)
  InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Tags:  serena
  Uname: Linux 4.9.10-040910-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1672439] Re: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520

[Carl Mueller]

Installed:

intel-microcode_3.20161104.1~deb8u1~bpo7+1_amd6

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

Title:
  No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision
  5520

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My processor does not appear to be utilizing and idling states deeper
  than C3.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-66-generic 4.4.0-66.87
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  carl   2446 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 13 08:57:06 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  HibernationDevice: RESUME=UUID=65474558-ead3-4d66-85e5-b55f81978b88
  InstallationDate: Installed on 2017-03-09 (3 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IwConfig:
   lono wireless extensions.
   
   wlp2s0no wireless extensions.
  MachineType: Dell Inc. Precision 5520
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic.efi.signed 
root=UUID=d19efcb8-515b-494c-a236-ee0da23f2393 ro acpi_rev_override locale=C 
quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-66-generic N/A
   linux-backports-modules-4.4.0-66-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 0X41RR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1672439] Re: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520

[Carl Mueller]

~$ dmesg |grep idle

[0.00] clocksource: refined-jiffies: mask: 0x max_cycles: 
0x, max_idle_ns: 7645519600211568 ns
[0.00] clocksource: hpet: mask: 0x max_cycles: 0x, 
max_idle_ns: 79635855245 ns
[0.044934] process: using mwait in idle threads
[0.153005] clocksource: jiffies: mask: 0x max_cycles: 0x, 
max_idle_ns: 764504178510 ns
[0.162345] cpuidle: using governor ladder
[0.178334] cpuidle: using governor menu
[0.343661] clocksource: acpi_pm: mask: 0xff max_cycles: 0xff, 
max_idle_ns: 2085701024 ns
[0.899900] intel_idle: does not run on family 6 model 158
[0.901622] ACPI: acpi_idle registered with cpuidle
[1.894828] clocksource: tsc: mask: 0x max_cycles: 
0x29dc020bb13, max_idle_ns: 440795273180 ns

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

Title:
  No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision
  5520

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My processor does not appear to be utilizing and idling states deeper
  than C3.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-66-generic 4.4.0-66.87
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  carl   2446 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 13 08:57:06 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  HibernationDevice: RESUME=UUID=65474558-ead3-4d66-85e5-b55f81978b88
  InstallationDate: Installed on 2017-03-09 (3 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IwConfig:
   lono wireless extensions.
   
   wlp2s0no wireless extensions.
  MachineType: Dell Inc. Precision 5520
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic.efi.signed 
root=UUID=d19efcb8-515b-494c-a236-ee0da23f2393 ro acpi_rev_override locale=C 
quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-66-generic N/A
   linux-backports-modules-4.4.0-66-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 0X41RR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1672439] Re: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520

[Carl Mueller]

Let me know what other information I could supply.

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

Title:
  No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision
  5520

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My processor does not appear to be utilizing and idling states deeper
  than C3.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-66-generic 4.4.0-66.87
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  carl   2446 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 13 08:57:06 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  HibernationDevice: RESUME=UUID=65474558-ead3-4d66-85e5-b55f81978b88
  InstallationDate: Installed on 2017-03-09 (3 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IwConfig:
   lono wireless extensions.
   
   wlp2s0no wireless extensions.
  MachineType: Dell Inc. Precision 5520
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic.efi.signed 
root=UUID=d19efcb8-515b-494c-a236-ee0da23f2393 ro acpi_rev_override locale=C 
quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-66-generic N/A
   linux-backports-modules-4.4.0-66-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 0X41RR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[Brian Murray]

** Also affects: makedumpfile (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857051
   Importance: Unknown
   Status: Unknown

-- 
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
Status in makedumpfile package in Debian:
  Unknown

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) 
  - AFAIK, there is no upstream bug database, so no URL available, ML only.
  - Patch will be merge in upstream version 1.6.2 # See comment #4

  * 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 1672439] [NEW] No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520

[Carl Mueller]

Public bug reported:

My processor does not appear to be utilizing and idling states deeper
than C3.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-66-generic 4.4.0-66.87
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  carl   2446 F pulseaudio
CurrentDesktop: Unity
Date: Mon Mar 13 08:57:06 2017
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
HibernationDevice: RESUME=UUID=65474558-ead3-4d66-85e5-b55f81978b88
InstallationDate: Installed on 2017-03-09 (3 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
IwConfig:
 lono wireless extensions.
 
 wlp2s0no wireless extensions.
MachineType: Dell Inc. Precision 5520
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic.efi.signed 
root=UUID=d19efcb8-515b-494c-a236-ee0da23f2393 ro acpi_rev_override locale=C 
quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-66-generic N/A
 linux-backports-modules-4.4.0-66-generic  N/A
 linux-firmware1.157.8
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/18/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.3
dmi.board.name: 0X41RR
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.name: Precision 5520
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug xenial

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

Title:
  No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision
  5520

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My processor does not appear to be utilizing and idling states deeper
  than C3.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-66-generic 4.4.0-66.87
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  carl   2446 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 13 08:57:06 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  HibernationDevice: RESUME=UUID=65474558-ead3-4d66-85e5-b55f81978b88
  InstallationDate: Installed on 2017-03-09 (3 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IwConfig:
   lono wireless extensions.
   
   wlp2s0no wireless extensions.
  MachineType: Dell Inc. Precision 5520
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic.efi.signed 
root=UUID=d19efcb8-515b-494c-a236-ee0da23f2393 ro acpi_rev_override locale=C 
quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-66-generic N/A
   linux-backports-modules-4.4.0-66-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 0X41RR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1672198] Re: RTL8723b Kernel driver not loading on normal boot.

[SB]

apport information

** Tags added: apport-collected serena

** Description changed:

  I use a very low and laptop with a built in rtl8723b wifi card. I always
  used the driver from lwfinger on github and that one worked well.
  
  But now Ubuntu comes with a driver for this card but that does not work on 
normal boot.
  Strange thing is this driver is initialised after resume from suspend.
  
  So i blacklisted the kernel module with:
  echo "blacklist rtl8xxxu" | sudo tee /etc/modprobe.d/rtl8xxxu.conf
  
  and used the lwfinger driver from github again.
  
  So with rtl8xxu driver wifi card does not work on normal boot but does
  work when recovering from suspend to ram.
  
  Thank you. Bye.
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.5
+ Architecture: amd64
+ CurrentDesktop: X-Cinnamon
+ DistroRelease: Linux 18.1
+ InstallationDate: Installed on 2016-12-23 (79 days ago)
+ InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=de_DE.UTF-8
+  SHELL=/bin/bash
+ Tags:  serena
+ Uname: Linux 4.9.10-040910-generic x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True

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

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

Title:
  RTL8723b Kernel driver not loading on normal boot.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use a very low and laptop with a built in rtl8723b wifi card. I
  always used the driver from lwfinger on github and that one worked
  well.

  But now Ubuntu comes with a driver for this card but that does not work on 
normal boot.
  Strange thing is this driver is initialised after resume from suspend.

  So i blacklisted the kernel module with:
  echo "blacklist rtl8xxxu" | sudo tee /etc/modprobe.d/rtl8xxxu.conf

  and used the lwfinger driver from github again.

  So with rtl8xxu driver wifi card does not work on normal boot but does
  work when recovering from suspend to ram.

  Thank you. Bye.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.1
  InstallationDate: Installed on 2016-12-23 (79 days ago)
  InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Tags:  serena
  Uname: Linux 4.9.10-040910-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1672439] Re: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520

[Carl Mueller]

cat /sys/module/intel_idle/parameters/max_cstate

~$ cat /sys/module/intel_idle/parameters/max_cstate
9

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

Title:
  No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision
  5520

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My processor does not appear to be utilizing and idling states deeper
  than C3.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-66-generic 4.4.0-66.87
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  carl   2446 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 13 08:57:06 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  HibernationDevice: RESUME=UUID=65474558-ead3-4d66-85e5-b55f81978b88
  InstallationDate: Installed on 2017-03-09 (3 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IwConfig:
   lono wireless extensions.
   
   wlp2s0no wireless extensions.
  MachineType: Dell Inc. Precision 5520
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic.efi.signed 
root=UUID=d19efcb8-515b-494c-a236-ee0da23f2393 ro acpi_rev_override locale=C 
quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-66-generic N/A
   linux-backports-modules-4.4.0-66-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 0X41RR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1672439] Re: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520

[Carl Mueller]

~$ sudo i7z

sudo i7z
i7z DEBUG: i7z version: svn-r93-(27-MAY-2013)
i7z DEBUG: Found Intel Processor
i7z DEBUG:Stepping 9
i7z DEBUG:Model e
i7z DEBUG:Family 6
i7z DEBUG:Processor Type 0
i7z DEBUG:Extended Model 9
i7z DEBUG: msr = Model Specific Register
i7z DEBUG: Unknown processor, not exactly based on Nehalem, Sandy bridge or Ivy 
Bridge
i7z DEBUG: msr device files exist /dev/cpu/*/msr
i7z DEBUG: You have write permissions to msr device files

--
--[core id]--- Other information
-
--[0] Processor number 0
--[0] Socket number/Hyperthreaded Sibling number  0,4
--[0] Core id number 0
--[0] Display core in i7z Tool: Yes

--[1] Processor number 1
--[1] Socket number/Hyperthreaded Sibling number  0,5
--[1] Core id number 1
--[1] Display core in i7z Tool: Yes

--[2] Processor number 2
--[2] Socket number/Hyperthreaded Sibling number  0,6
--[2] Core id number 2
--[2] Display core in i7z Tool: Yes

--[3] Processor number 3
--[3] Socket number/Hyperthreaded Sibling number  0,7
--[3] Core id number 3
--[3] Display core in i7z Tool: Yes

--[4] Processor number 4
--[4] Socket number/Hyperthreaded Sibling number  0,0
--[4] Core id number 0
--[4] Display core in i7z Tool: No

--[5] Processor number 5
--[5] Socket number/Hyperthreaded Sibling number  0,1
--[5] Core id number 1
--[5] Display core in i7z Tool: No

--[6] Processor number 6
--[6] Socket number/Hyperthreaded Sibling number  0,2
--[6] Core id number 2
--[6] Display core in i7z Tool: No

--[7] Processor number 7
--[7] Socket number/Hyperthreaded Sibling number  0,3
--[7] Core id number 3
--[7] Display core in i7z Tool: No

Socket-0 [num of cpus 4 physical 4 logical 8] 0,1,2,3,
Socket-1 [num of cpus 0 physical 0 logical 0] 
GUI has been Turned ON
i7z DEBUG: Single Socket Detected
i7z DEBUG: In i7z Single_Socket()
i7z DEBUG: guessing Nehalem


AND THEN


Cpu speed from cpuinfo 2903.00Mhz
cpuinfo might be wrong if cpufreq is enabled. To guess correctly try estimating 
via tsc
Linux's inbuilt cpu_khz code emulated now
True Frequency (without accounting Turbo) 2903 MHz
  CPU Multiplier 29x || Bus clock frequency (BCLK) 100.10 MHz

Socket [0] - [physical cores=4, logical cores=8, max online cores ever=4]
  TURBO ENABLED on 4 Cores, Hyper Threading ON
  Max Frequency without considering Turbo 3003.10 MHz (100.10 x [30])
  Max TURBO Multiplier (if Enabled) with 1/2/3/4 Cores is  39x/37x/36x/35x
  Real Current Frequency 1557.86 MHz [100.10 x 15.56] (Max of below)
Core [core-id]  :Actual Freq (Mult.)  C0%   Halt(C1)%  C3 %   C6 %  
Temp  VCore
Core 1 [0]:   1516.07 (15.15x)  2.8698.5   0   0
39  0.7573
Core 2 [1]:   1557.86 (15.56x)  2.1698.8   0   0
37  0.7573
Core 3 [2]:   1533.17 (15.32x)  2.1598.9   0   0
39  0.7550
Core 4 [3]:   1554.47 (15.53x)  1.5198.2   1   0
38  0.7552


C0 = Processor running without halting
C1 = Processor running with halts (States >C0 are power saver modes with cores 
idling)
C3 = Cores running with PLL turned off and core cache turned off
C6, C7 = Everything in C3 + core state saved to last level cache, C7 is deeper 
than C6
  Above values in table are in percentage over the last 1 sec
[core-id] refers to core-id number in /proc/cpuinfo
'Garbage Values' message printed when garbage values are read
  Ctrl+C to exit

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

Title:
  No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision
  5520

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My processor does not appear to be utilizing and idling states deeper
  than C3.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-66-generic 4.4.0-66.87
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  carl   2446 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 13 08:57:06 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  HibernationDevice: RESUME=UUID=65474558-ead3-4d66-85e5-b55f81978b88
  InstallationDate: Installed on 2017-03-09 (3 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IwConfig:
   lono wireless extensions.
   
   wlp2s0no wireless extensions.
  MachineType: Dell Inc. Precision 5520
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic.efi.signed 

[Kernel-packages] [Bug 1671063] Re: ubuntu_lttng_smoke_test failed on Yakkety s390x (zVM)

[Jonathan Rajotte Julien]

Hi Colin,

As you indicated it seems that an actual allocation problem occurred on:

syscall table list zmalloc: Cannot allocate memory (in syscall_table_list() at 
syscall.c:291)
>From the code:


/*  
 * Allocate at least the number of total syscall we have even if some of
 * them might not be valid. The count below will make sure to return the
 * right size of the events array.  
 */ 
events = zmalloc(syscall_table_nb_entry * sizeof(*events)); 
if (!events) {  
PERROR("syscall table list zmalloc");   
ret = -LTTNG_ERR_NOMEM; 
goto error; 
}   
syscall_table_nb_entry is assigned in syscall_init_table.

Could you link the full sessiond log and strace log? Also if possible
determine the value of syscall_table_nb_entry?

Cheers

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

Title:
  ubuntu_lttng_smoke_test failed on Yakkety s390x (zVM)

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Two test cases failed on this arch:
  == lttng smoke test list kernel events ==
  PASSED (lttng list --kernel)
  Error: Unable to list system calls: Not enough memory
  Error: Command error
  FAILED (lttng list --kernel --syscall)
  FAILED (lttng list --kernel --syscall more output expected)
   
  == lttng smoke test trace open/close system calls ==
  ...
  FAILED (did not trace any open system calls)

  Please find attachment for complete log.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-40-generic 4.8.0-40.43
  ProcVersionSignature: Ubuntu 4.8.0-40.43-generic 4.8.17
  Uname: Linux 4.8.0-40-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Wed Mar  8 06:39:24 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=/dev/mapper/kl02vg01-root crashkernel=196M debug 
udev.log-priority=debug rd.udev.log_priority=debug BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-40-generic N/A
   linux-backports-modules-4.8.0-40-generic  N/A
   linux-firmware1.161.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1671113] gonzo (i386) - tests ran: 7, failed: 0

[Brad Figg]

tests ran:   7, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/gonzo__4.4.0-67.88__2017-03-13_14-59-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/1671113

Title:
  linux: 4.4.0-67.88 -proposed tracker

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

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

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

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

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

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

[Kernel-packages] [Bug 1652185] Re: kernel BUG at /build/linux-7x12eW/linux-4.4.0/drivers/ata/sata_mv.c:2120!

[John Bridges]

I confirm the same crash bug in Kernel versions:

4.4.0-66-generic
4.4.0-64-generic
4.4.0-21-generic

I could not test with latest upstream kernel because I needed ZFS (I
looked into building it for latest upstream, but found no reasonable
path).

I can also confirm the crash is related to a drive with bad sectors. In my case 
a Seagate 2TB
ata-ST2000DM001-1ER164_Z4Z55RQ2

Once I removed that drive, the crashing stopped.

If I booted with drive offline, and then added it to a booted system, it
did not crash until I imported the ZFS pool.

I can try some simple tests with DD to confirm the crash in later or earlier 
kernels.
Since I do not want to break a now working system, any testing would be done 
booting a USB Flash image with only the failing drive connected to a sata_mv 
port.

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

Title:
  kernel BUG at /build/linux-
  7x12eW/linux-4.4.0/drivers/ata/sata_mv.c:2120!

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  # lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  # apt-cache policy linux-image-4.4.0-57-generic
  linux-image-4.4.0-57-generic:
Installed: 4.4.0-57.78
Candidate: 4.4.0-57.78
Version table:
   *** 4.4.0-57.78 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  
  Dec 22 16:59:20 crashplan-2 kernel: [ 9534.464076] [ cut here 
]
  Dec 22 16:59:20 crashplan-2 kernel: [ 9534.464173] kernel BUG at 
/build/linux-7x12eW/linux-4.4.0/drivers/ata/sata_mv.c:2120!
  Dec 22 16:59:20 crashplan-2 kernel: [ 9534.464281] invalid opcode:  [#1] 
SMP
  Dec 22 16:59:20 crashplan-2 kernel: [ 9534.464355] Modules linked in: 
binfmt_misc zfs(PO) zunicode(PO) zcommon(PO) znvpair(PO) spl(O) zavl(PO) 
gpio_ich ppdev i5000_edac edac_core parport_pc i5k_amb coretemp kvm parport 
irqbypass lpc_ich serio_raw input_leds 8250_fintek shpchp mac_hid ib_iser 
rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp 
libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid hid amdkfd amd_iommu_v2 radeon i2c_algo_bit 
ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm pata_acpi 
e1000e ptp pps_core sata_mv floppy fjes
  Dec 22 16:59:20 crashplan-2 kernel: [ 9534.466220] CPU: 0 PID: 198 Comm: 
scsi_eh_15 Tainted: P   O4.4.0-57-generic #78-Ubuntu
  Dec 22 16:59:20 crashplan-2 kernel: [ 9534.466355] Hardware name: Supermicro 
X7DB8/X7DB8, BIOS 6.00 12/03/2007
  Dec 22 16:59:20 crashplan-2 kernel: [ 9534.466452] task: 880034c40cc0 ti: 
880034c4c000 task.ti: 880034c4c000
  Dec 22 16:59:20 crashplan-2 kernel: [ 9534.466564] RIP: 
0010:[]  [] mv_qc_prep+0x213/0x230 [sata_mv]
  Dec 22 16:59:20 crashplan-2 kernel: [ 9534.466717] RSP: 0018:880034c4fa30 
 EFLAGS: 00010006
  Dec 22 16:59:20 crashplan-2 kernel: [ 9534.466797] RAX: 8800353188c0 RBX: 
8800352bdd70 RCX: 0047
  Dec 22 16:59:20 crashplan-2 kernel: [ 9534.466893] RDX: 8800353188ca RSI: 
88012a6af060 RDI: 8800352bdd70
  Dec 22 16:59:20 crashplan-2 kernel: [ 9534.466993] RBP: 880034c4fa48 R08: 
 R09: 0001
  Dec 22 16:59:20 crashplan-2 kernel: [ 9534.467092] R10: 0020 R11: 
 R12: 003f
  Dec 22 16:59:20 crashplan-2 kernel: [ 9534.467191] R13: 880035083c18 R14: 
0001 R15: 8800352bdd70
  Dec 22 16:59:20 crashplan-2 kernel: [ 9534.467291] FS:  
() GS:88012fc0() knlGS:
  Dec 22 16:59:20 crashplan-2 kernel: [ 9534.467412] CS:  0010 DS:  ES: 
 CR0: 8005003b
  Dec 22 16:59:20 crashplan-2 kernel: [ 9534.467489] CR2: 7f284278bc00 CR3: 
cb676000 CR4: 06f0
  Dec 22 16:59:20 crashplan-2 kernel: [ 9534.467588] Stack:
  Dec 22 16:59:20 crashplan-2 kernel: [ 9534.467628]  8800352bc000 
0001 8800352bde80 880034c4faa0
  Dec 22 16:59:20 crashplan-2 kernel: [ 9534.467774]  815d9caa 
88012a6af098 81e2c360 880034c4fb70
  Dec 22 16:59:20 crashplan-2 kernel: [ 9534.467920]  000281d1863d 
880034c4fbe0 8800352bde80 
  Dec 22 16:59:20 crashplan-2 kernel: [ 9534.468017] Call Trace:
  Dec 22 16:59:20 crashplan-2 kernel: [ 9534.468017]  [] 
ata_qc_issue+0x15a/0x390
  Dec 22 16:59:20 crashplan-2 kernel: [ 9534.468017]  [] 
ata_exec_internal_sg+0x302/0x600
  Dec 22 16:59:20 crashplan-2 kernel: [ 9534.468017]  [] 
ata_exec_internal+0x69/0xc0
  Dec 22 16:59:20 crashplan-2 kernel: [ 9534.468017]  [] ? 
blk_peek_request+0x4b/0x290
  Dec 22 

[Kernel-packages] [Bug 1671459] gonzo (i386) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-113.160~precise1-generic/gonzo__3.13.0-113.160~precise1__2017-03-13_08-42-00/results-index.html

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

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1671232
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1651981] Re: shaking screen

[Adrian]

Why the patch was dropped in the version 4.8.0.41.52 of linux-image-gerneric?
Does 4.8.0.41.52 corresponds to tag Ubuntu-4.8.0-41.44 ? If so, why the numbers 
don't match ?

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

Title:
  shaking screen

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  After login into Ubuntu the screen starts to shake permanently.
  The login screen is still fine, problem start after log in.
  The problem is caused by last kernel update: running Ubuntu with the older 
kernel 4.8.0-30-generic fixes the issue.

  Upstream patch submission:
  https://lists.freedesktop.org/archives/dri-devel/2016-December/128331.html

  WORKAROUND: Revert:
  # first bad commit: [9cc4fd5b9fbb0d74e77c81521da1e2fe712f6787] 
drm/radeon/si_dpm: workaround for SI kickers

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-32-generic 4.8.0-32.34
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  afiergol   7797 F pulseaudio
   /dev/snd/controlC1:  afiergol   7797 F pulseaudio
   /dev/snd/seq:timidity   6155 F timidity
  Date: Thu Dec 22 10:02:30 2016
  HibernationDevice: RESUME=UUID=7ca97ca1-ca2d-43f6-9b4c-cd61421c0831
  InstallationDate: Installed on 2015-04-02 (629 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Hewlett-Packard HP ZBook 15 G2
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro radeon.dpm=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-32-generic N/A
   linux-backports-modules-4.8.0-32-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-16 (66 days ago)
  dmi.bios.date: 04/25/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M70 Ver. 01.15
  dmi.board.name: 2253
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 03.12
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM70Ver.01.15:bd04/25/2016:svnHewlett-Packard:pnHPZBook15G2:pvrA3008CD10003:rvnHewlett-Packard:rn2253:rvrKBCVersion03.12:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ZBook 15 G2
  dmi.product.version: A3008CD10003
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3

[Huang YangWen]

CPU is Ryzen 1700x

However lm-sensor is not working properly.

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

Title:
  System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 
motherboard,
  and it has a load of problems, starting with not being able to boot normally.

  During normal boot, on 16.10 as well as 17.04 beta:
  system doesn't boot normally, hangs with a lot of "unexpected irq trap at 
vector 07"
  messages displayed.

  
  Following advice from various places, I've tried:disable cpu freq governor 
and cpu handling in acpi settings

  1. add "acpi=off" to boot params

  That helps, allowing me to boot into recovery mode, though it leaves
  me with system seeing only one core, is really slow and still only
  boots in recovery mode.

  2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor
  and cpu handling in acpi settings. Boot with "quiet loglevel=3"
  option.

  That gets me even further - system sees all cores now. Still only recovery 
mode though,
  but its enough to get info for this bug report.

  Some observed problems:

  1. dmesg reports *a lot* of messages like this all the time:

  [  163.362068] ->handle_irq():  87a7e090, 
  [  163.362081] bad_chained_irq+0x0/0x40
  [  163.362089] ->handle_irq():  87a7e090, 
  [  163.362090] amd_gpio_irq_handler+0x0/0x200
  [  163.362090] ->irq_data.chip(): 88587e20, 
  [  163.362090] ioapic_ir_chip+0x0/0x120
  [  163.362090] ->action(): 884601c0
  [  163.362091]IRQ_NOPROBE set
  [  163.362099] ->handle_irq():  87a7e090, 
  [  163.362099] amd_gpio_irq_handler+0x0/0x200
  [  163.362100] ->irq_data.chip(): 88587e20, 
  [  163.362100] ioapic_ir_chip+0x0/0x120
  [  163.362101] ->action(): 884601c0

  I've tried to redirect dmesg to a file, stopped after a short while,
  it generated 400M of those.

  2. Systemd cannot start journald. Perhaps because it cannot cope with
  amount of kernel logs?

  3. Looking at pci, I've noticed something called AMDI0040
  (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010,
  AMDI0020, AMDI0030. Those however are mentioned in kernel source,
  kernel and google are completely silent about AMDI0040.

  
  Phoronix tested ryzen using different motherboard, and it worked better 
(though not well),
  so I suspect it is an issue with motherboard.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2015-08-06 (581 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-rc1-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

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

[Brad Figg]

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-113.160~precise1-generic/gonzo__3.13.0-113.160~precise1__2017-03-13_09-00-00/results-index.html

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

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1671232
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3

[Huang YangWen]

Works find with Ubuntu 16.04 + 4.10.1-041001-generic

The kernel is downloaded from Ubuntu website

motherboard ASUS PRIME B350-PLUS.


** Attachment added: "Screenshot from 2017-03-13 16-53-20.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+attachment/4836844/+files/Screenshot%20from%202017-03-13%2016-53-20.png

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

Title:
  System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 
motherboard,
  and it has a load of problems, starting with not being able to boot normally.

  During normal boot, on 16.10 as well as 17.04 beta:
  system doesn't boot normally, hangs with a lot of "unexpected irq trap at 
vector 07"
  messages displayed.

  
  Following advice from various places, I've tried:disable cpu freq governor 
and cpu handling in acpi settings

  1. add "acpi=off" to boot params

  That helps, allowing me to boot into recovery mode, though it leaves
  me with system seeing only one core, is really slow and still only
  boots in recovery mode.

  2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor
  and cpu handling in acpi settings. Boot with "quiet loglevel=3"
  option.

  That gets me even further - system sees all cores now. Still only recovery 
mode though,
  but its enough to get info for this bug report.

  Some observed problems:

  1. dmesg reports *a lot* of messages like this all the time:

  [  163.362068] ->handle_irq():  87a7e090, 
  [  163.362081] bad_chained_irq+0x0/0x40
  [  163.362089] ->handle_irq():  87a7e090, 
  [  163.362090] amd_gpio_irq_handler+0x0/0x200
  [  163.362090] ->irq_data.chip(): 88587e20, 
  [  163.362090] ioapic_ir_chip+0x0/0x120
  [  163.362090] ->action(): 884601c0
  [  163.362091]IRQ_NOPROBE set
  [  163.362099] ->handle_irq():  87a7e090, 
  [  163.362099] amd_gpio_irq_handler+0x0/0x200
  [  163.362100] ->irq_data.chip(): 88587e20, 
  [  163.362100] ioapic_ir_chip+0x0/0x120
  [  163.362101] ->action(): 884601c0

  I've tried to redirect dmesg to a file, stopped after a short while,
  it generated 400M of those.

  2. Systemd cannot start journald. Perhaps because it cannot cope with
  amount of kernel logs?

  3. Looking at pci, I've noticed something called AMDI0040
  (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010,
  AMDI0020, AMDI0030. Those however are mentioned in kernel source,
  kernel and google are completely silent about AMDI0040.

  
  Phoronix tested ryzen using different motherboard, and it worked better 
(though not well),
  so I suspect it is an issue with motherboard.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2015-08-06 (581 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-rc1-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1616763] Re: System can't pair to bluetooth 4.0 keyboard/mouse [Intel 8260]

[Anthony Wong]

** Changed in: hwe-next
   Status: Confirmed => Invalid

** Changed in: linux-firmware (Ubuntu)
   Status: New => Invalid

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

Title:
  System can't pair to bluetooth 4.0 keyboard/mouse [Intel 8260]

Status in HWE Next:
  Invalid
Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  Intel 8260 BT module can't pair to BT 4.0 keyboard or mouse. There's
  already a new firmware to fix this issue and has passed our test:

  commit a4bbc8112cc04fcc0e0861e8b72197b6cb83ab83
  Author: Tedd Ho-Jeong An 
  Date: Wed Jun 8 12:53:26 2016 -0700

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

-- 
Mailing list: https://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 1644919] Re: [fn] plus F2, F3, F4, F5, F6, F10, F11, F12 not responding - Fresh Install

[Andrew F in Australia]

Thanks Kai-Heng.

Done (and attached.)

Many thanks,

A

On 13/03/17 15:56, Kai-Heng Feng wrote:
> We need some information from ACPI then.
>
> Please install acpica-tools and run acpidump,
>
> $ sudo apt install acpica-tools
> $ sudo acpidump > acpi-dump
>
> Attach acpi-dump file.
>


** Attachment added: "acpi-dump.txt"
   
https://bugs.launchpad.net/bugs/1644919/+attachment/4836847/+files/acpi-dump.txt

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

Title:
  [fn] plus F2,F3,F4,F5,F6,F10,F11,F12 not responding - Fresh Install

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Gigabyte P57 laptop

  Fresh install, 10 days old, updated yesterday so software/kernel
  should be current.

  Some function keys work.
  Function plus F1 puts the machine to sleep
  Function plus F7, F8, F9 control the volume

  However,
  Pressing Function plus F2 does not turn off wireless
  Pressing Function plus F3,F4 do not change brightness
  Function plus F5 does not change output to LCD or Monitor
  Pressing Function plus F6 does not toggle touchpad (a separate bug in this 
machine, but the Elantech touchpad is recognised at the moment.)
  Function plus F10 does not turn the display off
  Function plus F11 does not turn off bluetooth
  Function plus F12 does not disable the camera

  Please let me know if you need any further troubleshooting

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-47-generic 4.4.0-47.68
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  horace 1948 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Nov 26 07:44:13 2016
  HibernationDevice: RESUME=UUID=fba63969-ab35-4aa7-b2f7-e432edba169e
  InstallationDate: Installed on 2016-11-13 (12 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05af:1050 Jing-Mold Enterprise Co., Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GIGABYTE P57
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed 
root=UUID=e9ea66ca-2853-4d85-bc49-74de4c35c442 ro quiet splash i8042.nomux=1 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-47-generic N/A
   linux-backports-modules-4.4.0-47-generic  N/A
   linux-firmware1.157.5
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FB0B
  dmi.board.asset.tag: Default string
  dmi.board.name: P57
  dmi.board.vendor: GIGABYTE
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFB0B:bd05/30/2016:svnGIGABYTE:pnP57:pvrDefaultstring:rvnGIGABYTE:rnP57:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: P57
  dmi.product.version: Default string
  dmi.sys.vendor: GIGABYTE

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

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

[Kernel-packages] [Bug 1671459] gonzo (i386) - tests ran: 2, failed: 0

[Brad Figg]

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-113.160~precise1-generic/gonzo__3.13.0-113.160~precise1__2017-03-13_09-23-00/results-index.html

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

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1671232
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1671232] Re: linux: 3.13.0-113.160 -proposed tracker

[Brad Figg]

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

Title:
  linux: 3.13.0-113.160 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.13.0-113.160 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 --
  backports: 1671459
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1672318] [NEW] package linux-image-extra-3.13.0-108-generic 3.13.0-108.155 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it befor

[Debbie Record]

Public bug reported:

happened during the post trigger install part

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-extra-3.13.0-108-generic 3.13.0-108.155
ProcVersionSignature: Ubuntu 3.13.0-110.157-generic 3.13.11-ckt39
Uname: Linux 3.13.0-110-generic i686
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  debbie 1478 F pulseaudio
Date: Mon Mar 13 09:23:15 2017
DuplicateSignature: 
package:linux-image-extra-3.13.0-108-generic:3.13.0-108.155:package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
HibernationDevice: RESUME=UUID=b15bc548-bf77-4173-becf-5d0aec058133
InstallationDate: Installed on 2011-10-11 (1979 days ago)
InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1)
MachineType: DIXONSXP DIXONSXP
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-110-generic 
root=UUID=efb07609-e50d-45ac-9c35-59f2317bdea0 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.12
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: package linux-image-extra-3.13.0-108-generic 3.13.0-108.155 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: Upgraded to trusty on 2016-09-08 (185 days ago)
dmi.bios.date: 04/12/2007
dmi.bios.vendor: DIXONSXP
dmi.bios.version: 1.00.DIX
dmi.board.name: DIXONSXP
dmi.board.vendor: DIXONSXP
dmi.chassis.type: 10
dmi.chassis.vendor: DIXONSXP
dmi.modalias: 
dmi:bvnDIXONSXP:bvr1.00.DIX:bd04/12/2007:svnDIXONSXP:pnDIXONSXP:pvr:rvnDIXONSXP:rnDIXONSXP:rvr:cvnDIXONSXP:ct10:cvr:
dmi.product.name: DIXONSXP
dmi.sys.vendor: DIXONSXP

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


** Tags: apport-package i386 trusty

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

Title:
  package linux-image-extra-3.13.0-108-generic 3.13.0-108.155 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in linux package in Ubuntu:
  New

Bug description:
  happened during the post trigger install part

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.13.0-108-generic 3.13.0-108.155
  ProcVersionSignature: Ubuntu 3.13.0-110.157-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-110-generic i686
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  debbie 1478 F pulseaudio
  Date: Mon Mar 13 09:23:15 2017
  DuplicateSignature: 
package:linux-image-extra-3.13.0-108-generic:3.13.0-108.155:package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  HibernationDevice: RESUME=UUID=b15bc548-bf77-4173-becf-5d0aec058133
  InstallationDate: Installed on 2011-10-11 (1979 days ago)
  InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1)
  MachineType: DIXONSXP DIXONSXP
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-110-generic 
root=UUID=efb07609-e50d-45ac-9c35-59f2317bdea0 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.12
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-extra-3.13.0-108-generic 3.13.0-108.155 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to trusty on 2016-09-08 (185 days ago)
  dmi.bios.date: 04/12/2007
  dmi.bios.vendor: DIXONSXP
  dmi.bios.version: 1.00.DIX
  dmi.board.name: DIXONSXP
  dmi.board.vendor: DIXONSXP
  dmi.chassis.type: 10
  dmi.chassis.vendor: DIXONSXP
  dmi.modalias: 
dmi:bvnDIXONSXP:bvr1.00.DIX:bd04/12/2007:svnDIXONSXP:pnDIXONSXP:pvr:rvnDIXONSXP:rnDIXONSXP:rvr:cvnDIXONSXP:ct10:cvr:
  dmi.product.name: DIXONSXP
  dmi.sys.vendor: DIXONSXP

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

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

[Kernel-packages] [Bug 1647936] Re: Raspberry Pi 3: a small rainbow square on the top right of screen

[Ying-Chun Liu]

Hi.

I tried to 
"snap refresh pi3 --channel=edge"
"snap refresh pi2-kernel --channel=edge"

The rainbow square is still appeared. Is this the correct way to upgrade
gadgets and put the firmwares onto the system?

# snap info pi3
name:  pi3
summary:   "Raspberry Pi 3 support package"
publisher: canonical
description: |
  Support files for booting Raspberry Pi
  
type:gadget
tracking:edge
installed:   16.04-0.5 (14) 6MB -
refreshed:   2017-01-18 15:02:58 + UTC
channels:   
  stable:16.04-0.5 (6)  6MB -
  candidate: 16.04-0.5 (6)  6MB -
  beta:  16.04-0.5 (6)  6MB -
  edge:  16.04-0.5 (14) 6MB -

# snap info pi2-kernel
name:  pi2-kernel
summary:   "The canonical raspi2 armhf kernel"
publisher: canonical
description: |
  The Ubuntu linux-raspi2 kernel package as a snap
type:kernel
tracking:edge
installed:   4.4.0-1040-47 (26) 101MB -
refreshed:   2017-01-11 11:52:04 + UTC
channels:   
  stable:4.4.0-1030-3  (22) 89MB  -
  candidate: 4.4.0-1030-3  (22) 89MB  -
  beta:  4.4.0-1044-51 (27) 100MB -
  edge:  4.4.0-1040-47 (26) 101MB -

-- 
You 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 1672318] Re: package linux-image-extra-3.13.0-108-generic 3.13.0-108.155 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-extra-3.13.0-108-generic 3.13.0-108.155 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in linux package in Ubuntu:
  New

Bug description:
  happened during the post trigger install part

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.13.0-108-generic 3.13.0-108.155
  ProcVersionSignature: Ubuntu 3.13.0-110.157-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-110-generic i686
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  debbie 1478 F pulseaudio
  Date: Mon Mar 13 09:23:15 2017
  DuplicateSignature: 
package:linux-image-extra-3.13.0-108-generic:3.13.0-108.155:package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  HibernationDevice: RESUME=UUID=b15bc548-bf77-4173-becf-5d0aec058133
  InstallationDate: Installed on 2011-10-11 (1979 days ago)
  InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1)
  MachineType: DIXONSXP DIXONSXP
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-110-generic 
root=UUID=efb07609-e50d-45ac-9c35-59f2317bdea0 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.12
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-extra-3.13.0-108-generic 3.13.0-108.155 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to trusty on 2016-09-08 (185 days ago)
  dmi.bios.date: 04/12/2007
  dmi.bios.vendor: DIXONSXP
  dmi.bios.version: 1.00.DIX
  dmi.board.name: DIXONSXP
  dmi.board.vendor: DIXONSXP
  dmi.chassis.type: 10
  dmi.chassis.vendor: DIXONSXP
  dmi.modalias: 
dmi:bvnDIXONSXP:bvr1.00.DIX:bd04/12/2007:svnDIXONSXP:pnDIXONSXP:pvr:rvnDIXONSXP:rnDIXONSXP:rvr:cvnDIXONSXP:ct10:cvr:
  dmi.product.name: DIXONSXP
  dmi.sys.vendor: DIXONSXP

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

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

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

[Brad Figg]

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

Title:
  package linux-image-extra-3.13.0-108-generic 3.13.0-108.155 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  happened during the post trigger install part

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.13.0-108-generic 3.13.0-108.155
  ProcVersionSignature: Ubuntu 3.13.0-110.157-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-110-generic i686
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  debbie 1478 F pulseaudio
  Date: Mon Mar 13 09:23:15 2017
  DuplicateSignature: 
package:linux-image-extra-3.13.0-108-generic:3.13.0-108.155:package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  HibernationDevice: RESUME=UUID=b15bc548-bf77-4173-becf-5d0aec058133
  InstallationDate: Installed on 2011-10-11 (1979 days ago)
  InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1)
  MachineType: DIXONSXP DIXONSXP
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-110-generic 
root=UUID=efb07609-e50d-45ac-9c35-59f2317bdea0 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.12
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-extra-3.13.0-108-generic 3.13.0-108.155 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to trusty on 2016-09-08 (185 days ago)
  dmi.bios.date: 04/12/2007
  dmi.bios.vendor: DIXONSXP
  dmi.bios.version: 1.00.DIX
  dmi.board.name: DIXONSXP
  dmi.board.vendor: DIXONSXP
  dmi.chassis.type: 10
  dmi.chassis.vendor: DIXONSXP
  dmi.modalias: 
dmi:bvnDIXONSXP:bvr1.00.DIX:bd04/12/2007:svnDIXONSXP:pnDIXONSXP:pvr:rvnDIXONSXP:rnDIXONSXP:rvr:cvnDIXONSXP:ct10:cvr:
  dmi.product.name: DIXONSXP
  dmi.sys.vendor: DIXONSXP

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[Ying-Chun Liu]

I think I'm making wrong assumption? It seems to me that refresh gadget snaps 
won't upgrade the files in the system.
Upgrading kernel snap does change the kernel/uboot.env stuff. But not for 
gadgets right? Seems we need to regenerate an edge image for testing 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/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 1671058] Re: docker service failed to start on s390x (zVM) Yakkety

[Po-Hsu Lin]

Verified with the older 4.8.0-38 kernel, docker.io version
1.12.1-0ubuntu15 and 1.12.6-0ubuntu1~16.10.1 will both fail without the
-extra package as well.

So just like xnon mentioned above, we will need to add the missing
driver to the main kernel package.

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

Title:
  docker service failed to start on s390x (zVM) Yakkety

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

Bug description:
  docker.service failed to start on s390x(zVM) Yakkety 4.8.0-40-generic
  proposed kernel

  # systemctl status docker.service
  ● docker.service - Docker Application Container Engine
 Loaded: loaded (/lib/systemd/system/docker.service; disabled; vendor 
preset: enabled)
Drop-In: /etc/systemd/system/docker.service.d
 └─http-proxy.conf
 Active: failed (Result: start-limit-hit) since Wed 2017-03-08 06:06:54 
EST; 14min ago
   Docs: https://docs.docker.com
Process: 3752 ExecStart=/usr/bin/dockerd -H fd:// $DOCKER_OPTS 
(code=exited, status=1/FAILURE)
   Main PID: 3752 (code=exited, status=1/FAILURE)

  Mar 08 06:06:54 kernel02 systemd[1]: docker.service: Unit entered failed 
state.
  Mar 08 06:06:54 kernel02 systemd[1]: docker.service: Failed with result 
'exit-code'.
  Mar 08 06:06:54 kernel02 systemd[1]: docker.service: cgroup is empty
  Mar 08 06:06:54 kernel02 systemd[1]: docker.service: Trying to enqueue job 
docker.service/start/replace
  Mar 08 06:06:54 kernel02 systemd[1]: docker.service: Installed new job 
docker.service/start as 1897
  Mar 08 06:06:54 kernel02 systemd[1]: docker.service: Enqueued job 
docker.service/start as 1897
  Mar 08 06:06:54 kernel02 systemd[1]: docker.service: Start request repeated 
too quickly.
  Mar 08 06:06:54 kernel02 systemd[1]: docker.service: Job docker.service/start 
finished, result=failed
  Mar 08 06:06:54 kernel02 systemd[1]: Failed to start Docker Application 
Container Engine.
  Mar 08 06:06:54 kernel02 systemd[1]: docker.service: Failed with result 
'start-limit-hit'.

  Please find attachment for partial log from journalctl -xe

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: docker.io 1.12.6-0ubuntu1~16.10.1
  ProcVersionSignature: Ubuntu 4.8.0-40.43-generic 4.8.17
  Uname: Linux 4.8.0-40-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: s390x
  Date: Wed Mar  8 06:17:52 2017
  SourcePackage: docker.io
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1671459] gonzo (amd64) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-113.160~precise1-generic/gonzo__3.13.0-113.160~precise1__2017-03-13_08-22-00/results-index.html

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

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1671232
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[Joseph Maillardet]

Hi, here a video of the problem...

** Attachment added: "Demonstration"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1663637/+attachment/4836850/+files/radeon_flickering.mp4

-- 
You 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
Status in linux source package in Xenial:
  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)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jmaillar   3511 F pulseaudio
   /dev/snd/controlC1:  jmaillar   3511 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/main-swap
  MachineType: Hewlett-Packard HP ZBook 15 G2
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic.efi.signed 
root=UUID=79ab29f5-d9eb-4aff-bfb8-8639c60401cb ro quiet
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-66-generic N/A
   linux-backports-modules-4.4.0-66-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial xenial
  Uname: Linux 4.4.0-66-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (321 days ago)
  UserGroups: adm cdrom dip disk kismet kvm libvirtd lpadmin lxd plugdev 
sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/25/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M70 Ver. 01.15
  dmi.board.name: 2253
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 03.12
  dmi.chassis.asset.tag: CND54722DC
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM70Ver.01.15:bd04/25/2016:svnHewlett-Packard:pnHPZBook15G2:pvrA3009CD10002:rvnHewlett-Packard:rn2253:rvrKBCVersion03.12:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ZBook 15 G2
  dmi.product.version: A3009CD10002
  dmi.sys.vendor: Hewlett-Packard
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jmaillar   3496 F pulseaudio
   /dev/snd/controlC1:  jmaillar   3496 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/main-swap
  MachineType: Hewlett-Packard HP ZBook 15 G2
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic 
root=UUID=79ab29f5-d9eb-4aff-bfb8-8639c60401cb ro quiet
  ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-41-generic N/A
   linux-backports-modules-4.8.0-41-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial xenial
  Uname: Linux 4.8.0-41-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (322 days ago)
  UserGroups: adm cdrom dip disk kismet kvm libvirtd lpadmin lxd plugdev 
sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/25/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M70 Ver. 01.15
  dmi.board.name: 2253
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 03.12
  dmi.chassis.asset.tag: CND54722DC
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  

[Kernel-packages] [Bug 1497428] Re: kernel BUG at /build/buildd/linux-3.13.0/mm/page_alloc.c:968

[Craig Watcham]

Looks like this has been corrected, from a recent c4.8xl launch:
--
[0.00] Linux version 3.13.0-71-generic (buildd@lgw01-09) (gcc version 
4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #114-Ubuntu SMP Tue Dec 1 02:34:22 UTC 2015 
(Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic 
root=UUID=0fbd65e4-a082-4f5a-8392-49add7329657 ro console=tty1 console=ttyS0
[0.00] KERNEL supported cpus:
[0.00]   Intel GenuineIntel
[0.00]   AMD AuthenticAMD
[0.00]   Centaur CentaurHauls
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009dfff] usable
[0.00] BIOS-e820: [mem 0x0009e000-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000e-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0xefff] usable
[0.00] BIOS-e820: [mem 0xfc00-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x000f0fff] usable
--

Debug module output (for reference);
--
[6409565.542433] lp1497428: module verification failed: signature and/or  
required key missing - tainting kernel
[6409565.565990] pageblock_nr_pages 0x200
[6409565.568026] node 0 zone 0 info:
[6409565.569761] node 0 zone 0 provided page pfn 0xfff valid 1 present 1
[6409565.572417] node 0 zone 0 start pfn 0xe00 valid 1 present 1
[6409565.574936] node 0 zone 0 end pfn 0xfff valid 1 present 1
[6409565.577453] node 0 zone 0 page ea03ffc0 start_page 
ea038000 end_page ea03ffc0
[6409565.581422] node 0 zone 0 spans: provided pfn 1 start pfn 1 end pfn 1
[6409565.584305] node 0 zone 0 start pfn 0x1 spanned pages 0xfff end pfn 0x1000
[6409565.587379] node 0 zone 0 present pages 0xf9d managed pages 0xf88
[6409565.590125] node 0 start pfn 0x1 end pfn 0xf18000
[6409565.592238] node 0 normal pageblock multiple
[6409565.594218] node 0 zone 1 info:
[6409565.595756] node 0 zone 1 provided page pfn 0xf valid 0 present 0
[6409565.598642] node 0 zone 1 start pfn 0xffe00 valid 0 present 0
[6409565.601218] node 0 zone 1 end pfn 0xf valid 0 present 0
[6409565.603587] node 0 zone 1 page ea0003c0 start_page 
ea0003ff8000 end_page ea0003c0
[6409565.607428] node 0 zone 1 spans: provided pfn 1 start pfn 1 end pfn 1
[6409565.610296] node 0 zone 1 start pfn 0x1000 spanned pages 0xff000 end pfn 
0x10
[6409565.613730] node 0 zone 1 present pages 0xef000 managed pages 0xea2d3
[6409565.616697] node 0 start pfn 0x1 end pfn 0xf18000
[6409565.619146] node 0 normal pageblock multiple
[6409565.621321] node 0 zone 2 info:
[6409565.623000] node 0 zone 2 provided page pfn 0xf17fff valid 1 present 1
[6409565.625955] node 0 zone 2 start pfn 0xf17e00 valid 1 present 1
[6409565.628808] node 0 zone 2 end pfn 0xf17fff valid 1 present 1
[6409565.631467] node 0 zone 2 page ea003c5fffc0 start_page 
ea003c5f8000 end_page ea003c5fffc0
[6409565.635675] node 0 zone 2 spans: provided pfn 1 start pfn 1 end pfn 1
[6409565.638791] node 0 zone 2 start pfn 0x10 spanned pages 0xe18000 end 
pfn 0xf18000
[6409565.642571] node 0 zone 2 present pages 0x679100 managed pages 0x65aded
[6409565.645714] node 0 start pfn 0x1 end pfn 0xf18000
[6409565.648024] node 0 normal pageblock multiple
[6409565.650256] node 1 zone 2 info:
[6409565.651940] node 1 zone 2 provided page pfn 0xf0 valid 1 present 1
[6409565.654851] node 1 zone 2 start pfn 0xf0fe00 valid 1 present 1
[6409565.657571] node 1 zone 2 end pfn 0xf0 valid 1 present 1
[6409565.660316] node 1 zone 2 page ea003c3fffc0 start_page 
ea003c3f8000 end_page ea003c3fffc0
[6409565.664331] node 1 zone 2 spans: provided pfn 1 start pfn 1 end pfn 1
[6409565.667235] node 1 zone 2 start pfn 0x779100 spanned pages 0x796f00 end 
pfn 0xf1
[6409565.671038] node 1 zone 2 present pages 0x796f00 managed pages 0x7783b2
[6409565.673982] node 1 start pfn 0x779100 end pfn 0xf1
[6409565.676321] node 1 normal pageblock multiple
--

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

Title:
  kernel BUG at /build/buildd/linux-3.13.0/mm/page_alloc.c:968

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

Bug description:
  The kernel triggers a BUG when it finds it is in move_freepages() but
  the start and end pfns for the move are in different zones.

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

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

[Kernel-packages] [Bug 1672536] Re: task btrfs:841 blocked for more than 120 seconds.

[Karl-Philipp Richter]

** Description changed:

  After starting `btrfs scrub start /` `dmesg` contains
  
  ```
  [Mär13 21:49] INFO: task btrfs:841 blocked for more than 120 seconds.
  [  +0,09]   Tainted: PW  OE   4.8.0-41-generic #44-Ubuntu
  [  +0,05] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  +0,07] btrfs   D 9158a5cd3b08 0   841  26458 0x
  [  +0,05]  9158a5cd3b08 00ffadd9f58b 915bad6e1d80 
915986fb2c40
  [  +0,04]  9158a5cd3ae8 9158a5cd4000 915bac310714 
915986fb2c40
  [  +0,02]   915bac310718 9158a5cd3b20 
ae49bd35
  [  +0,03] Call Trace:
  [  +0,09]  [] schedule+0x35/0x80
  [  +0,03]  [] schedule_preempt_disabled+0xe/0x10
  [  +0,03]  [] __mutex_lock_slowpath+0xb9/0x130
  [  +0,02]  [] mutex_lock+0x1f/0x30
  [  +0,33]  [] btrfs_relocate_block_group+0x1a3/0x2a0 
[btrfs]
  [  +0,22]  [] btrfs_relocate_chunk.isra.40+0x49/0xd0 
[btrfs]
  [  +0,18]  [] __btrfs_balance+0x634/0xc70 [btrfs]
  [  +0,17]  [] btrfs_balance+0x2d0/0x5e0 [btrfs]
  [  +0,18]  [] btrfs_ioctl_balance+0x379/0x390 [btrfs]
  [  +0,18]  [] btrfs_ioctl+0xd1b/0x2010 [btrfs]
  [  +0,03]  [] ? __schedule+0x308/0x770
  [  +0,04]  [] ? hrtimer_try_to_cancel+0x2c/0x120
  [  +0,02]  [] ? do_nanosleep+0x96/0xf0
  [  +0,03]  [] do_vfs_ioctl+0xa3/0x610
  [  +0,03]  [] ? __hrtimer_init+0xa0/0xa0
  [  +0,02]  [] ? do_nanosleep+0x5a/0xf0
  [  +0,03]  [] SyS_ioctl+0x79/0x90
  [  +0,03]  [] entry_SYSCALL_64_fastpath+0x1e/0xa8
  [Mär13 21:51] INFO: task btrfs:841 blocked for more than 120 seconds.
  [  +0,10]   Tainted: PW  OE   4.8.0-41-generic #44-Ubuntu
  [  +0,04] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  +0,07] btrfs   D 9158a5cd3b08 0   841  26458 0x
  [  +0,05]  9158a5cd3b08 00ffadd9f58b 915bad6e1d80 
915986fb2c40
  [  +0,03]  9158a5cd3ae8 9158a5cd4000 915bac310714 
915986fb2c40
  [  +0,03]   915bac310718 9158a5cd3b20 
ae49bd35
  [  +0,03] Call Trace:
  [  +0,09]  [] schedule+0x35/0x80
  [  +0,03]  [] schedule_preempt_disabled+0xe/0x10
  [  +0,02]  [] __mutex_lock_slowpath+0xb9/0x130
  [  +0,03]  [] mutex_lock+0x1f/0x30
  [  +0,34]  [] btrfs_relocate_block_group+0x1a3/0x2a0 
[btrfs]
  [  +0,22]  [] btrfs_relocate_chunk.isra.40+0x49/0xd0 
[btrfs]
  [  +0,18]  [] __btrfs_balance+0x634/0xc70 [btrfs]
  [  +0,17]  [] btrfs_balance+0x2d0/0x5e0 [btrfs]
  [  +0,18]  [] btrfs_ioctl_balance+0x379/0x390 [btrfs]
  [  +0,18]  [] btrfs_ioctl+0xd1b/0x2010 [btrfs]
  [  +0,03]  [] ? __schedule+0x308/0x770
  [  +0,04]  [] ? hrtimer_try_to_cancel+0x2c/0x120
  [  +0,03]  [] ? do_nanosleep+0x96/0xf0
  [  +0,02]  [] do_vfs_ioctl+0xa3/0x610
  [  +0,03]  [] ? __hrtimer_init+0xa0/0xa0
  [  +0,03]  [] ? do_nanosleep+0x5a/0xf0
  [  +0,02]  [] SyS_ioctl+0x79/0x90
  [  +0,03]  [] entry_SYSCALL_64_fastpath+0x1e/0xa8
  [Mär13 21:53] INFO: task btrfs:841 blocked for more than 120 seconds.
  [  +0,11]   Tainted: PW  OE   4.8.0-41-generic #44-Ubuntu
  [  +0,05] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  +0,32] btrfs   D 9158a5cd3b08 0   841  26458 0x
  [  +0,05]  9158a5cd3b08 00ffadd9f58b 915bad6e1d80 
915986fb2c40
  [  +0,03]  9158a5cd3ae8 9158a5cd4000 915bac310714 
915986fb2c40
  [  +0,03]   915bac310718 9158a5cd3b20 
ae49bd35
  [  +0,03] Call Trace:
  [  +0,09]  [] schedule+0x35/0x80
  [  +0,03]  [] schedule_preempt_disabled+0xe/0x10
  [  +0,02]  [] __mutex_lock_slowpath+0xb9/0x130
  [  +0,03]  [] mutex_lock+0x1f/0x30
  [  +0,33]  [] btrfs_relocate_block_group+0x1a3/0x2a0 
[btrfs]
  [  +0,22]  [] btrfs_relocate_chunk.isra.40+0x49/0xd0 
[btrfs]
  [  +0,18]  [] __btrfs_balance+0x634/0xc70 [btrfs]
  [  +0,17]  [] btrfs_balance+0x2d0/0x5e0 [btrfs]
  [  +0,18]  [] btrfs_ioctl_balance+0x379/0x390 [btrfs]
  [  +0,18]  [] btrfs_ioctl+0xd1b/0x2010 [btrfs]
  [  +0,02]  [] ? __schedule+0x308/0x770
  [  +0,04]  [] ? hrtimer_try_to_cancel+0x2c/0x120
  [  +0,03]  [] ? do_nanosleep+0x96/0xf0
  [  +0,04]  [] do_vfs_ioctl+0xa3/0x610
  [  +0,02]  [] ? __hrtimer_init+0xa0/0xa0
  [  +0,03]  [] ? do_nanosleep+0x5a/0xf0
  [  +0,02]  [] SyS_ioctl+0x79/0x90
  [  +0,03]  [] entry_SYSCALL_64_fastpath+0x1e/0xa8
  [Mär13 21:55] INFO: task btrfs:841 blocked for more than 120 seconds.
  [  +0,11]   Tainted: PW  OE   4.8.0-41-generic #44-Ubuntu
  [  +0,06] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  +0,09] btrfs   D 9158a5cd3b08 0   841  26458 

[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument

[Mike Rushton]

We received the hardware back and have started testing all blockers
again. The latest test of the above mentioned PPA did not yield positive
results:

"Unable to find PowerPC CPU definition"

$ apt-cache policy qemu-system-ppc
qemu-system-ppc:
  Installed: 1:2.5+dfsg-5ubuntu10.10
  Candidate: 1:2.5+dfsg-5ubuntu10.10
  Version table:
 *** 1:2.5+dfsg-5ubuntu10.10 500
500 http://ppa.launchpad.net/ci-train-ppa-service/2502/ubuntu 
xenial/main ppc64el Packages
100 /var/lib/dpkg/status
 1:2.5+dfsg-5ubuntu10.9 500
500 http://ports.ubuntu.com/ubuntu-ports xenial-updates/main ppc64el 
Packages
 1:2.5+dfsg-5ubuntu10.6 500
500 http://ports.ubuntu.com/ubuntu-ports xenial-security/main ppc64el 
Packages
 1:2.5+dfsg-5ubuntu10 500
500 http://ports.ubuntu.com/ubuntu-ports xenial/main ppc64el Packages
$ uname -a
Linux fesenkov 4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:30:20 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux

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

Title:
  Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu
  failed: Invalid argument

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

Bug description:
  [Impact]

   * Some newer Power8 derivates fail to work correctly e.g. Power S822LC 
(8335-GTB) 

   * This is a toleration change (no exploitation) for those HW releases 
 following the SRU policy of "For Long Term Support releases we 
 regularly want to enable new hardware. Such changes are appropriate 
 provided that we can ensure not to affect upgrades on existing 
 hardware."

   * Without the Fix that hardware won't run Xenial guests under current 
 Xenials Qemu version

   * The fix lets processors that support it run in PowerISA 2.07 
 compatibility mode (plus a few no-op changes as backport 
 dependencies)

  
  [Test Case]

   * Run a Xenial Guest in KVM on one of the specific HW revisions being 
 affected.

  [Regression Potential]

   * Changes are PPC only, so fallout should be contained to that
   * Patches were created by IBM and in Upstream qemu since 2.7
   * The effective change is rather small, only allow different compat 
 level on this other cpu class
   * There are a few refactoring changes needed to get the backport done, 
 while they should be a no-op that is a regression potential (still 
 limited to ppc64el)

  [Other Info]
   
   * Needed for certifying this Hardware for Ubuntu


  
  Upon running the virtualization test from the certification test suite, the 
kvm guest test fails with the following error:

  kvm_init_vcpu failed: Invalid argument

  This same test works on multiple other IBM Power 8 and Openpower
  servers. kvm-ok tells us that kvm virtualization is supported. I have
  tried with SMT enabled and disabled. I have tried the latest cloud
  image as well as previous onces we had saved. I have tried running the
  qemu-system-ppc64 command found below manually with the same error.

  The full output from the test is as follows:

  Executing KVM Test
  DEBUG:root:Starting KVM Test
  DEBUG:root:Cloud image location specified: 
http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img.
  DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from 
http://10.1.10.2
  DEBUG:root:Creating cloud user-data
  DEBUG:root:Creating cloud meta-data
  I: -input-charset not specified, using utf-8 (detected in locale settings)
  Total translation table size: 0
  Total rockridge attributes bytes: 331
  Total directory bytes: 0
  Path table size(bytes): 10
  Max brk space used 0
  183 extents written (0 MB)
  DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img
  DEBUG:root:Attaching Cloud config disk
  DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic 
-net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 
-enable-kvm -machine pseries,usb=off -cpu POWER8 -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  INFO:root:Storing VM console output in 
/home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 22:18 seq
   crw-rw 1 root audio 116, 33 Jan 12 22:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 

[Kernel-packages] [Bug 1671063] Re: ubuntu_lttng_smoke_test failed on Yakkety s390x (zVM)

[Jonathan Rajotte Julien]

Hi Colin,

Please take a look at the following patch
https://lists.lttng.org/pipermail/lttng-dev/2017-March/026959.html

Could you report to us if it fixes your issue?

Please note that s390 is not supported/tested by LTTng-modules.

You probably encountered this bug since no syscalls tracepoints are
getting defined on lttng-modules side. Please take a look at this git
subtree [1] and the following readme [2] on how to generate it and add
the headers for the S390 architecture if you wish to.

Cheers

[1] https://github.com/lttng/lttng-modules/tree/master/instrumentation/syscalls
[2] 
https://github.com/lttng/lttng-modules/blob/master/instrumentation/syscalls/README

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

Title:
  ubuntu_lttng_smoke_test failed on Yakkety s390x (zVM)

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Two test cases failed on this arch:
  == lttng smoke test list kernel events ==
  PASSED (lttng list --kernel)
  Error: Unable to list system calls: Not enough memory
  Error: Command error
  FAILED (lttng list --kernel --syscall)
  FAILED (lttng list --kernel --syscall more output expected)
   
  == lttng smoke test trace open/close system calls ==
  ...
  FAILED (did not trace any open system calls)

  Please find attachment for complete log.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-40-generic 4.8.0-40.43
  ProcVersionSignature: Ubuntu 4.8.0-40.43-generic 4.8.17
  Uname: Linux 4.8.0-40-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Wed Mar  8 06:39:24 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=/dev/mapper/kl02vg01-root crashkernel=196M debug 
udev.log-priority=debug rd.udev.log_priority=debug BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-40-generic N/A
   linux-backports-modules-4.8.0-40-generic  N/A
   linux-firmware1.161.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1385113] Re: hid-generic 0005:099A:0500.0001: unknown main item tag 0x0

[Mal]

same, very annoying

Thinkpad T440, with Linux Mint 18.1 Cinnamon (based on Ubuntu 16.04) and
a Logitech K380 bluetooth keyboard

lsb_release -rd
Description:Linux Mint 18.1 Serena
Release:18.1

uname -a
Linux xochiquetzal 4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

the error, 2x (note it seems to reconnecct the device with a different
number):

[71585.431481] usb 2-7: USB disconnect, device number 12
[71585.902507] usb 2-7: new full-speed USB device number 14 using xhci_hcd
[71586.032157] usb 2-7: New USB device found, idVendor=8087, idProduct=07dc
[71586.032166] usb 2-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[71586.046505] Bluetooth: hci0: read Intel version: 370710018002030d55
[71586.046510] Bluetooth: hci0: Intel device is already patched. patch num: 55
[71594.739976] hid-generic 0005:046D:B342.0009: unknown main item tag 0x0
[71594.740229] input: Keyboard K380 as 
/devices/pci:00/:00:14.0/usb2/2-7/2-7:1.0/bluetooth/hci0/hci0:256/0005:046D:B342.0009/input/input25
[71594.740774] hid-generic 0005:046D:B342.0009: input,hidraw2: BLUETOOTH HID 
v42.00 Keyboard [Keyboard K380] on 5c:c5:d4:04:83:db
[71922.708526] usb 2-7: USB disconnect, device number 14
[71923.127502] usb 2-7: new full-speed USB device number 16 using xhci_hcd
[71923.256785] usb 2-7: New USB device found, idVendor=8087, idProduct=07dc
[71923.256790] usb 2-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[71923.271836] Bluetooth: hci0: read Intel version: 370710018002030d55
[71923.271838] Bluetooth: hci0: Intel device is already patched. patch num: 55
[71930.531386] hid-generic 0005:046D:B342.000A: unknown main item tag 0x0
[71930.531558] input: Keyboard K380 as 
/devices/pci:00/:00:14.0/usb2/2-7/2-7:1.0/bluetooth/hci0/hci0:256/0005:046D:B342.000A/input/input26
[71930.532179] hid-generic 0005:046D:B342.000A: input,hidraw2: BLUETOOTH HID 
v42.00 Keyboard [Keyboard K380] on 5c:c5:d4:04:83:db

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

Title:
  hid-generic 0005:099A:0500.0001: unknown main item tag 0x0

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

Bug description:
  Message with Mouse Bluetooth

  [   32.960478] hid-generic 0005:099A:0500.0001: unknown main item tag
  0x0

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-23-generic 3.16.0-23.31
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   3344 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Oct 24 05:22:54 2014
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2014-09-25 (29 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-23-generic 
root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet 
splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  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/1385113/+subscriptions

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

[Kernel-packages] [Bug 1672563] [NEW] ubuntu 16.04 doesnt boot normally on my asus k550vx

[farid]

Public bug reported:

i just can boot ubuntu 16.04 in nomodeset or acpi=off mode. and even in
this case when i try to install my nividia graphic cards driver, it
never boots again after installation.

my graphic card: nvidia 950m

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

Title:
  ubuntu 16.04 doesnt boot normally on my asus k550vx

Status in linux package in Ubuntu:
  New

Bug description:
  i just can boot ubuntu 16.04 in nomodeset or acpi=off mode. and even
  in this case when i try to install my nividia graphic cards driver, it
  never boots again after installation.

  my graphic card: nvidia 950m

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

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

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

[Brad Figg]

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

apport-collect 1672563

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

Title:
  ubuntu 16.04 doesnt boot normally on my asus k550vx

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  i just can boot ubuntu 16.04 in nomodeset or acpi=off mode. and even
  in this case when i try to install my nividia graphic cards driver, it
  never boots again after installation.

  my graphic card: nvidia 950m

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

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

[Kernel-packages] [Bug 1596469] Re: [Bug]tpm initialization fails on x86

[Tomas Winkler]

This is a BIOS issue can you please attach dmidecode of your platform, I'd like 
to know more detailed platform and bios information. 
Also please add the while dmesg and cat /proc/iomem
Thanks

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

Title:
  [Bug]tpm initialization fails on x86

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

Bug description:
  When trying to test TPM with Ubuntu 16.04 on Intel x86_64 platform, there's 
tpm initialization failure found in kernel log:
  root@SKLU1-leg:~# dmesg | grep -i tpm
  [0.00] ACPI: SSDT 0x7FFE4000 0004D6 (v02 Intel_ Tpm2Tabl 
1000 INTL 20141107)
  [0.00] ACPI: TPM2 0x7FFE2000 34 (v03 
  )
  [2.532245] ima: No TPM chip found, activating TPM-bypass!
  [3.489431] tpm_crb MSFT0101:00: can't request region for resource [mem 
0xfed40040-0xfed4103f]
  [3.489437] tpm_crb: probe of MSFT0101:00 failed with error -16

  which leads to tpm device missing under /dev:
  root@SKLU1-leg:~# ls -l /dev/tpm*
  ls: cannot access '/dev/tpm*': No such file or directory

  This error has been fixed with patch below, but not yet merged to upstream 
kernel:
  
http://git.infradead.org/users/jjs/linux-tpmdd.git/commit/0af6e0a2da2e4fedaa274da438d3b879192b

  Patch 0af6e0a has dependency to this patch:
  
http://git.infradead.org/users/jjs/linux-tpmdd.git/commit/3f944075e75e28c9cf1af8f82798398b
  So 0af6e0a has to be applied upon 3f94407, otherwise patch apply fails.

  I've verified with kernel 4.7-rc4 that above 2 patches can fix this TPM issue.
  So please Ubuntu team help on backporting these 2 patches into the kernel of 
their next release.

  PS, below are some information about Ubuntu & kernel & cpu info on my test 
server, for your reference:
  root@SKLU1-leg:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  Codename: xenial
  root@SKLU1-leg:~# uname -a
  Linux SKLU1-leg 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

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

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

[Kernel-packages] [Bug 1671063] Re: ubuntu_lttng_smoke_test failed on Yakkety s390x (zVM)

[Colin Ian King]

Thanks Jonathan, I'll get around to that first thing tomorrow morning.
Much appreciated.

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

Title:
  ubuntu_lttng_smoke_test failed on Yakkety s390x (zVM)

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Two test cases failed on this arch:
  == lttng smoke test list kernel events ==
  PASSED (lttng list --kernel)
  Error: Unable to list system calls: Not enough memory
  Error: Command error
  FAILED (lttng list --kernel --syscall)
  FAILED (lttng list --kernel --syscall more output expected)
   
  == lttng smoke test trace open/close system calls ==
  ...
  FAILED (did not trace any open system calls)

  Please find attachment for complete log.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-40-generic 4.8.0-40.43
  ProcVersionSignature: Ubuntu 4.8.0-40.43-generic 4.8.17
  Uname: Linux 4.8.0-40-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Wed Mar  8 06:39:24 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=/dev/mapper/kl02vg01-root crashkernel=196M debug 
udev.log-priority=debug rd.udev.log_priority=debug BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-40-generic N/A
   linux-backports-modules-4.8.0-40-generic  N/A
   linux-firmware1.161.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3

[Daniele]

Dear All,

I had exactly the same situation of post #23. Coming from Kubuntu 16.04, bought 
a new system Ryzen 1800x+GA-AB350 Gaming 3.
First boot, using the "old" SSD worked fine, so I decided to upgrade to version 
16.10. The procedure goes well, but after the reboot got plenty of error 
message "IRQ VECTOR 07". 
So I tried with a USB stick and Kubuntu live version 17.04 both beta 1 and 
Nightly but got the same error.
The only way to make the system working, is to manually select kernel 
4.4.0-64-generic from grub.

I've also tried to install ubuntu kernel 4.10 and 4.11rc1, but I always
get the same error.

Hope this helps

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

Title:
  System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 
motherboard,
  and it has a load of problems, starting with not being able to boot normally.

  During normal boot, on 16.10 as well as 17.04 beta:
  system doesn't boot normally, hangs with a lot of "unexpected irq trap at 
vector 07"
  messages displayed.

  
  Following advice from various places, I've tried:disable cpu freq governor 
and cpu handling in acpi settings

  1. add "acpi=off" to boot params

  That helps, allowing me to boot into recovery mode, though it leaves
  me with system seeing only one core, is really slow and still only
  boots in recovery mode.

  2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor
  and cpu handling in acpi settings. Boot with "quiet loglevel=3"
  option.

  That gets me even further - system sees all cores now. Still only recovery 
mode though,
  but its enough to get info for this bug report.

  Some observed problems:

  1. dmesg reports *a lot* of messages like this all the time:

  [  163.362068] ->handle_irq():  87a7e090, 
  [  163.362081] bad_chained_irq+0x0/0x40
  [  163.362089] ->handle_irq():  87a7e090, 
  [  163.362090] amd_gpio_irq_handler+0x0/0x200
  [  163.362090] ->irq_data.chip(): 88587e20, 
  [  163.362090] ioapic_ir_chip+0x0/0x120
  [  163.362090] ->action(): 884601c0
  [  163.362091]IRQ_NOPROBE set
  [  163.362099] ->handle_irq():  87a7e090, 
  [  163.362099] amd_gpio_irq_handler+0x0/0x200
  [  163.362100] ->irq_data.chip(): 88587e20, 
  [  163.362100] ioapic_ir_chip+0x0/0x120
  [  163.362101] ->action(): 884601c0

  I've tried to redirect dmesg to a file, stopped after a short while,
  it generated 400M of those.

  2. Systemd cannot start journald. Perhaps because it cannot cope with
  amount of kernel logs?

  3. Looking at pci, I've noticed something called AMDI0040
  (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010,
  AMDI0020, AMDI0030. Those however are mentioned in kernel source,
  kernel and google are completely silent about AMDI0040.

  
  Phoronix tested ryzen using different motherboard, and it worked better 
(though not well),
  so I suspect it is an issue with motherboard.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2015-08-06 (581 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-rc1-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1672198] Re: RTL8723b Kernel driver not loading on normal boot.

[SB]

It did start as I had to use kernel 4.8 in order to get my multimedia
keys and suspend to ram working on that machine. With Kernel 4.4 I had
to compile the the driver from lwfinger in order to use wifi.


I will test kernel 4.11 tomorrow and report.

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

Title:
  RTL8723b Kernel driver not loading on normal boot.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use a very low and laptop with a built in rtl8723b wifi card. I
  always used the driver from lwfinger on github and that one worked
  well.

  But now Ubuntu comes with a driver for this card but that does not work on 
normal boot.
  Strange thing is this driver is initialised after resume from suspend.

  So i blacklisted the kernel module with:
  echo "blacklist rtl8xxxu" | sudo tee /etc/modprobe.d/rtl8xxxu.conf

  and used the lwfinger driver from github again.

  So with rtl8xxu driver wifi card does not work on normal boot but does
  work when recovering from suspend to ram.

  Thank you. Bye.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.1
  InstallationDate: Installed on 2016-12-23 (79 days ago)
  InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Tags:  serena
  Uname: Linux 4.9.10-040910-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument

[Mike Rushton]

Just to be sure I installed qemu-system-ppc version 1:2.6.1+dfsg-
0ubuntu5.3 from yakkety-updates and the tests pass.

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

Title:
  Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu
  failed: Invalid argument

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

Bug description:
  [Impact]

   * Some newer Power8 derivates fail to work correctly e.g. Power S822LC 
(8335-GTB) 

   * This is a toleration change (no exploitation) for those HW releases 
 following the SRU policy of "For Long Term Support releases we 
 regularly want to enable new hardware. Such changes are appropriate 
 provided that we can ensure not to affect upgrades on existing 
 hardware."

   * Without the Fix that hardware won't run Xenial guests under current 
 Xenials Qemu version

   * The fix lets processors that support it run in PowerISA 2.07 
 compatibility mode (plus a few no-op changes as backport 
 dependencies)

  
  [Test Case]

   * Run a Xenial Guest in KVM on one of the specific HW revisions being 
 affected.

  [Regression Potential]

   * Changes are PPC only, so fallout should be contained to that
   * Patches were created by IBM and in Upstream qemu since 2.7
   * The effective change is rather small, only allow different compat 
 level on this other cpu class
   * There are a few refactoring changes needed to get the backport done, 
 while they should be a no-op that is a regression potential (still 
 limited to ppc64el)

  [Other Info]
   
   * Needed for certifying this Hardware for Ubuntu


  
  Upon running the virtualization test from the certification test suite, the 
kvm guest test fails with the following error:

  kvm_init_vcpu failed: Invalid argument

  This same test works on multiple other IBM Power 8 and Openpower
  servers. kvm-ok tells us that kvm virtualization is supported. I have
  tried with SMT enabled and disabled. I have tried the latest cloud
  image as well as previous onces we had saved. I have tried running the
  qemu-system-ppc64 command found below manually with the same error.

  The full output from the test is as follows:

  Executing KVM Test
  DEBUG:root:Starting KVM Test
  DEBUG:root:Cloud image location specified: 
http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img.
  DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from 
http://10.1.10.2
  DEBUG:root:Creating cloud user-data
  DEBUG:root:Creating cloud meta-data
  I: -input-charset not specified, using utf-8 (detected in locale settings)
  Total translation table size: 0
  Total rockridge attributes bytes: 331
  Total directory bytes: 0
  Path table size(bytes): 10
  Max brk space used 0
  183 extents written (0 MB)
  DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img
  DEBUG:root:Attaching Cloud config disk
  DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic 
-net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 
-enable-kvm -machine pseries,usb=off -cpu POWER8 -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  INFO:root:Storing VM console output in 
/home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 22:18 seq
   crw-rw 1 root audio 116, 33 Jan 12 22:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 12 22:45:34 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 
Pro
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard 
and Mouse
   Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1
  ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017
  

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

[bugproxy]

--- Comment From thiag...@br.ibm.com 2017-03-13 14:27 EDT---
Hello Canonical,

Let me provide a status update:

To fix this bug it's necessary to fix several issues with lifetime of
structures in the block subsystem, as well as a number of related race
conditions. A number of patches need to be backported to fix these
problems:

The "BDI lifetime fix" v3 series?, which was already merged into Linus'
tree:

f44f1ab5a2dc block: Unhash block device inodes on gendisk destruction
dc3b17cc8bf2 block: Use pointer to backing_dev_info from request_queue
d03f6cdc1fc4 block: Dynamically allocate and refcount backing_dev_info
b1d2dc5659b4 block: Make blk_get_backing_dev_info() safe without open bdev
efa7c9f97e3e block: Get rid of blk_get_backing_dev_info()

A couple of follow up fixes were merged for commits dc3b17cc8bf and
b1d2dc5659b4:

e17354961bb5 zram_drv: update for backing dev info changes
a5a79d00017c block: Initialize bd_bdi on inode initialization

The first 4 patches from the "block: Fix block device shutdown related
races" v2 series? were also merged:

4b8c861a7c79 block: Move bdev_unhash_inode() after invalidate_partition()
d06e05c026ab block: Unhash also block device inode for the whole device
cccd9fb9ec96 block: Revalidate i_bdev reference in bd_aquire()
165a5e22fafb block: Move bdi_unregister() to del_gendisk()

A couple of follow up fixes were also merged for commit 165a5e22fafb:

b6f8fec4448a block: Allow bdi re-registration
df23de55615f bdi: Fix use-after-free in wb_congested_put()

Commit df23de55615f depends on the following commit:

5f478e4ea5c5 block: fix double-free in the failure path of
cgwb_bdi_init()

In addition to the commits mentioned above, we will also need the
patches from v4 of the same series, which was posted today:

https://marc.info/?l=linux-block=148941806220331=2

I have a branch with the patches that were already merged upstream
backported on top of tag Ubuntu-4.4.0-65.86. Most of the commits didn't
have any conflicts, and the ones that did were simple to resolve.

I will attach the backported patches to this bug report when all of the
patches that we need are accepted upstream.

--
? https://marc.info/?l=linux-block=148604743126356=2
? https://marc.info/?l=linux-block=148769705431982=2

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

Title:
  UbuntuKVM guest crashed while running I/O stress test with Ubuntu
  kernel  4.4.0-47-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Attn. Canonical: For your awareness only at this time.

  == Comment: #0 - LEKSHMI C. PILLAI  - 2016-11-22 03:49:38 ==

  Machine INFO

  KVM HOST: luckyv1

  Guest :lucky05

  lucky05 crashed while running the I/O stress test for SAN disks.

  Installed lucky05 and enabled the xmon on that.After that started the
  RAW disk test on around 50 disks.After 6-7 hours after running,Now
  machine dropped into xmon.

  Logs:
  [25023.224182] Unable to handle kernel paging request for data at address 
0x
  [25023.224257] Faulting instruction address: 0xc0324c60
  cpu 0x3: Vector: 300 (Data Access) at [c000fffc3620]
  pc: c0324c60: locked_inode_to_wb_and_lock_list+0x50/0x290
  lr: c032831c: writeback_sb_inodes+0x30c/0x590
  sp: c000fffc38a0
 msr: 80019033
 dar: 0
   dsisr: 4000
current = 0xc000ff99e470
paca= 0xcfb41c80   softe: 0irq_happened: 0x01
  pid   = 14736, comm = kworker/u16:8
  enter ? for help
  [c000fffc3900] c032831c writeback_sb_inodes+0x30c/0x590
  [c000fffc3a10] c0328684 __writeback_inodes_wb+0xe4/0x150
  [c000fffc3a70] c0328aec wb_writeback+0x30c/0x450
  [c000fffc3b40] c03296b4 wb_workfn+0x264/0x570
  [c000fffc3c50] c00dd930 process_one_work+0x1e0/0x5a0
  [c000fffc3ce0] c00dde84 worker_thread+0x194/0x680
  [c000fffc3d80] c00e6980 kthread+0x110/0x130
  [c000fffc3e30] c0009538 ret_from_kernel_thread+0x5c/0xa4
  3:mon> f
  3:mon> th
  [c000fffc3900] c032831c writeback_sb_inodes+0x30c/0x590
  [c000fffc3a10] c0328684 __writeback_inodes_wb+0xe4/0x150
  [c000fffc3a70] c0328aec wb_writeback+0x30c/0x450
  [c000fffc3b40] c03296b4 wb_workfn+0x264/0x570
  [c000fffc3c50] c00dd930 process_one_work+0x1e0/0x5a0
  [c000fffc3ce0] c00dde84 worker_thread+0x194/0x680
  [c000fffc3d80] c00e6980 kthread+0x110/0x130
  [c000fffc3e30] c0009538 ret_from_kernel_thread+0x5c/0xa4 
  3:mon> sh
  [27384.651055] INFO: rcu_sched detected stalls on CPUs/tasks:
  [27384.651220]  (detected by 4, t=40598 jiffies, g=2849830, c=2849829, q=992)
  [27384.651286] All QSes seen, last rcu_sched kthread activity 40596 
(4301188714-4301148118), jiffies_till_next_fqs=1, root ->qsmask 0x0
  

[Kernel-packages] [Bug 1672198] Re: RTL8723b Kernel driver not loading on normal boot.

[SB]

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

Title:
  RTL8723b Kernel driver not loading on normal boot.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use a very low and laptop with a built in rtl8723b wifi card. I
  always used the driver from lwfinger on github and that one worked
  well.

  But now Ubuntu comes with a driver for this card but that does not work on 
normal boot.
  Strange thing is this driver is initialised after resume from suspend.

  So i blacklisted the kernel module with:
  echo "blacklist rtl8xxxu" | sudo tee /etc/modprobe.d/rtl8xxxu.conf

  and used the lwfinger driver from github again.

  So with rtl8xxu driver wifi card does not work on normal boot but does
  work when recovering from suspend to ram.

  Thank you. Bye.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.1
  InstallationDate: Installed on 2016-12-23 (79 days ago)
  InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Tags:  serena
  Uname: Linux 4.9.10-040910-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1672344] Re: 4.4.0-1008.17 - aws failed with kernel security test 152

[Steve Beattie]

Thanks for the report. Given that the kernel version is larger than
4.4.0-48, it should be skipping the line that resets the expected value
to 0; it looks like the version comparison is falling back to the string
version when handling the abi portion of the version (likely due to
python-apt not being installed), and because of *that*, it's treating
the ABI version of 1000+ as less than 48.

Realistically, the change in the setting as described in bug 1636461 should 
have made it out to all of the 4.4 kernels we ship, so I've gone ahead and 
removed that exception path from the test, committed in 
https://git.launchpad.net/qa-regression-testing/commit/?id=d67eca192876d31892d50ecd410a2b658a8d871a
. Closing, please re-open if that doesn't address the issue.

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

** Changed in: qa-regression-testing
   Status: New => Fix Released

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

Title:
  4.4.0-1008.17 - aws failed with kernel security test 152

Status in QA Regression Testing:
  Fix Released
Status in linux package in Ubuntu:
  Invalid

Bug description:
  test_152_sysctl_disables_apparmor_unpriv_userns failed on
  4.4.0-1008.17 - aws

  This issue can't be found on 4.4.0-67.88 generic kernel for aws.
  There was once a similar bug for this, please refer to bug 1636461

  As the kernel version here is bigger than '4.4.0-46', the expected
  return value is 0, but the test returned 1 instead.

  FAIL: test_152_sysctl_disables_apparmor_unpriv_userns 
(__main__.KernelSecurityTest)
  unprivileged_userns_apparmor_policy sysctl supported
  --
  Traceback (most recent call last):
  File "./test-kernel-security.py", line 1925, in 
test_152_sysctl_disables_apparmor_unpriv_userns
  self._test_sysctl_value('kernel/unprivileged_userns_apparmor_policy', 
expected, exists=exists)
  File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1182, in _test_sysctl_value
  self.assertEqual(value, expected, report)
  AssertionError: /proc/sys/kernel/unprivileged_userns_apparmor_policy is not 
0: 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1672344/+subscriptions

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

[Kernel-packages] [Bug 1590844] Re: Call with Bluetooth headset not working [Meizu Pro 5 Ubuntu Edition]

[Stefan Mikulaj]

Could this be just a kernel issue? I had Flyme installed on my Pro 5 for
a couple a days and I did not reflashed the whole system, just restored
it with TWRP and yes, Android Flyme latest stable had suddenly an issue
with a noise and distortion when using a Bluetooth. Then I realised that
I have not reflashed it ,just restored it. Then I flashed the Flyme
update and again restored the image with TWRP and problem with bluetooth
has gone. So it might be a worth to look on kernel, files it contains
and the configuration.

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

Title:
  Call with Bluetooth headset not working [Meizu Pro 5 Ubuntu Edition]

Status in Canonical System Image:
  Confirmed
Status in turbo:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  My bluetooth headset perfectly connects to my Meizu Pro 5. However,
  the sound quality is so poor (a lot of noise) such that you don't
  understand your communication partner. Note that the headset works
  perfectly together with Ubuntu on my Nexus 4.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+subscriptions

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

[Kernel-packages] [Bug 1672470] [NEW] ip_rcv_finish() NULL pointer kernel panic

[Dan Streetman]

Public bug reported:

The br_netfilter module processes packets traveling through its bridge,
and while processing each skb it places a special fake dst onto the skb.
When the skb leaves the bridge, it removes the fake dst and places a
real dst onto it.  However, it uses a hook to do this, and when the
br_netfilter module is unloading it unregisters that hook.  Any skbs
that are currently being processed in the bridge by the br_netfilter
module, but that leave the bridge after the hook is unregistered (or,
during br_netfilter module load, before the hook is registered) will
still have the fake dst; when other code then tries to process that dst,
it causes a kernel panic because the dst is invalid.

Recent upstream discussion:
https://www.spinics.net/lists/netdev/msg416912.html

Upstream patch (not yet merged into net-next):
https://patchwork.ozlabs.org/patch/738275/

example panic report:

[ 214.518262] BUG: unable to handle kernel NULL pointer dereference at (null)
[ 214.612199] IP: [< (null)>] (null)
[ 214.672744] PGD 0 [ 214.696887] Oops: 0010 [#1] SMP [ 214.735697] Modules 
linked in: br_netfilter(+) tun 8021q bridge stp llc bonding iTCO_wdt 
iTCO_vendor_support tpm_tis tpm kvm_intel kvm irqbypass sb_edac edac_core ixgbe 
mdio ipmi_si ipmi_msghandler lpc_ich mfd_core mousedev evdev igb dca 
procmemro(O) nokeyctl(O) noptrace(O)
[ 215.029240] CPU: 34 PID: 0 Comm: swapper/34 Tainted: G O 4.4.39 #1
[ 215.116720] Hardware name: Cisco Systems Inc UCSC-C220-M3L/UCSC-C220-M3L, 
BIOS C220M3.2.0.13a.0.0713160937 07/13/16
[ 215.241644] task: 882038fb4380 ti: 8810392b task.ti: 
8810392b
[ 215.331207] RIP: 0010:[<>] [< (null)>] (null)
[ 215.420877] RSP: 0018:88103fec3880 EFLAGS: 00010286
[ 215.484436] RAX: 881011631000 RBX: 881011067100 RCX: 
[ 215.569836] RDX:  RSI:  RDI: 881011067100
[ 215.655234] RBP: 88103fec38a8 R08: 0008 R09: 8810116300a0
[ 215.740629] R10:  R11:  R12: 881018917dce
[ 215.826030] R13: 81c9be00 R14: 81c9be00 R15: 881011630078
[ 215.911432] FS: () GS:88103fec() 
knlGS:
[ 216.008274] CS: 0010 DS:  ES:  CR0: 80050033
[ 216.077032] CR2:  CR3: 001011b9d000 CR4: 001406e0
[ 216.162430] Stack:
[ 216.186461] 8157d7f9 881011067100 881018917dce 
88101163
[ 216.275407] 81c9be00 88103fec3918 8157e0db 

[ 216.364352]    

[ 216.453301] Call Trace:
[ 216.482536]  [ 216.505533] [] ? 
ip_rcv_finish+0x99/0x320
[ 216.575442] [] ip_rcv+0x25b/0x370
[ 216.634842] [] __netif_receive_skb_core+0x2cb/0xa20
[ 216.712965] [] __netif_receive_skb+0x18/0x60
[ 216.783801] [] netif_receive_skb_internal+0x23/0x80
[ 216.861921] [] netif_receive_skb+0x1c/0x70
[ 216.930686] [] br_handle_frame_finish+0x1b9/0x5b0 [bridge]
[ 217.016091] [] ? ___slab_alloc+0x1d0/0x440
[ 217.084849] [] br_nf_pre_routing_finish+0x174/0x3d0 
[br_netfilter]
[ 217.178568] [] ? br_nf_pre_routing+0x97/0x470 [br_netfilter]
[ 217.266052] [] ? br_handle_local_finish+0x80/0x80 [bridge]
[ 217.351450] [] br_nf_pre_routing+0x1a7/0x470 [br_netfilter]
[ 217.437891] [] nf_iterate+0x5d/0x70
[ 217.499367] [] nf_hook_slow+0x64/0xc0
[ 217.562928] [] br_handle_frame+0x1b9/0x290 [bridge]
[ 217.641048] [] ? br_handle_local_finish+0x80/0x80 [bridge]
[ 217.726446] [] __netif_receive_skb_core+0x342/0xa20
[ 217.804566] [] ? tcp4_gro_receive+0x126/0x1d0
[ 217.876445] [] ? inet_gro_receive+0x1c6/0x250
[ 217.948322] [] __netif_receive_skb+0x18/0x60
[ 218.019161] [] netif_receive_skb_internal+0x23/0x80
[ 218.097281] [] napi_gro_receive+0xc3/0x110
[ 218.166051] [] ixgbe_clean_rx_irq+0x52f/0xa70 [ixgbe]
[ 218.246255] [] ixgbe_poll+0x438/0x790 [ixgbe]
[ 218.318131] [] net_rx_action+0x1ee/0x320
[ 218.384813] [] ? handle_irq_event_percpu+0x167/0x1d0
[ 218.463973] [] __do_softirq+0x101/0x280
[ 218.529608] [] irq_exit+0x8e/0x90
[ 218.589007] [] do_IRQ+0x54/0xd0
[ 218.646323] [] common_interrupt+0x82/0x82

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress


** Tags: sts

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

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

** Tags added: sts

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

Title:
  ip_rcv_finish() NULL pointer kernel panic

Status in linux package in Ubuntu:
  In Progress

Bug description:
  The br_netfilter module processes packets traveling through its
  bridge, and while processing each skb it places a special fake dst
  onto the skb.  When 

[Kernel-packages] [Bug 1671459] alkaid (amd64) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-113.160~precise1-generic/alkaid__3.13.0-113.160~precise1__2017-03-14_01-34-00/results-index.html

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

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1671232
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1655978] Re: Bluetooth not working in Ubuntu 16.4 LTS

[Launchpad Bug Tracker]

[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/1655978

Title:
  Bluetooth not working in Ubuntu 16.4 LTS

Status in linux package in Ubuntu:
  Expired

Bug description:
  Bluetooth not working in Ubuntu 16.4 LTS

  Dear,

  I want to send files from my phone to my Laptop and vice versa through
  Bluetooth. But the Bluetooth on my system doesn't work. When I turn on
  the Bluetooth switch in System Settings > Bluetooth, nothing happens
  and also the visibility switch on the right hand side is always
  disabled. please resolve the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  naveen 1643 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jan 12 19:33:21 2017
  HibernationDevice: RESUME=UUID=f3d17055-5b0c-4721-97fe-46797078d645
  InstallationDate: Installed on 2015-07-25 (536 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=8f697990-854f-4760-a486-9c9ba3bf274e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2017-01-09 (2 days ago)
  dmi.bios.date: 01/24/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.66
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 166D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 09.4C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.66:bd01/24/2013:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr05941120461610100:rvnHewlett-Packard:rn166D:rvr09.4C:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion g4 Notebook PC
  dmi.product.version: 05941120461610100
  dmi.sys.vendor: Hewlett-Packard

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[Ying-Chun Liu]

I've tried manually copy the binary blobs into /boot and the rainbow
square disappeared. And when the power is not enough it displayed a
"lightning" icon. So if we rebuild an image based on the gadget in edge
channel we should be able to fix the problem.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1664809] Re: [0bda:0328] Card reader failed after S3

[AceLan Kao]

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

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

Title:
  [0bda:0328] Card reader failed after S3

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

Bug description:
  Summary: [0bda:0328] Card reader failed after S3

  Steps:
  1. Check card reader can be used before S3
  2. Enter into S3
  3. Resume from S3
  4. Insert SD/MMC/SDHC into the card reader

  Expected results: Card reader passed after S3

  Actual results: Card reader failed after S3
  The card reader device is gone from lsusb
  Bus 002 Device 002: ID 0bda:0328 Realtek Semiconductor Corp.

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

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

[Kernel-packages] [Bug 1668031] Re: Network adapter keeps on hanging up

[Kai-Heng Feng]

Gerardus,

Can you make a Zesty LiveUSB and test if this issue happens?

I just grabbed a Killer 1535 and seems like the issue does not happen on
Zesty.

I'd like to make sure this issue is solved in 4.10, so I can bisect and
backport needed patch.

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

Title:
  Network adapter keeps on hanging up

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Every hour or so, I'm unable to access the internet through this
  laptop. dmesg usually reports errors related to the network adapter,
  but not always. Disconnecting from the current Wifi network and
  connecting to another, usually works. Immediately connecting to the
  original network after that does not cause the problem to reoccur. At
  least, not for another hour or so.

  I'm not sure how to better describe this bug.

  The network also provides a nfs drive that is mounted on the laptop,
  if that is significant.

  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
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ruud   2810 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Feb 26 02:13:55 2017
  HibernationDevice: RESUME=UUID=2f2d2c45-4fef-49ec-932a-8314b15c2f6b
  InstallationDate: Installed on 2016-11-08 (109 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-39-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-39-generic N/A
   linux-backports-modules-4.8.0-39-generic  N/A
   linux-firmware1.162
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0T3FTF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[Joseph Salisbury]

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: Tim Gardner (timg-tpi) => 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/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 1671459] alkaid (i386) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-113.160~precise1-generic/alkaid__3.13.0-113.160~precise1__2017-03-14_01-55-00/results-index.html

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

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1671232
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

[Brad Figg]

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-113.160~precise1-generic/alkaid__3.13.0-113.160~precise1__2017-03-14_02-15-00/results-index.html

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

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1671232
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1655521] Re: package linux-image-4.8.0-34-generic 4.8.0-34.36 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Launchpad Bug Tracker]

[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/1655521

Title:
  package linux-image-4.8.0-34-generic 4.8.0-34.36 failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Expired

Bug description:
  Just trying to update using Software Updater

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-34-generic 4.8.0-34.36
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mitchell   3143 F pulseaudio
   /dev/snd/controlC1:  mitchell   3143 F pulseaudio
   /dev/snd/controlC0:  mitchell   3143 F pulseaudio
  Date: Tue Jan 10 19:57:12 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2015-08-10 (519 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=195540f3-343e-4313-8a47-8f1fd8303313 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-36ubuntu11
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.8.0-34-generic 4.8.0-34.36 failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F10
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-UD5H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97X-UD5H
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1671854] Re: Bluetooth not enabling

[Kai-Heng Feng]

Is the bluetooth a USB device?
At least it's not listed in your USB devices.

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

Title:
  Bluetooth not enabling

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

Bug description:
  i m using hp probook 6460b and i am unbale to enable my bluetooth. i
  have tried everything i can find on google and http://askubuntu.com.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50 [modified: 
boot/vmlinuz-4.4.0-31-generic]
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kamran  F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Mar 10 20:37:29 2017
  HibernationDevice: RESUME=UUID=4c928787-6e98-4d4c-9712-faabc24813da
  InstallationDate: Installed on 2017-03-09 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 003: ID 0461:4dc7 Primax Electronics, Ltd 
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP ProBook 6460b
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=e339ab8f-1d8f-44ed-bba2-a8e950cdbe55 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/26/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCE Ver. F.08
  dmi.board.name: 161D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.45
  dmi.chassis.asset.tag: CNU14903Y9
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCEVer.F.08:bd08/26/2011:svnHewlett-Packard:pnHPProBook6460b:pvrA0001D02:rvnHewlett-Packard:rn161D:rvrKBCVersion97.45:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 6460b
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1672048] Re: Touchpad not working in a fresh install of Ubuntu 16.04, it works in a parallel intallation of Windows7.

[Seth Arnold]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  Touchpad not working in a fresh install of Ubuntu 16.04, it works in a
  parallel intallation of Windows7.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Touchpad not working in a fresh install of Ubuntu 16.04, it works in a 
parallel intallation of Windows7.
  No touchpad entry is found in /proc/bus/input/devices, see attachment.
  Laptop model: Akoya E6240.
  Touchpad Model (as obtained after booting Windows8): Synaptics Click Pad

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-3.11.0-15-generic 3.11.0-15.23
  ProcVersionSignature: Ubuntu 4.8.0-39.42~16.04.1-generic 4.8.17

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

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

[Kernel-packages] [Bug 1671996] Re: package linux-image-extra-4.4.0-38-generic (not installed) failed to install/upgrade: package linux-image-extra-4.4.0-38-generic is not ready for configuration cann

[Joseph Salisbury]

You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"


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

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04 LTS several problems after updating from previous version 14.xx. 
Cant get packages installed.
  For example these lines give nothing on screen, 1) cat 
/proc/version_signature > version.log
  2) sudo lspci -vnvn > lspci-vnvn.log

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-38-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kari   1523 F pulseaudio
  Date: Sat Mar  4 09:41:34 2017
  DuplicateSignature:
   package:linux-image-extra-4.4.0-38-generic:(not installed)
   Processing triggers for shared-mime-info (1.5-2ubuntu0.1) ...
   dpkg: error processing package linux-image-extra-4.4.0-38-generic 
(--configure):
package linux-image-extra-4.4.0-38-generic is not ready for configuration
  ErrorMessage: package linux-image-extra-4.4.0-38-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
  HibernationDevice: RESUME=UUID=66d27ffa-9c2e-4c7b-ae16-ea787f091715
  InstallationDate: Installed on 2016-08-14 (208 days ago)
  InstallationMedia: Ubuntu 16.04 LTS (Finnish Remix) "Xenial Xerus" - Release 
amd64 (20160420.1)
  MachineType: LENOVO 1951FDG
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=75be3895-5a85-4082-806c-c484404bbc41 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2
  SourcePackage: linux
  Title: package linux-image-extra-4.4.0-38-generic (not installed) failed to 
install/upgrade: package linux-image-extra-4.4.0-38-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/22/2006
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79ETC9WW (2.09 )
  dmi.board.name: 1951FDG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr79ETC9WW(2.09):bd12/22/2006:svnLENOVO:pn1951FDG:pvrThinkPadT60:rvnLENOVO:rn1951FDG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 1951FDG
  dmi.product.version: ThinkPad T60
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1672198] Re: RTL8723b Kernel driver not loading on normal boot.

[Joseph Salisbury]

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-rc2


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

Title:
  RTL8723b Kernel driver not loading on normal boot.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use a very low and laptop with a built in rtl8723b wifi card. I
  always used the driver from lwfinger on github and that one worked
  well.

  But now Ubuntu comes with a driver for this card but that does not work on 
normal boot.
  Strange thing is this driver is initialised after resume from suspend.

  So i blacklisted the kernel module with:
  echo "blacklist rtl8xxxu" | sudo tee /etc/modprobe.d/rtl8xxxu.conf

  and used the lwfinger driver from github again.

  So with rtl8xxu driver wifi card does not work on normal boot but does
  work when recovering from suspend to ram.

  Thank you. Bye.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.1
  InstallationDate: Installed on 2016-12-23 (79 days ago)
  InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Tags:  serena
  Uname: Linux 4.9.10-040910-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1672200] Re: Kernel error on i915 gpu driver

[Joseph Salisbury]

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-rc2

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

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

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

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

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

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

Title:
  Kernel error on i915 gpu driver

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

Bug description:
  The following error (warning?) shows up in dmesg during every boot:

  [3.244312] [ cut here ]
  [3.244397] WARNING: CPU: 0 PID: 170 at 
/build/linux-Nasqxe/linux-4.4.0/drivers/gpu/drm/i915/intel_fbdev.c:406 
intel_fb_initial_config+0x2d4/0x5f0 [i915]()
  [3.244410] WARN_ON(!encoder->crtc)
  [3.244413] Modules linked in:
  [3.244419]  i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect 
sysimgblt fb_sys_fops b44 drm ahci ssb psmouse pata_acpi libahci mii wmi fjes 
video
  [3.244451] CPU: 0 PID: 170 Comm: kworker/u4:6 Not tainted 
4.4.0-66-generic #87-Ubuntu
  [3.244462] Hardware name: Hewlett-Packard HP Compaq nx7400 
(RB525UT#ABA)/30A2, BIOS 68YGU Ver. F.07 07/28/2006
  [3.244477] Workqueue: events_unbound async_run_entry_fn
  [3.244484]  c1adf967 ebf0fd93 0286 f5da5d04 c13ac15f f5da5d44 
f8d3b99c f5da5d34
  [3.244499]  c1070457 f8d46600 f5da5d64 00aa f8d3b99c 0196 
f8ceb9a4 f8ceb9a4
  [3.244514]   0001 0001 f5da5d50 c10704ce 0009 
f5da5d44 f8d46600
  [3.244530] Call Trace:
  [3.244541]  [] dump_stack+0x58/0x79
  [3.244550]  [] warn_slowpath_common+0x87/0xc0
  [3.244615]  [] ? intel_fb_initial_config+0x2d4/0x5f0 [i915]
  [3.244678]  [] ? intel_fb_initial_config+0x2d4/0x5f0 [i915]
  [3.244687]  [] warn_slowpath_fmt+0x3e/0x60
  [3.244750]  [] intel_fb_initial_config+0x2d4/0x5f0 [i915]
  [3.244759]  [] ? idr_alloc+0xa4/0x120
  [3.244823]  [] ? intel_crtc_fb_gamma_get+0x40/0x40 [i915]
  [3.244847]  [] drm_setup_crtcs+0x21f/0xa90 [drm_kms_helper]
  [3.244866]  [] ? 
drm_helper_probe_single_connector_modes_merge_bits+0x1e3/0x480 [drm_kms_helper]
  [3.244879]  [] ? schedule+0x2d/0x80
  [3.244898]  [] drm_fb_helper_initial_config+0xbc/0x400 
[drm_kms_helper]
  [3.244911]  [] ? put_prev_entity+0x33/0xcc0
  [3.244919]  [] ? pick_next_task_fair+0x501/0x520
  [3.244982]  [] intel_fbdev_initial_config+0x19/0x20 [i915]
  [3.244991]  [] async_run_entry_fn+0x4e/0x170
  [3.245000]  [] process_one_work+0x121/0x3f0
  [3.245009]  [] worker_thread+0x37/0x490
  [3.245017]  [] ? process_one_work+0x3f0/0x3f0
  [3.245025]  [] kthread+0xa6/0xc0
  [3.245034]  [] ret_from_kernel_thread+0x21/0x38
  [3.245042]  [] ? kthread_create_on_node+0x170/0x170
  [3.245049] ---[ end trace 0bd04c67fb0cdbfa ]---
  [3.251264] fbcon: inteldrmfb (fb0) is primary device
  [3.251911] [ cut here ]
  [3.251933] WARNING: CPU: 0 PID: 170 at 
/build/linux-Nasqxe/linux-4.4.0/drivers/gpu/drm/drm_atomic_helper.c:723 
drm_atomic_helper_update_legacy_modeset_state+0x26a/0x280 [drm_kms_helper]()
  [3.251945] Modules linked in: i915 i2c_algo_bit drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops b44 drm ahci ssb psmouse 
pata_acpi libahci mii wmi fjes video
  [3.251949] CPU: 0 PID: 170 Comm: kworker/u4:6 Tainted: GW   
4.4.0-66-generic #87-Ubuntu
  [3.251950] Hardware name: Hewlett-Packard HP Compaq nx7400 
(RB525UT#ABA)/30A2, BIOS 68YGU Ver. F.07 07/28/2006
  [3.251956] Workqueue: events_unbound async_run_entry_fn
  [3.251962]  c1adf967 ebf0fd93 0286 f5da5b3c c13ac15f  
f85c51f0 f5da5b6c
  [3.251966]  c1070457 c19d054c  00aa f85c51f0 02d3 
f85bb98a f85bb98a
  [3.251970]  f67f8800  f07fc400 f5da5b7c c1070562 0009 
 f5da5ba4
  [3.251971] Call Trace:
  [3.251977]  [] dump_stack+0x58/0x79
  [3.251981]  [] warn_slowpath_common+0x87/0xc0
  [3.251994]  [] ? 

[Kernel-packages] [Bug 1672318] Re: package linux-image-extra-3.13.0-108-generic 3.13.0-108.155 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before

[Joseph Salisbury]

You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"


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

Title:
  package linux-image-extra-3.13.0-108-generic 3.13.0-108.155 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  happened during the post trigger install part

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.13.0-108-generic 3.13.0-108.155
  ProcVersionSignature: Ubuntu 3.13.0-110.157-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-110-generic i686
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  debbie 1478 F pulseaudio
  Date: Mon Mar 13 09:23:15 2017
  DuplicateSignature: 
package:linux-image-extra-3.13.0-108-generic:3.13.0-108.155:package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  HibernationDevice: RESUME=UUID=b15bc548-bf77-4173-becf-5d0aec058133
  InstallationDate: Installed on 2011-10-11 (1979 days ago)
  InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1)
  MachineType: DIXONSXP DIXONSXP
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-110-generic 
root=UUID=efb07609-e50d-45ac-9c35-59f2317bdea0 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.12
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-extra-3.13.0-108-generic 3.13.0-108.155 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to trusty on 2016-09-08 (185 days ago)
  dmi.bios.date: 04/12/2007
  dmi.bios.vendor: DIXONSXP
  dmi.bios.version: 1.00.DIX
  dmi.board.name: DIXONSXP
  dmi.board.vendor: DIXONSXP
  dmi.chassis.type: 10
  dmi.chassis.vendor: DIXONSXP
  dmi.modalias: 
dmi:bvnDIXONSXP:bvr1.00.DIX:bd04/12/2007:svnDIXONSXP:pnDIXONSXP:pvr:rvnDIXONSXP:rnDIXONSXP:rvr:cvnDIXONSXP:ct10:cvr:
  dmi.product.name: DIXONSXP
  dmi.sys.vendor: DIXONSXP

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

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

[Kernel-packages] [Bug 1672510] [NEW] kernel selftests ADT failure with linux 4.10.0-13.15 on ppc64el

[Seth Forshee]

Public bug reported:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-zesty/zesty/ppc64el/l/linux/20170311_003703_69a51@/log.gz

Error building some of the tests, likely because of generating position
independent executables by default:

  ptrace-gpr.c: In function ‘gpr’:
  ptrace-gpr.c:30:2: error: PIC register clobbered by ‘r30’ in ‘asm’
asm __volatile__(
^~~
  make[1]: *** [ptrace-gpr] Error 1
  ptrace-tm-gpr.c: In function ‘tm_gpr’:
  ptrace-tm-gpr.c:34:2: error: PIC register clobbered by ‘r30’ in ‘asm’
asm __volatile__(
^~~
  make[1]: *** [ptrace-tm-gpr] Error 1
  ptrace-tm-spd-gpr.c: In function ‘tm_spd_gpr’:
  ptrace-tm-spd-gpr.c:41:2: error: PIC register clobbered by ‘r30’ in ‘asm’
asm __volatile__(
^~~
  make[1]: *** [ptrace-tm-spd-gpr] Error 1
  make[1]: Target 'all' not remade because of errors.
  make: *** [ptrace] Error 2

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

** Affects: linux (Ubuntu Zesty)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

** Also affects: linux (Ubuntu Zesty)
   Importance: Medium
 Assignee: Seth Forshee (sforshee)
   Status: In Progress

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

Title:
  kernel selftests ADT failure with linux 4.10.0-13.15 on ppc64el

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

Bug description:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/ppc64el/l/linux/20170311_003703_69a51@/log.gz

  Error building some of the tests, likely because of generating
  position independent executables by default:

ptrace-gpr.c: In function ‘gpr’:
ptrace-gpr.c:30:2: error: PIC register clobbered by ‘r30’ in ‘asm’
  asm __volatile__(
  ^~~
make[1]: *** [ptrace-gpr] Error 1
ptrace-tm-gpr.c: In function ‘tm_gpr’:
ptrace-tm-gpr.c:34:2: error: PIC register clobbered by ‘r30’ in ‘asm’
  asm __volatile__(
  ^~~
make[1]: *** [ptrace-tm-gpr] Error 1
ptrace-tm-spd-gpr.c: In function ‘tm_spd_gpr’:
ptrace-tm-spd-gpr.c:41:2: error: PIC register clobbered by ‘r30’ in ‘asm’
  asm __volatile__(
  ^~~
make[1]: *** [ptrace-tm-spd-gpr] Error 1
make[1]: Target 'all' not remade because of errors.
make: *** [ptrace] Error 2

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

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

[Kernel-packages] [Bug 1672486] [NEW] arm64: Workaround QDF2400 erratum 0065

[dann frazier]

Public bug reported:

QDF2400 platforms require an erratum workaround to avoid a memory
corruption issue. This was fixed upstream in the following commit:

commit 90922a2d03d84de36bf8a9979d62580102f31a92
Author: Shanker Donthineni 
Date:   Tue Mar 7 08:20:38 2017 -0600

irqchip/gicv3-its: Add workaround for QDF2400 ITS erratum 0065

On Qualcomm Datacenter Technologies QDF2400 SoCs, the ITS hardware
implementation uses 16Bytes for Interrupt Translation Entry (ITE),
but reports an incorrect value of 8Bytes in GITS_TYPER.ITTE_size.

It might cause kernel memory corruption depending on the number
of MSI(x) that are configured and the amount of memory that has
been allocated for ITEs in its_create_device().

This patch fixes the potential memory corruption by setting the
correct ITE size to 16Bytes.

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: dann frazier (dannf)
 Status: In Progress

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

Title:
  arm64: Workaround QDF2400 erratum 0065

Status in linux package in Ubuntu:
  In Progress

Bug description:
  QDF2400 platforms require an erratum workaround to avoid a memory
  corruption issue. This was fixed upstream in the following commit:

  commit 90922a2d03d84de36bf8a9979d62580102f31a92
  Author: Shanker Donthineni 
  Date:   Tue Mar 7 08:20:38 2017 -0600

  irqchip/gicv3-its: Add workaround for QDF2400 ITS erratum 0065
  
  On Qualcomm Datacenter Technologies QDF2400 SoCs, the ITS hardware
  implementation uses 16Bytes for Interrupt Translation Entry (ITE),
  but reports an incorrect value of 8Bytes in GITS_TYPER.ITTE_size.
  
  It might cause kernel memory corruption depending on the number
  of MSI(x) that are configured and the amount of memory that has
  been allocated for ITEs in its_create_device().
  
  This patch fixes the potential memory corruption by setting the
  correct ITE size to 16Bytes.

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

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

[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3

[Cosmin Mutu]

@Robert ... sure, let me clarify the events.

1. I had Ubuntu 16.04 LTS for some time already running on my system.
2. I bought AMD Ryzen 1800 + Gigabyte AB350 Gaming 3 and I took the SSD from 
the old system and pushed it into the new one
3. Everything worked fine, except I had to install NVIDIA drivers (I also 
bought a better video card)
4. I noticed I couldn`t get CPU temperature, so I tried my luck by upgrading to 
16.10 (BAD DECISION)
> during OS boot the IRQ VECTOR 07 error is repeated over and over
5. I then downloaded the 17.04 on a disk, and tried to install it 
> ended up with IRQ VECTOR 07 error during install (so, no go)
6. I tried the Ubuntu 16.04 LTS from a disk (which was the origin of the OS at 
step 1 ...) --> worked fine
7. I installed Ubuntu 16.04 LTS and here I am .. back at step 3 :)

I`ve never installed STUDIO, only DESKTOP as in this :
http://releases.ubuntu.com/16.04.2/ubuntu-16.04.2-desktop-
amd64.iso?_ga=1.156896511.598999195.1489430754

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

Title:
  System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 
motherboard,
  and it has a load of problems, starting with not being able to boot normally.

  During normal boot, on 16.10 as well as 17.04 beta:
  system doesn't boot normally, hangs with a lot of "unexpected irq trap at 
vector 07"
  messages displayed.

  
  Following advice from various places, I've tried:disable cpu freq governor 
and cpu handling in acpi settings

  1. add "acpi=off" to boot params

  That helps, allowing me to boot into recovery mode, though it leaves
  me with system seeing only one core, is really slow and still only
  boots in recovery mode.

  2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor
  and cpu handling in acpi settings. Boot with "quiet loglevel=3"
  option.

  That gets me even further - system sees all cores now. Still only recovery 
mode though,
  but its enough to get info for this bug report.

  Some observed problems:

  1. dmesg reports *a lot* of messages like this all the time:

  [  163.362068] ->handle_irq():  87a7e090, 
  [  163.362081] bad_chained_irq+0x0/0x40
  [  163.362089] ->handle_irq():  87a7e090, 
  [  163.362090] amd_gpio_irq_handler+0x0/0x200
  [  163.362090] ->irq_data.chip(): 88587e20, 
  [  163.362090] ioapic_ir_chip+0x0/0x120
  [  163.362090] ->action(): 884601c0
  [  163.362091]IRQ_NOPROBE set
  [  163.362099] ->handle_irq():  87a7e090, 
  [  163.362099] amd_gpio_irq_handler+0x0/0x200
  [  163.362100] ->irq_data.chip(): 88587e20, 
  [  163.362100] ioapic_ir_chip+0x0/0x120
  [  163.362101] ->action(): 884601c0

  I've tried to redirect dmesg to a file, stopped after a short while,
  it generated 400M of those.

  2. Systemd cannot start journald. Perhaps because it cannot cope with
  amount of kernel logs?

  3. Looking at pci, I've noticed something called AMDI0040
  (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010,
  AMDI0020, AMDI0030. Those however are mentioned in kernel source,
  kernel and google are completely silent about AMDI0040.

  
  Phoronix tested ryzen using different motherboard, and it worked better 
(though not well),
  so I suspect it is an issue with motherboard.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2015-08-06 (581 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-rc1-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3

[Cosmin Mutu]

@Maciej : I think you missunderstood ... both Gigabyte (mine) and Asus
boards (Huang`s) work fine with 16.04 LTS ... what you need to do .. is
ask Huang to try his luck with 16.10 :) or 17.04

So, Huang, can you make 2 DVD`s .. one with 16.10 and another with 17.04
(or 2 bootable flashes) and just "TRY" both of them, without installing
... I wonder if that works for you.

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

Title:
  System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 
motherboard,
  and it has a load of problems, starting with not being able to boot normally.

  During normal boot, on 16.10 as well as 17.04 beta:
  system doesn't boot normally, hangs with a lot of "unexpected irq trap at 
vector 07"
  messages displayed.

  
  Following advice from various places, I've tried:disable cpu freq governor 
and cpu handling in acpi settings

  1. add "acpi=off" to boot params

  That helps, allowing me to boot into recovery mode, though it leaves
  me with system seeing only one core, is really slow and still only
  boots in recovery mode.

  2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor
  and cpu handling in acpi settings. Boot with "quiet loglevel=3"
  option.

  That gets me even further - system sees all cores now. Still only recovery 
mode though,
  but its enough to get info for this bug report.

  Some observed problems:

  1. dmesg reports *a lot* of messages like this all the time:

  [  163.362068] ->handle_irq():  87a7e090, 
  [  163.362081] bad_chained_irq+0x0/0x40
  [  163.362089] ->handle_irq():  87a7e090, 
  [  163.362090] amd_gpio_irq_handler+0x0/0x200
  [  163.362090] ->irq_data.chip(): 88587e20, 
  [  163.362090] ioapic_ir_chip+0x0/0x120
  [  163.362090] ->action(): 884601c0
  [  163.362091]IRQ_NOPROBE set
  [  163.362099] ->handle_irq():  87a7e090, 
  [  163.362099] amd_gpio_irq_handler+0x0/0x200
  [  163.362100] ->irq_data.chip(): 88587e20, 
  [  163.362100] ioapic_ir_chip+0x0/0x120
  [  163.362101] ->action(): 884601c0

  I've tried to redirect dmesg to a file, stopped after a short while,
  it generated 400M of those.

  2. Systemd cannot start journald. Perhaps because it cannot cope with
  amount of kernel logs?

  3. Looking at pci, I've noticed something called AMDI0040
  (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010,
  AMDI0020, AMDI0030. Those however are mentioned in kernel source,
  kernel and google are completely silent about AMDI0040.

  
  Phoronix tested ryzen using different motherboard, and it worked better 
(though not well),
  so I suspect it is an issue with motherboard.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2015-08-06 (581 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-rc1-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1672224] Re: Upgrade to kernel version 4.4.0-66 of Ubuntu 16.04 LTS caused major chaos/failures

[Joseph Salisbury]

Does the bug go away if you boot back into the prior kernel version?

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

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

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

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => 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/1672224

Title:
  Upgrade to kernel version 4.4.0-66 of Ubuntu 16.04 LTS caused major
  chaos/failures

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

Bug description:
  The most obvious issue upon logging in was that there were no network 
interfaces save the loopback.
  A review of the logs suggested there were many major problems with the 
upgrade.

  Interestingly, the system suggested that I delete all other versions
  of the kernel immediately after this failed upgrade.  This would have
  rendered the system nearly unusable.

  This is not the user experience I was thinking of when I chose an LTS
  version.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-66-generic 4.4.0-66.87
  ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
  Uname: Linux 4.4.0-63-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doug   2348 F pulseaudio
   /dev/snd/controlC2:  doug   2348 F pulseaudio
   /dev/snd/controlC0:  doug   2348 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar 12 15:23:41 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=caabec9a-7ba2-451a-91a5-af1bef3bfc38
  InstallationDate: Installed on 2017-01-20 (51 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.

   enp6s0no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-63-generic 
root=UUID=ecd4d068-85e7-40c9-8483-d2dbfaadc20b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-63-generic N/A
   linux-backports-modules-4.4.0-63-generic  N/A
   linux-firmware1.157.8
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/10/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0908
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V LE PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0908:bd12/10/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLEPLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1672502] [NEW] arm64 MSI/PCIe passthrough patches break build of certain configs

[dann frazier]

Public bug reported:

The zesty kernel has a backport of the MSI/PCIe passthrough changes for
arm64. This changeset introduced a bug that can cause a build failure
with certain configurations. Though it doesn't impact the Ubuntu config,
it could creep up again if we change our config. I reproduced it on
Ubuntu source b building the s390x image with CONFIG_PCI=n and
CONFIG_IRQ_DOMAIN=n.

** Affects: linux (Ubuntu)
 Importance: Low
 Assignee: dann frazier (dannf)
 Status: In Progress

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

Title:
  arm64 MSI/PCIe passthrough patches break build of certain configs

Status in linux package in Ubuntu:
  In Progress

Bug description:
  The zesty kernel has a backport of the MSI/PCIe passthrough changes
  for arm64. This changeset introduced a bug that can cause a build
  failure with certain configurations. Though it doesn't impact the
  Ubuntu config, it could creep up again if we change our config. I
  reproduced it on Ubuntu source b building the s390x image with
  CONFIG_PCI=n and CONFIG_IRQ_DOMAIN=n.

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

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

[Kernel-packages] [Bug 1671917] Re: perf probes on arm64 don't work with 4.10 kernel b/c of register name issue

[Seth Forshee]

This is a simple patch for perf and a clean cherry pick from upstream.
I'm going ahead and applying it.

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

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

Title:
  perf probes on arm64 don't work with 4.10 kernel b/c of register name
  issue

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

Bug description:
  perf probe doesn't work because the register names in the perf tool
  are incorrect. This was fixed upstream by
  https://patchwork.kernel.org/patch/9534823/.

  perf probe -x /lib/aarch64-linux-gnu/libc.so.6 -a 'malloc bytes'
  Failed to write event: Invalid argument
Error: Failed to add events.

  Rebuilding perf with the above mentioned change results in:
  ubuntu:/usr/src/linux-source-4.10.0/tools/perf# ./perf probe -x 
/lib/aarch64-linux-gnu/libc.so.6 -a 'malloc bytes'
  Added new event:
probe_libc:malloc(on malloc in /lib/aarch64-linux-gnu/libc-2.24.so with 
bytes)

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

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

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

[bugproxy]

--- Comment From thiag...@br.ibm.com 2017-03-13 15:22 EDT---
Small update:

The following commit is not actually necessary. It fixes code which is
not present in v4.4:

e17354961bb5 zram_drv: update for backing dev info changes

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

Title:
  UbuntuKVM guest crashed while running I/O stress test with Ubuntu
  kernel  4.4.0-47-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Attn. Canonical: For your awareness only at this time.

  == Comment: #0 - LEKSHMI C. PILLAI  - 2016-11-22 03:49:38 ==

  Machine INFO

  KVM HOST: luckyv1

  Guest :lucky05

  lucky05 crashed while running the I/O stress test for SAN disks.

  Installed lucky05 and enabled the xmon on that.After that started the
  RAW disk test on around 50 disks.After 6-7 hours after running,Now
  machine dropped into xmon.

  Logs:
  [25023.224182] Unable to handle kernel paging request for data at address 
0x
  [25023.224257] Faulting instruction address: 0xc0324c60
  cpu 0x3: Vector: 300 (Data Access) at [c000fffc3620]
  pc: c0324c60: locked_inode_to_wb_and_lock_list+0x50/0x290
  lr: c032831c: writeback_sb_inodes+0x30c/0x590
  sp: c000fffc38a0
 msr: 80019033
 dar: 0
   dsisr: 4000
current = 0xc000ff99e470
paca= 0xcfb41c80   softe: 0irq_happened: 0x01
  pid   = 14736, comm = kworker/u16:8
  enter ? for help
  [c000fffc3900] c032831c writeback_sb_inodes+0x30c/0x590
  [c000fffc3a10] c0328684 __writeback_inodes_wb+0xe4/0x150
  [c000fffc3a70] c0328aec wb_writeback+0x30c/0x450
  [c000fffc3b40] c03296b4 wb_workfn+0x264/0x570
  [c000fffc3c50] c00dd930 process_one_work+0x1e0/0x5a0
  [c000fffc3ce0] c00dde84 worker_thread+0x194/0x680
  [c000fffc3d80] c00e6980 kthread+0x110/0x130
  [c000fffc3e30] c0009538 ret_from_kernel_thread+0x5c/0xa4
  3:mon> f
  3:mon> th
  [c000fffc3900] c032831c writeback_sb_inodes+0x30c/0x590
  [c000fffc3a10] c0328684 __writeback_inodes_wb+0xe4/0x150
  [c000fffc3a70] c0328aec wb_writeback+0x30c/0x450
  [c000fffc3b40] c03296b4 wb_workfn+0x264/0x570
  [c000fffc3c50] c00dd930 process_one_work+0x1e0/0x5a0
  [c000fffc3ce0] c00dde84 worker_thread+0x194/0x680
  [c000fffc3d80] c00e6980 kthread+0x110/0x130
  [c000fffc3e30] c0009538 ret_from_kernel_thread+0x5c/0xa4 
  3:mon> sh
  [27384.651055] INFO: rcu_sched detected stalls on CPUs/tasks:
  [27384.651220]  (detected by 4, t=40598 jiffies, g=2849830, c=2849829, q=992)
  [27384.651286] All QSes seen, last rcu_sched kthread activity 40596 
(4301188714-4301148118), jiffies_till_next_fqs=1, root ->qsmask 0x0
  [27384.651501] rcu_sched kthread starved for 40596 jiffies! g2849830 c2849829 
f0x2 s3 ->state=0x0
  [27384.651747] INFO: rcu_sched detected stalls on CPUs/tasks:
  [27384.651905]  (detected by 4, t=590354 jiffies, g=2849830, c=2849829, 
q=1285)
  [27384.652012] All QSes seen, last rcu_sched kthread activity 590352 
(4301738470-4301148118), jiffies_till_next_fqs=1, root ->qsmask 0x0
  [27384.652191] rcu_sched kthread starved for 590352 jiffies! g2849830 
c2849829 f0x2 s3 ->state=0x0
  [27384.730645] Unable to handle kernel paging request for data at address 
0xffd8
  [27384.730781] Faulting instruction address: 0xc00e7258
  cpu 0x3: Vector: 300 (Data Access) at [c000fffc3000]
  pc: c00e7258: kthread_data+0x28/0x40
  lr: c00de940: wq_worker_sleeping+0x30/0x110
  sp: c000fffc3280
 msr: 80019033
 dar: ffd8
   dsisr: 4000
current = 0xc000ff99e470
paca= 0xcfb41c80   softe: 0irq_happened: 0x01
  pid   = 14736, comm = kworker/u16:8
  enter ? for help

  == Comment: #1 - LEKSHMI C. PILLAI - 2016-11-22 04:05:41 ==
  3:mon> th
  [c000fffc32b0] c00de940 wq_worker_sleeping+0x30/0x110
  [c000fffc32f0] c0af31bc __schedule+0x6ec/0x990
  [c000fffc33c0] c0af34a8 schedule+0x48/0xc0
  [c000fffc33f0] c00bd3d0 do_exit+0x760/0xc30
  [c000fffc34b0] c0020bf4 die+0x314/0x470
  [c000fffc3540] c0050d98 bad_page_fault+0xd8/0x150
  [c000fffc35b0] c0008680 handle_page_fault+0x2c/0x30
  --- Exception: 300 (Data Access) at c0324c60 
locked_inode_to_wb_and_lock_list+0x50/0x290
  [c000fffc3900] c032831c writeback_sb_inodes+0x30c/0x590
  [c000fffc3a10] c0328684 __writeback_inodes_wb+0xe4/0x150
  [c000fffc3a70] c0328aec wb_writeback+0x30c/0x450
  [c000fffc3b40] c03296b4 wb_workfn+0x264/0x570
  [c000fffc3c50] c00dd930 process_one_work+0x1e0/0x5a0