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

2017-10-22 Thread bugproxy
--- Comment From hasri...@in.ibm.com 2017-10-23 01:21 EDT---
(In reply to comment #66)
> This bug is awaiting verification that the kernel in -proposed solves the
> problem. Please test the kernel and update this bug with the results. If the
> problem is solved, change the tag 'verification-needed-zesty' to
> 'verification-done-zesty'. If the problem still exists, change the tag
> 'verification-needed-zesty' to 'verification-failed-zesty'.
>
> If verification is not done by 5 working days from today, this fix will be
> dropped from the source code, and this bug will be closed.
>

Test has passed with the zesty-proposed.

# ./check tests/generic/285
FSTYP -- xfs (non-debug)
PLATFORM  -- Linux/ppc64le alp10 4.10.0-38-generic
MKFS_OPTIONS  -- -f -bsize=4096 /dev/loop1
MOUNT_OPTIONS -- /dev/loop1 /mnt/scratch

generic/285  0s
Ran: generic/285
Passed all 1 tests

Thanks,
Harish

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

Title:
  xfstest sanity checks on seek operations fails

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

Bug description:
  == Comment: #0 - Harish Sriram 
  Issue:
  --
  xfstest fails with sanity checks on seek operations

  # uname -a
  Linux ltc-tuleta12 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 
12:54:57 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  
  1. Create a loop device with xfs filesystem
  2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd 
xfstests-dev
  3. make
  4. Create a local.config for running with created loop device
  5. Run xfstests-dev test  : ./check tests/generic/285 or ./check 
tests/generic/436

  The test 285 fails with following
  ...
  ...
  07. Test file with unwritten extents, only have dirty pages
  07.01 SEEK_HOLE expected 0 or 45056, got 0.   succ
  07.02 SEEK_HOLE expected 1 or 45056, got 1.   succ
  07.03 SEEK_DATA expected 40960 or 40960, got -1.  FAIL
  07.04 SEEK_DATA expected 40960 or 40960, got -1.  FAIL

  08. Test file with unwritten extents, only have unwritten pages
  08.01 SEEK_HOLE expected 0 or 45056, got 0.   succ
  08.02 SEEK_HOLE expected 1 or 45056, got 1.   succ
  08.03 SEEK_DATA expected 40960 or 40960, got -1.  FAIL
  08.04 SEEK_DATA expected 40960 or 40960, got -1.  FAIL

  The test 436 fails with 
  ...
  ...
  14. Test file with unwritten extents, small hole after pagevec dirty pages
  14.01 SEEK_HOLE expected 917504 or 4194304, got 3670016.  FAIL
  14.02 SEEK_HOLE expected 917504 or 4194304, got 3670016.  FAIL
  14.03 SEEK_HOLE expected 3670016 or 4194304, got 3670016. succ
  14.04 SEEK_DATA expected 0 or 0, got 0.   succ
  14.05 SEEK_DATA expected 1 or 1, got 1.   succ
  14.06 SEEK_DATA expected 2752512 or 2752512, got 2752512. succ

  seek sanity check failed!

  Full log is attached.

  == Comment: #6 - Harish Sriram

  commit 5375023ae1266553a7baa0845e82917d8803f48c
  Author: Jan Kara 
  Date:   Thu May 18 16:36:22 2017 -0700

  xfs: Fix missed holes in SEEK_HOLE implementation
  XFS SEEK_HOLE implementation could miss a hole in an unwritten extent as
  can be seen by the following command:
  
  xfs_io -c "falloc 0 256k" -c "pwrite 0 56k" -c "pwrite 128k 8k"
 -c "seek -h 0" file
  wrote 57344/57344 bytes at offset 0
  56 KiB, 14 ops; 0. sec (49.312 MiB/sec and 12623.9856 ops/sec)
  wrote 8192/8192 bytes at offset 131072
  8 KiB, 2 ops; 0. sec (70.383 MiB/sec and 18018.0180 ops/sec)
  Whence  Result
  HOLE139264
  
  Where we can see that hole at offset 56k was just ignored by SEEK_HOLE
  implementation. The bug is in xfs_find_get_desired_pgoff() which does
  not properly detect the case when pages are not contiguous.
  
  Fix the problem by properly detecting when found page has larger offset
  than expected.
  
  CC: sta...@vger.kernel.org
  Fixes: d126d43f631f996daeee5006714fed914be32368
  Signed-off-by: Jan Kara 
  Reviewed-by: Brian Foster 
  Reviewed-by: Darrick J. Wong 
  Signed-off-by: Darrick J. Wong 

  
  The above commit fixes the generic/436 test, but generic/285 still FAILS.

  The generic/285 failure is reproducible on most P8/P9 systems.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1724911] Re: text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

2017-10-22 Thread Steve Langasek
8162ae5c47977c3f13910b5c1718081d30e8a65a is bad.

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

Title:
  text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

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

Bug description:
  After upgrading my laptop to Ubuntu 17.10, I am unable to access
  gettys on any of the text-mode VTs on my system.

  gdm3 is running on VT1, my user session is running on VT2.  I can
  switch between these.  If I switch to VT3, I know that the VT switch
  has happened in the kernel because the X cursor disappears; but the
  display retains the output of my X session, and the text console with
  getty never appears.

  Switching back to VT2 works fine.

  The same problem occurs with either Wayland or X.

  My laptop is docked with an external monitor, which could be a factor.
  (I also notice that during boot, plymouth is only rendered on the
  internal monitor, not the external monitor; this may be related).  I
  have not yet tested whether this problem is reproducible if I undock.

  The system is booting with vt.handoff=7, which I believe is still the
  default in Ubuntu 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vorlon24080 F pulseaudio
   /dev/snd/controlC0:  vorlon24080 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 09:57:59 2017
  HibernationDevice: RESUME=UUID=6df76279-19ea-45a4-bec9-e4fdc858729a
  InstallationDate: Installed on 2010-09-24 (2582 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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


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

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

apport-collect 1726225

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

Title:
  s390x zKVM failed with selftest-setup and intercept test in kvm-unit-
  tests

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Steps:
  1. git clone https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  2. cd kvm-unit-tests
  3. ./configure; make
  4. sudo ./run_tests.sh -v

  And you will see the detailed command it use, run the one for selftest-setup 
as root:
  # TESTNAME=selftest-setup TIMEOUT=90s ACCEL= ./s390x/run s390x/selftest.elf 
-smp 1 -append 'test 123'
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-s390x -nodefaults 
-nographic -machine s390-ccw-virtio,accel=tcg -chardev stdio,id=con0 -device 
sclpconsole,chardev=con0 -kernel s390x/selftest.elf -smp 1 -append test 123 # 
-initrd /tmp/tmp.gj7cBJS2hH
  PASS: selftest: true
  PASS: selftest: argc == 3
  PASS: selftest: argv[0] == PROGNAME
  PASS: selftest: argv[1] == test
  PASS: selftest: argv[2] == 123
  PASS: selftest: 3.0/2.0 == 1.5
  PASS: selftest: Program interrupt: expected(1) == received(1)
  ABORT: selftest: Unexpected program interrupt: 5 at 0x12b94, ilen 6

  SUMMARY: 7 tests

  EXIT: STATUS=127

  Run the one for intercept as root:
  # TESTNAME=intercept TIMEOUT=90s ACCEL= ./s390x/run s390x/intercept.elf -smp 1
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-s390x -nodefaults 
-nographic -machine s390-ccw-virtio,accel=tcg -chardev stdio,id=con0 -device 
sclpconsole,chardev=con0 -kernel s390x/intercept.elf -smp 1 # -initrd 
/tmp/tmp.4QCRdccGRJ
  PASS: intercept: stpx: store prefix
  FAIL: intercept: stpx: Program interrupt: expected(4) == received(0)
  FAIL: intercept: stpx: Program interrupt: expected(6) == received(0)
  ABORT: intercept: stpx: Unexpected program interrupt: 5 at 0x109dc, ilen 4

  SUMMARY: 3 tests, 2 unexpected failures

  EXIT: STATUS=127

  Tried QEMU 2.10 built from source, this issue still exist.

  This is not a regression as we just add the test for s390x in this
  cycle.

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

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


[Kernel-packages] [Bug 1722330] Re: linux: 4.10.0-38.42 -proposed tracker

2017-10-22 Thread Po-Hsu Lin
** Tags added: regression-testing-passed

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

Title:
  linux: 4.10.0-38.42 -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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Zesty:
  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: 1722331,1722333
  derivatives: 1722334
  -- 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/1722330/+subscriptions

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


[Kernel-packages] [Bug 1726225] Re: s390x zKVM failed with selftest-setup and intercept test in kvm-unit-tests

2017-10-22 Thread Po-Hsu Lin
Note that these two tests have passed on s390x zVM, with QEMU 2.8.0

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

Title:
  s390x zKVM failed with selftest-setup and intercept test in kvm-unit-
  tests

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Steps:
  1. git clone https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  2. cd kvm-unit-tests
  3. ./configure; make
  4. sudo ./run_tests.sh -v

  And you will see the detailed command it use, run the one for selftest-setup 
as root:
  # TESTNAME=selftest-setup TIMEOUT=90s ACCEL= ./s390x/run s390x/selftest.elf 
-smp 1 -append 'test 123'
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-s390x -nodefaults 
-nographic -machine s390-ccw-virtio,accel=tcg -chardev stdio,id=con0 -device 
sclpconsole,chardev=con0 -kernel s390x/selftest.elf -smp 1 -append test 123 # 
-initrd /tmp/tmp.gj7cBJS2hH
  PASS: selftest: true
  PASS: selftest: argc == 3
  PASS: selftest: argv[0] == PROGNAME
  PASS: selftest: argv[1] == test
  PASS: selftest: argv[2] == 123
  PASS: selftest: 3.0/2.0 == 1.5
  PASS: selftest: Program interrupt: expected(1) == received(1)
  ABORT: selftest: Unexpected program interrupt: 5 at 0x12b94, ilen 6

  SUMMARY: 7 tests

  EXIT: STATUS=127

  Run the one for intercept as root:
  # TESTNAME=intercept TIMEOUT=90s ACCEL= ./s390x/run s390x/intercept.elf -smp 1
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-s390x -nodefaults 
-nographic -machine s390-ccw-virtio,accel=tcg -chardev stdio,id=con0 -device 
sclpconsole,chardev=con0 -kernel s390x/intercept.elf -smp 1 # -initrd 
/tmp/tmp.4QCRdccGRJ
  PASS: intercept: stpx: store prefix
  FAIL: intercept: stpx: Program interrupt: expected(4) == received(0)
  FAIL: intercept: stpx: Program interrupt: expected(6) == received(0)
  ABORT: intercept: stpx: Unexpected program interrupt: 5 at 0x109dc, ilen 4

  SUMMARY: 3 tests, 2 unexpected failures

  EXIT: STATUS=127

  Tried QEMU 2.10 built from source, this issue still exist.

  This is not a regression as we just add the test for s390x in this
  cycle.

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

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


[Kernel-packages] [Bug 1722330] Re: linux: 4.10.0-38.42 -proposed tracker

2017-10-22 Thread Po-Hsu Lin
4.10.0-38.42 - generic
Regression test CMPL.

Issue to note in amd64:
  hwclock - failed on lodygin only, bug 1714229
  monotonic_time - tsc failed on lodygin
  ubuntu_kvm_unit_tests - 29 failed on rizzo, 22 failed on hainzel, 61 failed 
on lodygin
  ubuntu_lxc - gpg key issue on amaura, passed after retest
  xfstests - btrfs/130 hang, bug 1718925

Issue to note in arm64:
  rtc - Update IRQs not supported on node wright
  ubuntu_bpf - failed to build, bug 1675395
  ubuntu_kernel_selftests - breakpoint test failed to build, bug 1680507
  ubuntu_kvm_unit_tests - all 11 tests passed after re-test
  ubuntu_zfs_xfs_generic - test 079, 317 failed

Issue to note in i386:
  monotonic_time - gtod failed on fozzie
  ubuntu_bpf - test_maps bpf test crashed, bug 1711512

Issue to note in ppc64le:
  libhugetlbfs - 5 failed, 6 killed by signal (small_const / small_data is not 
hugepage)
  rtc - Update IRQs not supported.
  ubuntu_kvm_unit_tests - sprs failed, bug 1712803
  xfstests - btrfs/130 hang, bug 1718925

Issue to note in s390x (zKVM):
  aio_dio_bugs - event res -22, not regression
  libhugetlbfs - 10 failed, 7 killed by signal, 1 bad config
  scrashme - failed to build bug 1689240
  ubuntu_bpf - failed to build, bug 1711299
  ubuntu_ecryptfs - miscdev-bad-count.sh.xfs ~ namelen.sh failed (28 failed)
  ubuntu_kvm_unit_tests - selftest-setup and intercept failed, bug 1726225

Issue to note in s390x (zVM):
  aio_dio_bugs - event res -22, not regression
  libhugetlbfs - IOError: [Errno 95] Operation not supported
  scrashme - failed to build bug 1689240
  ubuntu_bpf - failed to build, bug 1711299
  ubuntu_ecryptfs - miscdev-bad-count.sh.xfs ~ namelen.sh failed (28 failed)
  ubuntu_kvm_unit_tests - all 2 tests passed after retest

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

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

Title:
  linux: 4.10.0-38.42 -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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Zesty:
  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: 1722331,1722333
  derivatives: 1722334
  -- 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/1722330/+subscriptions

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


[Kernel-packages] [Bug 1724657] Re: Boot freeze with Ubuntu 17.10-beta2 on Surface Book

2017-10-22 Thread Kai-Heng Feng
Is it a regression in v4.13? Does v4.12 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/1724657

Title:
  Boot freeze with Ubuntu 17.10-beta2 on Surface Book

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When trying to boot 17.10-beta2 from USB key on a Surface Book the
  system freezes immediately after "boot" in grub. Not even a
  uncompressing message. Something similar happens even with Fedora 27:
  https://bugzilla.redhat.com/show_bug.cgi?id=1500057

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: evince 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  Date: Wed Oct 18 20:42:20 2017
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1726225] [NEW] s390x zKVM failed with selftest-setup and intercept test in kvm-unit-tests

2017-10-22 Thread Po-Hsu Lin
Public bug reported:

Steps:
1. git clone https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
2. cd kvm-unit-tests
3. ./configure; make
4. sudo ./run_tests.sh -v

And you will see the detailed command it use, run the one for selftest-setup as 
root:
# TESTNAME=selftest-setup TIMEOUT=90s ACCEL= ./s390x/run s390x/selftest.elf 
-smp 1 -append 'test 123'
timeout -k 1s --foreground 90s /usr/bin/qemu-system-s390x -nodefaults 
-nographic -machine s390-ccw-virtio,accel=tcg -chardev stdio,id=con0 -device 
sclpconsole,chardev=con0 -kernel s390x/selftest.elf -smp 1 -append test 123 # 
-initrd /tmp/tmp.gj7cBJS2hH
PASS: selftest: true
PASS: selftest: argc == 3
PASS: selftest: argv[0] == PROGNAME
PASS: selftest: argv[1] == test
PASS: selftest: argv[2] == 123
PASS: selftest: 3.0/2.0 == 1.5
PASS: selftest: Program interrupt: expected(1) == received(1)
ABORT: selftest: Unexpected program interrupt: 5 at 0x12b94, ilen 6

SUMMARY: 7 tests

EXIT: STATUS=127

Run the one for intercept as root:
# TESTNAME=intercept TIMEOUT=90s ACCEL= ./s390x/run s390x/intercept.elf -smp 1
timeout -k 1s --foreground 90s /usr/bin/qemu-system-s390x -nodefaults 
-nographic -machine s390-ccw-virtio,accel=tcg -chardev stdio,id=con0 -device 
sclpconsole,chardev=con0 -kernel s390x/intercept.elf -smp 1 # -initrd 
/tmp/tmp.4QCRdccGRJ
PASS: intercept: stpx: store prefix
FAIL: intercept: stpx: Program interrupt: expected(4) == received(0)
FAIL: intercept: stpx: Program interrupt: expected(6) == received(0)
ABORT: intercept: stpx: Unexpected program interrupt: 5 at 0x109dc, ilen 4

SUMMARY: 3 tests, 2 unexpected failures

EXIT: STATUS=127

Tried QEMU 2.10 built from source, this issue still exist.

This is not a regression as we just add the test for s390x in this
cycle.

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


** Tags: s390x zesty

** Package changed: qemu (Ubuntu) => linux (Ubuntu)

** Description changed:

  Steps:
  1. git clone https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  2. cd kvm-unit-tests
  3. ./configure; make
  4. sudo ./run_tests.sh -v
  
  And you will see the detailed command it use, run the one for selftest-setup 
as root:
  # TESTNAME=selftest-setup TIMEOUT=90s ACCEL= ./s390x/run s390x/selftest.elf 
-smp 1 -append 'test 123'
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-s390x -nodefaults 
-nographic -machine s390-ccw-virtio,accel=tcg -chardev stdio,id=con0 -device 
sclpconsole,chardev=con0 -kernel s390x/selftest.elf -smp 1 -append test 123 # 
-initrd /tmp/tmp.gj7cBJS2hH
  PASS: selftest: true
  PASS: selftest: argc == 3
  PASS: selftest: argv[0] == PROGNAME
  PASS: selftest: argv[1] == test
  PASS: selftest: argv[2] == 123
  PASS: selftest: 3.0/2.0 == 1.5
  PASS: selftest: Program interrupt: expected(1) == received(1)
  ABORT: selftest: Unexpected program interrupt: 5 at 0x12b94, ilen 6
  
  SUMMARY: 7 tests
  
  EXIT: STATUS=127
  
  Run the one for intercept as root:
  # TESTNAME=intercept TIMEOUT=90s ACCEL= ./s390x/run s390x/intercept.elf -smp 1
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-s390x -nodefaults 
-nographic -machine s390-ccw-virtio,accel=tcg -chardev stdio,id=con0 -device 
sclpconsole,chardev=con0 -kernel s390x/intercept.elf -smp 1 # -initrd 
/tmp/tmp.4QCRdccGRJ
  PASS: intercept: stpx: store prefix
  FAIL: intercept: stpx: Program interrupt: expected(4) == received(0)
  FAIL: intercept: stpx: Program interrupt: expected(6) == received(0)
  ABORT: intercept: stpx: Unexpected program interrupt: 5 at 0x109dc, ilen 4
  
  SUMMARY: 3 tests, 2 unexpected failures
  
  EXIT: STATUS=127
  
+ Tried QEMU 2.10 built from source, this issue still exist.
  
- Tried QEMU 2.10 built from source, this issue still exist.
+ This is not a regression as we just add the test for s390x in this
+ cycle.

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

Title:
  s390x zKVM failed with selftest-setup and intercept test in kvm-unit-
  tests

Status in linux package in Ubuntu:
  New

Bug description:
  Steps:
  1. git clone https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  2. cd kvm-unit-tests
  3. ./configure; make
  4. sudo ./run_tests.sh -v

  And you will see the detailed command it use, run the one for selftest-setup 
as root:
  # TESTNAME=selftest-setup TIMEOUT=90s ACCEL= ./s390x/run s390x/selftest.elf 
-smp 1 -append 'test 123'
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-s390x -nodefaults 
-nographic -machine s390-ccw-virtio,accel=tcg -chardev stdio,id=con0 -device 
sclpconsole,chardev=con0 -kernel s390x/selftest.elf -smp 1 -append test 123 # 
-initrd /tmp/tmp.gj7cBJS2hH
  PASS: selftest: true
  PASS: selftest: argc == 3
  PASS: selftest: argv[0] == PROGNAME
  PASS: selftest: argv[1] == test
  PASS: selftest: argv[2] == 123
  PASS: selftest: 3.0/2.0 == 1.5
  PASS: selftest: Program interrupt: expected(1) == received(1)
  ABORT: 

[Kernel-packages] [Bug 1726225] [NEW] s390x zKVM failed with selftest-setup and intercept test in kvm-unit-tests

2017-10-22 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Steps:
1. git clone https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
2. cd kvm-unit-tests
3. ./configure; make
4. sudo ./run_tests.sh -v

And you will see the detailed command it use, run the one for selftest-setup as 
root:
# TESTNAME=selftest-setup TIMEOUT=90s ACCEL= ./s390x/run s390x/selftest.elf 
-smp 1 -append 'test 123'
timeout -k 1s --foreground 90s /usr/bin/qemu-system-s390x -nodefaults 
-nographic -machine s390-ccw-virtio,accel=tcg -chardev stdio,id=con0 -device 
sclpconsole,chardev=con0 -kernel s390x/selftest.elf -smp 1 -append test 123 # 
-initrd /tmp/tmp.gj7cBJS2hH
PASS: selftest: true
PASS: selftest: argc == 3
PASS: selftest: argv[0] == PROGNAME
PASS: selftest: argv[1] == test
PASS: selftest: argv[2] == 123
PASS: selftest: 3.0/2.0 == 1.5
PASS: selftest: Program interrupt: expected(1) == received(1)
ABORT: selftest: Unexpected program interrupt: 5 at 0x12b94, ilen 6

SUMMARY: 7 tests

EXIT: STATUS=127

Run the one for intercept as root:
# TESTNAME=intercept TIMEOUT=90s ACCEL= ./s390x/run s390x/intercept.elf -smp 1
timeout -k 1s --foreground 90s /usr/bin/qemu-system-s390x -nodefaults 
-nographic -machine s390-ccw-virtio,accel=tcg -chardev stdio,id=con0 -device 
sclpconsole,chardev=con0 -kernel s390x/intercept.elf -smp 1 # -initrd 
/tmp/tmp.4QCRdccGRJ
PASS: intercept: stpx: store prefix
FAIL: intercept: stpx: Program interrupt: expected(4) == received(0)
FAIL: intercept: stpx: Program interrupt: expected(6) == received(0)
ABORT: intercept: stpx: Unexpected program interrupt: 5 at 0x109dc, ilen 4

SUMMARY: 3 tests, 2 unexpected failures

EXIT: STATUS=127


Tried QEMU 2.10 built from source, this issue still exist.

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


** Tags: s390x zesty
-- 
s390x zKVM failed with selftest-setup and intercept test in kvm-unit-tests
https://bugs.launchpad.net/bugs/1726225
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1572698] Re: [patch included]Slow speed and dropped connections with Realtek RTL8192CU-based wifi

2017-10-22 Thread Kai-Heng Feng
Unfortunately "all the necessary information" needs to be merged into
rtl8xxxu driver. Please file an upstream bug or ask maintainers on
mailing list.

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

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

Title:
  [patch included]Slow speed and dropped connections with Realtek
  RTL8192CU-based wifi

Status in linux package in Ubuntu:
  Triaged

Bug description:
  EDIT(other user): Some one fixed it in github, still works in at least in 
linux 4.4-4.11
  https://github.com/pvaret/rtl8192cu-fixes
  EDIT:

  I am using a D-Link DWA-131 USB wlan adapter to connect to my private wlan.
  The adapter works fine under Windows and I have no problems connecting to my 
wlan with other devices (e.g. my laptop running Linux Mint).
  However, the adapter, which is based on the Realtek rtl8192cu chipset, won't 
work correctly on any current Ubuntu machine (in my case Kubuntu 15.10 64bit):

  As also showcased by a myriad of other bug reports (most of which have 
expired by now), wlan-adapters based on the Realtek rtl8192cu chipset exhibit 
very slow connection speeds and frequently dropped connections with current 
Linux kernels.
  I have noticed this originally in Linux Mint 17 running kernel 3.19.x, in 
Kubuntu 15.10 up to 4.2.0.35 and can confirm that it is still present in a live 
session of Xenial Xerus (16.04).
  I have tried commonly mentioned "fixes" such as deactivating hardware 
encryption without success.

  The drivers available on the Realtek homepage are apparently intended
  for older kernels and won't install.

  There is, however, a fixed driver available via github 
(https://github.com/pvaret/rtl8192cu-fixes).
  I have followed the instructions found there and finally my wlan-adapter is 
working correctly.
  Apparently the issues caused by the broken driver in the linux kernels might 
be connected to power management.

  I am posting this bug here in the hope that some developer finally manages to 
incorporate the (obviously available) fixes found in the github-drivers into 
the drivers already included in the kernel.
  ---
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  patrick2300 F pulseaudio
   /dev/snd/controlC1:  patrick2300 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=28c49a78-8b93-495e-bc1b-22c87db4734c
  InstallationDate: Installed on 2015-10-22 (181 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Gigabyte Technology Co., Ltd. GA-870A-UD3
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic 
root=UUID=1016b861-fa27-4990-bac9-58a3ab27ff5b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  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.2.0-35-generic N/A
   linux-backports-modules-4.2.0-35-generic  N/A
   linux-firmware1.149.3
  RfKill:

  Tags:  wily
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  Uname: Linux 4.2.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 08/01/2011
  dmi.bios.vendor: AwardAward (授与する, じゅよする, juyosuru) Software International, 
Inc.
  dmi.bios.version: F5
  dmi.board.name: GA-870A-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd08/01/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-870A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-870A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-870A-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Kernel-packages] [Bug 1697450] Re: Gnome Shell hangs at startup

2017-10-22 Thread Daniel van Vugt
OK, we're going to need to analyse the hung gnome-shell process. Please
try to do this:

1. Install openssh-server:
   sudo apt install openssh-server
2. Using a second machine, log into the offending machine via SSH:
   ssh @ 
   where  is your username, and  is either hostname or the 
machine's IP address.
3. Reproduce the hang.
4. From your ssh login, run:
   killall -TRAP -u $USER gnome-shell
5. Look in /var/crash for a newly created file, something like 
'_usr_bin_gnome-shell.1000.crash'
6. Upload the crash file using this command or similar:
   ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash
7. Tell use the new bug ID that was created.


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

Title:
  Gnome Shell hangs at startup

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm trying to install from the daily Artful desktop image (20170612).

  After boot, the gnome session hangs at startup, while the "zoom"
  animation is being shown.

  I have an intel card:

  
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller])
  Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core 
processor Graphics Controller
  Flags: bus master, fast devsel, latency 0, IRQ 29
  Memory at f780 (64-bit, non-prefetchable) [size=4M]
  Memory at e000 (64-bit, prefetchable) [size=256M]
  I/O ports at f000 [size=64]
  [virtual] Expansion ROM at 000c [disabled] [size=128K]
  Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
  Capabilities: [d0] Power Management version 2
  Capabilities: [a4] PCI Advanced Features
  Kernel driver in use: i915
  Kernel modules: i915

  
  I'm not sure how to debug this further, but I had similar issues with the 
installer from Zesty as well (see 
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1681846)
  With Artful, at least it gets past the splash screen but then it hangs.

  Note that the system is currently running Yakkety with no issue.
  --- 
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-07-30 (71 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170730)
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Tags:  artful wayland-session
  Uname: Linux 4.8.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1724657] Re: Boot freeze with Ubuntu 17.10-beta2 on Surface Book

2017-10-22 Thread Benjamin Braun
To clarify: It still affects Arch Linux but the use of Launchpad to
report arch-linux-linux bugs is not supported.

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

Title:
  Boot freeze with Ubuntu 17.10-beta2 on Surface Book

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When trying to boot 17.10-beta2 from USB key on a Surface Book the
  system freezes immediately after "boot" in grub. Not even a
  uncompressing message. Something similar happens even with Fedora 27:
  https://bugzilla.redhat.com/show_bug.cgi?id=1500057

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: evince 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  Date: Wed Oct 18 20:42:20 2017
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2017-10-22 Thread Po-Hsu Lin
** 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/1723914

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

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  New

Bug description:
  Similar to bug 1723904, bug 1712803.
  The failed "emulator" test from kvm-unit-test will pass with qemu-2.7.1 built 
from source.

  ubuntu@modoc:~/kvm-unit-tests$ sudo /bin/bash -c "TESTNAME=emulator 
TIMEOUT=90s ACCEL= ./powerpc/run powerpc/emulator.elf -smp 1
  > "
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-ppc64 -nodefaults 
-machine pseries,accel=kvm -bios powerpc/boot_rom.bin -display none -serial 
stdio -kernel powerpc/emulator.elf -smp 1 # -initrd /tmp/tmp.BJ2sE7V2Jc
  FAIL: emulator: 64bit: detected
  PASS: emulator: invalid: exception
  PASS: emulator: lswx: alignment
  PASS: emulator: lswi: alignment
  SUMMARY: 4 tests, 1 unexpected failures

  EXIT: STATUS=3

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-37-generic 4.10.0-37.41~16.04.1
  ProcVersionSignature: User Name 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic ppc64le
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: ppc64el
  Date: Mon Oct 16 10:10:46 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcLoadAvg: 0.00 0.00 0.57 1/1457 83356
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 1604 00:14:19651 0 EOF
   2: POSIX  ADVISORY  WRITE 2937 00:14:55331 0 EOF
   3: FLOCK  ADVISORY  WRITE 3046 00:14:67623 0 EOF
   4: POSIX  ADVISORY  WRITE 3124 00:14:57398 0 EOF
   5: POSIX  ADVISORY  WRITE 3047 00:14:87068 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.10.0-37-generic (buildd@bos01-ppc64el-026) (gcc 
version 5.4.0 20160609 (User Name/IBM 5.4.0-6ubuntu1~16.04.4) ) 
#41~16.04.1-User Name SMP Fri Oct 6 22:44:24 UTC 2017
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_smt: SMT is off

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

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


[Kernel-packages] [Bug 1724657] Re: Boot freeze with Ubuntu 17.10-beta2 on Surface Book

2017-10-22 Thread Benjamin Braun
** Also affects: linux (Arch Linux)
   Importance: Undecided
   Status: New

** No longer affects: linux (Arch Linux)

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

Title:
  Boot freeze with Ubuntu 17.10-beta2 on Surface Book

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When trying to boot 17.10-beta2 from USB key on a Surface Book the
  system freezes immediately after "boot" in grub. Not even a
  uncompressing message. Something similar happens even with Fedora 27:
  https://bugzilla.redhat.com/show_bug.cgi?id=1500057

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: evince 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  Date: Wed Oct 18 20:42:20 2017
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1711936] Re: Severe graphical corruption in gnome-shell with nouveau [Nvidia GeForce 8400M GS]

2017-10-22 Thread Daniel van Vugt
Thanks Alex. Please update the bug description to cover what you see in
the 17.10 release.

** Changed in: gnome-shell (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/1711936

Title:
  Severe graphical corruption in gnome-shell with nouveau [Nvidia
  GeForce 8400M GS]

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When running gnome-shell on Ubuntu 17.10, text is visible only as white 
blocks (or sometimes not visible at all), and some graphics, such as the icons 
on the launcher menu, are corrupt. Only objects drawn by the gnome-shell and 
related programs seem to be affected. Software which is not part of the 
gnome-shell, such as LibreOffice, calculator, terminal, etc displays without 
corruption.
  --- 
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  GsettingsChanges: org.gnome.desktop.interface gtk-im-module 
'gtk-im-context-simple'
  InstallationDate: Installed on 2017-08-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170818)
  Package: linux
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Tags:  artful wayland-session
  Uname: Linux 4.12.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1711936/+subscriptions

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


[Kernel-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]

2017-10-22 Thread Daniel van Vugt
> FYI this problem sits high on the Pulseaudio bug list, but...

For Ubuntu users yes this is the "hottest" bug in the pulseaudio
package:

https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bugs?orderby=-heat=0

However, upstream have been mostly silent on this bug since January
2015:

https://bugs.freedesktop.org/show_bug.cgi?id=88827

Any solution here will likely come from upstream so if you continue to
experience this bug in Ubuntu 17.10 (and soon 18.04) please comment on
the above link.

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

Title:
  A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in
  audio stream"]

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped
  working properly. It was working fine in Jaunty.

  My headphones are detected and configured by pulse, but the audio
  skips as if it's spending half of each second paused. Music is
  buffered so that after I click stop on rhythmbox (or whatever--it
  happens with whatever player I use) the audio continues until it's
  caught up.

  syslog is full of the following lines:
  Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal 
latency to 1.00 ms
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
15128 us (= 2668 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36586 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
35593 us (= 6276 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36597 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32601 us (= 5748 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32589 us (= 5748 bytes) in audio stream

  This is with
  bluez 4.45-0ubuntu4
  pulseaudio1:0.9.15-4ubuntu2 0

  pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev
  didn't help.

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

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


[Kernel-packages] [Bug 1724911] Re: text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

2017-10-22 Thread Steve Langasek
f1f537c2e7f565a808623d3244ea73a65839240e is bad (idem.)

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

Title:
  text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

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

Bug description:
  After upgrading my laptop to Ubuntu 17.10, I am unable to access
  gettys on any of the text-mode VTs on my system.

  gdm3 is running on VT1, my user session is running on VT2.  I can
  switch between these.  If I switch to VT3, I know that the VT switch
  has happened in the kernel because the X cursor disappears; but the
  display retains the output of my X session, and the text console with
  getty never appears.

  Switching back to VT2 works fine.

  The same problem occurs with either Wayland or X.

  My laptop is docked with an external monitor, which could be a factor.
  (I also notice that during boot, plymouth is only rendered on the
  internal monitor, not the external monitor; this may be related).  I
  have not yet tested whether this problem is reproducible if I undock.

  The system is booting with vt.handoff=7, which I believe is still the
  default in Ubuntu 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vorlon24080 F pulseaudio
   /dev/snd/controlC0:  vorlon24080 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 09:57:59 2017
  HibernationDevice: RESUME=UUID=6df76279-19ea-45a4-bec9-e4fdc858729a
  InstallationDate: Installed on 2010-09-24 (2582 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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


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

2017-10-22 Thread Aun
I am unable to get useful debug info from the kernel for a bug report.
It hangs at a black screen and will not respond to any of the magic
sysreq commands.  I tried the intel drm-tip too and same result.  Fully
hung, can't ssh in, no console, nothing, completely wedged.  Don't want
to send bug report without details.

I'm building some tags between working and not working and will try a
bisect after I narrow it down.  linus v4.10 tag build works fine.

Any suggestions?

-- 
You 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 1725154] Re: mwifiex cannot connect to wifi AP when keeping wireless connection idle for more than 60 seconds

2017-10-22 Thread Anthony Wong
** 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/1725154

Title:
  mwifiex cannot connect to wifi AP when keeping wireless connection
  idle for more than 60 seconds

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

Bug description:
  Issue happens every time we get connected to any WPA network and stay
  idle for more than 60 seconds.

  We are working with upstream for a real fix:
  https://www.spinics.net/lists/linux-wireless/msg167017.html, please
  don't triage.

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

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


[Kernel-packages] [Bug 1724911] Re: text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

2017-10-22 Thread Steve Langasek
1a3b85ea36d38d5732fdd86b321b10bcaeb53512 is bad (idem.)

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

Title:
  text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

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

Bug description:
  After upgrading my laptop to Ubuntu 17.10, I am unable to access
  gettys on any of the text-mode VTs on my system.

  gdm3 is running on VT1, my user session is running on VT2.  I can
  switch between these.  If I switch to VT3, I know that the VT switch
  has happened in the kernel because the X cursor disappears; but the
  display retains the output of my X session, and the text console with
  getty never appears.

  Switching back to VT2 works fine.

  The same problem occurs with either Wayland or X.

  My laptop is docked with an external monitor, which could be a factor.
  (I also notice that during boot, plymouth is only rendered on the
  internal monitor, not the external monitor; this may be related).  I
  have not yet tested whether this problem is reproducible if I undock.

  The system is booting with vt.handoff=7, which I believe is still the
  default in Ubuntu 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vorlon24080 F pulseaudio
   /dev/snd/controlC0:  vorlon24080 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 09:57:59 2017
  HibernationDevice: RESUME=UUID=6df76279-19ea-45a4-bec9-e4fdc858729a
  InstallationDate: Installed on 2010-09-24 (2582 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1726159] Re: PCIe BUS Error causing really slow laptop performance

2017-10-22 Thread George Mathioudakis
** Description changed:

- I recently bought the following laptop: 
+ I recently bought the following laptop:
  Asus VivoBook X542UQ-DM148T - 15.6" (i7-7500U/8GB/256GB/GT 940MX 2GB)
  
  It came pre-installed with Win10 and I did a fresh install of Ubuntu
  16.04 LTS. The screen was flickering for some reason and installing
  Ubuntu 17.04 fixed the issue.
  
  The real problem is that when I'm booting the laptop, the following
  error is being shown on my screen:
  
  [   12.866073] pcieport :00:1c.5: can't find device of ID00e5
  [   12.898481] pcieport :00:1c.5: AER: Multiple Corrected error received: 
id=00e5
  [   12.898488] pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e5(Receiver ID)
  [   12.898491] pcieport :00:1c.5:   device [8086:9d15] error 
status/mask=2041/2000
  [   12.898492] pcieport :00:1c.5:[ 0] Receiver Error (First)
  [   12.898493] pcieport :00:1c.5:[ 6] Bad TLP
  
  I know that this error can be hid with one of the following kernel boot 
arguments:
  pci=nomsi / pci=noaer / pcie_aspm=off / pci=nommconf.
  
  The weird thing is that the above output is only being shown when the
  laptop is on AC Power (charging). When the laptop is not connected to AC
  (battery-mode), it has performance issues (slow boot and slow
  application launching). I was trying all day long to fix the problem. I
  removed everything that had to do with power-saving, reinstalled, re-
- tweaked for performance but had no luck. While diagnosing, I had the
- idea to benchmark the "M2 SATA-3 SSD" that my laptop had. The results
- are:
+ tweaked for performance, tried different kernels but had no luck. While
+ diagnosing, I had the idea to benchmark the "M2 SATA-3 SSD" that my
+ laptop had. The results are:
  
  * On AC Power: 522MB/s (READ) | 416MB/s (WRITE)
  * On Battery Power: 32MB/s (READ) | 31MB/s (WRITE)
  
  This explains everyting. That's why I'm having a slow boot and slow
  application launching!
  
  Commands "lspci" and "dmesg" say that the error comes from the following 
device:
  00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#6 (rev f1)
  
  I will attach lspci and dmesg output on a tar.gz file.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-37-generic 4.10.0-37.41
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  georgem2557 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  georgem2557 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Sun Oct 22 23:17:57 2017
  InstallationDate: Installed on 2017-10-20 (2 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 004: ID 13d3:3496 IMC Networks 
-  Bus 001 Device 003: ID 13d3:5a01 IMC Networks 
-  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 13d3:3496 IMC Networks
+  Bus 001 Device 003: ID 13d3:5a01 IMC Networks
+  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: ASUSTeK COMPUTER INC. X542UQ
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic.efi.signed 
root=UUID=38d32efc-d0cb-4a82-9e6c-e6a3bd62e51d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-4.10.0-37-generic N/A
-  linux-backports-modules-4.10.0-37-generic  N/A
-  linux-firmware 1.164.1
+  linux-restricted-modules-4.10.0-37-generic N/A
+  linux-backports-modules-4.10.0-37-generic  N/A
+  linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X542UQ.202
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X542UQ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX542UQ.202:bd05/18/2017:svnASUSTeKCOMPUTERINC.:pnX542UQ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX542UQ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X542UQ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

Title:
  PCIe 

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

2017-10-22 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  PCIe BUS Error causing really slow laptop performance

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently bought the following laptop: 
  Asus VivoBook X542UQ-DM148T - 15.6" (i7-7500U/8GB/256GB/GT 940MX 2GB)

  It came pre-installed with Win10 and I did a fresh install of Ubuntu
  16.04 LTS. The screen was flickering for some reason and installing
  Ubuntu 17.04 fixed the issue.

  The real problem is that when I'm booting the laptop, the following
  error is being shown on my screen:

  [   12.866073] pcieport :00:1c.5: can't find device of ID00e5
  [   12.898481] pcieport :00:1c.5: AER: Multiple Corrected error received: 
id=00e5
  [   12.898488] pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e5(Receiver ID)
  [   12.898491] pcieport :00:1c.5:   device [8086:9d15] error 
status/mask=2041/2000
  [   12.898492] pcieport :00:1c.5:[ 0] Receiver Error (First)
  [   12.898493] pcieport :00:1c.5:[ 6] Bad TLP

  I know that this error can be hid with one of the following kernel boot 
arguments:
  pci=nomsi / pci=noaer / pcie_aspm=off / pci=nommconf.

  The weird thing is that the above output is only being shown when the
  laptop is on AC Power (charging). When the laptop is not connected to
  AC (battery-mode), it has performance issues (slow boot and slow
  application launching). I was trying all day long to fix the problem.
  I removed everything that had to do with power-saving, reinstalled,
  re-tweaked for performance but had no luck. While diagnosing, I had
  the idea to benchmark the "M2 SATA-3 SSD" that my laptop had. The
  results are:

  * On AC Power: 522MB/s (READ) | 416MB/s (WRITE)
  * On Battery Power: 32MB/s (READ) | 31MB/s (WRITE)

  This explains everyting. That's why I'm having a slow boot and slow
  application launching!

  Commands "lspci" and "dmesg" say that the error comes from the following 
device:
  00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#6 (rev f1)

  I will attach lspci and dmesg output on a tar.gz file.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-37-generic 4.10.0-37.41
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  georgem2557 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Sun Oct 22 23:17:57 2017
  InstallationDate: Installed on 2017-10-20 (2 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 13d3:3496 IMC Networks 
   Bus 001 Device 003: ID 13d3:5a01 IMC Networks 
   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: ASUSTeK COMPUTER INC. X542UQ
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic.efi.signed 
root=UUID=38d32efc-d0cb-4a82-9e6c-e6a3bd62e51d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X542UQ.202
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X542UQ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX542UQ.202:bd05/18/2017:svnASUSTeKCOMPUTERINC.:pnX542UQ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX542UQ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X542UQ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1726159] Re: PCIe BUS Error causing really slow laptop performance

2017-10-22 Thread George Mathioudakis
** Summary changed:

- PCIe Error causing really slow laptop performance
+ PCIe BUS Error causing really slow laptop performance

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

Title:
  PCIe BUS Error causing really slow laptop performance

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently bought the following laptop: 
  Asus VivoBook X542UQ-DM148T - 15.6" (i7-7500U/8GB/256GB/GT 940MX 2GB)

  It came pre-installed with Win10 and I did a fresh install of Ubuntu
  16.04 LTS. The screen was flickering for some reason and installing
  Ubuntu 17.04 fixed the issue.

  The real problem is that when I'm booting the laptop, the following
  error is being shown on my screen:

  [   12.866073] pcieport :00:1c.5: can't find device of ID00e5
  [   12.898481] pcieport :00:1c.5: AER: Multiple Corrected error received: 
id=00e5
  [   12.898488] pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e5(Receiver ID)
  [   12.898491] pcieport :00:1c.5:   device [8086:9d15] error 
status/mask=2041/2000
  [   12.898492] pcieport :00:1c.5:[ 0] Receiver Error (First)
  [   12.898493] pcieport :00:1c.5:[ 6] Bad TLP

  I know that this error can be hid with one of the following kernel boot 
arguments:
  pci=nomsi / pci=noaer / pcie_aspm=off / pci=nommconf.

  The weird thing is that the above output is only being shown when the
  laptop is on AC Power (charging). When the laptop is not connected to
  AC (battery-mode), it has performance issues (slow boot and slow
  application launching). I was trying all day long to fix the problem.
  I removed everything that had to do with power-saving, reinstalled,
  re-tweaked for performance but had no luck. While diagnosing, I had
  the idea to benchmark the "M2 SATA-3 SSD" that my laptop had. The
  results are:

  * On AC Power: 522MB/s (READ) | 416MB/s (WRITE)
  * On Battery Power: 32MB/s (READ) | 31MB/s (WRITE)

  This explains everyting. That's why I'm having a slow boot and slow
  application launching!

  Commands "lspci" and "dmesg" say that the error comes from the following 
device:
  00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#6 (rev f1)

  I will attach lspci and dmesg output on a tar.gz file.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-37-generic 4.10.0-37.41
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  georgem2557 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Sun Oct 22 23:17:57 2017
  InstallationDate: Installed on 2017-10-20 (2 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 13d3:3496 IMC Networks 
   Bus 001 Device 003: ID 13d3:5a01 IMC Networks 
   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: ASUSTeK COMPUTER INC. X542UQ
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic.efi.signed 
root=UUID=38d32efc-d0cb-4a82-9e6c-e6a3bd62e51d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X542UQ.202
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X542UQ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX542UQ.202:bd05/18/2017:svnASUSTeKCOMPUTERINC.:pnX542UQ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX542UQ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X542UQ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1726159] [NEW] PCIe BUS Error causing really slow laptop performance

2017-10-22 Thread George Mathioudakis
Public bug reported:

I recently bought the following laptop: 
Asus VivoBook X542UQ-DM148T - 15.6" (i7-7500U/8GB/256GB/GT 940MX 2GB)

It came pre-installed with Win10 and I did a fresh install of Ubuntu
16.04 LTS. The screen was flickering for some reason and installing
Ubuntu 17.04 fixed the issue.

The real problem is that when I'm booting the laptop, the following
error is being shown on my screen:

[   12.866073] pcieport :00:1c.5: can't find device of ID00e5
[   12.898481] pcieport :00:1c.5: AER: Multiple Corrected error received: 
id=00e5
[   12.898488] pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e5(Receiver ID)
[   12.898491] pcieport :00:1c.5:   device [8086:9d15] error 
status/mask=2041/2000
[   12.898492] pcieport :00:1c.5:[ 0] Receiver Error (First)
[   12.898493] pcieport :00:1c.5:[ 6] Bad TLP

I know that this error can be hid with one of the following kernel boot 
arguments:
pci=nomsi / pci=noaer / pcie_aspm=off / pci=nommconf.

The weird thing is that the above output is only being shown when the
laptop is on AC Power (charging). When the laptop is not connected to AC
(battery-mode), it has performance issues (slow boot and slow
application launching). I was trying all day long to fix the problem. I
removed everything that had to do with power-saving, reinstalled, re-
tweaked for performance but had no luck. While diagnosing, I had the
idea to benchmark the "M2 SATA-3 SSD" that my laptop had. The results
are:

* On AC Power: 522MB/s (READ) | 416MB/s (WRITE)
* On Battery Power: 32MB/s (READ) | 31MB/s (WRITE)

This explains everyting. That's why I'm having a slow boot and slow
application launching!

Commands "lspci" and "dmesg" say that the error comes from the following device:
00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 
(rev f1)

I will attach lspci and dmesg output on a tar.gz file.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-37-generic 4.10.0-37.41
ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
Uname: Linux 4.10.0-37-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  georgem2557 F pulseaudio
CurrentDesktop: Unity:Unity7
Date: Sun Oct 22 23:17:57 2017
InstallationDate: Installed on 2017-10-20 (2 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 13d3:3496 IMC Networks 
 Bus 001 Device 003: ID 13d3:5a01 IMC Networks 
 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: ASUSTeK COMPUTER INC. X542UQ
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic.efi.signed 
root=UUID=38d32efc-d0cb-4a82-9e6c-e6a3bd62e51d ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-37-generic N/A
 linux-backports-modules-4.10.0-37-generic  N/A
 linux-firmware 1.164.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/18/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X542UQ.202
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X542UQ
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX542UQ.202:bd05/18/2017:svnASUSTeKCOMPUTERINC.:pnX542UQ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX542UQ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X542UQ
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug asus error kernel-bug laptop pcie vivobook zesty

** Attachment added: "The following compressed folder contains dmesg.txt and 
lspci.txt"
   
https://bugs.launchpad.net/bugs/1726159/+attachment/4986395/+files/report.tar.gz

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

Title:
  PCIe BUS Error causing really slow laptop performance

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently bought the following laptop: 
  Asus VivoBook X542UQ-DM148T - 15.6" (i7-7500U/8GB/256GB/GT 940MX 2GB)

  It came pre-installed with Win10 and I did a fresh install of Ubuntu
  16.04 LTS. The screen was flickering for some reason and installing
  Ubuntu 17.04 fixed the issue.

  The real problem is that when I'm booting the laptop, the following
  error is being shown on my screen:

  [   12.866073] pcieport :00:1c.5: can't find device of ID00e5
  [   12.898481] 

[Kernel-packages] [Bug 1572698] Re: [patch included]Slow speed and dropped connections with Realtek RTL8192CU-based wifi

2017-10-22 Thread Patrick Then
I'm currently not using the adapter since I've moved to a new apartment where 
it's easily possible to connect via cable to the lan.
I don't remember there being any errors though.
Seriously guys, the solution is available on github, I linked it over one year 
ago, all the necessary information should be there.

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

Title:
  [patch included]Slow speed and dropped connections with Realtek
  RTL8192CU-based wifi

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  EDIT(other user): Some one fixed it in github, still works in at least in 
linux 4.4-4.11
  https://github.com/pvaret/rtl8192cu-fixes
  EDIT:

  I am using a D-Link DWA-131 USB wlan adapter to connect to my private wlan.
  The adapter works fine under Windows and I have no problems connecting to my 
wlan with other devices (e.g. my laptop running Linux Mint).
  However, the adapter, which is based on the Realtek rtl8192cu chipset, won't 
work correctly on any current Ubuntu machine (in my case Kubuntu 15.10 64bit):

  As also showcased by a myriad of other bug reports (most of which have 
expired by now), wlan-adapters based on the Realtek rtl8192cu chipset exhibit 
very slow connection speeds and frequently dropped connections with current 
Linux kernels.
  I have noticed this originally in Linux Mint 17 running kernel 3.19.x, in 
Kubuntu 15.10 up to 4.2.0.35 and can confirm that it is still present in a live 
session of Xenial Xerus (16.04).
  I have tried commonly mentioned "fixes" such as deactivating hardware 
encryption without success.

  The drivers available on the Realtek homepage are apparently intended
  for older kernels and won't install.

  There is, however, a fixed driver available via github 
(https://github.com/pvaret/rtl8192cu-fixes).
  I have followed the instructions found there and finally my wlan-adapter is 
working correctly.
  Apparently the issues caused by the broken driver in the linux kernels might 
be connected to power management.

  I am posting this bug here in the hope that some developer finally manages to 
incorporate the (obviously available) fixes found in the github-drivers into 
the drivers already included in the kernel.
  ---
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  patrick2300 F pulseaudio
   /dev/snd/controlC1:  patrick2300 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=28c49a78-8b93-495e-bc1b-22c87db4734c
  InstallationDate: Installed on 2015-10-22 (181 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Gigabyte Technology Co., Ltd. GA-870A-UD3
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic 
root=UUID=1016b861-fa27-4990-bac9-58a3ab27ff5b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  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.2.0-35-generic N/A
   linux-backports-modules-4.2.0-35-generic  N/A
   linux-firmware1.149.3
  RfKill:

  Tags:  wily
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  Uname: Linux 4.2.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 08/01/2011
  dmi.bios.vendor: AwardAward (授与する, じゅよする, juyosuru) Software International, 
Inc.
  dmi.bios.version: F5
  dmi.board.name: GA-870A-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd08/01/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-870A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-870A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-870A-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Kernel-packages] [Bug 1724911] Re: text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

2017-10-22 Thread Steve Langasek
a7093ba162d942e29ae27a64f8432db65f7f21ab is bad; same symptoms as
04759194dc447ff0b9ef35bc641ce3bb076c2930 and
edc2988c548db05e33b921fed15821010bc74895.

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

Title:
  text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

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

Bug description:
  After upgrading my laptop to Ubuntu 17.10, I am unable to access
  gettys on any of the text-mode VTs on my system.

  gdm3 is running on VT1, my user session is running on VT2.  I can
  switch between these.  If I switch to VT3, I know that the VT switch
  has happened in the kernel because the X cursor disappears; but the
  display retains the output of my X session, and the text console with
  getty never appears.

  Switching back to VT2 works fine.

  The same problem occurs with either Wayland or X.

  My laptop is docked with an external monitor, which could be a factor.
  (I also notice that during boot, plymouth is only rendered on the
  internal monitor, not the external monitor; this may be related).  I
  have not yet tested whether this problem is reproducible if I undock.

  The system is booting with vt.handoff=7, which I believe is still the
  default in Ubuntu 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vorlon24080 F pulseaudio
   /dev/snd/controlC0:  vorlon24080 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 09:57:59 2017
  HibernationDevice: RESUME=UUID=6df76279-19ea-45a4-bec9-e4fdc858729a
  InstallationDate: Installed on 2010-09-24 (2582 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1725259] Re: general protection fault: 0000 [#1] SMP

2017-10-22 Thread Cedric Br
Test Kernel 4.14 rc5 mainline. The bug also exist there

The last good kernel was 4.12, but i'm not sure. For Kernel 4.9, i'm
sure the bug didn't exist

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

** Tags added: kernel-bug-exists-upstream

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

Title:
  general protection fault:  [#1] SMP

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  Got a GPU hang when playing videos in totem. When Playing in VLC everything 
is OK
  Same crash under mpv



  [drm] GPU HANG: ecode 5:0:0xfdff, in Xorg [2005], reason: Hang on rcs0, 
action: reset
  [  235.623605] [drm] GPU hangs can indicate a bug anywhere in the entire gfx 
stack, including userspace.
  [  235.623606] [drm] Please file a _new_ bug report on bugs.freedesktop.org 
against DRI -> DRM/Intel
  [  235.623607] [drm] drm/i915 developers can then reassign to the right 
component if it's not a kernel issue.
  [  235.623607] [drm] The gpu crash dump is required to analyze gpu hangs, so 
please always attach it.
  [  235.623608] [drm] GPU crash dump saved to /sys/class/drm/card0/error
  [  235.623687] drm/i915: Resetting chip after gpu hang

  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/controlC0:  gdm 984 F pulseaudio
brand101338 F pulseaudio
  Date: Fri Oct 20 13:47:22 2017
  Failure: oops
  InstallationDate: Installed on 2017-08-18 (63 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170816)
  Lsusb:
   Bus 002 Device 003: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude E6410
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=5810df9f-2bd6-4f2e-89a8-b16ac27ff5b2 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: general protection fault:  [#1] SMP
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 04373Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/05/2013:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn04373Y:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6410
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1726061] Re: Inspiron 5565 suspend issues after 17.10 upgrade

2017-10-22 Thread Aaron Peromsik
** Summary changed:

- Inspiron 5536 suspend issues after 17.10 upgrade
+ Inspiron 5565 suspend issues after 17.10 upgrade

** Description changed:

- On my Inspiron 5536, 17.10 seems to work fairly well, unless I try to
+ On my Inspiron 5565, 17.10 seems to work fairly well, unless I try to
  suspend. Suspend shuts off the display but doesn't seem to actually shut
  off the CPU -- fans still run. When I move the mouse the display comes
  back on but upon entering my password sometimes the session crashes and
  I am dumped back to the login screen; sometimes the session is still
  there but wifi is either disabled (all wifi-related menu items gone) or
  visible (with question mark) but non-functional. In any case once I have
  suspended I cannot shut down or reboot any way other than the hard way,
  by holding the power button for several seconds. Doesn't seem to matter
  whether I am using X or Wayland.
  
  Suspend works mostly fine if I choose the 4.10 kernel from GRUB...
  although I am prompted for login more times than necessary on resume.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  aaron  2489 F pulseaudio
-  /dev/snd/controlC1:  aaron  2489 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  aaron  2489 F pulseaudio
+  /dev/snd/controlC1:  aaron  2489 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 12:22:13 2017
  HibernationDevice: RESUME=UUID=3cc55560-1886-446c-8d60-15136ee14d32
  InstallationDate: Installed on 2016-12-25 (301 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. Inspiron 5565
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic.efi.signed 
root=UUID=c30eb880-24e4-41af-9203-feff0ab69c8c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-4.10.0-37-generic N/A
-  linux-backports-modules-4.10.0-37-generic  N/A
-  linux-firmware 1.169
+  linux-restricted-modules-4.10.0-37-generic N/A
+  linux-backports-modules-4.10.0-37-generic  N/A
+  linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago)
  dmi.bios.date: 07/20/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.2
  dmi.board.name: 0RVKF9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.0.2
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.2:bd07/20/2016:svnDellInc.:pnInspiron5565:pvr1.0.2:rvnDellInc.:rn0RVKF9:rvrA00:cvnDellInc.:ct10:cvr1.0.2:
  dmi.product.name: Inspiron 5565
  dmi.product.version: 1.0.2
  dmi.sys.vendor: Dell Inc.

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

Title:
  Inspiron 5565 suspend issues after 17.10 upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Inspiron 5565, 17.10 seems to work fairly well, unless I try to
  suspend. Suspend shuts off the display but doesn't seem to actually
  shut off the CPU -- fans still run. When I move the mouse the display
  comes back on but upon entering my password sometimes the session
  crashes and I am dumped back to the login screen; sometimes the
  session is still there but wifi is either disabled (all wifi-related
  menu items gone) or visible (with question mark) but non-functional.
  In any case once I have suspended I cannot shut down or reboot any way
  other than the hard way, by holding the power button for several
  seconds. Doesn't seem to matter whether I am using X or Wayland.

  Suspend works mostly fine if I choose the 4.10 kernel from GRUB...
  although I am prompted for login more times than necessary on resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron  2489 F pulseaudio
   /dev/snd/controlC1:  aaron  2489 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 12:22:13 2017
  HibernationDevice: RESUME=UUID=3cc55560-1886-446c-8d60-15136ee14d32
  InstallationDate: Installed on 2016-12-25 (301 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. Inspiron 5565
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic.efi.signed 

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

2017-10-22 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  Inspiron 5536 suspend issues after 17.10 upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Inspiron 5536, 17.10 seems to work fairly well, unless I try to
  suspend. Suspend shuts off the display but doesn't seem to actually
  shut off the CPU -- fans still run. When I move the mouse the display
  comes back on but upon entering my password sometimes the session
  crashes and I am dumped back to the login screen; sometimes the
  session is still there but wifi is either disabled (all wifi-related
  menu items gone) or visible (with question mark) but non-functional.
  In any case once I have suspended I cannot shut down or reboot any way
  other than the hard way, by holding the power button for several
  seconds. Doesn't seem to matter whether I am using X or Wayland.

  Suspend works mostly fine if I choose the 4.10 kernel from GRUB...
  although I am prompted for login more times than necessary on resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron  2489 F pulseaudio
   /dev/snd/controlC1:  aaron  2489 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 12:22:13 2017
  HibernationDevice: RESUME=UUID=3cc55560-1886-446c-8d60-15136ee14d32
  InstallationDate: Installed on 2016-12-25 (301 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. Inspiron 5565
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic.efi.signed 
root=UUID=c30eb880-24e4-41af-9203-feff0ab69c8c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago)
  dmi.bios.date: 07/20/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.2
  dmi.board.name: 0RVKF9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.0.2
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.2:bd07/20/2016:svnDellInc.:pnInspiron5565:pvr1.0.2:rvnDellInc.:rn0RVKF9:rvrA00:cvnDellInc.:ct10:cvr1.0.2:
  dmi.product.name: Inspiron 5565
  dmi.product.version: 1.0.2
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1726061] [NEW] Inspiron 5536 suspend issues after 17.10 upgrade

2017-10-22 Thread Aaron Peromsik
Public bug reported:

On my Inspiron 5536, 17.10 seems to work fairly well, unless I try to
suspend. Suspend shuts off the display but doesn't seem to actually shut
off the CPU -- fans still run. When I move the mouse the display comes
back on but upon entering my password sometimes the session crashes and
I am dumped back to the login screen; sometimes the session is still
there but wifi is either disabled (all wifi-related menu items gone) or
visible (with question mark) but non-functional. In any case once I have
suspended I cannot shut down or reboot any way other than the hard way,
by holding the power button for several seconds. Doesn't seem to matter
whether I am using X or Wayland.

Suspend works mostly fine if I choose the 4.10 kernel from GRUB...
although I am prompted for login more times than necessary on resume.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19
ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
Uname: Linux 4.10.0-37-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  aaron  2489 F pulseaudio
 /dev/snd/controlC1:  aaron  2489 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 22 12:22:13 2017
HibernationDevice: RESUME=UUID=3cc55560-1886-446c-8d60-15136ee14d32
InstallationDate: Installed on 2016-12-25 (301 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: Dell Inc. Inspiron 5565
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic.efi.signed 
root=UUID=c30eb880-24e4-41af-9203-feff0ab69c8c ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-37-generic N/A
 linux-backports-modules-4.10.0-37-generic  N/A
 linux-firmware 1.169
SourcePackage: linux
UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago)
dmi.bios.date: 07/20/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.2
dmi.board.name: 0RVKF9
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 1.0.2
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.2:bd07/20/2016:svnDellInc.:pnInspiron5565:pvr1.0.2:rvnDellInc.:rn0RVKF9:rvrA00:cvnDellInc.:ct10:cvr1.0.2:
dmi.product.name: Inspiron 5565
dmi.product.version: 1.0.2
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug artful

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

Title:
  Inspiron 5536 suspend issues after 17.10 upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Inspiron 5536, 17.10 seems to work fairly well, unless I try to
  suspend. Suspend shuts off the display but doesn't seem to actually
  shut off the CPU -- fans still run. When I move the mouse the display
  comes back on but upon entering my password sometimes the session
  crashes and I am dumped back to the login screen; sometimes the
  session is still there but wifi is either disabled (all wifi-related
  menu items gone) or visible (with question mark) but non-functional.
  In any case once I have suspended I cannot shut down or reboot any way
  other than the hard way, by holding the power button for several
  seconds. Doesn't seem to matter whether I am using X or Wayland.

  Suspend works mostly fine if I choose the 4.10 kernel from GRUB...
  although I am prompted for login more times than necessary on resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron  2489 F pulseaudio
   /dev/snd/controlC1:  aaron  2489 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 12:22:13 2017
  HibernationDevice: RESUME=UUID=3cc55560-1886-446c-8d60-15136ee14d32
  InstallationDate: Installed on 2016-12-25 (301 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. Inspiron 5565
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic.efi.signed 
root=UUID=c30eb880-24e4-41af-9203-feff0ab69c8c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago)
  dmi.bios.date: 07/20/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.2
  dmi.board.name: 0RVKF9
  dmi.board.vendor: Dell Inc.
  

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

2017-10-22 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  general protection fault:  [#1] SMP

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I was running audiacity program

  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/controlC0:  marwynne   1390 F pulseaudio
  Date: Sat Oct 21 12:53:15 2017
  Failure: oops
  HibernationDevice: RESUME=UUID=515d5826-aef9-4a9a-885f-090a1ee3bf6e
  InstallationDate: Installed on 2016-12-04 (321 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Hewlett-Packard HP Pavilion dv2700 Notebook PC
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=53eac7c5-6bcb-4dac-aebf-d9ac071c9a90 ro persistent quiet splash 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: general protection fault:  [#1] SMP
  UpgradeStatus: Upgraded to artful on 2017-10-20 (1 days ago)
  dmi.bios.date: 05/07/2008
  dmi.bios.vendor: Phoenix
  dmi.bios.version: F.2B
  dmi.board.name: 30CE
  dmi.board.vendor: Wistron
  dmi.board.version: 80.52
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvrF.2B:bd05/07/2008:svnHewlett-Packard:pnHPPaviliondv2700NotebookPC:pvrF.2B:rvnWistron:rn30CE:rvr80.52:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv2700 Notebook PC
  dmi.product.version: F.2B
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1715552] Re: VMWare does not start

2017-10-22 Thread Daniel
This occurs also with Kubuntu 17.10 RTM and VMware Workstation Pro 
12.5.7-5813279.
I remember that on 17.04 it didn't occur.
I used to install the same version of VMWare Workstation in Kubuntu 17.04, 
running inside a virtual machine (just for testing purposes).

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

Title:
  VMWare does not start

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Under Ubuntu 17.10 beta VMWare 12.5.7 cannot be started:

  /usr/lib/vmware/bin/vmware-modconfig: Relink `/lib/x86_64-linux-
  gnu/libbsd.so.0' with `/lib/x86_64-linux-gnu/librt.so.1' for IFUNC
  symbol `clock_gettime'

  Works under Ubuntu 17.04

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-13-generic 4.12.0-13.14
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wolf   9336 F pulseaudio
   /dev/snd/controlC0:  wolf   9336 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  7 07:53:43 2017
  HibernationDevice: RESUME=UUID=88d69bc7-ac96-42c6-bf6d-5c912964a63b
  InstallationDate: Installed on 2017-09-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-13-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.12.0-13-generic N/A
   linux-backports-modules-4.12.0-13-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B33.1706181928
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  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/1715552/+subscriptions

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


[Kernel-packages] [Bug 1726042] [NEW] general protection fault: 0000 [#1] SMP

2017-10-22 Thread Marwynne Kuhn
Public bug reported:

I was running audiacity program

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/controlC0:  marwynne   1390 F pulseaudio
Date: Sat Oct 21 12:53:15 2017
Failure: oops
HibernationDevice: RESUME=UUID=515d5826-aef9-4a9a-885f-090a1ee3bf6e
InstallationDate: Installed on 2016-12-04 (321 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: Hewlett-Packard HP Pavilion dv2700 Notebook PC
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=53eac7c5-6bcb-4dac-aebf-d9ac071c9a90 ro persistent quiet splash 
vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
SourcePackage: linux
Title: general protection fault:  [#1] SMP
UpgradeStatus: Upgraded to artful on 2017-10-20 (1 days ago)
dmi.bios.date: 05/07/2008
dmi.bios.vendor: Phoenix
dmi.bios.version: F.2B
dmi.board.name: 30CE
dmi.board.vendor: Wistron
dmi.board.version: 80.52
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenix:bvrF.2B:bd05/07/2008:svnHewlett-Packard:pnHPPaviliondv2700NotebookPC:pvrF.2B:rvnWistron:rn30CE:rvr80.52:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.family: 103C_5335KV
dmi.product.name: HP Pavilion dv2700 Notebook PC
dmi.product.version: F.2B
dmi.sys.vendor: Hewlett-Packard

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


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

Title:
  general protection fault:  [#1] SMP

Status in linux package in Ubuntu:
  New

Bug description:
  I was running audiacity program

  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/controlC0:  marwynne   1390 F pulseaudio
  Date: Sat Oct 21 12:53:15 2017
  Failure: oops
  HibernationDevice: RESUME=UUID=515d5826-aef9-4a9a-885f-090a1ee3bf6e
  InstallationDate: Installed on 2016-12-04 (321 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Hewlett-Packard HP Pavilion dv2700 Notebook PC
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=53eac7c5-6bcb-4dac-aebf-d9ac071c9a90 ro persistent quiet splash 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: general protection fault:  [#1] SMP
  UpgradeStatus: Upgraded to artful on 2017-10-20 (1 days ago)
  dmi.bios.date: 05/07/2008
  dmi.bios.vendor: Phoenix
  dmi.bios.version: F.2B
  dmi.board.name: 30CE
  dmi.board.vendor: Wistron
  dmi.board.version: 80.52
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvrF.2B:bd05/07/2008:svnHewlett-Packard:pnHPPaviliondv2700NotebookPC:pvrF.2B:rvnWistron:rn30CE:rvr80.52:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv2700 Notebook PC
  dmi.product.version: F.2B
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1726021] [NEW] Artful Aardvark cannot boot dm-raid raid5 array

2017-10-22 Thread David Lee
Public bug reported:

Rehash of bug 1313169 / bug 1683105

My patch was ignored. As a result I am left with two unbootable boxes
after upgrade.

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

** Description changed:

  Rehash of bug 1313169.
  
  My patch was ignored. As a result I am left with two unbootable boxes
  after upgrade.
+ 
+ System hangs at error device-manager: table: 253:1: raid: unknown target
+ type followed by dropping to busybox.

** Description changed:

- Rehash of bug 1313169.
+ Rehash of bug 1313169 / bug 1683105
  
  My patch was ignored. As a result I am left with two unbootable boxes
  after upgrade.
- 
- System hangs at error device-manager: table: 253:1: raid: unknown target
- type followed by dropping to busybox.

** Package changed: linux (Ubuntu) => dmraid (Ubuntu)

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

Title:
  Artful Aardvark cannot boot dm-raid raid5 array

Status in dmraid package in Ubuntu:
  New

Bug description:
  Rehash of bug 1313169 / bug 1683105

  My patch was ignored. As a result I am left with two unbootable boxes
  after upgrade.

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

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


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

2017-10-22 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [ksoftirqd/3:28]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The system freezed for a while and i needed to hard reset PC

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  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/controlC0:  gdm1091 F pulseaudio
matlin 1415 F pulseaudio
   /dev/snd/controlC1:  gdm1091 F pulseaudio
matlin 1415 F pulseaudio
  Date: Sun Oct 22 16:00:32 2017
  Failure: oops
  InstallationDate: Installed on 2017-10-20 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IwConfig:
   enp0s8no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=02653f53-eed9-4176-8ec8-6168848ded94 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [ksoftirqd/3:28]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2010
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2N-E ACPI BIOS Revision 5001
  dmi.board.name: M2N-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2N-EACPIBIOSRevision5001:bd03/23/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-E:rvr1.XX: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/1725987/+subscriptions

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


[Kernel-packages] [Bug 1725987] [NEW] watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [ksoftirqd/3:28]

2017-10-22 Thread Costa davide
Public bug reported:

The system freezed for a while and i needed to hard reset PC

ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
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/controlC0:  gdm1091 F pulseaudio
  matlin 1415 F pulseaudio
 /dev/snd/controlC1:  gdm1091 F pulseaudio
  matlin 1415 F pulseaudio
Date: Sun Oct 22 16:00:32 2017
Failure: oops
InstallationDate: Installed on 2017-10-20 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
IwConfig:
 enp0s8no wireless extensions.
 
 lono wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=02653f53-eed9-4176-8ec8-6168848ded94 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
RfKill:
 
SourcePackage: linux
Title: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [ksoftirqd/3:28]
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/23/2010
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS M2N-E ACPI BIOS Revision 5001
dmi.board.name: M2N-E
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2N-EACPIBIOSRevision5001:bd03/23/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-E:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


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

Title:
  watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [ksoftirqd/3:28]

Status in linux package in Ubuntu:
  New

Bug description:
  The system freezed for a while and i needed to hard reset PC

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  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/controlC0:  gdm1091 F pulseaudio
matlin 1415 F pulseaudio
   /dev/snd/controlC1:  gdm1091 F pulseaudio
matlin 1415 F pulseaudio
  Date: Sun Oct 22 16:00:32 2017
  Failure: oops
  InstallationDate: Installed on 2017-10-20 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IwConfig:
   enp0s8no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=02653f53-eed9-4176-8ec8-6168848ded94 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [ksoftirqd/3:28]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2010
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2N-E ACPI BIOS Revision 5001
  dmi.board.name: M2N-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Kernel-packages] [Bug 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

2017-10-22 Thread AS
I can confirm the issue with a week 33 Ryzen 1700 on Asus Prime B350 Plus.
I had segfaults with my previous 1700 (week 22 iirc). No more segfaults with 
the week 33 CPU but still random crashes on (long time) idle.

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-041100-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: 

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

2017-10-22 Thread Eduard
** Summary changed:

- Graphics problem -  80% of the Left hand side of screen solid black
+ Bug in Kernel 4.13 : Intel Mobile Graphics show 80 % black screen

** Summary changed:

- Bug in Kernel 4.13 : Intel Mobile Graphics show 80 % black screen
+ Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

** Also affects: opensuse via
   https://bugzilla.opensuse.org/show_bug.cgi?id=1058870
   Importance: Unknown
   Status: Unknown

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

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

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

Status in Ubuntu:
  Confirmed
Status in openSUSE:
  Unknown

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

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

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

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

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


[Kernel-packages] [Bug 1724639] Re: Graphics problem - 80% of the Left hand side of screen solid black

2017-10-22 Thread Eduard
@kaihengfeng;

I have tried both kernels you proposed, and can confirm what has been stated in 
the opensuse-Forum:
Both Kernels 4.11 and 4.12 SEEM to be working and show no graphic glitches.

So the first idea would be that something happend within the Kernel transition 
from 4.12 to 4.13, , but not too easy. 
Trying to open differnet Applications with 4.12 shows that there is already 
something fishy going on with the graphics, e.g. LibreOffice will not start 
with Kernel 4.12 and I believe it must have to do with the graphics.

This is in accordance with the errors / logs / exceptions posted in the
opensuse bug-report.

So for Computers / Laptops / Netbooks using the Intel Mobile 945
Chipsets and Ubuntu 17.10, I would personally recommend the 4.11 Kernel,
for I found it to be most stable and all applications I have tested so
far do work.

I can help with logs and dmesg if needed, please just tell me what logs
you need.



For everyone who has this error, I will show you a workaround so you can still 
use your computer even after the update to 17.10.
The workaround consists of installing kernel 4.11 and using it.

Enter Grub (which is the startup manager) by holding down the shift key while 
booting.
If you have Grub showing up on every boot (e.g. if you have a multi OS and also 
have Win 7/8/10) installed, even better. 
Now select Ubuntu ... enhanced options and then select starting up with the  
4.10 Kernel (which still should be installed if you have updated from 17.04). 
If the option to start up with the 4.10 kernel is not available, select 
recovery mode (which should also work fine, but you have to work with a low 
resolution then)

In the 4.10 Ubuntu (recovery mode) open your browser and go to this directory: 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11/

under "Build for i386 succeeded" download these 3 files:

linux-headers-4.11.0-041100_4.11.0-041100.201705041534_all.deb
linux-headers-4.11.0-041100-generic_4.11.0-041100.201705041534_i386.deb
linux-image-4.11.0-041100-generic_4.11.0-041100.201705041534_i386.deb

After the download, put those 3 Files in a new, seperate folder, and
open the directory with the terminal (right click on the folder --> open
in Terminal).

In the Terminal post:

sudo dpkg -i *.deb

Press enter and wait. The 4.11 Kernel will be installed, it takes a while.
After that, you can reboot your computer and in Grub in the enhanced options 
you can now start your computer with the 4.11 generic kernel, which works fine 
for me.

If you want Ubuntu to start up everytime with the 4.11 Kernel, you can
use the "Grub Customzier" for that. Here is how you install the grub
customizer:

http://ubuntuhandbook.org/index.php/2014/04/install-grub-customizer-
ubuntu-1404/


Let's hope that someone in this Linux world can make the Intel Mobile Graphics 
card work again in a de-bugged 4.13 kernel =)

Cheers and Kudos everyone !

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

Title:
  Graphics problem -  80% of the Left hand side of screen solid black

Status in linux package in Ubuntu:
  Confirmed

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-16-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian 918 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf034 irq 25'
 Mixer name : 'Realtek ALC272'
 Components : 'HDA:10ec0272,144dca00,0011'
 Controls  : 25
 Simple ctrls  : 12
  CurrentDesktop: LXDE
  Date: Wed Oct 18 18:30:15 2017
  HibernationDevice: RESUME=UUID=c54e130e-6625-4d96-ba75-4efaa6a9da75
  InstallationDate: Installed on 2017-10-18 (0 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: 

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

2017-10-22 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  system hangs during boot when using a USB Keyboard

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My USB Keyboard consistently turns off as soon as the boot process
  gets past the GRUB menu. The system then hangs - indefinitely, unless
  I plug the keyboard in again.

  This behaviour was present in Beta 2 and manifests itself in the
  official release - freshly installed - both in default and recovery
  mode.

  Dmesg reports:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0]
  watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0]
  (Obviously, the number of seconds depends on the time it takes me to plug the 
keyboard in again). 

  And well before those lines comes:
  pci :00:12.1: OHCI: BIOS handoff failed (BIOS bug?) 0184

  When I watch the boot messages roll off the screen, I see the system indeed 
get halted on a message about OHCI:
  ohci-pci :00:12.1: irq 16, io mem 0xfe02d000

  I doubt this is actually a BIOS bug because I have been using this
  same board without a glitch for six or seven years now.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jurgen 1331 F pulseaudio
   /dev/snd/controlC0:  jurgen 1331 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 10:48:01 2017
  HibernationDevice: RESUME=UUID=04fb3679-ef58-43f4-880d-5331e44f42cd
  InstallationDate: Installed on 2017-10-22 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-MA790XT-UD4P
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=2f0ee50f-9ce5-4a97-b6cf-4c9971e3d2e5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/20/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F7
  dmi.board.name: GA-MA790XT-UD4P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd11/20/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790XT-UD4P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790XT-UD4P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA790XT-UD4P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Kernel-packages] [Bug 1725948] [NEW] system hangs during boot when using a USB Keyboard

2017-10-22 Thread Jay S.
Public bug reported:

My USB Keyboard consistently turns off as soon as the boot process gets
past the GRUB menu. The system then hangs - indefinitely, unless I plug
the keyboard in again.

This behaviour was present in Beta 2 and manifests itself in the
official release - freshly installed - both in default and recovery
mode.

Dmesg reports:
watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0]
watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0]
(Obviously, the number of seconds depends on the time it takes me to plug the 
keyboard in again). 

And well before those lines comes:
pci :00:12.1: OHCI: BIOS handoff failed (BIOS bug?) 0184

When I watch the boot messages roll off the screen, I see the system indeed get 
halted on a message about OHCI:
ohci-pci :00:12.1: irq 16, io mem 0xfe02d000

I doubt this is actually a BIOS bug because I have been using this same
board without a glitch for six or seven years now.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  jurgen 1331 F pulseaudio
 /dev/snd/controlC0:  jurgen 1331 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 22 10:48:01 2017
HibernationDevice: RESUME=UUID=04fb3679-ef58-43f4-880d-5331e44f42cd
InstallationDate: Installed on 2017-10-22 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
IwConfig:
 enp2s0no wireless extensions.
 
 lono wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. GA-MA790XT-UD4P
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=2f0ee50f-9ce5-4a97-b6cf-4c9971e3d2e5 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-16-generic N/A
 linux-backports-modules-4.13.0-16-generic  N/A
 linux-firmware 1.169
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/20/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F7
dmi.board.name: GA-MA790XT-UD4P
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd11/20/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790XT-UD4P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790XT-UD4P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-MA790XT-UD4P
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug artful

** Attachment added: "dmesg2.txt"
   https://bugs.launchpad.net/bugs/1725948/+attachment/4984456/+files/dmesg2.txt

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

Title:
  system hangs during boot when using a USB Keyboard

Status in linux package in Ubuntu:
  New

Bug description:
  My USB Keyboard consistently turns off as soon as the boot process
  gets past the GRUB menu. The system then hangs - indefinitely, unless
  I plug the keyboard in again.

  This behaviour was present in Beta 2 and manifests itself in the
  official release - freshly installed - both in default and recovery
  mode.

  Dmesg reports:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0]
  watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0]
  (Obviously, the number of seconds depends on the time it takes me to plug the 
keyboard in again). 

  And well before those lines comes:
  pci :00:12.1: OHCI: BIOS handoff failed (BIOS bug?) 0184

  When I watch the boot messages roll off the screen, I see the system indeed 
get halted on a message about OHCI:
  ohci-pci :00:12.1: irq 16, io mem 0xfe02d000

  I doubt this is actually a BIOS bug because I have been using this
  same board without a glitch for six or seven years now.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jurgen 1331 F pulseaudio
   /dev/snd/controlC0:  jurgen 1331 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 10:48:01 2017
  HibernationDevice: 

[Kernel-packages] [Bug 1683508] Re: touchpad not working (elan_i2c invalid report id data)

2017-10-22 Thread Kai-Heng Feng
What's the output of `cat /sys/class/dmi/id/product_name`?

Also, please try kernel here:
http://people.canonical.com/~khfeng/lp1683508/

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

Title:
  touchpad not working (elan_i2c invalid report id data)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes upon boot mouse is not responsive. I get spammed the following in 
syslog every time I move the pointer:
  elan_i2c i2c-ELAN1000:00: invalid report id data (1)

  workaround:
  sudo rmmod elan_i2c
  sudo modprobe elan_i2c

  fixes it until next reboot, then it is a crapshoot about whether that
  problem will arise after boot or not.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lutostag   4214 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon Apr 17 16:26:12 2017
  HibernationDevice: RESUME=UUID=f32bc2f0-9063-4554-8204-936f2f51ffb3
  InstallationDate: Installed on 2016-09-20 (209 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cb Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305CA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-27 (20 days ago)
  dmi.bios.date: 09/11/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305CA.201
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX305CA.201:bd09/11/2015:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX305CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1724639] Re: Graphics problem - 80% of the Left hand side of screen solid black

2017-10-22 Thread Eduard
I can confirm the bug too.
After the Xubuntu update from 17.04 to 17.10, the intel mobile graphics is 
broken.

Moreover, the issue seems to be a little bigger.
The bug here is the same one as bug #1720703 , so Mods please merge the two 
bugs.
(https://bugs.launchpad.net/ubuntu-mate/+bug/1720703)
It seems to have nothing to do with the Ubuntu distro, as is is present in 
Ubuntu Mate,
Ubuntu, Lubuntu und Xubuntu, all Versions 17.10 -- > so this indicates that it 
is Kernel 4.13
related.


And it seems to affect other distros as well.
The bug also affects OpenSuse, with Kernel 4.13:
https://bugzilla.opensuse.org/show_bug.cgi?id=1058870

So there seems to be something wrong with Kernel 4.13 with the Intel
Graphics 945.

In the openSUSE Bug Report, users state that Kernels 4.11 and 4.12 are
still working.

I will test that right now and report back.

Thank you Community for all the efforts.


** Bug watch added: bugzilla.opensuse.org/ #1058870
   https://bugzilla.opensuse.org/show_bug.cgi?id=1058870

** Attachment added: "Photo of Graphics error."
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/+attachment/4984307/+files/IMG_20171021_232347.jpg

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

Title:
  Graphics problem -  80% of the Left hand side of screen solid black

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

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


[Kernel-packages] [Bug 1722269] PulseList.txt

2017-10-22 Thread YS1
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1722269/+attachment/4984296/+files/PulseList.txt

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

Title:
  No graphical boot with 4.4.0-96 and NVIDIA GeForce 840M

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My computer (using XUbuntu 16.04) boots and works normally with kernel
  4.4.0-92 but upgrading to 4.4.0-96 prevents lightdm from starting. In
  fact, the GPU detection service fails.

  The problem also appears with proposed 4.4.0-97.

  I tested with mainline kernel 4.13. It boots to lightdm but it is
  difficult to exactly tell what happens as some modules for my hardware
  were not found/compiled/installed (as a result, I cannot connect to
  wifi with this kernel).

  GPU is GEForce 840M with proprietary nvidia 475 drivers (purged and
  reinstalled once).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  NonfreeKernelModules: wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yann   1476 F pulseaudio
   /dev/snd/controlC0:  yann   1476 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct  9 15:40:16 2017
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (448 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-92-generic N/A
   linux-backports-modules-4.4.0-92-generic  N/A
   linux-firmware1.157.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yann   1438 F pulseaudio
   /dev/snd/controlC1:  yann   1438 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (450 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-97-generic N/A
   linux-backports-modules-4.4.0-97-generic  N/A
   linux-firmware1.157.12
  Tags:  xenial
  Uname: Linux 4.4.0-97-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (460 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 

[Kernel-packages] [Bug 1722269] UdevDb.txt

2017-10-22 Thread YS1
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1722269/+attachment/4984298/+files/UdevDb.txt

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

Title:
  No graphical boot with 4.4.0-96 and NVIDIA GeForce 840M

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My computer (using XUbuntu 16.04) boots and works normally with kernel
  4.4.0-92 but upgrading to 4.4.0-96 prevents lightdm from starting. In
  fact, the GPU detection service fails.

  The problem also appears with proposed 4.4.0-97.

  I tested with mainline kernel 4.13. It boots to lightdm but it is
  difficult to exactly tell what happens as some modules for my hardware
  were not found/compiled/installed (as a result, I cannot connect to
  wifi with this kernel).

  GPU is GEForce 840M with proprietary nvidia 475 drivers (purged and
  reinstalled once).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  NonfreeKernelModules: wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yann   1476 F pulseaudio
   /dev/snd/controlC0:  yann   1476 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct  9 15:40:16 2017
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (448 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-92-generic N/A
   linux-backports-modules-4.4.0-92-generic  N/A
   linux-firmware1.157.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yann   1438 F pulseaudio
   /dev/snd/controlC1:  yann   1438 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (450 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-97-generic N/A
   linux-backports-modules-4.4.0-97-generic  N/A
   linux-firmware1.157.12
  Tags:  xenial
  Uname: Linux 4.4.0-97-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (460 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 

[Kernel-packages] [Bug 1722269] ProcInterrupts.txt

2017-10-22 Thread YS1
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1722269/+attachment/4984294/+files/ProcInterrupts.txt

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

Title:
  No graphical boot with 4.4.0-96 and NVIDIA GeForce 840M

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My computer (using XUbuntu 16.04) boots and works normally with kernel
  4.4.0-92 but upgrading to 4.4.0-96 prevents lightdm from starting. In
  fact, the GPU detection service fails.

  The problem also appears with proposed 4.4.0-97.

  I tested with mainline kernel 4.13. It boots to lightdm but it is
  difficult to exactly tell what happens as some modules for my hardware
  were not found/compiled/installed (as a result, I cannot connect to
  wifi with this kernel).

  GPU is GEForce 840M with proprietary nvidia 475 drivers (purged and
  reinstalled once).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  NonfreeKernelModules: wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yann   1476 F pulseaudio
   /dev/snd/controlC0:  yann   1476 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct  9 15:40:16 2017
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (448 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-92-generic N/A
   linux-backports-modules-4.4.0-92-generic  N/A
   linux-firmware1.157.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yann   1438 F pulseaudio
   /dev/snd/controlC1:  yann   1438 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (450 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-97-generic N/A
   linux-backports-modules-4.4.0-97-generic  N/A
   linux-firmware1.157.12
  Tags:  xenial
  Uname: Linux 4.4.0-97-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (460 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 

[Kernel-packages] [Bug 1722269] WifiSyslog.txt

2017-10-22 Thread YS1
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1722269/+attachment/4984299/+files/WifiSyslog.txt

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

Title:
  No graphical boot with 4.4.0-96 and NVIDIA GeForce 840M

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My computer (using XUbuntu 16.04) boots and works normally with kernel
  4.4.0-92 but upgrading to 4.4.0-96 prevents lightdm from starting. In
  fact, the GPU detection service fails.

  The problem also appears with proposed 4.4.0-97.

  I tested with mainline kernel 4.13. It boots to lightdm but it is
  difficult to exactly tell what happens as some modules for my hardware
  were not found/compiled/installed (as a result, I cannot connect to
  wifi with this kernel).

  GPU is GEForce 840M with proprietary nvidia 475 drivers (purged and
  reinstalled once).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  NonfreeKernelModules: wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yann   1476 F pulseaudio
   /dev/snd/controlC0:  yann   1476 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct  9 15:40:16 2017
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (448 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-92-generic N/A
   linux-backports-modules-4.4.0-92-generic  N/A
   linux-firmware1.157.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yann   1438 F pulseaudio
   /dev/snd/controlC1:  yann   1438 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (450 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-97-generic N/A
   linux-backports-modules-4.4.0-97-generic  N/A
   linux-firmware1.157.12
  Tags:  xenial
  Uname: Linux 4.4.0-97-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (460 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 

[Kernel-packages] [Bug 1722269] ProcEnviron.txt

2017-10-22 Thread YS1
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1722269/+attachment/4984293/+files/ProcEnviron.txt

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

Title:
  No graphical boot with 4.4.0-96 and NVIDIA GeForce 840M

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My computer (using XUbuntu 16.04) boots and works normally with kernel
  4.4.0-92 but upgrading to 4.4.0-96 prevents lightdm from starting. In
  fact, the GPU detection service fails.

  The problem also appears with proposed 4.4.0-97.

  I tested with mainline kernel 4.13. It boots to lightdm but it is
  difficult to exactly tell what happens as some modules for my hardware
  were not found/compiled/installed (as a result, I cannot connect to
  wifi with this kernel).

  GPU is GEForce 840M with proprietary nvidia 475 drivers (purged and
  reinstalled once).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  NonfreeKernelModules: wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yann   1476 F pulseaudio
   /dev/snd/controlC0:  yann   1476 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct  9 15:40:16 2017
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (448 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-92-generic N/A
   linux-backports-modules-4.4.0-92-generic  N/A
   linux-firmware1.157.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yann   1438 F pulseaudio
   /dev/snd/controlC1:  yann   1438 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (450 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-97-generic N/A
   linux-backports-modules-4.4.0-97-generic  N/A
   linux-firmware1.157.12
  Tags:  xenial
  Uname: Linux 4.4.0-97-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (460 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 

[Kernel-packages] [Bug 1722269] Re: No graphical boot with 4.4.0-96 and NVIDIA GeForce 840M

2017-10-22 Thread YS1
Here is apport information for -92 kernel with NVIDIA 387 ; this boots
normally and the driver works.

BTW here is dkms status :
bbswitch, 0.8, 4.13.0-041300-generic, x86_64: installed
bbswitch, 0.8, 4.4.0-63-generic, x86_64: installed
bbswitch, 0.8, 4.4.0-77-generic, x86_64: installed
bbswitch, 0.8, 4.4.0-79-generic, x86_64: installed
bbswitch, 0.8, 4.4.0-87-generic, x86_64: installed
bbswitch, 0.8, 4.4.0-89-generic, x86_64: installed
bbswitch, 0.8, 4.4.0-91-generic, x86_64: installed
bbswitch, 0.8, 4.4.0-92-generic, x86_64: installed
bbswitch, 0.8, 4.4.0-96-generic, x86_64: installed
bbswitch, 0.8, 4.4.0-97-generic, x86_64: installed
bbswitch, 0.8, 4.4.0-98-generic, x86_64: installed
bcmwl, 6.30.223.271+bdcom, 4.4.0-63-generic, x86_64: installed
bcmwl, 6.30.223.271+bdcom, 4.4.0-77-generic, x86_64: installed
bcmwl, 6.30.223.271+bdcom, 4.4.0-79-generic, x86_64: installed
bcmwl, 6.30.223.271+bdcom, 4.4.0-87-generic, x86_64: installed
bcmwl, 6.30.223.271+bdcom, 4.4.0-89-generic, x86_64: installed
bcmwl, 6.30.223.271+bdcom, 4.4.0-91-generic, x86_64: installed
bcmwl, 6.30.223.271+bdcom, 4.4.0-92-generic, x86_64: installed
bcmwl, 6.30.223.271+bdcom, 4.4.0-96-generic, x86_64: installed
bcmwl, 6.30.223.271+bdcom, 4.4.0-97-generic, x86_64: installed
bcmwl, 6.30.223.271+bdcom, 4.4.0-98-generic, x86_64: installed
nvidia-387, 387.12, 4.13.0-041300-generic, x86_64: installed
nvidia-387, 387.12, 4.4.0-92-generic, x86_64: installed
nvidia-387, 387.12, 4.4.0-98-generic, x86_64: installed
virtualbox, 5.0.40, 4.4.0-77-generic, x86_64: installed
virtualbox, 5.0.40, 4.4.0-79-generic, x86_64: installed
virtualbox, 5.0.40, 4.4.0-87-generic, x86_64: installed
virtualbox, 5.0.40, 4.4.0-89-generic, x86_64: installed
virtualbox, 5.0.40, 4.4.0-91-generic, x86_64: installed
virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
virtualbox, 5.0.40, 4.4.0-96-generic, x86_64: installed
virtualbox, 5.0.40, 4.4.0-97-generic, x86_64: installed
virtualbox, 5.0.40, 4.4.0-98-generic, x86_64: installed

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

Title:
  No graphical boot with 4.4.0-96 and NVIDIA GeForce 840M

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My computer (using XUbuntu 16.04) boots and works normally with kernel
  4.4.0-92 but upgrading to 4.4.0-96 prevents lightdm from starting. In
  fact, the GPU detection service fails.

  The problem also appears with proposed 4.4.0-97.

  I tested with mainline kernel 4.13. It boots to lightdm but it is
  difficult to exactly tell what happens as some modules for my hardware
  were not found/compiled/installed (as a result, I cannot connect to
  wifi with this kernel).

  GPU is GEForce 840M with proprietary nvidia 475 drivers (purged and
  reinstalled once).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  NonfreeKernelModules: wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yann   1476 F pulseaudio
   /dev/snd/controlC0:  yann   1476 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct  9 15:40:16 2017
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (448 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-92-generic N/A
   linux-backports-modules-4.4.0-92-generic  N/A
   linux-firmware1.157.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yann   1438 F pulseaudio
   /dev/snd/controlC1:  yann   1438 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (450 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  

[Kernel-packages] [Bug 1722269] ProcCpuinfo.txt

2017-10-22 Thread YS1
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1722269/+attachment/4984291/+files/ProcCpuinfo.txt

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

Title:
  No graphical boot with 4.4.0-96 and NVIDIA GeForce 840M

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My computer (using XUbuntu 16.04) boots and works normally with kernel
  4.4.0-92 but upgrading to 4.4.0-96 prevents lightdm from starting. In
  fact, the GPU detection service fails.

  The problem also appears with proposed 4.4.0-97.

  I tested with mainline kernel 4.13. It boots to lightdm but it is
  difficult to exactly tell what happens as some modules for my hardware
  were not found/compiled/installed (as a result, I cannot connect to
  wifi with this kernel).

  GPU is GEForce 840M with proprietary nvidia 475 drivers (purged and
  reinstalled once).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  NonfreeKernelModules: wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yann   1476 F pulseaudio
   /dev/snd/controlC0:  yann   1476 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct  9 15:40:16 2017
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (448 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-92-generic N/A
   linux-backports-modules-4.4.0-92-generic  N/A
   linux-firmware1.157.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yann   1438 F pulseaudio
   /dev/snd/controlC1:  yann   1438 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (450 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-97-generic N/A
   linux-backports-modules-4.4.0-97-generic  N/A
   linux-firmware1.157.12
  Tags:  xenial
  Uname: Linux 4.4.0-97-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (460 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 

[Kernel-packages] [Bug 1722269] RfKill.txt

2017-10-22 Thread YS1
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1722269/+attachment/4984297/+files/RfKill.txt

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

Title:
  No graphical boot with 4.4.0-96 and NVIDIA GeForce 840M

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My computer (using XUbuntu 16.04) boots and works normally with kernel
  4.4.0-92 but upgrading to 4.4.0-96 prevents lightdm from starting. In
  fact, the GPU detection service fails.

  The problem also appears with proposed 4.4.0-97.

  I tested with mainline kernel 4.13. It boots to lightdm but it is
  difficult to exactly tell what happens as some modules for my hardware
  were not found/compiled/installed (as a result, I cannot connect to
  wifi with this kernel).

  GPU is GEForce 840M with proprietary nvidia 475 drivers (purged and
  reinstalled once).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  NonfreeKernelModules: wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yann   1476 F pulseaudio
   /dev/snd/controlC0:  yann   1476 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct  9 15:40:16 2017
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (448 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-92-generic N/A
   linux-backports-modules-4.4.0-92-generic  N/A
   linux-firmware1.157.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yann   1438 F pulseaudio
   /dev/snd/controlC1:  yann   1438 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (450 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-97-generic N/A
   linux-backports-modules-4.4.0-97-generic  N/A
   linux-firmware1.157.12
  Tags:  xenial
  Uname: Linux 4.4.0-97-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (460 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 

[Kernel-packages] [Bug 1722269] ProcCpuinfoMinimal.txt

2017-10-22 Thread YS1
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1722269/+attachment/4984292/+files/ProcCpuinfoMinimal.txt

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

Title:
  No graphical boot with 4.4.0-96 and NVIDIA GeForce 840M

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My computer (using XUbuntu 16.04) boots and works normally with kernel
  4.4.0-92 but upgrading to 4.4.0-96 prevents lightdm from starting. In
  fact, the GPU detection service fails.

  The problem also appears with proposed 4.4.0-97.

  I tested with mainline kernel 4.13. It boots to lightdm but it is
  difficult to exactly tell what happens as some modules for my hardware
  were not found/compiled/installed (as a result, I cannot connect to
  wifi with this kernel).

  GPU is GEForce 840M with proprietary nvidia 475 drivers (purged and
  reinstalled once).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  NonfreeKernelModules: wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yann   1476 F pulseaudio
   /dev/snd/controlC0:  yann   1476 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct  9 15:40:16 2017
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (448 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-92-generic N/A
   linux-backports-modules-4.4.0-92-generic  N/A
   linux-firmware1.157.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yann   1438 F pulseaudio
   /dev/snd/controlC1:  yann   1438 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (450 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-97-generic N/A
   linux-backports-modules-4.4.0-97-generic  N/A
   linux-firmware1.157.12
  Tags:  xenial
  Uname: Linux 4.4.0-97-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (460 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: 

[Kernel-packages] [Bug 1722269] ProcModules.txt

2017-10-22 Thread YS1
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1722269/+attachment/4984295/+files/ProcModules.txt

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

Title:
  No graphical boot with 4.4.0-96 and NVIDIA GeForce 840M

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My computer (using XUbuntu 16.04) boots and works normally with kernel
  4.4.0-92 but upgrading to 4.4.0-96 prevents lightdm from starting. In
  fact, the GPU detection service fails.

  The problem also appears with proposed 4.4.0-97.

  I tested with mainline kernel 4.13. It boots to lightdm but it is
  difficult to exactly tell what happens as some modules for my hardware
  were not found/compiled/installed (as a result, I cannot connect to
  wifi with this kernel).

  GPU is GEForce 840M with proprietary nvidia 475 drivers (purged and
  reinstalled once).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  NonfreeKernelModules: wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yann   1476 F pulseaudio
   /dev/snd/controlC0:  yann   1476 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct  9 15:40:16 2017
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (448 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-92-generic N/A
   linux-backports-modules-4.4.0-92-generic  N/A
   linux-firmware1.157.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yann   1438 F pulseaudio
   /dev/snd/controlC1:  yann   1438 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (450 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-97-generic N/A
   linux-backports-modules-4.4.0-97-generic  N/A
   linux-firmware1.157.12
  Tags:  xenial
  Uname: Linux 4.4.0-97-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (460 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 

[Kernel-packages] [Bug 1722269] IwConfig.txt

2017-10-22 Thread YS1
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1722269/+attachment/4984287/+files/IwConfig.txt

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

Title:
  No graphical boot with 4.4.0-96 and NVIDIA GeForce 840M

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My computer (using XUbuntu 16.04) boots and works normally with kernel
  4.4.0-92 but upgrading to 4.4.0-96 prevents lightdm from starting. In
  fact, the GPU detection service fails.

  The problem also appears with proposed 4.4.0-97.

  I tested with mainline kernel 4.13. It boots to lightdm but it is
  difficult to exactly tell what happens as some modules for my hardware
  were not found/compiled/installed (as a result, I cannot connect to
  wifi with this kernel).

  GPU is GEForce 840M with proprietary nvidia 475 drivers (purged and
  reinstalled once).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  NonfreeKernelModules: wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yann   1476 F pulseaudio
   /dev/snd/controlC0:  yann   1476 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct  9 15:40:16 2017
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (448 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-92-generic N/A
   linux-backports-modules-4.4.0-92-generic  N/A
   linux-firmware1.157.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yann   1438 F pulseaudio
   /dev/snd/controlC1:  yann   1438 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (450 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-97-generic N/A
   linux-backports-modules-4.4.0-97-generic  N/A
   linux-firmware1.157.12
  Tags:  xenial
  Uname: Linux 4.4.0-97-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (460 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 

[Kernel-packages] [Bug 1722269] Lspci.txt

2017-10-22 Thread YS1
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1722269/+attachment/4984289/+files/Lspci.txt

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

Title:
  No graphical boot with 4.4.0-96 and NVIDIA GeForce 840M

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My computer (using XUbuntu 16.04) boots and works normally with kernel
  4.4.0-92 but upgrading to 4.4.0-96 prevents lightdm from starting. In
  fact, the GPU detection service fails.

  The problem also appears with proposed 4.4.0-97.

  I tested with mainline kernel 4.13. It boots to lightdm but it is
  difficult to exactly tell what happens as some modules for my hardware
  were not found/compiled/installed (as a result, I cannot connect to
  wifi with this kernel).

  GPU is GEForce 840M with proprietary nvidia 475 drivers (purged and
  reinstalled once).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  NonfreeKernelModules: wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yann   1476 F pulseaudio
   /dev/snd/controlC0:  yann   1476 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct  9 15:40:16 2017
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (448 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-92-generic N/A
   linux-backports-modules-4.4.0-92-generic  N/A
   linux-firmware1.157.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yann   1438 F pulseaudio
   /dev/snd/controlC1:  yann   1438 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (450 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-97-generic N/A
   linux-backports-modules-4.4.0-97-generic  N/A
   linux-firmware1.157.12
  Tags:  xenial
  Uname: Linux 4.4.0-97-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (460 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 

[Kernel-packages] [Bug 1722269] CurrentDmesg.txt

2017-10-22 Thread YS1
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1722269/+attachment/4984286/+files/CurrentDmesg.txt

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

Title:
  No graphical boot with 4.4.0-96 and NVIDIA GeForce 840M

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My computer (using XUbuntu 16.04) boots and works normally with kernel
  4.4.0-92 but upgrading to 4.4.0-96 prevents lightdm from starting. In
  fact, the GPU detection service fails.

  The problem also appears with proposed 4.4.0-97.

  I tested with mainline kernel 4.13. It boots to lightdm but it is
  difficult to exactly tell what happens as some modules for my hardware
  were not found/compiled/installed (as a result, I cannot connect to
  wifi with this kernel).

  GPU is GEForce 840M with proprietary nvidia 475 drivers (purged and
  reinstalled once).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  NonfreeKernelModules: wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yann   1476 F pulseaudio
   /dev/snd/controlC0:  yann   1476 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct  9 15:40:16 2017
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (448 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-92-generic N/A
   linux-backports-modules-4.4.0-92-generic  N/A
   linux-firmware1.157.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yann   1438 F pulseaudio
   /dev/snd/controlC1:  yann   1438 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (450 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-97-generic N/A
   linux-backports-modules-4.4.0-97-generic  N/A
   linux-firmware1.157.12
  Tags:  xenial
  Uname: Linux 4.4.0-97-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (460 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 

[Kernel-packages] [Bug 1722269] Lsusb.txt

2017-10-22 Thread YS1
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1722269/+attachment/4984290/+files/Lsusb.txt

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

Title:
  No graphical boot with 4.4.0-96 and NVIDIA GeForce 840M

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My computer (using XUbuntu 16.04) boots and works normally with kernel
  4.4.0-92 but upgrading to 4.4.0-96 prevents lightdm from starting. In
  fact, the GPU detection service fails.

  The problem also appears with proposed 4.4.0-97.

  I tested with mainline kernel 4.13. It boots to lightdm but it is
  difficult to exactly tell what happens as some modules for my hardware
  were not found/compiled/installed (as a result, I cannot connect to
  wifi with this kernel).

  GPU is GEForce 840M with proprietary nvidia 475 drivers (purged and
  reinstalled once).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  NonfreeKernelModules: wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yann   1476 F pulseaudio
   /dev/snd/controlC0:  yann   1476 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct  9 15:40:16 2017
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (448 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-92-generic N/A
   linux-backports-modules-4.4.0-92-generic  N/A
   linux-firmware1.157.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yann   1438 F pulseaudio
   /dev/snd/controlC1:  yann   1438 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (450 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-97-generic N/A
   linux-backports-modules-4.4.0-97-generic  N/A
   linux-firmware1.157.12
  Tags:  xenial
  Uname: Linux 4.4.0-97-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (460 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 

[Kernel-packages] [Bug 1722269] CRDA.txt

2017-10-22 Thread YS1
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1722269/+attachment/4984285/+files/CRDA.txt

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

Title:
  No graphical boot with 4.4.0-96 and NVIDIA GeForce 840M

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My computer (using XUbuntu 16.04) boots and works normally with kernel
  4.4.0-92 but upgrading to 4.4.0-96 prevents lightdm from starting. In
  fact, the GPU detection service fails.

  The problem also appears with proposed 4.4.0-97.

  I tested with mainline kernel 4.13. It boots to lightdm but it is
  difficult to exactly tell what happens as some modules for my hardware
  were not found/compiled/installed (as a result, I cannot connect to
  wifi with this kernel).

  GPU is GEForce 840M with proprietary nvidia 475 drivers (purged and
  reinstalled once).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  NonfreeKernelModules: wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yann   1476 F pulseaudio
   /dev/snd/controlC0:  yann   1476 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct  9 15:40:16 2017
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (448 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-92-generic N/A
   linux-backports-modules-4.4.0-92-generic  N/A
   linux-firmware1.157.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yann   1438 F pulseaudio
   /dev/snd/controlC1:  yann   1438 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (450 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-97-generic N/A
   linux-backports-modules-4.4.0-97-generic  N/A
   linux-firmware1.157.12
  Tags:  xenial
  Uname: Linux 4.4.0-97-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (460 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 

[Kernel-packages] [Bug 1722269] JournalErrors.txt

2017-10-22 Thread YS1
apport information

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

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

Title:
  No graphical boot with 4.4.0-96 and NVIDIA GeForce 840M

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My computer (using XUbuntu 16.04) boots and works normally with kernel
  4.4.0-92 but upgrading to 4.4.0-96 prevents lightdm from starting. In
  fact, the GPU detection service fails.

  The problem also appears with proposed 4.4.0-97.

  I tested with mainline kernel 4.13. It boots to lightdm but it is
  difficult to exactly tell what happens as some modules for my hardware
  were not found/compiled/installed (as a result, I cannot connect to
  wifi with this kernel).

  GPU is GEForce 840M with proprietary nvidia 475 drivers (purged and
  reinstalled once).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  NonfreeKernelModules: wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yann   1476 F pulseaudio
   /dev/snd/controlC0:  yann   1476 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct  9 15:40:16 2017
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (448 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-92-generic N/A
   linux-backports-modules-4.4.0-92-generic  N/A
   linux-firmware1.157.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yann   1438 F pulseaudio
   /dev/snd/controlC1:  yann   1438 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (450 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-97-generic N/A
   linux-backports-modules-4.4.0-97-generic  N/A
   linux-firmware1.157.12
  Tags:  xenial
  Uname: Linux 4.4.0-97-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (460 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 

[Kernel-packages] [Bug 1722269] Re: No graphical boot with 4.4.0-96 and NVIDIA GeForce 840M

2017-10-22 Thread YS1
apport information

** Description changed:

  My computer (using XUbuntu 16.04) boots and works normally with kernel
  4.4.0-92 but upgrading to 4.4.0-96 prevents lightdm from starting. In
  fact, the GPU detection service fails.
  
  The problem also appears with proposed 4.4.0-97.
  
  I tested with mainline kernel 4.13. It boots to lightdm but it is
  difficult to exactly tell what happens as some modules for my hardware
  were not found/compiled/installed (as a result, I cannot connect to wifi
  with this kernel).
  
  GPU is GEForce 840M with proprietary nvidia 475 drivers (purged and
  reinstalled once).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  NonfreeKernelModules: wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yann   1476 F pulseaudio
   /dev/snd/controlC0:  yann   1476 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct  9 15:40:16 2017
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (448 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-92-generic N/A
   linux-backports-modules-4.4.0-92-generic  N/A
   linux-firmware1.157.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yann   1438 F pulseaudio
   /dev/snd/controlC1:  yann   1438 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (450 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-97-generic N/A
   linux-backports-modules-4.4.0-97-generic  N/A
   linux-firmware1.157.12
  Tags:  xenial
  Uname: Linux 4.4.0-97-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (460 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmware1.157.13
  Tags:  xenial
  Uname: Linux 4.4.0-98-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  

[Kernel-packages] [Bug 1724911] Re: text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

2017-10-22 Thread Steve Langasek
04759194dc447ff0b9ef35bc641ce3bb076c2930 is bad; same symptoms as
edc2988c548db05e33b921fed15821010bc74895.

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

Title:
  text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

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

Bug description:
  After upgrading my laptop to Ubuntu 17.10, I am unable to access
  gettys on any of the text-mode VTs on my system.

  gdm3 is running on VT1, my user session is running on VT2.  I can
  switch between these.  If I switch to VT3, I know that the VT switch
  has happened in the kernel because the X cursor disappears; but the
  display retains the output of my X session, and the text console with
  getty never appears.

  Switching back to VT2 works fine.

  The same problem occurs with either Wayland or X.

  My laptop is docked with an external monitor, which could be a factor.
  (I also notice that during boot, plymouth is only rendered on the
  internal monitor, not the external monitor; this may be related).  I
  have not yet tested whether this problem is reproducible if I undock.

  The system is booting with vt.handoff=7, which I believe is still the
  default in Ubuntu 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vorlon24080 F pulseaudio
   /dev/snd/controlC0:  vorlon24080 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 09:57:59 2017
  HibernationDevice: RESUME=UUID=6df76279-19ea-45a4-bec9-e4fdc858729a
  InstallationDate: Installed on 2010-09-24 (2582 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]

2017-10-22 Thread GPratique
@Konrad: thanks for taking the time to explain the situation details.

However I have to report that when switching to Windows 10, on the exact
same PC (just a drive swap), Bluetooth performs flawlessly with both my
speakers (JBL Flip 3 and UE Miniboom).

This suggests that it is not a hardware problem but a software one.

FYI this problem sits high on the Pulseaudio bug list, but...


Best Regards,

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

Title:
  A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in
  audio stream"]

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped
  working properly. It was working fine in Jaunty.

  My headphones are detected and configured by pulse, but the audio
  skips as if it's spending half of each second paused. Music is
  buffered so that after I click stop on rhythmbox (or whatever--it
  happens with whatever player I use) the audio continues until it's
  caught up.

  syslog is full of the following lines:
  Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal 
latency to 1.00 ms
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
15128 us (= 2668 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36586 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
35593 us (= 6276 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36597 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32601 us (= 5748 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32589 us (= 5748 bytes) in audio stream

  This is with
  bluez 4.45-0ubuntu4
  pulseaudio1:0.9.15-4ubuntu2 0

  pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev
  didn't help.

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

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


[Kernel-packages] [Bug 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

2017-10-22 Thread Franck Charras
Ryzen CPUs manufactured before week 24 of this year were known to have
issues (especially the segfault issue). It was officially fixed for all
ryzen manufactured after week 30. All my ryzen are pre-24 CPUs and they
all have this silent crash issue. Does it also happen with the post week
30 ryzen ? (@tgui what is yours ?)

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-041100-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu 

[Kernel-packages] [Bug 1722269] Re: No graphical boot with 4.4.0-96 and NVIDIA GeForce 840M

2017-10-22 Thread Kai-Heng Feng
bbswitch is not happy:
[4.379608] bbswitch: version 0.8
[4.379618] bbswitch: Found integrated VGA device :00:02.0: 
\_SB_.PCI0.GFX0
[4.379627] bbswitch: Found discrete VGA device :03:00.0: 
\_SB_.PCI0.RP05.D034
[4.379640] bbswitch: failed to evaluate \_SB_.PCI0.RP05.D034._DSM 
{0xF8,0xD8,0x86,0xA4,0xDA,0x0B,0x1B,0x47,0xA7,0x2B,0x60,0x42,0xA6,0xB5,0xBE,0xE0}
 0x100 0x0 {0x00,0x00,0x00,0x00}: AE_NOT_FOUND
[4.379648] bbswitch: failed to evaluate \_SB_.PCI0.RP05.D034._DSM 
{0xA0,0xA0,0x95,0x9D,0x60,0x00,0x48,0x4D,0xB3,0x4D,0x7E,0x5F,0xEA,0x12,0x9F,0xD4}
 0x102 0x0 {0x00,0x00,0x00,0x00}: AE_NOT_FOUND
[4.379657] bbswitch: failed to evaluate \_SB_.PCI0.GFX0._DSM 
{0xA0,0xA0,0x95,0x9D,0x60,0x00,0x48,0x4D,0xB3,0x4D,0x7E,0x5F,0xEA,0x12,0x9F,0xD4}
 0x102 0x0 {0x00,0x00,0x00,0x00}: AE_NOT_FOUND
[4.379658] bbswitch: No suitable _DSM call found.

Can you try to boot under 4.4.0-92?
Probably a cpu-manager/bbswitch issue instead of a kernel one.

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

Title:
  No graphical boot with 4.4.0-96 and NVIDIA GeForce 840M

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My computer (using XUbuntu 16.04) boots and works normally with kernel
  4.4.0-92 but upgrading to 4.4.0-96 prevents lightdm from starting. In
  fact, the GPU detection service fails.

  The problem also appears with proposed 4.4.0-97.

  I tested with mainline kernel 4.13. It boots to lightdm but it is
  difficult to exactly tell what happens as some modules for my hardware
  were not found/compiled/installed (as a result, I cannot connect to
  wifi with this kernel).

  GPU is GEForce 840M with proprietary nvidia 475 drivers (purged and
  reinstalled once).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  NonfreeKernelModules: wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yann   1476 F pulseaudio
   /dev/snd/controlC0:  yann   1476 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct  9 15:40:16 2017
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (448 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-92-generic N/A
   linux-backports-modules-4.4.0-92-generic  N/A
   linux-firmware1.157.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yann   1438 F pulseaudio
   /dev/snd/controlC1:  yann   1438 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (450 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-97-generic N/A
   linux-backports-modules-4.4.0-97-generic  N/A
   linux-firmware1.157.12
  Tags:  xenial
  Uname: Linux 4.4.0-97-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: