[Kernel-packages] [Bug 1723680] Re: GPU Hang in Xorg rcs0 drm/i915

[Horst Schirmeier]

Possibly this bug? https://bugs.freedesktop.org/show_bug.cgi?id=102435
-> Ubuntu 17.10's Mesa 17.2.2 seems to be broken

** Bug watch added: freedesktop.org Bugzilla #102435
   https://bugs.freedesktop.org/show_bug.cgi?id=102435

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

Title:
  GPU Hang in Xorg rcs0 drm/i915

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

Bug description:
  Distributor ID:   Ubuntu
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10
  Codename: artful

  When using linux kernel linux-image-4.13.0-12-generic to linux-
  image-4.13.0-16-generic Xorg fails to start with kernel error messages
  below. Kernel boots and displays messages allows for GUI to enter disk
  encryption key then tries to start Xorg login.  Shows blank screen,
  sometimes part of login dialog.  Then hangs and goes blank usually
  showing the low graphics mode error screen from Xorg and no
  functionality after a while.  Can ctrl+alt+f1 to console.  Using
  linux-image-4.10.0-35-generic everything works as expected.  System
  worked without issue with Ubuntu 17.04

  Kernel error messages:
  [   43.836641] [drm] GPU HANG: ecode 8:0:0x00df, in Xorg [1027], reason: 
Hang on rcs0, action: reset
  [   43.836645] [drm] GPU hangs can indicate a bug anywhere in the entire gfx 
stack, including userspace.
  [   43.836646] [drm] Please file a _new_ bug report on bugs.freedesktop.org 
against DRI -> DRM/Intel
  [   43.836647] [drm] drm/i915 developers can then reassign to the right 
component if it's not a kernel issue.
  [   43.836648] [drm] The gpu crash dump is required to analyze gpu hangs, so 
please always attach it.
  [   43.836649] [drm] GPU crash dump saved to /sys/class/drm/card0/error
  [   43.836718] drm/i915: Resetting chip after gpu hang
  [   55.812149] drm/i915: Resetting chip after gpu hang
  [   63.840645] drm/i915: Resetting chip after gpu hang
  [   71.836614] drm/i915: Resetting chip after gpu hang
  [   79.836882] drm/i915: Resetting chip after gpu hang
  [   88.828508] drm/i915: Resetting chip after gpu hang

  have tried kernel parameter intel_iommu=off, intel_iommu=igfx_off, 
i915.enable_rc6=0 with no better results.
  lshw, dmesg and card0/error file attached.

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

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

[Kernel-packages] [Bug 1738962] [NEW] Failed to build upstream bpf test on Artful ARM64

[Po-Hsu Lin]

Public bug reported:

Steps:
 1. git clone --depth=1 https://github.com/torvalds/linux.git
 2. sudo apt-get install clang llvm libcap-dev libelf-dev build-essential 
 3. Change the Makefile in linux/tools/testing/selftests/ to build bpf test only
 4. make

Result:
 * It complains about missing headers, like the 'bits/libc-header-start.h', but 
it can be found in /usr/include/aarch64-linux-gnu/bits/
 
$ find /usr -name libc-header-start.h
/usr/include/aarch64-linux-gnu/bits/libc-header-start.h

$ dpkg -S libc-header-start.h
libc6-dev:arm64: /usr/include/aarch64-linux-gnu/bits/libc-header-start.h


$ make
make[1]: Entering directory '/home/ubuntu/linux/tools/testing/selftests/bpf'
make -C ../../../lib/bpf OUTPUT=/home/ubuntu/linux/tools/testing/selftests/bpf/
make[2]: Entering directory '/home/ubuntu/linux/tools/lib/bpf'
make[2]: Leaving directory '/home/ubuntu/linux/tools/lib/bpf'
make -C ../../../lib/bpf OUTPUT=/home/ubuntu/linux/tools/testing/selftests/bpf/
make[2]: Entering directory '/home/ubuntu/linux/tools/lib/bpf'
make[2]: Leaving directory '/home/ubuntu/linux/tools/lib/bpf'
gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_verifier.c 
/home/ubuntu/linux/tools/testing/selftests/bpf/libbpf.a 
/home/ubuntu/linux/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -o 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_verifier
gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_tag.c 
/home/ubuntu/linux/tools/testing/selftests/bpf/libbpf.a 
/home/ubuntu/linux/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -o 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_tag
gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_maps.c 
/home/ubuntu/linux/tools/testing/selftests/bpf/libbpf.a 
/home/ubuntu/linux/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -o 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_maps
gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_lru_map.c 
/home/ubuntu/linux/tools/testing/selftests/bpf/libbpf.a 
/home/ubuntu/linux/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -o 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_lru_map
gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_lpm_map.c 
/home/ubuntu/linux/tools/testing/selftests/bpf/libbpf.a 
/home/ubuntu/linux/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -o 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_lpm_map
gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_progs.c 
/home/ubuntu/linux/tools/testing/selftests/bpf/libbpf.a 
/home/ubuntu/linux/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -o 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_progs
gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_align.c 
/home/ubuntu/linux/tools/testing/selftests/bpf/libbpf.a 
/home/ubuntu/linux/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -o 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_align
gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_verifier_log.c 
/home/ubuntu/linux/tools/testing/selftests/bpf/libbpf.a 
/home/ubuntu/linux/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -o 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_verifier_log
gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_dev_cgroup.c 
/home/ubuntu/linux/tools/testing/selftests/bpf/libbpf.a 
/home/ubuntu/linux/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -o 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_dev_cgroup
clang -I. -I./include/uapi -I../../../include/uapi \
 -Wno-compare-distinct-pointer-types  \
 -O2 -target bpf -emit-llvm -c 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_pkt_access.c -o - |  \
llc -march=bpf -mcpu=generic -filetype=obj -o 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_pkt_access.o
In file included from 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_pkt_access.c:8:
/usr/include/string.h:26:10: fatal error: 'bits/libc-header-start.h' file not 
found
#include 
 ^~
1 error generated.
clang -I. -I./include/uapi -I../../../include/uapi \
 -Wno-compare-distinct-pointer-types  \
 -O2 -target bpf -emit-llvm -c 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_xdp.c -o - |  \
llc -march=bpf -mcpu=generic -filetype=obj -o 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_xdp.o
In file included from 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_xdp.c:8:

[Kernel-packages] [Bug 1626299] Re: ACPI Errors in dmesg, battery monitor shows empty

[Andrea]

I have the same machine, by the way i opened a new bug here

https://bugzilla.kernel.org/show_bug.cgi?id=198177

** Bug watch added: Linux Kernel Bug Tracker #198177
   https://bugzilla.kernel.org/show_bug.cgi?id=198177

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

Title:
  ACPI Errors in dmesg, battery monitor shows empty

Status in linux package in Ubuntu:
  Expired

Bug description:
  I am using Xubuntu, and the power manager show an empty battery at all
  times, regardless of battery level. I essentially have no indicators
  of how much power my laptop has left. Once I run out of power, the
  laptop obviously shuts down causing data corruption.

  my dmesg shows:

  [   10.587295] ACPI Error: No handler for Region [PMRG] (88015a0c0090) 
[GenericSerialBus] (20150930/evregion-163)
  [   10.587303] ACPI Error: Region GenericSerialBus (ID=9) has no handler 
(20150930/exfldio-297)
  [   10.587309] ACPI Error: Method parse/execution failed [\_SB.TAMB._TMP] 
(Node 88015a0f7208), AE_NOT_EXIST (20150930/psparse-542)
  [   10.587325] thermal thermal_zone0: failed to read out thermal zone (-5)
  [   10.598876] ACPI Error: No handler for Region [PMRG] (88015a0c0090) 
[GenericSerialBus] (20150930/evregion-163)
  [   10.598882] ACPI Error: Region GenericSerialBus (ID=9) has no handler 
(20150930/exfldio-297)
  [   10.598886] ACPI Error: Method parse/execution failed [\_SB.TEFN._TMP] 
(Node 88015a0f76e0), AE_NOT_EXIST (20150930/psparse-542)
  [   10.598898] thermal thermal_zone1: failed to read out thermal zone (-5)
  [   10.600460] ACPI Error: No handler for Region [PMRG] (88015a0c0090) 
[GenericSerialBus] (20150930/evregion-163)
  [   10.600465] ACPI Error: Region GenericSerialBus (ID=9) has no handler 
(20150930/exfldio-297)
  [   10.600469] ACPI Error: Method parse/execution failed [\_SB.TSKN._TMP] 
(Node 88015a0f94b0), AE_NOT_EXIST (20150930/psparse-542)
  [   10.600479] thermal thermal_zone2: failed to read out thermal zone (-5)

  later it shows:

  [   11.235601] acer_wmi: Enabling Launch Manager failed: 0xe4 - 0x0

  
  It's unfortunate to never know how much power is left, as one might imagine.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  coder  1607 F pulseaudio
   /dev/snd/controlC1:  coder  1607 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Sep 22 00:34:51 2016
  HibernationDevice: RESUME=UUID=c0846449-28bd-4d6a-9ccb-732cf1582f3a
  InstallationDate: Installed on 2016-09-08 (13 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Acer Aspire SW5-173
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/11/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.08
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Crepe
  dmi.board.vendor: Acer
  dmi.board.version: V1.08
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.08
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.08:bd04/11/2016:svnAcer:pnAspireSW5-173:pvrV1.08:rvnAcer:rnCrepe:rvrV1.08:cvnAcer:ct9:cvrV1.08:
  dmi.product.name: Aspire SW5-173
  dmi.product.version: V1.08
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1738839] Re: [Medion S2217] Touchpad not properly recognized

[Full Name]

*** This bug is a duplicate of bug 1400463 ***
https://bugs.launchpad.net/bugs/1400463

I think the kernel-bug-exists-upstream

See here: https://marc.info/?l=linux-input=150150074208646

** This bug has been marked a duplicate of bug 1400463
   [Medion Akoya P2214T] Touchpad not properly recognized

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

Title:
  [Medion S2217] Touchpad not properly recognized

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The ELAN (not Elantech) touchpad in my Medion S2217 laptop is not
  properly recognized. The touchpad shows up as an ITE Tech. Inc. ITE
  Device(8910) and works only as a plain pointing device. Multitouch and
  scrolling or anything else however, do not function, nor do options
  for this show up in the Mouse & Touchpad options in Ubuntu.

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

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

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

[Brad Figg]

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

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

Title:
  linux-lts-trusty: 3.13.0-138.187~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:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  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: 1737911
  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/1737913/+subscriptions

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

[Kernel-packages] [Bug 1737920] Re: linux-aws: 4.4.0-1045.54 -proposed tracker

[Brad Figg]

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

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

Title:
  linux-aws: 4.4.0-1045.54 -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  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: 1737916
  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/1737920/+subscriptions

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

[Kernel-packages] [Bug 1737911] Re: linux: 3.13.0-138.187 -proposed tracker

[Po-Hsu Lin]

No bug was tagged with verification-needed for this kernel.

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

** Changed in: kernel-sru-workflow/verification-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

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

Title:
  linux: 3.13.0-138.187 -proposed tracker

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

Bug description:
  This bug is for tracking the  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: 1737913
  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/1737911/+subscriptions

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

[Kernel-packages] [Bug 1737916] Re: linux: 4.4.0-105.128 -proposed tracker

[Po-Hsu Lin]

No bug was tagged with verification-needed for this kernel.

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

** Changed in: kernel-sru-workflow/verification-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

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

Title:
  linux: 4.4.0-105.128 -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  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: 1737918,1737919
  derivatives: 1737920,1737921,1737922,1737923,1737925,1737927
  -- 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/1737916/+subscriptions

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

[Kernel-packages] [Bug 1737918] Re: linux-aws: 4.4.0-1007.7 -proposed tracker

[Po-Hsu Lin]

No bug was tagged with verification-needed for this kernel.

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

** Changed in: kernel-sru-workflow/verification-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

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

Title:
  linux-aws: 4.4.0-1007.7 -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws 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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1737916
  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/1737918/+subscriptions

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

[Kernel-packages] [Bug 1738224] Re: Suspend broken after kernel upgrade

[Kai-Heng Feng]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

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

Title:
  Suspend broken after kernel upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My machine (XPS 13 9360) won't go into suspend properly after
  upgrading from linux-image-4.13.0-17-generic to linux-
  image-4.13.0-19-generic.

  This affects both suspend through lid close and "systemctl suspend".
  Screen goes off, power led remains lit. Then after some time the
  screen comes back on, is stuck and lets me wait for a few before
  becoming responsive again.

  Booting back into 4.13.0-17 resolved the issue.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeffrey1963 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5
  InstallationDate: Installed on 2017-10-18 (56 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker input libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.3.1
  dmi.board.name: 0839Y6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.3.1:bd10/03/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue

[Kai-Heng Feng]

Shawn Thornton,

Do you still have this issue?

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

Title:
  Not Suspending When Lid is Closed Causing Heat Issue

Status in linux package in Ubuntu:
  Expired

Bug description:
  I installed Ubuntu Budgie 17.04 64-bit. I installed the operating
  system and then when booted, I apt-get update and apt-get upgrade. I
  went to the coffee shop and used the system for a while. When I came
  home I left my laptop Dell XPS 9360 in its leather case and inside my
  laptop bag. I left to do some errands and came back to a really hot
  laptop and case. The system had not gone to sleep when I closed the
  lid and the computer was very hot. I have attached a copy of the log
  files.

  I then:

  sudo vi /etc/systemd/logind.conf

  Changed: HandleLidSwitchDocked=suspend

  when I close the lid now it gives me a password to login when I open the lid, 
but I am not sure if it is sleeping properly. Please assist, as I do not want 
my laptop battery damaged by this heat again.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shawn  1786 F pulseaudio
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-04 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/02/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.0
  dmi.board.name: 05JK94
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.0:bd08/02/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue

[Launchpad Bug Tracker]

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

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

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

Title:
  Not Suspending When Lid is Closed Causing Heat Issue

Status in linux package in Ubuntu:
  Expired

Bug description:
  I installed Ubuntu Budgie 17.04 64-bit. I installed the operating
  system and then when booted, I apt-get update and apt-get upgrade. I
  went to the coffee shop and used the system for a while. When I came
  home I left my laptop Dell XPS 9360 in its leather case and inside my
  laptop bag. I left to do some errands and came back to a really hot
  laptop and case. The system had not gone to sleep when I closed the
  lid and the computer was very hot. I have attached a copy of the log
  files.

  I then:

  sudo vi /etc/systemd/logind.conf

  Changed: HandleLidSwitchDocked=suspend

  when I close the lid now it gives me a password to login when I open the lid, 
but I am not sure if it is sleeping properly. Please assist, as I do not want 
my laptop battery damaged by this heat again.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shawn  1786 F pulseaudio
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-04 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/02/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.0
  dmi.board.name: 05JK94
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.0:bd08/02/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1668062] Re: Black screen after waking from suspend, need to reboot to use the PC

[nullsteph]

Nope, it stopped working again.  I have the same problem as the OP.

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

Title:
  Black screen after waking from suspend, need to reboot to use the PC

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I installed a fresh Ubuntu 16.10.
  When I try to wake the system from suspend, I only get a black screen.
  The LCD back-light gets light up, the mouse pointer shows up, and it can be 
moved, but then I do not get anything else on the screen.

  I can still use Ctrl+Alt+F1 to switch to text screen.
  Switching  back with Alt+F7 leads back to the black screen.

  This makes it impossible to use Ubuntu 16.10, please address.
  I use Fedora 25 now, and does not suffer the same issue.

  I am happy to provide more details (hardware, logs), please let me
  know.

  Best regards,
  Marton
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D7p:   csalad22310 F...m pulseaudio
   /dev/snd/controlC1:  csalad22310 F pulseaudio
   /dev/snd/controlC0:  csalad22310 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=0d7c78b5-bcee-4f78-ac98-35861e943e69
  InstallationDate: Installed on 2017-02-22 (10 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-39-generic 
root=UUID=080d6932-790b-4bd2-84a7-c81995d324cc ro quiet splash
  ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-39-generic N/A
   linux-backports-modules-4.8.0-39-generic  N/A
   linux-firmware1.161.1
  RfKill:
   
  Tags:  yakkety
  Uname: Linux 4.8.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2507
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F1A75-V 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.:bvr2507:bd01/29/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF1A75-VPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1668062] Re: Black screen after waking from suspend, need to reboot to use the PC

[nullsteph]

I had to downgrade Nvidia driver from 384.xx to 381.34, running Ubu
17.04.

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

Title:
  Black screen after waking from suspend, need to reboot to use the PC

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I installed a fresh Ubuntu 16.10.
  When I try to wake the system from suspend, I only get a black screen.
  The LCD back-light gets light up, the mouse pointer shows up, and it can be 
moved, but then I do not get anything else on the screen.

  I can still use Ctrl+Alt+F1 to switch to text screen.
  Switching  back with Alt+F7 leads back to the black screen.

  This makes it impossible to use Ubuntu 16.10, please address.
  I use Fedora 25 now, and does not suffer the same issue.

  I am happy to provide more details (hardware, logs), please let me
  know.

  Best regards,
  Marton
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D7p:   csalad22310 F...m pulseaudio
   /dev/snd/controlC1:  csalad22310 F pulseaudio
   /dev/snd/controlC0:  csalad22310 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=0d7c78b5-bcee-4f78-ac98-35861e943e69
  InstallationDate: Installed on 2017-02-22 (10 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-39-generic 
root=UUID=080d6932-790b-4bd2-84a7-c81995d324cc ro quiet splash
  ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-39-generic N/A
   linux-backports-modules-4.8.0-39-generic  N/A
   linux-firmware1.161.1
  RfKill:
   
  Tags:  yakkety
  Uname: Linux 4.8.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2507
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F1A75-V 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.:bvr2507:bd01/29/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF1A75-VPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

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

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

Title:
  PGD 0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running the latest 18.04 daily (desktop), selected try out, opened a terminal 
window and a few seconds after I got the error.
  I was going to select install ...

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-17-generic 4.13.0-17.20
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 4264 F pulseaudio
   /dev/snd/controlC2:  ubuntu 4264 F pulseaudio
   /dev/snd/controlC0:  ubuntu 4264 F pulseaudio
  CasperVersion: 1.387
  Date: Tue Dec 19 03:33:40 2017
  Failure: oops
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171218)
  MachineType: Dell Inc. Precision T5600
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: PGD 0
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0Y56T3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd05/06/2017:svnDellInc.:pnPrecisionT5600:pvr01:rvnDellInc.:rn0Y56T3:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T5600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1738837] Re: BUG: unable to handle kernel NULL pointer dereference at (null)

[Maraschin]

I just got it again, inside 18.04 installation...
It is going to generate the same report...

Shall I collect anything in special??

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

Title:
  BUG: unable to handle kernel NULL pointer dereference at
  (null)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Just trying to run ubuntu 17.10 desktop installation and selected TRY
  it out...

  ProblemType: KernelOops
  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 x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  ubuntu 4342 F pulseaudio
   /dev/snd/controlC0:  ubuntu 4342 F pulseaudio
   /dev/snd/controlC1:  ubuntu 4342 F pulseaudio
  CasperVersion: 1.387
  Date: Mon Dec 18 15:55:33 2017
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at  
 (null) RIP: isci_task_abort_task+0x43/0x4e0 [isci] RSP: 
a693c7967c80
  Failure: oops
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Dell Inc. Precision T5600
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: BUG: unable to handle kernel NULL pointer dereference at   
(null)
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0Y56T3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd05/06/2017:svnDellInc.:pnPrecisionT5600:pvr01:rvnDellInc.:rn0Y56T3:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T5600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1738837] Re: BUG: unable to handle kernel NULL pointer dereference at (null)

[Maraschin]

See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738921

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

Title:
  BUG: unable to handle kernel NULL pointer dereference at
  (null)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Just trying to run ubuntu 17.10 desktop installation and selected TRY
  it out...

  ProblemType: KernelOops
  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 x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  ubuntu 4342 F pulseaudio
   /dev/snd/controlC0:  ubuntu 4342 F pulseaudio
   /dev/snd/controlC1:  ubuntu 4342 F pulseaudio
  CasperVersion: 1.387
  Date: Mon Dec 18 15:55:33 2017
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at  
 (null) RIP: isci_task_abort_task+0x43/0x4e0 [isci] RSP: 
a693c7967c80
  Failure: oops
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Dell Inc. Precision T5600
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: BUG: unable to handle kernel NULL pointer dereference at   
(null)
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0Y56T3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd05/06/2017:svnDellInc.:pnPrecisionT5600:pvr01:rvnDellInc.:rn0Y56T3:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T5600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1738921] [NEW] PGD 0

[Maraschin]

Public bug reported:

Running the latest 18.04 daily (desktop), selected try out, opened a terminal 
window and a few seconds after I got the error.
I was going to select install ...

ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.13.0-17-generic 4.13.0-17.20
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.8-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  ubuntu 4264 F pulseaudio
 /dev/snd/controlC2:  ubuntu 4264 F pulseaudio
 /dev/snd/controlC0:  ubuntu 4264 F pulseaudio
CasperVersion: 1.387
Date: Tue Dec 19 03:33:40 2017
Failure: oops
IwConfig:
 lono wireless extensions.
 
 enp0s25   no wireless extensions.
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171218)
MachineType: Dell Inc. Precision T5600
ProcFB: 0 nouveaufb
ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: PGD 0
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/06/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.name: 0Y56T3
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd05/06/2017:svnDellInc.:pnPrecisionT5600:pvr01:rvnDellInc.:rn0Y56T3:rvrA01:cvnDellInc.:ct7:cvr:
dmi.product.name: Precision T5600
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-kerneloops bionic kernel-driver-isci 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/1738921

Title:
  PGD 0

Status in linux package in Ubuntu:
  New

Bug description:
  Running the latest 18.04 daily (desktop), selected try out, opened a terminal 
window and a few seconds after I got the error.
  I was going to select install ...

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-17-generic 4.13.0-17.20
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 4264 F pulseaudio
   /dev/snd/controlC2:  ubuntu 4264 F pulseaudio
   /dev/snd/controlC0:  ubuntu 4264 F pulseaudio
  CasperVersion: 1.387
  Date: Tue Dec 19 03:33:40 2017
  Failure: oops
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171218)
  MachineType: Dell Inc. Precision T5600
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: PGD 0
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0Y56T3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd05/06/2017:svnDellInc.:pnPrecisionT5600:pvr01:rvnDellInc.:rn0Y56T3:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T5600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1737934] Re: Samsung SM961 NVMe SSD randomly unmounts/loses connection/unavailable

[Kai-Heng Feng]

Can you attach output of `nvme get-feature -f 0x0c -H /dev/nvme0` with
kernel in comment #13?

Also `sudo lspci -vvv`.

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

Title:
  Samsung SM961 NVMe SSD randomly unmounts/loses connection/unavailable

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Seems related to these bugs:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
  https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1682704
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748

  Problem:
  At seemingly random times my computer (brand new Lenovo Thinkpad T470) seems 
to lose access to the Samsung SM961 256GB SSD drive it has inside. When this 
happens the whole OS freezes up and when I try to power down I see a black 
terminal-like screen that prints the following errors:

  EXT4-fs error (device nvme0n1p2): ext4_find_entry:1431: inode #7471275
  (or #741278): comm gmain (or systemd-journal or ...): reading
  directory iblock 0

  This error seems to be repeated endlessly, though I've only let it go
  for a few minutes. No other errors are printed.

  This is the only drive it has.
  I don't know if this occurs in Windows too since I removed Windows and 
installed Ubuntu immediatly after updating the BIOS.

  Info:
  Distro: Ubuntu MATE 17.10

  sudo uname -r
  4.13.0-19-generic

  sudo nvme get-feature -f 0x0c -H /dev/nvme0 (with latency set to 250)
  get-feature:0xc (Autonomous Power State Transition), Current value:0x01
Autonomous Power State Transition Enable (APSTE): Enabled
Auto PST Entries.
Entry[ 0]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 1]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 2]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 3]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 4]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 5]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 6]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 7]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 8]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 9]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[10]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[11]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[12]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[13]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[14]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[15]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[16]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[17]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[18]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0

[Kernel-packages] [Bug 1738837] Re: BUG: unable to handle kernel NULL pointer dereference at (null)

[Maraschin]

I've managed to install it using 17.10 server but when I reboot I get the same 
error.
I'm having another problem, any version I try to install 16.04, 17.10, 18.04... 
DO NOT LET ME select the keyboard! My problem is that I'm trying to install 
English language on a computer with Swedish keyboard. I tried to install 
Swedish but after reboot it goes to English and I can't enter the encryption 
key...

I tried Bionic Beaver server, I can't select the option to manually set the 
partitions!
I can't use full disk! I've a windows disk with /boot partition and I want to 
encrypt the Ubuntu disk ...

I will try  Bionic Beaver desktop now...

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

Title:
  BUG: unable to handle kernel NULL pointer dereference at
  (null)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Just trying to run ubuntu 17.10 desktop installation and selected TRY
  it out...

  ProblemType: KernelOops
  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 x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  ubuntu 4342 F pulseaudio
   /dev/snd/controlC0:  ubuntu 4342 F pulseaudio
   /dev/snd/controlC1:  ubuntu 4342 F pulseaudio
  CasperVersion: 1.387
  Date: Mon Dec 18 15:55:33 2017
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at  
 (null) RIP: isci_task_abort_task+0x43/0x4e0 [isci] RSP: 
a693c7967c80
  Failure: oops
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Dell Inc. Precision T5600
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: BUG: unable to handle kernel NULL pointer dereference at   
(null)
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0Y56T3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd05/06/2017:svnDellInc.:pnPrecisionT5600:pvr01:rvnDellInc.:rn0Y56T3:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T5600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1738404] Re: Bluetooth sound extreme low quality

[Daniel van Vugt]

OK. If you wish to use Ubuntu 17.10 or later and still have a problem
then please try the next step: Find an older kernel more in line with
what 17.04 had (kernel version 4.10 or older): http://kernel.ubuntu.com
/~kernel-ppa/mainline/?C=N;O=D

If you can find the kernel version it stopped working in then we can
work with the kernel team to get a fix.

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

Title:
  Bluetooth sound extreme low quality

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I upgraded today from ubuntu 17.04 to ubuntu 17.10.

  I use 3 different bluetooth audio devices ( BT earphones, BT speaker,
  BT BOSE Soundlink speaker) , all of them worked properly on 17.04.

  Since the upgrade, the sound gets continuous interruptions/cracking. 
  These sound interruptions and cracking are so annoying that I cannot keep on 
listening to music.
  I could relate this to the fact that a new BT stack has replaced the former 
in Ubuntu.

  If I use wired devices (hdmi connected screen+audio, the sound quality is 
good and as before) so the issue is related to the use of the new Bluetooth 
stack.
  I have not found a way to parameterise it neither.

  I have not found any similar report. "apport" seems not ot exist in
  thise version, I cannot find and execute it.

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

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

[Kernel-packages] [Bug 1738838] Re: bluetooth does not turn on; settings interfaces are nonsensical

[Daniel van Vugt]

** Also affects: gnome-control-center (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  bluetooth does not turn on; settings interfaces are nonsensical

Status in bluez package in Ubuntu:
  New
Status in gnome-control-center package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  See video. I have installed bluetooth, blueman, bluez but it makes no
  difference to a broken interface to control bluetooth under Gnome
  17.10, as shown in the attached video.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluetooth 5.46-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 17 22:32:30 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-18 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: bnep btusb bluetooth
  MachineType: LENOVO 20BXCTO1WW
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed 
root=UUID=02bd5120-a925-442c-a0dd-1cce59920632 ro quiet splash 
psmouse.synaptics_intertouch=0 vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET54WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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

[Kernel-packages] [Bug 1738907] Re: Bluetooth audio latency / delay increasing on video streamig

[Daniel van Vugt]

If the delay increases over time then mathematically it sounds like the
output is consuming bits slower than the input. So /maybe/ you have
48kHz audio being played at 44.1kHz but I would have thought that would
be noticeable (sounding distorted - too low). And even if that's not the
problem, the delay should hit a limit via some buffering limit, after
which it turns into skipping (bug 405294).

Another thought is to see the suggestion in bug 1677202.

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

Title:
  Bluetooth audio latency / delay increasing on video streamig

Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  With my bluetooth headset (A2DP audio protocole) when I watch videos
  streaming with Google Chrome for example. there is a delay increasing
  between audio and video. I tried to change and set up the audio
  latency, but the delay increase, as much as I play bigger video

  
  ubuntu 17.04 or 17.10 64bit

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

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

[Kernel-packages] [Bug 1738907] Re: Bluetooth audio latency / delay increasing on video streamig

[Daniel van Vugt]

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

** Tags added: a2dp

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

Title:
  Bluetooth audio latency / delay increasing on video streamig

Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  With my bluetooth headset (A2DP audio protocole) when I watch videos
  streaming with Google Chrome for example. there is a delay increasing
  between audio and video. I tried to change and set up the audio
  latency, but the delay increase, as much as I play bigger video

  
  ubuntu 17.04 or 17.10 64bit

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

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

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

[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 1738911

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

Title:
  Support realtek new codec alc257 in the alsa hda driver

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Otherwise, the kernel will load generic codec driver, this will
  introduce lots of problem like mute/micmute hotkey can't work.

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

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

[Kernel-packages] [Bug 1738911] [NEW] Support realtek new codec alc257 in the alsa hda driver

[Hui Wang]

Public bug reported:

Otherwise, the kernel will load generic codec driver, this will
introduce lots of problem like mute/micmute hotkey can't work.

** Affects: hwe-next
 Importance: High
 Assignee: Hui Wang (hui.wang)
 Status: New

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Hui Wang (hui.wang)
 Status: New


** Tags: originate-from-1726245 sutton

** Tags added: originate-from-1726245 sutton

** Changed in: hwe-next
   Importance: Undecided => High

** Changed in: hwe-next
 Assignee: (unassigned) => Hui Wang (hui.wang)

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

Title:
  Support realtek new codec alc257 in the alsa hda driver

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Otherwise, the kernel will load generic codec driver, this will
  introduce lots of problem like mute/micmute hotkey can't work.

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

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

[Kernel-packages] [Bug 1732627] Re: enable CONFIG_SND_SOC_INTEL_BYT_CHT_NOCODEC_MACH easily confuse users

[Hui Wang]

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

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

Title:
  enable CONFIG_SND_SOC_INTEL_BYT_CHT_NOCODEC_MACH easily confuse users

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  The author of this config (pierre-louis.boss...@linux.intel.com)
  suggested that we should disable this config from ubuntu artful
  kernel, he said, "this is really for test environments or platforms
  with a connector. I don't think it should be enabled by default
  (better to fail the probe rather than get questions from users that
  they have no sound)."

  I also investigated this issue on my own, if our kernel is running on
  a platform which has a codec and the codec is supported by the
  existing driver, enabling this config will not bring side effect;
  if the platform has a codec but the codec is not supported by existing
  driver yet, the driver will fallback to this NOCODEC_MACH if this
  config is enabled, and snd-soc-sst-byt-cht-nocodec.ko will be loaded
  into the kernel, then user is easily confused that the kernel driver
  is loaded but I can't hear sound from the codec.

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

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

[Kernel-packages] [Bug 1510570] Re: Bluetooth LE pairing fail

[Yuan-Chen Cheng]

** Tags added: risk

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

Title:
  Bluetooth LE pairing fail

Status in OEM Priority Project:
  Confirmed
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Xenial:
  Confirmed

Bug description:
  [Impact]

  When the Bluetooth adapter is not powered on it is not possible to use
  it in normal way. We used to have a hack to force powering on by using
  an udev rule but this doe snot work anymore. Luckily the BlueZ has
  introduced "AutoEnable" option that makes the stack power on adapters by
  itself.

  Backporting this to xenial will improve life of the desktop users and
  will not require them to hack the solution on their own. The fix itself
  uses the well known solution to this problem that is floating around
  there for a while.

  The upload fixes the bug by enabling the 'AutoEnable' option in the
  bluetoothd config file.

  [Original Report]

  . 15.10 we now have bluez 5 so we can pair BLE devices like the
  Microsoft Arc Touch Bluetooth Mouse.

  But this pairing doesn't work very well. Mouse is seen but pairing fail.
  More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5

  This is due to udev rule that use "hcitool" to power on device.
  Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used
  instead of udev rules.

  here is a commit with this parameter:
  http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138

  [Test Case]

  Edit the /etc/bluetooth/main.conf and disable the 'AutoEnable' option.
  Remove file 50-bluetooth-hci-auto-poweron.rules located in
  /lib/udev/rules.d. Now reboot the machine. The BT adapter shall be
  powered off now.

  [Regression Potential]

  Cannot think of any

  [Other Info]

  This fix is included in the development release, see:
  http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions

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

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

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

Title:
  bug

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  freeze

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-19-generic 4.13.0-19.22
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ashish22207 F...m pulseaudio
   /dev/snd/controlC0:  ashish22207 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 16 15:33:49 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  HibernationDevice: RESUME=UUID=c1d38ce9-44c1-4c9c-899d-f4d1efaab9e5
  MachineType: Dell Inc. Vostro 14-3468
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=63f0bf97-2f6f-4571-954a-855cc648aa65 ro acpi_rev_override 
locale=en_GB splash acpi_osi=Linux quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-12-05 (10 days ago)
  dmi.bios.date: 03/23/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.08.00
  dmi.board.name: 0T1X3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:svnDellInc.:pnVostro14-3468:pvr:rvnDellInc.:rn0T1X3V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 14-3468
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1738823] Re: linux: 4.13.0-21.24 -proposed tracker

[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
  
  kernel-stable-phase-changed:Monday, 18. December 2017 18:02 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/1738823

Title:
  linux: 4.13.0-21.24 -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-meta series:
  Fix Released
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

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

  kernel-stable-phase-changed:Monday, 18. December 2017 18:02 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/1738823/+subscriptions

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

[Kernel-packages] [Bug 1738530] Re: bug

[Seth Arnold]

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

** Information type changed from Private Security to Public

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

Title:
  bug

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  freeze

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-19-generic 4.13.0-19.22
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ashish22207 F...m pulseaudio
   /dev/snd/controlC0:  ashish22207 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 16 15:33:49 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  HibernationDevice: RESUME=UUID=c1d38ce9-44c1-4c9c-899d-f4d1efaab9e5
  MachineType: Dell Inc. Vostro 14-3468
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=63f0bf97-2f6f-4571-954a-855cc648aa65 ro acpi_rev_override 
locale=en_GB splash acpi_osi=Linux quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-12-05 (10 days ago)
  dmi.bios.date: 03/23/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.08.00
  dmi.board.name: 0T1X3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:svnDellInc.:pnVostro14-3468:pvr:rvnDellInc.:rn0T1X3V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 14-3468
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1737903] Re: linux: 4.13.0-20.23 -proposed tracker

[Thadeu Lima de Souza Cascardo]

*** This bug is a duplicate of bug 1738823 ***
https://bugs.launchpad.net/bugs/1738823

** This bug has been marked a duplicate of bug 1738823
   linux: 4.13.0-21.24 -proposed tracker

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

Title:
  linux: 4.13.0-20.23 -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-meta series:
  Fix Released
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: 1737905,1737906,1737907,1737908
  derivatives: 1737909
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Wednesday, 13. December 2017 19:36 UTC

  -- swm properties --
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1738907] [NEW] Bluetooth audio latency / delay increasing on video streamig

[Jo Melnik]

Public bug reported:

With my bluetooth headset (A2DP audio protocole) when I watch videos
streaming with Google Chrome for example. there is a delay increasing
between audio and video. I tried to change and set up the audio latency,
but the delay increase, as much as I play bigger video


ubuntu 17.04 or 17.10 64bit

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

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

Title:
  Bluetooth audio latency / delay increasing on video streamig

Status in bluez package in Ubuntu:
  New

Bug description:
  With my bluetooth headset (A2DP audio protocole) when I watch videos
  streaming with Google Chrome for example. there is a delay increasing
  between audio and video. I tried to change and set up the audio
  latency, but the delay increase, as much as I play bigger video

  
  ubuntu 17.04 or 17.10 64bit

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

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

[Kernel-packages] [Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react

[Cubic PPA]

Looking forward to this fix. Do we know when linux-firmware version
1.169.2 will be in the Ubuntu repositories?

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

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Confirmed
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Confirmed
Status in linux-firmware source package in Artful:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Bluetooth peripherals work initially but stop working shortly
  with Linux 4.13.

  Fix: Updated firmware from Intel containing a fix for the issue.

  Regression Potential: Any firmware updates may bring regressions,
  however this is a bug fix update and therefore regression potential is
  expected to be minimal.

  ---

  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  ---
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp.
   Bus 001 Device 005: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 13d3:5664 IMC Networks
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  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: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
    UP RUNNING PSCAN ISCAN INQUIRY
    RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
    TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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

[Kernel-packages] [Bug 1716009] Re: problem with the sound since the latest update

[FilipGH]

not sure if this may be a cause of the problem, but, just for the
record, i am with gnome-session-flashback latest version, which has not
been upgraded for about 2 years

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

Title:
  problem with the sound since the latest update

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  i am with an old intel chipset motherboard having an integrated
  realtek alc888 sound, and Ubuntu 16.04 Desktop (64-bit); since the
  latest update there has had no effect when adjusting sound volume from
  the sound menu on the menu bar and sound settings, and no sound in
  counter strike 1.6 linux version, also, there has appeared an effect
  of a sound interruption/break (for less than a second) when switching
  between applications, however, i can still adjust the sound volume
  from gnome alsa mixer

  the latest update includes:

  snapd-login-service:amd64
  libsnapd-glib1:amd64
  linux-firmware:amd64
  libgd3:amd64

  the previous ——:

  libpackagekit-glib2-16:amd64
  gir1.2-packagekitglib-1.0:amd64

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

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

[Kernel-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

[Pete Hildebrandt]

Ubuntu: 17.10
Mainline Kernel: 4.14.7

Still not working :(

anti-egos fix didn't 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/1589008

Title:
  Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  In 16.04 when a bluetooth audio device is connected it freezes video
  playback and also no sound comes from online audio only streams. Issue
  does not exist with a wired headset.

  This issue does not exist with 15.10. All updates have been installed
  on 16.04 including backports but they have not fixed the issue.

  It is not browser specific and not website specific.

  It is not hardware specific as it affects my laptop with an intel 7260
  card and my pc with an intel 8260 card.

  The issue exists on both ubuntu and kubuntu 16.04.

  I have reported it on the ubuntu support forums and after
  investigation a moderator noticed changed in the kernel from 4.4 and
  4.2 that may becausing the issue and asked me to file a bug report.

  The ubuntu forum thread can be found here.
  http://ubuntuforums.org/showthread.php?t=2326672

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-23-generic 4.4.0-23.41
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stephen1435 F pulseaudio
   /dev/snd/controlC0:  stephen1435 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun  3 23:50:00 2016
  HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6
  InstallationDate: Installed on 2016-05-06 (28 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7978
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H170 GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel opps destroying interfaces on i386

[Joseph Salisbury]

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

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

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

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

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

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

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

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

Title:
  openvswitch: kernel opps destroying interfaces on i386

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

Bug description:
  Reproducable on bionic using the autopkgtest's from openvswitch on
  i386:

  [   41.420568] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [   41.421000] IP: igmp_group_dropped+0x21/0x220
  [   41.421246] *pdpt = 1d62c001 *pde =  

  [   41.421659] Oops:  [#1] SMP
  [   41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass 
input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg 
mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse 
virtio_blk virtio_net pata_acpi floppy
  [   41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW   
4.13.0-18-generic #21-Ubuntu
  [   41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [   41.424849] Workqueue: netns cleanup_net
  [   41.425071] task: db8fba80 task.stack: dba1
  [   41.425346] EIP: igmp_group_dropped+0x21/0x220
  [   41.425656] EFLAGS: 00010202 CPU: 0
  [   41.425864] EAX:  EBX: dd726360 ECX: dba11e6c EDX: 0002
  [   41.426335] ESI:  EDI: dd4db500 EBP: dba11dcc ESP: dba11d94
  [   41.426687]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [   41.426990] CR0: 80050033 CR2:  CR3: 1e6d6d60 CR4: 06f0
  [   41.427340] Call Trace:
  [   41.427485]  ? __wake_up+0x36/0x40
  [   41.427680]  ip_mc_down+0x27/0x90
  [   41.427869]  inetdev_event+0x398/0x4e0
  [   41.428082]  ? skb_dequeue+0x5b/0x70
  [   41.428286]  ? wireless_nlevent_flush+0x4c/0x90
  [   41.428541]  notifier_call_chain+0x4e/0x70
  [   41.428772]  raw_notifier_call_chain+0x11/0x20
  [   41.429023]  call_netdevice_notifiers_info+0x2a/0x60
  [   41.429301]  dev_close_many+0x9d/0xe0
  [   41.429509]  rollback_registered_many+0xd7/0x380
  [   41.429768]  unregister_netdevice_many.part.102+0x10/0x80
  [   41.430075]  default_device_exit_batch+0x134/0x160
  [   41.430344]  ? do_wait_intr_irq+0x80/0x80
  [   41.430650]  ops_exit_list.isra.8+0x4d/0x60
  [   41.430886]  cleanup_net+0x18e/0x260
  [   41.431090]  process_one_work+0x1a0/0x390
  [   41.431317]  worker_thread+0x37/0x450
  [   41.431525]  kthread+0xf3/0x110
  [   41.431714]  ? process_one_work+0x390/0x390
  [   41.431941]  ? kthread_create_on_node+0x20/0x20
  [   41.432187]  ret_from_fork+0x19/0x24
  [   41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 
56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 
8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00
  [   41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94
  [   41.433750] CR2: 
  [   41.433961] ---[ end trace 595db54cab84070c ]---

  
  system then becomes unresponsive; no further interfaces can be created.

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

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

[Kernel-packages] [Bug 1738491] Re: touchpad not working

[gm]

kernel-bug-exists-upstream

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

Title:
  touchpad not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  chuwi Lapbook Air touch pad not working

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

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

[Kernel-packages] [Bug 1706247] Re: Add support for 16g huge pages on Ubuntu 16.04.2 PowerNV

[Joseph Salisbury]

I built a Zesty test kernel with the following six patches:

a525108cf1cc14651602d678da38fa627a76a724
e1073d1e7920946ac4776a619cc40668b9e1401b
40692eb5eea209c2dd55857f44b4e1d7206e91d6
e24a1307ba1f99fc62a0bd61d5e87fcfb6d5503d
79cc38ded1e1ac86e69c90f604efadd50b0b3762
4ae279c2c96ab38a78b954d218790a8f6db714e5


The test kernel can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1706247/zesty

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

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

Title:
  Add support for 16g huge pages on Ubuntu 16.04.2 PowerNV

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  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

Bug description:
  16G Huge Pages are not supported on PowerNV (bare metal) installations. 
Ubuntu 16.04.2 still allows 16G huge pages to be turned on.
   
  Contact Information = Mike Hollinger (mchol...@us.ibm.com) 
   
  ---uname output---
  Linux aprilmin4 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:53:54 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8335-GTB 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Add the following to the kernel boot args (either via editing the 
petitboot boot option manually, or updating /boot/grub/grub.cfg:

  default_hugepagesz=16G hugepagesz=16G hugepages=4

  2. Boot Linux
  3. Observe that the kernel believes 16G huge pages are available:
  ubuntu@aprilmin7:~$ cat /proc/meminfo | grep -i huge
  AnonHugePages:475136 kB
  HugePages_Total:   0
  HugePages_Free:0
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:   16777216 kB
  ubuntu@aprilmin7:~$ ls /sys/devices/system/node/node0/hugepages
  hugepages-1024kB  hugepages-16384kB  hugepages-16777216kB

   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for Mike Hollinger (mchol...@us.ibm.com): 
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.

  
  This may be recreated on any bare metal POWER8 server with Ubuntu 16.04.2; I 
haven't checked other versions of Ubuntu.

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

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

[Kernel-packages] [Bug 1724120] Re: Ubuntu 16.04.3 - call traces occurs when memory-hotplug test is run with 16Gb hugepages configured

[Joseph Salisbury]

I built a Zesty test kernel with the six requested patches.

The test kernel can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1706247/zesty

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

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

Title:
  Ubuntu 16.04.3 - call traces occurs when memory-hotplug test is run
  with 16Gb hugepages configured

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

Bug description:
  Issue:

  Call traces occurs when memory-hotplug script is run with 16Gb
  hugepages configured.

  Environment:
  ppc64le PowerVM Lpar

  root@ltctuleta-lp1:~# uname -r
  4.4.0-34-generic

  root@ltctuleta-lp1:~# cat /proc/meminfo | grep -i huge
  AnonHugePages: 0 kB
  HugePages_Total:   2
  HugePages_Free:2
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:   16777216 kB

  root@ltctuleta-lp1:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:85G 32G 52G 16M193M 
52G
  Swap:   43G  0B 43G

  Steps to reproduce:
  1 - Download kernel source and enter to the directory- 
tools/testing/selftests/memory-hotplug/
  2 - Run  mem-on-off-test.sh script in it.

  System gives call traces like:

  offline_memory_expect_success 639: unexpected fail
  online-offline 668
  [   57.552964] Unable to handle kernel paging request for data at address 
0x0028
  [   57.552977] Faulting instruction address: 0xc029bc04
  [   57.552987] Oops: Kernel access of bad area, sig: 11 [#1]
  [   57.552992] SMP NR_CPUS=2048 NUMA pSeries
  [   57.553002] Modules linked in: btrfs xor raid6_pq pseries_rng sunrpc 
autofs4 ses enclosure nouveau bnx2x i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops drm vxlan ip6_udp_tunnel ipr udp_tunnel 
rtc_generic mdio libcrc32c
  [   57.553050] CPU: 44 PID: 6518 Comm: mem-on-off-test Not tainted 
4.4.0-34-generic #53-Ubuntu
  [   57.553059] task: c0072773c8e0 ti: c0072778 task.ti: 
c0072778
  [   57.553067] NIP: c029bc04 LR: c029bbdc CTR: 
c01107f0
  [   57.553076] REGS: c00727783770 TRAP: 0300   Not tainted  
(4.4.0-34-generic)
  [   57.553083] MSR: 80019033   CR: 24242882  
XER: 0002
  [   57.553104] CFAR: c0008468 DAR: 0028 DSISR: 4000 
SOFTE: 1 
  GPR00: c029bbdc c007277839f0 c15b5d00  
  GPR04: 0029d000 0800  fa01 
  GPR08: fa700020 0008 c185e270 c00e7e50 
  GPR12: 2200 ce6ea200 0029d000 2200 
  GPR16: 1000 c15e2200 0a70  
  GPR20: 0001 0100 0200 c15f16d0 
  GPR24: c1876510  0001 c1872a00 
  GPR28: 0029d000 f000 fa70 0029c000 
  [   57.553211] NIP [c029bc04] dissolve_free_huge_pages+0x154/0x220
  [   57.553219] LR [c029bbdc] dissolve_free_huge_pages+0x12c/0x220
  [   57.553226] Call Trace:
  [   57.553231] [c007277839f0] [c029bbdc] 
dissolve_free_huge_pages+0x12c/0x220 (unreliable)
  [   57.553244] [c00727783a80] [c02dcbc8] 
__offline_pages.constprop.6+0x3f8/0x900
  [   57.553254] [c00727783bd0] [c06fbb38] 
memory_subsys_offline+0xa8/0x110
  [   57.553265] [c00727783c00] [c06d6424] 
device_offline+0x104/0x140
  [   57.553274] [c00727783c40] [c06fba80] 
store_mem_state+0x180/0x190
  [   57.553283] [c00727783c80] [c06d1e58] dev_attr_store+0x68/0xa0
  [   57.553293] [c00727783cc0] [c0398110] sysfs_kf_write+0x80/0xb0
  [   57.553302] [c00727783d00] [c0397028] 
kernfs_fop_write+0x188/0x200
  [   57.553312] [c00727783d50] [c02e190c] __vfs_write+0x6c/0xe0
  [   57.553321] [c00727783d90] [c02e2640] vfs_write+0xc0/0x230
  [   57.553329] [c00727783de0] [c02e367c] SyS_write+0x6c/0x110
  [   57.553339] [c00727783e30] [c0009204] system_call+0x38/0xb4
  [   57.553346] Instruction dump:
  [   57.553351] 7e831836 4bfff991 e91e0028 e8fe0020 7d32e82a f9070008 f8e8 
fabe0020 
  [   57.553366] fade0028 79294620 79291764 7d234a14  3908 
f9030028 81091458 
  [   57.553383] ---[ end trace 617f7bdd75bcfc10 ]---
  [   57.557133] 
  Segmentation fault

  The following commit IDs were built into a 4.10.0-37-generic #41 test
  kernel and verified to fix the problem:

  a525108cf1cc14651602d678da38fa627a76a724
  

[Kernel-packages] [Bug 1738224] Re: Suspend broken after kernel upgrade

[Jeffrey Bouter]

Kai, it is: s2idle [deep]

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

Title:
  Suspend broken after kernel upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My machine (XPS 13 9360) won't go into suspend properly after
  upgrading from linux-image-4.13.0-17-generic to linux-
  image-4.13.0-19-generic.

  This affects both suspend through lid close and "systemctl suspend".
  Screen goes off, power led remains lit. Then after some time the
  screen comes back on, is stuck and lets me wait for a few before
  becoming responsive again.

  Booting back into 4.13.0-17 resolved the issue.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeffrey1963 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5
  InstallationDate: Installed on 2017-10-18 (56 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker input libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.3.1
  dmi.board.name: 0839Y6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.3.1:bd10/03/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1724120] Re: Ubuntu 16.04.3 - call traces occurs when memory-hotplug test is run with 16Gb hugepages configured

[Joseph Salisbury]

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

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

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

Title:
  Ubuntu 16.04.3 - call traces occurs when memory-hotplug test is run
  with 16Gb hugepages configured

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

Bug description:
  Issue:

  Call traces occurs when memory-hotplug script is run with 16Gb
  hugepages configured.

  Environment:
  ppc64le PowerVM Lpar

  root@ltctuleta-lp1:~# uname -r
  4.4.0-34-generic

  root@ltctuleta-lp1:~# cat /proc/meminfo | grep -i huge
  AnonHugePages: 0 kB
  HugePages_Total:   2
  HugePages_Free:2
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:   16777216 kB

  root@ltctuleta-lp1:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:85G 32G 52G 16M193M 
52G
  Swap:   43G  0B 43G

  Steps to reproduce:
  1 - Download kernel source and enter to the directory- 
tools/testing/selftests/memory-hotplug/
  2 - Run  mem-on-off-test.sh script in it.

  System gives call traces like:

  offline_memory_expect_success 639: unexpected fail
  online-offline 668
  [   57.552964] Unable to handle kernel paging request for data at address 
0x0028
  [   57.552977] Faulting instruction address: 0xc029bc04
  [   57.552987] Oops: Kernel access of bad area, sig: 11 [#1]
  [   57.552992] SMP NR_CPUS=2048 NUMA pSeries
  [   57.553002] Modules linked in: btrfs xor raid6_pq pseries_rng sunrpc 
autofs4 ses enclosure nouveau bnx2x i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops drm vxlan ip6_udp_tunnel ipr udp_tunnel 
rtc_generic mdio libcrc32c
  [   57.553050] CPU: 44 PID: 6518 Comm: mem-on-off-test Not tainted 
4.4.0-34-generic #53-Ubuntu
  [   57.553059] task: c0072773c8e0 ti: c0072778 task.ti: 
c0072778
  [   57.553067] NIP: c029bc04 LR: c029bbdc CTR: 
c01107f0
  [   57.553076] REGS: c00727783770 TRAP: 0300   Not tainted  
(4.4.0-34-generic)
  [   57.553083] MSR: 80019033   CR: 24242882  
XER: 0002
  [   57.553104] CFAR: c0008468 DAR: 0028 DSISR: 4000 
SOFTE: 1 
  GPR00: c029bbdc c007277839f0 c15b5d00  
  GPR04: 0029d000 0800  fa01 
  GPR08: fa700020 0008 c185e270 c00e7e50 
  GPR12: 2200 ce6ea200 0029d000 2200 
  GPR16: 1000 c15e2200 0a70  
  GPR20: 0001 0100 0200 c15f16d0 
  GPR24: c1876510  0001 c1872a00 
  GPR28: 0029d000 f000 fa70 0029c000 
  [   57.553211] NIP [c029bc04] dissolve_free_huge_pages+0x154/0x220
  [   57.553219] LR [c029bbdc] dissolve_free_huge_pages+0x12c/0x220
  [   57.553226] Call Trace:
  [   57.553231] [c007277839f0] [c029bbdc] 
dissolve_free_huge_pages+0x12c/0x220 (unreliable)
  [   57.553244] [c00727783a80] [c02dcbc8] 
__offline_pages.constprop.6+0x3f8/0x900
  [   57.553254] [c00727783bd0] [c06fbb38] 
memory_subsys_offline+0xa8/0x110
  [   57.553265] [c00727783c00] [c06d6424] 
device_offline+0x104/0x140
  [   57.553274] [c00727783c40] [c06fba80] 
store_mem_state+0x180/0x190
  [   57.553283] [c00727783c80] [c06d1e58] dev_attr_store+0x68/0xa0
  [   57.553293] [c00727783cc0] [c0398110] sysfs_kf_write+0x80/0xb0
  [   57.553302] [c00727783d00] [c0397028] 
kernfs_fop_write+0x188/0x200
  [   57.553312] [c00727783d50] [c02e190c] __vfs_write+0x6c/0xe0
  [   57.553321] [c00727783d90] [c02e2640] vfs_write+0xc0/0x230
  [   57.553329] [c00727783de0] [c02e367c] SyS_write+0x6c/0x110
  [   57.553339] [c00727783e30] [c0009204] system_call+0x38/0xb4
  [   57.553346] Instruction dump:
  [   57.553351] 7e831836 4bfff991 e91e0028 e8fe0020 7d32e82a f9070008 f8e8 
fabe0020 
  [   57.553366] fade0028 79294620 79291764 7d234a14  3908 
f9030028 81091458 
  [   57.553383] ---[ end trace 617f7bdd75bcfc10 ]---
  [   57.557133] 
  Segmentation fault

  The following commit IDs were built into a 4.10.0-37-generic #41 test
  kernel and verified to fix the problem:

  a525108cf1cc14651602d678da38fa627a76a724
  

[Kernel-packages] [Bug 1738534] Re: Processor turbo dsiabled/throttled after suspend

[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.15 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.15-rc4

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

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

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

Title:
  Processor turbo dsiabled/throttled after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After suspending/resuming my laptop on battery power, I noticed choppy
  video playback.  I've narrowed it down to the CPU being locked to
  lower frequencies after suspend/resume (only on battery).  Plugging
  the laptop back in does not restore the normal performance, nor does
  suspend/resume after plugging it back in.  The performance doesn't
  drop until after the suspend/resume, I'm not sure if it is _supposed_
  to throttle when on battery, but either way the behaviour is wrong.

  Doing a full shutdown and restart restores the performance to normal.

  Prior to a suspend/resume cycle, cpupower reports:

  $ sudo cpupower frequency-info
  analyzing CPU 0:
driver: intel_pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency:  Cannot determine or is not supported.
hardware limits: 800 MHz - 3.00 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 800 MHz and 3.00 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 1.26 GHz (asserted by call to kernel)
boost state support:
  Supported: yes
  Active: yes
  2800 MHz max turbo 4 active cores
  2800 MHz max turbo 3 active cores
  2800 MHz max turbo 2 active cores
  3000 MHz max turbo 1 active cores

  Afterwards, the frequency is clamped (cpufreq-set -r --max=3.0GHz has
  no effect) and turbo is disabled:

  $ sudo cpupower frequency-info
  analyzing CPU 0:
driver: intel_pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency:  Cannot determine or is not supported.
hardware limits: 800 MHz - 3.00 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 800 MHz and 1.80 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 950 MHz (asserted by call to kernel)
boost state support:
  Supported: no
  Active: no
  2800 MHz max turbo 4 active cores
  2800 MHz max turbo 3 active cores
  2800 MHz max turbo 2 active cores
  3000 MHz max turbo 1 active cores

  Trying to re-enable turbo mode by setting the no_turbo intel_pstate
  /sys/ entry back to 0 is rejected:

  $ echo 0 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo
  0
  tee: /sys/devices/system/cpu/intel_pstate/no_turbo: Operation not permitted

  However, these two commands *do* work around the problem, forcing
  turbo mode back on and then restoring the normal frequency range:

  sudo x86_energy_perf_policy --turbo-enable 1
  sudo cpufreq-set -r --min=0.8GHz --max=3.0GHz

  I also see this error in dmesg after some resumes (but the above
  problem sometimes happens without this error message):

  Dec 16 11:36:25 shauns-laptop kernel: intel_pstate: Turbo disabled by
  BIOS or unavailable on processor

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-19-generic 4.13.0-19.22
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shaun  1194 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 16 11:18:12 2017
  InstallationDate: Installed on 2017-12-14 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 001 Device 004: ID 2232:1024 Silicon Motion 
   Bus 001 Device 002: ID 8087:0024 

[Kernel-packages] [Bug 1738491] Re: touchpad not working

[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.15 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.15-rc4

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

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

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

Title:
  touchpad not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  chuwi Lapbook Air touch pad not working

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

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

[Kernel-packages] [Bug 1738773] Re: Connection issue in Bluetooth SPP mode between a Dell Edge Gateway 3000 and an HC-05 BT module attached to Arduino Uno

[Joseph Salisbury]

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

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

Title:
  Connection issue in Bluetooth SPP mode between a Dell Edge Gateway
  3000 and an HC-05 BT module attached to Arduino Uno

Status in linux package in Ubuntu:
  Triaged

Bug description:
  SRU Justification

  Impact: Connection issue in Bluetooth SPP mode between a Dell Edge
  Gateway 3000 and an HC-05 BT module attached to Arduino Uno

  Fix: Updated firmware from Redpine containing a fix for the issue.

  Regression Potential: Below stress tests are conducted to ensure there is no 
regression with updated firmware
  BT mouse + BT keyboard
  BT mouse + BLE keyboard
  BT keyboard + BLE mouse
  BLE keyboard + BLE mouse
  BT mouse or keyboard + Wifi connected
  BT mouse + BT keyboard + WiFi connected
  BLE mouse + BLE keyboard + WiFi Connected
  BT mouse + BLE keyboard + Wifi connected
  BLE mouse + BT keyboard + Wifi connected
  (BT or BLE) mouse and/or (BT or BLE) keyboard + Wifi connected + Wifi Scan
  (BT or BLE) mouse and/or (BT or BLE) keyboard + Wifi connected + BT inquiry + 
BLE scan
  BT file transfer from mobile + WiFi connected

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

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

[Kernel-packages] [Bug 1738523] Re: External HDMI monitor failed to show screen on Lenovo X1 series

[Joseph Salisbury]

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

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

Title:
  External HDMI monitor failed to show screen on Lenovo X1 series

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Thinkpad X1 yoga:
  CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (family: 0x6, model: 0x8e, 
stepping: 0xa)
  GPU: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])

  Steps:
  1, Connect an external monitor
  2, Try to switch display modes in mirrored, extended, displayed on external 
or internal.

  [Impact]
  External HDMI monitor failed to show screen on Lenovo X1 yoga/carbon

  [Fix]
  Add a workaround to bypass this TMDS_OE writing on identified laptop models.

  [Test Case]
  Tested on ThinkPad X1 yoga 2nd/3rd and Carbon 6th, external HDMI output
  OK.

  [Regression Potential]
  Low, it limits to ThinkPad specific laptops.

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

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

[Kernel-packages] [Bug 1738560] Re: touch pad stopped working after upgrade to artful 17.10

[Joseph Salisbury]

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

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

** Tags added: needs-bisect

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

Title:
  touch pad stopped working after upgrade to artful 17.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The touch pad worked fine on 16.10 and 17.04, but it stopped working after 
upgrade to artful 17.10.
  It doesn't appear with xinput list, and I cannot find any line in dmesg 
referring to the touchpad ... so I need help even to report the exact device id!

  Ubuntu 4.13.0-19.22-generic 4.13.13
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pang   1303 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df
  InstallationDate: Installed on 2017-12-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Micro-Star International Co., Ltd. GP62M 7RD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J9IMS.307
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J9
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: G
  dmi.product.name: GP62M 7RD
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Kernel-packages] [Bug 1738761] Re: Please document how to build a patched version of the current (non mainline) ubuntu kernel in a PPA

[Joseph Salisbury]

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

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

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/linux/+question/661951

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

Title:
  Please document how to build a patched version of the current (non
  mainline) ubuntu kernel in a PPA

Status in linux package in Ubuntu:
  Invalid

Bug description:
  In order to resolve some bugs, to workaround some hardware quirk, or
  to help developers test some bug-fixing patch it would be able to:

  - Get the sources of the *current* (non mainline) ubuntu kernel
  - Apply some patch
  - Rebuild the kernel in a PPA (so that it can be made available to multiple 
people for testing).

  Unfortunately, there is no documentation on how to do this.  In fact,
  to the best of my understanding there is no documentation on how to
  build patched kernels in PPAs at all.

  This seems to be both possible and involving some special recipes,
  because in some occasions I've been pointed by ubuntu developers to
  try some specially patched version of the current kernel made
  available via a PPA.

  Specifically, at the present time, I would like to try and help trying
  the patch in git://github.com/vsyrjala/linux.git plane_assert_v4.13
  which is not yet available in mainline. In other occasions I had
  similar situations with other patches.

  Please let me remark again that I am not looking for ways of building
  patched versions of the mainline kernel in a PPA (for this I have
  found some informal instructions in
  https://askubuntu.com/questions/784796/ppa-upload-of-custom-kernel-
  package/841981#841981 (incidentally, this too should in my opinion be
  officially documented). I am looking for ways to build a patched
  current kernel, so that:

  - systems needing proprietary drivers can be supported
  - patches can be tested with the current ubuntu kernel
  - as new versions of the ubuntu kernel for some distro come out, it is easy 
to bring forward the patch if needed.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-source (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  callegar  20848 F pulseaudio
  CurrentDesktop: KDE
  Date: Mon Dec 18 11:42:45 2017
  EcryptfsInUse: Yes
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. Precision WorkStation T5400
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic 
root=/dev/mapper/vg_ssd-root ro quiet splash mtrr_gran_size=2g 
mtrr_chunk_size=2g resume=/dev/sdc3 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-25 (53 days ago)
  WpaSupplicantLog:
   
  dmi.bios.date: 04/30/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0RW203
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd04/30/2012:svnDellInc.:pnPrecisionWorkStationT5400:pvr:rvnDellInc.:rn0RW203:rvr:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision WorkStation T5400
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1738736] Re: ACPI error message flooding syslog

[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.15 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.15-rc4

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

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

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

Title:
  ACPI error message flooding syslog

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This message :

  Dec 18 09:20:13 tignasse kernel: [   85.652805] ACPI Error: Needed type 
[Reference], found [Integer] 99eae08481f8 (20170531/exresop-103)
  Dec 18 09:20:13 tignasse kernel: [   85.652831] ACPI Exception: 
AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] 
(20170531/dswexec-461)
  Dec 18 09:20:13 tignasse kernel: [   85.652847] ACPI Error: Method 
parse/execution failed \_SB.PCI0.LPCB.H_EC._Q50, AE_AML_OPERAND_TYPE 
(20170531/psparse-550)

  Is flooding my syslog at a pace of on message every 200 ms !

  This is really annoying.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-19-generic 4.13.0-19.22
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   5166 F pulseaudio
   /dev/snd/controlC1:  alex   5166 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Dec 18 09:22:16 2017
  HibernationDevice: RESUME=UUID=870c2fd1-8a8f-49bb-9bf4-dbefaa08e583
  InstallationDate: Installed on 2015-11-10 (768 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Intel Corporation Skylake Platform
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=6814e3c1-8cea-4ecc-964d-535fd18782e9 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-23 (24 days ago)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: WhiteTip Mountain1 Fab2
  dmi.board.vendor: Topstar
  dmi.board.version: RVP7
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 9
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd11/06/2015:svnIntelCorporation:pnSkylakePlatform:pvr0.1:rvnTopstar:rnWhiteTipMountain1Fab2:rvrRVP7:cvnDefaultstring:ct9:cvrDefaultstring:
  dmi.product.family: Skylake System
  dmi.product.name: Skylake Platform
  dmi.product.version: 0.1
  dmi.sys.vendor: Intel Corporation

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

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

[Kernel-packages] [Bug 1738837] Re: BUG: unable to handle kernel NULL pointer dereference at (null)

[Joseph Salisbury]

Can you see if this issue also happens with the latest daily image?  It can be 
downloaded from:
Desktop:
http://cdimage.ubuntu.com/daily-live/current/
Server:
http://cdimage.ubuntu.com/ubuntu-server/daily/current/

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

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

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

Title:
  BUG: unable to handle kernel NULL pointer dereference at
  (null)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Just trying to run ubuntu 17.10 desktop installation and selected TRY
  it out...

  ProblemType: KernelOops
  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 x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  ubuntu 4342 F pulseaudio
   /dev/snd/controlC0:  ubuntu 4342 F pulseaudio
   /dev/snd/controlC1:  ubuntu 4342 F pulseaudio
  CasperVersion: 1.387
  Date: Mon Dec 18 15:55:33 2017
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at  
 (null) RIP: isci_task_abort_task+0x43/0x4e0 [isci] RSP: 
a693c7967c80
  Failure: oops
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Dell Inc. Precision T5600
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: BUG: unable to handle kernel NULL pointer dereference at   
(null)
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0Y56T3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd05/06/2017:svnDellInc.:pnPrecisionT5600:pvr01:rvnDellInc.:rn0Y56T3:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T5600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1738839] Re: [Medion S2217] Touchpad not properly recognized

[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.15 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.15-rc4

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

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

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

Title:
  [Medion S2217] Touchpad not properly recognized

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The ELAN (not Elantech) touchpad in my Medion S2217 laptop is not
  properly recognized. The touchpad shows up as an ITE Tech. Inc. ITE
  Device(8910) and works only as a plain pointing device. Multitouch and
  scrolling or anything else however, do not function, nor do options
  for this show up in the Mouse & Touchpad options in Ubuntu.

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

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

[Kernel-packages] [Bug 1738848] Re: linux: 4.14.0-13.15 -proposed tracker

[Brad Figg]

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

** Description changed:

  This bug is for tracking the 4.14.0-13.15 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:Monday, 18. December 2017 18:32 UTC
+ kernel-phase:Packaging

** Description changed:

  This bug is for tracking the 4.14.0-13.15 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:Monday, 18. December 2017 18:32 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/1738848

Title:
  linux: 4.14.0-13.15 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.14.0-13.15 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:Monday, 18. December 2017 18:32 UTC
  kernel-phase:Packaging

  -- swm properties --
  phase: Packaging

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

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

[Kernel-packages] [Bug 1738848] [NEW] linux: 4.14.0-13.15 -proposed tracker

[Seth Forshee]

Public bug reported:

This bug is for tracking the 4.14.0-13.15 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/1738848

Title:
  linux: 4.14.0-13.15 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status 

[Kernel-packages] [Bug 1738554] Re: linux: 4.14.0-12.14 -proposed tracker

[Seth Forshee]

*** This bug is a duplicate of bug 1738848 ***
https://bugs.launchpad.net/bugs/1738848

** This bug has been marked a duplicate of bug 1738848
   linux: 4.14.0-13.15 -proposed tracker

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

Title:
  linux: 4.14.0-12.14 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.14.0-12.14 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:Saturday, 16. December 2017 16:32 UTC
  kernel-phase:Packaging

  -- swm properties --
  phase: Packaging

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

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

[Kernel-packages] [Bug 1734728] Re: linux: 4.14.0-9.11 -proposed tracker

[Seth Forshee]

*** This bug is a duplicate of bug 1738848 ***
https://bugs.launchpad.net/bugs/1738848

** This bug is no longer a duplicate of bug 1738554
   linux: 4.14.0-12.14 -proposed tracker
** This bug has been marked a duplicate of bug 1738848
   linux: 4.14.0-13.15 -proposed tracker

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

Title:
  linux: 4.14.0-9.11 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.14.0-9.11 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:Monday, 27. November 2017 18:00 UTC

  -- swm properties --
  phase: Packaging

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

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

[Kernel-packages] [Bug 1738823] Re: linux: 4.13.0-21.24 -proposed tracker

[Brad Figg]

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

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

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

** 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
+ 
+ kernel-stable-phase-changed:Monday, 18. December 2017 18:02 UTC
+ kernel-stable-phase:Uploaded

** 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
  
  kernel-stable-phase-changed:Monday, 18. December 2017 18:02 UTC
  kernel-stable-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/1738823

Title:
  linux: 4.13.0-21.24 -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-meta series:
  Fix Released
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

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

  kernel-stable-phase-changed:Monday, 18. December 2017 18:02 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/1738823/+subscriptions

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

[Kernel-packages] [Bug 1736168] Re: linux: 4.14.0-11.13 -proposed tracker

[Seth Forshee]

*** This bug is a duplicate of bug 1738848 ***
https://bugs.launchpad.net/bugs/1738848

** This bug is no longer a duplicate of bug 1738554
   linux: 4.14.0-12.14 -proposed tracker
** This bug has been marked a duplicate of bug 1738848
   linux: 4.14.0-13.15 -proposed tracker

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

Title:
  linux: 4.14.0-11.13 -proposed tracker

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

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

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

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

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

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

[Kernel-packages] [Bug 1734901] Re: linux: 4.14.0-10.12 -proposed tracker

[Seth Forshee]

*** This bug is a duplicate of bug 1738848 ***
https://bugs.launchpad.net/bugs/1738848

** This bug is no longer a duplicate of bug 1738554
   linux: 4.14.0-12.14 -proposed tracker
** This bug has been marked a duplicate of bug 1738848
   linux: 4.14.0-13.15 -proposed tracker

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

Title:
  linux: 4.14.0-10.12 -proposed tracker

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

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

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

  kernel-phase-changed:Tuesday, 28. November 2017 15:01 UTC
  kernel-phase:Packaging

  -- swm properties --
  phase: Packaging

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

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

[Kernel-packages] [Bug 1734695] Re: linux: 4.14.0-8.10 -proposed tracker

[Seth Forshee]

*** This bug is a duplicate of bug 1738848 ***
https://bugs.launchpad.net/bugs/1738848

** This bug is no longer a duplicate of bug 1738554
   linux: 4.14.0-12.14 -proposed tracker
** This bug has been marked a duplicate of bug 1738848
   linux: 4.14.0-13.15 -proposed tracker

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

Title:
  linux: 4.14.0-8.10 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.14.0-8.10 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:Monday, 27. November 2017 14:00 UTC

  -- swm properties --
  phase: Packaging

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

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

[Kernel-packages] [Bug 1738632] Re: linux 4.14.0-12.14 ADT test failure with linux 4.14.0-12.14

[Seth Forshee]

The patch was reverted upstream, so I'll do the same in bionic.

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

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

Title:
  linux 4.14.0-12.14 ADT test failure with linux 4.14.0-12.14

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-unstable/bionic/amd64/l/linux/20171217_033543_755bb@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-unstable/bionic/arm64/l/linux/20171217_025131_755bb@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-unstable/bionic/i386/l/linux/20171217_033325_755bb@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-unstable/bionic/ppc64el/l/linux/20171217_034439_755bb@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-unstable/bionic/s390x/l/linux/20171217_032308_755bb@/log.gz

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

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

[Kernel-packages] [Bug 1738843] Re: Bionic update to v4.14.7 stable release

[Seth Forshee]

** Description changed:

  SRU Justification
  
  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The v4.14.7 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.
  
     git://git.kernel.org/
  
  TEST CASE: TBD
  
     The following patches from the v4.14.7 stable release shall be
  applied:
  
  net: qmi_wwan: add Quectel BG96 2c7c:0296
- net: thunderx: Fix TCP/UDP checksum offload for IPv6 pkts
- net: thunderx: Fix TCP/UDP checksum offload for IPv4 pkts
  net: realtek: r8169: implement set_link_ksettings()
  s390/qeth: fix early exit from error path
  tipc: fix memory leak in tipc_accept_from_sock()
  vhost: fix skb leak in handle_rx()
  rds: Fix NULL pointer dereference in __rds_rdma_map
  sit: update frag_off info
  tcp: add tcp_v4_fill_cb()/tcp_v4_restore_cb()
  packet: fix crash in fanout_demux_rollover()
  net/packet: fix a race in packet_bind() and packet_notifier()
  tcp: remove buggy call to tcp_v6_restore_cb()
  usbnet: fix alignment for frames with no ethernet header
  net: remove hlist_nulls_add_tail_rcu()
  stmmac: reset last TSO segment size after device open
  tcp/dccp: block bh before arming time_wait timer
  s390/qeth: build max size GSO skbs on L2 devices
  s390/qeth: fix thinko in IPv4 multicast address tracking
  s390/qeth: fix GSO throughput regression
  tcp: use IPCB instead of TCP_SKB_CB in inet_exact_dif_match()
  tipc: call tipc_rcv() only if bearer is up in tipc_udp_recv()
  tcp: use current time in tcp_rcv_space_adjust()
  net: sched: cbq: create block for q->link.block
  tap: free skb if flags error
  tcp: when scheduling TLP, time of RTO should account for current ACK
  tun: free skb in early errors
  net: ipv6: Fixup device for anycast routes during copy
  tun: fix rcu_read_lock imbalance in tun_build_skb
  net: accept UFO datagrams from tuntap and packet
  net: openvswitch: datapath: fix data type in queue_gso_packets
  cls_bpf: don't decrement net's refcount when offload fails
  sctp: use right member as the param of list_for_each_entry
  ipmi: Stop timers before cleaning up the module
  usb: gadget: ffs: Forbid usb_ep_alloc_request from sleeping
  fcntl: don't cap l_start and l_end values for F_GETLK64 in compat syscall
  fix kcm_clone()
  KVM: arm/arm64: vgic-its: Preserve the revious read from the pending table
  kbuild: do not call cc-option before KBUILD_CFLAGS initialization
  powerpc/powernv/idle: Round up latency and residency values
  ipvlan: fix ipv6 outbound device
  ide: ide-atapi: fix compile error with defining macro DEBUG
  blk-mq: Avoid that request queue removal can trigger list corruption
  nvmet-rdma: update queue list during ib_device removal
  audit: Allow auditd to set pid to 0 to end auditing
  audit: ensure that 'audit=1' actually enables audit for PID 1
  dm raid: fix panic when attempting to force a raid to sync
  md: free unused memory after bitmap resize
  RDMA/cxgb4: Annotate r2 and stag as __be32
  x86/intel_rdt: Fix potential deadlock during resctrl unmount
  media: dvb-core: always call invoke_release() in fe_free()
  dvb_frontend: don't use-after-free the frontend struct
  Linux 4.14.7
+ 
+    The following patches from the v4.14.7 stable release shall be
+ applied:
+ 
+ net: thunderx: Fix TCP/UDP checksum offload for IPv6 pkts
+ net: thunderx: Fix TCP/UDP checksum offload for IPv4 pkts

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

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

Title:
  Bionic update to v4.14.7 stable release

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The v4.14.7 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the v4.14.7 stable release shall be
  applied:

  net: qmi_wwan: add Quectel BG96 2c7c:0296
  net: realtek: r8169: implement set_link_ksettings()
  s390/qeth: fix early exit from error path
  tipc: fix memory leak in tipc_accept_from_sock()
  vhost: fix skb leak in handle_rx()
  rds: Fix NULL pointer dereference in __rds_rdma_map
  sit: update 

[Kernel-packages] [Bug 1736593] Re: ThunderX: TX failure unless checksum offload disabled

[dann frazier]

** Summary changed:

- ThunderX: IPv6 TX failure unless checksum offload disabled
+ ThunderX: TX failure unless checksum offload disabled

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

Title:
  ThunderX: TX failure unless checksum offload disabled

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

Bug description:
  [Impact]
  Most attempts to use IPv6 on the ThunderX NIC will fail.

  [Test Case]
  Attempt an IPv6 TCP connection:

  $ wget -6 'http://www.kernel.org/'

  The connection will time out.

  [Regression Risk]
  The fix is upstream, and is limited to the ThunderX nicvf driver.

  [Workaround]
  Disable TX checksum offload:

  $ ethtool -K eth0 tx off

  [More Details]
  The issue first appears in Linux 4.12.  A fix from Cavium has been merged 
upstream:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/cavium/thunder/nicvf_queues.c?id=fa6d7cb5d76cf0467c61420fc9238045aedfd379

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

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

[Kernel-packages] [Bug 1738843] [NEW] Bionic update to v4.14.7 stable release

[Seth Forshee]

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The v4.14.7 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the v4.14.7 stable release shall be
applied:

net: qmi_wwan: add Quectel BG96 2c7c:0296
net: thunderx: Fix TCP/UDP checksum offload for IPv6 pkts
net: thunderx: Fix TCP/UDP checksum offload for IPv4 pkts
net: realtek: r8169: implement set_link_ksettings()
s390/qeth: fix early exit from error path
tipc: fix memory leak in tipc_accept_from_sock()
vhost: fix skb leak in handle_rx()
rds: Fix NULL pointer dereference in __rds_rdma_map
sit: update frag_off info
tcp: add tcp_v4_fill_cb()/tcp_v4_restore_cb()
packet: fix crash in fanout_demux_rollover()
net/packet: fix a race in packet_bind() and packet_notifier()
tcp: remove buggy call to tcp_v6_restore_cb()
usbnet: fix alignment for frames with no ethernet header
net: remove hlist_nulls_add_tail_rcu()
stmmac: reset last TSO segment size after device open
tcp/dccp: block bh before arming time_wait timer
s390/qeth: build max size GSO skbs on L2 devices
s390/qeth: fix thinko in IPv4 multicast address tracking
s390/qeth: fix GSO throughput regression
tcp: use IPCB instead of TCP_SKB_CB in inet_exact_dif_match()
tipc: call tipc_rcv() only if bearer is up in tipc_udp_recv()
tcp: use current time in tcp_rcv_space_adjust()
net: sched: cbq: create block for q->link.block
tap: free skb if flags error
tcp: when scheduling TLP, time of RTO should account for current ACK
tun: free skb in early errors
net: ipv6: Fixup device for anycast routes during copy
tun: fix rcu_read_lock imbalance in tun_build_skb
net: accept UFO datagrams from tuntap and packet
net: openvswitch: datapath: fix data type in queue_gso_packets
cls_bpf: don't decrement net's refcount when offload fails
sctp: use right member as the param of list_for_each_entry
ipmi: Stop timers before cleaning up the module
usb: gadget: ffs: Forbid usb_ep_alloc_request from sleeping
fcntl: don't cap l_start and l_end values for F_GETLK64 in compat syscall
fix kcm_clone()
KVM: arm/arm64: vgic-its: Preserve the revious read from the pending table
kbuild: do not call cc-option before KBUILD_CFLAGS initialization
powerpc/powernv/idle: Round up latency and residency values
ipvlan: fix ipv6 outbound device
ide: ide-atapi: fix compile error with defining macro DEBUG
blk-mq: Avoid that request queue removal can trigger list corruption
nvmet-rdma: update queue list during ib_device removal
audit: Allow auditd to set pid to 0 to end auditing
audit: ensure that 'audit=1' actually enables audit for PID 1
dm raid: fix panic when attempting to force a raid to sync
md: free unused memory after bitmap resize
RDMA/cxgb4: Annotate r2 and stag as __be32
x86/intel_rdt: Fix potential deadlock during resctrl unmount
media: dvb-core: always call invoke_release() in fe_free()
dvb_frontend: don't use-after-free the frontend struct
Linux 4.14.7

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Seth Forshee (sforshee)

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The v4.14.7 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The v4.14.7 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+    git://git.kernel.org/
  
-git://git.kernel.org/
+ TEST CASE: TBD
  
- TEST CASE: TBD
+    The following patches from the v4.14.7 stable release shall be
+ applied:
  
-

[Kernel-packages] [Bug 1738839] Re: [Medion S2217] Touchpad not properly recognized

[Full Name]

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

Title:
  [Medion S2217] Touchpad not properly recognized

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The ELAN (not Elantech) touchpad in my Medion S2217 laptop is not
  properly recognized. The touchpad shows up as an ITE Tech. Inc. ITE
  Device(8910) and works only as a plain pointing device. Multitouch and
  scrolling or anything else however, do not function, nor do options
  for this show up in the Mouse & Touchpad options in Ubuntu.

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

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

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

[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 1738839

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

Title:
  [Medion S2217] Touchpad not properly recognized

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The ELAN (not Elantech) touchpad in my Medion S2217 laptop is not
  properly recognized. The touchpad shows up as an ITE Tech. Inc. ITE
  Device(8910) and works only as a plain pointing device. Multitouch and
  scrolling or anything else however, do not function, nor do options
  for this show up in the Mouse & Touchpad options in Ubuntu.

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

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

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

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

Title:
  BUG: unable to handle kernel NULL pointer dereference at
  (null)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Just trying to run ubuntu 17.10 desktop installation and selected TRY
  it out...

  ProblemType: KernelOops
  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 x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  ubuntu 4342 F pulseaudio
   /dev/snd/controlC0:  ubuntu 4342 F pulseaudio
   /dev/snd/controlC1:  ubuntu 4342 F pulseaudio
  CasperVersion: 1.387
  Date: Mon Dec 18 15:55:33 2017
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at  
 (null) RIP: isci_task_abort_task+0x43/0x4e0 [isci] RSP: 
a693c7967c80
  Failure: oops
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Dell Inc. Precision T5600
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: BUG: unable to handle kernel NULL pointer dereference at   
(null)
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0Y56T3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd05/06/2017:svnDellInc.:pnPrecisionT5600:pvr01:rvnDellInc.:rn0Y56T3:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T5600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1738839] Re: [Medion S2217] Touchpad not properly recognized

[Full Name]

Tested with:

- ubuntu 16.04
- ubuntu 16.10
- ubuntu 17.04

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

Title:
  [Medion S2217] Touchpad not properly recognized

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The ELAN (not Elantech) touchpad in my Medion S2217 laptop is not
  properly recognized. The touchpad shows up as an ITE Tech. Inc. ITE
  Device(8910) and works only as a plain pointing device. Multitouch and
  scrolling or anything else however, do not function, nor do options
  for this show up in the Mouse & Touchpad options in Ubuntu.

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

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

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Thadeu Lima de Souza Cascardo]

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Many users are reporting issues with bios corruption with
  17.10. This seems to stem from enabling the intel-spi-* drivers in the
  kernel, which don't appear to be ready for use on end-user machines.

  Fix: Disable this driver.

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Hi all,

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

   UPDATE (01/12/2017) 

  LENOVO machines affected so far (please add your affected model to
  this list):

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70

  The bug also affects Acer Aspire E5-771G.

  ---

  Temporary workaround:
  https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t
  -Save-Settings-Or-Exit/m-p/3853208#M157885

  ---

  result from apport-collect 1734147:

  ---

  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tob1608 F pulseaudio
   /dev/snd/controlC0:  tob1608 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO

  ---

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

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

[Kernel-packages] [Bug 1738839] [NEW] [Medion S2217] Touchpad not properly recognized

[Full Name]

Public bug reported:

The ELAN (not Elantech) touchpad in my Medion S2217 laptop is not
properly recognized. The touchpad shows up as an ITE Tech. Inc. ITE
Device(8910) and works only as a plain pointing device. Multitouch and
scrolling or anything else however, do not function, nor do options for
this show up in the Mouse & Touchpad options in Ubuntu.

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


** Tags: input legacy s2217 touch touchpad

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

Title:
  [Medion S2217] Touchpad not properly recognized

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The ELAN (not Elantech) touchpad in my Medion S2217 laptop is not
  properly recognized. The touchpad shows up as an ITE Tech. Inc. ITE
  Device(8910) and works only as a plain pointing device. Multitouch and
  scrolling or anything else however, do not function, nor do options
  for this show up in the Mouse & Touchpad options in Ubuntu.

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

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

[Kernel-packages] [Bug 1738838] [NEW] bluetooth does not turn on; settings interfaces are nonsensical

[Christopher Barrington-Leigh]

Public bug reported:

See video. I have installed bluetooth, blueman, bluez but it makes no
difference to a broken interface to control bluetooth under Gnome 17.10,
as shown in the attached video.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: bluetooth 5.46-0ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec 17 22:32:30 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-11-18 (30 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
InterestingModules: bnep btusb bluetooth
MachineType: LENOVO 20BXCTO1WW
PackageArchitecture: all
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed 
root=UUID=02bd5120-a925-442c-a0dd-1cce59920632 ro quiet splash 
psmouse.synaptics_intertouch=0 vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/06/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: JBET54WW (1.19 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BXCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T450s
dmi.product.name: 20BXCTO1WW
dmi.product.version: ThinkPad T450s
dmi.sys.vendor: LENOVO
hciconfig:

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


** Tags: amd64 apport-bug artful

** Attachment added: "Bluetooth options are to turn off only; turning on gives 
strange behaviour. Sliders do not work, effect is not as expected."
   https://bugs.launchpad.net/bugs/1738838/+attachment/5024237/+files/out-1.ogv

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

Title:
  bluetooth does not turn on; settings interfaces are nonsensical

Status in bluez package in Ubuntu:
  New

Bug description:
  See video. I have installed bluetooth, blueman, bluez but it makes no
  difference to a broken interface to control bluetooth under Gnome
  17.10, as shown in the attached video.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluetooth 5.46-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 17 22:32:30 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-18 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: bnep btusb bluetooth
  MachineType: LENOVO 20BXCTO1WW
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed 
root=UUID=02bd5120-a925-442c-a0dd-1cce59920632 ro quiet splash 
psmouse.synaptics_intertouch=0 vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET54WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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

[Kernel-packages] [Bug 1400463] Re: [Medion Akoya P2214T] Touchpad not properly recognized

[Full Name]

Reply from Vendor:
---

Dear Input Maintainer,

 
Nice to get your email.

ITE is chip provider. I am sorry that I do not have info related
customer’s design.

You might contact with notebook vendor to get support.
 

Thanks.

Mitch

從: ITE Tech. Inc. [no-re...@ite.com.tw]
寄件日期: 2017年12月13日 下午 02:59
至: Input Maintainer
主旨: ITE 聯陽半導體-聯絡我們通知信

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

Title:
  [Medion Akoya P2214T] Touchpad not properly recognized

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The ELAN (not Elantech) touchpad in my Medion Akoya P2214T (MD 99430)
  laptop/tablet hybrid is not properly recognized. Both the touchscreen
  and the touchpad function as a regular mouse, but the touchpad shows
  up as an ITE Tech. Inc. ITE Device(8910) pointer in xinput (see
  attachment). Multitouch and scrolling however, do not function, nor do
  options for this show up in the Mouse & Touchpad options in Ubuntu
  14.10 64-bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xserver-xorg-input-synaptics 1.8.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Dec  8 20:02:14 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  InstallationDate: Installed on 2014-11-12 (26 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Medion Akoya P2214T
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=06056019-c592-4d2d-9738-54e729126d7d ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/26/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 205
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Akoya P2214T
  dmi.board.vendor: Medion
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Medion
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr205:bd08/26/2014:svnMedion:pnAkoyaP2214T:pvr1.0:rvnMedion:rnAkoyaP2214T:rvr1.0:cvnMedion:ct8:cvrToBeFilledByO.E.M.:
  dmi.product.name: Akoya P2214T
  dmi.product.version: 1.0
  dmi.sys.vendor: Medion
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Mon Dec  8 18:30:57 2014
  xserver.configfile: default
  xserver.errors:
   Error loading keymap 
/var/lib/xkb/server-992DCD2811F9928D990F91F3229E52A1EC62B72A.xkm
   Error loading keymap 
/var/lib/xkb/server-992DCD2811F9928D990F91F3229E52A1EC62B72A.xkm
   Error loading keymap 
/var/lib/xkb/server-992DCD2811F9928D990F91F3229E52A1EC62B72A.xkm
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12637
   vendor AUO
  xserver.version: 2:1.16.0-1ubuntu1
  --- 
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mizuti 2439 F pulseaudio
  CRDA:
   country EU:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=325a292a-ad2c-493d-b148-aff85b17b41e
  InstallationDate: Installed on 2015-10-15 (616 days ago)
  InstallationMedia: Linux Mint 17.2 "Rafaela" - Release amd64 20150627
  MachineType: Medion Akoya P2214T
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=727a143b-7e46-4f81-8cc9-c37b396d582e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-24-generic N/A
   linux-backports-modules-3.16.0-24-generic  N/A
   linux-firmware 1.127.23
  Tags:  rafaela
  Uname: Linux 3.16.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably 

[Kernel-packages] [Bug 1738837] Re: BUG: unable to handle kernel NULL pointer dereference at (null)

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  BUG: unable to handle kernel NULL pointer dereference at
  (null)

Status in linux package in Ubuntu:
  New

Bug description:
  Just trying to run ubuntu 17.10 desktop installation and selected TRY
  it out...

  ProblemType: KernelOops
  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 x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  ubuntu 4342 F pulseaudio
   /dev/snd/controlC0:  ubuntu 4342 F pulseaudio
   /dev/snd/controlC1:  ubuntu 4342 F pulseaudio
  CasperVersion: 1.387
  Date: Mon Dec 18 15:55:33 2017
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at  
 (null) RIP: isci_task_abort_task+0x43/0x4e0 [isci] RSP: 
a693c7967c80
  Failure: oops
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Dell Inc. Precision T5600
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: BUG: unable to handle kernel NULL pointer dereference at   
(null)
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0Y56T3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd05/06/2017:svnDellInc.:pnPrecisionT5600:pvr01:rvnDellInc.:rn0Y56T3:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T5600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1738837] [NEW] BUG: unable to handle kernel NULL pointer dereference at (null)

[Maraschin]

Public bug reported:

Just trying to run ubuntu 17.10 desktop installation and selected TRY it
out...

ProblemType: KernelOops
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 x86_64
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  ubuntu 4342 F pulseaudio
 /dev/snd/controlC0:  ubuntu 4342 F pulseaudio
 /dev/snd/controlC1:  ubuntu 4342 F pulseaudio
CasperVersion: 1.387
Date: Mon Dec 18 15:55:33 2017
DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at
   (null) RIP: isci_task_abort_task+0x43/0x4e0 [isci] RSP: a693c7967c80
Failure: oops
IwConfig:
 lono wireless extensions.
 
 enp0s25   no wireless extensions.
LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: Dell Inc. Precision T5600
ProcFB: 0 nouveaufb
ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: BUG: unable to handle kernel NULL pointer dereference at   (null)
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/06/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.name: 0Y56T3
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd05/06/2017:svnDellInc.:pnPrecisionT5600:pvr01:rvnDellInc.:rn0Y56T3:rvrA01:cvnDellInc.:ct7:cvr:
dmi.product.name: Precision T5600
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-kerneloops artful kernel-driver-isci 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/1738837

Title:
  BUG: unable to handle kernel NULL pointer dereference at
  (null)

Status in linux package in Ubuntu:
  New

Bug description:
  Just trying to run ubuntu 17.10 desktop installation and selected TRY
  it out...

  ProblemType: KernelOops
  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 x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  ubuntu 4342 F pulseaudio
   /dev/snd/controlC0:  ubuntu 4342 F pulseaudio
   /dev/snd/controlC1:  ubuntu 4342 F pulseaudio
  CasperVersion: 1.387
  Date: Mon Dec 18 15:55:33 2017
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at  
 (null) RIP: isci_task_abort_task+0x43/0x4e0 [isci] RSP: 
a693c7967c80
  Failure: oops
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Dell Inc. Precision T5600
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: BUG: unable to handle kernel NULL pointer dereference at   
(null)
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0Y56T3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd05/06/2017:svnDellInc.:pnPrecisionT5600:pvr01:rvnDellInc.:rn0Y56T3:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T5600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1738823] Re: linux: 4.13.0-21.24 -proposed tracker

[Kleber Sacilotto de Souza]

** Changed in: kernel-sru-workflow/verification-testing
   Status: Invalid => New

** Changed in: kernel-sru-workflow/security-signoff
   Status: Invalid => New

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

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Invalid => New

** Changed in: kernel-sru-workflow/promote-to-security
   Status: Invalid => New

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

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: Invalid => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: Invalid => In Progress

** Changed in: kernel-sru-workflow/prepare-package
   Status: Invalid => In Progress

** Changed in: kernel-sru-workflow/certification-testing
   Status: Invalid => New

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

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

Title:
  linux: 4.13.0-21.24 -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-meta series:
  In Progress
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

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

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

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

[Kernel-packages] [Bug 1692538] Re: Ubuntu 16.04.02: ibmveth: Support to enable LSO/CSO for Trunk VEA

[Frank Heimes]

Siva and Daniel, may I just ask where we are on this?
Well it looks to me that Siva/IBM sees this more as a miss-configuration, so 
that the changes in comment #18 are _not_ needed. Daniel, do you see it now the 
same way?
But in this case this needs to be documented somewhere, so that we can point 
customers, too it - right?

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

Title:
  Ubuntu 16.04.02: ibmveth: Support to enable LSO/CSO for Trunk VEA

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

Bug description:
  
  == SRU Justification ==
  Commit 66aa0678ef is request to fix four issues with the ibmveth driver.
  The issues are as follows:
  - Issue 1: ibmveth doesn't support largesend and checksum offload features 
when configured as "Trunk".
  - Issue 2: SYN packet drops seen at destination VM. When the packet
  originates, it has CHECKSUM_PARTIAL flag set and as it gets delivered to IO
  server's inbound Trunk ibmveth, on validating "checksum good" bits in ibmveth
  receive routine, SKB's ip_summed field is set with CHECKSUM_UNNECESSARY flag.
  - Issue 3: First packet of a TCP connection will be dropped, if there is
  no OVS flow cached in datapath.
  - Issue 4: ibmveth driver doesn't have support for SKB's with frag_list.

  The details for the fixes to these issues are described in the commits
  git log.



  == Comment: #0 - BRYANT G. LY  - 2017-05-22 08:40:16 ==
  ---Problem Description---

   - Issue 1: ibmveth doesn't support largesend and checksum offload features
     when configured as "Trunk". Driver has explicit checks to prevent
     enabling these offloads.

   - Issue 2: SYN packet drops seen at destination VM. When the packet
     originates, it has CHECKSUM_PARTIAL flag set and as it gets delivered to
     IO server's inbound Trunk ibmveth, on validating "checksum good" bits
     in ibmveth receive routine, SKB's ip_summed field is set with
     CHECKSUM_UNNECESSARY flag. This packet is then bridged by OVS (or Linux
     Bridge) and delivered to outbound Trunk ibmveth. At this point the
     outbound ibmveth transmit routine will not set "no checksum" and
     "checksum good" bits in transmit buffer descriptor, as it does so only
     when the ip_summed field is CHECKSUM_PARTIAL. When this packet gets
     delivered to destination VM, TCP layer receives the packet with checksum
     value of 0 and with no checksum related flags in ip_summed field. This
     leads to packet drops. So, TCP connections never goes through fine.

   - Issue 3: First packet of a TCP connection will be dropped, if there is
     no OVS flow cached in datapath. OVS while trying to identify the flow,
     computes the checksum. The computed checksum will be invalid at the
     receiving end, as ibmveth transmit routine zeroes out the pseudo
     checksum value in the packet. This leads to packet drop.

   - Issue 4: ibmveth driver doesn't have support for SKB's with frag_list.
     When Physical NIC has GRO enabled and when OVS bridges these packets,
     OVS vport send code will end up calling dev_queue_xmit, which in turn
     calls validate_xmit_skb.
     In validate_xmit_skb routine, the larger packets will get segmented into
     MSS sized segments, if SKB has a frag_list and if the driver to which
     they are delivered to doesn't support NETIF_F_FRAGLIST feature.

  Contact Information = Bryant G. Ly/b...@us.ibm.com

  ---uname output---
  4.8.0-51.54

  Machine Type = p8

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   Increases performance greatly

  The patch has been accepted upstream:
  https://patchwork.ozlabs.org/patch/764533/

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

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

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Ionuț Dăscălescu]

** Description changed:

  SRU Justification
  
  Impact: Many users are reporting issues with bios corruption with 17.10.
  This seems to stem from enabling the intel-spi-* drivers in the kernel,
  which don't appear to be ready for use on end-user machines.
  
  Fix: Disable this driver.
  
  Test Case: Fix has been verified by our HWE team on affected hardware.
  
  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.
  
  ---
  
  Hi all,
  
  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.
  
  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.
  
  Moreover (and most important) USB booting is not possible anymore since
  USB is not recognized. It's very serious, since our machines do not have
  a CDROM.
  
  Lenovo forums at the moment are full of topics regading this issue.
  
  Thank you!!
  
   UPDATE (01/12/2017) 
  
  LENOVO machines affected so far (please add your affected model to this
  list):
  
  Lenovo B40-70
  Lenovo B50-70
+ Lenovo B50-80
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  
  The bug also affects Acer Aspire E5-771G.
  
  ---
  
  Temporary workaround:
  https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t
  -Save-Settings-Or-Exit/m-p/3853208#M157885
  
  ---
  
  result from apport-collect 1734147:
  
  ---
  
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tob1608 F pulseaudio
   /dev/snd/controlC0:  tob1608 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO
  
  ---

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

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

Bug description:
  SRU Justification

  Impact: Many users are reporting issues with bios corruption with
  17.10. This seems to stem from enabling the intel-spi-* drivers in the
  kernel, which don't appear to be ready for use on end-user machines.

  Fix: Disable this driver.

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Hi all,

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

   UPDATE (01/12/2017) 

  LENOVO machines affected so far (please add your affected model to
  this list):

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga 

[Kernel-packages] [Bug 1658733] libvirt XML for multipath guest dotg9

[bugproxy]

Default Comment by Bridge

** Attachment added: "libvirt XML for multipath guest dotg9"
   https://bugs.launchpad.net/bugs/1658733/+attachment/5024209/+files/dotg9.xml

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

Title:
  Ubuntu 16.04.2KVM:kdump fails to mount root file system when
  noirqdistrib is missing as dump kernel parameter

Status in The Ubuntu-power-systems project:
  Confirmed
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  New
Status in kexec-tools source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in kexec-tools source package in Zesty:
  New
Status in makedumpfile source package in Zesty:
  New
Status in kexec-tools source package in Artful:
  Invalid
Status in makedumpfile source package in Artful:
  Fix Committed
Status in kexec-tools source package in Bionic:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  On Power Systems, some interrupts are missed, and dumping the crash will 
fail. Adding the noirqdistrib kernel parameter to the kdump kernel will fix 
this.

  [Test Case]
  Setting up kdump to target a virtio-scsi device on a Power System.

  [Regression Potential]
  The parameter could be interpreted differently on a different platform and 
kdump would fail. However, it has been verified that no other platform uses 
such parameter. If another parameter would have been incorrectly removed on the 
patch, kdump could fail on other systems.


  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel
  fails to mount the root file system.  This error does not occur in a
  similar guest installed to a single path device.

  Full console output of the kdump failure is attached.  These messages
  from the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.

  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest

  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  >
  > Could you please recreate the guest for further debug?

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  this.)

  == Comment: #22 - Mauro Sergio Martins Rodrigues  - 2017-01-11 09:31:38 ==
  I managed to get kdump to mount rootfs and perform its tasks by setting 
KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see 
http://pastebin.hursley.ibm.com/8239

  I'm still investigating to figure out what is the reason behind this
  behavior.

  Thanks,

  --
  maurosr

  == Comment: #23 - Mauricio Faria De Oliveira  - 2017-01-11 11:56:40 ==
  Mauro,

  (In reply to comment #22)
  > I managed to get kdump to mount rootfs and perform its 

[Kernel-packages] [Bug 1658733] loglevel 8 kdump console log

[bugproxy]

Default Comment by Bridge

** Attachment added: "loglevel 8 kdump console log"
   
https://bugs.launchpad.net/bugs/1658733/+attachment/5024207/+files/dotg9-kdump-loglevel8.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/1658733

Title:
  Ubuntu 16.04.2KVM:kdump fails to mount root file system when
  noirqdistrib is missing as dump kernel parameter

Status in The Ubuntu-power-systems project:
  Confirmed
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  New
Status in kexec-tools source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in kexec-tools source package in Zesty:
  New
Status in makedumpfile source package in Zesty:
  New
Status in kexec-tools source package in Artful:
  Invalid
Status in makedumpfile source package in Artful:
  Fix Committed
Status in kexec-tools source package in Bionic:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  On Power Systems, some interrupts are missed, and dumping the crash will 
fail. Adding the noirqdistrib kernel parameter to the kdump kernel will fix 
this.

  [Test Case]
  Setting up kdump to target a virtio-scsi device on a Power System.

  [Regression Potential]
  The parameter could be interpreted differently on a different platform and 
kdump would fail. However, it has been verified that no other platform uses 
such parameter. If another parameter would have been incorrectly removed on the 
patch, kdump could fail on other systems.


  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel
  fails to mount the root file system.  This error does not occur in a
  similar guest installed to a single path device.

  Full console output of the kdump failure is attached.  These messages
  from the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.

  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest

  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  >
  > Could you please recreate the guest for further debug?

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  this.)

  == Comment: #22 - Mauro Sergio Martins Rodrigues  - 2017-01-11 09:31:38 ==
  I managed to get kdump to mount rootfs and perform its tasks by setting 
KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see 
http://pastebin.hursley.ibm.com/8239

  I'm still investigating to figure out what is the reason behind this
  behavior.

  Thanks,

  --
  maurosr

  == Comment: #23 - Mauricio Faria De Oliveira  - 2017-01-11 11:56:40 ==
  Mauro,

  (In reply to comment #22)
  > I managed to get kdump to mount rootfs and 

[Kernel-packages] [Bug 1658733] Adds "noirqdistrib" parameter to kdump command line

[bugproxy]

--- Comment on attachment From maur...@br.ibm.com 2017-01-23 12:10 
EDT---


This patch fixes the issue. The noirqdistrib is a necessary parameter for ppc64 
platform as stated in kdump docs 
https://www.kernel.org/doc//Documentation/kdump/kdump.txt
With this fix crash kernel uses the correct irq server for the case where only 
one cpu is online.

** Attachment added: "Adds "noirqdistrib" parameter to kdump command line"
   
https://bugs.launchpad.net/bugs/1658733/+attachment/5024210/+files/add_noirqdistrib_param_for_ppc64.diff

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

Title:
  Ubuntu 16.04.2KVM:kdump fails to mount root file system when
  noirqdistrib is missing as dump kernel parameter

Status in The Ubuntu-power-systems project:
  Confirmed
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  New
Status in kexec-tools source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in kexec-tools source package in Zesty:
  New
Status in makedumpfile source package in Zesty:
  New
Status in kexec-tools source package in Artful:
  Invalid
Status in makedumpfile source package in Artful:
  Fix Committed
Status in kexec-tools source package in Bionic:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  On Power Systems, some interrupts are missed, and dumping the crash will 
fail. Adding the noirqdistrib kernel parameter to the kdump kernel will fix 
this.

  [Test Case]
  Setting up kdump to target a virtio-scsi device on a Power System.

  [Regression Potential]
  The parameter could be interpreted differently on a different platform and 
kdump would fail. However, it has been verified that no other platform uses 
such parameter. If another parameter would have been incorrectly removed on the 
patch, kdump could fail on other systems.


  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel
  fails to mount the root file system.  This error does not occur in a
  similar guest installed to a single path device.

  Full console output of the kdump failure is attached.  These messages
  from the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.

  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest

  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  >
  > Could you please recreate the guest for further debug?

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  this.)

  == Comment: #22 - Mauro Sergio Martins Rodrigues  - 2017-01-11 09:31:38 ==
  I managed to get kdump to mount rootfs and perform its tasks by setting 

[Kernel-packages] [Bug 1658733] kdump kernel console msgs with bug 146907 workaround

[bugproxy]

Default Comment by Bridge

** Attachment added: "kdump kernel console msgs with bug 146907 workaround"
   
https://bugs.launchpad.net/bugs/1658733/+attachment/5024208/+files/dotg9-kdump-bz146907-workaround.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/1658733

Title:
  Ubuntu 16.04.2KVM:kdump fails to mount root file system when
  noirqdistrib is missing as dump kernel parameter

Status in The Ubuntu-power-systems project:
  Confirmed
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  New
Status in kexec-tools source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in kexec-tools source package in Zesty:
  New
Status in makedumpfile source package in Zesty:
  New
Status in kexec-tools source package in Artful:
  Invalid
Status in makedumpfile source package in Artful:
  Fix Committed
Status in kexec-tools source package in Bionic:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  On Power Systems, some interrupts are missed, and dumping the crash will 
fail. Adding the noirqdistrib kernel parameter to the kdump kernel will fix 
this.

  [Test Case]
  Setting up kdump to target a virtio-scsi device on a Power System.

  [Regression Potential]
  The parameter could be interpreted differently on a different platform and 
kdump would fail. However, it has been verified that no other platform uses 
such parameter. If another parameter would have been incorrectly removed on the 
patch, kdump could fail on other systems.


  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel
  fails to mount the root file system.  This error does not occur in a
  similar guest installed to a single path device.

  Full console output of the kdump failure is attached.  These messages
  from the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.

  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest

  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  >
  > Could you please recreate the guest for further debug?

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  this.)

  == Comment: #22 - Mauro Sergio Martins Rodrigues  - 2017-01-11 09:31:38 ==
  I managed to get kdump to mount rootfs and perform its tasks by setting 
KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see 
http://pastebin.hursley.ibm.com/8239

  I'm still investigating to figure out what is the reason behind this
  behavior.

  Thanks,

  --
  maurosr

  == Comment: #23 - Mauricio Faria De Oliveira  - 2017-01-11 11:56:40 ==
  Mauro,

  (In reply to comment #22)
  > I managed to 

[Kernel-packages] [Bug 1658733] target fix for artful

[bugproxy]

Default Comment by Bridge

** Attachment added: "target fix for artful"
   
https://bugs.launchpad.net/bugs/1658733/+attachment/5024211/+files/makedumpfile_1.6.1-2ubuntu0.1.diff

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

Title:
  Ubuntu 16.04.2KVM:kdump fails to mount root file system when
  noirqdistrib is missing as dump kernel parameter

Status in The Ubuntu-power-systems project:
  Confirmed
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  New
Status in kexec-tools source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in kexec-tools source package in Zesty:
  New
Status in makedumpfile source package in Zesty:
  New
Status in kexec-tools source package in Artful:
  Invalid
Status in makedumpfile source package in Artful:
  Fix Committed
Status in kexec-tools source package in Bionic:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  On Power Systems, some interrupts are missed, and dumping the crash will 
fail. Adding the noirqdistrib kernel parameter to the kdump kernel will fix 
this.

  [Test Case]
  Setting up kdump to target a virtio-scsi device on a Power System.

  [Regression Potential]
  The parameter could be interpreted differently on a different platform and 
kdump would fail. However, it has been verified that no other platform uses 
such parameter. If another parameter would have been incorrectly removed on the 
patch, kdump could fail on other systems.


  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel
  fails to mount the root file system.  This error does not occur in a
  similar guest installed to a single path device.

  Full console output of the kdump failure is attached.  These messages
  from the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.

  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest

  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  >
  > Could you please recreate the guest for further debug?

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  this.)

  == Comment: #22 - Mauro Sergio Martins Rodrigues  - 2017-01-11 09:31:38 ==
  I managed to get kdump to mount rootfs and perform its tasks by setting 
KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see 
http://pastebin.hursley.ibm.com/8239

  I'm still investigating to figure out what is the reason behind this
  behavior.

  Thanks,

  --
  maurosr

  == Comment: #23 - Mauricio Faria De Oliveira  - 2017-01-11 11:56:40 ==
  Mauro,

  (In reply to comment #22)
  > I managed to get kdump to mount rootfs and 

[Kernel-packages] [Bug 1658733] fix for bionic

[bugproxy]

Default Comment by Bridge

** Attachment added: "fix for bionic"
   
https://bugs.launchpad.net/bugs/1658733/+attachment/5024212/+files/makedumpfile_1.6.2-1ubuntu0.1.diff

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

Title:
  Ubuntu 16.04.2KVM:kdump fails to mount root file system when
  noirqdistrib is missing as dump kernel parameter

Status in The Ubuntu-power-systems project:
  Confirmed
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  New
Status in kexec-tools source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in kexec-tools source package in Zesty:
  New
Status in makedumpfile source package in Zesty:
  New
Status in kexec-tools source package in Artful:
  Invalid
Status in makedumpfile source package in Artful:
  Fix Committed
Status in kexec-tools source package in Bionic:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  On Power Systems, some interrupts are missed, and dumping the crash will 
fail. Adding the noirqdistrib kernel parameter to the kdump kernel will fix 
this.

  [Test Case]
  Setting up kdump to target a virtio-scsi device on a Power System.

  [Regression Potential]
  The parameter could be interpreted differently on a different platform and 
kdump would fail. However, it has been verified that no other platform uses 
such parameter. If another parameter would have been incorrectly removed on the 
patch, kdump could fail on other systems.


  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel
  fails to mount the root file system.  This error does not occur in a
  similar guest installed to a single path device.

  Full console output of the kdump failure is attached.  These messages
  from the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.

  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest

  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  >
  > Could you please recreate the guest for further debug?

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  this.)

  == Comment: #22 - Mauro Sergio Martins Rodrigues  - 2017-01-11 09:31:38 ==
  I managed to get kdump to mount rootfs and perform its tasks by setting 
KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see 
http://pastebin.hursley.ibm.com/8239

  I'm still investigating to figure out what is the reason behind this
  behavior.

  Thanks,

  --
  maurosr

  == Comment: #23 - Mauricio Faria De Oliveira  - 2017-01-11 11:56:40 ==
  Mauro,

  (In reply to comment #22)
  > I managed to get kdump to mount rootfs and perform its 

[Kernel-packages] [Bug 1738823] Re: linux: 4.13.0-21.24 -proposed tracker

[Kleber Sacilotto de Souza]

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

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

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Invalid

** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Invalid

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Invalid

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: In Progress => Invalid

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

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Invalid

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

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Invalid

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

Title:
  linux: 4.13.0-21.24 -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid

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

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

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

[Kernel-packages] [Bug 1738823] Re: linux: 4.13.0-21.24 -proposed tracker

[Thadeu Lima de Souza Cascardo]

** Summary changed:

- linux:  -proposed tracker
+ linux: 4.13.0-21.24 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de 
Souza Cascardo (cascardo)

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de 
Souza Cascardo (cascardo)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de 
Souza Cascardo (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/1738823

Title:
  linux: 4.13.0-21.24 -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid

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

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

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

[Kernel-packages] [Bug 1658733] Re: Ubuntu 16.04.2KVM:kdump fails to mount root file system when noirqdistrib is missing as dump kernel parameter

[Frank Heimes]

@ IBM: Please can you verify the packages from artful-proposed and 
xenial-proposed?
And thx for the artful and bionic patches.

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

Title:
  Ubuntu 16.04.2KVM:kdump fails to mount root file system when
  noirqdistrib is missing as dump kernel parameter

Status in The Ubuntu-power-systems project:
  Confirmed
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  New
Status in kexec-tools source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in kexec-tools source package in Zesty:
  New
Status in makedumpfile source package in Zesty:
  New
Status in kexec-tools source package in Artful:
  Invalid
Status in makedumpfile source package in Artful:
  Fix Committed
Status in kexec-tools source package in Bionic:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  On Power Systems, some interrupts are missed, and dumping the crash will 
fail. Adding the noirqdistrib kernel parameter to the kdump kernel will fix 
this.

  [Test Case]
  Setting up kdump to target a virtio-scsi device on a Power System.

  [Regression Potential]
  The parameter could be interpreted differently on a different platform and 
kdump would fail. However, it has been verified that no other platform uses 
such parameter. If another parameter would have been incorrectly removed on the 
patch, kdump could fail on other systems.


  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel
  fails to mount the root file system.  This error does not occur in a
  similar guest installed to a single path device.

  Full console output of the kdump failure is attached.  These messages
  from the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.

  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest

  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  >
  > Could you please recreate the guest for further debug?

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  this.)

  == Comment: #22 - Mauro Sergio Martins Rodrigues  - 2017-01-11 09:31:38 ==
  I managed to get kdump to mount rootfs and perform its tasks by setting 
KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see 
http://pastebin.hursley.ibm.com/8239

  I'm still investigating to figure out what is the reason behind this
  behavior.

  Thanks,

  --
  maurosr

  == Comment: #23 - Mauricio Faria De Oliveira  - 2017-01-11 11:56:40 ==
  Mauro,

  (In reply to comment #22)
  > I managed to get kdump to mount rootfs and perform its tasks by setting
  > 

[Kernel-packages] [Bug 1738823] [NEW] linux: -proposed tracker

[Kleber Sacilotto de Souza]

Public bug reported:

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

** 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/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 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: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

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

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

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

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


** Tags: artful kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2017.11.20-3 kernel-sru-master-kernel

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

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

** Tags added: artful

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

** Also affects: kernel-sru-workflow/certification-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-security
   Importance: Undecided
   Status: New

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

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

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

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

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

** 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/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

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

[Kernel-packages] [Bug 1724120] Re: Ubuntu 16.04.3 - call traces occurs when memory-hotplug test is run with 16Gb hugepages configured

[Joseph Salisbury]

An Artful SRU request for these commits was already submitted in bug
1706247.  I'm working on backporting them to Xenial(4.4 based), but have
had some issues with build failures.  There are some prereq commits that
are also needed for 4.4 kernels.  I'll see what the extent of these
prereqs are and post an update.

If there are too many prereqs for Xenial, we may have to have this
issues address in Xenial via the HWE kernels, but I'm investigating.

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

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

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

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

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

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

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

Title:
  Ubuntu 16.04.3 - call traces occurs when memory-hotplug test is run
  with 16Gb hugepages configured

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

Bug description:
  Issue:

  Call traces occurs when memory-hotplug script is run with 16Gb
  hugepages configured.

  Environment:
  ppc64le PowerVM Lpar

  root@ltctuleta-lp1:~# uname -r
  4.4.0-34-generic

  root@ltctuleta-lp1:~# cat /proc/meminfo | grep -i huge
  AnonHugePages: 0 kB
  HugePages_Total:   2
  HugePages_Free:2
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:   16777216 kB

  root@ltctuleta-lp1:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:85G 32G 52G 16M193M 
52G
  Swap:   43G  0B 43G

  Steps to reproduce:
  1 - Download kernel source and enter to the directory- 
tools/testing/selftests/memory-hotplug/
  2 - Run  mem-on-off-test.sh script in it.

  System gives call traces like:

  offline_memory_expect_success 639: unexpected fail
  online-offline 668
  [   57.552964] Unable to handle kernel paging request for data at address 
0x0028
  [   57.552977] Faulting instruction address: 0xc029bc04
  [   57.552987] Oops: Kernel access of bad area, sig: 11 [#1]
  [   57.552992] SMP NR_CPUS=2048 NUMA pSeries
  [   57.553002] Modules linked in: btrfs xor raid6_pq pseries_rng sunrpc 
autofs4 ses enclosure nouveau bnx2x i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops drm vxlan ip6_udp_tunnel ipr udp_tunnel 
rtc_generic mdio libcrc32c
  [   57.553050] CPU: 44 PID: 6518 Comm: mem-on-off-test Not tainted 
4.4.0-34-generic #53-Ubuntu
  [   57.553059] task: c0072773c8e0 ti: c0072778 task.ti: 
c0072778
  [   57.553067] NIP: c029bc04 LR: c029bbdc CTR: 
c01107f0
  [   57.553076] REGS: c00727783770 TRAP: 0300   Not tainted  
(4.4.0-34-generic)
  [   57.553083] MSR: 80019033   CR: 24242882  
XER: 0002
  [   57.553104] CFAR: c0008468 DAR: 0028 DSISR: 4000 
SOFTE: 1 
  GPR00: c029bbdc c007277839f0 c15b5d00  
  GPR04: 0029d000 0800  fa01 
  GPR08: fa700020 0008 c185e270 c00e7e50 
  GPR12: 2200 ce6ea200 0029d000 2200 
  GPR16: 1000 c15e2200 0a70  
  GPR20: 0001 0100 0200 c15f16d0 
  GPR24: c1876510  0001 c1872a00 
  GPR28: 0029d000 f000 fa70 0029c000 
  [   57.553211] NIP [c029bc04] dissolve_free_huge_pages+0x154/0x220
  [   57.553219] LR [c029bbdc] dissolve_free_huge_pages+0x12c/0x220
  [   57.553226] Call Trace:
  [   57.553231] [c007277839f0] [c029bbdc] 
dissolve_free_huge_pages+0x12c/0x220 (unreliable)
  [   57.553244] [c00727783a80] [c02dcbc8] 
__offline_pages.constprop.6+0x3f8/0x900
  [   57.553254] [c00727783bd0] [c06fbb38] 
memory_subsys_offline+0xa8/0x110
  [   57.553265] [c00727783c00] [c06d6424] 
device_offline+0x104/0x140
  [   57.553274] [c00727783c40] [c06fba80] 
store_mem_state+0x180/0x190
  [   57.553283] [c00727783c80] [c06d1e58] dev_attr_store+0x68/0xa0
  [   57.553293] [c00727783cc0] [c0398110] sysfs_kf_write+0x80/0xb0
  [   57.553302] [c00727783d00] [c0397028] 
kernfs_fop_write+0x188/0x200
  [   

[Kernel-packages] [Bug 1724120] Re: Ubuntu 16.04.3 - call traces occurs when memory-hotplug test is run with 16Gb hugepages configured

[Joseph Salisbury]

** Changed in: linux (Ubuntu)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph 
Salisbury (jsalisbury)

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

Title:
  Ubuntu 16.04.3 - call traces occurs when memory-hotplug test is run
  with 16Gb hugepages configured

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

Bug description:
  Issue:

  Call traces occurs when memory-hotplug script is run with 16Gb
  hugepages configured.

  Environment:
  ppc64le PowerVM Lpar

  root@ltctuleta-lp1:~# uname -r
  4.4.0-34-generic

  root@ltctuleta-lp1:~# cat /proc/meminfo | grep -i huge
  AnonHugePages: 0 kB
  HugePages_Total:   2
  HugePages_Free:2
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:   16777216 kB

  root@ltctuleta-lp1:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:85G 32G 52G 16M193M 
52G
  Swap:   43G  0B 43G

  Steps to reproduce:
  1 - Download kernel source and enter to the directory- 
tools/testing/selftests/memory-hotplug/
  2 - Run  mem-on-off-test.sh script in it.

  System gives call traces like:

  offline_memory_expect_success 639: unexpected fail
  online-offline 668
  [   57.552964] Unable to handle kernel paging request for data at address 
0x0028
  [   57.552977] Faulting instruction address: 0xc029bc04
  [   57.552987] Oops: Kernel access of bad area, sig: 11 [#1]
  [   57.552992] SMP NR_CPUS=2048 NUMA pSeries
  [   57.553002] Modules linked in: btrfs xor raid6_pq pseries_rng sunrpc 
autofs4 ses enclosure nouveau bnx2x i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops drm vxlan ip6_udp_tunnel ipr udp_tunnel 
rtc_generic mdio libcrc32c
  [   57.553050] CPU: 44 PID: 6518 Comm: mem-on-off-test Not tainted 
4.4.0-34-generic #53-Ubuntu
  [   57.553059] task: c0072773c8e0 ti: c0072778 task.ti: 
c0072778
  [   57.553067] NIP: c029bc04 LR: c029bbdc CTR: 
c01107f0
  [   57.553076] REGS: c00727783770 TRAP: 0300   Not tainted  
(4.4.0-34-generic)
  [   57.553083] MSR: 80019033   CR: 24242882  
XER: 0002
  [   57.553104] CFAR: c0008468 DAR: 0028 DSISR: 4000 
SOFTE: 1 
  GPR00: c029bbdc c007277839f0 c15b5d00  
  GPR04: 0029d000 0800  fa01 
  GPR08: fa700020 0008 c185e270 c00e7e50 
  GPR12: 2200 ce6ea200 0029d000 2200 
  GPR16: 1000 c15e2200 0a70  
  GPR20: 0001 0100 0200 c15f16d0 
  GPR24: c1876510  0001 c1872a00 
  GPR28: 0029d000 f000 fa70 0029c000 
  [   57.553211] NIP [c029bc04] dissolve_free_huge_pages+0x154/0x220
  [   57.553219] LR [c029bbdc] dissolve_free_huge_pages+0x12c/0x220
  [   57.553226] Call Trace:
  [   57.553231] [c007277839f0] [c029bbdc] 
dissolve_free_huge_pages+0x12c/0x220 (unreliable)
  [   57.553244] [c00727783a80] [c02dcbc8] 
__offline_pages.constprop.6+0x3f8/0x900
  [   57.553254] [c00727783bd0] [c06fbb38] 
memory_subsys_offline+0xa8/0x110
  [   57.553265] [c00727783c00] [c06d6424] 
device_offline+0x104/0x140
  [   57.553274] [c00727783c40] [c06fba80] 
store_mem_state+0x180/0x190
  [   57.553283] [c00727783c80] [c06d1e58] dev_attr_store+0x68/0xa0
  [   57.553293] [c00727783cc0] [c0398110] sysfs_kf_write+0x80/0xb0
  [   57.553302] [c00727783d00] [c0397028] 
kernfs_fop_write+0x188/0x200
  [   57.553312] [c00727783d50] [c02e190c] __vfs_write+0x6c/0xe0
  [   57.553321] [c00727783d90] [c02e2640] vfs_write+0xc0/0x230
  [   57.553329] [c00727783de0] [c02e367c] SyS_write+0x6c/0x110
  [   57.553339] [c00727783e30] [c0009204] system_call+0x38/0xb4
  [   57.553346] Instruction dump:
  [   57.553351] 7e831836 4bfff991 e91e0028 e8fe0020 7d32e82a f9070008 f8e8 
fabe0020 
  [   57.553366] fade0028 79294620 79291764 7d234a14  3908 
f9030028 81091458 
  [   57.553383] ---[ end trace 617f7bdd75bcfc10 ]---
  [   57.557133] 
  Segmentation fault

  The following commit IDs were built into a 4.10.0-37-generic #41 test
  kernel and verified to fix the problem:

  a525108cf1cc14651602d678da38fa627a76a724
  e1073d1e7920946ac4776a619cc40668b9e1401b
  40692eb5eea209c2dd55857f44b4e1d7206e91d6
  e24a1307ba1f99fc62a0bd61d5e87fcfb6d5503d
  79cc38ded1e1ac86e69c90f604efadd50b0b3762
  

[Kernel-packages] [Bug 1738483] Re: package linux-image-4.4.0-104-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Joseph Salisbury]

You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"

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

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

Title:
  package linux-image-4.4.0-104-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In the middle of a Software Update, this happened.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-104-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  Uname: Linux 4.4.0-103-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  w316673 F pulseaudio
   /dev/snd/seq:timidity   1726 F timidity
  Date: Fri Dec 15 10:29:58 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=152f6ef7-3554-422a-aad2-1224361fd43f
  InstallationDate: Installed on 2013-01-23 (1786 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: Dell Inc. Inspiron 530s
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic 
root=UUID=83a64b80-5a37-4659-b797-221b88ef41f8 ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.14
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.4.0-104-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.16
  dmi.board.name: 0RY007
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.16:bd12/12/2008:svnDellInc.:pnInspiron530s:pvr:rvnDellInc.:rn0RY007:rvr:cvnDellInc.:ct3:cvrOEM:
  dmi.product.name: Inspiron 530s
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1738490] Re: current boot config dims screen during initramfs

[Joseph Salisbury]

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.15 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.15-rc4

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

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

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

Title:
  current boot config dims screen during initramfs

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is a weird one. Shortly after moving to 17.10, my laptop has
  started dimming its internal screen to minimum brightness at the start
  of initramfs execution. shortly thereafter it restores it to normal
  brightness, but that only happens *after* typing in encrypted
  filesystem passwords, so the password dialogues are practically
  invisible. Not sure why its doing this, but whatever's restoring the
  brightness should do it before prompting for filesystem mounting so
  these prompts are actually visible.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-generic 4.13.0.19.20
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tessa 17026 F pulseaudio
   /dev/snd/controlC1:  tessa 17026 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Dec 15 13:44:02 2017
  InstallationDate: Installed on 2016-07-08 (524 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Apple Inc. MacBookPro11,4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic.efi.signed 
root=ZFS=rpool/root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-19 (57 days ago)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP114.88Z.0177.B00.1708080033
  dmi.board.name: Mac-06F11FD93F0323C5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,4
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-06F11FD93F0323C5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP114.88Z.0177.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro11,4
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1692538] Re: Ubuntu 16.04.02: ibmveth: Support to enable LSO/CSO for Trunk VEA

[Andrew Cloke]

** Tags removed: triage-g
** Tags added: triage-a

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

Title:
  Ubuntu 16.04.02: ibmveth: Support to enable LSO/CSO for Trunk VEA

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

Bug description:
  
  == SRU Justification ==
  Commit 66aa0678ef is request to fix four issues with the ibmveth driver.
  The issues are as follows:
  - Issue 1: ibmveth doesn't support largesend and checksum offload features 
when configured as "Trunk".
  - Issue 2: SYN packet drops seen at destination VM. When the packet
  originates, it has CHECKSUM_PARTIAL flag set and as it gets delivered to IO
  server's inbound Trunk ibmveth, on validating "checksum good" bits in ibmveth
  receive routine, SKB's ip_summed field is set with CHECKSUM_UNNECESSARY flag.
  - Issue 3: First packet of a TCP connection will be dropped, if there is
  no OVS flow cached in datapath.
  - Issue 4: ibmveth driver doesn't have support for SKB's with frag_list.

  The details for the fixes to these issues are described in the commits
  git log.



  == Comment: #0 - BRYANT G. LY  - 2017-05-22 08:40:16 ==
  ---Problem Description---

   - Issue 1: ibmveth doesn't support largesend and checksum offload features
     when configured as "Trunk". Driver has explicit checks to prevent
     enabling these offloads.

   - Issue 2: SYN packet drops seen at destination VM. When the packet
     originates, it has CHECKSUM_PARTIAL flag set and as it gets delivered to
     IO server's inbound Trunk ibmveth, on validating "checksum good" bits
     in ibmveth receive routine, SKB's ip_summed field is set with
     CHECKSUM_UNNECESSARY flag. This packet is then bridged by OVS (or Linux
     Bridge) and delivered to outbound Trunk ibmveth. At this point the
     outbound ibmveth transmit routine will not set "no checksum" and
     "checksum good" bits in transmit buffer descriptor, as it does so only
     when the ip_summed field is CHECKSUM_PARTIAL. When this packet gets
     delivered to destination VM, TCP layer receives the packet with checksum
     value of 0 and with no checksum related flags in ip_summed field. This
     leads to packet drops. So, TCP connections never goes through fine.

   - Issue 3: First packet of a TCP connection will be dropped, if there is
     no OVS flow cached in datapath. OVS while trying to identify the flow,
     computes the checksum. The computed checksum will be invalid at the
     receiving end, as ibmveth transmit routine zeroes out the pseudo
     checksum value in the packet. This leads to packet drop.

   - Issue 4: ibmveth driver doesn't have support for SKB's with frag_list.
     When Physical NIC has GRO enabled and when OVS bridges these packets,
     OVS vport send code will end up calling dev_queue_xmit, which in turn
     calls validate_xmit_skb.
     In validate_xmit_skb routine, the larger packets will get segmented into
     MSS sized segments, if SKB has a frag_list and if the driver to which
     they are delivered to doesn't support NETIF_F_FRAGLIST feature.

  Contact Information = Bryant G. Ly/b...@us.ibm.com

  ---uname output---
  4.8.0-51.54

  Machine Type = p8

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   Increases performance greatly

  The patch has been accepted upstream:
  https://patchwork.ozlabs.org/patch/764533/

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

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

[Kernel-packages] [Bug 1707875] Re: [18.04] include support for Python bindings in "perf"

[Andrew Cloke]

** Changed in: ubuntu-power-systems
   Status: In Progress => 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/1707875

Title:
  [18.04] include support for Python bindings in "perf"

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 - Paul A. Clarke  - 2017-07-26 09:59:57 ==
  ---Problem Description---
  Request to build python bindings support with perf.

  ---Steps to Reproduce---
   Ubuntu-17.04# perf script -g python
  Python scripting not supported.  Install libpython and rebuild perf to enable 
it.
  For example:
# apt-get install python-dev (ubuntu)
# yum install python-devel (Fedora)
etc.
   
  Userspace tool common name: perf 
   
  Userspace rpm: linux-tools-common 

  Userspace tool obtained from project website:  na

  == Comment: #2 - MAMATHA INAMDAR  - 2017-08-01 05:02:34 
==
  After installing libpython, downloaded ubuntu 17.04 linux source code and 
compiled perf tool then it works fine.

  # ./perf script  -g python 
  generated Python script: perf-script.py

  but when I run perf tool without rebuilding after installing libpython
  it shows an error

  # perf script  -g python 
  Python scripting not supported.  Install libpython and rebuild perf to enable 
it.
  For example:
# apt-get install python-dev (ubuntu)
# yum install python-devel (Fedora)
etc.
  root@p8wookie:/home/Mamatha/ubuntu/ubuntu-zesty/tools/perf# perf --version
  perf version 4.10.17

  == Comment: #3 - MAMATHA INAMDAR  - 2017-08-01 05:03:44 
==
  Request to build python bindings support with perf.

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

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

[Kernel-packages] [Bug 1738791] Re: linux: -proposed tracker

[Andy Whitcroft]

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

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

Title:
  linux:  -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:
  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-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: 1738792,1738793,1738794,1738796,1738797
  derivatives: 1738798

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

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

[Kernel-packages] [Bug 1725350] Re: KVM on 17.10 crashes the machine

[Andrew Cloke]

** Changed in: ubuntu-power-systems
   Status: Fix Committed => Fix Released

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

Title:
  KVM on 17.10 crashes the machine

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

Bug description:
  When you start qemu on a 17.10 machine, the whole machine goes down
  and crashes:

  [   90.689627] Unable to handle kernel paging request for data at address 
0xf2d3bda0
  [   90.689705] Faulting instruction address: 0xc0361224
  [   90.689840] Oops: Kernel access of bad area, sig: 11 [#1]
  [   90.689911] SMP NR_CPUS=2048 
  [   90.689912] NUMA 
  [   90.690053] PowerNV
  [   90.690092] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat xt_conntrack ipt_REJECT nf_reject_ipv4 
xt_tcpudp bridge stp llc kvm_hv kvm_pr kvm ebtable_filter ebtables 
ip6table_filter ip6_tables iptable_filter openvswitch nf_conntrack_ipv6 
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack_netlink nf_conntrack nfnetlink idt_89hpesx snd_hda_codec_hdmi xfs 
joydev input_leds mac_hid snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep 
snd_pcm snd_timer snd soundcore ofpart opal_prd cmdlinepart powernv_flash mtd 
at24 ipmi_powernv ipmi_devintf ipmi_msghandler powernv_rng uio_pdrv_genirq 
vmx_crypto ibmpowernv uio ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp 
libiscsi_tcp libiscsi scsi_transport_iscsi sunrpc ip_tables x_tables
  [   90.690724]  autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor hid_generic usbhid hid raid6_pq libcrc32c raid1 
raid0 multipath linear uas usb_storage ast crct10dif_vpmsum i2c_algo_bit 
crc32c_vpmsum ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
drm tg3 ahci libahci
  [   90.690937] CPU: 48 PID: 3986 Comm: qemu-system-ppc Not tainted 
4.13.0-12-generic #13-Ubuntu
  [   90.691001] task: c00b122d8700 task.stack: c00b431cc000
  [   90.691167] NIP: c0361224 LR: c0998960 CTR: 
c09a19b0
  [   90.691223] REGS: c00bff61b800 TRAP: 0300   Not tainted  
(4.13.0-12-generic)
  [   90.691277] MSR: 90009033 
  [   90.691282]   CR: 88002844  XER: 
  [   90.691347] CFAR: c099895c DAR: f2d3bda0 DSISR: 4000 
SOFTE: 0 
  [   90.691347] GPR00: c0998960 c00bff61ba80 c15e3000 
c00b4ef61f20 
  [   90.691347] GPR04: c00b44c61680  001f 
001f 
  [   90.691347] GPR08: 001f 02d3bd80 c178e8e8 
c00b5a0c26f0 
  [   90.691347] GPR12: 28002842 cfadf800 c00b52d07880 
c00b44c61680 
  [   90.691347] GPR16:  001f 001f 
c553a560 
  [   90.691347] GPR20: 0001 0002 08000553a560 
c00b5c62a228 
  [   90.691347] GPR24: c5531110 c00b5c632238 0210 
 
  [   90.691347] GPR28: c0998960 c00bff61bc20 c00b4ef61f20 
f2d3bd80 
  [   90.692089] NIP [c0361224] kfree+0x54/0x270
  [   90.692133] LR [c0998960] xhci_urb_free_priv+0x20/0x40
  [   90.692325] Call Trace:
  [   90.692345] [c00bff61ba80] [c00bff61bad0] 0xc00bff61bad0 
(unreliable)
  [   90.692402] [c00bff61bac0] [c0998960] 
xhci_urb_free_priv+0x20/0x40
  [   90.692459] [c00bff61bae0] [c099bfc8] 
xhci_giveback_urb_in_irq.isra.22+0x78/0x190
  [   90.692645] [c00bff61bb40] [c099c350] 
xhci_td_cleanup+0x130/0x200
  [   90.692702] [c00bff61bbc0] [c09a175c] 
handle_tx_event+0x74c/0x1380
  [   90.692759] [c00bff61bcc0] [c09a2894] xhci_irq+0x504/0xf20
  [   90.692808] [c00bff61bde0] [c017b110] 
__handle_irq_event_percpu+0x90/0x300
  [   90.692977] [c00bff61bea0] [c017b3b8] 
handle_irq_event_percpu+0x38/0x90
  [   90.693038] [c00bff61bee0] [c017b474] 
handle_irq_event+0x64/0xb0
  [   90.693094] [c00bff61bf10] [c0180da0] 
handle_fasteoi_irq+0xc0/0x230
  [   90.693155] [c00bff61bf40] [c017972c] 
generic_handle_irq+0x4c/0x70
  [   90.693332] [c00bff61bf60] [c001767c] __do_irq+0x7c/0x1c0
  [   90.693383] [c00bff61bf90] [c002ab70] call_do_irq+0x14/0x24
  [   90.693431] [c00b431cf9d0] [c001785c] do_IRQ+0x9c/0x130
  [   90.693478] [c00b431cfa20] [c0008ac4] 
hardware_interrupt_common+0x114/0x120
  [   90.693663] --- interrupt: 501 at __copy_tofrom_user_power7+0x1f4/0x7cc
  [   90.693663] LR = _copy_to_user+0x3c/0x60
  [   90.693736] [c00b431cfd10] [c00b431cfdc0] 0xc00b431cfdc0 
(unreliable)
  [   90.693797] 

[Kernel-packages] [Bug 1510570] Re: Bluetooth LE pairing fail

[Konrad Zapałowicz]

Testing::

1. using the bluez without the patch

- reboot
- try to pair and connect

2. using bluez with patch

- reboot
- try to pair and connect

In some cases pairing and connecting works better with the patch
applied. There is no negative behavior observed with patch applied
compared to w/o the patch.

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

Title:
  Bluetooth LE pairing fail

Status in OEM Priority Project:
  Confirmed
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Xenial:
  Confirmed

Bug description:
  [Impact]

  When the Bluetooth adapter is not powered on it is not possible to use
  it in normal way. We used to have a hack to force powering on by using
  an udev rule but this doe snot work anymore. Luckily the BlueZ has
  introduced "AutoEnable" option that makes the stack power on adapters by
  itself.

  Backporting this to xenial will improve life of the desktop users and
  will not require them to hack the solution on their own. The fix itself
  uses the well known solution to this problem that is floating around
  there for a while.

  The upload fixes the bug by enabling the 'AutoEnable' option in the
  bluetoothd config file.

  [Original Report]

  . 15.10 we now have bluez 5 so we can pair BLE devices like the
  Microsoft Arc Touch Bluetooth Mouse.

  But this pairing doesn't work very well. Mouse is seen but pairing fail.
  More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5

  This is due to udev rule that use "hcitool" to power on device.
  Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used
  instead of udev rules.

  here is a commit with this parameter:
  http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138

  [Test Case]

  Edit the /etc/bluetooth/main.conf and disable the 'AutoEnable' option.
  Remove file 50-bluetooth-hci-auto-poweron.rules located in
  /lib/udev/rules.d. Now reboot the machine. The BT adapter shall be
  powered off now.

  [Regression Potential]

  Cannot think of any

  [Other Info]

  This fix is included in the development release, see:
  http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions

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

[Kernel-packages] [Bug 1738791] Re: linux: -proposed tracker

[Kleber Sacilotto de Souza]

** 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: 1738792,1738793,1738794,1738796,1738797
+ derivatives: 1738798

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

Title:
  linux:  -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:
  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-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

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: 1738792,1738793,1738794,1738796,1738797
  derivatives: 1738798

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

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

[Kernel-packages] [Bug 1658733] fix for bionic

[bugproxy]

Default Comment by Bridge

** Attachment added: "fix for bionic"
   
https://bugs.launchpad.net/bugs/1658733/+attachment/5024184/+files/makedumpfile_1.6.2-1ubuntu0.1.diff

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

Title:
  Ubuntu 16.04.2KVM:kdump fails to mount root file system when
  noirqdistrib is missing as dump kernel parameter

Status in The Ubuntu-power-systems project:
  Confirmed
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  New
Status in kexec-tools source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in kexec-tools source package in Zesty:
  New
Status in makedumpfile source package in Zesty:
  New
Status in kexec-tools source package in Artful:
  Invalid
Status in makedumpfile source package in Artful:
  Fix Committed
Status in kexec-tools source package in Bionic:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  On Power Systems, some interrupts are missed, and dumping the crash will 
fail. Adding the noirqdistrib kernel parameter to the kdump kernel will fix 
this.

  [Test Case]
  Setting up kdump to target a virtio-scsi device on a Power System.

  [Regression Potential]
  The parameter could be interpreted differently on a different platform and 
kdump would fail. However, it has been verified that no other platform uses 
such parameter. If another parameter would have been incorrectly removed on the 
patch, kdump could fail on other systems.


  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel
  fails to mount the root file system.  This error does not occur in a
  similar guest installed to a single path device.

  Full console output of the kdump failure is attached.  These messages
  from the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.

  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest

  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  >
  > Could you please recreate the guest for further debug?

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  this.)

  == Comment: #22 - Mauro Sergio Martins Rodrigues  - 2017-01-11 09:31:38 ==
  I managed to get kdump to mount rootfs and perform its tasks by setting 
KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see 
http://pastebin.hursley.ibm.com/8239

  I'm still investigating to figure out what is the reason behind this
  behavior.

  Thanks,

  --
  maurosr

  == Comment: #23 - Mauricio Faria De Oliveira  - 2017-01-11 11:56:40 ==
  Mauro,

  (In reply to comment #22)
  > I managed to get kdump to mount rootfs and perform its 

[Kernel-packages] [Bug 1658733] target fix for artful

[bugproxy]

Default Comment by Bridge

** Attachment added: "target fix for artful"
   
https://bugs.launchpad.net/bugs/1658733/+attachment/5024183/+files/makedumpfile_1.6.1-2ubuntu0.1.diff

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

Title:
  Ubuntu 16.04.2KVM:kdump fails to mount root file system when
  noirqdistrib is missing as dump kernel parameter

Status in The Ubuntu-power-systems project:
  Confirmed
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  New
Status in kexec-tools source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in kexec-tools source package in Zesty:
  New
Status in makedumpfile source package in Zesty:
  New
Status in kexec-tools source package in Artful:
  Invalid
Status in makedumpfile source package in Artful:
  Fix Committed
Status in kexec-tools source package in Bionic:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  On Power Systems, some interrupts are missed, and dumping the crash will 
fail. Adding the noirqdistrib kernel parameter to the kdump kernel will fix 
this.

  [Test Case]
  Setting up kdump to target a virtio-scsi device on a Power System.

  [Regression Potential]
  The parameter could be interpreted differently on a different platform and 
kdump would fail. However, it has been verified that no other platform uses 
such parameter. If another parameter would have been incorrectly removed on the 
patch, kdump could fail on other systems.


  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel
  fails to mount the root file system.  This error does not occur in a
  similar guest installed to a single path device.

  Full console output of the kdump failure is attached.  These messages
  from the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.

  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest

  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  >
  > Could you please recreate the guest for further debug?

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  this.)

  == Comment: #22 - Mauro Sergio Martins Rodrigues  - 2017-01-11 09:31:38 ==
  I managed to get kdump to mount rootfs and perform its tasks by setting 
KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see 
http://pastebin.hursley.ibm.com/8239

  I'm still investigating to figure out what is the reason behind this
  behavior.

  Thanks,

  --
  maurosr

  == Comment: #23 - Mauricio Faria De Oliveira  - 2017-01-11 11:56:40 ==
  Mauro,

  (In reply to comment #22)
  > I managed to get kdump to mount rootfs and 

[Kernel-packages] [Bug 1635597] Re: Ubuntu:talclp1: Kdump failed with multipath disk

[Andrew Cloke]

** Tags removed: triage-r
** Tags added: triage-a

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

Title:
  Ubuntu:talclp1: Kdump failed with multipath disk

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  New
Status in makedumpfile source package in Zesty:
  Confirmed

Bug description:
  [Impact]
  When the target device where to dump the kernel is under a multipath 
configuration, dumping will fail, possibly leaving the system stuck in the 
kdump kernel.
  The fix is to include some scsi device handlers needed for the multipath 
setup inside the initramfs image that is used by kdump.
  All modules currently loaded in the system are included.

  [Test Case]
  Setting up kdump to target a multipath device using an appropriate storage 
that requires such scsi_dh modules and triggering a crash will demonstrate that 
kdump fails.
  After the fix, it works fine.

  [Regression Potential]
  If a bug is introduced, loading kdump might fail, and a crash will not be 
generated. A worse regression that might be considered is the system is stuck 
in such a kdump kernel and needs to be rebooted locally (and the crash file is 
not generated either). But since this is what we are trying to fix, we don't 
expect other systems to break. This didn't happen on a small (less than 1GiB of 
RAM) x86 VM, though.

  Problem  Description
  ==
  On talclp1, I enabled kdump. But kdump failed and it drop to BusyBox.

  root@talclp1:~# echo c> /proc/sysrq-trigger
  [  132.643690] sysrq: SysRq : Trigger a crash
  [  132.643739] Unable to handle kernel paging request for data at address 
0x
  [  132.643745] Faulting instruction address: 0xc05c28f4
  [  132.643749] Oops: Kernel access of bad area, sig: 11 [#1]
  [  132.643753] SMP NR_CPUS=2048 NUMA pSeries
  [  132.643758] Modules linked in: fuse ufs qnx4 hfsplus hfs minix ntfs msdos 
jfs rpadlpar_io rpaphp rpcsec_gss_krb5 nfsv4 dccp_diag cifs nfs dns_resolver 
dccp tcp_diag fscache udp_diag inet_diag unix_diag af_packet_diag netlink_diag 
binfmt_misc xfs libcrc32c pseries_rng rng_core ghash_generic gf128mul 
vmx_crypto sg nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables 
autofs4 ext4 crc16 jbd2 fscrypto mbcache crc32c_generic btrfs xor raid6_pq 
dm_round_robin sr_mod sd_mod cdrom ses enclosure scsi_transport_sas ibmveth 
crc32c_vpmsum ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath dm_mod
  [  132.643819] CPU: 49 PID: 10174 Comm: bash Not tainted 4.8.0-15-generic 
#16-Ubuntu
  [  132.643824] task: c00111767080 task.stack: c000d82e
  [  132.643828] NIP: c05c28f4 LR: c05c39d8 CTR: 
c05c28c0
  [  132.643832] REGS: c000d82e3990 TRAP: 0300   Not tainted  
(4.8.0-15-generic)
  [  132.643836] MSR: 80009033   CR: 28242422  
XER: 0001
  [  132.643848] CFAR: c00087d0 DAR:  DSISR: 4200 
SOFTE: 1
  GPR00: c05c39d8 c000d82e3c10 c0f67b00 0063
  GPR04: c0011d04a9b8 c0011d05f7e0 c0047fb0 00015998
  GPR08: 0007 0001  0001
  GPR12: c05c28c0 c7b4b900  2200
  GPR16: 10170dc8 01002b566368 10140f58 100c7570
  GPR20:  1017dd58 10153618 1017b608
  GPR24: 3e87a294 0001 c0ebff60 0004
  GPR28: c0ec0320 0063 c0e72a90 
  [  132.643906] NIP [c05c28f4] sysrq_handle_crash+0x34/0x50
  [  132.643911] LR [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643914] Call Trace:
  [  132.643917] [c000d82e3c10] [c0a245e8] 0xc0a245e8 
(unreliable)
  [  132.643923] [c000d82e3c30] [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643928] [c000d82e3cd0] [c05c4188] 
write_sysrq_trigger+0x78/0xa0
  [  132.643935] [c000d82e3d00] [c03ad770] proc_reg_write+0xb0/0x110
  [  132.643941] [c000d82e3d50] [c030fc3c] __vfs_write+0x6c/0xe0
  [  132.643946] [c000d82e3d90] [c0311144] vfs_write+0xd4/0x240
  [  132.643950] [c000d82e3de0] [c0312e5c] SyS_write+0x6c/0x110
  [  132.643957] [c000d82e3e30] [c00095e0] system_call+0x38/0x108
  [  132.643961] Instruction dump:
  [  132.643963] 38425240 7c0802a6 f8010010 f821ffe1 6000 6000 3d220019 
3949ba60
  [  132.643972] 3921 912a 

[Kernel-packages] [Bug 1714485] Re: Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs.

[Andrew Cloke]

** Tags removed: triage-g
** Tags added: triage-a

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

Title:
  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

Status in The Ubuntu-power-systems project:
  Triaged
Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Zesty:
  New
Status in makedumpfile source package in Artful:
  New
Status in makedumpfile source package in Bionic:
  In Progress

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-08-31 00:33:37 ==
  ---Problem Description---

  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

  ---Steps to Reproduce---

  1. Install Ubuntu 16.04.03 with / as xfs.
  2. Configure kdump.
  3. trigger crash.

  Machine hangs after below log. Attaching console log.

  [  OK  ] Reached target Network is Online.
   Starting Kernel crash dump capture service...
   Starting iSCSI initiator daemon (iscsid)...
  [   12.263089] kdump-tools[1205]: /etc/init.d/kdump-tools: 26: [: -ne: 
unexpected operator
  [  OK  ] Started Kernel crash dump capture service.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).

  
  4. After manual reboot  /etc/default/kdump-tools is empty.

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

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