[Kernel-packages] [Bug 1730829] Re: [Feature]Crystal Ridge:add support for the platform capabilities NFIT sub-table in ACPI 6.2A

2018-03-27 Thread quanxian
one more commit fe9a552e715 from upstream

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

Title:
  [Feature]Crystal Ridge:add support for the platform capabilities NFIT
  sub-table in ACPI 6.2A

Status in intel:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Description:

  Enable support for: "5.2.25.9 Platform Capabilities Structure" in ACPI 6.2A.
  This involves NFIT driver changes for the new table, and then detecting if 
the platform has cache flush on fail support. If it does, plumb that through as 
a region property so that we can pick the proper default to pass to the 
dax_write_cache() call in pmem_attach_disk().

  Target Kernel: 4.15
  Target Release: 18.04

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

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


[Kernel-packages] [Bug 1550779] Re: [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches

2018-03-27 Thread Will Foster
This still occurs for me on kernel 4.15.12.

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

Title:
  [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches,
  looks like the graphic buffer gets screwed up

  - funny repetition's patterns  (back in time glitches)
  - black screen (<1sec)
  - graphic errors  

  I can influence the severity of the issue with switching windows and
  using certain programs, e.g. Google Maps in chrome causes this issue
  reproducibly

  dmesg  | grep i915
  [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on 
minor 0
  [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit 
banging on pin 5
  [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device
  [3.471093] i915 :00:02.0: registered panic notifier
  [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe A FIFO underrun
  [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun

  linux-image-extra-4.2.0-27-generic works find

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Feb 27 20:26:07 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed
   virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21da]
  InstallationDate: Installed on 2016-02-11 (15 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 42912XG
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic 
root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt 
quiet
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET69WW (1.39 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42912XG
  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:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42912XG
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Sat Feb 27 20:25:23 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12359 
   vendor SEC
  xserver.version: 2:1.17.2-1ubuntu9.1

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

-- 
Mailing list: https://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 1758796] Re: Kernel Crash

2018-03-27 Thread Johnny Wunder
Thanks for getting back to me.

I've been running the system as a web server for 8 years round the clock
and this is the first and only time I had an unexplained kernel crash.
I sent the bug in because I was unable to interpret the dump and I was
actually worried someone had hacked my system causing the failure.

I'm willing to check the upstream kernel but I've been running on the
rebooted system since and have not seen the problem again so I'm not
sure how long I'd have to run to verify the new kernel made any
difference.

If you can tell me either that this was a straight failure and not a
hack or tell me how I could break down the dump and understand where and
how it failed I'd be ok with closing this out.  I just wanted to be sure
it wasn't caused by malicious outside activity.

The only thing different I noticed from my last automatic server upgrade
is that I'm getting periodic java exceptions seemingly trace to gnome
when I'm on the system.

Which way should I go?

Thanks again for getting back to me,
John

> On Mar 27, 2018, at 5:54 PM, Joseph Salisbury 
>  wrote:
> 
> 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.16 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.16-rc7
> 
> ** Changed in: linux (Ubuntu)
>   Importance: Undecided => High
> 
> ** Changed in: linux (Ubuntu)
>   Status: Confirmed => Incomplete
> 
> ** Tags added: kernel-da-key
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1758796
> 
> Title:
>  Kernel Crash
> 
> Status in linux package in Ubuntu:
>  Incomplete
> 
> Bug description:
>  Have the logs around this.  Failed while running unattended.
> 
>  ProblemType: KernelCrash
>  DistroRelease: Ubuntu 16.04
>  Package: linux-image-4.4.0-117-generic 4.4.0-117.141
>  ProcVersionSignature: Ubuntu 4.4.0-117.141-generic 4.4.114
>  Uname: Linux 4.4.0-117-generic x86_64
>  ApportVersion: 2.20.1-0ubuntu2.15
>  Architecture: amd64
>  AudioDevicesInUse:
>   USERPID ACCESS COMMAND
>   /dev/snd/controlC0:  johnny 8301 F pulseaudio
>  Date: Sun Mar 25 06:09:20 2018
>  HibernationDevice: RESUME=UUID=5ed7ec2d-76de-4b8d-b427-f94d429221a5
>  InstallationDate: Installed on 2011-12-21 (2285 days ago)
>  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
>  IwConfig:
>   lono wireless extensions.
> 
>   eth0  no wireless extensions.
>  MachineType: MSI MS-7680
>  ProcFB: 0 inteldrmfb
>  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-117-generic 
> root=UUID=430a9050-fa68-406c-812c-8a6384c75d43 ro quiet splash 
> crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
> crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
> crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
> crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
> crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
> crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M 
> crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
> crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
> crashkernel=384M-2G:128M,2G-:256M vt.handoff=7
>  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
> PulseAudio daemon running, or not running as session daemon.
>  RelatedPackageVersions:
>   linux-restricted-modules-4.4.0-117-generic N/A
>   linux-backports-modules-4.4.0-117-generic  N/A
>   linux-firmware 1.157.17
>  RfKill:
> 
>  SourcePackage: linux
>  UpgradeStatus: Upgraded to xenial on 2016-08-18 (583 days ago)
>  dmi.bios.date: 04/11/2011
>  dmi.bios.vendor: American Megatrends Inc.
>  dmi.bios.version: V17.1
>  dmi.board.asset.tag: To be filled by O.E.M.
>  dmi.board.name: H61M-P21 (MS-7680)
>  dmi.board.vendor: MSI
>  dmi.board.version: 3.0
>  dmi.chassis.asset.tag: To Be Filled By O.E.M.
>  dmi.chassis.type: 3
>  dmi.chassis.vendor: MSI
>  dmi.chassis.version: 3.0
>  dmi.modalias: 
> dmi:bvnAmericanMegatrendsInc.:bvrV17.1:bd04/11/2011:svnMSI:pnMS-7680:pvr3.0:rvnMSI:rnH61M-P21(MS-7680):rvr3.0:cvnMSI:ct3:cvr3.0:
>  dmi.product.name: MS-7680
>  dmi.product.version: 3.0
>  dmi.sys.vendor: MSI
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758796/+subscriptions

-- 

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

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

apport-collect 1759445

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

** Tags added: bionic

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

Title:
  Bionic due to kernel panic

Status in MAAS:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  cpe_foundation test deployment of Bionic failed.
  After some investigation, it looks like the nodes deployed and installed 
bionic, but never came back from a reboot.

  Accessing the ILO console of a node in question (all nodes failed), it
  revealed a kernel panic (attached)

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

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


[Kernel-packages] [Bug 1759445] Re: MAAS 2.3.1 fails to deploy Bionic due to kernel panic

2018-03-27 Thread Andres Rodriguez
Hi Eric,

I experience the same issue in non-MAAS deployed machines after
upgrading to the latest kernel. AS such, I'm marking this as invalid for
MAAS and opening a task for the kernel.

** Changed in: maas
   Status: New => Invalid

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

** Summary changed:

- MAAS 2.3.1 fails to deploy Bionic due to kernel panic
+ Bionic due to kernel panic

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

Title:
  Bionic due to kernel panic

Status in MAAS:
  Invalid
Status in linux package in Ubuntu:
  New

Bug description:
  cpe_foundation test deployment of Bionic failed.
  After some investigation, it looks like the nodes deployed and installed 
bionic, but never came back from a reboot.

  Accessing the ILO console of a node in question (all nodes failed), it
  revealed a kernel panic (attached)

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

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


[Kernel-packages] [Bug 1730775] Re: [Feature][CFL][ICL] [CNL]Thunderbolt support (Titan Ridge)

2018-03-27 Thread Anthony Wong
The main patchset "thunderbolt: Add support for Intel Titan Ridge" has been 
merged upstream:
- https://lkml.org/lkml/2018/3/2/570
- already merged into 
https://git.kernel.org/pub/scm/linux/kernel/git/westeri/thunderbolt.git/log/?h=next

There are two other related patchsets for thunderbolt native mode, one of which 
is still under review:
1. PCI: Fixes for native PCIe and ACPI hotplug
- https://patchwork.ozlabs.org/cover/877884/
- still pending on maintainer review

2. [PATCH] ACPICA: Recognize the Windows 10 RS3 OSI string
- https://marc.info/?l=linux-acpi=151854485331385=2
- this one has a dependency on the previous one.

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

Title:
  [Feature][CFL][ICL] [CNL]Thunderbolt support (Titan Ridge)

Status in intel:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:
  This is platform independent and can be verified on any of the three 
platforms mentioned here.
  ICL TBT support requires native mode.

  Target Kernel: 4.17
  Target Release: 18.04

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

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


[Kernel-packages] [Bug 1730775] Re: [Feature][CFL][ICL] [CNL]Thunderbolt support (Titan Ridge)

2018-03-27 Thread Anthony Wong
** Changed in: intel
   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/1730775

Title:
  [Feature][CFL][ICL] [CNL]Thunderbolt support (Titan Ridge)

Status in intel:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:
  This is platform independent and can be verified on any of the three 
platforms mentioned here.
  ICL TBT support requires native mode.

  Target Kernel: 4.17
  Target Release: 18.04

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

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


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

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

apport-collect 1730775

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

** Tags added: bionic

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

Title:
  [Feature][CFL][ICL] [CNL]Thunderbolt support (Titan Ridge)

Status in intel:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:
  This is platform independent and can be verified on any of the three 
platforms mentioned here.
  ICL TBT support requires native mode.

  Target Kernel: 4.17
  Target Release: 18.04

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

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


[Kernel-packages] [Bug 1730775] Re: [Feature][CFL][ICL] [CNL]Thunderbolt support (Titan Ridge)

2018-03-27 Thread Anthony Wong
** Information type changed from Proprietary to Public

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

Title:
  [Feature][CFL][ICL] [CNL]Thunderbolt support (Titan Ridge)

Status in intel:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:
  This is platform independent and can be verified on any of the three 
platforms mentioned here.
  ICL TBT support requires native mode.

  Target Kernel: 4.17
  Target Release: 18.04

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

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


[Kernel-packages] [Bug 1746740] Re: XPS13 L322X Bionic (daily dev) touchpad laggy

2018-03-27 Thread Daniel van Vugt
Sorry, maybe try:

  ubuntu-bug libinput10

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

Title:
  XPS13 L322X Bionic (daily dev) touchpad laggy

Status in libinput:
  Incomplete
Status in libinput package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Also, all function keys work as expected, even F6 (keyboard 3-states
  backlight), but OSD picture for this last feature randomly auto-
  triggers.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1876 F pulseaudio
  CasperVersion: 1.388
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  1 14:05:22 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- debian-installer/language=fr 
keyboard-configuration/layoutcode?=fr keyboard-configuration/variantcode?=oss
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1759429] [NEW] /usr/sbin/kerneloops:free(): invalid next size (normal)

2018-03-27 Thread errors.ubuntu.com bug bridge
Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
kerneloops.  This problem was most recently seen with package version 
0.12+git20140509-6ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/c61a76ca3c55eca400466128f5854ce8f8974b73 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: bionic

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

Title:
  /usr/sbin/kerneloops:free(): invalid next size (normal)

Status in kerneloops package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
kerneloops.  This problem was most recently seen with package version 
0.12+git20140509-6ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/c61a76ca3c55eca400466128f5854ce8f8974b73 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

-- 
Mailing list: https://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 1759342] Re: BUG: Bad rss-counter state mm:000000003cebd506 idx:0 val:75

2018-03-27 Thread BertN45
I update the system each day, so I assume it has been introduced this
week.


On 27-03-18 17:39, Joseph Salisbury wrote:
> 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.16 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.16-rc7
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> ** 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/1759342

Title:
  BUG: Bad rss-counter state mm:3cebd506 idx:0 val:75

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Crash happened after booting the system

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bertadmin   1745 F pulseaudio
  Date: Sat Mar 24 11:42:05 2018
  Failure: oops
  InstallationDate: Installed on 2018-03-11 (16 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=22835ac6-a7b5-4601-bd4b-a6c98e4df3fb ro quiet splash zwap.enabled=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: BUG: Bad rss-counter state mm:3cebd506 idx:0 val:75
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

-- 
Mailing list: https://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 1758546] Re: BUG: Bad rss-counter state mm:000000003cebd506 idx:0 val:75

2018-03-27 Thread BertN45
Yes, I update the system each day, so it has been introduced this week.


On 27-03-18 17:16, Joseph Salisbury wrote:
> 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.16 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.16-rc7
>
> ** 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/1758546

Title:
  BUG: Bad rss-counter state mm:3cebd506 idx:0 val:75

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Crash occured after reboot of the Saturday update.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bertadmin   1390 F pulseaudio
  Date: Sat Mar 24 11:41:02 2018
  Failure: oops
  InstallationDate: Installed on 2018-03-11 (13 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=22835ac6-a7b5-4601-bd4b-a6c98e4df3fb ro quiet splash zwap.enabled=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: BUG: Bad rss-counter state mm:3cebd506 idx:0 val:75
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


[Kernel-packages] [Bug 1758869] Re: Kernel panic with AWS 4.4.0-1053 / 4.4.0-1015 (Trusty)

2018-03-27 Thread Kamal Mostafa
Issue and patches described here:

https://lkml.org/lkml/2018/2/6/320

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

Title:
  Kernel panic with AWS 4.4.0-1053 / 4.4.0-1015 (Trusty)

Status in linux package in Ubuntu:
  In Progress

Bug description:
  This is a POTENTIAL REGRESSION.

  This issue only occurs on one of the AWS testing instance "c3.large"

  Reproduce rate: 100% (All jenkins deployment job failed with this
  instance)

  Steps:
    1. Deploy this instance with AWS kernel (4.4.0-1052)
    2. Enable -proposed, upgrade it and reboot.

  Result:
    * System can boot with 4.4.0-1052, but it won't be accessible after 
rebooting for 4.4.0-1053, from "aws ec2 get-console-output" command indicates 
it hang with kernel panic issue on boot. It looks like the intel-microcode is 
causing this issue.

  Output from the command: https://pastebin.ubuntu.com/p/3JvWNk5CTs/
  (it's a bit difficult to get full output, the instance will keep
  rebooting itself)

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

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


[Kernel-packages] [Bug 1758869] Re: Kernel panic with AWS 4.4.0-1053 / 4.4.0-1015 (Trusty)

2018-03-27 Thread Kamal Mostafa
This is caused by this commit from mainline:

linux-aws: 9f182bd x86/microcode/intel: Extend BDW late-loading further with 
LLC size check
mainline:  7e702d1 x86/microcode/intel: Extend BDW late-loading further with 
LLC size check

which adds a check which involves this computation:
+   do_div(llc_size, c->x86_max_cores);

But dmesg on a c3.large instance yields this interesting line:
[0.156084] smpboot: x86_max_cores == zero !?!?


** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

Title:
  Kernel panic with AWS 4.4.0-1053 / 4.4.0-1015 (Trusty)

Status in linux package in Ubuntu:
  In Progress

Bug description:
  This is a POTENTIAL REGRESSION.

  This issue only occurs on one of the AWS testing instance "c3.large"

  Reproduce rate: 100% (All jenkins deployment job failed with this
  instance)

  Steps:
    1. Deploy this instance with AWS kernel (4.4.0-1052)
    2. Enable -proposed, upgrade it and reboot.

  Result:
    * System can boot with 4.4.0-1052, but it won't be accessible after 
rebooting for 4.4.0-1053, from "aws ec2 get-console-output" command indicates 
it hang with kernel panic issue on boot. It looks like the intel-microcode is 
causing this issue.

  Output from the command: https://pastebin.ubuntu.com/p/3JvWNk5CTs/
  (it's a bit difficult to get full output, the instance will keep
  rebooting itself)

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

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


[Kernel-packages] [Bug 1752828] Re: nfp: fix disabling on hw-tc-offload in flower

2018-03-27 Thread Kamal Mostafa
** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Changed in: linux (Ubuntu Bionic)
   Status: Triaged => 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/1752828

Title:
  nfp: fix disabling on hw-tc-offload in flower

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

Bug description:
  This is a backport request from Netronome for Ubuntu 18.04 LTS

  This patchset corrects the following behaviour:
  1. Add TC filter to hardware while hw-tc-offload is on
  2. Switch hw-tc-offload to off using ethtool
  3. Filters added to hardware in step 1 are still active but can no longer be 
removed. 

  The upstream solution to this problem is to prohibit switching hw-tc-
  offload to off when filters are present in hardware.

  The upstream commits, accepted for v4.16, are:
  d692403e5cf8 (“nfp: forbid disabling hw-tc-offload on representors while 
offload active”)
  0b9de4ca853b (“nfp: don't advertise hw-tc-offload on non-port netdevs”)
  e3ac6c0737e2 (“nfp: bpf: require ETH table”)

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

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


[Kernel-packages] [Bug 1758662] Re: [Bionic] mlx4 ETH - mlnx_qos failed when set some TC to vendor

2018-03-27 Thread Joseph Salisbury
I built a test kernel with commit a42b63c1ac1986f17f71bc91a6b0aaa14d4dae71.  
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1758662

Can you test this kernel and see if it resolves this bug?

Note, to test this kernel, you need to install both the linux-image and
linux-image-extra .deb packages.

Thanks in advance!

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

Title:
  [Bionic] mlx4 ETH - mlnx_qos failed when set some TC to vendor

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

Bug description:
  reproduce:
  [root@reg-l-vrt-41018-010 ~]# /usr/bin/mlnx_qos -i ens8 -s 
vendor,ets,vendor,ets,ets,strict,ets,vendor -t 0,36,0,55,4,0,5,0
  Netlink error: Bad value. see dmesg.

  [root@reg-l-vrt-41018-010 ~]# dmesg
  [69718.992299] mlx4_en: ens8: TC[0]: Not supported TSA: 255

  
  There is a upstream commit that fix the issue, please add it to bionic 

  commit a42b63c1ac1986f17f71bc91a6b0aaa14d4dae71  
  Author: Moni Shoua   
  Date:   Thu Dec 28 16:26:11 2017 +0200   

  net/mlx4_en: Change default QoS settings
  
  Change the default mapping between TC and TCG as follows:
   
  Prio | TC/TCG
   |  from to  
   |(set by FW)  (set by SW)   
  -+---
  0|  0/0  0/7 
  1|  1/0  0/6 
  2|  2/0  0/5 
  3|  3/0  0/4 
  4|  4/0  0/3 
  5|  5/0  0/2 
  6|  6/0  0/1 
  7|  7/0  0/0 
   
  These new settings cause that a pause frame for any prio stops
  traffic for all prios.

  Fixes: 564c274c3df0 ("net/mlx4_en: DCB QoS support")  
  Signed-off-by: Moni Shoua 
  Signed-off-by: Maor Gottlieb  
  Signed-off-by: Tariq Toukan  
  Signed-off-by: David S. Miller   

  diff --git a/drivers/net/ethernet/mellanox/mlx4/en_dcb_nl.c 
b/drivers/net/ethernet/mellanox/mlx4/en_dcb_nl.c
  index 5f41dc9..1a0c3bf8 100644
  
  --- a/drivers/net/ethernet/mellanox/mlx4/en_dcb_nl.c  
  
  +++ b/drivers/net/ethernet/mellanox/mlx4/en_dcb_nl.c
  @@ -310,6 +310,7 @@ static int mlx4_en_ets_validate(struct mlx4_en_priv 
*priv, struct ieee_ets *ets)
  }

  switch (ets->tc_tsa[i]) {
  + case IEEE_8021QAZ_TSA_VENDOR:
  case IEEE_8021QAZ_TSA_STRICT:
  break;
  case IEEE_8021QAZ_TSA_ETS:
  @@ -347,6 +348,10 @@ static int mlx4_en_config_port_scheduler(struct 
mlx4_en_priv *priv,
  /* higher TC means higher priority => lower pg */
  for (i = IEEE_8021QAZ_MAX_TCS - 1; i >= 0; i--) {
  switch (ets->tc_tsa[i]) {
  + case IEEE_8021QAZ_TSA_VENDOR:
  + pg[i] = MLX4_EN_TC_VENDOR;
  + tc_tx_bw[i] = MLX4_EN_BW_MAX;
  + break;
  case IEEE_8021QAZ_TSA_STRICT:
  pg[i] = num_strict++;
  tc_tx_bw[i] = MLX4_EN_BW_MAX;
  diff --git a/drivers/net/ethernet/mellanox/mlx4/en_netdev.c 
b/drivers/net/ethernet/mellanox/mlx4/en_netdev.c
  index 99051a2..21bc17f 100644
  --- a/drivers/net/ethernet/mellanox/mlx4/en_netdev.c
  +++ b/drivers/net/ethernet/mellanox/mlx4/en_netdev.c
  @@ -3336,6 +3336,13 @@ int mlx4_en_init_netdev(struct mlx4_en_dev *mdev, int 
port,
  priv->msg_enable = MLX4_EN_MSG_LEVEL;
   #ifdef CONFIG_MLX4_EN_DCB
  if (!mlx4_is_slave(priv->mdev->dev)) {
  + u8 prio;
  +
  + for (prio = 0; prio < IEEE_8021QAZ_MAX_TCS; ++prio) {
  + priv->ets.prio_tc[prio] = prio;
  + priv->ets.tc_tsa[prio]  = IEEE_8021QAZ_TSA_VENDOR;
  + }
  +
  priv->dcbx_cap = DCB_CAP_DCBX_VER_CEE | DCB_CAP_DCBX_HOST |
  DCB_CAP_DCBX_VER_IEEE;
  priv->flags |= 

[Kernel-packages] [Bug 1746740] Re: XPS13 L322X Bionic (daily dev) touchpad laggy

2018-03-27 Thread Silvio Bierman
Well. I had reverted to Artful so that was easier said than done. I
upgraded to Bionic once more. That brought back the problem but "ubuntu-
bug libinput" then complained that I did not have that package
installed. I did not know what libinputxxx package to use and I got
tired of soft-stroking my touchpad and reinstalled Artful once more. I
may have more time to spend on this the coming weeks and then I will try
again.

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

Title:
  XPS13 L322X Bionic (daily dev) touchpad laggy

Status in libinput:
  Incomplete
Status in libinput package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Also, all function keys work as expected, even F6 (keyboard 3-states
  backlight), but OSD picture for this last feature randomly auto-
  triggers.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1876 F pulseaudio
  CasperVersion: 1.388
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  1 14:05:22 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- debian-installer/language=fr 
keyboard-configuration/layoutcode?=fr keyboard-configuration/variantcode?=oss
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1759421] [NEW] linux-kvm VFIO support for Kata containers

2018-03-27 Thread Julio Montes
Public bug reported:

Next configs are needed to support VFIO
* CONFIG_DMAR_TABLE
* CONFIG_HAVE_INTEL_TXT
* CONFIG_INTEL_IOMMU
* CONFIG_INTEL_IOMMU_DEFAULT_ON
* CONFIG_INTEL_IOMMU_FLOPPY_WA
* CONFIG_INTEL_IOMMU_SVM
* CONFIG_IOMMU_API
* CONFIG_IOMMU_IOVA
* CONFIG_IOMMU_SUPPORT
* CONFIG_IRQ_REMAP
* CONFIG_PCI_ATS
* CONFIG_PCI_PASID
* CONFIG_VFIO
* CONFIG_VFIO_IOMMU_TYPE1
* CONFIG_VFIO_PCI
* CONFIG_VFIO_PCI_INTX
* CONFIG_VFIO_PCI_MMAP
* CONFIG_VFIO_VIRQFD

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

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

Title:
   linux-kvm VFIO support for Kata containers

Status in linux-kvm package in Ubuntu:
  New

Bug description:
  Next configs are needed to support VFIO
  * CONFIG_DMAR_TABLE
  * CONFIG_HAVE_INTEL_TXT
  * CONFIG_INTEL_IOMMU
  * CONFIG_INTEL_IOMMU_DEFAULT_ON
  * CONFIG_INTEL_IOMMU_FLOPPY_WA
  * CONFIG_INTEL_IOMMU_SVM
  * CONFIG_IOMMU_API
  * CONFIG_IOMMU_IOVA
  * CONFIG_IOMMU_SUPPORT
  * CONFIG_IRQ_REMAP
  * CONFIG_PCI_ATS
  * CONFIG_PCI_PASID
  * CONFIG_VFIO
  * CONFIG_VFIO_IOMMU_TYPE1
  * CONFIG_VFIO_PCI
  * CONFIG_VFIO_PCI_INTX
  * CONFIG_VFIO_PCI_MMAP
  * CONFIG_VFIO_VIRQFD

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

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


[Kernel-packages] [Bug 1758662] Re: [Bionic] mlx4 ETH - mlnx_qos failed when set some TC to vendor

2018-03-27 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Also affects: linux (Ubuntu Bionic)
   Importance: Medium
   Status: Incomplete

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

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

Title:
  [Bionic] mlx4 ETH - mlnx_qos failed when set some TC to vendor

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

Bug description:
  reproduce:
  [root@reg-l-vrt-41018-010 ~]# /usr/bin/mlnx_qos -i ens8 -s 
vendor,ets,vendor,ets,ets,strict,ets,vendor -t 0,36,0,55,4,0,5,0
  Netlink error: Bad value. see dmesg.

  [root@reg-l-vrt-41018-010 ~]# dmesg
  [69718.992299] mlx4_en: ens8: TC[0]: Not supported TSA: 255

  
  There is a upstream commit that fix the issue, please add it to bionic 

  commit a42b63c1ac1986f17f71bc91a6b0aaa14d4dae71  
  Author: Moni Shoua   
  Date:   Thu Dec 28 16:26:11 2017 +0200   

  net/mlx4_en: Change default QoS settings
  
  Change the default mapping between TC and TCG as follows:
   
  Prio | TC/TCG
   |  from to  
   |(set by FW)  (set by SW)   
  -+---
  0|  0/0  0/7 
  1|  1/0  0/6 
  2|  2/0  0/5 
  3|  3/0  0/4 
  4|  4/0  0/3 
  5|  5/0  0/2 
  6|  6/0  0/1 
  7|  7/0  0/0 
   
  These new settings cause that a pause frame for any prio stops
  traffic for all prios.

  Fixes: 564c274c3df0 ("net/mlx4_en: DCB QoS support")  
  Signed-off-by: Moni Shoua 
  Signed-off-by: Maor Gottlieb  
  Signed-off-by: Tariq Toukan  
  Signed-off-by: David S. Miller   

  diff --git a/drivers/net/ethernet/mellanox/mlx4/en_dcb_nl.c 
b/drivers/net/ethernet/mellanox/mlx4/en_dcb_nl.c
  index 5f41dc9..1a0c3bf8 100644
  
  --- a/drivers/net/ethernet/mellanox/mlx4/en_dcb_nl.c  
  
  +++ b/drivers/net/ethernet/mellanox/mlx4/en_dcb_nl.c
  @@ -310,6 +310,7 @@ static int mlx4_en_ets_validate(struct mlx4_en_priv 
*priv, struct ieee_ets *ets)
  }

  switch (ets->tc_tsa[i]) {
  + case IEEE_8021QAZ_TSA_VENDOR:
  case IEEE_8021QAZ_TSA_STRICT:
  break;
  case IEEE_8021QAZ_TSA_ETS:
  @@ -347,6 +348,10 @@ static int mlx4_en_config_port_scheduler(struct 
mlx4_en_priv *priv,
  /* higher TC means higher priority => lower pg */
  for (i = IEEE_8021QAZ_MAX_TCS - 1; i >= 0; i--) {
  switch (ets->tc_tsa[i]) {
  + case IEEE_8021QAZ_TSA_VENDOR:
  + pg[i] = MLX4_EN_TC_VENDOR;
  + tc_tx_bw[i] = MLX4_EN_BW_MAX;
  + break;
  case IEEE_8021QAZ_TSA_STRICT:
  pg[i] = num_strict++;
  tc_tx_bw[i] = MLX4_EN_BW_MAX;
  diff --git a/drivers/net/ethernet/mellanox/mlx4/en_netdev.c 
b/drivers/net/ethernet/mellanox/mlx4/en_netdev.c
  index 99051a2..21bc17f 100644
  --- a/drivers/net/ethernet/mellanox/mlx4/en_netdev.c
  +++ b/drivers/net/ethernet/mellanox/mlx4/en_netdev.c
  @@ -3336,6 +3336,13 @@ int mlx4_en_init_netdev(struct mlx4_en_dev *mdev, int 
port,
  priv->msg_enable = MLX4_EN_MSG_LEVEL;
   #ifdef CONFIG_MLX4_EN_DCB
  if (!mlx4_is_slave(priv->mdev->dev)) {
  + u8 prio;
  +
  + for (prio = 0; prio < IEEE_8021QAZ_MAX_TCS; ++prio) {
  + priv->ets.prio_tc[prio] = prio;
  + priv->ets.tc_tsa[prio]  = IEEE_8021QAZ_TSA_VENDOR;
  + }
  +
  priv->dcbx_cap = DCB_CAP_DCBX_VER_CEE | DCB_CAP_DCBX_HOST |
  DCB_CAP_DCBX_VER_IEEE;
  priv->flags |= MLX4_EN_DCB_ENABLED;
  

[Kernel-packages] [Bug 1758466] Re: bionic: default io_timeout for nvme is 255 on AWS

2018-03-27 Thread Kamal Mostafa
** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

Title:
  bionic: default io_timeout for nvme is 255 on AWS

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

Bug description:
  According to AWS docs, using newer instance types that use NVME drivers 
(c5/m5), the io timeout should be set to maximum (ideally 4294967295).
  https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/nvme-ebs-volumes.html

  It appears this is done for 16.04, but in 18.04 it is the default.

  Test done by spinning up an m5.large instance in ap-southeast-2.

  Ubuntu 16.04 AMI on AWS (latest AMI - 20180126):

  $ cat /sys/module/nvme/parameters/io_timeout
  4294967295

  $ uname -r
  4.4.0-1049-aws

  Ubuntu 18.04 AMI on AWS (latest nightly AMI - 20180323):

  $ cat /sys/module/nvme_core/parameters/io_timeout
  255

  $ uname -r
  4.15.0-1001-aws

  Perhaps as part of the move to nvme_core this got lost.
  --- 
  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': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  DistroRelease: Ubuntu 18.04
  Ec2AMI: ami-5c5d903e
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2b
  Ec2InstanceType: m5.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  JournalErrors:
   -- Logs begin at Sat 2018-03-24 01:00:37 UTC, end at Sat 2018-03-24 01:01:37 
UTC. --
   Mar 24 01:00:56 ip-10-1-2-86 iscsid[849]: iSCSI daemon with pid=850 started!
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Amazon EC2 m5.large
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1001-aws 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 
nvme_core.io_timeout=255
  ProcVersionSignature: Ubuntu 4.15.0-1001.1-aws 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1001-aws N/A
   linux-backports-modules-4.15.0-1001-aws  N/A
   linux-firmware   N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic ec2-images
  Uname: Linux 4.15.0-1001-aws x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: False
  dmi.bios.date: 10/16/2017
  dmi.bios.vendor: Amazon EC2
  dmi.bios.version: 1.0
  dmi.board.asset.tag: i-0d27cecf4877dafa7
  dmi.board.vendor: Amazon EC2
  dmi.chassis.asset.tag: Amazon EC2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Amazon EC2
  dmi.modalias: 
dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.large:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:
  dmi.product.name: m5.large
  dmi.sys.vendor: Amazon EC2

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

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


[Kernel-packages] [Bug 1759312] Re: AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu 17.10

2018-03-27 Thread Joseph Salisbury
I built a test kernel with commit e4b79900222b8cccd4da4a7a89581f from 
linux-next.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1759312

Can you test this kernel and see if it resolves this bug?

Note, to test this kernel, you need to install both the linux-image and
linux-image-extra .deb packages.

Thanks in advance!

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

Title:
  AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu
  17.10

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  ---Problem Description---
  AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu 17.10
   
  ---Additional Hardware Info---
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  176
  On-line CPU(s) list: 0-175
  Thread(s) per core:  4
  Core(s) per socket:  22
  Socket(s):   2
  NUMA node(s):8
  Model:   2.2 (pvr 004e 1202)
  Model name:  POWER9, altivec supported
  CPU max MHz: 2800.
  CPU min MHz: 2300.
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:512K
  L3 cache:10240K
  NUMA node0 CPU(s):   0-87
  NUMA node8 CPU(s):   88-175
  NUMA node250 CPU(s): 
  NUMA node251 CPU(s): 
  NUMA node252 CPU(s): 
  NUMA node253 CPU(s): 
  NUMA node254 CPU(s): 
  NUMA node255 CPU(s): 
   
  Machine Type = P9, DD2.2, Witherspoon, baremetal 
   
  ---Steps to Reproduce---
   AT_BASE_PLATFORM in AIXV is not exported to userspace on P9 baremetal 
machines causing trouble to userspace tools and software that relie on that 
information, notably operf and opreport (from oprofile 1.2.0+) will refuse to 
run without that information show a error message like:

  gromero@ltc-wspoon3:/boot$ operf
  NULL returned for one or both of AT_PLATFORM/AT_BASE_PLATFORM
  AT_PLATFORM: power9;  AT_BASE_PLATFORM: (null)
  Unable to obtain cpu_type
  Verify that a pre-1.0 version of OProfile is not in use.
  If the /dev/oprofile/cpu_type file exists, locate the pre-1.0 OProfile
  installation, and use its 'opcontrol' command, passing the --deinit option.
  Unable to ascertain cpu type.  Exiting.
   
  ---uname output---
  linux-image-4.13.0-36-generic  4.13.0-36.40

  Userspace tool common name: operf, opreport 

  Dear maintainer. please consider applying the following fix that's
  already available upstream:

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=e4b79900222b8cccd4da4a7a89581f

  Thank you.

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

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


[Kernel-packages] [Bug 1758796] Re: Kernel Crash

2018-03-27 Thread 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.16 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.16-rc7

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

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

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

Title:
  Kernel Crash

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Have the logs around this.  Failed while running unattended.

  ProblemType: KernelCrash
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-117-generic 4.4.0-117.141
  ProcVersionSignature: Ubuntu 4.4.0-117.141-generic 4.4.114
  Uname: Linux 4.4.0-117-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  johnny 8301 F pulseaudio
  Date: Sun Mar 25 06:09:20 2018
  HibernationDevice: RESUME=UUID=5ed7ec2d-76de-4b8d-b427-f94d429221a5
  InstallationDate: Installed on 2011-12-21 (2285 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: MSI MS-7680
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-117-generic 
root=UUID=430a9050-fa68-406c-812c-8a6384c75d43 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-117-generic N/A
   linux-backports-modules-4.4.0-117-generic  N/A
   linux-firmware 1.157.17
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-08-18 (583 days ago)
  dmi.bios.date: 04/11/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V17.1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-P21 (MS-7680)
  dmi.board.vendor: MSI
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 3.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV17.1:bd04/11/2011:svnMSI:pnMS-7680:pvr3.0:rvnMSI:rnH61M-P21(MS-7680):rvr3.0:cvnMSI:ct3:cvr3.0:
  dmi.product.name: MS-7680
  dmi.product.version: 3.0
  dmi.sys.vendor: MSI

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

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


[Kernel-packages] [Bug 1759254] Re: BUG: unable to handle kernel paging request at ffff895ec6c60600

2018-03-27 Thread 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.16 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.16-rc7


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

** Also affects: linux (Ubuntu Bionic)
   Importance: Medium
   Status: Confirmed

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

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

Title:
  BUG: unable to handle kernel paging request at 895ec6c60600

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

Bug description:
  Ubuntu Bionic Beaver (development branch)

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13 [modified: 
boot/vmlinuz-4.15.0-12-generic]
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1109 F pulseaudio
delpianod   6436 F pulseaudio
  Date: Tue Mar 27 09:58:14 2018
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: 0x895ec6c60600 RSP: b87201717c40
  Failure: oops
  InstallationDate: Installed on 2018-03-26 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325)
  MachineType: ZOTAC XX
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=fab05f7e-b132-4a86-8464-6b5d05925d80 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: BUG: unable to handle kernel paging request at 895ec6c60600
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B301P016
  dmi.board.asset.tag: N/A
  dmi.board.name: XX
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 2
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB301P016:bd03/14/2016:svnZOTAC:pnXX:pvrXX:rvnZOTAC:rnXX:rvrXX:cvnDefaultstring:ct2:cvrDefaultstring:
  dmi.product.family: N/A
  dmi.product.name: XX
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

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

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


[Kernel-packages] [Bug 1758812] Re: BUG: Bad page map in process renderer_crash_ pte:00c30000 pmd:77266067

2018-03-27 Thread 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.16 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.16-rc7

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

Title:
  BUG: Bad page map in process renderer_crash_  pte:00c3
  pmd:77266067

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  BUG: Bad page map in process renderer_crash_  pte:00c3
  pmd:77266067

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1103 F pulseaudio
marge  1411 F pulseaudio
   /dev/snd/controlC1:  gdm1103 F pulseaudio
marge  1411 F pulseaudio
  Date: Sat Mar 24 21:46:04 2018
  Failure: oops
  InstallationDate: Installed on 2017-10-20 (156 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   eno1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: ASUS All Series
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=16439337-51ef-4bcb-954c-acacc49e546f ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: BUG: Bad page map in process renderer_crash_  pte:00c3 pmd:77266067
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2903
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97M-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2903:bd02/22/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97M-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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


[Kernel-packages] [Bug 1758815] Re: BUG: Bad rss-counter state mm:000000006498327e idx:2 val:-2

2018-03-27 Thread 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.16 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.16-rc7

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

Title:
  BUG: Bad rss-counter state mm:6498327e idx:2 val:-2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  BUG: Bad rss-counter state mm:6498327e idx:2 val:-2

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1103 F pulseaudio
marge  1411 F pulseaudio
   /dev/snd/controlC1:  gdm1103 F pulseaudio
marge  1411 F pulseaudio
  Date: Sat Mar 24 21:47:05 2018
  Failure: oops
  InstallationDate: Installed on 2017-10-20 (156 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   eno1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: ASUS All Series
  OopsText:
   BUG: Bad rss-counter state mm:6498327e idx:2 val:-2
   traps: kernel_oops[14082] general protection ip:4436c4 sp:7ffd52575458 
error:0 in python3.6[40+3c1000]
   apport[14087]: segfault at 340020 ip 00422187 sp 7ffe656bd068 
error 4 in python3.6[40+3c1000]
   Process 14087(apport) has RLIMIT_CORE set to 1
   Aborting core
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=16439337-51ef-4bcb-954c-acacc49e546f ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: BUG: Bad rss-counter state mm:6498327e idx:2 val:-2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2903
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97M-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2903:bd02/22/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97M-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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


[Kernel-packages] [Bug 1759312] Re: AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu 17.10

2018-03-27 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Artful)
   Status: Triaged => In Progress

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

** Also affects: linux (Ubuntu Bionic)
   Importance: Medium
 Assignee: Joseph Salisbury (jsalisbury)
   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/1759312

Title:
  AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu
  17.10

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  ---Problem Description---
  AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu 17.10
   
  ---Additional Hardware Info---
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  176
  On-line CPU(s) list: 0-175
  Thread(s) per core:  4
  Core(s) per socket:  22
  Socket(s):   2
  NUMA node(s):8
  Model:   2.2 (pvr 004e 1202)
  Model name:  POWER9, altivec supported
  CPU max MHz: 2800.
  CPU min MHz: 2300.
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:512K
  L3 cache:10240K
  NUMA node0 CPU(s):   0-87
  NUMA node8 CPU(s):   88-175
  NUMA node250 CPU(s): 
  NUMA node251 CPU(s): 
  NUMA node252 CPU(s): 
  NUMA node253 CPU(s): 
  NUMA node254 CPU(s): 
  NUMA node255 CPU(s): 
   
  Machine Type = P9, DD2.2, Witherspoon, baremetal 
   
  ---Steps to Reproduce---
   AT_BASE_PLATFORM in AIXV is not exported to userspace on P9 baremetal 
machines causing trouble to userspace tools and software that relie on that 
information, notably operf and opreport (from oprofile 1.2.0+) will refuse to 
run without that information show a error message like:

  gromero@ltc-wspoon3:/boot$ operf
  NULL returned for one or both of AT_PLATFORM/AT_BASE_PLATFORM
  AT_PLATFORM: power9;  AT_BASE_PLATFORM: (null)
  Unable to obtain cpu_type
  Verify that a pre-1.0 version of OProfile is not in use.
  If the /dev/oprofile/cpu_type file exists, locate the pre-1.0 OProfile
  installation, and use its 'opcontrol' command, passing the --deinit option.
  Unable to ascertain cpu type.  Exiting.
   
  ---uname output---
  linux-image-4.13.0-36-generic  4.13.0-36.40

  Userspace tool common name: operf, opreport 

  Dear maintainer. please consider applying the following fix that's
  already available upstream:

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=e4b79900222b8cccd4da4a7a89581f

  Thank you.

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

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


[Kernel-packages] [Bug 1758869] Re: Kernel panic with AWS 4.4.0-1053 / 4.4.0-1015 (Trusty)

2018-03-27 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  Kernel panic with AWS 4.4.0-1053 / 4.4.0-1015 (Trusty)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  This is a POTENTIAL REGRESSION.

  This issue only occurs on one of the AWS testing instance "c3.large"

  Reproduce rate: 100% (All jenkins deployment job failed with this
  instance)

  Steps:
    1. Deploy this instance with AWS kernel (4.4.0-1052)
    2. Enable -proposed, upgrade it and reboot.

  Result:
    * System can boot with 4.4.0-1052, but it won't be accessible after 
rebooting for 4.4.0-1053, from "aws ec2 get-console-output" command indicates 
it hang with kernel panic issue on boot. It looks like the intel-microcode is 
causing this issue.

  Output from the command: https://pastebin.ubuntu.com/p/3JvWNk5CTs/
  (it's a bit difficult to get full output, the instance will keep
  rebooting itself)

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

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


[Kernel-packages] [Bug 1758466] Re: bionic: default io_timeout for nvme is 255 on AWS

2018-03-27 Thread Robert C Jennings
** Also affects: cloud-images
   Importance: Undecided
   Status: New

** No longer affects: 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/1758466

Title:
  bionic: default io_timeout for nvme is 255 on AWS

Status in cloud-images:
  New
Status in linux source package in Bionic:
  Triaged

Bug description:
  According to AWS docs, using newer instance types that use NVME drivers 
(c5/m5), the io timeout should be set to maximum (ideally 4294967295).
  https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/nvme-ebs-volumes.html

  It appears this is done for 16.04, but in 18.04 it is the default.

  Test done by spinning up an m5.large instance in ap-southeast-2.

  Ubuntu 16.04 AMI on AWS (latest AMI - 20180126):

  $ cat /sys/module/nvme/parameters/io_timeout
  4294967295

  $ uname -r
  4.4.0-1049-aws

  Ubuntu 18.04 AMI on AWS (latest nightly AMI - 20180323):

  $ cat /sys/module/nvme_core/parameters/io_timeout
  255

  $ uname -r
  4.15.0-1001-aws

  Perhaps as part of the move to nvme_core this got lost.
  --- 
  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': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  DistroRelease: Ubuntu 18.04
  Ec2AMI: ami-5c5d903e
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2b
  Ec2InstanceType: m5.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  JournalErrors:
   -- Logs begin at Sat 2018-03-24 01:00:37 UTC, end at Sat 2018-03-24 01:01:37 
UTC. --
   Mar 24 01:00:56 ip-10-1-2-86 iscsid[849]: iSCSI daemon with pid=850 started!
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Amazon EC2 m5.large
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1001-aws 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 
nvme_core.io_timeout=255
  ProcVersionSignature: Ubuntu 4.15.0-1001.1-aws 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1001-aws N/A
   linux-backports-modules-4.15.0-1001-aws  N/A
   linux-firmware   N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic ec2-images
  Uname: Linux 4.15.0-1001-aws x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: False
  dmi.bios.date: 10/16/2017
  dmi.bios.vendor: Amazon EC2
  dmi.bios.version: 1.0
  dmi.board.asset.tag: i-0d27cecf4877dafa7
  dmi.board.vendor: Amazon EC2
  dmi.chassis.asset.tag: Amazon EC2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Amazon EC2
  dmi.modalias: 
dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.large:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:
  dmi.product.name: m5.large
  dmi.sys.vendor: Amazon EC2

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1758466/+subscriptions

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


[Kernel-packages] [Bug 1759314] Re: missing memory (32Gib instead of 64GiB)

2018-03-27 Thread 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.16 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.16-rc7


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

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

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

Title:
  missing memory (32Gib instead of 64GiB)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The box has 64GiB ram, EFI shell and dmidecode --type memory see 4 x
  16384 MiB, but dmesg and free report 32GiB

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-13-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Date: Tue Mar 27 17:48:32 2018
  HibernationDevice: RESUME=/dev/mapper/s02--vg-swap_1
  InstallationDate: Installed on 2018-03-27 (0 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180311)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.20
  dmi.board.name: X370 Taichi
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd04/20/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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


[Kernel-packages] [Bug 1758816] Re: BUG: Bad rss-counter state mm:000000006498327e idx:2 val:-2

2018-03-27 Thread Joseph Salisbury
*** This bug is a duplicate of bug 1758815 ***
https://bugs.launchpad.net/bugs/1758815

** This bug has been marked a duplicate of bug 1758815
   BUG: Bad rss-counter state mm:6498327e idx:2 val:-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/1758816

Title:
  BUG: Bad rss-counter state mm:6498327e idx:2 val:-2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  BUG: Bad rss-counter state mm:6498327e idx:2 val:-2

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1103 F pulseaudio
marge  1411 F pulseaudio
   /dev/snd/controlC1:  gdm1103 F pulseaudio
marge  1411 F pulseaudio
  Date: Sat Mar 24 21:47:05 2018
  Failure: oops
  InstallationDate: Installed on 2017-10-20 (156 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   eno1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: ASUS All Series
  OopsText:
   BUG: Bad rss-counter state mm:6498327e idx:2 val:-2
   traps: kernel_oops[14082] general protection ip:4436c4 sp:7ffd52575458 
error:0 in python3.6[40+3c1000]
   apport[14087]: segfault at 340020 ip 00422187 sp 7ffe656bd068 
error 4 in python3.6[40+3c1000]
   Process 14087(apport) has RLIMIT_CORE set to 1
   Aborting core
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=16439337-51ef-4bcb-954c-acacc49e546f ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: BUG: Bad rss-counter state mm:6498327e idx:2 val:-2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2903
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97M-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2903:bd02/22/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97M-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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


[Kernel-packages] [Bug 1758813] Re: BUG: Bad page map in process renderer_crash_ pte:001f0000 pmd:77266067

2018-03-27 Thread Joseph Salisbury
*** This bug is a duplicate of bug 1758812 ***
https://bugs.launchpad.net/bugs/1758812

** This bug has been marked a duplicate of bug 1758812
   BUG: Bad page map in process renderer_crash_  pte:00c3 pmd:77266067

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

Title:
  BUG: Bad page map in process renderer_crash_  pte:001f
  pmd:77266067

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  BUG: Bad page map in process renderer_crash_  pte:001f
  pmd:77266067

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1103 F pulseaudio
marge  1411 F pulseaudio
   /dev/snd/controlC1:  gdm1103 F pulseaudio
marge  1411 F pulseaudio
  Date: Sat Mar 24 21:46:05 2018
  Failure: oops
  InstallationDate: Installed on 2017-10-20 (156 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   eno1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: ASUS All Series
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=16439337-51ef-4bcb-954c-acacc49e546f ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: BUG: Bad page map in process renderer_crash_  pte:001f pmd:77266067
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2903
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97M-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2903:bd02/22/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97M-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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


[Kernel-packages] [Bug 1758814] Re: BUG: Bad page map in process renderer_crash_ pte:00c30000 pmd:77266067

2018-03-27 Thread Joseph Salisbury
*** This bug is a duplicate of bug 1758812 ***
https://bugs.launchpad.net/bugs/1758812

** This bug has been marked a duplicate of bug 1758812
   BUG: Bad page map in process renderer_crash_  pte:00c3 pmd:77266067

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

Title:
  BUG: Bad page map in process renderer_crash_  pte:00c3
  pmd:77266067

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  BUG: Bad page map in process renderer_crash_  pte:00c3
  pmd:77266067

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1103 F pulseaudio
marge  1411 F pulseaudio
   /dev/snd/controlC1:  gdm1103 F pulseaudio
marge  1411 F pulseaudio
  Date: Sat Mar 24 21:46:04 2018
  Failure: oops
  InstallationDate: Installed on 2017-10-20 (156 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   eno1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: ASUS All Series
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=16439337-51ef-4bcb-954c-acacc49e546f ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: BUG: Bad page map in process renderer_crash_  pte:00c3 pmd:77266067
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2903
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97M-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2903:bd02/22/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97M-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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


[Kernel-packages] [Bug 1759330] Re: kernel BUG at /build/linux-bdpCf2/linux-4.15.0/mm/slub.c:296!

2018-03-27 Thread Joseph Salisbury
Do you have a way to reproduce this bug, or was it a one time event?

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

Title:
  kernel BUG at /build/linux-bdpCf2/linux-4.15.0/mm/slub.c:296!

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  dont know it just gave me the error messege

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 966 F pulseaudio
techterror12   1382 F pulseaudio
   /dev/snd/controlC1:  gdm 966 F pulseaudio
techterror12   1382 F pulseaudio
  Date: Tue Mar 27 12:22:22 2018
  Failure: oops
  HibernationDevice: RESUME=UUID=b83a3832-8bd2-46ee-b79e-9bb804e1613d
  InstallationDate: Installed on 2018-02-25 (29 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305FA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi= acpi_backight_native 
vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: kernel BUG at /build/linux-bdpCf2/linux-4.15.0/mm/slub.c:296!
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305FA.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305FA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX305FA.208:bd03/26/2015:svnASUSTeKCOMPUTERINC.:pnUX305FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX305FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1759312] Re: AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu 17.10

2018-03-27 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Status: New => Triaged

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

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

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

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

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

** Changed in: linux (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
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/1759312

Title:
  AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu
  17.10

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  ---Problem Description---
  AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu 17.10
   
  ---Additional Hardware Info---
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  176
  On-line CPU(s) list: 0-175
  Thread(s) per core:  4
  Core(s) per socket:  22
  Socket(s):   2
  NUMA node(s):8
  Model:   2.2 (pvr 004e 1202)
  Model name:  POWER9, altivec supported
  CPU max MHz: 2800.
  CPU min MHz: 2300.
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:512K
  L3 cache:10240K
  NUMA node0 CPU(s):   0-87
  NUMA node8 CPU(s):   88-175
  NUMA node250 CPU(s): 
  NUMA node251 CPU(s): 
  NUMA node252 CPU(s): 
  NUMA node253 CPU(s): 
  NUMA node254 CPU(s): 
  NUMA node255 CPU(s): 
   
  Machine Type = P9, DD2.2, Witherspoon, baremetal 
   
  ---Steps to Reproduce---
   AT_BASE_PLATFORM in AIXV is not exported to userspace on P9 baremetal 
machines causing trouble to userspace tools and software that relie on that 
information, notably operf and opreport (from oprofile 1.2.0+) will refuse to 
run without that information show a error message like:

  gromero@ltc-wspoon3:/boot$ operf
  NULL returned for one or both of AT_PLATFORM/AT_BASE_PLATFORM
  AT_PLATFORM: power9;  AT_BASE_PLATFORM: (null)
  Unable to obtain cpu_type
  Verify that a pre-1.0 version of OProfile is not in use.
  If the /dev/oprofile/cpu_type file exists, locate the pre-1.0 OProfile
  installation, and use its 'opcontrol' command, passing the --deinit option.
  Unable to ascertain cpu type.  Exiting.
   
  ---uname output---
  linux-image-4.13.0-36-generic  4.13.0-36.40

  Userspace tool common name: operf, opreport 

  Dear maintainer. please consider applying the following fix that's
  already available upstream:

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=e4b79900222b8cccd4da4a7a89581f

  Thank you.

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

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


[Kernel-packages] [Bug 1759342] Re: BUG: Bad rss-counter state mm:000000003cebd506 idx:0 val:75

2018-03-27 Thread 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.16 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.16-rc7

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

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

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

Title:
  BUG: Bad rss-counter state mm:3cebd506 idx:0 val:75

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Crash happened after booting the system

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bertadmin   1745 F pulseaudio
  Date: Sat Mar 24 11:42:05 2018
  Failure: oops
  InstallationDate: Installed on 2018-03-11 (16 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=22835ac6-a7b5-4601-bd4b-a6c98e4df3fb ro quiet splash zwap.enabled=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: BUG: Bad rss-counter state mm:3cebd506 idx:0 val:75
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


[Kernel-packages] [Bug 1758463] Re: DVD drive works under Win dows 10 but not Ubuntu 17.10

2018-03-27 Thread 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.16 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.16-rc7


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

Title:
  DVD drive works under Win dows 10 but not Ubuntu 17.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Drive does not mount when any supported media type is inserted and is
  unusable. Older drive(NEC DVD+/-RW ND-6650A) with newer motherboard
  (Z370N-WIFI).

  greg@greg-Z370N-WIFI:~$ dmesg |grep -i ata3
  [0.660472] ata3: SATA max UDMA/133 abar m2048@0xf724b000 port 0xf724b200 
irq 129
  [0.980029] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
  [0.983555] ata3.00: ATAPI: _NEC DVD+/-RW ND-6650A, 103D, max UDMA/33
  [0.983556] ata3.00: applying bridge limits
  [0.990656] ata3.00: configured for UDMA/33
  [6.112005] ata3.00: qc timeout (cmd 0xa0)
  [6.116004] ata3.00: TEST_UNIT_READY failed (err_mask=0x4)
  [6.432011] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
  [6.442649] ata3.00: configured for UDMA/33
  [   11.488004] ata3.00: qc timeout (cmd 0xa0)
  [   11.488008] ata3.00: TEST_UNIT_READY failed (err_mask=0x4)
  [   11.488009] ata3: limiting SATA link speed to 1.5 Gbps
  [   11.488010] ata3.00: limiting speed to UDMA/33:PIO3
  [   11.804011] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [   11.814638] ata3.00: configured for UDMA/33
  [   16.864003] ata3.00: qc timeout (cmd 0xa0)
  [   16.864007] ata3.00: TEST_UNIT_READY failed (err_mask=0x4)
  [   16.864008] ata3.00: disabled
  [   16.868004] ata3: hard resetting link
  [   17.184011] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [   17.184014] ata3: EH complete
  greg@greg-Z370N-WIFI:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-37-generic 4.13.0-37.42
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  greg   1651 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 23 17:17:43 2018
  GvfsMonitorError:
   This tool has been deprecated, use 'gio mount' instead.
   See 'gio help mount' for more info.
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=c0e62877-bafa-4694-b2c3-8f4f2e1df82f
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2018-03-17 (6 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: Gigabyte Technology Co., Ltd. Z370N WIFI
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic.efi.signed 
root=UUID=4b0ef4f1-040a-46c5-af19-f012da1ef057 ro quiet splash acpi=off 
i915.alpha_support=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-37-generic N/A
   linux-backports-modules-4.13.0-37-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  Symptom: storage
  UdevMonitorLog:
   monitor will print the received events for:
   UDEV - the event which udev sends out after rule processing
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   17:18:20.743: The udisks-daemon is running (name-owner :1.2).
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/09/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: Default string
  dmi.board.name: Z370N WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd11/09/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370NWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370NWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  

[Kernel-packages] [Bug 1758507] Re: sky2 gigabit ethernet driver sometimes stops working after resume from sleep (88E8055)

2018-03-27 Thread 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.16 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.16-rc7

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

Title:
  sky2 gigabit ethernet driver sometimes stops working after resume from
  sleep (88E8055)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After resuming from sleep, OCCASIONALLY the NIC is not functional, and
  reloading the sky2 module does not work. Relevant parts from dmesg:

  [  582.852065] sky2 :04:00.0: Refused to change power state, currently in 
D3
  ...
  [  827.613729] sky2 :04:00.0: ignoring stuck error report bit
  [  827.613748] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613750] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613752] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613754] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613756] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613759] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613761] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613763] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613765] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613767] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613769] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613772] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613774] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613776] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613778] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613780] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613782] sky2 :04:00.0: enp4s0: phy I/O error

  And after reloading the module:
  [ 1421.781480] sky2: driver version 1.30
  [ 1421.781533] sky2 :04:00.0: enabling device ( -> 0003)
  [ 1421.781667] sky2 :04:00.0: unsupported chip type 0xff
  [ 1421.782292] sky2: probe of :04:00.0 failed with error -95

  Replicability: When it happens once, further suspend-resume cycles (tried ~5) 
don't fix it. Reboot may fix it, (again, for at least the 5 suspend cycles I've 
tried).
  Per-boot chance of encountering the issue - so far 2/5.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-12-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Date: Sat Mar 24 09:54:10 2018
  HibernationDevice: RESUME=UUID=02d18685-fc92-4ebe-a43e-34d1e52a26b1
  InstallationDate: Installed on 2018-03-21 (3 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180319)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: FUJITSU SIEMENS ESPRIMO Mobile U9200
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=bc171dce-b703-44f6-8244-22b6b3b1dc33 ro video=SVIDEO-1:d 
consoleblank=300
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2008
  dmi.bios.vendor: Phoenix
  dmi.bios.version: 1.11 - 067 - 1566
  dmi.board.name: S11D
  dmi.board.vendor: FUJITSU SIEMENS
  dmi.board.version: 

[Kernel-packages] [Bug 1758384] Re: [Acer AO532h] hibernate/resume failure

2018-03-27 Thread 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.16 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.16-rc7


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

Title:
  [Acer AO532h] hibernate/resume failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I put the computer in hibernation using sudo pm-hibernate. Computer
  seemed to go into hibernation normally but didn't wake up properly.
  System hibernates properly under Artful. Disk has a proper 2gb swap
  partition.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13 [modified: 
boot/vmlinuz-4.15.0-12-generic]
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ka1ssr 1005 F pulseaudio
  Date: Fri Mar 23 12:36:52 2018
  DuplicateSignature: hibernate/resume:Acer AO532h:V1.26
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=600f4807-bc16-448c-9a8f-bf5330a75d9e
  InstallationDate: Installed on 2018-03-23 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180323)
  InterpreterPath: /usr/bin/python3.6
  MachineType: Acer AO532h
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=d2c54fce-ed1a-4448-b75b-94fad1b35afd ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  Title: [Acer AO532h] hibernate/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/28/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.26
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: AO532h
  dmi.board.vendor: Acer
  dmi.board.version: V1.26
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.26
  dmi.modalias: 
dmi:bvnAcer:bvrV1.26:bd04/28/2011:svnAcer:pnAO532h:pvrV1.26:rvnAcer:rnAO532h:rvrV1.26:cvnAcer:ct10:cvrV1.26:
  dmi.product.family: Intel_Mobile
  dmi.product.name: AO532h
  dmi.product.version: V1.26
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1758442] Re: [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

2018-03-27 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

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

Title:
  [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Three of the "function" keys on this laptop don't work at all: "Mute",
  "Brightness Down", and "Brightness Up". I believe these keys are
  controlled by WMI. Other buttons not controlled by WMI, such as
  "Volume Up" and "Volume Down" (both by ACPI), work fine. Setting
  display brightness via software (e.g., GUI slider) works fine.

  Sometimes other keys (Windows, up/down arrow, pgup/pgdn) are
  interpreted as "Brightness Down". This behavior seems to come and go
  randomly after each reboot.

  I have tried setting (separately) acpi_osi=Linux and
  acpi_backlight=vendor without effect.

  The hp_wmi driver raises these message at each boot:
  [   19.610528] hp_wmi: query 0xd returned error 0x5
  [   19.610569] input: HP WMI hotkeys as /devices/virtual/input/input14

  This system has the latest BIOS (1.43A, released 2018-01-25) and the
  latest Intel ME firmware (9.1.42.3002, released 2017-12-19).

  No output is generated when pressing these buttons with evtest
  (choosing option 8, "HP WMI hotkeys"), xev, or acpi_listen).

  I have attached the debugging information requested at
  
,
  although fwts method does not seem to be a valid command (anymore?).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 1415 F pulseaudio
   /dev/snd/controlC0:  vectro 1415 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Mar 23 17:15:19 2018
  HibernationDevice: RESUME=UUID=0f34a9a4-0160-489a-9325-45913b03eb06
  InstallationDate: Installed on 2018-03-23 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash acpi_osi=Linux vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1758620] Re: Excessive kworker invocations after wake from suspend

2018-03-27 Thread 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.16 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.16-rc7

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

Title:
  Excessive kworker invocations after wake from suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Whenever I wake my computer from a "Suspend", System Monitor shows
  over 80 instances of kworker spontaneously get spawned.  If I move the
  mouse, the PC crashes and I must restart.

  If I don't touch the mouse and let the PC sit untouched for about 10
  minutes, the 80 extra kworker daemons terminate and only the "normal"
  8 remain.  The PC operates fine from then on.

  I get similar behaviour on 3 different machines, all 64 bit 16.04LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-116-generic 4.4.0-116.140
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bob1436 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar 25 02:26:12 2018
  HibernationDevice: RESUME=UUID=0e553f8e-0d16-4cd5-9faa-b131ebed6c74
  InstallationDate: Installed on 2018-03-01 (23 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard Presario CQ62 Notebook PC
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=c94db9b0-0eb0-4d47-a791-a9dab0dc42cf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-116-generic N/A
   linux-backports-modules-4.4.0-116-generic  N/A
   linux-firmware 1.157.17
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.0A
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1444
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 69.17
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.0A:bd06/08/2010:svnHewlett-Packard:pnPresarioCQ62NotebookPC:pvr0498102428102:rvnHewlett-Packard:rn1444:rvr69.17:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: Presario CQ62 Notebook PC
  dmi.product.version: 0498102428102
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1758466] Re: bionic: default io_timeout for nvme is 255 on AWS

2018-03-27 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Also affects: linux (Ubuntu Bionic)
   Importance: Medium
   Status: Confirmed

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

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

Title:
  bionic: default io_timeout for nvme is 255 on AWS

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

Bug description:
  According to AWS docs, using newer instance types that use NVME drivers 
(c5/m5), the io timeout should be set to maximum (ideally 4294967295).
  https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/nvme-ebs-volumes.html

  It appears this is done for 16.04, but in 18.04 it is the default.

  Test done by spinning up an m5.large instance in ap-southeast-2.

  Ubuntu 16.04 AMI on AWS (latest AMI - 20180126):

  $ cat /sys/module/nvme/parameters/io_timeout
  4294967295

  $ uname -r
  4.4.0-1049-aws

  Ubuntu 18.04 AMI on AWS (latest nightly AMI - 20180323):

  $ cat /sys/module/nvme_core/parameters/io_timeout
  255

  $ uname -r
  4.15.0-1001-aws

  Perhaps as part of the move to nvme_core this got lost.
  --- 
  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': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  DistroRelease: Ubuntu 18.04
  Ec2AMI: ami-5c5d903e
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2b
  Ec2InstanceType: m5.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  JournalErrors:
   -- Logs begin at Sat 2018-03-24 01:00:37 UTC, end at Sat 2018-03-24 01:01:37 
UTC. --
   Mar 24 01:00:56 ip-10-1-2-86 iscsid[849]: iSCSI daemon with pid=850 started!
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Amazon EC2 m5.large
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1001-aws 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 
nvme_core.io_timeout=255
  ProcVersionSignature: Ubuntu 4.15.0-1001.1-aws 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1001-aws N/A
   linux-backports-modules-4.15.0-1001-aws  N/A
   linux-firmware   N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic ec2-images
  Uname: Linux 4.15.0-1001-aws x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: False
  dmi.bios.date: 10/16/2017
  dmi.bios.vendor: Amazon EC2
  dmi.bios.version: 1.0
  dmi.board.asset.tag: i-0d27cecf4877dafa7
  dmi.board.vendor: Amazon EC2
  dmi.chassis.asset.tag: Amazon EC2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Amazon EC2
  dmi.modalias: 
dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.large:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:
  dmi.product.name: m5.large
  dmi.sys.vendor: Amazon EC2

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

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


[Kernel-packages] [Bug 1758545] Re: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer

2018-03-27 Thread Joseph Salisbury
** 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/1758545

Title:
  PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction
  Layer

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My dmesg gets completely spammed with the following messages appearing over 
and over again, and this keep increasing the size of log file. I can use 
pci=noaer parameter to suppress these annoying messages, but not sure what this 
parameter do, will it make my pc lost some function.Is this a bug? below is 
part of the dmesg infomation
  
--

  [  397.076509] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, id=0009(Requester ID)
  [  397.076517] pcieport :00:01.1:   device [1022:15d3] error 
status/mask=0010/0440
  [  397.076522] pcieport :00:01.1:[20] Unsupported Request(First)
  [  397.076526] pcieport :00:01.1:   TLP Header: 3400 01001f10 
 8c548c54
  [  397.081907] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, id=0009(Requester ID)
  [  397.081914] pcieport :00:01.1:   device [1022:15d3] error 
status/mask=0010/0440
  [  397.081918] pcieport :00:01.1:[20] Unsupported Request(First)
  [  397.081923] pcieport :00:01.1:   TLP Header: 3400 01001f10 
 8c548c54
  [  398.983368] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, id=0009(Requester ID)
  [  398.983376] pcieport :00:01.1:   device [1022:15d3] error 
status/mask=0010/0440
  [  398.983381] pcieport :00:01.1:[20] Unsupported Request(First)
  [  398.983385] pcieport :00:01.1:   TLP Header: 3400 01001f10 
 8c548c54
  [  398.984773] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, id=0009(Requester ID)
  [  398.984779] pcieport :00:01.1:   device [1022:15d3] error 
status/mask=0010/0440
  [  398.984783] pcieport :00:01.1:[20] Unsupported Request(First)
  [  398.984788] pcieport :00:01.1:   TLP Header: 3400 01001f10 
 8c548c54
  [  398.994170] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, id=0009(Requester ID)
  [  398.994176] pcieport :00:01.1:   device [1022:15d3] error 
status/mask=0010/0440
  [  398.994180] pcieport :00:01.1:[20] Unsupported Request(First)
  [  398.994185] pcieport :00:01.1:   TLP Header: 3400 01001f10 
 8c548c54
  [  399.333957] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, id=0009(Requester ID)
  [  399.333964] pcieport :00:01.1:   device [1022:15d3] error 
status/mask=0010/0440
  [  399.333968] pcieport :00:01.1:[20] Unsupported Request(First)
  [  399.333973] pcieport :00:01.1:   TLP Header: 3400 01001f10 
 8c548c54
  [  399.339347] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, id=0009(Requester ID)
  [  399.339353] pcieport :00:01.1:   device [1022:15d3] error 
status/mask=0010/0440
  [  399.339358] pcieport :00:01.1:[20] Unsupported Request(First)
  [  399.339362] pcieport :00:01.1:   TLP Header: 3400 01001f10 
 8c548c54

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ven1747 F pulseaudio
   /dev/snd/controlC0:  ven1747 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 24 23:24:16 2018
  InstallationDate: Installed on 2018-03-07 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  MachineType: LENOVO 81BR
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=a8a345d7-5b2e-495a-897a-351b10597e61 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  

[Kernel-packages] [Bug 1758546] Re: BUG: Bad rss-counter state mm:000000003cebd506 idx:0 val:75

2018-03-27 Thread 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.16 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.16-rc7

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

Title:
  BUG: Bad rss-counter state mm:3cebd506 idx:0 val:75

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Crash occured after reboot of the Saturday update.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bertadmin   1390 F pulseaudio
  Date: Sat Mar 24 11:41:02 2018
  Failure: oops
  InstallationDate: Installed on 2018-03-11 (13 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=22835ac6-a7b5-4601-bd4b-a6c98e4df3fb ro quiet splash zwap.enabled=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: BUG: Bad rss-counter state mm:3cebd506 idx:0 val:75
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


[Kernel-packages] [Bug 1758556] Re: Kernel BUG at 00000000fc8c686e [verbose debug info unavailable]

2018-03-27 Thread 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.16 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.16-rc7

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

Title:
  Kernel BUG at fc8c686e [verbose debug info unavailable]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I had just logged on after a fresh reboot.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  barbara1207 F pulseaudio
   /dev/snd/controlC0:  barbara1207 F pulseaudio
  Date: Sat Mar 24 12:37:16 2018
  Failure: oops
  HibernationDevice: RESUME=UUID=0acf7cb9-a0d3-4e0b-873f-0cbed278d697
  InstallationDate: Installed on 2018-03-23 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: Dell Inc. Venue 11 Pro 7140
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: Kernel BUG at fc8c686e [verbose debug info unavailable]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0321KP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd07/03/2017:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0321KP:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7140
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1758496] Re: Backlight does not work on a MacBookAir3, 2

2018-03-27 Thread 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.16 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.16-rc7

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

Title:
  Backlight does not work on a MacBookAir3,2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Backlight control does not work and there are no entries in
  /sys/class/backlight. When I boot my system with the option
  GRUB_CMDLINE_LINUX_DEFAULT="acpi_backlight=vendor" I can change the
  brightness with the command xrandr on a terminal.

  I attach all the system information about this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-37-generic 4.13.0-37.42
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  victor 2932 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 24 07:22:05 2018
  InstallationDate: Installed on 2018-03-04 (19 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Apple Inc. MacBookAir3,2
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic.efi.signed 
root=UUID=dd2bcce2-7d14-4df7-b7c8-6aea4fbb9c13 ro acpi_backlight=vendor
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-37-generic N/A
   linux-backports-modules-4.13.0-37-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/10
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA31.88Z.0061.B01.1011181342
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-942C5DF58193131B
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir3,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-942C5DF58193131B
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA31.88Z.0061.B01.1011181342:bd11/18/10:svnAppleInc.:pnMacBookAir3,2:pvr1.0:rvnAppleInc.:rnMac-942C5DF58193131B:rvrMacBookAir3,2:cvnAppleInc.:ct10:cvrMac-942C5DF58193131B:
  dmi.product.family: MacBook
  dmi.product.name: MacBookAir3,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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


[Kernel-packages] [Bug 1759045] Re: Important KVM fixes for ppc64el

2018-03-27 Thread Seth Forshee
We already had a few of these patches; the rest have been committed to
bionic/master-next.

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

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

Title:
  Important KVM fixes for ppc64el

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

Bug description:
  Hi Canonical,

  There are some critical bugs for KVM that didn't make kernel 4.15 and
  we must have then included in 18.04 kernel. They are:

  * Allow HPT guests on P9 DD2.2 without requiring indep_threads_mode=N.
   
  6964e6a4e489 KVM: PPC: Book3S HV: Do SLB load/unload with guest LPCR value 
loaded
  cda4a1473313 KVM: PPC: Book3S HV: Fix duplication of host SLB entries (needed 
once 6964e6a4e489 is in)
  00608e1f007e KVM: PPC: Book3S HV: Allow HPT and radix on the same core for 
POWER9 v2.2
   
  * Memory management fixes.

  c3856aeb2940 KVM: PPC: Book3S HV: Fix handling of large pages in radix page 
fault handler
  debd574f4195 KVM: PPC: Book3S HV: Fix VRMA initialization with 2MB or 1GB 
memory backing
   
  * Emulation of VMX loads and stores for MMIO.
   
  09f984961c13 KVM: PPC: Book3S: Add MMIO emulation for VMX instructions
  6df3877fc962 KVM: PPC: Book3S: Fix compile error that occurs with some gcc 
versions (needed once 09f984961c13 is in)
   
  * Other important fixes.
   
  05f2bb0313a2 KVM: PPC: Book3S HV: Fix handling of secondary HPTEG in HPT 
resizing code
  790a9df5fbef KVM: PPC: Book3S HV: Make HPT resizing work on POWER9
  a8b48a4dccea KVM: PPC: Book3S HV: Fix trap number return from 
__kvmppc_vcore_entry

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

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


[Kernel-packages] [Bug 1758641] Re: bluetooth wont connect to anything

2018-03-27 Thread 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.16 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.16-rc7

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

Title:
  bluetooth wont connect to anything

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The output of  sudo lsusb |grep Bluetooth is nothing.

  And the output of dmesg | grep Blue is:

  [   10.018628] Bluetooth: Core ver 2.22
  [   10.018676] Bluetooth: HCI device and connection manager initialized
  [   10.018686] Bluetooth: HCI socket layer initialized
  [   10.018693] Bluetooth: L2CAP socket layer initialized
  [   10.018710] Bluetooth: SCO socket layer initialized
  [   10.376753] Bluetooth: hci0: BCM: chip id 63
  [   10.377743] Bluetooth: hci0: BCM: features 0x07
  [   10.404276] Bluetooth: hci0: BCM20702A
  [   10.405762] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
  [   10.407317] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0a5c-21e3.hcd not 
found
  [   12.521504] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   12.521509] Bluetooth: BNEP filters: protocol multicast
  [   12.521520] Bluetooth: BNEP socket layer initialized
  [   19.011843] Bluetooth: RFCOMM TTY layer initialized
  [   19.011850] Bluetooth: RFCOMM socket layer initialized
  [   19.011855] Bluetooth: RFCOMM ver 1.11
  [  909.135892] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
  [  909.135905] Bluetooth: HIDP socket layer initialized

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-37-generic 4.13.0-37.42
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mohsen 2254 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 16:10:52 2018
  InstallationDate: Installed on 2018-03-21 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcFB:
   0 radeondrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=UUID=f9a99ba9-effc-4194-9e85-e10decf48af6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-37-generic N/A
   linux-backports-modules-4.13.0-37-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  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: 1670
  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:pnHPPaviliong6NotebookPC:pvr06961220421610100:rvnHewlett-Packard:rn1670:rvr09.4C:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.version: 06961220421610100
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1758557] Re: Kernel BUG at 00000000fc8c686e [verbose debug info unavailable]

2018-03-27 Thread Joseph Salisbury
*** This bug is a duplicate of bug 1758556 ***
https://bugs.launchpad.net/bugs/1758556

** This bug has been marked a duplicate of bug 1758556
   Kernel BUG at fc8c686e [verbose debug info unavailable]

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

Title:
  Kernel BUG at fc8c686e [verbose debug info unavailable]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The error occurred while waiting for Firefox to finish loading the
  report a bug page.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  barbara1207 F pulseaudio
   /dev/snd/controlC0:  barbara1207 F pulseaudio
  Date: Sat Mar 24 12:39:18 2018
  Failure: oops
  HibernationDevice: RESUME=UUID=0acf7cb9-a0d3-4e0b-873f-0cbed278d697
  InstallationDate: Installed on 2018-03-23 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: Dell Inc. Venue 11 Pro 7140
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: Kernel BUG at fc8c686e [verbose debug info unavailable]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0321KP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd07/03/2017:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0321KP:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7140
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1758910] Re: Important Kernel fixes to be backported for Power9 (kvm)

2018-03-27 Thread Seth Forshee
Every one of these except the last three (the ones from the powerpc
tree) are on the other bug, so I'm going to commit them as part of that
one. That bug also includes the additional fix I identified.

The last one, a5d4b5891c2f1f865a2def1eb0030f534e77ff86, does not apply
and seems to be missing prerequisite patches. I'm going to hold off
applying these three patches, please advise of the full list of patches
necessary to apply this commit. 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/1758910

Title:
  Important Kernel fixes to be backported for Power9 (kvm)

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

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-03-26 
02:18:44 ==
  ---Problem Description---
  Important Kernel fixes to be backported for Power9 (kvm)
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-13-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Following upstream patches are need to be backported for Power9 KVM to 
function well.

  * Emulation of VMX loads and stores for MMIO.
   
  09f984961c13 KVM: PPC: Book3S: Add MMIO emulation for VMX instructions
  6df3877fc962 KVM: PPC: Book3S: Fix compile error that occurs with some gcc 
versions (needed once 09f984961c13 is in)
   
  * Other important fixes.
   
  05f2bb0313a2 KVM: PPC: Book3S HV: Fix handling of secondary HPTEG in HPT 
resizing code
  790a9df5fbef KVM: PPC: Book3S HV: Make HPT resizing work on POWER9
  a8b48a4dccea KVM: PPC: Book3S HV: Fix trap number return from 
__kvmppc_vcore_entry

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=ff6781fd1bb404d8a551c02c35c70cec1da17ff1
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=e4b79900222b8cccd4da4a7a89581f0e1b764ed2
  and
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=a5d4b5891c2f1f865a2def1eb0030f534e77ff86

   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for sathe...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.

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

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


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

2018-03-27 Thread bugproxy
--- Comment From gwal...@br.ibm.com 2018-03-27 16:57 EDT---
Hi,

I have reordered and applied cleanly all and the source it's here:

https://github.com/walbon/ubuntu-bionic/commits/bug166067

Patchset list:

6ec1b83e114d KVM: PPC: Book3S HV: Fix duplication of host SLB entries
b2d6a40b332b KVM: PPC: Book3S HV: Fix trap number return from 
__kvmppc_vcore_entry
cbad716a019c KVM: PPC: Book3S HV: Fix VRMA initialization with 2MB or 1GB 
memory backing
fea273650947 KVM: PPC: Book3S HV: Fix handling of large pages in radix page 
fault handler
43fcdb842d83 KVM: PPC: Book3S: Fix compile error that occurs with some gcc 
versions
871f95f1f9dd KVM: PPC: Book3S HV: Fix handling of secondary HPTEG in HPT 
resizing code
504da52340ed KVM: PPC: Book3S: Add MMIO emulation for VMX instructions
1fa1e8c6295a KVM: PPC: Book3S HV: Make HPT resizing work on POWER9
7b6698f68033 KVM: PPC: Book3S HV: Allow HPT and radix on the same core for 
POWER9 v2.2
6e76e5f3e8c6 KVM: PPC: Book3S HV: Do SLB load/unload with guest LPCR value 
loaded

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

Title:
  Important KVM fixes for ppc64el

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  Hi Canonical,

  There are some critical bugs for KVM that didn't make kernel 4.15 and
  we must have then included in 18.04 kernel. They are:

  * Allow HPT guests on P9 DD2.2 without requiring indep_threads_mode=N.
   
  6964e6a4e489 KVM: PPC: Book3S HV: Do SLB load/unload with guest LPCR value 
loaded
  cda4a1473313 KVM: PPC: Book3S HV: Fix duplication of host SLB entries (needed 
once 6964e6a4e489 is in)
  00608e1f007e KVM: PPC: Book3S HV: Allow HPT and radix on the same core for 
POWER9 v2.2
   
  * Memory management fixes.

  c3856aeb2940 KVM: PPC: Book3S HV: Fix handling of large pages in radix page 
fault handler
  debd574f4195 KVM: PPC: Book3S HV: Fix VRMA initialization with 2MB or 1GB 
memory backing
   
  * Emulation of VMX loads and stores for MMIO.
   
  09f984961c13 KVM: PPC: Book3S: Add MMIO emulation for VMX instructions
  6df3877fc962 KVM: PPC: Book3S: Fix compile error that occurs with some gcc 
versions (needed once 09f984961c13 is in)
   
  * Other important fixes.
   
  05f2bb0313a2 KVM: PPC: Book3S HV: Fix handling of secondary HPTEG in HPT 
resizing code
  790a9df5fbef KVM: PPC: Book3S HV: Make HPT resizing work on POWER9
  a8b48a4dccea KVM: PPC: Book3S HV: Fix trap number return from 
__kvmppc_vcore_entry

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

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


[Kernel-packages] [Bug 1758910] Re: Important Kernel fixes to be backported for Power9 (kvm)

2018-03-27 Thread bugproxy
** Tags removed: bugnameltc-166023 kernel-da-key severity-critical
triage-g

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

Title:
  Important Kernel fixes to be backported for Power9 (kvm)

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

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-03-26 
02:18:44 ==
  ---Problem Description---
  Important Kernel fixes to be backported for Power9 (kvm)
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-13-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Following upstream patches are need to be backported for Power9 KVM to 
function well.

  * Emulation of VMX loads and stores for MMIO.
   
  09f984961c13 KVM: PPC: Book3S: Add MMIO emulation for VMX instructions
  6df3877fc962 KVM: PPC: Book3S: Fix compile error that occurs with some gcc 
versions (needed once 09f984961c13 is in)
   
  * Other important fixes.
   
  05f2bb0313a2 KVM: PPC: Book3S HV: Fix handling of secondary HPTEG in HPT 
resizing code
  790a9df5fbef KVM: PPC: Book3S HV: Make HPT resizing work on POWER9
  a8b48a4dccea KVM: PPC: Book3S HV: Fix trap number return from 
__kvmppc_vcore_entry

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=ff6781fd1bb404d8a551c02c35c70cec1da17ff1
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=e4b79900222b8cccd4da4a7a89581f0e1b764ed2
  and
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=a5d4b5891c2f1f865a2def1eb0030f534e77ff86

   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for sathe...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.

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

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


[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

2018-03-27 Thread Leonardo Müller
This is comparing the 4.15.0-13 kernel with the mainline kernel.

** Attachment added: "diff_415_416rc7.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757218/+attachment/5092728/+files/diff_415_416rc7.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/1757218

Title:
  QCA9377 isn't being recognized sometimes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes, the Wireless Network Card QCA9377 is not recognized on
  boot. This caused, on prior versions, a kernel panic at boot. With
  Bionic, the system boots but is unable to use wireless network. On
  dmesg there are messages like:

  [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd
  [2.808640] usb 1-7: device descriptor read/64, error -71
  [3.044337] usb 1-7: device descriptor read/64, error -71
  [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd
  [3.408245] usb 1-7: device descriptor read/64, error -71
  [3.644244] usb 1-7: device descriptor read/64, error -71
  [3.752193] usb usb1-port7: attempt power cycle
  [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd
  [4.404904] usb 1-7: Device not responding to setup address.
  [4.612478] usb 1-7: Device not responding to setup address.
  [4.820588] usb 1-7: device not accepting address 9, error -71
  [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd
  [4.949109] usb 1-7: Device not responding to setup address.
  [5.156893] usb 1-7: Device not responding to setup address.
  [5.364589] usb 1-7: device not accepting address 10, error -71
  [5.364655] usb usb1-port7: unable to enumerate USB device

  And lspci and lsusb don't show the wireless network card. The
  alternative is to turn the system off. Reboot don't work and reboot to
  Windows 10 also don't. The system must be powered off to restore
  functionality. Then, on the next boot, it works properly.

  However, after the system is turned off, it may cause the issue again.
  This is not 100% consistent, but mostly it cycles between powering off
  and powering on the notebook as:

  Work -> Don't work -> Work -> Don't work

  On Windows 10 this doesn't happen but when happens on Ubuntu, it's
  possible to reboot and see the status on Windows 10 too: on Device
  Manager it's shown a unidentified USB device at 1-7. Sometimes, on
  Windows 10's Network Devices it's shown, instead of the QCA9377, from
  four to six different devices with generic names and Bluetooth and/or
  Wireless don't work.

  When turning Ubuntu off, there are messages that appears a few
  instants before the system is turned off:

  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] 
ath10k_pci :02:00.0: failed to install key for vdev 0 peer 
xx:xx:xx:xx:xx:xx: -110
  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] 
wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110)

  Generally, only the second message appears (but both are recorded on
  kern.log). The MAC adress is the one from the router, not from the
  wireless card.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1364 F pulseaudio
   /dev/snd/seq:usuario1258 F timidity
  CurrentDesktop: XFCE
  Date: Tue Mar 20 14:43:42 2018
  HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
  InstallationDate: Installed on 2017-06-13 (279 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (151 days ago)
  dmi.bios.date: 07/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN43WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN43WW:bd07/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80UG
  

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

2018-03-27 Thread Leonardo Müller
The only thing I can think that is wrong is the configuration file of
the kernels. They have some significant differences regarding Bluetooth.

** Attachment added: "diff_415_416rc2+.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757218/+attachment/5092727/+files/diff_415_416rc2+.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/1757218

Title:
  QCA9377 isn't being recognized sometimes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes, the Wireless Network Card QCA9377 is not recognized on
  boot. This caused, on prior versions, a kernel panic at boot. With
  Bionic, the system boots but is unable to use wireless network. On
  dmesg there are messages like:

  [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd
  [2.808640] usb 1-7: device descriptor read/64, error -71
  [3.044337] usb 1-7: device descriptor read/64, error -71
  [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd
  [3.408245] usb 1-7: device descriptor read/64, error -71
  [3.644244] usb 1-7: device descriptor read/64, error -71
  [3.752193] usb usb1-port7: attempt power cycle
  [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd
  [4.404904] usb 1-7: Device not responding to setup address.
  [4.612478] usb 1-7: Device not responding to setup address.
  [4.820588] usb 1-7: device not accepting address 9, error -71
  [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd
  [4.949109] usb 1-7: Device not responding to setup address.
  [5.156893] usb 1-7: Device not responding to setup address.
  [5.364589] usb 1-7: device not accepting address 10, error -71
  [5.364655] usb usb1-port7: unable to enumerate USB device

  And lspci and lsusb don't show the wireless network card. The
  alternative is to turn the system off. Reboot don't work and reboot to
  Windows 10 also don't. The system must be powered off to restore
  functionality. Then, on the next boot, it works properly.

  However, after the system is turned off, it may cause the issue again.
  This is not 100% consistent, but mostly it cycles between powering off
  and powering on the notebook as:

  Work -> Don't work -> Work -> Don't work

  On Windows 10 this doesn't happen but when happens on Ubuntu, it's
  possible to reboot and see the status on Windows 10 too: on Device
  Manager it's shown a unidentified USB device at 1-7. Sometimes, on
  Windows 10's Network Devices it's shown, instead of the QCA9377, from
  four to six different devices with generic names and Bluetooth and/or
  Wireless don't work.

  When turning Ubuntu off, there are messages that appears a few
  instants before the system is turned off:

  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] 
ath10k_pci :02:00.0: failed to install key for vdev 0 peer 
xx:xx:xx:xx:xx:xx: -110
  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] 
wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110)

  Generally, only the second message appears (but both are recorded on
  kern.log). The MAC adress is the one from the router, not from the
  wireless card.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1364 F pulseaudio
   /dev/snd/seq:usuario1258 F timidity
  CurrentDesktop: XFCE
  Date: Tue Mar 20 14:43:42 2018
  HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
  InstallationDate: Installed on 2017-06-13 (279 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (151 days ago)
  dmi.bios.date: 07/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN43WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias: 

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

2018-03-27 Thread Leonardo Müller
This is insane. I have reset that bisect and tried again using "fixed"
and "broken" instead of "new" and "old" and, again, the bisect had the
following:

1fdb926974695d3dbc05a429bafa266fdd16510e is the first fixed commit
commit 1fdb926974695d3dbc05a429bafa266fdd16510e
Author: Hans de Goede 
Date:   Tue Feb 20 09:06:18 2018 +0100

Bluetooth: btusb: Use DMI matching for QCA reset_resume quirking

Commit 61f5acea8737 ("Bluetooth: btusb: Restore QCA Rome suspend/resume fix
with a "rewritten" version") applied the USB_QUIRK_RESET_RESUME to all QCA
USB Bluetooth modules. But it turns out that the resume problems are not
caused by the QCA Rome chipset, on most platforms it resumes fine. The
resume problems are actually a platform problem (likely the platform
cutting all power when suspended).

The USB_QUIRK_RESET_RESUME quirk also disables runtime suspend, so by
matching on usb-ids, we're causing all boards with these chips to use extra
power, to fix resume problems which only happen on some boards.

This commit fixes this by applying the quirk based on DMI matching instead
of on usb-ids, so that we match the platform and not the chipset.

Here is the /sys/kernel/debug/usb/devices for the Bluetooth module:

T:  Bus=01 Lev=01 Prnt=01 Port=07 Cnt=04 Dev#=  5 Spd=12   MxCh= 0
D:  Ver= 2.01 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=0cf3 ProdID=e300 Rev= 0.01
C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=81(I) Atr=03(Int.) MxPS=  16 Ivl=1ms
E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=83(I) Atr=01(Isoc) MxPS=   0 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms
I:  If#= 1 Alt= 1 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=83(I) Atr=01(Isoc) MxPS=   9 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=   9 Ivl=1ms
I:  If#= 1 Alt= 2 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=83(I) Atr=01(Isoc) MxPS=  17 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=  17 Ivl=1ms
I:  If#= 1 Alt= 3 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=83(I) Atr=01(Isoc) MxPS=  25 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=  25 Ivl=1ms
I:  If#= 1 Alt= 4 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=83(I) Atr=01(Isoc) MxPS=  33 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=  33 Ivl=1ms
I:  If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=83(I) Atr=01(Isoc) MxPS=  49 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=  49 Ivl=1ms

BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1514836
Fixes: 61f5acea8737 ("Bluetooth: btusb: Restore QCA Rome suspend/resume..")
Cc: sta...@vger.kernel.org
Cc: Brian Norris 
Cc: Kai-Heng Feng 
Reported-and-tested-by: Kevin Fenzi 
Signed-off-by: Hans de Goede 
Signed-off-by: Marcel Holtmann 

:04 04 2930a43c59c0e767763843528fa8526d4e17b764
626944fe592accb35e33c69be141dbcee910910c M  drivers

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

Title:
  QCA9377 isn't being recognized sometimes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes, the Wireless Network Card QCA9377 is not recognized on
  boot. This caused, on prior versions, a kernel panic at boot. With
  Bionic, the system boots but is unable to use wireless network. On
  dmesg there are messages like:

  [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd
  [2.808640] usb 1-7: device descriptor read/64, error -71
  [3.044337] usb 1-7: device descriptor read/64, error -71
  [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd
  [3.408245] usb 1-7: device descriptor read/64, error -71
  [3.644244] usb 1-7: device descriptor read/64, error -71
  [3.752193] usb usb1-port7: attempt power cycle
  [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd
  [4.404904] usb 1-7: Device not responding to setup address.
  [4.612478] usb 1-7: Device not responding to setup address.
  [4.820588] usb 1-7: device not accepting address 9, error -71
  [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd
  [4.949109] usb 1-7: Device not responding to setup address.
  [5.156893] usb 1-7: Device not responding to setup address.
  [5.364589] usb 1-7: device not accepting address 10, error -71
  [5.364655] usb usb1-port7: unable to enumerate USB device

  And lspci and lsusb don't show the wireless network card. The
  alternative 

[Kernel-packages] [Bug 1759045] Re: Important KVM fixes for ppc64el

2018-03-27 Thread Seth Forshee
** Changed in: linux (Ubuntu Bionic)
   Status: Triaged => In Progress

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

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

Title:
  Important KVM fixes for ppc64el

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  Hi Canonical,

  There are some critical bugs for KVM that didn't make kernel 4.15 and
  we must have then included in 18.04 kernel. They are:

  * Allow HPT guests on P9 DD2.2 without requiring indep_threads_mode=N.
   
  6964e6a4e489 KVM: PPC: Book3S HV: Do SLB load/unload with guest LPCR value 
loaded
  cda4a1473313 KVM: PPC: Book3S HV: Fix duplication of host SLB entries (needed 
once 6964e6a4e489 is in)
  00608e1f007e KVM: PPC: Book3S HV: Allow HPT and radix on the same core for 
POWER9 v2.2
   
  * Memory management fixes.

  c3856aeb2940 KVM: PPC: Book3S HV: Fix handling of large pages in radix page 
fault handler
  debd574f4195 KVM: PPC: Book3S HV: Fix VRMA initialization with 2MB or 1GB 
memory backing
   
  * Emulation of VMX loads and stores for MMIO.
   
  09f984961c13 KVM: PPC: Book3S: Add MMIO emulation for VMX instructions
  6df3877fc962 KVM: PPC: Book3S: Fix compile error that occurs with some gcc 
versions (needed once 09f984961c13 is in)
   
  * Other important fixes.
   
  05f2bb0313a2 KVM: PPC: Book3S HV: Fix handling of secondary HPTEG in HPT 
resizing code
  790a9df5fbef KVM: PPC: Book3S HV: Make HPT resizing work on POWER9
  a8b48a4dccea KVM: PPC: Book3S HV: Fix trap number return from 
__kvmppc_vcore_entry

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

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


[Kernel-packages] [Bug 1758910] Re: Important Kernel fixes to be backported for Power9 (kvm)

2018-03-27 Thread Seth Forshee
Actually it turns out that most of the commits requested here are also
requested on the other bug ...

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

Title:
  Important Kernel fixes to be backported for Power9 (kvm)

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

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-03-26 
02:18:44 ==
  ---Problem Description---
  Important Kernel fixes to be backported for Power9 (kvm)
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-13-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Following upstream patches are need to be backported for Power9 KVM to 
function well.

  * Emulation of VMX loads and stores for MMIO.
   
  09f984961c13 KVM: PPC: Book3S: Add MMIO emulation for VMX instructions
  6df3877fc962 KVM: PPC: Book3S: Fix compile error that occurs with some gcc 
versions (needed once 09f984961c13 is in)
   
  * Other important fixes.
   
  05f2bb0313a2 KVM: PPC: Book3S HV: Fix handling of secondary HPTEG in HPT 
resizing code
  790a9df5fbef KVM: PPC: Book3S HV: Make HPT resizing work on POWER9
  a8b48a4dccea KVM: PPC: Book3S HV: Fix trap number return from 
__kvmppc_vcore_entry

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=ff6781fd1bb404d8a551c02c35c70cec1da17ff1
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=e4b79900222b8cccd4da4a7a89581f0e1b764ed2
  and
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=a5d4b5891c2f1f865a2def1eb0030f534e77ff86

   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for sathe...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.

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

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


[Kernel-packages] [Bug 1758910] Re: Important Kernel fixes to be backported for Power9 (kvm)

2018-03-27 Thread Seth Forshee
Bah, I see that 6964e6a4e489 was requested on bug 1759045. However it
also has a patch that seems to indicate 09f984961c13 (requested on this
bug) is a dependency ...

I'll try to sort out the ordering of the commits between these two bugs.
It would be helpful if future requests could try to sort out these sorts
of dependencies beforehand so we don't end up with these tangled cross-
dependencies between bugs.

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

Title:
  Important Kernel fixes to be backported for Power9 (kvm)

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

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-03-26 
02:18:44 ==
  ---Problem Description---
  Important Kernel fixes to be backported for Power9 (kvm)
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-13-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Following upstream patches are need to be backported for Power9 KVM to 
function well.

  * Emulation of VMX loads and stores for MMIO.
   
  09f984961c13 KVM: PPC: Book3S: Add MMIO emulation for VMX instructions
  6df3877fc962 KVM: PPC: Book3S: Fix compile error that occurs with some gcc 
versions (needed once 09f984961c13 is in)
   
  * Other important fixes.
   
  05f2bb0313a2 KVM: PPC: Book3S HV: Fix handling of secondary HPTEG in HPT 
resizing code
  790a9df5fbef KVM: PPC: Book3S HV: Make HPT resizing work on POWER9
  a8b48a4dccea KVM: PPC: Book3S HV: Fix trap number return from 
__kvmppc_vcore_entry

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=ff6781fd1bb404d8a551c02c35c70cec1da17ff1
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=e4b79900222b8cccd4da4a7a89581f0e1b764ed2
  and
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=a5d4b5891c2f1f865a2def1eb0030f534e77ff86

   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for sathe...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.

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

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


[Kernel-packages] [Bug 1748157] Re: [MIR] thunderbolt-tools

2018-03-27 Thread Yehezkel Bernat
(Sorry, I meant: https://gitlab.freedesktop.org/bolt/bolt/issues/78)

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

Title:
   [MIR] thunderbolt-tools

Status in thunderbolt-tools package in Ubuntu:
  Confirmed

Bug description:
  == Overview ==

  Intel Thunderbolt userspace components provides components for using
  Intel Thunderbolt controllers with security level features.
  Thunderbolt™ technology is a transformational high-speed, dual
  protocol I/O that provides unmatched performance with up to 40Gbps bi-
  directional transfer speeds. It provides flexibility and simplicity by
  supporting both data (PCIe, USB3.1) and video (DisplayPort) on a
  single cable connection that can daisy-chain up to six devices.

  [ See https://github.com/intel/thunderbolt-software-user-space ]

  == Answers to UbuntuMainInclusionRequirements ==

  = Requirements =

  1. Availability
 Package is in universe: 
https://launchpad.net/ubuntu/+source/thunderbolt-tools

  2. Rationale
 Package a device enabler for users with Thunderbolt technology

  3. Security:
 No security issues exposed so far. However, the tools have only been in 
Ubuntu since
 2017-12-09, so this currently is less than the 90 days threshold.

  4. Quality assurance:
 * Manual is provided
 * No debconf questions higher than medium
 * No major outstanding bugs. I'm also helping Intel fix issues that I'm 
finding with
   static analysis tools such as scan-build, cppcheck and CoverityScan
   Bugs outstanding:
 #883857 please backport for stretch-backports
 #882525 thunderbolt-tools: FTBFS on kFreeBSD: 
_ZN5boost6system15system_categoryEv undefined
   - I can fix this, but it makes no sense to run on kFreeBSD
 * Exotic Hardware: Only Thunderbolt supported H/W is required, this is an 
industry standard
   and the support for the tools are in the 4.13+ kernels
 * No Test Suite shipped with the package
 * Does not rely on obsolete or demoted packages

  5. UI standards:
 * This is a CLI tool. Tool has normal CLI style short help and man pages
 * No desktop file required as it is a CLI tool.

  6. Binary Dependencies:
libboost-dev(main)
libboost-filesystem-dev (main)
libboost-program-options-dev(main)
udev(main)

  7. Standards compliance:
 lintian clean and meets the FHS + Debian Policy standards to the best of 
my knowledge

  8. Maintenance
 * Package owning team: The Ubuntu Kernel Team
 * Debian package maintained by Colin Ian King (myself from the Kernel Team)

  9. Background Information
 The user-space components implement device approval support:

 a. Easier interaction with the kernel module for approving connected 
devices.
 b. ACL for auto-approving devices white-listed by the user.

 Tools provided by this package:

  tbtacl - triggered by udev (see the udev rules in tbtacl.rules).
  It auto-approves devices that are found in ACL.

  tbtadm - user-facing CLI tool. It provides operations for device
  approval, handling the ACL and more.

  The user-space components operate in coordination with the
  upstream Thunderbolt kernel driver (found in v4.13) to provide the
  Thunderbolt functionalities. These components are NOT compatible with
  the old out-of-tree Thunderbolt kernel module.

  = Security checks =

http://cve.mitre.org/cve/cve.html: Search in the National Vulnerability 
Database using the package as a keyword
* No CVEs found

http://secunia.com/advisories/search/: search for the package as a keyword
* No security advisories found

Ubuntu CVE Tracker
  http://people.ubuntu.com/~ubuntu-security/cve/main.html
  * No
  http://people.ubuntu.com/~ubuntu-security/cve/universe.html
  * No
  http://people.ubuntu.com/~ubuntu-security/cve/partner.html
  * No

  Check for security relevant binaries. If any are present, this
  requires a more in-depth security review.

  Executables which have the suid or sgid bit set.
* Not applicable

  Executables in /sbin, /usr/sbin.
* None in these paths

  Packages which install daemons (/etc/init.d/*)
* No

  Packages which open privileged ports (ports < 1024).
* No

   Add-ons and plugins to security-sensitive software (filters,
   scanners, UI skins, etc)
* This does exec tbtacl from udev with new udev rules, so this
  needs security checking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbolt-tools/+bug/1748157/+subscriptions

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

[Kernel-packages] [Bug 1758910] Re: Important Kernel fixes to be backported for Power9 (kvm)

2018-03-27 Thread Seth Forshee
It looks like we probably also should include 6df3877fc962 "KVM: PPC:
Book3S: Fix compile error that occurs with some gcc versions" as it is a
fix for 09f984961c13.

a8b48a4dccea does not apply cleanly, at minimum it seems to depend on
changes from:

commit 6964e6a4e4894c707e42d51d9d30683c57f43201
Author: Paul Mackerras 
Date:   Thu Jan 11 14:51:02 2018 +1100

KVM: PPC: Book3S HV: Do SLB load/unload with guest LPCR value loaded

Can IBM please advise whether we should also take this commit, or else
provide a backport of a8b48a4dccea to 4.15? Thanks!

** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => 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/1758910

Title:
  Important Kernel fixes to be backported for Power9 (kvm)

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

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-03-26 
02:18:44 ==
  ---Problem Description---
  Important Kernel fixes to be backported for Power9 (kvm)
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-13-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Following upstream patches are need to be backported for Power9 KVM to 
function well.

  * Emulation of VMX loads and stores for MMIO.
   
  09f984961c13 KVM: PPC: Book3S: Add MMIO emulation for VMX instructions
  6df3877fc962 KVM: PPC: Book3S: Fix compile error that occurs with some gcc 
versions (needed once 09f984961c13 is in)
   
  * Other important fixes.
   
  05f2bb0313a2 KVM: PPC: Book3S HV: Fix handling of secondary HPTEG in HPT 
resizing code
  790a9df5fbef KVM: PPC: Book3S HV: Make HPT resizing work on POWER9
  a8b48a4dccea KVM: PPC: Book3S HV: Fix trap number return from 
__kvmppc_vcore_entry

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=ff6781fd1bb404d8a551c02c35c70cec1da17ff1
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=e4b79900222b8cccd4da4a7a89581f0e1b764ed2
  and
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=a5d4b5891c2f1f865a2def1eb0030f534e77ff86

   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for sathe...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.

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

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


[Kernel-packages] [Bug 1748157] Re: [MIR] thunderbolt-tools

2018-03-27 Thread Yehezkel Bernat
Seth,
It was disabled as the project is now handled at freedesktop's GitLab.
I opened an issue there: 
https://github.com/intel/thunderbolt-software-user-space/issues/60

** Bug watch added: github.com/intel/thunderbolt-software-user-space/issues #60
   https://github.com/intel/thunderbolt-software-user-space/issues/60

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

Title:
   [MIR] thunderbolt-tools

Status in thunderbolt-tools package in Ubuntu:
  Confirmed

Bug description:
  == Overview ==

  Intel Thunderbolt userspace components provides components for using
  Intel Thunderbolt controllers with security level features.
  Thunderbolt™ technology is a transformational high-speed, dual
  protocol I/O that provides unmatched performance with up to 40Gbps bi-
  directional transfer speeds. It provides flexibility and simplicity by
  supporting both data (PCIe, USB3.1) and video (DisplayPort) on a
  single cable connection that can daisy-chain up to six devices.

  [ See https://github.com/intel/thunderbolt-software-user-space ]

  == Answers to UbuntuMainInclusionRequirements ==

  = Requirements =

  1. Availability
 Package is in universe: 
https://launchpad.net/ubuntu/+source/thunderbolt-tools

  2. Rationale
 Package a device enabler for users with Thunderbolt technology

  3. Security:
 No security issues exposed so far. However, the tools have only been in 
Ubuntu since
 2017-12-09, so this currently is less than the 90 days threshold.

  4. Quality assurance:
 * Manual is provided
 * No debconf questions higher than medium
 * No major outstanding bugs. I'm also helping Intel fix issues that I'm 
finding with
   static analysis tools such as scan-build, cppcheck and CoverityScan
   Bugs outstanding:
 #883857 please backport for stretch-backports
 #882525 thunderbolt-tools: FTBFS on kFreeBSD: 
_ZN5boost6system15system_categoryEv undefined
   - I can fix this, but it makes no sense to run on kFreeBSD
 * Exotic Hardware: Only Thunderbolt supported H/W is required, this is an 
industry standard
   and the support for the tools are in the 4.13+ kernels
 * No Test Suite shipped with the package
 * Does not rely on obsolete or demoted packages

  5. UI standards:
 * This is a CLI tool. Tool has normal CLI style short help and man pages
 * No desktop file required as it is a CLI tool.

  6. Binary Dependencies:
libboost-dev(main)
libboost-filesystem-dev (main)
libboost-program-options-dev(main)
udev(main)

  7. Standards compliance:
 lintian clean and meets the FHS + Debian Policy standards to the best of 
my knowledge

  8. Maintenance
 * Package owning team: The Ubuntu Kernel Team
 * Debian package maintained by Colin Ian King (myself from the Kernel Team)

  9. Background Information
 The user-space components implement device approval support:

 a. Easier interaction with the kernel module for approving connected 
devices.
 b. ACL for auto-approving devices white-listed by the user.

 Tools provided by this package:

  tbtacl - triggered by udev (see the udev rules in tbtacl.rules).
  It auto-approves devices that are found in ACL.

  tbtadm - user-facing CLI tool. It provides operations for device
  approval, handling the ACL and more.

  The user-space components operate in coordination with the
  upstream Thunderbolt kernel driver (found in v4.13) to provide the
  Thunderbolt functionalities. These components are NOT compatible with
  the old out-of-tree Thunderbolt kernel module.

  = Security checks =

http://cve.mitre.org/cve/cve.html: Search in the National Vulnerability 
Database using the package as a keyword
* No CVEs found

http://secunia.com/advisories/search/: search for the package as a keyword
* No security advisories found

Ubuntu CVE Tracker
  http://people.ubuntu.com/~ubuntu-security/cve/main.html
  * No
  http://people.ubuntu.com/~ubuntu-security/cve/universe.html
  * No
  http://people.ubuntu.com/~ubuntu-security/cve/partner.html
  * No

  Check for security relevant binaries. If any are present, this
  requires a more in-depth security review.

  Executables which have the suid or sgid bit set.
* Not applicable

  Executables in /sbin, /usr/sbin.
* None in these paths

  Packages which install daemons (/etc/init.d/*)
* No

  Packages which open privileged ports (ports < 1024).
* No

   Add-ons and plugins to security-sensitive software (filters,
   scanners, UI skins, etc)
* This does exec tbtacl from udev with new udev rules, so this
  needs security checking

To manage 

[Kernel-packages] [Bug 1746971] Re: Please enable PAGE_POISONING

2018-03-27 Thread Seth Forshee
The referenced blog post and Kconfig help text both mention a
performance impact. This will need to be evaluated before enabling. At
this late stage of the bionic cycle I think we'll have to defer this to
18.10 and consider SRU to 18.04 if the performance impact is deemed
acceptable.

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

Title:
  Please enable PAGE_POISONING

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

Bug description:
  Hi,

  page poising is currently disabled in Ubuntu kernels:

  $ grep PAGE_POISON /boot/config-4.13.0-32-generic
  # CONFIG_PAGE_POISONING is not set

  It is also disabled in mainline kernels:

  $ grep PAGE_POISON /boot/config-4.14.16-041416-generic
  # CONFIG_PAGE_POISONING is not set

  On the contrary, it is enabled in Debian stretch and buster/sid
  kernels:

  # grep PAGE_POISON /boot/config-*
  /boot/config-4.9.0-5-amd64:CONFIG_PAGE_POISONING=y
  /boot/config-4.9.0-5-amd64:CONFIG_PAGE_POISONING_NO_SANITY=y
  /boot/config-4.9.0-5-amd64:# CONFIG_PAGE_POISONING_ZERO is not set

  $ grep PAGE_POISON /boot/config-*
  /boot/config-4.14.0-3-amd64:CONFIG_PAGE_POISONING=y
  /boot/config-4.14.0-3-amd64:CONFIG_PAGE_POISONING_NO_SANITY=y
  /boot/config-4.14.0-3-amd64:# CONFIG_PAGE_POISONING_ZERO is not set

  It is an interesting kernel hardening feature, so could you please
  enable those options in Ubuntu and mainline kernels?

  Some background information is here:

https://outflux.net/blog/archives/2016/09/30/security-things-in-
  linux-v4-6/

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   3167 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Feb  2 09:47:37 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cf81afe7-8427-45fa-9149-c11d060a5a26
  MachineType: Dell Inc. Latitude E6520
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro vsyscall=none 
ecurity=apparmor enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=32M 
mtrr_chunk_size=128M quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0NVF5K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1755073] Re: ubuntu_zram_smoke test will cause soft lockup on Artful ThunderX ARM64

2018-03-27 Thread Thadeu Lima de Souza Cascardo
** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
 Assignee: Paolo Pisati (p-pisati)
   Status: Confirmed

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

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

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

Title:
  ubuntu_zram_smoke test will cause soft lockup on Artful ThunderX ARM64

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Artful:
  New
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==

  Enabling virtual mapped kernel stacks breaks the thunderx_zip driver.
  On compression or decompression the executing CPU hangs in an endless
  loop. The reason for this is the usage of __pa() by the driver that
  does not work for an address that is not part of the 1:1 mapping.

  == Fix ==

  The patch in comment #12 fixes it.
  To reproduce the bug (and test the new kernel), see comment #9.

  == Regression Potential ==

  The patch affects only the thunderx_zip driver (that is already in a
  completely broken state), so the regression potential is low.

  ---

  This is a POTENTIAL REGRESSION.

  This test has passed with 4.13.0-36.40, but not 4.13.0-37.42

  The test will stuck with error message in dmesg:
  ubuntu@starmie-kernel:~$ dmesg
  [  470.227210] zram: Added device: zram0
  [  472.262544] zram0: detected capacity change from 0 to 134217728
  [  472.396960] EXT4-fs (zram0): mounted filesystem with ordered data mode. 
Opts: (null)
  [  475.761947] zram0: detected capacity change from 134217728 to 0
  [  476.796641] zram0: detected capacity change from 0 to 134217728
  [  476.909118] EXT4-fs (zram0): mounted filesystem with ordered data mode. 
Opts: (null)
  [  480.233817] zram0: detected capacity change from 134217728 to 0
  [  481.239001] zram0: detected capacity change from 0 to 134217728
  [  508.079684] watchdog: BUG: soft lockup - CPU#8 stuck for 23s! 
[mkfs.ext4:2253]
  [  508.086994] Modules linked in: lz4 lz4_compress zram nls_iso8859_1 
thunderx_edac i2c_thunderx thunderx_zip i2c_smbus shpchp cavium_rng_vf 
cavium_rng gpio_keys ipmi_ssif uio_pdrv_genirq uio ipmi_devintf ipmi_msghandler 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear nicvf nicpf ast i2c_algo_bit ttm 
drm_kms_helper syscopyarea sysfillrect aes_ce_blk sysimgblt aes_ce_cipher 
fb_sys_fops crc32_ce crct10dif_ce drm ghash_ce sha2_ce sha1_ce ahci libahci 
thunder_bgx thunder_xcv mdio_thunder thunderx_mmc mdio_cavium aes_neon_bs 
aes_neon_blk crypto_simd cryptd
  [  508.087138] CPU: 8 PID: 2253 Comm: mkfs.ext4 Not tainted 4.13.0-37-generic 
#42-Ubuntu
  [  508.087141] Hardware name: Cavium ThunderX CRB/To be filled by O.E.M., 
BIOS 5.11 12/12/2012
  [  508.087144] task: 801f57a86900 task.stack: 23ec
  [  508.087158] PC is at zip_deflate+0x184/0x2e8 [thunderx_zip]
  [  508.087164] LR is at zip_deflate+0x17c/0x2e8 [thunderx_zip]
  [  508.087167] pc : [] lr : [] pstate: 
20400145
  [  508.087169] sp : 23ec3580
  [  508.087171] x29: 23ec3580 x28: 
  [  508.087177] x27: 801f57a86900 x26: 0001b104
  [  508.087182] x25: 801f5618c000 x24: 801f6a15bc18
  [  508.087188] x23: 1000 x22: 23ec3688
  [  508.087193] x21: 801f5a2d4880 x20: 801f6a15bc18
  [  508.087199] x19: 23ec3608 x18: 
  [  508.087204] x17: 0001 x16: 
  [  508.087209] x15: bd4048db x14: fa13
  [  508.087215] x13: 1000 x12: fa12
  [  508.087220] x11:  x10: 
  [  508.087225] x9 :  x8 : 
  [  508.087230] x7 :  x6 : 8000101d6080
  [  508.087236] x5 : 01a69058 x4 : 0008
  [  508.087241] x3 :  x2 : 
  [  508.087246] x1 : 801f6a15be08 x0 : 
  [  508.087252] Call trace:
  [  508.087256] Exception stack(0x23ec3440 to 0x23ec3580)
  [  508.087260] 3440:  801f6a15be08  

  [  508.087264] 3460: 0008 01a69058 8000101d6080 

  [  508.087268] 3480:    

  [  508.087272] 34a0: fa12 1000 fa13 
bd4048db
  [  508.087276] 34c0:  0001  
23ec3608
  [  508.087280] 34e0: 801f6a15bc18 801f5a2d4880 23ec3688 
1000
  [  508.087284] 3500: 

[Kernel-packages] [Bug 1758910] Re: Important Kernel fixes to be backported for Power9 (kvm)

2018-03-27 Thread Seth Forshee
** Changed in: linux (Ubuntu Bionic)
   Status: Triaged => In Progress

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

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

Title:
  Important Kernel fixes to be backported for Power9 (kvm)

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

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-03-26 
02:18:44 ==
  ---Problem Description---
  Important Kernel fixes to be backported for Power9 (kvm)
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-13-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Following upstream patches are need to be backported for Power9 KVM to 
function well.

  * Emulation of VMX loads and stores for MMIO.
   
  09f984961c13 KVM: PPC: Book3S: Add MMIO emulation for VMX instructions
  6df3877fc962 KVM: PPC: Book3S: Fix compile error that occurs with some gcc 
versions (needed once 09f984961c13 is in)
   
  * Other important fixes.
   
  05f2bb0313a2 KVM: PPC: Book3S HV: Fix handling of secondary HPTEG in HPT 
resizing code
  790a9df5fbef KVM: PPC: Book3S HV: Make HPT resizing work on POWER9
  a8b48a4dccea KVM: PPC: Book3S HV: Fix trap number return from 
__kvmppc_vcore_entry

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=ff6781fd1bb404d8a551c02c35c70cec1da17ff1
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=e4b79900222b8cccd4da4a7a89581f0e1b764ed2
  and
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=a5d4b5891c2f1f865a2def1eb0030f534e77ff86

   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for sathe...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.

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

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


[Kernel-packages] [Bug 159356] Re: System freeze on high memory usage

2018-03-27 Thread Alekk
Very annoying. Successfully preventing from using Linux as reliable
system.

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

Title:
  System freeze on high memory usage

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  New

Bug description:
  I run a batch matlab job server here at my lab, running Dapper 6.06 (for the 
LTS). One of the users has submitted a very memory-consuming job, which 
successfully crashes the server. Upon closer inspection, the crash happens like 
this:
  1. I run matlab with the given file (as an ordinary, unpriveleged user)
  2. RAM usage quickly fills up
  3. Once the RAM meter hits 100%, the system freezes: All SSH connections 
freeze up, and while switching VTs directly on the machine works, no new 
processes run - so one can't log in, or do anything if he is logged in. 
(Sometimes typing doesn't work at all)

  Note that the swap - while 7 gigs of it are available - is never used.
  (The machine has 7 gigs of RAM as well)

  I've tried the same on my Gutsy 32-bit box, and there was no system
  freezeup - matlab simply notified that the system was out of memory.
  However, it did this once memory was 100% in use - and still, swap
  didn't get used at all! (Though it is mounted correctly and shows up
  in "top" and "free").

  So first thing's first - I'd like to eliminate the crash issue. I
  suppose I could switch the server to 32-bit, but I think that would be
  a performance loss, considering that it does a lot of heavy
  computation. There is no reason, however, that this should happen on a
  64-bit machine anyway. Why does it?

  WORKAROUND: Enabling DMA in the BIOS

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

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


[Kernel-packages] [Bug 1755161] Re: Update to ocxl driver

2018-03-27 Thread Seth Forshee
** Changed in: linux (Ubuntu Bionic)
   Status: Triaged => In Progress

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

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

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

Title:
  Update to ocxl driver

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

Bug description:
  == Comment: #2 - Frederic Barrat  - 2018-03-12 
02:54:38 ==
  Here are 3 small updates to the ocxl driver, to add on top of the feature LP 
1746988

  dedab7f0d313 ocxl: fix signed comparison with less than zero
  423688abd9ab ocxl: Fix potential bad errno on irq allocation
  07c5ccd70ad7 ocxl: Add get_metadata IOCTL to share OCXL information to 
userspace

  Can they be added to be available in Ubuntu 18.04?
  Thanks!

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

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


[Kernel-packages] [Bug 1752672] Re: CAPI Flash (cxlflash) update

2018-03-27 Thread Seth Forshee
** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
  CAPI Flash (cxlflash) update

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

Bug description:
  This is a feature for capi flash (cxlflash) inside the kernel.

  We have upstreamed the below 38 patches but they are not in the
  maintainers tree yet. I anticipate them to be available by Friday this
  week. I dont want to miss the boat for 18.04 feature code cutoff. Can
  you please suggest if I should submit these patches as SAUCE patches
  or can it be pulled from mainstream once maintainer pulls it in ?

  8d34234b7e44caa489bb7e684ead1f13b74faf72 cxlflash: Preserve number of 
interrupts for master contexts
  8f20948fde0a06a283b39c3646c8060b62319875 cxlflash: Avoid clobbering context 
control register value
  44569c367471bd57916798a701ad1c7250ec93fb cxlflash: Add argument identifier 
names
  9e63cdb74178a02fa76c3896c2e38479148e60bf cxlflash: Introduce OCXL backend
  0aa60ffb7ca4ce3f5cb33231d9358ab9f0ae9ec4 cxlflash: Hardware AFU for OCXL
  f9e6817464036867a6994732c3b8b873b6fdc530 cxlflash: Read host function 
configuration
  f1718592638ef1e3486ded07ba9aebf784b03db3 cxlflash: Setup function acTag range
  77ece8688ed48e693bbdfef7b856ed146dac5838 cxlflash: Read host AFU configuration
  6491b3338076c8a71f70c326aeacf7ecde139124 cxlflash: Setup AFU acTag range
  90fbea09364d3a32b6b2b0fbbd56c4fbaabe5400 cxlflash: Setup AFU PASID
  16e8be014d2efa0f7e713d5e7cfae9348eaab6fd cxlflash: Adapter context support 
for OCXL
  2d431a892b91f9f004a8b6413d990c55dac6ac16 cxlflash: Use IDR to manage adapter 
contexts
  d0dd47f71da4a9f37cfd2eced36f85c2751fcdf5 cxlflash: Support adapter file 
descriptors for OCXL
  1719110f42503bcac6962daf4492cec3c16c325f cxlflash: Support adapter context 
discovery
  e9ff19884da98139427e23c8ce3bed7614427fed cxlflash: Support image reload 
policy modification
  5706f2a40306b2fe5ffae6fa1eacc81afed3fa11 cxlflash: MMIO map the AFU
  99b7d36979c67708851f8058c9fb6e412d32577b cxlflash: Support starting an 
adapter context
  d8e72cf527fed71641dd011dff13fbd1e5fad2da cxlflash: Support process specific 
mappings
  8cc796025b082c13c1ec3db620e9f23f6082726a cxlflash: Support AFU state toggling
  9e0d9716935bdf9e2c24d3c27ae8be1756eff46e cxlflash: Support reading adapter 
VPD data
  b37e0fdd868e47221e706be4d51c66e5e9224f20 cxlflash: Setup function OCXL link
  099858c80b956752693e0d3bb8f01618a11d48dc cxlflash: Setup OCXL transaction 
layer
  5b1a1f3d49ee4b41778e41bf8147febc885df381 cxlflash: Support process element 
lifecycle
  0e3e9fbfada4506620610497cdc6ce0a0b3cdff2 cxlflash: Support AFU interrupt 
management
  ff7388a91f3739c5420b16f20d74644f5da9b03a cxlflash: Support AFU interrupt 
mapping and registration
  cfa71c77fd9e440b1d8f105151eaf30aff5f3241 cxlflash: Support starting user 
contexts
  270a401d0901eeb736b1da4fd728006ae4d40145 cxlflash: Support adapter context 
polling
  302ce17cba275e295803a2a2aad83debfd02cf5d cxlflash: Support adapter context 
reading
  cc8640bac30541ddc453834d5956ced223ed0020 cxlflash: Support adapter context 
mmap and release
  a071c05a8cab915a3a7d11a87b06da00bc5bc7d5 cxlflash: Support file descriptor 
mapping
  eb01b23138c73967c17c04e79ab4c5df4649984e cxlflash: Introduce object handle fop
  c6a2e3b15bd5a6f85472eac54fede0cffcd6d4e5 cxlflash: Setup LISNs for user 
contexts
  bbfdb7e4d852d213b3b474185918a94aabecad7f cxlflash: Setup LISNs for master 
contexts
  e8d361505cef408ec3afb5f0cf1e4c3fd7f6150b cxlflash: Update synchronous 
interrupt status bits
  dc8e5211cbd6457f618bc49df7e769895b6996bc cxlflash: Introduce OCXL context 
state machine
  9c5567f5e9c92a9f94f7790b2dd905235bc9842c cxlflash: Register for translation 
errors
  96cacd8347f27d258bae75d796cc1f523724a37a cxlflash: Support AFU reset
  966a6e64ddd9624999d895fffab190c7d2f96c85 cxlflash: Enable OCXL operations

  <<< The above is from my local git tree but it has been already sent
  to linux-scsi mailing list >>>

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

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


[Kernel-packages] [Bug 1752672] Re: CAPI Flash (cxlflash) update

2018-03-27 Thread Seth Forshee
** Changed in: linux (Ubuntu Bionic)
   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/1752672

Title:
  CAPI Flash (cxlflash) update

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  This is a feature for capi flash (cxlflash) inside the kernel.

  We have upstreamed the below 38 patches but they are not in the
  maintainers tree yet. I anticipate them to be available by Friday this
  week. I dont want to miss the boat for 18.04 feature code cutoff. Can
  you please suggest if I should submit these patches as SAUCE patches
  or can it be pulled from mainstream once maintainer pulls it in ?

  8d34234b7e44caa489bb7e684ead1f13b74faf72 cxlflash: Preserve number of 
interrupts for master contexts
  8f20948fde0a06a283b39c3646c8060b62319875 cxlflash: Avoid clobbering context 
control register value
  44569c367471bd57916798a701ad1c7250ec93fb cxlflash: Add argument identifier 
names
  9e63cdb74178a02fa76c3896c2e38479148e60bf cxlflash: Introduce OCXL backend
  0aa60ffb7ca4ce3f5cb33231d9358ab9f0ae9ec4 cxlflash: Hardware AFU for OCXL
  f9e6817464036867a6994732c3b8b873b6fdc530 cxlflash: Read host function 
configuration
  f1718592638ef1e3486ded07ba9aebf784b03db3 cxlflash: Setup function acTag range
  77ece8688ed48e693bbdfef7b856ed146dac5838 cxlflash: Read host AFU configuration
  6491b3338076c8a71f70c326aeacf7ecde139124 cxlflash: Setup AFU acTag range
  90fbea09364d3a32b6b2b0fbbd56c4fbaabe5400 cxlflash: Setup AFU PASID
  16e8be014d2efa0f7e713d5e7cfae9348eaab6fd cxlflash: Adapter context support 
for OCXL
  2d431a892b91f9f004a8b6413d990c55dac6ac16 cxlflash: Use IDR to manage adapter 
contexts
  d0dd47f71da4a9f37cfd2eced36f85c2751fcdf5 cxlflash: Support adapter file 
descriptors for OCXL
  1719110f42503bcac6962daf4492cec3c16c325f cxlflash: Support adapter context 
discovery
  e9ff19884da98139427e23c8ce3bed7614427fed cxlflash: Support image reload 
policy modification
  5706f2a40306b2fe5ffae6fa1eacc81afed3fa11 cxlflash: MMIO map the AFU
  99b7d36979c67708851f8058c9fb6e412d32577b cxlflash: Support starting an 
adapter context
  d8e72cf527fed71641dd011dff13fbd1e5fad2da cxlflash: Support process specific 
mappings
  8cc796025b082c13c1ec3db620e9f23f6082726a cxlflash: Support AFU state toggling
  9e0d9716935bdf9e2c24d3c27ae8be1756eff46e cxlflash: Support reading adapter 
VPD data
  b37e0fdd868e47221e706be4d51c66e5e9224f20 cxlflash: Setup function OCXL link
  099858c80b956752693e0d3bb8f01618a11d48dc cxlflash: Setup OCXL transaction 
layer
  5b1a1f3d49ee4b41778e41bf8147febc885df381 cxlflash: Support process element 
lifecycle
  0e3e9fbfada4506620610497cdc6ce0a0b3cdff2 cxlflash: Support AFU interrupt 
management
  ff7388a91f3739c5420b16f20d74644f5da9b03a cxlflash: Support AFU interrupt 
mapping and registration
  cfa71c77fd9e440b1d8f105151eaf30aff5f3241 cxlflash: Support starting user 
contexts
  270a401d0901eeb736b1da4fd728006ae4d40145 cxlflash: Support adapter context 
polling
  302ce17cba275e295803a2a2aad83debfd02cf5d cxlflash: Support adapter context 
reading
  cc8640bac30541ddc453834d5956ced223ed0020 cxlflash: Support adapter context 
mmap and release
  a071c05a8cab915a3a7d11a87b06da00bc5bc7d5 cxlflash: Support file descriptor 
mapping
  eb01b23138c73967c17c04e79ab4c5df4649984e cxlflash: Introduce object handle fop
  c6a2e3b15bd5a6f85472eac54fede0cffcd6d4e5 cxlflash: Setup LISNs for user 
contexts
  bbfdb7e4d852d213b3b474185918a94aabecad7f cxlflash: Setup LISNs for master 
contexts
  e8d361505cef408ec3afb5f0cf1e4c3fd7f6150b cxlflash: Update synchronous 
interrupt status bits
  dc8e5211cbd6457f618bc49df7e769895b6996bc cxlflash: Introduce OCXL context 
state machine
  9c5567f5e9c92a9f94f7790b2dd905235bc9842c cxlflash: Register for translation 
errors
  96cacd8347f27d258bae75d796cc1f523724a37a cxlflash: Support AFU reset
  966a6e64ddd9624999d895fffab190c7d2f96c85 cxlflash: Enable OCXL operations

  <<< The above is from my local git tree but it has been already sent
  to linux-scsi mailing list >>>

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

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


[Kernel-packages] [Bug 1758205] Re: Ubuntu 18.04 NVMe disks are not displayed on lsblk and /dev/disk/by-path (NVMe / Bolt ) (systemd?)

2018-03-27 Thread Joseph Salisbury
I built a test kernel with commit 8a30ecc6e0ecbb9ae95daf499b2680b885ed0349.  
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1758205

Can you test this kernel and see if it resolves this bug?

Note, to test this kernel, you need to install both the linux-image and
linux-image-extra .deb packages.

Thanks in advance!

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

Title:
  Ubuntu 18.04 NVMe disks are not displayed on lsblk and /dev/disk/by-
  path (NVMe / Bolt ) (systemd?)

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  ---Problem Description---

  Bolt based NVMe disks (namespaces) are not displayed on lsblk and 
/dev/disk/by-path
  # nvme list 
  Node SN   Model   
 Namespace Usage  Format   FW Rev  
    
 - -- 
 
  /dev/nvme0n1 S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 1  28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n10S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 10 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n11S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 11 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n12S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 12 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n13S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 13 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n14S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 14 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n15S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 15 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n16S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 16 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n17S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 17 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n18S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 18 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n19S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 19 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n2 S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 2  28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n20S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 20 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n21S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 21 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n22S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 22 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n23S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 23 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n24S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 24 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n25S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 25 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n26S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 26 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n27S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 27 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n28S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 28 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n29S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 29 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n3 S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 3  28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n30S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 30 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n31S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 31 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n32S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 32 28.67  GB /  28.67  GB  4 KiB +  0 B   

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

2018-03-27 Thread Ubuntu Kernel Bot
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/1759342

Title:
  BUG: Bad rss-counter state mm:3cebd506 idx:0 val:75

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Crash happened after booting the system

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bertadmin   1745 F pulseaudio
  Date: Sat Mar 24 11:42:05 2018
  Failure: oops
  InstallationDate: Installed on 2018-03-11 (16 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=22835ac6-a7b5-4601-bd4b-a6c98e4df3fb ro quiet splash zwap.enabled=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: BUG: Bad rss-counter state mm:3cebd506 idx:0 val:75
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


[Kernel-packages] [Bug 1759342] [NEW] BUG: Bad rss-counter state mm:000000003cebd506 idx:0 val:75

2018-03-27 Thread BertN45
Public bug reported:

Crash happened after booting the system

ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-12-generic 4.15.0-12.13
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bertadmin   1745 F pulseaudio
Date: Sat Mar 24 11:42:05 2018
Failure: oops
InstallationDate: Installed on 2018-03-11 (16 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
IwConfig:
 lono wireless extensions.
 
 enp0s3no wireless extensions.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: innotek GmbH VirtualBox
ProcFB: 0 vboxdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=22835ac6-a7b5-4601-bd4b-a6c98e4df3fb ro quiet splash zwap.enabled=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
RfKill:
 
SourcePackage: linux
Title: BUG: Bad rss-counter state mm:3cebd506 idx:0 val:75
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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


** Tags: amd64 apport-kerneloops bionic kernel-oops

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

Title:
  BUG: Bad rss-counter state mm:3cebd506 idx:0 val:75

Status in linux package in Ubuntu:
  New

Bug description:
  Crash happened after booting the system

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bertadmin   1745 F pulseaudio
  Date: Sat Mar 24 11:42:05 2018
  Failure: oops
  InstallationDate: Installed on 2018-03-11 (16 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=22835ac6-a7b5-4601-bd4b-a6c98e4df3fb ro quiet splash zwap.enabled=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: BUG: Bad rss-counter state mm:3cebd506 idx:0 val:75
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


[Kernel-packages] [Bug 1755470] Re: [P9, Power NV][Witherspoon][Ubuntu 18.04][Perf] : PMU events by name it is not listed under perf list

2018-03-27 Thread Frank Heimes
** Changed in: ubuntu-power-systems
   Status: Triaged => 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/1755470

Title:
  [P9,Power NV][Witherspoon][Ubuntu 18.04][Perf] : PMU events by name it
  is not listed under perf list

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

Bug description:
  == Comment: #0 - Shriya R. Kulkarni  - 2018-01-03 
04:50:13 ==
  Problem Description :
  =

  PMU events by name is not listed under perf  list on Witherspoon
  Machine.

  root@ltc-wspoon12:~# perf list | grep pm_
power:dev_pm_qos_add_request   [Tracepoint event]
power:dev_pm_qos_remove_request[Tracepoint event]
power:dev_pm_qos_update_request[Tracepoint event]
power:device_pm_callback_end   [Tracepoint event]
power:device_pm_callback_start [Tracepoint event]
power:pm_qos_add_request   [Tracepoint eve

  Hardware details :
  ==
  uname -a : Linux ltc-wspoon12 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 
10:03:08 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Machine : Witherspoon + DD2.0 + Power NV
  FW : OP9_v1.19_1.94
  OS : Ubuntu 18.04

  root@ltc-wspoon12:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="18.04 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu Bionic Beaver (development branch)"
  VERSION_ID="18.04"

  == Comment: #14 - Gustavo Luiz Ferreira Walbon  - 
2018-03-08 07:58:19 ==
  To set up the perf to list all PMU events for P9.

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

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


[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0

2018-03-27 Thread Luca
I too like Thorsten have a Ryzen workstation, and incidentally the same
network chipset but a different motherboard (asrock ab350m pro4)

1f:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller

I think this error message is generic and different type of problems
hides behind it, in my case every once in a while my PC slowly freeze,
before freezing I see the AER error, after I have seen a lot of them it
freeze.

adding "pcie_aspm=off" makes the error messages disappear and it freeze
silently or it shows "r8169:rtl_counters_cond == 1" before freezing.

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

Title:
  AER: Corrected error received: id=00e0

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Triaged

Bug description:
  Note: Current workaround is to add pci=noaer to your kernel command
  line:

  1) edit /etc/default/grub and and add pci=noaer to the line starting with 
GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: 
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
  2) run "sudo update-grub"
  3) reboot

  

  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
   /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.153
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1730770] Re: [Feature][CFL] Enable pmc_core driver for H, S, and U SKUs

2018-03-27 Thread Thadeu Lima de Souza Cascardo
** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
  [Feature][CFL] Enable pmc_core driver for H, S, and U SKUs

Status in intel:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Description:

  Need to enable pmc_core driver for Coffee Lake so we can get at the
  slp_s0# counter, which measures S0ix residency.

  Target Kernel:4.16
  Target Release: 18.04

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

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


[Kernel-packages] [Bug 1746019] Re: [Artful SRU] Fix capsule update regression

2018-03-27 Thread Manoj Iyer
-- Stock 17.10 kernel --

ubuntu@awrep06:~$ uname -a 
Linux awrep06 4.13.0-37-generic #42-Ubuntu SMP Wed Mar 7 14:13:33 UTC 2018 
aarch64 aarch64 aarch64 GNU/Linux
ubuntu@awrep06:~$ sudo modprobe capsule-loader
ubuntu@awrep06:~$ sudo su
root@awrep06:/home/ubuntu# cat 0ACJA530.CAP > /dev/efi_capsule_loader
cat: write error: Invalid 
root@awrep06:/home/ubuntu#

-- Proposed kernel --

ubuntu@awrep06:~$ apt policy linux-image-generic
linux-image-generic:
  Installed: 4.13.0.37.40
  Candidate: 4.13.0.38.41
  Version table:
 4.13.0.38.41 500
500 http://ports.ubuntu.com/ubuntu-ports artful-proposed/main arm64 
Packages
 *** 4.13.0.37.40 500
500 http://ports.ubuntu.com/ubuntu-ports artful-updates/main arm64 
Packages
500 http://ports.ubuntu.com/ubuntu-ports artful-security/main arm64 
Packages
100 /var/lib/dpkg/status
 4.13.0.16.17 500
500 http://ports.ubuntu.com/ubuntu-ports artful/main arm64 Packages

ubuntu@awrep06:~$ uname -a 
Linux awrep06 4.13.0-38-generic #43-Ubuntu SMP Wed Mar 14 15:22:25 UTC 2018 
aarch64 aarch64 aarch64 GNU/Linux
ubuntu@awrep06:~$ sudo modprobe capsule-loader
ubuntu@awrep06:~$ sudo su
root@awrep06:/home/ubuntu# cat 0ACJA530.CAP  > /dev/efi_capsule_loader
root@awrep06:/home/ubuntu# tail -n5 /var/log/kern.log 
Mar 27 17:23:48 awrep06 kernel: [   19.439681] qcom-emac QCOM8070:00 
enaqcom8070i0: Link is Down
Mar 27 17:23:48 awrep06 kernel: [   22.511124] qcom-emac QCOM8070:00 
enaqcom8070i0: Link is Up - 1Gbps/Full - flow control rx/tx
Mar 27 17:23:48 awrep06 kernel: [   22.511132] IPv6: ADDRCONF(NETDEV_CHANGE): 
enaqcom8070i0: link becomes ready
Mar 27 17:23:48 awrep06 kernel: [   46.136253] new mount options do not match 
the existing superblock, will be ignored
Mar 27 17:24:59 awrep06 kernel: [  116.552854] efi: Successfully upload capsule 
file with reboot type 'RESET_COLD'
root@awrep06:/home/ubuntu# 

NOTICE:  BL31: v1.3(release):STB_TZ.DF.2.0.R1__00935-2-g4917d82
NOTICE:_override variabNOTICE:  * IMC-TZ SYNC POINT REACHED *
INFO:TPM NOT IDENTIFIED
INFO:TPM VID : 0x DID : 0x
INFO:QUP version 2.5.1
ERROR:   CRB Driver Init Failed with error=4100 
ERROR:   TPM APP failed to initialize 
NOTICE:  BL31: Preparing for EL3 exit to normal world
DEBUG Mode : Off
Progress: [5F]
FW Family  : Qualcomm Centriq(TM) 2400
FW Version : XBL.DF.2.0.R1-00868 QDF2400_REL CRM
Build Info : 64b Feb 23 2018 15:37:40
Boot Mode  : Flash update

Version 2.19.1269. Copyright (C) 2018 American Megatrends, Inc. 
BIOS Date: 03/06/2018 13:04:36 Ver: 0ACJA530
EVALUATION COPY.
Press  or  to enter setup.


ubuntu@awrep06:~$ uname -a 
Linux awrep06 4.13.0-38-generic #43-Ubuntu SMP Wed Mar 14 15:22:25 UTC 2018 
aarch64 aarch64 aarch64 GNU/Linux
ubuntu@awrep06:~$ 

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

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

Title:
  [Artful SRU] Fix capsule update regression

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Artful:
  Fix Committed

Bug description:
  [IMPACT]
  Commit 82c3768b8d68 ("efi/capsule-loader: Use a cached copy of the
  capsule header") refactored the capsule loading code that maps the
  capsule header, to avoid having to map it several times. However,
  as it turns out, the vmap() call we ended up removing did not just
  map the header, but the entire capsule image, and dropping this
  virtual mapping breaks capsules that are processed by the firmware
  immediately (i.e., without a reboot).

  [FIX]
  The following patch fixes the issue
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/firmware/efi/capsule-loader.c?id=f24c4d478013d82bd1b943df566fff3561d52864

  [TEST]
  Please see comments below for testing information and details.

  [REGRESSION POTENTIAL]
  This patch fixes a regression in 4.13 and onward.

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

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


[Kernel-packages] [Bug 1755979] Re: Cpu utilization showing system time for kvm guests (performance) (sysstat)

2018-03-27 Thread Thadeu Lima de Souza Cascardo
** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
  Cpu utilization showing system time for kvm guests (performance)
  (sysstat)

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  All KVM guest cpu utilization is being reported as sys% time in the host.
  It turns out Guest time accounting (CONFIG_VIRT_CPU_ACCOUNTING_GEN) has
  been broken since v4.13 by commit 8b24e69fc47e436.

  Commit 61bd0f66ff92 fixes this bug and is included in mainline as of 
v4.16-rc5.
  The commit was cc'd to upstream stable, but has not yet landed in upstream 
4.15.

  == Fix ==
  61bd0f66ff92 ("KVM: PPC: Book3S HV: Fix guest time accounting with 
VIRT_CPU_ACCOUNTING_GEN")

  == Regression Potential ==
  Low.  Also cc'd to stable, so it has had additionl upstream review.  Limited 
to powerpc.

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


  == Comment: #0 - JENIFER HOPPER  - 2018-03-14 16:20:47 ==
  +++ This bug was initially created as a clone of Bug #163375 +++

  ---Problem Description---
  All KVM guest cpu utilization is being reported as sys% time in the host.
  It turns out Guest time accounting (CONFIG_VIRT_CPU_ACCOUNTING_GEN) has been 
broken since v4.13 by commit:

  commit 8b24e69fc47e43679bb29ddb481aa0e8dce2a3c5
  Author: Paul Mackerras 
  Date:   Mon Jun 26 15:45:51 2017 +1000

  KVM: PPC: Book3S HV: Close race with testing for signals on guest
  entry

  ---

  That is now fixed and upstream accepted in Paulus' tree as git commit:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-fixes=61bd0f66ff92d5ce765ff9850fd3cbfec773c560
  ("KVM: PPC: Book3S HV: Fix guest time accounting with 
VIRT_CPU_ACCOUNTING_GEN")

  Please include this patch in Ubuntu so that guest cpu accounting is
  correct.

  Contact Information = jhop...@us.ibm.com

  ---uname output---
  Linux ltc-b114 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:21:52 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 5104-22C

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   Start a KVM guest, run something that generates cpu utilization in the 
guest, observe mpstat on the host.

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

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


[Kernel-packages] [Bug 1736393] Re: [Artful][Wyse 3040] System hang when trying to enable an offlined CPU core

2018-03-27 Thread Thadeu Lima de Souza Cascardo
** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
 Assignee: Jesse Sung (wenchien)
   Status: Fix Released

** Also affects: linux-oem (Ubuntu Bionic)
   Importance: Undecided
   Status: Invalid

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

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

Title:
  [Artful][Wyse 3040] System hang when trying to enable an offlined CPU
  core

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Committed
Status in linux-oem source package in Artful:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Invalid

Bug description:
  1. disable cpu[1-3] $ echo 0 > /sys/devices/system/cpu/cpu[1-3]/online
  2. enable cpu[1-3] $ echo 1 > /sys/devices/system/cpu/cpu[1-3]/online

  System will hang on step 2.

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

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


[Kernel-packages] [Bug 1739522] Re: [Bug] ISH support for CFL-H

2018-03-27 Thread Thadeu Lima de Souza Cascardo
** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
  [Bug] ISH support for CFL-H

Status in intel:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Description

  ISH driver is not loaded on CFL-H.

  
  Target Kernel: 4.16
  Target Release: 18.04

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

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


[Kernel-packages] [Bug 1757164] Re: linux: 4.15.0-13.14 -proposed tracker

2018-03-27 Thread Dimitri John Ledkov
** Changed in: linux (Ubuntu Bionic)
   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/1757164

Title:
  linux: 4.15.0-13.14 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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-release series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in debian-installer source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

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

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

  backports: bug 1757173 (linux-hwe-edge)
  derivatives: bug 1757165 (linux-raspi2), bug 1757166 (linux-aws), bug 1757167 
(linux-azure), bug 1757168 (linux-gcp), bug 1757169 (linux-kvm)
  -- swm properties --
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1755470] Re: [P9, Power NV][Witherspoon][Ubuntu 18.04][Perf] : PMU events by name it is not listed under perf list

2018-03-27 Thread Thadeu Lima de Souza Cascardo
** Changed in: linux (Ubuntu Bionic)
   Status: Triaged => 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/1755470

Title:
  [P9,Power NV][Witherspoon][Ubuntu 18.04][Perf] : PMU events by name it
  is not listed under perf list

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

Bug description:
  == Comment: #0 - Shriya R. Kulkarni  - 2018-01-03 
04:50:13 ==
  Problem Description :
  =

  PMU events by name is not listed under perf  list on Witherspoon
  Machine.

  root@ltc-wspoon12:~# perf list | grep pm_
power:dev_pm_qos_add_request   [Tracepoint event]
power:dev_pm_qos_remove_request[Tracepoint event]
power:dev_pm_qos_update_request[Tracepoint event]
power:device_pm_callback_end   [Tracepoint event]
power:device_pm_callback_start [Tracepoint event]
power:pm_qos_add_request   [Tracepoint eve

  Hardware details :
  ==
  uname -a : Linux ltc-wspoon12 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 
10:03:08 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Machine : Witherspoon + DD2.0 + Power NV
  FW : OP9_v1.19_1.94
  OS : Ubuntu 18.04

  root@ltc-wspoon12:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="18.04 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu Bionic Beaver (development branch)"
  VERSION_ID="18.04"

  == Comment: #14 - Gustavo Luiz Ferreira Walbon  - 
2018-03-08 07:58:19 ==
  To set up the perf to list all PMU events for P9.

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

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


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

2018-03-27 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

** Tags added: bionic

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

Title:
  kernel BUG at /build/linux-bdpCf2/linux-4.15.0/mm/slub.c:296!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  dont know it just gave me the error messege

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 966 F pulseaudio
techterror12   1382 F pulseaudio
   /dev/snd/controlC1:  gdm 966 F pulseaudio
techterror12   1382 F pulseaudio
  Date: Tue Mar 27 12:22:22 2018
  Failure: oops
  HibernationDevice: RESUME=UUID=b83a3832-8bd2-46ee-b79e-9bb804e1613d
  InstallationDate: Installed on 2018-02-25 (29 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305FA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi= acpi_backight_native 
vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: kernel BUG at /build/linux-bdpCf2/linux-4.15.0/mm/slub.c:296!
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305FA.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305FA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX305FA.208:bd03/26/2015:svnASUSTeKCOMPUTERINC.:pnUX305FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX305FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1759330] [NEW] kernel BUG at /build/linux-bdpCf2/linux-4.15.0/mm/slub.c:296!

2018-03-27 Thread Ben Nixon
Public bug reported:

dont know it just gave me the error messege

ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-13-generic 4.15.0-13.14
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.9-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm 966 F pulseaudio
  techterror12   1382 F pulseaudio
 /dev/snd/controlC1:  gdm 966 F pulseaudio
  techterror12   1382 F pulseaudio
Date: Tue Mar 27 12:22:22 2018
Failure: oops
HibernationDevice: RESUME=UUID=b83a3832-8bd2-46ee-b79e-9bb804e1613d
InstallationDate: Installed on 2018-02-25 (29 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
 Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX305FA
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi= acpi_backight_native 
vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
SourcePackage: linux
Title: kernel BUG at /build/linux-bdpCf2/linux-4.15.0/mm/slub.c:296!
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/26/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX305FA.208
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX305FA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX305FA.208:bd03/26/2015:svnASUSTeKCOMPUTERINC.:pnUX305FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: UX
dmi.product.name: UX305FA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-kerneloops bionic kernel-oops

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

Title:
  kernel BUG at /build/linux-bdpCf2/linux-4.15.0/mm/slub.c:296!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  dont know it just gave me the error messege

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 966 F pulseaudio
techterror12   1382 F pulseaudio
   /dev/snd/controlC1:  gdm 966 F pulseaudio
techterror12   1382 F pulseaudio
  Date: Tue Mar 27 12:22:22 2018
  Failure: oops
  HibernationDevice: RESUME=UUID=b83a3832-8bd2-46ee-b79e-9bb804e1613d
  InstallationDate: Installed on 2018-02-25 (29 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305FA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi= acpi_backight_native 
vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: kernel BUG at /build/linux-bdpCf2/linux-4.15.0/mm/slub.c:296!
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305FA.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305FA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 

[Kernel-packages] [Bug 1758205] Re: Ubuntu 18.04 NVMe disks are not displayed on lsblk and /dev/disk/by-path (NVMe / Bolt ) (systemd?)

2018-03-27 Thread Frank Heimes
** Changed in: ubuntu-power-systems
   Status: Triaged => 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/1758205

Title:
  Ubuntu 18.04 NVMe disks are not displayed on lsblk and /dev/disk/by-
  path (NVMe / Bolt ) (systemd?)

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  ---Problem Description---

  Bolt based NVMe disks (namespaces) are not displayed on lsblk and 
/dev/disk/by-path
  # nvme list 
  Node SN   Model   
 Namespace Usage  Format   FW Rev  
    
 - -- 
 
  /dev/nvme0n1 S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 1  28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n10S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 10 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n11S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 11 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n12S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 12 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n13S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 13 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n14S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 14 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n15S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 15 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n16S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 16 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n17S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 17 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n18S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 18 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n19S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 19 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n2 S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 2  28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n20S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 20 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n21S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 21 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n22S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 22 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n23S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 23 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n24S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 24 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n25S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 25 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n26S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 26 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n27S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 27 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n28S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 28 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n29S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 29 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n3 S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 3  28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n30S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 30 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n31S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 31 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n32S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 32 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n4 S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 4  28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n5 S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 5  28.67  GB /  28.67  GB  4 KiB + 

[Kernel-packages] [Bug 1759312] Re: AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu 17.10

2018-03-27 Thread Frank Heimes
** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
   Importance: Undecided => Medium

** Changed in: ubuntu-power-systems
   Status: New => Triaged

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

** Tags added: triage-g

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

Title:
  AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu
  17.10

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu 17.10
   
  ---Additional Hardware Info---
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  176
  On-line CPU(s) list: 0-175
  Thread(s) per core:  4
  Core(s) per socket:  22
  Socket(s):   2
  NUMA node(s):8
  Model:   2.2 (pvr 004e 1202)
  Model name:  POWER9, altivec supported
  CPU max MHz: 2800.
  CPU min MHz: 2300.
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:512K
  L3 cache:10240K
  NUMA node0 CPU(s):   0-87
  NUMA node8 CPU(s):   88-175
  NUMA node250 CPU(s): 
  NUMA node251 CPU(s): 
  NUMA node252 CPU(s): 
  NUMA node253 CPU(s): 
  NUMA node254 CPU(s): 
  NUMA node255 CPU(s): 
   
  Machine Type = P9, DD2.2, Witherspoon, baremetal 
   
  ---Steps to Reproduce---
   AT_BASE_PLATFORM in AIXV is not exported to userspace on P9 baremetal 
machines causing trouble to userspace tools and software that relie on that 
information, notably operf and opreport (from oprofile 1.2.0+) will refuse to 
run without that information show a error message like:

  gromero@ltc-wspoon3:/boot$ operf
  NULL returned for one or both of AT_PLATFORM/AT_BASE_PLATFORM
  AT_PLATFORM: power9;  AT_BASE_PLATFORM: (null)
  Unable to obtain cpu_type
  Verify that a pre-1.0 version of OProfile is not in use.
  If the /dev/oprofile/cpu_type file exists, locate the pre-1.0 OProfile
  installation, and use its 'opcontrol' command, passing the --deinit option.
  Unable to ascertain cpu type.  Exiting.
   
  ---uname output---
  linux-image-4.13.0-36-generic  4.13.0-36.40

  Userspace tool common name: operf, opreport 

  Dear maintainer. please consider applying the following fix that's
  already available upstream:

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=e4b79900222b8cccd4da4a7a89581f

  Thank you.

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

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


[Kernel-packages] [Bug 1758242] Re: test_095_kernel_symbols_missing in kernel security test failed on AWS Bionic kernel

2018-03-27 Thread Joseph Salisbury
** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: Incomplete

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

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

Title:
  test_095_kernel_symbols_missing in kernel security test failed on AWS
  Bionic kernel

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

Bug description:
  This issue can be reproduced with 4.15.0-12-generic in -released, it
  will fail with "ValueError: invalid literal for int() with base 16:
  '(null)'"

==
ERROR: test_095_kernel_symbols_missing (__main__.KernelSecurityTest)
kernel addresses in kallsyms and modules are zeroed out
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 1521, in 
test_095_kernel_symbols_missing
self._check_pK_files(expected)
  File "./test-kernel-security.py", line 1440, in _check_pK_files
expected)
  File "./test-kernel-security.py", line 1401, in _read_twice
self.assertEqual(expected, 0 == int(address, 16), "%s: user saw %s" % 
(filename, address))
ValueError: invalid literal for int() with base 16: '(null)'

--

  With 4.15.0-13 and 4.15.0-1002.2, the error was a bit different, it
  will fail with: "AssertionError: /proc/self/stack: root saw 0"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: User Name 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 23 03:56 seq
   crw-rw 1 root audio 116, 33 Mar 23 03:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CurrentDmesg:
   
  Date: Fri Mar 23 04:14:33 2018
  Ec2AMI: ami-266cf15e
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2a
  Ec2InstanceType: x1e.xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  JournalErrors:
   -- Logs begin at Fri 2018-03-23 03:56:35 UTC, end at Fri 2018-03-23 04:12:28 
UTC. --
   Mar 23 03:56:35 username kernel: Cannot get hvm parameter CONSOLE_EVTCHN 
(18): -22!
   Mar 23 03:56:35 username kernel: Cannot get hvm parameter CONSOLE_EVTCHN 
(18): -22!
   Mar 23 03:56:56 hostname iscsid[980]: iSCSI daemon with pid=984 started!
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 
nvme_core.io_timeout=255
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2006
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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


[Kernel-packages] [Bug 1758201] Re: Bluetooth not discover devices

2018-03-27 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Bluetooth not discover devices

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  usb-devices | awk '/3018/' RS=

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-116-generic 4.4.0-116.140
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  francisco   2441 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 22 18:36:18 2018
  HibernationDevice: RESUME=UUID=ba97b130-3f79-4a09-afb8-87f1658a0da1
  InstallationDate: Installed on 2016-09-19 (548 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3490 IMC Networks 
   Bus 001 Device 002: ID 04f2:b52b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X456UF
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=abb93fa0-a860-4786-ab78-566a5db0a3a7 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-116-generic N/A
   linux-backports-modules-4.4.0-116-generic  N/A
   linux-firmware 1.157.16
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X456UF.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X456UF
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX456UF.206:bd01/28/2016:svnASUSTeKCOMPUTERINC.:pnX456UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX456UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X456UF
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1751887] Re: The brightness of the screen cannot be adjusted with either the buttons or the slider.

2018-03-27 Thread albertoiNET
No, /sys/class/backlight/acpi_video0/brightness doesn't change after
user xrandr. This value only change when with I move the brightness
slider at the right top of screen.

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

Title:
  The brightness of the screen cannot be adjusted with either the
  buttons or the slider.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Brightness is always at 100% and cannot be adjusted with either the FN
  brightness buttons or the Unity top bar slider.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  albertoinet   1199 F pulseaudio
   /dev/snd/controlC0:  albertoinet   1199 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 20:49:16 2018
  HibernationDevice: RESUME=UUID=56535002-bba2-4658-b57f-75ba5bb87d4f
  InstallationDate: Installed on 2018-02-25 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Micro-Star International Co., Ltd. GT72VR 7RD
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=Linux vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1785IMS.30E
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-1785
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1785IMS.30E:bd10/27/2017:svnMicro-StarInternationalCo.,Ltd.:pnGT72VR7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1785:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:
  dmi.product.family: GT
  dmi.product.name: GT72VR 7RD
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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


[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

2018-03-27 Thread Leonardo Müller
Don't mark this as fixed yet, it has just happened in a different way:
it progressed further on boot until it froze at the a message like
waiting for /dev/disk.

I, sincerely, don't know what to do now. This has never happened the
kernels starting from 4.16.0-rc5. I have uploaded the bisect log.

And the Ethernet problem was not fixed. It's important to say that I
have both a desktop and a notebook with this same Ethernet device (but
different revision) and only the desktop has this problem:

Desktop:
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 
PCI Express Gigabit Ethernet Controller (rev 03)

Notebook: 
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 
PCI Express Gigabit Ethernet Controller (rev 10)

** Attachment added: "bisect_wireless_bt_panic_log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757218/+attachment/5092474/+files/bisect_wireless_bt_panic_log.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/1757218

Title:
  QCA9377 isn't being recognized sometimes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes, the Wireless Network Card QCA9377 is not recognized on
  boot. This caused, on prior versions, a kernel panic at boot. With
  Bionic, the system boots but is unable to use wireless network. On
  dmesg there are messages like:

  [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd
  [2.808640] usb 1-7: device descriptor read/64, error -71
  [3.044337] usb 1-7: device descriptor read/64, error -71
  [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd
  [3.408245] usb 1-7: device descriptor read/64, error -71
  [3.644244] usb 1-7: device descriptor read/64, error -71
  [3.752193] usb usb1-port7: attempt power cycle
  [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd
  [4.404904] usb 1-7: Device not responding to setup address.
  [4.612478] usb 1-7: Device not responding to setup address.
  [4.820588] usb 1-7: device not accepting address 9, error -71
  [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd
  [4.949109] usb 1-7: Device not responding to setup address.
  [5.156893] usb 1-7: Device not responding to setup address.
  [5.364589] usb 1-7: device not accepting address 10, error -71
  [5.364655] usb usb1-port7: unable to enumerate USB device

  And lspci and lsusb don't show the wireless network card. The
  alternative is to turn the system off. Reboot don't work and reboot to
  Windows 10 also don't. The system must be powered off to restore
  functionality. Then, on the next boot, it works properly.

  However, after the system is turned off, it may cause the issue again.
  This is not 100% consistent, but mostly it cycles between powering off
  and powering on the notebook as:

  Work -> Don't work -> Work -> Don't work

  On Windows 10 this doesn't happen but when happens on Ubuntu, it's
  possible to reboot and see the status on Windows 10 too: on Device
  Manager it's shown a unidentified USB device at 1-7. Sometimes, on
  Windows 10's Network Devices it's shown, instead of the QCA9377, from
  four to six different devices with generic names and Bluetooth and/or
  Wireless don't work.

  When turning Ubuntu off, there are messages that appears a few
  instants before the system is turned off:

  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] 
ath10k_pci :02:00.0: failed to install key for vdev 0 peer 
xx:xx:xx:xx:xx:xx: -110
  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] 
wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110)

  Generally, only the second message appears (but both are recorded on
  kern.log). The MAC adress is the one from the router, not from the
  wireless card.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1364 F pulseaudio
   /dev/snd/seq:usuario1258 F timidity
  CurrentDesktop: XFCE
  Date: Tue Mar 20 14:43:42 2018
  HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
  InstallationDate: Installed on 2017-06-13 (279 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
  

[Kernel-packages] [Bug 1758205] Re: Ubuntu 18.04 NVMe disks are not displayed on lsblk and /dev/disk/by-path (NVMe / Bolt ) (systemd?)

2018-03-27 Thread Joseph Salisbury
** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
   Status: New

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
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/1758205

Title:
  Ubuntu 18.04 NVMe disks are not displayed on lsblk and /dev/disk/by-
  path (NVMe / Bolt ) (systemd?)

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  ---Problem Description---

  Bolt based NVMe disks (namespaces) are not displayed on lsblk and 
/dev/disk/by-path
  # nvme list 
  Node SN   Model   
 Namespace Usage  Format   FW Rev  
    
 - -- 
 
  /dev/nvme0n1 S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 1  28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n10S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 10 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n11S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 11 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n12S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 12 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n13S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 13 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n14S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 14 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n15S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 15 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n16S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 16 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n17S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 17 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n18S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 18 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n19S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 19 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n2 S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 2  28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n20S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 20 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n21S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 21 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n22S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 22 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n23S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 23 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n24S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 24 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n25S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 25 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n26S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 26 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n27S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 27 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n28S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 28 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n29S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 29 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n3 S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 3  28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n30S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 30 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n31S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 31 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n32S3RVNA0J600206   

[Kernel-packages] [Bug 1758264] Re: ISST-LTE: Witherspoon:Ubuntu1804:PowerNV:whip :Unable to start "STAF" on Witherspoon system due to java dumping

2018-03-27 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Status: New => In Progress

** Changed in: linux (Ubuntu)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph 
Salisbury (jsalisbury)

** Also affects: linux (Ubuntu Bionic)
   Importance: Critical
 Assignee: Joseph Salisbury (jsalisbury)
   Status: In Progress

** Changed in: linux (Ubuntu Bionic)
 Assignee: Joseph Salisbury (jsalisbury) => Manoj Iyer (manjo)

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

Title:
  ISST-LTE: Witherspoon:Ubuntu1804:PowerNV:whip :Unable to start "STAF"
  on Witherspoon system due to java dumping

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  == Comment: #0 - INDIRA P. JOGA  - 2018-03-22 
06:45:23 ==
  Problem Description:
  ===
  Unable to start  "STAF" on Witherspoon system due to java dumping

  Steps to re-create:
  ==
  > System installed with Ubunu1804 build.

  root@whip:# uname -a
  Linux whip 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:37:03 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux

  > We are using staf framework to run the LTP test buckets.

  > Unable to start the staf process.

  > It fails to start and i see java dumping core.

  > core details

  root@whip:/# ls -l core*
  -rw--- 1 root root  20709376 Mar 22 06:07 core
  -rw--- 1 root root 114753536 Mar 22 06:06 
core.20180322.060600.4626.0001.dmp
  -rw--- 1 root root 115736576 Mar 22 06:06 
core.20180322.060603.4631.0001.dmp

  > Attached core files

  NOTE:-
  --
  System is on a private network.  Access the private network via SSH to 
"banner.isst.aus.stglabs.ibm.com" using your GSA ID and password. 
  (Banner itself is behind a BSO, so must authenticate through that first.)

  Login details :  
  ssh banner.isst.aus.stglabs.ibm.com [debug/don2rry ]

  Host login:-ssh -p 2200 root@bmc-wax (0penBmc) (or)

  ssh root@wax (don2rry)

  == Comment: #5 - INDIRA P. JOGA  - 2018-03-22 
07:09:14 ==
  Unable to attach core file because huge size.

  Please find the path from the system:

  root@whip:/# pwd
  /
  root@whip:/# ls -l core*
  -rw--- 1 root root  20709376 Mar 22 06:07 core
  -rw--- 1 root root 114753536 Mar 22 06:06 
core.20180322.060600.4626.0001.dmp
  -rw--- 1 root root 115736576 Mar 22 06:06 
core.20180322.060603.4631.0001.dmp
  root@whip:/#

  Regards,
  Indira

  == Comment: #6 - INDIRA P. JOGA  - 2018-03-22 
07:20:12 ==
  Also you can find them in banner

  banner@banner:~> pwd
  /home/banner
  banner@banner:~> ls -l core*
  -rw--- 1 banner banner 114753536 Mar 22 06:46 
core.20180322.060600.4626.0001.dmp
  -rw--- 1 banner banner 115736576 Mar 22 06:46 
core.20180322.060603.4631.0001.dmp

  == Comment: #8 - SEETEENA THOUFEEK  - 2018-03-22
  09:00:18 ==

  
  Please pick 

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=e4b79900222b8cccd4da4a7a89581f0e1b764ed2
  ("powerpc/64s: Fix NULL AT_BASE_PLATFORM when using DT CPU features")

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

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


[Kernel-packages] [Bug 1759314] Re: missing memory (32Gib instead of 64GiB)

2018-03-27 Thread Nicolas Jungers
dmidecode --type memory

** Attachment added: "dmidecode --type memory"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759314/+attachment/5092475/+files/dmidecode_memory.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/1759314

Title:
  missing memory (32Gib instead of 64GiB)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The box has 64GiB ram, EFI shell and dmidecode --type memory see 4 x
  16384 MiB, but dmesg and free report 32GiB

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-13-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Date: Tue Mar 27 17:48:32 2018
  HibernationDevice: RESUME=/dev/mapper/s02--vg-swap_1
  InstallationDate: Installed on 2018-03-27 (0 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180311)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.20
  dmi.board.name: X370 Taichi
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd04/20/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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


[Kernel-packages] [Bug 1758246] Re: test_120_smep_works in ubuntu_qrt_kernel_security failed on AWS Bionic

2018-03-27 Thread Joseph Salisbury
** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: Confirmed

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

** Tags added: kernel-da-key

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

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

Title:
  test_120_smep_works in ubuntu_qrt_kernel_security failed on AWS Bionic

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

Bug description:
  This test was skipped on -release kernel 4.15.0-12:
test_120_smep_works (__main__.KernelSecurityTest)
SMEP works ... (skipped: unfinished test) ok

  But failed with the 4.15.0-13 proposed kernel:

FAIL: test_120_smep_works (__main__.KernelSecurityTest)
SMEP works
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 1666, in test_120_smep_works
self.assertShellExitEquals(0, ["insmod", "execuser/execuser.ko"])
  File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1134, in assertShellExitEquals
self.assertEqual(expected, rc, msg + result + report)
AssertionError: Got exit code 1, expected 0
Command: 'insmod', 'execuser/execuser.ko'
Output:
insmod: ERROR: could not insert module execuser/execuser.ko: Invalid module 
format

  This issue was spotted with manual run for the
  ubuntu_qrt_kernel_security test. The job executed by the jenkins will
  have this test skipped like the result in 4.15.0-12

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 23 04:29 seq
   crw-rw 1 root audio 116, 33 Mar 23 04:29 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Fri Mar 23 05:58:55 2018
  Ec2AMI: ami-266cf15e
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2a
  Ec2InstanceType: x1e.xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=f06dc295-8830-4ede-8aec-fda10bf30396 ro console=tty1 console=ttyS0 
nvme_core.io_timeout=255
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2006
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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


[Kernel-packages] [Bug 1759314] [NEW] missing memory (32Gib instead of 64GiB)

2018-03-27 Thread Nicolas Jungers
Public bug reported:

The box has 64GiB ram, EFI shell and dmidecode --type memory see 4 x
16384 MiB, but dmesg and free report 32GiB

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-13-generic 4.15.0-13.14
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-13-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
Date: Tue Mar 27 17:48:32 2018
HibernationDevice: RESUME=/dev/mapper/s02--vg-swap_1
InstallationDate: Installed on 2018-03-27 (0 days ago)
InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180311)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname--vg-root ro
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-13-generic N/A
 linux-backports-modules-4.15.0-13-generic  N/A
 linux-firmware 1.173
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/20/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.20
dmi.board.name: X370 Taichi
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd04/20/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: amd64 apport-bug bionic

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

Title:
  missing memory (32Gib instead of 64GiB)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The box has 64GiB ram, EFI shell and dmidecode --type memory see 4 x
  16384 MiB, but dmesg and free report 32GiB

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-13-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Date: Tue Mar 27 17:48:32 2018
  HibernationDevice: RESUME=/dev/mapper/s02--vg-swap_1
  InstallationDate: Installed on 2018-03-27 (0 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180311)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname--vg-root ro
  RelatedPackageVersions:
   

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

2018-03-27 Thread Ubuntu Kernel Bot
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/1759314

Title:
  missing memory (32Gib instead of 64GiB)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The box has 64GiB ram, EFI shell and dmidecode --type memory see 4 x
  16384 MiB, but dmesg and free report 32GiB

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-13-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Date: Tue Mar 27 17:48:32 2018
  HibernationDevice: RESUME=/dev/mapper/s02--vg-swap_1
  InstallationDate: Installed on 2018-03-27 (0 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180311)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.20
  dmi.board.name: X370 Taichi
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd04/20/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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


[Kernel-packages] [Bug 1754601] Re: openconnect has trouble maintaining a VPN connection

2018-03-27 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

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

Title:
  openconnect has trouble maintaining a VPN connection

Status in linux package in Ubuntu:
  Triaged
Status in openconnect package in Ubuntu:
  New

Bug description:
  Some time after upgrading to Bionic, I have found that openconnect has
  some trouble keeping a VPN connection open to our company VPN.  Since
  openconnect in Bionic seems to be based on the same upstream release
  as in Artful I assume that the problem is more likely to be in the
  kernel, and the timing of when it started could fit the kernel upgrade
  from 4.13 to 4.15..  I regularly see this in the output:

  SSL read error: Error in the pull function.; reconnecting.
  SSL negotiation with 
  SSL connection failure: The operation timed out
  sleep 10s, remaining timeout 300s
  SSL negotiation with 
  SSL connection failure: The operation timed out
  sleep 20s, remaining timeout 290
  ...

  Interestingly I just now saw it recover from that problem for the
  first time I am aware of.

  I know that it would make sense to test it with the old kernel, and I
  will try that some time (I don't reboot that often, and am not always
  on VPN).  In the mean time, I am creating this report in the hope that
  it will ring some bell with someone.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openconnect 7.08-3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  9 10:25:56 2018
  InstallationDate: Installed on 2017-10-24 (135 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: openconnect
  UpgradeStatus: Upgraded to bionic on 2018-02-06 (30 days ago)
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1608 F pulseaudio
   /dev/snd/controlC1:  michael1608 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=701963f8-cca7-4480-b062-4d2d5006f10d
  InstallationDate: Installed on 2017-10-24 (149 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Dell Inc. Latitude E7440
  Package: openconnect 7.08-3
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  Tags:  wayland-session bionic wayland-session
  Uname: Linux 4.15.0-12-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-02-06 (44 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 02/02/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0WK2DM
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1759045] Re: Important KVM fixes for ppc64el

2018-03-27 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Importance: Undecided => Critical

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

** Changed in: linux (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Canonical Kernel Team (canonical-kernel-team)

** Also affects: linux (Ubuntu Bionic)
   Importance: Critical
 Assignee: Canonical Kernel Team (canonical-kernel-team)
   Status: Triaged

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

Title:
  Important KVM fixes for ppc64el

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

Bug description:
  Hi Canonical,

  There are some critical bugs for KVM that didn't make kernel 4.15 and
  we must have then included in 18.04 kernel. They are:

  * Allow HPT guests on P9 DD2.2 without requiring indep_threads_mode=N.
   
  6964e6a4e489 KVM: PPC: Book3S HV: Do SLB load/unload with guest LPCR value 
loaded
  cda4a1473313 KVM: PPC: Book3S HV: Fix duplication of host SLB entries (needed 
once 6964e6a4e489 is in)
  00608e1f007e KVM: PPC: Book3S HV: Allow HPT and radix on the same core for 
POWER9 v2.2
   
  * Memory management fixes.

  c3856aeb2940 KVM: PPC: Book3S HV: Fix handling of large pages in radix page 
fault handler
  debd574f4195 KVM: PPC: Book3S HV: Fix VRMA initialization with 2MB or 1GB 
memory backing
   
  * Emulation of VMX loads and stores for MMIO.
   
  09f984961c13 KVM: PPC: Book3S: Add MMIO emulation for VMX instructions
  6df3877fc962 KVM: PPC: Book3S: Fix compile error that occurs with some gcc 
versions (needed once 09f984961c13 is in)
   
  * Other important fixes.
   
  05f2bb0313a2 KVM: PPC: Book3S HV: Fix handling of secondary HPTEG in HPT 
resizing code
  790a9df5fbef KVM: PPC: Book3S HV: Make HPT resizing work on POWER9
  a8b48a4dccea KVM: PPC: Book3S HV: Fix trap number return from 
__kvmppc_vcore_entry

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

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


[Kernel-packages] [Bug 1758305] Re: Panic during SyS_reboot

2018-03-27 Thread 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.16 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.16-rc7

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

** Also affects: linux (Ubuntu Bionic)
   Importance: High
   Status: Confirmed

** Tags added: kernel-da-key

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

Title:
  Panic during SyS_reboot

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

Bug description:
  BUG: unable to handle kernel NULL pointer dereference at (null)
  IP: device_shutdown+0xbb/0x200
  PGD 0 P4D 0
  Oops: 0002 [#1] SMP NOPTI

  See the screenshot for more.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ksta   1624 F pulseaudio
   /dev/snd/controlC2:  ksta   1624 F pulseaudio
   /dev/snd/controlC1:  ksta   1624 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 23 07:01:58 2018
  InstallationDate: Installed on 2018-03-13 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311)
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming 5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=5a435321-b09d-44ad-a2ca-cfda4521071d ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22b
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF22b:bd02/13/2018:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AX370-Gaming 5
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Kernel-packages] [Bug 1759312] [NEW] AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu 17.10

2018-03-27 Thread bugproxy
Public bug reported:

---Problem Description---
AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu 17.10
 
---Additional Hardware Info---
Architecture:ppc64le
Byte Order:  Little Endian
CPU(s):  176
On-line CPU(s) list: 0-175
Thread(s) per core:  4
Core(s) per socket:  22
Socket(s):   2
NUMA node(s):8
Model:   2.2 (pvr 004e 1202)
Model name:  POWER9, altivec supported
CPU max MHz: 2800.
CPU min MHz: 2300.
L1d cache:   32K
L1i cache:   32K
L2 cache:512K
L3 cache:10240K
NUMA node0 CPU(s):   0-87
NUMA node8 CPU(s):   88-175
NUMA node250 CPU(s): 
NUMA node251 CPU(s): 
NUMA node252 CPU(s): 
NUMA node253 CPU(s): 
NUMA node254 CPU(s): 
NUMA node255 CPU(s): 
 
Machine Type = P9, DD2.2, Witherspoon, baremetal 
 
---Steps to Reproduce---
 AT_BASE_PLATFORM in AIXV is not exported to userspace on P9 baremetal machines 
causing trouble to userspace tools and software that relie on that information, 
notably operf and opreport (from oprofile 1.2.0+) will refuse to run without 
that information show a error message like:

gromero@ltc-wspoon3:/boot$ operf
NULL returned for one or both of AT_PLATFORM/AT_BASE_PLATFORM
AT_PLATFORM: power9;AT_BASE_PLATFORM: (null)
Unable to obtain cpu_type
Verify that a pre-1.0 version of OProfile is not in use.
If the /dev/oprofile/cpu_type file exists, locate the pre-1.0 OProfile
installation, and use its 'opcontrol' command, passing the --deinit option.
Unable to ascertain cpu type.  Exiting.
 
---uname output---
linux-image-4.13.0-36-generic  4.13.0-36.40
  
Userspace tool common name: operf, opreport 

Dear maintainer. please consider applying the following fix that's
already available upstream:

https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=e4b79900222b8cccd4da4a7a89581f

Thank you.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-166086 severity-medium 
targetmilestone-inin1710

** Tags added: architecture-ppc64le bugnameltc-166086 severity-medium
targetmilestone-inin1710

** Changed in: ubuntu
 Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage 
(ubuntu-power-triage)

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

Title:
  AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu
  17.10

Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu 17.10
   
  ---Additional Hardware Info---
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  176
  On-line CPU(s) list: 0-175
  Thread(s) per core:  4
  Core(s) per socket:  22
  Socket(s):   2
  NUMA node(s):8
  Model:   2.2 (pvr 004e 1202)
  Model name:  POWER9, altivec supported
  CPU max MHz: 2800.
  CPU min MHz: 2300.
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:512K
  L3 cache:10240K
  NUMA node0 CPU(s):   0-87
  NUMA node8 CPU(s):   88-175
  NUMA node250 CPU(s): 
  NUMA node251 CPU(s): 
  NUMA node252 CPU(s): 
  NUMA node253 CPU(s): 
  NUMA node254 CPU(s): 
  NUMA node255 CPU(s): 
   
  Machine Type = P9, DD2.2, Witherspoon, baremetal 
   
  ---Steps to Reproduce---
   AT_BASE_PLATFORM in AIXV is not exported to userspace on P9 baremetal 
machines causing trouble to userspace tools and software that relie on that 
information, notably operf and opreport (from oprofile 1.2.0+) will refuse to 
run without that information show a error message like:

  gromero@ltc-wspoon3:/boot$ operf
  NULL returned for one or both of AT_PLATFORM/AT_BASE_PLATFORM
  AT_PLATFORM: power9;  AT_BASE_PLATFORM: (null)
  Unable to obtain cpu_type
  Verify that a pre-1.0 version of OProfile is not in use.
  If the /dev/oprofile/cpu_type file exists, locate the pre-1.0 OProfile
  installation, and use its 'opcontrol' command, passing the --deinit option.
  Unable to ascertain cpu type.  Exiting.
   
  ---uname output---
  linux-image-4.13.0-36-generic  4.13.0-36.40

  Userspace tool common name: operf, opreport 

  Dear maintainer. please consider applying the following fix that's
  already available upstream:

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=e4b79900222b8cccd4da4a7a89581f

  Thank you.

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

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

[Kernel-packages] [Bug 1759312] [NEW] AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu 17.10

2018-03-27 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

---Problem Description---
AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu 17.10
 
---Additional Hardware Info---
Architecture:ppc64le
Byte Order:  Little Endian
CPU(s):  176
On-line CPU(s) list: 0-175
Thread(s) per core:  4
Core(s) per socket:  22
Socket(s):   2
NUMA node(s):8
Model:   2.2 (pvr 004e 1202)
Model name:  POWER9, altivec supported
CPU max MHz: 2800.
CPU min MHz: 2300.
L1d cache:   32K
L1i cache:   32K
L2 cache:512K
L3 cache:10240K
NUMA node0 CPU(s):   0-87
NUMA node8 CPU(s):   88-175
NUMA node250 CPU(s): 
NUMA node251 CPU(s): 
NUMA node252 CPU(s): 
NUMA node253 CPU(s): 
NUMA node254 CPU(s): 
NUMA node255 CPU(s): 
 
Machine Type = P9, DD2.2, Witherspoon, baremetal 
 
---Steps to Reproduce---
 AT_BASE_PLATFORM in AIXV is not exported to userspace on P9 baremetal machines 
causing trouble to userspace tools and software that relie on that information, 
notably operf and opreport (from oprofile 1.2.0+) will refuse to run without 
that information show a error message like:

gromero@ltc-wspoon3:/boot$ operf
NULL returned for one or both of AT_PLATFORM/AT_BASE_PLATFORM
AT_PLATFORM: power9;AT_BASE_PLATFORM: (null)
Unable to obtain cpu_type
Verify that a pre-1.0 version of OProfile is not in use.
If the /dev/oprofile/cpu_type file exists, locate the pre-1.0 OProfile
installation, and use its 'opcontrol' command, passing the --deinit option.
Unable to ascertain cpu type.  Exiting.
 
---uname output---
linux-image-4.13.0-36-generic  4.13.0-36.40
  
Userspace tool common name: operf, opreport 

Dear maintainer. please consider applying the following fix that's
already available upstream:

https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=e4b79900222b8cccd4da4a7a89581f

Thank you.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-166086 severity-medium 
targetmilestone-inin1710
-- 
AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu 17.10
https://bugs.launchpad.net/bugs/1759312
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 1758206] Re: Ubuntu 18.04 [ WSP DD2.2 with stop4 and stop5 enabled ]: kdump fails to capture dump when smt=2 or off.

2018-03-27 Thread Frank Heimes
** Changed in: ubuntu-power-systems
   Status: Triaged => 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/1758206

Title:
  Ubuntu 18.04 [ WSP DD2.2 with stop4 and stop5 enabled ]: kdump fails
  to capture dump when smt=2 or off.

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  ---Problem Description---

  Ubuntu 18.04 [ WSP DD2.2 with stop4 and stop5 enabled ]: kdump fails
  to capture dump when smt=2 or off.

  ---Environment--
  Kernel Build:  4.15.0-13-generic
  System Name :  ltc-wspoon4
  Model/Type  :  P9
  Platform:  BML

  ---Steps to reproduce--

  1. Configure kdump.
  2. Set smt=off
  # ppc64_cpu --smt=off
  3. trigger crash.
  echo 1 > /proc/sys/kernel/sysrq
  echo "c" > /proc/sysrq-trigger

  ---Logs

  root@ltc-wspoon4:~# dpkg -l|grep kexec
  ii  kexec-tools 1:2.0.16-1ubuntu1 
ppc64el  tools to support fast kexec reboots
  root@ltc-wspoon4:~# makedumpfile -v
  makedumpfile: version 1.6.3 (released on 29 Jun 2018)
  lzo   enabled
  snappydisabled

  
  [  285.519832] [c01fe2d83de0] [c03d1898] SyS_write+0x68/0x110
  [  285.519926] [c01fe2d83e30] [c000b184] system_call+0x58/0x6c
  [  285.520007] Instruction dump:
  [  285.520053] 4bfff9f1 4bfffe50 3c4c00f0 3842e800 7c0802a6 6000 3921 
3d42001c 
  [  285.520158] 394a6db0 912a 7c0004ac 3940 <992a> 4e800020 
3c4c00f0 3842e7d0 
  [  285.520261] ---[ end trace 90a666dc7ca6f0ec ]---
  [  286.525787] 
  [  286.525883] Sending IPI to other CPUs
  [  28[  401.296284048,5] OPAL: Switch to big-endian OS
  [  402.297026662,3] OPAL: CPU 0x1 not in OPAL !
  6.851284] IPI complete
  [  403.455520784,3] OPAL: CPU 0x1 not in OPAL !nce.
  [  403.455569636,5] OPAL: Switch to little-endian OS
  [  404.455711332,3] OPAL: CPU 0x1 not in OPAL !
  [  404.470276386,3] PHB#[0:0]: CRESET: Unexpected slot state 0102, 
resetting...
  [  413.140065625,3] PHB#0003[0:3]: CRESET: Unexpected slot state 0102, 
resetting...
  [  421.393193605,3] PHB#0030[8:0]: CRESET: Unexpected slot state 0102, 
resetting...
  [  423.353977316,3] PHB#0033[8:3]: CRESET: Unexpected slot state 0102, 
resetting...
  [  425.314547966,3] PHB#0034[8:4]: CRESET: Unexpected slot state 0102, 
resetting...

  [5.004718] Processor 1 is stuck.
  [   10.007584] Processor 2 is stuck.
  [   15.010425] Processor 3 is stuck.
  [   16.135550] integrity: Unable to open file: /etc/keys/x509_ima.der (-2)
  [   16.135554] integrity: Unable to open file: /etc/keys/x509_evm.der (-2)
  [   16.250952] vio vio: uevent: failed to send synthetic uevent

  
  --== Welcome to Hostboot hostboot-5fc3b52/hbicore.bin ==--

4.52180|secure|SecureROM valid - enabling functionality
4.53193|secure|Booting in non-secure mode.
6.00924|Booting from SBE side 0 on master proc=0005

  
  There could be a firmware issue there but still there is need for the below 
kernel
  patches to be included to ensure kdump kernel captures dump successfully
  when SMT is set to 2/off

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=04b9c96eae72d862726f2f4bfcec2078240c33c5
  ("powerpc/crash: Remove the test for cpu_online in the IPI callback")

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4145f358644b970fcff293c09fdcc7939e8527d2
  ("powernv/kdump: Fix cases where the kdump kernel can get HMI's")

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=910961754572a2f4c83ad7e610d180
  ("powerpc/kdump: Fix powernv build break when KEXEC_CORE=n")

  Thanks
  Hari

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

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


  1   2   >