[Kernel-packages] [Bug 1699772] Re: linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic | Regressio

2018-03-07 Thread Joseph Salisbury
It might be worth also testing 4.16-rc4:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc4/

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

Title:
  linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-
  image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-
  image-3.13.0-121-generic | Regression: many user-space apps crashing

Status in LibreOffice:
  Won't Fix
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux package in Debian:
  Fix Released

Bug description:
  Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10)

  linux-image-4.4.0-81-generic appears to contain a regression, probably
  related to the CVE-2017-1000364 fix backport / patch.

  Using this kernel, the Oracle Java browser plugin always crashes
  during stack-related actions on initialization. This means, the plugin
  completely stopped working.

  
  It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to 
CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also 
contains a fix for CVE-2017-1000364.


  uname -a:

  > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06
  UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


  I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as
  well as Iceweasel / Firefox/3.5.16 in a chroot.

  Using linux-image-4.4.0-81-generic it crashes in all combinations
  while with both other kernels it works.

  
  I was not able to obtain any detailed crash information from Firefox 51.0.1, 
but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace 
which shows the relation to stack operations performed by the plugin, even 
without proper debug symbols:

  
  > (gdb) bt full
  > #0  0x7fa06d805307 in _expand_stack_to(unsigned char*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #1  0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, 
unsigned char*) ()
  >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #2  0x7fa06d80cf0b in JVM_handle_linux_signal () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #3  0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #4  

  
  I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6.

  
  The crash will be triggered by any applet, for example the test applet at:

  * https://java.com/en/download/installed8.jsp

  
  I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow 
apparently does not allow me to use apport to report this bug:

  > $ LANG= apport-cli linux-image-4.4.0-81-generic
  > 
  > *** Collecting problem information
  > 
  > The collected information can be sent to the developers to improve the
  > application. This might take a few minutes.
  > .
  > 
  > *** Problem in linux-image-4.4.0-81-generic
  > 
  > The problem cannot be reported:
  > 
  > This is not an official KDE package. Please remove any third party package 
and try again.

  If someone can tell me how to get apport working for this package, I
  can use it to collect additional information, but (unfortunately?) the
  problem should be fairly easy to reproduce...

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1699772/+subscriptions

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


[Kernel-packages] [Bug 1751398] Re: Brightness keys do nothing, stuck on full brightness

2018-03-07 Thread Kai-Heng Feng
What's the output of `find /sys/class/backlight`?

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

Title:
  Brightness keys do nothing, stuck on full brightness

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Brightness keys do nothing, stuck on full brightness

  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
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  forge  1895 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Feb 23 19:47:44 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-23 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: LENOVO 80R3
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=85451546-daae-4935-b12f-494e677b1dac 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: Upgraded to xenial on 2018-02-23 (0 days ago)
  dmi.bios.date: 12/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: D3CN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Flex 3-1480
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Flex 3-1480
  dmi.modalias: 
dmi:bvnLENOVO:bvrD3CN29WW:bd12/23/2015:svnLENOVO:pn80R3:pvrFlex3-1480:rvnLENOVO:rnFlex3-1480:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrFlex3-1480:
  dmi.product.name: 80R3
  dmi.product.version: Flex 3-1480
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1751798] Re: linux: 4.13.0-37.42 -proposed tracker

2018-03-07 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

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

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

Title:
  linux: 4.13.0-37.42 -proposed tracker

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

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

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

  backports: bug 1751799 (linux-azure), bug 1751801 (linux-azure-edge), bug 
1751802 (linux-gcp), bug 1751803 (linux-hwe), bug 1751805 (linux-oem)
  derivatives: bug 1751807 (linux-raspi2)
  kernel-stable-phase-changed:Tuesday, 27. February 2018 18:31 UTC
  kernel-stable-phase:Uploaded

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

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

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


[Kernel-packages] [Bug 1726362] Re: CONFIG_EFI=y on armhf

2018-03-07 Thread Seth Forshee
** 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/1726362

Title:
  CONFIG_EFI=y on armhf

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

Bug description:
  [Impact]

   * Please enable CONFIG_EFI on the armhf generic kernels
   * This may enable using armhf kernels with an armhf cloud-image and 
qemu-efi-arm under qemu-system-arm

  [Test Case]

   * Kernel config has CONFIG_EFI=y

  [Regression Potential]

   * Kernel config/image/modules will become larger in size due to more
  features enabled on the arm kernel.

  [Other Info]
   
   * qemu-efi-arm is available, experimental cloud-images are being produced, 
but not yet released to cloud-images.
   * expectations for cloud images to land into bb and then enabled on 
xenial/zesty/artful as well.

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

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


[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions

2018-03-07 Thread Nobuto Murata
With rc2 result. It looks like there is a noticeable difference between
v4.12-rc3 and v4.12-rc4.

@Joseph, can you please start looking into diffs? I'm keeping one
dedicated node just for this testing, so I can run the same script one
by one for more bisections.

v4.12-rc1 - bad (3 of 3)
v4.12-rc2 - bad (15 of 53 - 28.3%)
v4.12-rc3 - bad (24 of 90 - 26.6%)
v4.12-rc4 - relatively good (1 of 70 - 1.4%)
v4.12 - relatively good (5 out of 68 - 7.4%)
v4.13 - good (0 out of 41 - 0%)

FWIW, I will run the same test with xenial's 4.4 kernel to make sure
around 30% is the base line of "bad".

** Attachment added: "bond_check_xenial_mainline_4.12-rc2_full.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5072683/+files/bond_check_xenial_mainline_4.12-rc2_full.log

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

Title:
  [i40e] LACP bonding start up race conditions

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

Bug description:
  When provisioning Ubuntu servers with MAAS at once, some bonding pairs
  will have unexpected LACP status such as "Expired". It randomly
  happens at each provisioning with the default xenial kernel(4.4), but
  not reproducible with HWE kernel(4.13). I'm using Intel X710 cards
  (Dell-branded).

  Using the HWE kernel works as a workaround for short term, but it's
  not ideal since 4.13 is not covered by Canonical Livepatch service.

  How to reproduce:
  1. configure LACP bonding with MAAS
  2. provision machines
  3. check the bonding status in /proc/net/bonding/bond*

  frequency of occurrence:
  About 5 bond pairs in 22 pairs at each provisioning.

  [reproducible combination]
  $ uname -a
  Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 1.4.25-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  [non-reproducible combination]
  $ uname -a
  Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 2.1.14-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  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
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  6 06:37 seq
   crw-rw 1 root audio 116, 33 Mar  6 06:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Mar  6 06:46:32 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R730
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 
console=ttyS0,115200n8
  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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.5
  dmi.board.name: 072T6D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.asset.tag: 0018880
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R730
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1686189] Re: External monitor connecting problem on Intel graphics card

2018-03-07 Thread Kai-Heng Feng
Do you have package "xserver-xorg-video-intel"?

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

Title:
  External monitor connecting problem on Intel graphics card

Status in linux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am facing a problem with Intel Graphics driver. I have external
  monitor and in display settings the second monitor is detecting but
  it's not working, so could you email me a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.4.25-040425-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 25 21:45:16 2017
  DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
  InstallationDate: Installed on 2017-04-25 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 3537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic 
root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 03JPPR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 3537
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 25 21:37:24 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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


[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions

2018-03-07 Thread Nobuto Murata
With rc3, will test rc2 next.

v4.12-rc1 - bad (3 out of 3)
v4.12-rc3 - mixture result (24 out of 90)
v4.12-rc4 - relatively good (1 out of 70)
v4.12 - relatively good (5 out of 68)
v4.13 - good (0 out of 41)

** Attachment added: "bond_check_xenial_mainline_4.12-rc3_full.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5072525/+files/bond_check_xenial_mainline_4.12-rc3_full.log

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

Title:
  [i40e] LACP bonding start up race conditions

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

Bug description:
  When provisioning Ubuntu servers with MAAS at once, some bonding pairs
  will have unexpected LACP status such as "Expired". It randomly
  happens at each provisioning with the default xenial kernel(4.4), but
  not reproducible with HWE kernel(4.13). I'm using Intel X710 cards
  (Dell-branded).

  Using the HWE kernel works as a workaround for short term, but it's
  not ideal since 4.13 is not covered by Canonical Livepatch service.

  How to reproduce:
  1. configure LACP bonding with MAAS
  2. provision machines
  3. check the bonding status in /proc/net/bonding/bond*

  frequency of occurrence:
  About 5 bond pairs in 22 pairs at each provisioning.

  [reproducible combination]
  $ uname -a
  Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 1.4.25-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  [non-reproducible combination]
  $ uname -a
  Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 2.1.14-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  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
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  6 06:37 seq
   crw-rw 1 root audio 116, 33 Mar  6 06:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Mar  6 06:46:32 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R730
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 
console=ttyS0,115200n8
  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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.5
  dmi.board.name: 072T6D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.asset.tag: 0018880
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R730
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1748565] Re: Bluetooth: hci0: last event is not cmd complete (0x0f)

2018-03-07 Thread Bulent Besim
My problem was related to a faulty Bluetooth device. Sorry about the
noise, please disregard. 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/1748565

Title:
  Bluetooth: hci0: last event is not cmd complete (0x0f)

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

Bug description:
  Hello,

  dmesg:
  [ 3363.056494] Bluetooth: hci0: last event is not cmd complete (0x0f)

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-9-generic 4.15.0-9.10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1811 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Feb  9 20:35:29 2018
  InstallationDate: Installed on 2017-10-13 (119 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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


[Kernel-packages] [Bug 1754064] Re: linux: 4.15.0-12.13 -proposed tracker

2018-03-07 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

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

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

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

** Tags added: block-proposed-bionic

** Tags added: block-proposed

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

** Description changed:

  This bug is for tracking the 4.15.0-12.13 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
- kernel-phase-changed:Wednesday, 07. March 2018 15:30 UTC
- kernel-phase:Packaging
- 
  -- swm properties --
  phase: Packaging
+ kernel-phase-changed:Wednesday, 07. March 2018 22:01 UTC
+ kernel-phase:Uploaded

** Description changed:

  This bug is for tracking the 4.15.0-12.13 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
- phase: Packaging
- kernel-phase-changed:Wednesday, 07. March 2018 22:01 UTC
- kernel-phase:Uploaded
+ phase: Uploaded

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

Title:
  linux: 4.15.0-12.13 -proposed tracker

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

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

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

  -- swm properties --
  phase: Uploaded

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

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


[Kernel-packages] [Bug 1754059] Re: linux: 4.15.0-12.13 -proposed tracker

2018-03-07 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

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

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

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

** Tags added: block-proposed-bionic

** Tags added: block-proposed

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

** Description changed:

  This bug is for tracking the 4.15.0-12.13 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ kernel-phase-changed:Wednesday, 07. March 2018 22:00 UTC
+ kernel-phase:Uploaded

** Description changed:

  This bug is for tracking the 4.15.0-12.13 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  kernel-phase-changed:Wednesday, 07. March 2018 22:00 UTC
  kernel-phase:Uploaded
+ 
+ -- swm properties --
+ phase: Uploaded

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

Title:
  linux: 4.15.0-12.13 -proposed tracker

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

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

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

  kernel-phase-changed:Wednesday, 07. March 2018 22:00 UTC
  kernel-phase:Uploaded

  -- swm properties --
  phase: Uploaded

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

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


[Kernel-packages] [Bug 1751798] Re: linux: 4.13.0-37.42 -proposed tracker

2018-03-07 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-artful

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1751799 (linux-azure), bug 1751801 (linux-azure-edge), bug 
1751802 (linux-gcp), bug 1751803 (linux-hwe), bug 1751805 (linux-oem)
  derivatives: bug 1751807 (linux-raspi2)
  kernel-stable-phase-changed:Tuesday, 27. February 2018 18:31 UTC
  kernel-stable-phase:Uploaded
  
  -- swm properties --
+ boot-testing-requested: true
  phase: Uploaded

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

Title:
  linux: 4.13.0-37.42 -proposed tracker

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

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

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

  backports: bug 1751799 (linux-azure), bug 1751801 (linux-azure-edge), bug 
1751802 (linux-gcp), bug 1751803 (linux-hwe), bug 1751805 (linux-oem)
  derivatives: bug 1751807 (linux-raspi2)
  kernel-stable-phase-changed:Tuesday, 27. February 2018 18:31 UTC
  kernel-stable-phase:Uploaded

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

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

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


[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

2018-03-07 Thread Dan Streetman
Sorry for the long delay - I haven't forgot about this bug, but I have
to think about how best to add debug to track the dst leak(s) in a
generic way.  I'll try to get back to this bug sometime this or next
week.

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

Title:
  unregister_netdevice: waiting for lo to become free

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

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  See comment 16, reproducer provided at https://github.com/fho/docker-
  samba-loop

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

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


[Kernel-packages] [Bug 1748801] Re: Sometimes Freezes

2018-03-07 Thread Buda
kernel-fixed-upstream

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

** Tags added: kernel-fixed-upstream

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

Title:
  Sometimes Freezes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes freezes, i have 8gb of ram, i don't understand... Goodbye!

  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:  nixon  2430 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 11 21:27:10 2018
  HibernationDevice: RESUME=UUID=85d90702-6bb1-41d7-9ef9-776d17077151
  InstallationDate: Installed on 2018-02-11 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: VIT VIT P3400
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=d5a5f05f-a5a2-48d2-ae69-e6620f8a2f34 ro 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
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 2.00.01.IP_T4
  dmi.board.asset.tag: NULL
  dmi.board.name: VIT P3400
  dmi.board.vendor: VIT
  dmi.board.version: Not applicable
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: VIT
  dmi.chassis.version: Not applicable
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr2.00.01.IP_T4:bd03/25/2013:svnVIT:pnVITP3400:pvr1.0:rvnVIT:rnVITP3400:rvrNotapplicable:cvnVIT:ct9:cvrNotapplicable:
  dmi.product.family: ChiefRiver System
  dmi.product.name: VIT P3400
  dmi.product.version: 1.0
  dmi.sys.vendor: VIT

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

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


[Kernel-packages] [Bug 1748801] Re: Sometimes Freezes

2018-03-07 Thread Buda
Excellent!... no more Problem!... thanks for the help!... Bye!.. Kind of
Regards!...

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

Title:
  Sometimes Freezes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes freezes, i have 8gb of ram, i don't understand... Goodbye!

  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:  nixon  2430 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 11 21:27:10 2018
  HibernationDevice: RESUME=UUID=85d90702-6bb1-41d7-9ef9-776d17077151
  InstallationDate: Installed on 2018-02-11 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: VIT VIT P3400
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=d5a5f05f-a5a2-48d2-ae69-e6620f8a2f34 ro 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
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 2.00.01.IP_T4
  dmi.board.asset.tag: NULL
  dmi.board.name: VIT P3400
  dmi.board.vendor: VIT
  dmi.board.version: Not applicable
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: VIT
  dmi.chassis.version: Not applicable
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr2.00.01.IP_T4:bd03/25/2013:svnVIT:pnVITP3400:pvr1.0:rvnVIT:rnVITP3400:rvrNotapplicable:cvnVIT:ct9:cvrNotapplicable:
  dmi.product.family: ChiefRiver System
  dmi.product.name: VIT P3400
  dmi.product.version: 1.0
  dmi.sys.vendor: VIT

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

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


[Kernel-packages] [Bug 1745349] Re: Hard lockup during boot with linux-image-4.4.0-112-generic

2018-03-07 Thread Lars Behrens
linux-image-4.4.0-116-generic_4.4.0-116.140~lp1745349Commitb0c3e8bd0405Reverted_amd64
seems to work here, 3 reboots in a row on one machine without hard locks.

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

Title:
  Hard lockup during boot with linux-image-4.4.0-112-generic

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

Bug description:
  Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112
  instead they show

  NMI watchdog: Watchdog detected hard lockup on cpu 0
  NMI watchdog: Watchdog detected hard lockup on cpu 1
  NMI watchdog: Watchdog detected hard lockup on cpu 3
  NMI watchdog: Watchdog detected hard lockup on cpu 2

  I cannot provide any logs of course.

  Booting with 4.4.0-109 works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lr3200 2013 F pulseaudio
  Date: Thu Jan 25 11:38:55 2018
  HibernationDevice: RESUME=UUID=8e35131d-6d40-4f4f-a3db-c7336e72cbce
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp3s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=4dc5bb0a-ab7c-48fa-ac23-bcdf23755d93 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-109-generic N/A
   linux-backports-modules-4.4.0-109-generic  N/A
   linux-firmware 1.157.15
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3601
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-C
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions

2018-03-07 Thread Nobuto Murata
I have let rc4 run for hours.

v4.12-rc1 - bad (3 out of 3)
v4.12-rc4 - relatively good (1 out of 70)
v4.12 - relatively good (5 out of 68)
v4.13 - good (0 out of 41)

I will let rc3 run during my night.

** Attachment added: "bond_check_xenial_mainline_4.12-rc4_full.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5071915/+files/bond_check_xenial_mainline_4.12-rc4_full.log

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

Title:
  [i40e] LACP bonding start up race conditions

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

Bug description:
  When provisioning Ubuntu servers with MAAS at once, some bonding pairs
  will have unexpected LACP status such as "Expired". It randomly
  happens at each provisioning with the default xenial kernel(4.4), but
  not reproducible with HWE kernel(4.13). I'm using Intel X710 cards
  (Dell-branded).

  Using the HWE kernel works as a workaround for short term, but it's
  not ideal since 4.13 is not covered by Canonical Livepatch service.

  How to reproduce:
  1. configure LACP bonding with MAAS
  2. provision machines
  3. check the bonding status in /proc/net/bonding/bond*

  frequency of occurrence:
  About 5 bond pairs in 22 pairs at each provisioning.

  [reproducible combination]
  $ uname -a
  Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 1.4.25-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  [non-reproducible combination]
  $ uname -a
  Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 2.1.14-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  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
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  6 06:37 seq
   crw-rw 1 root audio 116, 33 Mar  6 06:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Mar  6 06:46:32 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R730
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 
console=ttyS0,115200n8
  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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.5
  dmi.board.name: 072T6D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.asset.tag: 0018880
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R730
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1753804] Re: versions 4.4.0-108 and up hang on reboot; HP 8300 Elite CMT

2018-03-07 Thread Nick Fankhauser
I installed 4.4.120-0404120-generic. Is this the version you intended?

This fixed my problem. Thank you!

Added kernel-fixed-upstream tag and changed status to Confirmed as
requested.

Advice requested: At this point, should I just keep running this kernel
until the regular release process catches up to this version?

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

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

Title:
  versions 4.4.0-108 and up hang on reboot; HP 8300 Elite CMT

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Shutdown works fine. 
  On Reboot, the system hangs.

  This is a problem on the current kernel (4.4.0.116) and appears to
  have been introduced in 4.4.0.106, 107 or 108. I make this assertion
  because I have version 4.4.0.105 and version 4.4.0.108 available on my
  computer. versions 105 and below work, versions 108 and up do not
  work.

  I will upload a screen shot of the trace, since it occurs after drives
  are dismounted.

  I started by making sure I have the most current firmware (BIOS) for
  this computer. It is on the most recent version.

  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
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nickf  2552 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Mar  6 12:52:16 2018
  HibernationDevice: RESUME=UUID=8f1f8ead-e0d0-4468-b7fb-1328c0495e93
  InstallationDate: Installed on 2012-09-27 (1986 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: Hewlett-Packard HP Compaq Elite 8300 CMT
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=9766c23d-8567-48c0-a1eb-b01e0eed0170 ro acpi=force
  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
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 10/05/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: K01 v03.04
  dmi.board.asset.tag: 2UA23822YR
  dmi.board.name: 3396
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 2UA23822YR
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v03.04:bd10/05/2016:svnHewlett-Packard:pnHPCompaqElite8300CMT:pvr:rvnHewlett-Packard:rn3396:rvr:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: HP Compaq Elite 8300 CMT
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1753804] Re: versions 4.4.0-108 and up hang on reboot; HP 8300 Elite CMT

2018-03-07 Thread Nick Fankhauser
** Tags added: kernel-fixed-upstream

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

Title:
  versions 4.4.0-108 and up hang on reboot; HP 8300 Elite CMT

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Shutdown works fine. 
  On Reboot, the system hangs.

  This is a problem on the current kernel (4.4.0.116) and appears to
  have been introduced in 4.4.0.106, 107 or 108. I make this assertion
  because I have version 4.4.0.105 and version 4.4.0.108 available on my
  computer. versions 105 and below work, versions 108 and up do not
  work.

  I will upload a screen shot of the trace, since it occurs after drives
  are dismounted.

  I started by making sure I have the most current firmware (BIOS) for
  this computer. It is on the most recent version.

  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
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nickf  2552 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Mar  6 12:52:16 2018
  HibernationDevice: RESUME=UUID=8f1f8ead-e0d0-4468-b7fb-1328c0495e93
  InstallationDate: Installed on 2012-09-27 (1986 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: Hewlett-Packard HP Compaq Elite 8300 CMT
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=9766c23d-8567-48c0-a1eb-b01e0eed0170 ro acpi=force
  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
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 10/05/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: K01 v03.04
  dmi.board.asset.tag: 2UA23822YR
  dmi.board.name: 3396
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 2UA23822YR
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v03.04:bd10/05/2016:svnHewlett-Packard:pnHPCompaqElite8300CMT:pvr:rvnHewlett-Packard:rn3396:rvr:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: HP Compaq Elite 8300 CMT
  dmi.sys.vendor: Hewlett-Packard

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

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


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

2018-03-07 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/1754052

Title:
  Dell Latitude 7480 press shift keys triggers random mouseclick when
  `Tap to click` enabled on touchpad.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 16.04.3 and 17.10.1 holding down either shift key on a Dell
  Latitude 7480 causes random mouse clicks to occur without being
  nowhere near the touchpad with palms. No external mouse/keyboard
  connected. Disabling `Tap to click` in `Mouse & Touchpad` settings
  makes the problem go away. The problem is not present in 14.04.5,
  whether installed or live CD.

  How to reproduce:

  1. On a Dell Latitude 7480 live boot (or install) one of the following images:
  - ubuntu-16.04.3-desktop-amd64.iso
  - ubuntu-17.10.1-desktop-amd64.iso

  2. Open `Mouse & Touchpad` and make sure `Tap to click` is enabled.
  3. Click `Test Your Settings` and make sure window has focus.
  4. Hold down either shift key and after a few seconds single/double clicks 
start registering.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CasperVersion: 1.376.2
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Mar  7 13:00:21 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:07a0]
  LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
  MachineType: Dell Inc. Latitude 7480
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.2
  dmi.board.name: 00F6D3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.2:bd01/30/2018:svnDellInc.:pnLatitude7480:pvr:rvnDellInc.:rn00F6D3:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Latitude 7480
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions

2018-03-07 Thread Joseph Salisbury
Do you happen to have results from any of the other release candidates,
such as 4.12-rc4?

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

Title:
  [i40e] LACP bonding start up race conditions

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

Bug description:
  When provisioning Ubuntu servers with MAAS at once, some bonding pairs
  will have unexpected LACP status such as "Expired". It randomly
  happens at each provisioning with the default xenial kernel(4.4), but
  not reproducible with HWE kernel(4.13). I'm using Intel X710 cards
  (Dell-branded).

  Using the HWE kernel works as a workaround for short term, but it's
  not ideal since 4.13 is not covered by Canonical Livepatch service.

  How to reproduce:
  1. configure LACP bonding with MAAS
  2. provision machines
  3. check the bonding status in /proc/net/bonding/bond*

  frequency of occurrence:
  About 5 bond pairs in 22 pairs at each provisioning.

  [reproducible combination]
  $ uname -a
  Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 1.4.25-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  [non-reproducible combination]
  $ uname -a
  Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 2.1.14-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  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
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  6 06:37 seq
   crw-rw 1 root audio 116, 33 Mar  6 06:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Mar  6 06:46:32 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R730
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 
console=ttyS0,115200n8
  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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.5
  dmi.board.name: 072T6D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.asset.tag: 0018880
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R730
  dmi.sys.vendor: Dell Inc.

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

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


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

2018-03-07 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 1754078

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

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

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

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

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

Title:
  reenable full variable debugging information within dbgsyms with gcc
  vta cflags

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Due to ubuntu kernel (Ubuntu 4.13.0-36.40-generic 4.13.13) being
  compiled with ""-fno-var-tracking-assignments", the debug symbols
  produced are of lesser quality, i.e. $context variables are not
  available.

  E.g.: (systemtap needs to be installed on the system)

  $> stap -L 'kernel.function("reparent_leader")'
  
kernel.function("reparent_leader@/build/linux-r9581B/linux-4.13.0/kernel/exit.c:632")

  on Fedora (Linux 4.15.6-300.fc27.x86_64) the same command gives:
  kernel.function("reparent_leader@kernel/exit.c:632") $dead:struct list_head* 
$p:struct task_struct* $father:struct task_struct*

  more info:
  SystemTap Release notes (known issues)
  https://sourceware.org/ml/systemtap/2017-q4/msg00096.html

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

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


[Kernel-packages] [Bug 1754076] Re: i2c-thunderx: erroneous error message "unhandled state: 0"

2018-03-07 Thread dann frazier
** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => dann frazier (dannf)

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => dann frazier (dannf)

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => dann frazier (dannf)

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

Title:
  i2c-thunderx: erroneous error message "unhandled state: 0"

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

Bug description:
  [Impact]
  A misleading error is occasionally emitted by the kernel.

  [Test Case]
  Boot a ThunderX system and watch for the error:

  i2c-thunderx :01:09.4: unhandled state: 0

  [Regression Risk]
  Driver is specific to a platform, and the only functional change is skipping 
the emission of an error message.

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

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


[Kernel-packages] [Bug 1754052] Re: Dell Latitude 7480 press shift keys triggers random mouseclick when `Tap to click` enabled on touchpad.

2018-03-07 Thread Timo Aaltonen
** Package changed: xorg (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/1754052

Title:
  Dell Latitude 7480 press shift keys triggers random mouseclick when
  `Tap to click` enabled on touchpad.

Status in linux package in Ubuntu:
  New

Bug description:
  In Ubuntu 16.04.3 and 17.10.1 holding down either shift key on a Dell
  Latitude 7480 causes random mouse clicks to occur without being
  nowhere near the touchpad with palms. No external mouse/keyboard
  connected. Disabling `Tap to click` in `Mouse & Touchpad` settings
  makes the problem go away. The problem is not present in 14.04.5,
  whether installed or live CD.

  How to reproduce:

  1. On a Dell Latitude 7480 live boot (or install) one of the following images:
  - ubuntu-16.04.3-desktop-amd64.iso
  - ubuntu-17.10.1-desktop-amd64.iso

  2. Open `Mouse & Touchpad` and make sure `Tap to click` is enabled.
  3. Click `Test Your Settings` and make sure window has focus.
  4. Hold down either shift key and after a few seconds single/double clicks 
start registering.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CasperVersion: 1.376.2
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Mar  7 13:00:21 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:07a0]
  LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
  MachineType: Dell Inc. Latitude 7480
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.2
  dmi.board.name: 00F6D3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.2:bd01/30/2018:svnDellInc.:pnLatitude7480:pvr:rvnDellInc.:rn00F6D3:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Latitude 7480
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Kernel-packages] [Bug 1743541] Re: Ubuntu18.04: PowerNV - cpupower monitor will not work when cpu0 is offline

2018-03-07 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => 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/1743541

Title:
  Ubuntu18.04: PowerNV - cpupower monitor will not work when cpu0 is
  offline

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

Bug description:
  == Comment: #0 - Shriya R. Kulkarni  - 2018-01-16 
04:58:48 ==
  Problem Description :
  =

  cpupower monitor fails to show stop states when cpu 0 is made offline.

  Testing :
  =
  root@ltc-wspoon12:~# echo 0 > /sys/devices/system/cpu/cpu0/online 
  root@ltc-wspoon12:~# cpupower monitor 
  WARNING: at least one cpu is offline
  No HW Cstate monitors found
  root@ltc-wspoon12:~# cpupower -c 12 monitor 
  WARNING: at least one cpu is offline
  No HW Cstate monitors found
  root@ltc-wspoon12:~# 

  root@ltc-wspoon12:~# echo 1 > /sys/devices/system/cpu/cpu0/online 
  root@ltc-wspoon12:~# cpupower -c 12 monitor 
|Idle_Stats
  PKG |CORE|CPU | snoo | stop | stop | stop | stop 
 0|  12|  12|  0.00|  0.00|  0.00|  0.00|  0.01

  Details :
  
  uname -a : Linux ltc-wspoon12 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 
21:15:55 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  OS : Ubuntu 18.04
  Machine : Witherspoon ( DD2.1) and Boston (DD.01)

  Patch :
  
  Patch that fixes the issue : 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=dbdc468f35ee827cab2753caa1c660bdb832243a

  == Comment: #1 - VIPIN K. PARASHAR  - 2018-01-16 
05:09:40 ==
  (In reply to comment #0)

  > Patch :
  > 
  > Patch that fixes the issue :
  > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/
  > ?id=dbdc468f35ee827cab2753caa1c660bdb832243a

  $ git log dbdc468f35ee827 -1
  commit dbdc468f35ee827cab2753caa1c660bdb832243a
  Author: Abhishek Goel 
  Date:   Wed Nov 15 14:10:02 2017 +0530

  cpupower : Fix cpupower working when cpu0 is offline
  
  cpuidle_monitor used to assume that cpu0 is always online which is not
  a valid assumption on POWER machines. This patch fixes this by getting
  the cpu on which the current thread is running, instead of always using
  cpu0 for monitoring which may not be online.
  
  Signed-off-by: Abhishek Goel 
  Signed-off-by: Shuah Khan 
  $

  Commit dbdc468f3 is available with 4.15-rc2 onwards.

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

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


[Kernel-packages] [Bug 1754078] [NEW] reenable full variable debugging information within dbgsyms with gcc vta cflags

2018-03-07 Thread Daniel Doron
Public bug reported:

Due to ubuntu kernel (Ubuntu 4.13.0-36.40-generic 4.13.13) being
compiled with ""-fno-var-tracking-assignments", the debug symbols
produced are of lesser quality, i.e. $context variables are not
available.

E.g.: (systemtap needs to be installed on the system)

$> stap -L 'kernel.function("reparent_leader")'
kernel.function("reparent_leader@/build/linux-r9581B/linux-4.13.0/kernel/exit.c:632")

on Fedora (Linux 4.15.6-300.fc27.x86_64) the same command gives:
kernel.function("reparent_leader@kernel/exit.c:632") $dead:struct list_head* 
$p:struct task_struct* $father:struct task_struct*

more info:
SystemTap Release notes (known issues)
https://sourceware.org/ml/systemtap/2017-q4/msg00096.html

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

Title:
  reenable full variable debugging information within dbgsyms with gcc
  vta cflags

Status in linux package in Ubuntu:
  New

Bug description:
  Due to ubuntu kernel (Ubuntu 4.13.0-36.40-generic 4.13.13) being
  compiled with ""-fno-var-tracking-assignments", the debug symbols
  produced are of lesser quality, i.e. $context variables are not
  available.

  E.g.: (systemtap needs to be installed on the system)

  $> stap -L 'kernel.function("reparent_leader")'
  
kernel.function("reparent_leader@/build/linux-r9581B/linux-4.13.0/kernel/exit.c:632")

  on Fedora (Linux 4.15.6-300.fc27.x86_64) the same command gives:
  kernel.function("reparent_leader@kernel/exit.c:632") $dead:struct list_head* 
$p:struct task_struct* $father:struct task_struct*

  more info:
  SystemTap Release notes (known issues)
  https://sourceware.org/ml/systemtap/2017-q4/msg00096.html

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

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


[Kernel-packages] [Bug 1754053] Re: oops in set_next_entity / ipmi_msghandler

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

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

** Tags added: kernel-da-key

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

Title:
  oops in set_next_entity / ipmi_msghandler

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

Bug description:
  Seen on a Cavium CRB1S a couple of times while running the
  com.canonical.certification::disk/disk_stress_ng_sda kernel from the
  canonical-certification-server test suite:

  [ 1823.116031] Unable to handle kernel read from unreadable memory at virtual 
address 0038
  [ 1823.124479] user pgtable: 4k pages, 48-bit VAs, pgd = 801f4bf0
  [ 1823.131068] [0038] *pgd=
  [ 1823.136080] Internal error: Oops: 9604 [#1] SMP
  [ 1823.141002] Modules linked in: nls_iso8859_1 i2c_thunderx thunderx_zip 
thunderx_edac i2c_smbus shpchp cavium_rng_vf cavi
  um_rng gpio_keys ipmi_ssif ipmi_devintf ipmi_msghandler uio_pdrv_genirq uio 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp l
  ibiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor as
  ync_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear nicvf nicpf ast 
i2c_algo_bit ttm drm_kms_helper syscopyarea sysf
  illrect aes_ce_blk sysimgblt aes_ce_cipher fb_sys_fops crc32_ce crct10dif_ce 
drm ghash_ce sha2_ce sha1_ce ahci libahci thun
  der_bgx thunder_xcv mdio_thunder thunderx_mmc mdio_cavium aes_neon_bs 
aes_neon_blk crypto_simd cryptd
  [ 1823.204136] CPU: 30 PID: 0 Comm: swapper/30 Not tainted 4.13.0-36-generic 
#40~16.04.1-Ubuntu
  [ 1823.212655] Hardware name: Cavium ThunderX CRB/To be filled by O.E.M., 
BIOS 5.11 12/12/2012
  [ 1823.221085] task: 801f7320bc00 task.stack: 801f7321
  [ 1823.227067] PC is at set_next_entity+0x28/0x5e8
  [ 1823.231640] LR is at pick_next_task_fair+0xa0/0x580
  [ 1823.236561] pc : [] lr : [] pstate: 
604001c5
  [ 1823.244026] sp : 801f73213dc0
  [ 1823.247368] x29: 801f73213dc0 x28: 801f7ca19800
  [ 1823.252731] x27: 08a76aac x26: 801f7ca19868
  [ 1823.258093] x25: 801f7320c2c0 x24: 093c8000
  [ 1823.263455] x23:  x22: 08fe1000
  [ 1823.268817] x21: 801f7ca19868 x20: 801f7ca19868
  [ 1823.274178] x19:  x18: ca622758
  [ 1823.279541] x17: 002711a2 x16: 
  [ 1823.284903] x15: 3dc0f68eb41e x14: 0001318c81308142
  [ 1823.290266] x13: 0003e800 x12: 00b4
  [ 1823.295628] x11:  x10: 00b4
  [ 1823.300990] x9 : 08aa5c98 x8 : 801f7320c760
  [ 1823.306353] x7 : 0020 x6 : 003541e45d3fef78
  [ 1823.311715] x5 : 0018 x4 : 08118e88
  [ 1823.317077] x3 : 08aa5a70 x2 : 0810cb18
  [ 1823.324394] x1 :  x0 : 08118f28
  [ 1823.331704] Process swapper/30 (pid: 0, stack limit = 0x801f7321)
  [ 1823.340536] Stack: (0x801f73213dc0 to 0x801f73214000)
  [ 1823.348292] 3dc0: 801f73213e10 08118f28  
801f7ca19868
  [ 1823.358135] 3de0: 801f73213f28 08fe1000  
093c8000
  [ 1823.367943] 3e00: 801f7320c2c0 801f7ca19868 801f73213eb0 
08a75f98
  [ 1823.377737] 3e20: 801f7ca19800 801f7320bc00 801f73213f28 
08fe1000
  [ 1823.387523] 3e40:  093c8000 801f7320c2c0 
801f7ca19800
  [ 1823.397271] 3e60: 08a76aac 093c8000 801f7ca19868 
0814a4e4
  [ 1823.406965] 3e80: 801f73213eb0 08aa5bb0 801f7320bc00 
801f73213f28
  [ 1823.416614] 3ea0: 801f7ca19800 00040d00 801f73213f40 
08a76aac
  [ 1823.426211] 3ec0: 801f7320bc00 093c9658 093c9000 
08ff1348
  [ 1823.435758] 3ee0:   801f7320bc00 

  [ 1823.445266] 3f00:   801f73213f60 
08aa5a70
  [ 1823.454714] 3f20: 08fe1000 093c9658  
00040d00
  [ 1823.464120] 3f40: 801f73213f60 08123238 08fe1000 
00040d00
  [ 1823.473470] 3f60: 801f73213fb0 08123534 0084 
001e
  [ 1823.482770] 3f80:    

  [ 1823.492031] 3fa0:  08123524 801f73213fd0 
08092308
  [ 1823.501281] 3fc0: 001e   
018831c4
  [ 1823.510542] 3fe0:    

  [ 1823.519768] Call trace:
  [ 

[Kernel-packages] [Bug 1745349] Re: Hard lockup during boot with linux-image-4.4.0-112-generic

2018-03-07 Thread Joseph Salisbury
The bisect reported the following as the first bad commit:
b0c3e8bd0405 ("x86/mm: Only set IBPB when the new thread cannot ptrace current 
thread")

I built a Xenial test kernel with a revert of this commit.  The test kernel can 
be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1745349

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.

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

Title:
  Hard lockup during boot with linux-image-4.4.0-112-generic

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

Bug description:
  Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112
  instead they show

  NMI watchdog: Watchdog detected hard lockup on cpu 0
  NMI watchdog: Watchdog detected hard lockup on cpu 1
  NMI watchdog: Watchdog detected hard lockup on cpu 3
  NMI watchdog: Watchdog detected hard lockup on cpu 2

  I cannot provide any logs of course.

  Booting with 4.4.0-109 works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lr3200 2013 F pulseaudio
  Date: Thu Jan 25 11:38:55 2018
  HibernationDevice: RESUME=UUID=8e35131d-6d40-4f4f-a3db-c7336e72cbce
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp3s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=4dc5bb0a-ab7c-48fa-ac23-bcdf23755d93 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-109-generic N/A
   linux-backports-modules-4.4.0-109-generic  N/A
   linux-firmware 1.157.15
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3601
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-C
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


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

2018-03-07 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 1754076

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

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

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

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

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

Title:
  i2c-thunderx: erroneous error message "unhandled state: 0"

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  A misleading error is occasionally emitted by the kernel.

  [Test Case]
  Boot a ThunderX system and watch for the error:

  i2c-thunderx :01:09.4: unhandled state: 0

  [Regression Risk]
  Driver is specific to a platform, and the only functional change is skipping 
the emission of an error message.

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

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


[Kernel-packages] [Bug 1754076] [NEW] i2c-thunderx: erroneous error message "unhandled state: 0"

2018-03-07 Thread dann frazier
Public bug reported:

[Impact]
A misleading error is occasionally emitted by the kernel.

[Test Case]
Boot a ThunderX system and watch for the error:

i2c-thunderx :01:09.4: unhandled state: 0

[Regression Risk]
Driver is specific to a platform, and the only functional change is skipping 
the emission of an error message.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: 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/1754076

Title:
  i2c-thunderx: erroneous error message "unhandled state: 0"

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  A misleading error is occasionally emitted by the kernel.

  [Test Case]
  Boot a ThunderX system and watch for the error:

  i2c-thunderx :01:09.4: unhandled state: 0

  [Regression Risk]
  Driver is specific to a platform, and the only functional change is skipping 
the emission of an error message.

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

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


[Kernel-packages] [Bug 1754052] [NEW] Dell Latitude 7480 press shift keys triggers random mouseclick when `Tap to click` enabled on touchpad.

2018-03-07 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

In Ubuntu 16.04.3 and 17.10.1 holding down either shift key on a Dell
Latitude 7480 causes random mouse clicks to occur without being nowhere
near the touchpad with palms. No external mouse/keyboard connected.
Disabling `Tap to click` in `Mouse & Touchpad` settings makes the
problem go away. The problem is not present in 14.04.5, whether
installed or live CD.

How to reproduce:

1. On a Dell Latitude 7480 live boot (or install) one of the following images:
- ubuntu-16.04.3-desktop-amd64.iso
- ubuntu-17.10.1-desktop-amd64.iso

2. Open `Mouse & Touchpad` and make sure `Tap to click` is enabled.
3. Click `Test Your Settings` and make sure window has focus.
4. Hold down either shift key and after a few seconds single/double clicks 
start registering.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CasperVersion: 1.376.2
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Mar  7 13:00:21 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:07a0]
LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: Dell Inc. Latitude 7480
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/30/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.8.2
dmi.board.name: 00F6D3
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.2:bd01/30/2018:svnDellInc.:pnLatitude7480:pvr:rvnDellInc.:rn00F6D3:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.name: Latitude 7480
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial
-- 
Dell Latitude 7480 press shift keys triggers random mouseclick when `Tap to 
click` enabled on touchpad.
https://bugs.launchpad.net/bugs/1754052
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 1686189] Re: External monitor connecting problem on Intel graphics card

2018-03-07 Thread mauro
Hi there,

I'm facing still this problem with kernel 4.4.0-116-generic

Any documentation I can post to help?
Dmesg?

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

Title:
  External monitor connecting problem on Intel graphics card

Status in linux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am facing a problem with Intel Graphics driver. I have external
  monitor and in display settings the second monitor is detecting but
  it's not working, so could you email me a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.4.25-040425-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 25 21:45:16 2017
  DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
  InstallationDate: Installed on 2017-04-25 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 3537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic 
root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 03JPPR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 3537
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 25 21:37:24 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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


[Kernel-packages] [Bug 1754064] Re: linux: 4.15.0-12.13 -proposed tracker

2018-03-07 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 4.15.0-12.13 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ kernel-phase-changed:Wednesday, 07. March 2018 15:30 UTC
+ kernel-phase:Packaging

** Description changed:

  This bug is for tracking the 4.15.0-12.13 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  kernel-phase-changed:Wednesday, 07. March 2018 15:30 UTC
  kernel-phase:Packaging
+ 
+ -- swm properties --
+ phase: Packaging

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

Title:
  linux: 4.15.0-12.13 -proposed tracker

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

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

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

  kernel-phase-changed:Wednesday, 07. March 2018 15:30 UTC
  kernel-phase:Packaging

  -- swm properties --
  phase: Packaging

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

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


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

2018-03-07 Thread bugproxy
--- Comment From drbr...@us.ibm.com 2018-03-07 10:21 EDT---
Kernel 4.15 is now in 18.04 daily builds. LP defects shows this as Fix 
Released. This should be closed.

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

Title:
  POWER9: NX842 module changes

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  This feature request will be used to submit NX842 changes needed to
  support on p9 - Using VAS interfaces instead of icswx to communicate
  with VAS (on PowerNV), modification of HCALL interface (on PowerVM, if
  needed) and other format changes.

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

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


[Kernel-packages] [Bug 1753144] Re: Booting kernel 4.4.0-116.140 fails

2018-03-07 Thread Simon Pepping
Installed: linux-image-4.4.120-0404120-generic, Linux kernel image for
version 4.4.120 on 32 bit x86 SMP, and associated headers.

Booting fine:

simon:~$ uname -a
Linux vuurvlinder 4.4.120-0404120-generic #201803040932 SMP Sun Mar 4 14:44:35 
UTC 2018 i686 i686 i686 GNU/Linux

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

Title:
  Booting kernel 4.4.0-116.140 fails

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Booting kernel 4.4.0-116.140 lands me in an ash shell with prompt
  'initramfs'. keyboard and mouse USB fails, so that I can do nothing.

  Error messages from module hid: 'unknown symbol __x86_indirect_thunk_XXX err 
-22' and
  'disagrees about version of __x86_indirect_thunk_XXX err -22, where XXX has 5 
or 6 different 3-letter values.

  I have gcc-5:i386 (5.4.0-6ubuntu1~16.04.6, 5.4.0-6ubuntu1~16.04.9),
  which would be correct according to bug report #1750937. Since there
  are no modules built by DKMS, there is no compilation involved in
  installation.

  I removed and reinstalled the kernel image and headers, but the problem did 
not disappear: 
  Install: linux-headers-generic:i386 (4.4.0.116.122, automatic), 
linux-image-generic:i386 (4.4.0.116.122, automatic), 
linux-headers-4.4.0-116:i386 (4.4.0-116.140, automatic), 
linux-image-extra-4.4.0-116-generic:i386 (4.4.0-116.140, automatic), 
linux-headers-4.4.0-116-generic:i386 (4.4.0-116.140, automatic), 
linux-generic:i386 (4.4.0.116.122), linux-image-4.4.0-116-generic:i386 
(4.4.0-116.140, automatic)

  Since I cannot boot into this kernel, I cannot generate a bug report,
  and there are no syslog entries.

  Description:Ubuntu 16.04.4 LTS
  Release:16.04

  linux-image-4.4.0-116-generic:
Geïnstalleerd: 4.4.0-116.140
  linux-image-extra-4.4.0-116-generic:
Geïnstalleerd: 4.4.0-116.140
  gcc-5:
Geïnstalleerd: 5.4.0-6ubuntu1~16.04.9

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

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


[Kernel-packages] [Bug 1754064] [NEW] linux: 4.15.0-12.13 -proposed tracker

2018-03-07 Thread Brad Figg
Public bug reported:

This bug is for tracking the 4.15.0-12.13 upload package. This bug will
contain status and testing results related to that upload.

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

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

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

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

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

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

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

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

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

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

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


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live

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

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

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

** Tags added: bionic

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Changed in: kernel-sru-workflow
   Status: New => 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/1754064

Title:
  linux: 4.15.0-12.13 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in 

[Kernel-packages] [Bug 1723904] Re: ubuntu-kvm-unit test failed with sprs test on ppc64le

2018-03-07 Thread David Britton
** Changed in: qemu (Ubuntu)
   Status: New => Incomplete

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

Title:
  ubuntu-kvm-unit test failed with sprs test on ppc64le

Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  The sprs test has failed on ppc64le
  This issue can be spotted on Zesty and Xenial. There is no history for this 
test on Artful

  $ sudo /bin/bash -c "MIGRATION=yes TESTNAME=sprs TIMEOUT=90s ACCEL= 
./powerpc/run powerpc/sprs.elf -smp 1 -append '-w'"
  run_migration timeout -k 1s --foreground 90s /usr/bin/qemu-system-ppc64 
-nodefaults -machine pseries,accel=kvm -bios powerpc/boot_rom.bin -display none 
-serial stdio -kernel powerpc/sprs.elf -smp 1 -append -w # -initrd 
/tmp/tmp.RUTL6E2JSi
  Settings SPRs to 0xcafefacec0debabe...
  Now migrate the VM, then press a key or send NMI...
  Checking SPRs...
  PASS: SPR 3:  0x00debabe <==> 0x00debabe
  PASS: SPR 13: 0xcafefacec0debabe <==> 0xcafefacec0debabe
  PASS: SPR 17: 0x00debabe <==> 0x00debabe
  PASS: SPR 18: 0xc0debabe <==> 0xc0debabe
  PASS: SPR 19: 0xcafefacec0debabe <==> 0xcafefacec0debabe
  PASS: SPR 29: 0xcafefacec0debabe <==> 0xcafefacec0debabe
  FAIL: SPR 61: 0x4054504440541014 <==> 00
  PASS: SPR 153:0x0a84 <==> 0x0a84
  PASS: SPR 157:0xcfcfc0cf <==> 0xcfcfc0cf
  FAIL: SPR 159:0xc0debabe <==> 00
  PASS: SPR 256:0xc0debabe <==> 0xc0debabe
  PASS: SPR 259:0xcafefacec0debabe <==> 0xcafefacec0debabe
  PASS: SPR 274:0xcafefacec0debabe <==> 0xcafefacec0debabe
  PASS: SPR 275:0xcafefacec0debabe <==> 0xcafefacec0debabe
  PASS: SPR 769:0xcafefacec0debabe <==> 0xcafefacec0debabe
  PASS: SPR 770:0xcafefacec006babe <==> 0xcafefacec006babe
  PASS: SPR 771:0xc0debabe <==> 0xc0debabe
  PASS: SPR 772:0xc0debabe <==> 0xc0debabe
  PASS: SPR 773:0xc0debabe <==> 0xc0debabe
  PASS: SPR 774:0xc0debabe <==> 0xc0debabe
  PASS: SPR 775:0xc0debabe <==> 0xc0debabe
  PASS: SPR 776:0xc0debabe <==> 0xc0debabe
  PASS: SPR 779:0xfa8b1afe <==> 0xfa8b1afe
  PASS: SPR 780:0xcafefacec0debabc <==> 0xcafefacec0debabc
  PASS: SPR 781:0xcafefacec0debabe <==> 0xcafefacec0debabe
  PASS: SPR 782:0xcafefacec0debabe <==> 0xcafefacec0debabe
  FAIL: SPR 784:0xcafefacec0debabe <==> 00
  PASS: SPR 785:0xcafefacec0debabe <==> 0xcafefacec0debabe
  PASS: SPR 786:0xcafefacec006babe <==> 0xcafefacec006babe
  PASS: SPR 787:0xc0debabe <==> 0xc0debabe
  PASS: SPR 788:0xc0debabe <==> 0xc0debabe
  PASS: SPR 789:0xc0debabe <==> 0xc0debabe
  PASS: SPR 790:0xc0debabe <==> 0xc0debabe
  PASS: SPR 791:0xc0debabe <==> 0xc0debabe
  PASS: SPR 792:0xc0debabe <==> 0xc0debabe
  PASS: SPR 795:0xfa8b1afe <==> 0xfa8b1afe
  PASS: SPR 796:0xcafefacec0debabc <==> 0xcafefacec0debabc
  PASS: SPR 797:0xcafefacec0debabe <==> 0xcafefacec0debabe
  PASS: SPR 798:0xcafefacec0debabe <==> 0xcafefacec0debabe
  PASS: SPR 800:0x8000c000 <==> 0x8000c000
  PASS: SPR 801:0x8000 <==> 0x8000
  PASS: SPR 802:0x8000c000 <==> 0x8000c000
  PASS: SPR 803:0x8000 <==> 0x8000
  PASS: SPR 804:0xcafefacec0debabe <==> 0xcafefacec0debabe
  PASS: SPR 805:0xcafefacec0debabc <==> 0xcafefacec0debabc
  PASS: SPR 806:0x8000c000 <==> 0x8000c000
  FAIL: SPR 815:0xcafefacec0debabe <==> 00
  SUMMARY: 47 tests, 4 unexpected failures

  EXIT: STATUS=3

  $ qemu-system-ppc --version
  QEMU emulator version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.16), Copyright (c) 
2003-2008 Fabrice Bellard

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-37-generic 4.10.0-37.41~16.04.1
  ProcVersionSignature: User Name 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic ppc64le
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: ppc64el
  Date: Mon Oct 16 09:16:08 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcLoadAvg: 0.02 0.14 0.17 1/1464 15093
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 1604 00:14:19651 0 EOF
   2: POSIX  ADVISORY  WRITE 2937 00:14:55331 0 EOF
   3: FLOCK  ADVISORY  WRITE 3046 00:14:67623 0 EOF
   4: POSIX  ADVISORY  WRITE 3124 

[Kernel-packages] [Bug 1747625] Re: [v4.13, mlx5_core] Oops: 0000 [#1] SMP PTI

2018-03-07 Thread Joseph Salisbury
** Tags removed: kernel-key
** Tags added: kernel-da-key

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

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

Title:
  [v4.13,mlx5_core] Oops:  [#1] SMP PTI

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

Bug description:
  PowerEdge R730
  4.13.0-26-generic #29~16.04.2-Ubuntu
  mlx5_core firmware version: 14.20.1820

  kernel trace: https://pastebin.ubuntu.com/26529021/

  Issue happened when I issued "reboot" command. Other nodes with same
  specifications and software versions didn't hit this bug.

  A new "reboot" on the node that panic'ed didn't hit the bug.

  I've set "pti=off" on all of them for now.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb  5 13:07 seq
   crw-rw 1 root audio 116, 33 Feb  5 13:07 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R730
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=2344957a-f5ed-46a7-87a5-255ab83876fb ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200 panic=30 raid=noautodetect 
modprobe.blacklist=floppy
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.14
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images xenial uec-images
  Uname: Linux 4.13.0-32-generic 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 libvirtd netdev plugdev sudo 
video
  _MarkForUpload: False
  dmi.bios.date: 09/06/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.5
  dmi.board.name: 04N3DF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A10
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.5:bd09/06/2016:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn04N3DF:rvrA10:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R730
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1754059] Re: linux: 4.15.0-12.13 -proposed tracker

2018-03-07 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   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/1754059

Title:
  linux: 4.15.0-12.13 -proposed tracker

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

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

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

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

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


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

2018-03-07 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 1754053

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: 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/1754053

Title:
  oops in set_next_entity / ipmi_msghandler

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

Bug description:
  Seen on a Cavium CRB1S a couple of times while running the
  com.canonical.certification::disk/disk_stress_ng_sda kernel from the
  canonical-certification-server test suite:

  [ 1823.116031] Unable to handle kernel read from unreadable memory at virtual 
address 0038
  [ 1823.124479] user pgtable: 4k pages, 48-bit VAs, pgd = 801f4bf0
  [ 1823.131068] [0038] *pgd=
  [ 1823.136080] Internal error: Oops: 9604 [#1] SMP
  [ 1823.141002] Modules linked in: nls_iso8859_1 i2c_thunderx thunderx_zip 
thunderx_edac i2c_smbus shpchp cavium_rng_vf cavi
  um_rng gpio_keys ipmi_ssif ipmi_devintf ipmi_msghandler uio_pdrv_genirq uio 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp l
  ibiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor as
  ync_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear nicvf nicpf ast 
i2c_algo_bit ttm drm_kms_helper syscopyarea sysf
  illrect aes_ce_blk sysimgblt aes_ce_cipher fb_sys_fops crc32_ce crct10dif_ce 
drm ghash_ce sha2_ce sha1_ce ahci libahci thun
  der_bgx thunder_xcv mdio_thunder thunderx_mmc mdio_cavium aes_neon_bs 
aes_neon_blk crypto_simd cryptd
  [ 1823.204136] CPU: 30 PID: 0 Comm: swapper/30 Not tainted 4.13.0-36-generic 
#40~16.04.1-Ubuntu
  [ 1823.212655] Hardware name: Cavium ThunderX CRB/To be filled by O.E.M., 
BIOS 5.11 12/12/2012
  [ 1823.221085] task: 801f7320bc00 task.stack: 801f7321
  [ 1823.227067] PC is at set_next_entity+0x28/0x5e8
  [ 1823.231640] LR is at pick_next_task_fair+0xa0/0x580
  [ 1823.236561] pc : [] lr : [] pstate: 
604001c5
  [ 1823.244026] sp : 801f73213dc0
  [ 1823.247368] x29: 801f73213dc0 x28: 801f7ca19800
  [ 1823.252731] x27: 08a76aac x26: 801f7ca19868
  [ 1823.258093] x25: 801f7320c2c0 x24: 093c8000
  [ 1823.263455] x23:  x22: 08fe1000
  [ 1823.268817] x21: 801f7ca19868 x20: 801f7ca19868
  [ 1823.274178] x19:  x18: ca622758
  [ 1823.279541] x17: 002711a2 x16: 
  [ 1823.284903] x15: 3dc0f68eb41e x14: 0001318c81308142
  [ 1823.290266] x13: 0003e800 x12: 00b4
  [ 1823.295628] x11:  x10: 00b4
  [ 1823.300990] x9 : 08aa5c98 x8 : 801f7320c760
  [ 1823.306353] x7 : 0020 x6 : 003541e45d3fef78
  [ 1823.311715] x5 : 0018 x4 : 08118e88
  [ 1823.317077] x3 : 08aa5a70 x2 : 0810cb18
  [ 1823.324394] x1 :  x0 : 08118f28
  [ 1823.331704] Process swapper/30 (pid: 0, stack limit = 0x801f7321)
  [ 1823.340536] Stack: (0x801f73213dc0 to 0x801f73214000)
  [ 1823.348292] 3dc0: 801f73213e10 08118f28  
801f7ca19868
  [ 1823.358135] 3de0: 801f73213f28 08fe1000  
093c8000
  [ 1823.367943] 3e00: 801f7320c2c0 801f7ca19868 801f73213eb0 
08a75f98
  [ 1823.377737] 3e20: 801f7ca19800 801f7320bc00 801f73213f28 
08fe1000
  [ 1823.387523] 3e40:  093c8000 801f7320c2c0 
801f7ca19800
  [ 1823.397271] 3e60: 08a76aac 093c8000 801f7ca19868 
0814a4e4
  [ 1823.406965] 3e80: 801f73213eb0 08aa5bb0 801f7320bc00 
801f73213f28
  [ 1823.416614] 3ea0: 801f7ca19800 00040d00 801f73213f40 
08a76aac
  [ 1823.426211] 3ec0: 801f7320bc00 093c9658 093c9000 
08ff1348
  [ 1823.435758] 3ee0:   801f7320bc00 

  [ 1823.445266] 3f00:   801f73213f60 
08aa5a70
  [ 1823.454714] 3f20: 08fe1000 093c9658  
00040d00
  [ 1823.464120] 3f40: 801f73213f60 08123238 08fe1000 
00040d00
  [ 1823.473470] 3f60: 801f73213fb0 

[Kernel-packages] [Bug 1754059] [NEW] linux: 4.15.0-12.13 -proposed tracker

2018-03-07 Thread Seth Forshee
Public bug reported:

This bug is for tracking the 4.15.0-12.13 upload package. This bug will
contain status and testing results related to that upload.

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

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

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

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

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

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

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

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

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

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

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


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live

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

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

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

** Tags added: bionic

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Changed in: kernel-sru-workflow
   Status: New => 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/1754059

Title:
  linux: 4.15.0-12.13 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  

[Kernel-packages] [Bug 1724639] Re: Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

2018-03-07 Thread Christian Staude
Sorry, but after upgrading the kernel to 4.13.0-36, the screen went bad
again. Even booting with the old kernel did not work anymore. But the
GRUB_GFXPAYLOAD_LINUX=text solution worked...

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

Title:
  Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

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

Bug description:
  Installed O.S. on Samsung NC10. Display worked O.K. in text mode so
  the install went smoothly. When the system is rebooted, however,
  switching to graphics mode results in the below described screen
  corruption:-

  Left  Hand Side 80% of screen black with a blue of white pixels and some blue 
lines at the top
  Right Hand Side 20% of screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-16-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian 918 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf034 irq 25'
 Mixer name : 'Realtek ALC272'
 Components : 'HDA:10ec0272,144dca00,0011'
 Controls  : 25
 Simple ctrls  : 12
  CurrentDesktop: LXDE
  Date: Wed Oct 18 18:30:15 2017
  HibernationDevice: RESUME=UUID=c54e130e-6625-4d96-ba75-4efaa6a9da75
  InstallationDate: Installed on 2017-10-18 (0 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=d74a58ab-e96e-4531-a2eb-13f0d1610658 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2009
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 07CA.M002.20090414.KTW
  dmi.board.name: NC10
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr07CA.M002.20090414.KTW:bd04/14/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnNC10:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNC10:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.name: NC10
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

-- 
Mailing list: https://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 1745349] Re: Hard lockup during boot with linux-image-4.4.0-112-generic

2018-03-07 Thread Lars Behrens
No success, hard locks with b0c3e8bd040

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

Title:
  Hard lockup during boot with linux-image-4.4.0-112-generic

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

Bug description:
  Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112
  instead they show

  NMI watchdog: Watchdog detected hard lockup on cpu 0
  NMI watchdog: Watchdog detected hard lockup on cpu 1
  NMI watchdog: Watchdog detected hard lockup on cpu 3
  NMI watchdog: Watchdog detected hard lockup on cpu 2

  I cannot provide any logs of course.

  Booting with 4.4.0-109 works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lr3200 2013 F pulseaudio
  Date: Thu Jan 25 11:38:55 2018
  HibernationDevice: RESUME=UUID=8e35131d-6d40-4f4f-a3db-c7336e72cbce
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp3s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=4dc5bb0a-ab7c-48fa-ac23-bcdf23755d93 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-109-generic N/A
   linux-backports-modules-4.4.0-109-generic  N/A
   linux-firmware 1.157.15
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3601
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-C
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Kernel-packages] [Bug 1754053] [NEW] oops in set_next_entity / ipmi_msghandler

2018-03-07 Thread dann frazier
Public bug reported:

Seen on a Cavium CRB1S a couple of times while running the
com.canonical.certification::disk/disk_stress_ng_sda kernel from the
canonical-certification-server test suite:

[ 1823.116031] Unable to handle kernel read from unreadable memory at virtual 
address 0038
[ 1823.124479] user pgtable: 4k pages, 48-bit VAs, pgd = 801f4bf0
[ 1823.131068] [0038] *pgd=
[ 1823.136080] Internal error: Oops: 9604 [#1] SMP
[ 1823.141002] Modules linked in: nls_iso8859_1 i2c_thunderx thunderx_zip 
thunderx_edac i2c_smbus shpchp cavium_rng_vf cavi
um_rng gpio_keys ipmi_ssif ipmi_devintf ipmi_msghandler uio_pdrv_genirq uio 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp l
ibiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor as
ync_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear nicvf nicpf ast 
i2c_algo_bit ttm drm_kms_helper syscopyarea sysf
illrect aes_ce_blk sysimgblt aes_ce_cipher fb_sys_fops crc32_ce crct10dif_ce 
drm ghash_ce sha2_ce sha1_ce ahci libahci thun
der_bgx thunder_xcv mdio_thunder thunderx_mmc mdio_cavium aes_neon_bs 
aes_neon_blk crypto_simd cryptd
[ 1823.204136] CPU: 30 PID: 0 Comm: swapper/30 Not tainted 4.13.0-36-generic 
#40~16.04.1-Ubuntu
[ 1823.212655] Hardware name: Cavium ThunderX CRB/To be filled by O.E.M., BIOS 
5.11 12/12/2012
[ 1823.221085] task: 801f7320bc00 task.stack: 801f7321
[ 1823.227067] PC is at set_next_entity+0x28/0x5e8
[ 1823.231640] LR is at pick_next_task_fair+0xa0/0x580
[ 1823.236561] pc : [] lr : [] pstate: 
604001c5
[ 1823.244026] sp : 801f73213dc0
[ 1823.247368] x29: 801f73213dc0 x28: 801f7ca19800
[ 1823.252731] x27: 08a76aac x26: 801f7ca19868
[ 1823.258093] x25: 801f7320c2c0 x24: 093c8000
[ 1823.263455] x23:  x22: 08fe1000
[ 1823.268817] x21: 801f7ca19868 x20: 801f7ca19868
[ 1823.274178] x19:  x18: ca622758
[ 1823.279541] x17: 002711a2 x16: 
[ 1823.284903] x15: 3dc0f68eb41e x14: 0001318c81308142
[ 1823.290266] x13: 0003e800 x12: 00b4
[ 1823.295628] x11:  x10: 00b4
[ 1823.300990] x9 : 08aa5c98 x8 : 801f7320c760
[ 1823.306353] x7 : 0020 x6 : 003541e45d3fef78
[ 1823.311715] x5 : 0018 x4 : 08118e88
[ 1823.317077] x3 : 08aa5a70 x2 : 0810cb18
[ 1823.324394] x1 :  x0 : 08118f28
[ 1823.331704] Process swapper/30 (pid: 0, stack limit = 0x801f7321)
[ 1823.340536] Stack: (0x801f73213dc0 to 0x801f73214000)
[ 1823.348292] 3dc0: 801f73213e10 08118f28  
801f7ca19868
[ 1823.358135] 3de0: 801f73213f28 08fe1000  
093c8000
[ 1823.367943] 3e00: 801f7320c2c0 801f7ca19868 801f73213eb0 
08a75f98
[ 1823.377737] 3e20: 801f7ca19800 801f7320bc00 801f73213f28 
08fe1000
[ 1823.387523] 3e40:  093c8000 801f7320c2c0 
801f7ca19800
[ 1823.397271] 3e60: 08a76aac 093c8000 801f7ca19868 
0814a4e4
[ 1823.406965] 3e80: 801f73213eb0 08aa5bb0 801f7320bc00 
801f73213f28
[ 1823.416614] 3ea0: 801f7ca19800 00040d00 801f73213f40 
08a76aac
[ 1823.426211] 3ec0: 801f7320bc00 093c9658 093c9000 
08ff1348
[ 1823.435758] 3ee0:   801f7320bc00 

[ 1823.445266] 3f00:   801f73213f60 
08aa5a70
[ 1823.454714] 3f20: 08fe1000 093c9658  
00040d00
[ 1823.464120] 3f40: 801f73213f60 08123238 08fe1000 
00040d00
[ 1823.473470] 3f60: 801f73213fb0 08123534 0084 
001e
[ 1823.482770] 3f80:    

[ 1823.492031] 3fa0:  08123524 801f73213fd0 
08092308
[ 1823.501281] 3fc0: 001e   
018831c4
[ 1823.510542] 3fe0:    

[ 1823.519768] Call trace:
[ 1823.523564] Exception stack(0x801f73213bd0 to 0x801f73213d00)
[ 1823.531424] 3bc0:    
0001
[ 1823.540734] 3be0: 0243d000 0810e310 604001c5 
0001
[ 1823.550059] 3c00:   801f73dbe880 
801f73dbd900
[ 1823.559408] 3c20: 0033 c000 0001 
0017
[ 1823.568763] 3c40: 0017 0017 0017 
0400
[ 1823.578098] 3c60: 0097 0001 0001 

[ 1823.587422] 3c80:  00040d00 

[Kernel-packages] [Bug 1749040] Re: KPTI support for arm64 systems

2018-03-07 Thread dann frazier
I've reproduced the CRB1S panic with the current (non-kpti) kernel and
without crypt lvm (standard MAAS install) and reported bug 1754053 to
track it. We can rule that out as being caused by kpti.

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

Title:
  KPTI support for arm64 systems

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

Bug description:
  While regression testing the current linux-hwe proposed kernel
  (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium
  ThunderX CRB. I've rebooted twice since upgrading from the current
  -updates kernel, and it's failed to boot both times, with different
  failure modes.

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

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


[Kernel-packages] [Bug 1751834] Re: Power9 DD 2.2 needs HMI fixup backport of upstream patch(d075745d893c78730e4a3b7a60fca23c2f764081) into kernel

2018-03-07 Thread Diane Brent
Manoj, Frank - what is availability outlook for this?

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

Title:
  Power9 DD 2.2 needs HMI fixup backport of upstream
  patch(d075745d893c78730e4a3b7a60fca23c2f764081) into kernel

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

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-02-23 
06:55:23 ==
  ---Problem Description---
  Power9 DD 2.2 needs HMI fixup backport of upstream 
patch(d075745d893c78730e4a3b7a60fca23c2f764081) into kernel
   
  ---uname output---
  4.15.0-10-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   commit d075745d893c78730e4a3b7a60fca23c2f764081
  Author: Paul Mackerras 
  Date:   Wed Jan 17 20:51:13 2018 +1100

  KVM: PPC: Book3S HV: Improve handling of debug-trigger HMIs on POWER9
  

  Dependancy commit, looks like already present.
  commit 5080332c2c893118dbc18755f35c8b0131cf0fc4
  Author: Michael Neuling 
  Date:   Fri Sep 15 15:25:48 2017 +1000

  powerpc/64s: Add workaround for P9 vector CI load issue
  

   
  Contact Information = sathe...@in.ibm.com 
   
  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/1751834/+subscriptions

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


[Kernel-packages] [Bug 1751798] Re: linux: 4.13.0-37.42 -proposed tracker

2018-03-07 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: In Progress => 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/1751798

Title:
  linux: 4.13.0-37.42 -proposed tracker

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

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

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

  backports: bug 1751799 (linux-azure), bug 1751801 (linux-azure-edge), bug 
1751802 (linux-gcp), bug 1751803 (linux-hwe), bug 1751805 (linux-oem)
  derivatives: bug 1751807 (linux-raspi2)
  kernel-stable-phase-changed:Tuesday, 27. February 2018 18:31 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  phase: Uploaded

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

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


[Kernel-packages] [Bug 1754043] Re: linux: 4.15.0-12.13 -proposed tracker

2018-03-07 Thread Seth Forshee
** Changed in: kernel-development-workflow
   Status: In Progress => Invalid

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

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

** Changed in: kernel-development-workflow/automated-testing
   Status: New => Invalid

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

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

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

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

** Changed in: kernel-development-workflow/promote-to-release
   Status: New => Invalid

** Changed in: kernel-development-workflow/regression-testing
   Status: New => Invalid

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

Title:
  linux: 4.15.0-12.13 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Invalid
Status in Kernel Development Workflow prepare-package series:
  Invalid
Status in Kernel Development Workflow prepare-package-meta series:
  Invalid
Status in Kernel Development Workflow prepare-package-signed series:
  Invalid
Status in Kernel Development Workflow promote-to-proposed series:
  Invalid
Status in Kernel Development Workflow promote-to-release series:
  Invalid
Status in Kernel Development Workflow regression-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

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

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

  kernel-phase:Packaging
  kernel-phase-changed:Wednesday, 07. March 2018 14:30 UTC

  -- swm properties --
  phase: Packaging

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

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


[Kernel-packages] [Bug 1754043] Re: linux: 4.15.0-12.13 -proposed tracker

2018-03-07 Thread Brad Figg
** Changed in: kernel-development-workflow/prepare-package
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 4.15.0-12.13 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ kernel-phase:Packaging
+ kernel-phase-changed:Wednesday, 07. March 2018 14:30 UTC

** Description changed:

  This bug is for tracking the 4.15.0-12.13 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  kernel-phase:Packaging
  kernel-phase-changed:Wednesday, 07. March 2018 14:30 UTC
+ 
+ -- swm properties --
+ phase: Packaging

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

Title:
  linux: 4.15.0-12.13 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Invalid
Status in Kernel Development Workflow prepare-package series:
  Invalid
Status in Kernel Development Workflow prepare-package-meta series:
  Invalid
Status in Kernel Development Workflow prepare-package-signed series:
  Invalid
Status in Kernel Development Workflow promote-to-proposed series:
  Invalid
Status in Kernel Development Workflow promote-to-release series:
  Invalid
Status in Kernel Development Workflow regression-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

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

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

  kernel-phase:Packaging
  kernel-phase-changed:Wednesday, 07. March 2018 14:30 UTC

  -- swm properties --
  phase: Packaging

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

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


[Kernel-packages] [Bug 1754047] [NEW] Fix spurious zeroing of r0

2018-03-07 Thread Frank Heimes
Private bug reported:

The kernel patch(es) of LP 1743560
'KVM patches for s390x to provide facility bits 81 (ppa15) and 82 (bpb)'
(accepted upstream)
introduced a problem due to spurious zeroing of r0.

The following fix is addressing this:
s390/entry.S: fix spurious zeroing of r0
https://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git/commit/?h=fixes=d3f468963cd6fd6d2aa5e26aed8b24232096d0e1

If our X, A and B kernels are affected by the above issue (what is
probably the case if the upstream patches got used), then the fix/patch
(commit d3f468963cd6fd6d2aa5e26aed8b24232096d0e1) needs to be applied,
too.

** Affects: ubuntu-z-systems
 Importance: Critical
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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


** Tags: s390x

** Information type changed from Public to Private

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

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

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

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

Title:
  Fix spurious zeroing of r0

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

Bug description:
  The kernel patch(es) of LP 1743560
  'KVM patches for s390x to provide facility bits 81 (ppa15) and 82 (bpb)'
  (accepted upstream)
  introduced a problem due to spurious zeroing of r0.

  The following fix is addressing this:
  s390/entry.S: fix spurious zeroing of r0
  
https://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git/commit/?h=fixes=d3f468963cd6fd6d2aa5e26aed8b24232096d0e1

  If our X, A and B kernels are affected by the above issue (what is
  probably the case if the upstream patches got used), then the
  fix/patch (commit d3f468963cd6fd6d2aa5e26aed8b24232096d0e1) needs to
  be applied, too.

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

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


[Kernel-packages] [Bug 1754043] [NEW] linux: 4.15.0-12.13 -proposed tracker

2018-03-07 Thread Seth Forshee
Public bug reported:

This bug is for tracking the 4.15.0-12.13 upload package. This bug will
contain status and testing results related to that upload.

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

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

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

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

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

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

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

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

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

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

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


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live

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

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

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

** Tags added: bionic

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Title:
  linux: 4.15.0-12.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status 

[Kernel-packages] [Bug 1751835] Kdump console logs

2018-03-07 Thread bugproxy
*** This bug is a duplicate of bug 1743529 ***
https://bugs.launchpad.net/bugs/1743529

Default Comment by Bridge

** Attachment added: "Kdump console logs"
   
https://bugs.launchpad.net/bugs/1751835/+attachment/5071694/+files/kdump_failure_on_proposed_4.15.txt

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

Title:
  Ubuntu 18.04 kdump does not work on bionic-proposed 4.15 ppc64el with
  AC922

Status in The Ubuntu-power-systems project:
  New
Status in kexec-tools package in Ubuntu:
  New

Bug description:
  no guest was running, only Ubuntu 18.04 Host installed and trying
  kdump only on the host

  ===
  tried on the ubuntu released proposed kernel 4.15.0-10-generic and kdump 
process was able to proceed (did not dump complete vmcore though) but hit 
issue, please check below console log
  

  root@ltciofvtr-spoon4:~# dmesg | grep -i crash 
  [0.00] Reserving 6144MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] Kernel command line: 
root=UUID=749429f9-83b9-4776-9a3e-147e297cdf99 ro quiet splash crashkernel=6144M
  root@ltciofvtr-spoon4:~# dmesg | grep -i reserv
  [0.00] Reserving 6144MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [0.00]   DMA zone: 0 pages reserved
  [0.00]   DMA zone: 0 pages reserved
  [0.00] Memory: 502952192K/536870912K available (13376K kernel code, 
2048K rwdata, 3648K rodata, 4800K init, 3037K bss, 7065344K reserved, 26853376K 
cma-reserved)
  root@ltciofvtr-spoon4:~# uname -a
  Linux ltciofvtr-spoon4 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:21:52 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
  root@ltciofvtr-spoon4:~# kdump
  kdump kdump-config  
  root@ltciofvtr-spoon4:~# kdump
  kdump kdump-config  
  root@ltciofvtr-spoon4:~# kdump-config 
  Usage: /usr/sbin/kdump-config 
{help|test|show|status|load|unload|savecore|propagate|symlinks kernel-version}
  root@ltciofvtr-spoon4:~# kdump-config  status
  current state   : ready to kdump
  root@ltciofvtr-spoon4:~# echo 1 > /proc/sys/kernel/sysrq 
  root@ltciofvtr-spoon4:~# echo c > /proc/sysrq-trigger 
  [  164.604204] sysrq: SysRq : Trigger a crash
  [  164.604264] Unable to handle kernel paging request for data at address 
0x
  [  164.604395] Faulting instruction address: 0xc07ea268
  [  164.604481] Oops: Kernel access of bad area, sig: 11 [#1]
  [  164.604559] LE SMP NR_CPUS=2048 NUMA PowerNV
  [  164.604628] Modules linked in: idt_89hpesx ofpart ipmi_powernv 
ipmi_devintf ipmi_msghandler ibmpowernv cmdlinepart vmx_crypto powernv_flash 
at24 uio_pdrv_genirq uio mtd opal_prd crct10dif_vpmsum sch_fq_codel ip_tables 
x_tables autofs4 mlx5_ib ib_core mlx5_core bnx2x ast i2c_algo_bit ttm 
drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops mdio ahci mlxfw 
libcrc32c crc32c_vpmsum drm tg3 libahci devlink
  [  164.605176] CPU: 72 PID: 3444 Comm: bash Not tainted 4.15.0-10-generic 
#11-Ubuntu
  [  164.605305] NIP:  c07ea268 LR: c07eb1a8 CTR: 
c07ea240
  [  164.605413] REGS: c0002038f8c2f9f0 TRAP: 0300   Not tainted  
(4.15.0-10-generic)
  [  164.605496] MSR:  90009033   CR: 2822 
 XER: 2004
  [  164.605641] CFAR: c07eb1a4 DAR:  DSISR: 4200 
SOFTE: 1 
  [  164.605641] GPR00: c07eb1a8 c0002038f8c2fc70 c16ea600 
0063 
  [  164.605641] GPR04: c000203993d0ce18 c000203993d24368 90009033 
0808 
  [  164.605641] GPR08: 0007 0001  
90001003 
  [  164.605641] GPR12: c07ea240 c7a51800 08f7fbb8e008 
 
  [  164.605641] GPR16: 08f7fb19e9f0 08f7fb231998 08f7fb2319d0 
08f7fb268204 
  [  164.605641] GPR20:  0001  
7fffed1e1b54 
  [  164.605641] GPR24: 7fffed1e1b50 08f7fb26afc4 c15e9930 
0002 
  [  164.605641] GPR28: 0063 0004 c1572a9c 
c15e9cd0 
  [  164.606714] NIP [c07ea268] sysrq_handle_crash+0x28/0x30
  [  164.606796] LR [c07eb1a8] __handle_sysrq+0xf8/0x2c0
  [  164.606865] Call Trace:
  [  164.606919] [c0002038f8c2fc70] [c07eb188] 
__handle_sysrq+0xd8/0x2c0 (unreliable)
  [  164.607043] [c0002038f8c2fd10] [c07eb9b4] 
write_sysrq_trigger+0x64/0x90
  [  164.607152] [c0002038f8c2fd40] [c047c548] proc_reg_write+0x88/0xd0
  [  164.607252] [c0002038f8c2fd70] [c03cf8dc] __vfs_write+0x3c/0x70
  [  164.607347] [c0002038f8c2fd90] [c03cfb38] vfs_write+0xd8/0x220
  [  164.607445] [c0002038f8c2fde0] [c03cfe58] SyS_write+0x68/0x110
  [  164.607545] [c0002038f8c2fe30] [c000b184] system_call+0x58/0x6c
  [  

[Kernel-packages] [Bug 1751994] Re: ppc64el: Support firmware disable of RFI flush

2018-03-07 Thread Seth Forshee
** Also affects: linux (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

** Also affects: linux (Ubuntu Bionic)
   Importance: High
 Assignee: Canonical Kernel Team (canonical-kernel-team)
   Status: Triaged

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

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

Title:
  ppc64el: Support firmware disable of RFI flush

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

Bug description:
  == Comment: #0 - Breno Leitao  - 2018-02-26 13:59:55 ==
  Hi Canonical,

  We still need some changes regarding spectre and meltdown. We need to
  backport the following commit to all supported kernel.

  I undertand that the backport for kernel 4.XX should be trivial. Not
  sure about kernel 3.13 yet.

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=582605a429e20ae68fd0b041b2e840af296edd08
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb0a2d2620ae431c543963c8c7f08f597366fc60

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

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


[Kernel-packages] [Bug 488720] Re: Suspend/resume with nvidia driver fails

2018-03-07 Thread Mark Yisri
Hi, I know this is an old bug, but I'm experiencing this problem on the
latest 4.13 kernel. I didn't have the issue on an older 4.10 kernel.

What I have found is that if I switch with Ctrl+Alt+F1, then suspend,
then resume and switch back to X, it works. If I just suspend I'm left
with a black 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/488720

Title:
  Suspend/resume with nvidia driver fails

Status in Linux:
  Fix Released
Status in Mactel Support:
  Invalid
Status in pm-utils:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in pm-utils package in Ubuntu:
  Fix Released
Status in linux source package in Lucid:
  Invalid
Status in pm-utils source package in Lucid:
  Fix Released

Bug description:
  Linux Kernel 2.6.32-5 completely fails to resume in my Macbook 5.1
  I am reporting this bug, because with previous version of this kernel 
(2.6.32-*), resume was long and sometimes machine went back to suspend but it 
always succed in resuming.
  Now, it is impossible to resume because the screen stays black and I am 
oblige to force the shutdown with the power button
  I am on:
  Ubuntu lucid (development branch)
  10.04

  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  demoneivo   1968 F pulseaudio
  CRDA: Error: [Errno 2] Nessun file o directory
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xd338 irq 16'
 Mixer name : 'Realtek ALC889A'
 Components : 'HDA:10ec0885,106b3f00,00100103'
 Controls  : 36
 Simple ctrls  : 20
  Date: Thu Nov 26 12:50:26 2009
  DistroRelease: Ubuntu 10.04
  HibernationDevice: RESUME=UUID=cc355bac-f00f-457c-99b0-4ddbb235f90e
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  MachineType: Apple Inc. MacBook5,1
  NonfreeKernelModules: wl nvidia
  Package: linux-image-2.6.32-5-generic 2.6.32-5.6
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-generic 
root=UUID=2a913905-8671-4792-b1a6-c335d9cb798d ro quiet splash
  ProcEnviron:
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-5.6-generic
  Regression: Yes
  RelatedPackageVersions: linux-firmware 1.25
  Reproducible: Yes
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Tags:  regression-potential
  TestedUpstream: Yes
  Uname: Linux 2.6.32-5-generic x86_64
  dmi.bios.date: 10/29/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB51.88Z.0073.B06.0810291326
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F42D89C8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Proto
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F42D89C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB51.88Z.0073.B06.0810291326:bd10/29/08:svnAppleInc.:pnMacBook5,1:pvr1.0:rvnAppleInc.:rnMac-F42D89C8:rvrProto:cvnAppleInc.:ct10:cvrMac-F42D89C8:
  dmi.product.name: MacBook5,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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


[Kernel-packages] [Bug 1750786] Re: stress-ng enosys stressor triggers a kernel BUG

2018-03-07 Thread Colin Ian King
Tested with i386 and amd64 arches, fix works. Verified.

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

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

Title:
  stress-ng enosys stressor triggers a kernel BUG

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

Bug description:
  We are seeing kernel BUGs when running the stress-ng enosys stresser
  on released trusty kernels.

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

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


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

2018-03-07 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/1754016

Title:
  watchdog: BUG: soft lockup - CPU#5 stuck for 22s! [kworker/5:4:4887]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  apear after reboot of new laptop installation

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11 [modified: 
boot/vmlinuz-4.15.0-10-generic]
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  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:  gdm1217 F pulseaudio
lenkaii1538 F pulseaudio
  Date: Wed Mar  7 13:53:15 2018
  Failure: oops
  HibernationDevice: RESUME=UUID=107145f9-3218-4291-a695-25f53618594a
  InstallationDate: Installed on 2018-03-07 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0cf3:e007 Atheros Communications, Inc. 
   Bus 001 Device 004: ID 0bda:568c Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 7520
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=/dev/mapper/ubuntu--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: watchdog: BUG: soft lockup - CPU#5 stuck for 22s! [kworker/5:4:4887]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/14/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 0GC6C7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: D20002763
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd06/14/2017:svnDellInc.:pnPrecision7520:pvr:rvnDellInc.:rn0GC6C7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 7520
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1754016] Re: watchdog: BUG: soft lockup - CPU#5 stuck for 22s! [kworker/5:4:4887]

2018-03-07 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-rc4

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

Title:
  watchdog: BUG: soft lockup - CPU#5 stuck for 22s! [kworker/5:4:4887]

Status in linux package in Ubuntu:
  New

Bug description:
  apear after reboot of new laptop installation

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11 [modified: 
boot/vmlinuz-4.15.0-10-generic]
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  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:  gdm1217 F pulseaudio
lenkaii1538 F pulseaudio
  Date: Wed Mar  7 13:53:15 2018
  Failure: oops
  HibernationDevice: RESUME=UUID=107145f9-3218-4291-a695-25f53618594a
  InstallationDate: Installed on 2018-03-07 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0cf3:e007 Atheros Communications, Inc. 
   Bus 001 Device 004: ID 0bda:568c Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 7520
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=/dev/mapper/ubuntu--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: watchdog: BUG: soft lockup - CPU#5 stuck for 22s! [kworker/5:4:4887]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/14/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 0GC6C7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: D20002763
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd06/14/2017:svnDellInc.:pnPrecision7520:pvr:rvnDellInc.:rn0GC6C7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 7520
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1754017] Re: watchdog: BUG: soft lockup - CPU#5 stuck for 23s! [kworker/5:4:4887]

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

** This bug has been marked a duplicate of bug 1754016
   watchdog: BUG: soft lockup - CPU#5 stuck for 22s! [kworker/5:4:4887]

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

Title:
  watchdog: BUG: soft lockup - CPU#5 stuck for 23s! [kworker/5:4:4887]

Status in linux package in Ubuntu:
  New

Bug description:
  n-A

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11 [modified: 
boot/vmlinuz-4.15.0-10-generic]
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  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:  gdm1217 F pulseaudio
lenkaii1538 F pulseaudio
  Date: Wed Mar  7 13:58:20 2018
  Failure: oops
  HibernationDevice: RESUME=UUID=107145f9-3218-4291-a695-25f53618594a
  InstallationDate: Installed on 2018-03-07 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0cf3:e007 Atheros Communications, Inc. 
   Bus 001 Device 004: ID 0bda:568c Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 7520
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=/dev/mapper/ubuntu--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: watchdog: BUG: soft lockup - CPU#5 stuck for 23s! [kworker/5:4:4887]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/14/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 0GC6C7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: D20002763
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd06/14/2017:svnDellInc.:pnPrecision7520:pvr:rvnDellInc.:rn0GC6C7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 7520
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1754017] [NEW] watchdog: BUG: soft lockup - CPU#5 stuck for 23s! [kworker/5:4:4887]

2018-03-07 Thread Lenka
Public bug reported:

n-A

ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-10-generic 4.15.0-10.11 [modified: 
boot/vmlinuz-4.15.0-10-generic]
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
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:  gdm1217 F pulseaudio
  lenkaii1538 F pulseaudio
Date: Wed Mar  7 13:58:20 2018
Failure: oops
HibernationDevice: RESUME=UUID=107145f9-3218-4291-a695-25f53618594a
InstallationDate: Installed on 2018-03-07 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 0cf3:e007 Atheros Communications, Inc. 
 Bus 001 Device 004: ID 0bda:568c Realtek Semiconductor Corp. 
 Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Precision 7520
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=/dev/mapper/ubuntu--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: watchdog: BUG: soft lockup - CPU#5 stuck for 23s! [kworker/5:4:4887]
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/14/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.6.0
dmi.board.name: 0GC6C7
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.asset.tag: D20002763
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd06/14/2017:svnDellInc.:pnPrecision7520:pvr:rvnDellInc.:rn0GC6C7:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 7520
dmi.sys.vendor: Dell Inc.

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

Title:
  watchdog: BUG: soft lockup - CPU#5 stuck for 23s! [kworker/5:4:4887]

Status in linux package in Ubuntu:
  New

Bug description:
  n-A

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11 [modified: 
boot/vmlinuz-4.15.0-10-generic]
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  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:  gdm1217 F pulseaudio
lenkaii1538 F pulseaudio
  Date: Wed Mar  7 13:58:20 2018
  Failure: oops
  HibernationDevice: RESUME=UUID=107145f9-3218-4291-a695-25f53618594a
  InstallationDate: Installed on 2018-03-07 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0cf3:e007 Atheros Communications, Inc. 
   Bus 001 Device 004: ID 0bda:568c Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 7520
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=/dev/mapper/ubuntu--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: watchdog: BUG: soft lockup - CPU#5 stuck for 23s! [kworker/5:4:4887]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/14/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 0GC6C7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: D20002763
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd06/14/2017:svnDellInc.:pnPrecision7520:pvr:rvnDellInc.:rn0GC6C7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 7520
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1754016] [NEW] watchdog: BUG: soft lockup - CPU#5 stuck for 22s! [kworker/5:4:4887]

2018-03-07 Thread Lenka
Public bug reported:

apear after reboot of new laptop installation

ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-10-generic 4.15.0-10.11 [modified: 
boot/vmlinuz-4.15.0-10-generic]
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
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:  gdm1217 F pulseaudio
  lenkaii1538 F pulseaudio
Date: Wed Mar  7 13:53:15 2018
Failure: oops
HibernationDevice: RESUME=UUID=107145f9-3218-4291-a695-25f53618594a
InstallationDate: Installed on 2018-03-07 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 0cf3:e007 Atheros Communications, Inc. 
 Bus 001 Device 004: ID 0bda:568c Realtek Semiconductor Corp. 
 Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Precision 7520
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=/dev/mapper/ubuntu--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: watchdog: BUG: soft lockup - CPU#5 stuck for 22s! [kworker/5:4:4887]
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/14/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.6.0
dmi.board.name: 0GC6C7
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.asset.tag: D20002763
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd06/14/2017:svnDellInc.:pnPrecision7520:pvr:rvnDellInc.:rn0GC6C7:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 7520
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-kerneloops 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/1754016

Title:
  watchdog: BUG: soft lockup - CPU#5 stuck for 22s! [kworker/5:4:4887]

Status in linux package in Ubuntu:
  New

Bug description:
  apear after reboot of new laptop installation

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11 [modified: 
boot/vmlinuz-4.15.0-10-generic]
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  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:  gdm1217 F pulseaudio
lenkaii1538 F pulseaudio
  Date: Wed Mar  7 13:53:15 2018
  Failure: oops
  HibernationDevice: RESUME=UUID=107145f9-3218-4291-a695-25f53618594a
  InstallationDate: Installed on 2018-03-07 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0cf3:e007 Atheros Communications, Inc. 
   Bus 001 Device 004: ID 0bda:568c Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 7520
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=/dev/mapper/ubuntu--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: watchdog: BUG: soft lockup - CPU#5 stuck for 22s! [kworker/5:4:4887]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/14/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 0GC6C7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: D20002763
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd06/14/2017:svnDellInc.:pnPrecision7520:pvr:rvnDellInc.:rn0GC6C7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 7520
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1726362] Re: CONFIG_EFI=y on armhf

2018-03-07 Thread Seth Forshee
** Changed in: linux (Ubuntu Bionic)
   Status: Fix Committed => 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/1726362

Title:
  CONFIG_EFI=y on armhf

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

Bug description:
  [Impact]

   * Please enable CONFIG_EFI on the armhf generic kernels
   * This may enable using armhf kernels with an armhf cloud-image and 
qemu-efi-arm under qemu-system-arm

  [Test Case]

   * Kernel config has CONFIG_EFI=y

  [Regression Potential]

   * Kernel config/image/modules will become larger in size due to more
  features enabled on the arm kernel.

  [Other Info]
   
   * qemu-efi-arm is available, experimental cloud-images are being produced, 
but not yet released to cloud-images.
   * expectations for cloud images to land into bb and then enabled on 
xenial/zesty/artful as well.

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

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


[Kernel-packages] [Bug 1753708] Re: Ubuntu18.04:PowerPC - Set Transparent Huge Pages (THP) by default to "always"

2018-03-07 Thread Thadeu Lima de Souza Cascardo
We changed the default to madvise, as using it as always results in
performance regressions in our testing. See bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1703742.

Have you run any specific tests on Power Systems that would justify
changing the setting for ppc64el only?

Thanks.
Cascardo.

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

Title:
  Ubuntu18.04:PowerPC - Set Transparent Huge Pages (THP) by default to
  "always"

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:
  == Comment: #0 - Praveen K. Pandey  - 2018-03-06 
02:06:31 ==
  Problem Description :

  PowerPC systems running Ubuntu18.04 have Transparent Huge Pages (THP) 
  always set to "madvise". It should be by default set to "always". 

  Reproducible Step:

  1-  Install Ubuntu 18.04 on PowerPC box 
  2- cat /sys/kernel/mm/transparent_hugepage/enabled
  3- grep  "TRANSPARENT" /boot/config-$(uname -r)

  it is set to  madvise

  LOG:

  root@system:~# grep  "TRANSPARENT" /boot/config-$(uname -r)
  CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE=y
  CONFIG_TRANSPARENT_HUGEPAGE=y
  # CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS is not set
  CONFIG_TRANSPARENT_HUGEPAGE_MADVISE=y
  CONFIG_TRANSPARENT_HUGE_PAGECACHE=y
  root@system:~# cat /sys/kernel/mm/transparent_hugepage/enabled
  always [madvise] never
  root@system:~# 

  Regards
  Praveen

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

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


[Kernel-packages] [Bug 1724639] Re: Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

2018-03-07 Thread Christian Staude
I had the same issue on an Acer Aspire One with a fresh Lubuntu 17.10.1 
install. Trying to prevent the system from continuously going to sleep I set 
"HandleSuspendKey" and "HandleLidSwitch" to ignore in /etc/systemd/login.conf. 
After that the screen problem appeared.
When I commented out the HandleSuspendKey again, everything worked fine!

Hope that helps

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

Title:
  Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

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

Bug description:
  Installed O.S. on Samsung NC10. Display worked O.K. in text mode so
  the install went smoothly. When the system is rebooted, however,
  switching to graphics mode results in the below described screen
  corruption:-

  Left  Hand Side 80% of screen black with a blue of white pixels and some blue 
lines at the top
  Right Hand Side 20% of screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-16-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian 918 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf034 irq 25'
 Mixer name : 'Realtek ALC272'
 Components : 'HDA:10ec0272,144dca00,0011'
 Controls  : 25
 Simple ctrls  : 12
  CurrentDesktop: LXDE
  Date: Wed Oct 18 18:30:15 2017
  HibernationDevice: RESUME=UUID=c54e130e-6625-4d96-ba75-4efaa6a9da75
  InstallationDate: Installed on 2017-10-18 (0 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=d74a58ab-e96e-4531-a2eb-13f0d1610658 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2009
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 07CA.M002.20090414.KTW
  dmi.board.name: NC10
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr07CA.M002.20090414.KTW:bd04/14/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnNC10:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNC10:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.name: NC10
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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


[Kernel-packages] [Bug 1751714] Re: [Feature] CFL/CNL (PCH:CNP-H): New GPIO Commit added (GPIO Driver needed)

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

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

Title:
  [Feature] CFL/CNL (PCH:CNP-H): New GPIO Commit added (GPIO Driver
  needed)

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

Bug description:
  Description:
  a commit id missed in LP#1685729. [CNL] - New device IDs for CNL

  v4.16
  cb5fda413e1d

  @Canonical, please take it into 18.04.

  Target Kernel: 4.16
  Target Release: 18.04

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

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


[Kernel-packages] [Bug 1751714] Re: [Feature] CFL/CNL (PCH:CNP-H): New GPIO Commit added (GPIO Driver needed)

2018-03-07 Thread Seth Forshee
It looks like at least two prerequisite patches are neeed.

03c4749dd6c7 gpio / ACPI: Drop unnecessary ACPI GPIO to Linux GPIO translation
a60eac3239f0 pinctrl: intel: Allow custom GPIO base for pad groups

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

Title:
  [Feature] CFL/CNL (PCH:CNP-H): New GPIO Commit added (GPIO Driver
  needed)

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

Bug description:
  Description:
  a commit id missed in LP#1685729. [CNL] - New device IDs for CNL

  v4.16
  cb5fda413e1d

  @Canonical, please take it into 18.04.

  Target Kernel: 4.16
  Target Release: 18.04

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

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


[Kernel-packages] [Bug 1751798] Re: linux: 4.13.0-37.42 -proposed tracker

2018-03-07 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Kleber Sacilotto de Souza (kleber-souza) => Khaled El Mously 
(kmously)

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

Title:
  linux: 4.13.0-37.42 -proposed tracker

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

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

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

  backports: bug 1751799 (linux-azure), bug 1751801 (linux-azure-edge), bug 
1751802 (linux-gcp), bug 1751803 (linux-hwe), bug 1751805 (linux-oem)
  derivatives: bug 1751807 (linux-raspi2)
  kernel-stable-phase-changed:Tuesday, 27. February 2018 18:31 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  phase: Uploaded

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

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


[Kernel-packages] [Bug 1751798] Re: linux: 4.13.0-37.42 -proposed tracker

2018-03-07 Thread Kleber Sacilotto de Souza
** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Khaled El Mously (kmously) => Kleber Sacilotto de Souza 
(kleber-souza)

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Khaled El Mously (kmously) => Kleber Sacilotto de Souza 
(kleber-souza)

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Khaled El Mously (kmously) => Kleber Sacilotto de Souza 
(kleber-souza)

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

Title:
  linux: 4.13.0-37.42 -proposed tracker

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

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

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

  backports: bug 1751799 (linux-azure), bug 1751801 (linux-azure-edge), bug 
1751802 (linux-gcp), bug 1751803 (linux-hwe), bug 1751805 (linux-oem)
  derivatives: bug 1751807 (linux-raspi2)
  kernel-stable-phase-changed:Tuesday, 27. February 2018 18:31 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  phase: Uploaded

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

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


[Kernel-packages] [Bug 1753950] Re: Ubuntu18.04[P9, WSP]: While running ltp kernel_misc test hitting cpu warn_on on unregister_blkdev+0xac/0x300

2018-03-07 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-rc4

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

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

Title:
  Ubuntu18.04[P9, WSP]:  While running ltp  kernel_misc test hitting cpu
  warn_on on  unregister_blkdev+0xac/0x300

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Praveen K. Pandey  - 2018-03-06 
05:19:10 ==
  Problem Description :

  While running ltp  kernel_misc  test hitting  cpu warn_on on
  unregister_blkdev

  Reproducible Step:

  1- Install WSP system with Ubuntu18.04
  2- get ltp from github 

  a- git clone https://github.com/linux-test-project/ltp.git
  b-cd ltp 
  c- make autotools
  d- ./configure
  e- make
  f- make install
  g- cd /opt/ltp
  h- ./runltp -f kernel_misc

  LOG:


  [87195.381004] WARNING: CPU: 8 PID: 25873 at 
/build/linux-jWa1Fv/linux-4.15.0/block/genhd.c:400 unregister_blkdev+0xac/0x300
  [87195.381166] Modules linked in: ltp_block_dev(OE) sctp nls_iso8859_1 ntfs 
btrfs zstd_compress xor raid6_pq xfs libcrc32c idt_89hpesx ofpart at24 
uio_pdrv_genirq cmdlinepart powernv_flash ibmpowernv vmx_crypto mtd 
ipmi_powernv ipmi_devintf ipmi_msghandler crct10dif_vpmsum opal_prd uio 
sch_fq_codel ip_tables x_tables autofs4 ast i2c_algo_bit ttm drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops ahci crc32c_vpmsum drm tg3 
libahci [last unloaded: ltp_fw_load]
  [87195.381750] CPU: 8 PID: 25873 Comm: block_dev Tainted: G   OE
4.15.0-10-generic #11-Ubuntu
  [87195.381869] NIP:  c069808c LR: c069803c CTR: 
c0697fe0
  [87195.381967] REGS: c01cf0bf3970 TRAP: 0700   Tainted: G   OE
 (4.15.0-10-generic)
  [87195.382078] MSR:  90029033   CR: 28000822 
 XER: 2004
  [87195.382177] CFAR: c069805c SOFTE: 1 
  [87195.382177] GPR00: c069803c c01cf0bf3bf0 c16ea600 
 
  [87195.382177] GPR04: c00819e113d8 000d 636f6c62 
c01cee876a00 
  [87195.382177] GPR08: c1a0f4b8   
c00819e111b8 
  [87195.382177] GPR12: c0697fe0 cfa85800  
 
  [87195.382177] GPR16:    
 
  [87195.382177] GPR20: 07399d9b8c10 07399d9b8c28 7fffd61064a4 
07399d9b8c50 
  [87195.382177] GPR24: 07399d9b8cf0 07399d9d0010 c01cf0bf3e00 
00fc 
  [87195.382177] GPR28: c00819e113d8 c15e2a60  
 
  [87195.383098] NIP [c069808c] unregister_blkdev+0xac/0x300
  [87195.383180] LR [c069803c] unregister_blkdev+0x5c/0x300
  [87195.383266] Call Trace:
  [87195.383302] [c01cf0bf3bf0] [c069803c] 
unregister_blkdev+0x5c/0x300 (unreliable)
  [87195.383424] [c01cf0bf3c30] [c00819e10790] sys_tcase+0x558/0xbe0 
[ltp_block_dev]
  [87195.383542] [c01cf0bf3ce0] [c08530dc] dev_attr_store+0x3c/0x60
  [87195.383628] [c01cf0bf3d00] [c049a6b4] sysfs_kf_write+0x64/0x90
  [87195.383726] [c01cf0bf3d20] [c04993ac] 
kernfs_fop_write+0x1ac/0x270
  [87195.383824] [c01cf0bf3d70] [c03cf8dc] __vfs_write+0x3c/0x70
  [87195.383919] [c01cf0bf3d90] [c03cfb38] vfs_write+0xd8/0x220
  [87195.384009] [c01cf0bf3de0] [c03cfe58] SyS_write+0x68/0x110
  [87195.384103] [c01cf0bf3e30] [c000b184] system_call+0x58/0x6c
  [87195.384196] Instruction dump:
  [87195.384241] 419e0030 812a0008 7f89f000 409e0018 48000144 813f0008 7f89f040 
419e0058 
  [87195.384347] 7feafb78 ebea 2fbf 409effe8 <0fe0> 7fa3eb78 
3be0 48668431 
  [87195.384459] ---[ end trace fdc18fb4b5cc1498 ]---

  
  Regards
  Praveen

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

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


[Kernel-packages] [Bug 1745349] Re: Hard lockup during boot with linux-image-4.4.0-112-generic

2018-03-07 Thread Joseph Salisbury
I built the next test kernel, up to the following commit:
b0c3e8bd040546f4dfedff77e3a171a9b15c6571

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

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

Thanks in advance

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

Title:
  Hard lockup during boot with linux-image-4.4.0-112-generic

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

Bug description:
  Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112
  instead they show

  NMI watchdog: Watchdog detected hard lockup on cpu 0
  NMI watchdog: Watchdog detected hard lockup on cpu 1
  NMI watchdog: Watchdog detected hard lockup on cpu 3
  NMI watchdog: Watchdog detected hard lockup on cpu 2

  I cannot provide any logs of course.

  Booting with 4.4.0-109 works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lr3200 2013 F pulseaudio
  Date: Thu Jan 25 11:38:55 2018
  HibernationDevice: RESUME=UUID=8e35131d-6d40-4f4f-a3db-c7336e72cbce
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp3s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=4dc5bb0a-ab7c-48fa-ac23-bcdf23755d93 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-109-generic N/A
   linux-backports-modules-4.4.0-109-generic  N/A
   linux-firmware 1.157.15
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3601
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-C
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13

2018-03-07 Thread Dr. Jens Harbott
The slow leak will probably be tolerable for the time being, having
those two patches added to the kernel would surely be a pretty valuable
step that I think should be done now. My target still is Xenial with the
hwe kernel, though. If you need to go via Artful to fix that, well, go
ahead.

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

Title:
  Servers going OOM after updating kernel from 4.10 to 4.13

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

Bug description:
  We are seeing this on multiple servers after upgrading from previous
  4.10 series HWE kernels to the new 4.13 HWE series. With the new
  kernel, free memory is continously decreasing at a high rate and the
  servers start swapping and finally OOMing services within days. With
  the 4.10 kernel, decrease of free memory is slower and stabilizes
  after a while.

  Latest kernel tested is linux-image-4.13.0-32-generic but the issue
  also affects older kernels from that series, tested back to linux-
  image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic.

  The servers are running as OpenStack controller nodes using either
  Ocata or Pike UCA plus ceph. See attached graph for the memory
  behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Feb  9 09:45:50 2018
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1753987] [NEW] Unable to start ubuntu_zfs_xfs_generic test on Bionic

2018-03-07 Thread Po-Hsu Lin
Public bug reported:

This is not a kernel issue.

The problem was caused by glibc-2.27, and fixed with commit 8041435de7
in xfsprogs-dev


The compilation will fail with:
copy_file_range.c:46:1: error: conflicting types for ‘copy_file_range’
copy_file_range(int fd, loff_t *src, loff_t *dst, size_t len)
^~~
In file included from ../include/platform_defs.h:33:0,
from ../include/project.h:21,
from ../include/input.h:24,
from copy_file_range.c:23:
/usr/include/unistd.h:1110:9: note: previous declaration of 
‘copy_file_range’ was here
ssize_t copy_file_range (int __infd, __off64_t *__pinoff,
^~~
make[3]: *** [../include/buildrules:60: copy_file_range.o] Error 1

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-11-generic 4.15.0-11.12
ProcVersionSignature: User Name 4.15.0-11.12-generic 4.15.5
Uname: Linux 4.15.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Mar  7 08:40 seq
 crw-rw 1 root audio 116, 33 Mar  7 08:40 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:
CurrentDmesg:
 
Date: Wed Mar  7 10:18:06 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
JournalErrors:
 -- Logs begin at Wed 2018-03-07 08:40:01 UTC, end at Wed 2018-03-07 10:17:01 
UTC. --
 Mar 07 08:40:01 hostname kernel: [Firmware Bug]: TSC_DEADLINE disabled due to 
Errata; please update microcode to version: 0x17 (or later)
 Mar 07 08:42:02 hostname systemd-networkd-wait-online[780]: Event loop failed: 
Connection timed out
 Mar 07 08:42:02 hostname systemd[1]: Failed to start Wait for Network to be 
Configured.
 Mar 07 08:42:04 hostname iscsid[906]: iSCSI daemon with pid=908 started!
MachineType: Intel Corporation S1200RP
PciMultimedia:
 
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcFB: 0 mgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-11-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-11-generic N/A
 linux-backports-modules-4.15.0-11-generic  N/A
 linux-firmware 1.172
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/01/2015
dmi.bios.vendor: Intel Corp.
dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
dmi.board.asset.tag: 
dmi.board.name: S1200RP
dmi.board.vendor: Intel Corporation
dmi.board.version: G62254-407
dmi.chassis.asset.tag: 
dmi.chassis.type: 17
dmi.chassis.vendor: ..
dmi.chassis.version: ..
dmi.modalias: 
dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: S1200RP
dmi.product.version: 
dmi.sys.vendor: Intel Corporation

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Po-Hsu Lin (cypressyew)
 Status: In Progress


** Tags: amd64 apport-bug bionic package-from-proposed uec-images

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

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

Title:
  Unable to start ubuntu_zfs_xfs_generic test on Bionic

Status in linux package in Ubuntu:
  In Progress

Bug description:
  This is not a kernel issue.

  The problem was caused by glibc-2.27, and fixed with commit 8041435de7
  in xfsprogs-dev


  The compilation will fail with:
  copy_file_range.c:46:1: error: conflicting types for ‘copy_file_range’
  copy_file_range(int fd, loff_t *src, loff_t *dst, size_t len)
  ^~~
  In file included from ../include/platform_defs.h:33:0,
  from ../include/project.h:21,
  from ../include/input.h:24,
  from copy_file_range.c:23:
  /usr/include/unistd.h:1110:9: note: previous declaration of 
‘copy_file_range’ was here
  ssize_t copy_file_range (int __infd, __off64_t *__pinoff,
  ^~~
  make[3]: *** [../include/buildrules:60: copy_file_range.o] Error 1

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-11-generic 4.15.0-11.12
  ProcVersionSignature: User Name 

[Kernel-packages] [Bug 1753950] Re: Ubuntu18.04[P9, WSP]: While running ltp kernel_misc test hitting cpu warn_on on unregister_blkdev+0xac/0x300

2018-03-07 Thread Frank Heimes
** 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/1753950

Title:
  Ubuntu18.04[P9, WSP]:  While running ltp  kernel_misc test hitting cpu
  warn_on on  unregister_blkdev+0xac/0x300

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Praveen K. Pandey  - 2018-03-06 
05:19:10 ==
  Problem Description :

  While running ltp  kernel_misc  test hitting  cpu warn_on on
  unregister_blkdev

  Reproducible Step:

  1- Install WSP system with Ubuntu18.04
  2- get ltp from github 

  a- git clone https://github.com/linux-test-project/ltp.git
  b-cd ltp 
  c- make autotools
  d- ./configure
  e- make
  f- make install
  g- cd /opt/ltp
  h- ./runltp -f kernel_misc

  LOG:


  [87195.381004] WARNING: CPU: 8 PID: 25873 at 
/build/linux-jWa1Fv/linux-4.15.0/block/genhd.c:400 unregister_blkdev+0xac/0x300
  [87195.381166] Modules linked in: ltp_block_dev(OE) sctp nls_iso8859_1 ntfs 
btrfs zstd_compress xor raid6_pq xfs libcrc32c idt_89hpesx ofpart at24 
uio_pdrv_genirq cmdlinepart powernv_flash ibmpowernv vmx_crypto mtd 
ipmi_powernv ipmi_devintf ipmi_msghandler crct10dif_vpmsum opal_prd uio 
sch_fq_codel ip_tables x_tables autofs4 ast i2c_algo_bit ttm drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops ahci crc32c_vpmsum drm tg3 
libahci [last unloaded: ltp_fw_load]
  [87195.381750] CPU: 8 PID: 25873 Comm: block_dev Tainted: G   OE
4.15.0-10-generic #11-Ubuntu
  [87195.381869] NIP:  c069808c LR: c069803c CTR: 
c0697fe0
  [87195.381967] REGS: c01cf0bf3970 TRAP: 0700   Tainted: G   OE
 (4.15.0-10-generic)
  [87195.382078] MSR:  90029033   CR: 28000822 
 XER: 2004
  [87195.382177] CFAR: c069805c SOFTE: 1 
  [87195.382177] GPR00: c069803c c01cf0bf3bf0 c16ea600 
 
  [87195.382177] GPR04: c00819e113d8 000d 636f6c62 
c01cee876a00 
  [87195.382177] GPR08: c1a0f4b8   
c00819e111b8 
  [87195.382177] GPR12: c0697fe0 cfa85800  
 
  [87195.382177] GPR16:    
 
  [87195.382177] GPR20: 07399d9b8c10 07399d9b8c28 7fffd61064a4 
07399d9b8c50 
  [87195.382177] GPR24: 07399d9b8cf0 07399d9d0010 c01cf0bf3e00 
00fc 
  [87195.382177] GPR28: c00819e113d8 c15e2a60  
 
  [87195.383098] NIP [c069808c] unregister_blkdev+0xac/0x300
  [87195.383180] LR [c069803c] unregister_blkdev+0x5c/0x300
  [87195.383266] Call Trace:
  [87195.383302] [c01cf0bf3bf0] [c069803c] 
unregister_blkdev+0x5c/0x300 (unreliable)
  [87195.383424] [c01cf0bf3c30] [c00819e10790] sys_tcase+0x558/0xbe0 
[ltp_block_dev]
  [87195.383542] [c01cf0bf3ce0] [c08530dc] dev_attr_store+0x3c/0x60
  [87195.383628] [c01cf0bf3d00] [c049a6b4] sysfs_kf_write+0x64/0x90
  [87195.383726] [c01cf0bf3d20] [c04993ac] 
kernfs_fop_write+0x1ac/0x270
  [87195.383824] [c01cf0bf3d70] [c03cf8dc] __vfs_write+0x3c/0x70
  [87195.383919] [c01cf0bf3d90] [c03cfb38] vfs_write+0xd8/0x220
  [87195.384009] [c01cf0bf3de0] [c03cfe58] SyS_write+0x68/0x110
  [87195.384103] [c01cf0bf3e30] [c000b184] system_call+0x58/0x6c
  [87195.384196] Instruction dump:
  [87195.384241] 419e0030 812a0008 7f89f000 409e0018 48000144 813f0008 7f89f040 
419e0058 
  [87195.384347] 7feafb78 ebea 2fbf 409effe8 <0fe0> 7fa3eb78 
3be0 48668431 
  [87195.384459] ---[ end trace fdc18fb4b5cc1498 ]---

  
  Regards
  Praveen

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

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


[Kernel-packages] [Bug 1751838] Re: linux: 3.13.0-143.192 -proposed tracker

2018-03-07 Thread Taihsiang Ho
Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-testing/trusty/3.13.0-143.192
/trusty-proposed-published.html

** Tags added: certification-testing-passed

** Changed in: kernel-sru-workflow/certification-testing
   Status: In Progress => 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/1751838

Title:
  linux: 3.13.0-143.192 -proposed tracker

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

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

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

  backports: bug 1751839 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel due to mainline commit 24247aeeabe

2018-03-07 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Artful)
   Status: Fix Committed => 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/1733662

Title:
  System hang with Linux kernel due to mainline commit 24247aeeabe

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 ==
  The following mainline commit introduced a regression in v4.14-rc1:
  24247aeeabe9 ("x86/intel_rdt/cqm: Improve limbo list processing")

  This commit made it's way into Artful via Launchpad bug 1591609 as Artful 
commit
  ac2fc5adab0f4b.

  This bug was causing regression tests to hang about one in four
  times when running cpu_offlining tests.

  This patch to fix this regression was just submitted to mainline, so it is 
also
  needed in Bionic.

  == Fix ==
  commit d47924417319e3b6a728c0b690f183e75bc2a702
  Author: Thomas Gleixner 
  Date:   Tue Jan 16 19:59:59 2018 +0100

  x86/intel_rdt/cqm: Prevent use after free

  == Regression Potential ==
  Low.  This patch fixes a current regression that is a use after free.


  ### Original Bug Description ###
  In doing Ubuntu 17.10 regression testing, we've encountered one computer 
(boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in four times when 
running our cpu_offlining test. This test attempts to take all the CPU cores 
offline except one, then brings them back online again. This test ran 
successfully on boldore with previous releases, but with 17.10, the system 
sometimes (about one in four runs) hangs. Reverting to Ubuntu 16.04.3, I found 
no problems; but when I upgraded the 16.04.3 installation to 
linux-image-4.13.0-16-generic, the problem appeared again, so I'm confident 
this is a problem with the kernel. I'm attaching two files, 
dmesg-output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output 
that appears when running the cpu_offlining test with 4.10.0-38 and 4.13.0-16 
kernels, respectively; the system hung on the 4.13 run. (I was running "dmesg 
-w" in a second SSH login; the files are cut-and-pasted from that.)

  I initiated this bug report from an Ubuntu 16.04.3 installation
  running a 4.10 kernel; but as I said, this applies to the 4.13 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1
  ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Nov 21 17:36:06 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1753583] Re: Ubuntu 16.04.4 HWE kernel lockup: Upstream commit missing

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

Commit d47924417319 has been requested in Artful in bug 1733662, but it has not 
yet been applied:
https://lists.ubuntu.com/archives/kernel-team/2018-January/089403.html

I'll mark this bug as a duplicate since you confirmed the same commit
fixes this bug.

** This bug has been marked a duplicate of bug 1733662
   System hang with Linux kernel due to mainline commit 24247aeeabe

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

Title:
  Ubuntu 16.04.4 HWE kernel lockup: Upstream commit missing

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

Bug description:
  I experience random lockups when disabling CPUs, with symptoms very
  much as described here:

  See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662

  and when double-checking the source code for 4.13.0-36.40~16.04.1 I can see 
that upstream commit d47924417319e3b6a728c0b690f183e75bc2a702 is indeed missing.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  5 19:30 seq
   crw-rw 1 root audio 116, 33 Mar  5 19:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: FUJITSU PRIMERGY RX2530 M4
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/image1/kernel root=/dev/czvg/image1 ro 
console=tty0 console=ttyS0,115200 earlyprintk=ttyS0 rootdelay=300 net.ifnames=0 
biosdevname=0 nomodeset scsi_mod.scan=sync cz-boot-fs=/dev/sda1 
cz-state-fs=/dev/czvg/state1
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/05/2017
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.12 R1.11.0 for D3383-A1x
  dmi.board.name: D3383-A1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3383-A12 WGS03 GS04
  dmi.chassis.asset.tag: System Asset Tag
  dmi.chassis.type: 23
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.version: RX2530M4R1
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.11.0forD3383-A1x:bd10/05/2017:svnFUJITSU:pnPRIMERGYRX2530M4:pvrGS01:rvnFUJITSU:rnD3383-A1:rvrS26361-D3383-A12WGS03GS04:cvnFUJITSU:ct23:cvrRX2530M4R1:
  dmi.product.family: SERVER
  dmi.product.name: PRIMERGY RX2530 M4
  dmi.product.version: GS01
  dmi.sys.vendor: FUJITSU

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

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


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

2018-03-07 Thread Taihsiang Ho
** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => Invalid

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

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

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

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

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

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

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


[Kernel-packages] [Bug 1753950] Re: Ubuntu18.04[P9, WSP]: While running ltp kernel_misc test hitting cpu warn_on on unregister_blkdev+0xac/0x300

2018-03-07 Thread Frank Heimes
** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

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

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

Title:
  Ubuntu18.04[P9, WSP]:  While running ltp  kernel_misc test hitting cpu
  warn_on on  unregister_blkdev+0xac/0x300

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Praveen K. Pandey  - 2018-03-06 
05:19:10 ==
  Problem Description :

  While running ltp  kernel_misc  test hitting  cpu warn_on on
  unregister_blkdev

  Reproducible Step:

  1- Install WSP system with Ubuntu18.04
  2- get ltp from github 

  a- git clone https://github.com/linux-test-project/ltp.git
  b-cd ltp 
  c- make autotools
  d- ./configure
  e- make
  f- make install
  g- cd /opt/ltp
  h- ./runltp -f kernel_misc

  LOG:


  [87195.381004] WARNING: CPU: 8 PID: 25873 at 
/build/linux-jWa1Fv/linux-4.15.0/block/genhd.c:400 unregister_blkdev+0xac/0x300
  [87195.381166] Modules linked in: ltp_block_dev(OE) sctp nls_iso8859_1 ntfs 
btrfs zstd_compress xor raid6_pq xfs libcrc32c idt_89hpesx ofpart at24 
uio_pdrv_genirq cmdlinepart powernv_flash ibmpowernv vmx_crypto mtd 
ipmi_powernv ipmi_devintf ipmi_msghandler crct10dif_vpmsum opal_prd uio 
sch_fq_codel ip_tables x_tables autofs4 ast i2c_algo_bit ttm drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops ahci crc32c_vpmsum drm tg3 
libahci [last unloaded: ltp_fw_load]
  [87195.381750] CPU: 8 PID: 25873 Comm: block_dev Tainted: G   OE
4.15.0-10-generic #11-Ubuntu
  [87195.381869] NIP:  c069808c LR: c069803c CTR: 
c0697fe0
  [87195.381967] REGS: c01cf0bf3970 TRAP: 0700   Tainted: G   OE
 (4.15.0-10-generic)
  [87195.382078] MSR:  90029033   CR: 28000822 
 XER: 2004
  [87195.382177] CFAR: c069805c SOFTE: 1 
  [87195.382177] GPR00: c069803c c01cf0bf3bf0 c16ea600 
 
  [87195.382177] GPR04: c00819e113d8 000d 636f6c62 
c01cee876a00 
  [87195.382177] GPR08: c1a0f4b8   
c00819e111b8 
  [87195.382177] GPR12: c0697fe0 cfa85800  
 
  [87195.382177] GPR16:    
 
  [87195.382177] GPR20: 07399d9b8c10 07399d9b8c28 7fffd61064a4 
07399d9b8c50 
  [87195.382177] GPR24: 07399d9b8cf0 07399d9d0010 c01cf0bf3e00 
00fc 
  [87195.382177] GPR28: c00819e113d8 c15e2a60  
 
  [87195.383098] NIP [c069808c] unregister_blkdev+0xac/0x300
  [87195.383180] LR [c069803c] unregister_blkdev+0x5c/0x300
  [87195.383266] Call Trace:
  [87195.383302] [c01cf0bf3bf0] [c069803c] 
unregister_blkdev+0x5c/0x300 (unreliable)
  [87195.383424] [c01cf0bf3c30] [c00819e10790] sys_tcase+0x558/0xbe0 
[ltp_block_dev]
  [87195.383542] [c01cf0bf3ce0] [c08530dc] dev_attr_store+0x3c/0x60
  [87195.383628] [c01cf0bf3d00] [c049a6b4] sysfs_kf_write+0x64/0x90
  [87195.383726] [c01cf0bf3d20] [c04993ac] 
kernfs_fop_write+0x1ac/0x270
  [87195.383824] [c01cf0bf3d70] [c03cf8dc] __vfs_write+0x3c/0x70
  [87195.383919] [c01cf0bf3d90] [c03cfb38] vfs_write+0xd8/0x220
  [87195.384009] [c01cf0bf3de0] [c03cfe58] SyS_write+0x68/0x110
  [87195.384103] [c01cf0bf3e30] [c000b184] system_call+0x58/0x6c
  [87195.384196] Instruction dump:
  [87195.384241] 419e0030 812a0008 7f89f000 409e0018 48000144 813f0008 7f89f040 
419e0058 
  [87195.384347] 7feafb78 ebea 2fbf 409effe8 <0fe0> 7fa3eb78 
3be0 48668431 
  [87195.384459] ---[ end trace fdc18fb4b5cc1498 ]---

  
  Regards
  Praveen

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

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


[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions

2018-03-07 Thread Nobuto Murata
For the record,

v4.12-rc1 - bad (3 out of 3)
v4.12 - relatively good (5 out of 68)
v4.13 - good (0 out of 41)

** Attachment added: "bond_check_xenial_mainline_4.13_full.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5071491/+files/bond_check_xenial_mainline_4.13_full.log

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

Title:
  [i40e] LACP bonding start up race conditions

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

Bug description:
  When provisioning Ubuntu servers with MAAS at once, some bonding pairs
  will have unexpected LACP status such as "Expired". It randomly
  happens at each provisioning with the default xenial kernel(4.4), but
  not reproducible with HWE kernel(4.13). I'm using Intel X710 cards
  (Dell-branded).

  Using the HWE kernel works as a workaround for short term, but it's
  not ideal since 4.13 is not covered by Canonical Livepatch service.

  How to reproduce:
  1. configure LACP bonding with MAAS
  2. provision machines
  3. check the bonding status in /proc/net/bonding/bond*

  frequency of occurrence:
  About 5 bond pairs in 22 pairs at each provisioning.

  [reproducible combination]
  $ uname -a
  Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 1.4.25-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  [non-reproducible combination]
  $ uname -a
  Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 2.1.14-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  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
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  6 06:37 seq
   crw-rw 1 root audio 116, 33 Mar  6 06:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Mar  6 06:46:32 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R730
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 
console=ttyS0,115200n8
  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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.5
  dmi.board.name: 072T6D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.asset.tag: 0018880
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R730
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions

2018-03-07 Thread Nobuto Murata
** Attachment added: "bond_check_xenial_mainline_4.12_full.log.gz"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5071492/+files/bond_check_xenial_mainline_4.12_full.log.gz

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

Title:
  [i40e] LACP bonding start up race conditions

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

Bug description:
  When provisioning Ubuntu servers with MAAS at once, some bonding pairs
  will have unexpected LACP status such as "Expired". It randomly
  happens at each provisioning with the default xenial kernel(4.4), but
  not reproducible with HWE kernel(4.13). I'm using Intel X710 cards
  (Dell-branded).

  Using the HWE kernel works as a workaround for short term, but it's
  not ideal since 4.13 is not covered by Canonical Livepatch service.

  How to reproduce:
  1. configure LACP bonding with MAAS
  2. provision machines
  3. check the bonding status in /proc/net/bonding/bond*

  frequency of occurrence:
  About 5 bond pairs in 22 pairs at each provisioning.

  [reproducible combination]
  $ uname -a
  Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 1.4.25-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  [non-reproducible combination]
  $ uname -a
  Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 2.1.14-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  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
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  6 06:37 seq
   crw-rw 1 root audio 116, 33 Mar  6 06:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Mar  6 06:46:32 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R730
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 
console=ttyS0,115200n8
  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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.5
  dmi.board.name: 072T6D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.asset.tag: 0018880
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R730
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1742561] Re: [Feature] [Graphics]Whiskey Lake (Coffelake-U 4+2) new PCI Device ID adds

2018-03-07 Thread Timo Aaltonen
the userspace support is tracked on

https://bugs.launchpad.net/ubuntu/bionic/+source/xorg-
server/+bug/1753954

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

Title:
  [Feature] [Graphics]Whiskey Lake (Coffelake-U 4+2) new PCI Device ID
  adds

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

Bug description:
  Description:
  Whiskey Lake (Coffelake-U 4+2) new PCI Device ID adds

  c99d7832dcd7423ba352386107118b9bd8b83158 (drm branch commit id)
  (https://patchwork.freedesktop.org/patch/194410/)

  Target Release: 18.04

  Target Kernel: TBD (mainline)

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

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


[Kernel-packages] [Bug 1752350] Re: Bionic x86_64 Linux Kernel 4.15 fails to boot on Xen

2018-03-07 Thread Joseph Salisbury
The commit that fixes this bug is in upstream stable 4.15.5.  These
updates have  been applied 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/1752350

Title:
  Bionic x86_64 Linux Kernel 4.15 fails to boot on Xen

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

Bug description:
  The Linux Kernel 4.15 from bionic on x86_64 immediately crashes when
  booted as a dom0 under Xen.

  A similar bug was reported by someone else for archlinux
  (https://bugs.archlinux.org/task/57500).

  A patch exists for 4.16. I tried this patch on 4.15.0-10-generic, it
  fixes the problem for me.
  
(https://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git/patch/?id=4f277295e54c5b7340e48efea3fc5cc21a2872b7).

  Xen output:

  (XEN) Xen version 4.9.0 (Ubuntu 4.9.0-0ubuntu3) (stefan.ba...@canonical.com) 
(gcc (Ubuntu 7.2.0-8ubuntu2) 7.2.0) debug=n  Fri Oct 13 15:58:41 UTC 2017
  (XEN) Bootloader: GRUB 2.02~beta2-36ubuntu3.9
  (XEN) Command line: placeholder com1=115200,8N1 console=com1,vga
  (XEN) Xen image load base address: 0
  (XEN) Video information:
  (XEN)  VGA is text mode 80x25, font 8x16
  (XEN)  VBE/DDC methods: none; EDID transfer time: 0 seconds
  (XEN)  EDID info not retrieved because no DDC retrieval method detected
  (XEN) Disc information:
  (XEN)  Found 1 MBR signatures
  (XEN)  Found 1 EDD information structures
  (XEN) Xen-e820 RAM map:
  (XEN)   - 0009ec00 (usable)
  (XEN)  000f - 0010 (reserved)
  (XEN)  0010 - cb6cfc00 (usable)
  (XEN)  cb6cfc00 - cb723c00 (ACPI NVS)
  (XEN)  cb723c00 - cb725c00 (ACPI data)
  (XEN)  cb725c00 - cc00 (reserved)
  (XEN)  f800 - fc00 (reserved)
  (XEN)  fec0 - fed00400 (reserved)
  (XEN)  fed2 - feda (reserved)
  (XEN)  fee0 - fef0 (reserved)
  (XEN)  ffb0 - 0001 (reserved)
  (XEN)  0001 - 00013000 (usable)
  (XEN) New Xen image base address: 0xcb00
  (XEN) ACPI: RSDP 000FEC00, 0024 (r2 DELL  )
  (XEN) ACPI: XSDT 000FC7E7, 006C (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: FACP 000FC8D7, 00F4 (r3 DELLB11K  15 ASL61)
  (XEN) ACPI: DSDT FFDC89E4, 47BC (r1   DELLdt_ex 1000 INTL 20050624)
  (XEN) ACPI: FACS CB6CFC00, 0040
  (XEN) ACPI: SSDT FFDCD2C1, 00AC (r1   DELLst_ex 1000 INTL 20050624)
  (XEN) ACPI: APIC 000FC9CB, 0092 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: BOOT 000FCA5D, 0028 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: ASF! 000FCA85, 0096 (r32 DELLB11K  15 ASL61)
  (XEN) ACPI: MCFG 000FCB1B, 003E (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: HPET 000FCB59, 0038 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: TCPA 000FCDB5, 0032 (r1 DELLB11K  15 ASL61)
  (XEN) ACPI: DMAR 000FCDE7, 0068 (r1 DELLB11K  15 ASL61)
  (XEN) System RAM: 4022MB (4118964kB)
  (XEN) Domain heap initialised
  (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec0, GSI 0-23
  (XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
  (XEN) Using scheduler: SMP Credit Scheduler (credit)
  (XEN) Platform timer is 14.318MHz HPET
  (XEN) Detected 2926.007 MHz processor.
  (XEN) Initing memory sharing.
  (XEN) Intel VT-d iommu 0 supported page sizes: 4kB.
  (XEN) Intel VT-d Snoop Control enabled.
  (XEN) Intel VT-d Dom0 DMA Passthrough not enabled.
  (XEN) Intel VT-d Queued Invalidation enabled.
  (XEN) Intel VT-d Interrupt Remapping not enabled.
  (XEN) Intel VT-d Posted Interrupt not enabled.
  (XEN) Intel VT-d Shared EPT tables not enabled.
  (XEN) :04:00.0: unknown type 4
  (XEN) I/O virtualisation enabled
  (XEN)  - Dom0 mode: Relaxed
  (XEN) Interrupt remapping disabled
  (XEN) ENABLING IO-APIC IRQs
  (XEN)  -> Using new ACK method
  (XEN) Allocated console ring of 16 KiB.
  (XEN) VMX: Supported advanced features:
  (XEN)  - APIC MMIO access virtualisation
  (XEN)  - APIC TPR shadow
  (XEN)  - Extended Page Tables (EPT)
  (XEN)  - Virtual-Processor Identifiers (VPID)
  (XEN)  - Virtual NMI
  (XEN)  - MSR direct-access bitmap
  (XEN) HVM: ASIDs enabled.
  (XEN) HVM: VMX enabled
  (XEN) HVM: Hardware Assisted Paging (HAP) detected
  (XEN) HVM: HAP page sizes: 4kB, 2MB
  (XEN) Brought up 4 CPUs
  (XEN) Dom0 has maximum 600 PIRQs
  (XEN) *** LOADING DOMAIN 0 ***
  (XEN)  Xen  kernel: 64-bit, lsb, compat32
  (XEN)  Dom0 kernel: 64-bit, PAE, lsb, paddr 0x100 -> 0x2b69000
  (XEN) PHYSICAL MEMORY ARRANGEMENT:
  (XEN)  Dom0 alloc.:   00012000->00012400 (952940 pages to be 
allocated)
  (XEN)  Init. 

[Kernel-packages] [Bug 1750810] Re: qeth: fix calculation of required buffer elements for skb

2018-03-07 Thread Joseph Salisbury
Submitted Xenial SRU request:
https://lists.ubuntu.com/archives/kernel-team/2018-March/090640.html

** Description changed:

+ == SRU Justification ==
+ 
  Description:  qeth: fix calculation of required buffer elements for skb
  
  Symptom:  Repeated device recovery due to Subchannel Program Checks
  
  Problem:  skbs of certain lengths cause qeth to miscalculate the
-   number of needed IO buffer elements, resulting in
-   malformed TX buffer descriptors. When such a buffer is
-   presented to the HW, it triggers a Subchannel Program
-   Check. qeth handles this by starting device recovery.
+   number of needed IO buffer elements, resulting in
+   malformed TX buffer descriptors. When such a buffer is
+   presented to the HW, it triggers a Subchannel Program
+   Check. qeth handles this by starting device recovery.
  
  Solution: Fix the buffer element calculation, so that qeth builds
-   proper TX buffer descriptors.
+   proper TX buffer descriptors.
  
  Reproduction: Occurs for skbs where the last byte of the linear data
-   range / of a page frag sits on a page boundary.
+   range / of a page frag sits on a page boundary.
  
  Upstream Git Commit:
  89271c65edd599207dd982007900506283c90ae3
  kernel 4.16
  
- 
  backported to xenial/master-next
  
  Here's a backport of the upstream commit for pre-4.8 kernels.

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

Title:
  qeth: fix calculation of required buffer elements for skb

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  == SRU Justification ==

  Description:  qeth: fix calculation of required buffer elements for
  skb

  Symptom:  Repeated device recovery due to Subchannel Program
  Checks

  Problem:  skbs of certain lengths cause qeth to miscalculate the
    number of needed IO buffer elements, resulting in
    malformed TX buffer descriptors. When such a buffer is
    presented to the HW, it triggers a Subchannel Program
    Check. qeth handles this by starting device recovery.

  Solution: Fix the buffer element calculation, so that qeth builds
    proper TX buffer descriptors.

  Reproduction: Occurs for skbs where the last byte of the linear data
    range / of a page frag sits on a page boundary.

  Upstream Git Commit:
  89271c65edd599207dd982007900506283c90ae3
  kernel 4.16

  backported to xenial/master-next

  Here's a backport of the upstream commit for pre-4.8 kernels.

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

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


[Kernel-packages] [Bug 1730832] Re: [Feature] Add xHCI debug device support in the driver

2018-03-07 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/1730832

Title:
  [Feature] Add xHCI debug device support in the driver

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

Bug description:
  Description

  xHCI compatible USB host controllers(i.e. super-speed USB3 controllers)
  can be implemented with the Debug Capability(DbC). It presents a debug
  device which is fully compliant with the USB framework and provides the
  equivalent of a very high performance full-duplex serial link. The debug
  capability operation model and registers interface are defined in 7.6.8
  of the xHCI specification, revision 1.1.

  The DbC debug device shares a root port with the xHCI host. By default,
  the debug capability is disabled and the root port is assigned to xHCI.
  When the DbC is enabled, the root port will be assigned to the DbC debug
  device, and the xHCI sees nothing on this port. This implementation uses
  a sysfs node named  under the xHCI device to manage the enabling
  and disabling of the debug capability.

  When the debug capability is enabled, it will present a debug device
  through the debug port. This debug device is fully compliant with the
  USB3 framework, and it can be enumerated by a debug host on the other
  end of the USB link. As soon as the debug device is configured, a TTY
  serial device named /dev/ttyDBC0 will be created.

  One use of this link is running a login service on the debug target.
  Hence it can be remote accessed by a debug host. Another use case can
  probably be found in servers. It provides a peer-to-peer USB link
  between two host-only machines. This provides a reasonable out-of-band
  communication method between two servers.

  Target Kernel: 4.16
  Target Release: 18.04

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

-- 
Mailing list: https://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 1745349] Re: Hard lockup during boot with linux-image-4.4.0-112-generic

2018-03-07 Thread Lars Behrens
47a07600efe does not work here, hard lock on two pcs.

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

Title:
  Hard lockup during boot with linux-image-4.4.0-112-generic

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

Bug description:
  Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112
  instead they show

  NMI watchdog: Watchdog detected hard lockup on cpu 0
  NMI watchdog: Watchdog detected hard lockup on cpu 1
  NMI watchdog: Watchdog detected hard lockup on cpu 3
  NMI watchdog: Watchdog detected hard lockup on cpu 2

  I cannot provide any logs of course.

  Booting with 4.4.0-109 works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lr3200 2013 F pulseaudio
  Date: Thu Jan 25 11:38:55 2018
  HibernationDevice: RESUME=UUID=8e35131d-6d40-4f4f-a3db-c7336e72cbce
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp3s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=4dc5bb0a-ab7c-48fa-ac23-bcdf23755d93 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-109-generic N/A
   linux-backports-modules-4.4.0-109-generic  N/A
   linux-firmware 1.157.15
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3601
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-C
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Kernel-packages] [Bug 1745349] Re: Hard lockup during boot with linux-image-4.4.0-112-generic

2018-03-07 Thread Mike Turner
That one, 47a0... , failed.

Unfortunately, that is the last one that I can test for you until next
week, as I have to go away for a few days.

I hope that someone else can help.

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

Title:
  Hard lockup during boot with linux-image-4.4.0-112-generic

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

Bug description:
  Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112
  instead they show

  NMI watchdog: Watchdog detected hard lockup on cpu 0
  NMI watchdog: Watchdog detected hard lockup on cpu 1
  NMI watchdog: Watchdog detected hard lockup on cpu 3
  NMI watchdog: Watchdog detected hard lockup on cpu 2

  I cannot provide any logs of course.

  Booting with 4.4.0-109 works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lr3200 2013 F pulseaudio
  Date: Thu Jan 25 11:38:55 2018
  HibernationDevice: RESUME=UUID=8e35131d-6d40-4f4f-a3db-c7336e72cbce
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp3s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=4dc5bb0a-ab7c-48fa-ac23-bcdf23755d93 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-109-generic N/A
   linux-backports-modules-4.4.0-109-generic  N/A
   linux-firmware 1.157.15
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3601
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-C
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13

2018-03-07 Thread Joseph Salisbury
Do you think an Artful SRU request should be sent for commits 2b9478 and
62b4c66?  Or would you like to investigate the slow memory leak further?

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

Title:
  Servers going OOM after updating kernel from 4.10 to 4.13

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

Bug description:
  We are seeing this on multiple servers after upgrading from previous
  4.10 series HWE kernels to the new 4.13 HWE series. With the new
  kernel, free memory is continously decreasing at a high rate and the
  servers start swapping and finally OOMing services within days. With
  the 4.10 kernel, decrease of free memory is slower and stabilizes
  after a while.

  Latest kernel tested is linux-image-4.13.0-32-generic but the issue
  also affects older kernels from that series, tested back to linux-
  image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic.

  The servers are running as OpenStack controller nodes using either
  Ocata or Pike UCA plus ceph. See attached graph for the memory
  behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Feb  9 09:45:50 2018
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1752748] Re: nouveau module can't be loaded

2018-03-07 Thread Seth Forshee
I don't think this is a kernel problem, it looks like modprobe is trying
to load a module named "off" which does not exist. I'm wondering if you
have some kind of strange aliases defined in /etc/modprobe.d, something
like 'alias nouveau off'. Can you check the files in there, and if you
find something like that comment it out and try again?

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

Title:
  nouveau module can't be loaded

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Module nouveou can't be loaded. I get the following error message when
  I try to load it manually:

  # modprobe nouveau
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='off'
  modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown 
parameter (see dmesg)
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='off'
  modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown 
parameter (see dmesg)
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='off'
  modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown 
parameter (see dmesg)
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='off'
  modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown 
parameter (see dmesg)
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='off'
  modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown 
parameter (see dmesg)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-lowlatency 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.15.0-10.11-lowlatency 4.15.3
  Uname: Linux 4.15.0-10-lowlatency x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  lvella 1453 F pulseaudio
   /dev/snd/controlC0:  lvella 1453 F pulseaudio
   /dev/snd/controlC1:  lvella 1453 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Mar  1 20:37:06 2018
  HibernationDevice: RESUME=UUID=3f064780-2aeb-44b4-a8a3-21e590bd1b8f
  InstallationDate: Installed on 2016-06-02 (637 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-lowlatency.efi.signed 
root=UUID=f127c524-7b47-4ff1-b1d6-620ed6f14a29 ro noprompt persistent quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-lowlatency N/A
   linux-backports-modules-4.15.0-10-lowlatency  N/A
   linux-firmware1.171
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-02-28 (1 days ago)
  dmi.bios.date: 04/20/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3701
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H67-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3701:bd04/20/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H67-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Kernel-packages] [Bug 1753950] Re: Ubuntu18.04[P9, WSP]: While running ltp kernel_misc test hitting cpu warn_on on unregister_blkdev+0xac/0x300

2018-03-07 Thread Joseph Salisbury
** 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/1753950

Title:
  Ubuntu18.04[P9, WSP]:  While running ltp  kernel_misc test hitting cpu
  warn_on on  unregister_blkdev+0xac/0x300

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Praveen K. Pandey  - 2018-03-06 
05:19:10 ==
  Problem Description :

  While running ltp  kernel_misc  test hitting  cpu warn_on on
  unregister_blkdev

  Reproducible Step:

  1- Install WSP system with Ubuntu18.04
  2- get ltp from github 

  a- git clone https://github.com/linux-test-project/ltp.git
  b-cd ltp 
  c- make autotools
  d- ./configure
  e- make
  f- make install
  g- cd /opt/ltp
  h- ./runltp -f kernel_misc

  LOG:


  [87195.381004] WARNING: CPU: 8 PID: 25873 at 
/build/linux-jWa1Fv/linux-4.15.0/block/genhd.c:400 unregister_blkdev+0xac/0x300
  [87195.381166] Modules linked in: ltp_block_dev(OE) sctp nls_iso8859_1 ntfs 
btrfs zstd_compress xor raid6_pq xfs libcrc32c idt_89hpesx ofpart at24 
uio_pdrv_genirq cmdlinepart powernv_flash ibmpowernv vmx_crypto mtd 
ipmi_powernv ipmi_devintf ipmi_msghandler crct10dif_vpmsum opal_prd uio 
sch_fq_codel ip_tables x_tables autofs4 ast i2c_algo_bit ttm drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops ahci crc32c_vpmsum drm tg3 
libahci [last unloaded: ltp_fw_load]
  [87195.381750] CPU: 8 PID: 25873 Comm: block_dev Tainted: G   OE
4.15.0-10-generic #11-Ubuntu
  [87195.381869] NIP:  c069808c LR: c069803c CTR: 
c0697fe0
  [87195.381967] REGS: c01cf0bf3970 TRAP: 0700   Tainted: G   OE
 (4.15.0-10-generic)
  [87195.382078] MSR:  90029033   CR: 28000822 
 XER: 2004
  [87195.382177] CFAR: c069805c SOFTE: 1 
  [87195.382177] GPR00: c069803c c01cf0bf3bf0 c16ea600 
 
  [87195.382177] GPR04: c00819e113d8 000d 636f6c62 
c01cee876a00 
  [87195.382177] GPR08: c1a0f4b8   
c00819e111b8 
  [87195.382177] GPR12: c0697fe0 cfa85800  
 
  [87195.382177] GPR16:    
 
  [87195.382177] GPR20: 07399d9b8c10 07399d9b8c28 7fffd61064a4 
07399d9b8c50 
  [87195.382177] GPR24: 07399d9b8cf0 07399d9d0010 c01cf0bf3e00 
00fc 
  [87195.382177] GPR28: c00819e113d8 c15e2a60  
 
  [87195.383098] NIP [c069808c] unregister_blkdev+0xac/0x300
  [87195.383180] LR [c069803c] unregister_blkdev+0x5c/0x300
  [87195.383266] Call Trace:
  [87195.383302] [c01cf0bf3bf0] [c069803c] 
unregister_blkdev+0x5c/0x300 (unreliable)
  [87195.383424] [c01cf0bf3c30] [c00819e10790] sys_tcase+0x558/0xbe0 
[ltp_block_dev]
  [87195.383542] [c01cf0bf3ce0] [c08530dc] dev_attr_store+0x3c/0x60
  [87195.383628] [c01cf0bf3d00] [c049a6b4] sysfs_kf_write+0x64/0x90
  [87195.383726] [c01cf0bf3d20] [c04993ac] 
kernfs_fop_write+0x1ac/0x270
  [87195.383824] [c01cf0bf3d70] [c03cf8dc] __vfs_write+0x3c/0x70
  [87195.383919] [c01cf0bf3d90] [c03cfb38] vfs_write+0xd8/0x220
  [87195.384009] [c01cf0bf3de0] [c03cfe58] SyS_write+0x68/0x110
  [87195.384103] [c01cf0bf3e30] [c000b184] system_call+0x58/0x6c
  [87195.384196] Instruction dump:
  [87195.384241] 419e0030 812a0008 7f89f000 409e0018 48000144 813f0008 7f89f040 
419e0058 
  [87195.384347] 7feafb78 ebea 2fbf 409effe8 <0fe0> 7fa3eb78 
3be0 48668431 
  [87195.384459] ---[ end trace fdc18fb4b5cc1498 ]---

  
  Regards
  Praveen

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

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


[Kernel-packages] [Bug 1749040] Re: KPTI support for arm64 systems

2018-03-07 Thread dann frazier
** Attachment added: "combined kern.log/serial log of lundmark SEA crash"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+attachment/5071412/+files/lundmark-cert-failure-sea.log

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

Title:
  KPTI support for arm64 systems

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

Bug description:
  While regression testing the current linux-hwe proposed kernel
  (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium
  ThunderX CRB. I've rebooted twice since upgrading from the current
  -updates kernel, and it's failed to boot both times, with different
  failure modes.

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

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


[Kernel-packages] [Bug 1751328] Re: kdump-tools won't create initrd for previously installed kernels

2018-03-07 Thread Thadeu Lima de Souza Cascardo
This is now fixed in Debian. It would be nice to sync it to Bionic.

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

Title:
  kdump-tools won't create initrd for previously installed kernels

Status in makedumpfile package in Ubuntu:
  Confirmed

Bug description:
  When kdump-tools is installed, it creates an initrd for the running
  kernel. For kernels installed after that, the postinst part will be
  run and a initrd will be created as well. However, for kernels that
  are already installed, it won't create them.

  As an example, when the user is running 4.4.0-112-generic, but has
  4.13.0-32-generic installed, kdump-tools will create an initrd for
  4.4.0-112-generic. When the user later reboots into 4.13.0-32-generic,
  the initrd is not present, and kdump-tools won't load.

  Cascardo.

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

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


[Kernel-packages] [Bug 1749040] Re: KPTI support for arm64 systems

2018-03-07 Thread dann frazier
I rebooted the machine (lundmark) and restarted the test mentioned in
the previous comment, this time the system crashed w/ a Synchronous
External Abort:

[23243.094384] Synchronous External Abort: synchronous parity or ECC
error (0x8618) at 0xb0f74f68

This suggests a non-software issue. I'll seek another CRB machine and
retest.

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

Title:
  KPTI support for arm64 systems

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

Bug description:
  While regression testing the current linux-hwe proposed kernel
  (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium
  ThunderX CRB. I've rebooted twice since upgrading from the current
  -updates kernel, and it's failed to boot both times, with different
  failure modes.

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

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


[Kernel-packages] [Bug 1753705] Re: stress-ng will make an Ubuntu on LPAR s390x Bionic system become very slow

2018-03-07 Thread Colin Ian King
** Package changed: linux (Ubuntu) => stress-ng (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/1753705

Title:
  stress-ng will make an Ubuntu on LPAR s390x Bionic system become very
  slow

Status in stress-ng package in Ubuntu:
  In Progress

Bug description:
  On an Ubuntu on LPAR s390x node, s2lp4, boot with Bionic kernel.

  When trying to run the ubuntu_stress_smoke test on it. This test will cause 
error like:
    
/home/ubuntu/autotest/client/tests/ubuntu_stress_smoke_test/ubuntu_stress_smoke_test.sh:
 fork: retry: Resource temporarily unavailable

  Not sure which test is the cause, but the system will become very slow
  after running this test suite. And it seems that the test suite will
  terminates itself before walking through all the test cases.

  1st run: terminates after the epoll test
  2nd run: crashed and rebooted after the branch test
  3rd run: terminates after the eventfd test
  4th run: terminates after the enosys test

  Command to run the test:
    AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_stress_smoke_test/control

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-11-generic 4.15.0-11.12
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  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: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:

  Date: Tue Mar  6 09:31:39 2018
  HibernationDevice: RESUME=UUID=e2735dd1-cbbc-4424-9c25-d37d073d9414
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:

  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=38f7d570-2973-4055-b668-12a9ace1e0c7 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-11-generic N/A
   linux-backports-modules-4.15.0-11-generic  N/A
   linux-firmware 1.172
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1753705/+subscriptions

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


[Kernel-packages] [Bug 1753950] [NEW] Ubuntu18.04[P9, WSP]: While running ltp kernel_misc test hitting cpu warn_on on unregister_blkdev+0xac/0x300

2018-03-07 Thread bugproxy
Public bug reported:

== Comment: #0 - Praveen K. Pandey  - 2018-03-06 
05:19:10 ==
Problem Description :

While running ltp  kernel_misc  test hitting  cpu warn_on on
unregister_blkdev

Reproducible Step:

1- Install WSP system with Ubuntu18.04
2- get ltp from github 

a- git clone https://github.com/linux-test-project/ltp.git
b-cd ltp 
c- make autotools
d- ./configure
e- make
f- make install
g- cd /opt/ltp
h- ./runltp -f kernel_misc

LOG:


[87195.381004] WARNING: CPU: 8 PID: 25873 at 
/build/linux-jWa1Fv/linux-4.15.0/block/genhd.c:400 unregister_blkdev+0xac/0x300
[87195.381166] Modules linked in: ltp_block_dev(OE) sctp nls_iso8859_1 ntfs 
btrfs zstd_compress xor raid6_pq xfs libcrc32c idt_89hpesx ofpart at24 
uio_pdrv_genirq cmdlinepart powernv_flash ibmpowernv vmx_crypto mtd 
ipmi_powernv ipmi_devintf ipmi_msghandler crct10dif_vpmsum opal_prd uio 
sch_fq_codel ip_tables x_tables autofs4 ast i2c_algo_bit ttm drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops ahci crc32c_vpmsum drm tg3 
libahci [last unloaded: ltp_fw_load]
[87195.381750] CPU: 8 PID: 25873 Comm: block_dev Tainted: G   OE
4.15.0-10-generic #11-Ubuntu
[87195.381869] NIP:  c069808c LR: c069803c CTR: c0697fe0
[87195.381967] REGS: c01cf0bf3970 TRAP: 0700   Tainted: G   OE 
(4.15.0-10-generic)
[87195.382078] MSR:  90029033   CR: 28000822  
XER: 2004
[87195.382177] CFAR: c069805c SOFTE: 1 
[87195.382177] GPR00: c069803c c01cf0bf3bf0 c16ea600 
 
[87195.382177] GPR04: c00819e113d8 000d 636f6c62 
c01cee876a00 
[87195.382177] GPR08: c1a0f4b8   
c00819e111b8 
[87195.382177] GPR12: c0697fe0 cfa85800  
 
[87195.382177] GPR16:    
 
[87195.382177] GPR20: 07399d9b8c10 07399d9b8c28 7fffd61064a4 
07399d9b8c50 
[87195.382177] GPR24: 07399d9b8cf0 07399d9d0010 c01cf0bf3e00 
00fc 
[87195.382177] GPR28: c00819e113d8 c15e2a60  
 
[87195.383098] NIP [c069808c] unregister_blkdev+0xac/0x300
[87195.383180] LR [c069803c] unregister_blkdev+0x5c/0x300
[87195.383266] Call Trace:
[87195.383302] [c01cf0bf3bf0] [c069803c] 
unregister_blkdev+0x5c/0x300 (unreliable)
[87195.383424] [c01cf0bf3c30] [c00819e10790] sys_tcase+0x558/0xbe0 
[ltp_block_dev]
[87195.383542] [c01cf0bf3ce0] [c08530dc] dev_attr_store+0x3c/0x60
[87195.383628] [c01cf0bf3d00] [c049a6b4] sysfs_kf_write+0x64/0x90
[87195.383726] [c01cf0bf3d20] [c04993ac] 
kernfs_fop_write+0x1ac/0x270
[87195.383824] [c01cf0bf3d70] [c03cf8dc] __vfs_write+0x3c/0x70
[87195.383919] [c01cf0bf3d90] [c03cfb38] vfs_write+0xd8/0x220
[87195.384009] [c01cf0bf3de0] [c03cfe58] SyS_write+0x68/0x110
[87195.384103] [c01cf0bf3e30] [c000b184] system_call+0x58/0x6c
[87195.384196] Instruction dump:
[87195.384241] 419e0030 812a0008 7f89f000 409e0018 48000144 813f0008 7f89f040 
419e0058 
[87195.384347] 7feafb78 ebea 2fbf 409effe8 <0fe0> 7fa3eb78 3be0 
48668431 
[87195.384459] ---[ end trace fdc18fb4b5cc1498 ]---


Regards
Praveen

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-165381 severity-high 
targetmilestone-inin---

** Tags added: architecture-ppc64le bugnameltc-165381 severity-high
targetmilestone-inin---

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

Title:
  Ubuntu18.04[P9, WSP]:  While running ltp  kernel_misc test hitting cpu
  warn_on on  unregister_blkdev+0xac/0x300

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Praveen K. Pandey  - 2018-03-06 
05:19:10 ==
  Problem Description :

  While running ltp  kernel_misc  test hitting  cpu warn_on on
  unregister_blkdev

  Reproducible Step:

  1- Install WSP system with Ubuntu18.04
  2- get ltp from github 

  a- git clone https://github.com/linux-test-project/ltp.git
  b-cd ltp 
  c- make autotools
  d- ./configure
  e- make
  f- make install
  g- cd /opt/ltp
  h- ./runltp -f kernel_misc

  LOG:


  [87195.381004] WARNING: CPU: 8 PID: 25873 at 
/build/linux-jWa1Fv/linux-4.15.0/block/genhd.c:400 unregister_blkdev+0xac/0x300
  [87195.381166] Modules linked in: ltp_block_dev(OE) sctp nls_iso8859_1 ntfs 
btrfs zstd_compress xor raid6_pq xfs libcrc32c 

[Kernel-packages] [Bug 1751021] Re: retpoline abi files are empty on i386

2018-03-07 Thread Kleber Sacilotto de Souza
Confirmed that the retpoline file is being populated on trusty kernel
for i386 (checked with contents from linux-
image-3.13.0-143-generic_3.13.0-143.192_i386.deb). Marking
'verification-done-trusty'.

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

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

Title:
  retpoline abi files are empty on i386

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  The .retpoline files in the current abi are actually blank.
  This is due to incorrect handling in retpoline-extract.

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

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


[Kernel-packages] [Bug 1753941] Re: ubuntu_bpf_jit test failed on Bionic s390x systems

2018-03-07 Thread Po-Hsu Lin
** Description changed:

- Not sure if this is related to bug 1751234, the ubuntu_bpf_jit test will
- fail with the following 5 test cases:
+ Not sure if this is related to bug 1751234 (error on AMD64 system is
+ different)
+ 
+ The ubuntu_bpf_jit test will fail with the following 5 test cases:
  
  test_bpf: #292 BPF_MAXINSNS: Ctx heavy transformations FAIL to prog_create 
err=-524 len=4096
  test_bpf: #293 BPF_MAXINSNS: Call heavy transformations FAIL to prog_create 
err=-524 len=4096
  test_bpf: #298 BPF_MAXINSNS: ld_abs+get_processor_id FAIL to prog_create 
err=-524 len=4096
  test_bpf: #299 BPF_MAXINSNS: ld_abs+vlan_push/pop FAIL to select_runtime 
err=-524
  test_bpf: #300 BPF_MAXINSNS: jump around ld_abs FAIL to select_runtime 
err=-524
  
  test_bpf: Summary: 337 PASSED, 5 FAILED, [329/329 JIT'ed]
  
  And modprobe error can be found in the report as well:
  modprobe: ERROR: could not insert 'test_bpf': Invalid argument
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-11-generic 4.15.0-11.12
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  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: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
-  
+ 
  Date: Wed Mar  7 08:13:51 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:
-  
+ 
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
-  
+ 
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=/dev/mapper/kl02vg01-root crashkernel=196M 
BOOT_IMAGE=0
  RelatedPackageVersions:
-  linux-restricted-modules-4.15.0-11-generic N/A
-  linux-backports-modules-4.15.0-11-generic  N/A
-  linux-firmware 1.172
+  linux-restricted-modules-4.15.0-11-generic N/A
+  linux-backports-modules-4.15.0-11-generic  N/A
+  linux-firmware 1.172
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  Not sure if this is related to bug 1751234 (error on AMD64 system is
  different)
  
  The ubuntu_bpf_jit test will fail with the following 5 test cases:
  
  test_bpf: #292 BPF_MAXINSNS: Ctx heavy transformations FAIL to prog_create 
err=-524 len=4096
  test_bpf: #293 BPF_MAXINSNS: Call heavy transformations FAIL to prog_create 
err=-524 len=4096
  test_bpf: #298 BPF_MAXINSNS: ld_abs+get_processor_id FAIL to prog_create 
err=-524 len=4096
  test_bpf: #299 BPF_MAXINSNS: ld_abs+vlan_push/pop FAIL to select_runtime 
err=-524
  test_bpf: #300 BPF_MAXINSNS: jump around ld_abs FAIL to select_runtime 
err=-524
  
  test_bpf: Summary: 337 PASSED, 5 FAILED, [329/329 JIT'ed]
  
  And modprobe error can be found in the report as well:
  modprobe: ERROR: could not insert 'test_bpf': Invalid argument
+ 
+ Issue can be reproduce on both zVM and Ubuntu on LPAR s390x systems.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-11-generic 4.15.0-11.12
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  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: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
  
  Date: Wed Mar  7 08:13:51 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:
  
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
  
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=/dev/mapper/kl02vg01-root crashkernel=196M 
BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-11-generic N/A
   linux-backports-modules-4.15.0-11-generic  N/A
   linux-firmware 1.172
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Kernel-packages] [Bug 1753950] [NEW] Ubuntu18.04[P9, WSP]: While running ltp kernel_misc test hitting cpu warn_on on unregister_blkdev+0xac/0x300

2018-03-07 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

== Comment: #0 - Praveen K. Pandey  - 2018-03-06 
05:19:10 ==
Problem Description :

While running ltp  kernel_misc  test hitting  cpu warn_on on
unregister_blkdev

Reproducible Step:

1- Install WSP system with Ubuntu18.04
2- get ltp from github 

a- git clone https://github.com/linux-test-project/ltp.git
b-cd ltp 
c- make autotools
d- ./configure
e- make
f- make install
g- cd /opt/ltp
h- ./runltp -f kernel_misc

LOG:


[87195.381004] WARNING: CPU: 8 PID: 25873 at 
/build/linux-jWa1Fv/linux-4.15.0/block/genhd.c:400 unregister_blkdev+0xac/0x300
[87195.381166] Modules linked in: ltp_block_dev(OE) sctp nls_iso8859_1 ntfs 
btrfs zstd_compress xor raid6_pq xfs libcrc32c idt_89hpesx ofpart at24 
uio_pdrv_genirq cmdlinepart powernv_flash ibmpowernv vmx_crypto mtd 
ipmi_powernv ipmi_devintf ipmi_msghandler crct10dif_vpmsum opal_prd uio 
sch_fq_codel ip_tables x_tables autofs4 ast i2c_algo_bit ttm drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops ahci crc32c_vpmsum drm tg3 
libahci [last unloaded: ltp_fw_load]
[87195.381750] CPU: 8 PID: 25873 Comm: block_dev Tainted: G   OE
4.15.0-10-generic #11-Ubuntu
[87195.381869] NIP:  c069808c LR: c069803c CTR: c0697fe0
[87195.381967] REGS: c01cf0bf3970 TRAP: 0700   Tainted: G   OE 
(4.15.0-10-generic)
[87195.382078] MSR:  90029033   CR: 28000822  
XER: 2004
[87195.382177] CFAR: c069805c SOFTE: 1 
[87195.382177] GPR00: c069803c c01cf0bf3bf0 c16ea600 
 
[87195.382177] GPR04: c00819e113d8 000d 636f6c62 
c01cee876a00 
[87195.382177] GPR08: c1a0f4b8   
c00819e111b8 
[87195.382177] GPR12: c0697fe0 cfa85800  
 
[87195.382177] GPR16:    
 
[87195.382177] GPR20: 07399d9b8c10 07399d9b8c28 7fffd61064a4 
07399d9b8c50 
[87195.382177] GPR24: 07399d9b8cf0 07399d9d0010 c01cf0bf3e00 
00fc 
[87195.382177] GPR28: c00819e113d8 c15e2a60  
 
[87195.383098] NIP [c069808c] unregister_blkdev+0xac/0x300
[87195.383180] LR [c069803c] unregister_blkdev+0x5c/0x300
[87195.383266] Call Trace:
[87195.383302] [c01cf0bf3bf0] [c069803c] 
unregister_blkdev+0x5c/0x300 (unreliable)
[87195.383424] [c01cf0bf3c30] [c00819e10790] sys_tcase+0x558/0xbe0 
[ltp_block_dev]
[87195.383542] [c01cf0bf3ce0] [c08530dc] dev_attr_store+0x3c/0x60
[87195.383628] [c01cf0bf3d00] [c049a6b4] sysfs_kf_write+0x64/0x90
[87195.383726] [c01cf0bf3d20] [c04993ac] 
kernfs_fop_write+0x1ac/0x270
[87195.383824] [c01cf0bf3d70] [c03cf8dc] __vfs_write+0x3c/0x70
[87195.383919] [c01cf0bf3d90] [c03cfb38] vfs_write+0xd8/0x220
[87195.384009] [c01cf0bf3de0] [c03cfe58] SyS_write+0x68/0x110
[87195.384103] [c01cf0bf3e30] [c000b184] system_call+0x58/0x6c
[87195.384196] Instruction dump:
[87195.384241] 419e0030 812a0008 7f89f000 409e0018 48000144 813f0008 7f89f040 
419e0058 
[87195.384347] 7feafb78 ebea 2fbf 409effe8 <0fe0> 7fa3eb78 3be0 
48668431 
[87195.384459] ---[ end trace fdc18fb4b5cc1498 ]---


Regards
Praveen

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-165381 severity-high 
targetmilestone-inin---
-- 
Ubuntu18.04[P9, WSP]:  While running ltp  kernel_misc test hitting cpu warn_on 
on  unregister_blkdev+0xac/0x300
https://bugs.launchpad.net/bugs/1753950
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 1745349] Re: Hard lockup during boot with linux-image-4.4.0-112-generic

2018-03-07 Thread Joseph Salisbury
I built the next test kernel, up to the following commit:
47a07600efeb2a180b847bb0e3e99e138a49198c

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

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

Thanks in advance

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

Title:
  Hard lockup during boot with linux-image-4.4.0-112-generic

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

Bug description:
  Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112
  instead they show

  NMI watchdog: Watchdog detected hard lockup on cpu 0
  NMI watchdog: Watchdog detected hard lockup on cpu 1
  NMI watchdog: Watchdog detected hard lockup on cpu 3
  NMI watchdog: Watchdog detected hard lockup on cpu 2

  I cannot provide any logs of course.

  Booting with 4.4.0-109 works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lr3200 2013 F pulseaudio
  Date: Thu Jan 25 11:38:55 2018
  HibernationDevice: RESUME=UUID=8e35131d-6d40-4f4f-a3db-c7336e72cbce
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp3s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=4dc5bb0a-ab7c-48fa-ac23-bcdf23755d93 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-109-generic N/A
   linux-backports-modules-4.4.0-109-generic  N/A
   linux-firmware 1.157.15
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3601
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-C
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Kernel-packages] [Bug 1753941] Re: ubuntu_bpf_jit test failed on Bionic s390x systems

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

** Tags added: kernel-da-key

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

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

Title:
  ubuntu_bpf_jit test failed on Bionic s390x systems

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Not sure if this is related to bug 1751234, the ubuntu_bpf_jit test
  will fail with the following 5 test cases:

  test_bpf: #292 BPF_MAXINSNS: Ctx heavy transformations FAIL to prog_create 
err=-524 len=4096
  test_bpf: #293 BPF_MAXINSNS: Call heavy transformations FAIL to prog_create 
err=-524 len=4096
  test_bpf: #298 BPF_MAXINSNS: ld_abs+get_processor_id FAIL to prog_create 
err=-524 len=4096
  test_bpf: #299 BPF_MAXINSNS: ld_abs+vlan_push/pop FAIL to select_runtime 
err=-524
  test_bpf: #300 BPF_MAXINSNS: jump around ld_abs FAIL to select_runtime 
err=-524

  test_bpf: Summary: 337 PASSED, 5 FAILED, [329/329 JIT'ed]

  And modprobe error can be found in the report as well:
  modprobe: ERROR: could not insert 'test_bpf': Invalid argument

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-11-generic 4.15.0-11.12
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  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: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   
  Date: Wed Mar  7 08:13:51 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=/dev/mapper/kl02vg01-root crashkernel=196M 
BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-11-generic N/A
   linux-backports-modules-4.15.0-11-generic  N/A
   linux-firmware 1.172
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2018-03-07 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 1753941

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

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

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

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

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

Title:
  ubuntu_bpf_jit test failed on Bionic s390x systems

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Not sure if this is related to bug 1751234, the ubuntu_bpf_jit test
  will fail with the following 5 test cases:

  test_bpf: #292 BPF_MAXINSNS: Ctx heavy transformations FAIL to prog_create 
err=-524 len=4096
  test_bpf: #293 BPF_MAXINSNS: Call heavy transformations FAIL to prog_create 
err=-524 len=4096
  test_bpf: #298 BPF_MAXINSNS: ld_abs+get_processor_id FAIL to prog_create 
err=-524 len=4096
  test_bpf: #299 BPF_MAXINSNS: ld_abs+vlan_push/pop FAIL to select_runtime 
err=-524
  test_bpf: #300 BPF_MAXINSNS: jump around ld_abs FAIL to select_runtime 
err=-524

  test_bpf: Summary: 337 PASSED, 5 FAILED, [329/329 JIT'ed]

  And modprobe error can be found in the report as well:
  modprobe: ERROR: could not insert 'test_bpf': Invalid argument

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-11-generic 4.15.0-11.12
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  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: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   
  Date: Wed Mar  7 08:13:51 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=/dev/mapper/kl02vg01-root crashkernel=196M 
BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-11-generic N/A
   linux-backports-modules-4.15.0-11-generic  N/A
   linux-firmware 1.172
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1753941] [NEW] ubuntu_bpf_jit test failed on Bionic s390x systems

2018-03-07 Thread Po-Hsu Lin
Public bug reported:

Not sure if this is related to bug 1751234, the ubuntu_bpf_jit test will
fail with the following 5 test cases:

test_bpf: #292 BPF_MAXINSNS: Ctx heavy transformations FAIL to prog_create 
err=-524 len=4096
test_bpf: #293 BPF_MAXINSNS: Call heavy transformations FAIL to prog_create 
err=-524 len=4096
test_bpf: #298 BPF_MAXINSNS: ld_abs+get_processor_id FAIL to prog_create 
err=-524 len=4096
test_bpf: #299 BPF_MAXINSNS: ld_abs+vlan_push/pop FAIL to select_runtime 
err=-524
test_bpf: #300 BPF_MAXINSNS: jump around ld_abs FAIL to select_runtime err=-524

test_bpf: Summary: 337 PASSED, 5 FAILED, [329/329 JIT'ed]

And modprobe error can be found in the report as well:
modprobe: ERROR: could not insert 'test_bpf': Invalid argument

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-11-generic 4.15.0-11.12
ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
Uname: Linux 4.15.0-11-generic s390x
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
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: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not 
found.
CurrentDmesg:
 
Date: Wed Mar  7 08:13:51 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lspci:
 
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
 
ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=/dev/mapper/kl02vg01-root crashkernel=196M BOOT_IMAGE=0
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-11-generic N/A
 linux-backports-modules-4.15.0-11-generic  N/A
 linux-firmware 1.172
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug bionic package-from-proposed s390x

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

Title:
  ubuntu_bpf_jit test failed on Bionic s390x systems

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Not sure if this is related to bug 1751234, the ubuntu_bpf_jit test
  will fail with the following 5 test cases:

  test_bpf: #292 BPF_MAXINSNS: Ctx heavy transformations FAIL to prog_create 
err=-524 len=4096
  test_bpf: #293 BPF_MAXINSNS: Call heavy transformations FAIL to prog_create 
err=-524 len=4096
  test_bpf: #298 BPF_MAXINSNS: ld_abs+get_processor_id FAIL to prog_create 
err=-524 len=4096
  test_bpf: #299 BPF_MAXINSNS: ld_abs+vlan_push/pop FAIL to select_runtime 
err=-524
  test_bpf: #300 BPF_MAXINSNS: jump around ld_abs FAIL to select_runtime 
err=-524

  test_bpf: Summary: 337 PASSED, 5 FAILED, [329/329 JIT'ed]

  And modprobe error can be found in the report as well:
  modprobe: ERROR: could not insert 'test_bpf': Invalid argument

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-11-generic 4.15.0-11.12
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  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: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   
  Date: Wed Mar  7 08:13:51 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=/dev/mapper/kl02vg01-root crashkernel=196M 
BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-11-generic N/A
   linux-backports-modules-4.15.0-11-generic  N/A
   linux-firmware 1.172
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1753791] Re: Requesting a backport of SMB2/SMB3 bugfix for DFS support

2018-03-07 Thread Joseph Salisbury
** Tags added: kernel-da-key

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

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

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

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

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

Title:
  Requesting a backport of SMB2/SMB3 bugfix for DFS support

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

Bug description:
  16.04 x64 with 4.4.0-112 or 4.4.0-116 - cannot traverse a DFS link for
  a cifs.mount from windows if vers is anything other than 1.0 default.
  (This submission was from a 112 host, but it's confirmed to still
  exist on anything less than 4.11.)

  Fix exists in 4.13.x in Ubuntu 18.x and works fine.

  Issue is that once you mount with vers=2 or greater, you cannot
  traverse the dfs root directory to any file server, and you cannot
  mount the dfs path directly - only a direct mount to the backend
  fileservers will work.

  Requesting a backport of the fix as described below as this makes it
  impossible to move forward with security action disabling SMB1 on our
  windows environment. If we do that now, will be unable to use that
  storage from all of our windows systems without directly mapping to
  individual file servers.

  https://www.spinics.net/lists/linux-cifs/msg13825.html

  1: https://bugzilla.samba.org/show_bug.cgi?id=12917

  Aurelien Aptel (3):
CIFS: set SERVER_NAME_LENGTH to serverName actual size
CIFS: make IPC a regular tcon
CIFS: use tcon_ipc instead of use_ipc parameter from SMB2_ioctl


  It's unclear if this should be treated as a security issue since it's
  not directly a security problem itself, but rather prevents taking
  security related action.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.112.118
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb  8 23:26 seq
   crw-rw 1 root audio 116, 33 Feb  8 23:26 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Mar  6 10:29:20 2018
  HibernationDevice: RESUME=/dev/mapper/main-swap
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-112-generic 
root=/dev/mapper/main-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-generic  N/A
   linux-firmware 1.157.15
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/21/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

-- 
Mailing list: https://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   >